micah wrote:
forwarded
https://savannah.nongnu.org/bugs/index.php?func=detailitem&item_id=15281
thanks
The Anarcat wrote:
On Wed Dec 14, 2005 at 06:36:21PM +0100, Ola Lundqvist wrote:
As I said, it's trivial, benign, but should be fixed and I don't know
where else to report this.
If you found this bug using the debian package, you should file it with
the Debian BTS. The reason is because the package maintainer may have
made changes to the upstream code and would know best if this is a local
debian issue, or actually an upstream issue. If the package maintainer
determines that this is not a Debian bug, then he/she files a bug in the
upstream tracker, tags the Debian bug as forwarded with a link to the
upstream submitted bug (which I have done above), and then keeps track
of the fix upstream.
I suggest you also file this upstream. See http://linux-vserver.org/
or just simply send an email to [email protected] describing
this.
Actually, it typically should be the Debian maintainer who does this as
the maintainer knows how to do this properly, and should be actively
cultivating a relationship with upstream so that communication happens
properly.
Addtionally, filing this particular bug is not done by sending an email
to the vserver mailing list, as Enrico (who maintains the upstream
tools) may or may not follow the list. Even if he does, he should not be
unnecessarily burdened with needing to file a bug in the proper bug
tracker so that he can remember to fix it later.
The bug tracker for util-vserver is located here:
https://savannah.nongnu.org/bugs/?group=util-vserver&func=browse&set=open
The proper way to go about this is to browse through the open issues
before submitting a duplicate bug.
BTW, I already submitted a patch on december 16:
https://savannah.nongnu.org/patch/?func=detailitem&item_id=4714
_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver
