gmane.linux.mandrake.cooker.devel

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

Blackcrack — 2013-05-15T04:17:32

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

"where is?…"

Kate Lebedeff — 2013-04-16T22:00:01

http://openmandriva.org/2013/04/nudge-nudge-wink-wink-know-what-i-mean/

blog

Kate Lebedeff — 2013-04-16T21:58:48

http://openmandriva.org/2013/04/we-all-are-the-community/

Automated fix of some rpmlint errors

Denis Silakov — 2013-04-16T08:37:41

Hi all,

as you known, in our build systems some errors found by rpmlint are 
treated very seriously and lead to build fails.

However, many of such issues are quite easy to fix (e.g., 
'description-line-too-long'). I believe it makes sense to try to fix 
such issues automatically and not to waste maintainers time.

We have developed a prototype of 'automated fixers' for some rpmlint 
errors, and the first attempt to apply such fixes was performed 
recently. We have tried to fix the following errors:
* summary-ended-with-dot
* description-line-too-long
* empty-%post
* empty-%pre
* empty-%postun
* empty-%preun

More than hundred of packages were affected. Note that the fixes are 
performed by automated scripts (though their are committed under my 
login:)) and some errors can arise. Sorry if these fixes break something 
in your packages; feel free to report any issues to me to avoid 
incorrect fixes in future.

Also note that rebuild was triggered for all modified packages, and this 
rebuild will take a whilem so ABF will be occupied for the nearest hour 
or so. Sorry for inconvenience.

At the time being, this "mass fix" is a non-permanent action. But if we 
find this experiment successful, we can implement regular automated 
launch of fixers as a part of repo monitoring performed at FBA.

Builds pending

Crispin Boylan — 2013-04-16T08:18:15

Hi

Builds today seem to be stuck in pending - can someone take a look?

thanks
cris.

Is it time for some testing/reporting?

Ben Bullard — 2013-04-14T11:22:34

Several problems in Fresh install from Moondrake CD.

Had no internet or sound on first boot. Updating from Cooker repos fixed 
sound.

After some mucking around discovered I have to:

# systemctl stop shorewall.service

to use the internet. Needless to say I'd rather not do this.

Any idea how to fix?

Also firefox crashes immediatly:

$ firefox

(process:10148): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

