Bug 8371 - Argument "48688|24100" isn't numeric in array element at /usr/lib/perl5/vendor_perl/5.14.2/x86_64-linux-thread-multi/URPM/Resolve.pm line 1378.
Summary: Argument "48688|24100" isn't numeric in array element at /usr/lib/perl5/vendo...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-12-12 11:51 CET by claire robinson
Modified: 2013-11-23 16:12 CET (History)
0 users

See Also:
Source RPM: perl-URPM
CVE:
Status comment:


Attachments

Description claire robinson 2012-12-12 11:51:28 CET
Noticed whilst using urpmi --test --debug --auto-select on bug 8164 comment 22

Argument "48688|24100" isn't numeric in array element at
/usr/lib/perl5/vendor_perl/5.14.2/x86_64-linux-thread-multi/URPM/Resolve.pm
line 1378.
Comment 1 claire robinson 2012-12-12 11:52:01 CET
$ rpm -q perl-URPM
perl-URPM-3.40.2-1.2.mga2
Thierry Vignaud 2012-12-12 18:09:44 CET

Priority: Normal => Low
Severity: normal => enhancement

Comment 2 Thierry Vignaud 2012-12-12 21:58:59 CET
It didn't crahed?
Humm...
Can you add the two following lines before line 1379 (the "map..." line):
    use Data::Dumper; warn Dumper \@_;
    use MDK::Common; warn backtrace();

Then run again the same command and attach its output to this bug report?

Keywords: (none) => NEEDINFO
Priority: Low => Normal
Status: NEW => ASSIGNED
Severity: enhancement => normal

Comment 3 Thierry Vignaud 2012-12-12 22:01:11 CET
Even better: run the following commands then send me the resulting bug8371.tar.xz file by mail.

urpmi --test --debug --auto-select --bug bug8371
tar cfa bug8371{.tar.xz,}
Comment 4 claire robinson 2012-12-12 23:28:54 CET
I'm not sure how useful it is Thierry but I've done so. Whatever was wrong before didn't show itself again.

It occurred at a time when an update has a new dependency from core release, something which was causing bug 2317 in the applet. Do you think that was just coincidence?

The links have been made now and updates installed so packages are currently up to date.

It's too big to attach so please find it here:
https://dl.dropbox.com/u/4147101/QA/bug8371.tar.xz
claire robinson 2012-12-12 23:30:26 CET

Keywords: NEEDINFO => (none)

Comment 5 Thierry Vignaud 2012-12-13 10:33:28 CET
Well I'll definitively need a tarball from an environment where you reproduce it.

Keywords: (none) => NEEDINFO

Comment 6 Manuel Hiebel 2013-10-22 12:09:15 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

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 Mageia version prior to Mageia 2'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 Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 7 Manuel Hiebel 2013-11-23 16:12:55 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

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

--
The Mageia Bugsquad

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


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