ubuntustudio-bugs team mailing list archive
-
ubuntustudio-bugs team
-
Mailing list archive
-
Message #12632
[Bug 2103747] Re: Regression: germinate failing to resolve packages correctly
Thanks, Julian.
Based on that I'm going to go ahead and add `ubuntustudio-meta` to the
bug with "Fix Released" just to keep track from my side as that means
the bug *was* valid with ubuntustudio-meta.
However, I'm going to leave the germinate component as it appears to be
a bug in the test case per our (brief) discussion on Matrix.
** Also affects: ubuntustudio-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntustudio-meta (Ubuntu)
Status: New => Fix Released
** Summary changed:
- Regression: germinate failing to resolve packages correctly
+ germinate fails to report error in improperly-specified archs
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to ubuntustudio-meta in Ubuntu.
Matching subscriptions: UbuntuStudioPackages
https://bugs.launchpad.net/bugs/2103747
Title:
germinate fails to report error in improperly-specified archs
Status in germinate package in Ubuntu:
New
Status in ubuntustudio-meta package in Ubuntu:
Fix Released
Bug description:
Florent 'Skia' Jacquet and Athos Ribeiro uploaded a new version of
ubuntustudio-meta, version 25.04.10 [1]. This version, after 'update'
was run, reported 'digikam' as removed from photography-recommends. I
noticed this when, on my plucky installation, it had been made a
candidate for autoremoval.
I then, after investigating, imported the diff from 25.04.10 and ran
'update' with an older debootstrap version, this one in noble. The
difference there was that this one re-added 'digikam' to photography-
recommends, so I re-uploaded it.[2]
However, running 'update' on a plucky machine caused it to disappear
again. This confirmed the bug for me:
$ ./update
[snip]
Removed digikam from photography-recommends
As this makes no sense since there is no difference other than the
debootstrap version, I have concluded that the issue lies in
debootstrap, 1.0.134ubuntu1 (noble) versus 1.0.140 (plucky).
As this involves two different germinate versions, 2.44 (noble) versus
2.46 (plucky), I'm adding that too, though I doubt that is the issue.
In particular, digikam has negative architecture constraints:
* (digikam) [!ppc64el] [!riscv64] [!s390x]
https://git.launchpad.net/~ubuntustudio-dev/ubuntu-
seeds/+git/ubuntustudio/tree/photography
EDIT: I confirmed the issue is _NOT_ debootstrap but germinate
[1] https://launchpad.net/ubuntu/+source/ubuntustudio-meta/25.04.10
[2] https://launchpad.net/ubuntu/+source/ubuntustudio-meta/25.04.11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/germinate/+bug/2103747/+subscriptions