Hello community, here is the log from the commit of package llvm for openSUSE:Factory checked in at 2019-12-25 10:54:35 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/llvm (Old) and /work/SRC/openSUSE:Factory/.llvm.new.6675 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "llvm" Wed Dec 25 10:54:35 2019 rev:108 rq:758955 version:9.0.1 Changes: -------- --- /work/SRC/openSUSE:Factory/llvm/llvm.changes 2019-10-28 16:46:35.108717573 +0100 +++ /work/SRC/openSUSE:Factory/.llvm.new.6675/llvm.changes 2019-12-25 10:55:01.329633454 +0100 @@ -1,0 +2,9 @@ +Fri Dec 20 21:13:19 UTC 2019 - Aaron Puchert <[email protected]> + +- Update to version 9.0.1. + * This release contains bug-fixes for the LLVM 9.0.0 release. + This release is API and ABI compatible with 9.0.0. +- Update README.packaging: we don't provide revision numbers any + longer, because upstream has moved from Subversion to git. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ llvm.spec ++++++ --- /var/tmp/diff_new_pack.2TU1Tn/_old 2019-12-25 10:55:02.253633743 +0100 +++ /var/tmp/diff_new_pack.2TU1Tn/_new 2019-12-25 10:55:02.253633743 +0100 @@ -1,7 +1,7 @@ # # spec file for package llvm # -# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2019 SUSE LLC # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -25,7 +25,7 @@ %endif %endif Name: llvm -Version: 9.0.0 +Version: 9.0.1 Release: 0 Summary: Low Level Virtual Machine License: Apache-2.0 WITH LLVM-exception OR NCSA @@ -98,7 +98,7 @@ %package -n clang Summary: CLANG frontend for LLVM Group: Development/Languages/C and C++ -Url: https://clang.llvm.org/ +URL: https://clang.llvm.org/ Requires: clang%{_sonum} = %{version} Recommends: clang-doc Provides: llvm-clang = %{version} @@ -114,7 +114,7 @@ %package -n clang-checker Summary: Static code analyzer for CLANG Group: Development/Languages/C and C++ -Url: https://clang-analyzer.llvm.org/ +URL: https://clang-analyzer.llvm.org/ Requires: clang%{_sonum}-checker = %{version} Provides: llvm-clang-checker = %{version} Obsoletes: llvm-clang-checker < %{version} @@ -213,7 +213,7 @@ %package -n lldb Summary: Software debugger built using LLVM libraries Group: Development/Tools/Debuggers -Url: https://lldb.llvm.org/ +URL: https://lldb.llvm.org/ Requires: lldb%{_sonum} = %{version} Recommends: python3-lldb @@ -254,7 +254,7 @@ %package -n lld Summary: Linker for Clang/LLVM Group: Development/Tools/Building -Url: https://lld.llvm.org/ +URL: https://lld.llvm.org/ Requires: lld%{_sonum} = %{version} %description -n lld ++++++ README.packaging ++++++ --- /var/tmp/diff_new_pack.2TU1Tn/_old 2019-12-25 10:55:02.277633750 +0100 +++ /var/tmp/diff_new_pack.2TU1Tn/_new 2019-12-25 10:55:02.277633750 +0100 @@ -52,18 +52,11 @@ new sources. 4. Update the version number in the patches to match the new sources. - 5. Update the "_revsn" tag in llvmX.spec to match the - revision number of the tag. This can be found on - https://lists.llvm.org/pipermail/llvm-branch-commits - and should have like "[llvm-tag]" and - "Creating release candidate final" in the subject - line. You want to find the one for the current LLVM - release. - 6. Update the "_relver" tag in llvmX.spec to match + 5. Update the "_relver" tag in llvmX.spec to match the "Version" tag. - 7. Confirm everything builds successfully and there are + 6. Confirm everything builds successfully and there are no new rpmlint issues. - 8. Update the llvmX.changes file. + 7. Update the llvmX.changes file. 2. llvm package: 1. Update the "Version" tag to match the new llvmX version. @@ -91,19 +84,12 @@ new sources. 4. Update the version number in the patches to match the new sources. - 5. Update the "_revsn" tag in llvmX.spec to match the - revision number of the tag. This can be found on - https://lists.llvm.org/pipermail/llvm-branch-commits - and should have like "[llvm-tag]" and - "Creating release candidate final" in the subject - line. You want to find the one for the current LLVM - release. - 6. Update the "_relver" tag in llvmX.spec to match + 5. Update the "_relver" tag in llvmX.spec to match the "Version" tag. - 7. Confirm everything builds successfully and there are + 6. Confirm everything builds successfully and there are no new rpmlint issues. Some patches may need to be removed or rebased. - 8. Update the llvmX.changes file. + 7. Update the llvmX.changes file. =============================== @@ -138,8 +124,8 @@ form "X.0". 8. Change the "_uaver" tag in llvmX.spec to match the new major/minor versions. It should be of the form "X00". - 9. Update the "Version", "_revsn", and "_relver" tags - and the version numbers in the patches as described in + 9. Update the "Version", and "_relver" tags and the + version numbers in the patches as described in PATCH-LEVEL UPDATES above. 10. Confirm llvmX.spec builds successfully and there are no new rpmlint issues.
