Bug#1031377: Info received (Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source)
Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): debian...@lists.debian.org If you wish to submit further information on this problem, please send it to 1031...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 1031377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source
On Thu, 16 Feb 2023 15:05:24 +0100 Lucas Nussbaum wrote: > What could work is: > run lintian on source > for each arch in the packages's architectures (except all) > run lintian on architecture packages + architecture 'all' packages > > But would that solve all issues? I discovered that it does not solve all issues. For example src:rust-bat builds bat. When you run lintian against the dsc and the deb it emits missing-notice-file-for-apache-license for the source package, but when you run it against only the dsc or only the deb it does not emit that tag. That is because the test checks that the NOTICE file from the source package is missing from the binary package. https://lists.debian.org/msgid-search/8062de5e3a1afbe988ce3d5453d211089242ba2a.ca...@debian.org -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: lintian.debian.org off ?
Otto Kekäläinen wrote on 27/09/2023 at 06:35:07+0200: > Hi! > > Thanks for the context - so there is no need technical incompatibility > at play, but mostly a matter of having resources and time to do it. > .. >> Regarding the 301 redirection I'll see with the interested parties (DSA >> and Lintian maintainers) if this option is fine with everyone. > > I could easily write Ansible code to maintain a simple Nginx server, > with 302 redirects https://lintian.debian.org/tags/(.*)/?$ -> > https://udd.debian.org/lintian-tag.cgi?tag=$1, use same Ansible style > as salsa.debian.org is maintained on > (https://salsa.debian.org/salsa/salsa-ansible), and also donate a tiny > virtual machine for Debian project if needed. Is there some special > bureaucracy on top of that work to do to be able to contribute with > this? Don't worry, the server still exists, it's just down, and reputting the DNS takes little to no time. Regarding apache config, I'm fine with doing it. It's a matter of checking with everyone that we want to do that as the plan was nuking the server from orbit. Providing debian.org infrastructure requires to be a member of the Debian System Administrators (DSA) team, which in turn requires to be a Debian Developer, so, sadly, you can't really help on that part. That being said, thank you for offering your time. > I know Lintian tag info is available via command line, but I > frequently need to educate upstreams about Lintian rules, and thus > really also need a URL to share to them. Perhaps I could implement > that later in the year. -- PEB signature.asc Description: PGP signature
