divfont face=Trebuchet MS size=02 color=00 br
//font/divdivfont face=Trebuchet MS size=02 color=00
bonjour ,br //font/divdivfont face=Trebuchet MS size=02
color=00 br //font/divdivfont face=Trebuchet MS size=02
color=00 nous sommes une entreprise d evenementielle basee a
On 05/31/2012 09:03 AM, Steve Langasek wrote:
If you're unhappy that the package has been unmaintained for a long time and
that the MIA process takes time to result in an orphaning... suck it up. If
it was actually a problem, someone would have noticed it earlier and done
something about it.
On Wed, 30 May 2012, Steve Langasek wrote:
There is no excuse for hijacking a package, ever.
If the maintainer is MIA, use the MIA process to get the package orphaned.
This goes too far IMO. One of the reasons why the MIA process has been
setup is because many DD fear forcibly taking over or
OoO En cette nuit striée d'éclairs du jeudi 31 mai 2012, vers 02:09,
Charles Plessy ple...@debian.org disait :
I do not know why developers prefer GitHub over Gitorious or other providers.
But I note that even gitlabhq, advertised on this list for its free license,
has its main download
[CCing debian-www as requested but I'm not subscribed]
Le 31/05/2012 00:34, Charles Plessy a écrit :
Le Sat, May 26, 2012 at 03:03:06AM +0100, Philip Ashmore a écrit :
What I noticed by its absence was that no-one linked to official Debian
policy detailing the choices made and their
On Thu, May 31, 2012 at 02:01:51PM +0800, Thomas Goirand wrote:
Did you see me writing I'd like to hijack php-codesniffer in order to rush
and get it into wheezy in time before the freeze? *NO* ! I didn't write
that.
Agreed. I'd have expected people, if anything, to answer suggesting the
On 05/30/2012 11:11 AM, Jonas Smedegaard wrote:
On 12-05-30 at 11:30am, Thomas Goirand wrote:
We aren't kicking him, we want to have the package team maintained.
He's fine to come and join!
You want to play by your rules (file), not his. That's kicking to me.
This doesn't really
Package: wnpp
Severity: wishlist
Owner: José Luis Segura Lucas josel.seg...@gmx.es
* Package name: grive
Version : 0.1.0
Upstream Author : Matchman Green match...@gmail.com
* URL : https://github.com/match065/grive
* License : GPL2
Programming Lang: C++
On Wed, May 30, 2012 at 06:03:05PM -0700, Steve Langasek wrote:
There is no excuse for hijacking a package, ever.
...
Hmm, this arguing sounds quite German to me. Rules are rules are rules
and you should not disregard them. So a German will wait in front of a
red traffic light even if there
Hi Charles,
On 12-05-31 at 08:29am, Charles Plessy wrote:
Le Wed, May 30, 2012 at 11:11:51AM +0200, Jonas Smedegaard a écrit :
*nothing* qualifies for a hijacking.
Dear Jonas,
your reaction seems to imply that hijacking is an implicit statement
of failure. But this can be
On 12-05-31 at 10:06am, Andreas Tille wrote:
On Wed, May 30, 2012 at 06:03:05PM -0700, Steve Langasek wrote:
There is no excuse for hijacking a package, ever.
...
Hmm, this arguing sounds quite German to me. Rules are rules are
rules and you should not disregard them. So a German will
On 12-05-31 at 09:22am, Bernd Zeimetz wrote:
On 05/30/2012 11:11 AM, Jonas Smedegaard wrote:
It is better to have a well maintained package than to ait for
somebody who collected a number of NMUs and doesn't react to bug
reports for years.
I perfectly agree.
But it is better to have
Package: general
Severity: normal
Every time I do updates or install a package via synaptics, adobe acrobat
reader is no longer on the menu, it should be listed always in the office menu.
-- System Information:
Debian Release: 6.0.5
APT prefers proposed-updates
APT policy: (500,
Jonas Smedegaard d...@jones.dk (31/05/2012):
I have heard before the argument of the sponsor having responsibility,
but in reality I have *never* heard of sponsors actually being held
responsible for anything but the concrete upload of a specific
packaging release.
Suggested reading:
Your message dated Thu, 31 May 2012 11:56:44 +0200
with message-id 201205311156.45092.hol...@layer-acht.org
and subject line Re: Bug#675327: general: Adobe acrobat reader problem
has caused the Debian Bug report #675327,
regarding general: Adobe acrobat reader problem
to be marked as done.
This
Hi Enrico,
On 12-05-31 at 09:19am, Enrico Zini wrote:
On Thu, May 31, 2012 at 02:01:51PM +0800, Thomas Goirand wrote:
Did you see me writing I'd like to hijack php-codesniffer in order
to rush and get it into wheezy in time before the freeze? *NO* ! I
didn't write that.
Agreed. I'd
On Donnerstag, 31. Mai 2012, Cyril Brulebois wrote:
[ Holger, that's fingerpointing. Pointing to how you quickly dealt with
those packages, thanks again. :-) ]
/me happily fingerpoints back at the release team and esp. KiBi, who greatly
deal with trying to get 1 packages and 1000 people in
On Thu, May 31, 2012 at 12:46:49AM +0300, Uoti Urpala wrote:
Also, nowadays normal filesystems are journaled; using a journal for
writes to /tmp damages the SSD for zero benefit.
Writing to /tmp will damage a SSD? Are you serious? And writing to /var
or /home will not?
If SSDs are so easy
On 05/31/2012 04:36 PM, Jonas Smedegaard wrote:
Hijacking, in my vocabulary, is when a non-maintainer takes matters in
his/her/their own hands and takes over maintainership without the
consent of the former maintainer and outside formal Debian procedures.
Nobody did that, or had the
Steve Langasek writes (Re: Orphaning php-codesniffer, then take it over by the
PHP PEAR team):
A hijack is, by definition, a declaration by the hijacker that they believe
they are not answerable to the project's processes for how package
maintenance is decided. It is antisocial vigilanteism
On 12-05-31 at 08:02pm, Thomas Goirand wrote:
On 05/31/2012 04:36 PM, Jonas Smedegaard wrote:
Hijacking, in my vocabulary, is when a non-maintainer takes matters
in his/her/their own hands and takes over maintainership without the
consent of the former maintainer and outside formal Debian
On 05/31/2012 03:03 AM, Steve Langasek wrote:
[...]
A hijack is, by definition, a declaration by the hijacker that they believe
they are not answerable to the project's processes for how package
maintenance is decided. It is antisocial vigilanteism and it is not
acceptable.
So asking people
On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
Hi,
You and a lot of others fail to realize that the *SPONSOR* is
responsible for the package.
Huh?!?
What does Maintainer: mean if not the entity being responsible for,
well, maintaining?!?
Who is responsible for the package
[dropping PHP Pear team as cc]
On 12-05-31 at 03:16pm, George Danchev wrote:
On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
You and a lot of others fail to realize that the *SPONSOR* is
responsible for the package.
Huh?!?
What does Maintainer: mean if not the entity
On Thursday 31 May 2012 14:43:00 Jonas Smedegaard wrote:
On 12-05-31 at 08:02pm, Thomas Goirand wrote:
On 05/31/2012 04:36 PM, Jonas Smedegaard wrote:
Hijacking, in my vocabulary, is when a non-maintainer takes matters
in his/her/their own hands and takes over maintainership without the
On 05/31/2012 08:43 PM, Jonas Smedegaard wrote:
I have no intention of spreading or amplifying wrong information.
Do I understand it correctly that your intention in your original
post was to have the package orphaned and then have a team take over
maintainance?
I was also pointing out
On Thursday 31 May 2012 16:15:31 Jonas Smedegaard wrote:
[dropping PHP Pear team as cc]
On 12-05-31 at 03:16pm, George Danchev wrote:
On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
You and a lot of others fail to realize that the *SPONSOR* is
responsible for the package.
On 31/05/12 16:40, Thomas Goirand wrote:
On 05/31/2012 08:43 PM, Jonas Smedegaard wrote:
I have no intention of spreading or amplifying wrong information.
Do I understand it correctly that your intention in your original
post was to have the package orphaned and then have a team take
over
On Thursday, May 31, 2012 03:16:06 PM George Danchev wrote:
On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
Hi,
You and a lot of others fail to realize that the *SPONSOR* is
responsible for the package.
Huh?!?
What does Maintainer: mean if not the entity being
On 31/05/12 15:11, Bernd Zeimetz wrote:
On 05/31/2012 03:03 AM, Steve Langasek wrote:
[...]
A hijack is, by definition, a declaration by the hijacker that
they believe they are not answerable to the project's processes for
how package maintenance is decided. It is antisocial vigilanteism
On 12-05-31 at 04:43pm, George Danchev wrote:
On Thursday 31 May 2012 16:15:31 Jonas Smedegaard wrote:
[dropping PHP Pear team as cc]
On 12-05-31 at 03:16pm, George Danchev wrote:
On Thursday 31 May 2012 11:47:21 Jonas Smedegaard wrote:
You and a lot of others fail to realize that
On Donnerstag, 31. Mai 2012, Jonas Smedegaard wrote:
You still avoid my question: What does Maintainer: mean?
why do you ask rhetoric questions? It's defined in policy and you know it. So
whats the point?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of
Hi Thomas,
On Donnerstag, 31. Mai 2012, Thomas Goirand wrote:
I was asking if it was alright to ask the MIA team to orphan the
package, yes, because no reply from Jack. Never I wanted to do
it myself, or take over the package without going through the
standard procedures.
yes, please do
On 05/31/2012 04:57 PM, Mehdi Dogguy wrote:
On 31/05/12 15:11, Bernd Zeimetz wrote:
On 05/31/2012 03:03 AM, Steve Langasek wrote:
[...]
A hijack is, by definition, a declaration by the hijacker that
they believe they are not answerable to the project's processes for
how package maintenance
On 31/05/12 18:15, Bernd Zeimetz wrote:
Part of the common and established procedure is to mail d-devel if
you intend to hijack a package
True, but it is _not_ common (nor acceptable) to let only 2-3 days for
the maintainer to reply.
The rest of the thread raised other questions such as the
Jonas Smedegaard dijo [Thu, May 31, 2012 at 05:52:47PM +0200]:
You avoided my question, it seems: What does Maintainer: mean, then?
What does Uploaders: field mean?
You still avoid my question: What does Maintainer: mean?
This is getting silly. Please stop the word-definitions game.
On 05/31/2012 06:25 PM, Mehdi Dogguy wrote:
On 31/05/12 18:15, Bernd Zeimetz wrote:
Part of the common and established procedure is to mail d-devel if
you intend to hijack a package
True, but it is _not_ common (nor acceptable) to let only 2-3 days for
the maintainer to reply.
They waited
On 05/31/2012 04:52 PM, Mehdi Dogguy wrote:
On 31/05/12 16:40, Thomas Goirand wrote:
On 05/31/2012 08:43 PM, Jonas Smedegaard wrote:
I have no intention of spreading or amplifying wrong information.
Do I understand it correctly that your intention in your original
post was to have the
On 05/31/2012 10:52 PM, Mehdi Dogguy wrote:
Please note that badly maintained is something quite different from
not maintained. AFAICS, the package we are talking about is not
affected by severe or critical bugs.
That's a mater of views. #470294 should be made RC IMO.
Or is writing to /usr
severity 470294 serious
thanks
Hi,
On Donnerstag, 31. Mai 2012, Thomas Goirand wrote:
That's a mater of views. #470294 should be made RC IMO.
somebody should do something ;-)
Or is writing to /usr not a good candidate for an RC bug?
I thought this was a serious violation of the policy. Am I
Dear all,
I have been trying to contact Patrick Winnertz (winnie-at-d.o). I
would like to see iTalc in Debian upgraded to 2.0 but Patrick is
neither replying to contact attempts via mail (Debian Edu mailing
list, directly), nor to contact attempts via IRC. My first attempt to
reach him
Hi,
On Wed, May 02, 2012 at 03:16:08PM +0100, Ben Hutchings wrote:
I'm also not seeing GNOME applications as file type handlers in
Akregator (KDE application). So I'm not sure this is even 'just' a
problem for text-mode applications.
I have no idea whether the solution proposed below could
Hi Thomas,
On Thu, May 31, 2012 at 02:01:51PM +0800, Thomas Goirand wrote:
On 05/31/2012 09:03 AM, Steve Langasek wrote:
A hijack is, by definition, a declaration by the hijacker that they
believe they are not answerable to the project's processes for how
package maintenance is decided.
Package: wnpp
Severity: wishlist
Owner: The Ayatana Packagers pkg-ayatana-de...@lists.alioth.debian.org
* Package name: libappindicator
Version : 0.4.92
Upstream Author : Ted Gould t...@ubuntu.com
* URL : https://launchpad.net/libappindicator
* License : GPL-3,
Hi,
A Short question. Is it possible to ITP a new release of some software
not being even considered by the DM, for whatever reason. Wishlist bugs
are submitted, etc. According to if there is no reply of bug reports,
there seems to be no interest at all from the DM to package that piece
of SW,
Svante Signell, le Thu 31 May 2012 22:22:21 +0200, a écrit :
A Short question. Is it possible to ITP a new release of some software
not being even considered by the DM, for whatever reason.
It's normally not a good thing to do. ITP is also not what you mean
here, BTW.
Wishlist bugs are
On 31.05.2012 21:35, Andreas Tille wrote:
In any case the idea is to collect issues of broken mime support where
maintainers are unable / not willing to respect Debian policy 9.7.
Adding more entries is simple: Just add the according mime file as
pkg.mime and add pkg to Enhances in
Svante Signell dijo [Thu, May 31, 2012 at 10:22:21PM +0200]:
Hi,
A Short question. Is it possible to ITP a new release of some software
not being even considered by the DM, for whatever reason. Wishlist bugs
are submitted, etc. According to if there is no reply of bug reports,
there seems
On Thu, 2012-05-31 at 16:20 -0500, Gunnar Wolf wrote:
Svante Signell dijo [Thu, May 31, 2012 at 10:22:21PM +0200]:
Hi,
A Short question. Is it possible to ITP a new release of some software
not being even considered by the DM, for whatever reason. Wishlist bugs
are submitted, etc.
Svante Signell dijo [Thu, May 31, 2012 at 11:45:13PM +0200]:
It's *usually* not what you want to do. There are several cases where
different versions of the same program are available in Debian, and I
am unfamiliar with the case at hand, but it's usually where a specific
older version of a
On Wed, 30 May 2012 18:03:05 -0700, Steve Langasek wrote:
There is no excuse for hijacking a package, ever.
[...]
Hi Steve,
while I really appreciate both your technical work and expertise as
well as your personal care for Debian, this mail didn't go down well
with me, for two reasons:
- It
Jonas, I think we all agree that the Maintainer should Maintain
whatever he signed up to. Non-Debian people have the right to maintain
packages through a sponsor, and they are encouraged to. And they are
encouraged to look for a different sponsor if their current one stops
being responsive,
Le Fri, Jun 01, 2012 at 01:47:07AM +0200, Salvo Tomaselli a écrit :
Jonas, I think we all agree that the Maintainer should Maintain
whatever he signed up to. Non-Debian people have the right to maintain
packages through a sponsor, and they are encouraged to. And they are
encouraged to look
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: 454 (new: 22)
Total number of packages offered up for adoption: 156 (new: 7)
Total number of packages
On Thu, May 31, 2012 at 09:19:37PM +0200, Mike Gabriel wrote:
Dear all,
I have been trying to contact Patrick Winnertz (winnie-at-d.o). I
would like to see iTalc in Debian upgraded to 2.0
Relevant bug report from 3 September 2011:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640200
but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 07:49:50 +0200
Source: libdatetime-format-natural-perl
Binary: libdatetime-format-natural-perl
Architecture: source all
Version: 1.00-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 08:51:39 +0200
Source: libpdl-netcdf-perl
Binary: libpdl-netcdf-perl
Architecture: source amd64
Version: 4.16-3
Distribution: unstable
Urgency: low
Maintainer: Henning Glawe gla...@debian.org
Changed-By: Henning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 30 May 2012 21:58:15 +0100
Source: presage
Binary: presage presage-dbg libpresage-doc libpresage1 libpresage1-dbg
libpresage-data libpresage-dev python-presage python-presage-dbg gprompter
gprompter-dbg pyprompter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 09:11:32 +0200
Source: libpdl-io-hdf5-perl
Binary: libpdl-io-hdf5-perl
Architecture: source amd64
Version: 0.63-3
Distribution: unstable
Urgency: low
Maintainer: Henning Glawe gla...@debian.org
Changed-By: Henning
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 09:22:06 +0200
Source: w3-dtd-mathml
Binary: w3-dtd-mathml
Architecture: source all
Version: 2.0.0.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian XML/SGML Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 30 May 2012 20:24:59 -0700
Source: qemu
Binary: qemu qemu-keymaps qemu-system qemu-user qemu-user-static qemu-utils
Architecture: source all i386
Version: 1.1.0~rc3+dfsg-1
Distribution: experimental
Urgency: low
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 30 May 2012 16:31:54 +0200
Source: uruk
Binary: uruk
Architecture: source all
Version: 20120530-1
Distribution: unstable
Urgency: low
Maintainer: Joost van Baal-Ilić joos...@debian.org
Changed-By: Joost van Baal-Ilić
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 09:25:50 +0200
Source: r-cran-surveillance
Binary: r-cran-surveillance
Architecture: source amd64
Version: 1.2-1-4
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 11:18:49 +0200
Source: libtext-format-perl
Binary: libtext-format-perl
Architecture: source all
Version: 0.56-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 23 May 2012 00:50:41 +
Source: serna-free
Binary: serna serna-dbg
Architecture: source amd64
Version: 4.3.0.20110221-7.1
Distribution: unstable
Urgency: low
Maintainer: Joachim Breitner nome...@debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 13:56:17 +1000
Source: libedit
Binary: libedit2 libedit-dev
Architecture: source mips mipsel sparc
Version: 2.11-20080614-4
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar ani...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 10:47:02 +0200
Source: citadel
Binary: citadel-server citadel-mta citadel-client citadel-doc citadel-dbg
Architecture: source amd64 all
Version: 8.11-1
Distribution: unstable
Urgency: low
Maintainer: Debian Citadel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 12:12:19 +0200
Source: fishpoll
Binary: fishpoke fishpolld
Architecture: source all
Version: 0.1.6-4
Distribution: unstable
Urgency: low
Maintainer: Fabrizio Regalli fab...@fabreg.it
Changed-By: Andrea Veri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 25 May 2012 11:28:54 +0200
Source: libcitadel
Binary: libcitadel2 libcitadel2-dbg libcitadel-dev
Architecture: source amd64
Version: 8.11-1
Distribution: unstable
Urgency: low
Maintainer: Debian Citadel Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 09:54:20 +0100
Source: logrotate
Binary: logrotate
Architecture: source amd64
Version: 3.8.1-5
Distribution: experimental
Urgency: low
Maintainer: Paul Martin p...@debian.org
Changed-By: Paul Martin p...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 23 May 2012 18:20:01 +0200
Source: webcit
Binary: citadel-webcit webcit-dbg citadel-suite
Architecture: source amd64 all
Version: 8.11-dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian Citadel Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 19:38:34 +1000
Source: libmnl
Binary: libmnl-dev libmnl0
Architecture: source mips mipsel sparc
Version: 1.0.3-3
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar ani...@debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 11:31:16 +0200
Source: dcmtk
Binary: dcmtk libdcmtk2 libdcmtk2-dev dcmtk-www dcmtk-doc
Architecture: source all amd64
Version: 3.6.0-11
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 08:04:34 +0200
Source: gnustep-icons
Binary: gnustep-icons
Architecture: source all
Version: 1.0-5
Distribution: unstable
Urgency: low
Maintainer: Gürkan Sengün gur...@phys.ethz.ch
Changed-By: Gürkan Sengün
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 12:03:03 +0200
Source: haskell-diagrams-lib
Binary: libghc-diagrams-lib-dev libghc-diagrams-lib-prof libghc-diagrams-lib-doc
Architecture: source all amd64
Version: 0.5-2
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 06:37:55 -0500
Source: lmtest
Binary: r-cran-lmtest
Architecture: source i386
Version: 0.9.30-1
Distribution: unstable
Urgency: low
Maintainer: Dirk Eddelbuettel e...@debian.org
Changed-By: Dirk Eddelbuettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 06:38:44 -0500
Source: strucchange
Binary: r-cran-strucchange
Architecture: source all
Version: 1.4-7-1
Distribution: unstable
Urgency: low
Maintainer: Dirk Eddelbuettel e...@debian.org
Changed-By: Dirk Eddelbuettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 13:48:17 +0200
Source: apcalc
Binary: apcalc apcalc-common apcalc-dev
Architecture: source all i386
Version: 2.12.4.4-3
Distribution: unstable
Urgency: low
Maintainer: Martin Buck mb...@debian.org
Changed-By: Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 25 May 2012 17:37:00 +
Source: libhibernate-validator-java
Binary: libhibernate-validator-java
Architecture: source all
Version: 4.0.2.GA-7
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 13:37:22 +0200
Source: xdms
Binary: xdms
Architecture: source amd64
Version: 1.3.2-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Axel Beckert a...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 14:21:07 +0200
Source: abi-compliance-checker
Binary: abi-compliance-checker
Architecture: source all
Version: 1.97.7-1
Distribution: unstable
Urgency: low
Maintainer: Ryan Niebur ryanrya...@gmail.com
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 31 May 2012 12:55:48 +0200
Source: flumotion
Binary: flumotion
Architecture: source amd64
Version: 0.10.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 12:04:54 +
Source: pixelmed
Binary: pixelmed-java
Architecture: source all
Version: 20120508-1
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 31 May 2012 13:53:27 +0200
Source: starpu
Binary: libstarpu-dev libstarpu-1.0 libstarpufft-1.0 libstarpumpi-1.0
starpu-tools starpu-top starpu-examples
Architecture: source amd64
Version: 1.0.1-2
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 31 May 2012 13:53:27 +0200
Source: starpu-contrib
Binary: libstarpu-contrib-dev libstarpu-contrib-1.0 libstarpu-contribfft-1.0
libstarpu-contribmpi-1.0 starpu-contrib-tools starpu-contrib-examples
libsocl-contrib-1.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 14:27:38 +0200
Source: japi-compliance-checker
Binary: japi-compliance-checker
Architecture: source all
Version: 1.1.1-1
Distribution: unstable
Urgency: low
Maintainer: Mathieu Malaterre ma...@debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 31 May 2012 21:50:55 +0900
Source: freewnn
Binary: freewnn-common freewnn-jserver freewnn-cserver freewnn-kserver libwnn0
libcwnn0 libkwnn0 libwnn-dev libcwnn-dev libkwnn-dev
Architecture: source all amd64
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:05:55 +0200
Source: klibc
Binary: libklibc-dev libklibc klibc-utils klibc-utils-udeb
klibc-utils-floppy-udeb libklibc-udeb
Architecture: source amd64
Version: 2.0-1
Distribution: unstable
Urgency: low
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:26:40 +0200
Source: claws-mail-extra-plugins
Binary: claws-mail-extra-plugins claws-mail-extra-plugins-dbg
claws-mail-vcalendar-plugin claws-mail-perl-filter claws-mail-feeds-reader
claws-mail-mailmbox-plugin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 30 May 2012 11:26:27 -0400
Source: facter
Binary: facter
Architecture: source all
Version: 1.6.9-2
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers
pkg-puppet-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 16:09:57 +0200
Source: gnome-games-extra-data
Binary: gnome-games-extra-data
Architecture: source all
Version: 3.2.0-3
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette j...@debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 16:37:10 +0200
Source: gnome-games-extra-data
Binary: gnome-games-extra-data
Architecture: source all
Version: 3.2.0-4
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette j...@debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:57:37 +0200
Source: initramfs-tools
Binary: initramfs-tools
Architecture: source all
Version: 0.103
Distribution: unstable
Urgency: low
Maintainer: Debian kernel team debian-ker...@lists.debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:42:03 +0200
Source: klibc
Binary: libklibc-dev libklibc klibc-utils klibc-utils-udeb
klibc-utils-floppy-udeb libklibc-udeb
Architecture: source amd64
Version: 2.0-2
Distribution: unstable
Urgency: low
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:45:25 +0200
Source: oath-toolkit
Binary: liboath-dev liboath0 oathtool oath-dbg libpam-oath
Architecture: source amd64
Version: 1.12.3-1
Distribution: unstable
Urgency: low
Maintainer: OATH Toolkit Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:24:07 +0200
Source: poppler
Binary: libpoppler19 libpoppler-dev libpoppler-private-dev libpoppler-glib8
libpoppler-glib-dev gir1.2-poppler-0.18 libpoppler-qt4-3 libpoppler-qt4-dev
libpoppler-cpp0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 31 May 2012 11:46:10 +0200
Source: python-crypto
Binary: python-crypto python-crypto-dbg python3-crypto python3-crypto-dbg
python-crypto-doc
Architecture: source amd64 all
Version: 2.6-2
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 28 May 2012 13:44:30 +
Source: xorp
Binary: xorp
Architecture: source amd64
Version: 1.8.5-1.1
Distribution: unstable
Urgency: low
Maintainer: Jose Calhariz jose.calha...@tagus.ist.utl.pt
Changed-By: Matthias Klose
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 31 May 2012 17:50:56 +0200
Source: devscripts
Binary: devscripts
Architecture: source amd64
Version: 2.11.8
Distribution: unstable
Urgency: low
Maintainer: Devscripts Devel Team devscripts-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 31 May 2012 15:41:34 +0200
Source: dicomscope
Binary: dicomscope
Architecture: source amd64
Version: 3.6.0-9
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team
debian-med-packag...@lists.alioth.debian.org
1 - 100 of 153 matches
Mail list logo
