| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was recently re-enabled in commit e2c45e167796ffb6d6d5c21e0fadfec82d2d4ebf
It worked fine on mga9 but it makes several freebsd & mga[3-7] to choke
on that test
perl: rpmal.c:293: rpmalAdd: Assertion `dspool == ((void *)0) || dspool == al->pool' failed.
That assertion was removed in later rpms
The stack trace is:
Program received signal SIGABRT, Aborted.
0x00007ffff7b21a7a in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x00007ffff7b21a7a in raise () from /lib64/libc.so.6
#1 0x00007ffff7b0a524 in abort () from /lib64/libc.so.6
#2 0x00007ffff7b0a40f in __assert_fail_base.cold.0 () from /lib64/libc.so.6
#3 0x00007ffff7b169a2 in __assert_fail () from /lib64/libc.so.6
#4 0x00007ffff788b682 in rpmalAdd () from /lib/../lib64/librpm.so.8
#5 0x00007ffff787c74b in rpmtsCreateAl () from /lib/../lib64/librpm.so.8
#6 0x00007ffff787d99f in rpmtsOrder () from /lib/../lib64/librpm.so.8
#7 0x00007ffff78ddde8 in XS_RPM4__Transaction_transorder (my_perl=<optimized out>, cv=<optimized out>) at RPM4.xs:1718
#8 0x00007ffff7da1b21 in Perl_pp_entersub () from /lib64/libperl.so.5.28
#9 0x00007ffff7d97e16 in Perl_runops_standard () from /lib64/libperl.so.5.28
#10 0x00007ffff7d15a17 in perl_run () from /lib64/libperl.so.5.28
#11 0x000000000040125a in main ()
|
| |
|
|
|
|
|
| |
We cannot free an rpmfi object we just wrapped into a SV
Bug introduced in commit f6d333affb60e5364bf30355869fd359da2317e8
|
|
|
|
| |
Test Te->files btw (which shows it was segfaulting before...)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
"Bug" introduced in commit 66504834514cdf96f5a366864982f0d2a0267ea2 when
introducing the same logic as in URPM
|
| |
|
| |
|
|
|
|
| |
It'll be simpler for next commits
|
| |
|
| |
|
|
|
|
|
| |
Was disabled at least since commit 9e2966a33f9148fdc8ef81783bab1fe18e87bd34
16 years ago
|
|
|
|
|
|
|
|
|
| |
Else traverse() is short-circuited... which breaks the testsuite...
I wonder how the testsuite was working previous to rpm-4.17.0 which
fixed something that exposed that issue.
This test runs smoothly on mga[2-8]
Note for future: traverse() really should be documented...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It's OK on aarch64 & on x86_64 but it's broken on i586
eg:
$ perl -MRPM4
RPM4.c: loadable library and perl binaries are mismatched (got handshake key 0x9100080, needed 0x9180080)
Just build with the flags used to build perl itself in order to fix it
|
| |
|
|
|
|
|
|
|
| |
Was already done in commit d939d0fcd43955f367768b4a0f378e360d6bd3ce
But got dropped in commit 66504834514cdf96f5a366864982f0d2a0267ea2
when switching to ExtUtils::PkgConfig
|
| |
|
|
|
|
|
|
|
|
|
|
| |
force using a version object
rationale:
- 4.12.0.2 < 4.12.90 will wrongly pass
- v4.12.0.2 < 4.12.90 will check as we expect
Thus fixing detecting rpm version so that we do compile with rpm < 4.13
See eg: http://www.cpantesters.org/cpan/report/315efa38-85f8-11ea-adf4-f9341f24ea8f
|
| |
|
|
|
|
| |
Also alter the way we count the plan
|
|
|
|
|
|
|
|
|
|
| |
It's no more needed to list all point version unless there's a change in
them we want to test for (such as 4.12.90)
Thus fixing detecting unlisted rpm versions such as
http://www.cpantesters.org/cpan/report/1d673d18-503a-11ea-8fff-b48f1f24ea8f
where 4.13.0.1 wasn't listed and thus choked on rpm >= 4.15 code path
set by commit 9e3deaefdbc54910d58dea28d06c2678673c9d09
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
thus preventing rpm-4.1[0-2] users to choke on rpmPkgSign
|
| |
|
| |
|
| |
|
|
|
|
| |
in order to investigate some strange compilation failures
|
|
|
|
|
| |
We need to include {cflags} even if empty on Linux as it contains
-I/usr/local/include on eg: FreeBSD
|