Re: Newbie: Installing Build Dependencies to gnupg-2.2.13 update from gnupg 2.0.22 on Ubuntu 14.04 LTS failed

[Daniel]

On 13.03.19 18:24, Peter Lebbing wrote:

On 13/03/2019 14:21, David wrote:

If someone posts hundreds of kilobytes or more, I agree,
but in this case I argue the opposite, for these reasons.

I fully agree. In fact, I much prefer someone include a lot of
information and maybe include too much than that the person trying to
help has to ask for more information. The one thing that would have made
the mail even better was if shell output was put between markers like
this:

--8<---cut here---start->8---
Terminal contents
--8<---cut here---end--->8---

Some mail clients auto-format this, which makes the e-mail more
readable, but even without special formatting it helps a /lot/ with the
flow.


4) it avoids running pastebin javascript.

In fact, Werner refuses to look at pastes on sites that require
JavaScript. That means you lose out on the expertise of the person who
knows the most about GnuPG! :-)

7) This is an FSF mailing list. Solely relying on libre services is much
preferred in any case. Suggesting people use non-free software quickly
ends up in the "not allowed here" territory!

Back on topic, I /do/ completely agree with Oscar Carlsson that it is
rather futile to compile stuff for an OS that will be unsupported in a
few weeks. Running an unsupported OS should not be done in almost every
instance. Running security software like GnuPG on an unsupported OS is
an enormous red flag and defeats the purpose of GnuPG IMNSHO.

My 2 cents,

Peter.

PS: I found it ironic that the person admonishing someone to be concise
was the one who forgot to trim the quotes per list rules :-P. This is
tongue in cheek and should not be taken seriously.

---


Dear Peter, dear Dave

Much thanks for your advice regarding my post, as well as your insight 
on the breached security issues using an unsupported OS. If I may ask 
you again how your input was meant dear Peter, I should add code inline 
in the future like so(?):


--8<---cut here---start->8---
dm@dm-ThinkPad-X240:/boot$ sudo apt-get autoremove linux-image-3.13.0-96-generic
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  linux-image-3.13.0-96-generic linux-image-extra-3.13.0-96-generic
  linux-signed-image-3.13.0-96-generic
0 upgraded, 0 newly installed, 3 to remove and 4 not upgraded.
After this operation, 195 MB disk space will be freed.
Do you want to continue? [Y/n]
--8<---cut here---end--->8---

Again thank you for your reply, you've all been very helpful and I 
appreciate it greatly.


Sincerely,

daniel


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


--
pgp fingerprint: 02EF 1CA4 A4FB 0F12 76CA BC08 B678 C658 9B03 AB5E

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

Re: Newbie: Installing Build Dependencies to gnupg-2.2.13 update from gnupg 2.0.22 on Ubuntu 14.04 LTS failed

[Peter Lebbing]

On 13/03/2019 14:21, David wrote:
> If someone posts hundreds of kilobytes or more, I agree,
> but in this case I argue the opposite, for these reasons.

I fully agree. In fact, I much prefer someone include a lot of
information and maybe include too much than that the person trying to
help has to ask for more information. The one thing that would have made
the mail even better was if shell output was put between markers like
this:

--8<---cut here---start->8---
Terminal contents
--8<---cut here---end--->8---

Some mail clients auto-format this, which makes the e-mail more
readable, but even without special formatting it helps a /lot/ with the
flow.

> 4) it avoids running pastebin javascript.

In fact, Werner refuses to look at pastes on sites that require
JavaScript. That means you lose out on the expertise of the person who
knows the most about GnuPG! :-)

7) This is an FSF mailing list. Solely relying on libre services is much
preferred in any case. Suggesting people use non-free software quickly
ends up in the "not allowed here" territory!

Back on topic, I /do/ completely agree with Oscar Carlsson that it is
rather futile to compile stuff for an OS that will be unsupported in a
few weeks. Running an unsupported OS should not be done in almost every
instance. Running security software like GnuPG on an unsupported OS is
an enormous red flag and defeats the purpose of GnuPG IMNSHO.

My 2 cents,

Peter.

