Summary: | New Versions of Zope/Plone Pull Inconsistent Dependencies | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bob Waycott <bobwaycott> |
Component: | [OLD] Server | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Bob Waycott
2007-02-14 08:35:55 UTC
*** This bug has been marked as a duplicate of bug 162712 *** I don't think this bug report has been read through fully. My bug is not reporting pulling two Zope instances as the problem. I have read the bug this has erroneously been referred to as a duplicate. I filed this bug because when attempting to emerge the new versions of Zope and Plone on a fresh system, there are no dependencies being pulled for Zope, and 1/3 of the dependencies being pulled for Plone compared to the older, stable versions. Marking this as a duplicate is not resolving anything. This is a valid bug. So, like(In reply to comment #2) > I filed this bug because when attempting to emerge the new versions of Zope and > Plone on a fresh system, there are no dependencies being pulled for Zope, and > 1/3 of the dependencies being pulled for Plone compared to the older, stable > versions. So, you get some errors on emerge or what? Still don't grok what's this bug about. (In reply to comment #3) > So, you get some errors on emerge or what? Still don't grok what's this bug > about. > I am not getting any errors that prevent the packages from emerging. As the title of the bug explains, there are entirely different dependency requirements between versions. I can understand some packages not being necessary, but has the tree changed so much that using Plone 2.5 eliminates about 20 packages that were dependencies under Plone 2.0? And does Zope 3.3 no longer need to install Python as a dependency, as Zope 2.8 did? I find this hard to believe because Zope is Python-based. I'd be happy to be informed that this really is the case--that new versions of Zope and Plone do not need the dependencies installed with earlier versions. Here's an idea - go file when when you actually *have* issues; not when you think that you might have issues and you don't have any. # tail -n5 plone-2.5.2.ebuild elog "This plone version is a bundled version = contains all necessary zope products" elog "You should carefully manage Your zope instance manually(!) with zprod-manager tool" elog "If You have simple installation (just zope and plone) you can safely execute:" elog "'zprod-manager add' and then mark ${P} to be added to your instance." Closed. Here's an idea: Read through a bug report to understand what is happening before filing it as a duplicate. Had you actually bothered to give this report a bit of thought, you would have seen I was not filing a duplicate bug about two instances of Zope being pulled in by Plone. In fact, you'd have seen my comment that I read that bug and understood it was due to slotting. A second idea: Don't moderate bugs if you're going to be an ass to the users who are trying to understand what is happening. Bug reports get filed because people *think* or *believe* they have a problem and are wanting to *know* if they do or not. Because I did not develop the latest Plone ebuild, I do not know that a change has been made in the structure. And an hour's worth of reading bug reports did not point me in that direction. There is no way to *know* if the problem I *think* I have is a real problem without asking. Here's a final idea - bugzilla is NOT a support forum, and NOT a place to ask questions. Move to #gentoo on Freenode or forums.gentoo.org for questions, and only file bugs after you have verified that it might reasonably be a bug. |