IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Previously, if the package in 'new' repo had larger version,
it was still called ORANGE. It was "optimization" from
the times when we had only sisyphus_mipsel, and never
packaged newer versions before the main repo. But for
p9_mipsel that's not true, as well as when comparing
p9_mipsel and sisyphus_mipsel, which we also would
like to do.
For now, we just load src/pkglists and build a simple
report on what packages you have to have in order
to satisfy SRPM's build requires. Everything is
very approxymate, of course.
... based on the file path.
Sometimes info.json is moved before the state
is set to DONE. we need to fix this in girar, but for now
we opt for a simpler workaround.
... to get all the ENVRs of the packages it has.
Now comparing different arches of the same repo
is not important, and Sisyphus deperecated
source pkglists, so we can use the official
information source.
Previously, BY_NAME did not include packages that were
absent from both repositories. This meant that some functions
like `gspi` ignored them, which is inconvenient because
it does not show packages that were never built (like new
kernel flavors) or already deleted.
This commit addresses this in the following way:
- colorize.colorize() now takes additional argument,
an explicit list of package names to colorize
- for interactive console, this list is formed from
both repositories, AND all the package names found
in PACKAGE_TASKS.
Sometimes, when lists are updated while we are
reading them, we get 0 results, and all our
reports become very confusing. This change
adds a check to raise an exception in this case.
This function displays subtasks of the tasks
that would update packages in the target repo.
It is especially useful for determining why
the particular task gets into next_tasks(...)
output.
Implementing it nicely required a bit of refactoring
to factor out certain parts of colorizing
and display mech.
A simple tool that compares dependencies of binary
packages in two repositories. For packages with
matching NEVR, it shows where their dependencies
differ, possibly hinting at the need to rebuild
one package or another.
It's hard to do 100% correctly, but the heuristics we
employ here works quite well for now: when a package
was rebuild by base repo (Sisyphus) after we've updated
it last time, we probably need to rebuild it.
This change adds new report, update_days, that nicely
displays how many days ago a package was updated. This
report is now available in interactive mode and included
into daily report.
tasks.py is now capable of using a dict id => task_info
as a cache; if task is already there and is recent
enough, we don't have to re-read its metadata.
