Package Details: rpm-org 4.14.2.1-1

Git Clone URL: https://aur.archlinux.org/rpm-org.git (read-only)
Package Base: rpm-org
Description: RPM Package Manager - RPM.org fork, used in major RPM distros
Upstream URL: http://www.rpm.org/
Licenses: GPL2
Conflicts: rpm, rpmextract
Provides: rpm=4.14.2.1, rpmextract=1.0-4
Submitter: Wintershade
Maintainer: codyps
Last Packager: codyps
Votes: 134
Popularity: 0.175194
First Submitted: 2009-09-20 15:51
Last Updated: 2018-10-24 16:47

Dependencies (10)

Required by (103)

Sources (4)

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 Next › Last »

ruario commented on 2011-01-04 13:38

@torto: You are right that some packages do require it themselves. This is a shame. :(

However on a related note (not really directed at torto, just a thought out loud), if some of the packages actually don't need it themselves and have rpmextract in their build depends (I have seen this in the past), then they are doing it wrong. Tell the maintainers of those PKGBUILDs to stop using rpmextract and just use the native tools included with all Arch installations. I can't see any reason why any PKGBUILD should require rpmextract (unless the package itself needs it). Indeed I would even go so far as to suggest that makepkg should automatically extract the contents of rpm files when they are provided as the source, in the same way it does for tar archives.

Q: How can all Arch installs extract the contents of RPMs?
A: With bsdcpio or bsdtar, i.e. 'bsdtar xf rpmpackage', just like rpmextract.sh does itself (it is only 4 lines long, check it out)

Q: Why are bsdtar and bsdcpio installed on all Arch systems, even slimmed down installs?
A: Because they are provided by libarchive and pacman itself depends on libarchive

$ pacman -Ql libarchive | grep -e bsdtar -e bsdcpio | head -n2
libarchive /usr/bin/bsdtar

$ pacman -Qi pacman | grep "^Depends"
Depends On : bash libarchive>=2.7.1 libfetch>=2.25 pacman-mirrorlist

jonnor commented on 2010-12-19 22:14

The python bindings does not work, as python3 is detected, which the bindings does not support.
Adding "export PYTHON=/usr/bin/python2" to build {} solves this. You should probably change the requires to python2 as well. Thanks!

Wintershade commented on 2010-11-10 12:59

+1

niqingliang2003 commented on 2010-11-10 07:54

to *torto*:
fully agree!

Anonymous comment on 2010-11-09 01:00

I think this should include rpmextract, because some packages require it and it conflicts with rpm-org...
http://aur.pastebin.com/LzWxuqVM

pht's versions patch works great!

PD: why "groups=('base-devel')" ???

olive commented on 2010-11-08 18:13

It is possible to build with the Berkeley database included. It works great this way including the old 4.5 db (it is included in rpm, it does not conflict with an installed db). This solve the build problem without patching. Moreover doing this way make it possible to upgrade the db without rebuilding rpm, which is an advantage.

I included the modified PKGBUILD for this in case someone is interested.

[code]
# Author: Wintershade <Wintershade AT google mail DOT com>
# Contributor: Konrad <konrad AT knauber DOT name>
# Contributor: Luka Perkov <archlinux <at> lukaperkov <dOt> net>

realname=rpm
pkgname=rpm-org
pkgver=4.8.1
pkgrel=9987
pkgdesc="RPM Package manager - the RPM.org fork, used in major RPM distros such as Fedora, Red Hat Enterprise Linux, Novell's openSUSE and SUSE Linux Enterprise, Mandriva and CentOS"
arch=('i686' 'x86_64')
url=("http://www.rpm.org/")
license=('GPL')
groups=('base-devel')
depends=('glibc' 'db>=4.5' 'beecrypt' 'lua' 'zlib' 'file' 'gettext' 'nss' 'nspr' 'gnupg')
makedepends=('pkgconfig' 'python>=2.3')
optdepends=('bzip2: support for bzip2 compression' 'gzip: support for gzip compression' 'xz-utils: support for xz/lzma compression')
conflicts=('rpm' 'rpmextract' 'rpmunpack')
source=(http://rpm.org/releases/rpm-4.8.x/$realname-$pkgver.tar.bz2
http://download.oracle.com/berkeley-db/db-4.5.20.tar.gz)
md5sums=('85b9cabd384ffe47b7c3ffb396133fb1'
'b0f1c777708cb8e9d37fb47e7ed3312d')
build() {
cd $srcdir/$realname-$pkgver
ln -s ../db-4.5.20 db
./configure --localstatedir=/var --prefix=/usr --without-selinux --enable-python CPPFLAGS="`pkg-config --cflags nss`" || return 1
make || return 1
make prefix=$pkgdir/usr localstatedir=$pkgdir/var install
rmdir $pkgdir/var/tmp
}
[/code]

Anonymous comment on 2010-11-05 09:19

The new db 5.x major version fucks up the build.

The following patch upgrades this package to 4.8.1-3 where the build is fixed http://aur.pastebin.com/qk1ujhfV
Until the package maintainer integrates it, just download the tarball and do a patch -p1 <downloadedpatchfile>

I have also submitted a ticket to rpm guys with the fix.

Anonymous comment on 2010-11-03 18:00

This error appears, when I try to compile rpm-org:

backend/db3.c: In Funktion »db_init«:
backend/db3.c:143:31: Fehler: »DB_VERB_CHKPOINT« undeclared (first use in this function)
backend/db3.c:143:31: Anmerkung: each undeclared identifier is reported only once for each function it appears in
backend/db3.c: In Funktion »db3stat«:
backend/db3.c:381:5: Warnung: Übergabe des Arguments 2 von »db->stat« von inkompatiblem Zeigertyp
backend/db3.c:381:5: Anmerkung: expected »struct DB_TXN *« but argument is of type »void **«
backend/db3.c:381:5: Warnung: Übergabe des Arguments 3 von »db->stat« erzeugt Zeiger von Ganzzahl ohne Typkonvertierung
backend/db3.c:381:5: Anmerkung: expected »void *« but argument is of type »unsigned int«
backend/db3.c:381:5: Fehler: Zu wenige Argumente für Funktion »db->stat«
backend/db3.c: In Funktion »db3close«:
backend/db3.c:428:33: Fehler: »DB_VERB_CHKPOINT« undeclared (first use in this function)
make[3]: *** [backend/db3.lo] Fehler 1
make[3]: Leaving directory `/tmp/yaourt-tmp-ace/aur-rpm-org/src/rpm-4.8.1/lib'
make[2]: *** [all] Fehler 2
make[2]: Leaving directory `/tmp/yaourt-tmp-ace/aur-rpm-org/src/rpm-4.8.1/lib'
make[1]: *** [all-recursive] Fehler 1
make[1]: Leaving directory `/tmp/yaourt-tmp-ace/aur-rpm-org/src/rpm-4.8.1'
make: *** [all] Fehler 2

Is there a solution to fix this error?

Wintershade commented on 2010-09-29 08:09

No.

niqingliang2003 commented on 2010-09-29 07:27

does it can coexist with "rpmextract"?