On Tuesday, March 08, 2011 11:38:21 am Anne nicolas wrote:
> 2011/3/8 Per Øyvind Karlsen :
> > 2011/3/3 Buchan Milne :
> >> - "devzero2000" wrote:
> >>> Apart from the rest - of which i will ask for sponsorship when it
> >>> will
> >>> be - I wanted to know if there are plans to move to rpm5 b
Le lundi 28 mars 2011 à 22:21 +0200, Remy CLOUARD a écrit :
> Hello,
>
> Version freeze is in 3 weeks.
Did we prevent in the past from uploading new packages during version
freeze ?
> In the meantime, I need to package some
> other ruby modules, but I would like to hear about your needs concern
Hello,
Version freeze is in 3 weeks. In the meantime, I need to package some
other ruby modules, but I would like to hear about your needs concerning
these modules.
At the moment I plan to do the following packages:
- passenger (a must have IMHO)
- thin
- rainbows
- unicorn
- gem2rpm (need to int
Hello
On lundi 28 mars 2011 at 00:33, andre999 wrote :
> If we want to avoid the situation where people are dissatisfied because
> the DVD they install produces a Mageia system where the hardware doesn't
> work properly, we have to provide a single DVD that is complete, in
> terms of hardware dr
'Twas brillig, and Pierre Jarillon at 02/03/11 21:11 did gyre and gimble:
> Le mercredi 2 mars 2011 16:29:20, Anne nicolas a écrit :
>> So I guess rpm5 is not for now a priority given the size of pending
>> todo list. Also If we do have a look on it, we will for better have a
>> team on it rather t
Thierry Vignaud writes:
> On 21 March 2011 23:16, Mageia Team wrote:
>> Mageia Mirrors management
>
> Please can we've a real description?
> We mere mortals cant understand what this package is about...
It's the web software (Catalyst) behind mirrors.mageia.org, written by Nanar
--
Olivier Bl
hello everyone,
i've been testing the mageia alpha-1 and -2 and i stumbled over a weird
behaviour of my lovely dropbox client.
(dropbox is a sync service) the client is available for fedora and ubuntu
and as tar archive for compilation.
the package as the comiled sources don't do very much, they
hello everyone,
i've been testing the mageia alpha-1 and -2 and i stumbled over a weird
behaviour of my lovely dropbox client.
(dropbox is a sync service) the client is available for fedora and ubuntu
and as tar archive for compilation.
the package as the comiled sources don't do very much, they
Le 21/03/2011 16:10, Stefano Negro a écrit :
>
>
> 2011/3/21 Thorsten van Lil mailto:tv...@gmx.de>>
>
> The last time I installed Ubuntu (one year ago, i think) it detected my
> mandriva installation and set it up in the grub. Nevertheless it doesn't
> worked and I had to manipulate grub
Hello,
I thought it would be a good idea to include the list of ISP for Peru in the
first Mageia. There are three companies here for 3G USB modem Internet
connections: Claro, Nextel and Movistar.
Claro configuration is:
APN: claro.pe (no longer tim.com.pe, as it says in Mandriva 2010.2)
user
Thanks.
-Original Message-
From: Raphaël Jadot
Sent: 02/03/2011, 17:41
To: Mageia development mailing-list
Subject: Re: [Mageia-dev] RPM5 AND MAGEIA
2011/3/2 devzero2000 :
> Hi to Mageia
Hi :)
>
>
> is there interest? Then if someone wants to directly participate in
> rpm5 I think tha
Hi to Mageia
I am part of rpm5 (but I follow rpm from more than 10 years) and
recently I did join Mageia, although I almost always used for work
other distros and OS (AIX, SVR4) that I also deal with Mandriva and
security (CEH) https: / /
www.redhat.com/wapps/training/certification/verify.html?cer
Le jeudi 3 mars 2011 10:53:25, Buchan Milne a écrit :
> rpm5 has wasted more than half of the time I could afford to contribute to
> Mandriva. It seems Mandriva has resources to waste, I don't think we have.
I fully agree. The users don't bother if it works with rpm4 or rpm5 or rpm17,
they want o
Le mercredi 2 mars 2011 16:29:20, Anne nicolas a écrit :
> So I guess rpm5 is not for now a priority given the size of pending
> todo list. Also If we do have a look on it, we will for better have a
> team on it rather than one guy to avoid single point of failure.
>
Clever decision, I fully agre
On 28 March 2011 13:13, Olivier Blin wrote:
> blino 0.16.3-3.mga1:
> + Revision: 78257
> - add back conflicts, needed because of
> girepository-1.0/Poppler-0.16.typelib
Then fix installation on a biarch machine...
>>>
>>> There is no file conflicts between libpopppler i
Thierry Vignaud writes:
> On 28 March 2011 11:31, Olivier Blin wrote:
blino 0.16.3-3.mga1:
+ Revision: 78257
- add back conflicts, needed because of
girepository-1.0/Poppler-0.16.typelib
>>>
>>> Then fix installation on a biarch machine...
>>
>> There is no file conflicts b
On 28 March 2011 11:31, Olivier Blin wrote:
>>> blino 0.16.3-3.mga1:
>>> + Revision: 78257
>>> - add back conflicts, needed because of
>>> girepository-1.0/Poppler-0.16.typelib
>>
>> Then fix installation on a biarch machine...
>
> There is no file conflicts between libpopppler i586 and x86_64 p
Thierry Vignaud writes:
> On 28 March 2011 10:14, Mageia Team wrote:
>> blino 0.16.3-3.mga1:
>> + Revision: 78257
>> - add back conflicts, needed because of girepository-1.0/Poppler-0.16.typelib
>
> Then fix installation on a biarch machine...
There is no file conflicts between libpopppler i58
On Mon, Mar 28, 2011 at 10:17, Oliver Burger wrote:
> What is our policy about "tainted packages"? It's quite clear we have to check
> every one of them, if they can be distributed by us, but do we have any
> guidlines?
The guidelines should be progressive: what goes into core, what goes
into non
On 28 March 2011 10:32, Michael scherer wrote:
>> >> - remove duplicate package entries (it breaks clean-rpmsrate), by
>> >> removing META_CLASS check
>> >
>> > was it not caught by check_rpmsrate which is supposed to be run in %check?
>>
>> Nope, it wasn't.
>> check_rpmsrate only uses DrakX's rp
On 28 March 2011 10:14, Mageia Team wrote:
> blino 0.16.3-3.mga1:
> + Revision: 78257
> - add back conflicts, needed because of girepository-1.0/Poppler-0.16.typelib
Then fix installation on a biarch machine...
On Mon, Mar 28, 2011 at 10:06:17AM +0200, Olivier Blin wrote:
> Thierry Vignaud writes:
>
> > On 28 March 2011 05:01, Mageia Team wrote:
> >> blino 1:1-14.mga1:
> >> + Revision: 78203
> >> - remove duplicate package entries (it breaks clean-rpmsrate), by removing
> >> META_CLASS check
> >
> >
Hi,
since the package version freeze is coming nearer (April, 20th), perhaps we
should discuss the "tainted" issue once more.
What is our policy about "tainted packages"? It's quite clear we have to check
every one of them, if they can be distributed by us, but do we have any
guidlines?
What
Thierry Vignaud writes:
> On 28 March 2011 05:01, Mageia Team wrote:
>> blino 1:1-14.mga1:
>> + Revision: 78203
>> - remove duplicate package entries (it breaks clean-rpmsrate), by removing
>> META_CLASS check
>
> was it not caught by check_rpmsrate which is supposed to be run in %check?
Nope
24 matches
Mail list logo
