> That is something I could try, but I might prefer to list all arches
> manually. After all, the arches should not change every other day?
-1
The most time-consuming, error-prone and tedious part of the armel
port was identifying all the packages that had
[long-list-of-arches-except-one-or-two]
On Thu, Oct 09, 2008 at 07:25:17AM +0200, Petr Salinger wrote:
> >>Currently, it wouldn't be build at least on kfreebsd-i386,
> >>kfreebsd-amd64, hurd-i386, m32r, ppc64 without obvious reason.
> >
> >It would also not be built on m68k and powerpc, because for these arches
> >the
> >native package
Currently, it wouldn't be build at least on kfreebsd-i386,
kfreebsd-amd64, hurd-i386, m32r, ppc64 without obvious reason.
It would also not be built on m68k and powerpc, because for these arches the
native package is being built. Can I change the Architecture line to any but
m68k and powerpc?
On Wed, Oct 08, 2008 at 10:09:58PM +0200, Petr Salinger wrote:
> >>could the buildd admins please enable building for amiga-fdisk and upload
> >>the resulting packages (powerpc has been built, but it seems it was never
> >>uploaded).
> >Second, you need to get amiga-fdisk removed from packages-arch
could the buildd admins please enable building for amiga-fdisk and upload
the resulting packages (powerpc has been built, but it seems it was never
uploaded).
Second, you need to get amiga-fdisk removed from packages-arch-specific
to have it built by the buildds, see
http://cvs.debian.org/srcdep/
Package: amiga-fdisk-cross
Version: 0.04-12
Not a bug in amiga-fdisk itself, but a Debian buildd issue that needs sorting
On 16 Jan 2008, armel was added to the architecture list for
amiga-fdisk-cross (bug #461081)
but, despite being enabled for 12 architectures, the package has not
been built fo
6 matches
Mail list logo
