Hi
user
Admin Login:
Username:
Password:
Name:
Why I (tried to) killed the LSB
--client
debian
--show
debconf17
--room buzz 12490 --force
Next: 1 DebConf 19 in your city!
show more...
Marks
Author(s):
Didier Raboud
Location
Buzz
Date
aug Sat 12
Days Raw Files
Start
15:30
First Raw Start
error-in-template
Duration
00:45:00
Offset
None
End
16:15
Last Raw End
Chapters
Total cuts_time
None min.
https://debconf17.debconf.org/talks/181/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Why_I_tried_to_killed_the_LSB.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
After many Debian stable versions trying to align Debian with LSB (or is it the reverse?), Stretch got released with a restrained support of the LSB; Buster will remove more LSB compatibility packages. How did this happen, and why? Will it make the LSB obsolete, or is it the final nail in Debian's coffin, condemning it to eternal uselessness?
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