ZCML move breaks incoming mail

Bug #727570 reported by William Grant
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
William Grant

Bug Description

The rename of script.zcml to zcml/script.zcml caused its inclusion of ../+*.zcml to fail to match production's incoming mail ZCML. An extra ../ is required.

Tags: qa-ok

Related branches

William Grant (wgrant)
Changed in launchpad:
milestone: none → 11.03
status: Triaged → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 727570] Re: ZCML move breaks incoming mail

Why didn't any tests break?

Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
Changed in launchpad:
status: In Progress → Fix Committed
Revision history for this message
Tim Penhey (thumper) wrote :

Because we don't test for the inclusion of files outside the tree.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Oh right, it wasn't obvious it was outside the tree. That sucks :(

William Grant (wgrant)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
Revision history for this message
Jonathan Lange (jml) wrote :

I guess we could test this, since it's important. We could create a file in the directory above root during the test process and see if it gets included (and then delete the file, naturally).

Revision history for this message
Robert Collins (lifeless) wrote :

On Thu, Mar 3, 2011 at 9:55 PM, Jonathan Lange <email address hidden> wrote:
> I guess we could test this, since it's important. We could create a file
> in the directory above root during the test process and see if it gets
> included (and then delete the file, naturally).

That would play very poorly during parallel testing. Better to remove
the file altoghether by using host based auth of some sort - e.g.
identd.

-Rob

Revision history for this message
Henning Eggers (henninge) wrote :

This was expected to happen again, see bug 698299.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.