On September 30, 2021 8:26 pm, David Galloway wrote: > > > On 9/21/21 12:13 PM, David Galloway wrote: >> >> >> On 9/20/21 4:54 AM, Fabian Grünbichler wrote: >>> On September 17, 2021 8:24 pm, David Galloway wrote: >>>> >>>> >>>> On 9/17/21 2:19 PM, David Galloway wrote: >>>>> >>>>> >>>>> On 9/17/21 5:36 AM, Fabian Grünbichler wrote: >>>>>> [...] >>>>>> >>>>>> I assume this is a bug in your repository software config or the scripts >>>>>> used for uploading - in case those are public I'd appreciate a pointer >>>>>> and might attempt fixing it myself. >>>>> >>>>> So the tool we use to store our repos before signing them is called >>>>> chacra. I added the Debian bullseye codename to the tool prior to this >>>>> recent release. >>>>> >>>>> https://github.com/ceph/chacra/commit/cc55ed5849be48a679ebc49200a9dc1600a4401a >>>>> >>>>> We combine all our Ubuntu and Debian repos on the main chacra.ceph.com node. >>>>> >>>>> Here's the focal repo: >>>>> https://chacra.ceph.com/r/ceph/pacific/ee28fb57e47e9f88813e24bbf4c14496ca299d31/ubuntu/focal/flavors/default/dists/ >>>>> >>>>> Here's the bullseye repo: >>>>> https://chacra.ceph.com/r/ceph/pacific/ee28fb57e47e9f88813e24bbf4c14496ca299d31/debian/bullseye/flavors/default/dists/ >>>>> >>>>> The script I use to pull packages from chacra.ceph.com to the signing >>>>> machine is here: >>>>> https://github.com/ceph/ceph-build/blob/master/scripts/sync-pull#L15-L25 >>>>> >>>>> The script just checks all possible combos for whichever repo has the >>>>> most packages because that's where they all got combined by the chacra tool. >>>>> >>>>> So I think the problem we're running into here is ubuntu/focal was the >>>>> latest distro combo and was where all the combined repos were going to. >>>>> But once debian/bullseye got added, that got reset somehow? >>>> >>>> Oh, actually, in this particular release, debian/buster is the combined >>>> repo where all the packages ended up: >>>> https://chacra.ceph.com/r/ceph/pacific/ee28fb57e47e9f88813e24bbf4c14496ca299d31/debian/buster/flavors/default/pool/main/c/ceph/ >>> >>> so if I understand correctly, the debs are picked up from the indivual >>> builds and collected, and then that collection is pulled, signed, and >>> pushed back out? >> >> I'm not sure. I'm not super familiar with .deb repos in the first place >> or what magic chacra does in the background. I think what I can do to >> rectify this problem is just build all of the previous Pacific versions >> for Bullseye. I will try that. > > This unfortunately isn't going to be possible because previous point > releases are still trying to pull in dependencies that don't exist in > Debian Bullseye. i.e., they don't have > > https://github.com/ceph/ceph/pull/43151 > https://github.com/ceph/ceph/pull/43131 > > Will this be problematic for each subsequent point release or is it okay > that we're sort of starting over with the Release files starting with > 16.2.6? we sorted it out for 16.2.6, and can keep pulling in from buster or whatever release has the Sources index ;) if it jumps too often it's a bit annoying, but now that we know that it can do that we can look it up and adapt accordingly ourselves.. _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
