| 1 |
Since no flames were started over something technical. Let me see if I |
| 2 |
can toss in some gasoline and get the bonfire going. |
| 3 |
|
| 4 |
On Sun, 2007-05-27 at 23:30 +0200, Jakub Moc wrote: |
| 5 |
> William L. Thomson Jr. napsal(a): |
| 6 |
> > This has sparked the following open bugs, and countless more closed |
| 7 |
> > ones :( |
| 8 |
> > |
| 9 |
> > http://bugs.gentoo.org/show_bug.cgi?id=153496 |
| 10 |
> > http://bugs.gentoo.org/show_bug.cgi?id=160302 |
| 11 |
> > http://bugs.gentoo.org/show_bug.cgi?id=164523 |
| 12 |
> > http://bugs.gentoo.org/show_bug.cgi?id=171871 |
| 13 |
> > |
| 14 |
> > Probably more open bugs, those are just what I stumbled across while |
| 15 |
> > looking for OTHER things :) |
| 16 |
> |
| 17 |
> M'kay... about 3 gnome apps have issues w/ gnupg-2. |
| 18 |
|
| 19 |
Question is, is that the root of the problem? If you look into the |
| 20 |
situation, you will see it's mostly a problem of gpgme <-> gnupg. |
| 21 |
|
| 22 |
http://bugs.gentoo.org/show_bug.cgi?id=164523 |
| 23 |
Comment 104 |
| 24 |
Update: |
| 25 |
[1] https://bugs.g10code.com/gnupg/issue772 |
| 26 |
[2] http://lists.gnupg.org/pipermail/gnupg-devel/2007-February/023676.html |
| 27 |
|
| 28 |
Should have been solved in gnupg-2.0.4, it may help with progress. |
| 29 |
|
| 30 |
Notice should, and that both links deal with gpgme, NOT SEAHORSE or |
| 31 |
anything gnome related. Which gpgme and gnupg have basically the same |
| 32 |
upstream. Who has made vague comments about it working for them. Despite |
| 33 |
reports from others about problems.T here still is not a 100% solution |
| 34 |
from upstream between gpgme <-> gnupg. |
| 35 |
|
| 36 |
> Seriously, I could |
| 37 |
> care less; their problem. |
| 38 |
|
| 39 |
Yes, and because of the word Gnome being included, you are overlooking |
| 40 |
the important details that matter. In which it's not a Gnome problem at |
| 41 |
all :) |
| 42 |
|
| 43 |
The gnome apps like Seahorse talk to gpgme, not gnupg directly. That's |
| 44 |
were the problem lies. |
| 45 |
|
| 46 |
> Maybe upstream will wake up sometimes, |
| 47 |
|
| 48 |
Yes gnupg/gpgme upstream. Not Gnome or other apps that are downstream |
| 49 |
from them. |
| 50 |
|
| 51 |
> or |
| 52 |
> what's the horrible issue with porting those, |
| 53 |
|
| 54 |
Port to what? |
| 55 |
|
| 56 |
> beyond 'oh we don't care, |
| 57 |
|
| 58 |
That should be you don't care. Users do care, if you notice the |
| 59 |
different people commenting on the different bugs. |
| 60 |
|
| 61 |
> use gnupg-1 because the legacy feeling is oh so great'? |
| 62 |
|
| 63 |
It's not just about legacy. gnupg-2 is not a COMPLETE replacement. There |
| 64 |
are FEATURES of gnupg-1. Upstream is still developing and supporting |
| 65 |
gnupg-1. So how is that legacy? |
| 66 |
|
| 67 |
Not to mention clearly stating gnupg-1 has benefits when used with |
| 68 |
gnupg-2. Not to mention server side and embedded uses. |
| 69 |
|
| 70 |
None of those features or benefits has anything to do with Gnome. That's |
| 71 |
about choice, and we aren't giving the user one. |
| 72 |
|
| 73 |
So here we are going on close to 6 months with no resolution. Which |
| 74 |
includes gnupg-2 not being stabilized. I fail to see how any of this is |
| 75 |
positive or progress. |
| 76 |
|
| 77 |
-- |
| 78 |
William L. Thomson Jr. |
| 79 |
Gentoo/Java |
Archives