openSUSE Release Process » Jump 15.2

Comment from Max

SLE-12161 actually is SLE-12162

2 replies
August 19, 2020 3:51 PM
shim is another topic... the problem is we have to stay with SLE's shim...
the whole chain, shim/grub2/kernel must to use the same signkey
if we rebuilt shim in opensuse, I don't think we can uses opensue key to verify SLE signed grub2
SLE-12161 actually is SLE-12162

mlin7442
this is also something we can't do it in Backports after talked to Ismail, they have problem for those HPC pacakges esp. openmpi stuff

mlin7442
we probably have to rebuild all HPC packages in Jump

lkocman-factory@deadrat:~> osc copypac openSUSE:Leap:15.2:Update gdb openSUSE:Jump:15.2
Copying files...
<revision rev="2" vrev="2">
  <srcmd5>018083c248f02075656fc9ee0625e828</srcmd5>
  <version>8.3.1</version>
  <time>1598013501</time>
  <user>lkocman-factory</user>
  <comment>osc copypac from project:openSUSE:Leap:15.2:Update package:gdb revision:34</comment>
  <requestid/>
</revision>

Fork: https://build.opensuse.org/package/show/openSUSE:Jump:15.2/gdb

Rest of 8 rejected features were either that package used is_opensuse only for legacy version check or a duplicate of some higher-level feature.

I'll keep this feature open to track any other features that might get rejected in the future.

SDL2 integration with qemu was rejected (SLE-11662). I did email opensuse-project@ and opensuse-factory@ with deadline for usecase until the end of the week. I'll revisit issue on Monday and either fork the package or drop the feature from Leap.

Update as of today: 9 features rejected so far (7 duplicates) and gdb/fpc and qemu/sdl2 integration.

python-oauth2client feature unification was rejected by SLE Product Management.
We want to keep django support in Leap therefore let's fork and rebuild the package.
https://en.opensuse.org/Portal:Jump/Leap15.2.1:Forks