On 2022-12-22, Vagrant Cascadian wrote:
> On 2022-10-06, Vagrant Cascadian wrote:
>> The attached alternate implements this for mc by touching the potential
>> files before running configure with a consistent timestamp.
>>
>> According to my local tests, applying this patch should make mc build
>>
On Thu, 22 Dec 2022, Vagrant Cascadian wrote:
I Intend to NMU with this patch on the 29th (with a 10-day delay) unless
I hear otherwise.
I have no objections to that; please proceed, if you believe that this is
the right thing to do. Your graceful heads up is appreciated.
I was just trying
On 2022-10-06, Vagrant Cascadian wrote:
> The attached alternate implements this for mc by touching the potential
> files before running configure with a consistent timestamp.
>
> According to my local tests, applying this patch should make mc build
> reproducibly once it lands in
On 2016-06-27, Yury V. Zaytsev wrote:
> On Mon, 27 Jun 2016, Reiner Herrmann wrote:
Going through some old outstanding reproducible builds related bugs...
>> You are right, the mtime of the file is used for the manpage timestamp.
>> But there is still a patch modifying the manpage:
>>
On Mon, Jun 27, 2016 at 10:39:52AM +0200, Yury V. Zaytsev wrote:
> For instance, it seems to me that it is only logical to set the mtime of
> patched files to the mtime of the last patch that touched them, and this
> will make the source mtime dependent builds fully reproducible.
>
> Have you
Hi Reiner,
On Mon, 27 Jun 2016, Reiner Herrmann wrote:
You are right, the mtime of the file is used for the manpage timestamp.
But there is still a patch modifying the manpage:
mcedit_full_path.patch. When this patch is upstreamed, the
SOURCE_DATE_EPOCH patch is not needed, though it would
On Sun, Jun 26, 2016 at 10:21:49PM +0200, Yury V. Zaytsev wrote:
> On Sun, 26 Jun 2016, Reiner Herrmann wrote:
>
> >While working on the "reproducible builds" effort [1], we have noticed
> >that mc could not be built reproducibly. It embeds the current date into
> >the mcedit manpage during
On Sun, 26 Jun 2016, Reiner Herrmann wrote:
While working on the "reproducible builds" effort [1], we have noticed
that mc could not be built reproducibly. It embeds the current date into
the mcedit manpage during build.
Ok, I think that I can now see what went wrong here: Debian used to
Hi Reiner,
On Sun, 26 Jun 2016, Reiner Herrmann wrote:
Yes, it is standardized [1] and already supported by a lot of build
tools [2], e.g. even by gcc. Other distributions and FreeBSD are
currently also in the process of adopting it.
Thank you for the clarifications! Maybe you could
Hi Reiner,
On Sun, 26 Jun 2016, Reiner Herrmann wrote:
While working on the "reproducible builds" effort [1], we have noticed
that mc could not be built reproducibly. It embeds the current date into
the mcedit manpage during build.
That's my fault: the dates were originally entered by hand,
On Sun, Jun 26, 2016 at 09:00:50PM +0200, Yury V. Zaytsev wrote:
> >The attached patch uses SOURCE_DATE_EPOCH as a deterministic timestamp
> >instead.
>
> I wouldn't mind upstreaming this patch as long as SOURCE_DATE_EPOCH is at
> least halfway standardized. Could you please tell me whether this
Source: mc
Version: 3:4.8.17-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi!
While working on the "reproducible builds" effort [1], we have noticed
that mc could not be built
12 matches
Mail list logo
