MythTV in breezy is updated to 0.18.1 but the plugins aren't
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mythtv (Ubuntu) |
Fix Released
|
Medium
|
Matt Zimmerman |
Bug Description
The mythtv package in breezy is updated to version 0.18.1 but the myth plugins are still at version 0.17 as far as I can tell from packages.ubuntu.com and the buildlogs at http://
I have tried to build the source package from http://
g++-3.4 -c -pipe -Wall -W -O3 -march=pentiumpro -fomit-
aacdecoder.cpp: In member function `bool aacDecoder:
aacdecoder.cpp:298: error: invalid conversion from `long unsigned int*' to `uint32_t*'
aacdecoder.cpp:298: error: initializing argument 4 of `int8_t faacDecInit2(void*, uint8_t*, uint32_t, uint32_t*, uint8_t*)'
make[3]: *** [aacdecoder.o] Error 1
make[3]: Leaving directory `/tmp/buildd/
make[2]: *** [sub-mythmusic] Error 2
make[2]: Leaving directory `/tmp/buildd/
make[1]: *** [sub-mythmusic] Error 2
make[1]: Leaving directory `/tmp/buildd/
make: *** [build-stamp] Error 2
pbuilder: Failed autobuilding of package
The following patch fixes this problem for me:
--- mythplugins-
+++ mythplugins-
@@ -52,7 +52,7 @@
bool done, finish;
long len, bitrate;
uchar channels;
- unsigned long sample_rate;
+ uint32_t sample_rate;
unsigned long output_size;
double totalTime, seekTime;
With this patch the mythplugins source package builds without further problems. As far as I can tell from the mythplugins source code the changes in this patch can hardly do any harm. The only problem is that I also had a quick look at the mythplugins-
I hope this helps to make it possible to update the mythplugins packages for breezy, because I am affraid that the current situation might cause some upgrade problems.
Sincerely,
Jordy Potman
Changed in mythtv: | |
assignee: | nobody → mdz |
Changed in mythtv: | |
status: | New → Fixed |
A mythplugins package has recently been imported to breezy and the mythplugins- 0.18.1- 3 source package contains a (slightly different) fix for the build problem I describe above. According to the buildlogs the package builds fine now, so I guess this bug can be closed.