PS: I found it ironic that the person admonishing someone to be concise
was the one who forgot to trim the quotes per list rules :-P. This is
tongue in cheek and should not be taken seriously.

-- 
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

Re: Newbie: Installing Build Dependencies to gnupg-2.2.13 update from gnupg 2.0.22 on Ubuntu 14.04 LTS failed

[David]

On Wed, 27 Feb 2019 at 23:16, Oscar Carlsson via Gnupg-users
 wrote:
>
> And in future emails, try to [...] use pastebin like
> services and/or attach logs instead of adding them inline like this.

Why is that suggested?

If someone posts hundreds of kilobytes or more, I agree,
but in this case I argue the opposite, for these reasons.
Providing the information inline has several advantages:
1) all information is available in one place.
2) it's easy to quote/reference in email replies.
3) it's less work for the responders who don't have to cut
and paste from other places.
4) it avoids running pastebin javascript.
5) it preserves the integrity of the email archive, so that the
conversation can help future readers, particularly when pastebin sites
are ephemeral and/or provide only temporary storage.
6) some mailing lists strip attachments.

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

Re: Newbie: Installing Build Dependencies to gnupg-2.2.13 update from gnupg 2.0.22 on Ubuntu 14.04 LTS failed

[Oscar Carlsson via Gnupg-users]

2019-02-26 21:37 skrev Daniel:

dear members of gnupg-users,

prolog:

hello my name is daniel. if i may introduce myself, i'm not an
entirely sophisticated or seasoned unix/linux user and usually
dependend on whatever snippets of information i can find in forums and
on the web that give me usually a ballpark idea of what i can or
cannot do via the command line. i understand that this approach
doesn't always make sense or seems abit farfetched to the more
experienced programmer. that said, i recently learned when trying to
update my outmoded gnupg 2.0.22 on my Ubuntu 14.04 LTS distro, that i
ran into some major issues for which i'm currently looking for advice
on how to resolve them and get my update to work. so, if there's
anyone who has the patience and the time necessary to give this
problem a fair introspection, your help would be greatly appreciated.
thanks.

the deal:

trying to install gnupg-2.2.13 on Ubuntu 14.04 LTS, including build
dependencies libgpg-error-1.35, libgcrypt-1.8.4, libassuan-2.5.3,
libksba-1.3.5, npth-1.6, pinentry-1.1.0 & gpg-agent

history/approach:

largely dependend on the information i deployed from a website called
https://gist.github.com/vt0r/a2f8c0bcb1400131ff51

i tried and followed the instructions there blindly, save for a few
alterations. 1. for instance i wrote (copy/paste) each line of code
separately for each building routine, instead of using &&. 2. I also
did a detailed log of each command (copy/paste) that I ran on the
shell in gedit, for each building block, including error messages that
I got in return. 3. instead of https://www.gnupg.org/ftp/gcrypt/ as
the mainsource from which to recover the tarball, I used for instance
$ sudo wget -c 
ftp://ftp.gnupg.org/gcrypt/pinentry/pinentry-1.1.0.tar.bz2


as the protocol on the website suggest, i first cleaned up the older
GNuPG 2.0.22 build, by sudo apt-get --purge remove gnupg2
mistakenly, I also removed gnupg-agent at first, because I thought it
also took an updated version. however re-installed gnupg-agent at a
later point in the process, when my enigmail add-on to thunderbird,
seemed to have trouble making the connection.

the next step I created directory /var/src/gnupg22 with mkdir.

the contents of var/src/gnupg22 currently look like this:

daniel@daniel-ThinkPad-X240:/var/src/gnupg22$ ls
gnupg-2.2.10.tar.bz2 libgcrypt-1.8.4.tar.gz.sig
gnupg-2.2.10.tar.bz2.sig libgpg-error-1.32.tar.gz
gnupg-2.2.13 libgpg-error-1.32.tar.gz.sig
gnupg-2.2.13.tar.bz2 libgpg-error-1.35
gnupg-2.2.13.tar.bz2.sig libgpg-error-1.35.tar.gz
index.html   libgpg-error-1.35.tar.gz.sig
libassuan-2.5.1.tar.bz2  libksba-1.3.5
libassuan-2.5.1.tar.bz2.sig  libksba-1.3.5.tar.bz2
libassuan-2.5.3  libksba-1.3.5.tar.bz2.sig
libassuan-2.5.3.tar.bz2  npth-1.6
libassuan-2.5.3.tar.bz2.sig  npth-1.6.tar.bz2
libgcrypt-1.8.3.tar.gz   npth-1.6.tar.bz2.sig
libgcrypt-1.8.3.tar.gz.sig   pinentry-1.1.0
libgcrypt-1.8.4  pinentry-1.1.0.tar.bz2
libgcrypt-1.8.4.tar.gz   pinentry-1.1.0.tar.bz2.sig

