Re: Why not 03 ?

2014-06-02 Thread Thomas Goirand
On 06/02/2014 05:07 AM, Julien Cristau wrote:
> For a lot of scientific packages, the upstream authors don't know what
> they're doing. So I'm not sure that's much of an argument.

[citation needed]

Also, it's easy to just play with the -O option and see what's faster.
So IMO, it's a package maintainer decision, and I can't see where
exactly we have an issue.

Thomas


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/538c2173.5070...@debian.org



Re: Why not 03 ?

2014-06-02 Thread Salvo Tomaselli

> What do we lose if we follow upstream's compiler options ?  As noted, the
> program may fail to build on other architectures than amd64.  I do not think
> that the unavailability of such non-core packages on other architectures is
> a problem (no user base), 
No, the problem is that it would compile just fine and then refuse to run, 
leading to (justified) bug reports.


-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1652010.TyemNprM1Y@hal9000



Bug#750158: general: cp -a does not respect file attributes

2014-06-02 Thread ecky
Package: general
Severity: serious
Justification: ?.?.?

Dear Maintainer,

   * What led up to the situation?
I installed a new bigger drive (array of 4 disks in raid5) and installed Debian
7.5 on this new drive. Then I wanted to copy files from the old drives that had
been running under Debian 6.0 to the new drive without compromizing new
configuration files that may be around in the new home directories.

   * What exactly did you do (or not do) that was effective (or ineffective)?
Therefore, as root, I issued the command "cp -anr  "

   * What was the outcome of this action?
All files were copied but the file attributes of the source-files were not
kept, all copied files belong now to root and permission-flags were reset to
the defaults of the root user.

   * What outcome did you expect instead?
I exspected that file attributes of the source-files are kept, notably
user,group and permission-flags as describet in the man-page for cp option -a.

*** End of the template - remove these lines ***



-- System Information:
Debian Release: 7.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602093542.32001.60993.report...@kurt.lewi.fr



Processed: Re: Bug#750158: general: cp -a does not respect file attributes

2014-06-02 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 coreutils
Bug #750158 [general] general: cp -a does not respect file attributes
Bug reassigned from package 'general' to 'coreutils'.
Ignoring request to alter found versions of bug #750158 to the same values 
previously set
Ignoring request to alter fixed versions of bug #750158 to the same values 
previously set
> severity -1 important
Bug #750158 [coreutils] general: cp -a does not respect file attributes
Severity set to 'important' from 'serious'

-- 
750158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b750158.1401697893499.transcr...@bugs.debian.org



Bug#750162: ITP: libdist-inkt-perl -- yet another distribution builder

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libdist-inkt-perl
  Version : 0.017
  Upstream Author : Toby Inkster 
* URL : https://metacpan.org/release/Dist-Inkt
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : yet another distribution builder

 Dist::Inkt itself does virtually nothing; it creates an empty
 directory, generates a MANIFEST file, and then wraps it all up into a
 gzipped tarball.  But it provides various hooks along the way for
 subclasses to grab hold of.  So the general idea is that you write a
 subclass of Dist::Inkt, which consumes various Moose::Roles to do the
 actual work of populating the distribution with files.
 .
 As such, Dist::Inkt is not so much a distribution builder, as it is a
 framework for writing your own distribution builder.
 .
 Several roles of varying utility are bundled with Dist::Inkt, as is
 Dist::Inkt::Profile::Simple, a subclass of Dist::Inkt which consumes
 most of these roles.

This package will be maintained in the Debian Perl Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjDnGXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWeHoH/ica9DLurhLkp6bddFgDN7PW
E6kAQkcUoEqBb/NnEQk3cgQUxRaCbCC0QRt1hmvN00PD7a23Dlpfo9sOL63weEaA
hxkPWG8rZk/zfD+eeN2sfraTggGTFVRgMM0PEKQDHHDr1DEkV5kSwKPMfCOOHeot
oomKgVl9Xtad6aCJedT4Hj3eX9O8A7m3FReWpwSSueb8CtyCHmk3upk0qdAZzJ1b
KTdciP4wPjyIuqOg4CAvPI14baXXoL5uOEXGUdoa1BQwn04Mk44/42bf83rLXik2
ZCQoyr3t/O+HlZHgWkKMKqkzO+ah6Xnvwe59Bwd2lkmCUUaaVb+Jx8HUbMzWg4M=
=Xd7d
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602084602.6325.98811.report...@bastian.jones.dk



