[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#958666: marked as done (lintian: please downgrade mailing-list-obsolete-in-debian-infrastructure warning)

Your message dated Sat, 25 Apr 2020 09:34:08 +0000
with message-id <E1jSHCK-000Gbh-P8@fasolo.debian.org>
and subject line Bug#958666: fixed in lintian 2.68.0
has caused the Debian Bug report #958666,
regarding lintian: please downgrade mailing-list-obsolete-in-debian-infrastructure warning
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
958666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958666
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
package: lintian
version: 2.67.0
x-debbugs-cc: Debian Med Project List <debian-med@lists.debian.org>, Debian Developers <debian-devel@lists.debian.org>, Debian Lintian Maintainers <lintian-maint@debian.org>, reproducible-builds@lists.alioth.debian.org

On Fri, Apr 24, 2020 at 09:56:24AM +0200, Andreas Tille wrote:
> today I've seen the first time this new lintian warning:
> 
>    mailing-list-obsolete-in-debian-infrastructure Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
> 
> I wonder whether we could this set from severity Warning to Pedandic.

definitly, yes, filing this bug now.

> The point is that this address works not only as maintainer but rather
> as key in several infrastrutural use case like database queries etc.
> The only reason that would convince me that a change is needed would be
> that the redirect to alioth-lists.debian.net would not work any more at
> some foreseable point of time.  So please note:  I would not mind about
> automatically replacing that address with something non-obsolete since
> we try to do some turnover of all (about 1000) Debian Med packages per
> release.  But once we start this change several tools will stop working
> reliably.  This is to much effort for something that looks cosmetical in
> my eyes.  So if you insist that this should be at severity warning I'll
> probably rather add a lintian override automatically for all our
> packages rather than automatically change the maintainer address.

we also still use reproducible-builds@lists.alioth.debian.org as our maintainer
address for Reproducible Builds related packages and it's our advertised point
of contact for Debian related Reproducible Builds stuff and we don't have
any plan to change this any time soon.

It's true that some @lists.alioth.debian.org stopped working but *many* have
been migrated to alioth-lists.debian.net and continue to work as 
@lists.alioth.debian.org so this lintian warning creates tons of non-actionable
and doubtful (not to say false-positive) warnings.

Please change this and thank you for maintaining lintian!


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

Dance like no one's watching. Encrypt like everyone is.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: lintian
Source-Version: 2.68.0
Done: Chris Lamb <lamby@debian.org>

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 958666@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb <lamby@debian.org> (supplier of updated lintian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 25 Apr 2020 08:54:19 +0000
Source: lintian
Architecture: source
Version: 2.68.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Closes: 949844 958666
Changes:
 lintian (2.68.0) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * Mark mailing-list-obsolete-in-debian-infrastructure as being
     experimental, essentially hiding it. (Closes: #958666)
   * Warn about packages --with=systemd with a debhelper compatibility level
     of 10 or higher. (Closes: #949844)
 .
   [ Michael Biebl ]
   * Stop recommending dh-systemd as a Build-Depends alternative in the long
     description of maintainer-script-calls-systemctl.
 .
   [ Simon Quigley ]
   * Add "groovy" as a known Ubuntu distribution.
Checksums-Sha1:
 1ec1c1903656cc3b2ddbd7053bca316916ea274e 4131 lintian_2.68.0.dsc
 7316489c73dbab8adf977bec312d0777e594b443 1884540 lintian_2.68.0.tar.xz
 b17dbf8458da6436c67f04b2731e806f7a67a20f 16543 lintian_2.68.0_amd64.buildinfo
Checksums-Sha256:
 824ca51b5e2f4c57fe4ea4940194feb320af86a6ecc9d7874b4ddd4652acc178 4131 lintian_2.68.0.dsc
 50f8a1b0967591e0cec43ebe6e5521c7c8643fbf668f0b933ede64a528f0edde 1884540 lintian_2.68.0.tar.xz
 2b385fe959ba0abfe2bcb2399427a8ba7576c01f050988f245ae66dce139afce 16543 lintian_2.68.0_amd64.buildinfo
Files:
 4f90dfc190a6e2d2be19f51475d1dc85 4131 devel optional lintian_2.68.0.dsc
 eb0397141ac399749df1262468025c77 1884540 devel optional lintian_2.68.0.tar.xz
 9b887cb0313a2254967eea5ce7fb1fce 16543 devel optional lintian_2.68.0_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl6kAD8ACgkQHpU+J9Qx
HliYzw//SnSk7Wxx7s9oKYU8wwRZv1MiPqWGJW7ghHMm7dT94pVxAVuDUil2Sy/X
wXtBr7f5CzZjOYdMC17DTF6h0nMYpbN/BTP/v/fIV+fedj28rZpZxwpurfGZ0LNw
HAMT2aq2IL/S7Uat++twN+ykvMgEoDmxEIXOuLBgKBR+c1c89zC62EnbsBrtI6af
fj1g6xKPOfFdjXOr1s9TDYQ6w4rLxxq+yFxW6bmec5Wt7wYz9beAEwJzD2rydrOM
UynGFiGNKacoAFwmzNeNKV8s07heV35PTypHq54h8g3voVzBeSogq3+W9bPGn6ba
Xh4jCTZu0Cs9BUwibbN+zzcdNDOmHxDznx4t+5cZKaqr0HzC71eySACuTINESRZj
2Wx3s7J8OJ1c2w+b5Y7kpdaAWZmutit4z6POmewc2W1grX6zYWstaeeWMl2W9DlN
Gl/Yf4r1vjfomSAOx7qVmEXmCAw6vB4Nla/aRC86NOftLd6xr9kDEdDEgxZh1qla
GzTPwOZAc1R4p/np1zsvYaTeTa+0ov+z365nwpH/wt6tsd4ghiNxIW/TmEgkT+52
It4Hae8C6ivtCDVm2QOUgr7jdyUAC+yF5qdWIIcIpVad3lPRtrOZ+Sn+14qiangl
ouvbQaj94Sx8j6fyhVL4hITI/Nuy5G0b6efCohK7mrJzyAwPzdY=
=6Pau
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: