Thanks Alex, but I can't do that on a production server. I believe you understand, as you already say "this might be inappropriate". :-) But you are right, it may help others on a Desktop system.
I know that I could have simply patched this package and compiled my own, but this would mean "removing" this package from the control of the package system, which is something I simply do not want; as ffserver is a network-facing tool; and which is something any Linux Distribution also wouldn't want. For me, I'm learning two things from this occasion: 1) Even in an LONG TERM SUPPORT release, even in the most severe regression ever (program once worked, but stopped working for everyone, and the fix is a well-tested, non-invasive, minimal-effort one-liner in the software itself, not in a core package) isn't enough for Ubuntu to fix it. Yes, call it a bit polemic, but that's the truth. I've not even gotten a 'ok, *if* there's another release of the package, we are including this one-liner' message to this day. 2) For me, it's back to Gentoo on those servers again. I wanted a somewhat less-effort approach on a stable standard-software system. I somehow thought Ubuntu LTS was designed to be just that. Back to 'do it all yourself' then. More work, more control. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/879018 Title: ffserver cannot bind listening port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/879018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
