On Tue, Oct 17, 2006 at 03:36:12PM +0200, Stefano Melchior wrote:
dizionario friulano, nè quello sardo, nè qualsivoglia altro dizionario, si
può pensare ad un pacchetto a parte che dipende da aspell-it. In fin dei
conti è come se si installasse un dizionario secondario. Può essere
una
Error in the command: The original message was received at Thu, 19 Oct 2006
14:05:57 +0600 from 177.180.128.188
Unrecognized command verb: THE
Subsequent commands ignored because of previous error.
Ignored: - The following addresses had permanent fatal errors -
Ignored: [EMAIL PROTECTED]
On Wed, Oct 18, 2006 at 10:26:26AM -0200, Yves Junqueira wrote:
It may be much cleaner to include help links /etc/motd, adivising the
user to read a hipothetical
/usr/share/doc/linux-beginners/new-users, or enter a help-mode by
typing a certain command.
Or we could mimic FreeBSD behaviour:
Wouter Verhelst wrote:
Or we could mimic FreeBSD behaviour: create a fortune-file with helpful
tips for newbies, and add a line in the default initialization files
(i.e., those in /etc/skel) for different shells that calls fortune for
those tips.
You mean like fortunes-debian-hints[1]?
Kind
Hi,
I have developed some new software, an audioscrobbler client for last.fm, which I would
like to see included, probably under Multimedia.
It consists of two simple C source files - how do I go about getting it included
in Debian?
Cheers,
David.
[EMAIL PROTECTED] --
On Thu, Oct 19, 2006 at 10:58:42AM +0200, Thomas Viehmann wrote:
Wouter Verhelst wrote:
Or we could mimic FreeBSD behaviour: create a fortune-file with helpful
tips for newbies, and add a line in the default initialization files
(i.e., those in /etc/skel) for different shells that calls
On Thu, Oct 19, 2006 at 09:47:10AM +0100, David Moore wrote:
Hi,
I have developed some new software, an audioscrobbler client for last.fm,
which I would
like to see included, probably under Multimedia.
It consists of two simple C source files - how do I go about getting it
included
in
#include hallo.h
* Thomas Viehmann [Thu, Oct 19 2006, 10:58:42AM]:
Wouter Verhelst wrote:
Or we could mimic FreeBSD behaviour: create a fortune-file with helpful
tips for newbies, and add a line in the default initialization files
(i.e., those in /etc/skel) for different shells that calls
On Thu, Oct 19, 2006 at 09:47:10AM +0100, David Moore wrote:
Hi,
I have developed some new software, an audioscrobbler client for
_l_a_s_t_._f_m, which
I would
like to see included, probably under Multimedia.
It consists of two simple C source files - how do I go about getting
Em Wed, 18 Oct 2006 10:26:26 -0200
Yves Junqueira [EMAIL PROTECTED] escreveu:
It may be much cleaner to include help links /etc/motd, adivising the
user to read a hipothetical
/usr/share/doc/linux-beginners/new-users, or enter a help-mode by
typing a certain command.
Much cleaner, but I
also sprach martin f krafft [EMAIL PROTECTED] [2006.10.17.1618 +0200]:
Thus, unless I get other suggestions, I'll package it up in its
own package, which diverts /sbin/{reboot,halt,shutdown} and puts
my shell script in their place. I'll Enhance whatever init systems
there are and I'll ask them
Dear list...
I'm the maintainer of the ethstatus package - a console-based ethernet
statistics monitor. You can e.g. run it on your gateway's 9 CRT on the
console and see how much bandwidth is currently used in a bar-like view.
I'm in the process of RFA'ing the package. But I wonder whether I
Hi all,
I have just run lintian on all the archive (amd64) for both binaries and
sources, and the results are a bit scary. It looks like a lot of
maintainers are uploading their packages, and don't really care with the
policy.
Maybe some errors (E:) of lintian could be changed to critical (C:)
Christoph Haas [EMAIL PROTECTED] writes:
I'm unhappy with the missing upstream situation. I could also wait for a
volunteer to maintain both the software and the maintainer.
^^
What kind of maintenance do *you* need?
Matthias
--
To
Hi all,
I maintain the package wormux and my dear upstream devels decided to
switch from autotools to cmake, for the best and the worse.
Are there people with experiences with it ? Maybe kde packagers are
already working on it ?
As a side effect, can someone tell me if there is a command to
[Aurelien Jarno]
I have just run lintian on all the archive (amd64) for both binaries and
sources, and the results are a bit scary. It looks like a lot of
maintainers are uploading their packages, and don't really care with the
policy.
What is the technical problem triggered by the
On 10/19/06, Jean Parpaillon [EMAIL PROTECTED] wrote:
As a side effect, can someone tell me if there is a command to search
for packages regarding Build-Depends ?
grep-dctrl -sPackage -F Build-Depends,Build-Depends-Indep cmake
/var/lib/apt/lists/*Sources
Or, see the more elaborate version,
On 10/19/06, Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Aurelien Jarno]
I have just run lintian on all the archive (amd64) for both binaries and
sources, and the results are a bit scary. It looks like a lot of
maintainers are uploading their packages, and don't really care with the
[Tshepang Lekhonkhobe]
Doesn't policy violation warrant Critical severity?
Well, policy isn't a stick to beat other maintainers with, it is a
tool to make sure our packages are well integrated and work properly.
Thus, policy issues are not problems by themselves, they are policy
issues because
Tshepang Lekhonkhobe wrote:
Doesn't policy violation warrant Critical severity?
No, it only warrants the lowest RC severity, serious [0], unless the
bug in addition makes the package or other software (mostly) unusable,
causes data loss, or introduces a security hole.
[0]
On Thursday 19 October 2006 18:45, Petter Reinholdtsen wrote:
If no problem is caused by it, I believe 'normal' or even 'wishlist'
severity is the proper severity to use.
s/wishlist/minor/
It _is_ a bug after all.
pgp8CuxfBlHbn.pgp
Description: PGP signature
On Thu, Oct 19, 2006 at 06:45:53PM +0200, Petter Reinholdtsen wrote:
Well, policy isn't a stick to beat other maintainers with, it is a
tool to make sure our packages are well integrated and work properly.
Thus, policy issues are not problems by themselves, they are policy
issues because they
* Tshepang Lekhonkhobe ([EMAIL PROTECTED]) [061019 18:09]:
On 10/19/06, Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Aurelien Jarno]
I have just run lintian on all the archive (amd64) for both binaries and
sources, and the results are a bit scary. It looks like a lot of
maintainers are
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 15:06]:
Among all of the bugs reported by lintian, one concerns a lot of
packages, the presence of the clean, binary, binary-arch, binary-indep
and build targets. This is required by both the section 4.9 of the
policy and the Etch release standards
On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
Doesn't policy violation warrant Critical severity?
No. Please see the top of http://release.debian.org/etch_rc_policy.txt
for which bugs are critical, grave and serious.
That is irrelevant for the severity of
On Thu, Oct 19, 2006 at 07:01:20PM +0200, Frans Pop wrote:
On Thursday 19 October 2006 18:45, Petter Reinholdtsen wrote:
If no problem is caused by it, I believe 'normal' or even 'wishlist'
severity is the proper severity to use.
s/wishlist/minor/
It _is_ a bug after all.
On Thu, 2006-10-19 at 19:51 +0200, Mike Hommey wrote:
On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
Doesn't policy violation warrant Critical severity?
No. Please see the top of http://release.debian.org/etch_rc_policy.txt
for which bugs are
On Thu, 2006-10-19 at 10:00 -0700, Kevin B. McCarty wrote:
Tshepang Lekhonkhobe wrote:
Doesn't policy violation warrant Critical severity?
No, it only warrants the lowest RC severity, serious [0], unless the
bug in addition makes the package or other software (mostly) unusable,
causes
On Thu, Oct 19, 2006 at 07:51:19PM +0200, Mike Hommey wrote:
On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
Doesn't policy violation warrant Critical severity?
No. Please see the top of http://release.debian.org/etch_rc_policy.txt
for which bugs are
On Thu, Oct 19, 2006 at 11:29:38AM -0700, Steve Langasek [EMAIL PROTECTED]
wrote:
On Thu, Oct 19, 2006 at 07:51:19PM +0200, Mike Hommey wrote:
On Thu, Oct 19, 2006 at 07:36:27PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
Doesn't policy violation warrant Critical severity?
No.
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
Note how subtly the Etch RC policy removes the first alternative of the
serious bug description...
Which do you mean? Please read the Etch RC policy. It tells:
| In addition to the issues listed in this document, an issue is release
| critical
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
Note how subtly the Etch RC policy removes the first alternative of the
serious bug description...
Which do you mean? Please read the Etch RC policy. It
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
Note how subtly the Etch RC policy removes the first alternative of the
serious bug description...
On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
Note how subtly the
Andreas Barth a écrit :
A violation of the parts of the debian policy as listed on
http://release.debian.org/etch_rc_policy.txt is serious level (that
should be the same as the must-directives in policy, but - well, I hope
that I have finally time post-etch to sync that finally).
Any other
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:25]:
On Thu, Oct 19, 2006 at 09:17:38PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL
PROTECTED] wrote:
* Mike Hommey
* Andreas Barth ([EMAIL PROTECTED]) wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 20:42]:
Note how subtly the Etch RC policy removes the first
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 21:31]:
Andreas Barth a écrit :
A violation of the parts of the debian policy as listed on
http://release.debian.org/etch_rc_policy.txt is serious level (that
should be the same as the must-directives in policy, but - well, I hope
that I have
On Thu, Oct 19, 2006 at 09:35:38PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
But I need to admit that I get sick, seriously sick. If someone doesn't
agree with something, he just says you do it wrong just for release of
etch on $date. I really hate that. Especially when it's about things
On Thu, Oct 19, 2006 at 03:53:56PM -0400, Eric Dorland [EMAIL PROTECTED]
wrote:
* Andreas Barth ([EMAIL PROTECTED]) wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 21:14]:
On Thu, Oct 19, 2006 at 09:06:42PM +0200, Andreas Barth [EMAIL
PROTECTED] wrote:
* Mike Hommey ([EMAIL
On Thu, Oct 19, 2006 at 09:56:37PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Aurelien Jarno ([EMAIL PROTECTED]) [061019 21:31]:
Andreas Barth a écrit :
A violation of the parts of the debian policy as listed on
http://release.debian.org/etch_rc_policy.txt is serious level (that
Hello d-dev,
I noticed yesterday that after an upgrade I got a /usr/lib64 dir
with some (not neded) stuff in it. I am not running any 64 bit arch.
$ dpkg -S /usr/lib64 # says:
libg2c0-dev, fakeroot, libgfortran1-dev: /usr/lib64
I have found that there is a bug [1] on fakeroot reporting the
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:06]:
That was not a link before it was changed before sarge release, in July
2004.
The link was added later because people were barking around. The meaning
was always the same.
Anyways, July 2004 is a *bit* history now, don't you think so?
So,
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]:
Where does it say the scope for 4. Autobuilding is buildds must not
fail ?
There are always bugs in any document.
For sarge, we e.g. sarge-ignored some MTAs which didn't provide -bs,
though LSB requires that. Now, we adjusted the policy to make
On Thu, Oct 19, 2006 at 10:15:16PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:06]:
That was not a link before it was changed before sarge release, in July
2004.
The link was added later because people were barking around. The meaning
was
On Thu, Oct 19, 2006 at 10:20:46PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]:
Where does it say the scope for 4. Autobuilding is buildds must not
fail ?
There are always bugs in any document.
Be aware that, even if you don't like it,
Hello,
Frank Küster napsal:
Jiri Palecek [EMAIL PROTECTED] wrote:
Hello,
can anyone explain why gcc-4.2 build-depends on libgconf2-dev,
libxul-dev, libart-2.0-dev, libgtk2.0-dev,
lib32asound2-dev, libcairo2-dev, libqt4-dev and several others? It
seems quite strange (well, even
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
[another agression]
Sorry, but enough is enough. I'm fed up about your sudden agressions
towards me for no reason at all. Welcome to my killfile.
Andi
--
http://home.arcor.de/andreas-barth/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Mike Hommey [EMAIL PROTECTED] wrote:
On Thu, Oct 19, 2006 at 10:20:46PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:09]:
Where does it say the scope for 4. Autobuilding is buildds must not
fail ?
There are always bugs in any document.
Be
On Thursday 19 October 2006 13:37, Christoph Haas wrote:
I'm the maintainer of the ethstatus package - a console-based ethernet
statistics monitor. You can e.g. run it on your gateway's 9 CRT on the
console and see how much bandwidth is currently used in a bar-like view.
I'm in the process of
Mike Hommey [EMAIL PROTECTED] writes:
So, what does the Etch RC policy remove from the bugs.d.o description?
'is a severe violation of Debian policy (roughly, it violates a must or
required directive), or'
Perhaps you should concentrate on the word roughly there. What
constitutes a severe
Mike Hommey [EMAIL PROTECTED] wrote:
Be aware that, even if you don't like it, this looks like you bend the
rules so that it doesn't alter the release plan.
Be also aware that too much bending the rules makes them useless.
Don't try to bend the rules, it's impossible. Instead, only realize
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
[another agression]
Waw, actually, i was trying to be less aggressive...
Anyways, since I'm too pissed and since I see no reason to put myself in
that mood any
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
[another agression]
Sorry, but enough is enough. I'm fed up about your sudden agressions
towards me for no reason at all. Welcome to my killfile.
Hi Andi,
from my
On Thu, Oct 19, 2006 at 10:52:25PM +0200, Mike Hommey wrote:
On Thu, Oct 19, 2006 at 10:37:38PM +0200, Andreas Barth [EMAIL PROTECTED]
wrote:
* Mike Hommey ([EMAIL PROTECTED]) [061019 22:29]:
[another agression]
Waw, actually, i was trying to be less aggressive...
This is a very, very
[Sander Marechal]
True, but I meant that an app can kill X, requiring it to be restarted.
Newbies get very confused at that point.
Look, if you typed startx once, you can type it again.
If you didn't, it means you're using a display manager like xdm, and
xdm will restart X when it dies.
If X
On Thu, 19 Oct 2006, Kevin Mark wrote:
DD's trying to use Debian policy as a guide to make all packages
pass policy requirement. Is this not what they are tasked to do?
There's nothing wrong with these goals. Indeed, I'm sure no one would
object to patches and bugs being filed to fix these
Hello,
There is a link to Checklib [0] in the Packages Overview page
of every maintainer. See for example vorlon's page at [1] where
you could see that link in the line starting with Reports:.
[0] http://rerun.lefant.net/checklib/
[1] http://qa.debian.org/developer.php?login=vorlon
I couldn't
On Fri, 20 Oct 2006 08:47:48 +1000, Aníbal Monsalve Salazar wrote:
I also couldn't find in the FAQ [3] any reference about how to
download checklib.
[3] http://rerun.lefant.net/checklib/faq.html
How can download and run checklib?
On http://rerun.lefant.net/checklib/ the last line says:
On Friday 20 October 2006 08:06, Peter Samuelson wrote:
[Sander Marechal]
True, but I meant that an app can kill X, requiring it to be restarted.
Newbies get very confused at that point.
Look, if you typed startx once, you can type it again.
If you didn't, it means you're using a display
access news: Hot XXX Fuckoing!!! Thebse girls lopve a nice stbiff coyck!! :)
GOTO: *** plbrl.zopurar.com ***
their capo look really eyes provide soon, after here can, form twice link all
form?
loose eyes surf add today out forever order; self and, just other they.
face online are told, access
On 10/19/06, Mike Hommey [EMAIL PROTECTED] wrote:
Waw, actually, i was trying to be less aggressive...
Anyways, since I'm too pissed and since I see no reason to put myself in
that mood any further, I'm taking a few days off Debian, which means my
current work on seamonkey^Hiceape will be on
[EMAIL PROTECTED] wrote:
Hello,
Frank Küster napsal:
Jiri Palecek [EMAIL PROTECTED] wrote:
Hello,
can anyone explain why gcc-4.2 build-depends on libgconf2-dev,
libxul-dev, libart-2.0-dev, libgtk2.0-dev,
lib32asound2-dev, libcairo2-dev, libqt4-dev and several others? It
seems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 09:07:55 +0200
Source: gui-apt-key
Binary: gui-apt-key
Architecture: source all
Version: 0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Martin Schulze [EMAIL PROTECTED]
Changed-By: Martin Schulze [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 23:01:42 +0200
Source: galeon
Binary: galeon galeon-common
Architecture: source i386 all
Version: 2.0.2-3
Distribution: unstable
Urgency: low
Maintainer: Loic Minier [EMAIL PROTECTED]
Changed-By: Loic Minier [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 17:58:35 +0200
Source: swish-e
Binary: swish-e swish-e-dev
Architecture: source i386
Version: 2.4.3-7
Distribution: unstable
Urgency: high
Maintainer: Ludovic Drolez [EMAIL PROTECTED]
Changed-By: Ludovic Drolez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 06:58:20 +0200
Source: mono
Binary: libmono-peapi1.0-cil libmono-cscompmgd8.0-cil libmono-security2.0-cil
libmono-system-runtime2.0-cil libmono-security1.0-cil libmono-relaxng2.0-cil
mono-mjs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:01:48 +0200
Source: gconf2
Binary: libgconf2-4 gconf2 gconf2-common libgconf2-dev
Architecture: source i386 all
Version: 2.16.0-2
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 07:48:13 +0200
Source: gcc-m68hc1x
Binary: gcc-m68hc1x
Architecture: source amd64
Version: 1:3.3.6+3.1+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno [EMAIL PROTECTED]
Changed-By: Aurelien
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 00:02:29 -0700
Source: tomboy
Binary: tomboy
Architecture: source i386
Version: 0.4.1-2
Distribution: unstable
Urgency: low
Maintainer: Dave Beckett [EMAIL PROTECTED]
Changed-By: Dave Beckett [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 23:45:26 +0200
Source: hal
Binary: libhal-dev libhal-storage1 hal-doc libhal-storage-dev hal libhal1
hal-device-manager
Architecture: source i386 all
Version: 0.5.8.1-2
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:46:48 +0200
Source: libgtk-trayicon-ruby
Binary: libgtk-trayicon-ruby libgtk-trayicon-ruby1.8
Architecture: source all amd64
Version: 0.1.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 10:03:57 +0200
Source: revolution
Binary: libevolution-ruby libevolution-ruby1.8
Architecture: source all amd64
Version: 0.5-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 10:01:31 +0200
Source: gtksourceview
Binary: libgtksourceview-dev libgtksourceview-common libgtksourceview1.0-0
libgtksourceview-doc
Architecture: source all i386
Version: 1.8.1-2
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:41:44 +0200
Source: libform-validator-ruby
Binary: libform-validator-ruby1.8 libform-validator-ruby
Architecture: source all
Version: 0.1.4-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 21:52:53 +0300
Source: firebird2
Binary: firebird2-utils-classic libfbclient1 firebird2-super-server libfbembed1
firebird2-dev firebird2-server-common firebird2-utils-super firebird2-examples
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:34:22 +0200
Source: gwget2
Binary: gwget epiphany-extension-gwget
Architecture: source amd64
Version: 0.97-2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Michael
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:23:52 +0200
Source: dlume
Binary: dlume
Architecture: source amd64
Version: 0.2.4-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Michael Ablassmeier [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 10:03:02 +0200
Source: libtermios-ruby
Binary: libtermios-ruby libtermios-ruby1.8
Architecture: source all amd64
Version: 0.9.4-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:31:37 +0200
Source: fpm
Binary: fpm
Architecture: source amd64
Version: 0.60-2
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Michael Ablassmeier [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 15 Oct 2006 14:43:26 +0300
Source: nzb
Binary: nzb
Architecture: source amd64
Version: 0.1.6-1
Distribution: unstable
Urgency: low
Maintainer: Mattias Nordstrom [EMAIL PROTECTED]
Changed-By: Mattias Nordstrom [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 10:22:18 +0200
Source: wallpaper-tray
Binary: wallpaper-tray
Architecture: source amd64
Version: 0.4.6-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Michael
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 11:37:40 +0200
Source: moodle
Binary: moodle
Architecture: source all
Version: 1.6.3-1
Distribution: unstable
Urgency: low
Maintainer: Isaac Clerencia [EMAIL PROTECTED]
Changed-By: Isaac Clerencia [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 11:09:37 +0200
Source: gforge
Binary: gforge-lists-mailman gforge-db-postgresql gforge-mta-postfix
gforge-shell-ldap gforge gforge-common gforge-web-apache gforge-mta-exim
gforge-mta-courier gforge-ftp-proftpd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 11:41:08 +0200
Source: gnome-menus
Binary: python-gmenu libgnome-menu2 gnome-menus libgnome-menu-dev
Architecture: source i386
Version: 2.16.0-2
Distribution: unstable
Urgency: low
Maintainer: Sebastien Bacher [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 13:01:44 +0200
Source: texlive-extra
Binary: texlive-pstricks texlive-plain-extra texlive-formats-extra
texlive-latex-extra texlive-latex3 texlive-chemistry texlive-generic-extra
texlive-games texlive-publishers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:02:04 +0200
Source: quota
Binary: quota
Architecture: source i386
Version: 3.14-3
Distribution: unstable
Urgency: low
Maintainer: Michael Meskes [EMAIL PROTECTED]
Changed-By: Michael Meskes [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 11:28:12 +0200
Source: libgnome
Binary: libgnome2-common libgnome2-0 libgnome2-doc libgnome2-dev
Architecture: source all i386
Version: 2.16.0-2
Distribution: unstable
Urgency: low
Maintainer: OndÅej Surý [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 18 Oct 2006 18:00:00 +0100
Source: coco-cs
Binary: coco-cs
Architecture: source all
Version: 20060919-2
Distribution: unstable
Urgency: low
Maintainer: Loeberbauer Markus [EMAIL PROTECTED]
Changed-By: Markus Loeberbauer [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 12:31:32 +0200
Source: libapache2-mod-encoding
Binary: libapache2-mod-encoding
Architecture: source amd64
Version: 20040616-4.2
Distribution: unstable
Urgency: medium
Maintainer: Tatsuki Sugiura [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 10:27:51 +0200
Source: texlive-bin
Binary: texlive-extra-utils texlive-pdfetex texlive-lang-indic texlive-omega
texlive-font-utils texlive-metapost texlive-base-bin texlive-music
Architecture: source i386
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 12:30:07 +0100
Source: clamav
Binary: clamav libclamav-dev clamav-dbg clamav-milter clamav-base
clamav-freshclam clamav-testfiles clamav-daemon libclamav1 clamav-docs
Architecture: source i386 all
Version: 0.88.5-2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 17 Oct 2006 18:27:31 +0100
Source: mod-bt
Binary: libbtutil0-dev libbttracker-utils libbttracker0 libapache2-mod-bt
libbttracker0-dev php5-apache2-mod-bt libbtutil-utils libbtutil0
php4-apache2-mod-bt libapache2-mod-bt-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 13:12:05 +0200
Source: kipina
Binary: kipina
Architecture: source amd64
Version: 0.1.1-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Michael Ablassmeier [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 14:46:32 +0200
Source: fai
Binary: fai-client fai-server fai-doc fai-quickstart fai-nfsroot
Architecture: source all
Version: 3.1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Lange [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 12:01:00 +0200
Source: ncurses
Binary: ncurses-base lib64ncurses5 libncursesw5-dev libncursesw5-dbg
ncurses-bin libncurses5 libncursesw5 libncurses5-dev ncurses-term
lib32ncurses5-dev lib32ncurses5 libncurses5-dbg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 12:55:26 +0200
Source: xmms-jess
Binary: xmms-jess
Architecture: source amd64
Version: 2.9.1-8.1
Distribution: unstable
Urgency: low
Maintainer: John Lightsey [EMAIL PROTECTED]
Changed-By: Michael Ablassmeier [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 13:44:12 +0100
Source: libclass-dbi-perl
Binary: libclass-dbi-perl
Architecture: source all
Version: 3.0.15-1
Distribution: unstable
Urgency: low
Maintainer: Stephen Quinney [EMAIL PROTECTED]
Changed-By: Stephen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 09:50:49 +0200
Source: xine-ui
Binary: xine-ui
Architecture: source i386
Version: 0.99.4+cvs20061019-1
Distribution: unstable
Urgency: low
Maintainer: Siggi Langauf [EMAIL PROTECTED]
Changed-By: Reinhard Tartler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 Oct 2006 14:50:09 +0200
Source: hddtemp
Binary: hddtemp
Architecture: source amd64
Version: 0.3-beta15-30
Distribution: unstable
Urgency: medium
Maintainer: Aurelien Jarno [EMAIL PROTECTED]
Changed-By: Aurelien Jarno [EMAIL
1 - 100 of 121 matches
Mail list logo
