On Sat, Aug 16, 2014 at 11:07:01AM +1000, Brian May wrote:
On that note, is it ok for me to upload packages that depend on packages
stuck in NEW, or do I have to wait for the packages to clear NEW first? I
have at least one pending Python3 package in this situation.
If you upload things to
On 16 Aug 2014 16:19, Lars Wirzenius l...@liw.fi wrote:
If you upload things to unstable that depend on things in NEW, nobody
will be able to install or upgrade that package (until the dependency
gets through NEW).
In this case however the 2nd package will also get blocked in New (Python3
On Sat, Aug 16, 2014 at 04:46:17PM +1000, Brian May wrote:
On 16 Aug 2014 16:19, Lars Wirzenius l...@liw.fi wrote:
If you upload things to unstable that depend on things in NEW, nobody
will be able to install or upgrade that package (until the dependency
gets through NEW).
In this case
On 08/15/2014 11:24 PM, Scott Kitterman wrote:
On August 15, 2014 4:57:19 PM EDT, Diogene Laerce me_buss...@yahoo.fr wrote:
On 08/15/2014 10:20 PM, Scott Kitterman wrote:
On August 15, 2014 1:42:04 PM EDT, Paul Tagliamonte
paul...@debian.org wrote:
On Fri, Aug 15, 2014 at 07:28:06PM
On 08/16/2014 09:07 AM, Brian May wrote:
Note that there is a huge number of Python packages in Debian. It is
very possible that your favourite packages aren't available as Python3
Debian packages, either because upstream doesn't support Python 3, or
because nobody has done the work yet to
On 08/16/2014 02:46 PM, Brian May wrote:
On 16 Aug 2014 16:19, Lars Wirzenius l...@liw.fi mailto:l...@liw.fi
wrote:
If you upload things to unstable that depend on things in NEW, nobody
will be able to install or upgrade that package (until the dependency
gets through NEW).
In this case
Hi,
On Fri, 15 Aug 2014, Alessandro Ghedini wrote:
Additionally, using the vendor/version scheme would allow for very simple
enumeration of debian vs. ubuntu vs. other with something like git tag | grep
^vendor/ without the need to actually parse debian/changelog or the
specific
version of
if I need to build a Debian package out of an upstream
commit, because there's some bug fixes which I need, but there's no
upstream tarball available?
- In my case, I'd just tag with something like this:
2014.2~b2+20140816+git+11ed391c. Then I'll use my standard process to
generate the orig.tar.xz
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand z...@debian.org
* Package name: python-xstatic-jsencrypt
Version : 2.0.0.2
Upstream Author : Radomir Dopieralski openst...@sheep.art.pl
* URL : https://github.com/stackforge/xstatic-jsencrypt
* License :
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand z...@debian.org
* Package name: python-xstatic-qunit
Version : 1.14.0.2
Upstream Author : Radomir Dopieralski openst...@sheep.art.pl
* URL : https://github.com/stackforge/xstatic-qunit
* License : Expat
Brian May br...@microcomaustralia.com.au wrote:
On 16 Aug 2014 16:19, Lars Wirzenius l...@liw.fi wrote:
If you upload things to unstable that depend on things in NEW, nobody
will be able to install or upgrade that package (until the dependency
gets through NEW).
In this case however the 2nd
Hi,
Marco d'Itri wrote (15 Aug 2014 18:17:16 GMT) :
On Aug 15, Raphael Hertzog hert...@debian.org wrote:
- we can more easily share our git repositories with upstreams
and downstreams
Did they ask for this?
Wrt. downstreams: I guess that Raphaël is implicitly asking for this
(with his Kali
On Sat, Aug 16, 2014 at 10:18:29AM +0200, Raphael Hertzog wrote:
[..snip..]
We do this for Kali Linux too but there are always cases where some
contributors forget about the suffix (in particular when we package stuff
not yet in Debian, or new upstream releases of packages that lag behind in
Hi,
On Sat, 16 Aug 2014, intrigeri wrote:
Marco d'Itri wrote (15 Aug 2014 18:17:16 GMT) :
On Aug 15, Raphael Hertzog hert...@debian.org wrote:
- we can more easily share our git repositories with upstreams
and downstreams
Did they ask for this?
Wrt. downstreams: I guess that Raphaël
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 basis. There's plenty of room for improvement,
e.g. the case where one
(Please trim the quoted mail when you answer)
On Fri, 15 Aug 2014, Scott Kitterman wrote:
- are there other important things to standardize?
We don't even agree on if repositories should be full source or Debian
directory only. Not sure how we can even start to discuss the rest if we
don't
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand z...@debian.org
* Package name: libjs-spin.js
Version : 1.2.8
Upstream Author : Felix Gnass fgn...@neteye.de
* URL : https://github.com/fgnass/spin.js
* License : Expat
Programming Lang: Javascript
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand z...@debian.org
* Package name: python-xstatic-spin
Version : 1.2.8.0+dfsg1
Upstream Author : Radomir Dopieralski openst...@sheep.art.pl
* URL : https://github.com/stackforge/xstatic-spin
* License : Expat
On August 16, 2014 8:03:18 AM EDT, Raphael Hertzog hert...@debian.org wrote:
(Please trim the quoted mail when you answer)
On Fri, 15 Aug 2014, Scott Kitterman wrote:
- are there other important things to standardize?
We don't even agree on if repositories should be full source or
Debian
On Sat, 16 Aug 2014, Scott Kitterman wrote:
Silly or not in your opinion, the Qt-KDE team repositories are set up this
way.
Sorry, I wasn't aware of that and didn't want to imply anything on people
using such a scheme.
Still it would be interesting to know why the team made this choice and
On Sat, 16 Aug 2014, Guido Günther wrote:
On Sat, Aug 16, 2014 at 10:18:29AM +0200, Raphael Hertzog wrote:
[..snip..]
We do this for Kali Linux too but there are always cases where some
contributors forget about the suffix (in particular when we package stuff
not yet in Debian, or new
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 Gerrit at the
Wireshark project and it helps a
On 08/15/2014 11:53 PM, The Wanderer wrote:
It's also something the Linux kernel is still doing, with apparent
success.
Yes, the Linux kernel is a successful project. Does this mean using a
list for reviewing patches is a good thing? No! The workflow with a list
is simply horrible. Using
Le septidi 27 thermidor, an CCXXII, Thomas Goirand a écrit :
If you guys could find a solution to try to work together
again, and merge back both projects, that'd be best for everyone.
When people suggest that, I always wonder how they see that happening with
regard to the code.
On Sat, Aug 16, 2014 at 5:30 PM, Nicolas George geo...@nsup.org wrote:
The only option is to make sure the users do not suffer from the fork, by
making sure they can easily use the version that is most suited for their
need without being sucked into the developers' disagreements.
Can we get
On Sat, 16 Aug 2014 23:29:56 +0800
Thomas Goirand z...@debian.org wrote:
On 08/15/2014 11:53 PM, The Wanderer wrote:
It's also something the Linux kernel is still doing, with apparent
success.
Yes, the Linux kernel is a successful project. Does this mean using a
list for reviewing
Hi,
On Fri, 15 Aug 2014, Simon McVittie wrote:
I've been hesitating on whether to ask this because it gets into
questions of workflow and repo structure that are very much a matter of
taste and don't have a single widely-declared-to-be-good answer, but I
think one of the important questions
Thomas Goirand z...@debian.org writes:
On 08/16/2014 07:05 AM, Jeremy Stanley wrote:
However upstream may build tarballs through a (hopefully
repeatable/automated) process at release time, publish checksums and
signatures for them, et cetera and prefer packagers use those as the
original
Pau Garcia i Quiles pgqui...@elpauer.org writes:
If libav and ffmpeg maintainers cannot reach an agreement regarding
library names and it's not possible to simply use either ffmpeg or libav
indistinctly due missing features binary compatibility, etc, the obvious
solution is that BOTH libav
Hi Russ,
Russ Allbery r...@debian.org (2014-08-16):
None of this is why libav and FFmpeg can't both be in the archive.
They can't both be in the archive because both the release team and
the security team have said that they're not interested in trying to
support both, due to the amount of
On Saturday 16 August 2014 17:09:54 Raphael Hertzog wrote:
On Sat, 16 Aug 2014, Scott Kitterman wrote:
Silly or not in your opinion, the Qt-KDE team repositories are set up this
way.
Sorry, I wasn't aware of that and didn't want to imply anything on people
using such a scheme.
Still
Cyril Brulebois k...@debian.org writes:
Russ Allbery r...@debian.org (2014-08-16):
None of this is why libav and FFmpeg can't both be in the archive.
They can't both be in the archive because both the release team and
the security team have said that they're not interested in trying to
Am 16.08.2014 18:20, schrieb Russ Allbery:
Thomas Goirand z...@debian.org writes:
On 08/16/2014 07:05 AM, Jeremy Stanley wrote:
However upstream may build tarballs through a (hopefully
repeatable/automated) process at release time, publish checksums and
signatures for them, et cetera and
On 8/16/14, Pau Garcia i Quiles pgqui...@elpauer.org wrote:
On Sat, Aug 16, 2014 at 5:30 PM, Nicolas George geo...@nsup.org wrote:
The only option is to make sure the users do not suffer from the fork, by
making sure they can easily use the version that is most suited for their
need without
Hi Nicolas,
2014-08-16 17:11 GMT+02:00 Nicolas George geo...@nsup.org:
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.
Hi Russ,
2014-08-16 18:59 GMT+02:00 Russ Allbery r...@debian.org:
Cyril Brulebois k...@debian.org writes:
Russ Allbery r...@debian.org (2014-08-16):
None of this is why libav and FFmpeg can't both be in the archive.
They can't both be in the archive because both the release team and
the
Ivan Kalvachev ikalvac...@gmail.com writes:
I'm quite sure the Security team is full of capable people who can
handle one more package.
One, no, this statement is not correct. Not because the security team is
not capable -- they are very capable -- but because they are not *full*.
You imply
Hi Thomas,
On Sat, 16 Aug 2014, Thomas Goirand wrote:
The goal here is to be able to host in the same repository the branches
for
multiple cooperating distributions (at least so that downstream can
clone the debian respository and inject their branches next to the
debian
On 16/08/14 17:09, Raphael Hertzog wrote:
On Fri, 15 Aug 2014, Simon McVittie wrote:
It is possible to use git-buildpackage with --git-export (either
explicitly, or configured in debian/gbp.conf) for packages that only
keep debian/ in git.
Are you sure that --git-export is the right option?
Hi,
On Sat, 16 Aug 2014, Philip Muskovac wrote:
I'm writing this from a Kubuntu POV which should be close to
debian-qt-kde as we have a pretty close workflow (one of the reasons why
we're talking about moving our branches to their repositories) as we
also only keep the debian/ dir in the VCS.
Hi,
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 the layout for native packages? how can be differentiate
between native/non-native layout?
Please don't. It would be Really Troublesome
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:
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.BRANCH.NAMING
which could serve as
On 08/16/2014 03:53 AM, Henrique de Moraes Holschuh wrote:
On Fri, 15 Aug 2014, Steve Langasek wrote:
The alternative is handwaving and ignoring the fact that your package
repository is not a complete representation of your package as it exists in
the archive.
What's wrong with storing the
On 08/16/2014 02:03 PM, Raphael Hertzog wrote:
I don't know of any git helper tools that work on git repositories with
Debian directory only.
git-buildpackage --git-overlay
works just fine since ~2009.
I'm wondering if you actually ever investigated if there is a tool instead of
blindly
On Sat, 16 Aug 2014, Bernd Zeimetz wrote:
On 08/16/2014 02:03 PM, Raphael Hertzog wrote:
I don't know of any git helper tools that work on git repositories with
Debian directory only.
git-buildpackage --git-overlay
works just fine since ~2009.
Thanks for the information.
I'm
On Aug 16, Don Armstrong d...@debian.org wrote:
Because you're a Debian Developer and might want to upload a package to
the archive without downloading the uploaded tarball which substantially
duplicates what you have in your source tree? Or you're collaborating
with someone and need to use a
m...@linux.it (Marco d'Itri) writes:
And anyway I'd say that downloading the original archive is simpler than
having to deal with pristine-tar...
I'm mystified. What is there to deal with? I literally never touch it.
It just works, completely transparently and silently.
--
Russ Allbery
Ansgar Burchardt ans...@debian.org (2014-08-17):
incoming.debian.org is used to publish recently uploaded source and
binary packages before they reach the mirror network of the main
archive. Until now, however, with the exception of the buildd network,
it has not been possible to verify the
On Sat, 16 Aug 2014 11:59:20 -0700
Russ Allbery r...@debian.org wrote:
The problem, however, is that taking security seriously, while possibly
necessary, is not sufficient. I'm glad that FFmpeg takes security
seriously, but what FFmpeg needs is to *have fewer security bugs*.
That is very
Hi,
On 16.08.2014 17:49, Pau Garcia i Quiles wrote:
On Sat, Aug 16, 2014 at 5:30 PM, Nicolas George geo...@nsup.org
mailto:geo...@nsup.org wrote:
The only option is to make sure the users do not suffer from the
fork, by
making sure they can easily use the version that is most
On 8/16/2014 11:27 PM, wm4 wrote:
That is very valuable advice. We'll get to work right away.
I've added it to my TODO:
* Don't write bugs.
- Derek
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
wm4 nfx...@googlemail.com writes:
Russ Allbery r...@debian.org wrote:
Note that all of the above statements also apply to libav. As near as I
can tell, this is not a distinguishing characteristic between the two
projects.
And that's an argument against switching to FFmpeg exactly how?
Derek Buitenhuis derek.buitenh...@gmail.com writes:
On 8/16/2014 11:27 PM, wm4 wrote:
That is very valuable advice. We'll get to work right away.
I've added it to my TODO:
* Don't write bugs.
That's a really bad way of avoiding security bugs.
I'm sure you know that and are just being
On Sat, 16 Aug 2014 14:03:18 +0200
Raphael Hertzog hert...@debian.org wrote:
(Please trim the quoted mail when you answer)
On Fri, 15 Aug 2014, Scott Kitterman wrote:
- are there other important things to standardize?
We don't even agree on if repositories should be full source or
On Sat, 16 Aug 2014 21:31:58 +0200
Raphael Hertzog hert...@debian.org wrote:
Hi,
On Sat, 16 Aug 2014, Philip Muskovac wrote:
I'm writing this from a Kubuntu POV which should be close to
debian-qt-kde as we have a pretty close workflow (one of the
reasons why we're talking about moving
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand z...@debian.org
* Package name: python-xstatic-rickshaw
Version : 1.5.0.0
Upstream Author : Radomir Dopieralski openst...@sheep.art.pl
* URL : https://github.com/stackforge/xstatic-rickshaw
* License :
On 08/16/2014 04:18 PM, Raphael Hertzog wrote:
- the above layout is for the traditional case of non-native packages,
what would be the layout for native packages? how can be differentiate
between native/non-native layout?
I've never maintained a native package so I don't really know what
On 16 August 2014 17:36, Thomas Goirand z...@debian.org wrote:
On 08/16/2014 09:07 AM, Brian May wrote:
Note that there is a huge number of Python packages in Debian. It is
very possible that your favourite packages aren't available as Python3
Debian packages, either because upstream
On 08/16/2014 07:59 PM, 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 basis. There's plenty of
Hi,
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
configuration.
The ntopng daemon takes multiple interfaces in the format of multiple
-i command-line options. For example.
ntopng -i eth0 -i wlan0
Currently the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 15:20:37 +0900
Source: last-align
Binary: last-align
Architecture: source amd64
Version: 475-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 11 Aug 2014 11:40:58 +0200
Source: antpm
Binary: antpm antpm-dbg
Architecture: source i386
Version: 1.16-7
Distribution: unstable
Urgency: low
Maintainer: Debian running development group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 08:42:04 +0200
Source: libsocket-perl
Binary: libsocket-perl
Architecture: source amd64
Version: 2.015-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 12 Aug 2014 01:27:57 -0500
Source: wmitime
Binary: wmitime
Architecture: source amd64
Version: 0.3+20120605-1
Distribution: unstable
Urgency: medium
Maintainer: Doug Torrance dtorra...@monmouthcollege.edu
Changed-By: Doug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Aug 2014 17:24:32 +0200
Source: sbcl
Binary: sbcl sbcl-doc sbcl-source
Architecture: source all
Version: 2:1.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 12:48:09 +0200
Source: xfce4-session
Binary: xfce4-session xfce4-session-dbg
Architecture: source amd64
Version: 4.10.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 10:51:23 +0200
Source: onioncat
Binary: onioncat
Architecture: source amd64
Version: 0.2.2+svn559-2
Distribution: unstable
Urgency: medium
Maintainer: Anonymity Tools Debian Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 12:01:35 +0100
Source: mozilla-gnome-keyring
Binary: xul-ext-gnome-keyring
Architecture: source amd64
Version: 0.6.11-3
Distribution: unstable
Urgency: medium
Maintainer: Ximin Luo infini...@pwned.gg
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 16 Aug 2014 13:09:04 +0200
Source: debian-edu
Binary: education-tasks education-menus education-astronomy education-chemistry
education-common education-desktop-gnome education-desktop-kde
education-desktop-lxde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 16 Aug 2014 12:49:07 +0200
Source: kradio4
Binary: kradio4 kradio
Architecture: source amd64 all
Version: 4.0.7+git20140816-1
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 13 Aug 2014 07:37:23 +0200
Source: autodocksuite
Binary: autodock autogrid autodock-test autogrid-test autodock-getdata
Architecture: source amd64 all
Version: 4.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 21:04:21 +0900
Source: mikutter
Binary: mikutter
Architecture: source all
Version: 3.0.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) d...@debian.org
Changed-By: HIGUCHI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Aug 2014 16:04:28 +0200
Source: lebiniou
Binary: lebiniou
Architecture: source amd64
Version: 3.22-1
Distribution: unstable
Urgency: low
Maintainer: Olivier Girondel oliv...@biniou.info
Changed-By: Olivier Girondel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 11 Aug 2014 09:09:02 -0400
Source: ruby-rack-google-analytics
Binary: ruby-rack-google-analytics
Architecture: source all
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 11 Aug 2014 21:24:55 -0400
Source: ruby-rails-autolink
Binary: ruby-rails-autolink
Architecture: source all
Version: 1.1.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 16 Aug 2014 14:22:17 +0200
Source: rygel
Binary: rygel rygel-dbg rygel-2.2-dev librygel-core-2.2-2 librygel-server-2.2-2
librygel-renderer-2.2-2 librygel-renderer-gst-2.2-2 rygel-mediathek
rygel-tracker rygel-gst-renderer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 11 Aug 2014 20:35:02 -0400
Source: ruby-uglifier
Binary: ruby-uglifier
Architecture: source all
Version: 2.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Aug 2014 22:52:54 -0400
Source: libdvdnav
Binary: libdvdnav4 libdvdnav-dbg libdvdnav-dev libdvdnav-doc
Architecture: source amd64 all
Version: 5.0.0-1
Distribution: unstable
Urgency: low
Maintainer: Reinhard Tartler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 15 Aug 2014 22:10:40 -0400
Source: libdvdread
Binary: libdvdread4 libdvdread-dbg libdvdread-dev
Architecture: source amd64
Version: 5.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 12:59:03 +
Source: libwfut
Binary: libwfut-0.2-1 libwfut-0.2-1-dbg libwfut-0.2-dev wfut
Architecture: source amd64
Version: 0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 17:38:28 +0200
Source: tcpdump
Binary: tcpdump
Architecture: source
Version: 4.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Romain Francoise rfranco...@debian.org
Changed-By: Romain Francoise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 18:02:30 +0200
Source: metastore
Binary: metastore
Architecture: source
Version: 1+20080623+debian-4
Distribution: unstable
Urgency: medium
Maintainer: Romain Francoise rfranco...@debian.org
Changed-By: Romain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 16 Aug 2014 10:57:56 -0500
Source: rpy2
Binary: python-rpy2
Architecture: source i386
Version: 2.4.3-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, 14 Aug 2014 00:39:46 -0500
Source: maitreya
Binary: maitreya fonts-maitreya
Architecture: source i386 all
Version: 7.0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Paul Elliott pelli...@blackpatchpanel.com
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 18:11:22 +0200
Source: visitors
Binary: visitors
Architecture: source
Version: 0.7-10
Distribution: unstable
Urgency: low
Maintainer: Romain Francoise rfranco...@debian.org
Changed-By: Romain Francoise
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 09:41:47 +0100
Source: codelite
Binary: codelite codelite-plugins
Architecture: source amd64
Version: 6.0.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: James Cowgill james...@cowgill.org.uk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 13:01:43 -0400
Source: pulseaudio
Binary: pulseaudio pulseaudio-dbg pulseaudio-utils pulseaudio-utils-dbg
pulseaudio-esound-compat pulseaudio-esound-compat-dbg
pulseaudio-module-zeroconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 11 Aug 2014 12:08:31 -0400
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev
network-manager-dbg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 19:07:55 +0200
Source: adequate
Binary: adequate
Architecture: source all
Version: 0.12.1
Distribution: unstable
Urgency: medium
Maintainer: Jakub Wilk jw...@debian.org
Changed-By: Jakub Wilk jw...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 16 Aug 2014 12:51:44 -0500
Source: car
Binary: r-cran-car
Architecture: source all
Version: 2.0-21-1
Distribution: unstable
Urgency: low
Maintainer: Dirk Eddelbuettel e...@debian.org
Changed-By: Dirk Eddelbuettel e...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 09:41:42 -0700
Source: pspp
Binary: pspp
Architecture: source i386
Version: 0.8.3-1.1
Distribution: unstable
Urgency: low
Maintainer: Friedrich Beckmann friedrich.beckm...@gmx.de
Changed-By: Ben Pfaff
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 21:02:49 +0200
Source: gpsd
Binary: gpsd gpsd-dbg gpsd-clients python-gps libgps21 libgps-dev libqgpsmm21
libqgpsmm-dev
Architecture: source amd64
Version: 3.10+dev3~d6b65b48-3
Distribution: unstable
Urgency:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 07 Aug 2014 00:06:06 +0200
Source: sslh
Binary: sslh
Architecture: source amd64
Version: 1.16-1
Distribution: unstable
Urgency: medium
Maintainer: Guillaume Delacour g...@iroqwa.org
Changed-By: Guillaume Delacour
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 14:52:52 +0200
Source: gdisk
Binary: gdisk gdisk-noicu
Architecture: source amd64 all
Version: 0.8.10-1
Distribution: unstable
Urgency: medium
Maintainer: Guillaume Delacour g...@iroqwa.org
Changed-By: Guillaume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 22:30:12 +0200
Source: libconfigreader-simple-perl
Binary: libconfigreader-simple-perl
Architecture: source all
Version: 1.29-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 22:12:33 +0200
Source: gpsd
Binary: gpsd gpsd-dbg gpsd-clients python-gps libgps21 libgps-dev libqgpsmm21
libqgpsmm-dev
Architecture: source amd64
Version: 3.10+dev3~d6b65b48-4
Distribution: unstable
Urgency:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 16 Aug 2014 21:21:55 +0200
Source: libuv
Binary: libuv-dev libuv0.10 libuv0.10-dbg
Architecture: source
Version: 0.10.28-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 16 Aug 2014 20:53:39 +0100
Source: procenv
Binary: procenv
Architecture: amd64 source
Version: 0.36-1
Distribution: sid
Urgency: medium
Maintainer: James Hunt james.h...@ubuntu.com
Changed-By: James Hunt james.h...@ubuntu.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 22:37:40 +0200
Source: open-vm-tools
Binary: open-vm-tools open-vm-tools-desktop open-vm-tools-dev open-vm-tools-dbg
open-vm-tools-dkms
Architecture: source amd64 all
Version: 2:9.4.6-1770165-2+exp1
Distribution:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 16 Aug 2014 14:08:30 -0700
Source: pspp
Binary: pspp
Architecture: source i386
Version: 0.8.3-1.2
Distribution: unstable
Urgency: low
Maintainer: Friedrich Beckmann friedrich.beckm...@gmx.de
Changed-By: Ben Pfaff
1 - 100 of 108 matches
Mail list logo
