Debian Patches
Status for adjtimex/1.29-12
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 01-makefile.in-ldflags.diff | add extra flags to Makefile.in to allow GCC hardening and modify the original upstream CFLAGS to accept flags from DH9. |
Joao Eriberto Mota Filho <eriberto@debian.org> | no | 2014-11-18 | ||
| 02-fix-manpage | fix some hyphen used as minus sign in manpage. | Joao Eriberto Mota Filho <eriberto@debian.org> | no | 2014-11-24 | ||
| 03-adjtimex-Blocks-the-access-to-the-hardware-cmos-clock.patch | adjtimex: Blocks the access to the hardware (cmos) clock Dear Maintainer, while "adjtimex" runs, the command "hwclock --show" does not work. The command keeps the device "/dev/rtc" open the whole time. It does not need to be open while the command sleeps, which is most of the time it is running. Necessary changes: a) Open the device inside the while loop (not in front of it) b) Close it before the program goes to sleep before the end of the while loop Other changes a) Fixed some code to eliminate warnings from the compiler b) Some cosmetic changes. [rogershimizu@gmail.com: slightly modified] |
Bjarni Ingi Gislason <bjarniig@rhi.hi.is> | no | 2013-09-29 | ||
| 04-fix-protential-uninitialized-memory-accessing.patch | adjtimex does not check the return value of stat() adjtimex does not check the return value of stat() and uses possibly uninitialized memory. |
peppe <g1pi@libero.it> | no | 2012-09-27 | ||
| 05-avoid-gcc-warnings.patch | avoid a few gcc warnings | Roger Shimizu <rogershimizu@gmail.com> | no | 2015-12-17 | ||
| 06-improve-precision.patch | Improve precision Thanks Christopher Alexander Tobias Schulze. |
Roger Shimizu <rogershimizu@gmail.com> | no | 2016-06-28 | ||
| 07-update-manpage-adjtimex.8.patch | update manpage adjtimex.8 - Add a few new timex status from kernel parameter, which was appended by commit: https://github.com/torvalds/linux/commit/eea83d896e318bda54be2d2770d2c5d6668d11db Thanks to Chris Hiestand <chiestand@salk.edu>. - Update the example to explain --frequency calculation. Thanks to Marco Marongiu <brontolinux@gmail.com>. |
Roger Shimizu <rogershimizu@gmail.com> | no | 2016-10-25 | ||
| 08-FTCBFS-uses-the-build-architecture-compiler.patch | FTCBFS: uses the build architecture compiler adjtimex fails to cross build from source, because its Makefile fails to use the compiler discovered by ./configure. Instead it uses the make default "cc". After adding the CC=@CC@ substitution to Makefile.in, adjtimex cross build successfully. Please consider applying the attached patch. |
Helmut Grohne <helmut@subdivi.de> | no | 2017-11-24 | ||
| 09-adjtimex.8-Some-fixes-to-the-manual.patch | adjtimex.8: Some fixes to the manual adjtimex.8 |
Bjarni Ingi Gislason <bjarniig@rhi.hi.is> | no | 2018-06-24 | ||
| 10-STA_NANO-confuses-adjtimex-8.patch | STA_NANO confuses adjtimex(8) Observe that the "raw time" line shows in its two-part form a time over 23 million microseconds, i.e., over 23 seconds, into the present second. Also, in its one-part form it shows a value that seems to treat these microseconds as each being 1e-8 seconds long. These displays are inconsistent with each other, and inconsistent with the meaning of microseconds. What's really going on is that the STA_NANO flag is set (8192 in the status), so the tv_usec field of the struct timeval doesn't actually represent microseconds. It represents *nanoseconds*. The true raw time is different from both of the values shown, and for the call made above should have been shown as raw time: 1490397277s 23837440ns = 1490397277.023837440 |
Zefram <zefram@fysh.org> | no | 2017-04-18 | ||
| 11-Fix-ntpdate-command.patch | Fix ntpdate command Add option "-p4" to ntpdate command due to: * http://bugs.debian.org/987625 |
Roger Shimizu <rosh@debian.org> | no | 2021-04-26 | ||
| 12-makefile.in-bindir.patch | =================================================================== | no |
Showing 1 to 12 of 12 entries