-
Robert Luberda authored
datefudge (1.22) unstable; urgency=medium * datefudge.c: Apply the following fixes from Thorsten Glaser (closes: #853724): + Operate more efficiently, especially if fudging to the epoch. + Fix running on 32-bit systems with 64-bit time_t (such as x32). * datefudge.man: Document that datefudge might be affected by the Y2K38 problem on some systems. * Use https in Vcs-Git and switch Vcs-Browser to cgit. * Standards-Version: 3.9.6 (no changes). datefudge (1.21) unstable; urgency=medium * datefudge.sh: don't fail when its date argument happens to be equal to the current time (i.e. make `datefudge now some_command' work). * Enable all hardening options in debian/rules. * Update man page to mention that the date can be given in any format accepted by date(1) command. * Switch debian/copyright to the DEP-5 format. * Use https in Vcs-Browser field (lintian). * Standards-Version: 3.9.6 (no changes). datefudge (1.20) unstable; urgency=medium * datefudge.c: don't override time(2) on GNU/Hurd, as it seems to internally call gettimeofday(2), which is overridden. This fixes FTBFS on that platform. datefudge (1.19) unstable; urgency=medium * Use `*-*' as multi-arch pattern to make sure the datefudge script is the same on all architectures, including 'hurd-i386' (closes: #730766). * Install datefudge.so into /usr/lib<arch>/datefudge instead of using an extra private dir /usr/lib/datefudge/<arch> (closes: #711892). * Cleanup makefiles a bit and add support for cross-compiling. * Standards-Version: 3.9.5 (no changes). datefudge (1.18) unstable; urgency=low * Introduce multi-arch support which allows one to use datefudge with 32-bit commands on 64-bit system (providing that both 32-bit and 64-bit versions of this package are installed on system) (LP: #1103281): + install datefudge.so library into /usr/lib/datefudge/<arch-tripplet>; + add each /u/l/d/<arch-tripplet> to LD_LIBRARY_PATH in datefudge scipt; + mark binary package as `Multi-Arch: same'. * Use debhelper v9. * debian/control: + fix Vcs-Browser field; + Standards-Version: 3.9.4 (no changes). datefudge (1.17) unstable; urgency=low * datefudge.{c,man}: Add the `--static' option for static dates. * debian/control: + Standards-Version: 3.9.2 (no changes); + add VCS fields. datefudge (1.16) unstable; urgency=low * datefudge.c: don't override clock_gettime(2) on GNU/Hurd - it seems it internally calls gettimeofday(2), which is overridden. This fixes FTBFS due to test failure on that platform. * Makefile: add test for `perl localtime()'. datefudge (1.15) unstable; urgency=low * Use the `3.0 (native)' source format. * Switch to debhelper v8. * Standards-Version: 3.9.1 (no changes). * debian/rules: + provide build-arch and build-indep targets; + call dpkg-buildflags to set CFLAGS and LDFLAGS; + simplify the file. * Reword the restriction in README (closes: #416174). * Update debian/copyright a bit. * Makefile: add a simple test case. datefudge (1.14) unstable; urgency=low * New maintainer (closes: #429467). * Standards-Version: 3.7.3 (no changes). * Use debhelper v7 and its minimised rules file. * datefudge.c: override clock_gettime(2) called with CLOCK_REALTIME argument to make it possible to fake `date' command (closes: #416175). * Update man page, add a simple example. datefudge (1.13) unstable; urgency=low * QA upload. * Package is orphaned (#429467); set maintainer to Debian QA Group. * Switch to debhelper. * Move datefudge.so to /usr/lib/datefudge as it's not a public library. * datefudge.c: Drop <asm/unistd.h> for portability. Closes: #414335. * Makefile: Remove datefudge.1 on clean. * debian/copyright: Update FSF address. * Conforms to Standards version 3.7.2. datefudge (1.12) unstable; urgency=low * Updated maintainer email. * Use a Lintian override to not-warn about the shared library (which is not linked against, and therefore doesn't require a shlibs entry) * Extended the package description * added COPYING file to source tarball * Updated Standards-Version to 3.6.1 (no changes) * Minor build fixes datefudge (1.11) unstable; urgency=low * de-debhelperization problems, part 2: removed debian/files use debian/shlibs => debian/tmp/DEBIAN/shlibs instead of incorrectly writing the latter from debian/rules datefudge (1.10) unstable; urgency=low * Fix debian complaints, part 1 datefudge (1.9) unstable; urgency=low * Debhelper removal and cleanup, step 2 datefudge (1.8) unstable; urgency=low * Ignore editor files datefudge (1.7) unstable; urgency=low * Debhelper removal and cleanup, step 1 datefudge (1.6) unstable; urgency=low * debianized * GPLized datefudge (1.5) unstable; urgency=low * Added README datefudge (1.4) unstable; urgency=low * check-in datefudge script datefudge (1.3) unstable; urgency=low * initial check-in datefudge (1.2) unstable; urgency=low * Versionsnummern-Updateskript datefudge (1.1) unstable; urgency=low * Initial repository create datefudge (1.0) unstable; urgency=low * BitKeeper file /var/tmp/b.s.10098/ChangeSet
ccfb1a69