Bugzilla Bug 87947

When daylight savings shifted the time to daylight time Saturday, MythTV
incorrectly reflected the start time of programs shifted by one hour.  This
problem was caused by a fix to a bug in QT 3.3.4 which broke a work around in
MythTV.  CVS has been patched to correct this bug but 0.17 has not.  

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Created an attachment (id=55294) [edit]
QDate Patch pulled from CVS updates

This is a patch for mythtv-0.17-r1.ebuild attached next.

Created an attachment (id=55295) [edit]
Ebuild using patch for qdate.

Ebuild to use the attached patch.

Created an attachment (id=55318) [edit]
qdate daylight savings time patch without ~ files

Same as patch above, but without the backup files (~) created by the editor.

Someone asked how to use this fix, if you already have a bad set of listings
you will have to log into mysql and truncate the program table, then rerun
mythfilldatabase after you recompile mythtv.  

For instance:
# /etc/init.d/mythbackend stop
# mysql -u mythtv -p 
mysql> use mythconverg;
mysql> truncate table program;
mysql> commit;
mysql> quit
# /etc/init.d/mythbackend start
# mythfilldatabase

Obviously I am skipping interactive prompts such as password. 

Not gonna happen. There's no clean upgrade path for someone just pushing a new
-r1 ebuild out. They're going to have to tinker with MySQL tables etc.

0.18 with the fixes will be out in 3 days.

Plus I don't have a dev box for 2 weeks. Windows bound.

This is great for those of us willing to tinker.  Thanks.

I added -r1 to portage with this patch but left it in package.mask since cardoe
wants to wait for 0.18.  You can unmask it with /etc/portage/package.unmask or
just wait for 0.18...

*** Bug 91698 has been marked as a duplicate of this bug. ***

Anyone in a Daylight Savings zone who, today, does an "emerge mythtv" (which
will give them 0.16 unless they want to unmask some stuff) will get an
application that is NON-FUNCTIONAL.  

Can the ebuilds for 0.16 be adjusted to say "I don't work with QT >=3.3.4" ? 
When I first encountered this problem I masked qt-3.3.4-r2, but then a recent
update installed qt-3.3.4-r3.

Using PORTDIR_OVERLAY I have determined that altering mythtv-0.16.ebuild to say

  DEPEND=">=media-libs/freetype-2.0
          >=media-sound/lame-3.93.1
!         X? ( >=x11-libs/qt-3.1 <x11-libs/qt-3.3.4 )
          directfb? ( dev-libs/DirectFB >=x11-libs/qt-embedded-3.1 )
...

is sufficient to express mythtv's requirements.

Never mind.  having a <x11-libs/qt-3.3.4 in the DEPENDS does not solve the
problem.  Some other fix is needed.