Package: lintian-brush
Version: 0.167
Severity: normal

Hi Jelmer,

I'm using lintian-brush nearly before any upload of my packages.
Recently I realised that it messes up Publication and Registry entries a
lot to make them either unusable (JSON sytnax becomes broken) or is
loosing a lot of information.  I would be happy if we could switch back
to some more conservative handling of these fields or rather do not
touch these.

I could assemble some specific examples if this might be helpful, thought

Thank you for lintian-brush anyway
   Andreas.

-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.18.12+deb14-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian-brush depends on:
ii  devscripts      2.26.5
ii  libc6           2.42-13
ii  libgcc-s1       15.2.0-13
ii  libgmp10        2:6.3.0+dfsg-5+b1
ii  libhogweed6t64  3.10.2-1
ii  liblzma5        5.8.2-2
ii  libnettle8t64   3.10.2-1
ii  libpython3.13   3.13.12-1
ii  libssl3t64      3.5.5-1
ii  python3-breezy  3.3.21-1

Versions of packages lintian-brush recommends:
ii  debhelper  13.30
ii  decopy     0.2.4.9-0.1
ii  dos2unix   7.5.2-1
ii  gpg        2.4.8-5
ii  lintian    2.129.0

Versions of packages lintian-brush suggests:
ii  brz-debian         2.8.80
ii  git-buildpackage   0.9.39
ii  po-debconf         1.0.22
ii  postgresql-common  289

-- no debconf information

Reply via email to