Commit 20b64713 authored by intrigeri's avatar intrigeri
Browse files

Update TODO.

parent edff2462
...@@ -75,43 +75,31 @@ little value. ...@@ -75,43 +75,31 @@ little value.
c. **done** initial reprepro setup for tagged snapshots c. **done** initial reprepro setup for tagged snapshots
d. **done** debootstrap in jessie-backports d. **done** debootstrap in jessie-backports
e. **WIP** how to create a partial snapshot from a manifest and e. **WIP** how to create a partial snapshot from a manifest and
the origin time-based snapshots? [k] the origin time-based snapshots?
- review and test k's code that is meant to address this [i]; in particular: * `generate-build-manifest` (main Git repo), aka. [[!tails_ticket 10748]]
* `generate-build-manifest` (main Git repo), aka. - cherry-pick the relevant bits and get them into Tails 2.3 [i]
[[!tails_ticket 10748]] - convert custom `data/debootstrap/tails-wheezy` into a patch,
- cherry-pick the relevant bits and get them into Tails 2.3 [i] or set up the process to update/replace it in the future,
- convert custom `data/debootstrap/tails-wheezy` into a patch, or something (we're using Jessie now) [i]
or set up the process to update/replace it in the future, - triage remaining XXX:s in the script, address what needs
or something (we're using Jessie now) [i] to be
- triage remaining XXX:s in the script, address what needs * `tails-prepare-tagged-apt-snapshot-import`, aka.
to be [[!tails_ticket 10749]] (`puppet-tails` repo):
* `tails-prepare-tagged-apt-snapshot-import`, aka. - review & test support for multiple architectures [i]:
[[!tails_ticket 10749]] (`puppet-tails` repo): * beware of differing versions due to binNMUs
- support for multiple architectures? needed for multiarch * test with a complete set of data (including all
that we'll have to use as soon as we want to upgrade Linux architectures we want, source packages, and a build
to 4.x, see manifest that includes amd64 (e.g.
[[!tails_gitweb_branch feature/8415-overlayfs]]; (it might [[!tails_gitweb_branch feature/8415-overlayfs]]) and
be good enough to import a bit too much, e.g. import each source packages
package for _all_ architectures our reprepro setup g. **WIP** have the manifest → partial snapshot process include source
supports even though we need it only for one architecture; packages
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: => review this [i], in particular:
- check the case when the binary package's version is different - check the case when the binary package's version is different
from the corresponding source package's one from the corresponding source package's one
(`libdevmapper1.02.1` vs. `lvm2`) (`libdevmapper1.02.1` vs. `lvm2`)
- torproject provides no source packages; how does - torproject provides no source packages; how does
`tails-prepare-tagged-apt-snapshot-import` deal with it? `tails-prepare-tagged-apt-snapshot-import` deal with it?
g. **WIP** have the manifest → partial snapshot process include source
packages [k]
=> review this [i], in particular:
- check the case when the binary package's version is different
from the corresponding source package's one
(`libdevmapper1.02.1` vs. `lvm2`)
h. for some Tails release: generate manifest, import packages into h. for some Tails release: generate manifest, import packages into
tagged snapshots, try building *offline* with these tagged tagged snapshots, try building *offline* with these tagged
snapshots [i] snapshots [i]
...@@ -124,7 +112,6 @@ little value. ...@@ -124,7 +112,6 @@ little value.
5. misc 5. misc
* implement whatever the "freeze exceptions" section requires * implement whatever the "freeze exceptions" section requires
* Puppetize every server-side thing that hasn't been yet.
# The big picture # The big picture
......
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