Re: RELEASE emelFM2 0.2

  • From: dsyates <dsyates@xxxxxxxxxxxxxx>
  • To: emelfm2@xxxxxxxxxxxxx
  • Date: Sat, 26 Aug 2006 14:13:28 -0400

dsyates wrote:

Florian Zähringer wrote:
Hi!

The problem is the changelog file.

Seems like Tom forgot to update this. No big deal.
Just add the lines

emelfm2 (0.2.0-1) unstable; urgency=low

* new upstream
-- Florian Zaehringer <flo.zaehringer@xxxxxx> Thu, 26 Aug 2006 20:03:20 -0400


on top. And it should label as 0.2

Cheers,
-- Florian

On Sat, 26 Aug 2006 13:08:41 -0400
dsyates <dsyates@xxxxxxxxxxxxxx> wrote:

tpgww@xxxxxxxxxxx wrote:
In summary, relative to 0.1.8:

* a variety of fine-tunes of the user-interface
* several small operational changes
* updated translations
* bugs fixed (the more serious ones were all done in the 0.1.8 patch)

See http://emelfm2.net/ChangeLog for details.

Three candles. Well, almost. Version 0.0.1 of emelFM2 was released on 6 September 2003.

Three years have included 18 official releases and 12 or 13 pre-releases, so maybe the speed is not so bad. We must do something about the numbering scheme, if we are to get to 1.0 this lifetime !

These days, the general shape and feel of emelFM2 is fairly stable. Presumably there will be bugs to find and fix, but probably no more significant change. A possible exception, the addition of vfs capability (in essence, the ability to show things other than mounted local directories in file-lists) is presently classed among the "changes that may not be worth the effort". More on this in another message.

Regards
Tom


Another fine release! I am having a little trouble making a deb package for this release. That's not completely accurate; I can make the deb package just fine with sudo debian/rules binary, and it installs fine too. The problem I am having is the package that gets built is emelfm2_0.1.8-1_i386.deb. The about dialog shows the version correctly as 0.2. I have edited both the /debian/files, and /debian/control files, and changed older instances to read 0.2.
Like I said, it works, and installs just fine, it is the latest version, just the deb package is incorrectly mis-labled. Any ideas?
btw, I don't have this problem using checkinstall to build the deb package.




--
David S. Yates
webpage: http://lottalinuxlinks.com
blog:    http://lottalinuxlinks.com/blog
podcast: http://lottalinuxlinks/podcast/


--
Users can unsubscribe from the list by sending email to emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by logging into the web interface.


Thanks!


I don't think that was the complete solution. i now get this error:

dh_installchangelogs
parsechangelog/debian: error: found start of entry where expected more change data or trailer, at changelog line 7
dh_installchangelogs: changelog parse failure


this is what the first part of the changelog now looks like:

emelfm2 (0.2.0-1) unstable; urgency=low

   * new upstream

-- Florian Zaehringer <flo.zaehringer@xxxxxx> Thu, 26 Aug 2006 20:03:20 -0400

emelfm2 (0.1.8-1) unstable; urgency=low

  * new upstream

-- Florian Zaehringer <flo.zaehringer@xxxxxx> Thu, 27 Jul 2006 20:03:20 -0400

emelfm2 (0.1.7-1) unstable; urgency=low

  * new upstream

-- Florian Zaehringer <flo.zaehringer@xxxxxx> Thu, 27 Apr 2006 20:03:20 -0400

emelfm2 (0.1.6-1) unstable; urgency=low

  * new upstream

-- Florian Zaehringer <flo.zaehringer@xxxxxx> Tue, 14 Mar 2006 20:03:20 -0400



--
David S. Yates
webpage: http://lottalinuxlinks.com
blog:    http://lottalinuxlinks.com/blog
podcast: http://lottalinuxlinks/podcast/


-- Users can unsubscribe from the list by sending email to emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by logging into the web interface.

Other related posts: