[Icecast-dev] Packages of icecast 2.4-beta?
"Thomas B. Rücker"
thomas at ruecker.fi
Sun Mar 31 09:44:44 PDT 2013
On 03/28/2013 02:47 PM, Daniel James wrote:
> Hi Thomas,
>> Do you have the infrastructure to stay current and rebuild e.g. on
>> dependency changes?
> Yes, we use pbuilder-dist for this. We are providing backports of
> related packages including liquidsoap, silan (a new silence detector
> application), and libopus0, as well as Airtime itself.
>> Actually I now wonder if using OBS could make this task easier. We could
>> have a community team and OBS should be able to produce packages for
>> most main stream distros and rebuild them automagically.
>> build.opensuse.org - they cover at least: opensuse, suse, debian,
>> ubuntu, fedora, centos/rhel and mandriva.
> Following their search tool I only found SuSE packages:
> but if they are willing to help, it's all good.
They actually have quite a catalogue of distros you can build against.
I set up a project to try out packaging and building on OBS:
Note that RPM distros are not building yet. Turns out they depend on the
debian packaging directory we removed last summer after releasing 2.3.3.
I'll fix that soon. This will lead to rebuilding of all distro targets.
Successfully built debian packages are available for testing
irrespectively of the current build state though.
Feel free to give them a spin, I didn't have the time yet to try them
myself, so don't scream if they bite your dog or eat your cat. ;-)
So far this looks like a reasonably low maintenance, high value output
approach to experimental Icecast packages.
I'm very interested to hear people's thoughts on this.
>>> We provide apt.sourcefabric.org which is not a PPA as such, it's a
>>> regular apt repo.
>> Sure, I guess people would be happy to see that and as long as there are
>> no major patches to them we'll be happy to support those builds in the
> I agree it wouldn't be helpful to patch with unofficial changes during a
> beta cycle. We usually only patch for production users between official
> releases, but in consultation with the upstream developers (for example,
> we have done this for liquidsoap).
Sounds sane. We're very happy about patches that fix issues.
>>> Is a beta2 on the horizon? Or are there fixes since beta1 we should
>>> include as patches?
>> Yeah, I should have rolled one a while ago, there are some issues that
>> are creeping out and more testing and eyes on those would actually be
> Great, we will give it a try :-)
I released that yesterday morning.
>>> Would it be generally useful to the Icecast community to have a 2.4 test
>>> server available? Or do people generally have spare machines to use for
>> That might actually be quite valuable for interested people to get a
>> feeling without having to set up too many things at once, so I very much
>> welcome the effort.
> OK, I have suggested this to the Airtime team.
>> Icecast should out of the box provide the configurability to avoid
>> making this a free-for-all abuse box
> Debian has tightened up the source/relay/admin passwords now. You get
> prompted for the passwords you would like to set at install time, via
> debconf, in the latest version.
Yeah, I noticed that, It's a nice thing the package maintainers did there.
>> e.g. time limit for listeners,
>> maybe also source timeout and max number of listeners.
> We currently set listener limits for our managed hosting, so that
> shouldn't be a problem.
>> I may be able to provide one too in the near future. We just received a
>> donation of nice machines from Intel at Xiph and they will be installed
>> hopefully soon.
> Airtime supports up to three independent output streams so it's actually
> very easy for users to set up an alternative test stream. I'm sure the
> Airtime community would provide some authentic test material if we asked
> them to.
Let's look at that once the machines are set up. Currently they are
powered off in some shelve at OSUOSL.
More information about the Icecast-dev