• 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 13
Gotham on Debian?
#46
I believe DD= debian developer.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#47
(2013-12-17, 22:13)Martijn Wrote: What is "DD " that you make it seam so important to be?
It stands for Debian Developer and in this context this seems to be important since only DD-s (and Debian Maintainers) can directly update packages in Debian.

(2013-12-17, 22:13)Martijn Wrote: I'm still in favour of pulling out the totally outdated version on debian repo.
It's not like we are going to push out an official version using libav any way so better remove it.
I would like to ask you to give a try to updating Debian's version instead of pulling it from the archive.
With the changes to the main screen and the version in the logs the package is differentiated from the packages distributed by XBMC directly.
This will prevent users from submitting libav related bugs here instead of the Debian BTS which as I understand is the biggest concern.
Not supporting libav in the original XBMC source is not an issue, I won't push accepting the libav related patches.
I share wsnipex's opinion with giving it a try, we can pull the package later if the strategy does not turn out to be working.
Reply
#48
Some additional things:

We did not further develop pulseaudio during gotham. We fixed some bugs concerning song change, but that's it. I suggest you build with --disable-pulse. If you would not do that, the new ActiveAE Audio engine won't work at all. Also it's not possible (without some hacks, e.g. environment variables) to run xbmc without the PAEngine, so alsa users won't have audio.

The other way round, pulseaudio people can just use the "pulse" device, when build with --disable-pulse. Despite that, we expect, that you have working vaapi and working vdpau support. In case of radeon oss vdpau, you need to make sure, that your debian system has libg3dvl-mesa and a mesa version >= 10 available.

Edit: Also make sure to revisit our ffmpeg/patches directory from time to time. I will push another one in some minutes.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#49
(2013-12-20, 12:37)fritsch Wrote: Some additional things:

We did not further develop pulseaudio during gotham. We fixed some bugs concerning song change, but that's it. I suggest you build with --disable-pulse. If you would not do that, the new ActiveAE Audio engine won't work at all. Also it's not possible (without some hacks, e.g. environment variables) to run xbmc without the PAEngine, so alsa users won't have audio.
Thanks, I'll keep that in mind when packaging Gotham.
I plan uploading the package tomorrow based on 12.2 since wsnipex is fine with it and Martijn just disappeared after noting that XBMC project is not interested in maintaining libav compatibility, which I can understand but there is no need for that.

I have prepared a repository for the packaging at http://anonscm.debian.org/gitweb/?p=coll...g-xbmc.git , but I would happily contribute to https://github.com/xbmc/xbmc-packaging/ , too.

Changelog since the last upload to experimental:
xbmc (2:12.2+dfsg1-1) unstable; urgency=low

* Base package on repacked upstream tarball
* Run bootstrap before configuration (without code generation enabled)
* Use external groovy
* Depend on doxygen to help code generation

-- Balint Reczey <[email protected]> Fri, 20 Dec 2013 21:23:12 +0100

xbmc (2:12.2-1) unstable; urgency=low

[ macmenot <[email protected]> ]
* XBMC 12.2 Frodo. Closes: #716806
* Add 01-Compile-against-system-libavcodec.patch and
02-Fix-avcodec-vdpau-detection.patch
(Closes: #706193)
* Fix typo in package description: "archiecture". Closes: #706826

[Balint Reczey]
* Disable libCEC temporarily since it has no usable version in unstable
* Detect Samba4 headers using patched configure.in
* Distinguish Debian build from vanilla XBMC build by showing changed
logo and version number
* Depend on gimp to generate the changed logo
* Adding myself to uploaders
* cherry-pick efbb36fa and c2c97cfd2 from upstream to fix child process
handling and make XBMC work with newer nvidia drivers > 304.
Thanks to Peter Frühberger <fritsch@xbmc.org>
* add get-orig-source target to debian/rules which prepares a DFSG-free
original tarball

-- Balint Reczey <[email protected]> Sun, 08 Dec 2013 00:34:57 +0100

(2013-12-20, 12:37)fritsch Wrote: The other way round, pulseaudio people can just use the "pulse" device, when build with --disable-pulse. Despite that, we expect, that you have working vaapi and working vdpau support. In case of radeon oss vdpau, you need to make sure, that your debian system has libg3dvl-mesa and a mesa version >= 10 available.

Edit: Also make sure to revisit our ffmpeg/patches directory from time to time. I will push another one in some minutes.
Only experimental has Mesa 10 yet, but I'll figure out something to handle the problematic case for the time it is not present in Sid.
Reply
#50
I have uploaded the updated package to unstable and also tried to explain "XBMC from Debian" in a blog post:
http://balintreczey.hu/blog/introducing-...om-debian/

I hope everything goes well. I started cleaning up bug reports in the BTS, too.

Thank you for all the help!
Reply
#51
thanks for your interest and work, now lets see how this works out.
Reply
#52
Sadly others still complain with us: http://trac.xbmc.org/ticket/14769#comment:7

I think debian should make clear very fast what is official and what not. I see my time wasted after telling all the arguments in this thread. If debian packagers are immune to valid arguments, then I see no chance for the future. We already provide an Ubuntu ppa (even automatically build), we can easily provide debian packages.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#53
(2013-12-23, 21:37)rbalint Wrote: I have uploaded the updated package to unstable and also tried to explain "XBMC from Debian" in a blog post:
http://balintreczey.hu/blog/introducing-...om-debian/

I hope everything goes well. I started cleaning up bug reports in the BTS, too.

Thank you for all the help!

You could have waited 1 day and now 12.3 stable is out.
Reply
#54
(2013-12-25, 12:17)fritsch Wrote: Sadly others still complain with us: http://trac.xbmc.org/ticket/14769#comment:7

I think debian should make clear very fast what is official and what not. I see my time wasted after telling all the arguments in this thread. If debian packagers are immune to valid arguments, then I see no chance for the future. We already provide an Ubuntu ppa (even automatically build), we can easily provide debian packages.
The ticket refers to the package shipped by http://deb-multimedia... . It has no connection to Debian and I can't stop the site from shipping XBMC packages.
If this works for you I can send an email to their mailing list asking for removal there as the maintainer in Debian CC-ing you and you can you can also ask for removal upstream.

Removing all links to http://deb-mulitimedia... from the forums would help in avoiding similar bug reports.

I'm registering to trac and answer the bug report, too.

Your time is not wasted at all and thank you for your help.

Debian already states that http://deb-multim... is not related to it https://wiki.debian.org/DebianMultimedia..._Debian.3F however more often we state this the more advertising http://deb-multim... receives improving its Google Rank. I think closing all similar bugs with "XBMC packages shipped by http://deb-multim... are not supported here. For help please turn to the site's bug tracker or mailing lists." would yield the best result long tem.

(2013-12-25, 12:40)uNiversal Wrote:
(2013-12-23, 21:37)rbalint Wrote: I have uploaded the updated package to unstable and also tried to explain "XBMC from Debian" in a blog post:
http://balintreczey.hu/blog/introducing-...om-debian/

I hope everything goes well. I started cleaning up bug reports in the BTS, too.

Thank you for all the help!

You could have waited 1 day and now 12.3 stable is out.
It was a great present for the holidays and I'm already working on packaging it. I would like to test it for a few days before I upload it and I also incorporate fixes based on feedback from packaged 12.2.
Reply
#55
@rbalint: I installed debian lenny jessie (testing) yesterday.

I was happy to see that all depends, we need to build Gotham are already in there. I also tested your debian 12.3 Package. I was quite happy within a short test. I could not test all the audio stuff, cause it was a virtual machine. But thx much that you did the work and added the Logo and so on.

Btw. You can keep out the "Readme" part on the front screen. a "packaged by Debian" would obviously be enough.

Thanks again
Peter
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#56
(2014-01-13, 19:24)fritsch Wrote: @rbalint: I installed debian lenny (testing) yesterday.

I was happy to see that all depends, we need to build Gotham are already in there. I also tested your debian 12.3 Package. I was quite happy within a short test. I could not test all the audio stuff, cause it was a virtual machine. But thx much that you did the work and added the Logo and so on.

Btw. You can keep out the "Readme" part on the front screen. a "packaged by Debian" would obviously be enough.

Thanks again
Peter

I'm glad you found the package good!
Now Frodo is available for unstable, testing and stable (through backports) and I'm looking forward to make Gotham available as well.

I will remove the README pointer as well as you suggested.
Reply
#57
Ouh I meant jessie not lenny :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#58
@wsipex: Now the packages in Debian seem to be OK. Could you please update the wiki at http://wiki.xbmc.org/index.php?title=HOW...nux#Debian reflecting that a simple "apt-get install xbmc" now instals XBMC on Debian?
Maybe a link to http://balintreczey.hu/blog/introducing-...rom-debian would help explaining the differences between vanilla XBMC and "XBMC from Debian".

Thanks!
Reply
#59
Note that we disable support for external ffmpeg and libav for Gotham. In case you tweak the code to use libav it is not XBMC anymore.
Reply
#60
(2014-01-21, 16:08)rbalint Wrote: @wsipex: Now the packages in Debian seem to be OK. Could you please update the wiki at http://wiki.xbmc.org/index.php?title=HOW...nux#Debian reflecting that a simple "apt-get install xbmc" now instals XBMC on Debian?
Maybe a link to http://balintreczey.hu/blog/introducing-...rom-debian would help explaining the differences between vanilla XBMC and "XBMC from Debian".

Thanks!

can't you do that yourself? I never understood people who ask others to change a wiki lol.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
  • 1
  • 2
  • 3
  • 4(current)
  • 5
  • 6
  • 13

Logout Mark Read Team Forum Stats Members Help
Gotham on Debian?0