branch name conflicts with zope.ManageContent

High as per zero-oops-policy

A bit of grepping suggests this comes from zope.app.publisher's browser/configure.zcml, registering the BrowserSkinsVocabulary for="*". Perhaps this can be disconnected.

zope.app.publisher was a year ago mostly split up -- the only thing for which we now depend on it is XML-RPC views. If I replace the zope.app.publisher include directive in zopeapp.zcml with zope.app.publisher.xmlrpc, the problematic view is no longer registered, and everything else continues to work fine.

Care to roll a custom version for us, and to forward the bug upstream?

@Robert, I can't understand what you are telling me. can you elaborate more
if you don't mind.

On Tue, Sep 28, 2010 at 7:11 AM, Robert Collins
<email address hidden>wrote:

> Care to roll a custom version for us, and to forward the bug upstream?
>
> --
> branch name conflicts with zope.ManageContent
> https://bugs.launchpad.net/bugs/640435
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (649500).
>
> Status in Launchpad Foundations: Triaged
>
> Bug description:
> This may be a blacklist problem or a Launchpad configuration problem:
>
> OOPS-1719E277 is caused by accessing
> https://code.launchpad.net/~jlungo/ihris-manage-tz/manage<https://code.launchpad.net/%7Ejlungo/ihris-manage-tz/manage>
> .
> ...
> Module zope.component._api, line 171, in getUtility
> raise ComponentLookupError(interface, name)
> ComponentLookupError: (<InterfaceClass
> canonical.launchpad.webapp.metazcml.ILaunchpadPermission>,
> 'zope.ManageContent')
>
> The branch is named manage. We expect to see the branch. Launchpad is
> loading the zope.ManageContent utility instead. It would be ideal to
> unregister the utility. If we cannot we need to add manage to the blacklist
> and rename the user's branch.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/launchpad-foundations/+bug/640435/+subscribe
>

--
Mobile: +255 71 6387 561

e-mail: <email address hidden>
           <email address hidden>

P. O. Box 15980
Dar es Salaam-Tanzania

Robert, it's zopeapp.zcml in the LP tree. No custom version required.

@Sovello I'm commenting on the bug;

@William - cool; patch it up?

Sovello, no further action by you is required in regard to this bug.
Thanks for telling us about it.

OK. Thanks

On Tue, Sep 28, 2010 at 9:49 AM, Martin Pool <email address hidden> wrote:

> Sovello, no further action by you is required in regard to this bug.
> Thanks for telling us about it.
>
> --
> branch name conflicts with zope.ManageContent
> https://bugs.launchpad.net/bugs/640435
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (649500).
>
> Status in Launchpad Foundations: Triaged
>
> Bug description:
> This may be a blacklist problem or a Launchpad configuration problem:
>
> OOPS-1719E277 is caused by accessing
> https://code.launchpad.net/~jlungo/ihris-manage-tz/manage<https://code.launchpad.net/%7Ejlungo/ihris-manage-tz/manage>
> .
> ...
> Module zope.component._api, line 171, in getUtility
> raise ComponentLookupError(interface, name)
> ComponentLookupError: (<InterfaceClass
> canonical.launchpad.webapp.metazcml.ILaunchpadPermission>,
> 'zope.ManageContent')
>
> The branch is named manage. We expect to see the branch. Launchpad is
> loading the zope.ManageContent utility instead. It would be ideal to
> unregister the utility. If we cannot we need to add manage to the blacklist
> and rename the user's branch.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/launchpad-foundations/+bug/640435/+subscribe
>

--
Mobile: +255 71 6387 561

e-mail: <email address hidden>
           <email address hidden>

P. O. Box 15980
Dar es Salaam-Tanzania

+1 on William's approach. We don't need that vocabulary. Also, generally, the less we rely on configuration in zope.app packages the easier it will be to get rid of them later.

Fixed in stable r11676 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11676>.