On Sun, Jan 08, 2017 at 04:38:36PM +0100, John Paul Adrian Glaubitz wrote:
> Control: user debian-al...@lists.debian.org
> Control: usertags alpha
>
> > Apparently (see Bug #821332), I would need somebody having an alpha to
> > check that "dpkg-buildpackage -A" works.
>
> I can actually do that,
Control: user debian-al...@lists.debian.org
Control: usertags alpha
> Apparently (see Bug #821332), I would need somebody having an alpha to
> check that "dpkg-buildpackage -A" works.
I can actually do that, I have access to an alpha porterbox. However, you
can also actually do it yourself by
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Hi.
I see that the "Architecture: all" package which may not be built on amd64
is really a "trick" to build the package on alpha and have its contents
to be automatically available on other architectures.
So: Could not we use "multiarch" for that?
We already use multiarch to make i386 libraries
retitle 805988 aboot: FTBFS on amd64 when built with dpkg-buildpackage -A
tags 805988 + help
thanks
Apparently (see Bug #821332), I would need somebody having an alpha to
check that "dpkg-buildpackage -A" works.
Can someone check this? (The package is very small so it should not take
a long time
Package: src:aboot
Version: 1.0~pre20040408-4
User: sanv...@debian.org
Usertags: binary-indep
Severity: important
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
6 matches
Mail list logo
