[OM Cooker] Migration oma 2014.2 -> OMA Lx3

Blackcrack blackcrack at blackysgate.de
Sun May 8 04:16:44 EDT 2016


--force-key (for updating the key signature or something, if you read 
the man, do you see it ..)

and i go along with you Luca, so +1 as a snapshot from the 
actually/updatet 2014 ..
all other is play around with dirty stuff like beta and not stable 
stuff.. .. something
like grub beta it's totally unreality and unnecessary, we need a stable 
stuff to trade as OMLx for our Distro..
all other it is a try to make negative and not a right thinking about.. 
and childish to think and to say,
"why, we have the the newest stuff and i have all done for.., what it is 
wrong on it ??? "
Wrong it is, to mean .. no, i want nobody attacking , particular not 
they are who programming us stuff..
I only want to say what strikes me, and this is just this what i say, i 
don't need a unstable with
many bugs betasoftware where it's the beta from the producer and 
unstable and makes
all bugish  in all corner in the distribution, we need a well working 
software and not the
greenest ricecorn of the ricefield , where it is not able to eat .
(and i want not hear, but why, we have the freshest corn of the rice, 
because this is NOT eat able !
if i allow me to give this comparison )

-----quote-TPG------------------------------------------
urpmi has one big design flaw, install/update/remove processes are run 
in user session.
This means if anything will kill session install/update/remove of rpm 
will be cancelled.
Finally this means user will get a black screen it VT with prompt.
---------------------------------------

this is wrong imho.
user session as su and su it is the administrator privileges
if this not work like it should work it's something wrong.
Because the Standard it is to work as root and not directly as user
and it is adjustable, or should be in drakconf (under security-config),
works this not, it is bug..ed or wrong reprogrammed. and should be have 
an work
again for correcting to configuring in drakconf..
(or should it be buged???????? (only a question.. in serious !) )

