Yes Reinhart, burek is definitely right. I expect from you, as a packager for libavtools, a bit more honour, professionalism and pride instead of trying to be smart. I do have to tell you that libav and libavtools are among the best tools in the world so you as a packager should reflect that.
The text in the libav-ffmpeg binary is harmful for FFmpeg and potentially harmful for libav because it is (without the context of a complicated backstory and a skewy explanation) indeed untrue. This could, together with the deceptive rigging of the apt packet manager, heavily taint the professional reputation of libav and could eventually be considered a criminal act. You also have to keep in mind that most of the ffmpeg users don't even know about the fork. With 28000+ packets in the ubuntu repository, you can't expect from every user to follow the backstory of every packet. Most of them don't even know that they didn't install ffmpeg but a fork. (apt-get install ffmpeg gives you ??? libavtools. Explain that one to joe user) So try to read the bugreport again and in particular the last two phrases. The message in the forked ffmpeg seems to cause a lot of confusion. Can you imagine why ? Can you explain it in your own words why people seem to find it confusing ? If you can't explain it then you don't understand the bug. No problem, just shut up and leave it to someone else on your team. If you can explain why it causes confusion, YOU can solve the bug. But keep in mind that even if 95% of the ffmpeg developers left the ffmpeg project to continue their work as a fork, it is still a fork so they have to fully come to terms with that. A true fork can only be proud of itself if it behaves like a true fork: 1) A fork is a NEW project. A fresh start. Don't keep old names or logos associated with which you forked from. 2) Never badmouth the motherproject. No nitpicking, no declaring it obsolete or depricating it and no other sneaky tricks. 3) that also means: NOT rigging packetmanagers like apt to let the fork pass for the motherproject. 4) If the fork has come to be out of disagreement, no problem, be proud and fight eachother with the power of coding. ( trespassing these rules will, as you have seen, inevitably and disasterously backfire, it will at least cost trust, loyalty, credibility and goodwill from users and peers alike . . .possibly a lawsuit. . . . .I don't like to see that happen to libav ) I recommend you to apply my proposed tekst as a bugfix or contact upstream a.s.a.p. , they need to know this ! If you don't : within a few years libav could be in a lot of trouble. Keep also in mind that this ubuntu version is supported for 5 years so it won't pass quickly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005536 Title: missleading message in ffmpeg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1005536/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
