Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin
* Package name: libapache-session-memcached-perl
Version : 0.03
Upstream Author : Enrico Sorcinelli
* URL : https://metacpan.org/release/Apache-Session-Memcached
* License : Perl 5.8.1 or later
Progr
On Mon, Jan 19, 2015 at 11:31:20AM +, Wookey wrote:
> Am I right that the
> only way to expliticly mail the submitter and the maintainer is to
> look the submitter's mail up in the initial bugrep and just CC it,
> whilst replying to bugnum@b.d.o, which will automatically include the
> maintaine
On Mon, 2015-01-19 at 16:57 -0500, Michael Gilbert wrote:
> Isn't the spam vector already wide open for
> nn-subscr...@bugs.debian.org, which isn't much (ab)used today?
>
> I fail to see how any of the discussed changes open an abuse vector
> that doesn't already exist.
OK, so let me help you
Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin
* Package name: libauthen-htpasswd-perl
Version : 0.171
Upstream Author : Matt S Trout
* URL : https://metacpan.org/release/Authen-Htpasswd
* License : Perl
Programming Lang: Perl
Description :
On Mon, Jan 19, 2015 at 4:41 AM, Russell Stuart wrote:
>> But isn't subscribing participants "natural"?
>
> It may be natural, but IMO you are underestimating the spam vector
> problem.
>
> Debian's bug submission mechanism does not try to verify you control the
> email address you are submitting f
On 19/01/15 01:14, Paul Wise wrote:
> On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
>
>> But isn't subscribing participants "natural"? Posting to a bug
>> report means participation and thus you'd get the follow-ups. Why
>> would you post to a bug report if you aren't interested in what
On Mon, 19. Jan 21:24 Adam Borowski wrote:
> You mean, Ugh? :p
Yes, that's the remake of Ugh, a great C-64/Amiga game but adapted to
modern hardware. :-) It also provides a HTML5 flavour, AFAIK the first
one of its kind in Debian.
signature.asc
Description: Digital signature
On Mon, Jan 19, 2015 at 02:39:47PM +0100, Markus Koschany wrote:
> * Package name: caveexpress
> * URL : http://www.caveproductions.org
> Description : 2D platformer with physic-based gameplay
>
> CaveExpress is a classic 2D platformer with physics-based gameplay and
> dozens
On 19 January 2015 at 08:25, Mathieu Malaterre wrote:
> Steven,
Hi Mathieu,
>
> While being in terrible position to tell you what you should or should
> not do, I'd still suggest you to read:
>
> https://www.debian.org/code_of_conduct
> https://people.debian.org/~enrico/dcg/
>
Thanks, I will gi
Package: wnpp
Severity: wishlist
Owner: Ruben Undheim
* Package name: pyvisa-py
Version : 0.1~20150106gitd86fb71
Upstream Author : Hernan E. Grecco
* URL : https://github.com/hgrecco/pyvisa-py
* License : MIT
Programming Lang: Python
Description : A PyV
Tomas Pospisek writes:
> But isn't subscribing participants "natural"? Posting to a bug report
> means participation and thus you'd get the follow-ups. Why would you
> post to a bug report if you aren't interested in what happens with it,
> how things proceed/evolve?
Most other bug systems requi
Package: wnpp
Severity: wishlist
Owner: Paul Novotny
* Package name: opensurgsim
Version : 0.6.0
Upstream Author : Paul Novotny
* URL : http://www.opensurgsim.org/
* License : Apache 2.0
Programming Lang: C++
Description : A free platform for surgical
Guillem Jover writes ("Re: new pre-dependency: perl{,-base,-modules} -> dpkg
(>= 1.17.17)"):
> On Sun, 2015-01-18 at 20:12:55 +0200, Niko Tyni wrote:
> > In order to fix trigger related wheezy->jessie upgrade failures in
> > xfonts-traditional (#774844, cc'd), I intend to make the main perl
> > bi
Firstly, I should say: I'm sorry that I got the design of this wrong
when I set up the BTS. I hadn't appreciated at the time that bug
reports are actually (amongst other things) ad-hoc mailing lists.
Paul Wise writes ("Re: Who gets an email when with bugreports [was: Re:
Unauthorised activity su
Package: wnpp
Severity: wishlist
Owner: Markus Koschany
* Package name: caveexpress
Version : 2.1
Upstream Author : Martin Gerhardy
* URL : http://www.caveproductions.org
* License : GPL3+, CC-BY-SA-4.0
Programming Lang: C++, Lua
Description : 2D platf
On 2015-01-19 11:31, Wookey wrote:
I recall looking at that list for the 'maintainer and submitter'
option, and being disappointed not to find one. Am I right that the
only way to expliticly mail the submitter and the maintainer is to
look the submitter's mail up in the initial bugrep and just CC
+++ Adam D. Barratt [2015-01-19 11:01 +]:
> On 2015-01-19 10:47, Mattia Rizzolo wrote:
> >On Mon, Jan 19, 2015 at 09:26:41AM +, Wookey wrote:
> >>Can someone remind me what the current rules are (or where it's
> >>written down). I know it doesn't work the way I expect it ought
> >>to, but I
On 2015-01-19 10:47, Mattia Rizzolo wrote:
On Mon, Jan 19, 2015 at 09:26:41AM +, Wookey wrote:
Can someone remind me what the current rules are (or where it's
written down). I know it doesn't work the way I expect it ought to,
but
I forget/never-understood exactly how it does work.
Do mai
On Mon, Jan 19, 2015 at 09:26:41AM +, Wookey wrote:
> Can someone remind me what the current rules are (or where it's
> written down). I know it doesn't work the way I expect it ought to, but
> I forget/never-understood exactly how it does work.
>
> Do maintainers always get the initial mail t
On 2015-01-19 10:03, Eugene Zhukov wrote:
Through my experience this is not the case - even the maintainer
doesn't get mail about a bug.
For example I'm listed as a maintainer of epubcheck package,
No, you're not:
Maintainer: Debian XML/SGML Group
You're listed in the "Uploaders" field, wh
[ CCing debian-release. ]
Hi!
On Sun, 2015-01-18 at 20:12:55 +0200, Niko Tyni wrote:
> In order to fix trigger related wheezy->jessie upgrade failures in
> xfonts-traditional (#774844, cc'd), I intend to make the main perl
> binary packages (perl, perl-base, and perl-modules) Pre-Depend on dpkg
>
Hi,
Am Montag, den 19.01.2015, 19:41 +1000 schrieb Russell Stuart:
> Debian's bug submission mechanism does not try to verify you control the
> email address you are submitting from.
At least trac allows you to put other people’s email address in the CC
header, at least in some configurations.
>
On Mon, Jan 19, 2015 at 11:26 AM, Wookey wrote:
> +++ Paul Wise [2015-01-19 17:14 +0800]:
>> On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
>>
>> > I can understand your point of view and I think also the why but isn't
>> > that position the exception from the rule? That is shouldn't the p
On Mon, 2015-01-19 at 10:03 +0100, Tomas Pospisek wrote:
> Am 19.01.2015 um 02:03 schrieb Ben Hutchings:
> > No, this would turn the BTS into a (worse) spam vector.
> >
> > But the acknowledgement mail should tell you how to subscribe, if you
> > aren't already subscribed.
>
> But isn't subscribi
+++ Paul Wise [2015-01-19 17:14 +0800]:
> On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
>
> > I can understand your point of view and I think also the why but isn't
> > that position the exception from the rule? That is shouldn't the process
> > be optimized for the "common" case and allo
On Mon, Jan 19, 2015 at 05:14:18PM +0800, Paul Wise wrote:
> People often file bugs for issues they discover in software they don't
> use or care about, getting followups to those isn't necessary.
Uh? What's your rationale for this, and in particular for the "often"
part?
Surely the typical use c
On Mon, January 19, 2015 10:14, Paul Wise wrote:
> On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
>
>> But isn't subscribing participants "natural"? Posting to a bug report
>> means participation and thus you'd get the follow-ups. Why would you
>> post to a bug report if you aren't interest
On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
> But isn't subscribing participants "natural"? Posting to a bug report
> means participation and thus you'd get the follow-ups. Why would you
> post to a bug report if you aren't interested in what happens with it,
> how things proceed/evolve
Am 19.01.2015 um 02:03 schrieb Ben Hutchings:
> On Mon, 2015-01-19 at 08:37 +0800, Paul Wise wrote:
>> On Mon, Jan 19, 2015 at 8:06 AM, Don Armstrong wrote:
>>
>>> I'm going to put together a bit more firm of a proposal in the next few
>>> weeks, but I think that basically everything but nnn-done@
On Mon, Jan 19, 2015 at 4:30 PM, Johannes Schauer wrote:
> how about the other way round then:
>
> - by default everything stays as it is and there is no auto subscription
> - by sending an email to the bts I can activate that I'm automatically
>subscribed to all bugs I submitted or contribu
On Mon, Jan 19, 2015 at 9:25 AM, Mathieu Malaterre wrote:
> Steven,
>
> While being in terrible position to tell you what you should or should
> not do, I'd still suggest you to read:
>
> https://www.debian.org/code_of_conduct
> https://people.debian.org/~enrico/dcg/
Just to be clear: I was sugge
Hi,
Quoting Ben Hutchings (2015-01-19 02:03:52)
> On Mon, 2015-01-19 at 08:37 +0800, Paul Wise wrote:
> > I'd very much appreciate the ability to not be auto-subscribed to
> > every bug so please do implement the opt-out thing, preferably before
> > this change is rolled out.
> >
> > Personally,
Steven,
While being in terrible position to tell you what you should or should
not do, I'd still suggest you to read:
https://www.debian.org/code_of_conduct
https://people.debian.org/~enrico/dcg/
On Fri, Jan 16, 2015 at 5:48 PM, Steven Capper wrote:
> Mathieu,
> I'm writing to express my incre
33 matches
Mail list logo
