On 7 May 2014 01:19, Charles Plessy ple...@debian.org wrote:
Hi Matthias,
your answer exemplifies very well what I mean with “pressed by the machine”…
I will reply on one point only.
Le Wed, May 07, 2014 at 01:46:32AM +0200, Matthias Klose a écrit :
Am 06.05.2014 03:05, schrieb Charles
Am 06.05.2014 03:05, schrieb Charles Plessy:
Le Mon, May 05, 2014 at 08:56:48PM +0200, Bas Wijnen a écrit :
I'm happy to see that there is consensus anyway that forwarding bugs upstream
is the task of the maintainer.
Hi all,
being a package maintainer, I am always uncomfortable when I
Hi Matthias,
your answer exemplifies very well what I mean with “pressed by the machine”…
I will reply on one point only.
Le Wed, May 07, 2014 at 01:46:32AM +0200, Matthias Klose a écrit :
Am 06.05.2014 03:05, schrieb Charles Plessy:
When the first mass rebuilds with GCC and porting
On Sun, May 04, 2014 at 05:36:53PM +0200, Jonas Smedegaard wrote:
I cannot imagine *any* example of a bug reported reported according to
guidelines being a waste of time.
Can you provide examples of that kind of response?
I remember it happening only once, and it was quite a while ago. I
previously on this list Bas Wijnen contributed:
Which means that if the maintainer is unable to do that, the response please
forward this upstream should be interpreted (and perhaps more clearly
written)
as sorry I don't have time, this is how you can try to make things happen
yourself.
Le Mon, May 05, 2014 at 08:56:48PM +0200, Bas Wijnen a écrit :
I'm happy to see that there is consensus anyway that forwarding bugs upstream
is the task of the maintainer.
Hi all,
being a package maintainer, I am always uncomfortable when I have the
impression that I am considered like a
On Mon, May 5, 2014 at 6:05 PM, Charles Plessy ple...@debian.org wrote:
Le Mon, May 05, 2014 at 08:56:48PM +0200, Bas Wijnen a écrit :
I'm happy to see that there is consensus anyway that forwarding bugs upstream
is the task of the maintainer.
Hi all,
being a package maintainer, I am
On Fri, 2 May 2014 21:29:34 +0200, Bas Wijnen wij...@debian.org
wrote:
On Fri, May 02, 2014 at 09:21:15PM +0200, 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
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
Hi,
Thorsten Glaser:
Did you *read* how upstream answered the one thing I *did* forward
myself?
For the benefit of the other readers here, would you please supply a
reference URL?
igli exceptions: a truly awful implementation of quite a nice idea.
igli just about the worst way you could do
Matthias Urlichs dixit:
Thorsten Glaser:
Did you *read* how upstream answered the one thing I *did* forward
myself?
For the benefit of the other readers here, would you please supply a
reference URL?
Sure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728053
igli exceptions: a truly
On Sun, May 04, 2014 at 09:14:50AM +0200, Marc Haber wrote:
I don't think this is very clear from the guidelines, and I have had mixed
responses from maintainers when reporting upstream bugs, varying from
thanks,
I'll report it upstream for you to stop wasting my time, report it upstream
On 05/03/2014 03:21 AM, Svante Signell wrote:
Hi,
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)?
The first one who
Quoting Bas Wijnen (2014-05-04 16:33:08)
On Sun, May 04, 2014 at 09:14:50AM +0200, Marc Haber wrote:
I don't think this is very clear from the guidelines, and I have had
mixed responses from maintainers when reporting upstream bugs,
varying from thanks, I'll report it upstream for you to stop
On Sun, 4 May 2014 16:33:08 +0200, Bas Wijnen wij...@debian.org
wrote:
On Sun, May 04, 2014 at 09:14:50AM +0200, Marc Haber wrote:
I don't think this is very clear from the guidelines, and I have had mixed
responses from maintainers when reporting upstream bugs, varying from
thanks,
I'll
Russ Allbery dixit:
Svante Signell svante.sign...@gmail.com writes:
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)?
I
On Sat, 2014-05-03 at 12:02 +, Thorsten Glaser wrote:
Russ Allbery dixit:
Svante Signell svante.sign...@gmail.com writes:
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
On 2014-05-03, Thorsten Glaser t...@mirbsd.de wrote:
This does not, of course, prevent people like the Mesa maintainers
from refusing to do it. I’ve got no idea how to enforce DevRef on
them, though.
Thank you for volunteering to help forwarding bug reports for the mesa
package.
/Sune
--
Sune Vuorela dixit:
On 2014-05-03, Thorsten Glaser t...@mirbsd.de wrote:
This does not, of course, prevent people like the Mesa maintainers
from refusing to do it. I’ve got no idea how to enforce DevRef on
Thank you for volunteering to help forwarding bug reports for the mesa
Did you *read*
Hi,
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)?
Thanks!
--
To UNSUBSCRIBE, email to
On Fri, May 02, 2014 at 09:21:15PM +0200, 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)?
I don't
Svante Signell svante.sign...@gmail.com writes:
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)?
I don't think we have
Am 02.05.2014 21:21, schrieb Svante Signell:
Hi,
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)?
For any essential
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
Quoting Russ Allbery (r...@debian.org):
That said, the process of forwarding bugs along is sort of annoying in
many cases and may not be a very appealing place for volunteers to spend
their time, so I think it tends to be one of the first things that stops
happening when maintainer teams are
25 matches
Mail list logo
