Package: src:ruby-hoe Followup-For: Bug #952041 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
I cannot reproduce this issue. The two dates shown are (probably) the date of the build (expected) and the date in hoe.gemspec of unstable's ruby-hoe 3.21.0+dfsg1 (got). When I run it locally the dates are both the one from the build. So the question probably is: how did the date in unstable's how.gemspec sneak into the ruby 2.7 build and why? Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5cX4kACgkQS80FZ8KW 0F0WmA//T+Bpcrg3v8NwclSRXlWGdxzy6Hrpa6YxaEQcfzACeOk3ltJr+gWIk2ga WFBrL5HnAN8kTY/tsjdaJI+Eeio+u1TU3CSNluYIc2oYK8hHanA7RNqpz68eW9nF OpDbQoan6y956rhaYeomVOoTF9Pz7yc2FL4YGcOaFGSyuMJdOd7ExWoMDdkF3TUl OHnTpQHFcNhLWLfn3OZpE/EZcC4tHg7jVHbjugtMMk2PAo6ha7IwFcdHI8LPFDRF XFbzFV/ljZV+qMZ4w7JY1U12J4jKMY4qoKt3oQ+qvu1+7tn/16PtPZTjNlgdjQn8 C1oE4y31vEU1NEHS484EWAaf3bQIEwCqkYroBgoz4+GyfYnQw91ugl+1fhkP35ka N7YvNhEmRnGTHqtVMlF0XJb8Rnb62Yihwsto8pE7MDXE/OdX1798RXTN6c7Japyu QUHEvYrpxuiKGhUYZDdXzxVEMGucIE6c+MwujuT00QenK5bqr5M64SqJgxq9cSQF QyKonYob4vT8DPdIjZ/0jHA2IHs8dAuJj25BebrrGxZw6ZTtnwF1pKk7MzwrRQfG 0VdRJNthhXsqQP705Kopto1tNN+mgpy64Y4fSi65pMCtAdcpHfNhOVwN9YLI/Vc4 8gOpc/0hRh1P8HHZEZhEQBcQfrlTka5uHdzcLCFv2D91OQrJ+ok= =eSIh -----END PGP SIGNATURE-----
