Hi
user
Admin Login:
Username:
Password:
Name:
Reproducible Builds for Debian, a year later
--client
debian
--show
debconf14
--room room3278 8598 --force
Next: 3 Removing obsolete packages for fun and profit
show more...
Marks
Author(s):
Jérémy Bobbio
Location
Room 327/8
Date
aug Tue 26
Days Raw Files
Start
14:30
First Raw Start
14:16
Duration
00:45:00
Offset
0:13:30
End
15:15
Last Raw End
15:17
Chapters
00:00
Total cuts_time
46 min.
https://summit.debconf.org/debconf14/meeting/78/reproducible-builds-for-debian/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
public
mp4
svg
png
assets
release.pdf
Reproducible_Builds_for_Debian_a_year_later.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
How can we enable multiple parties to verify that a binary package has been produced untampered from a given source in a distribution like Debian? With free software, anyone can inspect the source code for malicious flaws. But most distributions provide binary packages to their users. We would like them to be able to verify that no flaws are introduced during the build process. The idea of “deterministic” or “reproducible” builds is to enable anyone to reproduce a byte-for-byte identical binary packages from a given source. Last year at DebConf13, a last minute BoF kicked off the effort. The last large scale experiment on 5151 source packages yield 62% of them producing matching binaries after a couple changes to the toolchain. A pretty encouraging result! The presentation will explain why we need reproducible builds, what has been done over the past yeast, the problems that have been identified so far and possible solutions. A subsequent BoF will allow interested parties to discuss solutions to some hard problems that were found during this first year of research.
Comment:
production notes
2014-08-26/14_16_30.dv
Apply:
14:30:44 - 15:17:14 ( 00:46:30 )
S:
14:16:30 -
E:
15:17:14
D:
01:00:44
(
Start:
00:14:14.00)
show more...
vlc ~/Videos/veyepar/debian/debconf14/dv/room3278/2014-08-26/14_16_30.dv :start-time=0854.0 --audio-desync=0
Raw File
Cut List
14:16:30
seconds: 854.0
Wall: 14:30:44
Duration
01:00:44
15:17:14
seconds: 0.0
Wall: 14:16:30
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2014-08-26/14_16_30.dv
Veyepar
Video Eyeball Processor and Review