Jonathan Nieder wrote:
So what are the possible means of getting around the problem?
Me providing a login to an Alpha with an up-to-date unstable chroot?
A sponsored upload of aboot? Does that require at least a DM to prepare
the package?
Could you become a DD? I'm confident in your skills and ethics, for what
little that's worth.
Even assuming a dd could be found or created who was prepared to build
and upload
a package on alpha i'm not convinced that a binary package that can only
be built on a
debian-ports.org architecture should be in the official archive. I can't
seem to find any
policy directly prohibiting it but "packages must be buildable within
the same release".
would seem to imply to me that all "arch all" packages should be
buildable on at least
one release architecture.
If that takes a long time, in the meantime would it be possible to get
an alpha cross-toolchain packaged so the package can be built on non-alpha
machines? I'd be happy to help with that. (See [1] for a starting point.)
[1] http://bugs.debian.org/623953#20
I'm not a dd myself but that sounds like the way to go to me if it's
desired to keep
aboot-cross and aboot-core in the official archive.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
