Setting up Umegaya

Programs needed

  • Apache
  • Berkeley DB
  • curl
  • The following Perl modules:
    • BerkeleyDB
    • LWP
    • Mouse
    • YAML::XS
    • YAML::Appconfig


  • Set up an Apache virtual host using the umegaya.conf file in /etc/apache2/conf-available/.
  • Set up a directory where Apache can write the umegaya.db Berkeley DB and optionally save a copy of the upstream, copyright and control files in the packages-metatata pool (by default in /var/lib/umegaya).
  • Make sure that the Umegaya administrator has also write access to the directory.
  • Umegaya finds the package's VCS using the debcheckout command of the devscripts package, so a deb-src line tracking Sid is necessary for a full coverage. The cron-apt package is useful to keep the apt cache up to date.


Umegaya is a passive system, that refreshes itself only when accessed. It can be kept up to date by systems that will access it when some resources are refreshed, for intance commit hooks.

To refresh Umegaya for each package that has been uploaded to Debian, subscribe to the debian-devel-changes mailing list and pipe its messages to umegaya-ddc-ping(1).

Another way is to periodically access a list of selected packages. For instance, the script umegaya-refresh-blends(1) refreshes Umegaya for all packages in Debian Pure Blends. It is called by a daily cron job and can be must be activated through the refresh_blends parameter in /etc/umegaya/umegaya.conf.

umegaya-refresh-blends(1) tries to guess the VCS URL packages that are not know of debcheckout, using the layout policy of the blends.

The list of packages recommended by each blend overlap. To avoid unnecessary requests, the default refresh delay is set to one hour. Alioth is never queried when the last refresh was made within the refresh delay.

This (and below) assumes that the VCS name is the source package names. This is true in theory, but in practice, a safeguard for errors may be necessary.

To determine if a package managed with Git on Alioth contains a debian/upstream/metadata file.

for repo in /git/debian-med/*.git
  (cd $repo ; git ls-tree master debian/ |
   grep 'debian/upstream/metadata$' > /dev/null && echo "$repo")
done | sed -e 's|/git/debian-med/||' -e 's|.git$||'

Accumulating the files on the local disk

Via the store_files and debian_control and debian_copyright options, umegaya can keep a local copy of the upstream, control and copyright files of the packages, in the db_dir directory.

The Debian package provides a pooled directory structure in /var/lib/umegaya, but it needs to be created if another path is chosen.

Pushing these files to a remote Subversion server

Create a passwordless key, and restrict it to run only svnserve, as explained in the red bean book. Check out the repository in umegaya's db_dir (--force). Commit from time to time.

Notes about YAML

# Invalid
foo: bar:

# Valid
foo: "bar:"

# Also valid
foo: >

Also valid
foo: |

The difference between | and > is roughly the same as between the multi-line and folded fields in Debian control files.