Re: Bug#1135657: bmagic: DFSG Issues
Francesco Poli <[email protected]> Tue, 16 Jun 2026 00:07:07 +0200
| Newsgroups | gmane.linux.debian.devel.legal |
|---|---|
| Message-ID | <20260616000707.29954096@crunch> |
--Sig_/Zejj2UEjGP8r_KquUoAONUc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 15 Jun 2026 16:55:11 +0300 Adrian Bunk wrote: [...] > 4-clause BSD with the advertising clause has always been recognized > as DFSG-free (and is also listed at [1]): >=20 > All advertising materials mentioning features or use of this > software must display the following acknowledgement: This product > includes software developed by the <copyright holder>. Yes, although it is obnoxious, deprecated, problematic and almost everywhere recommended against, it has been traditionally considered acceptable with respect to the DFSG. The obnoxious advertising clause might be seen as similar to the bmagic license clause under consideration. So, maybe bmagic complies with the DFSG. >=20 >=20 > AGPLv3 with the following clause is DFSG-free[2]: >=20 > Notwithstanding any other provision of this License, if you modify > the Program, your modified version must prominently offer all users=20 > interacting with it remotely through a computer network (if your=20 > version supports such interaction) an opportunity to receive the=20 > Corresponding Source of your version by providing access to the=20 > Corresponding Source from a network server at no charge, through > some standard or customary means of facilitating copying of > software. I believe that this is an unfortunate example, for at least two reasons. First off, the GNU AfferoGPL v3 is a controversial license, which (this is true) has been considered acceptable for main by the Debian FTP Masters [2], but is seen as non-acceptable by a number of people (including me [3]). Secondly, I don't see much similarity between this clause and the bmagic license clause under consideration. Hence, I don't think that the DFSG-freeness of works released under the terms of the GNU AfferoGPL v3 is too relevant for the topic we're discussing here. [...] > [1] https://www.debian.org/legal/licenses/ > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=3D17;bug=3D495721 [3] https://bugs.debian.org/495721#28 --=20 http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr =3D=3D CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE --Sig_/Zejj2UEjGP8r_KquUoAONUc Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEygERR5zS79/7gjklPhwn4R9pv/4FAmowd4sACgkQPhwn4R9p v/70Xg/+OHCWyIkKN5IE2JpphnZ1hZRttu27/fn8CKuBYidX/8xPa2xA0Atpffyg Z4owXtQpD510jclarzkKDdzJawrK98LRHv0tFafw6Oipd1STLYHwr/Idy8MXypMo /gMmwDxBW3o8JsIk3oUOoK4wOLw3ozPZNLcf7fQ1KiU+S0UZVYyWN7bmDr8Zy2M0 AsIq6Di/mFuWC7sr11ICq6gS79FFjHUq2HDd6bYi5xSeIozPUfKQ4Bez3NWELCql gIMscS5B4/81hCGnKXsVH+OtplG2P4XTPqp+ZzjSkB0jwP9lb2MtMMF4nmir964d rAHRSw67gNS92cqJwCzolBQa5Gtz/a0tIphTyOx9qCDRCkGL+eoeAQd69yS9gJUP Tp9LVmJYJrorNLQ4X7FrJx5NO/31+x7Bc9SwWk0DSeq4DoHnrmCGdzcPoKfs75bC YB9SlwxYZaBiOO33IbS5I/HE5j4wmHE8xjnwFgfwbga+Xu8PvaQak9driELlz11v haor2yToQpRD8D+tTCvEm5sYWfJKIfiSVXP/6QkdJWMGMGJv6wyY1LR5G9t4hKlG k5j669nGnxYVI7DsrT9dkQ5mDkFd6YlgltNia4OMeKQJVlp97VKQZQInWkqNVFLP h/bZBE0VvnRDTmxaYTMdZW8TDm6tpm/lTs9W9Y0CbPi5GSesMh8= =ROGO -----END PGP SIGNATURE----- --Sig_/Zejj2UEjGP8r_KquUoAONUc--