On Wed, 26 Aug 2009, Manoj Srivastava sriva...@debian.org wrote:
if [ -e /etc/pam.d/login ]; then
perl -pli~ -e 'm/session.*pam_selinux.so/ s/^\#\s*//o'
/etc/pam.d/login rm /etc/pam.d/login~
fi
if [ -e /etc/pam.d/ssh ]; then
perl -pli~ -e 'm/session.*pam_selinux.so/ do { s/^\#\s*//o;
On Thu, 10 Sep 2009, Rogério Brito wrote:
I am really annoyed with the current trend of packages dragging in a
lot of dependencies on which the packages don't really depend. The
word dependency seems to has lost its meaning.
Please file bugs against these packages as appropriate, with
On Wed, 2009-09-09 at 19:02 -0400, James Vega wrote:
tag 528494 help
thanks
#528494 raised the idea of having vim-tiny (the default vi-like editor
on a base install) provide /bin/vi so that it would be accessible in
situations where /usr isn't available. At first glance, I naïvely
figured
package: sysv-rc
severity: important
x-debbugs-cc: debian-devel@lists.debian.org
User: debian...@lists.debian.org
Usertags: piuparts piuparts.d.o
Hi Petter,
On Mittwoch, 9. September 2009, Petter Reinholdtsen wrote:
today I noticed that quite many packages fail the piuparts test,
because of
Hi Luke,
On Wed, Sep 09, 2009 at 09:58:34PM -0400, Luke Faraone wrote:
I'm currently working on packaging
Rainbowhttp://wiki.laptop.org/go/Rainbow, an implementation of the
Bitfrost http://wiki.laptop.org/go/OLPC_Bitfrost security
spesification. Rainbow runs user-level desktop applications
One hidden feature of the current Debian boot sustem, is the ability
to run the init.d scripts in parallel. This require dependency based
boot sequencing to be enabled, and the init.d script dependencies to
be complete and correct to work reliably. The feature is hidden and
undocumented, because
Hello,
I'd like to remind maintainers that in order to reach bug reporters to
ask for tests etc. you _need_ to explicitely Cc the bug reporter, else
he won't receive the mail and of course not do the tests etc. It's now
quite a few times that I have received a you didn't answer mail...
Samuel
On Thu, Sep 10, 2009 at 15:45, Samuel Thibault sthiba...@debian.org wrote:
Hello,
I'd like to remind maintainers that in order to reach bug reporters to
ask for tests etc. you _need_ to explicitely Cc the bug reporter, else
he won't receive the mail and of course not do the tests etc. It's
Le jeudi 10 septembre 2009 à 16:09 +0200, Sandro Tosi a écrit :
I was thinking about this a couple of hours ago, but in the different
direction: why not mailing the submitter by default?
Because the debbugs maintainer doesn’t want it.
--
.''`. Josselin Mouette
: :' :
`. `' “I
* Sandro Tosi mo...@debian.org [090910 16:09]:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
But reporters are sacrifing some of their time to help us make our
distribution better. Do you really think we should scare them away
by rewarding bug
2009/9/10 Josselin Mouette j...@debian.org:
Le jeudi 10 septembre 2009 à 16:09 +0200, Sandro Tosi a écrit :
I was thinking about this a couple of hours ago, but in the different
direction: why not mailing the submitter by default?
Because the debbugs maintainer doesn’t want it.
Yes, I seemed
On Thu, Sep 10, 2009 at 04:21:50PM +0200, Bernhard R. Link wrote:
* Sandro Tosi mo...@debian.org [090910 16:09]:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
But reporters are sacrifing some of their time to help us make our
On Sep 04 2009, Boyd Stephen Smith Jr. wrote:
On Friday 04 September 2009 13:14:43 Alessandro Dentella wrote:
So I'd really prefer to leave those 2 drivers as dependencies.
Recommends, right? As a user it annoys me to no end when the packager
Depends
on something the system will work
On Thu, Sep 10, 2009 at 16:21, Bernhard R. Link brl...@debian.org wrote:
* Sandro Tosi mo...@debian.org [090910 16:09]:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
But reporters are sacrifing some of their time to help us make our
Am Donnerstag, den 10.09.2009, 16:09 +0200 schrieb Sandro Tosi:
Ideally, I'd imaging nnn...@b.d.o to reach
- submitter
- maintainers
- subscribers
We already have -quite if we want to not mail people.
Do others feel we should enable emailing the submitter by default?
Yes, please email
Sandro Tosi wrote:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
As raised by Berhard[0], this could bother some reporters, OTOH - as
Kumar said[1] - other posters would actually like being more closely
involved with their bugs.
Why not
* Sandro Tosi mo...@debian.org [090910 16:35]:
Yes, I do believe that submitters should be informed of any activity
on their bugs (to know they're not ignored, to contribute to the tech
discussion (not every reported is a non-tech guy), etc).
Not everyone is a non-tech guy, but even most
On Thu, Sep 10, 2009 at 09:32:55AM -0500, Kumar Appaiah wrote:
On Thu, Sep 10, 2009 at 04:21:50PM +0200, Bernhard R. Link wrote:
But reporters are sacrifing some of their time to help us make our
distribution better. Do you really think we should scare them away
by rewarding bug reports by
On Thu, Sep 10, 2009 at 03:43:16PM +0100, Mark Brown wrote:
This is subjective. I know of several bug reporters who would either
be happy to see that their bug is being dicussed/attended to, or even
be able to pariticipate in the fixing efforts if their technical
knowledge falls in the
On Thu, Sep 10, 2009 at 04:21:50PM +0200, Bernhard R. Link wrote:
* Sandro Tosi mo...@debian.org [090910 16:09]:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
But reporters are sacrifing some of their time to help us make our
Quoting Mark Brown broo...@sirena.org.uk:
What would be really useful here is the ability to set up the BTS to
subscribe you to bugs you've filed by default. That avoids the issue
with confusing less technical users.
That is exactly what I was going to suggest - with the addition that
the
Leo costela Antunes, le Thu 10 Sep 2009 16:52:43 +0200, a écrit :
Why not include a pseudo-header to subscribe to bugreports on submit?
I thought about that too, but that doesn't solve the original problem:
clueless reporters won't enable it and absent-minded maintainers will
forget to Cc them.
Le jeudi 10 septembre 2009 à 15:43 +0100, Mark Brown a écrit :
What would be really useful here is the ability to set up the BTS to
subscribe you to bugs you've filed by default. That avoids the issue
with confusing less technical users.
No, it wouldn’t be useful.
Not all reports are
Le jeudi 10 septembre 2009 à 16:58 +0200, Bernhard R. Link a écrit :
So we should punish users for incompotent developers?
Whoa? Informing users is punishing them?
This whole thread is a complete WTF, as were previous discussions on the
topic.
--
.''`. Josselin Mouette
: :' :
`. `'
* Pierre Habouzit madco...@madism.org [090910 17:08]:
On Thu, Sep 10, 2009 at 04:21:50PM +0200, Bernhard R. Link wrote:
* Sandro Tosi mo...@debian.org [090910 16:09]:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
But reporters are
Hi,
* Kumar Appaiah a.ku...@alumni.iitm.ac.in [2009-09-10 17:03]:
On Thu, Sep 10, 2009 at 04:21:50PM +0200, Bernhard R. Link wrote:
* Sandro Tosi mo...@debian.org [090910 16:09]:
Do others feel we should enable emailing the submitter by default?
there are some reasons not to?
But
Le jeudi 10 septembre 2009 à 15:45 +0200, Samuel Thibault a écrit :
I'd like to remind maintainers that in order to reach bug reporters to
ask for tests etc. you _need_ to explicitely Cc the bug reporter, else
he won't receive the mail and of course not do the tests etc. It's now
quite a few
On Thu, Sep 10, 2009 at 05:08:00PM +0200, Pierre Habouzit wrote:
When the maintainer think the bug reporter is not to be annoyed, then he
should mail nnn-silent or whatever, because that is the exception.
Full ACK.
Not the reverse. This is a major (if not _THE_ major) annoyance with the
BTS.
On Thu, 10 Sep 2009 11:01:45 -0400
Andres Salomon dilin...@collabora.co.uk wrote:
On Mon, 17 Aug 2009 18:57:38 -0400
Andres Salomon dilin...@collabora.co.uk wrote:
Hi,
Is trac being actively maintained? I no longer use it, so I'd like
to be removed from the uploaders list when
On Thu, Sep 10, 2009 at 10:04:19AM -0500, Kumar Appaiah wrote:
On Thu, Sep 10, 2009 at 03:43:16PM +0100, Mark Brown wrote:
What would be really useful here is the ability to set up the BTS to
subscribe you to bugs you've filed by default. That avoids the issue
with confusing less
Le jeudi 10 septembre 2009 à 17:19 +0200, Bernhard R. Link a écrit :
When the maintainer think the bug reporter is not to be annoyed, then he
should mail nnn-silent or whatever,
That is only true for very small packages where only the maintainer is
intrested in.
Since apparently you
On Mon, 17 Aug 2009 18:57:38 -0400
Andres Salomon dilin...@collabora.co.uk wrote:
Hi,
Is trac being actively maintained? I no longer use it, so I'd like to
be removed from the uploaders list when someone does the next upload.
If no one is maintaining it, it should really be orphaned..
On Thu, Sep 10, 2009 at 05:08:00PM +0200, Pierre Habouzit wrote:
Not the reverse. This is a major (if not _THE_ major) annoyance with the
BTS. FWIW this is a long discussed issue, and the BTS maintainers do not
share this opinion (that mailing @ should also mail the submitter)
so we're
* Josselin Mouette j...@debian.org [090910 17:26]:
Le jeudi 10 septembre 2009 à 17:19 +0200, Bernhard R. Link a écrit :
When the maintainer think the bug reporter is not to be annoyed, then he
should mail nnn-silent or whatever,
That is only true for very small packages where only the
Le jeudi 10 septembre 2009 à 17:55 +0200, Bernhard R. Link a écrit :
If all one does with the bugs is collecting them, hoping upstream will fix
them (for which one does not even have the manpower to check oneself)
or the submitters lose interest, then the current system is of course
not
* Josselin Mouette j...@debian.org [090910 18:11]:
Otherwise most packages have some crowd of people following the package
or even only specific bugs. Then additional user input not reaching them
is losing valuate chances for additional information.
We???re not talking about preventing
Le jeudi 10 septembre 2009 à 18:25 +0200, Bernhard R. Link a écrit :
That is the thread at large. Currently it was about why nnn-quiet is no
suitable workaround if the followup address for users (nnn@) would suddenly
also mail users.
Then use nnn-maintonly@, which will reach the PTS and
On Thu, Sep 10, 2009 at 05:23:32PM +0200, Stefano Zacchiroli wrote:
On Thu, Sep 10, 2009 at 05:08:00PM +0200, Pierre Habouzit wrote:
When the maintainer think the bug reporter is not to be annoyed, then he
should mail nnn-silent or whatever, because that is the exception.
Full ACK.
Not
On Thu, Sep 10, 2009 at 04:58:30PM +0200, Samuel Thibault wrote:
Leo costela Antunes, le Thu 10 Sep 2009 16:52:43 +0200, a écrit :
Why not include a pseudo-header to subscribe to bugreports on submit?
I thought about that too, but that doesn't solve the original problem:
clueless reporters
On Thu, 10 Sep 2009, Sandro Tosi wrote:
I was thinking about this a couple of hours ago, but in the
different direction: why not mailing the submitter by default?
Ideally, I'd imaging nnn...@b.d.o to reach
- submitter
n...@bdo should reach submitters who are interested in being reached by
also sprach Samuel Thibault sthiba...@debian.org [2009.09.10.1545 +0200]:
I'd like to remind maintainers that in order to reach bug reporters to
ask for tests etc. you _need_ to explicitely Cc the bug reporter, else
he won't receive the mail and of course not do the tests etc. It's now
quite
package: bugs.debian.org
severity: wishlist
x-debbugs-cc: debian-devel@lists.debian.org
Hi,
On Donnerstag, 10. September 2009, Bernhard R. Link wrote:
But reporters are sacrifing some of their time to help us make our
distribution better. Do you really think we should scare them away
by
Pierre Habouzit madco...@madism.org writes:
On Thu, Sep 10, 2009 at 05:23:32PM +0200, Stefano Zacchiroli wrote:
Conceptually, what we want is trivial: we want submitter to be
subscribed (in the sense of bts subscribe) by default. If they want,
they are free to opt unsubscribing.
That should
On Thu, 10 Sep 2009, Holger Levsen wrote:
Also it would be nice if #351856 would be implemented, so people who want
this, will be automatically subscribed to their bugs.
That actually is fairly easy to implement, but I haven't done so
primarily because I want to solve it properly, which means
On Thu, Sep 10, 2009 at 20:46, Russ Allbery r...@debian.org wrote:
Pierre Habouzit madco...@madism.org writes:
On Thu, Sep 10, 2009 at 05:23:32PM +0200, Stefano Zacchiroli wrote:
Conceptually, what we want is trivial: we want submitter to be
subscribed (in the sense of bts subscribe) by
On Thu,10.Sep.09, 09:32:55, Kumar Appaiah wrote:
Just my view, I try to remember to Cc the reporter, but I'd much
rather prefer being subscribed to bugs as I report them.
Or maybe make it possible to subscribe by just replying to the ACK mail.
Regards,
Andrei
--
If you can't explain it
Holger Levsen wrote:
But I also think the acknowledgement mail should contain the information
that the submitter is not being subscribed by default and how s/he can
subscribe.
IMHO this is very wrong: the user has already taken the trouble to report
the bug. We should not make him/her jump
Russ Allbery wrote:
That should probably be something that would fly for me actually. and
you could make reportbug take an option to add some kind of pseudo
header so that subscribing is not done for the rare cases when sender
doesn't want to be subscribed.
I would ideally like to see this
On Thu, Sep 10, 2009 at 04:05:19PM +0100, Colin Tuckley wrote:
Quoting Mark Brown broo...@sirena.org.uk:
What would be really useful here is the ability to set up the BTS to
subscribe you to bugs you've filed by default. That avoids the issue
with confusing less technical users.
That is
On Thu, 10 Sep 2009, David Nusinow wrote:
Don Armstrong wrote:
On Thu, 10 Sep 2009, Sandro Tosi wrote:
I was thinking about this a couple of hours ago, but in the
different direction: why not mailing the submitter by default?
Ideally, I'd imaging nnn...@b.d.o to reach
- submitter
On Thu, Sep 10, 2009 at 22:31, Don Armstrong d...@debian.org wrote:
On Thu, 10 Sep 2009, David Nusinow wrote:
Don Armstrong wrote:
On Thu, 10 Sep 2009, Sandro Tosi wrote:
I was thinking about this a couple of hours ago, but in the
different direction: why not mailing the submitter by default?
On Thu, 10 Sep 2009, Sandro Tosi wrote:
Given the high rate of people (at least in those that replied here)
in favor of adding submitter in the loop of n...@b.d.o, I think your
plan is very good:
- include the submitter in n...@b.d.o by default now;
Considering the fact that this thread has
On Thu, Sep 10, 2009 at 6:45 PM, W. Martin Borgert deba...@debian.org wrote:
Quoting Andres Salomon dilin...@collabora.co.uk:
Yes, trac will be maintained in the Python Application Packaging Team.
I already tried to copy the git history to the PAPT svn, but - lacking
any experience with git -
Package: wnpp
Severity: wishlist
Owner: Ivan Kohler ivan-deb...@420.am
* Package name: libnet-opensrs-perl
Version : 0.03
Upstream Author : Richard Siddall http://search.cpan.org/~rsiddall/
* URL : http://search.cpan.org/dist/Net-OpenSRS/
* License : Perl
On Thu, Sep 10, 2009 at 09:19:25AM +0200, Miquel van Smoorenburg wrote:
On Wed, 2009-09-09 at 19:02 -0400, James Vega wrote:
tag 528494 help
thanks
#528494 raised the idea of having vim-tiny (the default vi-like editor
on a base install) provide /bin/vi so that it would be accessible
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 495 (new: 0)
Total number of packages offered up for adoption: 161 (new: 0)
Total number of packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 07:40:14 +0200
Source: xserver-xorg-video-ati
Binary: xserver-xorg-video-ati xserver-xorg-video-ati-dbg
xserver-xorg-video-radeon xserver-xorg-video-radeon-dbg
Architecture: source i386
Version: 1:6.12.3-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 06:45:12 +0200
Source: kdevelop
Binary: kdevelop kdevelop-doc kdevelop-data kdevelop-dev
Architecture: source all amd64
Version: 4:3.5.5-1
Distribution: unstable
Urgency: low
Maintainer: Jeremy Lainé
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 08:19:39 +0200
Source: libg15
Binary: libg15-1 libg15-dev
Architecture: source amd64
Version: 1.2.7-2
Distribution: unstable
Urgency: low
Maintainer: Giacomo Catenazzi c...@debian.org
Changed-By: Giacomo Catenazzi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 02 Sep 2009 17:19:14 +0200
Source: libv4l
Binary: libv4l-0 libv4l-dev lib32v4l-0 lib32v4l-dev
Architecture: source i386
Version: 0.6.1-1
Distribution: unstable
Urgency: low
Maintainer: Gregor Jasny gja...@googlemail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 10 Sep 2009 14:02:42 +0800
Source: mojito
Binary: libmojito0 libmojito-dev libmojito0-dbg libmojito-client1
libmojito-client-dev libmojito-client1-dbg
Architecture: source i386
Version: 0.20.1+dfsg-1
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 08:56:30 +0200
Source: iceweasel
Binary: iceweasel iceweasel-gnome-support iceweasel-dbg
Architecture: source all amd64
Version: 3.0.14-1
Distribution: unstable
Urgency: low
Maintainer: Eric Dorland e...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 11:34:01 +0200
Source: pgdesigner
Binary: pgdesigner
Architecture: source all
Version: 1.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Pierre Chifflier pol...@debian.org
Changed-By: Pierre Chifflier
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 09:53:38 +0200
Source: kadu
Binary: kadu kadu-common kadu-external-modules kadu-themes
Architecture: source i386 all
Version: 0.6.5.3-1
Distribution: unstable
Urgency: low
Maintainer: Patryk Cisek pat...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 08:08:06 +0200
Source: xulrunner
Binary: xulrunner-1.9 xulrunner-1.9-gnome-support libmozjs1d libmozjs-dev
libmozjs1d-dbg spidermonkey-bin xulrunner-dev xulrunner-1.9-dbg
libmozillainterfaces-java python-xpcom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 11:12:08 +0200
Source: denemo
Binary: denemo
Architecture: source i386
Version: 0.8.8-1.1
Distribution: unstable
Urgency: low
Maintainer: Guenter Geiger (Debian/GNU) gei...@debian.org
Changed-By: Pietro Battiston
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 06 Sep 2009 19:36:42 +0200
Source: alsa-driver
Binary: linux-sound-base alsa-base alsa-source
Architecture: source all
Version: 1.0.21+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian ALSA Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 12:15:04 +0200
Source: qcontrol
Binary: qcontrol qcontrol-udeb
Architecture: source armel
Version: 0.4.2-3
Distribution: unstable
Urgency: low
Maintainer: Frans Pop f...@debian.org
Changed-By: Frans Pop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 10:50:03 +0100
Source: telepathy-salut
Binary: telepathy-salut
Architecture: source i386
Version: 0.3.10-1
Distribution: unstable
Urgency: low
Maintainer: Debian Telepathy maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 11:37:00 +0200
Source: fio
Binary: fio
Architecture: source i386
Version: 1.33.1-1
Distribution: unstable
Urgency: low
Maintainer: Martin Steigerwald m...@teamix.de
Changed-By: Martin Steigerwald m...@teamix.de
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Format: 1.8
Date: Thu, 10 Sep 2009 13:16:49 +0200
Source: sugar-toolkit-0.84
Binary: python-sugar-toolkit-0.84
Architecture: source amd64
Version: 0.84.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian OLPC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 13:02:34 +0200
Source: libaio
Binary: libaio1 libaio1-udeb libaio1-dbg libaio-dev
Architecture: source amd64
Version: 0.3.107-7
Distribution: unstable
Urgency: low
Maintainer: Guillem Jover guil...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 12:11:50 +0200
Source: libhdf4
Binary: libhdf4-0 hdf4-tools libhdf4g-dev libhdf4-dev libhdf4-doc libhdf4-0-alt
libhdf4-alt-dev
Architecture: source all i386
Version: 4.2r4-6
Distribution: unstable
Urgency: medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 13:35:24 +0200
Source: lustre
Binary: linux-patch-lustre lustre-source lustre-utils lustre-tests liblustre
lustre-dev
Architecture: source all i386
Version: 1.8.1-1
Distribution: experimental
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 14:36:09 +0200
Source: bzr-svn
Binary: bzr-svn
Architecture: source all
Version: 1.0.0~bzr3160-1
Distribution: experimental
Urgency: low
Maintainer: Debian Bazaar Maintainers pkg-bazaar-ma...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 14:42:13 +0200
Source: bzr-rebase
Binary: bzr-rebase
Architecture: source all
Version: 0.5.3+bzr165-1
Distribution: experimental
Urgency: low
Maintainer: Debian Bazaar Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 09 Sep 2009 06:32:40 +0100
Source: cl-irc
Binary: cl-irc
Architecture: source all
Version: 1:0.8.1-dfsg-3
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 09 Sep 2009 06:16:28 +0100
Source: flexi-streams
Binary: cl-flexi-streams
Architecture: source all
Version: 1.0.7-2
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 03 Sep 2009 16:41:31 +0100
Source: cl-ppcre
Binary: cl-ppcre
Architecture: source all
Version: 2.0.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 09:26:45 +0100
Source: slime
Binary: slime cl-swank
Architecture: source all
Version: 1:20090908-1
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 09 Sep 2009 06:24:19 +0100
Source: cl-usocket
Binary: cl-usocket
Architecture: source all
Version: 0.4.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 15:31:53 +0200
Source: bzr-hg
Binary: bzr-hg
Architecture: source all
Version: 0.1~bzr111-1
Distribution: unstable
Urgency: low
Maintainer: Debian Bazaar Maintainers pkg-bazaar-ma...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 09:40:43 +0100
Source: cl-xmls
Binary: cl-xmls
Architecture: source all
Version: 1.2-3
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 03 Sep 2009 16:35:33 +0100
Source: cl-split-sequence
Binary: cl-split-sequence
Architecture: source all
Version: 20050802-3
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 09:52:18 +0100
Source: cl-ptester
Binary: cl-ptester
Architecture: source all
Version: 2.1.2-6
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 07:17:43 +0100
Source: cl-rt
Binary: cl-rt
Architecture: source all
Version: 20040621-4
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 09 Sep 2009 06:04:44 +0100
Source: cl-portable-aserve
Binary: cl-aserve cl-acl-compat cl-htmlgen cl-webactions
Architecture: source all
Version: 1.2.42+cvs.2008.08.15-dfsg-1
Distribution: unstable
Urgency: low
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 08:41:02 +0100
Source: cl-md5
Binary: cl-md5
Architecture: source all
Version: 1:1.8.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 14:11:00 +0200
Source: why
Binary: why why-examples libjessie-ocaml-dev libwhy-coq
Architecture: source amd64 all
Version: 2.19+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Debian OCaml Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 15:09:49 +0200
Source: glide
Binary: glide2-bin libglide2 libglide2-dev libglide3 libglide3-dev
Architecture: source amd64
Version: 2002.04.10ds1-4
Distribution: unstable
Urgency: low
Maintainer: Guillem Jover
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 14:20:11 +0100
Source: cl-asdf
Binary: cl-asdf cl-cclan
Architecture: source all
Version: 1:20090819-2
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 13:48:15 +0200
Source: bzr
Binary: bzr
Architecture: source amd64
Version: 2.0~rc1-1
Distribution: experimental
Urgency: low
Maintainer: Debian Bazaar Maintainers pkg-bazaar-ma...@lists.alioth.debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 13:14:18 +0100
Source: cffi
Binary: cl-cffi
Architecture: source all
Version: 20090823-1
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 13:30:48 +0100
Source: cl-contextl
Binary: cl-contextl
Architecture: source all
Version: 0.52-1
Distribution: unstable
Urgency: low
Maintainer: Debian Common Lisp Team
pkg-common-lisp-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 13:11:56 +0200
Source: libconfig-model-perl
Binary: libconfig-model-perl
Architecture: source all
Version: 0.640-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 15:32:23 +0200
Source: fai
Binary: fai-client fai-doc fai-server fai-quickstart fai-nfsroot
Architecture: source all
Version: 3.2.20.1
Distribution: unstable
Urgency: low
Maintainer: Thomas Lange la...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 16:52:28 +0200
Source: blobandconquer
Binary: blobandconquer blobandconquer-data
Architecture: source all amd64
Version: 1.07-dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Guus Sliepen g...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 10 Sep 2009 17:24:04 +0200
Source: libfinance-quote-perl
Binary: libfinance-quote-perl
Architecture: source all
Version: 1.16-4
Distribution: unstable
Urgency: low
Maintainer: Bart Martens ba...@debian.org
Changed-By: Bart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 09 Sep 2009 22:27:15 +0200
Source: liblatex-table-perl
Binary: liblatex-table-perl
Architecture: source all
Version: 1.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 10 Sep 2009 16:10:19 +0200
Source: sivp
Binary: scilab-sivp
Architecture: source i386
Version: 0.5.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team
debian-science-maintain...@lists.alioth.debian.org
1 - 100 of 165 matches
Mail list logo