Bug#750164: ITP: tempest -- OpenStack Integration Test Suite

2014-06-02 Thread Thomas Goirand
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: tempest
  Version : 1
  Upstream Author : OpenStack Development Mailing List 

* URL : https://github.com/openstack/tempest
* License : Apache-2.0
  Programming Lang: Python
  Description : OpenStack Integration Test Suite

 Tempest is a set of integration tests to be run against a live Openstack
 cluster in order to make sure that all components are working as expected.
 Tempest will start and stop virtual machine in order to check that your
 cloud is working as expected.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602090102.16491.39477.report...@buzig.gplhost.com



Bug#750169: ITP: librdf-doap-lite-perl -- write DOAP data quickly and easily

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: librdf-doap-lite-perl
  Version : 0.002
  Upstream Author : Toby Inkster 
* URL : https://metacpan.org/release/RDF-DOAP-Lite
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : write DOAP data quickly and easily

 RDF::DOAP::Lite is a small companion module to RDF::DOAP, enabling you
 to output DOAP data easily from standard CPAN distribution files.
 .
 DOAP (Description of a Project) is an RDF Schema and XML vocabulary to
 describe software projects, in particular free and open source
 software.

This package is needed by libdist-inkt-perl.
It will be maintained in the Debian Perl Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjEgbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWawUH/3AL2Xnt1yhof5FwWZP6TE3q
ov78YAAFkmO5rpHq05iWGjVaZ2hC1sV46SLb8ZdjjkAEXP301lU7t+r04JvkrKej
AjejoyYauSMA3ueAOKjSCgij62QRuQlaEM18twMNswnDftJnx2WH3n5c3acXoH7n
ICH5H+oTSrjtCFNB/i3kLW3BzKkks07PVSowULx3mQdrddUSwqVLW3hsOII1sMU4
17CjUf08Kv+iP8gYqUb625v7dZCjlANFjeCHUIcfDaHALA01PrLq+2XFtb6nQNg1
Z8LApChSUvdn8eumOjqdf6HVJeOHP95qkq+V3ylREzUwoMcK3QBqJJEgwiWNPiI=
=xRPy
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602094711.13600.67150.report...@bastian.jones.dk



Bug#750170: ITP: libpath-iterator-rule-perl -- iterative, recursive file finder

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libpath-iterator-rule-perl
  Version : 1.008
  Upstream Author : David Golden 
* URL : https://github.com/dagolden/Path-Iterator-Rule
* License : Apache-2.0
  Programming Lang: Perl
  Description : iterative, recursive file finder

 Path::Iterator::Rule  iterates over files and directories to identify
 ones matching a user-defined set of rules.  The API is based heavily on
 File::Find::Rule, but with more explicit distinction between matching
 rules and options that influence how directories are searched.  A
 Path::Iterator::Rule object is a collection of rules (match criteria)
 with methods to add additional criteria.  Options that control
 directory traversal are given as arguments to the method that generates
 an iterator.
 .
 Here is a summary of features for comparison to other file finding
 modules:
  * provides many "helper" methods for specifying rules
  * offers (lazy) iterator and flattened list interfaces
  * custom rules implemented with callbacks
  * breadth-first (default) or pre- or post-order depth-first searching
  * follows symlinks (by default, but can be disabled)
  * directories visited only once (no infinite loop; can be disabled)
  * doesn't chdir during operation
  * provides an API for extensions
 .
 As a convenience, the PIR module is an empty subclass of this one that
 is less arduous to type for one-liners.

This package is needed by libdist-inkt-perl.
It will be maintained in the Debian Perl Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjErXXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWzLwH/0Cp6isi2wSzX1TR8H0qPp2a
prTMLYrlXCmDEJv6blr4qVpnL5CAUBFz6SUZRRukV2HL+bcn9AQjVY5oFZ57Y4St
Ep/PD3KYlohw2SfaPCBA4H7NF9iQU0VS/fPKHQlQN15w3+ZFAfsV1bbx4nOXvV1l
22mvQygbQiGygKdDVHOJxThlNV1tUTVoFlw+4bDY6nD5OsQa/gqs2h0Verc9izfa
3kNW6oW5Qwh4pxHARnxaXPfCnRgtDLLs8RyFaBTOntWNtx4w7dQgnkFM5AWW9PLh
14MVFSmUdBYIjhsgMXzRqoaPc8gZRkYZ8U5jJOAnaq/sANZRZHB/FG/RIO+UbV8=
=0Wto
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602095847.15682.18180.report...@bastian.jones.dk



