On Sun, Sep 12, 2010 at 7:52 AM, Evangelos Foutras wrote:
> I noticed that my python-jinja, python-pygments and python-south
> packages aren't on the rebuild list. Shall I add them myself, or can
> the list be regenerated?
>
I added them. BTW, last night I had to add lirc-utils to the list as
it
I noticed that my python-jinja, python-pygments and python-south
packages aren't on the rebuild list. Shall I add them myself, or can
the list be regenerated?
On Thu, 9 Sep 2010 18:57:18 +0300, Evangelos Foutras
wrote:
> On Thu, Sep 9, 2010 at 4:22 PM, Pierre Schmitz wrote:
>> On Sun, 29 Aug 2010 18:05:47 +0200, Pierre Schmitz
>> wrote:
>>> On Mon, 30 Aug 2010 00:48:06 +1000, Allan McRae
>>> wrote:
Just a reminder for people to look at their pac
On Thu, Sep 9, 2010 at 4:22 PM, Pierre Schmitz wrote:
> On Sun, 29 Aug 2010 18:05:47 +0200, Pierre Schmitz
> wrote:
>> On Mon, 30 Aug 2010 00:48:06 +1000, Allan McRae
>> wrote:
>>> Just a reminder for people to look at their packages and rebuild them
>>> for this. We seem to of stalled majorly.
Rémy Oudompheng writes:
> I have generated the attached quick-and-dirty list of safe packages
> from the wiki. There could be false positives, of course.
===begin list===
*SNIP*
> jython
Actually, this doesn't need a rebuild at all. jython doesn't rely on the C
implementation of Python for any
On Sun, 29 Aug 2010 13:31:16 -0500, Christopher Brannon
wrote:
>> Any updates regarding the creation of a [community-staging] repository?
>
> +1. Most of my packages are rebuilt; I'm just waiting to push.
>
> -- Chris
I could add it to dbscripts and devtools easily; but some admin of
sigurd ne
> Any updates regarding the creation of a [community-staging] repository?
+1. Most of my packages are rebuilt; I'm just waiting to push.
-- Chris
On Sun, Aug 29, 2010 at 5:48 PM, Allan McRae wrote:
> On 18/08/10 01:46, Allan McRae wrote:
>>
>> Hi,
>>
>> I have pushed the new python (3.1) and python2 (2.7) packages to the new
>> [staging] repo so rebuilds can start there. Remember the staging repo
>> should never be used outside a build chro
On 18/08/10 02:27, Rogutės Sparnuotos wrote:
Allan McRae (2010-08-18 01:46):
Hi,
I have pushed the new python (3.1) and python2 (2.7) packages to the
new [staging] repo so rebuilds can start there. Remember the
staging repo should never be used outside a build chroot... If you
do, everything
Allan McRae (2010-08-18 01:46):
> Hi,
>
> I have pushed the new python (3.1) and python2 (2.7) packages to the
> new [staging] repo so rebuilds can start there. Remember the
> staging repo should never be used outside a build chroot... If you
> do, everything python related will break on your s
On Tue, Aug 17, 2010 at 10:46 AM, Allan McRae wrote:
>
> Hi,
>
> I have pushed the new python (3.1) and python2 (2.7) packages to the new
> [staging] repo so rebuilds can start there. Remember the staging repo
> should never be used outside a build chroot... If you do, everything python
> re
11 matches
Mail list logo
