Hi Chris,
Christopher L Conway wrote:
> the problem architectures are not directly supported by
> upstream and I don't have access to testing machines for these
> architectures, I'm not sure what the correct resolution is. Should I
> remove these architectures in debian/control?
I’d suggest something like this:
1. First, request the removal of the broken packages currently in
testing. You can do this with a bug against the release.debian.org
package [1]. Once this finishes, the bug is no longer release
critical (though it is still important).
2. Clone this bug into separate bugs tracking information about
each collection of regressions that you think will have the same
fix.
3. Add information about how to track them down (a good command to
run, a patch to try, whatever) to the bug log.
4. Help anyone who is interested in working on the bugs.
If you have time, you can investigate further without access to a
porterbox:
* armel can be emulated with qemu [2].
* kfreebsd-amd64 and kfreebsd-i386 can be run natively on common
hardware. Or you can run them in a virtual machine (e.g., KVM),
still fairly quickly.
* s390 can be emulated with hercules [3], though rather slowly.
On a slow machine, this can try one’s patience, though. No need to get
carried away.
DDs have access to some machines [4] for porting. This is a good
reason to become a DD. :)
If you have any questions, please don’t hesitate to ask.
HTH,
Jonathan
[1] http://wiki.debian.org/ftpmaster_Removals
[2] http://www.aurel32.net/info/debian_arm_qemu.php
[3] http://www.josefsipek.net/docs/s390-linux/hercules-s390.html
[4] http://db.debian.org/machines.cgi
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
