On Sat, Aug 16, 2014 at 02:03:18PM +0200, Raphael Hertzog wrote:
The vast majority (all?) of git packaging repositories have the upstream
sources.
I think this point is not really contentious.
Others have demonstrated that this is not the case. However, I believe the
majority of git
On 08/16/2014 11:44 PM, wm4 wrote:
This reasoning may work when you have only a small amount of information
to read. When you are overwhelmed with it, having different places to do
different things is a much better approach. Sending patches to a list
simply doesn't scale.
Also, with a list,
On 08/16/2014 11:11 PM, Nicolas George wrote:
L'octidi 28 thermidor, an CCXXII, Bálint Réczey a écrit :
Using Gerrit and file ownersip are not mutually exclusive. Gerrit
can be configured to automatically invite the right people for review
based on the changed path. We recently migrated to
On 08/16/2014 11:30 PM, Nicolas George wrote:
So what about the code? Shall the FFmpeg developers discard three years of
work and start working on libav? Or shall the libav developers accept to
work with the code from FFmpeg that they do not like?
FFmpeg folks should rework the code to make it
Hi DD folks!
recently a bug has been opened against a package I maintain (debian science is
the maintainer, while I'm the only uploader), but I did not notice with a mail,
because:
A) I forgot to subscribe to debian-science archives
B) Even if subscribed I don't think I would have seen it,
On 08/17/2014 07:41 PM, Andreas Cadhalpun wrote:
Michael Niedermayer already volunteered to help with all security
related problems of FFmpeg in Debian.
So what should he do to relieve the impact on the security and release
teams?
Let's say he would take the role of patching stuff in Stable,
Hi Russ,
On Sun, Aug 17, 2014 at 10:31:26AM -0700, Russ Allbery wrote:
Thomas Goirand z...@debian.org writes:
As Charles wrote, pristine-tar works with small tarballs, but when
upstream has multi-megabytes tarballs and releases often, the Git
repository quickly grows to something not
❦ 18 août 2014 14:20 +0800, Thomas Goirand z...@debian.org :
What? Most patches are posted inline (with git-send-email).
Even worse then! It makes it hard to copy to your local fs.
The whole email is a valid patch in this case.
--
Follow each decision as closely as possible with its
On 08/18/2014 07:47 AM, Henrique de Moraes Holschuh wrote:
On Sun, 17 Aug 2014, Thomas Goirand wrote:
On 08/17/2014 03:52 AM, Raphael Hertzog wrote:
On Fri, 15 Aug 2014, Henrique de Moraes Holschuh wrote:
- the above layout is for the traditional case of non-native packages,
what would be
On 08/18/2014 01:49 AM, Russ Allbery wrote:
Joey took various approaches to work around this, including shipping some
of the older versions of the compressors in the package. However, the
issue also applies to tar, and so far has been addressed by modifying tar
to add a backword-compatibility
On 08/18/2014 03:08 PM, Thomas Goirand wrote:
On 08/18/2014 01:49 AM, Russ Allbery wrote:
Joey took various approaches to work around this, including shipping some
of the older versions of the compressors in the package. However, the
issue also applies to tar, and so far has been addressed by
On Mon, Aug 18, 2014 at 07:28:46AM +0100, Gianfranco Costamagna wrote:
recently a bug has been opened against a package I maintain (debian
science is the maintainer, while I'm the only uploader), but I did not
notice with a mail, because:
A) I forgot to subscribe to debian-science archives
B)
Le Mon, Aug 18, 2014 at 08:53:12AM +0200, Olivier Sallou a écrit :
do you know, by chance, what is the difference between samtools and the
net.sf.samtools Java lib of picard-tools ? They look quite the same.
The HTSlib fix an issue forigv (on SAMFileWriterFactory), but
On Sat, Aug 16, 2014 at 09:51:21PM +0200, Bastien ROUCARIES wrote:
On Sat, Aug 16, 2014 at 1:59 PM, Raphael Hertzog hert...@debian.org wrote:
Hi,
On Fri, 15 Aug 2014, Guido Günther wrote:
The gbp manual has a recommended branch layout:
On 2014-08-18 8:18, Adam Borowski wrote:
On Mon, Aug 18, 2014 at 07:28:46AM +0100, Gianfranco Costamagna wrote:
recently a bug has been opened against a package I maintain (debian
science is the maintainer, while I'm the only uploader), but I did not
notice with a mail, because:
A) I forgot to
You can also check this page periodically:
https://qa.debian.org/developer.php?login=costamagnagianfra...@yahoo.it
On Sun, Aug 17, 2014 at 11:28 PM, Gianfranco Costamagna
costamagnagianfra...@yahoo.it wrote:
Hi DD folks!
recently a bug has been opened against a package I maintain (debian
Package: wnpp
Severity: wishlist
Owner: Shih-Yuan Lee (FourDollars) fourdoll...@gmail.com
* Package name: ibus-zhuyin
Version : 0.1.0
Upstream Author : Shih-Yuan Lee (FourDollars) fourdoll...@gmail.com
* URL : https://github.com/fourdollars/ibus-zhuyin
* License
On Sun, Aug 17, 2014 at 01:13:36PM +0200, Marc Haber wrote:
On Sun, 17 Aug 2014 01:40:27 -0700, Josh Triplett
j...@joshtriplett.org wrote:
Ludovico Cavedon wrote:
I am writing a systemd service file for a daemon (ntopng) and I would
like to know what you think is the best way to load some
Hi,
On 18.08.2014 07:20, Dominik George wrote:
the libfreerdp1 package changed its soname without a transition and
without introducing a new package.
That broke binary compatibility of at least remmina and
libguac-client-rdp0 [0].
The bug report about this is:
https://bugs.debian.org/757926
Hi Thomas,
On 18.08.2014 08:36, Thomas Goirand wrote:
There's been a very well commented technical reason stated here: the
release team don't want to deal with 2 of the same library that are
doing (nearly) the same things, with potentially the same security
issues that we'd have to fix twice
Le primidi 1er fructidor, an CCXXII, Thomas Goirand a écrit :
The problem was enforcing patch review policies.
No, it never was.
There's been a very well commented technical reason stated here: the
release team don't want to deal with 2 of the same library that are
doing (nearly) the same
On Sat, 16 Aug 2014, Thomas Goirand wrote:
Why would you tag the upstream release? I mean, it's upstream's job to
Yeah, if upstream uses git at least it should NOT be done by
the packager.
If not, it depends.
- shall we standardize the pristine-tar branch?
As in, always use pristine-tar?
On Mon, Aug 18, 2014 at 01:19:55AM -0700, Andrew Kelley wrote:
You can also check this page periodically:
https://qa.debian.org/developer.php?login=costamagnagianfra...@yahoo.it
Alternatively
https://udd.debian.org/dmd/
Kind regards
Andreas.
--
http://fam-tille.de
--
To
On Fri, 15 Aug 2014, Russ Allbery wrote:
m...@linux.it (Marco d'Itri) writes:
The first step is to determine which problem you are trying to solve.
Surprisingly insightful, this one.
I want to be able to check out a git repository and do packaging work and
an upload, without having to
Andreas Cadhalpun andreas.cadhal...@googlemail.com schrieb:
Hi Thomas,
On 18.08.2014 08:36, Thomas Goirand wrote:
There's been a very well commented technical reason stated here: the
release team don't want to deal with 2 of the same library that are
doing (nearly) the same things, with
On Sun, 17 Aug 2014, Thomas Goirand wrote:
Like I wrote in another post, master doesn't express anything.
ACK.
All of this is error prone. Using upstream tags and merging them rather
than branches avoid troubles. I have yet to see a case where using
upstream tags wasn't practical.
There
On Sun, 17 Aug 2014, Neil Williams wrote:
The vast majority (all?) of git packaging repositories have the
upstream sources.
No. None of mine do, or will.
I’m working with some which also don’t, and find it would be easier
if there were a way to extract a .orig.tar.gz in the same way that
* Charles Plessy ple...@debian.org, 2014-08-17, 19:39:
for suites that are never released, I think that it is fine to not use
the codename. Otherwise, people will be confused with debian/rc-buggy.
FWIW, rc-buggy is not the codename for experimental:
$ wget -q -O-
Hi *,
Il Lunedì 18 Agosto 2014 10:20, Andrew Kelley superjo...@gmail.com ha scritto:
thanks to all for the useful replies!
So I will subscribe through the PTS interface, it is the best solution (I was
already wondering that) ;)
You can also check this page periodically:
On Sun, 17 Aug 2014, Jonathan Dowland wrote:
On Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog wrote:
- version encoding (due to git restrictions):
: - %
~ - _
I’d rather have something that sorts like Debian versions
in “git tag” output…
_ - _5f
: - _3a
~
On Sat, Aug 16, 2014 at 01:59:46PM +0200, Raphael Hertzog wrote:
Hi,
On Fri, 15 Aug 2014, Guido Günther wrote:
The gbp manual has a recommended branch layout:
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.BRANCH.NAMING
which could serve as a
Hi Moritz,
On 18.08.2014 14:05, Moritz Mühlenhoff wrote:
Andreas Cadhalpun andreas.cadhal...@googlemail.com schrieb:
On 18.08.2014 08:36, Thomas Goirand wrote:
There's been a very well commented technical reason stated here: the
release team don't want to deal with 2 of the same library that
On Mon, 18 Aug 2014, Thorsten Glaser wrote:
This does not work in Debian: you always need the .orig.tar.* file,
at least for the upload, for non-native packages.
You need it from somewhere, but the whole point of pristine-tar is that
you can generate the orig.tar.* from information in the git
On 08/18/2014 01:36 AM, Russ Allbery wrote:
The upstream source *can* be changed and improved for everyone.
Truth, but not always practical. If I was going to fix all the defects
of software I package, I don't think I'd have enough time to sleep even
one hour per night.
Thomas Goirand (zigo)
Greetings,
If we have a package, which doesn't migrate to testing, we usually
check the Why does package X not in testing yet? page or the PTS.
Usually they do a great job in telling us why our package doesn't
migrate.
But sometimes you have packages, which have complicated dependencies,
that
Thomas Goirand z...@debian.org writes:
On 08/18/2014 01:49 AM, Russ Allbery wrote:
Joey took various approaches to work around this, including shipping
some of the older versions of the compressors in the package. However,
the issue also applies to tar, and so far has been addressed by
On Mon, Aug 18, 2014 at 02:27:15PM +0200, Thorsten Glaser wrote:
I’d rather have something that sorts like Debian versions
in “git tag” output…
If that proves too hard to achieve with a mapping scheme, it would
be trivial to write a filter to implement it. It does sound useful.
Yikes!
Thomas Goirand z...@debian.org writes:
On 08/18/2014 01:36 AM, Russ Allbery wrote:
The upstream source *can* be changed and improved for everyone.
Truth, but not always practical. If I was going to fix all the defects
of software I package, I don't think I'd have enough time to sleep even
2014-08-18 14:27:15 Thorsten Glaser:
On Sun, 17 Aug 2014, Jonathan Dowland wrote:
On Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog wrote:
- version encoding (due to git restrictions):
: - %
~ - _
I’d rather have something that sorts like Debian versions
in “git
On Mon, 18 Aug 2014, Don Armstrong wrote:
On Mon, 18 Aug 2014, Thorsten Glaser wrote:
This does not work in Debian: you always need the .orig.tar.* file,
at least for the upload, for non-native packages.
You need it from somewhere, but the whole point of pristine-tar is that
you can
On Sun, 17 Aug 2014, Thomas Goirand wrote:
Obviously, when upstream are already doing everything correctly, creating
the upstream/version tag should not become some administrative chore but
it could be done automatically as part of a some gbp upstream-merge
upstream-tag command for
Hi,
I do think that this is quite common, and my preferred way of doing
things. It is easy for newcomers to handle, easy for me to handle, no
need to learn a lot of git specific tools or helpers, you can mostly
ignore git if you want to.
I've a couple of times tried to get myself to
Russ Allbery wrote:
No, I'm pretty sure that currently works. But I don't know how much that
relies on modifications to Debian's tar package.
It doesn't matter what tar was used to create the original tarball; as
long as we know the files present in it, we can use a (necessarily
stable version
On Sun, 17 Aug 2014, Marc Haber wrote:
Please. The attitute of requiring Debian maintainers to modify
upstream software instead of having simple two-line extension to an
init script is really unfriendly. Why do only systemd friends keep
recommending this?
Using my sysvinit hat, I've always
On Mon, Aug 18, 2014 at 09:31:37AM -0700, Russ Allbery wrote:
More generally (and this part is not pointed at Thomas), I realize it's
become de rigueur in any thread about systemd to reply to hm, you could
consider getting a dog with WHY DO YOU WANT TO KILL MY KITTENS?!?!?,
but seriously
On Sun, 2014-08-17 at 09:00 +0200, Raphael Hertzog wrote:
On Sun, 17 Aug 2014, Thomas Goirand wrote:
Well, I have nothing against derivative/downstream distros, but if
you're about to do a new DEP, please consider Debian first. In such
case, debian/unstable makes a lot more sense than just
On Mon, 18 Aug 2014 09:31:37 -0700, Russ Allbery r...@debian.org
wrote:
could we tone down the assumption that people with
differing preferences want to break everything you do? It's just a few
additional options.
And others removed. Or do you actually claims that the systemd
migration didn't
On 2014-08-16 16:28:40 +0800 (+0800), Thomas Goirand wrote:
[...]
If I prefer to use their git repository, and create my
own orig.tar.xz out of a signed git tag, what is the problem, as
long as I use the tag they provided by upstream?
[...]
Mainly that the checksums for your orig.tar.{g,x}z
On 2014-08-17 16:20:34 +0800 (+0800), Thomas Goirand wrote:
But then in which way will you check that the said upstream tarball,
without any upstream checksum, is valid? At least tags are
signed...
You keep coming back to the assumption that upstreams don't provide
signed lists of checksums. I
Marc Haber mh+debian-de...@zugschlus.de (2014-08-18):
And others removed. Or do you actually claims that the systemd
migration didn't actually break things? Not all of them, but a
noticeable number.
(I don't think Russ claimed anything along those lines, no.)
Anyway: things get broken, bugs
From: Sven Bartscher sven.bartsc...@weltraumschlangen.de
Hi again Sven,
Greetings,
If we have a package, which doesn't migrate to testing, we usually
check the Why does package X not in testing yet? page or the PTS.
Usually they do a great job in telling us why our package doesn't
Le Mon, Aug 18, 2014 at 02:16:55PM +0200, Jakub Wilk a écrit :
FWIW, rc-buggy is not the codename for experimental:
$ wget -q -O- http://http.debian.net/debian/dists/experimental/Release | grep
-m1 ^Codename:
Codename: experimental
Excellent news !
So seems that I have been confused by
Le Thu, Aug 14, 2014 at 09:36:50PM +0900, Charles Plessy a écrit :
Package: debian-policy
Version: 3.9.5
Severity: wishlist
Hi Guillem and everybody,
thanks for adding direct support for the Testsuite field in Dpkg.
Here is a patch to update the Policy accordingly. Do you have
On Aug 17, 2014, at 11:19 AM, Thomas Goirand wrote:
By the way, I try to always avoid using master as a branch name. This
doesn't express anything at all.
+1
In the context of Ubuntu (and when it works wink) I really like the approach
taken for UDD branches. I can always branch the version of
On Aug 16, 2014, at 01:15 AM, Thomas Goirand wrote:
As in, always use pristine-tar? No! The point of using git packaging is
also to be able to use upstream git repo.
What about cases where upstream doesn't use git but you still want to use git
for your packaging branch?
Also, it makes me
On Aug 17, 2014, at 08:47 PM, Henrique de Moraes Holschuh wrote:
It is not meaningless in the sense that it is a widely used convention in
git repositories.
And that's actually quite relevant.
It makes more sense when you're a pure upstream, as master might be where you
do all your cutting edge
On Aug 16, 2014, at 04:28 PM, Thomas Goirand wrote:
Why?!? Is there some sort of religion around tarballs? Shouldn't it be
the same stuff that git archive does? If it isn't, why is this the
case? Shouldn't one be able to use what's in the Git repository anyway?
Why can't it be fixed? Aren't we
Barry Warsaw ba...@python.org writes:
It makes more sense when you're a pure upstream, as master might be
where you do all your cutting edge development, and there isn't usually
a clear alternative naming scheme (e.g. code names). 'trunk' might be
better anyway. But in Debian's case, all
Hei Sven,
On 18/08/14 18:10, Sven Bartscher wrote:
If we have a package, which doesn't migrate to testing, we usually
check the Why does package X not in testing yet? page or the PTS.
Usually they do a great job in telling us why our package doesn't
migrate.
But sometimes you have
I've been looking at the RFS process [1]. Some of this was in the
debian-mentors list about a year ago, albeit using corrupt data.
First the good news:
- About 1000 RFS submissions have led to accepted packages since January 2012
- The package acceptance rate has consistently been about 2/3
-
Marc Haber wrote:
On Sun, 17 Aug 2014 23:14:33 -0500, Josh Triplett j...@joshtriplett.org
wrote:
Why a requirement to not improve upstream? Ideally, the Debian patches
for a piece of software should trend to zero over time, as fixes make
their way upstream.
Imagine an upstream author
On Mon, Aug 18, 2014 at 07:28:51PM -0400, Barry Warsaw wrote:
Also, it makes me somewhat uncomfortable to assume that a git tag in the
upstream repo will always be equivalent to their released tarball. In fact,
it's often not, as is the case with Python packages containing a MANIFEST.in.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 18 Aug 2014 13:51:41 +1000
Source: billiard
Binary: python-billiard python3-billiard python-billiard-doc
Architecture: source i386 all
Version: 3.3.0.18-2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 03 Aug 2014 11:32:34 +0300
Source: upgrade-system
Binary: upgrade-system
Architecture: source all
Version: 1.7.0.0
Distribution: unstable
Urgency: medium
Maintainer: Martin-Éric Racine martin-eric.rac...@iki.fi
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 08:07:59 +0200
Source: python-dbusmock
Binary: python-dbusmock python3-dbusmock
Architecture: source all
Version: 0.11.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 18 Aug 2014 13:30:19 +1000
Source: celery
Binary: python-celery-common python-celery python3-celery python-celery-doc
celeryd
Architecture: source all
Version: 3.1.13-1
Distribution: unstable
Urgency: low
Maintainer: Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 07:55:30 +0100
Source: hgsubversion
Binary: hgsubversion
Architecture: source all
Version: 1.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: Qijiang Fan fqj1...@gmail.com
Changed-By: Javi Merino
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 09:07:25 +0200
Source: findimagedupes
Binary: findimagedupes
Architecture: source amd64
Version: 2.18-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 14 Aug 2014 17:12:34 +
Source: scite
Binary: scite
Architecture: source amd64
Version: 3.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt m...@debian.org
Changed-By: Antonio Valentino
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 09 Jun 2014 09:51:45 +0400
Source: boinctui
Binary: boinctui
Architecture: source i386
Version: 2.3.5-1
Distribution: sid
Urgency: low
Maintainer: Sergey Suslov suleman1...@gmail.com
Changed-By: Sergey Suslov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 17 Aug 2014 12:59:45 +
Source: focuswriter
Binary: focuswriter
Architecture: source amd64
Version: 1.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter b...@debian.org
Changed-By: Graeme Gott
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 17 Aug 2014 10:00:19 +0200
Source: mlpack
Binary: libmlpack-dev libmlpack1 mlpack-bin mlpack-doc
Architecture: source amd64 all
Version: 1.0.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 14 Aug 2014 11:32:11 +0200
Source: vidalia
Binary: vidalia
Architecture: source amd64
Version: 0.2.21-5
Distribution: unstable
Urgency: medium
Maintainer: Anonymity Tools Debian Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 18 Aug 2014 09:43:43 +0200
Source: python2.7
Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal
libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev
libpython2.7-testsuite idle-python2.7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 09:22:36 +
Source: libdata-streamdeserializer-perl
Binary: libdata-streamdeserializer-perl
Architecture: source amd64
Version: 0.06-1.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry E. Oboukhov
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Aug 2014 11:08:06 +0200
Source: vidalia
Binary: vidalia
Architecture: source amd64
Version: 0.3.3~alpha-3
Distribution: experimental
Urgency: medium
Maintainer: Anonymity Tools Debian Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 12:33:44 +0200
Source: txtorcon
Binary: python-txtorcon
Architecture: source all
Version: 0.11.0-1
Distribution: unstable
Urgency: medium
Maintainer: Jérémy Bobbio lu...@debian.org
Changed-By: Jérémy Bobbio
- Interactive high-level object-oriented language (pyvenv
binary, v
Changes:
python3.4 (3.4.1-10) unstable; urgency=medium
.
* Update to 20140818 from the 3.4 branch.
* Build-depend on dpkg-dev (= 1.17.11).
Checksums-Sha1:
4f079e735f207c3899af3b9727ef94aa1ed70281 2591 python3.4_3.4.1-10.dsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 13:04:34 +0200
Source: r-cran-maldiquant
Binary: r-cran-maldiquant
Architecture: source amd64
Version: 1.11-1
Distribution: unstable
Urgency: low
Maintainer: The Debichem Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 13:11:09 +0200
Source: r-cran-maldiquantforeign
Binary: r-cran-maldiquantforeign
Architecture: source amd64
Version: 0.9-1
Distribution: unstable
Urgency: low
Maintainer: The Debichem Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 08:25:23 -0300
Source: debci
Binary: debci
Architecture: source all
Version: 0.8.1
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro terce...@debian.org
Changed-By: Antonio Terceiro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 13:26:07 +0200
Source: libnet-dns-sec-perl
Binary: libnet-dns-sec-perl
Architecture: source all
Version: 0.20-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 15 Aug 2014 09:23:03 -0400
Source: freeipmi
Binary: freeipmi-common freeipmi-tools freeipmi-bmc-watchdog
freeipmi-ipmidetect freeipmi-ipmiseld libfreeipmi16 libfreeipmi-dev
libipmidetect0 libipmidetect-dev libipmimonitoring5a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 17 Aug 2014 23:00:56 +1200
Source: wxpython3.0
Binary: python-wxgtk3.0 python-wxgtk3.0-dev python-wxgtk-media3.0
python-wxversion python-wxtools
Architecture: source all
Version: 3.0.0.0+dfsg-4
Distribution: unstable
Urgency:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 12:16:56 +0200
Source: php5
Binary: php5 php5-common libapache2-mod-php5 libapache2-mod-php5filter php5-cgi
php5-cli php5-phpdbg php5-fpm libphp5-embed php5-dev php5-dbg php-pear
php5-curl php5-enchant php5-gd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Aug 2014 10:45:45 +0100
Source: rpcbind
Binary: rpcbind
Architecture: source mips
Version: 0.2.1-6
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar ani...@debian.org
Changed-By: Anibal Monsalve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Aug 2014 14:19:40 +0200
Source: fxt
Binary: libfxt-dev libfxt0 fxt-tools
Architecture: source amd64
Version: 0.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault sthiba...@debian.org
Changed-By: Samuel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 18 Aug 2014 10:13:53 +0200
Source: qlandkartegt
Binary: qlandkartegt
Architecture: source amd64
Version: 1.7.7-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org
assembler, linker and binary utilities (source)
Changes:
binutils (2.24.51.20140818-1) unstable; urgency=high
.
* Snapshot, taken from the trunk 20140818.
- Fix GLIBC ifunc breakage on PowerPC64 ELFv2. LP: #1355962.
Checksums-Sha1:
adbc477361791d99e945e1553d883a7892475b33 1807
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 29 Jun 2014 09:38:49 -0400
Source: muparser
Binary: libmuparser-dev libmuparser2 libmuparser-doc
Architecture: source i386 all
Version: 2.2.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 13:48:04 +0200
Source: cuneiform
Binary: cuneiform cuneiform-common libcuneiform-dev libcuneiform0
Architecture: source all
Version: 1.1.0+dfsg-5
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 10:47:26 +0200
Source: cb2bib
Binary: cb2bib
Architecture: source amd64
Version: 1.4.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 14:58:00 +0200
Source: fakeroot
Binary: fakeroot libfakeroot
Architecture: source
Version: 1.20.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Clint Adams cl...@debian.org
Changed-By: Aurelien Jarno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 11:46:48 +0200
Source: lutefisk
Binary: lutefisk lutefisk-doc
Architecture: source amd64 all
Version: 1.0.7+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 11:47:51 +0200
Source: mmass
Binary: mmass mmass-modules
Architecture: source all amd64
Version: 5.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group debichem-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 18 Aug 2014 15:18:42 +0200
Source: xen
Binary: libxen-4.4 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml
libxen-ocaml-dev xen-utils-common xen-utils-4.4 xen-hypervisor-4.4-amd64
xen-system-amd64 xen-hypervisor-4.4-arm64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 16:51:02 +0200
Source: barman
Binary: barman
Architecture: source all
Version: 1.3.3-1
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini mnen...@debian.org
Changed-By: Marco Nenciarini
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 16:42:33 +0200
Source: discosnp
Binary: discosnp
Architecture: source amd64
Version: 1.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 15:27:41 +0200
Source: lintian4python
Binary: lintian4python
Architecture: source all
Version: 0.28.3
Distribution: experimental
Urgency: low
Maintainer: Jakub Wilk jw...@debian.org
Changed-By: Jakub Wilk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Aug 2014 11:55:14 +0200
Source: mona
Binary: mona
Architecture: source amd64
Version: 1.4-15-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
1 - 100 of 161 matches
Mail list logo
