Hi Andreas,
On 2015-03-14 01:56, Andreas Beckmann wrote:
> On 2015-03-13 23:49, Christian Kastner wrote:
Would you by chance be available for sponsoring? (No problem if not, but
if yes, please wait for an updated debdiff as the RT approved another
one-line fix.)
>
> I'm not sure th
On 2015-03-14 02:42, Christian Kastner wrote:
> Oh, I forgot to mention this. I too was concerned about this so I tested
> this with a jessie VM, and it worked fine.
Good. Uploaded. Removing piuparts workaround ... :-)
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.or
On 2015-03-14 01:56, Andreas Beckmann wrote:
> On 2015-03-13 23:49, Christian Kastner wrote:
Would you by chance be available for sponsoring? (No problem if not, but
if yes, please wait for an updated debdiff as the RT approved another
one-line fix.)
>
> I'm not sure that this is th
On 2015-03-13 23:49, Christian Kastner wrote:
>>> Would you by chance be available for sponsoring? (No problem if not, but
>>> if yes, please wait for an updated debdiff as the RT approved another
>>> one-line fix.)
I'm not sure that this is the correct approach for capability.conf -
it's not an o
On 2015-03-13 23:38, Andreas Beckmann wrote:
>> Would you by chance be available for sponsoring? (No problem if not, but
>> if yes, please wait for an updated debdiff as the RT approved another
>> one-line fix.)
>
> No problem, I can sponsor. Throw it onto mentors.d.net once ready and
> send me t
On 2015-03-13 23:34, Christian Kastner wrote:
> In #780432 [1] a fix using Breaks+Replaces was already approved. To
> maybe avoid another iteration, would you be satisfied with this?
That's fine.
> Would you by chance be available for sponsoring? (No problem if not, but
> if yes, please wait for
On 2015-03-13 23:22, Andreas Beckmann wrote:
> libcap2-bin had Conflicts: libcap-bin upto wheezy, this (and a
> corresponding Replaces) should return for jessie, it can go away
> afterwards, since the default (straight forward) upgrade paths should be
> covered.
Oh, I didn't notice that earlier Co
On 2015-03-13 21:34, Christian Kastner wrote:
> It's odd that this issue hasn't been reported before. I assume your test
> used a somewhat minimal system where libcap2-bin only gets pulled in via
Correct, I started with a minimal lenny and installed libcap-bin there.
Neither libcap-bin nor libcap
Processing control commands:
> tag -1 + confirmed pending
Bug #780411 [libcap2-bin] libcap2-bin: missing Breaks+Replaces: libcap-bin
Added tag(s) confirmed and pending.
--
780411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780411
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Control: tag -1 + confirmed pending
On 2015-03-13 16:33, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'lenny' to 'squeeze' to 'wheezy' to 'jessie'.
> Its predecessor 'libcap-bin' installed fine in 'lenny', and was kept
> installed during the
Package: libcap2-bin
Version: 1:2.24-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libcap-bin
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'lenny' to 'squeeze' to 'wheezy' to 'jessie'.
Its predecessor 'libcap-bin' ins
11 matches
Mail list logo
