Fwd: Re: Beta install Test from 14.05/May 2013 i586 Iso (not x86_64)

Beta install Test from 14.05/May 2013 i586 Iso (not x86_64)

Hi,

install fine, no hangs , no hard problems ...
hey i see the vbox-mousedrivers !! Very fine !!
so it is use the vbox-grafics driver by auto too cool .. ! Good work !

hey, p.s. share the work, get the poor omv-developers the vbox-mouse too *s*
common, do it.. *vbg*

1.st boot :

Pease let configure the Grub2 to 1024x768 !!!!!! and not at all 
resolutions !!
i have there a 1600x1200  a normal Monitor stops to work ad tell it's to 
hih resolution !!
THIS IS IMPORTANT TO FIX !!!!

grub.cfg -> Set gfxmode = 1024x768 !!

boots very fast !! VERY NICE !!

VBox-x11 works not .. i like it, but..it is important to fix the auto 
configuration if possible
(but i don't have configuration it not yet mus does it now in the cli 
per drakx11 )

humpfffhh.... no VBox-mouse !! the rpm is not include ! Like in OMV !!

PLEASE CREATE X11-driver-input-vboxmouse-%version%-omv.rpm !!!!!

use now Vesadrivers.. restart !

2rd.Boot
grubconfig has reset to 1600x1200 !! any Screen on real hardware poops 
now off again !!
PLEASE RECONFIG GRUB TO 1024x768 !!!!

X starts now with Vesa and my config.

Oky, KDE works now like should ..

Betatest Finish...

To do

*Add the Online-Source-Button on the Source listing by the installer

*Please Fix the bugs Grub.cfg(+backup and recovering !)

*Create vbox-mouse drivers rpm and check it again for start the X11+vbox 
finaly.

*Please add on kde the Folder-Desktop too and maybe Standart KDE-Panel
and maby add diffrent paneelconfigurations too.. i like kbfx too..
looks more cooler as Startpoint (Startbutton) :)

*!! good news- Cleaned up the boot process, very good and very fast !! 
Super !!*

Next Step maybe, test  install groundconfiguration like
all what really need for install the rest..

kernel, bash, urpmi , network config and all what's need
to run via prompt only for add mirrorlist or special source

*check the Task- dependencies from at all in the install list

if do all this and it's clean so far, it's ready for Beta-ending :)

now i want test the x86_64

best Regards
Blacky

_______________________________________________
Cooker mailing list
Cooker <at> zarb.org
https://zarb.org/mailman/listinfo.cgi/cooker

Re: moondrake-gnu-linux-2013-beta-twelve-angry-penguins-i586-dvd

_______________________________________________
Cooker mailing list
Cooker <at> zarb.org
https://zarb.org/mailman/listinfo.cgi/cooker

inkscape needs perl-YAML-Syck that needs to be rebuild

perl-YAML-Syck needs rebuild, since continues requiring perlapi-5.12.3
And its needed to install inkscape.

--

-- 
Salutem,
Zé

opennebula cloud computing

Re: Message distribution: Authorization denied

> ---------- Videresendt e-post ----------
> From: "Per Øyvind Karlsen" <proyvind <at> gmail.com>
> To: cooker <at> mandrivalinux.org
> Cc:
> Date: Thu, 26 Jan 2012 18:03:27 +0100
> Subject: Re: [Cooker] MCC continues broken
> Den 13:14 26. januar 2012 skrev alexander barakin
> <abarakin <at> mandriva.org> følgende:
>> On Thu, Jan 26, 2012 at 11:44:28AM +0000, Zé wrote:
>>> Hi,
>>>
>>> Continues impossible to run mcc:
>>>
>>> ]# /usr/bin/perl: symbol lookup error:
>>> /usr/lib/perl5/vendor_perl/5.12.3/x86_64-linux-thread-multi/auto/Gtk2/WebKit/WebKit.so:
>>> undefined symbol: Perl_Gthr_key_ptr
>>>
>>> Theres severall perl modules needed to rebuild...
>>
>> last build rejected:
>> http://kenobi.mandriva.com/bs//package.php?key=20120125174506.peroyvind.kenobi.28316
> Last build made it through fine:
> http://kenobi.mandriva.com/bs//package.php?key=20120126123440.peroyvind.kenobi.3250
> :)
>
> --
> Regards,
> Per Øyvind
>

MCC continues broken

Hi,

Continues impossible to run mcc:

]# /usr/bin/perl: symbol lookup error:
/usr/lib/perl5/vendor_perl/5.12.3/x86_64-linux-thread-multi/auto/Gtk2/WebKit/WebKit.so:
undefined symbol: Perl_Gthr_key_ptr

Theres severall perl modules needed to rebuild...
--

-- 
Salutem,
Zé

Mmmm, how I can taste Unity??

Hi

This morning I found a lot of new candies in Contrib, one of these is
Unity, I want taste it.

I installed the Unity packages but I ave not any idea on how use it,
there is not new voices in KDM list of DM, the command unity return me
an error.

Can someone explain me how configure and try Unity??

