Bug#911189: gpgme-json packaging

2024-05-29 Thread Andreas Metzler
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

Bug#911189: gpgme-json packaging

2024-05-24 Thread Sébastien Noel
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

Bug#911189: gpgme-json packaging

2024-05-17 Thread Detlef Eppers
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

Bug#911189: gpgme-json packaging

2023-08-11 Thread Norbert Lange
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

Bug#911189: gpgme-json packaging

2023-01-15 Thread Ángel
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

Bug#911189: gpgme-json packaging

2020-10-15 Thread Daniel Kahn Gillmor
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

Bug#911189: gpgme-json packaging

2020-10-01 Thread Sascha Wilde
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

Bug#911189: gpgme-json packaging

2020-09-11 Thread Sascha Wilde
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

Bug#911189: gpgme-json packaging

2020-09-09 Thread Sascha Wilde
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

Bug#911189: gpgme-json packaging

2020-09-02 Thread Bernhard Reiter
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

Bug#911189: gpgme-json packaging

2020-02-22 Thread Teemu Ikonen
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