| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
file back and forth, let's use --buildresult option of pbuilder to put resulted file directly where we want them
|
|
check_suitability() and handle_not_for_us()
|
|
up userContent while starting the build. Also I don't catch anymore race condition where the same package is already building. Marking as FIXME for now
|
|
variable declaration order
|
|
package to get_source_package() and handle_404()
|
|
initialization of the build environment
|
|
variables in a single place
|
|
be build in its own function choose_package()
|
|
strip out print_out_duration()
|
|
always there nowadays
|
|
the file inside
|
|
boring
|
|
use a temp file
|
|
|
|
|
|
subsequently clean up files
the db now stores tuple of (pkgname, suite, architecture) of every removed
packages, then reproducible_maintenance.sh pick up entries from it and
find+remove files.
For now the reproducible_maintenance only output what he would have remove.
|
|
_homl_notes to _html_indexes
|
|
the header line
|
|
|
|
|
|
its own function. it does not make sense to bloat the generic code by special casing it
|
|
|
|
|
|
|
|
|
|
this broke recently, and it start using ANSI_X3.4-1968 (o.O)
|
|
|
|
name/suite/arch returns html
|
|
and not the available version, if the package got already tested
|
|
(also as specified in the sudoers file)
|
|
|
|
should not be there" part to avoid logparse noise
|
|
are scheduled
|
|
chmod them. currently unknown the cause of these bad perms (only for very few files
|
|
noise in the build log)
|
|
|
|
|
|
|
|
|
|
SQL quering for a package to build
|
|
chroot IFF http_proxy is defined
|
|
|
|
didn't complain loudly
|
|
|
|
|
|
link alongside package names
|
|
|
|
issues
|
|
|
|
|