mythbuntu-bugs team mailing list archive

[Launchpad Bug Tracker <462405@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package mythplugins -
0.22.0+fixes23527-0ubuntu1

---------------
mythplugins (0.22.0+fixes23527-0ubuntu1) lucid; urgency=low

  * New snapshot (r23527)
  * debian/control:
    - Recommends for python-imaging (LP: #500313)
  * debian/mythweb.postinst:
    - Check that a 'default' site is available before attempting to
      make a new one. (LP: #462405)
    - Check that the new site to enable exists before enabling.
  * debian/mythvideo.cron.*:
    - Redirect all output on stderr into the log file too (LP: #487880)
    - Check that a frontend is installed to determine if this job should
      be ran. (LP: #507436)
  * debian/mythvideo.logrotate:
    - Supply a logrotate script for jamu.

  [ Nicholas J Kreucher ]
  * debian/mythvideo.cron.*:
    - Use getent instead of grep /etc/passwd (LP: #511858)
 -- Mario Limonciello <superm1@xxxxxxxxxx>   Sun, 14 Feb 2010 19:24:14 -0600

** Changed in: mythplugins (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
default-mythbuntu changed my root website when I recently upgraded
https://bugs.launchpad.net/bugs/462405
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Fix Committed
Status in “mythplugins” package in Ubuntu: Fix Released

Bug description:
My most recent weekly build upgrade of mythweb resulted in my root website being replaced by the mythweb site.  I traced the cause to the fact that a file was created (/etc/apache2/sites-enabled/default-mythbuntu) that was redirecting via 301 HTTP messages to the mythweb site.

Problem was resolved by

a2dissite default-mythbuntu

/etc/init.d/apache2 restart

This particular weekly update failed to install via apt and update-manager.  The reported reason via the command line was that it was unable to find a particular file (/etc/aache2/sites-available/default).  I use virtual hosting in apache and thus do not ahve a "default" site.  I manually created a symlink to my main website config file and called it default.  This allowed the upgrade to complete, but then the problem above occurred.

I hope future builds do not install this file, as it breaks my apache config and requires manually updating things (assuming the upgrade can occur without a default site).