Browse Source

Ubuntu changes.

suites/jessie-proposed-backports
Chris Lawrence 18 years ago
parent
commit
e0afd84391
  1. 1
      README.developers
  2. 7
      TODO
  3. 10
      debian/changelog

1
README.developers

@ -48,6 +48,7 @@ submitted to (i.e. the Package: field of the report). This will be mainly
used to redirect bugs in packages coming from a single source to where the
maintainer likes to have them.
This is done by having this line in /usr/share/bug/$package/control:
Submit-As: $new-package

7
TODO

@ -4,14 +4,11 @@ http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/reportbug/
--
Silly TODO list for 2.x:
Silly TODO list for 3.0 (possibly sarge, depending on RM's mood):
1. Document reportbug.conf properly in a man page.
Silly TODO list (in no particular order):
Since we're approaching sarge freeze time, these are probably all
reportbug 3.x (2.99.x) things.
Silly TODO list for 4.0 (sarge+1):
1. Proper GNOME interface. My current thinking is to hack the
bug-buddy Glade file to pieces, or do something similar in straight

10
debian/changelog

@ -8,8 +8,16 @@ reportbug (2.99.5) unstable; urgency=low
packages.debian.org. Thanks to Wolfgang Rohdewald for the patch.
(Closes: #274189, #271552)
* Document SMTP options in reportbug.conf. (Closes: #274280)
* Don't check packages.debian.org if options.bts is set to something
other than "debian".
* Incorporate applicable changes in 2.62ubuntu1 to this tree.
(Main advantage: --bts=ubuntu works now. If someone will kindly tell
me an easy way to tell a Ubuntu system from a Debian one, I will
incorporate code to eliminate the need for the forked package. Same
goes for any other Debian fork, BTW...)
--
-- Chris Lawrence <lawrencc@debian.org> Fri, 1 Oct 2004 03:23:05 -0500
reportbug (2.99.4) unstable; urgency=low

Loading…
Cancel
Save