Re: Maintainer address for collab-maint team maintained packages

2012-11-27 Thread Marc Haber
On Mon, Nov 19, 2012 at 06:54:26PM +0100, Arno Töll wrote:
 Thing is, you can't use the QA forwarder because it relies on your
 source control field to learn about actual forwardings. If you would add
 right that address, the result would be an infinite loop because you
 would essentially forward mail to package@packages.debian.org to
 package@packages.debian.org. I hope it is clear why this won't work.

so package@packages.debian.org forwards to all addresses listed in
Maintainer: and Uploaders: of the package in question, while
package@packages.qa.debian.org forwards to all addresses that are
subscribed in the PTS and to package@packages.debian.org?

If that's the case, then the obvious fix would be to have
package@packages.debian.org not forward to
package@packages.debian.org and to have the PTS forbid forwardings
to package@packages.debian.org.

That way, it would be possible to use package@packages.debian.org in
Maintainer:. I don't see anything wrong about this, but maybe I am
missing something.

In the mean time, I'll request an alioth project.

Greetings
Marc

-- 
-
Marc Haber | I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things.Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121127095659.gz28...@torres.zugschlus.de



Re: Maintainer address for collab-maint team maintained packages

2012-11-27 Thread Raphael Hertzog
On Mon, 19 Nov 2012, Arno Töll wrote:
 Thing is, you can't use the QA forwarder because it relies on your
 source control field to learn about actual forwardings. If you would add
 right that address, the result would be an infinite loop because you
 would essentially forward mail to package@packages.debian.org to
 package@packages.debian.org. I hope it is clear why this won't work.

Yeah, but this should be easily fixable... we can fix the script
generating the alias to strip those emails
(/srv/packages.debian.org/bin/build-maintainerdb).

The problem lies elsewhere. The BTS, dak and many Debian services mail
the address listed in the Maintainer field *and* send a copy to the PTS.
This includes packages.debian.org which mail the Maintainer (not
Uploaders) and the PTS.

If you put @packages.debian.org as Maintainer, the flow of email is
duplicated. Once via @packages.debian.org and once directly via the PTS.

This is also fixable but it's less easy to do it in a clean way, except by
teaching this special case to all services... which is painful.

It's one of the reason which pushed me to start
http://dep.debian.net/deps/dep2/ but alas I'm too busy to go forward with
it currently.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121127145422.ga29...@x230-buxy.home.ouaza.com



Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Marc Haber
Hi,

I am participating in a team-maintained package which is hosted on
collab-maint. We would like to have the Maintainer: address of that
package to forward to all members of the team, preferably by setting
an address there that forwards to the PTS, having team members and
other interested parties subscribed there.

This seems to be harder to do than I imagined.

package@packages.qa.debian.org wants a certain header to be set for
the message to be forwarded.

package@packages.debian.org seems to add that header automatically
before forwarding to the PTS, but using that address as Maintainer: is
a lintian _error_ (not even a warning) (Severity: serious, Certainty:
certain).

There do not seem to be public mailing lists on the collab-maint
Alioth project.

Do we really need to create a dedicated Alioth project just to get a
mailing list which can be used as Maintainer? Or am I missing a
policy-compliant possibility to do this with available resources?

Greetings
Marc

-- 
-
Marc Haber | I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things.Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121119142855.gh28...@torres.zugschlus.de



Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Bart Martens
On Mon, Nov 19, 2012 at 03:28:55PM +0100, Marc Haber wrote:
 Hi,

Hi Marc,

 
 I am participating in a team-maintained package which is hosted on
 collab-maint.

Which package ?

 We would like to have the Maintainer: address of that
 package to forward to all members of the team,

Why would you want to do that ? I mean, is the package you work on related to
all other maintainers maintaining other packages in collab-maint ?

http://wiki.debian.org/Teams/CollabMaint
not connected to any other teams

 preferably by setting
 an address there that forwards to the PTS, having team members and
 other interested parties subscribed there.
 
 This seems to be harder to do than I imagined.
 
 package@packages.qa.debian.org wants a certain header to be set for
 the message to be forwarded.
 
 package@packages.debian.org seems to add that header automatically
 before forwarding to the PTS, but using that address as Maintainer: is
 a lintian _error_ (not even a warning) (Severity: serious, Certainty:
 certain).

Would modifying lintian be a solution for your problem ?

 
 There do not seem to be public mailing lists on the collab-maint
 Alioth project.

Does this one not work ?
http://lists.alioth.debian.org/mailman/listinfo/collab-maint-devel
To post a message to all the list members, send email to
collab-maint-de...@lists.alioth.debian.org.

 
 Do we really need to create a dedicated Alioth project just to get a
 mailing list which can be used as Maintainer? Or am I missing a
 policy-compliant possibility to do this with available resources?

I agree that creating an Alioth project just for the mailing list feels
somewhat uncomfortable.

Regards,

Bart Martens


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121119173458.ga28...@master.debian.org



Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Marc Haber
On Mon, Nov 19, 2012 at 05:34:58PM +, Bart Martens wrote:
 On Mon, Nov 19, 2012 at 03:28:55PM +0100, Marc Haber wrote:
  I am participating in a team-maintained package which is hosted on
  collab-maint.
 
 Which package ?

