On Fri, 21 Nov 2014 16:32:15 +
Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So really, I'm tired to be insulted, and this was the last drop.
Goodbye. Diego Elio Pettenò — Flameeyes
+1!
Given our invested time; it's not the lack of encouragement, but rather
the presence of
Before I reply with a simple four letter words let me restate one
thing and than that will be it, and my next move unless council/devrel
stops this for good my time will be spent better: playing Baldur's
Gate.
The problem is not that I don't know python. Because I do know python (now).
The
Dnia 2014-11-20, o godz. 08:06:05
Anthony G. Basile bluen...@gentoo.org napisał(a):
On 11/20/14 04:37, Michał Górny wrote:
Dnia 2014-11-19, o godz. 17:41:53
Diego Elio Pettenò flamee...@flameeyes.eu napisał(a):
On 31 October 2014 09:28, Diego Elio Pettenò flamee...@flameeyes.eu
wrote:
On 11/21/14 18:05, Michał Górny wrote:
And yes, I'm waiting for some free time to redo the toolchain.
That I will help you with.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail: bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG
Dnia 2014-11-19, o godz. 17:41:53
Diego Elio Pettenò flamee...@flameeyes.eu napisał(a):
On 31 October 2014 09:28, Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now? Because I'm almost pissed off
enough to turn down the tinderbox and give a big FU to
On 11/20/14 04:37, Michał Górny wrote:
Dnia 2014-11-19, o godz. 17:41:53
Diego Elio Pettenò flamee...@flameeyes.eu napisał(a):
On 31 October 2014 09:28, Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now? Because I'm almost pissed off
enough to turn down
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/11/14 09:51 PM, Rich Freeman wrote:
On Wed, Nov 19, 2014 at 8:41 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
On 31 October 2014 09:28, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 20/11/14 09:47 AM, Ian Stakenvicius wrote:
On 19/11/14 09:51 PM, Rich Freeman wrote:
On Wed, Nov 19, 2014 at 8:41 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
On 31 October 2014 09:28, Diego Elio Pettenò
flamee...@flameeyes.eu
On 11/20/14 5:04 PM, Ian Stakenvicius wrote:
Ok, added the RESO/NEEDINFO case, and bumped my polling time to 5
minute intervals.
Diego, please keep going, your efforts are still very much appreciated.
+1, and thanks Ian for your script!
Paweł
signature.asc
Description: OpenPGP digital
On 31 October 2014 09:28, Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now? Because I'm almost pissed off
enough to turn down the tinderbox and give a big FU to Gentoo already.
https://bugs.gentoo.org/show_bug.cgi?id=527608
More!
On Wed, Nov 19, 2014 at 8:41 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
On 31 October 2014 09:28, Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now? Because I'm almost pissed off
enough to turn down the tinderbox and give a big FU to Gentoo
On Wed, 19 Nov 2014, Diego Elio Pettenò wrote:
More! https://bugs.gentoo.org/show_bug.cgi?id=529788
Again, is somebody going to stand up and do something or can I shut
down my tinderbox and spend my free time playing Baldur's Gate?
Excuse the top posting.
You don't need to strip the HTML. Change the extension to whatever.log and
it's already there in unmangled text.
On 2 Nov 2014 01:10, Ian Stakenvicius a...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/11/14 03:53 PM, Pacho Ramos wrote:
El
El sáb, 01-11-2014 a las 21:10 -0400, Ian Stakenvicius escribió:
[...]
Not at the moment ; I'm going to want to do a fair bit of cleanup
before i let anyone else's eyes on it.. :)
It's just a bash script, though -- i use 'pybugz search' to get a list
of the bugs Diego's filed (using --offset
How do you strip the html code? I was unsure about to do that :/
You should have asked. There is no need to strip. I upload both HTML and
text alike.
El dom, 02-11-2014 a las 13:07 +, Diego Elio Pettenò escribió:
How do you strip the html code? I was unsure about to do that :/
You should have asked. There is no need to strip. I upload both HTML
and text alike.
Ah, ok. Anyway, if AxS can tell me how was doing that would be
On 02/11/14 14:22, Pacho Ramos wrote:
El dom, 02-11-2014 a las 13:07 +, Diego Elio Pettenò escribió:
How do you strip the html code? I was unsure about to do that :/
You should have asked. There is no need to strip. I upload both HTML
and text alike.
Ah, ok. Anyway, if AxS can tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/11/14 09:44 AM, Luca Barbato wrote:
On 02/11/14 14:22, Pacho Ramos wrote:
El dom, 02-11-2014 a las 13:07 +, Diego Elio Pettenò
escribió:
How do you strip the html code? I was unsure about to do that
:/
You should have asked.
On 11/02/2014 03:08 AM, Rich Freeman wrote:
Well, nothing is ever ideal, but as issues come up they are being
dealt with now. I can't think of any situations where somebody has
been able to block out new contributors in the last year or two.
Sure, there have been a few attempts, but we've
On 1 November 2014 00:18, Rich Freeman ri...@gentoo.org wrote:
So, if there is a better way, I'm all ears for constructive
suggestions. By constructive I mean that somebody who comes up with a
script that automatically retrieves build logs and attaches them to
bugs is being more helpful than
On 1 November 2014 10:47, Diego Elio Pettenò flamee...@flameeyes.eu wrote:
But let's reason a moment on the no-linked-logs policy: as Rich
pointed out already, the policy is there for a reason and that reason
is that we don't want people to submit bugs with pastebins or home
server logs
El sáb, 01-11-2014 a las 10:47 +, Diego Elio Pettenò escribió:
On 1 November 2014 00:18, Rich Freeman ri...@gentoo.org wrote:
So, if there is a better way, I'm all ears for constructive
suggestions. By constructive I mean that somebody who comes up with a
script that automatically
On 11/01/2014 01:18 AM, Rich Freeman wrote:
What we can't do is force somebody to contribute. If somebody says
that if we don't do multilib their way, they'll stop being the only
libreoffice maintainer, and nobody else wants to maintain libreoffice,
then we are left in a hard place
On Sat, Nov 1, 2014 at 11:38 AM, hasufell hasuf...@gentoo.org wrote:
But there will be no improvement if we don't take such issues more
seriously. I don't really see that happening. It's something the
oldtimers have more power over than the council.
In a community project, the folks with
On 01/11/14 11:47, Diego Elio Pettenò wrote:
The problem with it's trivial to do that in python so just do it is
that first of all Python is not my language of choice, so the whole
infrastructure is currently not written in Python at all. And all the
people, including Luca, who promised they can
The newest member of Gentoo can have more power to direct the course
of the distro than every oldtimer or council member there is, if they
just contribute more than them.
If the maintainer of package A or provider of service B is a pain to
work with, all it takes is for somebody else who is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 31/10/14 10:37 PM, Ian Stakenvicius wrote:
Sorry for top posting. I volunteer to write something to get the
logs attached to bugs. I'll do it next week. Whether it be
something the tinderbox can run or something separate that will use
Ian Stakenvicius wrote:
OK, i've cobbled something together that looks like it'll work.
Cool! Thanks a lot for doing that.
//Peter
El sáb, 01-11-2014 a las 14:54 -0400, Ian Stakenvicius escribió:
On 31/10/14 10:37 PM, Ian Stakenvicius wrote:
Sorry for top posting. I volunteer to write something to get the
logs attached to bugs. I'll do it next week. Whether it be
something the tinderbox can run or something separate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/11/14 03:53 PM, Pacho Ramos wrote:
El sáb, 01-11-2014 a las 14:54 -0400, Ian Stakenvicius escribió:
On 31/10/14 10:37 PM, Ian Stakenvicius wrote:
Sorry for top posting. I volunteer to write something to get
the logs attached to bugs.
On Sat, Nov 1, 2014 at 2:30 PM, Andreas K. Huettel dilfri...@gentoo.org wrote:
The newest member of Gentoo can have more power to direct the course
of the distro than every oldtimer or council member there is, if they
just contribute more than them.
If the maintainer of package A or provider
On 19 October 2014 16:57, hasufell hasuf...@gentoo.org wrote:
If maintainers want to NEEDINFO or WONTFIX a tinderbox bug, well,
they'll be the ones picking up the pieces when the gcc upgrade moves
ahead.
We are all picking up the pieces.
I don't get why anybody wouldn't like seeing them.
On Fri, 31 Oct 2014 16:28:56 +
Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now? Because I'm almost pissed off
enough to turn down the tinderbox and give a big FU to Gentoo already.
https://bugs.gentoo.org/show_bug.cgi?id=527608
Apparently Mr.
On Fri, Oct 31, 2014 at 12:28 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
On 19 October 2014 16:57, hasufell hasuf...@gentoo.org wrote:
If maintainers want to NEEDINFO or WONTFIX a tinderbox bug, well,
they'll be the ones picking up the pieces when the gcc upgrade moves
ahead.
We
On 10/31/2014 05:58 PM, Jeroen Roovers wrote:
On Fri, 31 Oct 2014 16:28:56 +
Diego Elio Pettenò flamee...@flameeyes.eu wrote:
So who wants to pick up the pieces now? Because I'm almost pissed off
enough to turn down the tinderbox and give a big FU to Gentoo already.
On 31 October 2014 22:38, hasufell hasuf...@gentoo.org wrote:
Signs of his inability to collaborate in some situations have come up
repeatedly on this list, be it problems with crossdev/multilib, games
team and whatnot.
Most of these were either ignored or had to go through a council
I'm going to speak generally - this is a list and not really the best
way of dealing with individuals. If you think the principles apply to
you, feel free to apply them.
On Fri, Oct 31, 2014 at 7:50 PM, Diego Elio Pettenò
flamee...@flameeyes.eu wrote:
I'm more convinced than ever that either
Sorry for top posting. I volunteer to write something to get the logs attached
to bugs. I'll do it next week. Whether it be something the tinderbox can run
or something separate that will use pybugz to find bugs and then attach
whatever logs are pointed to by URLs, etc, I'll figure it out.
On Sat, 18 Oct 2014 14:03:07 -0400
Michael Orlitzky m...@gentoo.org wrote:
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 the bugzilla API allows it, a very simple script should be able to
do
On Sun, 19 Oct 2014 10:14:18 +0200
Jeroen Roovers j...@gentoo.org wrote:
On Sat, 18 Oct 2014 14:03:07 -0400
Michael Orlitzky m...@gentoo.org wrote:
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
Am Samstag, 18. Oktober 2014, 19:34:52 schrieb Pacho Ramos:
Perhaps a stupid question, but: why is it a problem if the logs are
linked rather than attached?
Supposedly we always must attach files to bug reports to ensure they are
kept forever with that bug reports instead of relying on
On Sun, Oct 19, 2014 at 8:10 AM, Andreas K. Huettel
dilfri...@gentoo.org wrote:
Am Samstag, 18. Oktober 2014, 19:34:52 schrieb Pacho Ramos:
Perhaps a stupid question, but: why is it a problem if the logs are
linked rather than attached?
Supposedly we always must attach files to bug
Rich Freeman:
If maintainers want to NEEDINFO or WONTFIX a tinderbox bug, well,
they'll be the ones picking up the pieces when the gcc upgrade moves
ahead.
We are all picking up the pieces.
I don't get why anybody wouldn't like seeing them.
I do, it's childish and uncollaborative
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,
On 10/11/14 22:06, Rich Freeman wrote:
On Sat, Oct 11, 2014 at 5:27 PM, Anthony G. Basile bluen...@gentoo.org wrote:
I would say the following still should be fixed:
...
These look like some namespace issues, and different use of registers (on
x86). #46 is hardened specific.
Do any of
On Sun, Oct 12, 2014 at 8:23 AM, Anthony G. Basile bluen...@gentoo.org wrote:
I'm working on that. I'm not sure that #46 is hardened i686 specific
right now. I'm hitting it on vm with even the vanilla gcc so something else
might be going on here.
VLC built fine on stable amd64 with
On 10/12/14 11:05, Rich Freeman wrote:
On Sun, Oct 12, 2014 at 8:23 AM, Anthony G. Basile bluen...@gentoo.org wrote:
I'm working on that. I'm not sure that #46 is hardened i686 specific
right now. I'm hitting it on vm with even the vanilla gcc so something else
might be going on here.
Hi,
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 scritto:
In my earlier thread
In my earlier thread
http://thread.gmane.org/gmane.linux.gentoo.devel/92113 I explored the
possibility to stabilize gcc-4.8, and we have that going now in
https://bugs.gentoo.org/show_bug.cgi?id=516152.
Meanwhile I just applied a small patch for chromium-38 that allows it to
compile with gcc-4.7.
I took a look a the list of the current blocker of gcc-4.8 and many /
most of them seem to be hardend or x86 related. Right now I'm using an
amd64 linux with some freaky lto + heavily optimized make.conf
flags and didn't find a gcc-4.8 related bug.
Except the usual list of package just not ready
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 consensus that this is going to be a stable target
it might make sense to start running mixed stable+gcc-4.8 systems as
widely as
Am Samstag, 11. Oktober 2014, 22:28:08 schrieb Rich Freeman:
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 consensus that this is going to be a stable target
it might make
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 consensus that this is going to be a stable target
it might make sense to start running
On Sat, Oct 11, 2014 at 5:27 PM, Anthony G. Basile bluen...@gentoo.org wrote:
I would say the following still should be fixed:
...
These look like some namespace issues, and different use of registers (on
x86). #46 is hardened specific.
Do any of these actually apply to non-hardened
67 matches
Mail list logo
