Re: transition plan from libcap to libcap2

Hi Adeodato, On Thu, Apr 2, 2009 at 9:35 AM, Adeodato Simó wrote: >> - vsftpd needs a binNMU scheduled on armel > > I have no idea why +b1 got rebuilt against libcap1, because libcap2 > clearly got installed in the chroot. Anyway, built +b2 now successfully. > >> - pulseaudio FTBFS on hppa and a

Re: transition plan from libcap to libcap2

* Torsten Werner [Wed, 01 Apr 2009 23:02:12 +0200]: > Hi Adeodato, Hi, > there are still some issues regarding the libcap2 transition in unstable: > - zorp needs binNMUs scheduled on all arches except armel because it > has been built with an old version of libzorp* Good catch, done. > - vsft

Re: transition plan from libcap to libcap2

Hi, On Wed Apr 01, 2009 at 23:02:12 +0200, Torsten Werner wrote: > - quagga fails to build on sparc that looks like a buildd failure > (sp...@buildd on Cc): > https://buildd.debian.org/fetch.cgi?pkg=quagga&arch=sparc&ver=0.99.11-1%2Bb1&stamp=1238271735&file=log&as=raw i thought i gave all packag

Re: transition plan from libcap to libcap2

Hi Adeodato, there are still some issues regarding the libcap2 transition in unstable: - zorp needs binNMUs scheduled on all arches except armel because it has been built with an old version of libzorp* - vsftpd needs a binNMU scheduled on armel - quagga fails to build on sparc that looks like

Re: transition plan from libcap to libcap2

* Torsten Werner [Mon, 23 Mar 2009 22:36:37 +0100]: > On Fri, Mar 20, 2009 at 9:30 PM, Adeodato Simó wrote: > > Thoughts? At any rate, whenever a libcap-dev 2.16-3 or higher hits > > unstable, please let us know and we’ll schedule the required Bin-NMUs. > I have uploaded a new version of libcap2

Re: transition plan from libcap to libcap2

On Fri, Mar 20, 2009 at 9:30 PM, Adeodato Simó wrote: > Thoughts? At any rate, whenever a libcap-dev 2.16-3 or higher hits > unstable, please let us know and we’ll schedule the required Bin-NMUs. I have uploaded a new version of libcap2. Please binNMU: libzorpll 3.0.6.4.2+nmu1 muddleftpd 1.3.13.

Re: transition plan from libcap to libcap2

Hi Adeodato, On Fri, Mar 20, 2009 at 9:30 PM, Adeodato Simó wrote: > I would recommend in that case that the libcap2-dev package gets > completely dropped (and not even kept as eg. a transitional package), > provided that you make the new libcap-dev Provide: libcap2-dev, in order > not to cause u

Re: transition plan from libcap to libcap2

* Torsten Werner [Mon, 23 Feb 2009 22:18:48 +0100]: > Hi, Hello, Torsten, and sorry for the awfully late reply. Since this wasn’t an imminent transition, I’m afraid it starved a bit. > libcap is no longer maintained upstream and has been replaced by > libcap2 which is supposed to be API compatib

transition plan from libcap to libcap2

Hi, libcap is no longer maintained upstream and has been replaced by libcap2 which is supposed to be API compatible. There are some packages left that Build-Depend on libcap: . My plan is to add a transitional binar