Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Hello Eugene, Eugene V. Lyubimkin wrote on 2012-11-14 19:08: > Just like Timo said, this patch doesn't fix this (RC) problem. Fix would > be: either apply the same idea (#if 0) to sys_linux.c or backport the > upstream patch [1]. I have thought the problem in sys_linux.c were already solved. I will look for a good solution in the next days. Thank you for the link of upstream patch. --- Have a nice day. Joachim (Germany) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121115213059.47096...@jupiter.home
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Hi Joachim, On 2012-11-10 22:10, Joachim Wiedorn wrote: > chrony (1.24-3.2) testing-proposed-updates; urgency=medium > > * Non-maintainer upload. > * Fix: Remove obsolete test of kernel version (rtc_linux.c) to run for >kernel versions 3.0 and higher. Nowadays all kernel versions have >RTC support (solves #642209 for version 1.24). Closes: #642209 > > -- Joachim Wiedorn Sat, 10 Nov 2012 19:19:19 +0100 Thank you for caring for RC bugs. Just like Timo said, this patch doesn't fix this (RC) problem. Fix would be: either apply the same idea (#if 0) to sys_linux.c or backport the upstream patch [1]. Please prepare the new upload with tested fix, new version string and proper Closes, and someone will surely upload it. [1] http://git.tuxfamily.org/chrony/chrony.git/?p=chrony/chrony.git;a=blobdiff;f=sys_linux.c;h=24f027c3b58663d290a59c36f09c31ba9e8c0c1f;hp=441e6e42c63868f621975c4c6ebf6f7e58c768fa;hb=ec7d302a6ca9e7974a05d338267b40491a1d7abb;hpb=8cc7ebffa91152d94b86247106e3fafe49600fc9 -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux userspace developer, Debian Developer -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121114170827.GA22915@r500-debian
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Le 10/11/2012 17:10, Joachim Wiedorn a écrit : >RTC support (solves #642209 for version 1.24). Closes: #642209 It should be “Closes: #691340”. Regards David signature.asc Description: OpenPGP digital signature
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Le 11/11/2012 09:00, Joachim Wiedorn a écrit : > David Prévot wrote on 2012-11-10 17:40: > >> Please use 1.24-3.1+deb7u1 as a version number (and eventually directly >> “wheezy” instead of “testing-proposed-updates”). > That's confusing me. Let me try a third time then… > What is that for a strange version numbering system? The purpose is to indicate that the upload was targeted to Wheezy (deb7), and it's the first one (u1), see #685646 for the rationales, or the debian-release list archives. > Which time is the right time to contact the release team? Now, with a debdiff, see Rule #5 http://release.debian.org/wheezy/freeze_policy.html > Now I see two ways: > > a) uploading (with sponsor) to testing-proposed-updates; then ask release >team (as bug report) for unblocking. Not an option. > b) ask release team; then upload (with sponsor) to testing-proposed- >updates or direct to wheezy. Optionally the release team do unblocking. Using « wheezy » in the changelog will lend in testing-proposed-updates, don't worry about that, just ask the release-team to ACK your bug fix, they may even sponsor directly your upload (if they don't have time, someone else will be happy to do it promptly, me included). Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQn7AyAAoJELgqIXr9/gnygFAQAJgPr+FyzTDU/o6vn6tGoJ5T +zTVV6THG7tPm6KPXp8K5izjUPgxLILUL2W2y9SRY7GSeWdVNthkNXAXWN9KwZMv kcTi0sNEB82eqe2CguYrmNZ6BLfVCci12JnG4r9bY4jKKxgzjMXdGrDqqkJytfZI FhwtXwA+VmERIrr8J+3CMOGKVuSPx72xcoDMaBYMC7dkjnhDmzufY/gxg7ItFasc DgxjMydTWy/ogSKOXZYT5WSg86zJ7OEuQDaMutds2uO5p1Rdutavd/x/1n4MRZCZ a9XcC+KkqvCVaWpIJ4w6GrzZOWzb7N4aTv3bn6s4NRh9uJEZbAfZmcd6//xAhIwc gUdxvUZwYifGhsVk75iatEhu7fGZeXQ/xeyrJM7HIY6D7nakbepcQhr0wc83Y80t yYeB65Ri9b4haJSe0yfn8qpkhFvOy8IcSBWRboKvP4eJLwjJIufX9w5BN4w8/iQ+ p7xK/F67r84sWuwMlwT0B6JhRfgPyzSny6cLwUeC6Ag7oUtpMnMeQ6o84D90WeU+ ioy0pHQ2LS0Ogby5+exub/+xtFLHY9sqBBF4oTx13zUcpgyDd0n2JjGbrP8CZt6g NEtWcCtgUHjxw2QhC8O9LWe/9RfYrbzsfK7kyfG9RzcWGIUZD0cFJQiZwtCmgVwe Pu1ltz/LqjLhF3n2ix6+ =w/jm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/509fb033.9000...@debian.org
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Hello David, David Prévot wrote on 2012-11-10 17:40: > Please use 1.24-3.1+deb7u1 as a version number (and eventually directly > “wheezy” instead of “testing-proposed-updates”). Since packages meant to > testing-proposed-updates should be acknowledged by the release team > prior to the upload, please do contact first the release-team > (preferably via a bug report against release.debian.org) with a debdiff > against the version in Wheezy. That's confusing me. What is that for a strange version numbering system? And what way is now the right? I am only DM. So I can only upload to mentors.d.n and need a sponsor for uploading. Which time is the right time to contact the release team? I hope there is only one right way? Now I see two ways: a) uploading (with sponsor) to testing-proposed-updates; then ask release team (as bug report) for unblocking. b) ask release team; then upload (with sponsor) to testing-proposed- updates or direct to wheezy. Optionally the release team do unblocking. What should I do now? --- Have a nice day. Joachim (Germany) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2012140008.6e899...@jupiter.home
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Le 10/11/2012 17:10, Joachim Wiedorn a écrit : > chrony (1.24-3.2) testing-proposed-updates; urgency=medium Please use 1.24-3.1+deb7u1 as a version number (and eventually directly “wheezy” instead of “testing-proposed-updates”). Since packages meant to testing-proposed-updates should be acknowledged by the release team prior to the upload, please do contact first the release-team (preferably via a bug report against release.debian.org) with a debdiff against the version in Wheezy. Regards David signature.asc Description: OpenPGP digital signature
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "chrony" (NMU). * Package name: chrony Version : 1.24-3.2 Upstream Author : Richard Curnow * URL : http://chrony.tuxfamily.org/ * License : GPL-2 Section : admin It builds those binary packages: chrony - Sets your computer's clock from time servers on the Net To access further information about this package, please visit the following URL: http://mentors.debian.net/package/chrony Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/chrony/chrony_1.24-3.2.dsc Changes since the last upload: chrony (1.24-3.2) testing-proposed-updates; urgency=medium * Non-maintainer upload. * Fix: Remove obsolete test of kernel version (rtc_linux.c) to run for kernel versions 3.0 and higher. Nowadays all kernel versions have RTC support (solves #642209 for version 1.24). Closes: #642209 -- Joachim Wiedorn Sat, 10 Nov 2012 19:19:19 +0100 Regards, Joachim Wiedorn -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121110221039.649aa...@jupiter.home