The NM integration it is a really good work, well done ! but why i
don't see a link in the drakconf from the netmanager too
(as independent Networkconfiguration by side of the netcenter as
"Network Manager" for configuring the networkstack from Drakconf ) ,
as further possibility to configuration the network stack in
drakconf .. i don't use the f... walled of KDE for the network-stack
and i want not depending from one WindowManager like KDE/Plasma
the Network Manager should able to use independent from any WM
to be able configurable in any wm, in my opinion for the Linux System, 
it meant Kernel and bash..
(and in the bash it's now possible and works really nice :) , like it! ) 
So, why not move at icon
from the NetworkManager in Drakconf, this is the original and normally 
Standart configuration
Center of Mandrake, Mandriva! So why not in OpenMandriva, want this 
anyone not /want this anyone not support ?

Also the Name of the Computer, should be also again configurable in 
Network & Internet again, because at moment it is not.
So, imho, we should have a Beta with well working Programs and a good 
together working packets
in one distribution .. and not alpha/beta rpm-packets where make at all 
more unstable like it should be.. (for a beta, please(common)...)
i want have a well running and stable system .. where i can also 
installing in a Server..
and can support therefore also the community with my making money as 
Provider
(i  guess i can it not say more clean if i see the server-try to have- 
thing (by the way, we want make a Server-Distribution ????) )
So, w.t.f. (sorry for the hard word, but this is my feel at moment)

do you thinking by take betasoftware as fresh rpm's for a should be 
stable Distro
although we actually what stable to have/need for a to do stable 
Distribution ?

i can not often enough to say, Mandrake, Mandriva
should has a RPM-Online-Installer and a MCC (so drakconf)
and should be independent from the Window manager as configuration.
only as a small statement from me and what strikes me .

and as last point, i stay fully behind Luca and MIB

(with a small other .. the well running 2014 should not brunch,
should be only hold up to date with stable sources in rpm and if it's
prove as stable should it move in the uptate/stable brunch for have
at all every a running update and every further new versions,
stable packages and well running system and by the update+ the updatet 
rpm's to be belong on the time ;)
So, snapshot from a stable-brunch, more extra small bugfixing and kick 
it out as new Version-snapshoot where
it is clean-est to install and well working on CD/install-iso as Version 
XX.XX of OMDV with online installer
and a small snapshot from the snapshot system on CD for liveCD .. (also 
for distributing and with 4 Gig it's many possible)
and the
mini-distribution with basesystem+recovery-possibility's for grub2 and 
linuxsystem(bashtools) ,wayland+calamares only with rpm-online-installer 
.. only as suggestion )

so, like Rugyada told before 3/4 years, the 3  possible repos
gooseskin(or cribleskin,indescribable or something), unstable(cooker) 
and stable.

this is my thinking/opinion if i read the last Mails in this mailing list.
and i guess, i be not the only one  where read this and makes his own 
thinking there about.

so, +1 Luca

best regards
Blacky

Am 07.05.2016 um 23:39 schrieb luca pedrielli:
>
> In my opinion is time to starting to think of.
>
> I have done some initial tests.
>
> - installed 2014.3 and full updated
>
> - disabled 2014 repos
>
> - added and enabled cooker repos
>
> - downloaded all needed pkgs in cache( urpmi --auto-update 
> --no-install --force) because network goes down during update 
> process(more than 2600 pkgs)
>
> - keep more than one root konsole because during update authentication 
> fails
>
> - started update with urpmi --auto-update --force (--force as I don't 
> know the way to prevent bad key messages)
>
> - process stops with:
>
> -------------------------------------------------------------------------------------------------------------------------------
>
> The following packages can't be installed because they depend on packages
> that are older than the installed ones:
> lib64KF5DNSSD5-5.21.0-1
> lib64notesharedprivate5-16.04.0-2
> lib64knotesprivate5-16.04.0-2
> Continue installation anyway? (Y/n)
>
>
> The following packages have to be removed for others to be upgraded:
> kdepim4-kresources-4.14.10-1-omv2014.0.x86_64
>  (due to unsatisfied kdepim4-core == 3:4.14.10-1:2014.0)
> korundum-4.14.3-2-omv2014.0.x86_64
>  (due to missing libokularcore.so.5()(64bit),
>   due to missing libsmokeokular.so.3()(64bit))
> ksendemail-4.14.10-1-omv2014.0.x86_64
>  (due to unsatisfied kdepim4-core == 3:4.14.10-1:2014.0)
> ktimetracker-4.14.10-1-omv2014.0.x86_64
>  (due to unsatisfied kdepim4-core == 3:4.14.10-1:2014.0)
> lib64dolphinprivate4-4.14.3-1.1-omv2014.0.x86_64
>  (due to missing libbaloowidgets.so.4()(64bit))
> lib64fltk0-1.3.2-4-omv2014.0.x86_64
>  (due to conflicts with lib64fltk1.3-1.3.3-4-omv2015.0.x86_64)
> lib64kadm5clnt_mit9-1.12.5-1-omv2014.0.x86_64
>  (due to unsatisfied krb5 == 1.12.5-1)
> lib64kadm5srv_mit9-1.12.5-1-omv2014.0.x86_64
>  (due to unsatisfied krb5 == 1.12.5-1)
> lib64pulseglib20-5.0-2.1-omv2014.0.x86_64
>  (due to missing libpulsecommon-5.0.so()(64bit))
> lib64smokeokular3-4.14.3-2-omv2014.0.x86_64
>  (due to missing libokularcore.so.5()(64bit))
> pinentry-qt4-0.8.2-3-omv2014.0.x86_64
>  (due to unsatisfied pinentry == 0.8.2-3)
> task-kde4-4.14.3-1.1-omv2014.0.noarch
>  (due to missing task-kde4-minimal)
> task-kde4-minimal-4.14.3-1.1-omv2014.0.noarch
>  (due to missing distro-kde4-config-common) (y/N)
>
>  Proceed with the installation of the 2381 packages? (Y/n)
>
>
>  Installation failed:
>         file /usr/share/man/en from install of 
> filesystem-3.0-18.x86_64 conflicts with file from package 
> man-pages-3.58-1.noarch
>         file /usr/share/man/it from install of 
> filesystem-3.0-18.x86_64 conflicts with file from package 
> man-pages-it-2.80-9.noarch
>         file /usr/lib64/libxkbcommon-x11.so.0.0.0 from install of 
> lib64xkbcommon-x11_0-0.6.1-1.x86_64 conflicts with file from package 
> lib64xkbcommon-x110-0.4.2-3.x86_64
>
> -------------------------------------------------------------------------------------------------------------------------------
>
> I think there will be some work to do
> Accept advice
>
>
> -- 
> Saluti, Luca Pedrielli
>
>
> _______________________________________________
> OM-Cooker mailing list
> OM-Cooker at ml.openmandriva.org
> http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://ml.openmandriva.org/pipermail/om-cooker_ml.openmandriva.org/attachments/20160508/f642e24b/attachment.html>


More information about the OM-Cooker mailing list