Bye Bye, Moreno

How multilib is done needs changing

  Initial spec at

https://blueprints.launchpad.net/rosa/+spec/rosa-multilib

  I have it done for x86_64 and i586 (actually, i586 is not
affected, tested just to ensure something did not break as
an unexpected side effect or bug added to specs) and running
for some weeks for gcc, and some days for glibc.

  I had not submitted packages, initially expecting to submit to
main/testing, to avoid any possible issue during perl updates.
But since it is just a rebuild with split of 32 bit libraries,
the only issue would be choosing to revert, what could be done
with minimal problems, i.e. change back from:

lib64foo1-2-3-mdv2012.0.x86_64.rpm <- 64 bit libraries
libfoo1-2-3-mdv2012.0.x86_64.rpm   <- 32 bit libraries

to have only one library package.

  Example of what I have installed:

$ rpm -q lib64stdc++6 libstdc++6
lib64stdc++6-4.6.2-11-mdv2012.0.x86_64
libstdc++6-4.6.2-11-mdv2012.0.x86_64

  Special case is glibc, that is kept named as glibc, but
there is a new 32 bit only package, with some binaries:

$ rpm -q libc6
libc6-2.14.90-12.1-mdv2012.0.x86_64

(yes, the name could also be glibc32 or a variant).

  I understand that different people have different ideas of
how this should be done, should not be done, etc, and thus,
any comment is welcome.

  Personally, I do not like it much, but other than doing
nothing, this is the least intrusive way to implement it.
I would prefer to have it implemented as:
  libstdc++6-4.6.2-11-mdv2012.0.x86_64 <- 64 bit libraries
  libstdc++6-4.6.2-11-mdv2012.0.i686   <- 32 bit libraries
have rpmbuild automatically split the packages, generate
enough dependency metadata, and have both in the same
repository. That is, pretty much what fedora does. But that
would have implications with %mklibname and a lot of other
stuff, like urpmi, repository updates, etc.
  Also, to not be intrusive, -devel packages require both,
example:

$ rpm -q --requires lib64stdc++-devel
lib64stdc++6 = 4.6.2-11
libstdc++6 = 4.6.2-11
python(abi) = 2.7
devel(libgcc_s)
devel(libgcc_s(64bit))
devel(libm)
devel(libm(64bit))
rpmlib(PayloadIsXz) <= 5.2-1

$ rpm -q --requires lib64stdc++-static-devel
lib64stdc++-devel = 4.6.2-11
rpmlib(PayloadIsXz) <= 5.2-1

---%<---
  For a more complete example, this is what I have:

$ urpmq --media gcc --requires lib64stdc++6 2>/dev/null
ld-linux-x86-64.so.2()(64bit)
ld-linux-x86-64.so.2(GLIBC_2.3)(64bit)
libc.so.6()(64bit)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3.2)(64bit)
libc.so.6(GLIBC_2.3)(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libgcc_s.so.1(GCC_3.3)(64bit)
libgcc_s.so.1(GCC_4.2.0)(64bit)
libm.so.6()(64bit)
libm.so.6(GLIBC_2.2.5)(64bit)

  And this is what currently is in the distro:

$ urpmq --media main --requires lib64stdc++6 2>/dev/null
ld-linux-x86-64.so.2()(64bit)
ld-linux-x86-64.so.2(GLIBC_2.3)(64bit)
ld-linux.so.2
ld-linux.so.2(GLIBC_2.3)
libc.so.6
libc.so.6()(64bit)
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.1.3)
libc.so.6(GLIBC_2.14)(64bit)
libc.so.6(GLIBC_2.2)
libc.so.6(GLIBC_2.2.5)(64bit)
libc.so.6(GLIBC_2.3)
libc.so.6(GLIBC_2.3)(64bit)
libc.so.6(GLIBC_2.3.2)
libc.so.6(GLIBC_2.3.2)(64bit)
libgcc_s.so.1
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)
libgcc_s.so.1(GCC_3.0)(64bit)
libgcc_s.so.1(GCC_3.3)
libgcc_s.so.1(GCC_3.3)(64bit)
libgcc_s.so.1(GCC_4.2.0)
libgcc_s.so.1(GCC_4.2.0)(64bit)
libgcc_s.so.1(GLIBC_2.0)
libm.so.6
libm.so.6()(64bit)
libm.so.6(GLIBC_2.0)
libm.so.6(GLIBC_2.2.5)(64bit)
---%<---

  I will hold a bit more submit of gcc and glibc with the
32 bit library split in case someone has any issues. I also
plan to submit a newer grub, with /sbin/grub linked statically,
so that the only things, on a non devel system that would case
the need to install 32 bit libraries would be some packages
needing to rebuild with lib{,64}ffi5 and zlib.

Thanks,
Paulo

[ANNOUNCE] Kernel v3.2.1-2.1 (cooker only)

Hello,

A new release is available since yesterday night, that contains one and
only one fix which addresses the already famous exploit regarding
/proc/≤pid>/mem write permission checking.

--

-- 
		Franck

xmlrpc-c libraries