Hello,
On Thu, 17 May 2012 16:52:02 +0200
Gergely Nagy alger...@balabit.hu wrote:
Git does have a complete view. What the above does, is tell
dpkg-source to fold any changes made to the upstream sources into a
single patch. Since the git tree already has the patches applied
(with upstream
On 05/17/2012 04:52 PM, Gergely Nagy wrote:
Chris Knadle chris.kna...@coredump.us writes:
On Wednesday, May 16, 2012 06:38:49, Adam Borowski wrote:
On Tue, May 15, 2012 at 10:10:28AM +0100, Jon Dowland wrote:
On Tue, May 15, 2012 at 03:17:17PM +0900, Norbert Preining wrote:
No, I hereby
Hi there!
On Tue, 15 May 2012 01:10:19 +0200, Norbert Preining wrote:
On Mo, 14 Mai 2012, Clint Adams wrote:
dpkg-source is more intolerant of fuzz than quilt itself.
Run quilt refresh on the patch and it should be happier.
Ar ... is this on purpose? Or by chance? Or to drive
18.05.2012 00:11, Russ Allbery пишет:
Tollef Fog Heen tfh...@err.no writes:
]] Russ Allbery
If I were to pick between the enhancements to Debian in this area, none
of which I have time to work on and therefore can't vote on via
implementation, I'd be way more interested in avoiding the
Hi,
Our bug tracker contains items for packages, which do (not longer) exist. What
should happen to them? I see, that it might be a good idea to keep them for the
case, a package is re-introduced. But this might happen only for a few
packages. Most of them got removed because newer versions
On Fri, May 18, 2012 at 4:45 PM, Daniel Leidert wrote:
Our bug tracker contains items for packages, which do (not longer) exist.
What should happen to them? I see, that it might be a good idea to keep them
for the case, a package is re-introduced. But this might happen only for a
few
On Thu, May 17, 2012 at 06:23:49PM -0400, Chris Knadle wrote:
Another thing I've seen with another package I'm working on in collaboration
is using a Git repo in which the only contents are the debian/ files and not
the original source tarball nor source files at all. To do a built the
On Fri, 18 May 2012 16:50:12 +0800
Paul Wise p...@debian.org wrote:
On Fri, May 18, 2012 at 4:45 PM, Daniel Leidert wrote:
Our bug tracker contains items for packages, which do (not longer) exist.
What should happen to them? I see, that it might be a good idea to keep
them for the
Daniel Leidert daniel.leidert.s...@gmx.net (18/05/2012):
Our bug tracker contains items for packages, which do (not longer)
exist. What should happen to them? I see, that it might be a good idea
to keep them for the case, a package is re-introduced. But this might
happen only for a few
On Fri, May 18, 2012 at 09:24:04AM +0200, Bernd Zeimetz wrote:
On 05/17/2012 04:52 PM, Gergely Nagy wrote:
I'm confused concerning the above; the point of a VCS in this context is
to
track changes to the source package, and the patches are themselves
important
changes to the source
]] Igor Pashev
What about stable release? Git branches?
Sure. Branches are cheap.
What about users who want rebuild a package (probably with new patches)?
They'll then just grab the git tree, apply their patches, build their
package.
--
Tollef Fog Heen
UNIX is user friendly, it's just
Hello,
On Fri, 18 May 2012 11:37:08 +0200
Adam Borowski kilob...@angband.pl wrote:
Quilt is a kind of really primitive VCS. It does not make sense to
use both it and a modern one, and when someone tries, this ends up
with no end of woe. Quilt sprinkles its modifications around the
source,
Excerpts from David Kalnischkies's message of Thu May 17 18:21:59 +0200 2012:
On Thu, May 17, 2012 at 3:16 PM, Michal Suchanek
michal.sucha...@ruk.cuni.cz wrote:
Excerpts from Ian Jackson's message of Thu May 17 14:53:30 +0200 2012:
Michal Suchanek writes (Re: Bug#671503: general: APT
Michal Suchanek michal.sucha...@ruk.cuni.cz writes:
Excerpts from Ian Jackson's message of Thu May 17 14:53:30 +0200 2012:
Michal Suchanek writes (Re: Bug#671503: general: APT repository format is
not documented):
Excerpts from Filipus Klutiero's message of Wed May 16 18:44:21 +0200 2012:
Daniel Leidert daniel.leidert.s...@gmx.net writes:
Hi,
Our bug tracker contains items for packages, which do (not longer)
exist. What should happen to them? I see, that it might be a good idea
to keep them for the case, a package is re-introduced. But this might
happen only for a few
CC'ing the apt list de...@lists.debian.org.
Goswin von Brederlow writes (Re: Bug#481129: Bug#671503: general: APT
repository format is not documented):
Michal Suchanek michal.sucha...@ruk.cuni.cz writes:
[ discussions regarding documenting the apt repository format ]
I would suggest you
Jon Dowland j...@debian.org writes:
On Wed, May 16, 2012 at 12:38:49PM +0200, Adam Borowski wrote:
It is true that 3.0 (quilt) does have a great downside, quilt, but it also
has a number of upsides. And working around quilt is simple:
echo single-debian-patch debian/source/options
echo
On Wed, May 16, 2012 at 07:45:24PM -0700, Russ Allbery wrote:
Charles Plessy ple...@debian.org writes:
Also, it is very sad that, as a project, we can not decide whether we go
for 3.0 (git) or not, or have a concrete list of resolvable objections
from the people whose work is direclty
Chris Knadle chris.kna...@coredump.us writes:
On Wednesday, May 16, 2012 06:38:49, Adam Borowski wrote:
On Tue, May 15, 2012 at 10:10:28AM +0100, Jon Dowland wrote:
On Tue, May 15, 2012 at 03:17:17PM +0900, Norbert Preining wrote:
No, I hereby start saying good by to 3.0
I'm hoping we
On Fri, May 18, 2012 at 12:02:47PM +0100, Ian Jackson wrote:
CC'ing the apt list de...@lists.debian.org.
Goswin von Brederlow writes (Re: Bug#481129: Bug#671503: general: APT
repository format is not documented):
Michal Suchanek michal.sucha...@ruk.cuni.cz writes:
[ discussions
On Fri, May 18, 2012 at 12:16:40PM +0200, Andrew Shadura wrote:
On Fri, 18 May 2012 11:37:08 +0200
Adam Borowski kilob...@angband.pl wrote:
Quilt is a kind of really primitive VCS. It does not make sense to
use both it and a modern one, and when someone tries,
I'm sorry to disappoint
debian-de...@liska.ath.cx (Olе Streicher) writes:
James McCoy vega.ja...@gmail.com writes:
On Wed, May 16, 2012 at 04:23:05PM +0200, Olе Streicher wrote:
Unpatching the sources *before* the build process was cleaned up makes
no sense to me at all. Could you provide a use case for that?
As
Roger Leigh rle...@codelibre.net writes:
On Wed, May 16, 2012 at 02:38:14PM +0200, Goswin von Brederlow wrote:
That just leaves the question of wether dpkg uses uid/gid or symbolic
names when unpacking debs.
I think this one is clear: it must be symbolic since the uids/gids
aren't static.
Daniel Leidert daniel.leidert.s...@gmx.net writes:
Hi,
Our bug tracker contains items for packages, which do (not longer) exist.
What should happen to them? I see, that it might be a good idea to keep them
for the case, a package is re-introduced. But this might happen only for a
few
+++ Mehdi Dogguy [2012-05-16 16:24 +0200]:
On 16/05/12 13:41, Wookey wrote:
is there any reason not to just upload this to Debian?
There are ITPs filed for it:
- http://bugs.debian.org/582884
- http://bugs.debian.org/576359
Yes. I discovered that when I went to file an ITP :-)
It turns
Hi,
Le 18/05/12 13:46, Goswin von Brederlow a écrit :
This works only for the special case that build does not change any
source file. Otherwise you would also commit the changed source files.
And it better not. There is no excuse for changing source files during
build. If you need to
On Fri, May 18, 2012 at 01:38:40PM +0200, Julian Andres Klode wrote:
On Fri, May 18, 2012 at 12:02:47PM +0100, Ian Jackson wrote:
CC'ing the apt list de...@lists.debian.org.
Goswin von Brederlow writes (Re: Bug#481129: Bug#671503: general: APT
repository format is not documented):
On Fri, May 18, 2012 at 01:27:50PM +0200, Adam Borowski wrote:
On Wed, May 16, 2012 at 07:45:24PM -0700, Russ Allbery wrote:
Charles Plessy ple...@debian.org writes:
Also, it is very sad that, as a project, we can not decide whether we go
for 3.0 (git) or not, or have a concrete list
Goswin von Brederlow goswin-...@web.de writes:
debian-de...@liska.ath.cx (Olе Streicher) writes:
James McCoy vega.ja...@gmail.com writes:
On Wed, May 16, 2012 at 04:23:05PM +0200, Olе Streicher wrote:
Unpatching the sources *before* the build process was cleaned up makes
no sense to me at
On Fri, May 18, 2012 at 01:38:40PM +0200, Julian Andres Klode wrote:
I do not think that APT is responsible for the repository format. The
repository format is defined by ftpmaster, not by APT. APT has to my
knowledge not defined anything new, but only implemented changes to
the repository
Hi,
2012/5/18 Daniel Leidert daniel.leidert.s...@gmx.net:
Hi,
Our bug tracker contains items for packages, which do (not longer) exist.
What should happen to them? I see, that it might be a good idea to keep them
for the case, a package is re-introduced. But this might happen only for a
On Thu, 17 May 2012, Thomas Goirand wrote:
On 05/03/2012 07:23 AM, Henrique de Moraes Holschuh wrote:
Well, FWIW postfix allows you to override all MTA notifications, not just
bounce messages, but the full set. We do that at work.
Interesting. Can you post an example here?
man
On Fri, 18 May 2012, Adam Borowski wrote:
On Fri, May 18, 2012 at 12:16:40PM +0200, Andrew Shadura wrote:
On Fri, 18 May 2012 11:37:08 +0200
Adam Borowski kilob...@angband.pl wrote:
Quilt is a kind of really primitive VCS. It does not make sense to
use both it and a modern one, and
FWIW
posted on the wiki: http://wiki.debian.org/RepositoryFormat
Thanks
Michal
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
* Adam Borowski kilob...@angband.pl [120518 11:37]:
You complain about forcing people to use git, while you push quilt onto
everyone else.
[...]
I really wish there was a 3.0 format besides 3.0 (quilt), so people are
not mislead into thinking they have to (or even, would gain anything) from
On Fri, 18 May 2012 14:34:40 +0100
Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote:
Hi,
2012/5/18 Daniel Leidert daniel.leidert.s...@gmx.net:
Hi,
Our bug tracker contains items for packages, which do (not longer) exist.
What should happen to them? I see, that it might
2012/5/18 Neil Williams codeh...@debian.org:
There's a big difference between these bugs and the rest - here there
are clear migration paths to later packages which can be used to triage
the bug reports in order not to lose reports. A lot of the rest *can*
be closed without more triage work
Le vendredi 18 mai 2012 17:41:55, Manuel A. Fernandez Montecelo a écrit :
2012/5/18 Neil Williams codeh...@debian.org:
There's a big difference between these bugs and the rest - here there
are clear migration paths to later packages which can be used to triage
the bug reports in order not
2012/5/18 Thomas Preud'homme robo...@celest.fr:
According to [1] salome is not part of any debian release now. Did I miss
something? IIRW, for package still in stable, if the -done mail contains the
right version then the bug will still be visible as long as it affects stable.
Oh yes,
On Fri, 18 May 2012 16:41:55 +0100
Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote:
Another question, perhaps unrelated is, what happens with the bugs
closed from egroupware or salome (removed from unstable/testing but
still present in stable releases) when their users look for
Guillem Jover wrote:
Only as long as the debian/control information matches the one from
the archive override.
I checked, and currently the only base package with an overridden priority
is libsigc++-2.0-0c2a
--
see shy jo
signature.asc
Description: Digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/18/2012 11:37 AM, Adam Borowski wrote:
On Fri, May 18, 2012 at 09:24:04AM +0200, Bernd Zeimetz wrote:
On 05/17/2012 04:52 PM, Gergely Nagy wrote:
I'm confused concerning the above; the point of a VCS in this context
is to track changes to
On Fri, May 18, 2012 at 04:06:23PM +0200, Michal Suchanek wrote:
FWIW
posted on the wiki: http://wiki.debian.org/RepositoryFormat
Thanks
Michal
I have now documented the Contents indices and the diffs
as well, mostly (sans the exact format we use for the
patches), and Translation
While this has been an interesting thread, it may be predicated on a
false premise. I examined the latest weekly CD build, and the reason no
desktop tasks at all (even lxde or xfce) appear on their respective CDs
is because debian-cd is simply not including tasksel's new task-*
packages, at all.
On Fri, May 18, 2012 at 04:06:23PM +0200, Michal Suchanek wrote:
FWIW
posted on the wiki: http://wiki.debian.org/RepositoryFormat
What's the opinion about the flat repository format, where you
just have one directory with Release, Packages, Sources, and
friends and no sub-directories?
Should
On Fri, May 18, 2012 at 06:45:00PM +0100, Wookey wrote:
+++ Julian Andres Klode [2012-05-18 13:38 +0200]:
We currently have three independent implementations of the repository
format in the archive: APT, cupt, smartpm.
I think reprepro is another?
Of course, I was just only talking
+++ Julian Andres Klode [2012-05-18 13:38 +0200]:
We currently have three independent implementations of the repository
format in the archive: APT, cupt, smartpm.
I think reprepro is another?
/usr/share/doc/reprepro/manual.html contains a 'repository basics'
section which includes useful
On Fri, May 18, 2012 at 08:12:16PM +0200, Michal Suchanek wrote:
The formatting is not consistent but that will have to be changed for
docbook anyway.
Yes, and it will also be more readable then, than the current wiki
version.
Also would need some proof-reading. If nothing else somebody
Excerpts from Julian Andres Klode's message of Fri May 18 18:49:10 +0200 2012:
On Fri, May 18, 2012 at 04:06:23PM +0200, Michal Suchanek wrote:
FWIW
posted on the wiki: http://wiki.debian.org/RepositoryFormat
Thanks
Michal
I have now documented the Contents indices and the
Hi!
On 18.05.2012 10:50, Paul Wise wrote:
Our bug tracker contains items for packages, which do (not longer) exist. What
should happen to them? I see, that it might be a good idea to keep them for the
case, a package is re-introduced. But this might happen only for a few
packages. Most of
Henrique de Moraes Holschuh h...@debian.org writes:
When it is time to release/upload, the branch gets git format-patch'd,
and makes its way to debian/patches for 3.0(quilt) to handle. That
branch is never published. git-pq can automate this stuff in an even
better way that is rebase-less
On Fri, May 18, 2012 at 12:27:15PM -0400, Joey Hess wrote:
Guillem Jover wrote:
Only as long as the debian/control information matches the one from
the archive override.
I checked, and currently the only base package with an overridden priority
is libsigc++-2.0-0c2a
So, would it be safe
On Sat, May 19, 2012 at 12:58 AM, Julian Andres Klode wrote:
What's the opinion about the flat repository format, where you
just have one directory with Release, Packages, Sources, and
friends and no sub-directories?
Should they be documented as well then? We would then have two
kind of
Hi Peter,
Thanks for bringing up this issue again. Admittedly, there hasn't been much
progress since it was discussed last year.
Hopefully, the discussion has focused on a solution to completely avoid the
problem during upgrades.
For the general issue, the only progress I made was in the form
Le Wed, May 16, 2012 at 07:45:24PM -0700, Russ Allbery a écrit :
Charles Plessy ple...@debian.org writes:
Also, it is very sad that, as a project, we can not decide whether we go
for 3.0 (git) or not, or have a concrete list of resolvable objections
from the people whose work is direclty
Le Sat, May 19, 2012 at 11:56:07AM +0900, Charles Plessy a écrit :
In the case of the initial copryight review, which is if I understand well the
strongest objection, wouldn't it be solved if the first upload to Debian would
contain as few history as possible ? Then the quantity of history
Le Fri, May 18, 2012 at 06:49:10PM +0200, Julian Andres Klode a écrit :
In a few months, I'd like to rework this in DocBook form, and submit it to
debian-policy for inclusion into official Policy, as a sub-policy like
copyright-format.
Dear Julian and everybody,
thank you for this
]] Roger Leigh
I think this is a key point. The aim of the git format should not be
provide the entire history, any more than the other formats do (not).
What should be provided needs to be
- sufficient to build the package
- sufficient to determine the changes made between the Upstream
Hi, List,
One of my packages [1] failed to build on armel, kfreebsd and hurd,
But I don't have such a machine to test my packages. Is it possible
to use debian porterbox to build the package and dig into this
problem ?
[1] https://buildd.debian.org/status/package.php?p=spice-vdagent
Thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 07:50:12 +0200
Source: btrfs-tools
Binary: btrfs-tools btrfs-tools-udeb btrfs-tools-dbg
Architecture: source i386
Version: 0.19+20120328-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 08:00:01 +0200
Source: dmidecode
Binary: dmidecode dmidecode-udeb
Architecture: source i386
Version: 2.11-7
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 08:25:16 +0200
Source: fuse
Binary: fuse fuse-dbg fuse-utils libfuse2 libfuse-dev fuse-udeb libfuse2-udeb
Architecture: source i386 all
Version: 2.9.0-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 May 2012 08:44:53 +0200
Source: libvalidation-class-perl
Binary: libvalidation-class-perl
Architecture: source all
Version: 7.21-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 08:45:24 +0200
Source: ntfs-3g
Binary: ntfs-3g ntfs-3g-dbg ntfs-3g-dev ntfs-3g-udeb ntfsprogs
Architecture: source i386 all
Version: 1:2012.1.15AR.5-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 16 May 2012 17:35:25 +0200
Source: eegdev
Binary: libeegdev0 eegdev-plugins-free libeegdev-dev libeegdev0-dbg
Architecture: source amd64
Version: 0.2-1
Distribution: unstable
Urgency: low
Maintainer: Nicolas Bourdaud
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 09:11:09 +0200
Source: syslinux
Binary: syslinux syslinux-udeb extlinux syslinux-common
Architecture: source i386 all
Version: 2:4.05+dfsg-4
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 00:23:21 +0200
Source: haskell-hakyll
Binary: libghc-hakyll-dev libghc-hakyll-prof libghc-hakyll-doc
Architecture: source all amd64
Version: 3.2.7.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Haskell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 09:38:01 +0200
Source: dictionaries-common
Binary: dictionaries-common dictionaries-common-dev
Architecture: source all
Version: 1.12.7
Distribution: unstable
Urgency: low
Maintainer: Agustin Martin Domingo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 12 May 2012 03:59:00 +0200
Source: freefem++
Binary: freefem++ libfreefem++ libfreefem++-dev freefem++-doc
Architecture: source amd64 all
Version: 3.19-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 15:59:58 +0800
Source: lcrt
Binary: lcrt
Architecture: source i386
Version: 1.1.2-1
Distribution: unstable
Urgency: low
Maintainer: Asias He asias.he...@gmail.com
Changed-By: Asias He asias.he...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 09:24:01 +0200
Source: llvm-2.9
Binary: libllvm2.9 llvm-2.9 llvm-2.9-runtime llvm-2.9-dev libllvm-2.9-ocaml-dev
llvm-2.9-doc llvm-2.9-examples llvm-2.9-source
Architecture: source i386 all
Version: 2.9+dfsg-6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 10:06:49 +0200
Source: lxde-common
Binary: lxde-common
Architecture: source all
Version: 0.5.5-5
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org
Changed-By: Daniel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 10:08:16 +0200
Source: lxde-metapackages
Binary: lxde-core lxde
Architecture: source all
Version: 2
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 09:48:38 +0200
Source: lxpolkit
Binary: lxpolkit lxpolkit-dbg
Architecture: source i386
Version: 0.1.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 09:39:29 +0200
Source: odin
Binary: odin mitools libodin-dev
Architecture: source amd64
Version: 1.8.5-2
Distribution: unstable
Urgency: low
Maintainer: NeuroDebian Team t...@neuro.debian.net
Changed-By: Michael
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 17 May 2012 18:15:46 +0200
Source: tig
Binary: tig
Architecture: source amd64
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Sebastian Harl tok...@debian.org
Changed-By: Sebastian Harl tok...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 15 May 2012 18:06:16 +0200
Source: atlas
Binary: libatlas3-base libatlas3gf-base libatlas-base-dev libatlas-dev
libatlas-test libatlas-doc
Architecture: source all i386
Version: 3.8.4-4~exp5
Distribution: experimental
Urgency:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 15 May 2012 16:09:04 +0800
Source: fcitx-hangul
Binary: fcitx-hangul
Architecture: source amd64
Version: 0.1.1-1
Distribution: unstable
Urgency: low
Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 01:13:50 +0200
Source: pmw
Binary: pmw pmw-doc
Architecture: source s390 all
Version: 1:4.24-1
Distribution: unstable
Urgency: low
Maintainer: Wouter Verhelst wou...@debian.org
Changed-By: Wouter Verhelst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 May 2012 12:23:25 +0200
Source: lsyncd
Binary: lsyncd
Architecture: source amd64
Version: 2.0.7-2
Distribution: unstable
Urgency: low
Maintainer: Jan Dittberner ja...@debian.org
Changed-By: Jan Dittberner ja...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 18 May 2012 12:15:21 +0200
Source: qjackctl
Binary: qjackctl
Architecture: source amd64
Version: 0.3.8-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 11:39:03 +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 amd64
Version: 1:6.14.4-3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 18 May 2012 11:47:25 +0200
Source: gdb-doc
Binary: gdb-doc
Architecture: source all
Version: 7.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Hector Oron zu...@debian.org
Changed-By: Hector Oron zu...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 12:36:27 +0200
Source: dmidecode
Binary: dmidecode dmidecode-udeb
Architecture: source i386
Version: 2.11-8
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 12:06:45 +0300
Source: pygpiv
Binary: python-gpiv
Architecture: source amd64
Version: 2.0.0-4.1
Distribution: unstable
Urgency: low
Maintainer: Gerber van der Graaf gerber_gr...@users.sourceforge.net
Changed-By: Jari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 10:59:21 +0530
Source: recoll
Binary: recoll python-recoll
Architecture: source amd64
Version: 1.17.2-1
Distribution: unstable
Urgency: low
Maintainer: Kartik Mistry kar...@debian.org
Changed-By: Kartik Mistry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 May 2012 19:44:00 +0900
Source: ruby-gir-ffi
Binary: ruby-gir-ffi
Architecture: source all
Version: 0.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 12:53:18 +0200
Source: traceroute
Binary: traceroute
Architecture: source i386
Version: 1:2.0.18-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 18 May 2012 13:11:45 +0200
Source: audacious
Binary: audacious audacious-dbg audacious-dev libaudclient2 libaudcore1
Architecture: source amd64
Version: 3.2.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 13:17:14 +0200
Source: aufs-tools
Binary: aufs-tools aufs-tools-dbg
Architecture: source i386
Version: 1:3.0+20120411-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 May 2012 20:14:29 +0900
Source: yash
Binary: yash
Architecture: source amd64
Version: 2.30-2
Distribution: unstable
Urgency: low
Maintainer: TANIGUCHI Takaki tak...@debian.org
Changed-By: TANIGUCHI Takaki tak...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 09:32:13 +0200
Source: db-defaults
Binary: libdb-dev db-util db-upgrade-util libdb++-dev libdb-sql-dev
libdb-java-dev libdb-java
Architecture: source amd64 all
Version: 5.1.6
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 11:26:16 +0200
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi1.3 openmpi-common openmpi-doc
libopenmpi-dbg openmpi-checkpoint
Architecture: source i386 all
Version: 1.4.5-1
Distribution: unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 13:32:14 +0200
Source: ecryptfs-utils
Binary: ecryptfs-utils ecryptfs-utils-dbg libecryptfs0 libecryptfs-dev
python-ecryptfs
Architecture: source i386
Version: 96-1
Distribution: unstable
Urgency: low
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 13:35:38 +0200
Source: caret
Binary: caret
Architecture: source amd64
Version: 5.6.4~dfsg.1-3
Distribution: unstable
Urgency: low
Maintainer: NeuroDebian Team t...@neuro.debian.net
Changed-By: Michael Hanke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 May 2012 13:29:53 +0100
Source: dnprogs
Binary: dnet-common dnet-progs libdnet libdnet-dev
Architecture: source amd64
Version: 2.59+nmu1
Distribution: unstable
Urgency: low
Maintainer: Christine Caulfield
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 May 2012 14:19:00 +0200
Source: efilinux
Binary: efilinux
Architecture: source i386
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 18 May 2012 13:28:08 +0100
Source: ekeyd
Binary: ekeyd ekeyd-egd-linux
Architecture: source amd64
Version: 1.1.5-4
Distribution: unstable
Urgency: low
Maintainer: Simtec Electronics supp...@simtec.co.uk
Changed-By: Paul Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 13 May 2012 14:25:21 +0200
Source: cbmc
Binary: cbmc
Architecture: source amd64
Version: 4.1-1.1
Distribution: unstable
Urgency: low
Maintainer: Michael Tautschnig m...@debian.org
Changed-By: Salvatore Bonaccorso
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 16 May 2012 19:36:38 +0200
Source: drawtk
Binary: libdrawtk0 libdrawtk0-dbg libdrawtk-dev
Architecture: source amd64
Version: 2.0-1
Distribution: unstable
Urgency: low
Maintainer: Nicolas Bourdaud nicolas.bourd...@gmail.com
1 - 100 of 191 matches
Mail list logo
