Re: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental
On Sat, Nov 24, 2012 at 2:09 AM, Reinhard Tartler siret...@gmail.com wrote: On Fri, Nov 23, 2012 at 8:26 PM, Andres Mejia amejia...@gmail.com wrote: On Thu, Nov 22, 2012 at 1:11 AM, Reinhard Tartler siret...@gmail.com wrote: On Tue, Nov 20, 2012 at 1:12 AM, Andres Mejia amejia...@gmail.com wrote: On Mon, Nov 19, 2012 at 7:07 PM, Andres Mejia amejia...@gmail.com wrote: Hi all, FYI, I uploaded a new version of XBMC. I'm notifying you all because of a major change. This version of XBMC will be built and run using XBMC's internal copy of FFMpeg (the 10.2 branch of FFMpeg that is). Due to the number of changes done between FFMpeg and Libav (particularly with libavfilter), it would have taken an enormous amount of work to try and get XBMC building and running using Libav. Also, I did forget to note this major change in the changelog, but I did add a NEWS entry for this. Sorry about that. Also as an aside, I think we should discuss how to get ffmpeg back into Debian again. As I said some time ago, either Libav, FFMpeg, or both have to get their libraries and header paths renamed. I also want to note this now, apparently chromium has been using it's own internal copy of FFMpeg for some time now. Therefore, XBMC is not the first package where using an internal ffmpeg is being done. Are you sure that all involved developers, including chromium xbmc upstream as well as their packagers, would agree on the same FFmpeg snapshot? I don't believe anyone ever mentioned that these two projects should use the same snapshot of ffmpeg. Well, it is out of question that having many different versions of a library such as libavcodec is not acceptable for a stable Debian release. FYI, I've asked on IRC the release team and the security team about that. The security team referred to the security team, who respond with: 23:47 gilbert_ siretart: iuculano made the switch to embedded libav. his plan is to bump chromium to each new upstream throughout wheezy's support lifetime, and having the embedded library makes that a lot more feasible. my opinion is to not release chromium in stable at all since even that is going to way too much work, but i've been overrulled. seems people actually want chromium in stable... Chromium is not a good precedent at all. The maintainer has even joined the security team for having and maintaining it in stable. Moreover, you have to keep in mind that most security issues and fixes do come from chromium upstream. Therefore, this is hardly an excuse for xbmc for handling and outdated, internal copy of FFmpeg in a distribution package. TBH, I'm very skeptical. And with FFmpeg releasing like crazy after the fork, I don't see the project suitable at all for a distro scenario such as Debian. For instance, you indicate that XBMC uses the 0.10 branch; the latest upstream release, however, is 1.0, the release before is 0.11. Chromium maintains it (defacto) own branch, which admittedly is based on FFmpeg master. Therefore, tracking upstream releases does not seem to accommodate either project. To conclude, I understand that xbmc is causing new challenges here, but TBH, I think the better solution would be to investigate what's missing in libav's libavfilter. For instance, I think you mean the audio filter still, which has landed in libav 9. I imagine that there is still some stuff missing, but if it is useful, I'm sure it can be submitted libav upstream. -- regards, Reinhard I don't work on the components of xbmc that uses ffmpeg. Elupus is who you want to speak to. You can either try the xbmc-dev channels or the xbmc forums to reach out to him to see what (if anything) libav could do so xbmc could work with libav. Sorry, I definitely do not have the resources to engage with xbmc, at least not at this point, as I am more than busy with preparing stable libav releases and getting the libav 9 transition going in ubuntu, here is the current progress: https://launchpad.net/~motumedia/+archive/libav9-raring/+packages Help would be more than welcome. To conclude, the fact that the xbmc source package bundles FFmpeg is an RC bug to me that hinders its acceptance jessie. This means that I have no problems having such a copy in experimental, or even unstable, but just not in testing. BTW, we have a similar problem with mplayer, were I have the very same opinion. -- regards, Reinhard I think you meant to respond in the mailing lists. Thanks for your input. -- ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental
I don't believe anyone ever mentioned that these two projects should use the same snapshot of ffmpeg. The point is, which would be the right version of ffmpeg to maintain in Debian if two random upstream projects build against two different versions of it? With its new releases every few weeks, ffmpeg currently seems about as hard to track as it was back then when there were no releases at all... - Fabian ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental
On Thu, Nov 22, 2012 at 1:11 AM, Reinhard Tartler siret...@gmail.com wrote: On Tue, Nov 20, 2012 at 1:12 AM, Andres Mejia amejia...@gmail.com wrote: On Mon, Nov 19, 2012 at 7:07 PM, Andres Mejia amejia...@gmail.com wrote: Hi all, FYI, I uploaded a new version of XBMC. I'm notifying you all because of a major change. This version of XBMC will be built and run using XBMC's internal copy of FFMpeg (the 10.2 branch of FFMpeg that is). Due to the number of changes done between FFMpeg and Libav (particularly with libavfilter), it would have taken an enormous amount of work to try and get XBMC building and running using Libav. Also, I did forget to note this major change in the changelog, but I did add a NEWS entry for this. Sorry about that. Also as an aside, I think we should discuss how to get ffmpeg back into Debian again. As I said some time ago, either Libav, FFMpeg, or both have to get their libraries and header paths renamed. I also want to note this now, apparently chromium has been using it's own internal copy of FFMpeg for some time now. Therefore, XBMC is not the first package where using an internal ffmpeg is being done. Are you sure that all involved developers, including chromium xbmc upstream as well as their packagers, would agree on the same FFmpeg snapshot? I don't believe anyone ever mentioned that these two projects should use the same snapshot of ffmpeg. TBH, I'm very skeptical. And with FFmpeg releasing like crazy after the fork, I don't see the project suitable at all for a distro scenario such as Debian. For instance, you indicate that XBMC uses the 0.10 branch; the latest upstream release, however, is 1.0, the release before is 0.11. Chromium maintains it (defacto) own branch, which admittedly is based on FFmpeg master. Therefore, tracking upstream releases does not seem to accommodate either project. To conclude, I understand that xbmc is causing new challenges here, but TBH, I think the better solution would be to investigate what's missing in libav's libavfilter. For instance, I think you mean the audio filter still, which has landed in libav 9. I imagine that there is still some stuff missing, but if it is useful, I'm sure it can be submitted libav upstream. -- regards, Reinhard I don't work on the components of xbmc that uses ffmpeg. Elupus is who you want to speak to. You can either try the xbmc-dev channels or the xbmc forums to reach out to him to see what (if anything) libav could do so xbmc could work with libav. -- ~ Andres ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental
On Tue, Nov 20, 2012 at 1:12 AM, Andres Mejia amejia...@gmail.com wrote: On Mon, Nov 19, 2012 at 7:07 PM, Andres Mejia amejia...@gmail.com wrote: Hi all, FYI, I uploaded a new version of XBMC. I'm notifying you all because of a major change. This version of XBMC will be built and run using XBMC's internal copy of FFMpeg (the 10.2 branch of FFMpeg that is). Due to the number of changes done between FFMpeg and Libav (particularly with libavfilter), it would have taken an enormous amount of work to try and get XBMC building and running using Libav. Also, I did forget to note this major change in the changelog, but I did add a NEWS entry for this. Sorry about that. Also as an aside, I think we should discuss how to get ffmpeg back into Debian again. As I said some time ago, either Libav, FFMpeg, or both have to get their libraries and header paths renamed. I also want to note this now, apparently chromium has been using it's own internal copy of FFMpeg for some time now. Therefore, XBMC is not the first package where using an internal ffmpeg is being done. Are you sure that all involved developers, including chromium xbmc upstream as well as their packagers, would agree on the same FFmpeg snapshot? TBH, I'm very skeptical. And with FFmpeg releasing like crazy after the fork, I don't see the project suitable at all for a distro scenario such as Debian. For instance, you indicate that XBMC uses the 0.10 branch; the latest upstream release, however, is 1.0, the release before is 0.11. Chromium maintains it (defacto) own branch, which admittedly is based on FFmpeg master. Therefore, tracking upstream releases does not seem to accommodate either project. To conclude, I understand that xbmc is causing new challenges here, but TBH, I think the better solution would be to investigate what's missing in libav's libavfilter. For instance, I think you mean the audio filter still, which has landed in libav 9. I imagine that there is still some stuff missing, but if it is useful, I'm sure it can be submitted libav upstream. -- regards, Reinhard ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Fwd: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental
Hi all, FYI, I uploaded a new version of XBMC. I'm notifying you all because of a major change. This version of XBMC will be built and run using XBMC's internal copy of FFMpeg (the 10.2 branch of FFMpeg that is). Due to the number of changes done between FFMpeg and Libav (particularly with libavfilter), it would have taken an enormous amount of work to try and get XBMC building and running using Libav. Also, I did forget to note this major change in the changelog, but I did add a NEWS entry for this. Sorry about that. Also as an aside, I think we should discuss how to get ffmpeg back into Debian again. As I said some time ago, either Libav, FFMpeg, or both have to get their libraries and header paths renamed. -- Forwarded message -- From: Debian FTP Masters ftpmas...@ftp-master.debian.org Date: Mon, Nov 19, 2012 at 6:49 PM Subject: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental To: Debian XBMC Packaging Team pkg-xbmc-maintain...@lists.alioth.debian.org, Andres Mejia ame...@debian.org Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 19 Nov 2012 17:56:50 -0500 Source: xbmc Binary: xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev xbmc-eventclients-wiiremote xbmc-eventclients-j2me xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send Architecture: source all amd64 Version: 2:12.0~git20121119.22795bc-1 Distribution: experimental Urgency: low Maintainer: Debian XBMC Packaging Team pkg-xbmc-maintain...@lists.alioth.debian.org Changed-By: Andres Mejia ame...@debian.org Description: xbmc - XBMC Media Center (arch-independent data package) xbmc-bin - XBMC Media Center (binary data package) xbmc-eventclients-common - XBMC Media Center (Event Client Common package) xbmc-eventclients-dev - XBMC Media Center (Event Client Dev package) xbmc-eventclients-j2me - XBMC Media Center (Event Client J2ME package) xbmc-eventclients-ps3 - XBMC Media Center (Event Client PS3 package) xbmc-eventclients-wiiremote - XBMC Media Center (Event Client WII Remote support package) xbmc-eventclients-xbmc-send - XBMC Media Center (Event Client XBMC-SEND package) Closes: 668901 681264 682312 685076 Changes: xbmc (2:12.0~git20121119.22795bc-1) experimental; urgency=low . * New upload for beta packages of XBMC Frodo. (Closes: #668901) (Closes: #681264) (Closes: #682312) * Recommends of python-qt3 is removed. (Closes: #685076) Checksums-Sha1: 8472b46a10e73a90c428bc6d328f3f7de38a97ea 3810 xbmc_12.0~git20121119.22795bc-1.dsc 938f168c780f803458cbda5eccfae1ec8860fbaf 54951931 xbmc_12.0~git20121119.22795bc.orig.tar.gz 3ad956b4addf812564d4c454b7028a2dbe7caf7e 37398 xbmc_12.0~git20121119.22795bc-1.debian.tar.gz dfd5c97e7ae3454af7f847fc26edf2f2082681db 21034010 xbmc_12.0~git20121119.22795bc-1_all.deb 4775e819446e436fba099b24eb6b577443a6af72 12077902 xbmc-bin_12.0~git20121119.22795bc-1_amd64.deb 81eefc8af233af513bd1714b5661f7cc3b5ab046 58012 xbmc-eventclients-common_12.0~git20121119.22795bc-1_all.deb e965b33bdc6fa6ff5b96859bcf4bf4844f682177 43332 xbmc-eventclients-dev_12.0~git20121119.22795bc-1_all.deb d81d331b436b68222d0774a6f4c1172389f600fb 61958 xbmc-eventclients-wiiremote_12.0~git20121119.22795bc-1_amd64.deb e620156fd4ae08b717a61bb4a2b807d18f902226 36410 xbmc-eventclients-j2me_12.0~git20121119.22795bc-1_all.deb 8eed3ec12c397346e544684a94b3e8abaa299613 36834 xbmc-eventclients-ps3_12.0~git20121119.22795bc-1_all.deb 11f4feae4ca1258edea2c13fd6f925efbb95a31a 35654 xbmc-eventclients-xbmc-send_12.0~git20121119.22795bc-1_all.deb Checksums-Sha256: 8a92846117224aea5e431abe73d8011b104528ab8cd54e40b3b6c6a199a1d4b4 3810 xbmc_12.0~git20121119.22795bc-1.dsc 777e5be318a901ec84914bb1029983d233ba615c7f6b71d8fd1191b7a5f83cb4 54951931 xbmc_12.0~git20121119.22795bc.orig.tar.gz 7cc5f5a2ed68ccbfb1660420f06372d1832bd56ed04ed31d03e5e2e5e1699ec0 37398 xbmc_12.0~git20121119.22795bc-1.debian.tar.gz ee3466c532549979154bc0aea70d047fafb49ad800e8358985dbc0bf63c14222 21034010 xbmc_12.0~git20121119.22795bc-1_all.deb d0502b10e7a7e9beb16e36929e86dd491fe7d62d6d70e6d8c952497dfa23c6bd 12077902 xbmc-bin_12.0~git20121119.22795bc-1_amd64.deb 5aa2ebacf4878c206ab7c5bac74d6ffe5597e9b736a72b8fe893b00dc8895377 58012 xbmc-eventclients-common_12.0~git20121119.22795bc-1_all.deb 32250ec6cf571dc65cdc25ff1c3d7a2a2c6cfb02077a96c5dfa277e824deb839 43332 xbmc-eventclients-dev_12.0~git20121119.22795bc-1_all.deb b1a54ea06e88a9f13e399ab082b693115bc18563ef50f1038a6cf67bd85f3ba4 61958 xbmc-eventclients-wiiremote_12.0~git20121119.22795bc-1_amd64.deb 44134bb33f740e3cdd1cea2f57ce3d2c27d0363edbb8e78997c8f935e194bc7f 36410 xbmc-eventclients-j2me_12.0~git20121119.22795bc-1_all.deb 151b1c66d1d5ffeb423ff36732e78b246a0e4a11cd2959d341b891b690d3ea6b 36834 xbmc-eventclients-ps3_12.0~git20121119.22795bc-1_all.deb 0d9b65033f992779bfe2983b9e59cd64fbcc8940750ee796d6c7c27574fb5a30 35654 xbmc-eventclients-xbmc-send_12.0~git20121119.22795bc-1_all.deb Files
Re: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental
On Mon, Nov 19, 2012 at 7:07 PM, Andres Mejia amejia...@gmail.com wrote: Hi all, FYI, I uploaded a new version of XBMC. I'm notifying you all because of a major change. This version of XBMC will be built and run using XBMC's internal copy of FFMpeg (the 10.2 branch of FFMpeg that is). Due to the number of changes done between FFMpeg and Libav (particularly with libavfilter), it would have taken an enormous amount of work to try and get XBMC building and running using Libav. Also, I did forget to note this major change in the changelog, but I did add a NEWS entry for this. Sorry about that. Also as an aside, I think we should discuss how to get ffmpeg back into Debian again. As I said some time ago, either Libav, FFMpeg, or both have to get their libraries and header paths renamed. I also want to note this now, apparently chromium has been using it's own internal copy of FFMpeg for some time now. Therefore, XBMC is not the first package where using an internal ffmpeg is being done. -- Forwarded message -- From: Debian FTP Masters ftpmas...@ftp-master.debian.org Date: Mon, Nov 19, 2012 at 6:49 PM Subject: xbmc_12.0~git20121119.22795bc-1_amd64.changes ACCEPTED into experimental To: Debian XBMC Packaging Team pkg-xbmc-maintain...@lists.alioth.debian.org, Andres Mejia ame...@debian.org Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 19 Nov 2012 17:56:50 -0500 Source: xbmc Binary: xbmc xbmc-bin xbmc-eventclients-common xbmc-eventclients-dev xbmc-eventclients-wiiremote xbmc-eventclients-j2me xbmc-eventclients-ps3 xbmc-eventclients-xbmc-send Architecture: source all amd64 Version: 2:12.0~git20121119.22795bc-1 Distribution: experimental Urgency: low Maintainer: Debian XBMC Packaging Team pkg-xbmc-maintain...@lists.alioth.debian.org Changed-By: Andres Mejia ame...@debian.org Description: xbmc - XBMC Media Center (arch-independent data package) xbmc-bin - XBMC Media Center (binary data package) xbmc-eventclients-common - XBMC Media Center (Event Client Common package) xbmc-eventclients-dev - XBMC Media Center (Event Client Dev package) xbmc-eventclients-j2me - XBMC Media Center (Event Client J2ME package) xbmc-eventclients-ps3 - XBMC Media Center (Event Client PS3 package) xbmc-eventclients-wiiremote - XBMC Media Center (Event Client WII Remote support package) xbmc-eventclients-xbmc-send - XBMC Media Center (Event Client XBMC-SEND package) Closes: 668901 681264 682312 685076 Changes: xbmc (2:12.0~git20121119.22795bc-1) experimental; urgency=low . * New upload for beta packages of XBMC Frodo. (Closes: #668901) (Closes: #681264) (Closes: #682312) * Recommends of python-qt3 is removed. (Closes: #685076) Checksums-Sha1: 8472b46a10e73a90c428bc6d328f3f7de38a97ea 3810 xbmc_12.0~git20121119.22795bc-1.dsc 938f168c780f803458cbda5eccfae1ec8860fbaf 54951931 xbmc_12.0~git20121119.22795bc.orig.tar.gz 3ad956b4addf812564d4c454b7028a2dbe7caf7e 37398 xbmc_12.0~git20121119.22795bc-1.debian.tar.gz dfd5c97e7ae3454af7f847fc26edf2f2082681db 21034010 xbmc_12.0~git20121119.22795bc-1_all.deb 4775e819446e436fba099b24eb6b577443a6af72 12077902 xbmc-bin_12.0~git20121119.22795bc-1_amd64.deb 81eefc8af233af513bd1714b5661f7cc3b5ab046 58012 xbmc-eventclients-common_12.0~git20121119.22795bc-1_all.deb e965b33bdc6fa6ff5b96859bcf4bf4844f682177 43332 xbmc-eventclients-dev_12.0~git20121119.22795bc-1_all.deb d81d331b436b68222d0774a6f4c1172389f600fb 61958 xbmc-eventclients-wiiremote_12.0~git20121119.22795bc-1_amd64.deb e620156fd4ae08b717a61bb4a2b807d18f902226 36410 xbmc-eventclients-j2me_12.0~git20121119.22795bc-1_all.deb 8eed3ec12c397346e544684a94b3e8abaa299613 36834 xbmc-eventclients-ps3_12.0~git20121119.22795bc-1_all.deb 11f4feae4ca1258edea2c13fd6f925efbb95a31a 35654 xbmc-eventclients-xbmc-send_12.0~git20121119.22795bc-1_all.deb Checksums-Sha256: 8a92846117224aea5e431abe73d8011b104528ab8cd54e40b3b6c6a199a1d4b4 3810 xbmc_12.0~git20121119.22795bc-1.dsc 777e5be318a901ec84914bb1029983d233ba615c7f6b71d8fd1191b7a5f83cb4 54951931 xbmc_12.0~git20121119.22795bc.orig.tar.gz 7cc5f5a2ed68ccbfb1660420f06372d1832bd56ed04ed31d03e5e2e5e1699ec0 37398 xbmc_12.0~git20121119.22795bc-1.debian.tar.gz ee3466c532549979154bc0aea70d047fafb49ad800e8358985dbc0bf63c14222 21034010 xbmc_12.0~git20121119.22795bc-1_all.deb d0502b10e7a7e9beb16e36929e86dd491fe7d62d6d70e6d8c952497dfa23c6bd 12077902 xbmc-bin_12.0~git20121119.22795bc-1_amd64.deb 5aa2ebacf4878c206ab7c5bac74d6ffe5597e9b736a72b8fe893b00dc8895377 58012 xbmc-eventclients-common_12.0~git20121119.22795bc-1_all.deb 32250ec6cf571dc65cdc25ff1c3d7a2a2c6cfb02077a96c5dfa277e824deb839 43332 xbmc-eventclients-dev_12.0~git20121119.22795bc-1_all.deb b1a54ea06e88a9f13e399ab082b693115bc18563ef50f1038a6cf67bd85f3ba4 61958 xbmc-eventclients-wiiremote_12.0~git20121119.22795bc-1_amd64.deb
