Bug 2226403

Created attachment 1979588 [details]
build.log

Created attachment 1979589 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Created attachment 1979590 [details]
state.log

Seeing an attempt to fix this [1], the commit is missing the patches.


[1] https://src.fedoraproject.org/rpms/rubygem-nifti/c/e41083463bb62845f6de5597c6b7eebca739e743?branch=rawhide

(In reply to Vít Ondruch from comment #4)
> Seeing an attempt to fix this [1], the commit is missing the patches.
> 
> 
> [1]
> https://src.fedoraproject.org/rpms/rubygem-nifti/c/
> e41083463bb62845f6de5597c6b7eebca739e743?branch=rawhide

Hi Vit, it's very odd. Using the fedpkg command, I can't add patches. They can be found here at the link: https://ilgrad.fedorapeople.org/specs/rubygem-nifti/

Hi Ilya,

Text files like patches can (should) be added to the src repo using `git add` etc. Binary files (like tars) can be uploaded to the look aside cache with `fedpkg new-sources`.

Cheers,

(In reply to Ankur Sinha (FranciscoD) from comment #6)
> Hi Ilya,
> 
> Text files like patches can (should) be added to the src repo using `git
> add` etc. Binary files (like tars) can be uploaded to the look aside cache
> with `fedpkg new-sources`.
> 
> Cheers,

Hi Ankur, thank you. I seem to be doing everything as before, but I still can't upload these patches. Maybe someone else can try to do it, I don't understand what I'm doing wrong. Locally everything builds well (fedpkg mockbuild).

(In reply to Ilia Gradina from comment #7)
> (In reply to Ankur Sinha (FranciscoD) from comment #6)
> > Hi Ilya,
> > 
> > Text files like patches can (should) be added to the src repo using `git
> > add` etc. Binary files (like tars) can be uploaded to the look aside cache
> > with `fedpkg new-sources`.
> > 
> > Cheers,
> 
> Hi Ankur, thank you. I seem to be doing everything as before, but I still
> can't upload these patches. Maybe someone else can try to do it, I don't
> understand what I'm doing wrong. Locally everything builds well (fedpkg
> mockbuild).

Sorry, figured it out - the patches were getting into .gitignore. Terrible)

FEDORA-2023-c6ec347650 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c6ec347650

FEDORA-2023-c6ec347650 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c6ec347650`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c6ec347650

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

The workflow I am using trying to not forget anything is:

1. fedpkg srpm
2. git add -u
3. fedpkg clog
4. git commit -F clog
5. fedpkg import some.srpm
6. git commit --am

This should take care of everything. Not sure what could have caused your issues with .gitignore.

BTW it still does not seems to be fixed everywhere. I suspect that you did your changes during branching period, so while you have f39 build, there is not associated Bodhi update and there still needs to be done the f40 / Rawhide build (don't forget to `git pull` prior doing any changes).

(In reply to Vít Ondruch from comment #12)
> BTW it still does not seems to be fixed everywhere. I suspect that you did
> your changes during branching period, so while you have f39 build, there is
> not associated Bodhi update and there still needs to be done the f40 /
> Rawhide build (don't forget to `git pull` prior doing any changes).

Or let me know and I can put everything in order for you ;)

(In reply to Vít Ondruch from comment #13)
> (In reply to Vít Ondruch from comment #12)
> > BTW it still does not seems to be fixed everywhere. I suspect that you did
> > your changes during branching period, so while you have f39 build, there is
> > not associated Bodhi update and there still needs to be done the f40 /
> > Rawhide build (don't forget to `git pull` prior doing any changes).
> 
> Or let me know and I can put everything in order for you ;)

Hi Vit! Thank you for the help). I've built for f40, but I can't add an update to bodhi for f39. I receive the following message:
Builds: Cannot manually create updates for a Release which is not composed by Bodhi. Read the 'Automatic updates' page in Bodhi docs about this error.
Can you help with adding a build for f39?

Until the Bodhi updates-testing activation point (https://fedorapeople.org/groups/schedule/f-39/f-39-key-tasks.html), Bodhi updates will be automatically created when you do a build for F39.

The weird thing is, your F39 build got tagged into f40-updates-candidate like a F40 build, instead of into f39-updates-candidate, which is why there is no automatic F39 Bodhi update for it: https://koji.fedoraproject.org/koji/buildinfo?buildID=2270956

Why that happened, I have no idea.

(In reply to Ilia Gradina from comment #14)
> (In reply to Vít Ondruch from comment #13)
> > (In reply to Vít Ondruch from comment #12)
> > > BTW it still does not seems to be fixed everywhere. I suspect that you did
> > > your changes during branching period, so while you have f39 build, there is
> > > not associated Bodhi update and there still needs to be done the f40 /
> > > Rawhide build (don't forget to `git pull` prior doing any changes).
> > 
> > Or let me know and I can put everything in order for you ;)
> 
> Hi Vit! Thank you for the help). I've built for f40

Thx!

> but I can't add an
> update to bodhi for f39. I receive the following message:
> Builds: Cannot manually create updates for a Release which is not composed
> by Bodhi. Read the 'Automatic updates' page in Bodhi docs about this error.
> Can you help with adding a build for f39?

Interesting. I guess the "easy" path is to bump the release and build (for F40 as well as F39). The other option could be to open Releng ticket (https://pagure.io/releng/issue/)

(In reply to Vít Ondruch from comment #16)
> I guess the "easy" path is to bump the release and build (for
> F40 as well as F39)

Just to clarify the bump and build for F40 is not strictly needed, but it is the right thing to do to preserve the upgrade path.

This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

FEDORA-2023-c6ec347650 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.