Bug#534063: pixfrogger: FTBFS: Nonexistent build-dependency: fenix

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#534063: pixfrogger: FTBFS: Nonexistent build-dependency: fenix

Jeremy Bicha-3
I think this patch was wrong. Although it enabled the package to build
on Ubuntu, it didn't enable the package to migrate out of the
-proposed repository Ubuntu uses. I'm guessing that's because it fails
basic install-ability checks.

Since pixfrogger is only installable on i386, I think the binary
Architecture field should be set to i386.

I don't think you need the XS-Build-Indep-Architecture line then.

Jeremy

Reply | Threaded
Open this post in threaded view
|

Bug#534063: pixfrogger: FTBFS: Nonexistent build-dependency: fenix

Jeremy Bicha-3
According to codesearch, this is the only place the XS field is used in Debian:
https://codesearch.debian.net/results/%20path%3Adebian%2Fcontrol%20XS-Build-Indep-Architecture

and therefore triggers
https://lintian.debian.org/tags/unknown-field-in-dsc.html

piuparts complains too:
https://piuparts.debian.org/sid/source/p/pixfrogger.html

Thanks,
Jeremy Bicha

Reply | Threaded
Open this post in threaded view
|

Bug#534063: pixfrogger: FTBFS: Nonexistent build-dependency: fenix

Vincent Cheng-2
In reply to this post by Jeremy Bicha-3
On Thu, Jun 2, 2016 at 8:42 PM, Jeremy Bicha <[hidden email]> wrote:
> I think this patch was wrong. Although it enabled the package to build
> on Ubuntu, it didn't enable the package to migrate out of the
> -proposed repository Ubuntu uses. I'm guessing that's because it fails
> basic install-ability checks.
>
> Since pixfrogger is only installable on i386, I think the binary
> Architecture field should be set to i386.
>
> I don't think you need the XS-Build-Indep-Architecture line then.

I disagree. The package is arch:all because it doesn't contain any
arch-specific files, and it would be installable on all architectures
if its dependencies are also installable on all archs. Listing out all
the archs that pixfrogger can run on (i.e. all non amd64 archs) would
just result in duplication across the archive for no particular
benefit.

The fact that it fails to migrate from proposed to release in Ubuntu
sounds more like an issue with whatever software Ubuntu is using for
testing package migrations.

Regards,
Vincent