| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Accidentally dropped in 02f1f851
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
There were 2 bugs:
- getting the architecture got broken due to a missing %
- name of the binary package instead of the src was used, somethimes
they are different
|
|
|
|
|
|
|
| |
All these point to valid https: resources, but there is a small chance
that some unusual interaction will cause it not to work. Some of these
changes also won't take effect until the server is restarted, so we'll
need to keep this in mind if failures occur long from now.
|
|
|
|
| |
These are for use by humans only.
|
|
|
|
|
|
|
| |
The test jobs seem to be working as desired, so make them actually
start deleting the old files every 4 hours. Use -ignore_readdir_race in
all of them to avoid errors when schedbot cleans the files in the middle
of a run (an unlikely situation because of the clean-up times involved).
|
| |
|
|
|
|
|
|
|
| |
Even if 9/nonfree/backports_testing/ hasn't had any builds recently, it
shouldn't be deleted. Only delete directories deeper in the hierarchy.
Follow-up to f7e017e8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's now confirmed that tidy() has been creating huge (2.6 GiB) state
files that the Puppet agent loads before every agent run, which causes
runs to take up to 4 days each and use of all RAM on the server.
Cleaning files using find is more straightforward and efficient and
avoids this problem.
The tidy() functions are disabled here and the cron jobs aren't actually
deleting files yet, so a follow-up commit will enable deleting
imminently, once testing shows it will work.
Follow-up to 59d57245
|
|
|
|
|
|
|
| |
The Puppet method for doing this seems to be what's causing its memory
usage to reach the size of the physical RAM in the system and take up to
4 days to complete a Puppet run. The test will show the files being
deleted and how long it takes, but won't actually delete them.
|
|
|
|
|
|
|
| |
Sometimes someone moves a package manually and we end up with several
versions of a package.
In this case we should delete the src.rpm and handle its binary
packages like if it was gone.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It did not really wait for 7d for removed subpackages.
Also remove an incorrect condition, src.rpm is usually slightly older
that binary rpms, and fix the tests.
|
| |
|
| |
|
|
|
|
|
|
| |
Add timeout for qtwebengine6 ( I used the same as qtwebengine5)
Remove for eclipse and java-1.8.0-openjfx, we do not have then in mageia
anymore
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
That test would pass even without the fix as it would be considered
that the package hasn't been rebuilt for this arch yet.
The bug could only happen when there was also another subpackage
remaining.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
It was checking if there is another version of the src, but using
the name of the package instead of the name of the src, and those
are usually different in the case we care most about (libraries).
|
| |
|
|
|
|
|
|
|
| |
urpmf --qf '%filename:%buildarchs:%buildtime' shifts fields when buildarchs is empty:
python-sphinxcontrib-svg2pdfconverter-0.1.0-2.mga8.src.rpm:noarch:1564917727
python-argon2_cffi-19.1.0-1.mga8.src.rpm:1564918990:
|
| |
|
| |
|
|
|
|
| |
This time it really looks like what I had tested...
|
| |
|
|
|
|
|
| |
Previous commit broke it but is was not visible initially due to another
broken thing in the config which has since been fixed.
|
|
|
|
|
|
|
|
|
| |
We use the same access list for all versions of the distribution
on the HTPP server (our internal machines) so there is no reason
to duplicate it per distro.
This also allows to access files at the top level directory (like
mageia_timestamp).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
rationale:
it badly broke installing some packages with rpm-4.16 which add provides
for every generated package to the SRPM
See https://rpm.org/wiki/Releases/4.16.0
Basically reverting commit cc1079609497da5d5700e27f1076d57bf2b9282c and
its 2 followup fixups
|
| |
|
| |
|
|
|
|
| |
it regularly fails on armv7
|