From trac at xiph.org Fri Apr 7 17:53:55 2017 From: trac at xiph.org (Xiph) Date: Fri, 07 Apr 2017 17:53:55 -0000 Subject: Bug#198765: Batch modify: #448, #502 Message-ID: Batch modification to #448, #502 by ePirat: component to Vorbis Tools -- Tickets URL: Xiph building a new era of Open multimedia From lamby at debian.org Thu Apr 27 06:21:44 2017 From: lamby at debian.org (Chris Lamb) Date: Thu, 27 Apr 2017 07:21:44 +0100 Subject: Bug#861298: oggvideotools: FTBFS: can not open file for reading Message-ID: <1493274104.2873026.957802104.05FA1EB6@webmail.messagingengine.com> Source: oggvideotools Version: 0.9.1-3 Severity: serious Justification: fails to build from source User: reproducible-builds at lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bugs at lists.alioth.debian.org Dear Maintainer, oggvideotools fails to build from source in unstable/amd64: [?] + echo info: Copy Ogg Theora file using oggJoin. info: Copy Ogg Theora file using oggJoin. + ?BUILDDIR?/obj-x86_64-linux-gnu/src/binaries/oggJoin out.ogv slideshow.ogv + echo info: Copy Ogg Vorbis file using oggJoin. info: Copy Ogg Vorbis file using oggJoin. + ?BUILDDIR?/obj-x86_64-linux-gnu/src/binaries/oggJoin out.ogv /usr/lib/python*/dist-packages/pygame/examples/data/house_lo.ogg FileRepository::open failed: No such file or directory Warning: can not open file for reading Error: could not open any stream - abort + at_exit + set +x info: test exiting, removing /tmp/tmp.zASt9fl82q debian/rules:11: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 255 make[1]: Leaving directory '?BUILDDIR?' debian/rules:4: recipe for target 'binary' failed make: *** [binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 [?] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` lamby at debian.org / chris-lamb.co.uk `- -------------- next part -------------- A non-text attachment was scrubbed... Name: oggvideotools.0.9.1-3.unstable.amd64.log.txt.gz Type: application/octet-stream Size: 34264 bytes Desc: not available URL: From pere at hungry.com Thu Apr 27 07:27:41 2017 From: pere at hungry.com (Petter Reinholdtsen) Date: Thu, 27 Apr 2017 09:27:41 +0200 Subject: Bug#861298: oggvideotools: FTBFS: can not open file for reading In-Reply-To: <1493274104.2873026.957802104.05FA1EB6@webmail.messagingengine.com> References: <1493274104.2873026.957802104.05FA1EB6@webmail.messagingengine.com> Message-ID: <2fl37cujonm.fsf@diskless.uio.no> [Chris Lamb] > info: Copy Ogg Vorbis file using oggJoin. > + ?BUILDDIR?/obj-x86_64-linux-gnu/src/binaries/oggJoin out.ogv /usr/lib/python*/dist-packages/pygame/examples/data/house_lo.ogg > FileRepository::open failed: No such file or directory > Warning: can not open file > > for reading Hm, I guess our dependency changed the file layout. :( The file is just a random ogg file used for self testing during build. Any ogg file will do. Can we figure a better source for a random ogg file? -- Vennlig hilsen Petter Reinholdtsen From ron at debian.org Thu Apr 27 08:50:28 2017 From: ron at debian.org (Ron) Date: Thu, 27 Apr 2017 18:20:28 +0930 Subject: Bug#861298: oggvideotools: FTBFS: can not open file for reading In-Reply-To: <2fl37cujonm.fsf@diskless.uio.no> References: <1493274104.2873026.957802104.05FA1EB6@webmail.messagingengine.com> <2fl37cujonm.fsf@diskless.uio.no> Message-ID: <20170427085028.GR7501@hex.shelbyville.oz> On Thu, Apr 27, 2017 at 09:27:41AM +0200, Petter Reinholdtsen wrote: > [Chris Lamb] > > info: Copy Ogg Vorbis file using oggJoin. > > + ?BUILDDIR?/obj-x86_64-linux-gnu/src/binaries/oggJoin out.ogv /usr/lib/python*/dist-packages/pygame/examples/data/house_lo.ogg > > FileRepository::open failed: No such file or directory > > Warning: can not open file > > > > for reading > > Hm, I guess our dependency changed the file layout. :( > > The file is just a random ogg file used for self testing during build. > Any ogg file will do. Can we figure a better source for a random ogg > file? If it's a self-test, then it should probably just include an explicitly known one for that purpose, rather than hoping something random from another source will remain suitable. Then you can test that the output is actually what would be expected rather than that it just doesn't completely explode in flames trying. And won't need to B-D on odd packages just for a data file in them. Cheers, Ron