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.
(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,
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
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
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).
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.