1 |
Hello, |
2 |
|
3 |
I selected the blocker option, forcing users to unmerge gnupg-1.9. |
4 |
Users that used only 1.9 slot, will be notified later by revbumping this slot. |
5 |
|
6 |
I am truly sorry for bothering users, but this is the only way to push |
7 |
this forward. |
8 |
|
9 |
Thank you for your comments, |
10 |
Alon Bar-Lev. |
11 |
|
12 |
BTW: If someone what to step forward and maintain gnupg, I will be most happy! |
13 |
But this derives maintaining all g10 Code GmbH software, as they are |
14 |
closely related. |
15 |
dev-libs/libgcrypt |
16 |
dev-libs/libksba |
17 |
dev-libs/libgpg-error |
18 |
app-crypt/pinentry |
19 |
dev-libs/libassuan |
20 |
app-crypt/dirmngr |
21 |
app-crypt/gpgme |
22 |
|
23 |
And probably more. |
24 |
|
25 |
On 12/8/07, Alon Bar-Lev <alonbl@g.o> wrote: |
26 |
> Hello, |
27 |
> |
28 |
> I want to make gnupg-2 stable. |
29 |
> |
30 |
> The problem is that gnupg-1.9 was slotted as slot "1.9" and made stable. |
31 |
> |
32 |
> So now we have two slots, slot "0" and slot "1.9". |
33 |
> |
34 |
> gnupg-2 is drop-in replacement of gnupg-1, so eventually no slotting |
35 |
> should be used. |
36 |
> |
37 |
> As far as I see, there are two migration pathes I can use: |
38 |
> |
39 |
> 1. Mark gnupg-2 stable, as it blocks older versions, this results in |
40 |
> forcing users to manually unmerge the gnugp-1.9 series, this is the |
41 |
> quickest and simplest migration path. |
42 |
> |
43 |
> 2. Perform slot-move of slot "0" and slot "1.9" into slot "2", so |
44 |
> migration will be smooth. The problem is that I need all archs to work |
45 |
> with me in timely manner so that this will be possible. I have |
46 |
> bug#194113 waiting for arm, mips, s390, sh, and this only for the |
47 |
> dependencies. |
48 |
> |
49 |
> Any thoughts? |
50 |
> |
51 |
> Best Regards, |
52 |
> Alon Bar-Lev. |
53 |
> |
54 |
-- |
55 |
gentoo-dev@g.o mailing list |