Bug 14122 - 5a2: unsatisfied perl(extra) for dpkg-1.17.13-2.mga5.x86_64
Summary: 5a2: unsatisfied perl(extra) for dpkg-1.17.13-2.mga5.x86_64
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-19 04:01 CEST by Bit Twister
Modified: 2014-09-24 13:05 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2014-09-19 04:01:22 CEST 
Description of problem:

Some requested packages cannot be installed:
dpkg-1.17.13-2.mga5.x86_64 (due to unsatisfied perl(extra))

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


How reproducible: Always


Steps to Reproduce:
1. urpmi --downloader wget --auto --auto-update
2.
3.


Reproducible: 

Steps to Reproduce:
Thierry Vignaud 2014-09-19 12:05:06 CEST

CC: (none) => thierry.vignaud
Summary: 5a2: unsatisfied perl(dumpvar.pl) for dpkg-1.17.13-2.mga5.x86_64 => 5a2: unsatisfied perl(extra) for dpkg-1.17.13-2.mga5.x86_64

Comment 1 Thierry Vignaud 2014-09-19 12:06:45 CEST 
The following would do it:
%global __requires_exclude perl\\(extra\\)
Comment 2 Thierry Vignaud 2014-09-19 19:20:07 CEST 
Fixed.

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

Comment 3 Bit Twister 2014-09-20 17:22:32 CEST 
(In reply to Thierry Vignaud from comment #2)
> Fixed.

Hope it is ok to re-open this until I can get the fix downloaded.

A requested package cannot be installed:
dpkg-1.17.13-2.mga5.x86_64 (due to unsatisfied perl(extra))
Maybe it will clear up when the rebuild gets through the perl* rpms.

I will resolve this bug when I get a clean update.

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

Comment 4 Thierry Vignaud 2014-09-24 13:05:36 CEST 
fixed+

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.