Re: ifupdown2: debconf followup

2016-08-01 Thread Guus Sliepen
On Sun, Jul 31, 2016 at 06:58:20PM -0700, Roopa Prabhu wrote: > And, we will be very happy to work towards making ifupdown2 > the default in Debian. If there are ways to make that happen, please let us > know. First, try to make it compatible with 99% of the non-trivial ifupdown configurations.

sybase license and openWatcom DFSGness

2016-08-01 Thread Gianfranco Costamagna
Hi, this is a question mainly for ftpmasters, but I think some public discussion here might be beneficial for me :) Basically, we thought OpenWatcom license wasn't DFSG for Debain standards, and now since I would like to put Virtualbox back in main, I'm trying to see if some statement clarifying

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Paul Wise
On Mon, Aug 1, 2016 at 5:44 PM, Gianfranco Costamagna wrote: > Hi, this is a question mainly for ftpmasters, but I think some public > discussion here > might be beneficial for me :) I didn't see a question in your mail :) > Basically, we thought OpenWatcom license wasn't DFSG for Debain standa

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Ben Finney
Gianfranco Costamagna writes: > Hi, this is a question mainly for ftpmasters, but I think some public > discussion here might be beneficial for me :) IMO this is what the ‘debian-legal’ discussion group is for: to save the many people who read ‘debian-devel’ but don't want intricate discussions

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Guus Sliepen
On Mon, Aug 01, 2016 at 09:44:33AM +, Gianfranco Costamagna wrote: > Hi, this is a question mainly for ftpmasters, but I think some public > discussion here > might be beneficial for me :) > > Basically, we thought OpenWatcom license wasn't DFSG for Debain standards, > and now since > I wou

Re: Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Gianfranco Costamagna
Hi Paul >I didn't see a question in your mail :) would a clear statement from them satisfy Debian standards? or should them relicense? >Is there any reason they can't relicense to something more standard? Not sure, big company, legal issues, difficult to track people for changing it, I don't

Re: ifupdown2: debconf followup

2016-08-01 Thread Marco d'Itri
On Aug 01, Guus Sliepen wrote: > I see one big drawback of ifupdown2, and that is that it's written in > Python. Nothing wrong with that language, but it means it pulls in > dependencies which a minimal install currently doesn't require, which is > not so nice for people running small VMs or embe

Re: ifupdown2: debconf followup

2016-08-01 Thread Adam Borowski
On Mon, Aug 01, 2016 at 12:31:14PM +0200, Marco d'Itri wrote: > On Aug 01, Guus Sliepen wrote: > > > I see one big drawback of ifupdown2, and that is that it's written in > > Python. Nothing wrong with that language, but it means it pulls in > > dependencies which a minimal install currently does

Re: ifupdown2: debconf followup