I did check and verify each signature of the respective tarball file!

installation procedure:

then I ran in the same order as on the website the complete
/.configure cycle, including

$ ./configure --prefix=/usr
$ make
$ make check
$ sudo make install

for the configuration of pinentry for instance, the return i got was:

Pinentry v1.1.0 has been configured as follows:

Revision:  02df3d2  (735)
Platform:  x86_64-pc-linux-gnu

Curses Pinentry ..: no
TTY Pinentry .: yes
Emacs Pinentry ...: no
GTK+-2 Pinentry ..: yes
GNOME 3 Pinentry .: no
Qt Pinentry ..: no
TQt Pinentry .: no
W32 Pinentry .: no
FLTK Pinentry : no

Fallback to Curses: no
Emacs integration : yes

libsecret : no

Default Pinentry .: pinentry-gtk-2

now for instance if i run: $ aptitude search pinentry-gtk-2

i get no search results in return! same is true for all other build
dependencies (libgpg-error-1.35, libgcrypt-1.8.4, libassuan-2.5.3,
libksba-1.3.5, npth-1.6, pinentry-1.1.0),  including gnupg-2.2.13.

one of the main problems of the build, seemed that libraries like
libgcrypt-1.8.4 couldn't detect it's build dependencies like
libgpg-error-1.35.. so the

$ make check of libgcrypt-1.8.4

returned 27 Test failed!!


the $ make check of libgpg-error-1.35 returned PASS: 
gpg-error-config-test.sh

=
1 test passed;

and
==
All 9 tests passed


and after $ sudo make install: the contents of usr/local/lib currently
looks like this:

daniel@daniel-ThinkPad-X240:/usr/local/lib$ ls
libgcrypt.la libgpg-error.la node_modules  site_ruby
libgcrypt.so libgpg-error.so pkgconfig
libgcrypt.so.20  libgpg-error.so.0   python2.7
libgcrypt.so.20.2.4  libgpg-error.so.0.26.1  python3.4

Newbie: Installing Build Dependencies to gnupg-2.2.13 update from gnupg 2.0.22 on Ubuntu 14.04 LTS failed

[Daniel]

dear members of gnupg-users,

prolog:

hello my name is daniel. if i may introduce myself, i'm not an entirely 
sophisticated or seasoned unix/linux user and usually dependend on 
whatever snippets of information i can find in forums and on the web 
that give me usually a ballpark idea of what i can or cannot do via the 
command line. i understand that this approach doesn't always make sense 
or seems abit farfetched to the more experienced programmer. that said, 
i recently learned when trying to update my outmoded gnupg 2.0.22 on my 
Ubuntu 14.04 LTS distro, that i ran into some major issues for which i'm 
currently looking for advice on how to resolve them and get my update to 
work. so, if there's anyone who has the patience and the time necessary 
to give this problem a fair introspection, your help would be greatly 
appreciated. thanks.


the deal:

trying to install gnupg-2.2.13 on Ubuntu 14.04 LTS, including build 
dependencies libgpg-error-1.35, libgcrypt-1.8.4, libassuan-2.5.3, 
libksba-1.3.5, npth-1.6, pinentry-1.1.0 & gpg-agent


history/approach:

largely dependend on the information i deployed from a website called 
https://gist.github.com/vt0r/a2f8c0bcb1400131ff51


