The release managers are actually supposed to maintain the filter list
in unneeded.yml, but that only applies to unsorted.yml not to the unsorted.group
(which is basically unfiltered to be published into OBS's SLE-15)
Since both pkglistgen and repo_checker share the same rpm metadata cache
either may update it first and thus bs_mirrorfull will only contain output
for one of the tools. As such the check in pkglistgen could cause the solv
file to remain stale. Instead write a secondary file containing the
repository state hash and check to see if the file already exists.
Distinct copyrights were left as I do not wish to track down commit
history to ensure it properly documents the copyright holders. Also left
non-GPLv2 licenses and left bs_copy untouched as a mirror from OBS.
Already have a mix of with and without headers and even OBS does not place
on majority of files. If SUSE lawyers have an issue it will come up in
legal review for Factory.
As the remote config is no longer optional for SLE and is utilized by
openSUSE to the point were it is dangerous not to load the remote config
it should be required. Currently only certain users call apply_remote()
while this will make it built-in during construction and thus makes the
usage consistent and no longer require StagingAPI.
For some yet to be determined reason, the namespaceprovider does not
pick up package that just provide eg. locale(ja). So find and and log
them (boo#1092055)
It's similiar but not the same as the droplist for openSUSE, so I created
a fork of the openSUSE command
To be called with the target project as first argument and then a
list of old projects
e.g. create_sle_weakremovers SUSE:SLE-15:GA SUSE:SLE-12-SP3:GA \
SUSE:SLE-12-SP3:Update SUSE:SLE-12-SP2:GA SUSE:SLE-12-SP2:Update ...
That check is aiming to check request rather than package, for release package
we indeed had multispecs and multibuild file together, just do not run
local service when committing to release package.
Ended up consistently creating a short XML file that created a null section
in solv file that cause pkglistgen drop list generator to create a <NULL>
drop entry.
Always flush() before you read(). :(
It certainly would have been nice if libsolv would have complained about
an invalid XML file rather than just producing garbage as the file just
ended. Then of course mergesolv did not complain and comes back in to
python as '<NULL>'. Failure to validate and multiple levels.