If that has anything to do with it, it's libopendbx, which has not yet
been pushed to collab-maint.

  We would like to have the Maintainer: address of that
  package to forward to all members of the team,
 
 Why would you want to do that ? I mean, is the package you work on related to
 all other maintainers maintaining other packages in collab-maint ?

Misunderstanding, either accidental or deliberate. I want the
Maintainer address to forward to all people listed in Uploaders: of
the respective package, not to all 519 members of the collab-maint
Alioth project. I am not out of my mind.

 http://wiki.debian.org/Teams/CollabMaint
 not connected to any other teams

I believe that I am working well within the definition of
collab-maint, thanks for trying to ask in a very subtle way.

 Would modifying lintian be a solution for your problem ?

Probably not, since the people behind lintian usually have sound
reasons for putting in errors and warnings, especially such with
Certainty: certain.

  There do not seem to be public mailing lists on the collab-maint
  Alioth project.
 
 Does this one not work ?
 http://lists.alioth.debian.org/mailman/listinfo/collab-maint-devel
 To post a message to all the list members, send email to
 collab-maint-de...@lists.alioth.debian.org.

https://alioth.debian.org/projects/collab-maint/
Mailing Lists (0 public mailing lists)

  Do we really need to create a dedicated Alioth project just to get a
  mailing list which can be used as Maintainer? Or am I missing a
  policy-compliant possibility to do this with available resources?
 
 I agree that creating an Alioth project just for the mailing list feels
 somewhat uncomfortable.

Indeed.

Greetings
Marc, now tryin to bring blood pressure down again

-- 
-
Marc Haber | I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things.Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121119175108.gk28...@torres.zugschlus.de



Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Arno Töll
Hi,

On 11/19/2012 03:28 PM, Marc Haber wrote:
 package@packages.debian.org seems to add that header automatically
 before forwarding to the PTS, but using that address as Maintainer: is
 a lintian _error_ (not even a warning) (Severity: serious, Certainty:
 certain).

Thanks for trying! I originally implemented that check out of a stupid
idea Paul Tag. came up with, but I'm glad it really helped someone to
find an error! :-)


Thing is, you can't use the QA forwarder because it relies on your
source control field to learn about actual forwardings. If you would add
right that address, the result would be an infinite loop because you
would essentially forward mail to package@packages.debian.org to
package@packages.debian.org. I hope it is clear why this won't work.


To answer your question: Yes, you really need a top level Alioth project
if you want your own mailing list (or any other third party hosted service).

That said, I'd be very glad to have some mailing list Debian service
different to lists.d.o for such lightweight list management purposes.


-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D



signature.asc
Description: OpenPGP digital signature


Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Paul Tagliamonte
On Mon, Nov 19, 2012 at 12:51 PM, Marc Haber mh+debian-ment...@zugschlus.de
 wrote:

 On Mon, Nov 19, 2012 at 05:34:58PM +, Bart Martens wrote:
  On Mon, Nov 19, 2012 at 03:28:55PM +0100, Marc Haber wrote:
   I am participating in a team-maintained package which is hosted on
   collab-maint.
 
  Which package ?

 If that has anything to do with it, it's libopendbx, which has not yet
 been pushed to collab-maint.

   We would like to have the Maintainer: address of that
   package to forward to all members of the team,
 
  Why would you want to do that ? I mean, is the package you work on
 related to
  all other maintainers maintaining other packages in collab-maint ?

 Misunderstanding, either accidental or deliberate. I want the
 Maintainer address to forward to all people listed in Uploaders: of
 the respective package, not to all 519 members of the collab-maint
 Alioth project. I am not out of my mind.

  http://wiki.debian.org/Teams/CollabMaint
  not connected to any other teams

 I believe that I am working well within the definition of
 collab-maint, thanks for trying to ask in a very subtle way.

  Would modifying lintian be a solution for your problem ?

 Probably not, since the people behind lintian usually have sound
 reasons for putting in errors and warnings, especially such with
 Certainty: certain.


