On Fri, Apr 22, 2016 at 05:34:20PM +0200, Adrian Schröter wrote: > On Freitag, 22. April 2016, 16:11:02 wrote Michal Kubecek: > > > (adding back other recipients who may not be all on the evergreen ML) > > > > Some were lost, including Adrian :-( Trying again > > > > On Fri, Apr 22, 2016 at 03:38:13PM +0200, Wolfgang Rosenauer wrote: > > > Am 22.04.2016 um 15:23 schrieb Adrian Schröter: > > > > You release from two different Maintenance projects into the same > > > > repository? > > > > > > > > This can't work ... I thought you handed over to > > > > Evergreen:Maintenance for 13.1:Update ? > > > > > > > > > > This was required to be able to do kernel updates at all because of > > > the signing keys. > > > > To clarify: this is about kernel image and modules signing for the > > purpose of UEFI Secure Boot. IIRC the problem was that a kernel update > > handled in openSUSE:Evergreen:Maintenance couldn't be signed by a key > > accepted by UEFI Secure Boot (as the standard 3.11 kernels were) so that > > on machines with UEFI, it could only be used if the key was added > > manually (if possible) or Secure Boot was disabled. That's why kernel > > updates are handled in openSUSE:Maintenance. > > The only short term solution I see is what Marcus is currently doing, > renaming the container. > > But we can maybe add some code which allows to configure a prefix > to avoid conflicts in future. > > That needs a second thought however, Marcus, can you create a fate > request for this?
FATE#320797: container prefixes for sharing maintenance projects Ciao, Marcus _______________________________________________ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
