Processed: Re: Bug#1030720: cherrytree: new upstream version 0.99.54 + patch

2023-02-06 Thread Debian Bug Tracking System
Processing control commands:

> owner -1 !
Bug #1030720 [cherrytree] cherrytree: new upstream version 0.99.54 + patch
Owner recorded as Andrius Merkys .
> block -1 by 1030743
Bug #1030720 [cherrytree] cherrytree: new upstream version 0.99.54 + patch
1030720 was not blocked by any bugs.
1030720 was not blocking any bugs.
Added blocking bug(s) of 1030720: 1030743

-- 
1030720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1030743: lintian: broken Unicode symbols in message

2023-02-06 Thread Andrius Merkys

Package: lintian
Version: 2.116.3

Hello,

One of the packages I maintain, cherrytree, has a file 
'tests/data_данные/test.export.html' which invokes source-is-missing 
lintian error. However, Unicode symbols in lintian output are shown broken:


$ lintian cherrytree_0.99.53+dfsg-1.dsc
E: cherrytree source: source-is-missing 
[tests/data_даннÑ?е/test.export.html]


Not sure if this is related, but LC_ALL for me is 'en_US.UTF-8' and 
setting it to 'C' does not help either.


Seeing broken Unicode I am not sure lintian will understand the name of 
this file in lintian override.


Andrius



Bug#858039: lintian | Make SVG graphs more understandable by adding the tag name. (!455)

2023-02-06 Thread Axel Beckert
Hi Brian,

Brian Thompson (@brianrobt) wrote:
> Make SVG graphs more understandable by adding the tag name.
>
> Fix for #858039.

Thanks a lot for your contribution! Had to look into the bug report to
see that this actually was my own feature request from many years ago.
:-)

Unfortunately the code for the lintian.debian.org website has been
rewritten completely since then (by a Lintian maintainer after Niels
who replied back then) and the current website doesn't seem to sport
these SVGs anymore. At least I couldn't find them.

Additionally generating the website broke under the previous
generation of Lintian maintainers and nobody of the current generation
(including myself) knows how it works or how to even access it.

Fixing the lintian.debian.org website is on our TODO list, but only
with lower priority for after the Bookworm release (or at only after
it is frozen enough so that we can focus on other things).

It's also not high priority because we have
https://udd.debian.org/lintian/ as slower (because non-static)
replacement for the most pressing up-to-date statistics about lintian
tags and packages.

Because of all that and because of we're in the first stage of the
freeze for Bookworm, I'll though merge your merge request only after
the Bookworm release as it does not bring any advantage for Lintian in
Bookworm.

(And yes, I'll merge it even though the feature is not used as of now.
I still have hope that we can bring it back. :-)

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



Bug#858039: lintian: Graph (SVG) files on https://lintian.debian.org/ lack tag name

2023-02-06 Thread Brian Thompson
I've submitted a PR to get this change in as proposed by Axel:

https://salsa.debian.org/lintian/lintian/-/merge_requests/455
-- 
Sincerely,

Brian


signature.asc
Description: This is a digitally signed message part


publickey - brianrobt@proton.me - 688c834d.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature


Bug#1028125: wrong source-contains-prebuilt-windows-binary for GB18030-encoded text file

2023-02-06 Thread James Addison
Package: lintian
Followup-For: Bug #1028125

Hi Rene,

Do you know whether this is a regression (as in: did lintian/file previously
correctly identify the file type for GB18030.txt)?

There seems to be some code adjustments in libmagic recently, in particular
related to PE32 file types.  I didn't manage to understand the reasoning and
effect of those changes, but am wondering if they could be related to this bug.

Thanks,
James