| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This means we can do stuff like moving /etc/os-release into /usr/lib
and leaving a compatibility symlink where the file was.
Previously baserock-system-config-sync would fail with the following:
ERROR: found two different types for 'os-release': regular and
symlink
One of the 'failure' test cases now passes, and I've added a specific
test for our 'os-release' case to the 'symblinks' test case too.
|
| |
|
|
|
|
|
| |
Since with 'system-version-manager' is possible to change
the default system, 'baserock-system-config-sync' shouldn't
get the default system, and get an extra parameter to choose
the system version to merge.
|
| |
|
|
|
| |
If a file was removed in vUser, and v2 doesn't have a new one,
then the file is not longer needed.
|
| | |
|
| |
|
|
|
| |
'baserock-system-config-sync' is doing reverse patching when
that happens. This test is to check the expected behaviour.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
baserock-sytem-config-sync:
Changes here are caused by a bug found in GNU patch
managing the permissions of the files when using the
patch command like:
patch <file_to_apply_patch> -t -o <output_file>
To reproduce the bug:
echo foo > file1
echo bar > file2
diff -u file1 file2 | patch 1 -t -o file3
ls -l
You can check that the permissions of 'file3' are different
than the permissions of 'file1' or 'file2'.
To avoid the bug, this patch changes the way we are using
patch, using it as following:
patch <file_to_apply_patch> -t
Since the output file is not specified, the output file will
be the file in which we want to apply the patch. And
due we cannot specify the output file, we are copying
the file to the destination directory, and then applying
the patch there.
As a consequence of changing the way of using patch, now
'patch' generates an extra file when patching fails. This
file is added in the test suite also in this commit.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Disabled (renamed) old tests that have been converted
Removed compilation instruction for symtime.c from README
|
| |
|
|
|
|
|
| |
directory
Or else the test using extended attributes will fail because extended
attributes are not supported in tmpfs.
|
| |
|
|
|
|
|
|
|
| |
Tests will now be handled by a test suite in a future commit, so this
mode will not be needed anymore. The test suite will work by replacing
the mounting script by a fake mounting script that points to a directory
with a systems folder.
Also add trap again, now that it is more tested.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit converts tbdiff to being an autotools-based project. This
means that we now support the usual
autoreconf -i && ./configure && make && make install
process, plus we provide 'make check' for the tbdiff test suite.
The tbdiff library is now build as a shared library and is also
installed into the system for others to use. The library is
libtool-versioned and ships a pkg-config file (tbdiff-1.pc).
The headers were adjusted so that only tbdiff/tbdiff.h may be included
directly; all others are considered internal. The tbdiff-create and
tbdiff-deploy tools were changed to include this header file.
The tbdiff library is still GPL, not LGPL. We might want to change this
in the future.
Thanks to switching to autotools we now have a way to make releases by
means of 'make dist' and 'make distcheck'. Unfortunately, the latter
currently fails, probably due to something being missing in
tbdiff/Makefile.am.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Fixed inconsequential memory leak in tbdiff_create.c
Lost memory would be cleaned up by OS at exit, but valgrind complains
|
| |
|
|
|
|
| |
directories can be inserted, to ensure mtime is not equal
now dir_add_remove fails because the mtime of the directory
changed after a file in it was altered
|
| |
|
|
|
|
|
|
|
|
|
| |
Actually it was losing all metadata other than that which changed
metadata was lost when the file was removed, but only the data
that changed was applied
the fix is to ignore the metadata diff mask as all the data is
written to the binary diff, however it needn't be, so if it gets
fixed to only send what changed, the metadata will have to be
read before the file is recreated and the metadata changed based
on what was sent in the binary diff
|
| |
|
|
|
| |
The corrected test also fails, however, so I guess I was right
about there being a bug, though that is coincidental.
|
| |
|
|
|
| |
added test for group changes in symlinks
symlinks change the group of what is referenced
|
| |
|
|
| |
directory would remove the directory
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
tbdiff-create will print a suggested fix
Made check_command shell function able to use any type of command
for return value checking
Fixed minor bugs in TBD_ERROR macro not being used for some errors
|
| |
|
|
|
|
|
|
|
|
| |
So expected failures can be made by comparing the return code to the expected
Also socket tests have been added, add and diff expect create to fail for now
The only sensible operation on sockets is to remove them as they need a
program to bind them and that program (or a child) needs to be a server
So tbdiff should fail if it has to perform such an act.
It may be worth having an option to ignore the change, but for now it's better
to fail and let the user know why so they can fix it
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The temporary test directory is now made using mktemp -d instead of using uuid
mktemp comes with coreutils, uuid does not, and mktemp makes the directory for
you.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
