Your message dated Sat, 07 Jan 2023 10:23:15 +0000
with message-id <[email protected]>
and subject line Bug#1027377: fixed in miller 6.6.0-2
has caused the Debian Bug report #1027377,
regarding miller: FTBFS in bullseye (missing build-depends on tzdata)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1027377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027377
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:miller
Version: 5.10.0-1
Severity: serious
Tags: ftbfs patch
Dear maintainer:
During a rebuild of all packages in bullseye, your package failed to build:
--------------------------------------------------------------------------------
[...]
debian/rules binary-arch
dh binary-arch
dh_update_autotools_config -a
dh_autoreconf -a
[...]
================================================================
Differences between ./expected/out and
/<<PKGBUILDDIR>>/c/reg_test/output-regtest/out:
*** ./expected/out 2020-11-29 20:56:56.000000000 +0000
--- /<<PKGBUILDDIR>>/c/reg_test/output-regtest/out 2022-07-15
11:48:14.641689838 +0000
***************
*** 24879,24942 ****
================================================================
DSL LOCAL DATE/TIME FUNCTIONS
mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b)
a b c d
! 2017-02-18 23:00:00 1487469600.000000 2017-02-18 23:00:00 2017-02-18
! 2017-02-18 23:59:59 1487473199.000000 2017-02-18 23:59:59 2017-02-18
! 2017-02-19 00:00:00 1487473200.000000 2017-02-19 00:00:00 2017-02-19
! 2017-02-19 00:30:00 1487475000.000000 2017-02-19 00:30:00 2017-02-19
! 2017-02-19 01:00:00 1487476800.000000 2017-02-19 01:00:00 2017-02-19
! 2017-10-14 23:00:00 1508032800.000000 2017-10-14 23:00:00 2017-10-14
! 2017-10-14 23:59:59 1508036399.000000 2017-10-14 23:59:59 2017-10-14
! 2017-10-15 00:00:00 1508036400.000000 2017-10-15 01:00:00 2017-10-15
! 2017-10-15 00:30:00 1508038200.000000 2017-10-15 01:30:00 2017-10-15
! 2017-10-15 01:00:00 1508040000.000000 2017-10-15 02:00:00 2017-10-15
mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b)
a b c d
! 2017-02-14 00:00:00 1487041200.000000 2017-02-14 01:00:00 2017-02-14
! 2017-02-15 00:00:00 1487127600.000000 2017-02-15 01:00:00 2017-02-15
! 2017-02-16 00:00:00 1487214000.000000 2017-02-16 01:00:00 2017-02-16
! 2017-02-17 00:00:00 1487300400.000000 2017-02-17 01:00:00 2017-02-17
! 2017-02-18 00:00:00 1487386800.000000 2017-02-18 01:00:00 2017-02-18
! 2017-02-19 00:00:00 1487473200.000000 2017-02-19 00:00:00 2017-02-19
! 2017-02-20 00:00:00 1487559600.000000 2017-02-20 00:00:00 2017-02-20
! 2017-10-12 00:00:00 1507777200.000000 2017-10-12 00:00:00 2017-10-12
! 2017-10-13 00:00:00 1507863600.000000 2017-10-13 00:00:00 2017-10-13
! 2017-10-14 00:00:00 1507950000.000000 2017-10-14 00:00:00 2017-10-14
! 2017-10-15 00:00:00 1508036400.000000 2017-10-15 01:00:00 2017-10-15
! 2017-10-16 00:00:00 1508122800.000000 2017-10-16 01:00:00 2017-10-16
! 2017-10-17 00:00:00 1508209200.000000 2017-10-17 01:00:00 2017-10-17
! 2017-10-18 00:00:00 1508295600.000000 2017-10-18 01:00:00 2017-10-18
! 2017-10-19 00:00:00 1508382000.000000 2017-10-19 01:00:00 2017-10-19
mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S")
a b c
! 2017-02-18 23:00:00 1487469600.000000 2017-02-18 23:00:00
! 2017-02-18 23:59:59 1487473199.000000 2017-02-18 23:59:59
! 2017-02-19 00:00:00 1487473200.000000 2017-02-19 00:00:00
! 2017-02-19 00:30:00 1487475000.000000 2017-02-19 00:30:00
! 2017-02-19 01:00:00 1487476800.000000 2017-02-19 01:00:00
! 2017-10-14 23:00:00 1508032800.000000 2017-10-14 23:00:00
! 2017-10-14 23:59:59 1508036399.000000 2017-10-14 23:59:59
! 2017-10-15 00:00:00 1508036400.000000 2017-10-15 01:00:00
! 2017-10-15 00:30:00 1508038200.000000 2017-10-15 01:30:00
! 2017-10-15 01:00:00 1508040000.000000 2017-10-15 02:00:00
mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S")
a b c
! 2017-02-18 23:00:00 1487469600.000000 2017-02-18 23:00:00
! 2017-02-18 23:59:59 1487473199.000000 2017-02-18 23:59:59
! 2017-02-19 00:00:00 1487473200.000000 2017-02-19 00:00:00
! 2017-02-19 00:30:00 1487475000.000000 2017-02-19 00:30:00
! 2017-02-19 01:00:00 1487476800.000000 2017-02-19 01:00:00
! 2017-10-14 23:00:00 1508032800.000000 2017-10-14 23:00:00
! 2017-10-14 23:59:59 1508036399.000000 2017-10-14 23:59:59
! 2017-10-15 00:00:00 1508036400.000000 2017-10-15 01:00:00
! 2017-10-15 00:30:00 1508038200.000000 2017-10-15 01:30:00
! 2017-10-15 01:00:00 1508040000.000000 2017-10-15 02:00:00
================================================================
DSL SUB/GSUB/REGEX_EXTRACT
--- 24879,24942 ----
================================================================
DSL LOCAL DATE/TIME FUNCTIONS
mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b)
a b c d
! 2017-02-18 23:00:00 1487458800.000000 2017-02-18 23:00:00 2017-02-18
! 2017-02-18 23:59:59 1487462399.000000 2017-02-18 23:59:59 2017-02-18
! 2017-02-19 00:00:00 1487462400.000000 2017-02-19 00:00:00 2017-02-19
! 2017-02-19 00:30:00 1487464200.000000 2017-02-19 00:30:00 2017-02-19
! 2017-02-19 01:00:00 1487466000.000000 2017-02-19 01:00:00 2017-02-19
! 2017-10-14 23:00:00 1508022000.000000 2017-10-14 23:00:00 2017-10-14
! 2017-10-14 23:59:59 1508025599.000000 2017-10-14 23:59:59 2017-10-14
! 2017-10-15 00:00:00 1508025600.000000 2017-10-15 00:00:00 2017-10-15
! 2017-10-15 00:30:00 1508027400.000000 2017-10-15 00:30:00 2017-10-15
! 2017-10-15 01:00:00 1508029200.000000 2017-10-15 01:00:00 2017-10-15
mlr --opprint put $b=localtime2sec($a); $c=sec2localtime($b); $d=sec2localdate($b)
a b c d
! 2017-02-14 00:00:00 1487030400.000000 2017-02-14 00:00:00 2017-02-14
! 2017-02-15 00:00:00 1487116800.000000 2017-02-15 00:00:00 2017-02-15
! 2017-02-16 00:00:00 1487203200.000000 2017-02-16 00:00:00 2017-02-16
! 2017-02-17 00:00:00 1487289600.000000 2017-02-17 00:00:00 2017-02-17
! 2017-02-18 00:00:00 1487376000.000000 2017-02-18 00:00:00 2017-02-18
! 2017-02-19 00:00:00 1487462400.000000 2017-02-19 00:00:00 2017-02-19
! 2017-02-20 00:00:00 1487548800.000000 2017-02-20 00:00:00 2017-02-20
! 2017-10-12 00:00:00 1507766400.000000 2017-10-12 00:00:00 2017-10-12
! 2017-10-13 00:00:00 1507852800.000000 2017-10-13 00:00:00 2017-10-13
! 2017-10-14 00:00:00 1507939200.000000 2017-10-14 00:00:00 2017-10-14
! 2017-10-15 00:00:00 1508025600.000000 2017-10-15 00:00:00 2017-10-15
! 2017-10-16 00:00:00 1508112000.000000 2017-10-16 00:00:00 2017-10-16
! 2017-10-17 00:00:00 1508198400.000000 2017-10-17 00:00:00 2017-10-17
! 2017-10-18 00:00:00 1508284800.000000 2017-10-18 00:00:00 2017-10-18
! 2017-10-19 00:00:00 1508371200.000000 2017-10-19 00:00:00 2017-10-19
mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S")
a b c
! 2017-02-18 23:00:00 1487458800.000000 2017-02-18 23:00:00
! 2017-02-18 23:59:59 1487462399.000000 2017-02-18 23:59:59
! 2017-02-19 00:00:00 1487462400.000000 2017-02-19 00:00:00
! 2017-02-19 00:30:00 1487464200.000000 2017-02-19 00:30:00
! 2017-02-19 01:00:00 1487466000.000000 2017-02-19 01:00:00
! 2017-10-14 23:00:00 1508022000.000000 2017-10-14 23:00:00
! 2017-10-14 23:59:59 1508025599.000000 2017-10-14 23:59:59
! 2017-10-15 00:00:00 1508025600.000000 2017-10-15 00:00:00
! 2017-10-15 00:30:00 1508027400.000000 2017-10-15 00:30:00
! 2017-10-15 01:00:00 1508029200.000000 2017-10-15 01:00:00
mlr --opprint put $b=strptime_local($a, "%Y-%m-%d %H:%M:%S"); $c=strftime_local($b, "%Y-%m-%d %H:%M:%S")
a b c
! 2017-02-18 23:00:00 1487458800.000000 2017-02-18 23:00:00
! 2017-02-18 23:59:59 1487462399.000000 2017-02-18 23:59:59
! 2017-02-19 00:00:00 1487462400.000000 2017-02-19 00:00:00
! 2017-02-19 00:30:00 1487464200.000000 2017-02-19 00:30:00
! 2017-02-19 01:00:00 1487466000.000000 2017-02-19 01:00:00
! 2017-10-14 23:00:00 1508022000.000000 2017-10-14 23:00:00
! 2017-10-14 23:59:59 1508025599.000000 2017-10-14 23:59:59
! 2017-10-15 00:00:00 1508025600.000000 2017-10-15 00:00:00
! 2017-10-15 00:30:00 1508027400.000000 2017-10-15 00:30:00
! 2017-10-15 01:00:00 1508029200.000000 2017-10-15 01:00:00
================================================================
DSL SUB/GSUB/REGEX_EXTRACT
Differences were found between ./expected/out and
/<<PKGBUILDDIR>>/c/reg_test/output-regtest/out !
Tests completed: 2939
FAIL run (exit status: 1)
[...]
make[3]: *** [Makefile:559: check-recursive] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/c/reg_test'
make[2]: *** [Makefile:567: check-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/c'
make[1]: *** [Makefile:409: check-recursive] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_test: error: make -j2 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:6: binary-arch] Error 25
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
--------------------------------------------------------------------------------
(The above is just how the build ends and not necessarily the most relevant
part)
Note: I'm using the "patch" tag because there is an obvious fix
(indicated in the subject).
About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
Source: miller
Source-Version: 6.6.0-2
Done: Stephen Kitt <[email protected]>
We believe that the bug you reported is fixed in the latest version of
miller, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stephen Kitt <[email protected]> (supplier of updated miller package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 07 Jan 2023 10:41:52 +0100
Source: miller
Architecture: source
Version: 6.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt <[email protected]>
Changed-By: Stephen Kitt <[email protected]>
Closes: 1027377
Changes:
miller (6.6.0-2) unstable; urgency=medium
.
* Build-depend on tzdata, which is needed for timezone-based tests.
Closes: #1027377.
Checksums-Sha1:
88caef08913646ed56ff80e0b485b4ffd14eb85c 2174 miller_6.6.0-2.dsc
39fa46448675ef1fc3ae2a3b5c6668bad7e514f0 4528 miller_6.6.0-2.debian.tar.xz
3997b55cb9513af71517e880c59fb4bc4d5478fe 6793 miller_6.6.0-2_source.buildinfo
Checksums-Sha256:
71f38d6817cdc22c6308c12da382e7fba0d1fe1f66a83b8c8a3bc71c1a98079e 2174
miller_6.6.0-2.dsc
be154eca4bc664e8668369598742f2ef50d85225f0ed24dcc636f2726f99b8de 4528
miller_6.6.0-2.debian.tar.xz
31a2894f20de49b7c07591315ece9ea1f649a0a4f8738da06090d0e94bef990d 6793
miller_6.6.0-2_source.buildinfo
Files:
d8c0073c588bf906318e292bf91a71c2 2174 utils optional miller_6.6.0-2.dsc
539b69aacaccb221ffe803ea3f0bcdb2 4528 utils optional
miller_6.6.0-2.debian.tar.xz
260055db3f2d4f4027f48f3d7489ae8d 6793 utils optional
miller_6.6.0-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmO5QYgACgkQgNMC9Yht
g5ynMBAAj6QvbLYRCJhk6yeTsUcCuDQwkpe7VKVqEXgAjB5nvkE43g4XPZ661Nvr
GMTMKCtQH3b8ZnCbo+LHU+0/XecxiUuyuEuXjfF5M8HjrJe2BGuy5Xe1qB0lQoRX
N3+ZxevnHxOUb0VQbO/Rm1Ht1HayHjhg5IwbjxcrWRI8Brx44mpzhLrh0VSMd9UX
+zz7AbU1GLrV+IMtp7oPw8oAGpXromAQkepkRpOu2kvhaHjHAPBTqd2XY1mfXVFj
GmuEbQhMss7mCFtxfu7fuUzmHOkvSLpAOAIqZEdTHuIh7kkqlO7GA2si+Pl4Ni75
6OtL8csGmrRtobI5U3G1NDG6OYoUP0T3Nt8Ljzvgw9/oXD4ki6BIlWyBzF5b+CwY
W0NLNZC1w6ez7R7hb1eBTF4RSkLbmujLOJQjwlXVnEoZjvCN5K1M0tYoyTsf7O68
usXLBRV4LAuinAQEWT+/a9WoITxmoLLhO4OLZzMdVK6Z5Meqck8P/1OYGTqKv/xj
1sppDhmaSZArsWQDJavfOyqT1p8schrsIUzZJSJ5HzGdwEGIp63xtyeUhscRgolI
hmIZDBmxddnCxee4beTsCTDQqaF69Hw7BDNO2YwAd59c5Sxu8qz2JWOV8We3Uh7m
gdkQf4RSlSwRWdLLnK9i3orrJpbT48b2FTKF6X3iao+htYPN0ro=
=qgzc
-----END PGP SIGNATURE-----
--- End Message ---
