Bug#745271: ITP: ruby-fog-brightbox -- Brightbox Cloud support for the fog gem

2014-04-19 Thread Praveen Arimbrathodiyil
Package: wnpp Severity: wishlist Owner: Pirate Praveen * Package name: ruby-fog-brightbox Version : 0.0.2 Upstream Author : Paul Thornthwaite * URL : https://rubygems.org/gems/fog-brightbox * License : Expat Programming Lang: Ruby Description : Brightbo

Re: Proposing amd64-hardened architecture for Debian

2014-04-19 Thread Riku Voipio
On Sat, Apr 19, 2014 at 02:06:45PM +0200, Bálint Réczey wrote: > Hi Riku, > > 2014-04-19 13:26 GMT+02:00 Riku Voipio : > > On Tue, Apr 15, 2014 at 12:00:33PM +0200, Balint Reczey wrote: > >> Facing last week's Heartbleed [1] bug the need for improving the > >> security of our systems became more a

Arm64 port live on debian-ports

2014-04-19 Thread Wookey
You may or may not have noticed that 'arm64' is coming. This a 64-bit arm architecture also known as 'aarch64' and implemented in the ARM CPU architecture 'v8'. Apart from iphones there is no publically available 64-bit silicon yet, but that'll be changing rapidly later this year and this port will

Bug#745259: ITP: apt-transport-tor -- APT transport for anonymous package downloads via Tor

2014-04-19 Thread Tim Retout
Package: wnpp Severity: wishlist Owner: Tim Retout * Package name: apt-transport-tor Version : 0.1 Upstream Author : Tim Retout * URL : https://github.com/diocles/apt-transport-tor * License : GPL Programming Lang: C++ Description : APT transport for a

Re: Proposing amd64-hardened architecture for Debian

2014-04-19 Thread Kevin Chadwick
previously on this list Michael Tautschnig contributed: > > Riding the Heartbleed publicity wave seems unwise, unless you can > > propose a hardening flag that would have protected users from > > Heartbleed. Else, Heartbleed merely serves on a example > > how wallpapering problems over with "harde

Re: Proposing amd64-hardened architecture for Debian

2014-04-19 Thread Michael Tautschnig
On Sat, Apr 19, 2014 at 14:26:59 +0300, Riku Voipio wrote: [...] > Riding the Heartbleed publicity wave seems unwise, unless you can > propose a hardening flag that would have protected users from > Heartbleed. Else, Heartbleed merely serves on a example > how wallpapering problems over with "harde

Re: Proposing amd64-hardened architecture for Debian

2014-04-19 Thread Bálint Réczey
Hi Riku, 2014-04-19 13:26 GMT+02:00 Riku Voipio : > On Tue, Apr 15, 2014 at 12:00:33PM +0200, Balint Reczey wrote: >> Facing last week's Heartbleed [1] bug the need for improving the >> security of our systems became more apparent than usually. In Debian >> there are widely used methods for Harden

Re: Proposing amd64-hardened architecture for Debian

2014-04-19 Thread Riku Voipio
On Tue, Apr 15, 2014 at 12:00:33PM +0200, Balint Reczey wrote: > Facing last week's Heartbleed [1] bug the need for improving the > security of our systems became more apparent than usually. In Debian > there are widely used methods for Hardening [2] packages at build time > and guidelines [3] for

Re: debconf reconfiguration from postinst of another package

2014-04-19 Thread Tollef Fog Heen
]] Jonas Smedegaard > How to reconfigure one package from another? I don't think this is supported today at all, and any success at doing so would be a bug. If you have a package that uses debconf as the UI to ask questions that go into a configuration file, that's fine. If you then later chan

RE:About a mass bug report not based on Sid or Jessie.

2014-04-19 Thread PICCA Frederic-Emmanuel
> It may be that libgc upstream's autogen.sh script is not really 'right' in > some way. But there may well be a lot of upstreams like that, which is > why maintainers need clear guidance on how to deal with this, without > having to become autotools experts. i.e how to determine when they can > ju