Subject: rpm -i should not need --force-debian for source packages
Package: rpm
Version: 4.7.2-1+b1
Severity: normal
When I try to unpack a source package, this happens:
wraith:/tmp$ rpm -i gnome-panel-2.24.1-2.27.1.src.rpm
rpm: please use alien to install rpm packages on Debian, if you are really sure use --force-debian switch. See README.Debian for more details.
This seems wrong to me. Obviously I shouldn't try to install binary
packages like this, but for a source package, rpm -i is roughly equivalent
to dpkg-source -x, both perfectly reasonable things to do on a non-native
system. README.Debian doesn't contain any suggestion of why unpacking
source packages should be a problem, and even comments on where they'll be
unpacked to.
I think the "rpm" command should only refuse to install a package if it
isn't a source package.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.27.9 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages rpm depends on:
ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libelf1 0.143-1 library to read and write ELF file
ii libnss3-1d 3.12.5-1 Network Security Service libraries
ii libpopt0 1.15-1 lib for parsing cmdline parameters
ii librpm0 4.7.2-1+b1 RPM shared library
ii librpmbuild0 4.7.2-1+b1 RPM build shared library
ii librpmio0 4.7.2-1+b1 RPM IO shared library
ii perl 5.10.1-8 Larry Wall's Practical Extraction
ii rpm-common 4.7.2-1 common files for RPM
ii rpm2cpio 4.7.2-1+b1 tool to convert RPM package to CPI
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
rpm recommends no packages.
Versions of packages rpm suggests:
ii alien 8.79 convert and install rpm and other
pn elfutils <none> (no description available)
pn rpm-i18n <none> (no description available)
-- debconf information:
* rpm/upgrade-failed:
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