Bug#750174: ITP: libtest-filename-perl -- portable filename comparison

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libtest-filename-perl
  Version : 0.03
  Upstream Author : David Golden 
* URL : https://metacpan.org/release/Test-Filename
* License : Apache-2.0
  Programming Lang: Perl
  Description : portable filename comparison

 Many cross-platform test failures -- particularly on Win32 -- are due
 to hard-coded file paths being used in comparison tests.
 .
  my $file = get_file(); # returns "foo\bar.t";
  is( $file, "foo/bar.t" );  # fails on Win32
 .
 Test::Filename provides some handy functions to convert all those path
 separators automatically so filename tests will just DWIM.
 .
 The alternative is to write your own utility subroutine and use it
 everywhere or just keep on littering your test code with calls to
 File::Spec -- yuck!
 .
  is( $file, File::Spec->canonpath("some/path"), "should pass" );
 .
 Since this module is so simple, you might not think it worth including
 as a dependency.  After all, it's not that hard to always remember to
 use File::Spec, Path::Tiny or some other file utility, right? But odds
 are that, at some point, you'll be so busy writing tests that you'll
 forget and hard-code a path in your haste to show what a clever
 programmer you are.
 .
 So just use this module and stop worrying about it.  You'll be happier
 and so will anyone trying to install your modules on Win32.

This package is needed by libpath-iterator-rule-perl and
libdist-inkt-perl.
It will be maintained in the Debian Perl Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjFYcXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW4l0IAIaz3dnvgBxVsWa3rMFzmAej
rTtYgZ04Z/dvmvBtZ8KLcwzBi/gEb5MiJuX8c1HEjPCAZLGZ6MuV1opb87ZVqBb2
lN+wxqt/YcdCPdSQZmjhksqcBTaeigohePPg0f58PbAvxkrZwlzTfFEtpKVCqnur
lLPOR47fokIjjzwZ7jZ7h1IoMUPlkEygwvjDCtlScuEIJDLlUd2Dc3Fg0vX+vsbW
ZFJO1ghvu9JAX0wc1M9bjmP62QNNx8wv2FpApAoC+mxzGDAfLICaB8CTx1P5vB6H
Ra9IgHdQjqHO60GRfFs8Xdy8GnC36LlxTikcDLQvE7/cg+OUvyUfxM1QMc6GuII=
=E1od
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602104656.30429.33133.report...@bastian.jones.dk



Bug#750180: ITP: libdist-inkt-doap-perl -- various DOAP-related roles for Dist::Inkt

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libdist-inkt-doap-perl
  Version : 0.017
  Upstream Author : Toby Inkster 
* URL : https://metacpan.org/release/Dist-Inkt-DOAP
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : various DOAP-related roles for Dist::Inkt

 Dist::Inkt::DOAP provides various DOAP-related roles for Dist::Inkt.
 .
 Dist::Inkt is a distribution builder - or more accurately a framework
 for writing your own distribution builder.

This package improves usability of libdist-inkt-perl.
It will be maintained in the Debian Perl Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjGT4XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vW3oEIAIZi8urJEt7ThfaqfYLIDCBH
EJ4c76Yo3jFZ5kX9HxYV+Y4//0BI7kmdlfSXVkwjX87ASpddfZbzsfcAewxPmZdC
O1H+NJJkQ/BXpdhc+TjH4XEmLtoQaFLvxtLNldsOiyMIOt4JIpbxdJoJtigBVE0b
CSOgbmOLRJpsQ3sB+DrfDwU4naiYOzU7ptozdLm01Qjm88gKgTKiOdT13aNq+4a5
d6hTkijnEOx6EuRuFnBW+o9NEaXjzdiwxKVkBiaMRhBgGsyWexR3gDg2jDknTc0w
kvBfvQ7EqXYmHXY8XVTZ6RNeg+S6uJJihb7ZjU6BWoCfJBP152UhTcuuhxngxhk=
=BEKY
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602115016.31556.78924.report...@bastian.jones.dk



Bug#750181: ITP: librdf-doap-perl -- object-oriented interface for DOAP data

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: librdf-doap-perl
  Version : 0.010
  Upstream Author : Toby Inkster 
* URL : https://metacpan.org/release/RDF-DOAP
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : object-oriented interface for DOAP data

 RDF::DOAP provides classes to parse and build DOAP data.
 .
 DOAP (Description of a Project) is an RDF Schema and XML vocabulary to
 describe software projects, in particular free and open source
 software.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjGqxXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWLwwH/i5+f92MiOpG6JXlwAGNbarF
KUWjs3sW0ooRLdphzqch2szNt880dx0mWqMjafF2YBZx/NHS80rht0nvSmwccwxI
ax3fN3TIMuvfqQ2ut6/Pnfq0byBu/UTL3TBmA7jxGuBdwlm+fGqKeAZtB1VwCt2k
rljU7wOVLpLCz97NBXGcF5DC9n8NlHPTeQXxxMz2tLT8WysnBkg/G/XOhnhx0NTF
vEPN/+rebZfIkO78IV1nUgwDuz71snY4cEPZ+91+vaKuUG1i7OlW7G6oxR6iQf/f
AMOZBXmvX3UQqKNiE+/6NPIbvkMkOEQ+lKPgHGeS0aJi4i9ckFyLRTxtIOkrLs8=
=eVB0
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602121442.2246.55378.report...@bastian.jones.dk



Bug#750190: ITP: libmoosex-attributetags-perl -- tag your Moose attributes

2014-06-02 Thread Jonas Smedegaard
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libmoosex-attributetags-perl
  Version : 0.001
  Upstream Author : Toby Inkster 
* URL : https://metacpan.org/release/MooseX-AttributeTags
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : tag your Moose attributes

 MooseX::AttributeTags is a factory for attribute traits.

This package is needed by librdf-doap-perl.
It will be maintained in the Debian Perl Team.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQF8BAEBCgBmBQJTjG33XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWWWMH/1dRWyouUj2NNf7cM/br8H5M
BwYP0OQwml6XtfiKINXPyaK9X4pEes0r0rWoYC37AhFAkiPB3hpLmrJ8caHuyU39
bhV3BLa6huN12GlZsOA6Bp10Qf+oY1Tic84T9CEQw3RSVqKuTJFmN8rZm9kK0wVj
Ba0YVETC7vN+LRsDw/9Pu7F74VIcMoaInGRTbdr6EnfBX6Mck2eqreFnmQCVvDJF
eYHdhGLN/yYitdW7JPfYOWzh61qg7qBSLvObm+9BaXJZQEO2YVYR2c4JGFEMi7gw
PlA14JofmVnLEoOdsjBQr0oaoj8QxSoB+ELfPptr3iGH+t3vh4ylHWunZ8umfRc=
=Cqzt
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140602122839.4135.87286.report...@bastian.jones.dk



Re: Why not 03 ?

2014-06-02 Thread Henrique de Moraes Holschuh
On Mon, 02 Jun 2014, Thomas Goirand wrote:
> On 06/02/2014 05:07 AM, Julien Cristau wrote:
> > For a lot of scientific packages, the upstream authors don't know what
> > they're doing. So I'm not sure that's much of an argument.
> 
> [citation needed]
> 
> Also, it's easy to just play with the -O option and see what's faster.

As long as you have a way to regression-test.  And I don't mean performance
regressions, either.  Although issues with -O3 are rare, they're not unheard
of.  And all bets are off when the C code has undefined behavior.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140602133601.ga25...@khazad-dum.debian.net



Re: Why not 03 ?

2014-06-02 Thread Xavier Roche
On Mon, Jun 02, 2014 at 10:36:01AM -0300, Henrique de Moraes Holschuh wrote:
> As long as you have a way to regression-test.  And I don't mean performance
> regressions, either.  Although issues with -O3 are rare, they're not unheard
> of.

