Hello Greg, Am Sonntag, 3. Mai 2020, 19:38:07 CEST schrieb Greg Freemyer:
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)
Did the license change compared to 2.6.1? - if no: use GPL-2.0-or-later as in 2.6.1 - if yes -- ask upsteam for clarification (https://spdx.org/licenses/ has the list of widely used licenses) -- wait for SUSE legal review
- 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
you could do as well: Conflicts: python-volatility < 10.0.0 Provides: python-volatility = 10.0.0
- I carried over the *.changes file. Not sure that should happen, or if I should start from a clean changes file.
In think this is OK to carry the changes file over - it is clearly stated that this is a rewrite. Does this version still support Python2? In this case a singlespec would be applicable. HTH Axel -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org