On Fri, May 19, 2017 at 10:04:20PM +0200, Petter Reinholdtsen wrote: > > [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)?
What's wrong with just adding one to the package for the test? It doesn't have to be generated on the fly, just make (or take) a suitable one and include it in the debian source.
