Hi, Ritesh Raj Sarraf <rrs@debian.org> (2021-04-30): > The upload I prepped failed on some of the architectures. > https://buildd.debian.org/status/logs.php?pkg=open-iscsi&ver=2.1.3-3 It's lacking a push to the Git repository (git fetch didn't get anything new from a few days ago). > In d/control, there is: > > ``` > Package: open-iscsi-udeb > # Note: the (virtual) udeb package scsi-modules (provided by different > # linux kernel udebs) must exist for these architectures - so > # check that before adding them to this list; the other > # scsi-(core|common|...)-modules are NOT sufficient! > Architecture: amd64 arm64 armhf i386 ia64 mips mipsel powerpc ppc64 > ppc64el s390x > Section: debian-installer > Package-Type: udeb > ``` > > > The udeb package was introduced by Colin Watson from Ubuntu. I extended > the architecture list, based on the supported architectures by d-i. But > I really don't use or test this functionality of the package. > > > How would you like to see this fixed Cyril ? > > The easiest option, if d-i supports, would be to extend architecture > list to: `linux-any`, keeping it in line with what the actual open- > iscsi package supports. Yes, I think that would be a good idea, so that you don't have to keep the list in sync between debian/control and debian/rules. We don't have many examples of packages maintained by the d-i team that use it, but at least src:haveged and src:systemd have similar udebs (after all, that only matters at build-time, d-i only sees the results of the build). Regarding your conditional, you could check whether you're building for linux (once you switch to linux-any) or you could check whether the udeb is being built: dh_listpackages (-a) can be use to determine that. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature