Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Emilio Pozuelo Monfort
On 27/06/17 07:04, Bastian Blank wrote: > On Mon, Jun 26, 2017 at 11:47:53PM +0200, Emilio Pozuelo Monfort wrote: >> Btw I just fixed these: >> ekiga-dbg_4.0.1-6+b5/postinst >> ekiga-dbg_4.0.1-6+b5/postrm >> ekiga-dbg_4.0.1-6+b5/preinst > > While you are at it, please convert these to automatic de

Re: IMPORTANT: Do live Debian images have a future?

2017-06-26 Thread Mechtilde
Hello Steve, thanks for your work on this task. I myself use it from time to time to show how Debian can looks like without installing at the target machine. So I have USB Sticks with me (with the inofficial non-free image). Kind regards Mechtilde Am 26.06.2017 um 16:08 schrieb Steve McIntyre

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Paul Wise
On Tue, Jun 27, 2017 at 4:23 AM, Ralf Treinen wrote: > we currently have in sid 84 maintainer scripts not using strict mode. > That is, they neither start on "#!/bin/[ba]sh -e", nor do a "set -e". > The list is attached. This list includes the 12 remaining scripts not > starting on #! (bugs are al

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Bastian Blank
On Mon, Jun 26, 2017 at 11:47:53PM +0200, Emilio Pozuelo Monfort wrote: > Btw I just fixed these: > ekiga-dbg_4.0.1-6+b5/postinst > ekiga-dbg_4.0.1-6+b5/postrm > ekiga-dbg_4.0.1-6+b5/preinst While you are at it, please convert these to automatic debug symbol packages. This can be done by just rem

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Paul Wise
On Tue, Jun 27, 2017 at 6:37 AM, Christoph Biedl wrote: > Let's be honest: Shell scripts, while easy to write, carry too many > risks of unsafe programming. So while your proposed fixing is a step in > the right direction, this is all just band-aid. We (as in Debian) should > look forward and try

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Johannes Schauer
Hi, Quoting Christoph Biedl (2017-06-27 00:37:33) > Let's be honest: Shell scripts, while easy to write, carry too many risks of > unsafe programming. So while your proposed fixing is a step in the right > direction, this is all just band-aid. We (as in Debian) should look forward > and try to rep

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Henrique de Moraes Holschuh
(updates, hopefully the last ones...) On Sun, 25 Jun 2017, Henrique de Moraes Holschuh wrote: > Fast-forward a few months, and Mark Shinwell noticed the mention of a > possible fix for a microcode defect with unknown hit-ratio in the > intel-microcode package changelog. He matched it to the issue

Bug#866053: ITP: emacs-ivy-doc -- documentation for emacs' Incremental Vertical completYon

2017-06-26 Thread Nicholas D Steeves
Package: wnpp Severity: wishlist Owner: Nicholas D Steeves * Package name: emacs-ivy-doc Version : 0.9.1-1 Upstream Author : Oleh Krehel * URL : https://github.com/abo-abo/swiper * License : GFDL Programming Lang: Markdown and TeX Description : docume

Bug#866047: ITP: factorio-server -- headless server for the game Factorio

2017-06-26 Thread Justin Gerhardt
Package: wnpp Severity: wishlist Owner: Justin Gerhardt * Package name: factorio-server Version : 0.15.23 Upstream Author : Wube Software * URL : https://www.factorio.com/ * License : Proprietary Programming Lang: C++ Description : headless server for

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Christoph Biedl
Ralf Treinen wrote... > What is your opinion? Certainly the right thing to do. These scripts run as root, that's reaon enough to enforce extra precautions. I'd consider even stricter modes like set -u, unless ... Let's be honest: Shell scripts, while easy to write, carry too many risks of unsaf

Re: IMPORTANT: Do live Debian images have a future?

2017-06-26 Thread Adam Borowski
On Mon, Jun 26, 2017 at 02:09:00PM -0700, Rick Thomas wrote: > PS: On a related topic: What I think would be really cool, would be > Debian Live images for some of the ARM architectures. Something I could > dd to a USB stick and boot right away when I get a new box in for testing. > Even cooler

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Emilio Pozuelo Monfort
On 26/06/17 22:23, Ralf Treinen wrote: > Hi, > > we currently have in sid 84 maintainer scripts not using strict mode. > That is, they neither start on "#!/bin/[ba]sh -e", nor do a "set -e". > The list is attached. This list includes the 12 remaining scripts not > starting on #! (bugs are already

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Holger Levsen
On Mon, Jun 26, 2017 at 10:23:56PM +0200, Ralf Treinen wrote: > What is your opinion? Policy says "should", not "must". If you agree > with the MBF, what do you think would be the appropriate severity? "normal" if there are no issues and "important" if you've encountered possible problems. and th

Re: Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Mattia Rizzolo
On Mon, Jun 26, 2017 at 10:23:56PM +0200, Ralf Treinen wrote: > we currently have in sid 84 maintainer scripts not using strict mode. > That is, they neither start on "#!/bin/[ba]sh -e", nor do a "set -e". > The list is attached. This list includes the 12 remaining scripts not > starting on #! (bug

Re: IMPORTANT: Do live Debian images have a future?

2017-06-26 Thread Rick Thomas
I'm a user and a tester, not a dev, and I know nothing (and don't want to know anything) about the personal politics between Debian developers. So that's all I'll say on that subject. To Steve's original point: First, a big THANK YOU! to Steve for taking this job on. I, for one, an grateful. I

Intended MBF: maintainer scripts not using strict mode

2017-06-26 Thread Ralf Treinen
Hi, we currently have in sid 84 maintainer scripts not using strict mode. That is, they neither start on "#!/bin/[ba]sh -e", nor do a "set -e". The list is attached. This list includes the 12 remaining scripts not starting on #! (bugs are already filed for these). Policy says in Section 10.4: S

Processed: reassign 859877 to general

2017-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 859877 general Bug #859877 [debian-maintainers] debian-maintainers: problem mit instalation HP DeskJet 2130 all-in-one Bug reassigned from package 'debian-maintainers' to 'general'. Ignoring request to alter found versions of bug #859877

Re: IMPORTANT: Do live Debian images have a future?

2017-06-26 Thread Michael .
I'm not a dev but I am a user and I do test so I'll add my bit here. Let's be frank Live Wrapper only exists because of animosity within Debian towards the originator of Live Build (and to be honest his own lack of concern for what Debian required of Live Build). Live Wrapper was rushed and was ne

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Ben Hutchings
On Mon, 2017-06-26 at 08:34 +, Holger Levsen wrote: > On Sun, Jun 25, 2017 at 09:19:36AM -0300, Henrique de Moraes Holschuh wrote: > [...] > > Apparently, Intel had indeed found the issue, *documented it* (see > > below) and *fixed it*.  There was no direct feedback to the OCaml > > people, so

Bug#866010: ITP: ruby-public-suffix -- Domain name parser based on the Public Suffix List

2017-06-26 Thread Sruthi Chandran
Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: ruby-public-suffix Version : 2.0.5 Upstream Author : Simone Carletti * URL : https://rubygems.org/gems/public_suffix * License : MIT Programmin

Bug#866009: ITP: python-aiosmtpd -- Python3 asyncio based SMTP server

2017-06-26 Thread Pierre-Elliott Bécue
Package: wnpp Severity: wishlist Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?= * Package name: python-aiosmtpd Version : 1.0 Upstream Author : Barry Warsaw , Eric V. Smith, Andrew Kuchling, Jason Coombs * URL : https://github.com/aio-libs/aiosmtpd *

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Jonathan Dowland
On Mon, Jun 26, 2017 at 06:14:36PM +0500, Andrey Rahmatullin wrote: On Mon, Jun 26, 2017 at 02:08:20PM +0100, Jonathan Dowland wrote: > Yet "don't buy anything" is not a good advice. Have we ruled out all ARM vendors yet? :) Are we still talknig about general-purpose computers? In 2017? Sure

IMPORTANT: Do live Debian images have a future?

2017-06-26 Thread Steve McIntyre
[ Note the cross-posting... ] Hey folks, Background: we released live images for Stretch using new tooling, namely live-wrapper. It is better than what we had before (live-build) in a number of ways, particularly in terms of build reliability and some important new features (e.g. UEFI support). B

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Andrey Rahmatullin
On Mon, Jun 26, 2017 at 02:08:20PM +0100, Jonathan Dowland wrote: > > Yet "don't buy anything" is not a good advice. > Have we ruled out all ARM vendors yet? :) Are we still talknig about general-purpose computers? -- WBR, wRAR signature.asc Description: PGP signature

Bug#866001: ITP: node-debuglog -- used for debugging

2017-06-26 Thread Saravanan P
Package: wnpp Severity: wishlist Owner: saravanan30erd X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-debuglog Version : 1.0.1 Upstream Author : Sam Roberts * URL : https://github.com/sam-github/node-debuglog * License : Expat Programming L

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Jonathan Dowland
On Mon, Jun 26, 2017 at 06:04:43PM +0500, Andrey Rahmatullin wrote: Yet "don't buy anything" is not a good advice. Have we ruled out all ARM vendors yet? :) -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland ⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net ⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Andrey Rahmatullin
On Mon, Jun 26, 2017 at 01:01:51PM +, Holger Levsen wrote: > > The same complaint can be said about the AMD microcode updates. > quite probably, yes. but that doesn't make any crap any better. Yet "don't buy anything" is not a good advice. -- WBR, wRAR signature.asc Description: PGP signat

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Holger Levsen
On Mon, Jun 26, 2017 at 02:30:24PM +0200, Benjamin Drung wrote: > The same complaint can be said about the AMD microcode updates. quite probably, yes. but that doesn't make any crap any better. -- cheers, Holger signature.asc Description: Digital signature

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Benjamin Drung
Am Montag, den 26.06.2017, 08:34 + schrieb Holger Levsen: > On Sun, Jun 25, 2017 at 09:19:36AM -0300, Henrique de Moraes Holschuh > wrote: > [...] > > Apparently, Intel had indeed found the issue, *documented it* (see > > below) and *fixed it*.  There was no direct feedback to the OCaml > > peo

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Holger Levsen
On Mon, Jun 26, 2017 at 08:39:10AM -0300, Henrique de Moraes Holschuh wrote: > As far as I know, so far OCaml is the only one that was verified to be > caused by the SKL150 erratum. [...] thanks for providing these details. -- cheers, Holger signature.asc Description: Digital signatu

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Henrique de Moraes Holschuh
On Mon, 26 Jun 2017, Holger Levsen wrote: > Are there any other public bug reports which got fixed by this, or is the > ocaml issue the only known issue which gets fixed by installing this microcode > update? As far as I know, so far OCaml is the only one that was verified to be caused by the SKL1

Re: Bug#865642: ITP: libgtk3-webkit-perl -- WebKit bindings for Perl

2017-06-26 Thread Mike Gabriel
Control: reopen -1 Control: retitle -1 ITP: libgtk3-webkit2-perl -- WebKit2 bindings for Perl Hi all, On Fri, Jun 23, 2017 at 01:32:37PM +, Mike Gabriel wrote: > Control: tags -1 wontfix > Control: close -1 > > Hi, > > On Fr 23 Jun 2017 14:28:49 CEST, Mike Gabriel wrote: > > > Package: wn

Bug#865989: ITP: ruby-native-package-installer -- Ruby library to help install native packages on "gem install"

2017-06-26 Thread HIGUCHI Daisuke (VDR dai)
Package: wnpp Severity: wishlist Owner: "HIGUCHI Daisuke (VDR dai)" -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: ruby-native-package-installer Version : 1.0.4 Upstream Author : Kouhei Sutou * URL : https://github.com/ruby-gnome2/native-package-inst

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Holger Levsen
On Mon, Jun 26, 2017 at 01:51:25PM +0500, Andrey Rahmatullin wrote: > > but YOU MUST INSTALL THIS BINARY BLOB > How is it worse than the blobs already in your hardware? it opens the door for targeted attacks. -- cheers, Holger signature.asc Description: Digital signature

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Andrey Rahmatullin
On Mon, Jun 26, 2017 at 08:34:57AM +, Holger Levsen wrote: > but YOU MUST INSTALL THIS BINARY BLOB How is it worse than the blobs already in your hardware? -- WBR, wRAR signature.asc Description: PGP signature

Re: [WARNING] Intel Skylake/Kaby Lake processors: broken hyper-threading

2017-06-26 Thread Holger Levsen
On Sun, Jun 25, 2017 at 09:19:36AM -0300, Henrique de Moraes Holschuh wrote: [...] > Apparently, Intel had indeed found the issue, *documented it* (see > below) and *fixed it*. There was no direct feedback to the OCaml > people, so they only found about it later. [...] > We do not have enough info