Daniel Leidert
2014-02-15 14:04:16 UTC
Hi,
With the release of bluefish 2.2.5 I hereby announce, that bluefish
backports for Debian stable beginning with Wheezy (current stable) are
now provided as official backport via debian.org and no longer via
debian.wgdd.de. Thus enabling wheezy-backports as source shall give any
Debian stable user access to the latest bluefish release. The advantages
are:
-The backport will be available for all architectures currently
supported by the Debian project.
-Bug reports will be sent to the Debian BTS.
-No longer need to include a third party (mine) repository. Everything
is provided via official Debian repositories.
The first bluefish backport (2.2.5-2~bpo70+1) will be available in 12
days. Note, that this delay will usually take place in the future too.
The package will be available as soon as the latest bluefish package
hits Debian Testing (which is usually 10 days after its upload to Debian
Unstable). This is to have at least 10 days to find serious issues in
this package before it goes to Testing. If nothing is found, one or two
days later it will be available for backport users too.
For instructions see http://backports.debian.org/Instructions/ and
related resources.
After following these instructions to setup the wheezy-backports tree as
package source for the bluefish package, it should be "safe" and
non-problematic to remove my repository (debian.wgdd.de) from your
source.list(.d), it's key and/or key-package (wgdd-archive-keyring) -
purging the key package will automatically remove the key from the
apt-keyring. As soon as you find bluefish in wheezy-backports:
apt-cache policy bluefish
[..]
2.2.5-2~bpo70+1 0
100 http://ftp.debian.org/debian/ wheezy-backports/main amd64 Packages
[..]
do:
apt-get|aptitude -t wheezy-backports install bluefish
Regards, Daniel
With the release of bluefish 2.2.5 I hereby announce, that bluefish
backports for Debian stable beginning with Wheezy (current stable) are
now provided as official backport via debian.org and no longer via
debian.wgdd.de. Thus enabling wheezy-backports as source shall give any
Debian stable user access to the latest bluefish release. The advantages
are:
-The backport will be available for all architectures currently
supported by the Debian project.
-Bug reports will be sent to the Debian BTS.
-No longer need to include a third party (mine) repository. Everything
is provided via official Debian repositories.
The first bluefish backport (2.2.5-2~bpo70+1) will be available in 12
days. Note, that this delay will usually take place in the future too.
The package will be available as soon as the latest bluefish package
hits Debian Testing (which is usually 10 days after its upload to Debian
Unstable). This is to have at least 10 days to find serious issues in
this package before it goes to Testing. If nothing is found, one or two
days later it will be available for backport users too.
For instructions see http://backports.debian.org/Instructions/ and
related resources.
After following these instructions to setup the wheezy-backports tree as
package source for the bluefish package, it should be "safe" and
non-problematic to remove my repository (debian.wgdd.de) from your
source.list(.d), it's key and/or key-package (wgdd-archive-keyring) -
purging the key package will automatically remove the key from the
apt-keyring. As soon as you find bluefish in wheezy-backports:
apt-cache policy bluefish
[..]
2.2.5-2~bpo70+1 0
100 http://ftp.debian.org/debian/ wheezy-backports/main amd64 Packages
[..]
do:
apt-get|aptitude -t wheezy-backports install bluefish
Regards, Daniel