Accepted agistudio 1.2.3+svn20070518-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:30:08 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.3+svn20070518-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen

Accepted nagi 2.07b-7 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:20:05 +0300 Source: nagi Binary: nagi Architecture: source i386 Version: 2.07b-7 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted memaid-pyqt 0.2.5-3 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:19:20 +0300 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.5-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted imediff2 1.1.1-2 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:18:09 +0300 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted cfourcc 0.1.2-2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:17:42 +0300 Source: cfourcc Binary: cfourcc Architecture: source i386 Version: 0.1.2-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted metacam 1.2-3 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:19:33 +0300 Source: metacam Binary: metacam Architecture: source i386 Version: 1.2-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 1.1.1-2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 May 2007 12:18:43 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted agistudio 1.2.3-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 18 Mar 2007 02:25:02 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.3-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted openoffice.org-soikko 1.1.1-3 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 31 Oct 2006 10:05:35 +0200 Source: openoffice.org-soikko Binary: openoffice.org-soikko Architecture: source i386 Version: 1.1.1-3 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno

Accepted openoffice.org-soikko 1.1.1-2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 25 Sep 2006 18:11:05 +0300 Source: openoffice.org-soikko Binary: openoffice.org-soikko Architecture: source i386 Version: 1.1.1-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno

Accepted openoffice.org-soikko 1.1.1-1.2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 23 Sep 2006 10:22:42 +0300 Source: openoffice.org-soikko Binary: openoffice.org-soikko Architecture: source i386 Version: 1.1.1-1.2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno

Accepted memaid-pyqt 0.2.5-2 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 21 Aug 2006 10:14:14 +0300 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.5-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted openoffice.org-soikko 1.1.1-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 3 Apr 2006 00:19:42 +0300 Source: openoffice.org-soikko Binary: openoffice.org2-soikko openoffice.org-soikko Architecture: source i386 Version: 1.1.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL

Accepted cfourcc 0.1.2-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 29 Mar 2006 20:21:15 +0300 Source: cfourcc Binary: cfourcc Architecture: source i386 Version: 0.1.2-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted openoffice.org2-soikko 1.0.1-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 25 Mar 2006 22:33:26 +0200 Source: openoffice.org2-soikko Binary: openoffice.org2-soikko Architecture: source i386 Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno

Bug#359657: ITP: cfourcc -- Command line tool for changing FourCC in Microsoft RIFF AVI files

Package: wnpp Severity: wishlist Owner: Jarno Elonen [EMAIL PROTECTED] * Package name: cfourcc Version : 0.1.2 Upstream Author : mypapit [EMAIL PROTECTED] * URL : http://sarovar.org/projects/gfourcc * License : GPL Description : Command line tool

Accepted agistudio 1.2.2-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Mar 2006 21:53:23 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.2-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted imediff2 1.1.1-1 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 10 Feb 2006 19:13:57 +0200 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.1.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 1.1.1-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 21 Nov 2005 09:13:20 +0200 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.1.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted memaid-pyqt 0.2.5-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 20 Oct 2005 11:42:33 +0300 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.5-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted memaid-pyqt 0.2.4-1 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 29 Sep 2005 00:11:08 +0300 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.4-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted agistudio 1.2.1-5 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 1 Sep 2005 22:24:15 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.1-5 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted memaid-pyqt 0.2.3-4 (source i386)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 21 Aug 2005 23:32:18 +0300 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.3-4 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted jpegpixi 1.1.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Jun 2005 13:17:26 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.1.0-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted memaid-pyqt 0.2.3-3 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 6 Apr 2005 11:29:10 +0300 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.3-3 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted jpegpixi 1.0.3-3 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 31 Mar 2005 12:50:27 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.0.3-3 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted memaid-pyqt 0.2.3-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Feb 2005 15:04:08 +0200 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.3-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted memaid-pyqt 0.2.3-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 Feb 2005 15:42:52 +0200 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.3-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted nagi 2.07b-6 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 3 Jan 2005 12:24:04 +0200 Source: nagi Binary: nagi Architecture: source i386 Version: 2.07b-6 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted memaid-pyqt 0.2.2-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 15 Nov 2004 01:06:22 +0200 Source: memaid-pyqt Binary: memaid-pyqt Architecture: source i386 Version: 0.2.2-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted imediff2 1.1.0+20041113-1 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 13 Nov 2004 01:18:42 +0200 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.1.0+20041113-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL

Accepted jpegpixi 1.0.3-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 27 Oct 2004 12:44:20 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.0.3-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted imediff2 1.1.0-1 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 22 Oct 2004 22:27:04 +0300 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.1.0-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 1.0.2-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 10 Oct 2004 00:28:09 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.0.2-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted imediff2 1.0.2-1 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 10 Oct 2004 02:44:39 +0300 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.0.2-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted agistudio 1.2.1-4 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 10 Oct 2004 03:01:09 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.1-4 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 1.0.1-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 4 Oct 2004 22:30:37 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 1.0.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 3 Oct 2004 15:59:48 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 1.0.0-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted metacam 1.2-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Sep 2004 01:43:09 +0300 Source: metacam Binary: metacam Architecture: source i386 Version: 1.2-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted metacam 1.2-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 4 Sep 2004 02:45:30 +0300 Source: metacam Binary: metacam Architecture: source i386 Version: 1.2-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 0.16.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Aug 2004 00:13:17 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 0.16.0-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted nagi 2.07b-5 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 22 Jul 2004 11:30:20 +0300 Source: nagi Binary: nagi Architecture: source i386 Version: 2.07b-5 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted imediff2 1.0.1-1 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 May 2004 21:16:53 +0300 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.0.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 0.15.1-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 7 May 2004 09:20:26 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 0.15.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 0.15.0-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 20 Apr 2004 15:42:18 +0300 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 0.15.0-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted jpegpixi 0.14.1-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 26 Jan 2004 12:13:59 +0200 Source: jpegpixi Binary: jpegpixi Architecture: source i386 Version: 0.14.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted imediff2 1.0-3 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 16 Jan 2004 11:41:41 +0200 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.0-3 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted nagi 2.07b-4 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 16 Jan 2004 11:35:09 +0200 Source: nagi Binary: nagi Architecture: source i386 Version: 2.07b-4 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted imediff2 1.0-2 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Nov 2003 14:46:34 +0200 Source: imediff2 Binary: imediff2 Architecture: source all Version: 1.0-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Problems verifying release.gpg

Hi, I'm having trouble verifying release.gpg for Unstable. Has the release key been changed to 30B34DD5, am I doing something wrong or what's up? After apt-secure failed to apt-get update today... Err http://ftp.fi.debian.org unstable Release The following signatures couldn't be verified

Re: Problems verifying release.gpg

I'm having trouble verifying release.gpg for Unstable. Has the release key been changed to 30B34DD5 Ah, so it has. I just found the announcement which had been filtered to a wrong mail folder by accident. Sorry. - Jarno

Bug#221135: ITP: imediff2 -- interactive full screen 2-way merge tool

Package: wnpp Severity: wishlist * Package name: imediff2 Version : 1.0 Upstream Author : Jarno Elonen [EMAIL PROTECTED] * URL : http://iki.fi/elonen/code/imediff/ * License : GPL Description : interactive full screen 2-way merge tool Imediff2 lets you

