Hi Niels,
On Sonntag, 7. Juni 2015, Niels Thykier wrote:
> I see no partial issue in setting this in either dh xor dh_auto_build,
> provided it is one ENV for all tools (and not one for each tool).
>
> Is the variable still actual? I vaguely remember seeing a mention of a
> "SOURCEDATE_UTC" or so
On 2015-06-04 17:24, Holger Levsen wrote:
> Hi,
>
> On Donnerstag, 4. Juni 2015, Ximin Luo wrote:
>> https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-2
>> 0150330/001317.html
>>
>> for details. TL;DR is to have SOURCEDATE as an environment variable in
>> ISO8601 format.
>>
On 05/06/15 04:19, Daniel Kahn Gillmor wrote:
> On Thu 2015-06-04 21:51:37 -0400, Brendan O'Dea wrote:
>> Local times, and daylight savings are just too much of a PITA. Just
>> use UTC and if builds on the first of the month are possibly different
>> to the changelog, so be it.
>
> I agree with B
On Thu 2015-06-04 21:51:37 -0400, Brendan O'Dea wrote:
> Local times, and daylight savings are just too much of a PITA. Just
> use UTC and if builds on the first of the month are possibly different
> to the changelog, so be it.
I agree with Brendan here.
If there are no objections to the idea th
On 5 June 2015 at 04:40, Ximin Luo wrote:
> On 04/06/15 19:30, Daniel Kahn Gillmor wrote:
>> What TZ should SOURCEDATE have? ISO8601 is capable of supplying a TZ as
>> well, so the current time could be written in a wide variety of ways
>> while meaning the same instant:
>>
>> 0 dkg@alice:~$ date
On 04/06/15 19:30, Daniel Kahn Gillmor wrote:
> What TZ should SOURCEDATE have? ISO8601 is capable of supplying a TZ as
> well, so the current time could be written in a wide variety of ways
> while meaning the same instant:
>
> 0 dkg@alice:~$ date '+%FT%T%z' && date -u '+%FT%T%z'
> 2015-06-04T13
On Thu 2015-06-04 10:38:53 -0400, Ximin Luo wrote:
> A few months ago I had an idea for this that would be more generalisable. See
>
> https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20150330/001317.html
>
> for details. TL;DR is to have SOURCEDATE as an environment variab
Hi,
On Donnerstag, 4. Juni 2015, Ximin Luo wrote:
> https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-2
> 0150330/001317.html
>
> for details. TL;DR is to have SOURCEDATE as an environment variable in
> ISO8601 format.
>
> It would be awesome for help2man to support this.
On Thu 2015-06-04 08:17:59 -0400, Brendan O'Dea wrote:
> The idea was that unless that environment variable was set, the
> behaviour would be unchanged: the current date would be used. It
> seems unlikely that DEB_BUILD_CHANGELOG would be set accidentally.
right, but this wouldn't be terribly use
On 4 June 2015 at 00:19, Daniel Kahn Gillmor wrote:
> On Wed 2015-06-03 08:24:51 -0400, Brendan O'Dea wrote:
>> My inclination is instead to do something fairly specific to your
>> project: If the environment variable DEB_BUILD_CHANGELOG (or something
>> similar) is set, then the file to which it
Hi Brendan--
Thanks for the quick followup! (cc'ing the r-b list)
On Wed 2015-06-03 08:24:51 -0400, Brendan O'Dea wrote:
> On 2 June 2015 at 04:49, Daniel Kahn Gillmor wrote:
>> Please consider the attached patch as a step on the way toward allowing
>> packages that use help2man to build reprodu
11 matches
Mail list logo
