gcc9
No description set
-
8
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:gcc/gcc9 && cd $_ - Create Badge
Refresh
Refresh
Source Files
Revision 57 (latest revision is 138)
Michael Matz (matz2)
committed
(revision 57)
Hmm, so maybe the build service does take conditions into account, and only osc checkconstraints doesn't. Let's try not using s390x in the conditions.
Comments 2
Hi Richard,
given 9.2.1+git is a pre-release of 9.2.1, shouldn't it be versioned 9.2.1~git in order to be compared correctly:
$ LANG=C zypper vcmp gcc9-9.2.1+git1022-1.1 gcc9-9.2.1~git1022-1.1 gcc9-9.2.1+git1022-1.1 is newer than gcc9-9.2.1~git1022-1.1
Especially, if a gcc-9.2.1 version is released (I know, it's very unlikely for openSUSE to package a released gcc package):
$ LANG=C zypper vcmp gcc9-9.2.1-1.1 gcc9-9.2.1~git1022-1.1 gcc9-9.2.1-1.1 is newer than gcc9-9.2.1~git1022-1.1
Compare to: a 9.2.1+ version is always interpreted as newer:
$ LANG=C zypper vcmp gcc9-9.2.1-1.1 gcc9-9.2.1+git1022-1.1 gcc9-9.2.1-1.1 is older than gcc9-9.2.1+git1022-1.1
Maybe, you want to consider this change, when the suite is updated the next time.
Hello.
Thanks for heads up. We know about the problem which is caused by GCC transition from SVN to GIT.