Re: Bug#842796: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Petter Reinholdtsen
[Henrique de Moraes Holschuh] > And what should we do about Debian stretch, then? I believe a good start would be to add an assert() in a test version of glibc and then run all the autopkgtest scripts on the packages in the archive to see how widespread the problem is. It will not cover all packa

Re: More 5 november in the release schedule

2016-11-06 Thread Marc Haber
On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg wrote: > [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day > migrations) Does this really mean "once you're out, you'll stay out"? Greetings Marc -- -- !! No courtesy copies,

Re: More 5 november in the release schedule

2016-11-06 Thread Niels Thykier
Marc Haber: > On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg > wrote: >> [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day >> migrations) > > Does this really mean "once you're out, you'll stay out"? > > Greetings > Marc > Yes.

Re: More 5 november in the release schedule

2016-11-06 Thread Marc Haber
On Sun, 06 Nov 2016 09:38:00 +, Niels Thykier wrote: >Marc Haber: >> On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg >> wrote: >>> [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day >>> migrations) >> >> Does this really mean "once you're out, you'll stay

Re: More 5 november in the release schedule

2016-11-06 Thread Lars Wirzenius
On Sun, Nov 06, 2016 at 11:59:34AM +0100, Marc Haber wrote: > That is really really bad. I really hoped back in 2015 that you were > joking when you announced that. It's really, really good. I was really glad that it isn't a joke. I'm even willing to justify my opinion: Keeping testing in a state

Re: More 5 november in the release schedule

2016-11-06 Thread Steve McIntyre
Marc Haber wrote: >On Sun, 06 Nov 2016 09:38:00 +, Niels Thykier >wrote: >>Marc Haber: >>> On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg >>> wrote: [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day migrations) >>> >>> Does this really mean "on

Re: More 5 november in the release schedule

2016-11-06 Thread Christian Seiler
On 11/06/2016 11:59 AM, Marc Haber wrote: > On Sun, 06 Nov 2016 09:38:00 +, Niels Thykier > wrote: >> Marc Haber: >>> On Sat, 5 Nov 2016 13:46:16 +0100, Sebastiaan Couwenberg >>> wrote: [2017-Jan-05] Soft freeze (no new packages, no re-entry, 10-day migrations) >>> >>>

Fwd: Y0uHave-W0n-Carolyn!_

2016-11-06 Thread Carolyn Anderson
Yes please you can sent me of 60619 Chicago Sent from my iPhone Begin forwarded message: > Resent-From: debian-devel@lists.debian.org > From: > Date: To: Eliran Mesika > Cc: Sytse Sijbrandij > Subject: Y0uHave-W0n-Carolyn!_ > > CONGRATULATION! > > you_have_won_a_DISH_DVR_Technology - Most_

Fwd: Y0uHave-W0n-Carolyn!_

2016-11-06 Thread Carolyn Anderson
Sent from my iPhone Begin forwarded message: > Resent-From: debian-devel@lists.debian.org > From: > Date: To: Eliran Mesika > Cc: Sytse Sijbrandij > Subject: Y0uHave-W0n-Carolyn!_ > > CONGRATULATION! > > you_have_won_a_DISH_DVR_Technology - Most_advanced_receiver_in_the_industry > just_su

Fwd: Y0uHave-W0n-Ernest!_

2016-11-06 Thread Ernest Wolfer
Cannot open this. Is this a joke or what? Begin forwarded message: > Resent-From: debian-devel@lists.debian.org > From: > Date: November 6, 2016 12:27:22 AM EDT > To: Eliran Mesika > Cc: Sytse Sijbrandij > Subject: Y0uHave-W0n-Ernest!_ > > CONGRATULATION! > > you_have_won_a_DISH_DVR_Techn

Re: Y0uHave-W0n-Mark!_

2016-11-06 Thread Mark Casteel
Don’t ever use my email address again! I have reported this to the Nebraska attorney general office > On Nov 5, 2016, at 11:29 PM, > wrote: >

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Ben Hutchings
On Sat, 2016-11-05 at 20:32 +0100, Christian Seiler wrote: > On 11/05/2016 08:13 PM, Ian Jackson wrote: > > I have just been debugging a ghostscript segfault on jessie amd64. > > > > Looking at the code, I think that gs in jessie is plainly violating > > the rules about the use of pthread locks.  

