So please excuse my ignorance here: But how does that work? How can we,
as Debian, ensure that a user automatically complies with the license
when a package is installed and spawns up a service on a port? (Or
similarly, installs itself into a web server found on the system.)
I don't think
On Wed, 7 May 2014, Bálint Réczey wrote:
2014-05-07 14:37 GMT+02:00 Thorsten Glaser t...@debian.org:
Which you may want to do, in order to patch a security issue
you just found, locally, before filing it upstream.
In my interpretation in this case I would have some reasonable time to
On Thu, 08 May 2014, Thorsten Glaser wrote:
On Wed, 7 May 2014, Bálint Réczey wrote:
In my interpretation in this case I would have some reasonable time
to comply, i.e. I don't have to publish all 0days on my site if I
run AGPL-covered software..
You only have to publish code to users who
Quoting Don Armstrong (2014-05-08 21:06:08)
On Thu, 08 May 2014, Thorsten Glaser wrote:
On Wed, 7 May 2014, Bálint Réczey wrote:
In my interpretation in this case I would have some reasonable time
to comply, i.e. I don't have to publish all 0days on my site if I
run AGPL-covered
* Jonas Smedegaard d...@jones.dk, 2014-05-08, 21:37:
So if Debian provides, say, a web frontend to Ghostscript, then with
AGPL Ghostscript running that web frontend as a service for others only
require an interface serving its sources if the _webmaster_ changes the
code for that frontend?
Quoting Jakub Wilk (2014-05-08 21:55:45)
* Jonas Smedegaard d...@jones.dk, 2014-05-08, 21:37:
So if Debian provides, say, a web frontend to Ghostscript, then with
AGPL Ghostscript running that web frontend as a service for others
only require an interface serving its sources if the
So if Debian provides, say, a web frontend to Ghostscript, then with
AGPL Ghostscript running that web frontend as a service for others
only require an interface serving its sources if the _webmaster_
changes the code for that frontend?
Not if Debian makes changes to both the frontend and
7 matches
Mail list logo
