On Mon, Aug 15, 2005 at 02:18:39AM +0200, Henning Makholm wrote:
...a lot of wise things...
I have to agree. So how to proceed? File minor bugs against
README files, that contain predominantly useless information?
Cheers,
--
W. Borgert [EMAIL PROTECTED], http://people.debian.org/~debacle/
On Sun, Aug 14, 2005 at 08:29:47PM -0300, Ben Armstrong wrote:
Says who? I maintain some packages like this. Let's say I support 50
to 100 niche users for a given package, but I'm the only developer in
the user community who cares to maintain the package in Debian. I
maintain the package
W. Borgert [EMAIL PROTECTED] writes:
Sorry, if people thought I want to propose enforcement of team
maintenance policy. However, team maintenance for all essential
and standard is worthwhile and not un-realistic.
It's a good idea to discuss it, unless it's been discussed to death
already.
Package: wnpp
Severity: wishlist
Owner: martin f krafft [EMAIL PROTECTED]
* Package name: libboost-log
Version : 0.0.20050801
Upstream Author : John Torjo john ät torjo.com
* URL : http://www.torjo.com/code/logging.zip
* License : Boost Public Licence
John Hasler [EMAIL PROTECTED] wrote:
Perhaps the upstream README should be renamed 'README.upstream'?
Why? We currently do not denote every file shippped by upstream with a
.upstream suffix but instead earmark added, Debian-specific items
using the same base name with a .Debian suffix.
This
On Mon, August 15, 2005 01:42, Ben Armstrong wrote:
Why not just help improve upstream's README when you encounter poor
quality work? That's what you'd do with code, wouldn't you?
Requirements on upstream README and information that's useful within
Debian differ. It often contains information
Scripsit W. Borgert [EMAIL PROTECTED]
On Mon, Aug 15, 2005 at 02:18:39AM +0200, Henning Makholm wrote:
...a lot of wise things...
I have to agree. So how to proceed? File minor bugs against
README files, that contain predominantly useless information?
What other way would there be to
On Mon, Aug 15, 2005 at 12:16:24AM -0500, Adam Heath wrote:
When a new source gets uploaded, it replaces the previous. If several NMUs
occur, each one replaces the former. So, when the real maintainer(s) wake up,
they can only see the most recent NMU that took place.
Only if each NMU does
On Sun, Aug 14, 2005 at 02:15:43PM +, W. Borgert wrote:
Assumptions:
III. The responsiveness on bug reports is higher, as more people
can react without having to NMU. Adjustments between team
members can slow down this, but this is just a matter of
agreements inside the
On Mon, 15 Aug 2005, Thijs Kinkhorst wrote:
It is not said that upstream README's are useless per se; I think
W.Borgert's point is the following: judge each upstream README on its own
merits. I agree that currently many people will automatically install this
README in the /u/s/doc dir,
On Sun, Aug 14, 2005 at 01:25:37PM -0500, John Hasler wrote:
Perhaps the upstream README should be renamed 'README.upstream'?
Given the context, it would probably make more sense to rename it to IGNOREME.
--
.''`. ** Debian GNU/Linux ** | Andrew Suffield
: :' : http://www.debian.org/ |
On Fri, 12 Aug 2005, Javier Fernández-Sanguino Peña wrote:
On Fri, Aug 12, 2005 at 09:52:38AM -0500, John Hasler wrote:
Timo Aaltonen writes:
Is there will to change the current policy regarding runlevels in Debian?
I'd propose to use the recommendation made by LSB:
Please check the
On Mon, Aug 15, 2005 at 10:55:20AM +0200, Andreas Tille wrote:
Idea 1:
lintian: W: /usr/share/doc/README contains installation instructions
I like that one.
Cheers,
--
Wolfgang Borgert [EMAIL PROTECTED], http://people.debian.org/~debacle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
On Mon, Aug 15, 2005 at 09:53:37AM +0200, Henning Makholm wrote:
Go ahead and file bugs. With patches. And perhaps an explanation
of why a README in the .deb is not required and, if it exists, is not
required to equal upstream's.
When a few dozen of your patches have made it to sid, condense
Bernd Eckenfels wrote:
In article [EMAIL PROTECTED] you wrote:
Please fix your packages. Filing bugs on nearly 500 packages is
something I'd prefer not to do
Why do you have filled bug reports, then? Only for my packages?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322813
Scripsit W. Borgert [EMAIL PROTECTED]
On Mon, Aug 15, 2005 at 10:55:20AM +0200, Andreas Tille wrote:
Idea 1:
lintian: W: /usr/share/doc/README contains installation instructions
I like that one.
Yes - but how should Lintian detect it? Of course one could look for
lines that start
I'm sure when I read through this thread the first time, I saw an
argument Get the mozilla people onto our wavelength, but I can't find
it now.
On Sun, Jul 31, 2005 at 10:01:15PM +0200, Martin Pitt wrote:
It was not an easy decision since usually we follow the same strict
minimal patches
On Fri, Aug 12, 2005 at 06:29:58PM +0900, wrote:
Hi,
I think that ruby1.6 should be removed from Debian.
Because Ruby 1.6.x is the old stable version of Ruby.
(current stable version is Ruby 1.8.x.)
I had authored some very simple ruby scripts on a stable machine in 1.6
which are now
Scripsit Timo Aaltonen [EMAIL PROTECTED]
2 multi-user, no network services exported, no NFS
-more secure service-wise than 3
-RH has network here, although they claim that 2 is not used
Given that it is very rare for machines these days to have banks of
local ttys attached, is a
On Sat, Aug 13, 2005 at 06:33:59PM +0200, Marc 'HE' Brockschmidt wrote:
Ron Johnson [EMAIL PROTECTED] writes:
apt-rdepends
Interesting, but not useful for the case I had today:
[EMAIL PROTECTED]:~$ apt-rdepends --build-depends --reverse foo
E: Reverse build-dependencies are not supported
* Henning Makholm [EMAIL PROTECTED] [2005-08-15 13:17:02]:
Scripsit Timo Aaltonen [EMAIL PROTECTED]
2 multi-user, no network services exported, no NFS
-more secure service-wise than 3
-RH has network here, although they claim that 2 is not used
Given that it is very rare for
On Mon, Aug 15, 2005 at 02:16:30PM +0200, Andreas Schuldei wrote:
My workstation has two heads, with independent Xservers, one for
me and one for my wife. The number of heads is limited by the
number of PCI/AGP video cards you can use. The linuxconsole
project works on a kernel patch that
On Mon, Aug 15, 2005 at 12:42:27PM +0200, Henning Makholm wrote:
Yes - but how should Lintian detect it? Of course one could look for
lines that start with whitespace plus ./configure , but how reliable
is that?
Attached test found some culprits: aptitude autofs dbus-1
dbus-glib-1 deborphan
[Steinar H. Gunderson]
How do you make this work? Last time I tried it, X would only show
the one connected to the ???active??? virtual console, and blanked
the other.
It need some patches to the kernel and X. I'm not sure how many of
these are included in the mainstream kernel and X
On Mon, 15 Aug 2005, Henning Makholm wrote:
Scripsit Timo Aaltonen [EMAIL PROTECTED]
2 multi-user, no network services exported, no NFS
-more secure service-wise than 3
-RH has network here, although they claim that 2 is not used
Given that it is very rare for machines these days to
On Mon, 2005-08-15 at 10:08 +0200, Thijs Kinkhorst wrote:
On Mon, August 15, 2005 01:42, Ben Armstrong wrote:
Why not just help improve upstream's README when you encounter poor
quality work? That's what you'd do with code, wouldn't you?
Requirements on upstream README and information
On Mon, 2005-08-15 at 06:14 +, W. Borgert wrote:
Some of the things under Dogme05 is certainly exaggeration.
Sorry, if people thought I want to propose enforcement of team
maintenance policy. However, team maintenance for all
essential and standard is worthwhile and not un-realistic.
W. Borgert wrote:
- Readme file for package.
Really?
Can be useful on printouts.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Scripsit W. Borgert [EMAIL PROTECTED]
On Mon, Aug 15, 2005 at 12:42:27PM +0200, Henning Makholm wrote:
Yes - but how should Lintian detect it? Of course one could look for
lines that start with whitespace plus ./configure , but how reliable
is that?
Attached test found some culprits:
It
Scripsit Timo Aaltonen [EMAIL PROTECTED]
On Mon, 15 Aug 2005, Henning Makholm wrote:
Given that it is very rare for machines these days to have banks of
local ttys attached, is a multi-user without network runlevel really
relevant for even a significant minory of our users? How would those
Scripsit Ben Armstrong [EMAIL PROTECTED]
On Mon, 2005-08-15 at 10:08 +0200, Thijs Kinkhorst wrote:
Requirements on upstream README and information that's useful within
Debian differ. It often contains information about building, installation
or bug reporting which is not relevant to Debian.
Henning Makholm wrote:
Given that it is very rare for machines these days to have banks of local
ttys attached, is a multi-user without network runlevel really relevant
for even a significant minory of our users? How would those multiple
users interact with the machine?
Timo Aaltonen writes:
Scripsit Thijs Kinkhorst [EMAIL PROTECTED]
I agree that currently many people will automatically install this
README in the /u/s/doc dir, regardless of its contents, while it
would make more sense to make a judgement whether including it
actually adds value.
I notice that dh-make will
On Mon, Aug 15, 2005 at 02:59:17PM +0200, Petter Reinholdtsen wrote:
[Steinar H. Gunderson]
How do you make this work? Last time I tried it, X would only show
the one connected to the ???active??? virtual console, and blanked
the other.
It need some patches to the kernel and X. I'm not
Package: lists.debian.org
Severity: wishlist
Hi,
I'd like to have a debian-planet list that would receive blog postings
from planet.debian.org.
The main reason is that after postings expire on the planet website,
it's very hard to find old postings if you cannot remember who wrote
it. Think of
Scripsit John Hasler [EMAIL PROTECTED]
Bringing the machine up without networking can be useful for problem
solving. I prefer to use multiple consoles when doing so. This requires
multiuser.
Perhaps I'm just missing some specific technical definition of
multiuser, but what you describe
Thijs Kinkhorst [EMAIL PROTECTED] writes:
Requirements on upstream README and information that's useful within
Debian differ. It often contains information about building,
installation or bug reporting which is not relevant to Debian.
I don't understand why people keep saying that upstream
On Mon, Aug 15, 2005 at 05:08:58PM +0200, Christoph Berg wrote:
I'd like to have a debian-planet list that would receive blog postings
from planet.debian.org.
Please don't introduce any more namespace confusion.
Cheers,
Rob
--
Rob Bradford - http://robster.org.uk
--
To UNSUBSCRIBE,
Mala direta via email e divulgação de Sites Mala direta via email e divulgação
de Sites mala direta dividida por atividade:
http://www.segmails.vze.com
ou
http://www.vendemails.cjb.net
ou
http://geocities.yahoo.com.br/webneggocios/listagemnova.htm
e-mails e-mail free marketing mala direta
Re: Rob Bradford in [EMAIL PROTECTED]
I'd like to have a debian-planet list that would receive blog postings
from planet.debian.org.
Please don't introduce any more namespace confusion.
Agreed. What about debian-planet-feed?
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
[Daniel Stone]
Ubuntu implements this from the installer down (although only for
the special cases of four nVidia, MGA, or ATI cards, and even then
you may need to fiddle with the configuration a little bit), with a
bunch of patches to xorg -- no kernel patches required. Those
patches are
On Mon, Aug 15, 2005 at 06:14:23PM +0200, Christoph Berg wrote:
Re: Rob Bradford in [EMAIL PROTECTED]
I'd like to have a debian-planet list that would receive blog postings
from planet.debian.org.
Please don't introduce any more namespace confusion.
Agreed. What about
On Mon, 2005-08-15 at 16:31 +0200, Henning Makholm wrote:
I don't think there is a way to get around this difference. There is a
fairly widespread convention of putting compilation instructions in an
INSTALL file, but there is no similarly widespread convention for
putting information about,
On Mon, 2005-08-15 at 08:54 -0700, Russ Allbery wrote:
I don't understand why people keep saying that upstream bug reporting
instructions are irrelevant to Debian. Surely I'm not the only person who
wants to be able to discuss some issues directly with upstream when
they're not in the
I hope a developer out there with access to commit packages can take the
initiative to package up agentcell. The authors settled on releasing
this software package under the GPL. It's a great contribution to the
scientific community.
Just thought I'd pass on the word,
Jeff
--
To UNSUBSCRIBE,
On Monday 15 August 2005 07:45 am, John Hasler wrote:
Bringing the machine up without networking can be useful for problem
solving. I prefer to use multiple consoles when doing so. This requires
multiuser.
You can also use openvt(1) in single-user mode.
Daniel
--
/---
On Mon, Aug 15, 2005 at 06:19:08PM +0200, Petter Reinholdtsen wrote:
[Daniel Stone]
Ubuntu implements this from the installer down (although only for
the special cases of four nVidia, MGA, or ATI cards, and even then
you may need to fiddle with the configuration a little bit), with a
Ben Armstrong [EMAIL PROTECTED] writes:
While exceptions certainly exist, most of the time, a user reporting a
bug on a Debian package directly upstream is not appropriate. It is
better for the user to first seek help from their distribution. Then,
if it is clear that the issue is
Package: wnpp
Severity: wishlist
Owner: Florian Ragwitz [EMAIL PROTECTED]
* Package name: viruskiller
Version : 1.0-1
Upstream Author : Stephen Sweeney [EMAIL PROTECTED]
* URL : http://www.parallelrealities.co.uk/virusKiller.php
* License : GPL-2
Description
Package: wnpp
Followup-For: Bug #302538
Owner: Steffen Joeris [EMAIL PROTECTED]
I intend to package unignuplot. We (Debian-edu) are interested in
unignuplot, because of educational purposes.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500,
Package: wnpp
Severity: wishlist
Owner: Florian Ragwitz [EMAIL PROTECTED]
* Package name: libpoe-component-jabber-perl
Version : 1.1
Upstream Author : Nicholas Perez [EMAIL PROTECTED]
* URL : http://search.cpan.org/~nperez/POE-Component-Jabber/
* License :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Ragwitz [EMAIL PROTECTED] wrote:
Package: wnpp
Severity: wishlist
Owner: Florian Ragwitz [EMAIL PROTECTED]
* Package name: viruskiller
Version : 1.0-1
Upstream Author : Stephen Sweeney [EMAIL PROTECTED]
* URL
Christoph Berg wrote:
I'd like to have a debian-planet list that would receive blog postings
from planet.debian.org
While I agree that an archive of Planet Debian is desirable, I'm not
sure this is the way to go. It seems to me that an archival feature to
PlanetPlanet would be more worthwhile
On Monday 15 August 2005 18:27, Florian Ragwitz wrote:
Package: wnpp
Severity: wishlist
Owner: Florian Ragwitz [EMAIL PROTECTED]
* Package name: libpoe-component-jabber-perl
Version : 1.1
Upstream Author : Nicholas Perez [EMAIL PROTECTED]
* URL :
On Mon, Aug 15, 2005 at 07:08:52PM +0100, David Goodenough wrote:
On Monday 15 August 2005 18:27, Florian Ragwitz wrote:
Package: wnpp
Severity: wishlist
Owner: Florian Ragwitz [EMAIL PROTECTED]
* Package name: libpoe-component-jabber-perl
Version : 1.1
Upstream
ok now how can i get my password from a for callwave, ihave it all install
please as soon as possible.
* Daniel Stone [EMAIL PROTECTED] [2005-08-16 01:09:53]:
On Mon, Aug 15, 2005 at 02:59:17PM +0200, Petter Reinholdtsen wrote:
[Steinar H. Gunderson]
How do you make this work? Last time I tried it, X would only show
the one connected to the ???active??? virtual console, and blanked
the
On Sun, 14 Aug 2005, W. Borgert wrote:
On Sun, Aug 14, 2005 at 12:55:11PM -0400, Benjamin Seidenberg wrote:
whether to compress the README and similar files, I always end up
typing less /usr/share/doc/blah/README.Debian[.gz] using tab
completion and have to go back and correcting my command
On Mon, Aug 15, 2005 at 09:50:41PM +0200, Andreas Schuldei wrote:
wasnt it me who included the interesting patches into the
*debian* kernel a year ago?
Depends if you want multiseat X or multiseat VTs, but hearty
congratulations in any case. Well done.
--
To UNSUBSCRIBE, email to [EMAIL
On Mon, 15 Aug 2005, Jeff Carr wrote:
I hope a developer out there with access to commit packages can take the
initiative to package up agentcell. The authors settled on releasing
this software package under the GPL. It's a great contribution to the
scientific community.
Just thought I'd pass
On Mon, 15 Aug 2005, Henning Makholm wrote:
Idea 1:
lintian: W: /usr/share/doc/README contains installation instructions
I like that one.
Yes - but how should Lintian detect it? Of course one could look for
lines that start with whitespace plus ./configure , but how reliable
is that?
I demand that Henning Makholm may or may not have written...
[snip]
There is a fairly widespread convention of putting compilation instructions
in an INSTALL file, but there is no similarly widespread convention for
putting information about, say, you'll need these libraries,
ISTM that
On Mon, 15 Aug 2005, Paul TBBle Hampson wrote:
On Mon, Aug 15, 2005 at 12:16:24AM -0500, Adam Heath wrote:
When a new source gets uploaded, it replaces the previous. If several NMUs
occur, each one replaces the former. So, when the real maintainer(s) wake
up,
they can only see the
On Sun, Aug 14, 2005 at 02:00:04PM +0200, Mike Hommey wrote:
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson [EMAIL PROTECTED]
wrote:
(...)
The 'reopen' command takes an optional submitter argument, so it was
difficult to get a version in here unambiguously. Instead, we've
Hi,
is it alright to make a file in /usr/share/PKG/examples executable?
I reported my wish #281892 to have a file in examples executable to make
it possible to create a symlink on it that is placed in the PATH. Or that
is to say I would like to have the file bogominitrain.pl in examples
Hi,
pbuilder CVS has a rough support for cdebootstrap;
it seems to be doing well, today it's not working
for me; maybe it could do better sometime.
This morning I've tried again, and apparently it's doing something
good.
I'm planning on getting a cdebootstrap supported version released
On Mon, Aug 15, 2005 at 08:51:31PM +, Joerg Sommer wrote:
I reported my wish #281892 to have a file in examples executable to
make it possible to create a symlink on it that is placed in the
PATH. Or that is to say I would like to have the file
bogominitrain.pl in examples executable
On Tue, Aug 16, 2005 at 08:51:25AM +0900, Junichi Uekawa wrote:
I'm planning on getting a cdebootstrap supported version released somewhat
soonish.
I'd be looking for sponsored upload, since if I'm not mistaken,
and finger [EMAIL PROTECTED] is telling me the correct thing,
my new gpg key is not
On Aug 15, Joerg Sommer [EMAIL PROTECTED] wrote:
is it alright to make a file in /usr/share/PKG/examples executable?
Sure. If it's a script and it's not compressed it should be executable.
--
ciao,
Marco
signature.asc
Description: Digital signature
On Mon, 2005-08-15 at 16:47 +0100, Rob Bradford wrote:
I'd like to have a debian-planet list that would receive blog
postings
from planet.debian.org.
Please don't introduce any more namespace confusion.
I second this proposal too, but I really think, IMHO, it should have a
name like
On Mon, 15 Aug 2005, Andreas Tille wrote:
Providing a link is the minimum you should do. Filing a RFP
... sorry, reading the subject of the mail again clarifies the link issue ...
;-)
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On Mon, Aug 15, 2005 at 06:02:06PM -0700, Debian Qt/KDE Maintainers wrote:
[snip]
libarts1c2 - aRts sound system core components
[snip]
* Use g++-3.4 on arm and m68k since 4.0 ICEs there (#323133):
Won't this create g++ transition chaos on those two platforms?!
Regards: David Weinehall
On Mon, Aug 15, 2005 at 03:41:43PM -0700, Steve Langasek [EMAIL PROTECTED]
wrote:
On Sun, Aug 14, 2005 at 02:00:04PM +0200, Mike Hommey wrote:
On Mon, Jul 18, 2005 at 12:06:29PM +0100, Colin Watson [EMAIL PROTECTED]
wrote:
(...)
The 'reopen' command takes an optional submitter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 14 Aug 2005 22:37:49 -0700
Source: miscfiles
Binary: miscfiles
Architecture: source all
Version: 1.3-7
Distribution: unstable
Urgency: low
Maintainer: Thomas Bushnell, BSG [EMAIL PROTECTED]
Changed-By: Thomas Bushnell, BSG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 13 Aug 2005 11:22:43 +0200
Source: molphy
Binary: molphy
Architecture: source i386
Version: 2.3b3-2
Distribution: unstable
Urgency: low
Maintainer: Andreas Tille [EMAIL PROTECTED]
Changed-By: Andreas Tille [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 07:58:02 +0200
Source: resmed-doc
Binary: resmed-doc
Architecture: source all
Version: 20020327-2
Distribution: unstable
Urgency: low
Maintainer: Andreas Tille [EMAIL PROTECTED]
Changed-By: Andreas Tille [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 02:15:16 -0400
Source: kismet
Binary: kismet
Architecture: source i386
Version: 2005.07.R1a-1
Distribution: unstable
Urgency: low
Maintainer: Francois Gurin [EMAIL PROTECTED]
Changed-By: Francois Gurin [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 13 Aug 2005 21:33:52 +0200
Source: sbcl
Binary: sbcl sbcl-common
Architecture: source i386 all
Version: 1:0.9.3.51-1
Distribution: unstable
Urgency: low
Maintainer: Peter Van Eynde [EMAIL PROTECTED]
Changed-By: Peter Van Eynde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 09:46:01 +0200
Source: cdcat
Binary: cdcat
Architecture: source i386
Version: 1.0-3
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch [EMAIL PROTECTED]
Changed-By: Eduard Bloch [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 08:31:50 +
Source: zope-debhelper
Binary: zope-debhelper
Architecture: source all
Version: 0.3.2.5
Distribution: experimental
Urgency: low
Maintainer: Debian Zope team [EMAIL PROTECTED]
Changed-By: Fabio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 07:35:26 +
Source: zope-cmfquickinstallertool
Binary: zope-cmfquickinstallertool
Architecture: source all
Version: 1.5.5-2
Distribution: experimental
Urgency: low
Maintainer: Fabio Tranchitella [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 14 Aug 2005 21:25:24 +
Source: zope-common
Binary: zope-common
Architecture: source all
Version: 0.5.5
Distribution: experimental
Urgency: low
Maintainer: Debian Zope team [EMAIL PROTECTED]
Changed-By: Fabio Tranchitella
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 11:02:07 +0200
Source: umfpack
Binary: libumfpack4-doc libumfpack4 libumfpack4-dev
Architecture: source all i386
Version: 4.4-3
Distribution: unstable
Urgency: low
Maintainer: Christophe Prud'homme [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 11:25:28 +0200
Source: drdsl
Binary: drdsl
Architecture: source i386
Version: 1.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose [EMAIL PROTECTED]
Changed-By: Matthias Klose [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 27 Jul 2005 23:26:42 +0200
Source: ocamlgraph
Binary: libocamlgraph-ocaml-dev
Architecture: source i386
Version: 0.94a-1
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall [EMAIL PROTECTED]
Changed-By: Sylvain Le
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 4 Aug 2005 15:08:59 +0200
Source: pike7.4
Binary: pike7.4-manual pike7.4-dev pike7.4-perl pike7.4-odbc pike7.4-gdbm
pike7.4-core pike7.4-sane pike7.4-gl pike7.4-sdl pike7.4-pg pike7.4-svg pike7.4
pike7.4-image pike7.4-meta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 27 Jul 2005 23:44:47 +0200
Source: ounit
Binary: libounit-ocaml-dev
Architecture: source i386
Version: 1.0.2-1
Distribution: unstable
Urgency: low
Maintainer: Sylvain Le Gall [EMAIL PROTECTED]
Changed-By: Sylvain Le Gall [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 10:45:58 +0100
Source: loudmouth
Binary: libloudmouth1-0 libloudmouth1-dev
Architecture: source i386
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Ross Burton [EMAIL PROTECTED]
Changed-By: Ross
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 11:25:51 +0200
Source: zope-epoz
Binary: zope-epoz
Architecture: source all
Version: 2.0.1-2
Distribution: experimental
Urgency: low
Maintainer: Andreas Tille [EMAIL PROTECTED]
Changed-By: Andreas Tille [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 12:24:03 +0200
Source: python-numeric
Binary: python-numeric python2.4-numeric-ext python2.3-numeric-ext
python2.3-numeric python-numeric-tutorial python-numeric-ext python2.4-numeric
Architecture: source all i386
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 12:40:38 +0200
Source: sshfs-fuse
Binary: sshfs
Architecture: source i386
Version: 1.2-1
Distribution: unstable
Urgency: low
Maintainer: Bartosz Fenski [EMAIL PROTECTED]
Changed-By: Bartosz Fenski [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 12:19:30 +0200
Source: python-numarray
Binary: python-numarray python-numarray-doc python2.3-numarray-ext
python2.3-numarray python2.4-numarray python2.4-numarray-ext python-numarray-ext
Architecture: source all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 13:20:27 +0200
Source: redet
Binary: redet-doc redet
Architecture: source all
Version: 7.0-1
Distribution: unstable
Urgency: low
Maintainer: Bartosz Fenski [EMAIL PROTECTED]
Changed-By: Bartosz Fenski [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 8 Aug 2005 14:32:22 -0500
Source: destar
Binary: destar
Architecture: source all
Version: 0.0.169-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Ruano Rincon [EMAIL PROTECTED]
Changed-By: Santiago Ruano Rincon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 14:21:36 +0200
Source: ipw2200
Binary: ipw2200-source
Architecture: source all
Version: 1.0.6-2
Distribution: unstable
Urgency: low
Maintainer: Mike Hommey [EMAIL PROTECTED]
Changed-By: Mike Hommey [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 3 Jul 2005 19:23:37 +
Source: kraptor
Binary: kraptor kraptor-data
Architecture: source i386 all
Version: 0.0.20040403-2
Distribution: unstable
Urgency: low
Maintainer: Miriam Ruiz [EMAIL PROTECTED]
Changed-By: Miriam Ruiz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 14:45:37 +0200
Source: ocamlnet
Binary: libocamlnet-ocaml libocamlnet-ocaml-dev
Architecture: source i386
Version: 1.1-4
Distribution: unstable
Urgency: low
Maintainer: Stefano Zacchiroli [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 14:47:55 +0200
Source: speechd-el
Binary: speechd-el-doc-cs speechd-el
Architecture: source all
Version: 1.0-3
Distribution: unstable
Urgency: low
Maintainer: Milan Zamazal [EMAIL PROTECTED]
Changed-By: Milan Zamazal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 11 Aug 2005 01:45:00 +0200
Source: p7zip
Binary: p7zip
Architecture: source i386
Version: 4.20-2
Distribution: unstable
Urgency: low
Maintainer: Mohammed Adnène Trojette [EMAIL PROTECTED]
Changed-By: Mohammed Adnène Trojette
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 15 Aug 2005 15:51:55 +0200
Source: mutt
Binary: mutt
Architecture: source i386
Version: 1.5.10-1
Distribution: unstable
Urgency: low
Maintainer: Adeodato Simó [EMAIL PROTECTED]
Changed-By: Adeodato Simó [EMAIL PROTECTED]
1 - 100 of 186 matches
Mail list logo
