Bug#926469: marked as done (lintian: Postfix results missing from lintian.d.o)
Your message dated Sun, 07 Apr 2019 06:22:00 +0000
with message-id <17b4d3d4-ea7f-56e8-db39-5c2834b43848@thykier.net>
and subject line Re: Bug#926469: lintian: Postfix results missing from lintian.d.o
has caused the Debian Bug report #926469,
regarding lintian: Postfix results missing from lintian.d.o
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.)
--
926469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926469
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.12.0
Severity: normal
Reporting this as a bug against the package because the web site says:
"Comments about these web pages? Please use reportbug to report a bug against
the lintian package."
I am 100% certain that postfix is not lintian clean, yet it isn't on
lintian.d.o as far as I can find. It's neither linked from tracker.d.o nor
listed on:
https://lintian.debian.org/packages_3.html
This can't be right?
Scott K
--- End Message ---
--- Begin Message ---
Scott Kitterman:
> Package: lintian
> Version: 2.12.0
> Severity: normal
>
> Reporting this as a bug against the package because the web site says:
>
> "Comments about these web pages? Please use reportbug to report a bug against
> the lintian package."
>
> I am 100% certain that postfix is not lintian clean, yet it isn't on
> lintian.d.o as far as I can find. It's neither linked from tracker.d.o nor
> listed on:
>
> https://lintian.debian.org/packages_3.html
>
> This can't be right?
>
> Scott K
>
Hi,
It is there now:
https://lintian.debian.org/full/lamont@debian.org.html#postfix_3.4.5-1
I believe the underlying issue is #926543 and the issue may therefore
reappear. Though in that case, please follow up on #926543.
Thanks,
~Niels
--- End Message ---
Reply to: