GitHub.com (and probably GitLab too) provides various ways to export the Git branch contents or tags and releases as Zip- or Tar-archives. When creating a release, these tar-/zipballs are automatically created and added to the release. I often find archives, which contain a lot of files not useful to the end user, like .github directories, Git (.gitignore, .gitattributes) or CI related files (.travis.yml, .appveyor.yml). Sometimes they also contain directories (e.g. for test files), the repository owner wants to host in Git, but does not need for the source distribution. But there is an easy way to keep these files out of the automatically created source archives and keep the latter clean by using the export-ignore attribute in the .gitattributes files:

# don't export the github-pages source
/docs export-ignore
# export some other irrelevant directories
/foo export-ignore
/test export-ignore
# don't export the files necessary for CI
Gemfile export-ignore
.appveyor.yml export-ignore
.travis.yml export-ignore
# ignore Git related files
.gitattributes export-ignore
.gitignore export-ignore

The repository archive key had expired. I’ve changed the expiration date, so you will have to update the key in your apt keyring. The updated key can be found at the pgp.mit.edu keyserver or locally in ASCII format at wgdd_archive_key.asc. Detailed information can be found here.

My repository is now signed. So maybe you see the following warning when running apt-get from Debian Etch or Sid or Ubuntu Breezy:

W: GPG error: http://debian.wgdd.de unstable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0F719C35E394D996
W: You may want to run »apt-get update« to correct these problems

Please read the related information about how getting my key under Archive signing key.

I am the new official maintainer for the bluefish. My repository will contain Bluefish packages for the CVS version and release candidates in the future (for testing purposes and feedback), but packages for the final release will directly go into Debian.

I’ve prepared a new Debian package for the newly released Winefish 1.2.0. The updated Debian packages can now be found in the unstable tree of my repository.

I provide bluefish packages made from CVS, which contain the latest features. If you want to test the latest bluefish version, then you can install the bluefish-cvs package in additon to a stable bluefish Debian package. Both packages use their own files and directories, so you can do relaxed testing of the latest features. Please note, that the development version may not be stable and crash. The packages are located in the experimental tree of my Debian package repository.

Hier wird hoffentlich bald mehr stehen? Die Prüfungszeit zwingt mich dazu, das Füllen dieser Seiten mit hoffentlich interessanten Informationen um einige Zeit zu verschieben. Man liest sich danach (hoffentlich).