Description of problem: Configuration file /usr/lib/systemd/system/mythbackend.service is marked executable. Please remove executable permission bits. Proceeding anyway. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. urpmi mythtv-backend 2. journalctl | grep permission Workaround: chmod -x /usr/lib/systemd/system/mythbackend.service
Keywords: (none) => 6sta2
CC: (none) => marja11, pkg-bugsAssignee: bugsquad => mageia
I will recommend updating to 0.28.1 sight unseen https://www.mythtv.org/wiki/Release_Notes_-_0.28.1 Just finished importing my mga5 mythtv dump. Lots of mysql duplicate key errors. Errors about some unknown user which research indicates something to do with mysql and not mythtv. After import, no way to unscramble mysql database. Deletion of myth database and whatnot did not clear up mysql database problems. Forced to do a clean install/update to get back to mythtv testing. Discontinuing mythtv testing until 0.28.1 is available in Mageia Cauldron. FYI: bug 19127 is going to bit mythtv users.
(In reply to Bit Twister from comment #1) Sorry, about misspell. FYI: bug 19127 is going to bite mythtv users.
(In reply to Bit Twister from comment #1) > Just finished importing my mga5 mythtv dump. Lots of mysql duplicate key > errors. Errors about some unknown user which research indicates something to > do with mysql and not mythtv. My mistake. The dump contained the mysql schema which caused all the mysql errors. Re-did the mythtv dump and mga6 install/import without mysql schema and a very basic go/no go test says mythbackend/frontend is ok.
CC'ing some committers, because the registered maintainer is unavailable.
CC: (none) => cjw, eatdirt, geiger.david68210, guillomovitch
Permission was changed in version 31
Status: NEW => RESOLVEDResolution: (none) => FIXED