Currently the posts are filtered by: May 1
Reset this filter to see all posts.
From VDR 1.6 to VDR 1.8: An ongoing journey

If you imagine the yaVDR distro being a human body, its heart would most likely be the VDR (core) software package. The VDR core is mainly maintained and extended by its inventor, Klaus Schmidinger. yaVDR 0.2 will use the currently latest VDR developer version 1.7.14 as its "heart". Although many users of VDR are very happy with 1.7.14, the current stable version of VDR is still version 1.6 which was released back in March 2008. Version 1.6 doesn't contain support for HDTV and DVB-S2 cards, that's why it doesn't make sense for us to use it within yaVDR.
[more]
yaVDR developers celebrate SVN commit 1000
The yaVDR developers have been quite active over the last few days - as you can tell from the diagram on the right. Eager to get the yaVDR 0.2 release ready for the masses, a lot of source code was committed to our source code repository (SVN).
Tonight we reached commit #1000! After a short but brutal fight about who would be the lucky guy to own this revision, we all relaxed and enjoyed this magical moment together in harmony. ;-)
We will give you an overview about the new features of the upcoming yaVDR 0.2 soon. It will be based on Ubuntu Lucid Lynx (10.04) and will impress with an even shorter boot duration than yaVDR 0.1.x. Stay tuned!
XBMC amd64 incomplete on Launchpad!? How come?

It happens from time to time - for example today: amd64 users are confused when they get an error message on installing the latest amd64 packages of XBMC-PVR-Testing from the hepi/yaVDR PPA via apt:
xbmc-data: Depends: xbmc-bin (< pvr-testing-32~hepi-lucid29507.1~) but pvr-testing-33~hepi-lucid29722 is to be installed
The reason for this is that Launchpad has finished building the amd64 packages before the i386 packages were built. How can that be a problem? Some of the packages that XBMC consists of, are marked as platform independent. This means, they only have to be built once and can be used on both platforms, be it i386 or amd64. Launchpad builds those packages marked as platform independent during the i386 build and ignores them during the amd64 build.
[more]

