On Thu, Sep 12, 2013 at 09:22:33AM +0800, Thomas Goirand wrote: > On 09/12/2013 05:02 AM, Bill Allombert wrote: > > Package: python-couleur > > Version: 0.5.0-1 > > Severity: important > > > > Hello OpenStack maintainers, > > > > There is a circular dependency between python-couleur, python-steadymark > > and python-sure: > > > > python-couleur :Depends: python-steadymark, python-sure > > python-steadymark :Depends: python-sure, python-couleur > > python-sure :Depends: python-steadymark > > > > Complex circular dependencies are known to cause problems during upgrade, > > so we > > should try to get rid of them. > > > > Cheers, > > Hi, > > These are needed, and there's no way to get rid of it. I don't really > understand how this case is complex, and how it would be a problem in > the case of non arch-specific set of package btw: could you explain?
Independently of other issues, this is increasing the complexity of the dependency graph and bloating the Package file without any benefit to the users. If really the circular dependency is required, then you could as well ship a single package that include the three. But from reading the descriptions of the packages, the dependencies seems strange. Why should a 'tool to play around with ANSI features in a unix terminal' should depend on an 'utility belt for automated testing for Python' ? Cheers, -- Bill. <[email protected]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
