veyepar: debdry - Debian Don't Repeat Yourself

Author(s):	Enrico Zini
Location	Room 327/8
Date	aug Fri 29	Days Raw Files
Start	11:00	First Raw Start	10:38
Duration	00:45:00	Offset	0:21:19
End	11:45	Last Raw End	11:46
Chapters	00:00
Total cuts_time	44 min.

https://summit.debconf.org/debconf14/meeting/25/debdry-debian-dont-repeat-yourself/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

assets release.pdf debdry_Debian_Dont_Repeat_Yourself.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

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

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Upstreams are doing their best packaging their tarballs, and then we redo most of their work when we debianise them. I personally find this situation wasteful and boring.

I like how debhelper7 allows to write debian/rules files that describe only when something diverges from the norm, and I think that debianising a package should be the same.
I want to debianise a package by just saying "I'm fine with everything upstream says, and put this in Section: foobar". I want to fix upstream's packaging by sending them patches instead of redoing it in debian/. I want most policy or toolchain updates to be handled with just a binNMU. I don't want to manually do any of the work that can possibly be done by a computer.

debdry is a prototype tool that tries to address that by running autodebianisation tools, which exist and work reasonably well for at least perl, python, haskell, ruby and node.js, and then applying semantically significant, manually maintained tweaks, if any is needed.

The bulk of my debian work should be adding Debian-specific metadata, testing, interacting with upstream, dealing with the BTS. It should not involve writing files that say that the README needs to be installed with the package documentation.

Let's make it happen.

Comment:

production notes