❦ 7 décembre 2016 11:27 +0100, Guilhem Moulin <[email protected]> :
>>> Unfortunately 1.2.x has many dependencies that aren't in
>>> jessie-backports yet. I personally don't have the time nor energy to
>>> maintain said dependencies, so we asked backports folks for an exception
>>> to stick to 1.1.x for the bpo version, exception which was rejected.
>>> I'm afraid the remaining alternative is to take remove the package from
>>> jessie-backports :-(
>>
>> Since the problem is quite serious, could you push the fix in bpo8+2
>> nonetheless? Then wait a bit before asking for removal from backports to
>> let actual users get an updated version. It seems far better than just
>> leaving some people with vulnerable versions on their systems.
>
> Just tagged and pushed ‘debian/1.1.5+dfsg.1-1_bpo8+2’. Note that I
> moved jessie-backports's HEAD to its parent first as is was on
> debian/1.1.6+dfsg.1-1_bpo8+1 which didn't make it to bpo. Running
>
> git branch jessie-backports debian/1.1.5+dfsg.1-1_bpo8+1
>
> before pull should fix this. Sorry for the inconvenience.
Is the tag for debian/1.1.5+dfsg.1-1_bpo8+1? The diff for it is pretty
big.
--
Follow each decision as closely as possible with its associated action.
- The Elements of Programming Style (Kernighan & Plauger)
signature.asc
Description: PGP signature
