Re: Packages still using /usr/doc in unstable
On Mon, 26 Mar 2001, Colin Watson wrote:
> Dale Scheetz <dwarf@polaris.net> wrote:
> >On Mon, 26 Mar 2001, Jordi Mallach wrote:
> >> On Mon, Mar 26, 2001 at 11:17:58AM +0100, Mark Brown wrote:
> >> > > Does anybody seriously object to NMUs taking place, with due care?
> >> > Please ask maintainers before doing it, though.
> >>
> >> I believe doogie filled bugs against all the packages, so everyone has
> >> been warned.
> >> Killing these will be a goal for the next bugsquash weekend.
>
> I think this is rather too short notice for normal bugs, FWIW, much as
> I'd like to get the /usr/doc monster slain.
>
> >Be sure to at least attempt to contact maintainers, so efforts aren't
> >duplicated. Some of us take more than one or two days to work through a
> >package upgrade, so while the bug you want to squash may look easy, it may
> >also already be fixed in the "soon to be uploaded" work of the maintainer.
> >
> >I know you guys are in a hurry during BSPs, but you really must contact
> >maintainers. Just because the bug is old and unfixed, doesn't mean that
> >the maintainer is not aware of and working on a fix.
>
> Bugs with any recent activity won't (shouldn't) be touched in
> bug-squashing party NMUs, so just a note in the bug to the effect that
> you're working on it is enough.
Great! Now when I want to work on a bug, I have to dedicate some time
before hand to making sure the BTS knows what I'm doing? That's never
going to happen. Sometimes I only have 20 minutes to work on the package.
Just how hard is it to send me a message when you want to work on one of
my packages? I'm not saying you need my permission in a reply in order to
make the upload, just that you inform me, personally, that you are working
on my package. If you fail to do this, your fix stands an excelent chance
of being overwritten by my next release.
Keeping the maintainer in the dark is pointless. Suggesting that a bug
report from the NMUer is the right thing to do would be ok except that
none of the NMUs made against my packages in the past ever submitted such
a report.
What's so difficult about droping the maintianer an e-mail?
>
> That's why NMU diffs are supposed to be filed in the BTS as soon as
> possible, isn't it?
I really don't know where all this "new procedure" comes from, but talking
to the BTS is pretty much like talking to yourself ;-)
It's really quite simple. Contact me when you want to work on one of my
packages. Otherwise you have no guarantee that your work will be of any
value.
Luck,
Dwarf
--
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: dwarf@polaris.net Tallahassee, FL 32308
_-_-_-_-_-_- See www.linuxpress.com for more details _-_-_-_-_-_-_-
Reply to: