Bug#829100: lintian: [patch] Warn about over-eagerly xz-compressed data.tar.xz

2018-01-13 Thread Chris Lamb
tags 829100 + pending thanks Thanks for all your input. To prevent this issue going stale, I've gone ahead and implemented the most basic regex-based checking. No need to be "too" clever, right?

Bug#829100: lintian: [patch] Warn about over-eagerly xz-compressed data.tar.xz

2016-08-12 Thread Guillem Jover
Hi! On Thu, 2016-06-30 at 17:23:46 +0200, Christoph Biedl wrote: > Package: lintian > Version: 2.5.45 > Severity: wishlist > Tags: patch > as not known to everybody, xz's higher compression levels have - > besides improving compression of big files - the side effect of taking > a lot of memory

Bug#829100: lintian: [patch] Warn about over-eagerly xz-compressed data.tar.xz

2016-06-30 Thread Jakub Wilk
* Christoph Biedl , 2016-06-30, 22:56: So we would only bother people who overrode the default add: In an unreasonable way. Right. However I'm undecided now how to deal with that. Using lintian, actually promoted by the developer's reference 7.1.1, is

Bug#829100: lintian: [patch] Warn about over-eagerly xz-compressed data.tar.xz

2016-06-30 Thread Christoph Biedl
Jakub Wilk wrote... > dpkg's current default is -6, which uses 9MiB of memory for decompression. > Before dpkg 1.15.6, the default was -9, which uses 65 MiB. > > If I understand Christoph's patch correctly, the tag won't be emitted if > memory needed for decompression is 10 MiB or less.

Bug#829100: lintian: [patch] Warn about over-eagerly xz-compressed data.tar.xz

2016-06-30 Thread Russ Allbery
Christoph Biedl writes: > The patch attached is just a proof of concept and not ready for > production yet, especially since data.tar.xz is unpacked (and later > removed) to the current working directory. Does dh_builddeb (or dpkg-deb) already pick appropriate