bin/build-packages	10	report back memory and hdd stats to the build master on successful build
bin/build-packages	12	some build failures should skip straws - e.g. if dependencies are unavailable,\\nwe should not try to rebuild with a cleaned chroot
bin/build-packages	15	some build environments should be archived when the build fails - but:\\nwhich/how?
bin/build-packages	18	it might be worth trying to build with makedepends installed from\\n[testing] and only depends installed from [staging]
bin/build-packages	21	the following things need proper locking and/or proper handling of\\nexternal locks:\\n- `git` on the package source\\n- `archbuild` (e.g. /var/lib/archbuilds/staging-i686-build/root.lock)\\n- `find ... -exec umount` on the build chroot
bin/build-packages	27	releave some locking conditions - meta goal: be able to run multiple\\nbuild slaves on one host from within one archlinux32/builder repository
bin/build-packages	30	remove hard-coded package suffixes
bin/build-packages	32	save build-logs in case of success, too - only the build is\\nguaranteed to have been successful, maybe the package is broken.
bin/build-packages	575	get the name of the key file from its finger print or\\nsome other information inside the repository
bin/build-packages	849	symbols may be in object files _inside_archives_\\nIn that case, we're interested in the object file's name,\\nnot the archive's file name
bin/build-packages	975	dependency-adding from make_source_info() should\\nbe replicated here, somehow ...
bin/manage-fail-reasons	6	deduplicate matching logic (with bin/return-assignment)
bin/nit-picker	15	\\n- check for differences of dependencies between mysql and git\\n- check for differences of dependencies between mysql and packages\\n- check for installability of packages
bin/filter-build-logs	10	remove hard-coded package suffixes
bin/get-package-updates	10	keep database clean in case of abort
bin/get-package-updates	324	maybe, we want to exclude our own packages here, too? But why\\nwould they be black listed in the first place?\\nshellcheck disable=SC2154
bin/get-package-updates	453	sometimes we schedule the identical package twice (once "normal"\\nand once, because we found the deleted package elsewhere) - this could\\nbe avoided
bin/copy-to-build-support	10	allow to introduce a manually built package into build-support
bin/copy-to-build-support	12	remove hard-coded package suffixes
bin/seed-build-list	19	allow to reschedule filtered by architecture
bin/seed-build-list	21	remove hard-coded package suffixes
bin/seed-build-list	23	-a reschedules too many packages (for example, packages, that have just been rescheduled in a previous run)
bin/seed-build-list	25	-a and -p leave the buildmaster in an unclean state
bin/seed-build-list	226	translate lib32-* packages instead of ignoring them for -m
bin/seed-build-list	424	this might become wrong if we ever change the order of the\\nrows in repository_stabilities -- we might want to refer to\\nrepository_stability_relations here somehow ...
bin/seed-build-list	687	this seems to be broken (deletes too few packages) - still valid\\nafter implementing the correct blacklisting below?
bin/why-dont-you	12	reintrocude "keep", "stubbornly_keep", "stabilize" and "unstage"\\nusing information from the database.
bin/why-dont-you	271	This logic is different from `calculate_maximal_moveable_set`:\\nIf a package has a broken dependency already, we do not see it, but\\ndb-update does.
bin/create-build-support-package	6	remove hard-coded package suffixes
bin/create-build-support-package	8	use the intention-queue
bin/create-build-support-package	10	add the possibility to add an "external" package - TBD: How to\\ncreate / Where to take from database information (e.g.\\npackage_sources).
bin/create-build-support-package	188	mangle customizable meta-infos here (new provides, keep some\\ndepends)
bin/create-build-support-package	360	maybe add (some?) depends here, too?
bin/return-assignment	379	We might want to prioritize broken dependencies, which are already\\non the build-list.
bin/return-assignment	382	We might also want to prioritize the returned package if there\\nwere broken dependencies identified, but none of these is still on the\\nbuild list (e.g. some race condition between this build and its\\ndependencies occured).
bin/return-assignment	387	Iff broken dependencies were rescheduled or prioritized, we\\nshould raise the priority of the returned package to one less than the\\nmaximum value (so it will be rebuilt after the broken dependencies).
bin/return-assignment	427	We might want to make this architecture-sensitive.
bin/return-assignment	896	maybe, we should not put "any" packages into repositories of all\\narchitectures at once, but wait until they can actually be installed\\non that architecture? (They might be missing an architecture specific\\ndependency)
bin/return-assignment	1039	this makes sense for provide= entries in .PKGINFO, too
bin/return-assignment	1069	sign database
bin/return-assignment	1198	possibly remove install_target_providers with less restrictive\\nversions than we have now
bin/return-assignment	1355	set _correct_ version of install_target_providers
bin/bootstrap-mysql	63	`package_blobs` needs too much space!
bin/ping-to-master	13	abort build if requested to
bin/interpret-mail	8	remove hard-coded default package suffixes
bin/local-build-package	10	remove hard-coded package suffixes
bin/db-update	10	make (all) locking less restrictive
bin/db-update	12	intentionally break packages that failed to build for a certain time
bin/db-update	14	-p seems to try to move stuff from community to community and from\\nextra to extra - which of course leads to problems.
bin/db-update	625	sign repositories
bin/clean-cache	8	remove hard-coded package suffixes
bin/get-assignment	323	This is broken, it cannot work and probably never will do this way.
bin/check-opcodes	107	pentium4
lib/mysql-functions~	358	we might want to keep the pkgrel part and only remove the\\nsub_pkgrel part - but then we need to include pkgrels on the provide\\nside, too(?)
lib/mysql-functions~	507	we might want to move packages of blacklisted architectures to\\nthe deletion-list instead of the build-list
lib/mysql-functions~	1109	only consider installable providers (at least for haskell-*, but\\nit would be probably best to do so for all packages)
lib/mysql-functions~	1411	needs a left-join variant, too (possibly a right-join, too?)
lib/mysql-functions	358	we might want to keep the pkgrel part and only remove the\\nsub_pkgrel part - but then we need to include pkgrels on the provide\\nside, too(?)
lib/mysql-functions	507	we might want to move packages of blacklisted architectures to\\nthe deletion-list instead of the build-list
lib/mysql-functions	1109	only consider installable providers (at least for haskell-*, but\\nit would be probably best to do so for all packages)
lib/mysql-functions	1411	needs a left-join variant, too (possibly a right-join, too?)