On 2019-03-27 00:48, wf...@niif.hu wrote:
> Yes, I'm on it. It's somewhat bizarre: libcrmcluster1-dev wasn't part
> of jessie or stretch. Similarly, pacemaker-dev was present in wheezy
> only, until I reintroduced it recently, and looks like its ghost came
> back to haunt us. I didn't anticipate
Valentin Vidic writes:
> On Mon, Mar 25, 2019 at 03:45:58PM +0100, Andreas Beckmann wrote:
>
>> In that case you should probably add Breaks+Replaces against all of the
>> old -dev packages that were merged, just to be on the safe side.
>
> Yes, that is the plan. I think wferi will take care of it
On Mon, Mar 25, 2019 at 03:45:58PM +0100, Andreas Beckmann wrote:
> In that case you should probably add Breaks+Replaces against all of the
> old -dev packages that were merged, just to be on the safe side.
Yes, that is the plan. I think wferi will take care of it if he
has time?
--
Valentin
On 2019-03-25 14:09, Valentin Vidic wrote:
> Yep, all -dev packages were merged at one point into pacemaker-dev.
> Breaks+Replaces on old packages should do the trick here.
In that case you should probably add Breaks+Replaces against all of the
old -dev packages that were merged, just to be on the
On Sat, Mar 23, 2019 at 05:19:59PM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'wheezy' to 'jessie' to 'stretch' to 'buster'.
> It installed fine in 'wheezy', and upgraded to 'jessie' and 'stretch'
> successfully,
> but then the upgrad
Package: pacemaker-dev
Version: 2.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'wheezy' to 'jessie' to 'stretch' to 'buster'.
It installed fine in 'wheezy', and upgraded to 'jessie' and 'st
6 matches
Mail list logo
