Re: "How to recognise different ETCH wishlists from quite a long way away" (revised)
On Sat, 09 Jul 2005 20:13:57 +1000, Brian May <bam@debian.org> said:
> 1. Review bugs in web browser.
> 2. Identify questionably bug that you haven't already looked at
> before today.
Hint: have a local notebook that you mark bugs you look at.
> 3. Inspect bug report, in new window, install package, install
> source, inspect as required. Open up new browser windows to find
> information as required.
There is a download bug reports as mailbox feature.
> 4. Make changes as required to source code.
> 5. Enter one/more emails to either forward bug upstream, change
> tags, or close the bug.
> 6. Go back to step 3.
> 7. Fix up the all the silly typos made in every BTS email sent so
> far and retransmit. (note: this is after the BTS has decided to
> respond).
!!!!! [1]
> 8. upload the changes to source code.
> 9. realize that I forgot to sign the upload due to a bug in by
> pbuilder wrapper script, create a *.commands file to send to the
> upload queue to delete the old upload and reupload again.
!!!!! [2]
Are we sure we want someone who is routinely this incompetent
to help with bug triage? Seems to me we would be bette off without
such substandard help; anyone this incompetent is probably creating
more problems than they are solving.
> 4. Make dupload obsolete, and replace with dput. Make dput the
> default in debrelease. I think dput would have prevented me
> uploading my unsigned package.
~/.dupload.conf:
$preupload{'changes'} = 'gpg --verify %1';
$preupload{'sourcepackage'} = 'j=$(echo %1 | tr " " "_"); gpg --verify "$j.dsc"';
$preupload{'deb'} = 'lintian -v -i %1';
Just this point (not knowing ones tools) makes this message
highly suspect.
manoj
--
Only the hypocrite is really rotten to the core. Hannah Arendt
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: