Re: Completed: lists.alioth.debian.org migration

Hi Carsten, > it's the only mentioned email contact on > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo > > I suggest to change the text passage in the site then. Messages to that list will be delivered to admin@ from now on. I've found several other requests that were made through

Re: Completed: lists.alioth.debian.org migration

Excerpts from Carsten Schoenert's message of april 25, 2018 11:12 am: Am 25.04.2018 um 10:02 schrieb Alex Muntada: So far I've read the overview on alioth-lists.d.n [1] the correct address to get in contact for requests like this is mail...@alioth-lists.debian.net. [...] The

Re: Completed: lists.alioth.debian.org migration

Hello Alex, Am 25.04.2018 um 10:02 schrieb Alex Muntada: > Hi Carsten, > >> So far I've read the overview on alioth-lists.d.n [1] the correct >> address to get in contact for requests like this is >> mail...@alioth-lists.debian.net. > > AFAICR it's always been admin@. In fact, I don't remember

Re: Completed: lists.alioth.debian.org migration

Hi Carsten, > So far I've read the overview on alioth-lists.d.n [1] the correct > address to get in contact for requests like this is > mail...@alioth-lists.debian.net. AFAICR it's always been admin@. In fact, I don't remember any mention of mailman@. Where did you find that mailman address?

Re: Completed: lists.alioth.debian.org migration

Hello Dominic, Am 20.04.2018 um 12:21 schrieb Dominic Hargreaves: ... >> Except that we would want the forward to only forward user emails and not >> automatic emails sent by the BTS, DAK, etc. since we already get those >> through the package tracker. I'm not sure that they are willing to do >>

Re: Completed: lists.alioth.debian.org migration

On Fri, Apr 20, 2018 at 09:24:48AM +0200, Raphael Hertzog wrote: > On Fri, 20 Apr 2018, Christoph Biedl wrote: > > However, keep in mind I would certainly not agree to that since it's a > > terrible hack, creates a precedent I wouldn't want to see, and mostly: > > There's another option, ask the

Re: Completed: lists.alioth.debian.org migration

On Fri, 20 Apr 2018, Adam Borowski wrote: > On Fri, Apr 20, 2018 at 09:24:48AM +0200, Raphael Hertzog wrote: > > On Fri, 20 Apr 2018, Christoph Biedl wrote: > > > On the other hand I fully agree doing dozens or hundreds of uploads just > > > because an address out of my control became invalid is

Re: Completed: lists.alioth.debian.org migration

On Fri, Apr 20, 2018 at 09:24:48AM +0200, Raphael Hertzog wrote: > On Fri, 20 Apr 2018, Christoph Biedl wrote: > > On the other hand I fully agree doing dozens or hundreds of uploads just > > because an address out of my control became invalid is a huge waste of > > ressources that are better

Re: Completed: lists.alioth.debian.org migration

Hi, On Fri, 20 Apr 2018, Christoph Biedl wrote: > On the other hand I fully agree doing dozens or hundreds of uploads just > because an address out of my control became invalid is a huge waste of > ressources that are better spent elsewhere. However, that's why > alioth-lists was created. We

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

Hi Joël, On Thu, Apr 19, 2018 at 08:02:33PM +0200, Joël Krähemann wrote: > > I just replaced the alioth mail address of gsequencer repository. Thanks for the quick response. > What about an old debian changelog entry? > > -- Joël Krähemann Wed, >

Re: Completed: lists.alioth.debian.org migration

Raphael Hertzog wrote... > Packages maintained by forensics-devel@ and pkg-security-team@ all > have a fixed maintainer email in git. I was not planning on doing any mass > upload right now and I would be really annoyed to have to hand-edit all > changelog entries to add a bug closure. Debian

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

On Thu, Apr 19, 2018 at 09:06:09AM +0200, Andreas Tille wrote: > > OTOH, there are some packages that have users.alioth.debian.org > > e-mail addresses in Maintainer and Uploaders, that may be worth > > dealing with. Andreas, thanks for digging out the facts and informing those affected! --

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

On Thu, Apr 19, 2018 at 3:12 AM, Andreas Tille wrote: > Maintainers: > > udd=# select distinct source, maintainer from packages where release = 'sid' > and maintainer like '%alioth.debian.org%' and maintainer not like > '%lists.alioth.debian.org%' ; >source|

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

