Commit edff2462 authored by intrigeri's avatar intrigeri
Browse files

TODO update.

parent d97de6aa
......@@ -42,7 +42,7 @@ little value.
c. **done** decide how many reprepro instances we want/have to split all
this among
d. **done** mirror relevant suites of deb.tails.b.o as well
d. clean up Wheezy packages (hint: snapshots)
d. WIP: clean up Wheezy packages (hint: snapshots)
d. publish the snapshots over HTTP
e. try using such snapshots for building an ISO
e. publish the snapshots' serial: a file is updated, now needs to
......@@ -83,9 +83,6 @@ little value.
- convert custom `data/debootstrap/tails-wheezy` into a patch,
or set up the process to update/replace it in the future,
or something (we're using Jessie now) [i]
- The architecture information is not part of the manifest.
It's fine if `tails-prepare-tagged-apt-snapshot-import` can
do its job without this information. Can it?
- triage remaining XXX:s in the script, address what needs
to be
* `tails-prepare-tagged-apt-snapshot-import`, aka.
......@@ -97,9 +94,10 @@ little value.
be good enough to import a bit too much, e.g. import each
package for _all_ architectures our reprepro setup
supports even though we need it only for one architecture;
beware of differing versions due to binNMUs, though)
- triage remaining XXX:s in the script, address what needs
to be
beware of differing versions due to binNMUs, though) [k]
- test with a complete set of data (including all
architectures we want, source packages, and a build
manifest that includes amd64 and source packages) [i]
f. **WIP** expand list of source packages with those that the binary
packages were built from [k]
=> review this [i], in particular:
......@@ -555,6 +553,15 @@ XXX: find out how we can solve these two problems.
None of these problems seem to warrant going back to the other
option... and having to deal with 80GB+ BDB databases.
E.g. to remove all Wheezy snapshots:
reprepro dumpreferences \
| grep -E '^s=wheezy' \
| awk '{print $1}' \
| sort -u \
| xargs -n 1 reprepro _removereferences \
&& reprepro deleteunreferenced
<a id="build-manifest"></a>
## Listing used packages
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment