[buildd-tools-devel] Bug#843773: Bug#843773: Bug#843773: misleading timestamps in binnmus
Johannes Schauer
josch at debian.org
Mon Nov 14 14:38:24 UTC 2016
Hi,
Quoting Ian Jackson (2016-11-14 14:52:18)
> I don't think it is possible to make the binnmu timestamp the same
> across architectures. For example, a package might be rebuilt only
> on some architectures. I don't think we want to change that. In
> particular, even if we were prepared to change that in Debian, we
> should not impose always-binnmu-all-arches as a rule on all our
> downstreams.
Thank you for your analysis and your proposal.
I want to understand why passing the same timestamp to all architectures is an
inferior solution to your proposal. I also don't see why it's a problem that a
package might only be rebuilt on some architectures. If only some architectures
of a M-A:same package get a binNMU, then they are not co-installable anyways.
Thanks!
cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20161114/b772d1ee/attachment.sig>
More information about the Buildd-tools-devel
mailing list