bug#35289: closed (Re: bug#35289: date+%-Y -d "- N years" errors when N > 111)

[Assaf Gordon]

Hello,

On 2019-04-15 11:55 a.m., C de-Avillez wrote:
> 19.04:

It is worth noting that Ubuntu 19.04 has not been officially released
yet, so you are testing on a development branch (or a release-candidate,
or a special built infrastructure as hinted by your path).

> address@hidden:/data/buildd/coreutils$ date +%-Y -d '- 2010 years'
> date: invalid date ‘- 2010 years’
> 1 address@hidden:/data/buildd/coreutils$ date --version
> date (GNU coreutils) 8.30

[...]

> On Mon, Apr 15, 2019 at 12:16 PM O. Emmerson <address@hidden> wrote:
> > $ file /bin/date
> > /bin/date: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
> > dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
> > GNU/Linux 3.2.0, BuildID[sha1]=26fa7f6c43c354d8c5647ebf946255a2b8e3c53d,
> > stripped

I just downloaded a recent daily snapshot of
ubuntu desktop live CD for amd64 from 
http://cdimage.ubuntu.com/daily-live/current/ .
The file "disco-desktop-amd64.iso" dated 2019-04-13 22:28 size 1.9GB,
with the following checksum:

  $ sha1sum disco-desktop-amd64.iso
  b89fb143b51e17482a3882abe2f5f4e3b69942fe  disco-desktop-amd64.iso

Booting with QEMU as live-cd, I tested the same command and got "9" as
the (correct) result. So this can't be easily reproduced.

An interesting benefit of reproducible builds is that I see on the
live-cd image the sha1 checksum of "/bin/date" is the same as you listed
above. This hints to me the problem is somewhere else in your setup.

As this is not an official release, we really can't support it.
You'll have to dig further and see what is the issue.

A good starting point is adding the "--debug" option to date(1)
and examining its output.

regards,
 - assaf