Hi
user
Admin Login:
Username:
Password:
Name:
Rebuilding Debian as a Toolchain Test
--client
debian
--show
debconf15
--room BerlinLondon 10162 --force
Next: 1 AppArmor Crash Course
show more...
Marks
Author(s):
Wookey
Location
Berlin/London
Date
aug Thu 20
Days Raw Files
Start
14:30
First Raw Start
error-in-template
Duration
00:20:00
Offset
None
End
14:50
Last Raw End
Chapters
Total cuts_time
None min.
https://summit.debconf.org/debconf15/meeting/243/rebuilding-debian-as-toolchain-test/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
public
mp4
svg
png
assets
release.pdf
Rebuilding_Debian_as_a_Toolchain_Test.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
ARM needs to test toolchain fixes, and 'all of debian' is a good way of finding whether your fix works 'everywhere', and how likely a particular code sequence is. This talk describes how we set the build system up to rebuild everything as quickly as possible, and shows the results we got. Feedback from others doing this sort of thing would be appreciated.
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