[Georges Racinet] > I don't really have insight on the best place to put a sample ogg file ; > in the meanwhile, that one is now in python-pygame-doc, and the attached > patch fixes the FTBFS for me. Hoping this short-term fix can be > useful.
Thank you for investigating. The patch look good, but I believe it can not be applied right away, due to issues with other packages. I'll try to explain. The problem at hand seem to be that pygame in unstable (but not testing) changed[1], and introduced a new python-pygame-doc with the file we use in oggvideotools to get a random sample ogg file, causing the build of oggvideotools to fail. The build failure is only in unstable, and do not affect testing. The new version of pygame is unlikely to make it into testing because it contain too many changes. We want to make sure any new uploads of oggvideotool done to unstable are suitable for testing, and thus can not change the build dependency to include the python-pygame-doc package that is missing in testing. [1] http://metadata.ftp-master.debian.org/changelogs/main/p/pygame/unstable_changelog I suspect the two options we have is (1) find another package with a sample ogg file to use during the self testing or (2) generate a ogg file on the fly to do the self testing. Any suggestions for (1) or (2)? The bug version information here is problematic, as the problem is with the version currently in testing and unstable, but the problem only exist in unstable. And as long as the bug is flagged as valid for the version in unstable, it will cause oggvideotools to be removed from testing, even though the problem do not exist there. CC to the release managers, in case any of you have a tip on how to best handle this? Perhaps tag it to ignore this bug in stretch? -- Happy hacking Petter Reinholdtsen
