| tgm4883 | !repos | 02:02 |
|---|---|---|
| Zinn | The Mythbuntu team provides updates for MythTV and Mythbuntu package using the Mythbuntu Repos http://mythbuntu.org/repos | 02:02 |
| === croppa is now known as croppa_ | ||
| === croppa_ is now known as croppa | ||
| KungFuJe1us | So who on earth thought it was a great idea to automatically force an update to the mythtv schema on the master backend when the packages were updated? | 17:58 |
| KungFuJe1us | So who on earth thought it was a great idea to automatically force an update to the mythtv schema on the master backend when the packages were updated? | 17:59 |
| KungFuJe1us | and then subsequently do it each time mythbackend wanted to start?* | 17:59 |
| KungFuJe1us | sorry for the repeated message. Anyway, I've had to restore my mythbackend's database from backups twice now due to an incidental reboot of an ubuntu based computer | 17:59 |
| gregL | KungFuJe1us, When there is a change in the Binary it forces the schema change ..If you run Master,you have to put up with it..If you don't want to do the schema changes,you should only use the fixes branch.. | 18:04 |
| KungFuJe1us | no I get it, it was just updated incidentally, and in a vanilla config before mythbackend launches it warns you and prompts you rightly. Actually mythbackend doesn't even launch until you run mythtv-setup first between revisions | 18:06 |
| KungFuJe1us | Ubuntu packages did it invisibly :( | 18:07 |
| === peterpops_ is now known as peterpops | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!