aaf7851f4250f1072f6fee8c/lib/debian/copyright.py#L485
[2]
https://salsa.debian.org/python-debian-team/python-debian/-/blob/master/src/debian/copyright.py#L758
--
Lasse Collin
e --help output but it's mentioned
in INSTALL section 3.1. That is an alternative to patching to get
reproducible builds.
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
; Excuse me for the mistranslation. Fixed PO file is attached.
Thanks. I have committed it to the v5.0 and master branches in the git
repository.
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 2010-09-26 Thorsten Glaser wrote:
> Lasse Collin dixit:
> >default memory usage limit for compression (but not decompression),
> >but I don't know what that should be (40 %, 80 %, 95 % of RAM?
> >max(80 % of RAM, RAM - 256 MiB)?). Some default limit may be needed
&g
rouble
in certain situations also for Debian users, even if you haven't got any
bug reports so far.
Other than the possible changes to the memory usage limiter, there won't
be any big changes to the code. It will be mostly documentation updates
before 5.0.0.
--
Lasse Collin |
On 2010-07-27 Jonathan Nieder wrote:
> A patch. I checked with hunspell -n to see if there was
> anything else automatically detectable to fix in the man
> pages and all I found was an extra l in parallellize,
> which I have squashed into A Costa’s patch.
Thanks, applied.
--
On 2010-04-20 Philipp Weis wrote:
> attached is a patch that adds a small section about concatenating
> compressed files to the manpage.
Thanks. There is now a subsection "Concatenation and padding with .xz
files" in the man page in the upstream Git repository.
--
Lasse Collin
On 2010-04-12 Jonathan Nieder wrote:
> Lasse Collin wrote:
> > On 2010-03-21 Jonathan Nieder wrote:
> >> 100.0 % 10,000 GiB / 10,000 GiB = 1.000 999 KiB/s 9 h 40
> >> min
> >>
> >> :50:50 (less padding, more units)
> >
> >
On 2010-03-21 Jonathan Nieder wrote:
> Lasse Collin wrote:
> > I thought it would be useful to see how long it had been working
> > especially when it fails due to corrupt input when decompressing.
>
> I guess this is to know how long it would take to reproduce?
Yes.
>
ing time would need reworking the progress message line so
that all the info would fit into 80 chars.
> - message_progress_end(success);
> + if (success)
> + message_progress_end(success);
T
;
> % lzma -t baz.lzm
> lzma: Decoder error: incomplete archive quits at byte: #77824
LZMA Utils 5 will say something like "file is corrupt". It cannot know
what was the first corrupt byte though. It is possible that the decoder
produces quite a lot of output before de
Robert Millan wrote:
> On Tue, Oct 23, 2007 at 04:36:07PM +0300, Lasse Collin wrote:
> > Robert Millan wrote:
> > > On Tue, Oct 23, 2007 at 12:11:31PM +0200, Géraud Meyer wrote:
> > > > Package: file
> > > > Version: 4.21-3
> > > >
> >
esult.
>
> I recall they had plans to change the signature. CCing the lzma
> maintainers, maybe they know something..
The .lzma format currently in use is too hard to detect without looking
at the filename suffix. The new .lzma format will fix this and a few
other problems, but there are no stable tools to handle the new format
yet.
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
13 matches
Mail list logo
