Re: [Mageia-dev] Adding a new license to rpmlint

[Dan Fandrich]

On Tue, Feb 07, 2012 at 11:06:00PM -0500, Juan Luis Baptiste wrote:
> I did a clean mga2 alpha3 install, updated it to cauldron, and just
> installed mgarepo, bm and warsow's spec BR and again it builds fine.
> 
> arrgghhh I don't know why it fails on the BS !! the only thing I
> noticed comparing the build logs from the local build against the BS
> build is that stuff is built in a different order, also the linking,
> but I really don't have a clue of what's going on :(
> 
> 
> Can someone please please pretty please take a look ? here are the logs:
> 
> http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120201173847.juancho.valstar.7315/

It's very likely a missing dependency in the make files. The build
server uses the make -j24 flag, so it's going to build the various
modules in a very different order than without that flag. Ideally, you
would find the missing dependecy and patch the make files, but you could
also just remove the -j24 and have make build it sequentially instead
(at up to 24 times slower, of course).

>>> Dan

[Mageia-dev] problem with obsoleting packages

[Kamil Rytarowski]

Hello!

I've got problem with obsoleting some myspell packages.

$ rpm -qa|grep csb
myspell-csb_CSB-1.0.2-30.mga1
hunspell-csb-0.20050311.1-7.mga2

$ urpmq --provides myspell-csb_CSB
myspell-pl[== 1.0.2-30.mga1]
myspell-dictionary[== 1.0.2-30.mga1]
enchant-dictionary[== 2]
myspell-csb_CSB[== 1.0.2-30.mga1]

$ urpmq --provides hunspell-csb
enchant-dictionary[== 2]
hunspell-dictionary
hunspell-csb_PL[== 0.20050311.1-7.mga2]
dictionary-csb[== 2]
dictionary-csb_PL[== 2]
myspell-csb
myspell-csb_CSB
hunspell-csb[== 0.20050311.1-7.mga2]


$ urpmq --obsoletes hunspell-csb
myspell-csb[<= 1.0.2-30]
myspell-csb_CSB[<= 1.0.2-30]

The obsoleting is working when I'm adding ending ".mga1.noarch". Where 
is the problem? Am I doing something wrong?

Re: [Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases

[andre999]

Maarten Vanraes a écrit :

Op maandag 06 februari 2012 08:50:21 schreef Sander Lepik:
   

06.02.2012 09:38, Funda Wang kirjutas:
 

And, don't forget, we still have a package named firefox-beta. If we
stick with FF10, then some day we will come to a situation of
firefox-10.0.4 and firefox-beta-15b1 for Mageia 2, which is
unacceptable. Or, we should make an exception on firefox-beta, it
should be obsoleted by updated firefox for stable distros.
   


The long-term support versions just obsolete lower-numbered 
non-long-term-support versions.



Indeed, firefox-beta must be obsoleted on stable release like chrome's
similar versions are as we don't have maintaner who wants to keep them
up-to-date on stable releases.
I agree with D.Morgan that if we want to continue with ESR version then
cauldron will stay on 10.0 (not sure how we can have newer versions of
beta if they depend on the same packages).
And it's also true that we will lose some users if they don't want to
use tarball version and will pick distro that can keep browsers
up-to-date. Sad, but true.

(Funda, can you please stop top-posting. This is rude man!)

--
Sander
 

possibly if someone has time, they could try to maintain/backport the non-ESR
branch...

but imho, if people want the latest, they don't wait for packagers to
finish+test it in one week, the get upstream version...

so the other persons are fine with ESR versions... imho

   

+1
I doubt that we will lose any (or many) users interested in the latest 
version, as all distros will be faced with this time lag relative to 
upstream.


--
André

Re: [Mageia-dev] Seamonkey mga1 package missing updates - mozilla branding issues -- was [Seamonkey package]

[andre999]

Kamil Rytarowski a écrit :

On 06.02.2012 22:15, Florian Hubold wrote:

Am 06.02.2012 21:43, schrieb Kamil Rytarowski:


In my opinion we can drop that package, and in its place have 
Firefox-ESR,

next to standard Firefox.


How are we supposed to drop seamonkey/iceape from a released distro?
BTW: Do you use seamonkey/iceape, and know how it is different from a
standalone browser like firefox?
I'm thinking about Mageia 2 right now. It seems there is a maintainer 
lacking for many months.


Yes, I know. It's different from Friefox and Thunderbird, but in my 
opinion for a standard user it's replaceable by ff and tb.



Seamonkey = firefox + composer + thunderbird + chatzilla
I find it convenient to have them all installed together, and running 
firefox + thunderbird at the same time takes more memory than seamonkey 
with the navigator and email agent open.  (Unless that has changed.)
There is also the plus of adding new navigator features to seamonkey 
after they have been tested on firefox, so there are somewhat fewer bugs.
Now I'm using upstream Seamonkey, but it would be nice to have an 
up-to-date version in Mageia.

(When I have more time, I might be interested in maintaining it myself.)

--
André

Re: [Mageia-dev] Adding a new license to rpmlint

[Juan Luis Baptiste]

On Fri, Feb 3, 2012 at 12:00 AM, Juan Luis Baptiste  wrote:
> Sorry for the late reply, I went into vacations just after this...
>
> On Fri, Jan 20, 2012 at 11:13 AM, Balcaen John  wrote:
>> On Friday 20 January 2012 10:39:18 Juan Luis Baptiste wrote :
>> g++: error:
>> ../libsrcs/angelscript/angelSVN/sdk/angelscript/lib/libangelscript.a: No such
>> file or directory
>> make: *** [release/libs/angelwrap_x86_64.so] Error 1
>>
>> The error seems to be here.
>>
>
> I'm not sure that's the error as I have seen it too with my local
> build and still builds fine.
>
> Any other ideas ? I'm stuck with this.. :S
>

I did a clean mga2 alpha3 install, updated it to cauldron, and just
installed mgarepo, bm and warsow's spec BR and again it builds fine.

arrgghhh I don't know why it fails on the BS !! the only thing I
noticed comparing the build logs from the local build against the BS
build is that stuff is built in a different order, also the linking,
but I really don't have a clue of what's going on :(


Can someone please please pretty please take a look ? here are the logs:

http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120201173847.juancho.valstar.7315/


Thanks in advance.

-- 
Juancho

Re: [Mageia-dev] -- mozilla branding issues -- was [Seamonkey package]

[andre999]

Julien a écrit :

Le Mon, 06 Feb 2012 21:04:05 +0100,
Florian Hubold  a écrit :

   

Am 12.01.2012 16:55, schrieb Florian Hubold:
 

Am 07.01.2012 18:36, schrieb Florian Hubold:
   

Am 16.04.2011 16:05, schrieb Christiaan Welvaart:
 

On Fri, 11 Mar 2011, Tux99 wrote:

   

(...)
   

Pinging again, because nobody replied. This should also be discussed
at next packager meeting, together with the situation according the
branding of other mozilla packages. Because we have branding enabled,
which we shouldn't have as we can't use branding AND have modified builds
(different than upstream tarball)
without approval of all modifications from mozilla.


For reference, here's the upstream report i was talking about, which i've
recently found again:
https://bugzilla.mozilla.org/show_bug.cgi?id=555935

--

resending because of maintainer mail adress typo
 

FTR, the Mozilla trademark policy :
https://www.mozilla.org/foundation/trademarks/policy.html

the relevant part :

"  Modifications

If you're taking full advantage of the open-source nature of Mozilla's
products and making significant functional changes, you may not
redistribute the fruits of your labor under any Mozilla trademark, without
Mozilla's prior written consent. For example, if the product you've
modified is Firefox, you may not use Mozilla or Firefox, in whole or in
part, in its name. Also, it would be inappropriate for you to say "based on
Mozilla Firefox". Instead, in the interest of complete accuracy, you could
describe your executables as "based on Mozilla technology", or
"incorporating Mozilla source code." In addition, you may want to read the
discussion on the "Powered by Mozilla" logo.

In addition, if you compile a modified version, as discussed above, with
branding enabled (the default in our source code is branding disabled), you
will require Mozilla's prior written permission. If it's not the unmodified
installer package from www.mozilla.com, and you want to use our
trademark(s), our review and approval of your modifications is required.
You also must change the name of the executable so as to reduce the chance
that a user of the modified software will be misled into believing it to be
a native Mozilla product.

Again, any modification to the Mozilla product, including adding to,
modifying in any way, or deleting content from the files included with an
installer, file location changes, added code, modification of any source
files including additions and deletions, etc., will require our permission
if you want to use the Mozilla Marks. If you have any doubt, just ask us at
tradema...@mozilla.com.
"

regards
Julien

   

The key words seem to be "significant functional changes".
If we use the Mozilla tarball, and just apply Mozilla patches, we 
shouldn't require any special permission for that.
They do say that additionally we would require written permission to 
compile the source with branding enabled.
Since the source tarball can be installed wherever the user wants, only 
changing the relative locations would potentially be problematic.


In any case, I'm in favour of packaging all of 
Firefox/Thunderbird/Seamonkey, essentially unmodified, and in the 
extended support versions where available.
(Not trying to say that we shouldn't package filerunner separately.  Or 
add security patches not yet added by Mozilla.  Both of which would 
require approval from Mozilla.)


The suggested -ESR suffix for extended support releases seems a good idea.
Alternately, we could tag them with the version, but that would be less 
evident.


--
André

Re: [Mageia-dev] Grub and Grub2

[Michel Catudal]

  
  
Le 2012-02-07 06:39, Maurice Batey a écrit :

  On Mon, 06 Feb 2012 19:39:24 -0500, Michel Catudal wrote:


  
You didn't understand what I said. 

  
  
  I know! :-(


  
The xosl install that I have runs off a floppy diskette which has been
formatted to PC DOS. You should be able to find dos bootable image on the
net. xosl has a nice graphic install.

  
  
  Do you have a step-by-step description of how to create such floppy, please?

(1st problem is: what do you mean by 'formatted to PC DOS'?

Exactly that, formatted with PC Dos boot on it. I don't think that
you can buy PC Dos anymore. You can get freedos boot disk.
Even a DRDOS, win 95 or win 98 boot disket would work.

They don't seem to have a boot disk with the new freedos 1.1, If you
have a small partition you can install freedos on it.

http://www.freedos.org/
http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/


  
   Write a disk image to the floppy?
   Presumably not simply --> FAT32, as the disk will be booted.


Slackware provides programs to do that, some that run under dos,
windows and Linux

You don't have FAT32 on a floppy, it's too small, its FAT16.
http://www.bootdisk.com/helpdesk.htm



  
   What files need to be found and put on the floppy? Where from?)




http://sourceforge.net/projects/xosl/files/xosl/xosl%20%201.1.5/

For boot the minimum number of files. On PC DOS there is some hidden
files and command.com
With a minimum number of files you can still have room for a backup
of the MBR. With a win 95 boot that should be possible also.
It gets too big with a win98 boot. Ideally you would have a
partition with freedos and a boot disk in case the MBR gets whacked.
Your freedos partition needs to be less 2G or smaller.

On my computer I first partitioned the disk with fdisk with a SuSE
boot CD. I then installed free dos

michel@catudal ~/Téléchargement/temp $ dir /mnt/freedos/FDOS/XOSL/
total 1276
drwxrwxrwx  2 michel michel   4096 12 fév  2011 .
drwxrwxrwx 29 michel michel   4096 12 fév  2011 ..
-rwxrwxrwx  1 michel michel   4096 12 fév  2011 BOOTITEM.XDF
-rwxrwxrwx  1 michel michel    512 16 fév  2000 CURR_MBR.XCF
-rwxrwxrwx  1 michel michel    512 26 nov  1999 DEFAULT.MBR
-rwxrwxrwx  1 michel michel   7936 24 aoû  1999 DEFAULT.XFF
-rwxrwxrwx  1 michel michel   8192  1 jui  2000 EXTRA.XFF
-rwxrwxrwx  1 michel michel  24553 23 déc  2000 INSTALL.EXE
-rwxrwxrwx  1 michel michel    440 23 déc  2000 IPL06.BIN
-rwxrwxrwx  1 michel michel    440 23 déc  2000 IPL06LBA.BIN
-rwxrwxrwx  1 michel michel    440 23 déc  2000 IPL0B.BIN
-rwxrwxrwx  1 michel michel    440 23 déc  2000 IPL0BLBA.BIN
-rwxrwxrwx  1 michel michel    512 23 déc  2000 IPLS.BIN
-rwxrwxrwx  1 michel michel    512 23 déc  2000 IPLSLBA.BIN
-rwxrwxrwx  1 michel michel   2333 23 déc  2000 NOTES.TXT
-rwxrwxrwx  1 michel michel    512 12 fév  2011 ORIG_MBR.XCF
-rwxrwxrwx  1 michel michel 403462 12 fév  2011 PARTIMG.BIN
-rwxrwxrwx  1 michel michel  60684  8 déc  2000 SBMINST.EXE
-rwxrwxrwx  1 michel michel    512 12 fév  2011 SBM_IPL0.XCF
-rwxrwxrwx  1 michel michel  31828 24 aoû  1999 SPLASHLG.XBF
-rwxrwxrwx  1 michel michel    512 12 fév  2011 XOSLDATA.XDF
-rwxrwxrwx  1 michel michel 401408 12 fév  2011 XOSLIMG.FS
-rwxrwxrwx  1 michel michel  19970 23 déc  2000 XOSLIMG0.XXF
-rwxrwxrwx  1 michel michel  32768 23 déc  2000 XOSLIMG1.XXF
-rwxrwxrwx  1 michel michel  32768 23 déc  2000 XOSLIMG2.XXF
-rwxrwxrwx  1 michel michel  32768 23 déc  2000 XOSLIMG3.XXF
-rwxrwxrwx  1 michel michel  32768 23 déc  2000 XOSLIMG4.XXF
-rwxrwxrwx  1 michel michel  17011 23 déc  2000 XOSLIMG5.XXF
-rwxrwxrwx  1 michel michel   7820 23 déc  2000 XOSLLOAD.XCF
-rwxrwxrwx  1 michel michel  31828 24 aoû  1999 XOSLLOGO.XBF
-rwxrwxrwx  1 michel michel  22500 24 aoû  1999 XOSLWALL.XBF
-rwxrwxrwx  1 michel michel  32768 27 fév  2000 XRPART00.XXF
-rwxrwxrwx  1 michel michel  32768 27 fév  2000 XRPART01.XXF

michel@catudal ~/Téléchargement/temp $ du /mnt/freedos/FDOS/XOSL/
1272    /mnt/freedos/FDOS/XOSL/


michel@catudal ~/Téléchargement/temp $ df
Sys. fich. 1K-blocks Util. Disponible Uti% Monté sur
rootfs 481481584 182256920  294405916  39% /
udev   10240   432   9808   5% /dev
/dev/sda10 481481584 182256920  294405916  39% /
rc-svcdir   1024    84    940   9% /lib64/rc/init.d
cgroup_root    10240 0  10240   0% /sys/fs/cgroup
shm  2027500    88    2027412   1% /dev/shm
/dev/sda7 118656 50709  61925  46% /boot
/dev/sdb10 376508104  33424476  324237416  10%
/home/michel/vm_file

Re: [Mageia-dev] Cannot compile LLVM/Clang under Mageia 1

[Thierry Vignaud]

On 7 February 2012 22:58, Dan Fandrich  wrote:
>> > I do need this compiler and think it can be useful for programmers.
>> >
>> > I thank you by advance for your help.
>> >
>> > Thomas Lottmann aka Skiper.
>>
>> bugzilla is about Mageia bugs, not about your own compilation issues.
>> So I closed this BR.
>
> The bug report was an RPM package request. The compile problem is really
> a side issue (although still relevant to whoever takes on the bug report
> eventually and packages clang). The bug report should be reopened unless
> it's deemed that clang is not to be packaged in Mageia at this time.

The package already exist so it cannot be a new package request.
It's just older in mga1 (but up to date in mga2)

The new LLVM release needs updating dependencies.
If one wants the newer LLVM, he should switch to cauldron or wait for mga2.
We won't update the build chain in mga1.

Re: [Mageia-dev] Cannot compile LLVM/Clang under Mageia 1

[Florian Hubold]

Am 07.02.2012 22:58, schrieb Dan Fandrich:
> On Tue, Feb 07, 2012 at 10:43:31PM +0100, Thierry Vignaud wrote:
>> On 7 February 2012 20:02, Thomas Lottmann  wrote:
>>> https://bugs.mageia.org/show_bug.cgi?id=4179
>>>
>>> I do need this compiler and think it can be useful for programmers.
>>>
>>> I thank you by advance for your help.
>>>
>>> Thomas Lottmann aka Skiper.
>> bugzilla is about Mageia bugs, not about your own compilation issues.
>> So I closed this BR.
> The bug report was an RPM package request. The compile problem is really
> a side issue (although still relevant to whoever takes on the bug report
> eventually and packages clang). The bug report should be reopened unless
> it's deemed that clang is not to be packaged in Mageia at this time.
Also it could be interesting why the error message displays:

Consultez  pour plus de détail.


>
 Dan

Re: [Mageia-dev] Cannot compile LLVM/Clang under Mageia 1

[Dan Fandrich]

On Tue, Feb 07, 2012 at 10:43:31PM +0100, Thierry Vignaud wrote:
> On 7 February 2012 20:02, Thomas Lottmann  wrote:
> > https://bugs.mageia.org/show_bug.cgi?id=4179
> >
> > I do need this compiler and think it can be useful for programmers.
> >
> > I thank you by advance for your help.
> >
> > Thomas Lottmann aka Skiper.
> 
> bugzilla is about Mageia bugs, not about your own compilation issues.
> So I closed this BR.

The bug report was an RPM package request. The compile problem is really
a side issue (although still relevant to whoever takes on the bug report
eventually and packages clang). The bug report should be reopened unless
it's deemed that clang is not to be packaged in Mageia at this time.

>>> Dan

Re: [Mageia-dev] Cannot compile LLVM/Clang under Mageia 1

[Thierry Vignaud]

On 7 February 2012 20:02, Thomas Lottmann  wrote:
> Hello everyone,
>
> I am just asking for a little help, as I cannot compile LLVM/Cland 3.0 under
> Mageia 1. And I just cannot figure out why I get the error I described in
> the following bug report.
>
> https://bugs.mageia.org/show_bug.cgi?id=4179
>
> I do need this compiler and think it can be useful for programmers.
>
> I thank you by advance for your help.
>
> Thomas Lottmann aka Skiper.

bugzilla is about Mageia bugs, not about your own compilation issues.
So I closed this BR.

Re: [Mageia-dev] [RFE] Bundled copies of system libraries - call for participation

[Maarten Vanraes]

Op dinsdag 07 februari 2012 14:42:22 schreef Florian Hubold:
> I've just whipped up
> https://wiki.mageia.org/en/Packages_carrying_bundled_copies_of_system_libra
> ries
> 
> It's purpose is listing and maybe documenting the reasons why
> some packages carry bundled copies of system libraries. I've begun
> with ffmpeg, as it has a rather bad record for security updates on
> Mageia 1 IMHO, as some security updates would almost have been
> missed, some were delayed for a long time, and some wouldn't
> have been noticed unless by accident.
> 
> Please, every packager participate, and list the packages you know about.
> Another good example would be xulrunner.

i added the internal readline  v5 for GPLv2 reasons

[Mageia-dev] Cannot compile LLVM/Clang under Mageia 1

[Thomas Lottmann]

Hello everyone,

I am just asking for a little help, as I cannot compile LLVM/Cland 3.0 
under Mageia 1. And I just cannot figure out why I get the error I 
described in the following bug report.


https://bugs.mageia.org/show_bug.cgi?id=4179

I do need this compiler and think it can be useful for programmers.

I thank you by advance for your help.

Thomas Lottmann aka Skiper.

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release embryo-1.1.0-0.r67715.1.mga2

[Thierry Vignaud]

On 7 February 2012 17:57, trem  wrote:
> trem  1.1.0-0.r67715.1.mga2:
> + Revision: 205979
> - update to release 67715
> - update to release 67703
> - update to release 67702
> - update to release 67698
> - update to release 67688
> - update to release 67680

Do we really get to package every SVN revision?

Re: [Mageia-dev] [RFE] Bundled copies of system libraries - call for participation

[Pascal Terjan]

On Tue, Feb 7, 2012 at 16:41, Guillaume Rousse  wrote:
> Le 07/02/2012 17:19, David Walser a écrit :
>
>> Another thing that would be helpful related to this would be to have an
>> install of rq in the Mageia infrastructure:
>> https://fedorahosted.org/rq/
>>
>> It can be used to see when some code is affected by a security
>> vulnerability if any other packages contain the same code.
>
> I guess you can use Sophie (http://sophie.zarb.org) for this kind of
> queries.

It has some more informations (symbols available in binaries, and
source file names in the source tarballs, to find bundled copies of
the vulnerable code)

Re: [Mageia-dev] [RFE] Bundled copies of system libraries - call for participation

[Guillaume Rousse]

Le 07/02/2012 17:19, David Walser a écrit :

Another thing that would be helpful related to this would be to have an install 
of rq in the Mageia infrastructure:
https://fedorahosted.org/rq/

It can be used to see when some code is affected by a security vulnerability if 
any other packages contain the same code.
I guess you can use Sophie (http://sophie.zarb.org) for this kind of 
queries.


--
BOFH excuse #207:

We are currently trying a new concept of using a live mouse. 
Unfortunately, one has yet to survive being hooked up to the 
computer.please bear with us.

Re: [Mageia-dev] [RFE] Bundled copies of system libraries - call for participation

[David Walser]

Florian Hubold wrote:
> I've just whipped up
> https://wiki.mageia.org/en/Packages_carrying_bundled_copies_of_system_libraries
> 
> It's purpose is listing and maybe documenting the reasons why
> some packages carry bundled copies of system libraries. I've begun
> with ffmpeg, as it has a rather bad record for security updates on
> Mageia 1 IMHO, as some security updates would almost have been
> missed, some were delayed for a long time, and some wouldn't
> have been noticed unless by accident.
> 
> Please, every packager participate, and list the packages you know about.
> Another good example would be xulrunner.
> 
> 
> PS: Maybe it should also be used to documented the packages which
> require some static linking, and the reasons, if there are any of these.

Thanks Florian.

Another thing that would be helpful related to this would be to have an install 
of rq in the Mageia infrastructure:
https://fedorahosted.org/rq/

It can be used to see when some code is affected by a security vulnerability if 
any other packages contain the same code.

[Mageia-dev] [RFE] Bundled copies of system libraries - call for participation

[Florian Hubold]

I've just whipped up
https://wiki.mageia.org/en/Packages_carrying_bundled_copies_of_system_libraries

It's purpose is listing and maybe documenting the reasons why
some packages carry bundled copies of system libraries. I've begun
with ffmpeg, as it has a rather bad record for security updates on
Mageia 1 IMHO, as some security updates would almost have been
missed, some were delayed for a long time, and some wouldn't
have been noticed unless by accident.

Please, every packager participate, and list the packages you know about.
Another good example would be xulrunner.


PS: Maybe it should also be used to documented the packages which
require some static linking, and the reasons, if there are any of these.

Re: [Mageia-dev] USB Flash drive broken since latest Cauldron updates

[Thierry Vignaud]

On 7 February 2012 12:01, Robert Fox  wrote:
> Feb  7 11:58:35 localhost kernel: usb 3-1: new low-speed USB device
> number 9 using uhci_hcd
> Feb  7 11:58:35 localhost kernel: usb 3-1: device not accepting address
> 9, error -71
> Feb  7 11:58:35 localhost kernel: usb 3-1: new low-speed USB device
> number 10 using uhci_hcd
> Feb  7 11:58:36 localhost kernel: usb 3-1: device not accepting address
> 10, error -71
> Feb  7 11:58:36 localhost kernel: hub 3-0:1.0: unable to enumerate USB
> device on port 1
>
> Although on other machines it works fine (both Mageia before the updates
> & Windows)
>
> What could this be?

This happens sometimes.
For years. So it's not related to any update.
Changing USB port or rebooting usually help

Re: [Mageia-dev] where are the live-isos? (was: Consolidation of the spell checkers - current status before Beta 1 and general version freeze)

[Anne nicolas]

2012/2/7 Christian Lohmaier :
> Hi *-

Hi there

>
> On Tue, Feb 7, 2012 at 3:23 AM, Kamil Rytarowski  wrote:
>>
>> We are just only one month before the version freeze and two weeks before
>> planned release of Beta 1.
>
> Not related to dictionaries/spell-checking engines, but isn't it still
> too early for beta, given that there still are no live isos of alpha3.
> The initial announcement mentioned a delay of about one week, but till
> today no sign of alpha3 live isos.

It took much more time than expected and we should provide live cds
for beta1 version in 2 weeks

>
> ciao
> Christian



-- 
Anne
http://www.mageia.org

Re: [Mageia-dev] Grub and Grub2

[Maurice Batey]

On Mon, 06 Feb 2012 19:39:24 -0500, Michel Catudal wrote:

> You didn't understand what I said. 

  I know! :-(

> The xosl install that I have runs off a floppy diskette which has been
> formatted to PC DOS. You should be able to find dos bootable image on the
> net. xosl has a nice graphic install.

  Do you have a step-by-step description of how to create such floppy, please?

(1st problem is: what do you mean by 'formatted to PC DOS'?
   Write a disk image to the floppy?
   Presumably not simply --> FAT32, as the disk will be booted.
   What files need to be found and put on the floppy? Where from?)

-- 
/\/\aurice 

[Mageia-dev] USB Flash drive broken since latest Cauldron updates

[Robert Fox]

When I plug in an 8G USB (fat32) thumbdrive - I get the following
errors:

Feb  7 11:58:34 localhost kernel: usb 3-1: new low-speed USB device
number 7 using uhci_hcd
Feb  7 11:58:34 localhost kernel: usb 3-1: device descriptor read/64,
error -71
Feb  7 11:58:34 localhost kernel: usb 3-1: device descriptor read/64,
error -71
Feb  7 11:58:34 localhost kernel: usb 3-1: new low-speed USB device
number 8 using uhci_hcd
Feb  7 11:58:34 localhost kernel: usb 3-1: device descriptor read/64,
error -71
Feb  7 11:58:35 localhost kernel: usb 3-1: device descriptor read/64,
error -71
Feb  7 11:58:35 localhost kernel: usb 3-1: new low-speed USB device
number 9 using uhci_hcd
Feb  7 11:58:35 localhost kernel: usb 3-1: device not accepting address
9, error -71
Feb  7 11:58:35 localhost kernel: usb 3-1: new low-speed USB device
number 10 using uhci_hcd
Feb  7 11:58:36 localhost kernel: usb 3-1: device not accepting address
10, error -71
Feb  7 11:58:36 localhost kernel: hub 3-0:1.0: unable to enumerate USB
device on port 1

Although on other machines it works fine (both Mageia before the updates
& Windows)

What could this be?

Thx,
R.Fox

[Mageia-dev] where are the live-isos? (was: Consolidation of the spell checkers - current status before Beta 1 and general version freeze)

[Christian Lohmaier]

Hi *-

On Tue, Feb 7, 2012 at 3:23 AM, Kamil Rytarowski  wrote:
>
> We are just only one month before the version freeze and two weeks before
> planned release of Beta 1.

Not related to dictionaries/spell-checking engines, but isn't it still
too early for beta, given that there still are no live isos of alpha3.
The initial announcement mentioned a delay of about one week, but till
today no sign of alpha3 live isos.

ciao
Christian

Re: [Mageia-dev] Look what i found here

[Olav Vitters]

On Mon, Feb 06, 2012 at 10:24:45PM +, Pascal Terjan wrote:
> In this case it was sent by Yahoo, so yes it seems this account was 
> compromised.
> The email was sent from 203.87.162.2, in Philippines

Exactly the same happens on the GNOME mailing lists. I usually ban the
people straight away. From my experience, even if you advise that
they're sending spam, the spam actually never stops (tried the friendly
approach initially).

I sometimes get similar compromised spam from people I know. Spam is
sent to pretty much everyone who ever emailed the compromised account.

-- 
Regards,
Olav