On 10/13/14 1:38 AM, viv...@gmail.com wrote:
have you considered to stabilize gcc:4.9 instead possibly 4.9.2 ?
I'm not really suggesting to do so, but seem that most of the problems
of 4.9.1 are the same of 4.8.3 so maybe it's worth considering.
Il 11/10/2014 13:57, Paweł Hajdan, Jr. ha
I can spend some time with the tinderbox on 4.9 but the maintainers will
have to accept that the logs will be linked and not attached.
(This being the main reason why I stopped bothering unless people asked me
explicitly, given how many times someone closed my bugs with NEEDINFO
because the logs
On Sun Oct 12 01:27:38 2014 Anthony G. Basile bluen...@gentoo.org wrote:
On 10/11/14 16:28, Rich Freeman wrote:
On Sat, Oct 11, 2014 at 4:07 PM, M. Ziebell ziebell_ma...@posteo.de
wrote:
But if anyone would ask me to stabilize gcc-4.8 I would say amd64
ok.
If there is general
El sáb, 18-10-2014 a las 12:35 +0100, Diego Elio Pettenò escribió:
I can spend some time with the tinderbox on 4.9 but the maintainers
will have to accept that the logs will be linked and not attached.
(This being the main reason why I stopped bothering unless people
asked me explicitly,
If you write the code for that, be my guest. But the code is in Ruby and
does not open the bug directly (only links to a pre-filled bug form).
When I wrote it, Python was definitely not among my strong languages. While
I can probably write it now, I don't have the time.
As I said I'm happy to
On 10/18/14 07:56, Alexander Tsoy wrote:
On Sun Oct 12 01:27:38 2014 Anthony G. Basile bluen...@gentoo.org wrote:
On 10/11/14 16:28, Rich Freeman wrote:
On Sat, Oct 11, 2014 at 4:07 PM, M. Ziebell ziebell_ma...@posteo.de
wrote:
But if anyone would ask me to stabilize gcc-4.8 I would say amd64
El sáb, 18-10-2014 a las 14:15 +0100, Diego Elio Pettenò escribió:
If you write the code for that, be my guest. But the code is in Ruby
and does not open the bug directly (only links to a pre-filled bug
form).
When I wrote it, Python was definitely not among my strong languages.
While I
All the stack is at https://github.com/gentoo/tboxanalysis
The opening of the bug report is done by a piece of meatware called me.
The UI displays a link that I can click to pre-fill the bug report. The
rest of the information is filled in manually and submitted.
Also remember that the linked
On 10/18/2014 01:00 PM, Diego Elio Pettenò wrote:
All the stack is at https://github.com/gentoo/tboxanalysis
The opening of the bug report is done by a piece of meatware called
me. The UI displays a link that I can click to pre-fill the bug
report. The rest of the information is filled in
El sáb, 18-10-2014 a las 18:00 +0100, Diego Elio Pettenò escribió:
All the stack is at https://github.com/gentoo/tboxanalysis
The opening of the bug report is done by a piece of meatware called
me. The UI displays a link that I can click to pre-fill the bug
report. The rest of the
El sáb, 18-10-2014 a las 13:19 -0400, Michael Orlitzky escribió:
On 10/18/2014 01:00 PM, Diego Elio Pettenò wrote:
All the stack is at https://github.com/gentoo/tboxanalysis
The opening of the bug report is done by a piece of meatware called
me. The UI displays a link that I can click to
On 10/18/2014 01:34 PM, Pacho Ramos wrote:
Supposedly we always must attach files to bug reports to ensure they are
kept forever with that bug reports instead of relying on external
resources that could disappear in the future (or far future). If I don't
misremember, flameeyes was paying for
El sáb, 18-10-2014 a las 14:03 -0400, Michael Orlitzky escribió:
On 10/18/2014 01:34 PM, Pacho Ramos wrote:
Supposedly we always must attach files to bug reports to ensure they are
kept forever with that bug reports instead of relying on external
resources that could disappear in the
On 18 October 2014 19:03, Michael Orlitzky m...@gentoo.org wrote:
Dude... what?
If this is what's holding up a tinderbox run, add me to the bug template
as a CC and I'll personally download and attach every log to bugzilla.
If at some point we all decide this is super silly and embarrassing,
This updated patch adds --search-index y | n . I'll be maintaining
this patch in the following branch:
https://github.com/zmedico/portage/tree/bug_525718
From 2aca92f664fd2ff669b77b38a49b06fafbc66b8d Mon Sep 17 00:00:00 2001
From: Zac Medico zmed...@gentoo.org
Date: Fri, 17 Oct 2014
15 matches
Mail list logo
