On 0808, Paul Wise wrote:
>On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote:
>
>> How should a new maintainer go about closing old bug reports?
>
>I noticed that you have been:
>
>Closing bug reports without any explanation.
>
>Closing what looks like legitimat
On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote:
> How should a new maintainer go about closing old bug reports?
I noticed that you have been:
Closing bug reports without any explanation.
Closing what looks like legitimate feature requests.
Neither of these is a good idea IMO.
--
On Sat, Aug 7, 2021 at 10:54 PM Brian Thompson wrote:
> What's the best way to go about handling old bug reports?
Triage them; go through each bug, try to find out if it was fixed and
which version it was fixed in. For the definitely fixed bugs, close
them with a versioned -done mess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
How should a new maintainer go about closing old bug reports? For
instance, I recently just took over apt-listchanges and see a lot of old
bug reports, including one from the year 2000.
I read https://www.debian.org/Bugs/Developer#closing
A bug is years old. It will probably not be fixed. It should probably not be
fixed. It is probably not even a bug.
The bug's submitter is not complaining.
Why is the bug still open?
Example: #619363. [1]
1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619363
If I were the
. What should I learn from this example about proper bug
handling, please?
That proper and timely bug triaging is a very important (and time
consuming) part of maintaining a package with a lot of open bug reports,
which is often not done because a maintainer doesn't have time for it.
--
WBR, wRAR
On 2015-06-02 20:10, Thaddeus H. Black wrote:
[...]
If I were the maintainer, I believe that I would have closed a bug like this.
The actual maintainer however (now emeritus) is smarter than me. He did not
close it. This suggests that he knew something I do not understand about
proper
On Tuesday 25 November 2008 19:21:46 Paul Wise wrote:
On Tue, Nov 25, 2008 at 7:18 AM, Jonathan Wiltshire
[EMAIL PROTECTED] wrote:
Do you think it is severe enough to be put forward for lenny?
I'm not sure. The patch looks straight-forward enough, so perhaps the
release team would approve
On Tue, Nov 25, 2008 at 7:18 AM, Jonathan Wiltshire
[EMAIL PROTECTED] wrote:
Do you think it is severe enough to be put forward for lenny?
I'm not sure. The patch looks straight-forward enough, so perhaps the
release team would approve it.
PS: it is a good idea to document in your patches why
Dear mentors
I had a quick look in the list archives but couldn't find an answer, so
perhaps you can help.
My adopted package gxemul has a bug in Ubuntu[1] (seg fault on command
line parameters) which reproduces in the current Debian package. It has
been fixed recently in upstream's CVS so I
On Mon, Nov 24, 2008 at 5:59 PM, Jonathan Wiltshire
[EMAIL PROTECTED] wrote:
My adopted package gxemul has a bug in Ubuntu[1] (seg fault on command
line parameters) which reproduces in the current Debian package. It has
been fixed recently in upstream's CVS so I plan to add a patch for the
On Monday 24 November 2008 10:13:23 Paul Wise wrote:
On Mon, Nov 24, 2008 at 5:59 PM, Jonathan Wiltshire
[EMAIL PROTECTED] wrote:
My adopted package gxemul has a bug in Ubuntu[1] (seg fault on command
line parameters) which reproduces in the current Debian package. It has
been fixed
On Mon, Nov 24, 2008 at 06:13:23PM +0900, Paul Wise wrote:
Sounds fine. Be sure to prepare an upload for testing-proposed-updates
if you want to add the patch to lenny and the release team are likely
to approve the patch, since your package is not in sync between lenny
sid.
Can you advise
On Mon, Nov 24, 2008 at 8:00 PM, Jonathan Wiltshire
[EMAIL PROTECTED] wrote:
Can you advise further or point me to somewhere to find out more? I've
never used testing-proposed-updates, but it would be a good thing to
learn about.
http://www.debian.org/doc/developers-reference/pkgs.html#t-p-u
On Mon, Nov 24, 2008 at 08:07:45PM +0900, Paul Wise wrote:
http://www.debian.org/doc/developers-reference/pkgs.html#t-p-u [1]
http://lists.debian.org/debian-devel-announce/2008/09/msg0.html [2]
Ok, I understand the theory according to [1]. But [2] states that bugs
should be at severity
G'day,
I maintain a few unoffical Debian packages. Before I make my repository
available to the world, I'd like to ensure that if someone runs
reportbug on one of my packages, it will email me, and not the Debian
BTS.
The packages are targeted at sarge or better.
Thank you for your kind
On Wed, 09 Mar 2005, Jamie Jones wrote:
G'day,
I maintain a few unoffical Debian packages. Before I make my repository
available to the world, I'd like to ensure that if someone runs
reportbug on one of my packages, it will email me, and not the Debian
BTS.
See
On Tue, 2005-03-08 at 18:28 -0800, Don Armstrong wrote:
On Wed, 09 Mar 2005, Jamie Jones wrote:
G'day,
I maintain a few unoffical Debian packages. Before I make my repository
available to the world, I'd like to ensure that if someone runs
reportbug on one of my packages, it will email
On Wed, 18 Jun 2003 07:55:19 +0200, Johannes Rohr [EMAIL PROTECTED]
wrote:
Am Wed, 18 Jun 2003 02:40:05 +0200 schrieb Henrique de Moraes Holschuh:
On Tue, 17 Jun 2003, Johannes Rohr wrote:
as you both suggested. But I wonder if the BTS could have an invalid
tag for such cases?!?
Why clog it
Am Wed, 18 Jun 2003 02:40:05 +0200 schrieb Henrique de Moraes Holschuh:
On Tue, 17 Jun 2003, Johannes Rohr wrote:
as you both suggested. But I wonder if the BTS could have an invalid
tag for such cases?!?
Why clog it up with invalid reports? They stay around as closed for a small
while,
Am Wed, 18 Jun 2003 02:40:05 +0200 schrieb Henrique de Moraes Holschuh:
On Tue, 17 Jun 2003, Johannes Rohr wrote:
as you both suggested. But I wonder if the BTS could have an invalid
tag for such cases?!?
Why clog it up with invalid reports? They stay around as closed for a small
while,
[EMAIL PROTECTED] (Craig Small) writes:
[...]
What is the generally accepted way within the Debian culture to deal
with such reports? Do I close the bug right away? Do I downgrade it?
Do I reassign it (in this case to gstreamer)?
I'd close it. At the very worse tag it wontfix and set it
On Tue, 17 Jun 2003, Johannes Rohr wrote:
as you both suggested. But I wonder if the BTS could have an invalid
tag for such cases?!?
Why clog it up with invalid reports? They stay around as closed for a small
while, then get archived...
--
One disk to rule them all, One disk to find them.
[EMAIL PROTECTED] (Craig Small) writes:
[...]
What is the generally accepted way within the Debian culture to deal
with such reports? Do I close the bug right away? Do I downgrade it?
Do I reassign it (in this case to gstreamer)?
I'd close it. At the very worse tag it wontfix and set it
On Tue, 17 Jun 2003, Johannes Rohr wrote:
as you both suggested. But I wonder if the BTS could have an invalid
tag for such cases?!?
Why clog it up with invalid reports? They stay around as closed for a small
while, then get archived...
--
One disk to rule them all, One disk to find them.
Dear all,
some days ago someone filed an obviously bogus bug against a package
I'm co-maintaining (nautilus-media, bug #197352), i.e. he complained
about being unable to install the gnome-core metapackage on hppa
because nautilus-media on which gnome-core depends is unavailable on
that arch.
On Mon, Jun 16, 2003 at 10:43:25PM +0200, Johannes Rohr wrote:
some days ago someone filed an obviously bogus bug against a package
I'm co-maintaining (nautilus-media, bug #197352), i.e. he complained
about being unable to install the gnome-core metapackage on hppa
because nautilus-media on
Dear all,
some days ago someone filed an obviously bogus bug against a package
I'm co-maintaining (nautilus-media, bug #197352), i.e. he complained
about being unable to install the gnome-core metapackage on hppa
because nautilus-media on which gnome-core depends is unavailable on
that arch.
On Mon, Jun 16, 2003 at 10:43:25PM +0200, Johannes Rohr wrote:
some days ago someone filed an obviously bogus bug against a package
I'm co-maintaining (nautilus-media, bug #197352), i.e. he complained
about being unable to install the gnome-core metapackage on hppa
because nautilus-media on
On Mon, 16 Jun 2003, Johannes Rohr wrote:
What is the generally accepted way within the Debian culture to deal
with such reports? Do I close the bug right away? Do I downgrade it?
Do I reassign it (in this case to gstreamer)?
You can reassign it with the priority and bug title changed to
};
}
-execbrowser($btsurl.$email);
+ browse($email);
}
=item clone bug [new IDs]
@@ -314,6 +356,70 @@
mailbts(bug $bug is not forwarded, notforwarded $bug);
}
+=item cache [email address | package]
+
+Generate or update a cache of bug reports for the given email address
+or package
On May 30, Joey Hess ([EMAIL PROTECTED]) wrote:
Neil Roeth wrote:
Thanks for the hints. I should have been more clear - I have no problem
getting the main page, i.e., [EMAIL PROTECTED] There are
links in that page to bugs.debian.org/cgi-bin/bugreport.cgi?bug=num for each
bug, and I
};
}
-execbrowser($btsurl.$email);
+ browse($email);
}
=item clone bug [new IDs]
@@ -314,6 +356,70 @@
mailbts(bug $bug is not forwarded, notforwarded $bug);
}
+=item cache [email address | package]
+
+Generate or update a cache of bug reports for the given email address
+or package
On May 30, Joey Hess ([EMAIL PROTECTED]) wrote:
Neil Roeth wrote:
Thanks for the hints. I should have been more clear - I have no problem
getting the main page, i.e., [EMAIL PROTECTED] There are
links in that page to bugs.debian.org/cgi-bin/bugreport.cgi?bug=num for
each
bug,
On May 28, Xavier Roche ([EMAIL PROTECTED]) wrote:
Hi,
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I
, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work,
What's the error message? At least it works for me
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work, I think because they are not static pages, they are
created on the fly by scripts
Hi,
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work, I think
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work, I think because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil,
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work, I think because they are not static pages, they are
created on the fly by scripts
Hi,
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work, I think
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them offline.
But, wget doesn't work, I think because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil,
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer
On May 28, Xavier Roche ([EMAIL PROTECTED]) wrote:
Hi,
On Wed, May 28, 2003 at 06:49:50AM -0400, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I
, Neil Roeth wrote:
I'd like to download the web page of bugs by maintainer,
http://bugs.debian.org/cgi-bin/[EMAIL PROTECTED], and all
the bug reports linked to on that page, so that I can refer to them
offline.
But, wget doesn't work,
What's the error message? At least it works
Yes. The bugs that are closed are those where the changelog entry is
included in the changes file for the upload. Unless you use the -v
option to dpkg-genchanges or equivalent this will only be the last
entry.
SNIP
Thanks all!
Hugo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Tue, Oct 30, 2001 at 10:55:02PM +0200, Hugo van der Merwe wrote:
I have the following in my changelog:
* New maintainer (closes: #98251)
* Install upstream man page (closes: #93474)
* Removed Suggests: wmaker (closes: #82998)
however the bugs weren't closed automatically. Might
Yes. The bugs that are closed are those where the changelog entry is
included in the changes file for the upload. Unless you use the -v
option to dpkg-genchanges or equivalent this will only be the last
entry.
SNIP
Thanks all!
Hugo
On Tue, Oct 30, 2001 at 10:55:02PM +0200, Hugo van der Merwe wrote:
I have the following in my changelog:
* New maintainer (closes: #98251)
* Install upstream man page (closes: #93474)
* Removed Suggests: wmaker (closes: #82998)
however the bugs weren't closed automatically. Might
I have the following in my changelog:
* New maintainer (closes: #98251)
* Install upstream man page (closes: #93474)
* Removed Suggests: wmaker (closes: #82998)
however the bugs weren't closed automatically. Might it be because of:
* Not uploaded, found new upstream release
(I made
On Tue, Oct 30, 2001 at 10:55:02PM +0200, Hugo van der Merwe wrote:
(I made another new version, and only uploaded then. So this was never
the topmost paragraph. Might that be the problem?)
Yes. The bugs that are closed are those where the changelog entry is
included in the changes file for
Hugo van der Merwe writes:
(I made another new version, and only uploaded then. So this was never
the topmost paragraph. Might that be the problem?)
Yes, dpkg-genchanges will only look at the most recent version when
generating the Closes: field. Try using the -vversion, option, where
On 30-Oct-2001 Hugo van der Merwe wrote:
I have the following in my changelog:
* New maintainer (closes: #98251)
* Install upstream man page (closes: #93474)
* Removed Suggests: wmaker (closes: #82998)
however the bugs weren't closed automatically. Might it be because of:
*
At Tue, 30 Oct 2001 22:55:02 +0200, Hugo van der Merwe [EMAIL PROTECTED] wrote:
(I made another new version, and only uploaded then. So this was never
the topmost paragraph. Might that be the problem?)
The closed bugs get listed in the .changes file you upload. You might
want to look at the -v
I have the following in my changelog:
* New maintainer (closes: #98251)
* Install upstream man page (closes: #93474)
* Removed Suggests: wmaker (closes: #82998)
however the bugs weren't closed automatically. Might it be because of:
* Not uploaded, found new upstream release
(I made
On Tue, Oct 30, 2001 at 10:55:02PM +0200, Hugo van der Merwe wrote:
(I made another new version, and only uploaded then. So this was never
the topmost paragraph. Might that be the problem?)
Yes. The bugs that are closed are those where the changelog entry is
included in the changes file for
Hugo van der Merwe writes:
(I made another new version, and only uploaded then. So this was never
the topmost paragraph. Might that be the problem?)
Yes, dpkg-genchanges will only look at the most recent version when
generating the Closes: field. Try using the -vversion, option, where
On 30-Oct-2001 Hugo van der Merwe wrote:
I have the following in my changelog:
* New maintainer (closes: #98251)
* Install upstream man page (closes: #93474)
* Removed Suggests: wmaker (closes: #82998)
however the bugs weren't closed automatically. Might it be because of:
*
At Tue, 30 Oct 2001 22:55:02 +0200, Hugo van der Merwe [EMAIL PROTECTED]
wrote:
(I made another new version, and only uploaded then. So this was never
the topmost paragraph. Might that be the problem?)
The closed bugs get listed in the .changes file you upload. You might
want to look at the -v
On Sat, Mar 10, 2001 at 08:57:44PM +0100, Josip Rodin wrote:
On Sat, Mar 10, 2001 at 01:08:49PM -0500, Bob Hilliard wrote:
If I fix a bug in my package, and send the patch upstream, should
the bug be marked "forwarded", or should "forwarded" be reserved for
bugs that are waiting for
On Sat, Mar 10, 2001 at 08:57:44PM +0100, Josip Rodin wrote:
On Sat, Mar 10, 2001 at 01:08:49PM -0500, Bob Hilliard wrote:
If I fix a bug in my package, and send the patch upstream, should
the bug be marked forwarded, or should forwarded be reserved for
bugs that are waiting for
If I fix a bug in my package, and send the patch upstream, should
the bug be marked "forwarded", or should "forwarded" be reserved for
bugs that are waiting for upstream to fix?
Bob
--
_
|_) _ |_ Robert D. Hilliard [EMAIL PROTECTED]
|_) (_) |_) 1294 S.W. Seagull
If I fix a bug in my package, and send the patch upstream, should
the bug be marked forwarded, or should forwarded be reserved for
bugs that are waiting for upstream to fix?
Bob
--
_
|_) _ |_ Robert D. Hilliard [EMAIL PROTECTED]
|_) (_) |_) 1294 S.W. Seagull Way
On Sat, Mar 10, 2001 at 01:08:49PM -0500, Bob Hilliard wrote:
If I fix a bug in my package, and send the patch upstream, should
the bug be marked forwarded, or should forwarded be reserved for
bugs that are waiting for upstream to fix?
If you've informed the upstream about the bug, it's
-BEGIN PGP SIGNED MESSAGE-
On Fri, 24 Jul 1998, Shaleh wrote:
Help! My bug reports have gone AWOL. The BTS does not display the
correct number of bugs, nor does it show all of my bugs.
Something similar happened to me with pine packages.
Please, download the file Maintainers
66 matches
Mail list logo
