Ciao.
Mancano meno di due mesi: è il caso di iniziare a contarsi e
organizzarsi per la debconf 3 di Oslo?
Io sarei per fare la debconf e almeno parte del debcamp, più contare
tre/quattro giorni di viaggio per l'andata e altrettanti per il ritorno,
magari seguendo due strade diverse.
Il debcamp
On Tue, May 27, 2003 at 10:14:50AM +0200, Enrico Zini wrote:
Ciao.
Mancano meno di due mesi: è il caso di iniziare a contarsi e
organizzarsi per la debconf 3 di Oslo?
Io sarei per fare la debconf e almeno parte del debcamp, più contare
tre/quattro giorni di viaggio per l'andata e
On Tue, 27 May 2003, Enrico Zini wrote:
On Tue, May 27, 2003 at 10:48:51AM +0200, Fabio Massimo Di Nitto wrote:
- Una settimana per trovare il pullmino / i pullmini a minor costo
Sei sicuro che convenga in termini di costi e tempo?
Quando se ne discusse la prima volta, si puntava sul
On Mon, May 26, 2003 at 04:46:56PM +0200, Loïc Le Guyader wrote:
Le 26 mai 2003, Pierre THIERRY, à bout, prit son clavier pour
taper sur son écran:
Essaie debian-mentors...
Déjà essayé.
Peut etre que tu pourrait insister sur debian-mentors, comme tu vient de
le faire ici ?
Amicalement,
Salut à tous,
Ce petit message pour vous avertir que je viens de finir mon processus
new-maintainer. Mon compte a été créé hier soir.
Merci, à tous ceux qui m'ont épaulé pour arriver à faire bouger les
choses.
Pour les personnes qui liraient ce message et qui seraient dans le
processus
Le 26 mai 2003, Christian Perrier, à bout, prit son clavier pour
taper sur son écran:
Quoting Loïc Le Guyader ([EMAIL PROTECTED]):
Le 26 mai 2003, Pierre THIERRY, à bout, prit son clavier pour
taper sur son écran:
Essaie debian-mentors...
Déjà essayé.
Le pb, c'est que le cas est
bonjour,
je viens de mettre à jour mes paquets debian, et il y en a un (fam ) qui
m'affiche directement sur le terminal sans passer par debconf:
Installation de la nouvelle version du fichier de configuration
/etc/fam.conf ...
- IMPORTANT INFORMATION FOR XINETD USERS --
The
Le 27 mai 2003, Loïc Le Guyader, à bout, prit son clavier pour
taper sur son écran:
Mais bon, j'attends un sponsors pour aller plus loin.
Il y en a qui s'impatiente!
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=194656
--
JabberID: [EMAIL PROTECTED]
Toy Story: US$177M domestic box office
On Tue, May 27, 2003 at 10:01:04AM +0200, sferriol wrote:
bonjour,
je viens de mettre à jour mes paquets debian, et il y en a un (fam ) qui
m'affiche directement sur le terminal sans passer par debconf:
Installation de la nouvelle version du fichier de configuration
/etc/fam.conf ...
[...]
Quoting sferriol ([EMAIL PROTECTED]):
bonjour,
je viens de mettre à jour mes paquets debian, et il y en a un (fam ) qui
m'affiche directement sur le terminal sans passer par debconf:
Installation de la nouvelle version du fichier de configuration
/etc/fam.conf ...
- IMPORTANT
* Christian Perrier [EMAIL PROTECTED] [2003-05-27 11:01] :
Quoting sferriol ([EMAIL PROTECTED]):
[...]
= y'a t-il un rapport de bug à faire pour cela???
Rien, dans la Policy, n'oblige à utiliser debconf.
Dans le Developer's Reference, il y a tout de même :
» Direct user interactions must
Quoting Frédéric Bothamy ([EMAIL PROTECTED]):
Dans le Developer's Reference, il y a tout de même :
» Direct user interactions must now be avoided in favor of debconf
» interaction.
(http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-config-mgmt)
* Christian Perrier [EMAIL PROTECTED] [2003-05-27 14:05] :
Quoting Frédéric Bothamy ([EMAIL PROTECTED]):
Dans le Developer's Reference, il y a tout de même :
» Direct user interactions must now be avoided in favor of debconf
» interaction.
Le Tue, May 27, 2003 at 02:05:10PM +0200, Christian Perrier écrivait:
» Direct user interactions must now be avoided in favor of debconf
» interaction.
(http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-config-mgmt)
Grmbl. Je savais que
Quoting Frédéric Bothamy ([EMAIL PROTECTED]):
utiliser debconf pour fournir/demander des informations à l'utilisateur
peut le faire (voir la configuration d'exim 3 par exemple), mais il lui
exim 3 n'utilise pas debconf ?
Il y a un endroit où la raison est donnée ?
* Christian Perrier [EMAIL PROTECTED] [2003-05-27 17:49] :
Quoting Frédéric Bothamy ([EMAIL PROTECTED]):
utiliser debconf pour fournir/demander des informations à l'utilisateur
peut le faire (voir la configuration d'exim 3 par exemple), mais il lui
exim 3 n'utilise pas debconf ?
Non, il
On Mon, May 26, 2003 at 05:15:48PM +0200, Philipp Matthias Hahn wrote:
On Mon, May 26, 2003 at 08:12:51AM -0500, Luca - De Whiskey's - De Vitis
wrote:
On Mon, May 26, 2003 at 02:45:16PM +0200, Josip Rodin wrote:
Yes, but there's still no bloody point in making the submitter hunt around
On Mon, May 26, 2003 at 09:58:25PM +0200, Bernhard R. Link wrote:
* Matt Zimmerman [EMAIL PROTECTED] [030526 21:41]:
It is _not_ obvious, and closes: #... gives no clue to someone reading
the changelog what might have been changed. Internet access, knowledge
of debbugs, etc. are not
On Mon, May 26, 2003 at 05:21:05PM +0200, Gerfried Fuchs wrote:
Not only does the mail from bts _not_ include the message (like you
were told by others already), also other people reading the changelog
might be interested in it. I for my part am. Is it really asked for too
much to write
* Joachim Breitner [EMAIL PROTECTED] [2003-05-26 18:05:11 +0200]:
Am Mon, 2003-05-26 um 17.15 schrieb Philipp Matthias Hahn:
Or do you expect everbody to file duplicate bugs or subscribe to
existing bugs ?
AFAIK you can't subscribe to single bugs (at least I was told that a few
month
On Tue, May 27, 2003 at 07:23:27AM +1000, Herbert Xu wrote:
On Mon, May 26, 2003 at 10:00:06PM +0200, Yann Dirson wrote:
We could get around Guido's point mentionned above by having a list of
default patches to apply, which would by default contain the debian
patch.
Yes, but then the
On Monday 26 May 2003 22:30, Kai Henningsen wrote:
[EMAIL PROTECTED] (Gerfried Fuchs) wrote on 26.05.03 in
[EMAIL PROTECTED]:
As for the long descriptions, I really don't see what the use is in an
ITP. The packages will of course have them.
A proper long description will help avoid question
reopen 159971
reopen 124472
reopen 147059
reopen 70184
thanks
Anselm Lingnau [EMAIL PROTECTED] writes:
Format: 1.7
Date: Tue, 27 May 2003 01:15:33 +0200
Source: bwidget
Binary: bwidget
Architecture: source all
Version: 1.6.0-1
Distribution: unstable
Urgency: low
Maintainer: Anselm
Arnd wrote:
Actually, I was thinking of a different concept with a 'Replaces: tag,
Hm. As I understand it, it would be more something like a Provides:
declaration, it seems. Such a feature does not seem useless to me at
first glance (we already see aglomerations of patches, like FOLK,
which
On Tue, May 27, 2003 at 07:37:42AM +0200, Sven Luther wrote:
On Tue, May 27, 2003 at 07:23:27AM +1000, Herbert Xu wrote:
On Mon, May 26, 2003 at 10:00:06PM +0200, Yann Dirson wrote:
We could get around Guido's point mentionned above by having a list of
default patches to apply, which
Matt Zimmerman [EMAIL PROTECTED] wrote:
All definite benefits. The one thing which seems to be missing is to ensure
that the arch-specific kernels do not miss out on important fixes (such as
security) to the main kernel source tree.
Yes that isn't easy to check apart from the fact that if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 27 May 2003 10:27, Yann Dirson wrote:
Let's look at your example:
| Patch-name: Debian base patch
| Patch-id: debian
| Architecture: all
| Kernel-version: 2.4.20
| Depends: ptrace, isdnbonding, binfmtmisc, ethernetpadding, ...
|
|
On Tue, May 27, 2003 at 12:42:29AM -0400, Matt Zimmerman wrote:
Or better:
1. discover security vulnerability
2. was it fixed in the Debian package?
3. read changelog
4. see a bunch of completely worthless Closes: messages
5. throttle maintainer
1. defenestrate loser maintainers
2. ???
3.
RTC does not work either compiled as a module or into the kernel. A patch for
this is needed or a new kernel-source-2.5.69 package is needed.
Cheers,
Victor
On Tue, May 27, 2003 at 12:47:10AM -0400, Matt Zimmerman wrote:
It is. Unfortunately, common sense is not always as common as we would
like.
Are you trying to say that i've no common sense?
ciao,
--
Luca - De Whiskey's - De Vitis | Elegant or ugly code as well
aliases: Luca ^De
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 27 May 2003 17:45, Victor Torrico wrote:
RTC does not work either compiled as a module or into the kernel. A
patch for this is needed or a new kernel-source-2.5.69 package is needed.
In 2.5.69 many things are not working... there are
On Tue, 27 May 2003 19:04, Arnd Bergmann wrote:
Here I suppose the pre-patch is supposed to be applied first, and then
the application of the debian patch would only trigger application of
those dependant patches not provided by the pre-patch.
The order in which the patches are applied
On Tue, May 27, 2003 at 12:46:02AM -0400, Matt Zimmerman wrote:
* Matt Zimmerman [EMAIL PROTECTED] [030526 21:41]:
It is _not_ obvious, and closes: #... gives no clue to someone reading
the changelog what might have been changed. Internet access, knowledge
of debbugs, etc. are not
On Tue, May 27, 2003 at 08:16:59PM +1000, Russell Coker wrote:
On Tue, 27 May 2003 19:04, Arnd Bergmann wrote:
Here I suppose the pre-patch is supposed to be applied first, and then
the application of the debian patch would only trigger application of
those dependant patches not provided
On Mon 26 May 2003, Brian Nelson wrote:
Umm, no, the changelog is for listing changes (*change* log, get it?),
not for just closing bugs without any reason given whatsoever.
Why do so many seem to have difficulty with this concept? Is it
worthwhile to Cc this stuff to -devel, or should I
debian-devel:!
,
www.spwe.com
CCTV200
CCTV
http://www.spwe.com
010-66027364010-66026820
010-66025560
010-66027364
QQ94631723
!
[EMAIL PROTECTED]
2003-05-27
On Tue, May 27, 2003 at 10:47:15PM +1200, Nick Phillips wrote:
If your changelog merely says New upstream version, closes: #123 #456,
it's no help whatsoever, and I will (rightly) think that you suck.
This is debian-devel: as soon as one declares he stops reading a thread,
beasts came out and
dear sirs,
does VMware also support 64-bit x86 systems HP i2000 itanium
... what do we need?
paul!
_
NOTE: This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged
On Tue, May 27, 2003 at 07:14:28AM -0500, Luca - De Whiskey's - De Vitis wrote:
To demostrate how much this issue is stupid, i'll make any one here
happy by including the entire upstream changelog in
changelog.Debian.gz, next time i'll build a new upstream.
Didn't you just complain that people
Luca - De Whiskey's - De Vitis [EMAIL PROTECTED] a tapoté :
You discriminate and offend people only by reading a list of
changes, and i should be the one who suks (supposing i'm not right)?
He has the right to think that you sucks at filling changelogs,
regarding how you fill changelogs.
Thus spake PPMW:
dear sirs,
does VMware also support 64-bit x86 systems HP i2000 itanium
... what do we need?
http://www.debian.org/ports/ia64/
The HP i2000 is mentioned as working well with Debian ia64.
--
Nathan Poznick [EMAIL PROTECTED]
Not that I'm against
On Tue, May 27, 2003 at 03:10:36PM +0200, Mathieu Roy wrote:
Anybody has the right to express a point of view on anybody else work,
right?
I'll try to keep in mind this gentlemen example of expressing a point of view
on
anybody else work next time, so i'll not misunderstend it with an offense.
On Tue, May 27, 2003 at 03:11:11PM +0200, Michael Banck wrote:
Didn't you just complain that people said you wouldn't have common
sense?
How odd.
Not that odd: if someone feels to be in the position of telling me that i've no
common sense or express any other kind of colorful expression
On Tue, May 27, 2003 at 07:14:28AM -0500, Luca - De Whiskey's - De Vitis wrote:
The contraddiction of all this tread, is that: if i make a change to a package
i've to list my change in the package changelog (Matt Zimmerman, no one ever
objected this). If i build a new upstream, i've to list
Package: wnpp
Version: unavailable; reported 2003-05-27
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: libfilesys-statvfs-perl
Version : 0.68
Upstream Author : Ian Guthrie [EMAIL PROTECTED]
* URL :
*
Luca - De Whiskey's - De Vitis [EMAIL PROTECTED] a tapoté :
You said you have to list each change in the upstream changelog to
know which bug can be declared as closed. And that's, as maintainer,
your job, isn't it? But is it users job to do it too?
I do not understand that: could you
Luca - De Whiskey's - De Vitis [EMAIL PROTECTED] writes:
On Tue, May 27, 2003 at 10:47:15PM +1200, Nick Phillips wrote:
If your changelog merely says New upstream version, closes: #123 #456,
it's no help whatsoever, and I will (rightly) think that you suck.
This is debian-devel: as soon as
Paul Slootman [EMAIL PROTECTED] writes:
On Mon 26 May 2003, Brian Nelson wrote:
Umm, no, the changelog is for listing changes (*change* log, get it?),
not for just closing bugs without any reason given whatsoever.
Why do so many seem to have difficulty with this concept? Is it
worthwhile
David Nusinow [EMAIL PROTECTED] writes:
Another point of note is that nascent packagers are encouraged to adopt
other software that's already in the archive before packaging new
items. In this case, he is merely following that advice.
Granted. OTOH, applications may be a better place to
On Tue, May 27, 2003 at 05:12:22PM +0200, Mathieu Roy wrote:
I can.
You wrote that you have to list each change in the upstream
changelog to know which bug can be declared as closed. Right?
That is what i wrote, but is not what i meant: it have a difference meaning if
you take it out of the
On Tue, May 27, 2003 at 08:31:39AM -0700, Brian Nelson wrote:
Uhh, your packages include the upstream source, and therefore the
upstream source is part of your package working.
So it is part of my work, and changes to my work should be included in
changelog.Debian...
To demostrate how much
Brian Nelson writes:
If you're not going to describe upstream fixes in the changelog, then
don't close the bug in the changelog. The changelog is for describing
changes, not listing meaningless numbers.
If you want to have rigid, detailed rules for the content and structure of
changelog
On Tue, May 27, 2003 at 08:39:50AM -0700, Brian Nelson wrote:
Perhaps a separate, concise message to debian-devel-announce?
I doubt it would help. I see changelog abuse as an act of laziness, not
ignorance. Common sense says that you should be listing changes in the
changelog. It's not
On Tue, May 27, 2003 at 11:43:22AM -0500, John Hasler wrote:
Brian Nelson writes:
If you're not going to describe upstream fixes in the changelog, then
don't close the bug in the changelog. The changelog is for describing
changes, not listing meaningless numbers.
If you want to have
Package: wnpp
Version: unavailable; reported 2003-05-27
Severity: wishlist
* Package name: drivel
Version : 0.9.1
Upstream Author : Todd Kulesza [EMAIL PROTECTED]
* URL : http://sourceforge.net/projects/drivel/
* License : GPL
Description : A LiveJournal
Luca - De Whiskey's - De Vitis [EMAIL PROTECTED] wrote:
You people told me that:
- If i make a change to a package i've to list my changes in the package
changelog (Matt Zimmerman, no one ever objected this).
- If i build a new upstream, i've to list each change in the upstream
changelog
Sven wrote:
Why don't we use a scheme similar to what xfree86 use for its patches.
Sure we would need to adapt it as the patches are distributed, but we
could well do it.
As I understand it, the xfree86 package uses (some derivative of) dbs,
in which the package maintainer has to order the
Josip Rodin [EMAIL PROTECTED] writes:
On Tue, May 27, 2003 at 08:39:50AM -0700, Brian Nelson wrote:
Perhaps a separate, concise message to debian-devel-announce?
I doubt it would help. I see changelog abuse as an act of laziness, not
ignorance. Common sense says that you should be
Hi there,
Since I'm overloaded with work (in and out of Debian) I'm considering
orphaning a number of packages related to astronomy, they are:
- openuniverse
- starplot
- spacechart
- yale
and
- gliese
The first three are GUIs to view astronomical date whileas the last
two include astronomic
Andreas Metzler wrote:
It would be nice if there were documented mechanisms to move a list
/painlessly/ from alioth to lists and vice versa, i.e. keeping the
subscriber list and redirections for the old list addresses.
Please send me a patch to the List HOWTO I once wrote. You'll need
monthly
Arnd wrote:
Let's look at your example:
| Patch-name: Debian base patch
| Patch-id: debian
| Architecture: all
| Kernel-version: 2.4.20
| Depends: ptrace, isdnbonding, binfmtmisc, ethernetpadding, ...
|
| Patch-name: Pre-patch 2.4.21-pre7
| Patch-id: patch-2.4.21-pre7
|
Herbert wrote:
Yes that isn't easy to check apart from the fact that if there isn't
an arch update after a security update to kernel-source, then that arch
is probably vulnerable. If you've got an idea on how this can improved,
please let us know.
A possibility would be to define a
Christian Kurz [EMAIL PROTECTED] writes:
Hi Brian
On [26/05/03 23:13], Brian Nelson wrote:
Anselm Lingnau [EMAIL PROTECTED] writes:
[...]
* Closes: #159971, #124472, #147059, #70184.
Umm, no, the changelog is for listing changes (*change* log, get it?),
not for just closing bugs
Adam wrote:
So doing bts work is worthless? :)
Hey, someone once wrote similar scripts to count how many bugreports
were reported by anyone !
/me rejoices recalling he was ranked 3rd by the number of open bugs :)
Well, never mind :)
--
Yann Dirson[EMAIL PROTECTED] |Why make M$-Bill
Yann Dirson dijo [Tue, May 27, 2003 at 10:38:54AM +0200]:
That's more or less what I'd think of as well. We can start with an
empty security patch, and have this one grow as needed. This way, apt
will show people they have an outdated security patch - which, BTW,
may be more of an incentive
On Sun, May 18, 2003 at 11:39:09PM +0200, Denis Barbier wrote:
Hi,
below is a list of source packages containing gettext .po files,
for which binary packages do not ship any file under a LC_MESSAGES
directory.
There might be several reasons:
a. Programs use gettext PO files to store
Package: wnpp
Version: unavailable; reported 2003-05-27
Severity: wishlist
* Package name: yaz
Version : 2.0.2
Upstream Author : IndexData
* URL : http://www.indexdata.dk/yaz/
* License : BSD-ish: http://www.indexdata.dk/yaz/doc/license.php
Description :
Hi!
Habe gerade die Bestätigung erhalten, das mein Kontakt-Video bei
Echter-Sex.com veröffentlicht wurde.
Jetzt kannst Du Dir mein Video ansehen. Am Ende des Videos wird meine
Kontaktadresse veröffentlicht.
Schau Dir mein privates Kontaktvideo an unter:
http://www.echter-sex.com/?ref=276505
Ç×°®µÄÍø³æ£ºÈç¹ûÕâ·âÓʼþ´òÈÅÁËÄ㣬ÎÒÉî¸Ð²»°²²¢ÖÂǸ£¡
ÓÐÓÃÊÇÐÅÏ¢£¬ÎÞÓÃÊÇÀ¬»ø¡£ÇëÄã¿´ÍêÔÙɾ£¡ ^0^
ÍøÂçʱ´ú£¬¿ÉÄÜÄãʲô¶¼ÍæÁË£¬¾ÍÊÇûÓÐÍæÍøÂç׬Ǯ¡£Ôõô˵ÄØ£¬ÓÐÇ®µÄ²»Ð¼ÓÚÍæÕâÑùµÄ¶«Î÷£¬Ã»Ç®µÄÓÖÅÂÉϵ±¡£ÒÔÎÒÀ´Ëµ£¬²»Íæ
On Tue, May 27, 2003 at 10:40:06PM +0200, Yann Dirson wrote:
Adam wrote:
So doing bts work is worthless? :)
Hey, someone once wrote similar scripts to count how many bugreports
were reported by anyone !
Try:
http://bugs.debian.org/cgi-bin/pkgindex.cgi?indexon=submittersortby=count
On Tue, 27 May 2003, Zed Pobre wrote:
Could you elaborate on what ways yours works better than the original
adduser? I'm sure Roland would love to hear about functionality
improvements, and I'd certainly be keen for any improvements to the
LDAP-specific code...
My version will
On Tue, May 27, 2003 at 12:15:37PM -0700, Brian Nelson wrote:
1. To show others, especially NM's, what not to do. NM's mostly learn
by example, and I think it helps to ensure they don't follow bad
examples.
2. It's something that should be obvious. Producing poor quality
Steve Langasek [EMAIL PROTECTED] writes:
On Tue, May 27, 2003 at 12:15:37PM -0700, Brian Nelson wrote:
1. To show others, especially NM's, what not to do. NM's mostly learn
by example, and I think it helps to ensure they don't follow bad
examples.
2. It's something that should be
On Tue, May 27, 2003 at 07:41:34PM -0700, Brian Nelson wrote:
Obvious is a key word indicating that you need to check your
assumptions at the door. While I will certainly concede that changelogs
that spell out the nature of relevant upstream changes are more useful
than those which do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 26 May 2003 15:48:37 -0400
Source: liblingua-en-words2nums-perl
Binary: liblingua-en-words2nums-perl
Architecture: source all
Version: 0.11
Distribution: unstable
Urgency: low
Maintainer: Joey Hess [EMAIL PROTECTED]
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 26 May 2003 20:59:54 +0200
Source: urlview
Binary: urlview
Architecture: source i386
Version: 0.9-4
Distribution: unstable
Urgency: low
Maintainer: Emanuele Rocca [EMAIL PROTECTED]
Changed-By: Emanuele Rocca [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 17:19:33 +0200
Source: dhis-mx-sendmail-engine
Binary: dhis-mx-sendmail-engine
Architecture: source i386
Version: 5.0-2
Distribution: unstable
Urgency: low
Maintainer: Guus Sliepen [EMAIL PROTECTED]
Changed-By: Guus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 11:35:27 -0400
Source: base-config
Binary: base-config
Architecture: source all
Version: 1.62
Distribution: unstable
Urgency: low
Maintainer: Joey Hess [EMAIL PROTECTED]
Changed-By: Joey Hess [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 11:19:25 -0500
Source: ddrmat
Binary: ddrmat-source
Architecture: source all
Version: 0.9-2
Distribution: unstable
Urgency: low
Maintainer: Joe Wreschnig [EMAIL PROTECTED]
Changed-By: Joe Wreschnig [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 09:23:37 -0700
Source: nmh
Binary: nmh
Architecture: source i386
Version: 1.1-RC1-2
Distribution: unstable
Urgency: low
Maintainer: Nick Rusnov [EMAIL PROTECTED]
Changed-By: Nick Rusnov [EMAIL PROTECTED]
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 10:39:16 -0600
Source: docbookide
Binary: docbookide
Architecture: source all
Version: 0.1-5
Distribution: unstable
Urgency: low
Maintainer: Kevin M. Rosenberg [EMAIL PROTECTED]
Changed-By: Kevin M. Rosenberg [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 10 May 2003 17:11:11 +0200
Source: docbook-utils
Binary: docbook-utils
Architecture: source all
Version: 0.6.13-1
Distribution: unstable
Urgency: low
Maintainer: Christian Marillat [EMAIL PROTECTED]
Changed-By: Christian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 10:35:55 -0600
Source: common-lisp-controller
Binary: common-lisp-controller
Architecture: source i386
Version: 3.63
Distribution: unstable
Urgency: low
Maintainer: Kevin M. Rosenberg [EMAIL PROTECTED]
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 26 May 2003 19:00:00 +0200
Source: xmorph
Binary: libmorph xmorph gtkmorph libmorph-dev gtkmorph-example
Architecture: source
Version: 1:20030527
Distribution: unstable
Urgency: low
Maintainer: A Mennucc1 [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 12:26:50 -0500
Source: vm
Binary: mime-codecs vm
Architecture: source all i386
Version: 7.16-1
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava [EMAIL PROTECTED]
Changed-By: Manoj Srivastava [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 11:42:13 -0600
Source: ilisp
Binary: ilisp-doc ilisp
Architecture: source all
Version: 5.12.0+cvs.2003.05.27
Distribution: unstable
Urgency: low
Maintainer: Kevin M. Rosenberg [EMAIL PROTECTED]
Changed-By: Kevin M.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 11:58:46 -0600
Source: ilisp
Binary: ilisp-doc ilisp
Architecture: source all
Version: 5.12.0+cvs.2003.05.27.1
Distribution: unstable
Urgency: low
Maintainer: Kevin M. Rosenberg [EMAIL PROTECTED]
Changed-By: Kevin M.
-BEGIN PGP SIGNED MESSAGE-
Format: 1.7
Date: Fri, 16 May 2003 21:49:21 +0200
Source: ethstatus
Binary: ethstatus
Architecture: source i386
Version: 0.4-1
Distribution: unstable
Urgency: low
Maintainer: Christoph Haas [EMAIL PROTECTED]
Changed-By: Christoph Haas [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 16:37:06 +0200
Source: libpam-mount
Binary: libpam-mount
Architecture: source i386
Version: 0.5.16-2
Distribution: unstable
Urgency: low
Maintainer: Bastian Kleineidam [EMAIL PROTECTED]
Changed-By: Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 12:29:51 +0200
Source: roundup
Binary: roundup
Architecture: source all
Version: 0.5.7debian-2
Distribution: unstable
Urgency: low
Maintainer: Bastian Kleineidam [EMAIL PROTECTED]
Changed-By: Bastian Kleineidam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 20:14:38 +0200
Source: bison++
Binary: bison++
Architecture: source i386
Version: 1.21.10-1
Distribution: unstable
Urgency: low
Maintainer: Magnus Ekdahl [EMAIL PROTECTED]
Changed-By: Magnus Ekdahl [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 18 May 2003 09:05:59 -0500
Source: kwiki
Binary: kwiki
Architecture: source all
Version: 0.13-1
Distribution: unstable
Urgency: low
Maintainer: Michael D. Ivey [EMAIL PROTECTED]
Changed-By: Michael D. Ivey [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Fri, 23 May 2003 15:27:04 +
Source: kwiki
Binary: kwiki
Architecture: source all
Version: 0.14-1
Distribution: unstable
Urgency: low
Maintainer: Michael D. Ivey [EMAIL PROTECTED]
Changed-By: Michael D. Ivey [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 20 May 2003 01:22:22 -0400
Source: libwww-curl-perl
Binary: libwww-curl-perl
Architecture: source i386
Version: 2.0-2
Distribution: unstable
Urgency: low
Maintainer: Deedra Waters [EMAIL PROTECTED]
Changed-By: Deedra Waters
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 10:16:09 +0200
Source: cln
Binary: libcln2 pi libcln-dev
Architecture: source i386
Version: 1.1.5-2
Distribution: unstable
Urgency: low
Maintainer: Richard Kreckel [EMAIL PROTECTED]
Changed-By: Richard Kreckel [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 21 May 2003 00:12:08 +0900
Source: jack-audio-connection-kit
Binary: jackd libjack0.71.2-dev libjack0.71.2-0
Architecture: source i386
Version: 0.71.2-1
Distribution: unstable
Urgency: low
Maintainer: Junichi Uekawa [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sat, 24 May 2003 04:02:38 -0700
Source: gnome-pilot
Binary: libgnome-pilot2-dev libgnome-pilot2 gnome-pilot
Architecture: source i386
Version: 2.0.9-1
Distribution: unstable
Urgency: low
Maintainer: Mike Markley [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 25 May 2003 02:15:54 -0700
Source: synaesthesia
Binary: synaesthesia
Architecture: source i386
Version: 2.1-5
Distribution: unstable
Urgency: low
Maintainer: Devin Carraway [EMAIL PROTECTED]
Changed-By: Devin Carraway [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 19:29:25 +0100
Source: popt
Binary: libpopt-dev libpopt0
Architecture: source i386
Version: 1.7-1
Distribution: unstable
Urgency: low
Maintainer: Paul Martin [EMAIL PROTECTED]
Changed-By: Paul Martin [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 27 May 2003 18:52:24 +
Source: dancer-bot
Binary: dancer-bot
Architecture: source i386
Version: 4.16p1-8
Distribution: unstable
Urgency: low
Maintainer: Søren Boll Overgaard [EMAIL PROTECTED]
Changed-By: Søren Boll Overgaard
1 - 100 of 155 matches
Mail list logo
