Dear J??r??my Bobbio, you wrote:
Control: tags -1 + patch
tony mancill:
Thanks for the suggestion and for looking into the cause of the issue
with the bobcat build. I'm suspect that Frank, the upstream developer,
will be willing to address this in a future upstream release.
Of course I
Hi Frank,
Frank B. Brokken:
Of course I am. Could somebody please enlighten me what the problem actually
is? This is the first time in my l-o-o-o-o-ng life that I learn about a thing
called a `timestamp of a gzip file' and that it may cause problems.
In Debian context, it currently can pause
Dear J?r?my Bobbio, you wrote:
...
For the latter to work, we need to eliminate any variations coming from
external factors, like timestamps.
Hope that helps,
Absolutely,
Thanks for the speedy clarification!
Cheers,
--
Frank B. Brokken
Center for Information Technology,
On Mon, Sep 09, 2013 at 08:47:49AM +0200, Frank B. Brokken wrote:
Dear J?r?my Bobbio, you wrote:
...
For the latter to work, we need to eliminate any variations coming from
external factors, like timestamps.
Hope that helps,
Absolutely,
Thanks for the speedy clarification!
Package: bobcat
Version: 3.15.00-1
Severity: wishlist
Hi!
In the effort of making Debian binary package build reproducible [1], I
have noticed that your package currently ship gz compressed files with a
timestamp.
Adding the `-n` or `--no-name` flag to the various calls to `gzip` made
in
On 09/08/2013 10:30 AM, Jérémy Bobbio wrote:
Package: bobcat
Version: 3.15.00-1
Severity: wishlist
Hi!
In the effort of making Debian binary package build reproducible [1], I
have noticed that your package currently ship gz compressed files with a
timestamp.
Adding the `-n` or
Control: tags -1 + patch
tony mancill:
Thanks for the suggestion and for looking into the cause of the issue
with the bobcat build. I'm suspect that Frank, the upstream developer,
will be willing to address this in a future upstream release.
Great! Attached is a patch that indeed did the
7 matches
Mail list logo
