Bug 784455 - "make check" of gnutls library 2.12.14 fails on fully patched Fedora 16
Summary: "make check" of gnutls library 2.12.14 fails on fully patched Fedora 16
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnutls
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-25 01:15 UTC by Michal Ambroz
Modified: 2013-02-13 23:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 23:42:34 UTC
Type: ---


Attachments (Terms of Use)
rebuild_gnutls-2.12.14-1.txt (243.48 KB, text/plain)
2012-01-25 01:15 UTC, Michal Ambroz
no flags Details
rebuild_gnutls-2.12.7.2.txt (289.31 KB, text/plain)
2012-01-25 01:16 UTC, Michal Ambroz
no flags Details
pkg_diff.txt (7.94 KB, text/plain)
2012-01-26 03:40 UTC, Michal Ambroz
no flags Details

Description Michal Ambroz 2012-01-25 01:15:56 UTC
Created attachment 557347 [details]
rebuild_gnutls-2.12.14-1.txt

Description of problem:
make check of gnutls library fails on fully patched Fedora 16 (i686).
I believe this might be one of the sources for issues I am experiencing with the gnutls library in relation to openvas-cli interface to openvas-manager (omp_authenticate function from openvas-libraries).


Version-Release number of selected component (if applicable):
gnutls-2.12.14-1.fc16.i686


How reproducible:
100%

Steps to Reproduce:
1. Have a 32 bit Fedora 16
2. yum -y update
3. rpmbuild --rebuild 
  
Actual results
make check part reports a lot of errors.

Expected results:
make check should be clean

Additional info:
make check shows errors for 2.12.7-2 (from release) and for 2.12.16 (upstream head for 2.12) as well. 

According to Nikos Mavrogiannopoulos <nmav>:
" There is a particular version of gcc that miscompiles libtasn1
and the errors seen look similar to yours. Could you try with
--with-included-libtasn1 flag?"

"I see these are issues in your libgcrypt. It could be also the
same miscompilation issue, but I cannot help you much on that,
except to tell you to report it in the libgcrypt list. I suggest
to use nettle which is the recommended crypto library for gnutls
2.12 and 3.0."

Comment 1 Michal Ambroz 2012-01-25 01:16:58 UTC
Created attachment 557348 [details]
rebuild_gnutls-2.12.7.2.txt

Comment 2 Tomas Mraz 2012-01-25 08:17:02 UTC
Note that the %check passed fine on build of gnutls-2.12.14-1.fc16.i686 package. It is always run during the rpm build in koji.

See:
http://kojipkgs.fedoraproject.org/packages/gnutls/2.12.14/1.fc16/data/logs/i686/build.log

Can you try to rebuild the libtasn1 on your testing machine and upgrade it?

Also we cannot switch to nettle in released Fedora and I don't really know what Nikos means about the issues in the libgcrypt - I do not see much related to libgcrypt in your build logs.

Comment 3 Michal Ambroz 2012-01-26 03:37:28 UTC
Hi Tomas,
yes I have seen the build log already when you released 2.12.14 because I was curious how did you handle it there as I was not successful at that time building 2.12.16. 

I actually tried to rebuild the package when I run into some additional networking problems with openvas. 

I have tried to rebuild both libtasn1 and libgcrypt - both rebuilded, make check was complaining, but package was built.
After forcefull upgrade nothing changed for gnutls - it complains on make check part and fails to build.

I diffed the package versions reported by koji to be installed for the build - 
http://kojipkgs.fedoraproject.org/packages/gnutls/2.12.14/1.fc16/data/logs/i686/root.log
Report shows no major differences (attaching).

What is surprising is that there is actually more differences between the builds - if you search for string gaa you will found some differences as well.

Seems like there is something in my toolchain different than in koji.
I would say "yum -y update" should put us inline and results should be the same, but actually it is not like that.

Comment 4 Michal Ambroz 2012-01-26 03:40:10 UTC
Created attachment 557583 [details]
pkg_diff.txt

This is diff of package versions from koji and from my machine during the build.
On my machine I have got many more packages.

Comment 5 Fedora End Of Life 2013-01-16 20:15:14 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2013-02-13 23:42:37 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.