erhaps
d/lintian-overrides.
That being said, I would like to improve the error message.
Unfortunately, the version of your sources in sid does not declare
overrides or a Vcs. Would you please post the sources somewhere? Thank
you!
Kind regards
Felix Lechner
tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t
That test was adjusted for recent versions of Binutils. [2]
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/deba665363a3dd4da8b806df07091c9c482206d7
[2]
https://salsa.d
shing for some kind of improvement.
Lintian already does other things, such as checking that your most
recent timestamp postdates the release date of the policy version with
which the sources declare compliance [1] but that would not have
caught gensio, which I think is the package you uploaded.
Kind
ntire archives that contain no code, i.e. when there is no code in
any of the object files?
Kind regards
Felix Lechner
o issue the warning,
or perhaps even for the archive to reject the upload?
Kind regards
Felix Lechner
ble
however. I would not commit them if only the time stamps have changed.
Eventually, we might like to stop committing data to the Git repo.
Your ideas on how to achieve that in the context of Debian source
packaging from Git are most welcome. Thanks!
Kind regards
Felix Lechner
tclsh to reprocess the entire
> script. When tclsh starts up, it treats all three lines as comments,
> since the backslash at the end of the second line causes the third
> line to be treated as part of the comment on the second line.
Kind regards
Felix Lechner
he way to check for the presence of a
field is with '->declares'. [3] Most significantly, there are no NULL
pointers. [4]
It would be a little bit of a philosophical stretch for Lintian to
alert users to problems with other parsers, rather than the document
itself.
Kind regards
Felix L
Kind regards
Felix Lechner
[1] https://tracker.debian.org/media/packages/u/uglifyjs/copyright-2.8.29-8
[2]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Debian/Copyright/Dep5.pm
ython3-sphinx, but with
> the :native qualifier
That is a separate bug, and actually more interesting. Cloning.
Kind regards
Felix Lechner
e output
will not appear on our website or be shown to any users, but you could
(relatively soon) access archive-wide results via our JSON interface.
[2] We would then try to refine the tag for public consumption
together.
What do you think, please?
Kind regards
Felix Lechner
[1] https://salsa.de
ed after the package name (due to camel case).
Should I allow all subfolders?
Kind regards
Felix Lechner
ould make Lintian's output variable over time. Do
we really need the upper bound (or the whole tag)?
Kind regards
Felix Lechner
Bug Number vs Filing Date.pdf
Description: Adobe PDF document
Filing Date,Bug Number
11/12/99,"50,004"
06/07/01,"100,000"
06/14/02,"150,000"
required to support all so called XSI enhancements
mentioned in the POSIX standard." [3]
What do you think, please? Thanks!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Shell/NonPosix/BashCentric.pm#L128
[2] https://unix.stackex
Hi Julien,
On Sat, Nov 13, 2021 at 1:15 AM Julien Puydt wrote:
>
> I hope this is precise enough to improve the hint.
We would like to test improvements. Would you please point to
installable packages that triggered the false positives? Thanks!
Kind regards
Felix Lechner
;elf->{NEEDED} // [] }
&& $depends->is_empty;
What do you think, please? Thanks!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Index/Elf.pm#L85
[2]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Index/Elf.pm#
g/lintian/lintian/-/commit/7f4621daf12355d271b943cbd1179829f7e12159
Do we need a separate tag for all uses of LTO, as requested here?
Would a classification tag be appropriate? At a minimum, it would
allow further research into the prevalence. Thanks!
Kind regards,
Felix Lechner
Hi Yadd,
On Tue, Nov 9, 2021 at 8:17 AM Yadd wrote:
>
> same author
No sweat! The check merely requires separate wildcards. They can be in
the same Files field. That means they can share the same author.
Kind regards
Felix Lechner
1]
Thank you for all your hard work on node!
Kind regards
Felix Lechner
[1] https://lintian.debian.org/tags/add-component-copyright
ined
with the above, I am not sure the tag is fixable.
As a last step before a possible removal, the tag was marked as
experimental, which tends to hide it from view. [1]
Please submit any additional positions to this bug. Thanks!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintia
ltidy settings in unstable better. A
diff for lintian is attached.
Thank you so much for your help in this matter!
Kind regards
Felix Lechner
diff.xz
Description: application/xz
Control: tags -1 + pending
Hi,
This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html
Control: tags -1 + pending
Hi,
This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html
Control: tags -1 + pending
Hi,
This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html
Control: tags -1 + pending
Hi,
This upload of wolfssl version 5.0.0-1 to the NEW queue [1] will close
your bug in the near future. Thanks!
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/new/wolfssl_5.0.0-1.html
Hi,
> that links returns a 404
Lintian's new website is no longer static but a database-driven web
application. It does many things well, but unfortunately the manual is
not currently available.
We are looking to improve that situation. It is also a problem in the wiki. [1]
Kind regar
- firefox-esr
- linux
- llvm-toolchain-9
- llvm-toolchain-10
- llvm-toolchain-11
- llvm-toolchain-snapshot
- nvidia-cuda-toolkit
- thunderbird
I believe the tag functions properly because there is a unit test for
it. [4] [5]
Kind regards
Felix Lechner
[1]
https://
I added a Lintian classification tag for it
[1] and will answer that question shortly.
Kind regards
Felix Lechner
P.S. I would be happy to add additional tags for statistics if they
are helpful to your cause.
[1]
https://salsa.debian.org/lintian/lintian/-/commit/bc48c6e2114c1cf9ca143db3ad9b6068ddca791d
Hi Guillem,
On Fri, Oct 1, 2021 at 6:57 PM Guillem Jover wrote:
>
> Unamused,
I am sorry that happened. Did I not accept your patch in full? [1]
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/3758bfafd5dd742c327f2312dac8e3a71b1f036e
given.
Kind regards
Felix Lechner
short period in early October (and possibly late September) but some,
like colortest-python, are clearly unrelated.
Either way, isn't the issue fixed?
Kind regards
Felix Lechner
Hi Graham,
On Wed, Nov 3, 2021 at 9:48 AM Graham Inggs wrote:
>
> Control: affects -1 src:python-boto3
Isn't that bug closed?
Kind regards
Felix Lechner
unstable as unfit for release, perhaps even
replacing it with one that works with UTF-8? The version in bullseye
does not have the issue. Thanks!
Kind regards
Felix Lechner
contributors to Lintian, Lintian's
testsuite enforces a project-wide style in Salsa CI (but not in Deb
CI). Your help would be very much appreciated.
I also mentioned it briefly on the Perl team's mailing list [1] but
have not received any replies yet. Thanks!
Kind regards
Felix Lechner
hat any of the suggested fixes are
acceptable. (After a year, they are for the Lintian maintainers.)
Sorry if that looks like I jumped the gun.
Thank you for spending so much time on this, and for solving the riddle!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/salsa-ci
uired. Policy section 5.2 presently shows
the field as merely recommended. Thanks!
Kind regards
Felix Lechner
did not mean to suggest that the entry points are removed.
Furthermore, the bug was already closed when you wrote.
If the entry points are missing from asciidoc and it breaks your
package, you may wish to file a bug there instead. Thanks!
Kind regards
Felix Lechner
Control: reopen -1
Hi,
On Sun, Oct 31, 2021 at 3:24 AM Mattia Rizzolo wrote:
>
> dpkg maintainers pointed me to #555743 - so I think this "just"
> needs some Policy massaging.
> I filed #998165 on that regard
Lintian will soon allow the field, too. Thanks for the researc
There was a valuable discussion of Salsa here. [1] It included this
valuable information:
[1] https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/312
Santiago R.R. commented:
I think some of you already knew it, but I confirmed this is something
related to the running environment, m
wrote
Lintian's from scratch. Thanks!
Kind regards
Felix Lechner
n_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
The output from 'locale -a' is too long. I must have 'locales-all' installed.
Kind regards
Felix Lechner
. [1]
Should it only use LANG? How does that jibe with the recommendation
here [2][3] to always use LC_ALL when running programs? Thanks!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Documentation/Manual.pm#L295
[2] https://stackoverflo
gt; install it.
For now, I requested locales-all. [1]
Kind regards
Felix Lechner
[1] https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/312
blame. The
shared runner operates in 'privileged' mode. [1]
I also contemplated other methods making the C.UTF-8 locale available
via the Docker file. [2]
I'll look into the Salsa runner package list again, unless you beat me to it.
Thanks!
Kind regards
吴大菲 (Felix Lechner)
[1] htt
Hi,
On Fri, Oct 22, 2021 at 8:20 AM Yves-Alexis Perez wrote:
>
> That page doesn't apparently mention the term 'plugin', which I think is one
> good reason to set the runpath on a binary, though :)
Maybe you could add it to the Wiki page, if you have time. Thanks!
Kind regards,
Felix Lechner
nable to find
packages using that exemption.) Is your package affected by that
change?
The commit [2] reduced the nesting depth and the complexity of the
conditionals. It is therefore possible that the relevant portion of
the check did not previously run for your package.
Kind regards
Felix Lech
ecks and are beautiful little things!
> an exception for autotools files would be warranted?
Yes, the exception is probably warranted. If it's okay with you,
however, I will postpone the decision until the cruft check, which
issues the offending tag, is fixed. It is currently malfunctionin
see the
issue, please?
Kind regards
Felix Lechner
d regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/37a4e213600e467442fd30de8b23080c1ad77e5f
es "$1"
echo "${@}" >>"${DESTDIR}/conf/modules"
}
The hook could check if the module exists, but it seems more robust to
do it at boot time.
Is this a bug in mdadm or in initramfs-tools?
Kind regards
Felix Lechner
pdated tag description is now live on our website. [2]
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/af93172c7a9ef326a68fd337c5089c52b74eb3f5
[2]
https://lintian.debian.org/tags/possibly-insecure-handling-of-tmp-files-in-maintainer-script
ae0 ("Bring the binaries check up to the latest
> coding standards.")
Thanks for your hard work! A fix was committed, and your hints on
Lintian's website were updated:
https://lintian.debian.org/sources/ncurses
https://lintian.debian.org/sources/libpcap
Kind regards
Felix Lechner
egards
Felix Lechner
while the name
detection is broader and more user-friendly.
After some contemplation, I left the duplication issue to be solved on
another day.
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/blob/master/data/cruft/non-free-files
tectures." but got "Sorry, your search gave no
results." Thanks!
Kind regards
Felix Lechner
Hi,
> I wondered how one would come up with such a strange dependency
As a follow-on, Lintian may be able to help with additional warnings.
Kind regards
Felix Lechner
e that the fix is acceptable for now!
Kind regards
Felix Lechner
issue. The hint is wrong
altogether, isn't it?
Kind regards
Felix Lechner
outside Salsa CI.
- static-library-has-unneeded-sections is Bug#995991. [4] The fix is
pending, but has not yet been uploaded.
- superficial-tests is being disputed in Bug#994139. [5]
Kind regards
Felix Lechner
[1] https://bugs.debian.org/993613
[2] https://bugs.debian.org/973313
[3]
https://lintian.
led because Lintian produced a lot of errors and warnings.
You can also see results for the version currently in unstable on our
website [2] but they look quite different.
Kind regards
Felix Lechner
[1]
https://debian.pages.debian.net/-/freetype/-/jobs/2061949/artifacts/debian/output/lintian.htm
Hi,
On Mon, Oct 11, 2021 at 6:16 PM Hugh McMaster wrote:
>
> I'll look into enabling Salsa CI for the repo.
With some luck, you can simply add a file like this one [1] to your repo.
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lechner/mdadm/-/blob/debian/master/debian/salsa-ci.yml
t the array as susceptible to new upstream
versions as four separate lines?
BTW, Lintian's test suite has an automatic hint adjuster. (No editor
required.) Would that be helpful to the public for use on their
overrides?
Kind regards
Felix Lechner
Control: reopen -1
Hi,
A recent commit [1] gave rise to a different fix, which is coming soon. Thanks!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/93b4e49c805ccf767f948ada5993318ab711120c
Hi Hugh,
On Sun, Oct 10, 2021 at 9:54 PM Hugh McMaster wrote:
>
> Is it possible to make the line number component an optional array? line
> [1,3,5]
Do you mean overriding some line numbers, but leaving others? Thanks!
Kind regards
Felix Lechner
e: source-contains-prebuilt-javascript-object
ft2docs/docs/js/jquery.ba-resize.min.js
Will you please include your full invocation (and also point us to an
interim build in Salsa CI, if needed) so we can investigate? Thanks!
Kind regards
Felix Lechner
Hi,
On Sun, Oct 10, 2021 at 3:33 PM Thorsten Glaser wrote:
>
> I’ve not yet tested ...
> whether the asterisk indeed allows anything to come after,
> i.e. “line * ot to” isn’t equivalent to “line *”…
I am not sure it's a good feature, but it should work. [1][2]
Kind regards
Hi,
On Wed, Oct 6, 2021 at 6:21 PM Thorsten Glaser wrote:
>
> Can I use a wildcard then?
By the way, you should also be able to use the wildcards * and ? in
lieu of the line numbers right now. Please let me know if that works.
Thanks!
Kind regards
Felix Lechner
ng you trouble? If so, I'll have a look. Thanks!
Kind regards
Felix Lechner
n.) Would it help for your override issue to relegate
the line numbers to the end of the context? Thanks!
Kind regards
Felix Lechner
hanges will probably be reverted when
the ':any' is dropped from the Python prerequisites.
Thank you for bringing the matter to our attention!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/beb1094db955fd99b693fca1e4c87958676dfe74
[2] https://bugs.debi
Maybe I will take it as an opportunity to give the matter some thought.
Kind regards
Felix Lechner
ther way to identify R packages?
The tag is issued for sources. [3] Maybe you can find some ideas in
the existing checks. [4][5][6]
Thanks for bringing this to our attention!
Kind regards
Felix Lechner
[1] https://lintian.debian.org/screens
[2] Sorry to quote myself,
https://lists.debian.org/debian-p
Hi,
> It is possible the files are being saved in a format not understood
> by my PDF reader
I believe the corruption is caused by the page cleanup. Dirty pages
are affected more often, while legible and corrupted pages appear
together in the same documents. Thanks!
Kind regards
Felix Lechner
reportbug. I do not use it much but it worked very
well, especially with the custom data collection.
I use your tool almost every day. Thanks for looking into this issue!
Kind regards
Felix Lechner
simple-scan.log.xz
Description: application/xz
umped the visibility [1] until we can figure out a better way to
proceed?
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/cbf654cce71dd2ac294c82767963cc0507093d42
f it (or so it seemed when I
wrote). The bug is also somewhat treacherous: The image on the screen
looks fine. One has to open the saved file to see the issue.
Thanks for simple-scan! It's a great and best-in-class program!
Kind regards
Felix Lechner
[1] https://www.debian.org/Bugs/Developer#severities
Package: postgresql-semver
Severity: serious
The sole purpose of this bug is to keep version 0.31.1-3 out of
testing until version 0.31.1-2~bpo11+1 is in backports.
r your patience!
Kind regards
Felix Lechner
specially for Perl.
Thank you for your diligent maintainership, and especially for this report!
Kind regards
Felix Lechner
at we have—either in that tag or in the
'breakout-link' tag being discussed here.
Maybe 'breakout-link' is not useful and we should get rid of it, but
it looks to me like we found an issue in the way libgpg-error or
Pkg-config invoke Libtool.
Kind regards
Felix Lechner
[1] ht
o /opt, for example.
Prior to Glibc, I encountered only packages in which links and shared
objects shared a parent folder.
Kind regards
Felix Lechner
[1] https://bugs.debian.org/243158
ere dropped from Lintian two years ago. [2]
In addition, it is not well-publicized that version numbers for
installation (aka "binary") packages are not necessarily tied to the
version strings for their sources, but I do not remember an example
right now.
Kind regards
Fel
ressed at the same time, although I am not yet sure how.
Kind regards
Felix Lechner
nused build time tests
I am not sure how to implement the original request. Your suggestions
are welcome.
Thank you for figuring out the purpose of this report!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/7428997ded64b57
of the changed circumstances, the present report is
likewise downgraded to 'normal'.
Kind regards
Felix Lechner
[1] https://ftp-master.debian.org/static/lintian.tags
[2] https://lintian.debian.org/autoreject
[3] https://lists.debian.org/debian-vote/2021/09/msg1.html
[4] https://lists.
#
# mkdir GIT
# git clone git://ozlabs.org/~paulus/ppp.git
# cd ..
#
# rsync --delete --archive --verbose GIT/ppp/ ppp-2.4.5~$(date
+%Y%m%d).orig/ --exclude=.git
# cp -a ppp-2.4.5~$(date +%Y%m%d).orig/ ppp-2.4.5~$(date +%Y%m%d)/
#
Kind regards
Felix Lechner
[1]
https://www.debian.org/doc/debian-
[1]
Interestingly, the call to ./configure specified '--disable-rpath' but
was not successful. It seemed to resemble an issue in opendkim [2].
Perhaps this Debian doc about the topic [3] is helpful to you.
Kind regards
Felix Lechner
[1] https://salsa.debian.org/auth-team/sh
fig paths derived here [4] in part
from the multiarch path components found here. [5][6]
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/SharedLibs.pm#L307-309
[2]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Shar
in /usr/lib?
> glibc has always been installed like that.
The analysis may not apply to Glibc. I do not see a Pkgconfig in
libc6-dev (and would have been surprised). Does Glibc recommend any
linker paths to consuming packages?
Kind regards
Felix Lechner
d ld.so
features, but I am reading up on this blog page [3].
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/debian/libgpg-error/-/commit/7c408ba0968c14492b6f087c57c6d44af4878de6#8756c63497c8dc39f7773438edf53b220c773f67_34_33
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992573#5
[3] http://blog.tremily.us/posts/rpath/
controversy in the
past. At this point, I would simply like to change the documentation.
Would that work for you? What is your use case, please? Thank you!
Kind regards
Felix Lechner
Hi,
On Tue, Sep 14, 2021 at 5:44 AM Bill Allombert
wrote:
>
> I do not know, I also tried
Do you still see the bug? Here is the fix:
https://salsa.debian.org/lintian/lintian/-/commit/3fc81b4576fac2b911a59660d19fa1567b90139f
Kind regards
Felix Lechner
be used to mask the tag superficial-tests (or any other
autopkgtest tag discussed here) for sources for which meaningful tests
do not exist.
[6]
https://salsa.debian.org/lintian/lintian/-/commit/8c3d587559cfbdf5dd41e9ba1f66c9ab52de577e
[7] https://lintian.debian.org/screens
Kind regards
Felix Lechner
like autopkgtest. Either way, the project relies here on the fact
that having a meaningful testsuite may provide a faster migration from
unstable to testing.
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Testsuite.pm#L89-91
[2]
https://
usually for teams). [3]
Lintian also issues 'no-tests' for defective control stanzas [4] and
the somewhat specialized 'no-op-testsuite' for fakers [5]. The
relevant code with a few other tags is located here. [6]
I will likely respond with a suggested solution at some point in
bug without action.
Please reply to Bug#743694 if your response concerns Lintian's
treatment of privacy breaches. Thanks!
Kind regards
Felix Lechner
ardsVersion.pm#L76-81
Kind regards
Felix Lechner
an CI is failing (but
separately, since I copied the policy bug). Thanks!
Kind regards
Felix Lechner
[1]
https://salsa.debian.org/lintian/lintian/-/commit/d2f692f564ac725a0eb58a7d62abe57f66cdc753
[2]
https://salsa.debian.org/lintian/lintian/-/commit/21fd3c7d1ae24bf3bb00ffbab6a0dd99acd3503c
[3]
> for certain files under debian/ like debian/upstream/metadata ?
I would certainly welcome such a tool.
Kind regards
Felix Lechner
a homepage classification.
I think there is a difference. A project's home page is often the
first point of contact, especially in search of documentation. When do
people look at the Registration field in the upstream metadata,
please?
Kind regards
Felix Lechner
[1]
https://codesearch.debi
101 - 200 of 985 matches
Mail list logo
