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 mai
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 https://alioth-lis
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 a
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?
May
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
>> s
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 a
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 a
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 spent
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 have
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 pol
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 so
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 you'
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 now-fail
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 p
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.
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 from
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 r
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
* 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 process!
>
> * Alexander Wirt
19 matches
Mail list logo
