[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1021207: marked as done (lintian: Please reconsider the type and size of field-too-long)

Your message dated Wed, 31 Dec 2025 03:52:24 +0000
with message-id <E1vanG4-00000004Dnr-1oS8@fasolo.debian.org>
and subject line Bug#1021207: fixed in lintian 2.128.0
has caused the Debian Bug report #1021207,
regarding lintian: Please reconsider the type and size of field-too-long
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1021207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021207
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.115.3
Severity: normal
X-Debbugs-Cc: team+tryton-team@tracker.debian.org


Dear Maintainers,

I was hit by

E: tryton-modules-all: field-too-long Depends (5604 chars > 5000)
N:                    
N:   The length of the specified field is too long.
N:             
N:   Overly-long fields not only can break some tools tools (eg.
reprepro(1))
N:   they can waste space as they are shipped to all users. 
N:                         
N:   Please reduce the number of characters.
N:             
N:   Please refer to Bug#942493 for details.
N:        
N:   Visibility: error
N:   Show-Always: no
N:   Check: fields/length   

The one and only purpose of tryton-modules-all is to list all
available Tryton modules in Depends (or Recommends, but that shouldn't
matter). For now I have added a lintian-override, but of course I don't
want to break infrastructure.

Looking at #942943 and #942487 it looks as if the issue with reprepro
should be mitigated with 
https://salsa.debian.org/debian/reprepro/-/commit/7cb8fcf53c077467c4f38b5a48f706e7b5f75f4c

So I am asking for re-evaluation and/or advice

- if this limitation still stands?
- if the former is true this shouldn't be rather a warning than an
  error?
- if the former is true the only way out is to split the Depends into
  sub-packages?



-- 

    Mathias Behrle
    PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6
    AC29 7E5C 46B9 D0B6 1C71  7681 D6D0 9BE4 8405 BBF6

--- End Message ---
--- Begin Message --- 
Source: lintian
Source-Version: 2.128.0
Done: Louis-Philippe Véronneau <pollo@debian.org>

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1021207@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Louis-Philippe Véronneau <pollo@debian.org> (supplier of updated lintian package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 30 Dec 2025 19:00:24 -0500
Source: lintian
Architecture: source
Version: 2.128.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Louis-Philippe Véronneau <pollo@debian.org>
Closes: 896012 909267 931112 999785 1021207 1111513 1118442 1119083 1120737 1123580 1123984
Changes:
 lintian (2.128.0) unstable; urgency=medium
 .
   [ Louis-Philippe Véronneau ]
   * Refresh data sources - 2025-12-28
   * Downgrade field-too-long from 'error' to 'warning'. Closes: #1021207
   * Add debian/.gitlab-ci.yml to @KNOWN_LOCATIONS. (Closes: #1123984)
   * Remove tag 'built-using-field-on-arch-all-package' (Closes: #999785)
 .
   [ Nilesh Patra ]
   * Remove recommended-field check for "Priority:" field (Closes: #1111513)
   * Remove bsdutils from essential package set check (Closes: #1118442)
   * Add some missing team domains for team maintained packages and flagging
     packages using alioth domain
   * Do not check for missing-call-to-dpkg-maintscript-helper on udeb (Closes:
     #1119083)
 .
   [ Rong Fu ]
   * Add known-dists for eLxr
 .
   [ Luca Boccassi ]
   * Downgrade hardening-no-fortify-functions to experimental (Closes: #931112)
 .
   [ Rafael Laboissière ]
   * Prevent non-ar *.a files from triggering false positives in
     unpack-message-for-{source,orig,deb-data} (Closes: #1120737)
 .
   [ Jeremy Bícha ]
   * Remove library-not-linked-against-libc check (Closes: #896012, #909267)
   * Remove stray-devhelp-documentation
 .
   [ Bas Couwenberg ]
   * Fix FTBFS with dpkg 1.23.0. (closes: #1123580)
Checksums-Sha1:
 88c1af237de19e9e2f1c655274a8db4f5a8c8ec9 3631 lintian_2.128.0.dsc
 cc037fbb5bcd7e95b5072c846e933716aee27299 2264248 lintian_2.128.0.tar.xz
 e95302ab422f68e652e46c529389ebe3467dd2cc 21962 lintian_2.128.0_amd64.buildinfo
Checksums-Sha256:
 1cb6f12265f5155fae0617993079a409fc97a080764ee2c3b04171d387d6f889 3631 lintian_2.128.0.dsc
 69e5ea30879d5e39ddd53737b652c09676ce6532a58562c49faa597a7b0fb2de 2264248 lintian_2.128.0.tar.xz
 04872bec71288df442e65703eba3201ad92527afa1dd1f77d5d66c079b8a3014 21962 lintian_2.128.0_amd64.buildinfo
Files:
 bf2c79d037e6e567835970edc731d110 3631 devel optional lintian_2.128.0.dsc
 03b603894c989e8b51524a06f1f62423 2264248 devel optional lintian_2.128.0.tar.xz
 cd67fe81d8602a8d85f956e97145c3ed 21962 devel optional lintian_2.128.0_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQTKp0AHB6gWsCAvw830JXpQshz6hQUCaVSS9wAKCRD0JXpQshz6
hTnFAP9S/mVu5rOQH0uIux7hZIdeSHR1/OQOoT4jYhqzsIuxFwEAgbP73FjrorAR
hZYHMue/cM+TAbEX1kxj/EM/2sEKHQk=
=yIFS
-----END PGP SIGNATURE-----

Attachment: pgph4rZRhNVpU.pgp
Description: PGP signature


--- End Message ---
Reply to: