Generating built-using in d-i (was: Providing (armhf) u-boot images together with d-i images?)
- To: Cyril Brulebois <kibi@debian.org>
- Cc: Karsten Merker <merker@debian.org>, Ian Campbell <ijc@debian.org>, debian-boot@lists.debian.org
- Subject: Generating built-using in d-i (was: Providing (armhf) u-boot images together with d-i images?)
- From: Karsten Merker <merker@debian.org>
- Date: Mon, 2 Feb 2015 23:19:28 +0100
- Message-id: <[🔎] 20150202221928.GA16070@excalibur.cnev.de>
- In-reply-to: <20150102154038.GD1836@mraw.org>
- References: <87vbls72j6.fsf@aikidev.net> <20141218182845.GA4567@excalibur.cnev.de> <20141223163128.GA6448@excalibur.cnev.de> <20141223235141.GK16659@mraw.org> <20141226230054.GA2950@excalibur.cnev.de> <1419953311.13595.190.camel@debian.org> <20141231005908.GA4590@excalibur.cnev.de> <1420195597.2030.48.camel@debian.org> <20150102135118.GA4614@excalibur.cnev.de> <20150102154038.GD1836@mraw.org>
On Fri, Jan 02, 2015 at 04:40:38PM +0100, Cyril Brulebois wrote:
> Karsten Merker <merker@debian.org> (2015-01-02):
> > > (Do your patches end up adding the correct Built-Using on u-boot?)
> >
> > No, they don't, but d-i does not do that for similar components
> > on other platforms (syslinux/isolinux/grub) as well. Probably we
> > should do that, but then it would have to be done for all
> > platforms. Kibi?
>
> ISTR having proposed a patch to #700026 / #696418, but that wasn't
> commented upon.
Hello,
I have tried your patch from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700026#26,
but unfortunately it does not work correctly in some cases
involving platform-specific packages. For example running
dpkg-query -f '${source:Package} (= ${source:Version}), ' -W syslinux
on armhf (for which the "syslinux" binary package is not built)
results in
syslinux (= ),
which is not the intended output for generating the built-using
list. I currently do not see how to get dpkg-query to explicitly
check for the availability of a specific binary package on the
current platform - dpkg-query exits with a returncode of 1 if one
queries for a completely non-existing package, but returns 0 when
checking for syslinux on armhf, probably because the syslinux
source also builds arch:all packages. Any ideas?
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: