On Dec 9, 2007 9:21 AM, Donnie Berkholz <[EMAIL PROTECTED]> wrote: > On 15:49 Sat 08 Dec , Alon Bar-Lev 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. > > Seems reasonable. Any particular reason to slot gnupg-2 as SLOT 0 rather > than SLOT 1.9?
he end result would be one slot... If I need to chose 1.9 or 0, I prefer the standard is to have slot 0. > > 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. > > I can imagine this resulting in very weird issues, when you have two of > the same package installed in the same slot. What? These are two versions.... If nobody else address this, I will chose the easy way -> option#0. Best Regards, Alon Bar-Lev. -- [EMAIL PROTECTED] mailing list
