On Thu 2024-08-08 20:49:42 +0200, Sébastien Noel wrote:
> Mailvelope has 2 "backends", one is OpenPGP.js, where it works without
> interacting with the local GnuPG install and the keys are stored in the
> browser's local folder. This just works, today, without change in any
> gnupg component.
t
Le 2024-08-08 18:50, Daniel Kahn Gillmor a écrit :
Hi Sébastien--
On Thu 2024-08-08 00:53:04 +0200, Sébastien Noel wrote:
[...]
except for the part where you ask for an analysis, i'm sure I can
answer
to everything else. I will do that promptly.
I hope we can work on the analysis part as wel
Hi Sébastien--
On Thu 2024-08-08 00:53:04 +0200, Sébastien Noel wrote:
> Thank you very much again for taking the time to respond to my offensive
> email that i'm not proud of :/
I appreciate your retraction of the offensive parts of your message. I
understand the frustration (i've been in you
Hi Daniel,
Thank you very much again for taking the time to respond to my offensive
email that i'm not proud of :/
Le 2024-08-07 01:57, Daniel Kahn Gillmor a écrit :
Hi Sébastien--
[...]
I don't understand why you, with your "downstream packager hat", have
to
rethink about that.
As a do
Hi Sébastien--
On Tue 2024-08-06 23:53:21 +0200, Sébastien Noel wrote:
> I acknowledge that the last 5 years have been "bumpy" in the gnupg
> community (omg the certificates flooding incident was that long ago ??
> time flies) and that working with an increasingly hostile upstream
> must be diffic
Le 2024-08-01 08:56, Daniel Kahn Gillmor a écrit :
Hi Sébastian--
I understand your frustration -- it's a frustrating situation.
I've been the only one stepping up to make policy-style changes in the
past several years, and i'm overwhelmed by several things related to
the
json interface:
Hi
Hi Sébastian--
I understand your frustration -- it's a frustrating situation.
I've been the only one stepping up to make policy-style changes in the
past several years, and i'm overwhelmed by several things related to the
json interface:
- the technical complexity of the GnuPG architecture,
-
Le mercredi 17 juillet 2024 à 08:16 +0200, Andreas Metzler a écrit :
>
> Good morning Sébastien,
>
> I can understand your unhappiness but sadly cannot do much alleviate
> it.
>
> Regarding my role in team: I am limiting myself to changes that do
> not
> include policy choices. I cannot take the
On 2024-07-14 Sébastien Noel wrote:
[...]
> You are the first person of the "debian gpg team" (i saw "team upload"
> in the changelog on your latest upload, so i supposed you are part of
> it) to react to this bug in 5 years.
> I will not lie, I'm (like others) pissed off by this situation, where
On Wed, 29 May 2024 19:04:22 +0200 Andreas Metzler
wrote:
> On 2024-05-17 Detlef Eppers wrote:
> [...]
> > So I'm throwing my hat in the ring for gpgme-json :)
> [...]
>
> Given that iirc Ubuntu has gone with gpgme-json we will probably go
> this avenue, when we package it.
>
> cu Andreas
Hi A
On 2024-05-17 Detlef Eppers wrote:
[...]
> So I'm throwing my hat in the ring for gpgme-json :)
[...]
Given that iirc Ubuntu has gone with gpgme-json we will probably go this
avenue, when we package it.
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grat
On Fri, 17 May 2024 11:36:00 + Detlef Eppers
wrote:
> That said: naming is important and naming is hard, but three years
> have passed, and it is my impression that this is getting somewhat
> out of proportion.
+1
i have been building my own gpgme packages for the last 5+ years
because of a
On Fri, 11 Aug 2023 18:16:13 +0200 Norbert Lange
wrote:
On Mon, 16 Jan 2023 02:01:37 +0100 =?ISO-8859-1?Q?=C1ngel?=
wrote:
> I have tested https://salsa.debian.org/debian/gpgme/-/merge_requests/1
> and it works fine.
> I would however name the new package gpgme-json, not libgpgme-bin
>
> The pa
On Mon, 16 Jan 2023 02:01:37 +0100 =?ISO-8859-1?Q?=C1ngel?=
wrote:
> I have tested https://salsa.debian.org/debian/gpgme/-/merge_requests/1
> and it works fine.
> I would however name the new package gpgme-json, not libgpgme-bin
>
> The package is only providing gpgme-json(1). If it is going to sh
I have tested https://salsa.debian.org/debian/gpgme/-/merge_requests/1
and it works fine.
I would however name the new package gpgme-json, not libgpgme-bin
The package is only providing gpgme-json(1). If it is going to ship
more binaries in the future, it can always be replaced. If someone is
told
On Thu 2020-10-01 14:05:59 +0200, Sascha Wilde wrote:
> so far I haven't received any reply to either my pull request or my
> questions in the bug report issue from Fri, 11 Sep 2020 15:38:13 +0200.
>
> I would still appreciate input on my work, especially if there is
> anything I need to do to make
Hello,
so far I haven't received any reply to either my pull request or my
questions in the bug report issue from Fri, 11 Sep 2020 15:38:13 +0200.
I would still appreciate input on my work, especially if there is
anything I need to do to make the changes acceptable for the Debian
package.
Thank
Sascha Wilde writes:
> As a first step I created a merge request to deploy gpgme-json together
> with the library:
> https://salsa.debian.org/debian/gpgme/-/merge_requests/1
After realizing that the current MR breaks multi arch compatibility for
the library I revised it and added a new -bin packa
Hello,
as promised by Bernhard in his mail we stated to work on this again.
As a first step I created a merge request to deploy gpgme-json together
with the library:
https://salsa.debian.org/debian/gpgme/-/merge_requests/1
Next I will look into creating specific packages with browser
manifests..
Hello,
sorry the work from our side got stuck.
We (from Intevation) will be looking into it.
Timeframe: first look next week, fix can take a few more days.
From my rough understanding: The extension ID would need to go into the
personal configuration of the webbrowsers and cannot be configured g
Has there been any progress with this bug?
gpgme-json is already built in the Debian sources, so adding it to a
(possibly separate) binary package should not be a big problem. Are
there tests failing or missing?
Best,
Teemu
21 matches
Mail list logo
