How to close bug which should be reported upstream?
Jan Beich
jbeich at vfemail.net
Mon Oct 19 02:06:47 UTC 2015
Lev Serebryakov <lev at serebryakov.spb.ru> writes:
> Hello freebsd-ports,
>
>
> How to close bug which should be reported upstream and is not easily
> fixable by port maintainer?
>
> Closed->WHAT?
RESOLVED->INVALID translates to Closed->Not a Bug. The state is ambiguous
but bugs outside of scope for bugzilla product generally fall there when
they cannot be re-categorized within a project. With contrib/ and ports/
this depends on how much FreeBSD support exists upstream. In case of none
only downstream maintainer can realistically file bugs upstream.
Examples of closed bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195700
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199120
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200167
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200854
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202700
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 602 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20151019/2459d0d2/attachment.bin>
More information about the freebsd-ports
mailing list