Looking at the `man gcc' page, I fail to see, outside compiler bugs, what could 
cause issues at 03 vs. O2.

I have the feeling that most "dangerous" (ie. breaking dirty code, or code 
using non-specified C behavior) features are already on O2:
  * -fstrict-aliasing (code aliasing the same pointer wirh a different type)
  * -fstrict-overflow (signed arithmetic overflow being undefined)

Outside architecture issues, such as "will produce bytecode unsupported by old 
processors", what typical optimizations can harm us at O3 ?


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140602165606.GA14725@proliant.localnet



Re: Why not 03 ?

2014-06-02 Thread Henrique de Moraes Holschuh
On Mon, 02 Jun 2014, Xavier Roche wrote:
> On Mon, Jun 02, 2014 at 10:36:01AM -0300, Henrique de Moraes Holschuh wrote:
> > As long as you have a way to regression-test.  And I don't mean performance
> > regressions, either.  Although issues with -O3 are rare, they're not unheard
> > of.
> 
> Looking at the `man gcc' page, I fail to see, outside compiler bugs, what 
> could cause issues at 03 vs. O2.

It is a moving target.

For GCC 4.9:
-O3 turns on all optimizations specified by -O2 and also turns on the:
-finline-functions, -funswitch-loops, -fpredictive-commoning,
-fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize,
-fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.

For GCC 4.7:
-O3 turns on all optimizations specified by -O2 and also turns on the:
-finline-functions, -funswitch-loops, -fpredictive-commoning,
-fgcse-after-reload, -ftree-vectorize and -fipa-cp-clone options.

And compiler bugs _are_ an issue.  Which is why testing done on an
optimization level is not strictly valid for other optimization levels.  You
can ignore this, but it may eventually bite you (especially on less common
arches and optimization modes).

> I have the feeling that most "dangerous" (ie. breaking dirty code, or code 
> using non-specified C behavior) features are already on O2:
>   * -fstrict-aliasing (code aliasing the same pointer wirh a different type)
>   * -fstrict-overflow (signed arithmetic overflow being undefined)

Optimizations related to memory reuse are _always_ a bit dangerous to enable
blindly on anything that has complex signal handlers, needs to be able to
"secure clobber" memory, implements multithreading syncronization directly,
etc.

> Outside architecture issues, such as "will produce bytecode unsupported by
> old processors", what typical optimizations can harm us at O3 ?

All of the optimizations in -O3 are known to be harmful[1] in certain
situations, otherwise they'd be in the -O2 set in the first place.

Fortunately, only compiler bugs and code with undefined behaviour will cause
incorrect program behaviour [unrelated to performance] when you change among
-Os,-Og,-O0,-O1,-O2,-O3.


[1] supposedly they are only possibly harmful to performance.  When it
causes miscompiling, it is a bug.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140602174106.ga2...@khazad-dum.debian.net



bootlogd fills up entire disk eventually

2014-06-02 Thread 積丹尼 Dan Jacobson
severity 725120 critical
version 725120  2.88dsf-55
forcemerge 725120 743001
forcemerge 725120 724712
thanks
The logs finally got so big,
never getting rotated,
that they filled up the disk,
rendering the ENTIRE SYSTEM unusable!


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87wqcyr4ab@jidanni.org



Bug#750396: ITP: python-ldap3 -- A strictly RFC 4511 conforming LDAP V3 pure Python client

2014-06-02 Thread Brian May
Package: wnpp
Severity: wishlist
Owner: Brian May 

* Package name: python-ldap3
  Version : 0.9.3.3
  Upstream Author : Giovanni Cannata 
* URL : https://pypi.python.org/pypi/python3-ldap
* License : GPLv3
  Programming Lang: Python
  Description : A strictly RFC 4511 conforming LDAP V3 pure Python client

Please correct me if I got something wrong.

I believe that python-ldap, already in Debian does not support python3.
I see emails from April 2012 stating people are working on Python 3 support,
but nothing since. So I can only assume that this has stalled.

http://comments.gmane.org/gmane.comp.python.ldap/1078

This library, known as python3-ldap upstream, provides the ldap3 module.
It is claimed it works with Python 2 and Python 3.

This library has the advantage that it is pure Python code, I believe
this means it doesn't require the C ldap library.

I am considering naming the source python-ldap3, which is different from
the upstream name, as it works with both python 2 and python 3, and it
supplies the ldap3 module, not the ldap module. So it shouldn't conflict
with the existing python-ldap package.  If I know what I am doing, it
will provide the python-ldap3 and python3-ldap binary packages.

I haven't yet tried to use python-ldap3, so I assume the claims made
upstream are accurate. The API looks somewhat different, although I
haven't examined it in detail yet.

Unfortunately, don't have a good test for this yet, my application
uses the python-ldap API. I guess this will have to be updated too.


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20140603060405.11320.84794.report...@aquitard.in.vpac.org