Trouble installing Version 2.1 on Debian Jessie

[zap]

You should use debian stretch if you want 2.1


but I also say that you should install lxde first if you use the rc2
installer which is what I used.


because mate install causes wifi to be nonexistant if you install that
first.

If you install stretch that is...

and yes, stretch is extremely stable for me.

but I Would reinstall from scratch after saving your important files to
something.


On 04/30/2017 12:03 AM, Rex Kneisley wrote:
> Hello All,
>
> I'm trying to install version 2.1 the "Debian way".
>
> According to dkg's web-log entry titled "GnuPG 2.1.0 in debian
> experimental"
>
> I should use experimental.
>
> so I added the experimental repository:
> # Experimental repository - main, contrib and non-free branches
> deb http://http.us.debian.org/debian experimental main non-free contrib
> deb-src http://http.us.debian.org/debian experimental main non-free
> contrib
>
> Created an apt preferences file
> /etc/apt/preferences.d/my_preferences
> with:
> Package: *
> Pin: release a=stable
> Pin-Priority: 700
>
> Package: *
> Pin: release a=testing
> Pin-Priority: 650
>
> Package: *
> Pin: release a=experimental
> Pin-Priority: 625
>
>
> Package: *
> Pin: release a=unstable
> Pin-Priority: 600
>
> ran:
> sudo apt-get update
> checked priorities with:
> rexk at debian-pc:~$ sudo apt-cache policy gnupg
> gnupg:
>   Installed: 1.4.18-7+deb8u3
>   Candidate: 1.4.18-7+deb8u3
>   Version table:
>      2.1.20-3 0
>         625 http://http.us.debian.org/debian/ experimental/main amd64
> Packages
>      2.1.18-6 0
>         650 http://http.us.debian.org/debian/ testing/main amd64 Packages
>         600 http://http.us.debian.org/debian/ unstable/main amd64 Packages
>  *** 1.4.18-7+deb8u3 0
>         700 http://ftp.us.debian.org/debian/ jessie/main amd64 Packages
>         100 /var/lib/dpkg/status
>      1.4.18-7+deb8u2 0
>         700 http://security.debian.org/ jessie/updates/main amd64 Packages
>
> and finally ran the commands:
> cp -aT .gnupg .gnupg.bak
> sudo apt install -t experimental gnupg2 gnupg-agent dirmngr gpgsm gpgv2 scdaemon
>
> which produced the following results:
> Reading package lists... Done
> Building dependency tree      
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  dirmngr : Depends: libassuan0 (>= 2.4.0) but 2.1.2-2 is to be installed
>            Depends: libgcrypt20 (>= 1.7.0) but 1.6.3-2+deb8u2 is to be
> installed
>            Depends: libgnutls30 (>= 3.5.6) but it is not going to be
> installed
>            Depends: libksba8 (>= 1.3.4) but 1.3.2-1+deb8u1 is to be
> installed
>            Recommends: gnupg (= 2.1.20-3) but 1.4.18-7+deb8u3 is to be
> installed
>  gnupg-agent : Depends: libassuan0 (>= 2.3.0) but 2.1.2-2 is to be
> installed
>                Depends: libgcrypt20 (>= 1.7.0) but 1.6.3-2+deb8u2 is
> to be installed
>  gnupg2 : Depends: gnupg (>= 2.1.20-3) but 1.4.18-7+deb8u3 is to be
> installed
>  gpgsm : Depends: libgcrypt20 (>= 1.7.0) but 1.6.3-2+deb8u2 is to be
> installed
>          Depends: libksba8 (>= 1.3.4) but 1.3.2-1+deb8u1 is to be
> installed
>  gpgv2 : Depends: gpgv (>= 2.1.20-3) but 1.4.18-7+deb8u3 is to be
> installed
>  scdaemon : Depends: libassuan0 (>= 2.2.0) but 2.1.2-2 is to be installed
>             Depends: libgcrypt20 (>= 1.7.0) but 1.6.3-2+deb8u2 is to
> be installed
>             Depends: libksba8 (>= 1.3.4) but 1.3.2-1+deb8u1 is to be
> installed
> E: Unable to correct problems, you have held broken packages.
>
> Was I missing a step?
>
> Any help would be appreciated.
>
>
> -- 
> Sincerely,
>
>
> Rex Kneisley
>
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20170430/f1e8e883/attachment-0001.html>