# Admonitions (FAQ, NOTE, TODO, BUG)

Automated index of all admonitions (in this manual as well as in python code documentation). For simplicity, we only use four admonitions: error, attention, note, tip.

Error

(BUG) Ongoing issues: No fix yet

Attention

(TODO) Ongoing issues: Minor or has workaround

- administrator: Manual Setup Section: Has not been revised since `1.0.x`

- administrator: When adding a Remote, be sure to use the exact same hostname (in the `http` field) the instance uses

- python/mini_buildd.api: Call debmirror (external workarounds): `apt update` fails on `experimental` suites (contents not mirrored) (Debian Bug #819925)

- python/mini_buildd.api: Call handshake: In production, we occasionally see `W: Remote handshake failed for ...: 'tuple' object has no attribute 'signatures'`. Reproduce?

- python/mini_buildd.models: AptKeys: Duplicates possible (will break API call `setup`)

- python/mini_buildd.models: Chroot: LVM chroots fail running lvcreate with ‘not found: device not cleared’ (Debian Bug #705238)

- python/mini_buildd.models: Daemon: When changing ftp network settings, then PCA: Still not active, needs explicit restart?

- python/mini_buildd.models: Distribution (`workaround in __str__`): Not unique for base source (historic fluke)

- python/mini_buildd.models: Distribution: When adding Architecture: No indication that we need to re-index (run check on repository)

- python/mini_buildd.reprepro: reprepro (`dist.py` setup workaround): Can’t handle Ubuntu’s `ddeb` (Debian Bug #730572)

- python/mini_buildd.reprepro: reprepro: Don’t switch to `reprepro 5.4` yet (Debian Bug #1017983)

- python/mini_buildd.reprepro: reprepro: Fails with `debian/` being a symlink in Debian native packages (Debian Bug #768046)

- python/mini_buildd.sbuild: sbuild (retry-workaround in `gnupg.py`): Spurious build failures `can't connect to the agent: IPC connect call failed` (Debian Bug #849551)

- python/mini_buildd.sbuild: sbuild (workaround in `apt-update` snippet): `apt-get update` “File has unexpected size … Mirror sync in progress?” failures

- python/mini_buildd.sbuild: sbuild: Fails to build “all” packages with “build archall” flag set to arch “x” in case DSP has >= 1 arch “all” and >=1 arch “y” binary package (Debian Bug #706086)

- python/mini_buildd.sbuild: sbuild+apt-cacher-ng (workaround in `apt-update` snippet): `apt-get update` stalls on parallel access

- python/mini_buildd.schroot: schroot: ‘target is busy’ on session close (stale schroot sessions)

- python/mini_buildd.schroot: wheezy or older builds on amd64: Re-enable linux’ vsyscall

- roadmap: buster-based install: 500 Internal Error: `[Errno 2] No such file or directory: 'S.gpg-agent.extra'`

Note

(NOTE) Something not obvious you should be aware of

- python/mini_buildd.api: Call keyring-packages: No compat for urold <= squeeze (`apt-key add`)

- python/mini_buildd.api: Call keyring-packages: squeeze or older only: apt secure problems after initial (unauthorized) install of the archive-key package (Debian Bug #657561)

- python/mini_buildd.api: Call stop: Ongoing `PACKAGING` or `BUILDING` are lost on restart

- python/mini_buildd.builtins: http://tools.ietf.org/html/rfc5147: This, in theory, could be some way to create a TOC for text/plain (buildlogs and such). However

- python/mini_buildd.models: Chroot (`mbd_workaround_debmirror_script`): Be able to strap ‘newer Ubuntus’ with Debian’s `debootstrap`

- python/mini_buildd.models: Chroot (setup workaround in `dist.py`): debootstrap fails for <=lenny chroots on >=jessie host kernel (uname) (Debian Bug #642031)

- python/mini_buildd.models: Daemon: Instance does not touch the GPG setup once it’s created – unless you do an explicit remove on the instance.

- python/mini_buildd.models: Uploader: Don’t add or delete instances manually!

- python/mini_buildd.reprepro: reprepro: Multiple versions of packages in one distribution

- python/mini_buildd.sbuild: This will iterate all lines of the build log,

- python/mini_buildd.schroot: schroot: Verbosely logs commands (“Running command …”) explicitly via syslog (journalctl)

Tip

(FAQ) Free tip

- abstract: Some links do not work in this manual?

- administrator: Can I manually instantiate a build chroot to repeat/debug a failed build?

- administrator: How much disk space do I need to run mini-buildd?

- administrator: How to enable encrypted uploads (FTPS)?

- administrator: How to manually fix a failing check in a `Source` due to wrong/missing APT key(s)?

- administrator: How to run mini-buildd in a systemd container (nspawn)?

- administrator: In the web configurator, you may use the `PCA` shortcut (`prepare`, `check` and `activate`).

- administrator: My chroot creation fails due to missing arch in archive (partial mirror)?

- administrator: What’s `eatmydata` and `ccache`?

- administrator: sudo fails with “sudo: no tty present and no askpass program specified”?

- consumer: How can I upgrade after Debian main release version fix?

- consumer: How do I verify mini-buildd’s APT key?

- consumer: How to save credentials when working from the shell?

- consumer: What’s the `hotfix` suite good for?

- consumer: `firefox`: How can I reset (table) searches (like in webkit browsers)?

- developer: Can I access built packages that have not been installed into the repository?

- developer: Do mini-buildd commands support bash autocompletion?

- developer: Is package building parallel? (a.k.a. Where is the ‘sbuild_jobs’ settings?)

- developer: Is there support for `emacs`?

- python/mini_buildd.dist: What does `LTS` (mini-buildd speak) include for Debian?

- python/mini_buildd.dist: What does `LTS` (mini-buildd speak) include for Ubuntu?

- python/mini_buildd.models: Chroot: Install Debian package ‘qemu-user-static’ for seamless access to foreign archs (albeit with a speed penalty)

- roadmap: Can I skip migrating from 0.8.x?