Re: The future of src:ntp
- To: Debian Development <debian-devel@lists.debian.org>
- Subject: Re: The future of src:ntp
- From: Richard Laager <rlaager@debian.org>
- Date: Tue, 22 Mar 2022 16:04:32 -0500
- Message-id: <[🔎] f611a664-b20b-8c7c-adfe-3f88e9b46457@debian.org>
- In-reply-to: <32b8145a-cad1-e3f5-29ac-ed1c72a94658@debian.org>
- References: <454d0e14-7448-5cef-ad68-cbdff7467edd@debian.org> <bbf31462-c651-54f3-e0ef-320f4ece889c@debian.org> <4ba63521-526c-a523-b69c-ad94abf0fa8e@debian.org> <ad154fa9-84b3-fdcb-fa9b-ecf1d7a95fdc@debian.org> <32b8145a-cad1-e3f5-29ac-ed1c72a94658@debian.org>
If you use ntp, I would appreciate if you could test the transition to
ntpsec. ntpsec 1.2.1+dfsg1-5 has been uploaded to experimental and
cleared the NEW queue.
Bernhard Schmidt suggested and I used
1:4.2.8p15+dfsg-2~$(DEB_VERSION_UPSTREAM_REVISION) as the version for
the transitional packages. The first part (before the ~) is the current
src:ntp version, but with the Debian revision bumped from 1 to 2. This
allows for potential security or stable fix uploads to existing Debian
releases, if needed.
Barring bugs, I believe the next steps are:
1. Upload to unstable.
2. Request ftpmaster removal of src:ntp?
--
Richard
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
Reply to: