On Sat, 2014-05-03 at 11:48 +0800, Paul Wise wrote: > On Sat, May 3, 2014 at 3:21 AM, Svante Signell wrote: > > > Does the Debian guidelines give any hints on who is responsible to > > report a patch upstream? Is it the bug submitters or the Debian package > > maintainers responsibility (in addition to eventually apply them to the > > packages)? > > Is this in relation to a particular package or situation?
No it is not. The most convenient way to get patches reviewed/accepted upstream is that the maintainer does this since he/she is normally subscribed and follows their mailing/bug report lists. As a bug submitter including patches this can be very cumbersome to do if you have more than a only a few packages reported. Regarding the response from Debian maintainers to patches it varies a lot: Many just don't react at all, some advise to go upstream with/without applying them to the package, some apply patches and don't report upstream and some do both apply and report upstream. Then we have to distinguish which parts are relevant to upstream, some parts are Debian specific, some are upstream material but should stay Debian specific and some are pure upstream. I think a good compromise solution is that the Debian maintainers at least acknowledge the reports and give feedback to the bug submitter (containing all kind of responses). This applies also to wishlist bug reports asking to package a new release giving the reason for doing/not doing that. A lot of packages are far behind upstream, even in experimental. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399190323.8487.44.camel@PackardBell-PC
