Re: [Cooker] Cooker RPM's
Le Vendredi 17 Janvier 2003 21:58, Laurent Saint-Michel a écrit : > Le Vendredi 17 Janvier 2003 14:09, Pascal Terjan a écrit : > > Cooker is for development purpose. New packages go out, sometime with > > bugs in packaging (e.g. wrong dependencies), someone reports the problem > > and it get fixed. There is allready a bot which check dependency, I have one each weeks for plf too. -- Linux pour Mac !? Enfin le moyen de transformer une pomme en véritable ordinateur. - JL. Olivier Thauvin - http://nanardon.homelinux.org/
Re: [Cooker] Cooker RPM's
Le Vendredi 17 Janvier 2003 22:58, Laurent Saint-Michel a écrit : > Le Vendredi 17 Janvier 2003 14:09, Pascal Terjan a écrit : > > Cooker is for development purpose. New packages go out, sometime with > > bugs in packaging (e.g. wrong dependencies), someone reports the problem > > and it get fixed. > > BTW isn't it possible to make the testing automatic with something like > that : > > 1- strict minimum install (kernel + rpm tools) > > 2 - make an "urpmi .rpm" on each pakage existing (excluding the base) > 3 - report the succes / failure for each package > 4 - remove the package and associated items > 5 - restart at point 5 Cause the point is to use the software also, not just to succeed to install them. -- Disks are always full. It is futile to try to get more disk space. Data expands to fill any void. -- Murphy's Computer Laws n°4
Re: [Cooker] Cooker RPM's
Le Vendredi 17 Janvier 2003 14:09, Pascal Terjan a écrit : > Cooker is for development purpose. New packages go out, sometime with > bugs in packaging (e.g. wrong dependencies), someone reports the problem > and it get fixed. BTW isn't it possible to make the testing automatic with something like that : 1- strict minimum install (kernel + rpm tools) 2 - make an "urpmi .rpm" on each pakage existing (excluding the base) 3 - report the succes / failure for each package 4 - remove the package and associated items 5 - restart at point 5 ? Laurent
Re: [Cooker] Cooker RPM's
This really sounds like you are using cooker RPMS on a 9.0 system. Please tell me you are not doing that! It is not the way cooker should be used!! Danny On Fri, 17 Jan 2003, marrandy wrote: > Hello. > > I am seeing a lot of problems with cooker RPM's. For example, my latest > install quanta3.1-1mdk.i586.rpm > > On attempted install, this aborts with messages showing several failed > dependencies. > > Yet when I use regular mandrake releases, I never see dependency problems. It > would seem the files required are already installed, with the package or > retrieved and installed transparently. > > Why is this such a problem with cooker releases ? > > In the BSD's using the package system, it is setup to check for the required > filkes and libraries plus version, if it doesn't find it, it checks the cdrom > and then goes to the net, downloads and installs it, and continues with the > install. The BSD's have done this for several years. > > I thought this dependency/stop install problem had been fixed in the RPM > system with added capability (go get the required dependency RPM) at least > Three years ago. > > Do we still have to manually go and install, each and every dependency listed > in this day and age. > > Opinions ? Bricks, clubbings...well you know. > > Please enlighten me. > > Regards...Martin > >
Re: [Cooker] Cooker RPM's
On Friday 17 January 2003 08:09 am, Pascal Terjan wrote: > marrandy wrote: > > On attempted install, this aborts with messages showing several failed > > dependencies. > > > > Yet when I use regular mandrake releases, I never see dependency problems. It > > would seem the files required are already installed, with the package or > > retrieved and installed transparently. > > > > Why is this such a problem with cooker releases ? > > Cooker is for development purpose. New packages go out, sometime with > bugs in packaging (e.g. wrong dependencies), someone reports the problem > and it get fixed. > > Another current problem is the mirrors syncing. If you update from a > mirror while it is syncing some of the dependencies may not yet be > available. O.K. - Thanks for the heads-up Regards...Martin
Re: [Cooker] Cooker RPM's
marrandy wrote: On attempted install, this aborts with messages showing several failed dependencies. Yet when I use regular mandrake releases, I never see dependency problems. It would seem the files required are already installed, with the package or retrieved and installed transparently. Why is this such a problem with cooker releases ? Cooker is for development purpose. New packages go out, sometime with bugs in packaging (e.g. wrong dependencies), someone reports the problem and it get fixed. Another current problem is the mirrors syncing. If you update from a mirror while it is syncing some of the dependencies may not yet be available.