Accepted agistudio 1.2.1-2 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 11 Sep 2003 19:57:00 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.1-2 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted nagi 2.07b-3 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Aug 2003 19:26:30 +0300 Source: nagi Binary: nagi Architecture: source i386 Version: 2.07b-3 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Accepted agistudio 1.2.1-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 8 Aug 2003 10:07:44 +0300 Source: agistudio Binary: agistudio Architecture: source i386 Version: 1.2.1-1 Distribution: unstable Urgency: low Maintainer: Jarno Elonen [EMAIL PROTECTED] Changed-By: Jarno Elonen [EMAIL PROTECTED

Open questions of package descriptions (Was: Bug#198665: ITP: pmk...)

* lose the article Why? * do not capitalize the beginning of the description unless a proper noun, proper adjective, abbreviation, or acronym requires it Why? Argh, we really should decide these two points now and for good. Just today I received through DDTP a description

Proposal: a generic dpkg event hook broker

Hi, Packages often benefit from having other packages installed but don't necessary require them, hence 'suggests' and 'recommends'. Such packages, however, often require additional configuration to make them work with those optional packages. It's not usually very complicated and could in

Re: Debian conference in the US?

That's funny considering just how many people are risking their LIVES to get here. Then again, maybe its not, maybe its an insult to the ones who've died trying to get here over the years. I don't think not wanting to go somewhere is an insult to other people who do want to go there. The

Re: Debian conference in the US?

As other people have said: I'm not going, but I don't object to a conference in the US per se. Same here. Even if I had the money to attend, I wouldn't like to travel to the US because of the new copyright and anti-terrorist laws. Still, I think it's a good idea to arrange a conference for

Re: Accepted pointless 0.3-3 (i386 source)

Uhhh, nope, sorry. Close them correctly or don't close them at all. Note, that a new upload, that correctly closes the bugs, will be incorrect as well. The reason for that is [...] Although I'm not in any way involved in the actual issue: Thank you for a good and calm explanation, Adam. I

Re: dpkg conffiles merging - request for status summary

Afaik the original conffile is not available, dpkg just has the md5sum of it in /var/lib/dpkg/status. I doubt that two-way-merging is _very_ useful. Well, you can now try for yourself. :-) http://elonen.iki.fi/code/dpkg-merge/ - Jarno

Re: experimental conffile merge for dpkg

Why two-way merge instead of three-way? Because of... Unfortunately neither is currently possible at the moment, simply because dpkg doesn't save a copy of the last installed config file anywhere. ...this. I thought it would make big difference to have even 2-way merging now instead of

Re: experimental conffile merge for dpkg

There might be things to think about though: some packages have lots of conffiles, and that could mean some extra disk space, which not everyone will want to spend. Maybe make it optional. Bzipping could help, and maybe even tarring them all to one file. As a quick test, I bzip-tarred my

experimental conffile merge for dpkg

Hi, I've written an experimental conffile merge support for dpkg. http://elonen.iki.fi/code/dpkg-merge/ contains the patched dpkg and a new interactive python curses based two-way merge tool called imediff2 (+ 3 screenshots for the impatient). For those who would like try it: + install

Don't remove Reiserfstools (Re: plagiarism of reiserfs by Debian)

I guess if Reiser doesn't want an fsck/mkreiserfs without his beloved credits message, it's time to dump reiserfs from Debian and switch to ext3/XFS/whatever. Please don't. I'm running reiserfs on most of my home system's disks and have been *very* happy with it (..and don't even have the

Re: plagiarism of reiserfs by Debian

I note that few people are cc'ing Hans Reiser on things they seem to expect him to respond to; is everybody assuming that he's subscribed to debian-devel? Anyway, now that Ed has come back, let us just wait for him to clarify the issue with Hans (and/or continue the *license* debate in

Re: If Debian decides that the Gnu Free Doc License is not free...

(Hans Reiser wrote:) I look forward to the release of GPL V3 which will hopefully cover fair crediting of code as well as documentation, and stem this rising tide of plagiarism and political bowlderization by distros. I think nobody here has anything against keeping all the credits in

Re: If Debian decides that the Gnu Free Doc License is not free then I will be honored to join Stallman and the FSF in the not free section of your distro

We are having a small debate about wheter a user has freedom to modify code of free software when it concerns where a long version of author sponsor list is displayed. It has also been speculated that GPL v3 will have a say on this. Could elaborate what will be in it? (The following message

Re: If Debian decides that the Gnu Free Doc License is not free...

[About menu item] First time users go to them expecting to find out what the program does, and instead they get the name of the author and remain just as puzzled about what the program itself is for as they were before. I hate them. I see.. :) It has become a GUI idiom though, so most people

Re: plagiarism of reiserfs by Debian

It's also worth considering that perhaps there is a language difference (does Hans have English as a first language?) that make it seem that the email seem harsher than it really is. Many Europeans are naturally very honest with what they say and at first this comes across as been rude/blunt

dpkg conffiles merging - request for status summary

Just to bring the uninitiated like me up to date about ways to upgrade changed dpkg conffiles, I would greatly appreciate if someone with insight could summarize the current status: + How emotional has the discussion on this topic been in the past? Scale: 0 (mostly technical) ... 5

Re: New project proposal: debian-lex

rant If english people don't even know what lex means, they should make a damn effort and and learn it, or at least try to see if they can. The rest of people on Earth using computers have been having headaches learning stupid english slang words like widgets, gadgets or applets for years:

Re: anti-spam trick for debian ml (was Re: News about the Package Tracking System)

But for mailing lists it would be annoying to have to add an extra-header each time you want to write to the list. And there are people who don't use mutt or gnus and can't easily add arbitrary headers. I really think that this auto-approval thingie is just a temporary measure until we do

Re: Proposed handling of generated configuration files (Re: stop the manage with debconf madness)

ucf still has the same fundamental problem with regard to preconfiguration, which was the primary issue that I raised in my original message. The consensus, as I recall, was that preconfiguration is important, and that prompting in postinst should be minimized. I may have missed something

Re: Proposed handling of generated configuration files (Re: stop the manage with debconf madness)

I may have missed something but why can't the changed/merged configuration files be saved somewhere in preinstall phase [...] Again: see my first message and followups for a specific, concrete example of why this won't work. Thanks, I read the thread. So the reason was that configuration

Re: plagiarism of reiserfs by Debian

If the upstream author is rude to me, he does not deserve any consideration from myself. If he chooses to alienate his clientele, he should expect to reap what he sowed. The difficulty of their character unfortunately often seems to correlate with the important of their software. ;)

Re: Proposed handling of generated configuration files (Re: stop the manage with debconf madness)

I may have missed something but why can't the changed/merged configuration files be saved somewhere in preinstall phase and the [...] Well, for configuration files that require the unpacked package to generate, you can't ask during preconfiguration. For files created using non

Re: New project proposal: debian-lex

In England there is a move to remove all the Latin and obscure language from the Law, so I would suggest that the project should be called Debian-law not Debian-lex. lex is the better word, as it is not only known in English, but also in most other (roman) Languages for law. The first

Re: plagiarism of reiserfs by Debian

I'd hardly call it plagiarism. Your copyright is, by will of our own policy and to abide by authors wishes, distributed with the tools in /usr/share/doc/pkg/copyright. Ah.. I guess Hans is referring to the author list in README? The package maintainer probably looked at COPYING (contains GPL,

Re: Bug#189461: ITP: oilwar -- Defend your country from oil-thirsty invaders

Evil army is attacking your country and tries to steal your oil. Your mission is to waste the invaders, protect the oil and save your mother land. I'm not quite sure if you these joke games of current interest really deserve to go in the repository.. They usually have no playability nor any

Re: stop the manage with debconf madness

Would it already be time for a long term solution that no doubt has been discussed sometimes in the past: looking at configuration files in /etc and ~/.*, most of them are actually very simple. Instead of treating them as flat files with arbitrary content and *generating* the managed ones from

Re: Bug#188665: RC issue

I'm now getting a redefinition error and couldn't easily figure it out: In file included from conf_analysis_yy.h:5, from conf_analysis.yy:7: /usr/include/FlexLexer.h:112: redefinition of `class yyFlexLexer' /usr/include/FlexLexer.h:112: previous definition of

Re: Bug#127252: -unstable compiled against the wrong libpng

Problem is we still have lots of users who will be wondering where their graphics have gone and will be filing bug reports against all sorts of packages, as well as creating all sorts of bogus links to the wrong shared libraies to work around the problem. (Have a look in debian-kde) How