Bug 7399 - lynx in cauldron segfaults. I have a new one built
Summary: lynx in cauldron segfaults. I have a new one built
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Barry Jackson
QA Contact:
URL:
Whiteboard: OK
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-08 08:08 CEST by Joseph Wang
Modified: 2012-10-09 16:29 CEST (History)
2 users (show)

See Also:
Source RPM: lynx-2.8.7-4.mga1
CVE:
Status comment:


Attachments
lynx spec for 2-8-8 (5.77 KB, text/x-rpm-spec)
2012-09-08 10:00 CEST, Joseph Wang
Details
lynx 2-8-8 patch needed for uploaded lynx (2.54 KB, patch)
2012-09-08 10:01 CEST, Joseph Wang
Details | Diff

Description Joseph Wang 2012-09-08 08:08:29 CEST
Description of problem:

lynx in cauldron segfaults.  I've build a new SRPMS with 2.8.8 that works fine.  I've added my name to the packagers wiki, and I just need a mentor to contact me at (joequant@gmail.com) to tell me what I should do next.


Version-Release number of selected component (if applicable):


How reproducible:

install lynx
it fails

Steps to Reproduce:
1.
2.
3.
Comment 1 Manuel Hiebel 2012-09-08 09:56:43 CEST
(feel free to attach the spec here)

Keywords: (none) => Junior_job, PATCH
CC: (none) => mageia
Source RPM: lynx2.8.7-4.mga1 => lynx-2.8.7-4.mga1
Severity: critical => major

Comment 2 Joseph Wang 2012-09-08 10:00:25 CEST
Created attachment 2767 [details]
lynx spec for 2-8-8
Comment 3 Joseph Wang 2012-09-08 10:01:55 CEST
Created attachment 2768 [details]
lynx 2-8-8 patch needed for uploaded lynx
Comment 4 Joseph Wang 2012-09-08 10:03:03 CEST
spec and patch files attached the one patch obsoletes the 2.8.7 one

there is another patch in 2.8.7 that I removed because upstream had fixed the issue
Comment 5 Barry Jackson 2012-10-09 02:25:43 CEST
Thanks Joseph for your efforts.
I have committed a new version, however it fails to build in i586.
The x86_64 version is fine. If you have any ideas please let me know.

The BS log for i586 is here:-
http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20121008232719.barjac.valstar.1202/log/botcmd.1349738896.ecosse.log

For comparison my local iurt build of x86_64 is here:-
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/lynx-2.8.8-0.dev.8.mga3.src.rpm/build.0.20121008235020.log

The current svn is here:-
http://svnweb.mageia.org/packages/cauldron/lynx/current/

Barry

Keywords: Junior_job, PATCH => (none)
Status: NEW => ASSIGNED
CC: (none) => zen25000
Assignee: bugsquad => zen25000
Whiteboard: (none) => OK

Comment 6 Barry Jackson 2012-10-09 10:52:39 CEST
I have tried going back to dev.3 and also non-parallel build.
Same error.
Comment 7 Joseph Wang 2012-10-09 11:14:44 CEST
I can't see any obvious problems.  

I'm trying to do a local cross-compiler i586 build, but I don't know how to set up rpmbuild to do that.
Comment 8 Barry Jackson 2012-10-09 11:53:17 CEST
I use iurt - the same way the BS does it with a local mirror. It creates a clean chroot and installs a base system plus the BuildRequires.
You don't *have* to use a local mirror though to use iurt, there is urpmi-proxy which keeps a local copy of just what you use. I have never tried it but many use it regularly.
Are you on irc? #mageia-mentoring ?
Comment 9 Barry Jackson 2012-10-09 16:04:20 CEST
I just realized that I had the wrong source tarball - I have now uploaded the dev.14 version and switched back to your original config.patch (I wondered why it didn't apply).

Bad news is that it will still only build in x86_64, which runs fine.
Still the same build error in i586:-
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/i586/log/lynx-2.8.8-1.dev.14.mga3.src.rpm/build.0.20121009134335.log
Comment 10 Barry Jackson 2012-10-09 16:29:31 CEST
\o/
Found it!
revision log tells all ;)

Thanks again Joseph, another package working again :)

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


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