GitLab

Integrate the „check“ test suite into the build system. Teach the build
system to run tests, by:
• make test (only the test)
• make valgrind (tests run inside valgrind)
• make check (everything above).

Build the test binaries only when they are needed, not by default.

Just empty Makefiles doing nothing.

As described on the router, not by finding any existing docs or reading
opkg code.

Dump some implementation ideas so they are not lost either.

Write down the requirements as a summary of what was talked about
personally and over the email.

Initialize the build system and create an empty documentation file.

Don't get confused & angry, when the real updater runs and the
updater-resume is started at the same time. This seems to happen when
updater is updated and '/etc/init.d/updater enable' is issued from the
post-inst script on the newest openWRT.

Each instance of passthrough package has its own set of flags, possibly
different from the non-passthrough instance.

The functionality of deleting packages not matching versions got
assigned a flag.

Another flag (for generator passthrough) got assigned. Both flags are
documented.

Don't warn (emit only info message) when the hash checker is not
installed. It still can be installed by the user, but updater won't do
it.

Pick the working version, not the broken one, if there are multiple
possibilities.

The create notification script is only soft dependency of updater, it
should still work without it. So make the errors non-fatal and don't
crash because of it.

It's a temporary solution ‒ we should handle these on the box and we
will do it soon.

Due to a typo & variable name collision, no collision was ever acted
upon, even whet it was detected.

As there are two colliding and we have no immediate solution.

The same package (including version) may have different sets of hashes.
This may happen, for exaple, if the same version is present across
multiple generations. Be able to handle the situation by checking all
possibilities and trying to find one.

• Include empty packages in the output, as they may be needed in to
  describe package that is empty in one generation and non-empty in other.
• Generate hashes for generation 0.
• Merge the generations together to form possibilities of hashes of
  single package.

If something eats a symbolic link, the package needs to be restored as
well. Generate hashes for symbolic links.

So it doesn't crash every time it is called and generates something else
than just empty hash sets.

The new layout has subdirectories, each one containing the Packages
file. We take all of them in such case.

• This will allow to read them from multiple subdirectories.
• Also remember the subdirectory used.

Delete the lock if it is there for too long time.

Uncomment previously commented-out line responsible for cleaning up.
It was commented out for testing purposes and committed by mistake.

This was responsible for broken first-run wizard.

Closes: #4005.