Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Completed: lists.alioth.debian.org migration
18 views
Skip to first unread message
Mathias Behrle
Apr 16, 2018, 7:40:03 AM4/16/18
to
* 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 for his assistance as current alioth admin
> * Julien Cristau and Tollef Fog Heen for the DNS/redirection changes
> * Alex Muntada and Bernhard Schmidt, co-admins of the new service
>
> Dominic.
Big thanks to all involved also from my side, it is great to have the mailing
lists seamlessly running!
Mathias
--
Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
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 for his assistance as current alioth admin
> * Julien Cristau and Tollef Fog Heen for the DNS/redirection changes
> * Alex Muntada and Bernhard Schmidt, co-admins of the new service
>
> Dominic.
Big thanks to all involved also from my side, it is great to have the mailing
lists seamlessly running!
Mathias
--
Mathias Behrle
PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
Christoph Biedl
Apr 17, 2018, 4:50:03 PM4/17/18
to
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 this service? Indefinitely, or are users
kindly asked to move away from these addresses when convenient? In the
latter case lintian should emit according hints since even then this
might take several years.
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 rather messy, I've counted some 1450 packages.
Christoph
> Big thanks to all involved also from my side, it is great to have the mailing
> lists seamlessly running!
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 these addresses when convenient? In the
latter case lintian should emit according hints since even then this
might take several years.
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 rather messy, I've counted some 1450 packages.
Christoph
Holger Levsen
Apr 17, 2018, 4:50:03 PM4/17/18
to
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 rather messy, I've counted some 1450 packages.
please file bugs, so that autoremovals can kick in. Thanks.
> 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 rather messy, I've counted some 1450 packages.
--
cheers,
Holger
Dominic Hargreaves
Apr 17, 2018, 5:10:02 PM4/17/18
to
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 these addresses when convenient? In the
> latter case lintian should emit according hints since even then this
> might take several years.
We committed to supporting it for 1-2 release cycles. Speaking for myself,
> 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 these addresses when convenient? In the
> latter case lintian should emit according hints since even then this
> might take several years.
I plan to take a step back after the dust has settled and we see how
running the service works out before setting a firm timeline.
> 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 rather messy, I've counted some 1450 packages.
but I am surprised it is so high. Can you share the results of
that analysis? It would be interesting to see what the distribution of
packages to lists is.
Thanks,
Dominic.
Christoph Biedl
Apr 18, 2018, 1:50:02 AM4/18/18
to
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.
> please file bugs, so that autoremovals can kick in. Thanks.
they are in good shape which, among many other things, means there is a
working well-defined maintainer contact address.
Scott Kitterman
Apr 18, 2018, 2:50:03 AM4/18/18
to
to alioth lists going away. Yesterday and today it was 5 RC bugs and one
package rejected from New.
Please, check you've got a working maintainer address before doing a new
upload. You'll end up waiting a long time for the Accepted mail if you don't.
Scott K
Emilio Pozuelo Monfort
Apr 18, 2018, 3:10:02 AM4/18/18
to
Emilio
Alex Muntada
Apr 18, 2018, 4:20:03 PM4/18/18
to
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
> address is listed in
> <https://alioth-lists-archive.debian.net/pipermail/>. Since I'd like to
> avoid false and missing alerts if ever possible, I'm hereby asking for
> explicit confirmation this assumption is correct.
IIRC, the lists with private archives that nobody requested to
migrate to alioth-lists are also failing since last weekend,
i.e. alioth-lists-archive has only those lists with public
archives that nobody requested to migrate.
I'm not sure that we have a list of lists that haven't been
migrated, but I guess we can easily get that list.
OTOH, there are some packages that have users.alioth.debian.org
e-mail addresses in Maintainer and Uploaders, that may be worth
dealing with.
Cheers,
Alex
> 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
> address is listed in
> <https://alioth-lists-archive.debian.net/pipermail/>. Since I'd like to
> avoid false and missing alerts if ever possible, I'm hereby asking for
> explicit confirmation this assumption is correct.
IIRC, the lists with private archives that nobody requested to
migrate to alioth-lists are also failing since last weekend,
i.e. alioth-lists-archive has only those lists with public
archives that nobody requested to migrate.
I'm not sure that we have a list of lists that haven't been
migrated, but I guess we can easily get that list.
OTOH, there are some packages that have users.alioth.debian.org
e-mail addresses in Maintainer and Uploaders, that may be worth
dealing with.
Cheers,
Alex
Christoph Biedl
Apr 19, 2018, 2:20:03 AM4/19/18
to
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're willing to
do a bit more than your actual chores, I'll organize this MBF. Currently
some coordination with the alioth-lists maintainers is happening, also
we might implement some shortcuts for deceased lists that maintain
*many* packages, some numbers have three digits ...
Stay tuned.
Christoph
> 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?
do a bit more than your actual chores, I'll organize this MBF. Currently
some coordination with the alioth-lists maintainers is happening, also
we might implement some shortcuts for deceased lists that maintain
*many* packages, some numbers have three digits ...
Stay tuned.
Christoph
Andreas Tille
Apr 19, 2018, 3:10:02 AM4/19/18
to
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 that have users.alioth.debian.org
> e-mail addresses in Maintainer and Uploaders, that may be worth
> dealing with.
udd=# select distinct source, maintainer from packages where maintainer like '%alioth.debian.org%' and maintainer not like '%lists.alioth.debian.org%' ;
source | maintainer
---------------------+----------------------------------------------------
gconfmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
glibmm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
gnome-vfsmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
gtkmm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
gtkmm-documentation | Deng Xiyue <manphi...@users.alioth.debian.org>
libglademm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomecanvasmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomemm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomeuimm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
libnotifymm | Deng Xiyue <manphi...@users.alioth.debian.org>
libxml++2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
scim-pinyin | Ming Hua <minghu...@users.alioth.debian.org>
scim-tables | Ming Hua <minghu...@users.alioth.debian.org>
scim-uim | Ming Hua <minghu...@users.alioth.debian.org>
(14 rows)
I've added those two maintainers in CC.
Similar with Uploaders (I've excluded in the list the sources that are
mentioned above):
udd=# select distinct source, uploaders from sources where uploaders like '%alioth.debian.org%' and uploaders not like '%lists.alioth.debian.org%' and source not in ( select distinct source from packages where maintainer like '%alioth.debian.org%' and maintainer not like '%lists.alioth.debian.org%');
source | uploaders
--------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
atkmm1.6 | Deng Xiyue <manphi...@users.alioth.debian.org>, Michael Biebl <bi...@debian.org>, Krzysztof Klimonda <kkli...@syntaxhighlighted.com>
autoconf-archive | Deng Xiyue <manphi...@users.alioth.debian.org>
glade-3 | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Loic Minier <lo...@dooz.org>, Michael Biebl <bi...@debian.org>
glade-3 | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Loic Minier <lo...@dooz.org>, Sebastian Dröge <sl...@debian.org>
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>,
gtkmm3.0 | Deng Xiyue <manphi...@users.alioth.debian.org>, Emilio Pozuelo Monfort <po...@debian.org>, Michael Biebl <bi...@debian.org>, Sebastian Dröge <sl...@debian.org>
libgtksourceviewmm | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Michael Biebl <bi...@debian.org>
libgtksourceviewmm | Deng Xiyue <manphi...@users.alioth.debian.org>, Loic Minier <lo...@dooz.org>, Michael Biebl <bi...@debian.org>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Martin Pitt <mp...@debian.org>, Michael Biebl <bi...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Martin Pitt <mp...@debian.org>, Michael Biebl <bi...@debian.org>, Sebastian Dröge <sl...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Michael Biebl <bi...@debian.org>, Sebastian Dröge <sl...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
postgrey | Jon Daley <jondale...@alioth.debian.org>
scim | Osamu Aoki <os...@debian.org>, LI Daobing <lida...@debian.org>, Ming Hua <minghu...@users.alioth.debian.org>
scim-hangul | Ming Hua <minghu...@users.alioth.debian.org>
scim-m17n | Osamu Aoki <os...@debian.org>, Ming Hua <minghu...@users.alioth.debian.org>
(16 Zeilen)
Kind regards
Andreas.
--
http://fam-tille.de
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 that have users.alioth.debian.org
> e-mail addresses in Maintainer and Uploaders, that may be worth
> dealing with.
source | maintainer
---------------------+----------------------------------------------------
gconfmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
glibmm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
gnome-vfsmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
gtkmm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
gtkmm-documentation | Deng Xiyue <manphi...@users.alioth.debian.org>
libglademm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomecanvasmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomemm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomeuimm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
libnotifymm | Deng Xiyue <manphi...@users.alioth.debian.org>
libxml++2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
scim-pinyin | Ming Hua <minghu...@users.alioth.debian.org>
scim-tables | Ming Hua <minghu...@users.alioth.debian.org>
scim-uim | Ming Hua <minghu...@users.alioth.debian.org>
(14 rows)
I've added those two maintainers in CC.
Similar with Uploaders (I've excluded in the list the sources that are
mentioned above):
udd=# select distinct source, uploaders from sources where uploaders like '%alioth.debian.org%' and uploaders not like '%lists.alioth.debian.org%' and source not in ( select distinct source from packages where maintainer like '%alioth.debian.org%' and maintainer not like '%lists.alioth.debian.org%');
source | uploaders
--------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
atkmm1.6 | Deng Xiyue <manphi...@users.alioth.debian.org>, Michael Biebl <bi...@debian.org>, Krzysztof Klimonda <kkli...@syntaxhighlighted.com>
autoconf-archive | Deng Xiyue <manphi...@users.alioth.debian.org>
glade-3 | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Loic Minier <lo...@dooz.org>, Michael Biebl <bi...@debian.org>
glade-3 | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Loic Minier <lo...@dooz.org>, Sebastian Dröge <sl...@debian.org>
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>,
gtkmm3.0 | Deng Xiyue <manphi...@users.alioth.debian.org>, Emilio Pozuelo Monfort <po...@debian.org>, Michael Biebl <bi...@debian.org>, Sebastian Dröge <sl...@debian.org>
libgtksourceviewmm | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Michael Biebl <bi...@debian.org>
libgtksourceviewmm | Deng Xiyue <manphi...@users.alioth.debian.org>, Loic Minier <lo...@dooz.org>, Michael Biebl <bi...@debian.org>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Martin Pitt <mp...@debian.org>, Michael Biebl <bi...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Martin Pitt <mp...@debian.org>, Michael Biebl <bi...@debian.org>, Sebastian Dröge <sl...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Michael Biebl <bi...@debian.org>, Sebastian Dröge <sl...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
postgrey | Jon Daley <jondale...@alioth.debian.org>
scim | Osamu Aoki <os...@debian.org>, LI Daobing <lida...@debian.org>, Ming Hua <minghu...@users.alioth.debian.org>
scim-hangul | Ming Hua <minghu...@users.alioth.debian.org>
scim-m17n | Osamu Aoki <os...@debian.org>, Ming Hua <minghu...@users.alioth.debian.org>
(16 Zeilen)
Kind regards
Andreas.
--
http://fam-tille.de
Andreas Tille
Apr 19, 2018, 3:20:02 AM4/19/18
to
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 definitely shorter if it is restricted to release='sid'
which is the only thing we can change (and Ming Hua
<minghu...@users.alioth.debian.org> does not need to change
anything anymore - thanks for doing this pro-actively):
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 | maintainer
---------------------+----------------------------------------------------
Uploaders (here is even a duplicate, probably due to different arches):
udd=# select distinct source, uploaders from sources where uploaders like '%alioth.debian.org%' and uploaders not like '%lists.alioth.debian.org%' and source not in ( select distinct source from packages where maintainer like '%alioth.debian.org%' and maintainer not like '%lists.alioth.debian.org%');
udd=# select distinct source, uploaders from sources where release = 'sid' and uploaders like '%alioth.debian.org%' and uploaders not like '%lists.alioth.debian.org%' and source not in ( select distinct source from packages where maintainer like '%alioth.debian.org%' and maintainer not like '%lists.alioth.debian.org%');
source | uploaders
--------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------
(7 Zeilen)
Kind regards
Andreas.
--
http://fam-tille.de
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.
which is the only thing we can change (and Ming Hua
<minghu...@users.alioth.debian.org> does not need to change
anything anymore - thanks for doing this pro-actively):
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 | maintainer
---------------------+----------------------------------------------------
libglademm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
libgnomecanvasmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
(2 Zeilen)
libgnomecanvasmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
Uploaders (here is even a duplicate, probably due to different arches):
udd=# select distinct source, uploaders from sources where uploaders like '%alioth.debian.org%' and uploaders not like '%lists.alioth.debian.org%' and source not in ( select distinct source from packages where maintainer like '%alioth.debian.org%' and maintainer not like '%lists.alioth.debian.org%');
source | uploaders
--------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------
atkmm1.6 | Deng Xiyue <manphi...@users.alioth.debian.org>, Michael Biebl <bi...@debian.org>, Krzysztof Klimonda <kkli...@syntaxhighlighted.com>
autoconf-archive | Deng Xiyue <manphi...@users.alioth.debian.org>
autoconf-archive | Deng Xiyue <manphi...@users.alioth.debian.org>
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>,
gsequencer | Joël Krähemann <jkraehem...@users.alioth.debian.org>, IOhannes m zmölnig (Debian/GNU) <umla...@debian.org>,
libgtksourceviewmm | Deng Xiyue <manphi...@users.alioth.debian.org>, Josselin Mouette <jo...@debian.org>, Michael Biebl <bi...@debian.org>
pangomm | Deng Xiyue <manphi...@users.alioth.debian.org>, Martin Pitt <mp...@debian.org>, Michael Biebl <bi...@debian.org>, Michael Casadevall <sonicm...@gmail.com>
postgrey | Jon Daley <jondale...@alioth.debian.org>
(7 Zeilen)
Kind regards
Andreas.
http://fam-tille.de
Raphael Hertzog
Apr 19, 2018, 3:30:02 AM4/19/18
to
Hello,
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.
So please don't file bugs for those. However a new check and/or a ping a
few months before the freeze would certainly be welcome.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
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.
So please don't file bugs for those. However a new check and/or a ping a
few months before the freeze would certainly be welcome.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
Joël Krähemann
Apr 19, 2018, 2:10:02 PM4/19/18
to
Hi,
I just replaced the alioth mail address of gsequencer repository. What about
an old debian changelog entry?
-- Joël Krähemann <jkraehem...@users.alioth.debian.org> Wed,
01 Feb 2017 11:14:14 +0100
Bests,
Joël
I just replaced the alioth mail address of gsequencer repository. What about
an old debian changelog entry?
-- Joël Krähemann <jkraehem...@users.alioth.debian.org> Wed,
01 Feb 2017 11:14:14 +0100
Bests,
Joël
Jeremy Bicha
Apr 19, 2018, 2:40:03 PM4/19/18
to
On Thu, Apr 19, 2018 at 3:12 AM, Andreas Tille <and...@an3as.eu> 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 | maintainer
> ---------------------+----------------------------------------------------
> libglademm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
> libgnomecanvasmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
Neither of those 2 packages are in Testing and it's intended for them
> 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 | maintainer
> ---------------------+----------------------------------------------------
> libglademm2.4 | Deng Xiyue <manphi...@users.alioth.debian.org>
> libgnomecanvasmm2.6 | Deng Xiyue <manphi...@users.alioth.debian.org>
to be removed from Unstable "soon".
Thanks,
Jeremy Bicha
Holger Levsen
Apr 19, 2018, 4:40:02 PM4/19/18
to
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!
> > OTOH, there are some packages that have users.alioth.debian.org
> > e-mail addresses in Maintainer and Uploaders, that may be worth
> > dealing with.
--
cheers,
Holger
Christoph Biedl
Apr 20, 2018, 1:10:03 AM4/20/18
to
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 policy has a clear statement on the validity of the address in
the Maintainer: field. I fully support this "must" requirement, that's
why I'm doing this cleanup job - and not because I'm a huge fan of
beaurocratic processes.
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.
So I see two options: Either get wide consensus packages like yours are
not considered rc-buggy for the time being, also make sure it's assured
important mails like bug reports do reach people who are in charge of
the respective package.
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 alioth-list administrators to create an
according forward. For you, this should take less time than writing an
answer to this message, for them hopefully not much longer.
> So please don't file bugs for those.
Noted. But anybody could do this as well.
Christoph
> 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.
the Maintainer: field. I fully support this "must" requirement, that's
why I'm doing this cleanup job - and not because I'm a huge fan of
beaurocratic processes.
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.
So I see two options: Either get wide consensus packages like yours are
not considered rc-buggy for the time being, also make sure it's assured
important mails like bug reports do reach people who are in charge of
the respective package.
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 alioth-list administrators to create an
according forward. For you, this should take less time than writing an
answer to this message, for them hopefully not much longer.
> So please don't file bugs for those.
Christoph
Andreas Tille
Apr 20, 2018, 2:10:02 AM4/20/18
to
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 <jkraehem...@users.alioth.debian.org> Wed,
> 01 Feb 2017 11:14:14 +0100
These changelog entries do not make it into apt cache, UDD and the tools
that are consuming these data. If you adapt d/control and the recent
changelog entry fits the ID you gave in d/control that's fine.
BTW, I guess that lots of old changelog entries are containing invalid
e-mail addresses (including my first packages) - so there is no point in
change the past.
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.
> What about an old debian changelog entry?
>
> -- Joël Krähemann <jkraehem...@users.alioth.debian.org> Wed,
> 01 Feb 2017 11:14:14 +0100
that are consuming these data. If you adapt d/control and the recent
changelog entry fits the ID you gave in d/control that's fine.
BTW, I guess that lots of old changelog entries are containing invalid
e-mail addresses (including my first packages) - so there is no point in
change the past.
Raphael Hertzog
Apr 20, 2018, 3:30:02 AM4/20/18
to
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 switched to a common mailing list on lists.debian.org:
https://lists.debian.org/debian-security-tools/
But this list should not get bug reports and usual package maintainance
mail. It's a discussion list between team members.
> So I see two options: Either get wide consensus packages like yours are
> not considered rc-buggy for the time being, also make sure it's assured
> important mails like bug reports do reach people who are in charge of
> the respective package.
Package maintainers are subscribed to team packages through the package
tracker (either individually or through the team):
https://tracker.debian.org/teams/pkg-security/
> 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 alioth-list administrators to create an
> according forward. For you, this should take less time than writing an
> answer to this message, for them hopefully not much longer.
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
something like this, it would require local delivery to something like
procmail.
Still I'm ccing them to get their feedback on this.
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.
https://lists.debian.org/debian-security-tools/
But this list should not get bug reports and usual package maintainance
mail. It's a discussion list between team members.
> So I see two options: Either get wide consensus packages like yours are
> not considered rc-buggy for the time being, also make sure it's assured
> important mails like bug reports do reach people who are in charge of
> the respective package.
tracker (either individually or through the team):
https://tracker.debian.org/teams/pkg-security/
> 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 alioth-list administrators to create an
> according forward. For you, this should take less time than writing an
> answer to this message, for them hopefully not much longer.
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
something like this, it would require local delivery to something like
procmail.
Still I'm ccing them to get their feedback on this.
Adam Borowski
Apr 20, 2018, 4:20:02 AM4/20/18
to
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 elsewhere. However, that's why
> > alioth-lists was created.
>
> We have switched to a common mailing list on lists.debian.org:
> https://lists.debian.org/debian-security-tools/
>
> But this list should not get bug reports and usual package maintainance
> mail. It's a discussion list between team members.
A lot of other teams are in this situation. And no one seems to know what
> 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 switched to a common mailing list on lists.debian.org:
> https://lists.debian.org/debian-security-tools/
>
> But this list should not get bug reports and usual package maintainance
> mail. It's a discussion list between team members.
are we supposed to do. So the results are quite... random.
For example, on my packages:
4 have Debian Fonts Task Force <pkg-fon...@lists.alioth.debian.org>
1 has Debian Desktop Theme Team <darkcold-...@packages.debian.org>
2 (in NEW) have debian...@lists.debian.org
The first four are traditional, and just became buggy as that list has been
migrated to l.d.o rather than not-yet-then-announced alioth-lists (which is,
as I understand, only a temporary measure). I need to fix those.
The next one, has only the human name matching, with some crap as e-mail.
Most tools match by the latter, thus this scheme doesn't seem to work. I'll
change it as soon as anyone tells me _what_ to switch to.
The last two have a good working maintainer address, but violate the rules
for l.d.o lists (as you say, these shouldn't get maintainership mails).
> > So I see two options: Either get wide consensus packages like yours are
> > not considered rc-buggy for the time being, also make sure it's assured
> > important mails like bug reports do reach people who are in charge of
> > the respective package.
>
> Package maintainers are subscribed to team packages through the package
> tracker (either individually or through the team):
> https://tracker.debian.org/teams/pkg-security/
forgotten.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ ... what's the frequency of that 5V DC?
⠈⠳⣄⠀⠀⠀⠀
Alexander Wirt
Apr 20, 2018, 4:30:02 AM4/20/18
to
maintainership **only** lists. If you have a combined discussion and
maintainership mail list thats fine.
Alex - Debian Listmaster
Dominic Hargreaves
Apr 20, 2018, 6:30:02 AM4/20/18
to
On Fri, Apr 20, 2018 at 09:24:48AM +0200, Raphael Hertzog wrote:
(for a few weeks) to request late migration of lists, though.
Dominic.
Carsten Schoenert
Apr 23, 2018, 1:20:02 AM4/23/18
to
Hello Dominic,
Am 20.04.2018 um 12:21 schrieb Dominic Hargreaves:
...
this.
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
mai...@alioth-lists.debian.net.
We have two old mailing list from the pkg-giraffe-group that aren't
migrated (and we have no migration related questing found in the inbox)
so I've wrote a email some days ago about this and also a wishlist's
question if the lists could still be migrated targeted to this address.
But I haven't a feedback yet. So, need I to be more patient or tried I
the wrong contact for such late migrations?
The wiki page [2] nor the information on alioth-lists.d.n [3] hold some
information about how the possibilities are for such possible migrations
after the main change. What need people to do with a similar situation?
[1] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo
[2] https://wiki.debian.org/Alioth/MailingListContinuation
[3] https://alioth-lists.debian.net/
--
Regards
Carsten Schoenert
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
>> something like this, it would require local delivery to something like
>> procmail.
>>
>> Still I'm ccing them to get their feedback on this.
>
> That is not an option on alioth-lists.debian.net. It's not too late
> (for a few weeks) to request late migration of lists, though.
maybe i missed something, but I need to ask some further questions about
>> 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
>> something like this, it would require local delivery to something like
>> procmail.
>>
>> Still I'm ccing them to get their feedback on this.
>
> That is not an option on alioth-lists.debian.net. It's not too late
> (for a few weeks) to request late migration of lists, though.
this.
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
mai...@alioth-lists.debian.net.
We have two old mailing list from the pkg-giraffe-group that aren't
migrated (and we have no migration related questing found in the inbox)
so I've wrote a email some days ago about this and also a wishlist's
question if the lists could still be migrated targeted to this address.
But I haven't a feedback yet. So, need I to be more patient or tried I
the wrong contact for such late migrations?
The wiki page [2] nor the information on alioth-lists.d.n [3] hold some
information about how the possibilities are for such possible migrations
after the main change. What need people to do with a similar situation?
[1] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo
[2] https://wiki.debian.org/Alioth/MailingListContinuation
[3] https://alioth-lists.debian.net/
--
Regards
Carsten Schoenert
Alex Muntada
Apr 25, 2018, 4:10:03 AM4/25/18
to
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
> mai...@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?
Maybe you missed the last announcement on d-d-annouce on this
topic:
https://lists.debian.org/debian-devel-announce/2018/04/msg00004.html
> We have two old mailing list from the pkg-giraffe-group that aren't
> migrated (and we have no migration related questing found in the inbox)
> so I've wrote a email some days ago about this and also a wishlist's
> question if the lists could still be migrated targeted to this address.
Sorry, probably the mailman address is not being attended.
> But I haven't a feedback yet. So, need I to be more patient or tried I
> the wrong contact for such late migrations?
> The wiki page [2] nor the information on alioth-lists.d.n [3] hold some
> information about how the possibilities are for such possible migrations
> after the main change. What need people to do with a similar situation?
>
> [1] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo
> [2] https://wiki.debian.org/Alioth/MailingListContinuation
> [3] https://alioth-lists.debian.net/
The https://alioth-lists.debian.net/ lists several means of
contact with the team (salsa issues, email and irc). I'd suggest
salsa issues to better keep track of such requests.
There's no explicit information about requesting late migrations
but people can request them as long as alioth is alive, which
won't be for much longer.
Cheers,
Alex
> 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
> mai...@alioth-lists.debian.net.
mention of mailman@. Where did you find that mailman address?
Maybe you missed the last announcement on d-d-annouce on this
topic:
https://lists.debian.org/debian-devel-announce/2018/04/msg00004.html
> We have two old mailing list from the pkg-giraffe-group that aren't
> migrated (and we have no migration related questing found in the inbox)
> so I've wrote a email some days ago about this and also a wishlist's
> question if the lists could still be migrated targeted to this address.
> But I haven't a feedback yet. So, need I to be more patient or tried I
> the wrong contact for such late migrations?
> The wiki page [2] nor the information on alioth-lists.d.n [3] hold some
> information about how the possibilities are for such possible migrations
> after the main change. What need people to do with a similar situation?
>
> [1] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo
> [2] https://wiki.debian.org/Alioth/MailingListContinuation
> [3] https://alioth-lists.debian.net/
contact with the team (salsa issues, email and irc). I'd suggest
salsa issues to better keep track of such requests.
There's no explicit information about requesting late migrations
but people can request them as long as alioth is alive, which
won't be for much longer.
Cheers,
Alex
Carsten Schoenert
Apr 25, 2018, 5:20:02 AM4/25/18
to
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
>> mai...@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?
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.
> Maybe you missed the last announcement on d-d-annouce on this
> topic:
>
> https://lists.debian.org/debian-devel-announce/2018/04/msg00004.html
I've seen and read this announcement, due some other stuff I probably
don't have understand it the way it was intended.
...
Debian BTS. But o.k., I'll open a new issue for the migration of our
lists. Thanks for answering.
--
Regards
Carsten Schoenert
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
>> mai...@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?
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo
I suggest to change the text passage in the site then.
> Maybe you missed the last announcement on d-d-annouce on this
> topic:
>
> https://lists.debian.org/debian-devel-announce/2018/04/msg00004.html
don't have understand it the way it was intended.
...
> The https://alioth-lists.debian.net/ lists several means of
> contact with the team (salsa issues, email and irc). I'd suggest
> salsa issues to better keep track of such requests.
Hmm, then this is mostly different from the typical workflow by the
> contact with the team (salsa issues, email and irc). I'd suggest
> salsa issues to better keep track of such requests.
Debian BTS. But o.k., I'll open a new issue for the migration of our
lists. Thanks for answering.
--
Regards
Carsten Schoenert
Jonas Smedegaard
Apr 25, 2018, 5:40:03 AM4/25/18
to
Excerpts from Carsten Schoenert's message of april 25, 2018 11:12 am:
One detail that (does not reduce confusion, but at least) may help
understand one of the reason _why_ it is confusing is this:
alioth-lists.debian.net is a debian.net service (not debian.org), and as
such only loosely related to Debian.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
> 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
>>> mai...@alioth-lists.debian.net.
[...]
>>> 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
>>> mai...@alioth-lists.debian.net.
>> The https://alioth-lists.debian.net/ lists several means of contact
>> with the team (salsa issues, email and irc). I'd suggest salsa issues
>> to better keep track of such requests.
>
> Hmm, then this is mostly different from the typical workflow by the
> Debian BTS. But o.k., I'll open a new issue for the migration of our
> lists. Thanks for answering.
I find it confusing as well.
>> with the team (salsa issues, email and irc). I'd suggest salsa issues
>> to better keep track of such requests.
>
> Hmm, then this is mostly different from the typical workflow by the
> Debian BTS. But o.k., I'll open a new issue for the migration of our
> lists. Thanks for answering.
One detail that (does not reduce confusion, but at least) may help
understand one of the reason _why_ it is confusing is this:
alioth-lists.debian.net is a debian.net service (not debian.org), and as
such only loosely related to Debian.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
Alex Muntada
Apr 25, 2018, 6:20:02 AM4/25/18
to
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 mailman
address and that we missed too.
Thanks a lot for bringing this up!
> Hmm, then this is mostly different from the typical workflow by the
> Debian BTS. But o.k., I'll open a new issue for the migration of our
> lists. Thanks for answering.
Thank you for opening an issue, but feel free to send your
requests to admin@ if you feel more comfortable. We're using
salsa issues for now because it was very easy to set up. We may
consider other options in the future.
Cheers!
Alex
> 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.
I've found several other requests that were made through mailman
address and that we missed too.
Thanks a lot for bringing this up!
> Hmm, then this is mostly different from the typical workflow by the
> Debian BTS. But o.k., I'll open a new issue for the migration of our
> lists. Thanks for answering.
requests to admin@ if you feel more comfortable. We're using
salsa issues for now because it was very easy to set up. We may
consider other options in the future.
Cheers!
Alex
0 new messages