On 08/11/16 at 16:01 -0200, Henrique de Moraes Holschuh wrote:
> I fear it might be bad, but
> I would love to be pleasantly surprised that people did get libpthreads
> locking right most of the time...
I wonder if it has been considered to "fix" glibc so that the misuses
that are tolerated withou
unsubscribe
On 07.11.2016 09:07, Stefano Zacchiroli wrote:
> TL;DR: all Debian contributors --- from bug reporters to Debian project
> members and participants in any Debian team --- are invited to take part
> in the first edition of the Debian contributors survey. To participate
> visit:
>
> h
On 09/11/16 04:16, Paul Wise wrote:
> On Wed, Nov 9, 2016 at 1:36 AM, Emilio Pozuelo Monfort wrote:
>
>> Right. We want auto-removals to be useful for the release process, so that we
>> don't end up with a thousand of RC bugs in testing when we freeze, most of
>> them
>> on packages that nobody c
On Wed, Nov 09, 2016 at 10:04:28AM +0100, Sven Joachim wrote:
> I'm afraid I don't really have a good suggestion. Using current date
> would work but obviously break reproducibility, and any other date seems
> arbitrary.
Why would that break reproducibility? reproducible builds is about
reproduc
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss
* Package name: s4cmd
Version : 2.0.1
Upstream Author : BloomReach Inc.
* URL : https://github.com/bloomreach/s4cmd
* License : Apache
Programming Lang: Python
Description : Super Amazon S3 comman
On Wed, 09 Nov 2016 at 17:03:45 +1100, Brian May wrote:
> Another situation: You are not listed as the maintainer of the package
> you really care about, and the real maintainer ignores the autoremoval
> notifications. Other people looking at the package bug reports (there
> may be none) may not re
[Walter Landry, 2016-11-08]
> Doing a quick search
>
> curl -s
> https://codesearch.debian.net/results/22044ee2fe5c4350/packages.json | jq -r
> '.Packages[]' | wc -l
this result is no longer available
>
> shows 39 packages might also benefit from a central installation of
> waf.
IMHO there
Raphael Hertzog writes ("Re: DEP14 policy for two dots"):
> On Tue, 08 Nov 2016, Ian Jackson wrote:
> > > The reverse rule is to convert _ and % and delete all #.
> >
> > Quoted for completeness.
>
> Ok, can you prepare a patch for DEP-14 then? I'll apply it as it looks like
> a reasonable extens
(CCing reproducible-builds again:)
Sven Joachim writes ("Re: misleading timestamps in binnmus"):
> I'm afraid I don't really have a good suggestion. Using current date
> would work but obviously break reproducibility, and any other date seems
> arbitrary.
I don't understand why using the current
Hi!
On Wed, 2016-11-09 at 11:16:09 +, Ian Jackson wrote:
> Sven Joachim writes ("Re: misleading timestamps in binnmus"):
> > I'm afraid I don't really have a good suggestion. Using current date
> > would work but obviously break reproducibility, and any other date seems
> > arbitrary.
>
> I
Package: wnpp
Severity: wishlist
Owner: Jordi Mallach
* Package name: golang-gopkg-alexcesaro-statsd.v1
Version : 0.0~git20160306.0.c289775-1
Upstream Author : Alexandre Cesaro
* URL : https://github.com/alexcesaro/statsd
* License : MIT
Programming Lang: Go
Peter Colberg writes ("What to do when a maintainer is blocking maintenance for
stretch?"):
> Improving the package would require significant changes that are not
> appropriate for a minimal NMU. With the maintainer not responding to
> anything other than MIA requests to retain their maintainer st
Thanks to everyone who has provided information. I have summarised
it in #843773, against sbuild.
What version of sbuild do buildds run ? Ie, supposing that this is
fixed in sbuild in stretch, will this be fixed on the buildds ? Or do
we need to update jessie, or what ?
Ian.
--
Ian Jackson
* Emilio Pozuelo Monfort [161108 16:01]:
> It is true for other removals from testing, which can happen in two different
> ways:
>
> - The package was removed from unstable
> - The package was hinted for testing removal by the release team
>
> Since britney doesn't enforce (atm) that build-depe
Marvin Renich writes ("Re: More 5 november in the release schedule"):
> Emilio Pozuelo Monfort [161108 16:01]:
> > It is true for other removals from testing, which can happen in two
> > different ways:
> >
> > - The package was removed from unstable
> > - The package was hinted for testing remo
On Wed, Nov 09, 2016 at 12:12:43PM +, Ian Jackson wrote:
> The advice from Emilio to upload your proposed big changes to
> DELAYED/10 is probably good.
agreed.
> In theory you should ask the Technical Committee to depose the
> maintainer.
I disagree here. I think the next/first step should
Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant
* Package name: dcm2niix
Version : 1.0.20161101
Upstream Author : Chris Rorden
* URL : https://github.com/rordenlab/dcm2niix
* License : BSD
Programming Lang: C++
Description : next genera
On Wed, 09 Nov 2016 14:01:13 +, Ian Jackson wrote:
> If it turns out to be a more common problem and there are many
> packages affected, then this would mean delays to the stretch release,
> indeed. But it would also highlight where the real problem is - ie,
> not with the maintenance of the
On Wed, Nov 09, 2016 at 03:51:12PM +, Holger Levsen wrote:
> On Wed, Nov 09, 2016 at 12:12:43PM +, Ian Jackson wrote:
> > In theory you should ask the Technical Committee to depose the
> > maintainer.
>
> I disagree here. I think the next/first step should be contacting the
> MIA team and
Package: wnpp
Severity: wishlist
Owner: "Dr. Tobias Quathamer"
* Package name: golang-github-mreiferson-go-httpclient
Version : 0.0~git20160630.0.31f0106-1
Upstream Author : Matt Reiferson
* URL : https://github.com/mreiferson/go-httpclient
* License : Expat
On Wed, Nov 09, 2016 at 06:45:43PM +, Mattia Rizzolo wrote:
>...
> Also, a personal pledge to everybody who's reading this: please don't
> attach yourself to your packages like mussels on a rock. If you realize
> (or somebody else is making you realize) that you're doing a bad job on
> a packa
On Wed, Nov 09, 2016 at 11:16:36AM +0800, Paul Wise wrote:
> On Wed, Nov 9, 2016 at 1:36 AM, Emilio Pozuelo Monfort wrote:
>
> > Right. We want auto-removals to be useful for the release process, so that
> > we
> > don't end up with a thousand of RC bugs in testing when we freeze, most of
> > th
On Tue, Nov 08, 2016 at 11:16:53AM +0800, Paul Wise wrote:
> On Tue, Nov 8, 2016 at 4:26 AM, Adam Borowski wrote:
>
> > Forced reboot on upgrade is damage. Let's learn from errors of others.
>
> needrestart has a mechanism (needrestart-session) to hook into user
> sessions, perhaps that could be
On Mon, Nov 07, 2016 at 08:58:53PM +0100, Adam Borowski wrote:
> On Sun, Oct 30, 2016 at 06:55:33PM +, Clint Adams wrote:
> > On Sun, Oct 30, 2016 at 06:28:41AM +0100, Adam Borowski wrote:
> > > A maintainer would then file "ITR: dasher" and wait for responses before
> > > requesting RM.
> >
>
Raphael Hertzog writes ("Re: DEP14 policy for two dots"):
> Ok, can you prepare a patch for DEP-14 then? I'll apply it as it looks like
> a reasonable extension.
Attached. FYI I intend to implement this in dgit.
Thanks,
Ian.
>From 5c63400e9be8cb1532515764a1179730aed550fb Mon Sep 17 00:00:00 200
On Sun, Nov 06, 2016 at 12:03:03AM +0100, Philipp Kern wrote:
> On 2016-11-05 22:23, Adrian Bunk wrote:
> > The solution you are trying to sell is apt-transport-https as default.
> [...]
> > Your solution would be a lot of work with relatively little improvement.
>
> Well, the client-side exists a
On Wed, Nov 09, 2016 at 11:24:37PM +0200, Adrian Bunk wrote:
> On Mon, Nov 07, 2016 at 08:58:53PM +0100, Adam Borowski wrote:
> > On Sun, Oct 30, 2016 at 06:55:33PM +, Clint Adams wrote:
> > > On Sun, Oct 30, 2016 at 06:28:41AM +0100, Adam Borowski wrote:
> > > > A maintainer would then file "I
On 09.11.2016 [21:27:14 +], Ian Jackson wrote:
> Raphael Hertzog writes ("Re: DEP14 policy for two dots"):
> > Ok, can you prepare a patch for DEP-14 then? I'll apply it as it looks like
> > a reasonable extension.
>
> Attached. FYI I intend to implement this in dgit.
Thank you! We will foll
Quoting Mattia Rizzolo (2016-11-09 16:45:43)
> Also, a personal pledge to everybody who's reading this: please don't attach
> yourself to your packages like mussels on a rock.
on that topic, I am warmly recommending Enrico Zini's "semi serious stand up
comedy notes":
Compersion, n: the feelin
Package: wnpp
Severity: wishlist
Owner: Jordi Mallach
* Package name: golang-github-ctdk-chefcrypto
Version : 0.0~git20161109.0.dea96d7-1
Upstream Author : Jeremy Bingham
* URL : https://github.com/ctdk/chefcrypto
* License : Apache-2.0
Programming Lang: Go
On Tue, Nov 08, 2016 at 11:05:59AM +0100, Christian Seiler wrote:
> 30 days within the deep freeze should be plenty enough - and as I
> said: if the problem is more complicated, just talk to the release
> team _while the package is still in testing_.
Let's say I'm on holiday (or I get hit by a bus
Nish Aravamudan writes ("Re: DEP14 policy for two dots"):
> Thank you! We will follow the same in the Ubuntu tooling used by the Server
> Team.
Great, thanks.
Can I ask you a rather unrelated question ? AIUI you are working on
importing Ubuntu's history into git. That's great.
Can you confirm
On Tue, Nov 08, 2016 at 10:41:09PM +, Ian Jackson wrote:
> Is this a recommended recipe ? AIUI a buildd doing a binnmu will not
> modify the debian/changelog file.
Are you sure? When last I checked, this was not true (it may have
changed since, however).
--
< ron> I mean, the main *practica
gregor herrmann writes ("Re: More 5 november in the release schedule"):
> I don't quite understand where all this fuzz about auto-removals
> suddenly comes from. The auto-removals exist since Septemer 2013 [0]
> and they were also in place for the jessie freeze [1], with the small
> difference that
Adam Borowski writes ("Re: NRSS has been deprecated [#696302]"):
> On Wed, Nov 09, 2016 at 11:24:37PM +0200, Adrian Bunk wrote:
> > What you are suggesting is a proper process for handling all source
> > removals, instead of the current practice where the maintainer can
> > just submit an "RM: das
Package: wnpp
Severity: wishlist
Owner: Jordi Mallach
* Package name: golang-github-ctdk-go-trie
Version : 0.0~git20161027.0.6443fbc-1
Upstream Author : Jeremy Bingham
* URL : https://github.com/ctdk/go-trie
* License : MIT
Programming Lang: Go
Description
On 09.11.2016 [23:38:30 +], Ian Jackson wrote:
> Nish Aravamudan writes ("Re: DEP14 policy for two dots"):
> > Thank you! We will follow the same in the Ubuntu tooling used by the Server
> > Team.
>
> Great, thanks.
>
> Can I ask you a rather unrelated question ? AIUI you are working on
> im
Nish Aravamudan writes ("Re: DEP14 policy for two dots"):
> On 09.11.2016 [23:38:30 +], Ian Jackson wrote:
> > Can you confirm what approach you have taken to the representation of
> > Debian source packges as git trees ? I would like to encourage you to
> > use a representation which is compa
Package: wnpp
Severity: wishlist
Owner: Jordi Mallach
* Package name: golang-github-raintank-met
Version : 0.0~git20161103.0.05a94bb-1
Upstream Author : raintank
* URL : https://github.com/raintank/met
* License : TODO
Programming Lang: Go
Description :
I forgot one:
Ian Jackson writes ("Re: DEP14 policy for two dots"):
> A patches-unapplied tree:
>
> * produces confusing and sometimes misleading output from
>git grep, or (even if appropriate history is available)
>with git blame;
>
> * cannot be used with `git cherry pick ';
>
> *
On Wed, 2016-11-09 at 23:06 +0200, Adrian Bunk wrote:
> Any "solution" for the reboot problem that assumes that there is a
> user who regularly logs into the machine misses the problem.
Any solution that is the same for every device is completely wrong.
Cloud images should probably auto-reboot A
On Wed, 2016-11-09 at 22:55 +0200, Adrian Bunk wrote:
> Is anyone tracking what packages are installed from backports on
> Debian machines, and the CVEs in them?
backports is unsupported by the security team, so DSA & backports users
rely on service maintainers and backporters to do the right thi
Ian Jackson (2016-11-09):
> What version of sbuild do buildds run ? Ie, supposing that this is
> fixed in sbuild in stretch, will this be fixed on the buildds ? Or do
> we need to update jessie, or what ?
sbuild on buildds uses a specific version of sbuild, for reasons I'm not
going to summariz
On Thu, Nov 10, 2016 at 12:24:20AM +0100, Wouter Verhelst wrote:
> On Tue, Nov 08, 2016 at 11:05:59AM +0100, Christian Seiler wrote:
> > 30 days within the deep freeze should be plenty enough - and as I
> > said: if the problem is more complicated, just talk to the release
> > team _while the packa
Piotr Ożarowski wrote:
> [Walter Landry, 2016-11-08]
>> Doing a quick search
>>
>> curl -s
>> https://codesearch.debian.net/results/22044ee2fe5c4350/packages.json | jq -r
>> '.Packages[]' | wc -l
>
> this result is no longer available
Oh bother. I did a slightly more sophisticated search a
Ian Jackson wrote...
> I think what is really worrying people is the fear that they might
> miss something, for good reasons, and then find that their work that
> they care about is thrown out of stretch.
>
> It is difficult to address this fear with logical arguments intended
> to demonstrate tha
Wouter Verhelst:
> On Tue, Nov 08, 2016 at 11:05:59AM +0100, Christian Seiler wrote:
>> 30 days within the deep freeze should be plenty enough - and as I
>> said: if the problem is more complicated, just talk to the release
>> team _while the package is still in testing_.
>
> Let's say I'm on holi
Wouter Verhelst writes:
> On Tue, Nov 08, 2016 at 11:05:59AM +0100, Christian Seiler wrote:
>> 30 days within the deep freeze should be plenty enough - and as I
>> said: if the problem is more complicated, just talk to the release
>> team _while the package is still in testing_.
>
> Let's say I'm
48 matches
Mail list logo
