* Tollef Fog Heen tfh...@err.no [120223 22:21]:
]] Bernhard R. Link
Your shell is most likely implemented in C, but it's not like you sit
down and have to debug it every other day. Why do you assume that you
need to do so just because policy is encoded in .ini-like files instead
of shell
Le vendredi 24 février 2012 à 08:47 +0100, Bernhard R. Link a écrit :
What I try to say is If there can only be one, then this should not
be systemd. So if Debian shall have systemd, it should support multiple
init systems.
What we say is: there should be only one, and it will certainly not
Package: wnpp
Severity: normal
I request assistance with maintaining the scim package.
scim comprises software to input complex characters in non-latin languages
such as Chinese Hanzi, Japanese Kanji or Korean Hangul and others. It
enjoys widespread and growing use. scim is scheduled to be
On 02/23/2012 05:54 PM, Lars Wirzenius wrote:
On Thu, Feb 23, 2012 at 10:29:37AM +0100, Thomas Hood wrote:
I know the System V init system fairly well but I am new to both
Upstart and systemd. Obviously the two are similar insofar as they are
both able to supersede SysV init.
I'm
Package: wnpp
Severity: normal
(I hope reportbug will actually do the right thing, despite
incorrectly claiming that isdnutils package did not exist)
I am requesting assistance to maintain isdnutils in Debian. The main
use case would be faxing, I assume. That's what I use the package for.
But
Package: wnpp
Severity: wishlist
Owner: Laszlo Kajan lka...@rostlab.org
* Package name: ffindex
Version : 0.9.3
Upstream Author : Andreas Hauser hau...@genzentrum.lmu.de
* URL :
http://pubshare.genzentrum.lmu.de/scientific_computing/software/ffindex/
* License
Hi Martin,
On Tue, Feb 21, 2012 at 01:06:41PM +0100, W. Martin Borgert wrote:
If I understand correctly, the current Ubuntu version 1.4-0ubuntu8
works perfectly for Debian. Is there any reason to not upload this
version to Debian?
The main reason is that there is as yet no solid policy that
On Fri, 24 Feb 2012 17:07:46 +0800
Thomas Goirand z...@debian.org wrote:
On 02/23/2012 05:54 PM, Lars Wirzenius wrote:
On Thu, Feb 23, 2012 at 10:29:37AM +0100, Thomas Hood wrote:
I know the System V init system fairly well but I am new to both
Upstart and systemd. Obviously the two
]] Bernhard R. Link
* Tollef Fog Heen tfh...@err.no [120223 22:21]:
]] Bernhard R. Link
Your shell is most likely implemented in C, but it's not like you sit
down and have to debug it every other day. Why do you assume that you
need to do so just because policy is encoded in .ini-like
On Wed, Feb 22, 2012 at 03:24:47PM +0200, Riku Voipio wrote:
On Tue, Feb 21, 2012 at 01:12:08PM -0800, Steve Langasek wrote:
The meme that systemd is better than upstart because it doesn't depend
on a shell is poppycock. No one has done any benchmarking to support
the claim that /bin/sh is
On Fri, 2012-02-24 at 09:16 +0100, Josselin Mouette wrote:
Le vendredi 24 février 2012 à 08:47 +0100, Bernhard R. Link a écrit :
What I try to say is If there can only be one, then this should not
be systemd. So if Debian shall have systemd, it should support multiple
init systems.
What
Svante Signell svante.sign...@telia.com writes:
policy? While at the time supporting non-linux systems (like kFreeBSD
and Hurd, and others to come)
I understood that Hurd does not use sysvinit either. Is that still the
case?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Matthias Urlichs matth...@urlichs.de
* Package name: python-ultramysql
Version : 2.1
Upstream Author : Jonas Tarnstrom and ESN Social Software AB
jonas.tarnst...@esn.me
* URL : https://github.com/esnme/ultramysql
* License
On Fri, 2012-02-24 at 11:57 +0200, Timo Juhani Lindfors wrote:
Svante Signell svante.sign...@telia.com writes:
policy? While at the time supporting non-linux systems (like kFreeBSD
and Hurd, and others to come)
I understood that Hurd does not use sysvinit either. Is that still the
case?
On 02/21/2012 11:22 PM, Steve Langasek wrote:
On Tue, Feb 21, 2012 at 10:28:55PM +0100, John Paul Adrian Glaubitz wrote:
What do you know of the upstart design that makes you think systemd's design
is better? The above could be a paraphrase of Lennart's blog, for all it
says about the upstart
On 02/22/2012 09:52 AM, Josselin Mouette wrote:
Le mardi 21 février 2012 à 23:37 +0100, John Paul Adrian Glaubitz a
écrit :
The biggest disadvantage of systemd is surely that it is Linux-only and
probably won't work with other kernels in near future, so it's absolutely
desirable to support
On Fri, Feb 24, 2012 at 10:51:23AM +0100, Svante Signell wrote:
On Fri, 2012-02-24 at 09:16 +0100, Josselin Mouette wrote:
Le vendredi 24 février 2012 à 08:47 +0100, Bernhard R. Link a écrit :
What I try to say is If there can only be one, then this should not
be systemd. So if Debian
Le vendredi 24 février 2012 à 10:45 +, Lars Wirzenius a écrit :
Should we allow kFreeBSD and Hurd (and, possibly, other kernels in
the future), which do not support the features required by systemd
and upstart, allow us to get away from sysvinit and start using an
event based init system?
* Tollef Fog Heen tfh...@err.no [120224 10:45]:
]] Bernhard R. Link
* Tollef Fog Heen tfh...@err.no [120223 22:21]:
]] Bernhard R. Link
Your shell is most likely implemented in C, but it's not like you sit
down and have to debug it every other day. Why do you assume that you
need
On Fri, Feb 24, 2012 at 10:45:41AM +, Lars Wirzenius wrote:
On Fri, Feb 24, 2012 at 10:51:23AM +0100, Svante Signell wrote:
Then you are excluding all non-linux systems. Is that part of Debian
policy? While at the time supporting non-linux systems (like kFreeBSD
and Hurd, and others to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 24.02.2012 12:10, Josselin Mouette wrote:
There is another option here. We make a project-wide decision of
which init system to use for Linux (systemd or upstart). And we
write a compatibility layer for non-Linux systems, that generates
]] Bernhard R. Link
* Tollef Fog Heen tfh...@err.no [120224 10:45]:
[...]
systemd unit files are declarative.
And that is exactly why I think you will likely need to be C programmer
and understand the internals of systemd to debug your boot process and
to fix it in case you have
On Fri, Feb 24, 2012 at 9:10 AM, Josselin Mouette j...@debian.org wrote:
Of course the hard part is to make the initial decision to switch to a
given init system; this is the kind of things Debian is very bad at.
That's something I've always wondered. It seems to me that we'll
*never* reach any
* Tollef Fog Heen tfh...@err.no [120224 13:05]:
And that is exactly why I think you will likely need to be C programmer
and understand the internals of systemd to debug your boot process and
to fix it in case you have problems.
How do you come to that conclusion? It's not like you need to
On Fri, 24 Feb 2012, Roger Leigh rle...@codelibre.net wrote:
There's nothing intrinsically non-portable about the systemd
socket-based activation scheme. It's just all the cgroups and other
stuff on top of that that's the problem. And the attitude of the
upstream maintainer towards
[Bernhard R. Link]
Currently we have a system where every user has a chance to debug
and fix those problems and make their system work again.
I just wanted to give a small comment on this, as one of the sysvinit
package maintainers in Debian. The quoted text give the impression
that the
On Thu, Feb 23, 2012 at 02:09:54PM -0800, Russ Allbery wrote:
Does this have any influence on #658139?
This particular change is unrelated. It just moved language from one
document to another;
I've got this part. My question was targeting rather in the direction:
Does the fact that this
Hi,
I plan to ask for the removal of the yiff sound package from Debian late
next week.
- It no longer appears to have any upstream maintainer.
- The only package that depends on yiff is roaraudio, and I think that's
only as a minor plugin. (I'm cc'ing the maintainers of roaraudio.)
Am 24.02.2012 14:12, schrieb Phil Brooke:
Hi,
I plan to ask for the removal of the yiff sound package from Debian late
next week.
- It no longer appears to have any upstream maintainer.
- The only package that depends on yiff is roaraudio, and I think that's
only as a minor plugin.
Roger Leigh wrote:
I certainly don't think it's fair for fairly niche platforms to hold
back Linux indefinitely. There is a high cost on maintainers to
support these platforms, and it would be an ideal situation if
systemd or upstart were sufficiently portable to run on them, even
if they
On Fri, 2012-02-24 at 12:57 +0100, Arno Töll wrote:
Hi,
On 24.02.2012 12:10, Josselin Mouette wrote:
There is another option here. We make a project-wide decision of
which init system to use for Linux (systemd or upstart). And we
write a compatibility layer for non-Linux systems, that
m...@linux.it (Marco d'Itri) writes:
On Feb 23, Goswin von Brederlow goswin-...@web.de wrote:
Say you have a desktop system but also have apache, postgresql, ... for
some developement work installed. First thing you need when you turn it
on is your desktop. The apache and postgresql do not
Salvo Tomaselli tipos...@tiscali.it writes:
But for me all the new init systems have a fundamental lack: They do not
have priorities.
I think that's gone already.. update-rc.d already does whatever it wants with
the priorities.
Not what I ment. The traditional init doesn't have this
On Fri, Feb 24, 2012 at 11:31:38AM +1100, Russell Coker wrote:
Finally one benefit of an event based booting system is that it won't become
stuck if one daemon hangs. I've had problems in the past when one daemon
didn't start up and that prevented other daemons from starting due to the
Josselin Mouette j...@debian.org writes:
Le vendredi 24 février 2012 à 10:45 +, Lars Wirzenius a écrit :
Should we allow kFreeBSD and Hurd (and, possibly, other kernels in
the future), which do not support the features required by systemd
and upstart, allow us to get away from
Petter Reinholdtsen p...@hungry.com writes:
[Bernhard R. Link]
Currently we have a system where every user has a chance to debug
and fix those problems and make their system work again.
I just wanted to give a small comment on this, as one of the sysvinit
package maintainers in Debian. The
Package: wnpp
Severity: wishlist
Owner: Sylvestre Ledru sylves...@debian.org
* Package name: scirenderer
Version : 0.3.3
Upstream Author : Pierre Lando (Digiteo) and other (Digiteo + Scilab
Enterprises)
* URL : http://forge.scilab.org/index.php/p/scirenderer/
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24.02.2012 17:07, Goswin von Brederlow wrote:
Josselin Mouette j...@debian.org writes: And we write a
compatibility layer for non-Linux
systems, that generates sysvinit-compatible scripts based on
systemd services or upstart jobs.
...
So what
Yaroslav Halchenko deb...@onerussian.com writes:
Hi,
I am about to upload a fresh new package -- CDE
http://www.stanford.edu/~pgbovine/cde.html
which is heavily based on strace (pretty much it is a code fork of
strace to provide necessary functionality).
Upstream author maintains it for
Steve Langasek vor...@debian.org writes:
On Thu, Feb 23, 2012 at 12:13:33PM +0100, Goswin von Brederlow wrote:
the goal for wheezy is to support multiarch and that means we can finaly
get rid of the ugly ia32-libs packages. For this to happen all packages
used in ia32-libs need to be
On Fri, 24 Feb 2012, Goswin von Brederlow wrote:
up, I would start disabling architectures. Since the package has never
been built on any architecture the build failures will not hold you back
in any way. All they do is generate build logs.
ah -- I thought those FTBFS would forbid migration
Yaroslav Halchenko, le Fri 24 Feb 2012 12:00:00 -0500, a écrit :
On Fri, 24 Feb 2012, Goswin von Brederlow wrote:
up, I would start disabling architectures. Since the package has never
been built on any architecture the build failures will not hold you back
in any way. All they do is
[ Sending this late reply now, which I had around as a draft, but with
the latest incarnation of this debate it's become relevant again. ]
Hi!
On the other kernels lack of features I'll just point to the
“Functionality Equivalence” section in the Porting Guidelines draft I've
been preparing at
On Thu, 2012-02-23 at 07:24:20 +0100, Tollef Fog Heen wrote:
]] Tzafrir Cohen
In sysv init scripts the daemon forks into the background. In upstrart
and systemd it doesn't have to (or shouldn't). (not) forking requires a
different command-line argument, normally. This leads to odd beasts
[Goswin von Brederlow]
Not what I ment. The traditional init doesn't have this either.
But sysvinit/startpar have it at the moment. The display managers
have priority, and startpar try very hard to get them running early
during the boot. :)
If I remember correctly, the xdm, kdm and gdm scripts
Steve Langasek vor...@debian.org writes:
On Tue, Feb 21, 2012 at 01:06:41PM +0100, W. Martin Borgert wrote:
If I understand correctly, the current Ubuntu version 1.4-0ubuntu8
works perfectly for Debian. Is there any reason to not upload this
version to Debian?
The main reason is that there
Bernhard R. Link brl...@debian.org writes:
* Tollef Fog Heen tfh...@err.no [120224 13:05]:
How do you come to that conclusion? It's not like you need to be a C
programmer to debug CSS files or a C programmer to debug Makefiles.
As big a fan of Makefile that I am, but they are essentially
Fernando Lemos fernando...@gmail.com writes:
Josselin Mouette j...@debian.org wrote:
Of course the hard part is to make the initial decision to switch to a
given init system; this is the kind of things Debian is very bad at.
That's something I've always wondered. It seems to me that we'll
On Freitag, 24. Februar 2012, Karl Goetz wrote:
Contributors *to upstart* need to agree to the canonical contribution
agreement, I'm not sure what gives you the idea that all daemon
maintainers will fall in that category.
still.
a blocker.
signature.asc
Description: This is a digitally
On Fri, Feb 24, 2012 at 10:25:14AM -0800, Russ Allbery wrote:
Steve Langasek vor...@debian.org writes:
On Tue, Feb 21, 2012 at 01:06:41PM +0100, W. Martin Borgert wrote:
If I understand correctly, the current Ubuntu version 1.4-0ubuntu8
works perfectly for Debian. Is there any reason to
On Freitag, 24. Februar 2012, Karl Goetz wrote:
Contributors *to upstart* need to agree to the canonical contribution
agreement, I'm not sure what gives you the idea that all daemon
maintainers will fall in that category.
[Holger Levsen]
still.
a blocker.
Eh, it's only a problem if
Peter Samuelson pe...@p12n.org writes:
Eh, it's only a problem if the upstart maintainers in Debian refuse to
accept work (via either BTS patches, or done directly by comaintainers)
that upstream will not also accept.
I don't really want Debian to be in the position of forking its own init
On Thu, Feb 23, 2012 at 11:58:08AM +0100, Goswin von Brederlow wrote:
Upstart also does not support Should-Start which makes it impossible to
provide corect init scripts for a number of services. For example autofs
will not work if it uses nis because nis is not started before
autofs. Due to
Guillem Jover wrote:
On the other kernels lack of features I'll just point to the
“Functionality Equivalence” section in the Porting Guidelines draft I've
been preparing at http://www.hadrons.org/~guillem/debian/ports/porting.
Most of the features listed as required for systemd are either
On Fri, Feb 24, 2012 at 12:50:15PM -0600, Peter Samuelson wrote:
On Freitag, 24. Februar 2012, Karl Goetz wrote:
Contributors *to upstart* need to agree to the canonical contribution
agreement, I'm not sure what gives you the idea that all daemon
maintainers will fall in that
On Fri, Feb 24, 2012 at 05:02:25PM +0100, Goswin von Brederlow wrote:
On Fri, Feb 24, 2012 at 11:31:38AM +1100, Russell Coker wrote:
Finally one benefit of an event based booting system is that it won't
become
stuck if one daemon hangs. I've had problems in the past when one daemon
Lars Wirzenius l...@liw.fi writes:
I see the following as a serious issue: upstart requires contributors
to sign the Canonical contributor agreement
(http://www.canonical.com/contributors).
This is unlike most free-software projects, where “inbound = outbound”
On Fri, Feb 24, 2012 at 04:20:47PM +0200, Uoti Urpala wrote:
Roger Leigh wrote:
I certainly don't think it's fair for fairly niche platforms to hold
back Linux indefinitely. There is a high cost on maintainers to
support these platforms, and it would be an ideal situation if
systemd or
On Fri, Feb 24, 2012 at 20:17, Steve Langasek vor...@debian.org wrote:
On Thu, Feb 23, 2012 at 11:58:08AM +0100, Goswin von Brederlow wrote:
Upstart also does not support Should-Start which makes it impossible to
provide corect init scripts for a number of services. For example autofs
will
* Russ Allbery r...@debian.org [120224 19:28]:
Staring at the bug and the makefile and thinking hard is usually sufficient.
It's usually sufficient (because the concept is quite easy), but once
that does not work there is hardly any other chance, except wild
experimenting (which I hardly would
Bernhard R. Link brl...@debian.org writes:
* Russ Allbery r...@debian.org [120224 19:28]:
One of the primary features of newer init systems like upstart and
systemd is that they take care of the routine stuff automatically and
thereby reduce the conceptual surface of your init script
Roger Leigh wrote:
On Fri, Feb 24, 2012 at 04:20:47PM +0200, Uoti Urpala wrote:
Portability is not necessarily a positive attribute. When you're talking
about standard functionality available on all platforms, it's cleaner to
write it using standard interfaces that work everywhere. But if
On Fri, 2012-02-24 at 21:09 +0200, Uoti Urpala wrote:
Guillem Jover wrote:
...
I think it's quite arrogant of BSD users to expect others to work to
support their systems. The BSD userbase is small enough that most
projects have alternative things to work on that help a lot more people
than
On Fri, Feb 24, 2012 at 10:55:46PM +0100, Thomas Hood wrote:
On Fri, Feb 24, 2012 at 20:17, Steve Langasek vor...@debian.org wrote:
On Thu, Feb 23, 2012 at 11:58:08AM +0100, Goswin von Brederlow wrote:
Upstart also does not support Should-Start which makes it impossible to
provide corect
On Feb 25, 2012, at 12:42 AM, Steve Langasek wrote:
Well, I fudged a little here. You're right that, as written above, nis is
not guaranteed to start before autofs. Due to a (well-understood and
recognized) limitation of upstart's current event handling, if the
'runlevel' event is seen
On Fri, 2012-02-24 at 15:42 -0800, Steve Langasek wrote:
On Fri, Feb 24, 2012 at 10:55:46PM +0100, Thomas Hood wrote:
On Fri, Feb 24, 2012 at 20:17, Steve Langasek vor...@debian.org wrote:
On Thu, Feb 23, 2012 at 11:58:08AM +0100, Goswin von Brederlow wrote:
Upstart also does not
Svante Signell svante.sign...@telia.com writes:
Why not simply implement the early boot event driven parts in init as
proposed earlier, and get rid of these non-portable commercial stuff.
Are you really committed to Debian? Maybe you should work for Canonical
or RedHat?
This sort of personal
On Sat, Feb 25, 2012 at 8:41 AM, Nandakumar wrote:
The Chalanam 2D Animation Studio
https://launchpad.net/chalanam/
There doesn't appear to be any source code repository or tarballs.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to
Package: wnpp
Severity: wishlist
Owner: Robert S. Edmonds edmo...@debian.org
* Package name: mtbl
Version : 0.1
Upstream Author : Internet Systems Consortium, Inc.
* URL : https://github.com/edmonds/mtbl
* License : ISC, BSD-3-Clause, Apache-2.0
Programming
Package: wnpp
Severity: wishlist
Owner: Robert S. Edmonds edmo...@debian.org
* Package name: pymtbl
Version : 0.1
Upstream Author : Internet Systems Consortium, Inc.
* URL : https://github.com/edmonds/pymtbl
* License : ISC
Programming Lang: Cython
On Sat, Feb 25, 2012 at 08:26:16AM +1100, Ben Finney wrote:
I see the following as a serious issue: upstart requires contributors
to sign the Canonical contributor agreement
(http://www.canonical.com/contributors).
This is unlike most free-software projects, where “inbound = outbound”
Steve Langasek vor...@debian.org writes:
[1] Examples: MySQL as the default database for lots of projects;
Sleepycat/BDB as the backend for plenty of software, sometimes chosen
over GDBM; Qt; fox of ice and fire; and probably countless others that
don't come to mind because nobody really
Hi Roger,
On Fri, Feb 24, 2012 at 11:41:35AM +, Roger Leigh wrote:
Another alternative is to let sysvinit run systemd units and/or
upstart jobs. Given their declarative syntax, would it be possible
for these to be translated into init script form so that they can
be run by init? This
Steve Langasek vor...@debian.org writes:
There are two main challenges here that I'm aware of with trying to
generate init scripts from upstart jobs:
- Process supervision. A lot of the win of moving to an init system like
upstart or systemd is that init *knows* which process
On Fri, 2012-02-24 at 18:18 -0800, Steve Langasek wrote:
On Fri, Feb 24, 2012 at 07:58:21PM +, Ben Hutchings wrote:
Also, the only practical way this differs from the situation with
software from either the Free Software Foundation or the Apache
Software Foundation seems to be that,
On Sat, Feb 25, 2012 at 1:00 AM, Russ Allbery r...@debian.org wrote:
Steve Langasek vor...@debian.org writes:
There are two main challenges here that I'm aware of with trying to
generate init scripts from upstart jobs:
- Process supervision. A lot of the win of moving to an init system
Fernando Lemos fernando...@gmail.com writes:
How about a converter from a different, init-agnostic format into the
specific formats? That way we could specify stuff that's specific to
each format, things such as:
* Socket activation information for systemd (and possibly upstart with
On Sat, Feb 25, 2012 at 1:35 AM, Fernando Lemos fernando...@gmail.com wrote:
* Socket activation information for systemd (and possibly upstart with
upstart-socket-bridge)
By the way, I wonder if we could also come up with a wrapper that
allowed upstart to work with the systemd socket activation
On Sat, Feb 25, 2012 at 1:44 AM, Russ Allbery r...@debian.org wrote:
This file could be easier to parse than a upstart/systemd unit too. I
think even more than scripts could be converted into this basic
format. The only drawback I can see is that it's another init
description syntax to learn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 24 Feb 2012 08:24:25 +
Source: intercal
Binary: intercal
Architecture: source amd64
Version: 29:0.29-2
Distribution: unstable
Urgency: low
Maintainer: Mark Brown broo...@debian.org
Changed-By: Mark Brown broo...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 23 Feb 2012 11:43:06 +0100
Source: libconfig-gitlike-perl
Binary: libconfig-gitlike-perl
Architecture: source all
Version: 1.08-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 23 Feb 2012 18:36:19 +0100
Source: libdist-zilla-plugins-cjm-perl
Binary: libdist-zilla-plugins-cjm-perl
Architecture: source all
Version: 4.07-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 10:00:17 +0100
Source: libapp-daemon-perl
Binary: libapp-daemon-perl
Architecture: source all
Version: 0.15-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 09:15:53 +0100
Source: nspr
Binary: libnspr4-0d libnspr4-dev libnspr4-0d-dbg
Architecture: source amd64
Version: 4.9-1
Distribution: unstable
Urgency: low
Maintainer: Maintainers of Mozilla-related packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 09:56:10 +0100
Source: nss
Binary: libnss3-1d libnss3-tools libnss3-dev libnss3-1d-dbg
Architecture: source amd64
Version: 3.13.3-1
Distribution: unstable
Urgency: low
Maintainer: Maintainers of Mozilla-related
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 08:56:18 +
Source: openssh
Binary: openssh-client openssh-server ssh ssh-krb5 ssh-askpass-gnome
openssh-client-udeb openssh-server-udeb
Architecture: source i386 all
Version: 1:5.9p1-3
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 10:18:00 +0100
Source: consolekit
Binary: consolekit libck-connector0 libck-connector-dev libpam-ck-connector
Architecture: source amd64
Version: 0.4.5-2
Distribution: unstable
Urgency: low
Maintainer: Utopia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 24 Feb 2012 11:31:50 +0200
Source: php-mdb2
Binary: php-mdb2
Architecture: source all
Version: 2.5.0b3-0.1
Distribution: unstable
Urgency: low
Maintainer: Debian PHP PEAR Maintainers pkg-php-p...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 12:15:43 +0200
Source: upgrade-system
Binary: upgrade-system
Architecture: source all
Version: 1.5.1.1
Distribution: unstable
Urgency: low
Maintainer: Martin-Éric Racine martin-eric.rac...@iki.fi
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 24 Feb 2012 11:48:02 +0100
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-13
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 24 Feb 2012 11:07:02 +
Source: movabletype-opensource
Binary: movabletype-opensource movabletype-plugin-core
movabletype-plugin-zemanta
Architecture: source all
Version: 5.1.3+dfsg-1
Distribution: unstable
Urgency: high
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 01:07:17 +0100
Source: relatorio
Binary: python-relatorio
Architecture: source all
Version: 0.5.6-1
Distribution: unstable
Urgency: low
Maintainer: Debian Tryton Maintainers try...@lists.debian-maintainers.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 12:45:16 +0100
Source: sdlpango
Binary: libsdl-pango1 libsdl-pango-dev
Architecture: source amd64
Version: 0.1.2-6
Distribution: unstable
Urgency: low
Maintainer: Debian SDL packages maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 16 Dec 2011 15:53:41 +0100
Source: biomaj-watcher
Binary: biomaj-watcher
Architecture: source all
Version: 1.2.0-4
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 23 Feb 2012 17:25:54 +0100
Source: openvpn
Binary: openvpn
Architecture: source i386
Version: 2.2.1-5
Distribution: unstable
Urgency: low
Maintainer: Alberto Gonzalez Iniesta a...@inittab.org
Changed-By: Alberto Gonzalez Iniesta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 22 Feb 2012 07:14:07 +0100
Source: couriergrey
Binary: couriergrey
Architecture: source amd64
Version: 0.3.1-3
Distribution: unstable
Urgency: low
Maintainer: Marco Balmer ma...@balmer.name
Changed-By: Marco Balmer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 24 Feb 2012 14:03:51 +
Source: cmdtest
Binary: cmdtest
Architecture: source all
Version: 0.3-1
Distribution: unstable
Urgency: low
Maintainer: Lars Wirzenius l...@liw.fi
Changed-By: Lars Wirzenius l...@liw.fi
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 24 Feb 2012 14:44:27 +0100
Source: grml-debootstrap
Binary: grml-debootstrap
Architecture: source all
Version: 0.49
Distribution: unstable
Urgency: low
Maintainer: Grml Team t...@grml.org
Changed-By: Michael Prokop m...@grml.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 23 Feb 2012 11:40:45 +0100
Source: libextutils-cbuilder-perl
Binary: libextutils-cbuilder-perl
Architecture: source all
Version: 0.280205-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 23 Feb 2012 11:39:34 +0100
Source: libhttp-tiny-perl
Binary: libhttp-tiny-perl
Architecture: source all
Version: 0.017-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
1 - 100 of 144 matches
Mail list logo
