Op zaterdag 19 juli 2014 22:54:47 schreef u:
]] Wouter Verhelst
Op zondag 13 juli 2014 22:13:10 schreef Martin Zobel-Helas:
Furthermore, we will change the people.debian.org web-service such that
only HTTPS connections will be supported (unencrypted requests will be
redirected).
]] Wouter Verhelst
Op zaterdag 19 juli 2014 22:54:47 schreef u:
]] Wouter Verhelst
Op zondag 13 juli 2014 22:13:10 schreef Martin Zobel-Helas:
Furthermore, we will change the people.debian.org web-service such that
only HTTPS connections will be supported (unencrypted requests will
On Sun, Jul 20, 2014, at 08:15, Wouter Verhelst wrote:
Additionally, since debian.org uses DNSSEC, if you can somehow MITM
people.debian.org then due to DANE you can MITM it for HTTP as well as
HTTPS, so forcing HTTPS really doesn't gain you much.
But that implies that the attacker has access
Package: wnpp
Severity: wishlist
Owner: LIU Dongyuan liu.dongy...@gmail.com
* Package name: fonts-adobe-sourcehansans-cn
Version : 1.000
Upstream Author : Ken Lunde lu...@adobe.com
* URL : http://sourceforge.net/projects/source-han-sans.adobe/
* License :
Package: wnpp
Severity: wishlist
Owner: LIU Dongyuan liu.dongy...@gmail.com
* Package name: fonts-adobe-sourcehansans-jp
Version : 1.000
Upstream Author : Ken Lunde lu...@adobe.com
* URL : http://sourceforge.net/projects/source-han-sans.adobe/
* License :
Package: wnpp
Severity: wishlist
Owner: LIU Dongyuan liu.dongy...@gmail.com
* Package name: fonts-adobe-sourcehansans-twhk
Version : 1.000
Upstream Author : Ken Lunde lu...@adobe.com
* URL : http://sourceforge.net/projects/source-han-sans.adobe/
* License :
Package: wnpp
Severity: wishlist
Owner: LIU Dongyuan liu.dongy...@gmail.com
* Package name: fonts-adobe-sourcehansans-kr
Version : 1.000
Upstream Author : Ken Lunde lu...@adobe.com
* URL : http://sourceforge.net/projects/source-han-sans.adobe/
* License :
Hi,
Ondřej Surý:
Pervasive monitoring.
In and of itself, if you only access publicly-availble files, that's not a
threat.
Really we should introduce encryption
*everywhere*.
This change does not introduce encryption.
It disables the option not to use encryption.
I can accept that e.g. if
Op zondag 20 juli 2014 09:23:55 schreef u:
On Sun, Jul 20, 2014, at 08:15, Wouter Verhelst wrote:
Additionally, since debian.org uses DNSSEC, if you can somehow MITM
people.debian.org then due to DANE you can MITM it for HTTP as well as
HTTPS, so forcing HTTPS really doesn't gain you much.
Hi All,
On Sat, 2014-07-19 at 22:57 +0300, Arto Jantunen wrote:
(please don't CC me on replies, I read the list)
Abou Al Montacir abou.almonta...@sfr.fr writes:
We have several forums for user support requests, the main one being
debian-user@l.d.o. The bts general pseudopackage is not a
Op zondag 20 juli 2014 08:47:07 schreef Tollef Fog Heen:
]] Wouter Verhelst
Op zaterdag 19 juli 2014 22:54:47 schreef u:
]] Wouter Verhelst
Op zondag 13 juli 2014 22:13:10 schreef Martin Zobel-Helas:
Furthermore, we will change the people.debian.org web-service such
that
On Sun, 2014-07-20 at 07:50 +0800, Paul Wise wrote:
On Sun, Jul 20, 2014 at 2:56 AM, Abou Al Montacir wrote:
I'd recommend that reportbug(-ng) provide a clear message when creating
a bug, just like some other packages do it (evolution to name my
preferred mail client). This will then
On Sun, 2014-07-20 at 11:09 +0200, Abou Al Montacir wrote:
Please file bugs about it. Unfortunately reportbug{,-ng} maintenance
is not happening often right now so it might take a long time for
that
to happen.
Sure I'll do.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755392
Cheers,
On Sun, Jul 20, 2014 at 09:23:55AM +0200, Ondřej Surý wrote:
On Sun, Jul 20, 2014, at 08:15, Wouter Verhelst wrote:
There are lots of attack vectors. It's not a response to a single
attack being exploited in the wild.
So name one?
Pervasive monitoring. Really we should introduce
* Tollef Fog Heen tfh...@err.no, 2014-07-20, 08:47:
Would you be happy with
http://people.debian.org/THIS-IS-INSECURE/YES-I-WANT-TO-PROCEED/~user/file
as the URLs?
No need to be condescending. :-(
Also, I wouldn't say “insecure”, which might be vague in this context.
My proposal:
On 20 July 2014 10:07, Wouter Verhelst w...@uter.be wrote:
With the state of the CA cartel these days, I have little
trust in the strength of HTTPS as a verification mechanism, and so I
wouldn't trust a file to be correct even if it came through an HTTPS
connection that validates. Instead, I
On Sun, 20 Jul 2014 10:45:10 +0200, Wouter Verhelst w...@uter.be wrote:
Op zondag 20 juli 2014 09:23:55 schreef u:
On Sun, Jul 20, 2014, at 08:15, Wouter Verhelst wrote:
Additionally, since debian.org uses DNSSEC, if you can somehow MITM
people.debian.org then due to DANE you can MITM it for
On Sun, 20 Jul 2014, Steve Langasek wrote:
On Sun, Jul 20, 2014 at 09:23:55AM +0200, Ondřej Surý wrote:
On Sun, Jul 20, 2014, at 08:15, Wouter Verhelst wrote:
There are lots of attack vectors. It's not a response to a single
attack being exploited in the wild.
So name one?
On 07/19/2014 08:49 PM, Abou Al Montacir wrote:
Control: reopen -1
On Sat, 2014-07-19 at 17:03 +, Debian Bug Tracking System wrote:
...
Missing information, dupe.
Kind regards,
Andrei
Hi Andrei,
I don't think that missing information is enough argument to close a
bug.
Hi AL Nik,
Can
On Sun, 20 Jul 2014, Ondřej Surý wrote:
Pervasive monitoring. Really we should introduce encryption
*everywhere*.
And indeed we have been moving towards https for most services over the
last 12 months.
www is still not done, due to unfortunate push-bash by the service
owners, but most others
On Sun, Jul 20, 2014 at 07:50:17AM +0800, Paul Wise wrote:
I think that would probably just add more noise to debian-devel.
Maybe general bugs should go to debian-user instead?
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
At Sun, 20 Jul 2014 11:07:16 +0200,
Wouter Verhelst wrote:
Even ignoring that, assuming people trust that code off
people.debian.org is safe, if they run a validating DNS resolver they
don't run more of a risk than if they use only HTTPS.
I don't really follow that. A validating DNS resolver
Op zondag 20 juli 2014 11:06:00 schreef Tim Retout:
On 20 July 2014 10:07, Wouter Verhelst w...@uter.be wrote:
With the state of the CA cartel these days, I have little
trust in the strength of HTTPS as a verification mechanism, and so I
wouldn't trust a file to be correct even if it came
Op zondag 20 juli 2014 12:53:59 schreef Jeroen Dekkers:
At Sun, 20 Jul 2014 11:07:16 +0200,
Wouter Verhelst wrote:
Even ignoring that, assuming people trust that code off
people.debian.org is safe, if they run a validating DNS resolver they
don't run more of a risk than if they use only
On Sun, July 20, 2014 08:15, Wouter Verhelst wrote:
Op zaterdag 19 juli 2014 22:54:47 schreef u:
Please note that there remain cases where accessing HTTPS is difficult
or impossible. One of these (but by no means the only one) is the
current release of debian-installer: the wget
Op zondag 20 juli 2014 11:38:13 schreef Marc Haber:
On Sun, 20 Jul 2014 10:45:10 +0200, Wouter Verhelst w...@uter.be wrote:
Op zondag 20 juli 2014 09:23:55 schreef u:
On Sun, Jul 20, 2014, at 08:15, Wouter Verhelst wrote:
Additionally, since debian.org uses DNSSEC, if you can somehow MITM
On Sun, 20 Jul 2014 13:21:03 +0200, Wouter Verhelst w...@uter.be wrote:
Op zondag 20 juli 2014 11:38:13 schreef Marc Haber:
I might me missing something, and I admit not having read the entire
thread, but how would they have access to private key material?
Beyond GPG keys there are also DNSSEC
]] Wouter Verhelst
AFAIK, people.debian.org does not allow running server-side HTTP scripts
(and even if it does, I think that's a bad idea and we should disable it
ASAP). As such, people.debian.org is not an interface for reading mail
in your browser over HTTP, or doing IRC, or whatnot. So
On Sun, 20 Jul 2014, Wouter Verhelst wrote:
These are all good arguments for enabling HTTPS and making it the
default (which I've said repeatedly is a move that I support, or at the
very least don't oppose), but not for *disabling* the possibility of
plain HTTP.
Pray tell: How do you make it
On Sun, Jul 20, 2014 at 10:38:23AM +0200, Matthias Urlichs wrote:
Pervasive monitoring.
In and of itself, if you only access publicly-availble files, that's not a
threat.
1 Security service has unknown exploit.
2 Pervasive monitoring sees you install a package from somewhere over HTTP.
3
On Sun, Jul 20, 2014 at 12:03:59PM +0200, Jakub Wilk wrote:
My proposal:
http://nohttps.people.debian.org/~user/file
This is similar to my proposal[1], using a seperate VHOST that would allow HTTP
access. It's clear in the URL what is going on, and most people will be
using HTTPS but there are
On Sun, Jul 20, 2014 at 01:52:20PM +0200, Peter Palfrader wrote:
On Sun, 20 Jul 2014, Wouter Verhelst wrote:
These are all good arguments for enabling HTTPS and making it the
default (which I've said repeatedly is a move that I support, or at the
very least don't oppose), but not for
On Sun, 20 Jul 2014, Iain R. Learmonth wrote:
Pray tell: How do you make it default.
See: http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
It sends a header to tell you you should be using HTTPS.
Alas, that's not what HSTS is about or for. It cannot be used for this.
--
On Sat, Jul 19, 2014 at 08:25:05PM +0200, Abou Al Montacir wrote:
because it is duplicate and not because it is missing information. It
may be clear for may that dupe means duplicate, but this is not clear
for every body especially that in French this means stupid.
Considering the language is
On Sun, 2014-07-20 at 13:10 +0300, Aleksandar Nikolov wrote:
I tried this experiment:
Installed sshd and connected from another computer - it works. But
after
the lid closed and opened, I cannot connect. The system must be dead,
although the fans blows and the power led is on.
This means
hello
searching on packages.debian.org shows btrfs only for testing, oldstable,
NOT in stable? how that?!
please also CC me (not in mailinglist)
thanks
Andrew
Not a user of btrfs, but the userspace tools are in package btrfs-tools
https://packages.debian.org/search?keywords=btrfs-tools
and the kernel modules seem to be in the default kernel packages
$ dpkg -L linux-image-3.2.0-4-amd64 | grep btrfs.ko
/lib/modules/3.2.0-4-amd64/kernel/fs/btrfs/btrfs.ko
W dniu 20/07/2014 11:01, Peter Palfrader napisał(a):
I do think that if DSA are going to enforce such a policy, they should
be
able to explain why.
What Ondřej said
a.k.a. “because”. Do try better.
– j.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of
On Sun, Jul 20, 2014 at 10:55:55AM +0200, Abou Al Montacir wrote:
upgrade == not working anymore == bug
I think this is a typical acceptable situation, what ever the user's
level of experience.
It is more about how much we care about our users rather than about the
validity of the bug report.
Op zondag 20 juli 2014 13:52:20 schreef Peter Palfrader:
On Sun, 20 Jul 2014, Wouter Verhelst wrote:
These are all good arguments for enabling HTTPS and making it the
default (which I've said repeatedly is a move that I support, or at the
very least don't oppose), but not for *disabling*
Op zondag 20 juli 2014 13:28:43 schreef Marc Haber:
On Sun, 20 Jul 2014 13:21:03 +0200, Wouter Verhelst w...@uter.be wrote:
Op zondag 20 juli 2014 11:38:13 schreef Marc Haber:
I might me missing something, and I admit not having read the entire
thread, but how would they have access to
On Sun, Jul 20, 2014, at 12:06, Tim Retout wrote:
On 20 July 2014 10:07, Wouter Verhelst w...@uter.be wrote:
With the state of the CA cartel these days, I have little
trust in the strength of HTTPS as a verification mechanism, and so I
wouldn't trust a file to be correct even if it came
On Sun, 20 Jul 2014, Wouter Verhelst wrote:
These are all good arguments for enabling HTTPS and making it the
default (which I've said repeatedly is a move that I support, or at the
very least don't oppose), but not for *disabling* the possibility of
plain HTTP.
Pray tell: How do
On Sun, Jul 20, 2014 at 06:19:14PM +0200, Peter Palfrader wrote:
None of these brings people who type in people.debian.org into their
browser to https.
Right.
AFAICT the only technical change that will do that (sanely) is an
HTTP-level redirection from http://(.*) to https://$1 . Having that
Package: wnpp
Owner: Dominique Dumont d...@debian.org
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,
pkg-javascript-de...@lists.alioth.debian.org, debian-p...@lists.debian.org
* Package name: prettify
Version : 2013.03.04
Upstream Author : mikesam...@gmail.com
*
On 2014-07-20 08:15, Wouter Verhelst wrote:
True, but debian-installer simply does not support any signed/encrypted
preseeding.
[…]
Granted, these are probably bugs, and IIRC Colin was working on
providing HTTPS support for jessie. Still, I while I support enabling
HTTPS for people.d.o, I
On Sun, Jul 20, 2014 at 08:23:58PM +0200, Philipp Kern wrote:
On 2014-07-20 08:15, Wouter Verhelst wrote:
True, but debian-installer simply does not support any signed/encrypted
preseeding.
[…]
Granted, these are probably bugs, and IIRC Colin was working on
providing HTTPS support for
Op zondag 20 juli 2014 18:19:14 schreef Peter Palfrader:
On Sun, 20 Jul 2014, Wouter Verhelst wrote:
These are all good arguments for enabling HTTPS and making it the
default (which I've said repeatedly is a move that I support, or at
the
very least don't oppose), but not for
On Sun, 20 Jul 2014, Stefano Zacchiroli wrote:
AFAICT the only technical change that will do that (sanely) is an
HTTP-level redirection from http://(.*) to https://$1 .
That is my understanding as well.
- it's not entirely clear how much extra work implementing this would
require. In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/20/2014 03:08 PM, Wouter Verhelst wrote:
Op zondag 20 juli 2014 18:19:14 schreef Peter Palfrader:
None of these brings people who type in people.debian.org into
their browser to https.
If they type it in because they want to avoid
On Sun, 20 Jul 2014, Wouter Verhelst wrote:
If HSTS is enabled and you access people.debian.org even once (and you
don't clear out their entire cache for as long as the HSTS timeout
lives), then HSTS will ensure that the HTTP URL gets turned into an
HTTPS URL automatically.
Alas, no.
--
On Sun, Jul 20, 2014 at 01:19:58PM +0200, Thijs Kinkhorst wrote:
On Sun, July 20, 2014 08:15, Wouter Verhelst wrote:
Op zaterdag 19 juli 2014 22:54:47 schreef u:
Please note that there remain cases where accessing HTTPS is difficult
or impossible. One of these (but by no means the only
On 07/20/2014 04:25 PM, Abou Al Montacir wrote:
On Sun, 2014-07-20 at 13:10 +0300, Aleksandar Nikolov wrote:
I tried this experiment:
Installed sshd and connected from another computer - it works. But
after
the lid closed and opened, I cannot connect. The system must be dead,
although the fans
On Sun, Jul 20, 2014 at 09:00:05PM +0200, Peter Palfrader wrote:
IMO, a dedicated vhost name sounds much more appealing than magic apache
configs. I wonder whether it should use the same UserDirs.
Oh, right. With different UserDirs (bonus point: the default one,
public_html/, being the one
On Mon, Jul 21, 2014 at 12:05:56AM +0200, Stefano Zacchiroli wrote:
On Sun, Jul 20, 2014 at 09:00:05PM +0200, Peter Palfrader wrote:
IMO, a dedicated vhost name sounds much more appealing than magic apache
configs. I wonder whether it should use the same UserDirs.
Oh, right. With
Hi,
On Sun, Jul 20, 2014 at 07:30:35PM +0100, Colin Watson wrote:
I'll hopefully get to finishing this at DebConf; I think I merged most
of the safe and independent pieces already, and mostly just need to deal
with wget-udeb. I'm not expecting to backport this to wheezy though.
yeah, it
On Sun, Jul 20, 2014 at 9:12 PM, Chris Bannister wrote:
Considering the language is English, it would be a pity if the reader
made this mistake. Let's assume a modicum of 'common sense' at least.
With an international project like Debian, we can't assume that
English is everyone's first
On Sun, Jul 20, 2014 at 3:59 PM, LIU Dongyuan wrote:
* Package name: fonts-adobe-sourcehansans-cn
Due to the need for Adobe's ADFKO, this will have to go to contrib.
IIRC ADFKO will become open source at some point and the font could
move to main then.
--
bye,
pabs
On Sun, Jul 20, 2014 at 4:13 PM, LIU Dongyuan wrote:
* Package name: fonts-adobe-sourcehansans-jp
Due to the need for Adobe's ADFKO, this will have to go to contrib.
IIRC ADFKO will become open source at some point and the font could
move to main then.
--
bye,
pabs
On Sun, Jul 20, 2014 at 4:16 PM, LIU Dongyuan liu.dongy...@gmail.com wrote:
* Package name: fonts-adobe-sourcehansans-kr
Due to the need for Adobe's ADFKO, this will have to go to contrib.
IIRC ADFKO will become open source at some point and the font could
move to main then.
--
bye,
pabs
Hi
On Mon, 21 Jul 2014, Paul Wise wrote:
Due to the need for Adobe's ADFKO, this will have to go to contrib.
IIRC ADFKO will become open source at some point and the font could
move to main then.
Why? There are many fonts around in otf format and packaged for
Debian. I don't see that problem
On Mon, 21 Jul 2014, Norbert Preining wrote:
On Mon, 21 Jul 2014, Paul Wise wrote:
Due to the need for Adobe's ADFKO, this will have to go to contrib.
IIRC ADFKO will become open source at some point and the font could
move to main then.
Why? There are many fonts around in otf format and
On Sun, Jul 20, 2014 at 6:29 PM, Jonathan Dowland wrote:
On Sun, Jul 20, 2014 at 07:50:17AM +0800, Paul Wise wrote:
I think that would probably just add more noise to debian-devel.
Maybe general bugs should go to debian-user instead?
That would be change in meaning of the pseudo-package, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 19 Jul 2014 23:18:07 -0700
Source: python-scrapy
Binary: python-scrapy python-scrapy-doc
Architecture: source all
Version: 0.24.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 08:15:23 +0200
Source: findutils
Binary: findutils locate
Architecture: source i386
Version: 4.5.14-1
Distribution: experimental
Urgency: medium
Maintainer: Andreas Metzler ametz...@debian.org
Changed-By: Andreas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 09:27:28 +0200
Source: debian-security-support
Binary: debian-security-support
Architecture: source all
Version: 2014.07.20
Distribution: sid
Urgency: low
Maintainer: Christoph Biedl debian.a...@manchmal.in-ulm.de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 08 Jul 2014 01:48:08 +0200
Source: dovecot
Binary: dovecot-core dovecot-dev dovecot-imapd dovecot-pop3d dovecot-lmtpd
dovecot-managesieved dovecot-pgsql dovecot-mysql dovecot-sqlite dovecot-ldap
dovecot-gssapi dovecot-sieve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 11:33:16 +0200
Source: codespeak-lib
Binary: python3-py python-py
Architecture: source all
Version: 1.4.22-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 19 Jul 2014 23:57:46 -0700
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-glx xserver-xorg-video-nvidia libgl1-nvidia-glx
libgl1-nvidia-glx-i386 libegl1-nvidia libgles1-nvidia libgles2-nvidia
libnvidia-eglcore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 12:10:26 +0200
Source: base-files
Binary: base-files
Architecture: source amd64
Version: 7.5
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila sanv...@debian.org
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 11:36:26 +0200
Source: fsl
Binary: fsl fsl-5.0 fsl-core fsl-5.0-core
Architecture: source amd64 all
Version: 5.0.7-3
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team t...@neuro.debian.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 18 Jul 2014 10:58:46 +0200
Source: libcap2
Binary: libcap2-bin libcap2 libcap-dev libpam-cap
Architecture: source amd64
Version: 1:2.24-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann m...@daniel-baumann.ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 10:41:59 +
Source: ui-auto
Binary: ui-auto
Architecture: source all
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Stephan Sürken abs...@debian.org
Changed-By: Stephan Sürken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 10:56:30 +0200
Source: meld
Binary: meld
Architecture: source all
Version: 1.8.6-1
Distribution: unstable
Urgency: medium
Maintainer: Balint Reczey bal...@balintreczey.hu
Changed-By: Balint Reczey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 03:05:38 +0200
Source: meld
Binary: meld
Architecture: source all
Version: 3.11.2-1
Distribution: experimental
Urgency: medium
Maintainer: Balint Reczey bal...@balintreczey.hu
Changed-By: Balint Reczey
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 08 Jul 2014 15:49:42 +0200
Source: inkscape
Binary: inkscape
Architecture: source amd64
Version: 0.48.5-1
Distribution: unstable
Urgency: medium
Maintainer: Wolfram Quester wo...@sigxcpu.org
Changed-By: Matteo F. Vescovi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 10:20:05 +0200
Source: mesa
Binary: libgl1-mesa-swx11 libgl1-mesa-swx11-dbg libgl1-mesa-swx11-i686
libgl1-mesa-swx11-dev libxatracker2 libxatracker2-dbg libxatracker-dev libgbm1
libgbm1-dbg libgbm-dev libegl1-mesa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 19 Jul 2014 22:44:11 +0200
Source: ocrad
Binary: ocrad libocrad-dev
Architecture: source amd64
Version: 0.24~pre1-1
Distribution: experimental
Urgency: medium
Maintainer: Alexander Alemayhu alexan...@bitraf.no
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 14:53:25 +0200
Source: libnet-netmask-perl
Binary: libnet-netmask-perl
Architecture: source all
Version: 1.9021-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 15:01:25 +0200
Source: pinto
Binary: pinto
Architecture: source all
Version: 0.97+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 15:21:11 +0200
Source: libtest-kwalitee-perl
Binary: libtest-kwalitee-perl
Architecture: source all
Version: 1.19-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 18:13:25 +0530
Source: ctpp2
Binary: ctpp2-utils ctpp2-doc libctpp2-2 libctpp2-2-dbg libctpp2-dev
Architecture: source all amd64
Version: 2.8.3-13
Distribution: unstable
Urgency: medium
Maintainer: Vasudev Kamath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 15:31:48 +0200
Source: libtext-multimarkdown-perl
Binary: libtext-multimarkdown-perl
Architecture: source all
Version: 1.35-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 14:06:59 +0100
Source: apt-transport-tor
Binary: apt-transport-tor
Architecture: source amd64
Version: 0.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Tim Retout dioc...@debian.org
Changed-By: Tim Retout
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 17 Jul 2014 22:08:19 +0800
Source: freefem
Binary: freefem freefem-doc freefem-examples libfreefem0 libfreefem-dev
libfreefem-doc
Architecture: source all amd64
Version: 3.5.8-5.1
Distribution: unstable
Urgency: low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Jul 2014 15:47:40 +0200
Source: libyaml-perl
Binary: libyaml-perl
Architecture: source all
Version: 0.97-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 16 Jul 2014 19:21:31 +0200
Source: prerex
Binary: prerex vprerex
Architecture: source amd64
Version: 6.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh r...@debian.org
Changed-By: Ryan Kavanagh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 10:40:43 -0500
Source: sandwich
Binary: r-cran-sandwich
Architecture: source all
Version: 2.3-1-1
Distribution: unstable
Urgency: low
Maintainer: Dirk Eddelbuettel e...@debian.org
Changed-By: Dirk Eddelbuettel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 17:15:28 +0200
Source: shotwell
Binary: shotwell shotwell-common shotwell-dbg
Architecture: source amd64 all
Version: 0.18.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Shotwell Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 13:30:18 +0800
Source: openstack-debian-images
Binary: openstack-debian-images
Architecture: source all
Version: 0.11
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 17:38:43 +0100
Source: stress-ng
Binary: stress-ng
Architecture: source amd64
Version: 0.01.24-1
Distribution: unstable
Urgency: medium
Maintainer: Colin King colin.k...@canonical.com
Changed-By: Colin King
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 10:47:18 +0300
Source: mtpaint
Binary: mtpaint
Architecture: source amd64
Version: 3.40-2
Distribution: unstable
Urgency: medium
Maintainer: Muammar El Khatib muam...@debian.org
Changed-By: Muammar El Khatib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 18:05:01 +0100
Source: stress-ng
Binary: stress-ng
Architecture: source amd64
Version: 0.01.25-1
Distribution: unstable
Urgency: medium
Maintainer: Colin King colin.k...@canonical.com
Changed-By: Colin King
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 19:16:14 +0200
Source: poppler
Binary: libpoppler46 libpoppler-dev libpoppler-private-dev libpoppler-glib8
libpoppler-glib-dev libpoppler-glib-doc gir1.2-poppler-0.18 libpoppler-qt4-4
libpoppler-qt4-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 19:52:46 +0200
Source: gnome-pie
Binary: gnome-pie
Architecture: source amd64
Version: 0.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group packa...@qa.debian.org
Changed-By: Alessandro Ghedini
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 19 Jul 2014 20:24:55 -0700
Source: s3ql
Binary: s3ql s3ql-dbg
Architecture: source amd64
Version: 2.9+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Nikolaus Rath nikol...@rath.org
Changed-By: Nikolaus Rath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 02 Jul 2014 08:40:49 +0200
Source: crashme
Binary: crashme
Architecture: source amd64
Version: 2.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl
Changed-By:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 23:27:45 +0530
Source: ctpp2
Binary: ctpp2-utils ctpp2-doc libctpp2-2 libctpp2-2-dbg libctpp2-dev
Architecture: source all amd64
Version: 2.8.3-14
Distribution: unstable
Urgency: medium
Maintainer: Vasudev Kamath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 20 Jul 2014 19:53:07 +0200
Source: skycat
Binary: skycat
Architecture: source amd64
Version: 3.1.2+starlink1~b-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 20 Jul 2014 14:57:15 -0400
Source: libav
Binary: libav-tools libav-dbg libav-doc libavutil53 libavcodec55 libavdevice54
libavformat55 libavfilter4 libswscale2 libavutil-dev libavcodec-dev
libavdevice-dev libavformat-dev
1 - 100 of 115 matches
Mail list logo
