Your message dated Mon, 20 Jun 2022 14:34:13 +
with message-id
and subject line Bug#941656: fixed in lintian 2.115.0
has caused the Debian Bug report #941656,
regarding lintian: changelog-file-missing-explicit-entry: false positives with
successive stable uploads
to be marked as done
651 [lintian] lintian: changelog-file-missing-explicit-entry: false
positives with successive stable uploads
Severity set to 'normal' from 'important'
Marked as found in versions lintian/2.24.0.
Merged 941656 1001651
> severity 941656 important
Bug #941656 [lintian] lintian: changelog-file-missing-ex
Control: forcemerge 941656 -1
Control: severity 941656 important
Hi,
On Mon, Dec 13, 2021 at 11:00 AM Cyril Brulebois wrote:
>
> W: debian-installer source: changelog-file-missing-explicit-entry
> 20210731+deb11u1 -> 20210731 (missing) -> 20210731+deb11u2
Your case from stable was already
Package: lintian
Version: 2.104.0
Severity: important
Hi,
This is similar to #941656, but I wanted to have it tracked separately,
with a slightly higher priority, as that's affecting people performing
regular uploads to stable.
I would expect this to apply to backports and security as well
Package: lintian
Severity: wishlist
Hi,
Depending on the skeleton selected, the test suite generates full
uploads even in situations when the tag being tested arises solely
from a source package. Please build full uploads, which include
installation packages, only when source-only uploads
Your message dated Wed, 21 Aug 2019 17:25:13 +
with message-id
and subject line Bug#934982: fixed in lintian 2.19.0
has caused the Debian Bug report #934982,
regarding latest-debian-changelog-entry-without-new-version triggered for
buster/stable uploads
to be marked as done.
This means
Package: lintian
Version: 2.18.0
Severity: normal
Hi,
I have a package where I want to prepare a stable/buster upload. In
this case it is systemd, where the current version in buster is 241-5.
I want to upload 241-7 from unstable/testing as-is to buster.
For that I added a changelog entry like
Your message dated Tue, 07 Aug 2018 13:50:29 +
with message-id
and subject line Bug#905467: fixed in lintian 2.5.95
has caused the Debian Bug report #905467,
regarding lintian: Please detect source-only non-free uploads w/o opt-in
autobuild
to be marked as done.
This means that you claim
Chris Lamb wrote:
> Updated in:
>
> […]
That should have been:
https://salsa.debian.org/lintian/lintian/commit/adf09be624fc450738f40613bd5098d056a678e2
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Hi Guillem & Niels,
> > I seem to recall that "XS-Autobuild: Yes" requires being added to a
> > whitelist as well
[…]
> Yes, this is item 3 from the dev-ref link I provided. And I agree it's
> probably worth mentioning, or just pointing people to read the dev-ref
> for the most up-to-date
On Sun, 2018-08-05 at 08:06:00 +, Niels Thykier wrote:
> Chris Lamb:
> > tags 905467 + pending
> > thanks
> >
> > Implemented in Git, pending upload:
> >
> >
> > https://salsa.debian.org/lintian/lintian/commit/514313860d51930c986bbcb3eca6ec4ac7905852
> I seem to recall that
Chris Lamb:
> tags 905467 + pending
> thanks
>
> Implemented in Git, pending upload:
>
>
> https://salsa.debian.org/lintian/lintian/commit/514313860d51930c986bbcb3eca6ec4ac7905852
>
> checks/changes-file.desc | 12
> checks/changes-file.pm
Processing commands for cont...@bugs.debian.org:
> tags 905467 + pending
Bug #905467 [lintian] lintian: Please detect source-only non-free uploads w/o
opt-in autobuild
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
905467:
tags 905467 + pending
thanks
Implemented in Git, pending upload:
https://salsa.debian.org/lintian/lintian/commit/514313860d51930c986bbcb3eca6ec4ac7905852
checks/changes-file.desc | 12
checks/changes-file.pm | 8
into the non-free autobuild network.
[M] <https://tracker.debian.org/pkg/snmp-mibs-downloader>
I think lintian should at least warn (or perhaps even error) on
source-only non-free uploads that do not declare the Autobuild:yes
field. [A]
[A]
<https://www.debian.org/doc/manuals/developers-
uot;~bpo7+N" as the suffix for wheezy-backports-sloppy
uploads
---
checks/changes-file.pm | 7 +--
debian/changelog | 4
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/checks/changes-file.pm b/checks/changes-file.pm
index 4761d09..a9b8c46 100644
--- a/checks/changes-file
Your message dated Mon, 28 Jun 2010 05:32:10 +
with message-id e1ot6x0-00033h...@ries.debian.org
and subject line Bug#582741: fixed in lintian 2.4.2
has caused the Debian Bug report #582741,
regarding lintian: [checks/nmu] Team uploads.
to be marked as done.
This means that you claim
Package: lintian
Version: 2.4.1
Severity: wishlist
Tags: patch
Dear Lintian maintainers,
the concept of team uploads has been discussed a couple of times on
debian-devel, and is finally making its way in the Developers Reference. You
can find more informations in the following wiki page:
http
Package: lintian
Severity: wishlist
Some of us are not so good at remembering to set the upload target
(unstable/experimental/stable/whatever) correctly. It would be handy if
lintian could warn about this. For example (names changed):
foo liw: we have bar 3.0.x series in unstable and 3.2.x in
something here, but wouldn't this essentially always be
wrong when looking at the whole archive? Almost no one uploads new
upstream versions to experimental first.
liw although I guess that would be best done by a lintian check
liw possibly even enabled only if there is a debian/lintian-me-harder
la, 2008-05-31 kello 11:08 -0700, Russ Allbery kirjoitti:
You'd need some way to request only that specific check, I think, since
even people who normally want lintian to be as verbose as possible aren't
going to want that.
Yeah, thus the debian/lintian-me-harder suggestion: only do the check
Wouldn't this be more suitable in dput/dupload?
Those already have similar options, some of which are disabled by default,
but available anyway.
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See
that it's the kind of static checking that belongs to
lintian, so I'd like to see it in lintian, rather than every upload tool
separately. If nothing else, it would help find problems even when
things are not uploaded, just (re)built.
The thing is that just like Russ said, almost no one uploads new
On Fri, Jun 23, 2006 at 01:28:45PM -0700, Russ Allbery wrote:
Raphael Hertzog [EMAIL PROTECTED] writes:
(moving to lintian-maint)
On Fri, 23 Jun 2006, Russ Allbery wrote:
Raphael Hertzog [EMAIL PROTECTED] writes:
I tend to think that you're doing too much checks here. Having too
(moving to lintian-maint)
On Fri, 23 Jun 2006, Russ Allbery wrote:
Raphael Hertzog [EMAIL PROTECTED] writes:
FWIW, packages using CDBS and the python-distutils class and
Build-Depending on python-dev have a similar warning... and yet they
need python-dev for the clean target.
Yeah,
Raphael Hertzog [EMAIL PROTECTED] writes:
(moving to lintian-maint)
On Fri, 23 Jun 2006, Russ Allbery wrote:
Raphael Hertzog [EMAIL PROTECTED] writes:
I tend to think that you're doing too much checks here. Having too
much in Build-Depends is not *that* bad. You'd better check only for
| --=-=-=
| Content-Transfer-Encoding: quoted-printable
|
| On 10403 March 1977, Jari Aalto wrote:
|
| | While they are listed in there at the page, they seem to be
| | rejection criterias. At least my package jwm submittal was
| | refused for upload until extra # dh_* lines were removed.
Package: lintian
Version: 1.23.12
Severity: wishlist
There is now rejection criterias outlined in:
http://ftp-master.debian.org/REJECT-FAQ.html
One of the criterias are extra # dh_* templates which now seem to
have to be removed. Currently this is W: in lintian, it should
probably be raised
On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote:
There is now rejection criterias outlined in:
http://ftp-master.debian.org/REJECT-FAQ.html
One of the criterias are extra # dh_* templates which now seem to
have to be removed. Currently this is W: in lintian, it should
On Mon, Sep 05, 2005 at 04:07:48PM +0300, Jari Aalto wrote:
| On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote:
| There is now rejection criterias outlined in:
|
| http://ftp-master.debian.org/REJECT-FAQ.html
|
| One of the criterias are extra # dh_* templates which now
| On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote:
| There is now rejection criterias outlined in:
|
| http://ftp-master.debian.org/REJECT-FAQ.html
|
| One of the criterias are extra # dh_* templates which now seem to
| have to be removed. Currently this is W: in lintian, it
Your message dated Mon, 5 Sep 2005 15:00:31 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#326732: lintian: Added checks that prevent ftp-master
uploads
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
| On Mon, Sep 05, 2005 at 04:07:48PM +0300, Jari Aalto wrote:
| | On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote:
| | There is now rejection criterias outlined in:
| |
| | http://ftp-master.debian.org/REJECT-FAQ.html
| |
| | One of the criterias are extra # dh_*
33 matches
Mail list logo
