Bug 612982

Summary:	net-print/xerox-drivers - suspect LICENSE
Product:	Gentoo Linux	Reporter:	Michael Palimaka (kensington) <kensington>
Component:	Current packages	Assignee:	No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status:	RESOLVED FIXED
Severity:	normal	CC:	licenses
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=381073
Whiteboard:
Package list:		Runtime testing required:	---

Description Michael Palimaka (kensington) gentoo-dev

2017-03-18 08:19:27 UTC

From the ebuild:

LICENSE="public-domain"

I doubt that's correct, and judging by the scary-looking EULA at $HOMEPAGE I wonder if we should ship this package at all.

Comment 1 Ulrich Müller gentoo-dev

2017-03-18 08:50:19 UTC

This package came from Sunrise, where it was labelled with a "Xerox" license:
https://gitweb.gentoo.org/proj/sunrise.git/commit/?id=7aa3b8710ece1606e5471494a8b38380c79dd132

No idea why this was lost when the package was moved to the main tree.

We definitely need fetch and bindist restrictions here.

Comment 2 Michael Palimaka (kensington) gentoo-dev

2017-03-18 09:10:15 UTC

Fixed in git.

https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=bc2dd4304cde21bcc5214927e042421480d46dfe...9cf5e51decb366992d1fb56b95ca763390bec80a

Comment 3 Matthew Schultz 2018-01-02 16:03:47 UTC

Why was a fetch restrict added?  Why wouldn't ACCEPT_LICENSE suffice?  There is no mirror restriction or anything other than just accepting the license that bars the ebuild from downloading the package.

Comment 4 Matthew Schultz 2018-01-02 16:07:45 UTC

I digress, it does appear there is a mirror restriction in the license.  So why not just restrict it to mirror?

Comment 5 Ulrich Müller gentoo-dev

2018-01-02 22:36:18 UTC

(In reply to Matthew Schultz from comment #3)
> Why was a fetch restrict added?

If you look at ${HOMEPAGE}, you'll find that the download is behind an "accept license" button. Our standard practice is then to add fetch restriction to the ebuild. We won't bypass upstream's acceptance mechanism by deep-linking to the download page (even if it would be trivial, as in this case).