lib/rpmliblua.c | 1 1 + 0 - 0 !
luaext/lposix.c | 1 1 + 0 - 0 !
luaext/lrexlib.c | 1 1 + 0 - 0 !
rpmio/rpmlua.c | 1 1 + 0 - 0 !
4 files changed, 4 insertions(+)

 avoid undefined functions with lua 5.2

python/Makefile.am | 12 6 + 6 - 0 !
1 file changed, 6 insertions(+), 6 deletions(-)

 avoid linking with libpython
    This only introduces (useless) dependency on all supported python
    versions, while the linking itself is not needed.

autodeps/kfreebsd.prov | 61 61 + 0 - 0 !
autodeps/kfreebsd.req | 135 135 + 0 - 0 !
2 files changed, 196 insertions(+)

 add kfreebsd support

autodeps/gnu.prov | 61 61 + 0 - 0 !
autodeps/gnu.req | 135 135 + 0 - 0 !
2 files changed, 196 insertions(+)

 add hurd support

installplatform | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 verbose installplatform
    Just make installplatform to ease debugging problems with creatin platform files.

macros.in | 4 3 + 1 - 0 !
1 file changed, 3 insertions(+), 1 deletion(-)

 move default rpmdb path to user home

configure.ac | 2 2 + 0 - 0 !
lib/poptI.c | 5 5 + 0 - 0 !
lib/rpmprob.h | 3 2 + 1 - 0 !
rpmqv.c | 8 8 + 0 - 0 !
4 files changed, 17 insertions(+), 1 deletion(-)

 rpm is not default package manager on debian
 In Debian, rpm should be used to install packages, but rather as a tool to
 work with rpm packages or as a helper in alien. Because of this we protect
 complain, when user tries to install a package. This warning can be hidden 
 by --force-debian.

Makefile.am | 6 3 + 3 - 0 !
doc/manual/builddependencies | 2 1 + 1 - 0 !
macros.in | 2 1 + 1 - 0 !
platform.in | 2 1 + 1 - 0 !
4 files changed, 6 insertions(+), 6 deletions(-)

 fix installation directories
 - Do not install rpm to /bin/.
 - Setup default directories so that source RPMs rebuilt on Debian get
   the right directories and also that builds occur in /usr/src/rpm
 - Fix statedir and init.d patch

scripts/vpkg-provides.sh | 24 12 + 12 - 0 !
1 file changed, 12 insertions(+), 12 deletions(-)

 use the debian standard (and safe) mechanism of generating temporary files

autodeps/linux.req | 4 2 + 2 - 0 !
1 file changed, 2 insertions(+), 2 deletions(-)

 no linux-gate.so dependency
 If we rebuild an rpm, don't generate a dependancy on linux-gate.so as
 that is a virtual shared library generated by 2.6 kernels so that can
 decide upon the best mechanism to transition from user to kernelspace

autogen.sh | 24 24 + 0 - 0 !
1 file changed, 24 insertions(+)

 delete some crap after running autogen.

configure.ac | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 in debian, lua library is called lua5.2.

lib/depends.c | 107 106 + 1 - 0 !
1 file changed, 106 insertions(+), 1 deletion(-)

 add fedora compatible rpm builtin provides

configure.ac | 4 2 + 2 - 0 !
python/Makefile.am | 2 1 + 1 - 0 !
2 files changed, 3 insertions(+), 3 deletions(-)

 fix python include issues due to multiarch.
 .
 rpm (4.10.1-2.1ubuntu1) raring; urgency=low
 .
  * debian/patches/fix-python-multiarch-include.patch:
    Fix python multiarch include issue that causes FTBFS.

build/parseReqs.c | 7 5 + 2 - 0 !
1 file changed, 5 insertions(+), 2 deletions(-)

 reduce the double separator spec parse error into a warning (#1065563)

See https://bugzilla.redhat.com/show_bug.cgi?id=1065563

lib/cpio.c | 3 3 + 0 - 0 !
1 file changed, 3 insertions(+)

 limit the length of the file name to a reasonable value
 It was found that RPM could encounter an integer overflow, leading to
 a stack-based overflow, while parsing a crafted CPIO header in the
 payload section of an RPM file.  This could allow an attacker to
 modify signed RPM files in such a way that they would execute code
 chosen by the attacker during package installation.

lib/fsm.c | 7 6 + 1 - 0 !
1 file changed, 6 insertions(+), 1 deletion(-)

 create the file with mode 0
 It was found that RPM wrote file contents to the target installation
 directory under a temporary name, and verified its cryptographic
 signature only after the temporary file has been written
 completely. Under certain conditions, the system interprets the
 unverified temporary file contents and extracts commands from
 it. This could allow an attacker to modify signed RPM files in such a
 way that they would execute code chosen by the attacker during
 package installation.