(process:10156): GLib-CRITICAL **: g_slice_set_config: assertion 
`sys_page_size == 0' failed

(firefox:10148): GLib-GIO-ERROR **: No GSettings schemas are installed 
on the system
Trace/breakpoint trap (core dumped)

$ rpm -qa firefox
firefox-20.0.1-1-omv2013.0.x86_64

Also drakconf is crashing:

$ drakconf
$ "" is not executable [3D] at /usr/sbin/drakconf.real line 820.
"/usr/sbin/drakbackup" is not executable [Backups] at 
/usr/sbin/drakconf.real line 820.
"/usr/sbin/drakvirt" is not executable [Virtualization] at 
/usr/sbin/drakconf.real line 820.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at 
/usr/sbin/drakconf.real line 820.

(drakconf.real:11682): GLib-GIO-ERROR **: No GSettings schemas are 
installed on the system

# drakconf
[root< at >localhost ~]# Gtk-WARNING **: Unable to locate theme engine in 
module_path: "pixmap", at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", 
at /usr/sbin/drakconf.real line 98.
"" is not executable [3D] at /usr/sbin/drakconf.real line 820.
"/usr/sbin/drakbackup" is not executable [Backups] at 
/usr/sbin/drakconf.real line 820.
"/usr/sbin/drakvirt" is not executable [Virtualization] at 
/usr/sbin/drakconf.real line 820.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at 
/usr/sbin/drakconf.real line 820.

(drakconf.real:12577): GLib-GIO-ERROR **: No GSettings schemas are 
installed on the system

$ rpm -qa drakconf
drakconf-12.19.2-5-mdv2013.0.noarch

Any ideas how to fix? Are these related problems?

As always am willing to provide information, try whatever, file a bug 
report (where now?), even, gasp, learn something new if it gets results.

Compiz stable

Andrey Bondrov — 2013-04-13T02:26:54

In case anyone cares, I packaged working stable Compiz 0.8.x for ROSA 
2012.1 and Cooker. It was requested by users because 0.9.x is too buggy.

Feel free to install task-compiz-stable meta package (includes compiz 
itself, emerald, emerald themes etc) and test. You can control Compiz 
settings from Compiz Fusion Icon (Menu -> Utilities -> System).

It doesn't obsolete main compiz packages. Only conflicts with them.

Known issues:

1) KDE4's deKorator doesn't work well with Compiz when KDE4 Window 
Decorator is used for decorations. But other native KDE4 decoration 
engines seem to work fine. Emerald also works fine.

2) There is no MATE support. Fedora has patches for it but I don't use 
MATE and don't even know if it works in ROSA 2012.1 and Cooker. So in 
case anyone cares, feel free to use Fedora patches and rebuild Compiz 
with MATE support. I guess you'll need to patch compiz0.8 and 
compiz-fusion-plugins-main for that.

Tested only in ROSA 2012.1.

SRPMs list:

ccsm0.8-0.8.8-0.20130330.1.src.rpm
compiz0.8-0.8.9-0.20130330.2.src.rpm
compiz0.8-bcop-0.8.8-1.src.rpm
compiz-fusion-2012.1-1.src.rpm
compiz-fusion-plugins-extra-0.8.8-1.src.rpm
compiz-fusion-plugins-main-0.8.8-2.src.rpm
emerald-0.8.8-1.src.rpm
emerald-themes-0.6.0-0.20080210.4.src.rpm
fusion-icon-0.1-0.20100215.4.src.rpm
libcompizconfig0.8-0.8.9-0.20130330.1.src.rpm
python-compizconfig0.8-0.8.5-0.20130330.1.src.rpm
task-compiz-stable-2012.1-1.src.rpm

The new wiki

Anurag Bhandari — 2013-04-13T02:02:27

The old wiki at wiki.mandrivalinux.org has been moved to
http://wiki.openmandriva.org/. Please use this new one from now on as the
former will cease to exist in a couple months' time.

Summary of the common TC+ council meeting

Kate Lebedeff — 2013-04-12T09:19:31

Hello everybody

On April 10th, a common TC (Technical committee, for now = all active developers) + Council meeting took place. Logs will be posted. Here is the agenda and summary.

Best,

OMA secretary

__________________________________________

Agenda point:

Technical committee, council and all-active-developers (“cooker”) definitions and their relations. Suggestions to discuss.

This occasion is used to once more invite all active developers to enter Association and speak out (even they are not members) about any concerns they have. Association is to serve these concerns and solve issues, this is exactly why it was founded.

Result summary:

Here are some main definitions, which were agreed.

Definition for clarity:

Cooker community = OpenMandriva Association. (This means, there exists just one community, involving everybody. There is no separate “cooker” community).

This includes developers, translators, artwork people, marketing people, etc. Everyone that likes or contribute, including users, testers, those who do support - is part of this broader community (community is a term to refer to the active devs, inactive developers and users and sporadic contributors)

Any contributor/member/developer/manager could be free will contributor or paid by sponsors through the Association.

Everyone has the same chances and no one is going to be protected or treated in any special way.

Some notes on wording and extras:

Cooker is OMA's, but contribution is open

Cooker is also the active/rolling development of the OMA project.

It is also meant to be a base for other projects outside of OMA's scope (it's more inclusive of people who want to use the code base to build something else).

The project predates the association, and MDV saying they were giving the project to the community predates the association. The association was set up to help support the project. It could potentially support other projects too if it wanted.

It's possible to contribute in the community and have no involvement with the association.

TC (Technical committee).

The TC is a form of representation inside the cooker community.

Currently TC involves all active developers.

The next TC (whenever it comes, tomorrow or much later) is to be the most valuable and experienced members, or natural born leaders that take the front.

Who can be in TC?

The members of the "cooker community" who are also OMA member, (s)elected by "cooker community" (with some possible argumented recommendations from council). TC acts as the projects engine and communicator with all other involved parties, including council, and takes the technical responsibilities. Veto power (if needed in some extreme case not easily solvable) on decisions and selection of members is a shared responsibility of the council (representing the majority of the community that shares the same ideas) and the TC itself, that regulates the technical responsibilities.

(TC members need to be OMA's members. There are exceptions possible, given full mutual agreement (cooker including council).

(to be defined ASAP with cooker: exact roles, who should be in the TC (from the point of view of functions, next step asap: ideas for candidacies).

Project leader (s).

Members of the TC, responsible for overall route and development. Take decisions based on extensive consultations with cooker members. Take the RESPONSIBILITY for decisions in case of conflicts or attempts of hijack. If it can solve it by itself, or the decision taken is in conflict with other TC members, a joint decision need to be taken, reverting the power to the unity of the community.

Council:

The directive body of the Association, responsible for coordinating overall work and resources. Important to remember: council consists of members of the association, and is designed to represent everybody in the Association, and is elected by the members.

Council does not have own opinion as such, these people are elected to represent members (this means, that when council speaks, it is not just a blunt group of people out of nowhere: they were elected to represent community. They do not produce their own opinions, they represent).

2. Association as an entity: why founded, for whom and it’s functions

Membership in OMA is free and open to anybody, no obligations or restrictions. OMA's goal is to make the project's distro successful (by providing resources, infrastructure, marketing, attracting sponsors, etc.).

Normally OMA members should include both all cooker community + other non technical contributors.

We use this chance to say once again: contributors are most welcome to join OMA, the association was founded to serve your needs. Become a member and influence decisions, elect your representatives, participate and form the common work with your input and opinion.

If anybody was bypassed with invitation so far, we apologize, this was not the intention. Association is young, it all just starts. Doors are wide open.

The association is representing a lot of people that share the same vision for the future of the, soon to be, best linux distro of the world

Normally all cooker community should be OMA members if they share the goal to make the distro successful.

3. Distro name issue.

The temporary solution is go with a distro with no name for

Now. We still don't have the appropriate technical resources (support on ABF) in place to a multi-name/multi-spin distro right now, and we never discussed this topic thoroughly so can we agree on having no-name now, not to go into that? The issue caused enough trouble already.

Reason is simple: if we were to decide now, how would we do that? Vote? By who?

Just decision of several people? Who?

We can make support on ABF for shared packages with different spins to support generating multiple distro, changing even the name, and we probably want to include some discussion on how our merit ( based on xxxx TM) should be approached.

So whatever spin we want, we need support on ABF first and then we can even let the RPM patched to be "nothing" , and the spins can tag the names appropriately depending on the platform used to compile

So, no name for now, until we can find a proper way to do it.

We could call the distro cooker, or some other fancy codename.

And each spin can name the ISO and artwork the way they want.

There is a suggestion to have Innominata (Latin for noname) as temporary name. Most people in a meeting said they are in favor of it, however, a separate discussion will be started by Gmoro in cooker ML for that.

Update: Joao Patricio drafts a suggestion on rules, how we choose the name. Draft to be discussed all together (details of procedure to come soon). The target is to have the rules and fully common community decision on the name before the release is out. For the moment “Innominata” takes the place as a placeholder.

Attention! If the topic is important for you, please follow it in general ML and the blog, in order to supply your opinion on time.

4. Recent conflict, summary from Association and suggestion for discussion/closing the topic.

Postponed to next week. Gmoro will post an agenda and confirm the time.

reminder: cooker meeting

Per Øyvind Karlsen — 2013-04-11T14:27:59

IRC meeting about to begin in 30 min.

--
Regards,
Per Øyvind

Broken packages to fix for beta release

Per Øyvind Karlsen — 2013-04-09T17:16:08

Heyo!

I'm in the process of putting on final touches of first beta now, and
related to I thought that I'd share list of package errors reported by
smart while generating iso:

Unsatisfied dependency: 2mandvd-1.8.2-1-rosa2012.1< at >x86_64 requires
libavutil.so.51()(64bit)

Unsatisfied dependency: 2mandvd-1.8.2-1-rosa2012.1< at >x86_64 requires
libavutil.so.51(LIBAVUTIL_51)(64bit)

Unsatisfied dependency:
apache-mod_perl-1:2.0.7-2.svn1458708.1-mdv2013.0< at >x86_64 requires perl =
2:5.16.2

Unsatisfied dependency: atunes-1.8.2-2mdv2009.0< at >noarch requires
jna-examples

Unsatisfied dependency: c-icap-modules-4:0.2.3-1-rosa2012.1< at >x86_64 requires
libperl.so()(64bit)

Unsatisfied dependency: dkms-dahdi-2.6.1-2-rosa2012.1< at >x86_64 requires
/bin/true

Unsatisfied dependency: dvdstyler-1:2.3-1-rosa2012.1< at >x86_64 requires
libavutil.so.51()(64bit)

Unsatisfied dependency: dvdstyler-1:2.3-1-rosa2012.1< at >x86_64 requires
libavutil.so.51(LIBAVUTIL_51)(64bit)

Unsatisfied dependency:
eclipse-platform-1:3.7.0-1.3-mdv2011.0< at >x86_64requires eclipse-rcp =
3.7.0-1.3

Unsatisfied dependency: flphoto-1.3.1-13-mdv2012.0< at >x86_64 requires
libgphoto2_port.so.0()(64bit)

Unsatisfied dependency: flphoto-1.3.1-13-mdv2012.0< at >x86_64 requires
lib64gphoto2 >= 2.1.1

Unsatisfied dependency: flphoto-1.3.1-13-mdv2012.0< at >x86_64 requires
libgphoto2.so.2()(64bit)

Unsatisfied dependency: gnome-libs-1.4.2-27-mdv2013.0< at >x86_64 requires
libgtk-1.2.so.0()(64bit)

Unsatisfied dependency: gtkam-0.1.17-1-mdv2011.0< at >x86_64 requires
libgphoto2_port.so.0()(64bit)

Unsatisfied dependency: gtkam-0.1.17-1-mdv2011.0< at >x86_64 requires
libgphoto2.so.2()(64bit)

Unsatisfied dependency:
gtkam-gimp-plugin-0.1.17-1-mdv2011.0< at >x86_64requires
libgphoto2_port.so.0()(64bit)

Unsatisfied dependency:
gtkam-gimp-plugin-0.1.17-1-mdv2011.0< at >x86_64requires
libgphoto2.so.2()(64bit)

Unsatisfied dependency: gtktalog-1.0.4-11mdv2011.0< at >x86_64 requires
libgtk-1.2.so.0()(64bit)

Unsatisfied dependency: gtktalog-1.0.4-11mdv2011.0< at >x86_64 requires
libgdk-1.2.so.0()(64bit)

Unsatisfied dependency: hamcrest-1.1-10.7-mdv2012.0< at >noarch requires
java-1.6.0

Unsatisfied dependency: horde-browser-0.0.2-3mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: horde-datatree-0.0.3-3mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-form-0.0.2-7mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: horde-form-0.0.2-7mdv2011.0< at >noarch requires
pear(Services/Weather.php)

Unsatisfied dependency: horde-form-0.0.2-7mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-group-0.1.0-4mdv2011.0< at >noarch requires
pear(Horde/Auth.php)

Unsatisfied dependency: horde-group-0.1.0-4mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-history-0.0.2-3mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-icalendar-0.1.0-4mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: horde-image-0.0.2-3mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: horde-ingo-1.2.4-1mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-kolab-0.0.6-3mdv2011.0< at >noarch requires
pear(Horde.php)

Unsatisfied dependency: horde-mime-0.0.2-60mdv2011.0< at >noarch requires
pear(Horde/Text.php)

Unsatisfied dependency: horde-passwd-3.1.3-2mdv2011.0< at >noarch requires
pear(Crypt/CHAP.php)

Unsatisfied dependency: horde-passwd-3.1.3-2mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-prefs-0.0.3-3mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-serialize-0.0.2-3mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-text-filter-0.0.2-3mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: horde-text-filter-0.0.2-3mdv2011.0< at >noarch requires
pear(Horde.php)

Unsatisfied dependency: horde-token-0.0.4-2mdv2011.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency: horde-token-0.0.4-2mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: horde-util-0.1.0-3mdv2011.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: hsfmodem-7.80.02.05-4mdv2010.1< at >x86_64 requires
kmod(hsfengine)

Unsatisfied dependency: junit-4.10-2-mdv2013.0< at >noarch requires java-1.6.0


Unsatisfied dependency: kile-2:2.1.2-2-rosa2012.1< at >x86_64 requires
texlive-latex.bin

Unsatisfied dependency: kino-2:1.3.4-9-mdv2012.0< at >x86_64 requires
libavutil.so.51()(64bit)

Unsatisfied dependency: kino-2:1.3.4-9-mdv2012.0< at >x86_64 requires
libavutil.so.51(LIBAVUTIL_51)(64bit)

Unsatisfied dependency:
kipi-plugins-expoblending-2:3.0.0-1-mdv2013.0< at >x86_64requires hugin

Unsatisfied dependency:
kipi-plugins-panorama-2:3.0.0-1-mdv2013.0< at >x86_64requires hugin

Unsatisfied dependency: lib64gail-gnome-1.20.4-3-mdv2011.0< at >x86_64 requires
libpanel-applet-2.so.0()(64bit)

Unsatisfied dependency: lib64gdk-pixbuf2-0.22.0-17mdv2011.0< at >x86_64 requires
libgtk-1.2.so.0()(64bit)

Unsatisfied dependency: lib64gdk-pixbuf2-0.22.0-17mdv2011.0< at >x86_64 requires
libgdk-1.2.so.0()(64bit)

Unsatisfied dependency: lib64gdkimlib1-1.9.15-15-mdv2013.0< at >x86_64 requires
libgdk-1.2.so.0()(64bit)

Unsatisfied dependency: lib64gexiv2_0-0.3.92-1-mdv2012.0< at >x86_64 requires
libexiv2.so.11()(64bit)

Unsatisfied dependency: lib64gnome32-1.4.2-27-mdv2013.0< at >x86_64 requires
libgtk-1.2.so.0()(64bit)

Unsatisfied dependency: lib64gnome32-1.4.2-27-mdv2013.0< at >x86_64 requires
libgdk-1.2.so.0()(64bit)

Unsatisfied dependency: lib64kmf0-0.8.1-1-rosa2012.1< at >x86_64 requires
libavutil.so.51()(64bit)

Unsatisfied dependency: lib64kmf0-0.8.1-1-rosa2012.1< at >x86_64 requires
libavutil.so.51(LIBAVUTIL_51)(64bit)

Unsatisfied dependency: lib64soup-2.2_8-2.2.105-7-mdv2012.0< at >x86_64 requires
libgnutls.so.26()(64bit)

Unsatisfied dependency: lib64wxsvg0-1.1.9-1-rosa2012.1< at >x86_64 requires
libavutil.so.51()(64bit)

Unsatisfied dependency: lib64wxsvg0-1.1.9-1-rosa2012.1< at >x86_64 requires
libavutil.so.51(LIBAVUTIL_51)(64bit)

Unsatisfied dependency:
lib64xulrunner2.0.1-2.0.1-2-mdv2011.0< at >x86_64requires
libvpx.so.0()(64bit)

Unsatisfied dependency:
libopensync-plugin-evolution2-1:0.22-6mdv2011.0< at >x86_64 requires
libedataserver-1.2.so.14()(64bit)

Unsatisfied dependency:
libopensync-plugin-evolution2-1:0.22-6mdv2011.0< at >x86_64 requires
libecal-1.2.so.8()(64bit)

Unsatisfied dependency:
libopensync-plugin-evolution2-1:0.22-6mdv2011.0< at >x86_64 requires
libebook-1.2.so.10()(64bit)

Unsatisfied dependency:
libreoffice-pdfimport-1:3.5.4-4-mdv2012.0< at >x86_64requires
libpoppler.so.25()(64bit)

Unsatisfied dependency:
libreoffice-pdfimport-1:3.5.4-4-mdv2012.0< at >x86_64requires
libreoffice-common = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-pdfimport-1:3.5.4-4-mdv2012.0< at >x86_64requires
libreoffice-core = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-pdfimport-1:3.5.4-4-mdv2012.0< at >x86_64requires
libreoffice-draw = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-presentation-minimizer-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-impress = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-presentation-minimizer-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-core = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-presentation-minimizer-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-common = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-presenter-screen-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-common = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-presenter-screen-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-core = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-presenter-screen-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-impress = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-wiki-publisher-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-core = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-wiki-publisher-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-common = 1:3.5.4-4:2012.0

Unsatisfied dependency:
libreoffice-wiki-publisher-1:3.5.4-4-mdv2012.0< at >x86_64 requires
libreoffice-writer = 1:3.5.4-4:2012.0

Unsatisfied dependency: lxdm-0.4.1-1-mdv2013.0< at >x86_64 requires
libck-connector.so.0()(64bit)

Unsatisfied dependency:
nautilus-filesharing-0.6-6-mdv2013.0< at >x86_64requires mdk-menu-messages

Unsatisfied dependency:
nautilus-filesharing-0.6-6-mdv2013.0< at >x86_64requires drakxtools-newt

Unsatisfied dependency: openldap-servers-2.4.33-4-mdv2013.0< at >x86_64 requires
db-utils >= 5.2.0

Unsatisfied dependency: perl-Gimp-1:2.2-0.pre1.11-mdv2012.0< at >x86_64 requires
perl(abi) = 5.14.2

Unsatisfied dependency: perl-Gimp-1:2.2-0.pre1.11-mdv2012.0< at >x86_64 requires
libperl.so()(64bit)

Unsatisfied dependency: perl-Goo-Canvas-0.60.0-2-mdv2012.0< at >x86_64 requires
perl(abi) = 5.14.2

Unsatisfied dependency: perl-Goo-Canvas-0.60.0-2-mdv2012.0< at >x86_64 requires
libperl.so()(64bit)

Unsatisfied dependency:
perl-Gtk2-GladeXML-1.007-4-rosa2012.1< at >x86_64requires perl(abi) =
5.14.2

Unsatisfied dependency:
perl-Gtk2-GladeXML-1.007-4-rosa2012.1< at >x86_64requires
libperl.so()(64bit)

Unsatisfied dependency:
perl-Gtk2-ImageView-0.50.0-2-mdv2012.0< at >x86_64requires perl(abi) =
5.14.2

Unsatisfied dependency:
perl-Gtk2-ImageView-0.50.0-2-mdv2012.0< at >x86_64requires
libperl.so()(64bit)

Unsatisfied dependency: perl-Linux-DVB-1.10.0-3-rosa2012.1< at >x86_64 requires
perl(abi) = 5.14.2

Unsatisfied dependency: perl-Linux-DVB-1.10.0-3-rosa2012.1< at >x86_64 requires
libperl.so()(64bit)

Unsatisfied dependency:
perl-Proc-ProcessTable-0.450.0-4-rosa2012.1< at >x86_64requires perl(abi) =
5.14.2

Unsatisfied dependency:
perl-Proc-ProcessTable-0.450.0-4-rosa2012.1< at >x86_64requires
libperl.so()(64bit)

Unsatisfied dependency: perl-Sane-0.50.0-1-rosa2012.1< at >x86_64 requires
perl(abi) = 5.14.2

Unsatisfied dependency: perl-Sane-0.50.0-1-rosa2012.1< at >x86_64 requires
libperl.so()(64bit)

Unsatisfied dependency: perl-Video-ivtv-0.13-10-rosa2012.1< at >x86_64 requires
perl(abi) = 5.14.2

Unsatisfied dependency: perl-Video-ivtv-0.13-10-rosa2012.1< at >x86_64 requires
libperl.so()(64bit)

Unsatisfied dependency: php-pear-Date-1.5.0a2-2-mdv2012.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency:
php-pear-HTTP_Request-1.4.4-7-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency: php-pear-Log-1.12.7-3-mdv2012.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency:
php-pear-MDB2-2:2.5.0-0.0.b3.3-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency:
php-pear-MDB2_Driver_sqlite-1:1.5.0-0.0.b3.2-mdv2012.0< at >noarch requires
php-sqlite

Unsatisfied dependency:
php-pear-Mail-1.2.0-0.b1.9-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency:
php-pear-Mail_mimeDecode-1.5.5-4-mdv2012.0< at >noarchrequires
pear(PEAR.php)

Unsatisfied dependency:
php-pear-Net_FTP-1.4.0a2-2-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency: php-pear-Net_SMTP-1.6.1-3-mdv2012.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency:
php-pear-Net_Sieve-1.3.2-2-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency:
php-pear-Net_Socket-1.0.10-4-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency:
php-pear-Numbers_Words-0.16.3-3-mdv2012.0< at >noarchrequires
pear(PEAR.php)

Unsatisfied dependency: php-pear-SOAP-0.12.0-7-mdv2012.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency:
php-pear-Text_Figlet-1.0.2-3-mdv2012.0< at >noarchrequires
pear(PEAR/Config.php)

Unsatisfied dependency:
php-pear-Text_Figlet-1.0.2-3-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency: php-pear-VFS-0.3.0-2-mdv2012.0< at >noarch requires
pear(PEAR.php)

Unsatisfied dependency: php-pear-VFS-0.3.0-2-mdv2012.0< at >noarch requires
pear(DB.php)

Unsatisfied dependency:
php-pear-XML_Parser-1.3.4-3-mdv2012.0< at >noarchrequires pear(PEAR.php)

Unsatisfied dependency:
php-pear-XML_Serializer-0.20.2-2-mdv2012.0< at >noarchrequires
pear(XML/Util.php)

Unsatisfied dependency:
php-pear-XML_Serializer-0.20.2-2-mdv2012.0< at >noarchrequires
pear(PEAR.php)

Unsatisfied dependency:
php-pear-XML_sql2xml-0.3.4-7-mdv2012.0< at >noarchrequires pear(DB.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(url_generating.lib.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(libraries/config/user_preferences.forms.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(libraries/Advisor.class.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(Export_Relation_Schema.class.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(db_export.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(libraries/db_table_exists.lib.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(libraries/sysinfo.lib.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(libraries/relation.lib.php)

Unsatisfied dependency: phpmyadmin-3.5.2-1-mdv2012.0< at >noarch requires
pear(pmd_save_pos.php)

Unsatisfied dependency: rails-3.2.9-1-rosa2012.1< at >noarch requires
rubygem(railties) = 3.2.9

Unsatisfied dependency: rails-3.2.9-1-rosa2012.1< at >noarch requires
rubygem(activeresource) = 3.2.9

Unsatisfied dependency: rails-3.2.9-1-rosa2012.1< at >noarch requires
rubygem(actionpack) = 3.2.9

Unsatisfied dependency: rails-3.2.9-1-rosa2012.1< at >noarch requires
rubygem(activerecord) = 3.2.9

Unsatisfied dependency: rails-3.2.9-1-rosa2012.1< at >noarch requires
rubygem(actionmailer) = 3.2.9

Unsatisfied dependency: rails-3.2.9-1-rosa2012.1< at >noarch requires
rubygem(activesupport) = 3.2.9

Unsatisfied dependency: samba-doc-1:3.6.9-2-mdv2012.0< at >noarch requires
samba-common = 1:3.6.9

Unsatisfied dependency: synce-hal-0.15-2mdv2011.0< at >x86_64 requires
libhal.so.1()(64bit)

Unsatisfied dependency: synce-trayicon-0.15-4-mdv2011.0< at >x86_64 requires
libhal.so.1()(64bit)

Unsatisfied dependency: texinfo-5.1-1-mdv2013.0< at >x86_64 requires
texlive-collection-texinfo

Unsatisfied dependency: thunderbird-ar-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-be-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-bg-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-ca-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-cs-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-da-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-de-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-el-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-et-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-eu-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-fi-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-fr-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-fy-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-ga-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-gd-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-gl-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-he-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-hu-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-id-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-is-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-it-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-ja-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-ko-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-lt-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-nb_NO-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-nl-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-nn_NO-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-pl-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-ro-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-ru-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-si-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-sk-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-sl-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-sq-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-tr-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-uk-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency: thunderbird-vi-14.0-1-mdv2012.0< at >noarch requires
thunderbird = 14.0

Unsatisfied dependency:
x11-driver-video-nvidia-long-lived-310.32-3-mdv2013.0< at >x86_64 requires
kmod(nvidia-long-lived) = 310.32

Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires
libXext.so.6

Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires libX11.so.6


Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires
libXdamage.so.1

Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires libdrm.so.2


Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires
libXfixes.so.3

Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires libva.so.0


Unsatisfied dependency:
x11-driver-video-psb-binary-blobs-0-4-mdv2012.0< at >x86_64 requires
libexpat.so.1



So if anyone lacks anything to do, then look no further.. ;)

--
Regards,
Per Øyvind

Technical committee (cooker devs) meeting with the council

Guilherme Moro — 2013-04-09T10:02:17

Hello all,

We are planning for tomorrow (Wednesday, April 10th at 4PM UTC) a IRC
meeting (at freenode #mandriva-cooker) to clear some things with the
community, so if all the interested persons can please join us tomorrow, or
at least send some discussion points, we will be glad.

Proposed agenda:


1.    Technical committee, council and all-active-developers (“cooker”)
definitions and their relations. Suggestions to discuss.

2.    Association as an entity: why founded, for whom and it’s functions

3.    Name of the Association and distro: offered temporary solution.

4.    Recent conflict, summary from Association and suggestion for
discussion/closing the topic.


Details of agenda (some definitions as we understand now):

“Cooker” is the unity of all developers, active for the distro. Distro,
around which community united itself and founded Association to handle
organizational issues and support in various forms. Cooker is kind of
self-organized anarchy,  but by it’s own good will (s)elects few members
(could be people invited form old members, not active now, or even externs,
up to the team), who become the “engines” of the process. Any process needs
organization inside, leaders of certain routes, and project
leader(s)/manager(s).

Any developer or manager could be free will contributor or paid by sponsors
through the Association.

“Technical committee”. The members, (s)elected by cooker (with some
possible argumented recommendations from council). TC acts as the projects
engine and communicator with all other involved parties, including Council.

(to be defined ASAP with cooker: exact roles, who should be in the TC (from
the point of view of functions, next step asap: ideas for candidacies).

 Project leader (s). Members of the TC, responsible for overall route and
development. Take decisions based on extensive consultations with cooker
members. Take the RESPONSIBILITY for decisions in case of conflicts or
attempts of hijack (reverting the power to cooker as unity).

“Council”. The governing body of the Association, responsible for
coordinating overall work and resources. Has a veto right on TC decisions
in extreme cases (needs to be better defined). Uses this veto right only
after using all possible options for consensus. Important to remember:
council consists of same members (at the moment half of council is
developers), and is designed to represent everybody in the Association, and
are elected by the members. Council does not have “own opinion” as such –
these people are elected to represent members.

This occasion is used to once more invite all active developers to enter
Association and speak out (even they are not members) about any concerns
they have. Association is to serve these concerns and solve issues, this is
exactly why it was founded.


Name issue

Name issue. There is a lot of controversy about it, and we have our doubts
- same as you. But it is ridiculous to be going around about the name, when
we

a) just founded organization (please, let's not discuss the past. Let's be
constructive and stick to the facts. It exists). You do not rename 3 months
after founding: you make yourself ridiculous.

b) there was no proper discussion of all arguments "for" and "against".
 And we can not know, without having proper analysis, what is best. We
should attend to this important issue properly.

We could make the change at any point in time. We just need to be sure, all
of us, that we do the right thing and change for good.

c) properly and in time. And when we have time. For some people issue is
indeed hot, so in the end of the day it will require attention from
everybody.

The first target is to do it all to have best possible conditions for
development from all POVs. We are attending to that all the time, and ask
you to please help where you can, to report issues or give recommendations
about improvements. Let's attend to this important issue about
"deco"/Artwork, once we have all basics (at least basics) fixed for really
important and needed things, ie development.

We still don't have the appropriate technical resources (support on ABF) in
place to a multi-name/multi-spin distro right now, and we never discussed
this topic thoroughly so can we agree on having no-name now, not to go into
that? The issue caused enough trouble already.

Reason is simple: if we were to decide now, how would we do that? Vote? By
who?

Just decision of several people? Who?

This needs to be done very right, to avoid ANY questions or concerns from
members in the future. In current situation it is hardly possible.

And remembering that there's no such vision of council as a separated
entity of evil, they are ruled by a statute and we developers got to choose
who is going to be in there in the next General Assembly.

Regards,

Guilherme Moro

armv7l qemu boot image

Alexander Khryukin — 2013-04-05T12:07:40

Hi everyone.
I prepared very lite armv7l image with kernel 3.8.2 and our armv7l
OpenMandriva chroot
from http://lindev.ch/arm-root/root/home/fdkit/repo/main/


Little F.A.Q for future releases.

How to create own armv7 bootable image
* Create chroot from armv7l repo
for example it can be done with abf mock-urpm tool


* create the hard disk file
fallocate -l 2GiB openmandriva-arm.ext3
mkfs.ext3 openmandriva-arm.ext3

* mount the hard disk file
mkdir mnt
sudo mount -o loop openmandriva-arm.ext3 mnt

* copy cache.tar.gz to your local machine, unpack it
in staging dir

sudo tar -xf cache.tar.gz -C  mnt/

* compile own vexpress-a9 kernel

# check out the sources
git clone -depth=1 git://
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
# create a .config based on the versatile express default configuration
make ARCH=arm vexpress_defconfig
make menuconfig
* enable DEVTMPFS=y
# compile the kernel
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j5 zImage
copy zImage file to your /tmp dir

Let's go to boot

qemu-system-arm -M vexpress-a9 -kernel zImage -drive
file=openmandriva-arm.ext3,if=sd,cache=writeback -append "rw console=tty1
root=/dev/mmcblk0"

And after 5-7 seconds of booting you are into Openmandriva 2013.0 armv7l
edition.



In short time i present download links to disk image and kernel.
Wait a bit

Per Øyvind vs. the council

Bernhard Rosenkränzer — 2013-04-05T09:39:42

Hi,
I think we've spent way too much time on this already, so this is going to be 
my last comment on the issue:

While it may not appear like this at first, I believe that the current 
situation is actually the best outcome possible.

There are large disagreements between Per Øyvind and the council on the 
project's governance, name, branding, both internal and external 
communication, etc.
There's a lot of (though not 100%) overlap on technical issues.

So the best way is actually to create 2 projects that are independent of each 
other (let's refer to them as Moondrake and OpenMandriva for now, though both 
names can still change - the final decision is up to the projects) -- the 
projects can share a lot of code and work together where there is agreement, 
and agree to disagree (and use different packages) where there is disagreement 
- and both projects can come to their final decisions in different ways.

There is even agreement in the council that the association's infrastructure 
can be used to build and host Moondrake in addition to the association's 
release.

The action of excluding Per Øyvind from the OpenMandriva association may seem 
like a "punishment", even a harsh punishment, by some, but that's not what it 
is and not what it is intended to be: This is as much about getting the 
council off Per Øyvind's back as it is about getting Per Øyvind off the 
council's back.

Per Øyvind needs to be able to do what he does best - developing what is 
consistent with his ideas - without having the council or anyone telling him 
that something cannot be done in that particular way.
The association on the other hand needs to be able to build something that 
matches its ideas even if some of them are considered bad or outright stupid 
by some, and it can't tolerate effectively becoming the joke it has been 
accused of being by making a decision just to see that the decision was 
overruled by those implementing it.

Most developers are somewhere between the 2 positions and I fully expect 
developers to contribute to both projects (I, for one, will help out both 
projects if I'm wanted there).

ttyl
bero

Cooker meeting scheduled for Thursday, April 11 & agenda

Per Øyvind Karlsen — 2013-04-06T14:45:29

Hi!

I've added a preliminary agenda for next cooker meeting scheduled for
upcoming Thursday < at > 1500 UTC:
http://wiki.mandriva.com/en/Development/Meetings/2013/Week15

Feel free to contribute to it. :)

--
Regards,
Per Øyvid

Resignation

Per Øyvind Karlsen — 2013-04-06T06:32:34

In light of recent events with the association's council violating the
cooker project's sovereignty (recently reaffirmed during last cooker/TC
meeting) by interferring with the project outside of it's established
channels and it's failure at answering objections of, I hereby resign from
this council in protest.

A cooker meeting is scheduled for next Thursday at 15:00 UTC where the
relationship between the project and association will be (re)discussed.

--
Regards,
Per Øyvind

Unifying Name

Colin Close — 2013-04-05T20:04:09

I am soon to be 62 years old and for the last 12 years I have been gradually 
learning the skills required to help maintain rpm packages. I thought that 
finally when Mandriva went truly open I would have the opportunity to make a 
contribution however small. In the light of the current disarray I see this 
hope fading. I have but one suggestion; that all parties join in producing:-
"THE Distribution" 
A name which embodies not only major technical merit but also implys an 
elegance of operation, style and integration that only you all can provide.
Most people will want to be a part of that which is new and upcoming. A 
distribution that encourages contribution however small, one that makes room 
for those who are young to join and learn the ways of true cooperation so "The 
Distribution" becomes like a living thing that continues to grow and flourish.
The truth of all this is that if you aspire to a distribution which is greater 
than your collective vision it will bind you with the need to find a means to 
achieve the dream.
Fine words you might say but set in the light of the current troubles their 
relevance is inescapable.

Best,
Colin Close

Potentially destructive behavior

Colin Close — 2013-04-05T08:42:26

As a long term user and supporter of Mandriva I am saddened by the current 
conflict involving the council and a major developer. This "high-handed" 
approach to the resolution of what is in essence a minor disagreement could 
lead to resentment and lack of cooperation in later years and threatens the 
continuation of the distro after the enormous effort that have been made to 
save it.
What saddens me even more is that the Cooker list (The major source of 
information on Mandriva development and progress) is not being used as the 
forum for the discussion of these important matters. The process of naming the 
distro is something that should be as public as possible and it is up to the 
various camps to argue their choices publicly so an informed choice can be 
made by those who do not hold such strong opinions.
I am very much against the use of IRC for this purpose as it encourages 
disordered and largly unreferenceable conversations. It also limits the 
attendence to those who happen to be around at the time. 
The advantages of a mailing list are obvious by comparison (properly minuted 
and structured exchanges).
The problem with situations such as these is that being "right" does not bring 
about a positive result what is needed is acceptance on both sides that 
perhaps this was not the best way to go about things and to seek a more 
positive solution.
Best,

Colin Close
Long term Mandiva user

Package tracker for Cooker

Andrey Ponomarenko — 2013-04-05T08:29:27

Hello,

The package tracker for Cooker is opened: 
http://upstream-tracker.org/updates/mdv/cooker/

Enjoy!

Odp.: Cooker on fba.rosalinux.ru

Tomasz Paweł Gajc — 2013-04-01T09:05:10

Finally :)

Thanks Denis.
------Oryginalna wiadomość------
Od: Denis Silakov
Nadawca: cooker-request< at >mandrivalinux.org
Do: cooker< at >mandrivalinux.org
Odpowiedz adresatowi: cooker< at >mandrivalinux.org
Temat: [Cooker] Cooker on fba.rosalinux.ru
Wysłano: 1 kwi 2013 10:03

Hi all,

As some of you know, we (ROSA) have a site with different reports 
concerning repo consistency (rpmlint, missing dependencies, etc.) - 
http://fba.rosalinux.ru/.

And we have just added reports for the cooker repos there. Feel free to 
try, provide feedback, report issues and ask if something is unclear.

Reports are updated daily.

Cooker on fba.rosalinux.ru

Denis Silakov — 2013-04-01T08:03:53

Hi all,

As some of you know, we (ROSA) have a site with different reports 
concerning repo consistency (rpmlint, missing dependencies, etc.) - 
http://fba.rosalinux.ru/.

And we have just added reports for the cooker repos there. Feel free to 
try, provide feedback, report issues and ask if something is unclear.

Reports are updated daily.