Hi, I just replaced the alioth mail address of gsequencer repository. What about an old debian changelog entry? -- Joël Krähemann Wed, 01 Feb 2017 11:14:14 +0100 Bests, Joël On Thu, Apr 19, 2018 at 9:12 AM, Andreas Tille wrote: >

Re: Completed: lists.alioth.debian.org migration

Hello, On Thu, 19 Apr 2018, Christoph Biedl wrote: > > Also, @lists.alioth.debian.org addresses that were *not* migrated now > > result in bounces as expected. Are there already plans for a MBF > > severity RC against all packages with a now-failing maintainer address? > > Following the rule a

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

Hi again, On Thu, Apr 19, 2018 at 09:06:09AM +0200, Andreas Tille wrote: > Hi, > > if you are in CC of this mail please replace your e-mail address > in the named source package in Maintainer and Uploaders field since > the e-mail becomes invalid soon with the shutdown of Alioth. the lists are

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

Hi, if you are in CC of this mail please replace your e-mail address in the named source package in Maintainer and Uploaders field since the e-mail becomes invalid soon with the shutdown of Alioth. On Wed, Apr 18, 2018 at 10:09:40PM +0200, Alex Muntada wrote: > OTOH, there are some packages

Re: Completed: lists.alioth.debian.org migration

Christoph Biedl wrote... > Also, @lists.alioth.debian.org addresses that were *not* migrated now > result in bounces as expected. Are there already plans for a MBF > severity RC against all packages with a now-failing maintainer address? Following the rule a social ecosystem can work only if

Re: About the MBF on now-failing alioth list addresses (was: Completed: lists.alioth.debian.org migration)

Hi Christoph, > First, Dom asked for the analysis that led to my number of somewhat > 1450 affected packages. He got this in private, a refined version > below, it boils down to: Any package with a @lists.alioth.debian.org > address in Maintainer: is affected if and only if the localpart of that

Re: Completed: lists.alioth.debian.org migration

On 17/04/18 22:42, Holger Levsen wrote: > On Tue, Apr 17, 2018 at 10:39:22PM +0200, Christoph Biedl wrote: >> Also, @lists.alioth.debian.org addresses that were *not* migrated now >> result in bounces as expected. Are there already plans for a MBF >> severity RC against all packages with a

Re: Completed: lists.alioth.debian.org migration

On Tuesday, April 17, 2018 08:42:22 PM Holger Levsen wrote: > On Tue, Apr 17, 2018 at 10:39:22PM +0200, Christoph Biedl wrote: > > Also, @lists.alioth.debian.org addresses that were *not* migrated now > > result in bounces as expected. Are there already plans for a MBF > > severity RC against all

Re: Completed: lists.alioth.debian.org migration

Holger Levsen wrote... > please file bugs, so that autoremovals can kick in. Thanks. Sheesh, it's not about removing package but keeping them. By making sure they are in good shape which, among many other things, means there is a working well-defined maintainer contact address.

Re: Completed: lists.alioth.debian.org migration

On Tue, Apr 17, 2018 at 10:39:22PM +0200, Christoph Biedl wrote: > A few questions, though (asking for a friend, of course). It might have > been mentioned before but I have missed it then. > > What is the long-term plan for this service? Indefinitely, or are users > kindly asked to move away

Re: Completed: lists.alioth.debian.org migration

On Tue, Apr 17, 2018 at 10:39:22PM +0200, Christoph Biedl wrote: > Also, @lists.alioth.debian.org addresses that were *not* migrated now > result in bounces as expected. Are there already plans for a MBF > severity RC against all packages with a now-failing maintainer address? > This might become

Re: Completed: lists.alioth.debian.org migration

Mathias Behrle wrote... > Big thanks to all involved also from my side, it is great to have the mailing > lists seamlessly running! Seconded. A few questions, though (asking for a friend, of course). It might have been mentioned before but I have missed it then. What is the long-term plan for

Re: Completed: lists.alioth.debian.org migration

* Dominic Hargreaves: " Completed: lists.alioth.debian.org migration" (Sat, 14 Apr 2018 13:11:56 +0100): > On Fri, Apr 13, 2018 at 06:02:37PM +0100, Dominic Hargreaves wrote[1]: ... > Thanks > -- > > Thanks to the following for their help and support with this