** Description changed: Binary package hint: mythexport Relies on ffmpeg from medibuntu, which no longer exists for intrepid, ffmpeg lines need to be modified to fit new intrepid ffmpeg flags. Related bugs: https://bugs.launchpad.net/ubuntu/+source/ffmpeg-debian/+bug/6366 and https://bugs.launchpad.net/medibuntu/+bug/291011 Additional SRU information: Bug 297019 (https://bugs.edge.launchpad.net/ubuntu/+source/mythexport/+bug/297019) - Why Needed: The new dependencies are needed for ffmpeg, otherwise every attempt by MythExport to export a recording from MythTV will fail, thus making this package essentially useless. This change adds a few new dependencies that are needed in order to properly use ffmpeg. - Regression Potential: Regression potential would be a broken dependency. - Steps Taken to Avoid Regression: Installation on virtualbox, testing hardware, and production hardware. - Code Change: http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/44 - Test Case: Attempt to export a recording from MythTV. File will not be created, check the backend logs for error indicating current ffmpeg does not have aac or mp3 capabilities. + WHY NEEDED: The new dependencies are needed for ffmpeg, otherwise every attempt by MythExport to export a recording from MythTV will fail, thus making this package essentially useless. This change adds a few new dependencies that are needed in order to properly use ffmpeg. + + REGRESSION POTENTIAL: Regression potential would be a broken dependency. + + STEPS TAKEN TO AVOID REGRESSION: Installation on virtualbox, testing + hardware, and production hardware. + + CODE CHANGE: + http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/44 + + TEST CASE: Attempt to export a recording from MythTV. File will not be + created, check the backend logs for error indicating current ffmpeg does + not have aac or mp3 capabilities. + Bug 288184 (https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/288184) - Why Needed: It is common to run scripts on MythTV recordings in order to make the files human readable. Doing so normally adds spaces which will result in MythExport to fail on these files. This change surrounds the file names with quotes in all ffmpeg commands. - Regression Potential: Possible regression would include an failure to running the perl script. - Steps Taken to Avoid Regression: Perl script uses strict, any errors would be noted immediately. - Code Change: http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/39 - Test Case: Rename a MythTV recording's file name to include spaces. Attempt to export this recording. Exporting will fail due to the spaces. + WHY NEEDED: It is common to run scripts on MythTV recordings in order to make the files human readable. Doing so normally adds spaces which will result in MythExport to fail on these files. This change surrounds the file names with quotes in all ffmpeg commands. + + REGRESSION POTENTIAL: Possible regression would include an failure to + running the perl script. + + STEPS TAKEN TO AVOID REGRESSION: Perl script uses strict, any errors + would be noted immediately. + + CODE CHANGE: + http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/39 + + TEST CASE: Rename a MythTV recording's file name to include spaces. + Attempt to export this recording. Exporting will fail due to the spaces. + Bug 282498 (https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/282498) - Why Needed: Moved mythtv-backend or mythtv-database to Pre-Depends. Some users who were installing MythExport with a fresh install of MythTV received errors while installing. MythExport expects MythTV's database to exist before it installs. - Regression Potential: I don't see much regression potential here, the packages were depends and are now pre-depends. - Steps Taken to Avoid Regression: Installation on virtualbox, testing hardware, and production hardware - Code Change: http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/41 - Test Case: Install MythExport before the mythtv-backend or mythtv-database are installed. Installation will fail as mentioned in above comments. + WHY NEEDED: Moved mythtv-backend or mythtv-database to Pre-Depends. Some users who were installing MythExport with a fresh install of MythTV received errors while installing. MythExport expects MythTV's database to exist before it installs. + + REGRESSION POTENTIAL: I don't see much regression potential here, the + packages were depends and are now pre-depends. + + STEPS TAKEN TO AVOID REGRESSION: Installation on virtualbox, testing + hardware, and production hardware + + CODE CHANGE: + http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/41 + + TEST CASE: Install MythExport before the mythtv-backend or mythtv- + database are installed. Installation will fail as mentioned in above + comments. + Bug 297016 (https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/297016) - Why Needed: Archos player ffmpeg commands were missing the aspect option that all other players had. Simply adding this to the ffmpeg command fixes the issue. This is more of a typo than anything as I missed adding it in the first place. - Regression Potential: Possible regression would include an failure to running the perl script or an invalid export for Archos players. - Steps Taken to Avoid Regression: Perl script uses strict, any errors would be noted immediately. Users who own Archos players specifically tested this out for me. - Code Change: http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/43 - Test Case: Use the following in a MythTV user job: + WHY NEEDED: Archos player ffmpeg commands were missing the aspect option that all other players had. Simply adding this to the ffmpeg command fixes the issue. This is more of a typo than anything as I missed adding it in the first place. + + REGRESSION POTENTIAL: Possible regression would include an failure to + running the perl script or an invalid export for Archos players. + + STEPS TAKEN TO AVOID REGRESSION: Perl script uses strict, any errors + would be noted immediately. Users who own Archos players specifically + tested this out for me. + + CODE CHANGE: + http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/43 + + TEST CASE: Use the following in a MythTV user job: mythexport exportdir=/var/lib/mythtv/mythexport starttime=%STARTTIME% chanid=%CHANID% size=430x240 aspect=16:9 audio_bitrate=192kb video_bitrate=900kb export_device=archos export_codec=xvid Resulting files will not obey the selecting aspect ratio. + Bug 288186 (https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/288186) - Why Needed: The RSS script is written so that an address does not need to be hard coded and it should be able to figure out which address the user is using and continue using that to point at files in the RSS feed itself. This worked well for all users except one who used a reverse proxy. This change simply uses the HTTP_X_FORWARDED_HOST environment variable if available instead of the HTTP_HOST environment variable. - Regression Potential: Possible regression would include a user having a setup that for some reason returned a HTTP_X_FORWARDED_HOST when one shouldn't exist. - Steps Taken to Avoid Regression: Tested on production and testing hardware. The user who reported the issue verified that this fixes the issue for his setup. - Code Change: http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/39 - Test Case: "My MythTV box is behind a few firewalls so the 1.0.2 version of "mythexportRSS.cgi" didn't have the correct value in HTTP_HOST when my front-end reverse proxy (Apache) web server returns the output of the script from the MythTV web server" + WHY NEEDED: The RSS script is written so that an address does not need to be hard coded and it should be able to figure out which address the user is using and continue using that to point at files in the RSS feed itself. This worked well for all users except one who used a reverse proxy. This change simply uses the HTTP_X_FORWARDED_HOST environment variable if available instead of the HTTP_HOST environment variable. + + REGRESSION POTENTIAL: Possible regression would include a user having a + setup that for some reason returned a HTTP_X_FORWARDED_HOST when one + shouldn't exist. + + STEPS TAKEN TO AVOID REGRESSION: Tested on production and testing + hardware. The user who reported the issue verified that this fixes the + issue for his setup. + + CODE CHANGE: + http://bazaar.launchpad.net/~mythbuntu/mythexport/trunk/revision/39 + + TEST CASE: "My MythTV box is behind a few firewalls so the 1.0.2 version + of "mythexportRSS.cgi" didn't have the correct value in HTTP_HOST when + my front-end reverse proxy (Apache) web server returns the output of the + script from the MythTV web server" I maintain the upstream for this, so all these changes have been made by myself. I run this every day on my production box, and this version has been on the Mythbuntu Testing PPA for quite some time now. I have the wiki and release announcement in the forum pointing at the Mythbuntu Testing PPA as well, this is fairly well tested and the changes are minor with very little risk involved.
-- mythexport relies on ffmpeg from medibuntu https://bugs.launchpad.net/bugs/297019 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
