Flatpak build missing files #9542

Closed
opened 2020-12-18 13:30:21 +00:00 by kalev · 4 comments

In gnome-music-master-3320201217190641.1 build, /app/lib/python3.9/site-packages/gnomemusic/grilowrappers/grltrackerplaylists.py has gone missing. The file is correctly there in the matching module build rpm, gnome-music-3.38.2-1.module_f33+10852+7d381cf3.x86_64.rpm.

I have double checked and the file is missing in the payload inside oci-image-sha256_ec8005dd15e30e671e05e1645bad1fe33755f195bbd78571eec0a61386080305.x86_64.tar.gz in bfbada7e144daf746c404f0c6b9464ec721f5935a84846a439fd8740219a37d4 file, so it's not a client side (flatpak cli) issue.

Koji tasks for the matching module build and container build are here:
gnome-music-master-3320201217190641.1: https://koji.fedoraproject.org/koji/buildinfo?buildID=1659959
gnome-music-3.38.2-1.module_f33+10852+7d381cf3: https://koji.fedoraproject.org/koji/buildinfo?buildID=1659135

I don't see anything suspicious in the logs.

@otaylor Any ideas? :)

In gnome-music-master-3320201217190641.1 build, /app/lib/python3.9/site-packages/gnomemusic/grilowrappers/grltrackerplaylists.py has gone missing. The file is correctly there in the matching module build rpm, gnome-music-3.38.2-1.module_f33+10852+7d381cf3.x86_64.rpm. I have double checked and the file is missing in the payload inside oci-image-sha256_ec8005dd15e30e671e05e1645bad1fe33755f195bbd78571eec0a61386080305.x86_64.tar.gz in bfbada7e144daf746c404f0c6b9464ec721f5935a84846a439fd8740219a37d4 file, so it's not a client side (flatpak cli) issue. Koji tasks for the matching module build and container build are here: gnome-music-master-3320201217190641.1: https://koji.fedoraproject.org/koji/buildinfo?buildID=1659959 gnome-music-3.38.2-1.module_f33+10852+7d381cf3: https://koji.fedoraproject.org/koji/buildinfo?buildID=1659135 I don't see anything suspicious in the logs. @otaylor Any ideas? :)

It seems to me that this, issue 9532 and issue 9538 are all the same thing. What that same thing is not apparent to me yet :-)

It seems to me that this, issue 9532 and issue 9538 are all the same thing. What that same thing is not apparent to me yet :-)

Let's retest once we have the buildroot updated with the fix for issue 9532, and see if that fixes this issue too. I don't quite understand how this exact symptom would be triggered, but it seems very related.

Let's retest once we have the buildroot updated with the fix for issue 9532, and see if that fixes this issue too. I don't quite understand how this exact symptom would be triggered, but it seems very related.

Updated buildroot with the fix from #9532 fixes this - this can be closed.

(Hopefully there aren't other places where we've built things recently and files are missing - at worst, they should be resolved as things get naturally rebuilt)

Updated buildroot with the fix from #9532 fixes this - this can be closed. (Hopefully there aren't other places where we've built things recently and files are missing - at worst, they should be resolved as things get naturally rebuilt)

Metadata Update from @mobrien:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @mobrien**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#9542
No description provided.