Summary: | dev-lisp/hyperspec-7.0 : * ERROR: dev-lisp/hyperspec-7.0::gentoo failed (unpack phase): | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | licenses, yana |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-lisp:hyperspec-7.0:20160517-185702.log
emerge-history.txt environment |
Description
Toralf Förster
2016-05-17 20:02:14 UTC
Created attachment 434556 [details]
dev-lisp:hyperspec-7.0:20160517-185702.log
Created attachment 434558 [details]
emerge-history.txt
Created attachment 434560 [details]
environment
Thanks for the report. There is a bump in the lisp overlay [1] which removes the restriction. Don't know if it's time to copy it to the tree and ask for stabilization. It seems to be there since 2010. Any ideas? https://gitweb.gentoo.org/proj/lisp.git/tree/dev-lisp/hyperspec/hyperspec-7.0-r2.ebuild It is fetch restricted, as correctly stated in 7.0-r1 commit ab48131ac0e496482b97e41fbe70b00ab5deda79 Author: Andrey Grozin <grozin@gentoo.org> Date: Thu Dec 15 21:00:35 2016 +0700 dev-lisp/hyperspec: cleaning 7.0 Bug: 583332 Package-Manager: portage-2.3.3 (In reply to Chema Alonso Josa from comment #4) > Thanks for the report. > > There is a bump in the lisp overlay [1] which removes the restriction. Don't > know if it's time to copy it to the tree and ask for stabilization. > > It seems to be there since 2010. Any ideas? > > https://gitweb.gentoo.org/proj/lisp.git/tree/dev-lisp/hyperspec/hyperspec-7. > 0-r2.ebuild I don't think it's legal to remove RESTRICT=fetch as done in the lisp overlay ebuild: if this ebuild is copied to the main tree, hyperspec will be copied to Gentoo rsync mirrors and redistributed from there. This is not allowed. So, the correct ebuild is 7.0-r1 which is in the main tree for ages. In addition to this, the ebuild from the lisp overlay simply does not work because of the line dosym "/usr/share/doc/${PF} /usr/share/doc/${PN}" || die ln -s correctly complains that it cannot have 1 argument. The correct line would be dosym "/usr/share/doc/${PF}" "/usr/share/doc/${PN}" Can somebody remove this ebuild from the lisp overlay? The correct (and working) one is 7.0-r1 in the main tree. I've fixed some minor QA complaints in the portage tree and synced the overlay. Thanks. Andrey, they allow mirroring (redistribution). I've sent them a message, forwarding their reply. Delivered-To: yegortimoshenko@gmail.com Received: by 10.31.220.66 with SMTP id t63csp96870vkg; Tue, 23 May 2017 05:14:45 -0700 (PDT) X-Received: by 10.223.157.29 with SMTP id k29mr16040711wre.156.1495541685872; Tue, 23 May 2017 05:14:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1495541685; cv=none; d=google.com; s=arc-20160816; b=OJ5XyfbsBewv1eYMyi5UC2PAhiXMYU1qOBADIA2tzPTLvX/Yd0itC5q9Q11wnCZ5Fz RPJhdBFeoSArjJE4yV2lPrFpJVnUK/EDUlbwXHdAOhlle6mCQRdWT5K4VCFmC0umGkqd JwEvfWmXkzdmH0RBKdAZmtddz9n9qvGUtQUIE22eY4YTcntV0+cFHDEzQqftDKn2V9ba IfY2JGW/quUpbnELS17ZfsyzyjAkl9RImDKZfZmCEmAYa/tPEDHcQt6Oo4RWgqsFJVUH ZzD0CvUW8Xp8Q2mr2+Knd+B9PJ83qFZfLM3ZHgIqku+F9UK5owYfbDziy+wI3BGgXNMT bOIw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=references:subject:in-reply-to:cc:to:from:message-id:date :arc-authentication-results; bh=lWe1ITz09qdZ4mBngg3JjpzxBzSu2cP0cCfY8PW9Fis=; b=xg4FLRE6DsLo4ckzHOaxIXxRWFnPICNBsT2NUwEHA0U+zHPfq8qdyu43HgiXvIMaYf bUtbNbc6wmQadbawu7k/fdeuvSB6QOqjtZvUIa50p5LbkhOsEWSuzK9Feh1iADIHsjRB TrPdAL5+T74Lq4NEZZCof/e/eXQa5gQOrpp6zjEymP7kZepRaLBk/ccCWbIzn6Qvsws7 YsMTGNViccAQ2m2Q6nozcVGeVYKom3ZoujQUOTap3NHFYEt9AfeK75i6wFSZbVH2XLie yH6KWxe6klpQN26EhddZr3aMmcHjkG13VIVXku1/E51+wuExCmjejdEgfMBCvVjy5zOW 9uVg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of martin@lispworks.com designates 46.17.166.21 as permitted sender) smtp.mailfrom=martin@lispworks.com Return-Path: <martin@lispworks.com> Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com. [46.17.166.21]) by mx.google.com with ESMTP id m66si2153353wma.23.2017.05.23.05.14.45 for <yegortimoshenko@gmail.com>; Tue, 23 May 2017 05:14:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of martin@lispworks.com designates 46.17.166.21 as permitted sender) client-ip=46.17.166.21; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of martin@lispworks.com designates 46.17.166.21 as permitted sender) smtp.mailfrom=martin@lispworks.com Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.15.2/8.15.2) with ESMTP id v4NCEg9a000693; Tue, 23 May 2017 13:14:42 +0100 (BST) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id v4NCEgOc009112; Tue, 23 May 2017 13:14:42 +0100 Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id v4NCEgIf009108; Tue, 23 May 2017 13:14:42 +0100 Date: Tue, 23 May 2017 13:14:42 +0100 Message-Id: <201705231214.v4NCEgIf009108@higson.cam.lispworks.com> From: Martin Simmons <martin@lispworks.com> To: Yegor Timoshenko <yegortimoshenko@gmail.com> CC: webmaster@lispworks.com In-reply-to: <9BE7CAB9-A8B5-4EB4-A0E1-3CD23B24DC21@gmail.com> (message from Yegor Timoshenko on Mon, 22 May 2017 21:37:35 +0300) Subject: Re: (LispWorks Webmaster Support Call #59443) Hyperspec redistribution References: <9BE7CAB9-A8B5-4EB4-A0E1-3CD23B24DC21@gmail.com> >>>>> On Mon, 22 May 2017 21:37:35 +0300, Yegor Timoshenko said: > > Currently Gentoo users have to manually fetch your tarball in order to install hyperspec. > >From https://bugs.gentoo.org/show_bug.cgi?id=583332#c6: > > > I don't think it's legal to remove RESTRICT=fetch as done in the lisp overlay ebuild: > > if this ebuild is copied to the main tree, hyperspec will be copied to Gentoo rsync mirrors > > and redistributed from there. This is not allowed. > > Is it allowed to mirror your hyperspec tarball? Mirror yes, but you cannot redistribute it under a different license. The license terms are here: http://www.lispworks.com/documentation/HyperSpec/Front/Help.htm#Legal -- Martin Simmons LispWorks Ltd http://www.lispworks.com/ > I don't think it's legal to remove RESTRICT=fetch as done in the lisp overlay ebuild: if this ebuild is copied to the main tree, hyperspec will be copied to Gentoo rsync mirrors and redistributed from there. This is not allowed. So, the correct ebuild is 7.0-r1 which is in the main tree for ages. Even if mirroring was not permitted by the license (which is not the case, see the previous message), we would only have to specify RESTRICT=mirror, and not RESTRICT=fetch. Making this package nofetch was not necessary. See: https://devmanual.gentoo.org/general-concepts/mirrors/ ebuild(5) man page The HyperSpec license says: "Permission to copy, distribute, display, and transmit the Common Lisp HyperSpec is granted provided that copies are not made or distributed or displayed or transmitted for direct commercial advantage, that notice is given that copying, distribution, display, and/or transmission is by permission of Xanalys Incorporated, and that any copy made is COMPLETE and UNMODIFIED. IN PARTICULAR, the material that MUST appear in the copy includes:" (This is followed by a list of things that must be included, which seems redundant because only unmodified distribution is allowed.) So IMHO the mirror restriction can be lifted. CCing licenses team. (In reply to Ulrich Müller from comment #10) > > (This is followed by a list of things that must be included, which seems > redundant because only unmodified distribution is allowed.) > > So IMHO the mirror restriction can be lifted. CCing licenses team. Agreed. If there are no objections, I'll apply the patch in the following days. https://github.com/gentoo/gentoo/pull/4773 Thanks all! The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/lisp.git/commit/?id=41cc3955039844fb9e3c8f8eb2df25e75c3609d3 commit 41cc3955039844fb9e3c8f8eb2df25e75c3609d3 Author: Yegor Timoshenko <yegortimoshenko@gmail.com> AuthorDate: 2017-06-05 11:16:38 +0000 Commit: Chema Alonso Josa <nimiux@gentoo.org> CommitDate: 2018-03-09 17:37:41 +0000 dev-lisp/hyperspec: Removes fetch restrictions Bug: https://bugs.gentoo.org/show_bug.cgi?id=583332 Closes: https://github.com/gentoo/gentoo/pull/4773 dev-lisp/hyperspec/Manifest | 2 +- dev-lisp/hyperspec/hyperspec-7.0-r1.ebuild | 16 +--------------- 2 files changed, 2 insertions(+), 16 deletions(-)} The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/lisp.git/commit/?id=115cf71a91bfa8401ab468e844b4158639267513 commit 115cf71a91bfa8401ab468e844b4158639267513 Author: Yegor Timoshenko <yegortimoshenko@gmail.com> AuthorDate: 2017-06-05 11:16:38 +0000 Commit: Chema Alonso Josa <nimiux@gentoo.org> CommitDate: 2018-03-09 21:34:03 +0000 dev-lisp/hyperspec: Removes fetch restrictions Bug: https://bugs.gentoo.org/show_bug.cgi?id=583332 Closes: https://github.com/gentoo/gentoo/pull/4773 dev-lisp/hyperspec/Manifest | 2 +- dev-lisp/hyperspec/hyperspec-7.0-r1.ebuild | 16 +--------------- 2 files changed, 2 insertions(+), 16 deletions(-)} |