Re: systemd-fsck?
> As far as I have read in this thread, the only reported problem with > upgrading from sysv to systemd concerns remote virtual machines that > won't boot. As I said earlier: some bits of my log entries are getting discarded by journald. -- 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/21221428.hoSJR14PtD@hal9000
Re: Redefining critical bug severity
On Sat, May 17, 2014 at 01:02:08PM -0700, Manoj Srivastava wrote: > > Over the years, I've seen endless confusion about the current definition > > of a critical bug severity: Totally agree. > > makes unrelated software on the system (or the whole system) break, or > > causes serious data loss, or introduces a security hole on systems > > where you install the package. > > > The confusion seems to always be around the "unrelated software" part of > > that definition. The intended meaning is completely unrelated software on > > the system, indicating a package that's mangling the system in some > > fundamental way, but I've frequently seen people believe, sincerely, that > > reverse dependencies, Perl programs that use a buggy module, or X programs > > on a system with a buggy video driver qualify as unrelated software. > > > This makes me think that part of the bug definition is adding more > > confusion than clarity. Should we just drop it? > Could this explanation instead be added as an informative > footnote? Packages that declrare a direct or indirect dependency are > not unrelated? Yes please. Dropping the option altogether seems worse idea than adding an explanation. -- WBR, wRAR signature.asc Description: Digital signature
Re: preparing for GCC 4.9 (bug squashing on May 16/17)
On Tue, May 13, 2014 at 02:56:39PM +0200, Matthias Klose wrote:
> With gcc-4.9 now available in testing, it is time to prepare for the change of
> the default to 4.9, for a subset of architectures or for all (release)
> architectures. The defaults for the gdc, gccgo, gcj and gnat frontends
> already
> point to 4.9 and are used on all architectures. Issue #746805 tracks the
> gfortran default change, including the change of the Fortran 90 module
> version.
>
> An email a week ago to debian-{release,ports} [1] didn't show any obvious
> blockers, and various test rebuilds don't show at least any internal compiler
> errors anymore.
>
> The Debian archive was rebuilt twice on amd64, once in February, resulting in
> bug submissions for GCC and feedback for the porting guide [2], a second time
> in
> March to file issues for packages failing to build with GCC 4.9 [3]. Another
> test rebuild for mips64 didn't show any additional build failures [4]. Another
> test rebuild for Ubuntu on amd64, i386, armhf, ppc64el didn't show any other
> compiler regressions on these architectures.
>
> I'll work on fixing the build failures in [3], help is of course appreciated.
> Trying to be online on May 16/17 on IRC #debian-toolchain (OFTC) and uploading
> packages to the delayed queue.
>
> Almost all build failures are analysed and should be easy to fix (exceptions
> e.g. #746883). Patches for the ones not caused by the Debian packaging may be
> found in distributions already using GCC 4.9 as the default compiler (e.g.
> Fedora 21).
>
> If anything goes well, and a large amount of build failures are fixed, I plan
> to
> make GCC 4.9 the default for the C/C++/ObjC/Obj-C++ frontends at the end of
> May,
> beginning of June.
>
> Bugs reports for packages building with a legacy version of GCC (4.6, 4.7) are
> filed [5] [6], and will be filed for 4.8 once 4.9 is the default.
There is a gcc 4.8.2 bug that currently prevents iceweasel 29 to build
on armhf, and it appears this bug is fixed in 4.9. Is it fine to build
depend on 4.9?
Mike
--
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/20140518091700.ga14...@glandium.org
Bug#748556: general: Power Off does not work
Package: general Severity: normal Dear Maintainer, Since update/upgrade of Jessie on or about 14th May:- Select menu "Power Off" - dialogue Cancel/Restart/PowerOff appears. Select "Power Off" very little appears to happen all tasks continue to run and new tasks can be started. Enter "shutdown now" command - system closes down and stops - shows "INIT_ no more processes left in this runlevel". Does not power down Running uGet to download files overnight with option to "Shutdown when complete" appears to do the right thing and the system is powered off in the morning. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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/20140518111517.5093.56931.reportbug@jupiter2.priorycomputers.local
Re: how to deal with a missed so bump already uploaded ?
On Sat, May 17, 2014 at 01:18:29PM +0200, Julien Cristau wrote: > On Sat, May 17, 2014 at 12:42:10 +0200, Alessandro Ghedini wrote: > > > Note that e.g. haskell-zeromq4-haskell already requires zeromq 4.x to > > build, and > > others (python-zmq, hbro, ...) depend on libzmq3 >= 4.0.1, so zeromq4 > > should be > > packaged first, those packages updated to build depend on libzmq4-dev and > > then > > zeromq3 re-uploaded with the old version. The other reverse build-deps of > > zeromq3 should probably be binNMUed as well once that's done to get the > > proper > > build-time macros. > > > Is there any chance we can avoid shipping 3 different zeromq versions? Well, if libtango is updated to the new behaviour, zeromq3 can probably be removed (assuming no other package is broken). Or maybe the old behaviour can be made available using a flag or something in zeromq4. As for zeromq (zeromq 2.x) the only real reverse depends is libzeromq-perl but that's not a leaf package either. This should be discussed with the zeromq maintainer though (and possibly upstream), but he hasn't responded to the bug report or this discussion yet. Cheers signature.asc Description: Digital signature
Bug#748556: general: Power Off does not work
Am 18.05.2014 13:15, schrieb prioryc: > Package: general > Severity: normal > > Dear Maintainer, > > Since update/upgrade of Jessie on or about 14th May:- > Select menu "Power Off" - dialogue Cancel/Restart/PowerOff appears. > Select "Power Off" very little appears to happen all tasks continue to run and > new tasks can be started. Which desktop environment is this? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#748562: ITP: execpermfix -- Fixes executable permissions
Package: wnpp Severity: wishlist Owner: Leandro Lisboa Penz * Package name: execpermfix Version : 1.0.5 Upstream Author : Leandro Lisboa Penz * URL : http://github.com/lpenz/execpermfix * License : GPL-2 * Programming Lang: C Description : Fixes executable permissions execpermfix sets or resets the executable permission bit of a file based on its contents: ELF header and shebang. The permission given is synchronized with the read permission. That's useful when unpacking files from compression formats or network transmission protocols that do not support execution permission meta-information. It can also be used to synchronize the execution permission with the read permission. I will maintain it in collab-maint. I already have a sponsor. -- 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/20140518133300.5665.32910.report...@leandro.penz
Unidentified subject!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi all Have you read about Encrypted Media Extensions (EME)? See: https://u.fsf.org/xk I think next releases of Iceweasel should be build *without* EME and any other DRM-related stuff. -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJTeNlPAAoJEAkexyki2U7qm4EH/0aEDp/hLHd8OCL8Wk/3ZYSs zD407Sm29pN4wngaCPy6FdLTJjkyLCnwRlMCzWk9lmpPkS4MsA7scSgfclGBU007 Qv3Sucd9BG4zVevl+F/DJy24KEqFcexrpaiQVyeUNlHRksBfjnWw64X8g7BJ97FD XR4LbYIXLQdoY9fmuGbSgj5yHw88au8ZF/m8DYb8OoMOKD87dbRHb1+OP6hLTUTb K7t4dPqa4lTgBSxsmU3fW5EugU8Qt8AFP2xkxbPpAHGyihvgtDvkbPAfR+IiJE30 /dWXRMmaR5CHjkU/Yb4pWgO8Z7JmpN7HoA3gBT0soNeuRU5fZaWC1fZbQKorTgI= =4z6P -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/5378d94f.8020...@me.com
Bug#748581: ITP: libmoox-configfromfile-perl -- Moo extension for initializing objects from config file
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: libmoox-configfromfile-perl Version : 0.002 Upstream Author : Jens Rehsack * URL : https://metacpan.org/release/MooX-ConfigFromFile * License : Artistic or GPL-1+ Programming Lang: Perl Description : Moo extension for initializing objects from config file MooX::ConfigFromFile is intended to easy load initialization values for attributes on object construction from an appropriate config file. The building is done in MooX::ConfigFromFile::Rule - using MooX::ConfigFromFile ensures the role is applied. This module is needed by recent releases of libmoox-options-perl. It will be maintained in the Debian Perl team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJTeNkSXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWbXYIAJRC7d7FDCDQZmO2mNOqkE/3 IpRlt5OMxxcuwSy1lU/hqhisxMea9Bo1wcycJc9Y3FKAp9nnUecQpv88eFeYoBly X1VkB7ZmxNR7Z38xOZGmtn7Lssiwoxye4GObl4sVYb118Eahb/BWnWSXYN59eohD TICjmjM6zNVtc12iqeZukZ3bHddcjDehND1P16PGl6iVfCy4vDnk0eJQ/5wNcCXj 6C6xRcjJakgkqzA92YYSQMErw6SCcttlTqjRl0tccxLQgpZoFACTvAwxxw6mMYd8 ZS9nCIvwsgErTUORliZnZqsJVpRnbo6XV8L6+1NHdhpL+shoMWVZg7T4n0UoBpc= =aYrs -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/20140518160021.27184.63565.report...@bastian.jones.dk
Bug#748582: ITP: libmoox-file-configdir-perl -- Moo extension for File::ConfigDir
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: libmoox-file-configdir-perl Version : 0.003 Upstream Author : Jens Rehsack * URL : https://metacpan.org/release/MooX-File-ConfigDir * License : Artistic or GPL-1+ Programming Lang: Perl Description : Moo extension for File::ConfigDir MooX::File::ConfigDir is a helper for easily find configuration file locations. Whether to use this information for find a suitable place for installing them or looking around for finding any piece of settings, heavily depends on the requirements. This module is needed (indirectly) by recent releases of libmoox-options-perl. It will be maintained in the Debian Perl team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJTeNzVXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWJhYIAJxp5ZTuOriapPBFgIqnFCVb XKg2D+rGe7wmsfgUdyI7IHOIkatfBFgvV7X+SsMY7y1l+PpRR7T1rMThGMSAP7ZW reHJnsTZDkweLCSqHe5bvrNLLVjpcM7/jvITouF0pPWzEA53BSJaq9VwNS4mjdwS AGuHy48+XyB6r32O88yL5VxzevXO5PKdmzFaHzo7wR5F6/Kpa/mXbXO3FX3m5o36 Ah7st3AfciSfWkWmKUvmhYIUmO8EqibYWvLAQ+847LCsFkCNzdMEoD5qkpbseX6q 8lzQ2zSUngEt4y2GugPXCtW9GITbbBedIPvE0tAp8CdwDj9aoPD/EWDPmCpdDKU= =SyTC -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/20140518161625.28271.77708.report...@bastian.jones.dk
Bug#748583: ITP: get directories of configuration files -- get directories of configuration files
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: get directories of configuration files Version : 0.013 Upstream Author : Jens Rehsack * URL : https://metacpan.org/release/File-ConfigDir * License : Artistic or GPL-1+ Programming Lang: Perl Description : get directories of configuration files File::ConfigDir is a helper for installing, reading and finding configuration file locations. It's intended to work in every supported Perl5 environment and will always try to Do The Right Thing(tm). This module is needed (indirectly) by recent releases of libmoox-options-perl. It will be maintained in the Debian Perl team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJTeN/zXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWGm0H/jfTRYDwEeFKLBok7azMQVL/ 9JtPSMHV5Brtbu0zHrdvmBIp+BhAIh7IrDQ3hxAwjLbOsxVcBsVfI1L1ejxhZWYo AolQGuv5sI8Ff2CbDa7Fkv1aC1sitVsgXL956kL/+XI5bb6xxzLZDFgGhDbso7ci xqJy53X2UW/T5xV1n/+d8+pZWq7AWtVAUtTtydPzToyZuEq6p1ES5P56ROSbCfl2 NLZIBt8SsulbUwm58w8e/hepgf+9W7EOsGCUgzJ3XHxfM9egzEwO76q4vF+R9atr jkRbRExOMy2HEW3axcbVDbmyo2B84zGzaIkTxk0GdBEGS1JGrncSXvOM7ddRCso= =e6E2 -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/20140518162939.29411.28327.report...@bastian.jones.dk
Bug#748610: ITP: node-lodash -- node-lodash
Package: wnpp Severity: wishlist Owner: Matthew Pideil * Package name: node-lodash Version : 2.4.1 Upstream Author : John-David Dalton * URL : http://lodash.com/ * License : expat Programming Lang: js Description : Lo-dash is a Node.js utility library Lo-dash is a Node.js utility library delivering consistency, customization, performance, & extras. Sponsored by the pkg-javascript-team -- 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/20140518203946.26841.42363.reportbug@pcplat68.interne-mtd
Re: Unidentified subject!
On Mon, May 19, 2014 at 12:01 AM, Solal wrote: > I think next releases of Iceweasel should be build *without* EME and > any other DRM-related stuff. Iceweasel is not available on MacOS X, which you appear to be using. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6hfqt3ewtfvqk8vlkubkwn4qjoddlcad50pjhioz6t...@mail.gmail.com
