Processed: Bug#999768 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #999768 [lintian] lintian: false report: adopted-extended-field XS-Autobuild Added tag(s) pending. -- 999768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#995492: lintian: Broken --fails-on=none as default never got reverted
Processing control commands: > tag -1 + moreinfo Bug #995492 [lintian] lintian: Broken --fails-on=none as default never got reverted Added tag(s) moreinfo. > severity -1 important Bug #995492 [lintian] lintian: Broken --fails-on=none as default never got reverted Severity set to 'important' from 'serious' -- 995492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995492: lintian: Broken --fails-on=none as default never got reverted
Control: tag -1 + moreinfo Control: severity -1 important Hi Guillem, I'm trying to catch up with that chaos which is in lintian's current state. Guillem Jover wrote: > So the problematic --fail-on default change never got actually reverted > as the patch applied in commit 3758bfafd5dd742c327f2312dac8e3a71b1f036e > omitted the relevant part that would make it work. :( Can you please elaborate what exactly is the bug? You refer to something being problematic without explaining what actually is problematic. You refer to 3758bfafd5dd742c327f2312dac8e3a71b1f036e and https://bugs.debian.org/962158 which has been closed about 2 years and ca. 35 Lintian releases ago. That thread in #962158 is quite long and difficult to grasp. > None of the previous arguments against the default change brought up > in #962158 have stopped being relevant (also contrary to the commit > message…). Worse, this sneaked in what has shipped now in a stable > Debian release. :( So any errors found in CI systems and through other > tooling has been silently ignored since then. :/ This doesn't really makes the issue easier to understand. I don't ask for a patch, but at least for a list of defects what is wrong where and probably why. So far I got that there is an issue with the exit codes having changed to be somewhat less helpful for automatic usage. (When did it change and how? Do you happen to know a commit id? What condition should in your opinion cause which exit code?) > Only noticed now due to #994414, a great excuse to now keep the broken > behavior I guess. So this bug report actually should no more be fixed?!? > (Where the --help output still does not match…) So --help seems outdated. At which line or option exactly and what should it say instead? Downgrading to import for now as I can't really fix something which is totally unclear, both, the how and the why. P.S.: Sorry if you explained that in the past, but the whole situation in general and with this issue in specific is quite tangled, so that I'd really appreciate a summary to get an idea what this bug report exactly is about. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
[Git][lintian/lintian][master] 2 commits: Update data for Debian policy releases (4.6.1 added)
Axel Beckert pushed to branch master at lintian / lintian
Commits:
f274aa0e by Damyan Ivanov at 2022-06-13T22:17:00+00:00
Update data for Debian policy releases (4.6.1 added)
- - - - -
3ad582e2 by Damyan Ivanov at 2022-06-13T22:17:00+00:00
update releases.json via lintian itself
magic incantation:
perl -Ilib -wEuse Lintian::Deb822; use Lintian::Data::Policy::Releases;
my $r = Lintian::Data::Policy::Releases-new; $r-refresh(0,
data);
Downloads the debian-policy changelog from salsa
- - - - -
1 changed file:
- data/debian-policy/releases.json
Changes:
=
data/debian-policy/releases.json
=
@@ -8,18 +8,42 @@
"author" : "Sean Whitton ",
"changes" : [
"",
-"debian-policy (4.6.0.2) UNRELEASED; urgency=medium",
+"debian-policy (4.6.1.0) unstable; urgency=medium",
+"",
+" * Policy: Allow non-64-bit packages to install to /usr/lib64",
+"Wording: Sean Whitton ",
+"Seconded: Simon McVittie ",
+"Seconded: Russ Allbery ",
+"Closes: #992601",
+" * Policy: Define 'upstream' & document several version
conventions",
+"Wording: Russ Allbery ",
+"Seconded: Sam Hartman ",
+"Seconded: Sean Whitton ",
+"Closes: #542288, #850729",
+" * virtual-package-names-list: Add {default,}dbus-system-bus
(Closes: #998063).",
+"Thanks to Simon McVittie for the patch.",
+" * Update 9.7.2 and 9.7.3 for package split of bin:mime-support
into",
+"bin:media-types and bin:mailcap (Closes: #1008480).",
+"Thanks to Charles Plessy for the patch.",
"",
" * Fix several problems with footnote regarding the autobuilders
and",
"build dependency alternatives (Closes: #999826).",
-"Thanks to Johannes Schauer Marin Rodrigues for the report and
patch."
+"Thanks to Johannes Schauer Marin Rodrigues for the report and
patch.",
+" * Use syntax highlighting for some source code blocks (Closes:
#999566).",
+"Thanks to Stéphane Blondon for the patch."
],
"closes" : [
-999826.0
- ],
- "epoch" : 1640320759,
- "timestamp" : "2021-12-24T04:39:19Z",
- "version" : "4.6.0.2"
+542288,
+850729,
+992601,
+998063,
+999566,
+999826,
+1008480
+ ],
+ "epoch" : 1652292179,
+ "timestamp" : "2022-05-11T18:02:59Z",
+ "version" : "4.6.1.0"
},
{
"author" : "Sean Whitton ",
View it on GitLab:
https://salsa.debian.org/lintian/lintian/-/compare/ccd30b72f3ad9b9d7621a0058f07aee52ae49a73...3ad582e27b1fc690dbbc81623173c7513a9124bc
--
View it on GitLab:
https://salsa.debian.org/lintian/lintian/-/compare/ccd30b72f3ad9b9d7621a0058f07aee52ae49a73...3ad582e27b1fc690dbbc81623173c7513a9124bc
You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#1012090 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #1012090 [lintian] riscv support in lintian tag binary-from-other-architecture Added tag(s) pending. -- 1012090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1000977 marked as pending in lintian
Processing control commands: > tag -1 pending Bug #1000977 [lintian] lintian: bogus elf-error in debug symbols Added tag(s) pending. -- 1000977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unblock 1006348 with 1003272 1007002 1003353
Processing commands for cont...@bugs.debian.org: > # Totally unrelated *shrug* > unblock 1006348 with 1003272 1007002 1003353 Bug #1006348 [lintian] lintian: Tag improbable-bug-number-in-closes condition considers 7-digit bug numbers improbable 1006348 was blocked by: 1003272 1003353 1006348 was not blocking any bugs. Removed blocking bug(s) of 1006348: 1007002, 1003353, and 1003272 > thanks Stopping processing here. Please contact me if you need assistance. -- 1006348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1003272 to lintian: chokes on overrides with "(" but no ")"
Processing commands for cont...@bugs.debian.org:
> # Back to the original titles for these unmerged bug reports
> retitle 1003272 lintian: chokes on overrides with "(" but no ")"
Bug #1003272 [lintian] lintian: Override processing defective for square
brackets, parentheses and curly brackets
Changed Bug title to 'lintian: chokes on overrides with "(" but no ")"' from
'lintian: Override processing defective for square brackets, parentheses and
curly brackets'.
> retitle 1003353 lintian: Cannot use brackets in suppression rules?
Bug #1003353 [lintian] lintian: Override processing defective for square
brackets and curly brackets
Changed Bug title to 'lintian: Cannot use brackets in suppression rules?' from
'lintian: Override processing defective for square brackets and curly brackets'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1003272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003272
1003353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1007002: lintian: transition to "pointed hints" has invalidated many overrides
Hi Simon, Simon McVittie wrote: > Control: unblock 1006348 by -1 Thanks! > #1007002 was marked as blocking #1006348 "lintian: Tag > improbable-bug-number-in-closes condition considers 7-digit bug numbers > improbable", but I think that was a side-effect of the merge Definitely. All three unmerged bug reports had that block. > and I don't consider #1007002 to be RC or a blocker for #1006348, so > I'm removing that metadata. Actually it was still on my TODO list to find out which of the bug reports was related to #1006348 and why. You reduced that part of my TODO list to 2/3 by no more having to check this bug report. Thanks! :-) > > Since at least I will not revert such huge changes, I'll tag #1007002 > > as "wontfix" for now and downgrade it to its original severity. > > > > We can continue working on that bug report if we find someone who > > either will work on reverting all the related work (although I think, > > it's both, too late and also probably way too much work given all the > > other recent changes) or, probably much better, provide either a > > migration script or some code which also accepts the old override > > formats. In that case, I'd remove the "wontfix" again. (Sorry, Simon, > > I generally agree with #1007002, but we currently have way more severe > > issues with Lintian than #1007002. Hence I also didn't remove the > > confirmed tag.) Oh, JFTR: This refers to Lintian as it was in Git when I took over. There are parts of that tag format transition already committed in Git which aren't yet in Debian Unstable. :-/ There were nearly 200 commits in git since 2.114.0 before I started working again on Lintian. I won't triage and revert them either unless they are outright buggy in a technical sense. Sorry. As mentioned it would need much more man power to "fix" this issue, even with what is so far only in git. And with Felix and Chris left the Lintian development, there's much less man power so far. At least so far I'm the only one who did commits since then, but there were at least three DDs asking for group membership on Salsa (Thanks!), so I hope they will start working on Lintian as well. I'm also updating the development how-tos where I notice that they're outdated. > That makes sense to me. I should have reported #1007002 earlier No offence meant. > (or, ideally, a Lintian co-maintainer should have pointed out the > problems with a major tag format transition before it got that far), That's more a thing. Actually I already thought if we should setup a similar rule for Lintian tag syntaxes as we did for using epoch in package versions, maybe just not as stringent. I'm though not sure where such a rule should be placed. The Debian Policy seems the wrong place. So that rule should be probably documented inside Lintian itself or so. > which would have made pausing or reverting the transition > lower-cost. Ack. > Thank you for picking up this package! It's an important QA tool and > I'm glad someone is looking after it again. Should have noticed the resignation of Felix and Chris (or looked for such a thing after noticing that there were no lintian uploads for a while) earlier, too. Probably would have been less (or at least more distributed) work to get it back in shape as the remainder of Debian Unstable didn't stand still while Lintian did. Especially I found one case where the amount of lines replacing the #DEBHELPER# token caused test suite failures after a debhelper update seem to have added some lines. Took a few hours to understand what went wrong and why. (Granted, because many things I knew about Lintian's test suite had changed since I last used it, I first had to relearn how to use the current setup and this took probably some of that time as well.) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Re: [Git][lintian/lintian][master] 9 commits: Update copyright years in debian/copyright
Hi,
Axel Beckert (@abe) wrote:
> Axel Beckert pushed to branch master at lintian / lintian
>
> Commits:
> 1b26acec by Axel Beckert at 2022-06-11T17:00:27+02:00
> Update copyright years in debian/copyright
>
> … before lintian starts complaining about it. ;-)
>
> - - - - -
> 648144e9 by Axel Beckert at 2022-06-11T18:59:43+02:00
> Run perltidy over bin/lintian and private/{runtests,refresh-perl-provides}
Axel Beckert (@abe) wrote:
> Axel Beckert pushed to branch master at lintian / lintian
>
> Commits:
> d53aff54 by Axel Beckert at 2022-06-11T16:49:27+02:00
> Replace all occurrences of Copyright © with Copyright
> (C) again until https://github.com/Perl-Critic/Perl-Critic/issues/925
> is fixed
I got these two mails for pushes of mine to the Lintian git repo, but
only these. I though pushed more often than that. (I also checked that
none of them got caught by my local spam filter.)
Anyone knows why only some of my pushes trigger these mails and others
do not? According to
https://salsa.debian.org/lintian/lintian/-/integrations/emails_on_push/edit
it should be on every push.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: Bug#1007002: lintian: transition to "pointed hints" has invalidated many overrides
Processing control commands: > unblock 1006348 by -1 Bug #1006348 [lintian] lintian: Tag improbable-bug-number-in-closes condition considers 7-digit bug numbers improbable 1006348 was blocked by: 1003272 1007002 1003353 1006348 was not blocking any bugs. Removed blocking bug(s) of 1006348: 1007002 -- 1006348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006348 1007002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007002: lintian: transition to "pointed hints" has invalidated many overrides
Control: unblock 1006348 by -1 On Mon, 13 Jun 2022 at 05:15:19 +0200, Axel Beckert wrote: > And #1007002 is only (!) about design decision to change nearly all > tag formats involving file paths and line numbers. It has nothing to > do with the other two real bugs and I have no idea why they have been > merged. I agree with your reasoning for unmerging, and I don't understand why they were merged either. #1007002 was marked as blocking #1006348 "lintian: Tag improbable-bug-number-in-closes condition considers 7-digit bug numbers improbable", but I think that was a side-effect of the merge and I don't consider #1007002 to be RC or a blocker for #1006348, so I'm removing that metadata. > Since at least I will not revert such huge changes, I'll tag #1007002 > as "wontfix" for now and downgrade it to its original severity. > > We can continue working on that bug report if we find someone who > either will work on reverting all the related work (although I think, > it's both, too late and also probably way too much work given all the > other recent changes) or, probably much better, provide either a > migration script or some code which also accepts the old override > formats. In that case, I'd remove the "wontfix" again. (Sorry, Simon, > I generally agree with #1007002, but we currently have way more severe > issues with Lintian than #1007002. Hence I also didn't remove the > confirmed tag.) That makes sense to me. I should have reported #1007002 earlier (or, ideally, a Lintian co-maintainer should have pointed out the problems with a major tag format transition before it got that far), which would have made pausing or reverting the transition lower-cost. Getting a new Lintian release into testing and backports would at least mitigate #1007002 by making sure that maintainers can write one tag format that is equally valid for stable-backports Lintian, testing Lintian, unstable Lintian and lintian.debian.org. Thank you for picking up this package! It's an important QA tool and I'm glad someone is looking after it again. smcv
Processed: tagging 1012326, tagging 1012690, tagging 1012464, tagging 1001317, tagging 1012221, tagging 1011807 ...
Processing commands for cont...@bugs.debian.org:
> tags 1012326 + sid bookworm
Bug #1012326 [src:python-jenkinsapi] python-jenkinsapi: build-depends on pylint3
Added tag(s) sid and bookworm.
> tags 1012690 + sid bookworm
Bug #1012690 [src:pagetools] pagetools: FTBFS with netpbm11
Added tag(s) bookworm and sid.
> tags 1012464 + sid bookworm
Bug #1012464 [libvtk6.3] libvtk6.3: not installable in sid
Added tag(s) bookworm and sid.
> tags 1001317 - sid bookworm
Bug #1001317 [src:pocl] Please upgrade to llvm-toolchain-13 or 14
Removed tag(s) sid and bookworm.
> tags 1012221 + sid bookworm
Bug #1012221 [rust-stdweb-internal-macros] rust-stdweb-internal-macros
(build-)depends on old version of rust-sha1.
Added tag(s) sid and bookworm.
> tags 1011807 - sid bookworm
Bug #1011807 {Done: Yadd } [src:twitter-bootstrap4]
twitter-bootstrap4: FTBFS: make[1]: *** [debian/rules:13:
override_dh_auto_build] Error 1
Removed tag(s) bookworm and sid.
> tags 1012277 + sid bookworm
Bug #1012277 [src:hipspy] hipspy fails with astropy 5.1
Added tag(s) sid and bookworm.
> notfound 1012255 2.3.1+dfsg
Bug #1012255 [hatari] hatari: FTBFS for RISC-V due to RISC-V system header
There is no source info for the package 'hatari' at version '2.3.1+dfsg' with
architecture ''
Unable to make a source version for version '2.3.1+dfsg'
No longer marked as found in versions 2.3.1+dfsg.
> found 1012255 2.3.1+dfsg-1
Bug #1012255 [hatari] hatari: FTBFS for RISC-V due to RISC-V system header
Marked as found in versions hatari/2.3.1+dfsg-1.
> tags 1012255 + sid bookworm
Bug #1012255 [hatari] hatari: FTBFS for RISC-V due to RISC-V system header
Added tag(s) bookworm and sid.
> tags 1011989 + experimental
Bug #1011989 [src:haskell-tasty-lua] FTBFS: : commitBuffer: invalid
argument (invalid character)
Added tag(s) experimental.
> tags 1011992 + experimental
Bug #1011992 [src:haskell-hslua-module-text] ftbfs: : commitBuffer:
invalid argument (invalid character)
Added tag(s) experimental.
> tags 1011783 - sid bookworm
Bug #1011783 [src:pandoc] pandoc: FTBFS: make: ***
[/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Removed tag(s) bookworm and sid.
> found 1003353 2.114.0
Bug #1003353 [lintian] lintian: Override processing defective for square
brackets and curly brackets
Marked as found in versions lintian/2.114.0.
> found 1000929 8.8.4-3
Bug #1000929 {Done: Gianfranco Costamagna } [src:ghc]
Please upgrade to llvm-toolchain-13 or 14
Marked as found in versions ghc/8.8.4-3.
> found 1000922 0.38.0-1
Bug #1000922 [src:llvmlite] Please upgrade to llvm-toolchain-13 or 14
Marked as found in versions llvmlite/0.38.0-1.
> tags 1000927 + sid bookworm
Bug #1000927 [src:creduce] Please upgrade to llvm-toolchain-13 or 14
Added tag(s) bookworm and sid.
> found 1000927 2.10.0+20201029-3
Bug #1000927 [src:creduce] Please upgrade to llvm-toolchain-13 or 14
Marked as found in versions creduce/2.10.0+20201029-3.
> tags 1012338 + sid bookworm
Bug #1012338 {Done: Peter Michael Green }
[librust-rusty-fork-dev] librust-rusty-fork-dev: depends on missing package
Added tag(s) bookworm and sid.
> tags 1012538 + sid bookworm
Bug #1012538 [chirp] knocked out usability - module 'collections' has no
attribute 'Callable'
Added tag(s) bookworm and sid.
> notfixed 986083 2.1.0-1
Bug #986083 {Done: "Kevin J. McCarthy" } [mutt] mutt: when mutt
is run with the standard input not attached to a terminal and without an e-mail
address as an argument, it sends a mail
There is no source info for the package 'mutt' at version '2.1.0-1' with
architecture ''
Unable to make a source version for version '2.1.0-1'
No longer marked as fixed in versions mutt/2.1.0-1.
> fixed 986083 2.1.3-1
Bug #986083 {Done: "Kevin J. McCarthy" } [mutt] mutt: when mutt
is run with the standard input not attached to a terminal and without an e-mail
address as an argument, it sends a mail
Marked as fixed in versions mutt/2.1.3-1.
> notfixed 837045 1.9.0-1
Bug #837045 {Done: "Kevin J. McCarthy" } [mutt] mutt: wrong
handling of symbol '>' in conditional expression
There is no source info for the package 'mutt' at version '1.9.0-1' with
architecture ''
Unable to make a source version for version '1.9.0-1'
No longer marked as fixed in versions mutt/1.9.0-1.
> fixed 837045 1.9.1-1
Bug #837045 {Done: "Kevin J. McCarthy" } [mutt] mutt: wrong
handling of symbol '>' in conditional expression
Marked as fixed in versions mutt/1.9.1-1.
> notfixed 838992 1.9.0-1
Bug #838992 {Done: "Kevin J. McCarthy" } [mutt] mutt: using mutt,
will not default to home mail directory: "c", "?" with "set folder" remains in
/var/mail
There is no source info for the package 'mutt' at version '1.9.0-1' with
architecture ''
Unable to make a source version for version '1.9.0-1'
No longer marked as fixed in versions mutt/1.9.0-1.
> fixed 838992 1.9.1-1
Bug #838992 {Done: "Kevin J. McCarthy" } [mutt] mutt: using mutt,
will not default to home mail directory: "c", "?" with "set folder" remains in
/var/mail
Marked as
