>> > I'm thinking that a wishlist bug against dpkg-cross could be handy
>> > so that dpkg-cross maybe uses debconf to ask the user for a default
>> > target architecture. emdebian-tools can't configure cross_compile
>> > itself because that conffile belongs to dpkg-cross.
>> dpkg-cross is de-facto not maintained by me since long ago.
>> Maintainer is currently set to debian-e,email@example.com, but
>> actually nobody does any work on the package.
> How does that actually work? Is there a GnuPG key for the list or do
> all uploads just happen via the co-maintainers?
Co-maintainers are listed in Uploaders: ontrol field.
Btw, every DD has enough permossions to upload any package. But uploads by
those not listed in Maintainer: or Uploaders: are treated as NMUs.
>> Since you have been very active on related topics over last months,
>> maybe you are the correct person to take over dpkg-cross?
> I'm not sure I'm the right person to fix the current bugs in dpkg-cross
> but I can help out - I'll take a look at 379597 as part of the debconf
> thing and maybe apt-cross can provide a solution for 113279 but those
> are minor bugs. It may be best if I'm listed as another co-maintainer for
You may add yourself to Uploaders.
>> I will provide any necessary permissions on dpkg-cross alioth project
>> on request.
> Thanks. My alioth login is the same as debian: codehelp.