Closed
Bug 1341486
Opened 8 years ago
Closed 8 years ago
comment out 1.0 generation for thunderbird autoconfig
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Infrastructure & Operations Graveyard
WebOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Atoll, Assigned: joeyk)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4279])
The new operator (soon) for the Thunderbird components found a bug in the current dataset, that's resolved by disabling autoconfig v1.0 support.
Research reveals that the v1.0 API was replaced by v1.1 prior to Thunderbird 3.1 (2010), which itself has been EOL for some time.
However, this one specific issue could cause Thunderbird users out in the wild to not get correct mail server information for their providers, and so we have a single-character change to request.
staticadm:/data/static/src/autoconfig.thunderbird.net/update
python ../tools/convert.py -a -d $DEST/v1.0 -v 1.0 *
python ../tools/convert.py -a -d $DEST/v1.1 *
Please comment out the -v 1.0 line in this script, so that v1.1 can be generated correctly. A single character is fine, and we're not likely to see any changes upstream prior to the cutover to new repos.
Assignee | ||
Comment 1•8 years ago
|
||
Line commented out, here is the new content of the update file:
[jkrejci@staticadm.private.phx1 autoconfig.thunderbird.net]$ cat update
#!/bin/sh
DEST=/data/static/src/autoconfig.thunderbird.net/docroot
cd /data/static/src/autoconfig.thunderbird.net/autoconfig
#Line below commented out Bug 1341486
#python ../tools/convert.py -a -d $DEST/v1.0 -v 1.0 *
python ../tools/convert.py -a -d $DEST/v1.1 *
/data/static/deploy -nq autoconfig.thunderbird.net
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•