Re: An attempt at backporting 2.1.16 from Debian sid to Debian jessie

[Stephan Beck]

Peter Lebbing:
> On 08/12/16 21:42, Stephan Beck wrote:
>> [...], so I don't see the real need for a forced coexistence of the two
>> (or three) versions on Jessie.
> 
> I did that because all the software in jessie that depends on GnuPG 1.4
> might not work with GnuPG 2.1. So by doing it like this, I'm not
> breaking any packages that have the package "gnupg" in their dependency
> tree.
> 

Yes, I understand, and it's great work! I just wanted to say that I,
personally, don't see the need since I upgraded to a 2.1 only installation.

Cheers

Stephan




signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: An attempt at backporting 2.1.16 from Debian sid to Debian jessie

[Peter Lebbing]

On 08/12/16 21:42, Stephan Beck wrote:
> [...], so I don't see the real need for a forced coexistence of the two
> (or three) versions on Jessie.

I did that because all the software in jessie that depends on GnuPG 1.4
might not work with GnuPG 2.1. So by doing it like this, I'm not
breaking any packages that have the package "gnupg" in their dependency
tree.

Cheers,

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: An attempt at backporting 2.1.16 from Debian sid to Debian jessie

[Peter Lebbing]

I discovered I accidentally wasn't allowing public access to the
repository. I've fixed this and you can now download from:

https://gitlab.com/DigitalBrains1/alt-debian-gnupg2

The offending setting seemed to have been:

Feature Visibility
- Repository
  Push files to be stored in this project

Now I thought setting this to "Everyone" would allow anyone to push
files to the project, which seemed like a truly horrendous feature.
Apparently, it allows pushes/files to be visible?

Peter.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: An attempt at backporting 2.1.16 from Debian sid to Debian jessie

[Stephan Beck]

Teemu Likonen:
> Peter Lebbing [2016-12-08 18:12:50+01] wrote:
> 
>> I forked the Debian git repo for GnuPG 2.1 [1], and had a go at what
>> was primarily the reversal of the changes introduced by 2.1.11-7+exp1.
>> You can find the result at GitLab at [2].
> 
> Thanks. I'm not brave enough to try it yet. I wonder what is the status
> of official backport. There's a Debian bug report about that:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822974

A few days ago, I successfully updated to 2.1.16 on my Debian Stretch
installation, watching how gpg (1.4.20something) was being replaced with
2.1.16, so I don't see the real need for a forced coexistence of the two
(or three) versions on Jessie. Maybe I'll cast a glance at it, though.

Cheers

Stephan



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

Re: An attempt at backporting 2.1.16 from Debian sid to Debian jessie

[Teemu Likonen]

Peter Lebbing [2016-12-08 18:12:50+01] wrote:

> I forked the Debian git repo for GnuPG 2.1 [1], and had a go at what
> was primarily the reversal of the changes introduced by 2.1.11-7+exp1.
> You can find the result at GitLab at [2].

Thanks. I'm not brave enough to try it yet. I wonder what is the status
of official backport. There's a Debian bug report about that:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822974

Quote 2016-10-06:

It'll happen soon, i promise :)

  --dkg

-- 
/// Teemu Likonen   - .-..    //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///


signature.asc
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users

An attempt at backporting 2.1.16 from Debian sid to Debian jessie

[Peter Lebbing]

Hello dkg and list!

Let me start out by thanking Daniel Kahn Gillmor for all his work on GnuPG and
its Debian packages. And also thanks to all the other devs!

I'd like to use the latest GnuPG 2.1 on my Debian jessie machines. When the
Debian package went from version 2.1.11-7 to 2.1.11-7+exp1, it started providing
/usr/bin/gpg and the other stuff that was up till then provided by GnuPG 1.4.
Starting with stretch, if all works out, GnuPG 1.4 will no longer be providing
the major role it had in Debian so far.

I forked the Debian git repo for GnuPG 2.1 [1], and had a go at what was
primarily the reversal of the changes introduced by 2.1.11-7+exp1. You can find
the result at GitLab at [2].

I'm running this version myself now, and it all works so far (famous last 
words...).

I'm giving you all the loaded gun to shoot yourself in the foot. I do not
recommend my fork for general use, but rather as a service to people who really
want 2.1 and are prepared to deal with issues arising from having both 1.4 and
2.1 on the same system.[3]

I'm very interested in feedback! I'd like it if people check my changes, do they
seem okay to you? Did you run into issues? I'd also like to hear from people
succesfully using it, but don't feel obliged to tell me.

If you feel I shouldn't be doing this, we could discuss it further. Maybe we can
work out a deterring formulation for the README to prevent people installing it
:-). Or you convince me of my folly.

This version will replace jessie's 2.0.26 with 2.1.16, but it will install next
to GnuPG 1.4. However, mixing 1.4 and 2.1 is not for the faint of heart. There
are good reasons that dkg is choosing not to support 1.4 and 2.1 on the same
machine starting with Debian stretch: while on the surface they are compatible,
they quickly go out of sync regarding private keys and it can get interesting
with public keys as well. "Interesting" as in "May you live in interesting
times". not as in "Hey, that's interesting!"... that is, not a good thing at 
all.

*Use at your own risk! This is provided as-is without any warranties.*

I tried my best, but sometimes, your best isn't good enough... ;)

Oh, and I'm already behind. The latest and greatest is now 2.1.16-3, and I'm
still providing 2.1.16-2~dbbp8+1 [4].

Cheers,

Peter.


[1] https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git

[2] https://gitlab.com/DigitalBrains1/alt-debian-gnupg2

[3] Hey, that's pretty good, I'll put that in the README.

[4] I means: Digital Brains BackPort Debian 8.x version 1. Same numbering scheme
as backports.org, different identifier.

-- 
I use the GNU Privacy Guard (GnuPG) in combination with Enigmail.
You can send me encrypted mail if you want some privacy.
My key is available at 



signature.asc
Description: OpenPGP digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users