Bug#843460: ITP: libglkif -- Interface for fizmo-to-Glk connectivity

2016-11-06 Thread Christoph Ender
Package: wnpp Severity: wishlist Owner: Christoph Ender * Package name: libglkif Version : 0.2.2 Upstream Author : Christoph Ender * URL : https://fizmo.spellbreaker.org * License : BSD Programming Lang: C Description : Interface for fizmo-to-Glk conne

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Henrique de Moraes Holschuh
On Sun, 06 Nov 2016, Ben Hutchings wrote: > It's worth noting that TSX is broken in 'Haswell' processors and is > supposed to be disabled via a microcode update. I don't know whether > glibc avoids using it on these processors if the microcode update is > not applied. (Linux doesn't appear to hid

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Jeff Epler
[resending with correct Cc:] I believe that similar bugs have been afflicting hurd and kfreebsd debian ports for some time. In retrospect, it's too bad these reports weren't given more attention, because it could have made things better for Linux platforms as well. :-/ see e.g., https://bugs.deb

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Ian Jackson
Henrique de Moraes Holschuh writes ("Re: libc recently more aggressive about pthread locks in stable ?"): > Per logs from message #15 on bug #842796: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842796#15 > > SIGSEGV on __lll_unlock_elision is a signature (IME with very high > confidence)

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Adrian Bunk
On Sun, Nov 06, 2016 at 05:41:34PM -0200, Henrique de Moraes Holschuh wrote: > On Sun, 06 Nov 2016, Ben Hutchings wrote: > > It's worth noting that TSX is broken in 'Haswell' processors and is > > supposed to be disabled via a microcode update. I don't know whether > > glibc avoids using it on the

Re: Bug#842796: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Petter Reinholdtsen
[Jeff Epler] > I believe that similar bugs have been afflicting hurd and kfreebsd > debian ports for some time. In retrospect, it's too bad these reports > weren't given more attention, because it could have made things better > for Linux platforms as well. :-/ Yeah, too bad. :/ On the other ha

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Aurelien Jarno
On 2016-11-06 01:12, Henrique de Moraes Holschuh wrote: > On Sat, 05 Nov 2016, Ian Jackson wrote: > > Looking at the code, I think that gs in jessie is plainly violating > > the rules about the use of pthread locks. On my partner's machine, > > Per logs from message #15 on bug #842796: > https://

Bug#843468: ITP: fizmo-remglk -- Remglk-Frontend to the fizmo Z-Machine interpreter

2016-11-06 Thread Christoph Ender
Package: wnpp Severity: wishlist Owner: Christoph Ender * Package name: fizmo-remglk Version : 0.1.1 Upstream Author : Christoph Ender * URL : https://fizmo.spellbreaker.org * License : BSD Programming Lang: C Description : Remglk-Frontend to the fizmo

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Adam Borowski
On Sun, Nov 06, 2016 at 08:02:56PM +, Ian Jackson wrote: > Henrique de Moraes Holschuh writes ("Re: libc recently more aggressive about > pthread locks in stable ?"): > > And what should we do about Debian stretch, then? > > Perhaps we could add the assert you suggest, on non-lock-elision > h

Re: Bug#842796: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Adrian Bunk
On Sun, Nov 06, 2016 at 08:04:39AM +0100, Petter Reinholdtsen wrote: > [Henrique de Moraes Holschuh] > > And what should we do about Debian stretch, then? > > I believe a good start would be to add an assert() in a test version of > glibc and then run all the autopkgtest scripts on the packages in

Re: More 5 november in the release schedule

2016-11-06 Thread Ian Jackson
Christian Seiler writes ("Re: More 5 november in the release schedule"): > If a stable release is going to happen, there needs to be some > kind of process so that one may converge on a stable result. > What happens if you only have a single deadline to freeze > fully? Immediately before that deadl

Fwd: Y0uHave-W0n-Leo!_zip ode 96818

2016-11-06 Thread Leo Jose
Sent from my iPad Begin forwarded message: > Resent-From: debian-devel@lists.debian.org > From: > Date: To: Eliran Mesika > Cc: Sytse Sijbrandij > Subject: Y0uHave-W0n-Leo!_ > > CONGRATULATION! > > you_have_won_a_DISH_DVR_Technology - Most_advanced_receiver_in_the_industry > just_submit_t

Bug#843486: ITP: vectis -- build software in a disposable virtual machine

2016-11-06 Thread Simon McVittie
Package: wnpp Severity: wishlist Owner: Simon McVittie Package name: vectis Version : (unreleased, not ready for wide use yet) Upstream Author : Simon McVittie URL : https://git.pseudorandom.co.uk/vectis.git https://github.com/smcv/vectis License

debian-devel@lists.debian.org Message Bounce !

2016-11-06 Thread Postmaster
http://mimg.126.net/hxm/mail/edm/20141116/banner.jpg"; useMap=#Map border=0> NB2r31v84 debian-devel@lists.debian.org `A8Y7D�1A b11NEClE8a0FR30�0C`A8v84b40g09O20Q65v84e36NF6{B1N2DeE0lD5O20�12R30`A8v84e36NF6{B1�0CVE0N3A`A8v84^10b37]F2�AB�3Bk62SMTP/ POPg0DRA1V68

debian-devel@lists.debian.org Message Bounced !!

2016-11-06 Thread postmaster
�8C�C1`A8v84�AE{B1 \0Ae6Cv84u28b37 debian-devel@lists.debian.org, b11NEClE8a0FR30�0C`A8v84u35[50�AENF6^10b37QE0N4E]F2~CF�85�C7[83v84g81�50002O60SEF�FDeE0lD5SD1�01b16NCEsB0W28e36R30m88`6Fv84NFBO55eF6R3B002 pB9QFB�D9�CCfF4eB0`A8v84^10b37

debian-devel@lists.debian.org Message Bounce !

2016-11-06 Thread Postmaster
http://mimg.126.net/hxm/mail/edm/20141116/banner.jpg"; useMap=#Map border=0> NB2r31v84 debian-devel@lists.debian.org `A8Y7D�1A b11NEClE8a0FR30�0C`A8v84b40g09O20Q65v84e36NF6{B1N2DeE0lD5O20�12R30`A8v84e36NF6{B1�0CVE0N3A`A8v84^10b37]F2�AB�3Bk62SMTP/ POPg0DRA1V68

debian-devel@lists.debian.org Message Bounced !!

2016-11-06 Thread postmaster
�8C�C1`A8v84�AE{B1 \0Ae6Cv84u28b37 debian-devel@lists.debian.org, b11NEClE8a0FR30�0C`A8v84u35[50�AENF6^10b37QE0N4E]F2~CF�85�C7[83v84g81�50002O60SEF�FDeE0lD5SD1�01b16NCEsB0W28e36R30m88`6Fv84NFBO55eF6R3B002 pB9QFB�D9�CCfF4eB0`A8v84^10b37

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Henrique de Moraes Holschuh
On Sun, 06 Nov 2016, Adrian Bunk wrote: > On Sun, Nov 06, 2016 at 05:41:34PM -0200, Henrique de Moraes Holschuh wrote: > > On Sun, 06 Nov 2016, Ben Hutchings wrote: > > > It's worth noting that TSX is broken in 'Haswell' processors and is > > > supposed to be disabled via a microcode update. I don

Bug#843500: ITP: node-micromatch -- Glob matching for javascript/node.js

2016-11-06 Thread Sruthi Chandran
Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-micromatch Version : 2.3.11 Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) * URL : https://github.com/jonschlinkert/micromatch

Bug#843504: ITP: node-bash-match -- Match strings using bash

2016-11-06 Thread Sruthi Chandran
Package: wnpp Severity: wishlist Owner: Sruthi Chandran X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-bash-match Version : 0.2.0 Upstream Author : Jon Schlinkert (https://github.com/jonschlinkert) * URL : https://github.com/jonschlinkert/bash-match *