rpm5 lacks a SRPM deliverable for CentOS 5

Yoper has a rpm-5.2.2 packaged up here:
    http://ftp.yoper-linux.org/pub/yoper/pkg/SRPMS.rocketfuel/rpm-5.2.2-5.src.rpm
Adjusting for CentOS now ...

... package builds and is rather "forward" looking and featureful. Cool!

But that means its gonna take a bit to do the Yoper -> Centos
configuration change.

Source/binary packages are on harwich if you want soonestly. I'd suggest
being lazy instead ... ymmv.

something wrong here -- possibly a yoper'ness ?

[herrold@python26-32 rpm5]$ rpm -Uvh rpm-5.2.2-5.src.rpm
error: Failed dependencies:
        g++ is needed by rpm-5.2.2-5.i686
        linux-libc-headers is needed by rpm-5.2.2-5.i686
        automake is needed by rpm-5.2.2-5.i686
        perl-devel >= 5.12.1 is needed by rpm-5.2.2-5.i686
        python-devel >= 2.7 is needed by rpm-5.2.2-5.i686
        popt-devel >= 1.16 is needed by rpm-5.2.2-5.i686
        elfutils-devel >= 0.148 is needed by rpm-5.2.2-5.i686
        libxml2-devel >= 2.7.7 is needed by rpm-5.2.2-5.i686
        file-devel is needed by rpm-5.2.2-5.i686
        keyutils-devel >= 1.4 is needed by rpm-5.2.2-5.i686
        lua-devel is needed by rpm-5.2.2-5.i686
        beecrypt-devel is needed by rpm-5.2.2-5.i686
        rpm = 4.4.2.3-20.el5_5.1 is needed by (installed) rpm-libs-4.4.2.3-20.el5_5.1.i386
        rpm = 4.4.2.3-20.el5_5.1 is needed by (installed) rpm-python-4.4.2.3-20.el5_5.1.i386
        rpm = 4.4.2.3-20.el5_5.1 is needed by (installed) rpm-build-4.4.2.3-20.el5_5.1.i386
        /bin/rpm is needed by (installed) policycoreutils-1.33.12-14.8.el5.i386
[herrold@python26-32 rpm5]$

SRPMs should not Require much at all to unpack

sure LOOKS like a SRPM

[herrold@python26-32 rpm5]$ rpm -qlp rpm-5.2.2-5.src.rpm
rpm-5.2-2010-10-19.tar.xz
rpm-5.2-no-parentdir-deps.diff
rpm-5.2-no-symlink-deps.diff
rpm-5_2-beecrypt+lgomp.diff
rpm-bootstrap-build.sh
rpm-bootstrap-install.sh
rpm-bootstrap-prep.sh
rpm-brp-yoper
rpm-test-1.diff
rpm.spec
rpm5-arch-macros-amd64-linux
rpm5-arch-macros-athlon-linux
rpm5-arch-macros-i386-linux
rpm5-arch-macros-i486-linux
rpm5-arch-macros-i586-linux
rpm5-arch-macros-i686-linux
rpm5-arch-macros-ia32e-linux
rpm5-arch-macros-ia64-linux
rpm5-arch-macros-pentium3-linux
rpm5-arch-macros-pentium4-linux
rpm5-arch-macros-x86_64-linux
rpm5-macro-changes-yoper
[herrold@python26-32 rpm5]$

Patience grasshopper ;-)

(chirp) (chirp) go the crickets

BTW, you were seeing the RPMTAG_SOURCERPM incompatibility --

that SRPM was headed for an rpmdb, not just "unpacking".

Also: harwich has _MOST_ of the dependencies & stuff fixed. What I cannot
say anything about is the content yet.

* nod * I figured it was some tag incompatibility and wanted to flag it

Um its not an incompatibility, but rather a
   Have it your own way!
choice how Yoper decided to build rpm-5.2.2 SRPM's.

And its rpm-4.4.2.3 in CentOS that isn't flagging the incompatibility.
Wot's a grrl to do?!?

We simply haven't discovered yet, how to disable the dependencies on source rpms. Its not intentional and if someone knows how to disable it , I'd be quite grateful for an hint. To maintain an upgrade path we've manually switched the binary_payload of the packages mandatory for the rpm5 upgrade path to gzip (%define _binary_payload w9.gzdio) .

The other mandatory bit is this :

#disable PROT_READ to have a viable upgrade path coming from rpm 4.4.5
#thx to jbj for the hint
sed -i -e '
/^static int _rpmmi_usermem/ c\
static int _rpmmi_usermem = 0;
' rpmdb/rpmdb.c

Forgot the details of why though .

Tobia: for context ...

If you can believe it, there's no rpm.spec file that exists for _ANY_ version
of @rpm5.org code atm, largely because of policy decisons to distribute
only tar balls and be "vendor neutral"

The yoper rpm.spec is the best I've seen: it's "forward" looking and featureful
and recent. Yes, there's some sereious hacks, but that's @rpm5.org's fault,
not yours or Yoper's. I can/will fix up the rpm-5.2.2 tarball too.

The yoper.spec file will then be used to deploy rpm 5.2.2/5.3.5 under a buildbot
farm currently at http://eastham.rpm5.org:8010. I tried (but not too hard yet)
to get Yoper into the build farm, but the Live CD install into VMFusion did
not reboot (unity live-cd install had same issue, I've just forgotten the fix)).

Russ: rpm-5.2.2/rpm.spec.in is building for me on harwich

Tobias: getting yoper -- either as a VM or a chroot -- underneath buildbot's
is close to the top of my todo++ stack. The issue is that the cat likes the "mag-safe"
power cord on my wee little MacBookPro and so he keep yanking the cord,
taking out 4+ VM's (all of which need manual VM and buildbot restart) nightly.
Sigh, oh well ...

Russ: rpm-5.3.5/rpm.spec.in checkin is now nearly as "good enuf" as rpm-5.2.2.

Tobias: still todo++. The cat is prehensile, I will be there shortly ..