Status of the src:lsb package (was: Debian LSB compliance)

2015-09-17 Thread Didier 'OdyX' Raboud
Hi all, It is time for an update about the lsb source package status, especially as a quite important change landed in testing. After the discussion [0] about these changes back in July (on both debian-lsb@ and debian-devel@), I have uploaded src:lsb 9.20150826 to unstable, building no LSB

Re: Status of the src:lsb package (was: Debian LSB compliance)

2015-09-17 Thread Marco d'Itri
On Sep 17, Didier 'OdyX' Raboud wrote: > This change landed in stretch on September 14. and is de facto the > "outright giving up" of LSB support for Debian, from stretch onwards. As Is there any point in (formally?) maintaining LSB compatibility? Is there any proprietary

Re: Debian LSB compliance

2015-07-08 Thread Didier 'OdyX' Raboud
Le vendredi, 3 juillet 2015, 13.20:08 Mats Wichmann a écrit : On 07/03/15 07:28, Didier 'OdyX' Raboud wrote: The crux of the issue is, I think, whether this whole game is worth the work: I am yet to hear about software distribution happening through LSB packages [4]. There are only _8_

Re: Debian LSB compliance

2015-07-08 Thread Moritz Mühlenhoff
Didier 'OdyX' Raboud o...@debian.org wrote: Given a) the work that certifying Debian would take; b) the interest in having Debian be certified (I am yet to see any of that interest); c) the marginal interest by application vendors for the LSB; I'm leaning towards outright giving up.

Debian LSB compliance (was: Re: Standard-producing bodies and Debian)

2015-07-03 Thread Didier 'OdyX' Raboud
Hi Gunnar, just jumping on one specific point, sorry to hijack the thread… (Reply-To set to debian-lsb, please followup there…) tl;dr: proposal to shrink src:lsb to only produce lsb-base and lsb- release Le jeudi, 2 juillet 2015, 09.15:12 Gunnar Wolf a écrit : But then I realized I was lying.

Re: Debian LSB compliance

2015-07-03 Thread Mats Wichmann
On 07/03/15 07:28, Didier 'OdyX' Raboud wrote: We're also not checking this because the LSB compatibility of Debian releases has never been a topic and I don't see anyone asking a library maintainer to stay at an older version and/or maintain a patch series to keep this compatibility [2]. By