On Thu, Jun 17, 2021 at 02:05:16PM +0200, Fabio Valentini wrote:
On Thu, Jun 17, 2021 at 1:57 PM Ewoud Kohl van Wijngaarden
<ewoud+fedora@xxxxxxxxxxxxxxxxxxxxx> wrote:
Hello everyone,
As someone who just got started, I'm looking for some help.
I'd like to update packages. I'm used to git, so my typical flow is to
make sure I have some clean branch to start working from (clone is just
for completeness):
fedpkg clone mypackage
cd mypackage
git checkout -b rawhide-update-to-new-version
rpmdev-bumpspec -n 1.2.3 mypackage.spec
Now comes the part I'm not sure about. To fetch the new sources I
usually perform:
spectool -g mypackage.spec
After that, I'm looking for a command to update the sources file with
new checksums so I can run:
fedpkg --release f35 mockbuild
I could not find such a command so until now I've been using sha512sum
manually, but there must be a better way :)
I assume you're looking for the "fedpkg new-sources" subcommand.
Using sha512sum alone is not doing everything you need, i.e. it's not
uploading the sources to the dist-git lookaside cache, so not using
"fedpkg new-sources" but only fiddling with the "sources" file
manually would result in broken builds, because the build system would
not find those sources.
To be clear: I don't want to fiddle with the sources file, hence this
email. However, I would like to at least complete a local mockbuild
before uploading to the lookaside cache. It is my understanding that
new-sources always does this.
PS: I would recommend not creating custom branches, not even locally.
If you ever accidentally push such a branch, you might not be able to
delete it, *ever*. Additionally, if you stick to the normal "rawhide",
"f34", "f33" branches, then "fedpkg mockbuild" will infer the
"--release fXX" argument for you instead of you having to specify it
manually.
This feels very odd to me as a new contributor but very familiar with
git.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
