Bug 1215287

Summary: [Patch] Make dpkg-perl an arch-specific package
Product: [Fedora] Fedora Reporter: Michael Kuhn <suraia>
Component: dpkgAssignee: Andrew Colin Kissa <andrew>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: andrew, sergio, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dpkg-1.16.16-5.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-08 07:44:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Make dpkg-perl an arch-specific package none

Description Michael Kuhn 2015-04-24 22:50:48 UTC
Created attachment 1018639 [details]
Make dpkg-perl an arch-specific package

Description of problem:
dpkg-perl's files are actually arch-specific (currently noarch); this causes several changelog-related tools to not work.

/usr/share/perl5/vendor_perl/Dpkg.pm contains the following line on my x86_64 system:
  our $dpkglibdir="/usr/lib/dpkg";

This line should contain lib64 instead and is actually set correctly at dpkg build time. However, the noarch package is built on an 32-bit system and is thus wrong for 64-bit ones.

Simply changing the dpkg-perl package to be arch-specific fixes the problem.


Version-Release number of selected component (if applicable):
dpkg-perl.noarch  1.16.16-3.fc22  @System


How reproducible:
Try to use debchange or dpkg-parsechangelog and notice the following error: "changelog format debian is unknown"


Actual results:
Changelog tools do not work.


Expected results:
Changelog tools do work.

Comment 1 Sergio Basto 2015-04-25 13:18:01 UTC
(In reply to Michael Kuhn from comment #0)
> Created attachment 1018639 [details]
> Make dpkg-perl an arch-specific package
> 
> Description of problem:
> dpkg-perl's files are actually arch-specific (currently noarch); this causes
> several changelog-related tools to not work.
> 
> /usr/share/perl5/vendor_perl/Dpkg.pm contains the following line on my
> x86_64 system:
>   our $dpkglibdir="/usr/lib/dpkg";
> 
> This line should contain lib64 instead and is actually set correctly at dpkg
> build time. However, the noarch package is built on an 32-bit system and is
> thus wrong for 64-bit ones.
> 
> Simply changing the dpkg-perl package to be arch-specific fixes the problem.
> 
> 
> Version-Release number of selected component (if applicable):
> dpkg-perl.noarch  1.16.16-3.fc22  @System
> 
> 
> How reproducible:
> Try to use debchange or dpkg-parsechangelog and notice the following error:
> "changelog format debian is unknown"

Hi, thanks for report and testing , actually I changed that recently because I can't built it on epel6 

in dpkg-1.16.15-2.fc21 we got : 

our $dpkglibdir="/usr/libexec/dpkg";

I will try correct this by reverting what I done 

Thanks,

Comment 2 Fedora Update System 2015-04-25 15:17:25 UTC
dpkg-1.16.16-4.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/dpkg-1.16.16-4.fc22

Comment 3 Fedora Update System 2015-04-26 03:20:36 UTC
dpkg-1.16.16-5.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/dpkg-1.16.16-5.fc22

Comment 4 Fedora Update System 2015-04-27 08:41:45 UTC
Package dpkg-1.16.16-5.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dpkg-1.16.16-5.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-6974/dpkg-1.16.16-5.fc22
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2015-05-08 07:44:56 UTC
dpkg-1.16.16-5.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.