2016-08-01 Thread Marco d'Itri
On Aug 01, Adam Borowski wrote: > > We should also think hard about switching to a new default since > > currently many other major distributions are moving to NetworkManager > > and/or systemd-networkd (which nowadays is usable, works well for > > simpler use cases and will be installed on ev

Re: Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Gianfranco Costamagna
(I'll drop -devel starting from next email, following up on debian-legal isntead) >If you agree, I think it's better to ask the question instead at >‘debian-legal’. Hi Debian-Legal list :) forwarding the discussion from -devel here Basically, we thought OpenWatcom license wasn't DFSG for Debain

Re: ifupdown2: debconf followup

2016-08-01 Thread Guus Sliepen
On Mon, Aug 01, 2016 at 12:31:14PM +0200, Marco d'Itri wrote: > We should also think hard about switching to a new default since > currently many other major distributions are moving to NetworkManager > and/or systemd-networkd (which nowadays is usable, works well for > simpler use cases and wi

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Adam Borowski
On Mon, Aug 01, 2016 at 12:24:12PM +0200, Guus Sliepen wrote: > Why does VirtualBox keep relying on the OpenWatcom provider? There's bcc > and faucc. AFAIK, VirtualBox upstream decided to use non-standard OpenWatcom extensions. > QEMU's SeaBIOS is compiled with GCC (but looking at the source, al

Re: Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Gianfranco Costamagna
Hi Guus >I don't see that anything has changed in the past ten years, so I don't >think a clarification will do any good. Why does VirtualBox keep relying >on the OpenWatcom provider? There's bcc and faucc. QEMU's SeaBIOS is >compiled with GCC (but looking at the source, all the 16-bit code is in

Bug#833140: RFP: embroidermodder -- Free machine embroidery software

2016-08-01 Thread Balint Reczey
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org * Package name: embroidermodder Version : 2.0 * URL : http://embroidermodder.org * License : Zlib Programming Lang: C/C++ Description : Free machine embroidery software Embroider

Re: ifupdown2: debconf followup

2016-08-01 Thread Adam Borowski
On Mon, Aug 01, 2016 at 12:42:39PM +0200, Marco d'Itri wrote: > On Aug 01, Adam Borowski wrote: > > > > We should also think hard about switching to a new default since > > > currently many other major distributions are moving to NetworkManager > > > and/or systemd-networkd (which nowadays is u

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Christian Seiler
On 08/01/2016 12:56 PM, Gianfranco Costamagna wrote: > We are not allowed to touch SeaBIOS for licence reasons. Not our decision. Maybe I don't quite understand what VirtualBox upstream meant by this sentence, but if the SeaBIOS license does not allow modification, then it would not be DFSG-free,

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Gianfranco Costamagna
Hi, >Maybe I don't quite understand what VirtualBox upstream meant by this >sentence, but if the SeaBIOS license does not allow modification, >then it would not be DFSG-free, so the fact that VirtualBox is in >contrib would actually be an error, because it should rather be in >non-free. And that w

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Guus Sliepen
On Mon, Aug 01, 2016 at 11:24:46AM +, Gianfranco Costamagna wrote: > SeaBIOS license is not used by VirtualBox, I was just mentioning it because it is a BIOS and it is compiled by GCC, so it was an argument that OpenWatcom is not a requirement to build working BIOS code. > and I think a good

Re: ifupdown2: debconf followup

2016-08-01 Thread Lars Wirzenius
On Mon, Aug 01, 2016 at 12:42:39PM +0200, Marco d'Itri wrote: > Sorry, what I actually meant was "every non-toy Debian system". Marco, we get that you have strong preferences. However, could you please avoid inflammatory language when talking about anything that isn't according to your preference

Re: MBF: Removing old GNOME python bindings

2016-08-01 Thread Emilio Pozuelo Monfort
On 29/07/16 00:20, Jonas Smedegaard wrote: > Quoting Emilio Pozuelo Monfort (2016-07-28 23:29:00) >> It is high time that we remove the old GNOME python bindings. We have >> had the "new" GObject introspection support since at least Squeeze. >> The old ones are completely unmaintained and unsuppo

Re: [Pkg-sugar-devel] MBF: Removing old GNOME python bindings

2016-08-01 Thread Jonas Smedegaard
Quoting Emilio Pozuelo Monfort (2016-08-01 16:43:06) > On 29/07/16 00:20, Jonas Smedegaard wrote: >> Quoting Emilio Pozuelo Monfort (2016-07-28 23:29:00) >>> It is high time that we remove the old GNOME python bindings. We >>> have had the "new" GObject introspection support since at least >>> Sq

Re: ifupdown2: debconf followup

2016-08-01 Thread Simon McVittie
On Mon, 01 Aug 2016 at 12:40:37 +0200, Adam Borowski wrote: > On Mon, Aug 01, 2016 at 12:31:14PM +0200, Marco d'Itri wrote: > > We should also think hard about switching to a new default since > > currently many other major distributions are moving to NetworkManager > > and/or systemd-networkd (w

Re: ifupdown2: debconf followup

2016-08-01 Thread Simon McVittie
On Mon, 01 Aug 2016 at 12:48:26 +0200, Guus Sliepen wrote: > Last time I looked at it, systemd-networkd required several > configuration files just to bring up a single interface. What were the others, beyond the .network file? This is live configuration from my home server, which has two network

Bug#833168: ITP: scala-asm -- Fork of ASM for the Scala Compiler

2016-08-01 Thread Emmanuel Bourg
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg * Package name: scala-asm Version : 5.0.4-scala-3 Upstream Author : INRIA, France Telecom * URL : https://github.com/scala/scala-asm * License : BSD-3-clause Programming Lang: Java Description : For

Re: ifupdown2: debconf followup

2016-08-01 Thread Guus Sliepen
On Mon, Aug 01, 2016 at 04:43:27PM +0100, Simon McVittie wrote: > > Last time I looked at it, systemd-networkd required several > > configuration files just to bring up a single interface. > > What were the others, beyond the .network file? This is live configuration > from my home server, which

Re: ifupdown2: debconf followup

2016-08-01 Thread Marco d'Itri
On Aug 01, Lars Wirzenius wrote: > > Sorry, what I actually meant was "every non-toy Debian system". > we get that you have strong preferences. However, could you please > avoid inflammatory language when talking about anything that isn't > according to your preferences? Reasonable people should

Re: ifupdown2: debconf followup

2016-08-01 Thread Marco d'Itri
On Aug 01, Guus Sliepen wrote: > The time spent writing such a hypothetical tool would then be better > spent keeping support for ifupdown in the installer for the non-Linux > platforms. I agree: if the Hurd/kFreeBSD porters will be able to keep sysvinit on life support then continuing to use if

Re: ifupdown2: debconf followup

2016-08-01 Thread Lars Wirzenius
On Mon, Aug 01, 2016 at 09:01:20PM +0200, Marco d'Itri wrote: > On Aug 01, Lars Wirzenius wrote: > > > > Sorry, what I actually meant was "every non-toy Debian system". > > we get that you have strong preferences. However, could you please > > avoid inflammatory language when talking about anythi

Re: ifupdown2: debconf followup

2016-08-01 Thread Marc Haber
On Mon, 1 Aug 2016 12:48:26 +0200, Guus Sliepen wrote: >On Mon, Aug 01, 2016 at 12:31:14PM +0200, Marco d'Itri wrote: >> We should also think hard about switching to a new default since >> currently many other major distributions are moving to NetworkManager >> and/or systemd-networkd (which now

Re: ifupdown2: debconf followup

2016-08-01 Thread Marc Haber
On Mon, 1 Aug 2016 12:42:39 +0200, m...@linux.it (Marco d'Itri) wrote: >On Aug 01, Adam Borowski wrote: > >> > We should also think hard about switching to a new default since >> > currently many other major distributions are moving to NetworkManager >> > and/or systemd-networkd (which nowadays

Re: [Pkg-sugar-devel] MBF: Removing old GNOME python bindings

2016-08-01 Thread James Cameron
On Mon, Aug 01, 2016 at 05:37:19PM +0200, Jonas Smedegaard wrote: > Quoting Emilio Pozuelo Monfort (2016-08-01 16:43:06) > > On 29/07/16 00:20, Jonas Smedegaard wrote: > >> Quoting Emilio Pozuelo Monfort (2016-07-28 23:29:00) > >>> It is high time that we remove the old GNOME python bindings. We >

Re: [Pkg-sugar-devel] MBF: Removing old GNOME python bindings

2016-08-01 Thread Emilio Pozuelo Monfort
On 01/08/16 17:37, Jonas Smedegaard wrote: > Yes, most of those activities are not in Debian - just as most of shell > scripts depending on Zsh is not in Debian, but it would still be a bad > idea to kick that package judging from its reverse dependencies (I > guess: I am not a Zsh user myself).

Re: ifupdown2: debconf followup

2016-08-01 Thread Michael Biebl
Am 01.08.2016 um 12:48 schrieb Guus Sliepen: > I'd say a good starting point would be to try to switch the installer to > configuring NetworkManager or systemd-networkd, instead of generating a > /etc/network/interfaces file. It already does that if the network-manager packages is installed by d-i

Re: sybase license and openWatcom DFSGness

2016-08-01 Thread Jakub Wilk
* Guus Sliepen , 2016-08-01, 14:01: Virtualbox is under GPL-2 with a lot of exception, allowing it to be used with MPL, Apache 2.0, OpenSSL. So, LGPL-3 will be too restrictive I think for them. It should be fine to combine GPL-2 and LGPL-3. No, GPLv2 and LGPLv3 are not compatible: https://w

Re: ifupdown2: debconf followup

2016-08-01 Thread Roopa Prabhu
On Mon, Aug 1, 2016 at 12:00 AM, Guus Sliepen wrote: > On Sun, Jul 31, 2016 at 06:58:20PM -0700, Roopa Prabhu wrote: > >> And, we will be very happy to work towards making ifupdown2 >> the default in Debian. If there are ways to make that happen, please let us >> know. > > First, try to make it c

Re: [Pkg-sugar-devel] MBF: Removing old GNOME python bindings

2016-08-01 Thread Jonas Smedegaard
Quoting Emilio Pozuelo Monfort (2016-08-01 23:11:58) > On 01/08/16 17:37, Jonas Smedegaard wrote: >> Yes, most of those activities are not in Debian - just as most of >> shell scripts depending on Zsh is not in Debian, but it would still >> be a bad idea to kick that package judging from its reve