Hello, I selected the blocker option, forcing users to unmerge gnupg-1.9. Users that used only 1.9 slot, will be notified later by revbumping this slot.
I am truly sorry for bothering users, but this is the only way to push this forward. Thank you for your comments, Alon Bar-Lev. BTW: If someone what to step forward and maintain gnupg, I will be most happy! But this derives maintaining all g10 Code GmbH software, as they are closely related. dev-libs/libgcrypt dev-libs/libksba dev-libs/libgpg-error app-crypt/pinentry dev-libs/libassuan app-crypt/dirmngr app-crypt/gpgme And probably more. On 12/8/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > Hello, > > I want to make gnupg-2 stable. > > The problem is that gnupg-1.9 was slotted as slot "1.9" and made stable. > > So now we have two slots, slot "0" and slot "1.9". > > gnupg-2 is drop-in replacement of gnupg-1, so eventually no slotting > should be used. > > As far as I see, there are two migration pathes I can use: > > 1. Mark gnupg-2 stable, as it blocks older versions, this results in > forcing users to manually unmerge the gnugp-1.9 series, this is the > quickest and simplest migration path. > > 2. Perform slot-move of slot "0" and slot "1.9" into slot "2", so > migration will be smooth. The problem is that I need all archs to work > with me in timely manner so that this will be possible. I have > bug#194113 waiting for arm, mips, s390, sh, and this only for the > dependencies. > > Any thoughts? > > Best Regards, > Alon Bar-Lev. > -- [EMAIL PROTECTED] mailing list
