found 963895 1:7.0.0~beta2-2 severity 963895 minor
reassign 963895 libuno-cppu3,libuno-sal3,libuno-cppuhelpergcc3-3,libuno-salhelpergcc3-3,uno-libs3,ure retitle 963895 circular dependencies between libuno-cppu3,libuno-sal3,libuno-cppuhelpergcc3-3,libuno-salhelpergcc3-3,uno-libs3,ure thanks [ And again you did it. Again by accussing people of carelessness and not thinking and by using the words "dependency hell". There is no dependency "hell" here. Didn't we already have this the last time you came up with a "bug" like this? ] Hi, Am 28.06.20 um 17:56 schrieb Bill Allombert: > Package: libuno-cppu3 If this was a circular dependency, why only filed on this one? If you file "bugs", please some care. > Version: 1:6.4.5~rc1-2 Dead. There will only be a update to 6.4.5-1 final next week and then 6.4.x will be dead. Unstable will get 7.0.0 rc1. And I simply will not rush something like this in for a last 6.4.x upload, no, sorry. > Severity: important Wrong. Please tell me how this fits into --- snip --- 1 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. --- snip --- How does it have "a major effect on the usability of a package"? The use of this package is at runtime, where everything is straight. > There is a circular dependency between libuno-cppu3, libuno-cppuhelpergcc3-3, > libuno-purpenvhelpergcc3-3, libuno-salhelpergcc3-3, uno-libs-private and ure: > > libuno-cppu3 :Depends: libuno-salhelpergcc3-3 (>= 1.4.0), ure > libuno-cppuhelpergcc3-3 :Depends: uno-libs-private (= 1:6.4.5~rc1-2), > libuno-cppu3 (>= 4.4.0~alpha), libuno-salhelpergcc3-3 (>= 1.4.0), ure Unfortunately the public libuno_cppuhelpergcc3.so.3 depends on private libs. (uno-libs-private). What are you expecting? Not declare that dependency? That would be a policy violation. > libuno-purpenvhelpergcc3-3 :Depends: libuno-cppu3 (>= 1.4.0), ure > libuno-salhelpergcc3-3 :Depends: ure One can argue about the "ure" here. This comes from the .symbols and is - if I remember right - just there to have C++ stuff using those libs have the appropriate runtime dependencies. (We don't have some right now, one in the past was libreoffice-voikko, though.) Because those libraries in itself are totally useless without ure. > uno-libs-private :Depends: libuno-cppu3 (>= 1.4.0), > libuno-salhelpergcc3-3 (>= 1.4.0), ure > ure :Depends: uno-libs-private (= 1:6.4.5~rc1-2), libuno-cppu3 (>= > 4.4.0~alpha), libuno-cppuhelpergcc3-3 (>= 4.0.0~alpha), > libuno-purpenvhelpergcc3-3 (>= 1.4.0), libuno-salhelpergcc3-3 (>= 3.6.0~beta) These are simply not discussable since that are the actual library dependencies. The nature of private libs is that they are private. One might merge uno-libs-private into ure, but I don't think that makes sense. Neither does merging all those libuno* somewhere else (packages of public libraries should be named to that they change if the SONAME changes, and lintian correctly complains about package-name-not-matching-soname or however it it called.) > Complex circular dependencies are known to cause problems during upgrade, If said stuff is used during the upgrade. None of these is. If apt broke the cycle up during update so what? After the upgrade they will be present as intended. Regards, Rene