Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
- With the new warning on failure to open selinux labels from
commit 7a8b75d26605cf7a3fde9f624a80d6fb8390fcbd, the test-suite
fails on large number of tests due to the extra output. This
takes care of these false alarms on F16 at least.
- Recent selinux wants /etc/selinux and /sys (for /sys/fs/selinux),
older ones would want /selinux. Add in /proc for good measure,
selinux doesn't need it butit wont hurt either, other things will
want it sooner or later.
|
|
Partially resolves ticket #851.
|
|
- The two "hello" binaries packages used for various multilib checks were
accidentally using xz payload compression, causing test-suite to
fail when rpm was configured without xz support. Rebuild them with gzip
compression instead to avoid silly failures - gzip compression
support is mandatory, xz is not.
|
|
- Includes a test suite for the case.
Signed-off-by: Panu Matilainen <pmatilai@redhat.com>
|
|
- The current method that --requires and friends use is kinda
cumbersome and outputs extra whitespace for dependencies which
dont have flags+version attached. Adding extensions for this
is likely to be easier than teaching query formatting to
permit conditionalizing on current value instead of just tag existence.
|
|
- For a more consistent experience wrt all the state-awareness stuff,
this needs to be easily querifiable too.
- Also makes the tagnames kludgery from commit
cac8c389607d7a5735b2905035fdfe4404670d06 unnecessary
|
|
|
|
- Only allow [[-]<number>] in the format field, users have no business
telling which format conversion sprintf() should use for tag data.
Fixes embarrassing segfaults from things like %s{size} which rpm
has merrily passed on to sprintf() as-is.
|
|
|
|
- Prior to previous patch this segfaulted and tracebacked...
|
|
- Similarly to python file object having o.name, export Fdescr()
as fd.name. Python uses <foo> for non-paths but [foo] seems like
a safer choice wrt accidental redirections.
- Also add a basic testcase for fd.name
|
|
|
|
|
|
|
|
- parseForAttr() doesn't know whether it's dealing with a directory or
a file, so it can't know which defaults it should use.
Move all the decision making on which of the explicit/default/implicit
attributes into addFile() where we do know what kind of entry we're
dealing with, and only parse in parseForAttr().
- Update the test-case status to expect success now.
|
|
- Currently this fails expectedly due to RhBug:681540 on the last
directory of the test rpm.
|
|
|
|
- This would've caught the breakage introduced in commit
7e4415fcc5e11cfd4cd9d0dfe19568be73f15d74, but better late than never...
|
|
- Handle double [] "escaping" at RPM_PYRUN to avoid surprises when
its used on its own
- Spin python-wrapped AT_CHECK into a macro of its own (RPMPY_CHECK)
- What formerly was RPMPY_CHECK is now RPMPY_TEST: this represents
one entire testcase with all its setup and cleanup, whereas
RPMPY_CHECK (the new one) might be used several times within a
single test
|
|
|
|
- Actually verify we got the expected result, ie exactly one instance
of the pkg installed after successful reinstall.
|
|
|
|
- Testcase for the file state consideration implemented in commit
566a15c9c08aa593d05e2f55f1c171a48bc1b1bc
|
|
- Add colored binary packages (as there's no guarantee we can build
them from test-suite), test that colored conflicts get resolved
to preferred color.
|
|
- Except for four rpmbuild tests which rely on an actual compiler
being available (faking *that* would get entertaining...), the entire
test-suite is now executing everything in the fakechroot environment.
|
|
- Build needs a whole bunch of utilities there, including file + its
magic database. The exact location of the magic db varies between
systems but file -C lets us basically make a copy of the system magicdb
into the fakechroot env and then we can override the location with MAGIC
|
|
- This leaves only the "real" builds where the packages contain files
to be executed outside fakechroot
|
|
- All the packages here have no files making them "easy" to build
inside the chroot
|
|
- Running builds in fakechroot needs a whole lot of things.. add symlinks
to various system config + dev files to give some trivial packages
a chance to build under fakechroot
|
|
|
|
- Since they're running in fakechroot there's no need to arrange
user writable directories this way
|
|
- Executing rpmbuild in the fakeroot gets fairly tricky, especially
for the tests that actually compile things. Overriding the dbpath
prevents it from accessing system rpmdb for keyring and build-requires.
- With this patch, the test-suite now passes the smoke-test of
"chmod go-rx /var/lib/rpm" on system rpmdb.
|
|
- We can't run python easily in the chroot so override the dbpath
to our test area instead of potentially accessing the system db
for keyring etc
|
|
- Otherwise various places will be emitting "generating xx missing indexes"
warnings, we dont want that noise in the test-suite results
|
|
- Everything in the test-suite except rpmbuild execution is now
performed in the fakechroot environment
|
|
|
|
- We'll need shell and various other bits in order to do many
things wrt specs and builds in the root...
|
|
- one of the manifest tests is failing mysteriously in root mode though..
|
|
|
|
|
|
|
|
- We could just ditch the entire buildroot lines from the specs
but leaving one case to test that we dont actually fail on specs
that do have it.
|
|
|
|
- Remove duplicate --version checks (doh) and some commented out
build tests that are unlikely to ever be implemented in reality
|
|
- The idea behind the patch is that a missing release is handled
as "all/any release". Nothing changes for "foo < 1.2" or
"foo > 1.2", it still just compares the version. But "foo = 1.2"
means "everything with version 1.2". Thus, any match against
a package with version "1.2" a any non-empty release must
return true.
- Update test-suite expectations to the new behavior.
Signed-off-by: Panu Matilainen <pmatilai@redhat.com>
|
|
- Turns out this change does more harm than good, people are actually
relying on this behavior to avoid zillion conditionals in the spec.
We'll want a saner way to conditionally disable/enable packages
but until we have that, revert to the former longstanding behavior.
- This effectively reverts commit d010ec1c9026b35f5b2521be965c03c826894ce8
|
|
|