-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-12-2010 19:13, Alec Warner wrote:
> On Tue, Nov 30, 2010 at 8:02 PM, Jorge Manuel B. S. Vicetto
> wrote:
> On 29-11-2010 10:34, Sebastian Pipping wrote:
On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote:
> There will probably
On Wed, 01 Dec 2010 21:58:20 +0100
"Paweł Hajdan, Jr." wrote:
> So we have some automatic reporting. Can we have a webpage for
> that, or a mailing list that people can subscribe to?
Mailing list: http://bugs.gentoo.org/329165
I have no idea how to go about doing an automated webpage or other
in
On Wed, 01 Dec 2010 21:58:20 +0100, Paweł Hajdan, Jr. wrote:
On 12/1/10 9:34 PM, Joshua Saddler wrote:
Catalyst sends automated emails to rel...@gentoo.org from the
various build boxes: dolphin, poseidon, other dev.g.o machines.
So we have some automatic reporting. Can we have a webpage for th
On 12/1/10 9:34 PM, Joshua Saddler wrote:
> Catalyst sends automated emails to rel...@gentoo.org from the
> various build boxes: dolphin, poseidon, other dev.g.o machines.
So we have some automatic reporting. Can we have a webpage for that, or
a mailing list that people can subscribe to?
Idea: ma
On 12/1/10 9:13 PM, Alec Warner wrote:
>> How does a developer know when the stage generation is broken? Is
>> there a dashboard? At work we have a guy who is basically a build cop
>> and checks our build dashboard once a day or so and if it is broken he
>> goes and finds the guy who broke it and
On Wed, 1 Dec 2010 12:13:03 -0800
Alec Warner wrote:
> On Tue, Nov 30, 2010 at 8:02 PM, Jorge Manuel B. S. Vicetto
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 29-11-2010 10:34, Sebastian Pipping wrote:
> >> On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrot
On Tue, Nov 30, 2010 at 8:02 PM, Jorge Manuel B. S. Vicetto
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 29-11-2010 10:34, Sebastian Pipping wrote:
>> On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote:
>>> There will probably be no active version of Python set.
>>
>>
On 12/01/10 05:02, Jorge Manuel B. S. Vicetto wrote:
> As Arfrever noted, this is likely the cause of the broken automated
> weekly stages for this past week. By not having a python symlink /
> wrapper, stages generation failed on stage2 run.
Yes, a fellow dev already reported that issue to me.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-12-2010 03:02, Jorge Manuel B. S. Vicetto wrote:
> On 29-11-2010 10:34, Sebastian Pipping wrote:
> As Arfrever noted, this is likely the cause of the broken automated
> weekly stages for this past week. By not having a python symlink /
> wrapper,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29-11-2010 10:34, Sebastian Pipping wrote:
> On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote:
>> There will probably be no active version of Python set.
>
> You had two weeks to come up with this.
>
> Please find my on IRC to team up
On 11/29/10 09:35, Arfrever Frehtes Taifersar Arahesis wrote:
> There will probably be no active version of Python set.
You had two weeks to come up with this.
Please find my on IRC to team up on an agreed fix.
Sebastian
2010-11-29 08:39:46 Sebastian Pipping napisał(a):
> On 11/28/10 19:04, Arfrever Frehtes Taifersar Arahesis wrote:
> > You probably broke generation of stages :) .
> > (I have restored a minimal version of eselect_python_update() in python
> > overlay.)
>
> Could you elaborate on that, please? Ho
On 11/28/10 19:04, Arfrever Frehtes Taifersar Arahesis wrote:
> You probably broke generation of stages :) .
> (I have restored a minimal version of eselect_python_update() in python
> overlay.)
Could you elaborate on that, please? How did I break stages? Which
stages? Future stage tarballs?
2010-11-27 14:00:28 Sebastian Pipping napisał(a):
> On 11/14/10 17:28, Sebastian Pipping wrote:
> > So I plan to remove the call to eselect_python_update from all Python
> > ebuilds in two weeks from now.
>
> Now fixed in both the main tree as well as the Python overlay.
> Please let me know in ca
On 11/14/10 17:28, Sebastian Pipping wrote:
> So I plan to remove the call to eselect_python_update from all Python
> ebuilds in two weeks from now.
Now fixed in both the main tree as well as the Python overlay.
Please let me know in case I broke anything.
Best,
Sebastian
On 11/15/2010 02:02 PM, Alexis Ballier wrote:
> Since none are slotted, I don't understand what outcome you expect by
> contacting the maintainers.
> At best, perl-cleaner and ocaml-rebuild.sh shall be merged into portage in a
> preserve-libs like manner.
In case some aren't aware, I'll mention
On Monday 15 November 2010 11:37:08 Sebastian Pipping wrote:
> On 11/14/10 22:42, Florian Philipp wrote:
> > Is there a chance to do the same for perl and perl-cleaner?
> >
> > I understand perl is not slotted at the moment and there are probably
> > good technical reasons for not doing so but I s
On 11/14/10 22:42, Florian Philipp wrote:
> Is there a chance to do the same for perl and perl-cleaner?
>
> I understand perl is not slotted at the moment and there are probably
> good technical reasons for not doing so but I still wanted to ask. :)
I'm not sure if the Perl team is watching this
Am 14.11.2010 17:28, schrieb Sebastian Pipping:
>
> With Python, when you install a newer version if gets activated, leaving
> your system in broken state. An update of Python always involves
> running python-updater. If the user/admin has to run that anyway, why
> should we take the call to ese
Hello,
thanks for your interest. This thread is not about Python 3.x in
particular, in case you wonder.
In this mail
- Typical GCC update (for comparison)
- Python 2.7 update simulation (and how it fails)
- The scenario
- What happens
- How it happens
- Conclusion
Typical
20 matches
Mail list logo
