[Bug 2103747] Re: germinate is missing packages

[Erich Eickmeyer]

** Description changed:

  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

** Summary changed:

- germinate is missing packages
+ Regression: germinate failing to resolve packages correctly

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to germinate in Ubuntu.
https://bugs.launchpad.net/bugs/2103747

Title:
  Regression: germinate failing to resolve packages correctly

Status in germinate package in Ubuntu:
  New

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