On Mon, 09 May 2016 at 06:47:38 +0200, Helmut Grohne wrote:
> In order for pkg-config to be "better" than your foo-config script, you
> need to tell it about the current host architecture by prefixing it with
> the triplet. Instead of calling pkg-config, you should be calling
> $DEB_HOST_GNU_TYPE-p
On Wed, Feb 10, 2016 at 11:03:04AM +0100, Bastien ROUCARIES wrote:
> On Wed, Feb 10, 2016 at 10:59 AM, Alastair McKinstry
> > In particular, for any non-standard variables, you can read them, by eg:
> >
> > f90_compiler=$(pkg-config mypkg --variable=f90_compiler)
> >
> > Its probably a good idea to
Package: wnpp
Severity: wishlist
Owner: Daniel Kahn Gillmor
* Package name: python-pytest-pep8
Version : 1.0.6
Upstream Author : Holger Krekel
* URL : http://bitbucket.org/hpk42/pytest-pep8/
* License : MIT
Programming Lang: Python
Description : py.tes
Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin
* Package name: geronimo-servlet-3.0-spec
Version : 1.0
Upstream Author : The Apache Software Foundation
* URL :
http://svn.apache.org/viewvc/geronimo/specs/tags/geronimo-servlet_3.0_spec-1.0/
* License
On Sun, 8 May 2016 16:40:22 +0200, Adam Borowski
wrote:
>On Sun, May 08, 2016 at 02:20:45PM +0200, Marc Haber wrote:
>> Tracking sid is a good idea if you can debug and fix breakages. If you
>> want to be warned for disruptions, use something that we actually
>> released.
>
>Another way is to use
* Andrew Shadura [160507 17:27]:
> Fingerprint readers are insecure, and that's something that can't be
> fixed. I'd prefer to see fewer fingerprint-related software packages
> in Debian rather than more.
I cringe when I see blanket statements like this from security
advocates. Instead of saying
On Sun, 2016-05-08 at 09:36 -0400, The Wanderer wrote:
> On 2016-05-08 at 09:09, Neil Williams wrote:
>
> >
> > On Sun, 08 May 2016 07:18:40 -0400 The Wanderer
> > wrote:
> >
> > >
> > > On 2016-05-08 at 03:45, Neil Williams wrote:
> > >
> > > >
> > > > On Sun, 8 May 2016 00:51:57 +0200 Pier
On Sun, May 08, 2016 at 09:00:12AM -0400, The Wanderer wrote:
> I agree, but I have seen people on debian-user advocating tracking sid
> by preference over testing as a recommended practice, even to the point
> of arguing against people who recommend otherwise. (Of whom I have seen
> fewer than I w
On Sun, May 08, 2016 at 02:20:45PM +0200, Marc Haber wrote:
> Tracking sid is a good idea if you can debug and fix breakages. If you
> want to be warned for disruptions, use something that we actually
> released.
Another way is to use btrfs (or zfs or perhaps LVM snapshots): whenever
something goe
On 2016-05-08 at 09:09, Neil Williams wrote:
> On Sun, 08 May 2016 07:18:40 -0400 The Wanderer
> wrote:
>
>> On 2016-05-08 at 03:45, Neil Williams wrote:
>>
>>> On Sun, 8 May 2016 00:51:57 +0200 Pierre Ynard
>>> wrote:
>>
>> Even if running unstable, I would certainly expect that something
>>
On Sun, 08 May 2016 07:18:40 -0400
The Wanderer wrote:
> On 2016-05-08 at 03:45, Neil Williams wrote:
>
> > On Sun, 8 May 2016 00:51:57 +0200 Pierre Ynard
> > wrote:
>
> Even if running unstable, I would certainly expect that something
> which is known to break certain types of systems this
On 2016-05-08 at 08:20, Marc Haber wrote:
> On Sun, 08 May 2016 07:18:40 -0400, The Wanderer
> wrote:
>
>> Even if running unstable, I would certainly expect that something
>> which is known to break certain types of systems this badly would
>> be announced at package install time, giving me a
On Sun, 08 May 2016 11:28:50 +0800, Paul Wise wrote:
> > Is there an effort to package fingerprint-GUI?
> Generally you can answer this by looking at wnpp bugs:
> https://www.debian.org/devel/wnpp/
> There is a search interface here:
> http://wnpp.debian.net/
Or from the command line:
% wnpp-che
On Sun, 08 May 2016 07:18:40 -0400, The Wanderer
wrote:
>Even if running unstable, I would certainly expect that something which
>is known to break certain types of systems this badly would be announced
>at package install time, giving me a chance to cancel the install... and
>the more so consider
Holger Levsen wrote:
> On Sun, May 08, 2016 at 10:44:29AM +0800, Paul Wise wrote:
>> d-d-a is mostly for developers, you might like to reach our users via
>> the Debian publicity team:
> running unstable is not for users who don't know how to deal with
> breakage. dealing with breakage involves r
On 2016-05-08 at 03:45, Neil Williams wrote:
> On Sun, 8 May 2016 00:51:57 +0200 Pierre Ynard
> wrote:
>> I was thinking more along the lines of adding some central check
>> in dpkg maybe, that detects the lack of i686 support and errors out
>> on new, incompatible packages. Discriminating packa
On Sun, May 8, 2016 at 6:21 PM, Holger Levsen wrote:
> running unstable is not for users who don't know how to deal with
> breakage. dealing with breakage involves reading d-d-a.
I was thinking to give users running affected hardware more warning
than reading the release notes in the next stable
On Sun, May 08, 2016 at 10:44:29AM +0800, Paul Wise wrote:
> d-d-a is mostly for developers, you might like to reach our users via
> the Debian publicity team:
running unstable is not for users who don't know how to deal with
breakage. dealing with breakage involves reading d-d-a.
--
cheers,
On Sun, 8 May 2016 00:51:57 +0200
Pierre Ynard wrote:
> > My recommendation would be going to jessie[1], it has whole four
> > years of support left. Anything you need from unstable can be
> > backported.
>
> Hopefully the downgrade path would be workable.
Backports can help with that - those
19 matches
Mail list logo
