[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debootsnap fails to install transitional dummy packages



Hi,

Quoting Jochen Sprickerhof (2024-11-08 20:11:37)
> [Feel free to publish this message and discuss it openly if you see a 
> suitable location.]

done. :)

> Hi Josch,
> 
> earlier today I asked you in #debian-reproducible why these to 
> debrebuild jobs failed:
> 
> https://rebuilder-snapshot.debian.net/api/v0/builds/76832/log
> https://rebuilder-snapshot.debian.net/api/v0/builds/76839/log
> 
> I looked into it and my understanding is now that it is a problem in 
> debootsnap vs. sbuild vs. apt. Imagine two packages:
> 
> Package: A
> Depends: B
> Description: transitional dummy package
> 
> Package: B
> Provides: A
> 
> If a package build depends on A then sbuild will generate a 
> sbuild-build-depends-main-dummy package with the dependency and apt will 
> install A and B. debootsnap instead will generate a debootsnap-dummy 
> package depending on A and B. Here apt will figure out that B provides A 
> and only install B. Those we have two different package sets and 
> debootsnap fails as in the logs above.
> 
> I looked into a different ways to fix this. One would be generating the 
> same dummy package as sbuild. This fails because we would need to know 
> the sbuild version and what other packages it injected (like usrmerge in 
> the 76839 case above). I also looked into tricking apt to install A 
> anyhow but did not find a reliable way. So the only way I see is 
> assuming that the Provides: is correct and we can ignore the missing 
> package. I don't see an easy way to filter out those packages from the 
> pkglist. On the other hand I don't see a way to create a real difference 
> in the generated chroot, given that mmdebstrap is only provided with the 
> exact package set and the dummy package specifies the installed packages 
> and versions. So I would repeat my proposes to drop the extra check of 
> the build environment.

maybe stupid question, but did you try to just list them all in a single "apt
install" command line? I don't have pkg-config (seems to be a dummy even in
bookworm) installed and both "apt install pkg-config pkgconf" as well as "apt
install pkgconf pkg-config" will install pkg-config.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature


Reply to: