severity 914291 serious thanks On Wed, 21 Nov 2018, Markus Koschany wrote: > Am 21.11.18 um 18:15 schrieb Thorsten Glaser:
> > Justification: Policy 2.3, 12.5, possibly 2.1 OK, not 2.1 — after a quick review and word diff against EPLv1 it looks DFSG-free enough. > Further investigation into the issue would have yielded the following: > > The project is still dual-licensed under EPL-2.0 and > GPL-2+-with-class-path-exception. See the NOTICE file. This is wrong, see the NOTICE file: | ## Declared Project Licenses | | This program and the accompanying materials are made available under the terms | of the Eclipse Public License v. 2.0 which is available at | http://www.eclipse.org/legal/epl-2.0. This Source Code may also be made | available under the following Secondary Licenses when the conditions for such | availability set forth in the Eclipse Public License v. 2.0 are satisfied: GNU | General Public License, version 2 with the GNU Classpath Exception which is | available at https://www.gnu.org/software/classpath/license.html. This means the licence is EPLv2 “period”. GPLv2 with Classpath Exception is listed as Secondary License, which, in EPLv2 parlance, may _not_ simply be applied to any given work just because the permission is there, but only if certain extra conditions are met, namely, being combined, in a single work, with other code under such licence. As such, it’s explicitly *not* a dual licence. Furthermore, even then, the debian/copyright file states… | License: CDDL-1.1 or GPL-2 with Classpath exception … which simply is wrong, and does not list the EPLv2 at all (given it came into existence only in 2017). bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