i tried and followed the instructions there blindly, save for a few 
alterations. 1. for instance i wrote (copy/paste) each line of code 
separately for each building routine, instead of using &&. 2. I also did 
a detailed log of each command (copy/paste) that I ran on the shell in 
gedit, for each building block, including error messages that I got in 
return. 3. instead of https://www.gnupg.org/ftp/gcrypt/ as the 
mainsource from which to recover the tarball, I used for instance

$ sudo wget -c ftp://ftp.gnupg.org/gcrypt/pinentry/pinentry-1.1.0.tar.bz2

as the protocol on the website suggest, i first cleaned up the older 
GNuPG 2.0.22 build, by sudo apt-get --purge remove gnupg2
mistakenly, I also removed gnupg-agent at first, because I thought it 
also took an updated version. however re-installed gnupg-agent at a 
later point in the process, when my enigmail add-on to thunderbird, 
seemed to have trouble making the connection.


the next step I created directory /var/src/gnupg22 with mkdir.

the contents of var/src/gnupg22 currently look like this:

daniel@daniel-ThinkPad-X240:/var/src/gnupg22$ ls
gnupg-2.2.10.tar.bz2 libgcrypt-1.8.4.tar.gz.sig
gnupg-2.2.10.tar.bz2.sig libgpg-error-1.32.tar.gz
gnupg-2.2.13 libgpg-error-1.32.tar.gz.sig
gnupg-2.2.13.tar.bz2 libgpg-error-1.35
gnupg-2.2.13.tar.bz2.sig libgpg-error-1.35.tar.gz
index.html   libgpg-error-1.35.tar.gz.sig
libassuan-2.5.1.tar.bz2  libksba-1.3.5
libassuan-2.5.1.tar.bz2.sig  libksba-1.3.5.tar.bz2
libassuan-2.5.3  libksba-1.3.5.tar.bz2.sig
libassuan-2.5.3.tar.bz2  npth-1.6
libassuan-2.5.3.tar.bz2.sig  npth-1.6.tar.bz2
libgcrypt-1.8.3.tar.gz   npth-1.6.tar.bz2.sig
libgcrypt-1.8.3.tar.gz.sig   pinentry-1.1.0
libgcrypt-1.8.4  pinentry-1.1.0.tar.bz2
libgcrypt-1.8.4.tar.gz   pinentry-1.1.0.tar.bz2.sig

I did check and verify each signature of the respective tarball file!

installation procedure:

then I ran in the same order as on the website the complete /.configure 
cycle, including


$ ./configure --prefix=/usr
$ make
$ make check
$ sudo make install

for the configuration of pinentry for instance, the return i got was:

Pinentry v1.1.0 has been configured as follows:

Revision:  02df3d2  (735)
Platform:  x86_64-pc-linux-gnu

Curses Pinentry ..: no
TTY Pinentry .: yes
Emacs Pinentry ...: no
GTK+-2 Pinentry ..: yes
GNOME 3 Pinentry .: no
Qt Pinentry ..: no
TQt Pinentry .: no
W32 Pinentry .: no
FLTK Pinentry : no

Fallback to Curses: no
Emacs integration : yes

libsecret : no

Default Pinentry .: pinentry-gtk-2

now for instance if i run: $ aptitude search pinentry-gtk-2

i get no search results in return! same is true for all other build 
dependencies (libgpg-error-1.35, libgcrypt-1.8.4, libassuan-2.5.3, 
libksba-1.3.5, npth-1.6, pinentry-1.1.0),  including gnupg-2.2.13.


one of the main problems of the build, seemed that libraries like 
libgcrypt-1.8.4 couldn't detect it's build dependencies like 
libgpg-error-1.35.. so the


$ make check of libgcrypt-1.8.4
>>returned 27 Test failed!!

the $ make check of libgpg-error-1.35 returned PASS: 
gpg-error-config-test.sh

=
1 test passed;

and
==
All 9 tests passed


and after $ sudo make install: the contents of usr/local/lib currently 
looks like this:


daniel@daniel-ThinkPad-X240:/usr/local/lib$ ls
libgcrypt.la libgpg-error.la node_modules  site_ruby
libgcrypt.so libgpg-error.so pkgconfig
libgcrypt.so.20  libgpg-error.so.0   python2.7
libgcrypt.so.20.2.4  libgpg-error.so.0.26.