Hi
user
Admin Login:
Username:
Password:
Name:
Automating Architecture Bootstrap
--client
debian
--show
debconf15
--room Heidelberg 10113 --force
Next: 1 Enrico's semi serious stand up comedy
show more...
Marks
Author(s):
Helmut Grohne
Location
Heidelberg
Date
aug Mon 17
Days Raw Files
Start
18:00
First Raw Start
error-in-template
Duration
00:45:00
Offset
None
End
18:45
Last Raw End
Chapters
Total cuts_time
None min.
https://summit.debconf.org/debconf15/meeting/288/automating-architecture-bootstrap/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
public
mp4
svg
png
assets
release.pdf
Automating_Architecture_Bootstrap.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
Bootstrapping an architecture refers to building the initial set of binary packages to populate the archive. The early phase discussed in this talk uses cross building to obtain essential packages. The following questions will be addressed: Why should we care about architecture bootstrap? What aspects are manual, but don't have to be? What are build profiles and why do we need them? Which packages need to support cross compilation? How to translate Build-Depends for a cross build?
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review