Yeah, I think I might have had something to do with this at some point. I
remember wondering if it would lead to a MUA loop (since it would send to
it's self)



   There do not seem to be public mailing lists on the collab-maint
   Alioth project.
 
  Does this one not work ?
  http://lists.alioth.debian.org/mailman/listinfo/collab-maint-devel
  To post a message to all the list members, send email to
  collab-maint-de...@lists.alioth.debian.org.

 https://alioth.debian.org/projects/collab-maint/
 Mailing Lists (0 public mailing lists)

   Do we really need to create a dedicated Alioth project just to get a
   mailing list which can be used as Maintainer? Or am I missing a
   policy-compliant possibility to do this with available resources?
 
  I agree that creating an Alioth project just for the mailing list feels
  somewhat uncomfortable.

 Indeed.

 Greetings
 Marc, now tryin to bring blood pressure down again

 --

 -
 Marc Haber | I don't trust Computers. They | Mailadresse im Header
 Mannheim, Germany  |  lose things.Winona Ryder | Fon: *49 621 31958061
 Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062


 --
 To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive:
 http://lists.debian.org/20121119175108.gk28...@torres.zugschlus.de




-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Sune Vuorela
On 2012-11-19, Arno Töll a...@debian.org wrote:
 That said, I'd be very glad to have some mailing list Debian service
 different to lists.d.o for such lightweight list management purposes.

wasn't there a teams.dn ?

/Sune


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnkal18a.me.nos...@sshway.ssh.pusling.com



Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Arno Töll
On 11/19/2012 08:10 PM, Sune Vuorela wrote:
 On 2012-11-19, Arno Töll a...@debian.org wrote:
 That said, I'd be very glad to have some mailing list Debian service
 different to lists.d.o for such lightweight list management purposes.
 
 wasn't there a teams.dn ?

Does not seem to be alive anymore and definitively B.D. (before
daemonkeeper). Aside, I think there also was a similar concept driven by
dba as debian-maintainers.orgorso.

-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D



signature.asc
Description: OpenPGP digital signature


Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Bart Martens
On Mon, Nov 19, 2012 at 06:51:08PM +0100, Marc Haber wrote:
 On Mon, Nov 19, 2012 at 05:34:58PM +, Bart Martens wrote:
  On Mon, Nov 19, 2012 at 03:28:55PM +0100, Marc Haber wrote:
   I am participating in a team-maintained package which is hosted on
   collab-maint.
  
  Which package ?
 
 If that has anything to do with it, it's libopendbx, which has not yet
 been pushed to collab-maint.
 
   We would like to have the Maintainer: address of that
   package to forward to all members of the team,
  
  Why would you want to do that ? I mean, is the package you work on related 
  to
  all other maintainers maintaining other packages in collab-maint ?
 
 Misunderstanding, either accidental or deliberate. I want the
 Maintainer address to forward to all people listed in Uploaders: of
 the respective package, not to all 519 members of the collab-maint
 Alioth project. I am not out of my mind.

Accidental misunderstanding.  I understood all members of the team as all
members of collab-maint, and now I understand it as the co-maintainers of the
package.

Regards,

Bart Martens


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121119192007.ga18...@master.debian.org



Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Charles Plessy
Le Mon, Nov 19, 2012 at 06:54:26PM +0100, Arno Töll a écrit :
 
 On 11/19/2012 03:28 PM, Marc Haber wrote:
  package@packages.debian.org seems to add that header automatically
  before forwarding to the PTS, but using that address as Maintainer: is
  a lintian _error_ (not even a warning) (Severity: serious, Certainty:
  certain).
 
 Thing is, you can't use the QA forwarder because it relies on your
 source control field to learn about actual forwardings. If you would add
 right that address, the result would be an infinite loop because you
 would essentially forward mail to package@packages.debian.org to
 package@packages.debian.org. I hope it is clear why this won't work.

Hi all,

I think that the best way forward would be to fix the PTS and remove the
infinite loop.  This would be tremendously useful for many packages that are
collectively maintained.

I have no time to do it myself, but see the following wiki page to contribute.

  http://wiki.debian.org/qa.debian.org/pts

Have a nice day,

-- 
Charles Plessy
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121119230404.gb10...@falafel.plessy.net



Re: Maintainer address for collab-maint team maintained packages

2012-11-19 Thread Paul Tagliamonte
On Tue, Nov 20, 2012 at 08:04:04AM +0900, Charles Plessy wrote:
 Le Mon, Nov 19, 2012 at 06:54:26PM +0100, Arno Töll a écrit :
  
  On 11/19/2012 03:28 PM, Marc Haber wrote:
   package@packages.debian.org seems to add that header automatically
   before forwarding to the PTS, but using that address as Maintainer: is
   a lintian _error_ (not even a warning) (Severity: serious, Certainty:
   certain).
  
  Thing is, you can't use the QA forwarder because it relies on your
  source control field to learn about actual forwardings. If you would add
  right that address, the result would be an infinite loop because you
  would essentially forward mail to package@packages.debian.org to
  package@packages.debian.org. I hope it is clear why this won't work.
 
 Hi all,
 
 I think that the best way forward would be to fix the PTS and remove the
 infinite loop.  This would be tremendously useful for many packages that are
 collectively maintained.

This seems pretty silly - the Maintainer: field should be useful, not a
hack just to get email (more preceisely, it says: The maintainer of this
package is the maintainer of this package)

I'd much rather see something like what Arno is talking about, at least
that's a *bit* more descriptive and less tautological

 
 I have no time to do it myself, but see the following wiki page to contribute.
 
   http://wiki.debian.org/qa.debian.org/pts
 
 Have a nice day,
 
 -- 
 Charles Plessy
 Tsurumi, Kanagawa, Japan
 
 
 -- 
 To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20121119230404.gb10...@falafel.plessy.net
 

Cheery-bye,
  Paul

-- 
 .''`.  Paul Tagliamonte paul...@debian.org
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature