On Sat, Mar 14, 2020 at 10:16:30PM +0100, Anton Gladky wrote: > * May I set the version number for this update as > 2.20160316.1+really3.20181128.1~deb8u1? After the next Stretch point > release I can reupload it with the version number 3.20181128.1~deb8u1. > Or there are better alternatives?
from #debian-release, slightly edited for better readability:
<h01ger> is there an ETA/idea for 10.4 and 9.13 dates already?
<h01ger> asking because CVE-2017-5715 could be fixed in jessie now,
just the most reasonable version number would be higher what
stretch has atm, as the security team wants to fix the issue
at a pointrelease.
<h01ger> (so also asking whether it makes more sense to delay the upload
for jessie or just live with the fact that version numbers are
temporarily out of proper ordering)
<h01ger>
https://lists.debian.org/<e348ef55-5aff-fc62-64e0-eddfdd293...@debian.org>
for full context
<elbrus> h01ger: no ETA/idea yet
<ivodd> h01ger: version constraint violations in *-security happened before,
if you want to upload to jessie, just do it
<ivodd> the versions will be ok once the new version goes into stretch
<ivodd> you can also upload to stretch-pu, so people can get it there
if they want to (once it's approved by SRMs)
* | h01ger nods and thanks. may i quote you, elbrus and ivodd and me in a
reply to that mail?
<elbrus> yes
<ivodd> sure :)
--
cheers,
Holger
-------------------------------------------------------------------------------
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
There are no jobs on a dead planet.
signature.asc
Description: PGP signature
