What is an ordinary bug submitter's recourse when a bug report
is closed without resolution? The response sent to the poster is that
a reasonable response must have been received (or a paraphrase); what
happens then the response is missing?
The exact phrasing is
Their explanatio
Closing valid bugs which were merely assigned to the wrong package
isn't acceptable (though admitedly, it *is* better than just ignoring
them entirely.)
Closing a valid bug without fixing is generally wrong, like in this
case, whether there is enough manpower to treat it or not.
And if you have
I want to hear your opinion about the following question: If you think
a bug does not belong to your package, do you think it is your duty as a
maintainer to reassign to bug to the package it belongs to or do you
think just closing the bug is fine?
Closing a report merely because it is assigned
Package: wnpp
Severity: wishlist
Owner: Rene Mayorga <[EMAIL PROTECTED]>
* Package name: libhtml-wikiconverter-mediawiki-perl
Version : 0.55
Upstream Author : David J. Iberri <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/dist/HTML-WikiConverter-MediaWiki/
* License
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: qnapi
Version: 0.1.5
Upstream Author: Krzemin <[EMAIL PROTECTED]>
License: GPLv2 or later (some parts are licensed under GPLv2 only)
Homepage: http://krzemin.iglu.cz/qnapi
www.napiprojekt.pl provides a data
On Fri, 18 Apr 2008, Manoj Srivastava wrote:
> What is an ordinary bug submitter's recourse when a bug report is
> closed without resolution?
Reopen the bug once with more information, then if it's closed again
without resolution, contact -devel or similar if they're convinced
that it's a bug whic
On Fri, 18 Apr 2008, Andrei Popescu wrote:
If anybody would confirm that this problem might belong to module-init-tools
I would volunteer to take over the job of proper reassignment - but I
just don't know exactly and "my experts in questions like this" just
refuse proper communication.
See #4
On Thu, 17 Apr 2008 12:17:34 +0200, Bas Wijnen <[EMAIL PROTECTED]> said:
> On Thu, Apr 17, 2008 at 01:44:55AM -0500, Manoj Srivastava wrote:
>> >> > What if the library says "You must call /usr/bin/foo during
>> >> > build"?
>> >>
>> >> How does the library say that? Why can't I just have gcc -o
On Fri, 18 Apr 2008 11:18:52 -0700, Don Armstrong <[EMAIL PROTECTED]> said:
> Closing valid bugs which were merely assigned to the wrong package
> isn't acceptable
My sentiments as well.
> That said, as a submitter, you don't need to reopen the bug to
> reassign it, and playing reopen g
On Fri, Apr 18, 2008 at 02:40:47PM +0200, Andreas Tille wrote:
[...]
> On Tue, 8 Apr 2008 I filed #474964 against linux-2.6:
> Loads pcspkr and others even if explicitely excluded in modprobe.conf
[...]
> If anybody would confirm that this problem might belong to module-init-tools
> I would vol
On Fri, 18 Apr 2008, Andreas Tille wrote:
> I want to hear your opinion about the following question: If you
> think a bug does not belong to your package, do you think it is your
> duty as a maintainer to reassign to bug to the package it belongs to
> or do you think just closing the bug is fine?
On Thu, 17 Apr 2008, Andreas Tille wrote:
I get even at these days 3.4.6 (which is strange anyway) but which gives
no explanation for the 4.1 dependency I faced.
Hi,
I just found out the reason for the problem and most probably it is really
the same reason as reported in bug
If I apply the f
Sorry, copy-paste error.. meant to fwd to [EMAIL PROTECTED] :(
Friday effect probably.
Le vendredi 18 avril 2008 à 18:42 +0200, Olivier Berger a écrit :
> Salut.
>
> Bien-sûr, pour les français/francophones proches, ce sera encore plus
> simple de faire le déplacement...
>
> A vos contributions
Salut.
Bien-sûr, pour les français/francophones proches, ce sera encore plus
simple de faire le déplacement...
A vos contributions ;)
Cordialement,
Message transféré
De: Olivier Berger <[EMAIL PROTECTED]>
À: debian-devel@lists.debian.org
Sujet: Call for contributions on forges
Hello.
I'm requesting contributions from Debian developpers wishing to
present / discuss the topic of the development infrastructure used in
the Debian project (as well as the software forges), at the forecoming
Libre Software Meeting (LSM/RMLL), held in Mont-de-Marsan (France) early
July 2008 (1-
Hi folks,
for the upcoming Hackontest here in Switzerland, we are still
looking for more feature requests:
http://www.hackontest.org/index.php?action=Root-projectDetail%2815%29
The idea is that random teams might implement these features in the
hope that their implementation wins a prize. They
[Thibaut Paumard]
> One of my packages, [1]yorick-yeti has been [2]built successfully on
> all official platforms, including [3]mips on Fri 28 Mar, but the mips
> package is still [2]not installed on the archive. It is held out of
> Lenny for this reason. I sent an e-mail to [EMAIL PROTECTED] on Tu
On Wed, Apr 16, 2008 at 08:58:52PM +0200, Ralf Treinen wrote:
> I will file bugs soon (hopefully before leaving on [VAC] on 18/4). One
> interesting question is: against which of the conflicting packages
> should the bug be filed? The less popular one according to popcon? The
> more recent one in t
Hi,
I want to hear your opinion about the following question: If you think
a bug does not belong to your package, do you think it is your duty as a
maintainer to reassign to bug to the package it belongs to or do you
think just closing the bug is fine?
My understanding of handling bugs is that
Hi,
On Fri, Apr 11, 2008 at 04:13:05PM -0500, Steve M. Robbins wrote:
> On Fri, Apr 11, 2008 at 03:13:15PM -0400, Joshua Judson Rosen wrote:
> >
> > If you guys need some help, I can try updating the packaging for 1.35.
>
> Packaging is not the issue, however. I think I can do that over the
> w
---
Princy Webmanager wants to stay in better touch using some of Google's
coolest new
products.
If you already have Gmail or Google Talk, visit:
http://mail.google.com/mail/b-ccc9bdd8ac-d6e1580952-b3a1e16048ec720a
You'll need to
21 matches
Mail list logo
