Debian now officially contains packages for Gtk+Extra 2.0. So I removed the packages from my repository. Please use the ones officially provided by Debian. There is no automatic way of upgrading to the official Debian packages, so you have to remove my packages first
su -c "apt-get remove --purge libgtkextra-2.0-1 libgtkextra-2.0-1-dev"
before you install the official Debian packages!
I'm proud to announce, that chemical MIME was accepted by the Debian FTP-masters and it is now part of the Debian distribution as package chemical-mime-data . However the GNOME chemistry utils are not yet accepted, but they are awaiting the review by the FTP-masters in the NEW-queue. The next packages will be gchempaint (probably 0.6.7) and bkchem (probably 0.11.5).
The Debian packaging files of these packages are officially maintained by the debichem Alioth project members (I belong to this group too) and they can be found in our SVN repository. I have to say "Many thanks!" to Michael Banck, my sponsor, and "Join us!" to all, who want to help packaging.
I've updated the Debian Wiki to fit the new situation. Search there, of you want to know, which packages await an review to suggest them for Debian officially.
Stay tuned.
Because of issues and changes inside the sourceforge.net CVS infrastructure, it will need a few more days, before I can release the next RC for chemical-mime-data, which will be version 0.1.93. There are still a few steps to go for release 0.2.0, but we are on the way.
Today I released the first official version of chemical-mime-data after moving back to sourceforge.net. This release is thought to be the first RC for the upcoming 0.2.0 version. I made massive changes since our last release of chemicalMIME 2. One important improvement is IMHO the database, which is now the place to drop all informations. Have a look at the release notes to get an overview, what has changed.
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 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 you maybe 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 Debian package. 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.