Re: Uploaded glibc-pre2.1 2.0.106-0.2 (hurd-i386) to master
Hi!
>>>>> Christian Meder writes:
CM> Argh. Did you coordinate this glibc-pre2.1 upload with the glibc
CM> maintainer Joel Klecker <espy@debian.org> ?
Hoik! (That's Gordish for ``oops''.)
This is my first upload, so if I've dealt incorrectly with any policy
issues, please let me know. I've acted on my (limited) understanding
of Debian policy and maintainership instructions.
This upload was only done to provide the Debian GNU/Hurd folks with a
working binary package, not to change the course of glibc-pre2.1
development. That's why I used `0.2' as the package version number.
I also released a `0.1' version, but didn't upload it to master.
It was my intention to solicit feedback from the debian-hurd people,
then, after arriving on something stable, to report the Hurd-specific
changes we need to make back to Joel. I didn't want to involve him at
this point because things are still quite in flux.
I thought that attempting a port to a non-supported architecture was a
legitimate reason for an NMU, but I may just have been misreading the
spirit of the Debian maintainer's guide.
CM> What's libc0.2 ? Is it the soname for glibc2.1 on the hurd
CM> kernel?
Yes. The two `0.2's are just a cooincidence... I really am making the
0.2 package release of libc.so.0.2.
CM> Could you please separate in orig.tar.gz and diff.gz (pristine
CM> upstream source and debian specific stuff) ?
Absolutely.
Seeing as there must be issues here I don't understand, I'll wait for
further response from you folks before attempting to send anything
else.
Thanks for your note,
--
Gordon Matzigkeit <gord@fig.org> //\ I'm a FIG (http://www.fig.org/)
Lovers of freedom, unite! \// I use GNU (http://www.gnu.org/)
[Unfortunately, www.fig.org is broken. Please stay tuned for details.]
Reply to: