Please upgrade bluefish to 2.0.0 version

Bug #540126 reported by Úr Balázs on 2010-03-17
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
bluefish (Debian)
Fix Released
Unknown
bluefish (Ubuntu)
Wishlist
Unassigned
Declined for Lucid by Sebastien Bacher

Bug Description

Binary package hint: bluefish

The latest stable version is Bluefish 2.0.0.
http://bluefish.openoffice.nl/changelogs/ChangeLog_2_0_0

This is a release with 2 zeros. My plans are to wait a few bug-fix releases, before this is put into Debian and then it can by synced to Ubuntu. There are packages for Ubuntu 9.04 and 9.10 at debian.wgdd.de, which I build and provide.

http://debian.wgdd.de/debian/#ubuntu

2010/3/17 Daniel Leidert <email address hidden>:
> This is a release with 2 zeros. My plans are to wait a few bug-fix
> releases, before this is put into Debian and then it can by synced to
> Ubuntu. There are packages for Ubuntu 9.04 and 9.10 at debian.wgdd.de,
> which I build and provide.

Hi!

Thanks the fast answer! I found it is a PPA too
(https://launchpad.net/~klaus-vormweg/+archive/ppa), but it would be
great, if this package will be the part of the official repository.

OK, I'm waiting for the bugfix and use the PPA version.

Thanks
--
Úr Balázs

The package you mention from the PPA have several issues. These are mostly based on the packaging of the bluefish 1.0 series (which I'm responsible for). The packaging files have not been adjusted for the changes in bluefish and list outdated build- and runtime-dependencies. These packages won't be part of Bluefish repositories and I cannot suggest to add it to Ubuntu. And again: There are packages of Bluefish 2.0 built for Ubuntu versions 9.04 and 9.10 at debian.wgdd.de. These are the packages, which will go into Debian and then synced to Ubuntu. If anybody decides different, then live with the results.

Úr Balázs (urbalazs) wrote :

2010/3/17 Daniel Leidert <email address hidden>:
> The package you mention from the PPA have several issues. These are
> mostly based on the packaging of the bluefish 1.0 series (which I'm
> responsible for). The packaging files have not been adjusted for the
> changes in bluefish and list outdated build- and runtime-dependencies.
> These packages won't be part of Bluefish repositories and I cannot
> suggest to add it to Ubuntu. And again: There are packages of Bluefish
> 2.0 built for Ubuntu versions 9.04 and 9.10 at debian.wgdd.de. These are
> the packages, which will go into Debian and then synced to Ubuntu. If
> anybody decides different, then live with the results.

OK
Thanks for the information.

--
Úr Balázs
Telefon: +36 (20) 336 1191
E-mail: urbalazs [kukac] gmail [pont] com
Skype: urbalazs
MSN: urbalazs [kukac] gmail [pont] com
Weblap: http://www.urbalazs.hu/
iWiW: http://iwiw.hu/pages/user/userdata.jsp?userID=76603

nomnex (nomnex) wrote :

Daniel, how do I install version 2.0 on Karmic? will you provide a .deb link anytime soon? Thanks

nomnex (nomnex) wrote :

I did, yesterday after commenting on the thread. I will install using these packages, thanks.

nomnex (nomnex) wrote :

Daniel, I have removed your the key in my software source by mistake.
what's the command to call it back?

when I do an update:
W: GPG error: http://debian.wgdd.de jaunty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0F719C35E394D996

installing the key has no effect:
user@pc:~$ sudo apt-get install wgdd-archive-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
wgdd-archive-keyring is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thanks

nomnex (nomnex) wrote :

edit #8, line 9: [re]-installing the key does not bring it back in my software sources > authentication (Trusted software providers)

A simple `apt-get install $package" has no effect on an installed package, which you should already know, when you use a Debian-based Linux. You have to tell apt-get, that you want to install the package again via the `--reinstall' switch. Comment #9 is probably wrong. I doubt you have really reinstalled the package.

Besides possible (obvious) ways to restore the key: e.g. removing the package and installing it again or following the two alternative ways described on my pages (there are 3 ways of getting the key - via package, via key from my server and via public key servers), you can simply run:

apt-get install --reinstall wgdd-archive-keyring

Please read the information I provided. I'm not willing to give you personal assistance for things, which have already been described.

nomnex (nomnex) wrote :

Daniel, when a key is missing on Ubuntu, I usually pass the command:

sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com {NNNNNNNNN}

From your page http://debian.wgdd.de/debian/#gpgkey, I have tried the command:

sudo apt-key adv --recv-keys --keyserver pgp.mit.edu --recv-keys 0xE394D996

(but the command returned an error msg., would you be kind enough to give me the correct syntax, if I have to re-install a key located on an external server.)

-----

I did not know the "--reinstall" switch, my comment #9 "[re]-installing" implied passing the command "sudo apt-get install wgdd-archive-keyring" over again. -- we all have been newbie once...

-----

Again thank you for your kind answers and BlueFish 2.0 package. It is the first time I am using a Debian repository.

sudo preserves $HOME IIRC, which might be the problem here. But you don't quote the error message ...

Second issue: --recv-keys is a gpg command, whereas --keyserver is an option. gpg expects options before commands. So the first --recv-keys might be a problem in several cases. But that's JFTR.

It works from the root user account without any issues. So become root or try the -H switch of sudo or fix the sudoers file - I guess this will help. Please ask such things on your favourite Ubuntu user list/newsgroup/community.

nomnex (nomnex) wrote :

On Sun, 2010-05-30 at 12:25 +0000, Daniel Leidert wrote:
> sudo preserves $HOME IIRC, which might be the problem here. But you
> don't quote the error message ...

user@machine:~$ sudo gpg --keyserver pgp.mit.educ --recv-keys 0xE394D996
gpg: WARNING: unsafe ownership on configuration file
`/home/user/.gnupg/gpg.conf'
gpg: external program calls are disabled due to unsafe options file
permissions
gpg: keyserver communications error: general error
gpg: keyserver receive failed: general error

> Second issue: --recv-keys is a gpg command, whereas --keyserver is an
> option. gpg expects options before commands. So the first --recv-keys
> might be a problem in several cases. But that's JFTR.

E: Command line option --recv-keys is not understood
user@machine:~$ sudo # gpg --keyserver pgp.mit.edu --recv-keys
0xE394D996

it makes sens now.

> It works from the root user account without any issues. So become root
> or try the -H switch of sudo or fix the sudoers file - I guess this will
> help. Please ask such things on your favourite Ubuntu user
> list/newsgroup/community.

I will. Again thank you for the lead. I can now formulate my pgp related
questions and ask on the newsgroup/forum.
 regards,
 nomnex

nomnex (nomnex) wrote :

I made a mistake in my second command. corrected:

user@machine:~$ sudo apt-key adv --recv-keys --keyserver pgp.mit.edu
--recv-keys 0xE394D996
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
--secret-keyring /etc/apt/secring.gpg
--trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg
--recv-keys --keyserver pgp.mit.edu --recv-keys 0xE394D996
gpg: requesting key E394D996 from hkp server pgp.mit.edu
gpg: key E394D996: "Automatic Archive Signing Key for wgdd.de
(2009/2010) <email address hidden>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1

and... it worked! but it took >50 sec. to process. I will wait a longer
time next time, before to ctrl+c.

Changed in bluefish (Ubuntu):
status: New → In Progress
Sebastien Bacher (seb128) wrote :
Changed in bluefish (Ubuntu):
importance: Undecided → Wishlist
Changed in bluefish (Debian):
status: Unknown → New
Changed in bluefish (Debian):
status: New → Fix Committed
Changed in bluefish (Debian):
status: Fix Committed → Fix Released
Ben Coleman (oloryn) wrote :

Wouldn't you know, the 2.0.1 release announcement appeared a couple of days ago.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluefish - 2.0.1-1

---------------
bluefish (2.0.1-1) unstable; urgency=low

  * New upstream release - the first release of the 2.0 series for Debian
    (closes: #570731; LP: #540126). This release fixes these reported issues:
    - Better settings handling (closes: #548272).
    - Improved filebrowser (LP: #45927).
    - Improved syntax highlighting engine (LP: #108628).
    - Improved file operations (LP: #181110).
    - Translated menu descriptions (LP: #371318, #371322). The chosen menu
      name is fine.
    - Improved browser commands and handling (LP: #158891, #348408).
  * Updated and adjusted packaging files.
  * debian/bluefish_icon.xpm: Renamed to debian/bluefish.xpm.
  * debian/bluefish.install: Adjusted.
  * debian/bluefish.menu (icon): Adjusted.
  * debian/bluefish-data.install, debian/bluefish-plugins.install: Added.
  * debian/control: Added bluefish-data, bluefish-dbg and bluefish-plugins.
    (Build-Depends): Dropped deprecated build-dependencies libaspell-dev,
    libgnomeui-dev, libgnomevfs2-dev, libpcre3-dev and dpatch. Added intltool,
    libtool, libenchant-dev and libgucharmap2-dev.
    (Standards-Version): Bumped to 3.8.4.
    (Depends, Suggests): Adjusted. Added gvfs-backends as dependency.
  * debian/copyright: Updated.
  * debian/rules: Rewritten. Dropped dpatch.
    (LDFLAGS): Dropped -Wl,-z,defs because of plugins.
    (config.status:): Adjusted configure switches.
    (install): Install to debian/tmp and list missing files.
    (binary-indep): Added for bluefish-data.
    (binary-arch): Adjusted. Put debugging symbols into bluefish-dbg.
  * debian/watch: Added support for RCs.
  * debian/README.Debian: Dropped (useless with 2.0).
  * debian/README.source: Dropped together with dpatch.
  * debian/patches/: Dropped (obsolete).
  * debian/reportbug/: Dropped.
 -- Lorenzo De Liso <email address hidden> Tue, 29 Jun 2010 21:40:10 +0200

Changed in bluefish (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.