openSUSE Packaging

Download

packaging@lists.opensuse.org

May 2020

29 participants
22 discussions

[opensuse-packaging] Fwd: Prep'ing python-volatiliity replacement package volatility3 for factory submission. Can someone please review the license and the Obsoletes/Provides statements
by Greg Freemyer 04 May '20

04 May '20

All, I'm prepping https://build.opensuse.org/package/show/security:forensics/volatility3 for submission to factory, but: - I'm not sure which license to use. I've copied the contents of the LICENSE.txt file below my signature (see below) - Because this is a replacement package I'm obsoleting python-volatility (python2 only), but the fact the version number for this is lower than it was for python-volatility leaves me in doubt if I did it right. I would normally say: Obsoletes: python-volatility <= 2.6.1 But because the version number for the new package is less than 2.6.1 that is causing [ 18s] volatility3.noarch: W: self-obsoletion python-volatility <= 2.6.1 obsoletes python-volatility = 1.0.0+beta.1 [ 18s] volatility3.noarch: W: self-obsoletion volatility <= 2.4 obsoletes volatility = 1.0.0+beta.1 [ 18s] The package obsoletes itself. This is known to cause errors in various tools [ 18s] and should thus be avoided, usually by using appropriately versioned Obsoletes [ 18s] and/or Provides and avoiding unversioned ones. So, I'm just using = in the spec file currently. Obsoletes: python-volatility = 2.6.1 - I carried over the *.changes file. Not sure that should happen, or if I should start from a clean changes file. Advice appreciated, Thanks Greg -- Greg Freemyer Advances are made by answering questions. Discoveries are made by questioning answers. — Bernard Haisch =============== contents of LICENSE.txt file ================== Volatility Software License Version 1.0 dated October 3, 2019. This license covers the Volatility software, Copyright 2019 Volatility Foundation. Software The software referred to in this license includes the software named above, and any data (such as operating system profiles or configuration information), and documentation provided with the software. Purpose This license gives you permission to use, share, and build with this software for free, but requires you to share source code for changes, additions, and software that you build with it. Acceptance In order to receive this license, you must agree to its rules. The rules of this license are both obligations under that agreement and conditions to your license. You must not do anything with this software that triggers a rule that you cannot or will not follow. Copyright Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it. Notices You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to https://www.volatilityfoundation.org/license/vsl-v1.0. You must not remove any copyright notice in the Software. Patent Each contributor licenses you to do everything with this software that would otherwise infringe any patent claims they can license or become able to license. Reliability No contributor can revoke this license. Copyleft If you make any Additions available to others, such as by providing copies of them or providing access to them over the Internet, you must make them publicly available, according to this paragraph. "Additions" includes changes or additions to the software, and any conte nt or materials, including any training materials, you create that contain any portion of the software. "Additions" also includes any translations or ports of the software. "Additions" also includes any software designed to execute the software and parse its results, suc h as a wrapper written for the software, but does not include shell or execution menu software designed to execute software generally. When this license requires you to make Additions available: - You must publish all source code for software under this license, in the preferred form for making changes, through a freely accessible distribution system widely used for similar source code, so the developer and others can find and copy it. - You must publish all data or content under this license, in a format customarily used to make changes to it, through a freely accessible distribution system, so the developer and others can find and copy it. - You are responsible to ensure you have rights in Additions necessary to comply with this section. Contributing If you contribute (or offer to contribute) any materials to Volatility Foundation for the software, such as by submitting a pull request to the repository for the software or related content run by Volatility Foundation, you agree to contribute them under the under the B SD 2-Clause Plus Patent License (in the case of software) or the Creative Commons Zero Public Domain Dedication (in the case of content), unless you clearly mark them "Not a Contribution." Trademarks This license grants you no rights to any trademarks or service marks. Termination If you violate any term of this license, your license ends immediately. No Liability As far as the law allows, the software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim. Versions Volatility Foundation is the steward of this license and may publish new versions of this license with new version numbers. You may use the software under the version of this license under which you received the software, or, at your choice, any later version. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2

[opensuse-packaging] Need help understanding E: lto-no-text-in-archive RPMLINT error.
by andythe_great 02 May '20

02 May '20

Hello, I have been trying to build Avogadrolibs https://github.com/OpenChemistry/avogadrolibs https://build.opensuse.org/package/live_build_log/home:andythe_great/avogad… However, this error prevent it from building. E: lto-no-text-in-archive (Badness: 10000) I found this documentation: https://en.opensuse.org/openSUSE:LTO#LTO_enablement_in_openSUSE:Factory Which it says to add the flag %global _lto_cflags %{?_lto_cflags} -ffat-lto-objects to fix the issue which it did. But Science repo maintainer won't accept it as a fix. https://build.opensuse.org/request/show/780593 So I ask in openSUSE forum, which was told that it got something to do with reproducibility. https://forums.opensuse.org/showthread.php/539911-How-to-detect-GCC-using-C… I decide to ask the Avogadro dev to fix the issue but neither me, openSUSE forum admin or Avogadro dev understand why should it be done. https://github.com/OpenChemistry/avogadrolibs/issues/455 Which the issue remain unsolved, so I would like to know what E: lto-no-text-in-archive means so I can tell the Avogadro dev why they should fix it and why it is exclusive to openSUSE. Thanks Andy -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 5