Bug#843867: pbuilder: allow passing the timestamp for the new changelog entry for binNMUs
Mattia Rizzolo
mattia at mapreri.org
Thu Nov 10 11:07:03 UTC 2016
On Thu, 10 Nov 2016, 11:48 a.m. Johannes Schauer, <josch at debian.org> wrote:
> Package: pbuilder
> Severity: normal
>
> Hi,
>
> currently, binNMUs changelog entries are generated by re-using the
> timestamp from the previous upload with source.
In pbuilder's case the date of a binNMU is just `date -R` when the command
runs, thus we don't have the same problem as described there.
I'm following that discussion to see what it'll lead to, but I'm
unconvinced that we need to mangle the date like you suggest. Especially
your last email that talks about m-a:same potential troubles leaves me
unbought, as ma:same is afaik only avout file contents, surely not file
metadata (timestamps) (which would be different anyway for the "last
timestamp+1sec" as you said?!).
Anyway, I'm following :)
This is undesirable as
> described in the corresponding bug for sbuild #843773. pbuilder should
> support a similar facility as is discussed there for sbuild to stay
> compatible and able to reproduce binNMUs from the archive.
>
Surely adding flags is easy, but I'd like to avoid polluting the command
line ;)
> Thanks!
>
> cheers, josch
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pbuilder-maint/attachments/20161110/50d47f15/attachment.html>
More information about the Pbuilder-maint
mailing list