Ansgar Burchardt writes:
> the host for the security upload queue changed. The new location is
>
> ftp://ftp.security.upload.debian.org/pub/SecurityUploadQueue
For some reason I can't upload to this host (or the old one) from my
network without disabling IPv6 first (by overriding the IP addre
On Tue, Oct 10, 2017 at 3:05 PM, Matthias Klose wrote:
> On 10.10.2017 12:38, Mathieu Malaterre wrote:
>> Mathias,
>>
>> On Tue, Oct 10, 2017 at 12:25 PM, Matthias Klose wrote:
>>> On 10.10.2017 11:42, Mathieu Malaterre wrote:
On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote:
> On
Package: wnpp
Severity: wishlist
Owner: Mike Gabriel
* Package name: mate-window-applets
Version : 1.5
Upstream Author : IKRadulov (https://github.com/IKRadulov)
* URL : https://github.com/IKRadulov/mate-window-applets
* License : GPL-3+
Programming Lang: Val
On Tue, Oct 10, 2017 at 05:36:47PM +0100, Dimitri John Ledkov wrote:
On 10 October 2017 at 14:26, Michael Stone wrote:
On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote:
On 10 October 2017 at 14:07, Gert Wollny wrote:
I think nobody would object if you set the flag to -st
On 10 October 2017 at 14:26, Michael Stone wrote:
> On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote:
>>
>> On 10 October 2017 at 14:07, Gert Wollny wrote:
>>>
>>> I think nobody would object if you set the flag to -std=c++98 for a
>>> certain package, especially if upstream is
Package: wnpp
Severity: wishlist
Owner: Preyass Chandran
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-protoduck
Version : 4.0.0
Upstream Author : Kat Marchán
* URL : https://github.com/zkat/protoduck#readme
* License : CC0-1.0
Programming
On Tue, Oct 10, 2017 at 02:16:36PM +0100, Dimitri John Ledkov wrote:
On 10 October 2017 at 14:07, Gert Wollny wrote:
I think nobody would object if you set the flag to -std=c++98 for a
certain package, especially if upstream is dead or unwilling to move to
a newer standard, but I wouldn't want
On 10 October 2017 at 14:07, Gert Wollny wrote:
> Hello Mathieu,
>
> Am Dienstag, den 10.10.2017, 11:45 +0200 schrieb Mathieu Malaterre:
> [...]
> I don't think there is much to gain from it. Whenever there is a
> change
>> > in the major version of gcc/g++ many bugs show up and all involved
>> >
On 10 October 2017 at 07:45, Mathieu Malaterre wrote:
> Dear all,
>
> Since the GCC 6 release [1], the default mode for C++ is now
> -std=gnu++14 instead of -std=gnu++98. What this means is that upon
> (re)compilation a library written for c++98 will be recompiled using a
> different c++ standard
Hello Mathieu,
Am Dienstag, den 10.10.2017, 11:45 +0200 schrieb Mathieu Malaterre:
[...]
I don't think there is much to gain from it. Whenever there is a
change
> > in the major version of gcc/g++ many bugs show up and all involved
> > really do a great job fixing these. IMHO switching from an ol
On 10.10.2017 12:38, Mathieu Malaterre wrote:
> Mathias,
>
> On Tue, Oct 10, 2017 at 12:25 PM, Matthias Klose wrote:
>> On 10.10.2017 11:42, Mathieu Malaterre wrote:
>>> On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote:
On 10.10.2017 08:45, Mathieu Malaterre wrote:
> Dear all,
>>>
On Tue, Oct 10, 2017 at 12:38:03PM +0200, Mathieu Malaterre wrote:
As with Gert's answer, I fail to understand your point: You would
prefer to see packages being (re)compiled *without* an explicit -std=
flag, so that it always gets recompiled using whatever is the current
c++ standard used by gcc
Mike Gabriel schrieb am Tuesday, dem 10. October 2017:
> So, indeed the
> question is, why DSA cannot provide a VM or physical machine to a group of
> DDs and trust this group regarding the server maintenance?
DSA is not in the business of p
Mathias,
On Tue, Oct 10, 2017 at 12:25 PM, Matthias Klose wrote:
> On 10.10.2017 11:42, Mathieu Malaterre wrote:
>> On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote:
>>> On 10.10.2017 08:45, Mathieu Malaterre wrote:
Dear all,
Since the GCC 6 release [1], the default mode for
On 10.10.2017 11:42, Mathieu Malaterre wrote:
> On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote:
>> On 10.10.2017 08:45, Mathieu Malaterre wrote:
>>> Dear all,
>>>
>>> Since the GCC 6 release [1], the default mode for C++ is now
>>> -std=gnu++14 instead of -std=gnu++98. What this means is t
Hi Gert !
On Tue, Oct 10, 2017 at 11:31 AM, Gert Wollny wrote:
> Am Dienstag, den 10.10.2017, 08:45 +0200 schrieb Mathieu Malaterre:
>
> [...]
> With this mind I'd like to make mandatory the -std=c++XY flags when
>> compiling either a c++ library or a stand-alone c++ program:
>>
>> 1. Either upst
On 10.10.2017 08:45, Mathieu Malaterre wrote:
> Dear all,
>
> Since the GCC 6 release [1], the default mode for C++ is now
> -std=gnu++14 instead of -std=gnu++98. What this means is that upon
> (re)compilation a library written for c++98 will be recompiled using a
> different c++ standard (c++14 i
On Mo 18 Sep 2017 13:34:49 CEST, Dominic Hargreaves wrote:
On Mon, Sep 18, 2017 at 09:22:34AM +, Holger Levsen wrote:
On Mon, Sep 18, 2017 at 01:57:31AM +0100, peter green wrote:
> Just because a team isn't big or established doesn't mean they
don't need a place to discuss issues relatin
On Tue, Oct 10, 2017 at 11:38 AM, Matthias Klose wrote:
> On 10.10.2017 08:45, Mathieu Malaterre wrote:
>> Dear all,
>>
>> Since the GCC 6 release [1], the default mode for C++ is now
>> -std=gnu++14 instead of -std=gnu++98. What this means is that upon
>> (re)compilation a library written for c++
Am Dienstag, den 10.10.2017, 08:45 +0200 schrieb Mathieu Malaterre:
[...]
With this mind I'd like to make mandatory the -std=c++XY flags when
> compiling either a c++ library or a stand-alone c++ program:
>
> 1. Either upstream define the explicit -std=c++XY flags by mean of
> its build system,
>
Ansgar,
On Tue, Oct 10, 2017 at 9:17 AM, Mathieu Malaterre wrote:
> Ansgar,
>
> On Tue, Oct 10, 2017 at 9:11 AM, Ansgar Burchardt wrote:
>> Mathieu Malaterre writes:
>>> With this mind I'd like to make mandatory the -std=c++XY flags when
>>> compiling either a c++ library or a stand-alone c++ pr
[continued]
On Tue, Oct 10, 2017 at 9:11 AM, Ansgar Burchardt wrote:
> Mathieu Malaterre writes:
>> With this mind I'd like to make mandatory the -std=c++XY flags when
>> compiling either a c++ library or a stand-alone c++ program:
>>
>> 1. Either upstream define the explicit -std=c++XY flags by
On Tue, Oct 10, 2017 at 09:12:45AM +0200, Mathieu Malaterre wrote:
> > lintian doesn't scan build logs, it scans source and binary packages.
>
> Right. I always forgot that. What is the mechanism used for
> shlib-calls-exit, does it rely on source parsing ?
No, it just looks at the imported symbol
Ansgar,
On Tue, Oct 10, 2017 at 9:11 AM, Ansgar Burchardt wrote:
> Mathieu Malaterre writes:
>> With this mind I'd like to make mandatory the -std=c++XY flags when
>> compiling either a c++ library or a stand-alone c++ program:
>>
>> 1. Either upstream define the explicit -std=c++XY flags by mean
On Tue, Oct 10, 2017 at 9:05 AM, Julien Cristau wrote:
> On Tue, Oct 10, 2017 at 08:45:49 +0200, Mathieu Malaterre wrote:
>
>> Dear all,
>>
>> Since the GCC 6 release [1], the default mode for C++ is now
>> -std=gnu++14 instead of -std=gnu++98. What this means is that upon
>> (re)compilation a lib
Mathieu Malaterre writes:
> With this mind I'd like to make mandatory the -std=c++XY flags when
> compiling either a c++ library or a stand-alone c++ program:
>
> 1. Either upstream define the explicit -std=c++XY flags by mean of its
> build system,
> 2. Or the package maintainers needs to explicit
On Tue, Oct 10, 2017 at 08:45:49 +0200, Mathieu Malaterre wrote:
> Dear all,
>
> Since the GCC 6 release [1], the default mode for C++ is now
> -std=gnu++14 instead of -std=gnu++98. What this means is that upon
> (re)compilation a library written for c++98 will be recompiled using a
> different c
27 matches
Mail list logo
