Mandrake Linux Archives: cooker@mandrivalinux.org
Mandrake Linux: cooker@mandrivalinux.org
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
- From: Guillaume Rousse
- Subject: Re: [Cooker] Broken dependencies
- Date: 31 May 2005 20:50:59 -0000
Gustavo Niemeyer wrote:
Greetings!The official catch procedure is: run some old half broken script turn weekly
I'm researching about migration from Conectiva Linux to the future Mandriva Linux 2006, and I've got several problems regarding broken dependencies on packages currently in Cooker (main/contrib). Is there any standard procedure to catch those problems and fix them eventually?
The official fix procedure is: cry/scream after warly.
A full resume of the current QA reports is available from http://qa.mandriva.com/twiki/bin/view/Main/PackagingReports
Nothing yet. And I doubt the state of the upload script is susceptible to add such mechanism quickly.Also, is there any mechanism to avoid breaking relations (or at least warn the packager) when a new package which will break something is submitted?
--
When reviewing your notes before an exam, the most important ones will be illegible.
-- Laws of Applied Terror n°1
- References:
- [Cooker] Broken dependencies
- From: Gustavo Niemeyer
- [Cooker] Broken dependencies
- Prev by Date: Re: [Cooker] rpm and nptl
- Next by Date: Re: [Cooker] Broken dependencies
- Previous by thread: [Cooker] Broken dependencies
- Next by thread: Re: [Cooker] Broken dependencies
- Index(es):
