Bug#497165: [EMAIL PROTECTED]: Bug#497165: amiga-fdisk-cross is not being built on any architecture other than i386]

2008-10-10 Thread Christian T. Steigies
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 is being built. Can I change the Architecture line to any 
 but
 m68k and powerpc?
 
 Would be problem to build amiga-fdisk-cross even on native arches ?

Cross indicates that this is not the native fdisk program for the
architecture. IIRC there is no difference in the code, but the resulting
packages have different priorities.
 
 You could also use debhelper -Namiga-fdisk-cross on them,
 by something like
 
 ifeq (,$(filter-out m68k powerpc,$(DEB_HOST_ARCH_CPU)))
  DH_EXTRAS=-Namiga-fdisk-cross
 endif

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?

Christian



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497165: [EMAIL PROTECTED]: Bug#497165: amiga-fdisk-cross is not being built on any architecture other than i386]

2008-10-08 Thread Petr Salinger

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/Packages-arch-specific?root=dakview=markup
and the contact addresses at the top of that file.


And third, what about change Architecture line
of amiga-fdisk-cross into any ?

Currently, it wouldn't be build at least on kfreebsd-i386, 
kfreebsd-amd64, hurd-i386, m32r, ppc64 without obvious reason.


Petr



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497165: [EMAIL PROTECTED]: Bug#497165: amiga-fdisk-cross is not being built on any architecture other than i386]

2008-10-08 Thread Christian T. Steigies
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-specific
 to have it built by the buildds, see
 http://cvs.debian.org/srcdep/Packages-arch-specific?root=dakview=markup
 and the contact addresses at the top of that file.

It seems I was not precise enough, amiga-fdisk (the source) builds
amiga-fdisk for amiga and powerpc only, and it builds amiga-fdisk-cross for
(nearly) every other arch.
 
 And third, what about change Architecture line
 of amiga-fdisk-cross into any ?
 
 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?

Christian



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#497165: [EMAIL PROTECTED]: Bug#497165: amiga-fdisk-cross is not being built on any architecture other than i386]

2008-10-08 Thread Petr Salinger

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?


Would be problem to build amiga-fdisk-cross even on native arches ?

You could also use debhelper -Namiga-fdisk-cross on them,
by something like

ifeq (,$(filter-out m68k powerpc,$(DEB_HOST_ARCH_CPU)))
 DH_EXTRAS=-Namiga-fdisk-cross
endif

Petr



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]