Closed Bug 365725 Opened 15 years ago Closed 15 years ago

add check for read-only files to l10n verification

Categories

(Release Engineering :: General, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: rhelmer)

Details

(Keywords: fixed1.8.0.10, fixed1.8.1.2)

Attachments

(1 file)

l10n verification should catch problems like bug 364599, patch coming up.
Flags: blocking1.8.1.2?
Flags: blocking1.8.0.10?
Check for read-only files when doing l10n test.

Note - this runs on Mac, no "-printf" in BSD "find".
Assignee: nobody → rhelmer
Status: NEW → ASSIGNED
Attachment #250231 - Flags: superreview?
Attachment #250231 - Flags: review?
Attachment #250231 - Flags: superreview?(rcampbell)
Attachment #250231 - Flags: superreview?
Attachment #250231 - Flags: review?(tfullhart)
Attachment #250231 - Flags: review?
Attachment #250231 - Flags: review?(tfullhart) → review+
Attachment #250231 - Flags: superreview?(rcampbell) → superreview+
Landed, thanks:

Checking in verify_l10n.sh;
/cvsroot/mozilla/testing/release/l10n/verify_l10n.sh,v  <--  verify_l10n.sh
new revision: 1.6; previous revision: 1.5
done
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Flags: blocking1.8.1.2?
Flags: blocking1.8.1.2+
Flags: blocking1.8.0.10?
Flags: blocking1.8.0.10+
You guys don't really have branches do you? Can this be marked "fixed1.8.1.2 fixed1.8.0.10" based on the trunk tool checkin? That will get it off our unfixed-blocker list.
Component: Testing → Release Engineering
Flags: blocking1.8.1.2+
Flags: blocking1.8.0.10+
Product: Core → mozilla.org
QA Contact: testing → release
Version: Trunk → other
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.