Bug#912076: marked as done (kodiplatform FTBFS with debhelper 11.4)
Your message dated Mon, 24 Jun 2019 19:18:36 + with message-id and subject line Bug#912076: fixed in kodiplatform 17.1.0-1.1 has caused the Debian Bug report #912076, regarding kodiplatform FTBFS with debhelper 11.4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 912076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kodiplatform Version: 17.1.0-1 Severity: serious Tags: ftbfs https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kodiplatform.html ... dh_auto_install cd obj-x86_64-linux-gnu && make -j1 install DESTDIR=/build/1st/kodiplatform-17.1.0/debian/tmp AM_UPDATE_INFO_DIR=no make[1]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' /usr/bin/cmake -H/build/1st/kodiplatform-17.1.0 -B/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu --check-build-system CMakeFiles/Makefile.cmake 0 /usr/bin/cmake -E cmake_progress_start /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/progress.marks make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make -f CMakeFiles/kodiplatform.dir/build.make CMakeFiles/kodiplatform.dir/depend make[3]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' cd /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /build/1st/kodiplatform-17.1.0 /build/1st/kodiplatform-17.1.0 /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles/kodiplatform.dir/DependInfo.cmake --color= make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make -f CMakeFiles/kodiplatform.dir/build.make CMakeFiles/kodiplatform.dir/build make[3]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make[3]: Nothing to be done for 'CMakeFiles/kodiplatform.dir/build'. make[3]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' [100%] Built target kodiplatform make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' /usr/bin/cmake -E cmake_progress_start /build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/CMakeFiles 0 make -f CMakeFiles/Makefile2 preinstall make[2]: Entering directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' make[2]: Nothing to be done for 'preinstall'. make[2]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' Install the project... /usr/bin/cmake -P cmake_install.cmake -- Install configuration: "None" -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16.0.0 -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so.16 -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/libkodiplatform.so -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/usr/include/kodi/util/XMLUtils.h -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/pkgconfig/kodiplatform.pc -- Installing: /build/1st/kodiplatform-17.1.0/debian/tmp/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu/kodiplatform/kodiplatform-config.cmake make[1]: Leaving directory '/build/1st/kodiplatform-17.1.0/obj-x86_64-linux-gnu' dh_install dh_install: Cannot find (any matches for) "usr/lib/*/*.so" (tried in ., debian/tmp) dh_install: libkodiplatform-dev missing files: usr/lib/*/*.so dh_install: Cannot find (any matches for) "usr/lib/*/pkgconfig/*.pc" (tried in ., debian/tmp) dh_install: libkodiplatform-dev missing files: usr/lib/*/pkgconfig/*.pc dh_install: Cannot find (any matches for) "usr/lib/*/kodiplatform/*" (tried in ., debian/tmp) dh_install: libkodiplatform-dev missing files: usr/lib/*/kodiplatform/* dh_install: Cannot find (any matches for) "usr/lib/*/*.so.*" (tried in ., debian/tmp) dh_install: libkodiplatform16 missing files: usr/lib/*/*.so.* dh_install: missing files, aborting
Processed: Re: Bug#931309: Multiple security issues (CVE-2018-14449..14459, CVE-2018-18192..18197)
Processing commands for cont...@bugs.debian.org: > retitle 931309 libgig: Multiple security issues (CVE-2018-14449..14459, > CVE-2018-18192..18197) Bug #931309 [libgig] Multiple security issues (CVE-2018-14449..14460, CVE-2018-18192..18197) Changed Bug title to 'libgig: Multiple security issues (CVE-2018-14449..14459, CVE-2018-18192..18197)' from 'Multiple security issues (CVE-2018-14449..14460, CVE-2018-18192..18197)'. > thanks Stopping processing here. Please contact me if you need assistance. -- 931309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: raising severity of GCC 9 ftbfs issues (will be raised further in July/August)
2: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925732 925733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925733 925734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925734 925735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925735 925736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925736 925737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925737 925738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925738 925739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925739 925740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925740 925742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925742 925743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925743 925744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925744 925745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925745 925746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925746 925747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925747 925748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925748 925749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925749 925751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925751 925752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925752 925753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925753 925754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925754 925755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925755 925756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925756 925757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925757 925758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925758 925759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925759 925760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925760 925761: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925761 925762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925762 925763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925763 925764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925764 925765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925765 925766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925766 925767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925767 925768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925768 925769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925769 925770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925770 925771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925771 925772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925772 925773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925773 925774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925774 925775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925775 925776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925776 925777: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925777 925778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925778 925779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925779 925780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925780 925781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925781 925782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925782 925783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925783 925784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925784 925785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925785 925786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925786 925787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925787 925788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925788 925789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925789 925790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925790 925791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925791 925792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925792 925793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925793 925794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925794 925795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925795 925796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925796 925797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925797 925798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925798 925799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925799 925800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925800 925801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925801 925802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925802 925803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925803 925804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925804 925805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925805 925806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925806 925807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925807 925809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925809 925810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925810 925811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925811 925812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925812 925813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925813 925814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925814 925816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925816 925818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925818 925819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925819 925820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925820 925822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925822 925823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925823 925824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925824 925825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925825 925826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925826 925827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925827 925828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925828 925829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925829 925830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925830 925831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925831 925832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925832 925833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925833 925834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925834 925835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925835 925836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925836 925837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925837 925838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925838 925839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925839 925840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925840 925841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925841 925842: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925842 925843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925843 925844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925844 925845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925845 925846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925846 925847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925847 925848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925848 925849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925849 925850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925850 925851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925851 925852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925852 925853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925853 925854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925854 925855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925855 925856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925856 925857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925857 925859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925859 925862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925862 925863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925863 925864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925864 925866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925866 925867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925867 925869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#925651: marked as done (cheesecutter: ftbfs with GCC-9)
Your message dated Thu, 11 Jul 2019 11:18:54 + with message-id and subject line Bug#925651: fixed in cheesecutter 2.9+git20190611-1 has caused the Debian Bug report #925651, regarding cheesecutter: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 925651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cheesecutter Version: 2.9+git20181112-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-9 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc9-20190321/cheesecutter_2.9+git20181112-2_unstable_gcc9.log The last lines of the build log are at the end of this report. To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-9/porting_to.html GCC 9 also passes the linker option --as-needed by default; typical build issues are passing libraries before object files to the linker, or underlinking of convenience libraries built from the same source. [...] Check disk space Sufficient free space for build User Environment APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/sbuild-nonexistent LANG=en_US.UTF-8 LC_ALL=POSIX LOGNAME=user42 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-a6c5ac55-420f-4080-9dd7-81cc08e908e6 SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - dpkg-buildpackage: info: source package cheesecutter dpkg-buildpackage: info: source version 2.9+git20181112-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Gürkan Myczko dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh_auto_clean make -j4 clean make[1]: Entering directory '/<>/cheesecutter-2.9+git20181112' rm -f *.o *~ resid/*.o resid-fp/*.o ccutter ct2util \ src/c64/player.bin src/derelict/util/compat.o src/derelict/util/sharedlib.o src/derelict/util/exception.o src/derelict/util/loader.o src/derelict/util/wintypes.o src/derelict/util/xtypes.o src/derelict/sdl/sdl.o src/derelict/sdl/net.o src/derelict/sdl/ttf.o src/derelict/sdl/mixer.o src/derelict/sdl/image.o src/derelict/sdl/sdlfuncs.o src/derelict/sdl/sdltypes.o src/derelict/sdl/macinit/CoreFoundation.o src/derelict/sdl/macinit/DerelictSDLMacLoader.o src/derelict/sdl/macinit/ID.o src/derelict/sdl/macinit/MacTypes.o src/derelict/sdl/macinit/NSApplication.o src/derelict/sdl/macinit/NSArray.o src/derelict/sdl/macinit/NSAutoreleasePool.o src/derelict/sdl/macinit/NSDictionary.o src/derelict/sdl/macinit/NSEnumerator.o src/derelict/sdl/macinit/NSEvent.o src/derelict/sdl/macinit/NSGeometry.o src/derelict/sdl/macinit/NSMenu.o src/derelict/sdl/macinit/NSMenuItem.o src/derelict/sdl/macinit/NSNotification.o src/derelict/sdl/macinit/NSObject.o src/derelict/sdl/macinit/NSProcessInfo.o src/derelict/sdl/macinit/NSString.o src/derelict/sdl/macinit/NSZone.o src/derelict/sdl/macinit/runtime.o src/derelict/sdl/macinit/SDLMain.o src/derelict/sdl/macinit/selectors.o src/derelict/sdl/macinit/string.o src/audio/audio.o src/audio/player.o src/audio/timer.o src/audio/callback.o src/ct/purge.o src/ct/base.o src/ct/dump.o src/com/fb.o src/com/cpu.o src/com/kbd.o src/com/session.o src/com/util.o src/main.o src/ui/tables.o src/ui/dialogs.o src/ui/ui.o src/ui/input.o src/ui/help.o src/seq/seqtable.o src/seq/tracktable.o src/seq/trackmap.o src/seq
Processed: Re: Your mail
Processing control commands: > tags -1 + upstream patch Bug #931810 [aeolus] (no subject) Added tag(s) upstream and patch. -- 931810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#931810
Processing commands for cont...@bugs.debian.org: > retitle 931810 aeolus: segfault on startup Bug #931810 [aeolus] (no subject) Changed Bug title to 'aeolus: segfault on startup' from '(no subject)'. > End of message, stopping processing here. Please contact me if you need assistance. -- 931810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931810 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#930391 marked as pending in frei0r
Processing control commands: > tag -1 pending Bug #930391 [frei0r-plugins-dev] frei0r-plugins-dev: Missing header files in /usr/include directory Added tag(s) pending. -- 930391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#930391: marked as done (frei0r-plugins-dev: Missing header files in /usr/include directory)
Your message dated Tue, 16 Jul 2019 13:18:56 + with message-id and subject line Bug#930391: fixed in frei0r 1.6.1-3 has caused the Debian Bug report #930391, regarding frei0r-plugins-dev: Missing header files in /usr/include directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 930391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: frei0r-plugins-dev Version: 1.6.1-2 Severity: important Dear Maintainer, I was trying to build a frei0r plugin I wrote in C++. But the compilation failed because the header file frei0r.hpp was not present in /usr/include The unique present header file is frei0r.h which allows to build C plugins only, and with limited functionality. Note : The problem is also present in upstream distribution. Please find a patch below, which may allow to install these headers. Regards, diff -ru a/CMakeLists.txt b/CMakeLists.txt --- a/CMakeLists.txt2017-05-31 07:57:25.0 +0200 +++ b/CMakeLists.txt2019-06-11 21:22:25.637472171 +0200 @@ -46,7 +46,10 @@ INCLUDE( cmake/modules/TargetDistclean.cmake OPTIONAL) # See this thread for a ridiculous discussion about the simple question how to install a header file with CMake: http://www.cmake.org/pipermail/cmake/2009-October/032874.html -install (DIRECTORY include DESTINATION . FILES_MATCHING PATTERN "frei0r.h" PATTERN "msvc" EXCLUDE) +install (DIRECTORY include DESTINATION . FILES_MATCHING +PATTERN "frei0r*.h" +PATTERN "frei0r*.hpp" +PATTERN "msvc" EXCLUDE) add_subdirectory (doc) add_subdirectory (src) -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/6 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information --- End Message --- --- Begin Message --- Source: frei0r Source-Version: 1.6.1-3 We believe that the bug you reported is fixed in the latest version of frei0r, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 930...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated frei0r package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 16 Jul 2019 14:49:24 +0200 Source: frei0r Architecture: source Version: 1.6.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 930391 Changes: frei0r (1.6.1-3) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ IOhannes m zmölnig (Debian/GNU) ] * frei0r-plugins-dev * Install frei0r.hpp (Closes: #930391) * Make frei0r-plugins-dev arch:all * Install arch-independent pkg-config snippets into /usr/share/ * frei0r-plugins-doc * Move html-documentation from /u/s/frei0r/ to /usr/share/doc/frei0r-plugin-dev/ * Removed trailing whitespace from d/changelog * Drop obsolete d/source/local-options * Bump standards-version to 4.4.0 * Don't require "root" powers for building the package Checksums-Sha1: c9a00f240a4839374648d8acadfbb92428654b9b 2337 frei0r_1.6.1-3.dsc 21467129307e4b87f39a0fb439afa7e41db564e0 15892 frei0r_1.6.1-3.debian.tar.xz Checksums-Sha256: 4466184b8c4bd88ec566864196b0ffaf168518f4e006483c28e42cf7404b8c80 2337 frei0r_1.6.1-3.dsc f67ab643258fd997dfb1e68994aba59f679f2e41f52d1e12af95399cae02ef44 15892 frei0r_1.6.1-3.debian.tar.xz Files: eb9416a1e9d62e710fa8ed3b30026ca4 2337 video optional frei0r_1.6.1-3.dsc 1ac9cd57e8bd5b83300ce1662a053183 1
Processed: Removing libgtk2-perl from testing
Processing control commands: > severity -1 serious Bug #912882 [src:gmusicbrowser] gmusicbrowser: Depends on libgtk2-perl, that won't be part of Bullseye Severity set to 'serious' from 'normal' -- 912882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#922817 marked as pending in libvpx
Processing control commands: > tag -1 pending Bug #922817 [libvpx] neon library variant no longer installed, ARM performance regression Added tag(s) pending. -- 922817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#890050 marked as pending in zynaddsubfx
Processing control commands: > tag -1 pending Bug #890050 [zynaddsubfx] zynaddsubfx: German L10n missing in desktop files Added tag(s) pending. -- 890050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: found 912877 in 0.4-2.2, tagging 912877, tagging 932386, found 932585 in 0.8.0~dev650-1 ...
se migrate to emacs25 soon
Added tag(s) bullseye and sid.
> found 922434 3.0.15-4.2
Bug #922434 [sass-elisp] sass-elisp: Should depend on generic emacs
Marked as found in versions sass-elisp/3.0.15-4.2.
> tags 922434 + sid bullseye
Bug #922434 [sass-elisp] sass-elisp: Should depend on generic emacs
Added tag(s) sid and bullseye.
> found 933321 0.992-6
Bug #933321 {Done: gregor herrmann } [src:sepia] sepia:
please update emacs dependency to versionless variant
Marked as found in versions sepia/0.992-6.
> tags 933321 + sid bullseye patch
Bug #933321 {Done: gregor herrmann } [src:sepia] sepia:
please update emacs dependency to versionless variant
Added tag(s) patch, bullseye, and sid.
> found 912890 0.1-2
Bug #912890 [src:pidgin-openpgp] pidgin-openpgp: Depends on libgtk2-perl, that
won't be part of Bullseye
Marked as found in versions pidgin-openpgp/0.1-2.
> tags 912890 + sid bullseye
Bug #912890 [src:pidgin-openpgp] pidgin-openpgp: Depends on libgtk2-perl, that
won't be part of Bullseye
Added tag(s) sid and bullseye.
> found 912894 1.3.0-0.1
Bug #912894 [src:odot] odot: Depends on libgtk2-perl, that won't be part of
Bullseye
Marked as found in versions odot/1.3.0-0.1.
> tags 912894 + sid bullseye
Bug #912894 [src:odot] odot: Depends on libgtk2-perl, that won't be part of
Bullseye
Added tag(s) bullseye and sid.
> tags 932865 + sid bullseye
Bug #932865 [python-qrtools] python-qrtools: not installable: depends on
python2 version of zbar
Added tag(s) bullseye and sid.
> tags 926521 + sid bullseye
Bug #926521 [obdgpslogger] libgps changed API of gps_read
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
852105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852105
904557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904557
904562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904562
912860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912860
912870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912870
912874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912874
912877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912877
912879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912879
912880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912880
912882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912882
912888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912888
912889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912889
912890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912890
912894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912894
914783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914783
922434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922434
926521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926521
926522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926522
926528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926528
926534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926534
927762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927762
930398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930398
930399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930399
931034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931034
932020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932020
932156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932156
932320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932320
932386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932386
932542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932542
932543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932543
932584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932584
932585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932585
932827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932827
932865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932865
932938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932938
932981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932981
932983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932983
932985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932985
933066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933066
933077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933077
933128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933128
933130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933130
933146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933146
933185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933185
933317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933317
933319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933319
933321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933321
933322: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933322
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: block 894663 with 933407 933408 933411 933412 933413 933414 933415 933416 933417 933418 933420 933421 933422 933423 933424 933425 933426 933427 933429 933430 933431 933432 933433 933434 933
Processing commands for cont...@bugs.debian.org: > block 894663 with 933407 933408 933411 933412 933413 933414 933415 933416 > 933417 933418 933420 933421 933422 933423 933424 933425 933426 933427 933429 > 933430 933431 933432 933433 933434 933435 933436 933438 933439 933440 933441 > 933442 933443 933444 933445 933446 933447 933448 933450 933451 933452 933454 > 933455 933456 933457 933458 933459 933460 933461 933462 933463 933465 933466 > 933467 933468 933469 933470 933471 933472 933473 933474 933475 933476 933477 > 933478 933479 933480 933409 933428 933453 933464 Bug #894663 [release.debian.org] transition: wxwidgets3.0 894663 was blocked by: 895134 933419 894663 was not blocking any bugs. Added blocking bug(s) of 894663: 933408, 933463, 933446, 933427, 933469, 933407, 933456, 933418, 933479, 933434, 933440, 933420, 933429, 933473, 933448, 933416, 933480, 933435, 933467, 933436, 933452, 933470, 933411, 933475, 933428, 933450, 933465, 933471, 933426, 933414, 933468, 933455, 933444, 933466, 933458, 933421, 933472, 933425, 933438, 933439, 933461, 933424, 933474, 933443, 933431, 933451, 933445, 933477, 933422, 933442, 933441, 933423, 933417, 933433, 933453, 933478, 933464, 933460, 933462, 933412, 933430, 933415, 933476, 933432, 933447, 933459, 933409, 933457, 933413, and 933454 > thanks Stopping processing here. Please contact me if you need assistance. -- 894663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#922817: marked as done (neon library variant no longer installed, ARM performance regression)
Your message dated Thu, 01 Aug 2019 10:00:13 +
with message-id
and subject line Bug#922817: fixed in libvpx 1.8.1-1
has caused the Debian Bug report #922817,
regarding neon library variant no longer installed, ARM performance regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
922817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvpx
Version: 1.6.1-3+deb9u1
In Debian Jessie, ARM VP9 decoding was working well on many platforms
thanks to the neon library additionaly provided at
/usr/lib/arm-linux-gnueabihf/vfp/neon/libvpx.so.1.
However, as of Debian Stretch (and also in Debian Buster), the neon
library variant is no longer installed by the package, so the system
falls back on the "generic" version, where the decoding performance is
very noticably worse. On Endless Mini (Amlogic S805) this makes most
videos unwatchable due to excessively low framerate.
The bug is that the entry in libvpx{4,5}.install for the neon variant
ends with the [arm] arch selector, but this should actually be [armhf
armel] in order for the file to be included in the installation.
--- End Message ---
--- Begin Message ---
Source: libvpx
Source-Version: 1.8.1-1
We believe that the bug you reported is fixed in the latest version of
libvpx, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 922...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ondřej Nový (supplier of updated libvpx package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 17 Jul 2019 00:05:27 +0200
Source: libvpx
Binary: libvpx-dev libvpx-doc libvpx6 libvpx6-dbgsym vpx-tools vpx-tools-dbgsym
Architecture: source amd64 all
Version: 1.8.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Ondřej Nový
Description:
libvpx-dev - VP8 and VP9 video codec (development files)
libvpx-doc - VP8 and VP9 video codec (API documentation)
libvpx6- VP8 and VP9 video codec (shared library)
vpx-tools - VP8 and VP9 video codec encoding/decoding tools
Closes: 922817
Changes:
libvpx (1.8.1-1) experimental; urgency=medium
.
* New upstream release
- This release is ABI incompatible
* Bump debhelper compat level to 12 and use debhelper-compat
* Bump Standards-Version to 4.4.0 (no changes needed)
* d/changelog, d/control: Remove trailing empty line at the end of file
* Fix installation of neon version of library on ARM (Closes: #922817)
Checksums-Sha1:
97af34a7a871f009a391b1d42a3dcbd5c7ae2663 2247 libvpx_1.8.1-1.dsc
6c9a55e1f92d7301383f387486bb574f22faf855 2922587 libvpx_1.8.1.orig.tar.gz
2e16745008835e47b6529518ba96992a2c108f47 11524 libvpx_1.8.1-1.debian.tar.xz
ff73f055477ae0a6e21b1738803c0d70a7a833bf 992068 libvpx-dev_1.8.1-1_amd64.deb
8c91207b8cd14ab68813ace36ab7cab5b26b8c92 290432 libvpx-doc_1.8.1-1_all.deb
ff768ae36517db0ff49efcfe7a66f69964202a53 3732780
libvpx6-dbgsym_1.8.1-1_amd64.deb
f682e981a7c1e68500c95f7865323aebb068692b 859484 libvpx6_1.8.1-1_amd64.deb
1ab38e4cf0c6863d951119128bd994733621035c 6891 libvpx_1.8.1-1_amd64.buildinfo
49f13ce01d996bb8ac786a7e3bacef00d6adca77 1289464
vpx-tools-dbgsym_1.8.1-1_amd64.deb
45c63e63498d07c81d8f4d8239acc224edcdff00 275952 vpx-tools_1.8.1-1_amd64.deb
Checksums-Sha256:
174790354038d779245c3a309a3274e95afd38c1c75852f06b5abbf926bcb096 2247
libvpx_1.8.1-1.dsc
df19b8f24758e90640e1ab228ab4a4676ec3df19d23e4593375e6f3847dee03e 2922587
libvpx_1.8.1.orig.tar.gz
e1853baf9c1a7abc58fe100aec3c0cfea5da109272fc91e895b9f87b51ba369a 11524
libvpx_1.8.1-1.debian.tar.xz
1bb4b7420a48b27848ca369bf00e839b6f2b7de8fadeb5a17c1fed1dc5456393 992068
libvpx-dev_1.8.1-1_amd64.deb
374f64fa944162c41ac75aa6e3dbbb0c863fa2b9f54baede128ec78dd1129811 290432
libvpx-doc_1.8.1-1_all.deb
046b547c32add18ebfa07d251acd0d37fccb8e73f1afe4223a86953b4d07f884 3732780
libvpx6-dbgsym_1.8.1-1_amd64.deb
7ab6f32a8e7827c988bc39cc908d0c074190cdcf6e5870d4aba9a597a5d811e0 859484
libvpx6_1.8.1-1_amd64.deb
03eece4e1f2ed6859733d512b61860351ca32604f134aa1accdd8ae7fa8ae5ba 6891
libvpx_1.8.1-1_amd64
Bug#890050: marked as done (zynaddsubfx: German L10n missing in desktop files)
Your message dated Thu, 01 Aug 2019 11:00:51 + with message-id and subject line Bug#890050: fixed in zynaddsubfx 3.0.5-1 has caused the Debian Bug report #890050, regarding zynaddsubfx: German L10n missing in desktop files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 890050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zynaddsubfx Version: 3.0.1-1 Severity: minor Tags: patch, l10n The zynaddsubfx desktop files are missing a German translation. This is user visible e.g. in the KDE Plasma start menu. The attached patch fixes this issue. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zynaddsubfx depends on: ii libasound2 1.1.3-5 ii libc6 2.24-11+deb9u1 ii libfftw3-double3 3.3.5-3 ii libfltk-images1.3 1.3.4-4 ii libfltk1.3 1.3.4-4 ii libgcc1 1:6.3.0-18 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20150825git1ed50c92~dfsg-5 ii liblo7 0.28-5+b2 ii libmxml1 2.10-1+b1 ii libstdc++6 6.3.0-18 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxpm4 1:3.5.12-1 ii zlib1g 1:1.2.8.dfsg-5 ii zynaddsubfx-data 3.0.1-1 zynaddsubfx recommends no packages. zynaddsubfx suggests no packages. -- no debconf information >From 0c96bb0edecb048910427fbd9f53d798245c106a Mon Sep 17 00:00:00 2001 From: Ronny Standtke Date: Sat, 10 Feb 2018 15:24:08 +0100 Subject: [PATCH] added German translation to desktop files --- zynaddsubfx-alsa.desktop | 1 + zynaddsubfx-jack.desktop | 1 + zynaddsubfx-oss.desktop | 1 + 3 files changed, 3 insertions(+) diff --git a/zynaddsubfx-alsa.desktop b/zynaddsubfx-alsa.desktop index 9c20ee4..84a0e71 100644 --- a/zynaddsubfx-alsa.desktop +++ b/zynaddsubfx-alsa.desktop @@ -1,6 +1,7 @@ [Desktop Entry] Name=ZynAddSubFX - Alsa Comment=A powerful realtime software synthesizer +Comment[de]=Ein mächtiger Echtzeit-Software-Synthesizer Comment[fr]=Un synthétiseur logiciel temps-réel puissant Comment[pl]=Funkcjonalny syntezator wirtualny czasu rzeczywistego Keywords=audio;sound;alsa;midi;synth;synthesizer; diff --git a/zynaddsubfx-jack.desktop b/zynaddsubfx-jack.desktop index aa7497c..a6a0cf1 100644 --- a/zynaddsubfx-jack.desktop +++ b/zynaddsubfx-jack.desktop @@ -1,6 +1,7 @@ [Desktop Entry] Name=ZynAddSubFX - Jack Comment=A powerful realtime software synthesizer +Comment[de]=Ein mächtiger Echtzeit-Software-Synthesizer Comment[fr]=Un synthétiseur logiciel temps-réel puissant Comment[pl]=Funkcjonalny syntezator wirtualny czasu rzeczywistego Keywords=audio;sound;jack;midi;synth;synthesizer; diff --git a/zynaddsubfx-oss.desktop b/zynaddsubfx-oss.desktop index 85cba25..ec69e08 100644 --- a/zynaddsubfx-oss.desktop +++ b/zynaddsubfx-oss.desktop @@ -1,6 +1,7 @@ [Desktop Entry] Name=ZynAddSubFX - OSS Comment=A powerful realtime software synthesizer +Comment[de]=Ein mächtiger Echtzeit-Software-Synthesizer Comment[fr]=Un synthétiseur logiciel temps-réel puissant Comment[pl]=Funkcjonalny syntezator wirtualny czasu rzeczywistego Keywords=audio;sound;alsa;midi;synth;synthesizer; -- 2.11.0 --- End Message --- --- Begin Message --- Source: zynaddsubfx Source-Version: 3.0.5-1 We believe that the bug you reported is fixed in the latest version of zynaddsubfx, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 890...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated zynaddsubfx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the
Bug#892969: marked as done (zynaddsubfx: move out of asciidoc)
Your message dated Thu, 01 Aug 2019 11:00:51 + with message-id and subject line Bug#892969: fixed in zynaddsubfx 3.0.5-1 has caused the Debian Bug report #892969, regarding zynaddsubfx: move out of asciidoc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 892969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zynaddsubfx Version: 3.0.3-1 Usertags: asciidoc-eol Hi, As announced with asciidoc 8.6.10, asciidoc is EOL. As long as there's no python3 compatibility, all the tools using asciidoc as a dependency will be asked to move to asciidoctor or pandoc or whatever equivalent you feel the most confortable with. I already took care of the upstream part in: https://sourceforge.net/p/zynaddsubfx/code/merge-requests/6/ But asciidoc is used in debian/rules for the packaging itself so we need to move it there too. Thanks for your help, Joseph --- End Message --- --- Begin Message --- Source: zynaddsubfx Source-Version: 3.0.5-1 We believe that the bug you reported is fixed in the latest version of zynaddsubfx, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 892...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated zynaddsubfx package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 22 Jul 2019 23:33:27 +0200 Source: zynaddsubfx Binary: zynaddsubfx zynaddsubfx-data zynaddsubfx-dbgsym zynaddsubfx-dssi zynaddsubfx-dssi-dbgsym zynaddsubfx-lv2 zynaddsubfx-lv2-dbgsym zynaddsubfx-vst zynaddsubfx-vst-dbgsym Architecture: source all amd64 Version: 3.0.5-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Reiner Herrmann Description: zynaddsubfx - Realtime software synthesizer for Linux zynaddsubfx-data - Realtime software synthesizer for Linux (data) zynaddsubfx-dssi - dssi plugin of zynaddsubfx zynaddsubfx-lv2 - lv2 plugin of zynaddsubfx zynaddsubfx-vst - vst plugin of zynaddsubfx Closes: 890050 892969 Changes: zynaddsubfx (3.0.5-1) unstable; urgency=medium . * Team upload. . [ Reiner Herrmann ] * New upstream version 3.0.5. * Document new upstream copyrights. * New binary packages for lv2 and vst plugins: - zynaddsubfx-lv2 - zynaddsubfx-vst * Drop patch by explicitly listing installed files. * Mark zynaddsubfx-data as Multi-Arch: foreign. * Add German translation also to new .desktop file. * Use installed paths relative to d/tmp so that dh_missing finds them. * Mark intentionally not installed files in d/not-installed. * Add German translation to .desktop files. * Build-depend on bash-completion for finding completions path. * Build-depend on cxxtest for running unit tests. * Bump debhelper compat version to 12. * Update Standards-Version to 4.4.0. * Declare that d/rules does not require root. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field. * d/control: Set Vcs-* to salsa.debian.org. * Use debhelper-compat instead of debian/compat. . [ Joseph Herlant ] * d/control, d/rule: migrate from asciidoc/a2x to asciidoctor to generate man pages. Closes: #892969 . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org. . [ Olivier Humbert ] * Installs LV2 and VST versions. * Update control wrt: LV2 build and install. * Adds myself to d/copyright. . [ Ronny Standtke ] * Add German translation to .desktop files. Closes: #890050 . [ Mattia Rizzolo ] * Drop unused lintian overrides. Checksums-Sha1: 41673116a59e42966fcefe62bfbaa6a4827df1fb 2557 zynaddsubfx_3.0.5-1.dsc 8f4ad3cd0f26d360dd97124b2a0c7b6262853e61 8141703 zynaddsubfx_3.0.5.orig.tar.bz2 ba50cc7471a6f11267bd0d6da3bd58b699602094 8680 zynaddsubfx_3.0.5-1.debian.tar.xz a11230283af2fc4b0f7adeb8a0b64c522d97f705 3013116 zynaddsubfx-data_3.0.5-1_all.deb 4f4c0a112457205b54de5954346e298f368d13e7 11931092 zynaddsubfx-dbgsym_3.0.5-1_amd64.deb 606ed36f0b92a3b947ddba4af4bab6f248149a5b 5003440 zynaddsubfx-dssi-dbgsym_3.0.5-1_amd6
Processed: bug 885478 is forwarded to https://github.com/wavexx/screenkey/issues/3 ...
Processing commands for cont...@bugs.debian.org: > forwarded 885478 https://github.com/wavexx/screenkey/issues/3 Bug #885478 [src:screenkey] screenkey: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://github.com/wavexx/screenkey/issues/3'. > forwarded 885302 https://github.com/dsacre/gtklick/issues/2 Bug #885302 [src:gtklick] gtklick: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://github.com/dsacre/gtklick/issues/2'. > forwarded 885294 https://github.com/gnuradio/gnuradio/issues/2478 Bug #885294 [src:gnuradio] gnuradio: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://github.com/gnuradio/gnuradio/issues/2478'. > forwarded 885880 https://github.com/doadin/deluge/milestone/1 Bug #885880 [deluge-gtk] deluge: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://github.com/doadin/deluge/milestone/1'. > forwarded 885259 https://gitlab.com/arandr/arandr/issues/32 Bug #885259 [src:arandr] arandr: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://gitlab.com/arandr/arandr/issues/32'. > forwarded 816643 https://github.com/muflone/gespeaker/issues/66 Bug #816643 [gespeaker] Missing dependency on python-dbus Set Bug forwarded-to-address to 'https://github.com/muflone/gespeaker/issues/66'. > forwarded 885364 https://github.com/xrmx/bootchart/issues/34 Bug #885364 [pybootchartgui] pybootchartgui: Depends on unmaintained pygtk Set Bug forwarded-to-address to 'https://github.com/xrmx/bootchart/issues/34'. > thanks Stopping processing here. Please contact me if you need assistance. -- 816643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816643 885259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885259 885294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885294 885302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885302 885364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885364 885478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885478 885880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#932502: marked as done (olive-editor: The olive-editor package has an unmet dependency)
Your message dated Thu, 08 Aug 2019 16:37:09 + with message-id and subject line Bug#932502: fixed in olive-editor 20190502-3 has caused the Debian Bug report #932502, regarding olive-editor: The olive-editor package has an unmet dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932502 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: olive-editor Version: 20190502-2 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After installing version 20190502-2 of the olive-editor package I found that the program failed to play the audio for any media loaded. In addition the audio level meters were missing in the program's interface. The debugging info provided from running the program indicated that there was an error with configuring the audio interface when the program started: 2019-07-19T22:56:20 [DEBUG] using qt5ct plugin 2019-07-19T22:56:20 [WARNING] libpng warning: iCCP: known incorrect sRGB profile 2019-07-19T22:56:20 [INFO] Initializing custom cursors 2019-07-19T22:56:20 [INFO] Finished initializing custom cursors 2019-07-19T22:56:20 [INFO] Initializing icons 2019-07-19T22:56:20 [INFO] Finished initializing icons 2019-07-19T22:56:20 [INFO] Initializing effects... 2019-07-19T22:56:20 [DEBUG] D-Bus global menu: no 2019-07-19T22:56:20 [WARNING] Audio format is not supported by backend, using nearest 2019-07-19T22:56:20 [WARNING] using null output device, none available 2019-07-19T22:56:20 [WARNING] Received nullptr audio device. No compatible audio output was found. 2019-07-19T22:56:20 [DEBUG] palette support is disabled 2019-07-19T22:56:20 [WARNING] libpng warning: iCCP: known incorrect sRGB profile 2019-07-19T22:56:21 [INFO] Finished initializing effects * What exactly did you do (or not do) that was effective (or ineffective)? I installed the libqt5multimedia5-plugins package which provide the multimedia plugins needed by Qt programs. * What was the outcome of this action? The program can now play the audio for loaded media files. Also the audio level meters are now visible in the program's interface. * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (200, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages olive-editor depends on: ii ffmpeg 7:4.1.3-1 ii frei0r-plugins 1.6.1-2 ii libavcodec58 7:4.1.3-1 ii libavfilter7 7:4.1.3-1 ii libavformat58 7:4.1.3-1 ii libavutil567:4.1.3-1 ii libc6 2.28-10 ii libgcc11:8.3.0-6 ii libgl1 1.1.0-1 ii libqt5core5a 5.11.3+dfsg1-1 ii libqt5gui5 5.11.3+dfsg1-1 ii libqt5multimedia5 5.11.3-2 ii libqt5network5 5.11.3+dfsg1-1 ii libqt5svg5 5.11.3-2 ii libqt5widgets5 5.11.3+dfsg1-1 ii libstdc++6 8.3.0-6 ii libswresample3 7:4.1.3-1 ii libswscale57:4.1.3-1 olive-editor recommends no packages. olive-editor suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: olive-editor Source-Version: 20190502-3 We believe that the bug you reported is fixed in the latest version of olive-editor, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated olive-editor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 13:33:55 +0200 Source: olive-editor Architecture: source Ve
Bug#926998: marked as done (protracker: FTBFS on i386: attempts to use SSE intrinsics)
Your message dated Thu, 08 Aug 2019 16:38:55 + with message-id and subject line Bug#926998: fixed in protracker 2.3d.r191-1 has caused the Debian Bug report #926998, regarding protracker: FTBFS on i386: attempts to use SSE intrinsics to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 926998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926998 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: protracker Version: 2.3d.r176-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, protracker/experimental FTBFS on i386: https://buildd.debian.org/status/fetch.php?pkg=protracker&arch=i386&ver=2.3d.r176-1&stamp=1554765850&raw=0 Compiling, please wait... gcc src/gfx/*.c src/*.c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -lSDL2 -lm -Wall -Wno-unused-result -Wc++-compat -Wshadow -Winit-self -Wextra -Wunused -Wunreachable-code -Wredundant-decls -Wswitch-default -o release/other/protracker -Wl,-z,relro -Wl,-z,now -Wl,--as-needed src/pt_audio.c: In function ‘paulaSetPeriod’: src/pt_audio.c:348:18: warning: variable ‘s’ set but not used [-Wunused-but-set-variable] scopeChannel_t *s; ^ In file included from src/pt_audio.c:27: src/pt_audio.c: In function ‘mixChannels’: src/pt_helpers.h:45:7: warning: SSE vector return without SSE enabled changes the ABI [-Wpsabi] i = _mm_cvttsd_si32(_mm_load_sd(&d)); \ ^~~~ src/pt_audio.c:540:4: note: in expansion of macro ‘double2int32_trunc’ double2int32_trunc(j, dPeakAmp); ^~ In file included from /usr/lib/gcc/i686-linux-gnu/8/include/xmmintrin.h:1252, from /usr/lib/gcc/i686-linux-gnu/8/include/immintrin.h:29, from /usr/include/SDL2/SDL_cpuinfo.h:67, from /usr/include/SDL2/SDL.h:38, from src/pt_audio.c:14: src/pt_audio.c: In function ‘processMixedSamples’: /usr/lib/gcc/i686-linux-gnu/8/include/emmintrin.h:852:1: error: inlining failed in call to always_inline ‘_mm_cvttsd_si32’: target specific option mismatch _mm_cvttsd_si32 (__m128d __A) ^~~ and so on ... Andreas --- End Message --- --- Begin Message --- Source: protracker Source-Version: 2.3d.r191-1 We believe that the bug you reported is fixed in the latest version of protracker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 926...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated protracker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Aug 2019 17:17:19 +0200 Source: protracker Architecture: source Version: 2.3d.r191-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 926998 Changes: protracker (2.3d.r191-1) unstable; urgency=medium . * New upstream version. (Closes: #926998) Checksums-Sha1: 0fb1e4b98341dad47928c684139e608af835c042 1856 protracker_2.3d.r191-1.dsc d8f2fee66df13584310f63a3225b72048e2f164c 387460 protracker_2.3d.r191.orig.tar.gz 917a80d1e260c6d7973bda9cb2118b30490325f3 6048 protracker_2.3d.r191-1.debian.tar.xz f08f57e3be6087bbd01733136417d34f83daff18 5516 protracker_2.3d.r191-1_source.buildinfo Checksums-Sha256: 8c8e91985af0c549fdbb2c0cb83e0c6a024b2dd9d90e27eb40eb9314f8142975 1856 protracker_2.3d.r191-1.dsc 7b4dec67b3963d8d7f6e563a7102381039d5c017eb7018fdff31cad4b5b0cb1f 387460 protracker_2.3d.r191.orig.tar.gz 7cade457dd8521e32ccc02f278faf94a4a8827acde3d5ea73087c79310d63b33 6048 protracker_2.3d.r191-1.debian.tar.xz 97253f7289cd095e89af6c903b4eb2dbcd1ecf1190d0df5b5a0f841dac287430 5516 protracker_2.3d.r191-1_source.buildinfo Files: 024b4370c7f429c42fe7729e6421451c 1856 sound optional protracker_2.3d.r191-1.dsc 0871470089e8d2ec0354e72b8585e091 387460 sound optional protracker_2.3d.r191.orig.tar.gz a6bbfe89cf83bc8d2e2aa087820fe4ce 6048 sound optional protracker_2.3d.r191-1.debian.tar.xz f49c7cfd2d72c9f04
Bug#933808: marked as done (schism: CVE-2019-14524)
Your message dated Thu, 08 Aug 2019 16:39:51 + with message-id and subject line Bug#933808: fixed in schism 2:20190805-1 has caused the Debian Bug report #933808, regarding schism: CVE-2019-14524 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: schism Version: 2:20190722-1 Severity: important Tags: security upstream Forwarded: https://github.com/schismtracker/schismtracker/issues/201 Hi, The following vulnerability was published for schism. CVE-2019-14524[0]: | An issue was discovered in Schism Tracker through 20190722. There is a | heap-based buffer overflow via a large number of song patterns in | fmt_mtm_load_song in fmt/mtm.c, a different vulnerability than | CVE-2019-14465. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-14524 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14524 [1] https://github.com/schismtracker/schismtracker/issues/201 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: schism Source-Version: 2:20190805-1 We believe that the bug you reported is fixed in the latest version of schism, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated schism package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Aug 2019 11:33:06 +0200 Source: schism Architecture: source Version: 2:20190805-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 933807 933808 933809 Changes: schism (2:20190805-1) unstable; urgency=medium . * New upstream version. (Closes: #933807, #933808, #933809) - fmt_mtm_load_song in fmt/mtm.c (CVE-2019-14465) - heap-based buffer overflow via a large number of song patterns in fmt_mtm_load_song in fmt/mtm.c (CVE-2019-14524) - integer underflow via a large plen in fmt_okt_load_song in the Amiga Oktalyzer parser in fmt/okt.c (CVE-2019-14523) Checksums-Sha1: 6e09e8ea11f4fd5f41b196f08ea27ec0659aa2e6 2023 schism_20190805-1.dsc 87133ebe20689be67284ffb574fc5d845caa1b15 1315705 schism_20190805.orig.tar.gz e4d59a6df2f0b02a15edf38f2e2abc7d51bc7690 4076 schism_20190805-1.debian.tar.xz ddf093acd30715c3028777ab3192866d59d16103 6436 schism_20190805-1_source.buildinfo Checksums-Sha256: fdb651b2217d95f16dd7c3aa5d55df00e134d2ffb05f28d0f779a69075a37878 2023 schism_20190805-1.dsc 3f80919c01e35ee55a749e7a1ebc5d510896a3322e0fc8b249ac34def5e69ec6 1315705 schism_20190805.orig.tar.gz 36c65e05d65442eb6d16ecd4f18d17502b02fe330a1cc740b274e940f74c0a72 4076 schism_20190805-1.debian.tar.xz 1b2d432cedb9947bf4efc59f3810b12e296348d922c357040d2b8aaa6585880f 6436 schism_20190805-1_source.buildinfo Files: 64b8ce073bd41fb3a4af8cceaeede1fb 2023 sound optional schism_20190805-1.dsc f8c1b188c7ebf2f9fdd3179ab7ecc2cc 1315705 sound optional schism_20190805.orig.tar.gz bc8bdf7a8565b7c84ee8a6911f732a47 4076 sound optional schism_20190805-1.debian.tar.xz 3a2dac2b034b8f1345a25e7079365b61 6436 sound optional schism_20190805-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl1MSToACgkQweDZLphv fH4tHBAA4UzOWZ3iYMj2Kr7o4zNU86Jcn/CAmYZ0VO2Zo4jojHqeiuw5Z7Q9X3MC Z+cIv5NyHiLl7bUbM7+Bi43uFZBw3kMZ/ehkHHyjILRrUh9LyxaEOzxy68iqyf/1 ORL1OBMdKxYBwa9TN9nJ6lu8KrvxygxoG+Uo6E33AqLMwKogIaiBOZ2ujp/ZR//i 3AVr4RbbQonFXvYst7NhfjfxbD8x946Gf0y9YXLzcQ5obP17UG9SaV8nHI/r54bE NoK/BckKcLojJzQNOqCwnnFR/WimYycYJMksK4vZixrVs4yKKqWf9C9CKXZZS7UA EFduZwxw+tgwi/7JUfs5hTEj9zLXbBLE/0lbFKCBV/ZinZxkW3AdH06QKFgxrBEw E9t+C3SBMfRC54orej9laMrf6Iq0yvzHugfgdqdUBLSLUzEQ6Bdv1tH9BR958csm XcfZtk0pku7dots4rynngLkUum/W7FdcaRDUQX0uaCOHudsv8HU6+1ZuLNlaI3tU tqq1vh/S3GLmEO5LvpSYUvNIzrn2Bahzed9hc3oskzxxbSSZ42evJl6wnnklYsXF oDTg
Bug#933809: marked as done (schism: CVE-2019-14523)
Your message dated Thu, 08 Aug 2019 16:39:51 + with message-id and subject line Bug#933809: fixed in schism 2:20190805-1 has caused the Debian Bug report #933809, regarding schism: CVE-2019-14523 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: schism Version: 2:20190722-1 Severity: important Tags: security upstream Forwarded: https://github.com/schismtracker/schismtracker/issues/202 Hi, The following vulnerability was published for schism. CVE-2019-14523[0]: | An issue was discovered in Schism Tracker through 20190722. There is | an integer underflow via a large plen in fmt_okt_load_song in the | Amiga Oktalyzer parser in fmt/okt.c. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-14523 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14523 [1] https://github.com/schismtracker/schismtracker/issues/202 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: schism Source-Version: 2:20190805-1 We believe that the bug you reported is fixed in the latest version of schism, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated schism package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Aug 2019 11:33:06 +0200 Source: schism Architecture: source Version: 2:20190805-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 933807 933808 933809 Changes: schism (2:20190805-1) unstable; urgency=medium . * New upstream version. (Closes: #933807, #933808, #933809) - fmt_mtm_load_song in fmt/mtm.c (CVE-2019-14465) - heap-based buffer overflow via a large number of song patterns in fmt_mtm_load_song in fmt/mtm.c (CVE-2019-14524) - integer underflow via a large plen in fmt_okt_load_song in the Amiga Oktalyzer parser in fmt/okt.c (CVE-2019-14523) Checksums-Sha1: 6e09e8ea11f4fd5f41b196f08ea27ec0659aa2e6 2023 schism_20190805-1.dsc 87133ebe20689be67284ffb574fc5d845caa1b15 1315705 schism_20190805.orig.tar.gz e4d59a6df2f0b02a15edf38f2e2abc7d51bc7690 4076 schism_20190805-1.debian.tar.xz ddf093acd30715c3028777ab3192866d59d16103 6436 schism_20190805-1_source.buildinfo Checksums-Sha256: fdb651b2217d95f16dd7c3aa5d55df00e134d2ffb05f28d0f779a69075a37878 2023 schism_20190805-1.dsc 3f80919c01e35ee55a749e7a1ebc5d510896a3322e0fc8b249ac34def5e69ec6 1315705 schism_20190805.orig.tar.gz 36c65e05d65442eb6d16ecd4f18d17502b02fe330a1cc740b274e940f74c0a72 4076 schism_20190805-1.debian.tar.xz 1b2d432cedb9947bf4efc59f3810b12e296348d922c357040d2b8aaa6585880f 6436 schism_20190805-1_source.buildinfo Files: 64b8ce073bd41fb3a4af8cceaeede1fb 2023 sound optional schism_20190805-1.dsc f8c1b188c7ebf2f9fdd3179ab7ecc2cc 1315705 sound optional schism_20190805.orig.tar.gz bc8bdf7a8565b7c84ee8a6911f732a47 4076 sound optional schism_20190805-1.debian.tar.xz 3a2dac2b034b8f1345a25e7079365b61 6436 sound optional schism_20190805-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl1MSToACgkQweDZLphv fH4tHBAA4UzOWZ3iYMj2Kr7o4zNU86Jcn/CAmYZ0VO2Zo4jojHqeiuw5Z7Q9X3MC Z+cIv5NyHiLl7bUbM7+Bi43uFZBw3kMZ/ehkHHyjILRrUh9LyxaEOzxy68iqyf/1 ORL1OBMdKxYBwa9TN9nJ6lu8KrvxygxoG+Uo6E33AqLMwKogIaiBOZ2ujp/ZR//i 3AVr4RbbQonFXvYst7NhfjfxbD8x946Gf0y9YXLzcQ5obP17UG9SaV8nHI/r54bE NoK/BckKcLojJzQNOqCwnnFR/WimYycYJMksK4vZixrVs4yKKqWf9C9CKXZZS7UA EFduZwxw+tgwi/7JUfs5hTEj9zLXbBLE/0lbFKCBV/ZinZxkW3AdH06QKFgxrBEw E9t+C3SBMfRC54orej9laMrf6Iq0yvzHugfgdqdUBLSLUzEQ6Bdv1tH9BR958csm XcfZtk0pku7dots4rynngLkUum/W7FdcaRDUQX0uaCOHudsv8HU6+1ZuLNlaI3tU tqq1vh/S3GLmEO5LvpSYUvNIzrn2Bahzed9hc3oskzxxbSSZ42evJl6wnnklYsXF oDTg
Bug#933807: marked as done (schism: CVE-2019-14465)
Your message dated Thu, 08 Aug 2019 16:39:51 + with message-id and subject line Bug#933807: fixed in schism 2:20190805-1 has caused the Debian Bug report #933807, regarding schism: CVE-2019-14465 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 933807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933807 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: schism Version: 2:20190722-1 Severity: important Tags: security upstream Forwarded: https://github.com/schismtracker/schismtracker/issues/198 Hi, The following vulnerability was published for schism. CVE-2019-14465[0]: | fmt_mtm_load_song in fmt/mtm.c in Schism Tracker 20190722 has a heap- | based buffer overflow. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-14465 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14465 [1] https://github.com/schismtracker/schismtracker/issues/198 [2] https://github.com/schismtracker/schismtracker/commit/b78e8d32883f8a865035436af4fa6d541b6ebb42 Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: schism Source-Version: 2:20190805-1 We believe that the bug you reported is fixed in the latest version of schism, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 933...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated schism package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Aug 2019 11:33:06 +0200 Source: schism Architecture: source Version: 2:20190805-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 933807 933808 933809 Changes: schism (2:20190805-1) unstable; urgency=medium . * New upstream version. (Closes: #933807, #933808, #933809) - fmt_mtm_load_song in fmt/mtm.c (CVE-2019-14465) - heap-based buffer overflow via a large number of song patterns in fmt_mtm_load_song in fmt/mtm.c (CVE-2019-14524) - integer underflow via a large plen in fmt_okt_load_song in the Amiga Oktalyzer parser in fmt/okt.c (CVE-2019-14523) Checksums-Sha1: 6e09e8ea11f4fd5f41b196f08ea27ec0659aa2e6 2023 schism_20190805-1.dsc 87133ebe20689be67284ffb574fc5d845caa1b15 1315705 schism_20190805.orig.tar.gz e4d59a6df2f0b02a15edf38f2e2abc7d51bc7690 4076 schism_20190805-1.debian.tar.xz ddf093acd30715c3028777ab3192866d59d16103 6436 schism_20190805-1_source.buildinfo Checksums-Sha256: fdb651b2217d95f16dd7c3aa5d55df00e134d2ffb05f28d0f779a69075a37878 2023 schism_20190805-1.dsc 3f80919c01e35ee55a749e7a1ebc5d510896a3322e0fc8b249ac34def5e69ec6 1315705 schism_20190805.orig.tar.gz 36c65e05d65442eb6d16ecd4f18d17502b02fe330a1cc740b274e940f74c0a72 4076 schism_20190805-1.debian.tar.xz 1b2d432cedb9947bf4efc59f3810b12e296348d922c357040d2b8aaa6585880f 6436 schism_20190805-1_source.buildinfo Files: 64b8ce073bd41fb3a4af8cceaeede1fb 2023 sound optional schism_20190805-1.dsc f8c1b188c7ebf2f9fdd3179ab7ecc2cc 1315705 sound optional schism_20190805.orig.tar.gz bc8bdf7a8565b7c84ee8a6911f732a47 4076 sound optional schism_20190805-1.debian.tar.xz 3a2dac2b034b8f1345a25e7079365b61 6436 sound optional schism_20190805-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl1MSToACgkQweDZLphv fH4tHBAA4UzOWZ3iYMj2Kr7o4zNU86Jcn/CAmYZ0VO2Zo4jojHqeiuw5Z7Q9X3MC Z+cIv5NyHiLl7bUbM7+Bi43uFZBw3kMZ/ehkHHyjILRrUh9LyxaEOzxy68iqyf/1 ORL1OBMdKxYBwa9TN9nJ6lu8KrvxygxoG+Uo6E33AqLMwKogIaiBOZ2ujp/ZR//i 3AVr4RbbQonFXvYst7NhfjfxbD8x946Gf0y9YXLzcQ5obP17UG9SaV8nHI/r54bE NoK/BckKcLojJzQNOqCwnnFR/WimYycYJMksK4vZixrVs4yKKqWf9C9CKXZZS7UA EFduZwxw+tgwi/7JUfs5hTEj9zLXbBLE/0lbFKCBV/ZinZxkW3AdH06QKFgxrBEw E9t+C3SBMfRC54orej9laMrf6Iq0yvzHugfgdqdUBLSLUzEQ6Bdv1tH9BR958csm XcfZtk0pku7dots4rynngLkUum/W7FdcaRDUQX0uaCOHudsv8HU6+1ZuLNlaI3tU tqq1vh/S3GLmEO5LvpSYUvNIzrn2Bahzed9hc3oskzxxbSSZ42evJl6wnnklYsXF oDTg
Processed: [bts-link] source package src:schism
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:schism
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was
debian-bts-l...@lists.debian.org).
> # remote status report for #933807 (http://bugs.debian.org/933807)
> # Bug title: schism: CVE-2019-14465
> # * https://github.com/schismtracker/schismtracker/issues/198
> # * remote status changed: (?) -> closed
> # * closed upstream
> tags 933807 + fixed-upstream
Bug #933807 {Done: Gürkan Myczko } [src:schism] schism:
CVE-2019-14465
Added tag(s) fixed-upstream.
> usertags 933807 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #933808 (http://bugs.debian.org/933808)
> # Bug title: schism: CVE-2019-14524
> # * https://github.com/schismtracker/schismtracker/issues/201
> # * remote status changed: (?) -> closed
> # * closed upstream
> tags 933808 + fixed-upstream
Bug #933808 {Done: Gürkan Myczko } [src:schism] schism:
CVE-2019-14524
Added tag(s) fixed-upstream.
> usertags 933808 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #933809 (http://bugs.debian.org/933809)
> # Bug title: schism: CVE-2019-14523
> # * https://github.com/schismtracker/schismtracker/issues/202
> # * remote status changed: (?) -> closed
> # * closed upstream
> tags 933809 + fixed-upstream
Bug #933809 {Done: Gürkan Myczko } [src:schism] schism:
CVE-2019-14523
Added tag(s) fixed-upstream.
> usertags 933809 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933807
933808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933808
933809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: Bug#934490: ffmpeg2theora: FTBFS in sid: python2/3
Processing control commands: > severity -1 important Bug #934490 [ffmpeg2theora] ffmpeg2theora: FTBFS in sid: python2/3 Severity set to 'important' from 'serious' -- 934490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: Bug#934984: Acknowledgement (mjpegtools: please mark shared libraries and development packages as "Multi-Arch: same")
Processing commands for cont...@bugs.debian.org: > submitter 934984 ! Bug #934984 [src:mjpegtools] mjpegtools: please mark shared libraries and development packages as "Multi-Arch: same" Changed Bug submitter to 'Jens Reyer ' from 'Jens Reyer '. > End of message, stopping processing here. Please contact me if you need assistance. -- 934984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Raising severities
ugs.debian.org/cgi-bin/bugreport.cgi?bug=874945 874947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874947 874950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874950 874952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874952 874953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874953 874954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874954 874955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874955 874956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874956 874964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874964 874968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874968 874969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874969 874970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874970 874973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874973 874977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874977 874978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874978 874979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874979 874980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874980 874985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874985 874987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874987 875003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875003 875010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875010 875018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875018 875021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021 875022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875022 875025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875025 875026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875026 875029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875029 875031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875031 875036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875036 875038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875038 875041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875041 875047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875047 875050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875050 875051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875051 875054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875054 875057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875057 875059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875059 875061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875061 875062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875062 875064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875064 875065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875065 875066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875066 875068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875068 875070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875070 875071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875071 875074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875074 875075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875075 875076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875076 875077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875077 875078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875078 875087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875087 875088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875088 875089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875089 875092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875092 875095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875095 875098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875098 875109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875109 875112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875112 875114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875114 875115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875115 875122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875122 875130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875130 875133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875133 875134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875134 875136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875136 875137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875137 875138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875138 875139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875139 875140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875140 875141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875141 875144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875144 875146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875146 875149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875149 875150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875150 875151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875151 875155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875155 875157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875157 875158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875158 875159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875159 875160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875160 875161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875161 875164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875164 875165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875165 875166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875166 875168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875168 875169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875169 875172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875172 875176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875176 875177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875177 875178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875178 875180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875180 875181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875181 875183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875183 875184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875184 875190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875190 875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195 875199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875199 875200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875200 875207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875207 875208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875208 875212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875212 875215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215 875219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875219 875221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875221 875222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875222 875227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875227 875228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875228 875234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875234 875238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875238 875240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875240 875242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875242 875243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875243 875250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875250 875258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875258 875494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875494 875499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Limit to bullseye
ian.org/cgi-bin/bugreport.cgi?bug=875234 875238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875238 875240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875240 875242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875242 875243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875243 875250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875250 875258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875258 875494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875494 875499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875499 935003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 925823, tagging 875146, tagging 875243, tagging 875242, tagging 875234, tagging 875227 ...
ugreport.cgi?bug=875161 875164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875164 875165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875165 875166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875166 875168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875168 875172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875172 875176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875176 875177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875177 875178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875178 875180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875180 875181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875181 875183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875183 875184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875184 875190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875190 875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195 875199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875199 875200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875200 875207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875207 875208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875208 875215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215 875219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875219 875221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875221 875222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875222 875227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875227 875234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875234 875238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875238 875240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875240 875242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875242 875243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875243 875250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875250 875258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875258 875494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875494 925823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925823 935003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Re: Bug#849862: kmidimon needs updaing to latest libdrumstick (1.0.2-1)
Processing control commands: > severity -1 serious Bug #849862 [kmidimon] kmidimon needs updaing to latest libdrumstick (1.0.2-1) Severity set to 'serious' from 'wishlist' -- 849862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#874857: [dssi] Future Qt4 removal from Buster - patch available
Processing control commands: > tags -1 + patch Bug #874857 [src:dssi] [dssi] Future Qt4 removal from Buster Added tag(s) patch. -- 874857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#829312 marked as pending in mjpegtools
Processing control commands: > tag -1 pending Bug #829312 [src:mjpegtools] Updating the mjpegtools Uploaders list Added tag(s) pending. -- 829312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#794751 marked as pending in mjpegtools
Processing control commands: > tag -1 pending Bug #794751 [mjpegtools] mjpegtools: lav2avi fails because mencoder is missing Added tag(s) pending. -- 794751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#772354 marked as pending in mjpegtools
Processing control commands: > tag -1 pending Bug #772354 [mjpegtools] mjpegtools: bashism in /bin/sh script Added tag(s) pending. -- 772354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#797169 marked as pending in mjpegtools
Processing control commands: > tag -1 pending Bug #797169 [src:mjpegtools] mjpegtools: FTBFS with x32 because of unused SIMD code remains Added tag(s) pending. -- 797169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#934984: marked as done (mjpegtools: please mark shared libraries and development packages as "Multi-Arch: same")
Your message dated Tue, 20 Aug 2019 09:05:53 +
with message-id
and subject line Bug#934984: fixed in mjpegtools 1:2.1.0+debian-6
has caused the Debian Bug report #934984,
regarding mjpegtools: please mark shared libraries and development packages as
"Multi-Arch: same"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
934984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mjpegtools
Version: 1:2.1.0+debian-5
Tags: patch
User: multiarch-de...@lists.alioth.debian.org
Usertags: multiarch
Hi
Please find attached a patch to mark the library and development
packages in mjpegtools as "Multi-Arch: same".
I rebuilt your package with my proposed patch applied and successfully
co-installed all packages from amd64 and i386.
Background:
Wine requires gstreamer1.0-plugins-bad to play some media. To support
both 32-bit and 64-bit Windows executables Wine needs to be installed on
two architectures, usually amd64 being the host arch and i386 the
foreign arch. Both Wine versions need their libraries from the same
arch, so gstreamer1.0-plugins-bad:amd64 and
gstreamer1.0-plugins-bad:i386 need to be co-installed.
gstreamer1.0-plugins-bad itself supports this, but some of its
dependencies not. From src:mjpegtools these are:
libmjpegutils-2.1-0
libmpeg2encpp-2.1-0
libmplex2-2.1-0
Generally the multi-arch hinter at https://tracker.debian.org/mjpegtools
currently reports:
There are issues with the multiarch metadata for this package.
liblavfile-2.1-0 could be marked Multi-Arch: same
liblavjpeg-2.1-0 could be marked Multi-Arch: same
liblavplay-2.1-0 could be marked Multi-Arch: same
libmjpegtools-dev could be marked Multi-Arch: same
libmjpegutils-2.1-0 could be marked Multi-Arch: same
libmpeg2encpp-2.1-0 could be marked Multi-Arch: same
libmplex2-2.1-0 could be marked Multi-Arch: same
Thanks and greets
jre
>From 09bc71493bff42010f143a009b7d5f147ea04f1c Mon Sep 17 00:00:00 2001
From: Jens Reyer
Date: Sat, 17 Aug 2019 16:56:07 +0200
Subject: Mark shared libraries and development packages as "Multi-Arch: same"
This adds the "Multi-Arch: same" header to the following packages:
liblavfile-2.1-0
liblavjpeg-2.1-0
liblavplay-2.1-0
libmjpegtools-dev
libmjpegutils-2.1-0
libmpeg2encpp-2.1-0
libmplex2-2.1-0
diff --git a/debian/control b/debian/control
index a84a973..4953fd8 100644
--- a/debian/control
+++ b/debian/control
@@ -48,6 +48,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (GTK+ fronte
Package: libmjpegtools-dev
Section: libdevel
+Multi-Arch: same
Architecture: any
Depends:
liblavfile-2.1-0 (= ${binary:Version}),
@@ -67,6 +68,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (development
Package: liblavfile-2.1-0
Section: libs
Architecture: any
+Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends}
@@ -80,6 +82,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (library)
Package: liblavjpeg-2.1-0
Section: libs
Architecture: any
+Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends}
@@ -93,6 +96,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (library)
Package: liblavplay-2.1-0
Section: libs
Architecture: any
+Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends}
@@ -106,6 +110,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (library)
Package: libmjpegutils-2.1-0
Section: libs
Architecture: any
+Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends}
@@ -119,6 +124,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (library)
Package: libmpeg2encpp-2.1-0
Section: libs
Architecture: any
+Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends}
@@ -132,6 +138,7 @@ Description: MJPEG capture/editing/replay and MPEG encoding toolset (library)
Package: libmplex2-2.1-0
Section: libs
Architecture: any
+Multi-Arch: same
Depends:
${misc:Depends},
${shlibs:Depends}
--- End Message ---
--- Begin Message ---
Source: mjpegtools
Source-Version: 1:2.1.0+debian-6
We believe that the bug you reported is fixed in the latest version of
mjpegtools, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 934...@bugs.debian.org,
and the maintainer will re
Bug#829312: marked as done (Updating the mjpegtools Uploaders list)
Your message dated Tue, 20 Aug 2019 09:05:53 + with message-id and subject line Bug#829312: fixed in mjpegtools 1:2.1.0+debian-6 has caused the Debian Bug report #829312, regarding Updating the mjpegtools Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 829312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mjpegtools Version: 1:2.1.0+debian-4 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Maia Kozheva has not been working on the mjpegtools package for quite some time. We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: mjpegtools Source-Version: 1:2.1.0+debian-6 We believe that the bug you reported is fixed in the latest version of mjpegtools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 829...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath (supplier of updated mjpegtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Aug 2019 10:21:46 +0200 Source: mjpegtools Architecture: source Version: 1:2.1.0+debian-6 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Fabian Greffrath Closes: 772354 794751 797169 829312 934984 Changes: mjpegtools (1:2.1.0+debian-6) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Fabian Greffrath ] * Remove myself from Uploaders * Add "Recommends: mencoder" to the mjpegtools package for the lav2avi script to work (Closes: #794751). * Extend 08_use_bash.patch to also run the lav2avi script with /bin/bash, as it contains bashisms (Closes: #772354). * Remove Maia Kozheva from Uploaders (Closes: #829312). . [ Ondřej Nový ] * d/watch: Use https protocol * Use debhelper-compat instead of debian/compat . [ Jens Reyer ] * Mark shared libraries and development packages as "Multi-Arch: same" (Closes: #934984). . [ Thorsten Glaser ] * New patch to disable unused CPU detection (Closes: #797169). Checksums-Sha1: 8694ab27e5d892653d988783d303fc4013bcdbcb 2673 mjpegtools_2.1.0+debian-6.dsc fd4eb0e9d0042c926f523a242893ccab6ec737fd 12436 mjpegtools_2.1.0+debian-6.debian.tar.xz 30f9ff89ae9740fe180ed25dd8eccd1760fbf405 18946 mjpegtools_2.1.0+debian-6_amd64.buildinfo Checksums-Sha256: f87447b38127628474a553107180451a4ec3dac6753f2d5c116c8a70fff095f8 2673 mjpegtools_2.1.0+debian-6.dsc ac5b669d40bbd79d94a7f8d68bd063104f05d197d992c69dd6a22c0946913f19 12436 mjpegtools_2.1.0+debian-6.debian.tar.xz 5c6aebfe68d19357e55c3b0e007a0e454d577223d1da50633512e6d45627ca15 18946 mjpegtools_2.1.0+debian-6_amd64.buildinfo Files: 0b4d1ecdfb8e6e7bfa872e7dc5fe68b6 2673 video optional mjpegtools_2.1.0+debian-6.dsc f195208d2d9aa04bbd8983b33cb33651 12436 video optional mjpegtools_2.1.0+debian-6.debian.tar.xz 5e48aac46cb91f2106a40524c5b7dcf6 18946 video optional mjpegtools_2.1.0+debian-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCAAwFiEEIsF2SKlSa4TfGRyWy+qOlwzNWd8FAl1bsdQSHGZhYmlhbkBk ZWJpYW4ub3JnAAoJEMvqjpcMzVnfOs8QAOaR/evMYlSVOE0UmwCKO7U1a2oqnv43 9IZ6pf86QrxUTWB9V6rRCV89cYYglk5VBq+Httn6iUKsupNA+jzL7keUDGpZ9mSA S2C+zKy9vXn6zbzbDlar7iwleZfQf+u3b/+OREPtPb97KuMCRoE9+GbPQamE1L+/ 6sFlKprkVHlCMV3j7EVt5fbW
Bug#772354: marked as done (mjpegtools: bashism in /bin/sh script)
Your message dated Tue, 20 Aug 2019 09:05:53 + with message-id and subject line Bug#772354: fixed in mjpegtools 1:2.1.0+debian-6 has caused the Debian Bug report #772354, regarding mjpegtools: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 772354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mjpegtools Severity: normal Version: 1:2.1.0+debian-2.1+b2 User: debian-rele...@lists.debian.org Usertags: goal-dash Hi, I've ran checkbashisms (from the 'devscripts' package) over the whole archive and I found that your package has a /bin/sh script that uses a "bashism". checkbashisms' output: > possible bashism in ./usr/lib/mjpegtools/bin/lav2avi.sh line 75 (echo -e): >echo -e "USAGE:\t`basename $0` filename.eli" > possible bashism in ./usr/lib/mjpegtools/bin/lav2avi.sh line 76 (echo -e): >echo -e "\n\tfilename - MJPEG Tools lav editing file\n" > possible bashism in ./usr/lib/mjpegtools/bin/lav2avi.sh line 77 (echo -e): >echo -e "EXAMPLE:\n\t`basename $0` SecondFilm.eli\n" Not using bash (or a Debian Policy compliant shell interpreter that doesn't provide such an extra feature) as /bin/sh is likely to lead to errors or unexpected behaviours. Please be aware that dash is the default /bin/sh. Please closely examine the above output and the script, and determine what the proper severity of the bug is, and adjust it accordingly. If it's important or greater please hurry to get this fixed for jessie. Hints about how to fix bashisms can be found at: https://wiki.ubuntu.com/DashAsBinSh Thanks in advance, Raphael Geissert --- End Message --- --- Begin Message --- Source: mjpegtools Source-Version: 1:2.1.0+debian-6 We believe that the bug you reported is fixed in the latest version of mjpegtools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath (supplier of updated mjpegtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Aug 2019 10:21:46 +0200 Source: mjpegtools Architecture: source Version: 1:2.1.0+debian-6 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Fabian Greffrath Closes: 772354 794751 797169 829312 934984 Changes: mjpegtools (1:2.1.0+debian-6) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Fabian Greffrath ] * Remove myself from Uploaders * Add "Recommends: mencoder" to the mjpegtools package for the lav2avi script to work (Closes: #794751). * Extend 08_use_bash.patch to also run the lav2avi script with /bin/bash, as it contains bashisms (Closes: #772354). * Remove Maia Kozheva from Uploaders (Closes: #829312). . [ Ondřej Nový ] * d/watch: Use https protocol * Use debhelper-compat instead of debian/compat . [ Jens Reyer ] * Mark shared libraries and development packages as "Multi-Arch: same" (Closes: #934984). . [ Thorsten Glaser ] * New patch to disable unused CPU detection (Closes: #797169). Checksums-Sha1: 8694ab27e5d892653d988783d303fc4013bcdbcb 2673 mjpegtools_2.1.0+debian-6.dsc fd4eb0e9d0042c926f523a242893ccab6ec737fd 12436 mjpegtools_2.1.0+debian-6.debian.tar.xz 30f9ff89ae9740fe180ed25dd8eccd1760fbf405 18946 mjpegtools_2.1.0+debian-6_amd64.buildinfo Checksums-Sha256: f87447b38127628474a553107180451a4ec3dac6753f2d5c116c8a70fff095f8 2673 mjpegtools_2.1.0+debian-6.dsc ac5b669d40bbd79d94a7f8d68bd063104f05d197d992c69dd6a22c0946913f19 12436 mjpegtools_2.1.0+debian-6.debian.tar.xz 5c6aebfe68d19357e55c3b0e007a0e454d577223d1da50633512e6d45627ca15 18946 mjpegtools_2.1.0+debian-6_amd64.buildinfo Files: 0b4d1ecdfb8e6e7bfa872e7dc5fe68b6 2673 video optional mjpegtools_2.1.0+debian-6.dsc f195208d2d9aa04bbd8983b33cb33651
Bug#797169: marked as done (mjpegtools: FTBFS with x32 because of unused SIMD code remains)
Your message dated Tue, 20 Aug 2019 09:05:53 +
with message-id
and subject line Bug#797169: fixed in mjpegtools 1:2.1.0+debian-6
has caused the Debian Bug report #797169,
regarding mjpegtools: FTBFS with x32 because of unused SIMD code remains
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
797169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mjpegtools
Version: 1:2.1.0+debian-3
Severity: important
Tags: patch
Hi,
your package configures with --disable-simd-accel but the upstream
code fails to fully disable all related functions, leading to some
asm code still being compiled, which fails on x32 due to its model.
The attached patch fully disables the (unused anyway!) code making
it buildable on x32. I tested on i386, where it still builds, too.
Please apply and forward upstream. Thanks!
-- System Information:
Debian Release: stretch/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64
Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)
diff -Nru mjpegtools-2.1.0+debian/debian/changelog mjpegtools-2.1.0+debian/debian/changelog
--- mjpegtools-2.1.0+debian/debian/changelog 2014-12-08 11:08:24.0 +0100
+++ mjpegtools-2.1.0+debian/debian/changelog 2015-08-28 10:37:41.0 +0200
@@ -1,3 +1,10 @@
+mjpegtools (1:2.1.0+debian-3+x32.1) unreleased; urgency=medium
+
+ * Non-maintainer upload.
+ * New patch to disable unused CPU detection
+
+ -- Thorsten Glaser Fri, 28 Aug 2015 10:37:14 +0200
+
mjpegtools (1:2.1.0+debian-3) unstable; urgency=medium
[ Alessio Treglia ]
diff -Nru mjpegtools-2.1.0+debian/debian/patches/18_no-simd.patch mjpegtools-2.1.0+debian/debian/patches/18_no-simd.patch
--- mjpegtools-2.1.0+debian/debian/patches/18_no-simd.patch 1970-01-01 01:00:00.0 +0100
+++ mjpegtools-2.1.0+debian/debian/patches/18_no-simd.patch 2015-08-28 10:37:06.0 +0200
@@ -0,0 +1,76 @@
+Description: Test for SIMD instructions at run-time only if configured.
+ Do not attempt to use e.g. CPU detection if the result does not matter
+ anyway; fixes FTBFS on architectures with slightly different asm, such
+ as x32.
+Author: Thorsten Glaser
+Forwarded: no
+Bug-Debian: coming
+Last-Update: 2015-08-28
+
+--- a/configure.ac
b/configure.ac
+@@ -386,6 +386,8 @@ AC_SUBST(PROGRAM_NOPIC)
+
+ if test "$enable_simd_accel" != "false" -a "$enable_simd_accel" != "no"
+ then
++ AC_DEFINE(HAVE_SIMD_ACCEL, 1, [use SIMD multimedia instructions if possible])
++
+ if test x$have_x86cpu = xtrue
+ then
+ AC_MSG_CHECKING([if C compiler accepts inline MMX assembly])
+--- a/utils/cpu_accel.c
b/utils/cpu_accel.c
+@@ -38,7 +38,7 @@
+ #include
+ #endif
+
+-#ifdef HAVE_ALTIVEC
++#if defined(HAVE_SIMD_ACCEL) && defined(HAVE_ALTIVEC)
+ extern int altivec_copy_v0();
+ #endif
+
+@@ -77,7 +77,7 @@ extern int altivec_copy_v0();
+
+ static char *parse_next(char **, const char *);
+
+-#ifdef HAVE_X86CPU
++#if defined(HAVE_SIMD_ACCEL) && defined(HAVE_X86CPU)
+
+ /* Some miscelaneous stuff to allow checking whether SSE instructions cause
+illegal instruction errors.
+@@ -208,7 +208,7 @@ static int x86_accel (void)
+ #endif
+
+
+-#ifdef HAVE_ALTIVEC
++#if defined(HAVE_SIMD_ACCEL) && defined(HAVE_ALTIVEC)
+ /* AltiVec optimized library for MJPEG tools MPEG-1/2 Video Encoder
+ * Copyright (C) 2002 James Klicman
+ *
+@@ -263,7 +263,7 @@ noAltiVec:
+
+ int32_t cpu_accel (void)
+ {
+-#ifdef HAVE_X86CPU
++#if defined(HAVE_SIMD_ACCEL) && defined(HAVE_X86CPU)
+ static int got_accel = 0;
+ static int accel;
+
+@@ -273,7 +273,7 @@ int32_t cpu_accel (void)
+ }
+
+ return accel;
+-#elif defined(HAVE_ALTIVEC)
++#elif defined(HAVE_SIMD_ACCEL) && defined(HAVE_ALTIVEC)
+ return detect_altivec();
+ #else
+ return 0;
+@@ -356,7 +356,7 @@ void *bufalloc( size_t size )
+
+ if( !bufalloc_init )
+ {
+-#ifdef HAVE_X86CPU
++#if defined(HAVE_SIMD_ACCEL) && defined(HAVE_X86CPU)
+ if( (cpu_accel() & (ACCEL_X86_SSE|ACCEL_X86_3DNOW)) != 0 )
+ {
+ simd_alignment = 64;
diff -Nru mjpegtools-2.1.0+debian/debian/patches/series mjpegtools-2.1.0+debian/debian/patches/series
--- mjpegtools-2.1.0+debian/debian/patches/series 2014-12-08 09:
Bug#794751: marked as done (mjpegtools: lav2avi fails because mencoder is missing)
Your message dated Tue, 20 Aug 2019 09:05:53 + with message-id and subject line Bug#794751: fixed in mjpegtools 1:2.1.0+debian-6 has caused the Debian Bug report #794751, regarding mjpegtools: lav2avi fails because mencoder is missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794751 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mjpegtools Version: 1:2.1.0+debian-3 Severity: important Dear Maintainer, When running something like: lav2avi test.eli I get: # # Entering to 1st phase # # /usr/bin/lav2avi: 42: /usr/bin/lav2avi: mencoder: not found INFO: [lav2yuv] chroma '422' recommended with this input INFO: [lav2yuv] set default chroma '420jpeg' ## # Entering to 2nd phase with bitrate # ## /usr/bin/lav2avi: 55: /usr/bin/lav2avi: mencoder: not found INFO: [lav2yuv] chroma '422' recommended with this input INFO: [lav2yuv] set default chroma '420jpeg' ## # Entering to 3rd phase with bitrate # ## /usr/bin/lav2avi: 70: /usr/bin/lav2avi: mencoder: not found INFO: [lav2yuv] chroma '422' recommended with this input INFO: [lav2yuv] set default chroma '420jpeg' If I install the package mencoder then lav2avi does work, hence perhaps mjpegtools should have mencoder as a dependency? Regards. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mjpegtools depends on: ii dpkg 1.18.1 ii install-info 6.0.0.dfsg.1-3 ii libc62.19-19 ii libdv4 1.0.0-6 ii libgcc1 1:5.1.1-14 ii libjpeg62-turbo 1:1.4.1-1 ii liblavfile-2.1-0 1:2.1.0+debian-3 ii liblavjpeg-2.1-0 1:2.1.0+debian-3 ii liblavplay-2.1-0 1:2.1.0+debian-3 ii libmjpegutils-2.1-0 1:2.1.0+debian-3 ii libmpeg2encpp-2.1-0 1:2.1.0+debian-3 ii libmplex2-2.1-0 1:2.1.0+debian-3 ii libpng12-0 1.2.50-2+b2 ii libsdl1.2debian 1.2.15-11 ii libstdc++6 5.1.1-14 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages mjpegtools recommends: ii mjpegtools-gtk 1:2.1.0+debian-3 mjpegtools suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: mjpegtools Source-Version: 1:2.1.0+debian-6 We believe that the bug you reported is fixed in the latest version of mjpegtools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath (supplier of updated mjpegtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 20 Aug 2019 10:21:46 +0200 Source: mjpegtools Architecture: source Version: 1:2.1.0+debian-6 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Fabian Greffrath Closes: 772354 794751 797169 829312 934984 Changes: mjpegtools (1:2.1.0+debian-6) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Fabian Greffrath ] * Remove myself from Uploaders * Add "Recommends: mencoder" to the mjpegtools package for the lav2avi script to work (Closes: #794751). * Extend 08_use_bash.patch to also run the lav2avi script with /bin/bash, as it contains bashisms (Closes: #772354). * Remove Maia Kozheva from Uploaders (Closes: #82
Bug#849862: marked as done (kmidimon needs updaing to latest libdrumstick (1.0.2-1))
Your message dated Sat, 24 Aug 2019 01:21:30 + with message-id and subject line Bug#935541: Removed package(s) from unstable has caused the Debian Bug report #849862, regarding kmidimon needs updaing to latest libdrumstick (1.0.2-1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 849862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kmidimon Version: 0.7.5-3 Severity: wishlist Dear Maintainer, I am looking to join in with the maintenance of the libdrumstick suite of packages (vmpk, kmetronome etc.). Libdrumstick 1.0.2-1 is currently sitting in experimental, waiting for a transition slot. Unfortunately, we missed the date of the transition freeze for Debian Stretch, so it will have to wait for Buster. Kmidimon is the only remaining reverse dependency of libdrumstick in Debian that does not build with the latest version in experimental. Discussions with the upstream maintainer suggest that it will be upgraded (including migration to the latest Qt5 libraries) in early 2017. -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 'xenial'), (100, 'xenial-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-24-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Version: 0.7.5-3+rm Dear submitter, as the package kmidimon has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/935541 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#874955: marked as done ([kmidimon] Future Qt4 removal from Buster)
Your message dated Sat, 24 Aug 2019 01:21:30 + with message-id and subject line Bug#935541: Removed package(s) from unstable has caused the Debian Bug report #874955, regarding [kmidimon] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 874955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kmidimon Version: 0.7.5-3 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Version: 0.7.5-3+rm Dear submitter, as the package kmidimon has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/935541 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 875321, tagging 925667, tagging 934709, tagging 935246, tagging 928993, tagging 935086 ...
=875327 875500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875500 875501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875501 891993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891993 906564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906564 906578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906578 916195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916195 925667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925667 928993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928993 931921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931921 932614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932614 932653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932653 932668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932668 934709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934709 935086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935086 935246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935246 935272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935272 935290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935290 935324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935324 935335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935335 935339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935339 935375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935375 935384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935384 935486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#874852: marked as done ([dgedit] Future Qt4 removal from Buster)
Your message dated Sat, 24 Aug 2019 09:34:36 + with message-id and subject line Bug#874852: fixed in dgedit 0.10.0-1 has caused the Debian Bug report #874852, regarding [dgedit] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 874852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dgedit Version: 0~git20160401-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: dgedit Source-Version: 0.10.0-1 We believe that the bug you reported is fixed in the latest version of dgedit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated dgedit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Aug 2019 11:14:30 +0200 Source: dgedit Architecture: source Version: 0.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 874852 Changes: dgedit (0.10.0-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * debian/watch: Add watch file. * New upstream release - Build with Qt 5. (Closes: #874852) * debian/: Remove get-orig-source. * debian/contol: - Bump debhelper compat to 12. - Bump Standards-Version. * debian/patches: Fix rcc invocation. Checksums-Sha1: 50aeddd39d08e8b5a215016b463e34abecf2b67f 1988 dgedit_0.10.0-1.dsc c4be2d69b90f1cc1649b029c36155cde18d46b61 515934 dgedit_0.10.0.orig.tar.gz 0fd6f4db6b0df3392d39cedb56487dbe27f13ac7 3120 dgedit_0.10.0-1.debian.tar.xz Checksums-Sha256: 1ab3216abd428d1a40040308b5c58a524fecca04cabbff6bf9e3b491b376918b 1988 dgedit_0.10.0-1.dsc 846f580d5a12eff7e5668893d18547c5a0032d2cf11b9bee37ac7ac094aa83e4 515934 dgedit_0.10.0.orig.tar.gz d49b1ed797ed2425ecae223fa9c5f604314124031ff81662e8ddceefa0acf73e 3120 dgedit_0.10.0-1.debian.tar.xz Files: d2286e174773cfebf7972515ca4d3
Bug#874823: marked as done ([ams] Future Qt4 removal from Buster)
Your message dated Sat, 24 Aug 2019 14:42:41 + with message-id and subject line Bug#874823: fixed in ams 2.1.2-1 has caused the Debian Bug report #874823, regarding [ams] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 874823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ams Version: 2.1.1-1.1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: ams Source-Version: 2.1.2-1 We believe that the bug you reported is fixed in the latest version of ams, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated ams package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 24 Aug 2019 14:13:33 +0200 Source: ams Architecture: source Version: 2.1.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 874823 Changes: ams (2.1.2-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org * d/changelog: Remove trailing whitespaces . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/watch: Use https protocol * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release. * debian/patches: Apply upstream patches to switch to Qt 5 and fixes for some other smaller issues. (Closes: #874823) * debian/: Bump debhelper compat to 12. * debian/control: - Bump Standards-Version. - Switch to Qt 5. * debian/menu: Remove in favor of desktop file. Checksums-Sha1: ffe22b1151dd54858b24e57f7cbef1681b4f86af 2094 ams_2.1.2-1.dsc 42ca644082ce1409fbb46160a7bbcac90cf8b779 348027 ams_2.1.2.orig.tar.bz2 930d5c38fbc1601da7039a724b38a5b4ff79 18588 ams_2.1.2-1.debian.tar.xz Checksums-Sha256: 5b787cd037e051e20012e614377673a3fc62ea4145ad781caebedc5ee847c712 2094 ams_2.1.2-1.dsc 808630674101cefa90567b14f4eefdb61baa0c3facbe79f2f2d692e92eccebab 348027
Processed: Bug#874857 marked as pending in dssi
Processing control commands: > tag -1 pending Bug #874857 [src:dssi] [dssi] Future Qt4 removal from Buster Added tag(s) pending. -- 874857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#874857: marked as done ([dssi] Future Qt4 removal from Buster)
Your message dated Sun, 25 Aug 2019 11:49:00 + with message-id and subject line Bug#874857: fixed in dssi 1.1.1~dfsg0-2 has caused the Debian Bug report #874857, regarding [dssi] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 874857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874857 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dssi Version: 1.1.1~dfsg0-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: dssi Source-Version: 1.1.1~dfsg0-2 We believe that the bug you reported is fixed in the latest version of dssi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 874...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ross Gammon (supplier of updated dssi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 25 Aug 2019 13:02:39 +0200 Source: dssi Architecture: source Version: 1.1.1~dfsg0-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Ross Gammon Closes: 874857 Changes: dssi (1.1.1~dfsg0-2) unstable; urgency=medium . [ Stuart Prescott ] * Disable building of Qt4 examples (Closes: #874857). * Update to debhelper compat 12. * Update Standards-Version to 4.4.0 (no changes required). * Enable additional hardening options at build-time. * Move pkgconfig file to arch:all location. * Move non-dev packages to Section: sound * Remove trailing whitespace in changelog . [ Jaromír Mikeš ] * Added myself as uploader . [ Ondřej Nový ] * d/copyright: Change Format URL to correct one * d/control: Set Vcs-* to salsa.debian.org * d/changelog: Remove trailing whitespaces . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/watch: Use https protocol . [ Ross Gammon ] * Add myself to uploaders Checksums-Sha1: 97fcd99b04caa82fa88033244555d10ba7c95423 2350 dssi_1.1.1~dfsg0-2.dsc 8288f7f63d40158ecbaba6c3b0f094c6458f791a 4420 dssi_1.1.1~dfsg0-2.debian.tar.xz 6b4575199d043783f7c751100252c25a605b5f99 8716 dssi_1.1.1~dfsg0-2_amd64.buildinfo Checksums-Sha256: 5af369b085ae95abca72ff8dde010cc283aef27712a5cc18f77bf5834c6b3a16 2350
Processed: Bug#923566 marked as pending in jacktrip
Processing control commands: > tag -1 pending Bug #923566 [src:jacktrip] jacktrip FTCBFS: uses the wrong pkg-config Added tag(s) pending. -- 923566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#923566: marked as done (jacktrip FTCBFS: uses the wrong pkg-config)
Your message dated Wed, 28 Aug 2019 09:08:33 + with message-id and subject line Bug#923566: fixed in jacktrip 1.1~repack-6 has caused the Debian Bug report #923566, regarding jacktrip FTCBFS: uses the wrong pkg-config to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 923566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jacktrip Version: 1.1~repack-5 Tags: patch User: helm...@debian.org Usertags: rebootstrap jacktrip fails to cross build from source, because debian/rules hard codes the build architecture pkg-config and thus fails finding rtaudio. The attached patch fixes that part, but jacktrip continues to fail due to its use of help2man. There is no good solution for help2man except not using it. Please consider applying the attached patch and close this bug when addressing the pkg-config part. Helmut diff --minimal -Nru jacktrip-1.1~repack/debian/changelog jacktrip-1.1~repack/debian/changelog --- jacktrip-1.1~repack/debian/changelog2016-08-03 12:31:59.0 +0200 +++ jacktrip-1.1~repack/debian/changelog2019-03-01 14:52:29.0 +0100 @@ -1,3 +1,10 @@ +jacktrip (1.1~repack-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Improve cross building: Use a triplet-prefixed pkg-config. (Closes: #-1) + + -- Helmut Grohne Fri, 01 Mar 2019 14:52:29 +0100 + jacktrip (1.1~repack-5) unstable; urgency=medium * Only build 'release' profile diff --minimal -Nru jacktrip-1.1~repack/debian/rules jacktrip-1.1~repack/debian/rules --- jacktrip-1.1~repack/debian/rules2016-08-03 12:30:30.0 +0200 +++ jacktrip-1.1~repack/debian/rules2019-03-01 14:52:28.0 +0100 @@ -26,12 +26,15 @@ # SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. export QT_SELECT=qt5 +-include /usr/share/dpkg/buildtools.mk include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/qmake.mk include /usr/share/cdbs/1/rules/utils.mk -CPPFLAGS+=$(shell pkg-config --cflags rtaudio || true) -LDFLAGS +=$(shell pkg-config --libs rtaudio || true) +PKG_CONFIG ?= pkg-config + +CPPFLAGS+=$(shell $(PKG_CONFIG) --cflags rtaudio) +LDFLAGS +=$(shell $(PKG_CONFIG) --libs rtaudio) DEB_MAKE_BUILD_TARGET = release DEB_MAKE_INSTALL_TARGET = release-install INSTALL_ROOT=$(DEB_DESTDIR) --- End Message --- --- Begin Message --- Source: jacktrip Source-Version: 1.1~repack-6 We believe that the bug you reported is fixed in the latest version of jacktrip, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated jacktrip package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 28 Aug 2019 09:19:01 +0200 Source: jacktrip Architecture: source Version: 1.1~repack-6 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 923566 Changes: jacktrip (1.1~repack-6) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ IOhannes m zmölnig ] * Improve cross building: Use a triplet-prefixed pkg-config. Thanks to Helmut Grohne (Closes: #923566) * Switch build-system from CDBS to dh * Add fix for another spelling error * Update d/copyright * Add Files-Excluded stanza * Update dates * Regenerate d/copyright_hints * Fix typo in d/README.source * Declare that building the package doesn't require 'root' powers * Drop obsolete d/source/local-options to allow 'dgit push' * Removed Jonas from uploaders (after a quick check on IRC) * Bump dh compat to 12 * Use debhelper-compat instead of debian/compat * Bump standards-version to 4.4.0 Checksums-Sha1: 38b4adade777dc0363e4e0776b76053e5aa91e24 2238 jacktrip_1.1~repack-6.dsc 2fecfd69ffb3f6443ca0f3cde8f07f846
Processed: block 936371 with 938637 936104 936166 936173 936270 936297 936531 936555 936594 612636 936721 936757 936812 936813 936948 936981 936987 937044 937073 937125 937137 937224 937233 781914
Processing commands for cont...@bugs.debian.org: > block 936371 with 938637 936104 936166 936173 936270 936297 936531 936555 > 936594 612636 936721 936757 936812 936813 936948 936981 936987 937044 937073 > 937125 937137 937224 937233 781914 Bug #936371 [src:dbus-python] dbus-python: Python2 removal in sid/bullseye 936371 was not blocked by any bugs. 936371 was blocking: 938625 Added blocking bug(s) of 936371: 936531, 936981, 781914, 937125, 936987, 936812, 937233, 936270, 936104, 936948, 936173, 936555, 937137, 936721, 937044, 936757, 937073, 936166, 938637, 937224, 936594, 936813, 612636, and 936297 > thanks Stopping processing here. Please contact me if you need assistance. -- 936371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: your mail
bian.org/cgi-bin/bugreport.cgi?bug=938627 938674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938674 938725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938725 938731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938731 938807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938807 938822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938822 938827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938827 938854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938854 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#899241 marked as pending in mustang-plug
Processing control commands: > tag -1 pending Bug #899241 [mustang-plug] Amplifier detected by source from program developer but not by Debian package. Added tag(s) pending. -- 899241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 899241
Processing commands for cont...@bugs.debian.org: > tags 899241 - pending Bug #899241 [mustang-plug] Amplifier detected by source from program developer but not by Debian package. Removed tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 899241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: severity of 899241 is important
Processing commands for cont...@bugs.debian.org: > severity 899241 important Bug #899241 [mustang-plug] Amplifier detected by source from program developer but not by Debian package. Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 899241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899241 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#875050: marked as done ([mustang-plug] Future Qt4 removal from Buster)
Your message dated Thu, 05 Sep 2019 22:09:42 + with message-id and subject line Bug#875050: fixed in mustang-plug 1.2-2 has caused the Debian Bug report #875050, regarding [mustang-plug] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 875050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mustang-plug Version: 1.2-1 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: mustang-plug Source-Version: 1.2-2 We believe that the bug you reported is fixed in the latest version of mustang-plug, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Muehlenhoff (supplier of updated mustang-plug package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 05 Sep 2019 22:55:30 +0200 Source: mustang-plug Architecture: source Version: 1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Moritz Muehlenhoff Closes: 875050 Changes: mustang-plug (1.2-2) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org * Use debhelper-compat instead of debian/compat . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Olivier Humbert ] * Adds a desktop file * Installs the desktop file * Installs a doc file * Adds myself to the d/copyright file . [ Moritz Mühlenhoff ] * Cherrypick upstream for commit for Qt5 and switch the dependencies away from Qt4 (Closes: #875050) * Use debhelper compat level 12 * Bump standards version to 4.4.0 Checksums-Sha1: 64aa95e53fa54768eac524e3b661520a1436db57 1972 mustang-plug_1.2-2.dsc 399c29863d5fe6ab6a6df51a3eca13c18ae9442a 3652 mustang-plug_1.2-2.debian.tar.xz cb7a4dfbaa1a7cf640b5efcf38e38b23c8aa8ca8 10774 mustang-plug_1.2-2_amd64.buildinfo Checksums-Sha256: 67d4b57dc65813f780dbc8bcadee313a94216103b3d331b2f64abe93c5efcc7a 1972 mustang-plug_1.2-2.dsc dd9efafed0d269efe1a349cd72131e7e22f826655f07b31043d7787d84e46570 3652 mustang-p
Bug#902403: marked as done (qjackctl FTCBFS: uses the build architecture qmake)
Your message dated Fri, 06 Sep 2019 07:19:36 + with message-id and subject line Bug#902403: fixed in qjackctl 0.5.9-1 has caused the Debian Bug report #902403, regarding qjackctl FTCBFS: uses the build architecture qmake to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 902403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qjackctl Version: 0.5.0-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap qjackctl fails to cross build from source, because ./configure detects the build architecture qmake with AC_PATH_PROG while it should have been using AC_PATH_TOOL for architecture-dependent commands. The attached patch fixes that and makes qjackctl cross build successfully. Please consider applying it. Helmut --- qjackctl-0.5.0.orig/configure.ac +++ qjackctl-0.5.0/configure.ac @@ -254,12 +254,12 @@ ac_errmsg="not found in current PATH. Maybe QT development environment isn't available." if test "x$ac_qt4" = "xyes"; then - AC_PATH_PROG(ac_qmake, qmake-qt4, [no], $ac_path) + AC_PATH_TOOL(ac_qmake, qmake-qt4, [no], $ac_path) else - AC_PATH_PROG(ac_qmake, qmake-qt5, [no], $ac_path) + AC_PATH_TOOL(ac_qmake, qmake-qt5, [no], $ac_path) fi if test "x$ac_qmake" = "xno"; then - AC_PATH_PROG(ac_cv_qmake, qmake, [no], $ac_path) + AC_PATH_TOOL(ac_cv_qmake, qmake, [no], $ac_path) ac_qmake=$ac_cv_qmake fi if test "x$ac_qmake" = "xno"; then --- End Message --- --- Begin Message --- Source: qjackctl Source-Version: 0.5.9-1 We believe that the bug you reported is fixed in the latest version of qjackctl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 902...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated qjackctl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Sep 2019 08:59:08 +0200 Source: qjackctl Architecture: source Version: 0.5.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 902403 Changes: qjackctl (0.5.9-1) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Olivier Humbert ] * Update copyright years for Rui (upstream) . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release. - Use AC_PATH_TOOL. (Closes: #902403) * debian/control: - Bump debhelper compat to 12. - Bump Standards-Version. * debian/rules: Remove QT_SELECT, no longer needed. Checksums-Sha1: 17d1b2e9894e33f4bb1634fa9372e75b88f7ac0c 2167 qjackctl_0.5.9-1.dsc 4b64b94fe765b2a6eafa28db90c8c21a1f503e11 925690 qjackctl_0.5.9.orig.tar.gz 9a0e4ab25acae684c78689a9fe8b7800c997e327 8156 qjackctl_0.5.9-1.debian.tar.xz Checksums-Sha256: ac843fecb38a077e5e797791798c39a80f1f9f36bca844c214490bba33b5fd59 2167 qjackctl_0.5.9-1.dsc f3fa7b3c1e28d56632de10c32e978a54f94c29b0239e2b6b2622d4a49ae65ee9 925690 qjackctl_0.5.9.orig.tar.gz a1821512c0d65220efaa2e0fe929fefff8f67ec4137e4523c559484afe4fd626 8156 qjackctl_0.5.9-1.debian.tar.xz Files: 2482f857f948160dd92398ed57689f0e 2167 sound optional qjackctl_0.5.9-1.dsc 11c5c8d89066de04064a2f8f409adeea 925690 sound optional qjackctl_0.5.9.orig.tar.gz 802159e1ad3bd9b863b1987560d95d27 8156 sound optional qjackctl_0.5.9-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl1yBD0VHHNyYW1hY2hl ckBkZWJpYW4ub3JnAAoJEGny/FFupxmTa0oQALHXg3vd9Emn4pVr6ZCv0A+k0cpp a0K/8hN/kIfB+jNA9yLKh5U5ByppSpGq8FOVdnbY4j5DlIjulevaozm7fonC/C+7 FsaATt1zsJGtgDNKjDLNsBYdQMts2GKEw3f2R7QJV+3jskIECli2R9FFLHwREhgQ Uhz66Sx/Gn9JRLCaI012Rle2jiZwG9xsXPzKlZyFcwmZxVzMi/kyIzIDC0ciHPul AW3n/WOmDWAA1zmUxFUH34KlFuU5tZgg6s+0XIz0U5jY3F6au03yys+7NJYJxDYg dOhpTKakA87eY/vViki8/S9gJ+GWOuwfGzYRApEvFS7+xniJAu7gzSWQwAEIMh2R
Processed: limit source to gigedit, tagging 915329
Processing commands for cont...@bugs.debian.org: > limit source gigedit Limiting to bugs with field 'source' containing at least one of 'gigedit' Limit currently set to 'source':'gigedit' > tags 915329 + pending Bug #915329 [src:gigedit] gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 915329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#751615: marked as done (libsoxr: Conflicting declarations of src_strerror mix up pointer and integer)
Your message dated Mon, 9 Sep 2019 20:31:03 +0200 with message-id <20190909183103.ga3...@ramacher.at> and subject line Re: Bug#751615: libsoxr: Conflicting declarations of src_strerror mix up pointer and integer has caused the Debian Bug report #751615, regarding libsoxr: Conflicting declarations of src_strerror mix up pointer and integer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 751615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsoxr Version: 0.1.1-1 Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. Please note that we use our research compiler tool-chain (using tools from the cbmc package), which permits extended reporting on type inconsistencies at link time. [...] /usr/bin/cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fopenmp -Wconversion -Wall -W -pedantic -Wundef -Wcast-align -Wpointer-arith -Wno-long-long -Wnested-externs -Wmissing-prototypes -Wstrict-prototypes -Wl,-z,relro CMakeFiles/1a-lsr.dir/1a-lsr.c.o -o 1a-lsr -rdynamic -lm ../src/libsoxr.so.0.1.0 ../src/libsoxr-lsr.so.0.1.9 ../src/libsoxr.so.0.1.0 -Wl,-rpath,/srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/obj-x86_64-linux-gnu/src error: conflicting function declarations "src_strerror" old definition in module 1a-lsr file /srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/src/soxr-lsr.h line 69 const char * (signed int) new definition in module lsr file /srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/src/lsr.c line 108 const char * (const char *error) examples/CMakeFiles/1a-lsr.dir/build.make:91: recipe for target 'examples/1a-lsr' failed make[3]: *** [examples/1a-lsr] Error 64 make[3]: Leaving directory '/srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/obj-x86_64-linux-gnu' CMakeFiles/Makefile2:354: recipe for target 'examples/CMakeFiles/1a-lsr.dir/all' failed make[2]: *** [examples/CMakeFiles/1a-lsr.dir/all] Error 2 Looking at the code it seems there is an nice mix of preprocessor macros and typedefs in place, which unfortunately seem to have led to confusion. Looking at the code and the (single) use, it really seems that the implementation gets it wrong, where soxr_error_t expands to a const char*. Best, Michael pgpmfSmgFYFGC.pgp Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.1.2-1 On 2014-06-14 19:59:58, Michael Tautschnig wrote: > Package: libsoxr > Version: 0.1.1-1 > Usertags: goto-cc > > During a rebuild of all Debian packages in a clean sid chroot (using > cowbuilder > and pbuilder) the build failed with the following error. Please note that we > use our research compiler tool-chain (using tools from the cbmc package), > which > permits extended reporting on type inconsistencies at link time. > > [...] > /usr/bin/cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat > -Werror=format-security -D_FORTIFY_SOURCE=2 -fopenmp -Wconversion -Wall -W > -pedantic -Wundef -Wcast-align -Wpointer-arith -Wno-long-long > -Wnested-externs -Wmissing-prototypes -Wstrict-prototypes -Wl,-z,relro > CMakeFiles/1a-lsr.dir/1a-lsr.c.o -o 1a-lsr -rdynamic -lm > ../src/libsoxr.so.0.1.0 ../src/libsoxr-lsr.so.0.1.9 ../src/libsoxr.so.0.1.0 > -Wl,-rpath,/srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/obj-x86_64-linux-gnu/src > > > error: conflicting function declarations "src_strerror" > old definition in module 1a-lsr file > /srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/src/soxr-lsr.h > line 69 > const char * (signed int) > new definition in module lsr file > /srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/src/lsr.c line > 108 > const char * (const char *error) > examples/CMakeFiles/1a-lsr.dir/build.make:91: recipe for target > 'examples/1a-lsr' failed > make[3]: *** [examples/1a-lsr] Error 64 > make[3]: Leaving directory > '/srv/jenkins-slave/workspace/sid-goto-cc-libsoxr/libsoxr-0.1.1/obj-x86_64-linux-gnu' > CMakeFiles/Makefile2:354: recipe for target > 'examples/CMakeFiles/1a-lsr.dir/all' failed > make[2]: *** [examples/CMakeFiles/1a-lsr.dir/all] Error 2 > > Looking at the code it seems there i
Bug#934612: marked as done (libsoxr new version 0.1.3 available)
Your message dated Mon, 09 Sep 2019 18:49:12 + with message-id and subject line Bug#934612: fixed in libsoxr 0.1.3-1 has caused the Debian Bug report #934612, regarding libsoxr new version 0.1.3 available to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 934612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libsoxr Version: 0.1.2-3 There is a new 0.1.3 version available since february 2018 including those improvements * SIMD enhancements: SSE, AVX, Neon. * Improve support for clang, ARM, and cross-compilation. * Provide env. var. override of runtime parameters. It would be nice to get it uploaded to Debian --- End Message --- --- Begin Message --- Source: libsoxr Source-Version: 0.1.3-1 We believe that the bug you reported is fixed in the latest version of libsoxr, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libsoxr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Sep 2019 20:28:47 +0200 Source: libsoxr Architecture: source Version: 0.1.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 934612 Changes: libsoxr (0.1.3-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/watch: Use https protocol * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release. (Closes: #934612) * debian/control: - Bump Standards-Version. - Bump debhelper compat to 12. - Remove obsolete Pre-Depends. * debian/rules: Remove obsolete configure flag * debian/patches: Remove since applied upstream. * debian/copyright: Remove unused paragraph. Checksums-Sha1: 9c8077f8df0506fa9830befcb2ff8fc225b7b720 2146 libsoxr_0.1.3-1.dsc 32ea46b1a8c0c15f835422892d02fce8286aec3c 94384 libsoxr_0.1.3.orig.tar.xz 5751745fbb79ff77a2b3f77b894b7cc171a754ac 4216 libsoxr_0.1.3-1.debian.tar.xz Checksums-Sha256: 771dff17bcdde749db2d4352811c3430335af9c2c8862ac35d6d9c1f60ce3814 2146 libsoxr_0.1.3-1.dsc b111c15fdc8c029989330ff559184198c161100a59312f5dc19ddeb9b5a15889 94384 libsoxr_0.1.3.orig.tar.xz f16a56a2831bc985182aaf84b51988c1d2a8c4bb536326b121ab5992dfe34a94 4216 libsoxr_0.1.3-1.debian.tar.xz Files: f2805423dedb8761c78e7ad7a7520bb4 2146 libs optional libsoxr_0.1.3-1.dsc 3f16f4dcb35b471682d4321eda6f6c08 94384 libs optional libsoxr_0.1.3.orig.tar.xz 9db05e9c9a86812baef40951811f85e6 4216 libs optional libsoxr_0.1.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl12mnUACgkQafL8UW6n GZOorxAAkufy4FlxLThMrCNJMJ9fQm5lGDxdztaoF97p/oguZ9Jiw4lkpEzyaMkG sNhM9jLEjwgqboofSwf+S7go7KJIiQMFjmn5YWAXCukofRD4ntQ5MLU+V7rUE8HE CbuQ5xy5yXdVmO/Xcc17Ak1aZDSjzRCr5M5PEvzDLNNA+n6DJjnQ48ia05lyqYdF fSYU+eGSa08824Zy75mS/p1Ycgxfj29Ev8v00nWDAt6DNeA5K5DNTl4ZlK01IOoN pbHPDY7HB5UmlXdwyfTCK+0yxEMOX7R3f1ewzXsWuqzqAoYQP/9GE/SklDTkxdF2 bTO3sgQl2CwegZ9KFZI47+1G5f1RALqnpUloIL//aEPz8/LqHaJXeBhcmVV54HFw WC6quZp3GJ9D5huLzTJ+sBZMCoBfVXFIlwjJ5b66H/Hvh4oNUf/biMnMwQ7nZzFN PlgLQZr1yqmq2tiPDWZQmRWeJq3A9Cna4H5ducfmjvwE9O/KfWt8q67xzlo1bOI2 KV9Suvj2GHM2ibKlGh8CZZbCN8oQ/DWQfJfghdgunxPYeYFBG8/bVb4bHo4fI40v 4ZQqm3DU4yVxA3HiP2XN0kEK1I03WR8fazzfUFz3ELF2KfTafj/WHNVdinwbaiXF mm9f3WjKCce3o/zXKAu3uKVuttjK5eCGREFqInuC/rv7zbYX+1A= =3x+X -END PGP SIGNATURE End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#895151: marked as done (Guitarix update 35.2-2 (stretch) -> 36.1-1 (buster) improvement)
Your message dated Mon, 09 Sep 2019 19:22:12 +
with message-id
and subject line Bug#895151: fixed in guitarix 0.38.1-1
has caused the Debian Bug report #895151,
regarding Guitarix update 35.2-2 (stretch) -> 36.1-1 (buster) improvement
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
895151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: guitarix
Version: 36.1-1
While upgrading from the Stretch package (35.2-2) to the sid/buster one
(36.1-1), it doesn't update the libgxw0 and libgxwmm0 packages which are
needed by the Guitarix application.
Then, the application isn't fully functional since it requires those
libs to work with, and doesn't have those in the right version, then
missing the right versionned functions. Hence there are some errors
while using guitarix.
In d/control, adding to the binary "Package: guitarix" 's "Depends" '
field the following seems to fix the issue :
libgxw0 (>= ${source:Version}),
libgxwmm0 (>= ${source:Version}),
Please double check before applying.
Hope that helps.
Olivier
--- End Message ---
--- Begin Message ---
Source: guitarix
Source-Version: 0.38.1-1
We believe that the bug you reported is fixed in the latest version of
guitarix, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated guitarix package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 09 Sep 2019 21:00:58 +0200
Source: guitarix
Architecture: source
Version: 0.38.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 895151
Changes:
guitarix (0.38.1-1) unstable; urgency=medium
.
* Team upload.
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
.
[ Felipe Sateler ]
* Change maintainer address to debian-multime...@lists.debian.org
.
[ Víctor Cuadrado Juan ]
* Move to dh_missing --fail-missing as dh_install option is deprecated
* Add version dependency information to shlibs files (Closes: #895151)
* Remove --no-mod-lv2 from configure as not needed anymore
* Add --ladspa to configure as it's needed now
* Remove 02-libdl.patch as not needed anymore
* Add new Build-Depends on libboost-iostreams-dev
* Bump dh compat to 11, no changes needed
* Bump Std-Ver to 4.1.5, Added Rules-Requires-Root: no
* Update d/watch to version 4
* New upstream version 0.38.1
* Fix guitarix-doc files location
* Remove trailing whitespace in d/rules
.
[ Ondřej Nový ]
* Use debhelper-compat instead of debian/compat
* d/watch: Use https protocol
.
[ Sebastian Ramacher ]
* debian/control:
- Bump debhelper compat to 12.
- Bump Standards-Version.
* debian/gxw-glade.lintian-overrides: Override incorrect lintian error.
Checksums-Sha1:
a187c64dc88e8ff6f9e15164daa2c34882e13de5 2810 guitarix_0.38.1-1.dsc
b5c94337641f9e8a7c363c393a8b0b6b63a9ad4a 80768608 guitarix_0.38.1.orig.tar.xz
de0036eded9931d18b5853db302314132010a08a 13108 guitarix_0.38.1-1.debian.tar.xz
Checksums-Sha256:
8e9d39cc10fb65f7c8542071f6706fb227e6144ac5db0c931eaae66e57bfc656 2810
guitarix_0.38.1-1.dsc
00fda3e1ce1d5f1691665f9ff32bb3c9800381313d49b7c2e25618d0b3ed872f 80768608
guitarix_0.38.1.orig.tar.xz
a78c30caaf5830c533ac3bf93487d557bdef9258b2e65035b485bd29df53e6a7 13108
guitarix_0.38.1-1.debian.tar.xz
Files:
789aef6116348918add9ed5b4d2e650c 2810 sound optional guitarix_0.38.1-1.dsc
d9aec810bf164cbf040b298cb9c45d50 80768608 sound optional
guitarix_0.38.1.orig.tar.xz
79ab787d21a9ee32ea472a85466234a6 13108 sound optional
guitarix_0.38.1-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl12okQACgkQafL8UW6n
GZO/Ow//bWc88vuMvkRmkwXt7dKl6jFaqdrNg5fxSz3l9F8T3BFJvGr1d+WR9BkE
RMx77WnV0zMVDYSWnfxEjXAzQB29ifKT+b8LWrPH/94sMkMPNsh2xPOPFpYwoozA
XfXXhGrJGOh6/HUvVpfZMnyQBmWdCP6ajG2D/jcSsjK7hEvAgvQwTAYAP6nHw/Dp
BM7JK
Bug#920206: marked as done (Update devede to 4.12.0 - Upstream switched to GitLab)
Your message dated Mon, 09 Sep 2019 19:49:50 + with message-id and subject line Bug#920206: fixed in devede 4.15.0-1 has caused the Debian Bug report #920206, regarding Update devede to 4.12.0 - Upstream switched to GitLab to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: devede Please update to version 4.12.0. Upstream has switched to GitLab, so please fix the watch file and homepage. https://gitlab.com/rastersoft/devedeng http://www.rastersoft.com/programas/devede.html History of versions: version 4.12.0 (2018-06-28) * Now ensures that the audio bitrate is always a legal value version 4.11.0 (2018-05-01) * Added support for XFBurn * Added experimental support for 16:9 menues version 4.10.0 (2018-04-29) * Now, when using a custom audio in the menu, it will last the whole audio duration, not 30 seconds version 4.9.0 (2018-04-08) * Fixed a division by 0 when it is not possible to get the original aspect ratio * Added extra check for MSGFMT binary, needed to install Devede version 4.8.12 (2018-01-21) * Fixed the icons in the main window version 4.8.11 (2017-12-03) * Now shows the icon in wayland * Now sets transient for settings window version 4.8.10 (2017-11-26) * Removed minrate during second pass when using two-pass encoding because it fails with ffmpeg version 4.8.9 (2017-07-10) * Fixed bug when there are no CD burner installed version 4.8.8 (2017-02-07) * Fixed genisoimage bug with some locales version 4.8.7 (2017-01-29) * Allows to translate the "Play all" text in the DVD menu * Fixed mkisofs bug with some locales version 4.8.6 (2016-12-14) * Now ensures that the average bitrate is never smaller than the minimum bitrate * Now the matroska and divx files have the right extension version 4.8.5 (2016-11-24) * Fixed a bug when loading a project file (thanks to RecursiveProgrammer) * Updated the german translation version 4.8.4 (2016-11-03) * Allows to set if a movie is shown or not in the DVD menu from the main window version 4.8.3 (2016-10-16) * Fixed the problem fixed bitrate problem with FFMpeg and AVConv (thanks to Juniorsnet) version 4.8.2 (2016-09-24) * Fixed a problem when adding several subtitles to the same movie (thanks to Rocco Barisci) version 4.8.1 (2016-09-05) * Fixed a float value used for volume where it expected an integer --- End Message --- --- Begin Message --- Source: devede Source-Version: 4.15.0-1 We believe that the bug you reported is fixed in the latest version of devede, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 920...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated devede package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 09 Sep 2019 21:25:08 +0200 Source: devede Architecture: source Version: 4.15.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 920206 Changes: devede (4.15.0-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/control: Remove ancient X-Python3-Version field . [ Gabor Karsay ] * Update watch file, project moved to GitLab . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release. (Closes: #920206) * debian/control: - Bump debhelper compat to 12. - Bump Standards-Version. * debian/rules: Build with pybuild. * debian/: Remove xpm, upstream includes a svg. Checksums-Sha1: 0cb97f07ba8082cae78d92862926458f87909259 1997 devede_4.15.0-1.dsc 63143f3805ff4ed569796ae1a4fabf44d389d2ff 1889776 devede_4.15.0.orig.tar.gz 9cdc6da9738540821ad965dc21f04c18be81a562 4880 devede_4.15.0-1.debian.tar.xz Checks
Processed: severity of 933407 is important, severity of 933408 is important, severity of 933411 is important ...
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933450 933451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933451 933455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933455 933457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933457 933458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933458 933459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933459 933462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933462 933463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933463 933464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933464 933465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933465 933466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933466 933469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933469 933473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933473 933474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933474 933475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933475 933476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933476 933477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933477 933478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933478 933479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933479 934096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934096 934097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934097 934098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934098 934099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#923888: marked as done (goattracker FTCBFS: builds for the build architecture)
Your message dated Tue, 10 Sep 2019 12:35:22 + with message-id and subject line Bug#923888: fixed in goattracker 2.75-3 has caused the Debian Bug report #923888, regarding goattracker FTCBFS: builds for the build architecture to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 923888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: goattracker Version: 2.74+dfsg1-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap goattracker fails to cross build from source, because it does not pass cross tools to make. Using dh_auto_build mostly fixes that except for a few hard coded compiler invocations that need to be made substitutable. Please consider applying the attached patch. Helmut --- goattracker-2.74+dfsg1/debian/changelog +++ goattracker-2.74+dfsg1/debian/changelog @@ -1,3 +1,12 @@ +goattracker (2.74+dfsg1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) ++ Let dh_auto_build pass cross tools to make. ++ cross.patch: Make gcc substitutable. + + -- Helmut Grohne Tue, 06 Mar 2019 19:11:13 +0100 + goattracker (2.74+dfsg1-1) unstable; urgency=medium * debian/README.source: updated to also drop the *.exe files. --- goattracker-2.74+dfsg1/debian/patches/cross.patch +++ goattracker-2.74+dfsg1/debian/patches/cross.patch @@ -0,0 +1,23 @@ +--- goattracker-2.74+dfsg1.orig/src/makefile.common goattracker-2.74+dfsg1/src/makefile.common +@@ -41,16 +41,16 @@ + $(CXX) -DGT2RELOC -o $@ $^ $(LIBS) + + $(PREFIX)mod2sng$(SUFFIX): mod2sng.o bme/bme_end.o +- gcc -o $@ $^ ++ $(CC) -o $@ $^ + + $(PREFIX)ins2snd2$(SUFFIX): ins2snd2.o bme/bme_end.o +- gcc -o $@ $^ ++ $(CC) -o $@ $^ + + $(PREFIX)sngspli2$(SUFFIX): sngspli2.o bme/bme_end.o +- gcc -o $@ $^ ++ $(CC) -o $@ $^ + + $(PREFIX)betaconv$(SUFFIX): betaconv.o bme/bme_end.o +- gcc -o $@ $^ ++ $(CC) -o $@ $^ + + goattrk2.dat: player.s altplayer.s chargen.bin palette.bin cursor.bin goattrk2.bmp goattrk2.seq + bme/datafile $@ goattrk2.seq --- goattracker-2.74+dfsg1/debian/patches/series +++ goattracker-2.74+dfsg1/debian/patches/series @@ -1 +1,2 @@ makefile +cross.patch --- goattracker-2.74+dfsg1/debian/rules +++ goattracker-2.74+dfsg1/debian/rules @@ -17,8 +17,8 @@ build-stamp: dh_testdir - $(MAKE) -C src/bme CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" - $(MAKE) -C src CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" + dh_auto_build --sourcedirectory=src/bme -- CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" + dh_auto_build --sourcedirectory=src -- CFLAGS="$(CFLAGS)" CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)" touch $@ clean: --- End Message --- --- Begin Message --- Source: goattracker Source-Version: 2.75-3 We believe that the bug you reported is fixed in the latest version of goattracker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 923...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated goattracker package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Sep 2019 10:39:13 +0200 Source: goattracker Architecture: source Version: 2.75-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Packages Maintainers Changed-By: Gürkan Myczko Closes: 923888 Changes: goattracker (2.75-3) unstable; urgency=medium . * Apply dh_auto_build part of patch to fix FTCBFS. (Closes: 923888) Thanks Helmut Grohne for the patch. * Bump standards version to 4.4.0. Checksums-Sha1: 754fee6b27895a0292a1d87ef0048b37aa64ac74 1864 goattracker_2.75-3.dsc c26345c564818beefff18367402bc9247837cd2b 6512 goattracker_2.75-3.debian.tar.xz efde8e4f2e7a357576f76bc0e99a07785bfcac93 5808 goattracker_2.75-3_source.buildinfo Checksums-Sha256: a4eaeddd486aa3d994372674d3ce21e143413bf9cb516cbf9026e393a97cdb61 1864 goattra
Bug#598817: marked as done ([traverso] Crashes when opening file dialogs in KDE4)
Your message dated Tue, 10 Sep 2019 21:44:42 +0200 with message-id <20190910194442.ga4...@ramacher.at> and subject line Re: Bug#598817: [traverso] Crashes when opening file dialogs in KDE4 has caused the Debian Bug report #598817, regarding [traverso] Crashes when opening file dialogs in KDE4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 598817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: traverso Version: 0.49.2-1 Severity: important --- Please enter the report below this line. --- Traverso crashes when first starting in KDE4 environment with the following output in console (crash is catched and a dialog box is shown, then program is terminated): ---console output--- daniele@cougar:~$ traverso No Hardware specific optimizations in use Themer:: Using themefile: :/themes/TraversoLight/traversotheme.xml creating alsa driver ... default|default|512|3|44100|0|0|-|32bit configuring for 44100 Hz, period=512 frames (11,6 ms), buffer=3 periods ALSA: final selected sample format for capture: 32bit little-endian ALSA: cannot set period size to 512 frames for capture Creating Null Driver... Starting AudioDeviceThread. Running! Traverso(6296)/ KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-daniele/ksycoca4" Catched the SIGSEGV signal! Stopped Starting to shutdown AudioThread.. AudioDeviceThread finished, stopping driver ---end of console output--- If manually editing ~/.traverso/Traverso-DAW/Traverso.ini as stated in http://savannah.nongnu.org/bugs/?30401#comment0, traverso starts and works, but crashes in the same way every time a file dialog should be opened (eg.: Edit->Import audio or Project->Open Project->Select Project Dir. Still crashes starting with a clean user profile or without DE (xterm-only X session). Does not crash in a sid virtual machine running e17. Does not crash in xterm-only session if running with Qt's GTK+ theme/engine (using Raleigh GTK theme) or changing theme to Qt's GTK+ one while running (when this theme is selected GTK file dialog is shown). After this change all other Qt themes do NOT trigger the crash until program is closed. Unfortunately trying the same steps when running Traverso in a KDE4 session does not help (may be related to KDE font and color settings applied to GTK applications). --- System information. --- Architecture: amd64 Kernel: Linux 2.6.35-trunk-amd64 Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstablelinux.wuertz.org 500 unstableftp.debian.org 500 stable dl.google.com 102 experimentalwww.debian-multimedia.org 102 experimentalftp.debian.org --- Package information. --- Depends(Version) | Installed -+- libasound2 (>> 1.0.18) | 1.0.23-2 libc6 (>= 2.2.5) | 2.11.2-6 libfftw3-3 | 3.2.2-1 libflac8 (>= 1.2.1) | 1.2.1-3 libgcc1 (>= 1:4.1.1) | 1:4.4.4-17 libjack-jackd2-0 (>= 1.9.5~dfsg-14) | OR libjack-0.116| libmad0 (>= 0.15.1b-3) | 0.15.1b-5 libogg0 (>= 1.0rc3) | 1.2.0~dfsg-1 libqt4-xml (>= 4:4.5.3) | 4:4.6.3-2 libqtcore4 (>= 4:4.6.1) | 4:4.6.3-2 libqtgui4 (>= 4:4.5.3) | 4:4.6.3-2 libraptor1 (>= 1.4.19) | 1.4.21-2 librdf0 (>= 1.0.9) | 1.0.10-3 libsamplerate0 | 0.1.7-3 libsndfile1 (>= 1.0.20) | 1.0.21-3 libstdc++6(>= 4.1.1) | 4.4.4-17 libvorbis0a (>= 1.1.2) | 1.3.1-1 libvorbisenc2 (>= 1.1.2) | 1.3.1-1 libvorbisfile3(>= 1.1.2) | 1.3.1-1 libwavpack1 (>= 4.40.0) | 4.60.1-1 Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Version: 0.49.5-1 On 2010-10-02 13:06:39, Daniele Benucci wrote: > Package: traverso > Version: 0.49.2-1 > Severity: important > > --- Please enter the report below this line. --- > > Traverso crashes when first starting in KDE4 environment with the following > output in console (crash is catched and a dialog box is shown, then program >
Bug#852440: marked as done (lv2proc new upstream version)
Your message dated Tue, 10 Sep 2019 20:44:47 + with message-id and subject line Bug#852440: fixed in lv2proc 0.5.1-1 has caused the Debian Bug report #852440, regarding lv2proc new upstream version to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 852440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lv2proc Version: 0.5.0-2 Dear debian maintainers, it looks like there is a newer version of lv2proc : http://naspro.sourceforge.net/ HTH Olivier --- End Message --- --- Begin Message --- Source: lv2proc Source-Version: 0.5.1-1 We believe that the bug you reported is fixed in the latest version of lv2proc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 852...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated lv2proc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Sep 2019 22:09:29 +0200 Source: lv2proc Architecture: source Version: 0.5.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 852440 Changes: lv2proc (0.5.1-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/watch: Use https protocol . [ Sebastian Ramacher ] * New upstream release (Closes: #852440) * debian/: Bump debhelper compat to 12. * debian/control: Bump Standards-Version. * debian/patches: Remove, no longer needed. Checksums-Sha1: 84bb2067ae3b50754ffd71d87f5b570c8d978461 1957 lv2proc_0.5.1-1.dsc 1188783cffb0726c230d536c05ec31c813095c1a 96602 lv2proc_0.5.1.orig.tar.bz2 c373a770e233c60b85e79b478cf2c390df052b4e 2196 lv2proc_0.5.1-1.debian.tar.xz Checksums-Sha256: 0ece655707a5a8f49f928896da92b0cfd64892c713632aec2645c40c8d80c11d 1957 lv2proc_0.5.1-1.dsc 8c21a2a54a4c36f023e217ffa5debf34b88daa90cbe43549b05aa8e30c8d684c 96602 lv2proc_0.5.1.orig.tar.bz2 0bcfc1acdb1724ab98867bf5fba7149a4a691946067b55fb6809517c5c021e26 2196 lv2proc_0.5.1-1.debian.tar.xz Files: 3bec8300018ea0f1c3e4e936612940a3 1957 sound optional lv2proc_0.5.1-1.dsc ab05eca009dcf96ca093555b6536e65b 96602 sound optional lv2proc_0.5.1.orig.tar.bz2 a66d9b43b3818307c93635487aa955e0 2196 sound optional lv2proc_0.5.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl14AzoACgkQafL8UW6n GZPaEw//SsvyLQYurBZF0BFQYIFWq5yWm61fQOchsQ+2cegVIgeNhrcZxzQZqh18 ae5i4aXu8XNQcZvmoX7X+v9VAEbajlj5CYu/a4VeTrqHZwY9M79QccY+Dc/wLd5m GdBZOp+4ROx4lGFdujK0ruX37mKxuI3FzoD+IwqPpHQe8l06jneuRQLkmZb1EyT3 n1Vdv5+sf5u/6I+jiEpMagjCMedGhuKZyrOo494J8v+ncqlbJGWABFfIq9LbNqQO UFmaHc6zZVkZ0HM6M4sAqZS9neSL87sr4HB58sUU55oJwkoq79KgLFUfsKzZwOS/ 535rjdXZOSW3sUSEPHFvDsalV1M/A66ICMZtDgKUv2TI+6cq9wlgQIaTQB5htjbB J1yHVRAzeAeE3+UZWI4wN9kfDPE8KArwr49b0zGarlQABkwX01jEy7RuP/fff+Go c2tdFADn/8ax9XZ7r5PRGQwgoXXKHdgV4lQJvBisAnJqevOQvL6psE1mDeIDhkfD q5f/esKd9ManCdwlC7vWM8PkgPjl9xz0xHI2PaUxenWR3IAGWIw/MBqlOnVe94eL th98OZc+8G+U5Z4eZYz0iUp5wEoMRGnILDOKkIsz+VUr9i4scNt6f2pBAftTN7w2 xkGWG/vdGAXwb75GASfuxu83UFcH7eeaB47ADTbTmmADdTPyhNA= =XWU+ -END PGP SIGNATURE End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#916286: marked as done (traverso: baseline violation on i386)
Your message dated Tue, 10 Sep 2019 20:46:32 + with message-id and subject line Bug#916286: fixed in traverso 0.49.6-1 has caused the Debian Bug report #916286, regarding traverso: baseline violation on i386 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: traverso Version: 0.49.4-2 Severity: serious SSE is not part of the i386 baseline. Even worse is that when built on binet -m3dnow is passed on gcc, this is not supported by any modern CPU. --- End Message --- --- Begin Message --- Source: traverso Source-Version: 0.49.6-1 We believe that the bug you reported is fixed in the latest version of traverso, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated traverso package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Sep 2019 21:31:48 +0200 Source: traverso Architecture: source Version: 0.49.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 916286 939684 Changes: traverso (0.49.6-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org * d/changelog: Remove trailing whitespaces . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Dmitry Eremin-Solenikov ] * d/rules: fix baseline CPU instructions violation (Closes: #916286) * d/rules: stop overriding dh_install . [ Olivier Humbert ] * debian/control: http -> https. * debian/copyright: adding myself to the debian packaging copyright field. * debian/traverso.desktop: adding comments and French. . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release * debian/control: - Bump Standards-Version - Bump debhelper compat to 12 * debian/rules: Set optimization flags for amd64. Thanks to Helmut Grohne for the patch. (Closes: #939684) Checksums-Sha1: 02b0b999fa89f07f0049817e64132739e29e70f8 2204 traverso_0.49.6-1.dsc 40c8f5cd86e73e65d5a9c63953bf5dc7ad8685bf 1511714 traverso_0.49.6.orig.tar.gz 75a8804bc5aaa4727669959351f429275b6664ab 10924 traverso_0.49.6-1.debian.tar.xz Checksums-Sha256: 549e50b16a61eecf2e26e43f7570dd59199140490a40f791836ebe8a8809df13 2204 traverso_0.49.6-1.dsc f850b88cbb64529655514b7cfe01c56133e21929374b3e3b90813bc227eac789 1511714 traverso_0.49.6.orig.tar.gz 54cbf4e0cc21b781ec09707e21f2604765df0c86286c461e7740f69cd83f3c32 10924 traverso_0.49.6-1.debian.tar.xz Files: 95d91e7b0eb5e8b3a6c855c4c6bc5a13 2204 sound optional traverso_0.49.6-1.dsc ac4bf93a690533b2121c2d4e4a7f556b 1511714 sound optional traverso_0.49.6.orig.tar.gz bbf454f35712e1a968bf5142fd207b87 10924 sound optional traverso_0.49.6-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl13/UEACgkQafL8UW6n GZO7bQ/+OtWo6WZghhD20jCfJvVC/wdmCl5PthN5PVZewok/1Zyi3ASpg9b+7Bwu wy/mtgBGLcww6O8aFnvhMJM87QlZfGBzqJoSOyrDWV+6j20SfITwbVdWkqig2yA9 g1iF7aCwi8De8d6nwVq64b5TpcM2poUfOLNmwOZomVsBqzWMZ3qGRC0SrrLpm9+F br8y/aXXarsz+MDOjoZ0fRsJ7/uFkT5N1xaPmBvG0zuNpJuGc/jD66O2LSkTqPRp UfTU6/7NUdQrVrIan/SHFssVrFKb0HwjJyBh6WYPQMdVt8/A36NLrWpRXTauNrsY 97nJvOtD5pCATmG7d3wAaTaDuivWFi3d57Nl+Du+A+hiN2vFVsbmFrsEOD+fjmvo LkY3n2ZhMpop5wAC/FlUKJ25JI6j/NcU0JBk1aUVKYQwqgaJ7PqBETEyUUlASQaL KnHTUo/oZENVmlrfipl0+3gMPclaR7+4FsMSZKyaM/5az1MF8YcLKV83tIuPYJFp ccpZrOyS8lUgOfX91HbayH9Pzmwf52rPLE0Dy2YfRT/+l8Pj8xlLcWZHr43LTOMl 6V4ey7ZMQDjr7ZIThEmdpaPij4SlUaXwYlS3qtGoFOlcv5EjSSID2LoWyCYhvQ6m 248JR9VeOpGP5BnTAnRbEKC/yx/nBSSc72YUYrSPQgejnXU33I0= =kuYS -END PGP SIGNATURE End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multime
Bug#939684: marked as done (traverso FTCBFS: detects compiler flags from the current cpu)
Your message dated Tue, 10 Sep 2019 20:46:33 + with message-id and subject line Bug#939684: fixed in traverso 0.49.6-1 has caused the Debian Bug report #939684, regarding traverso FTCBFS: detects compiler flags from the current cpu to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 939684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: traverso Version: 0.49.5-3 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs traverso fails to cross build from source from amd64 to non-amd64, because it tries to detect compiler flags from the current cpu. That makes it pass e.g. -msse to an arm compiler. The attached patch disables the detection and adds back some flags for amd64 explicitly. Doing so also fixes #916286. It also improves reproducibility of the package. Further flags can be added to debian/rules by checking DEB_HOST_* variables without compromising base lines or reproducibility as needed. Please consider using or extending the attached patch. Helmut diff --minimal -Nru traverso-0.49.5/debian/changelog traverso-0.49.5/debian/changelog --- traverso-0.49.5/debian/changelog2018-05-18 17:49:06.0 +0200 +++ traverso-0.49.5/debian/changelog2019-09-07 19:45:59.0 +0200 @@ -1,3 +1,11 @@ +traverso (0.49.5-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Don't let the build system detect optimization flags based on the current +cpu. (Closes: #-1) + + -- Helmut Grohne Sat, 07 Sep 2019 19:45:59 +0200 + traverso (0.49.5-3) unstable; urgency=medium * Team upload. diff --minimal -Nru traverso-0.49.5/debian/rules traverso-0.49.5/debian/rules --- traverso-0.49.5/debian/rules2017-10-11 09:03:09.0 +0200 +++ traverso-0.49.5/debian/rules2019-09-07 19:45:59.0 +0200 @@ -1,9 +1,13 @@ #!/usr/bin/make -f -DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) +include /usr/share/dpkg/architecture.mk ifneq ($(DEB_HOST_ARCH_OS),linux) cmake_extra_args += -DWANT_ALSA=OFF endif +ifeq ($(DEB_HOST_ARCH_CPU),amd64) +export DEB_CPPFLAGS_MAINT_APPEND=-DSSE_OPTIMIZATIONS -DUSE_X86_64_ASM +export DEB_CXXFLAGS_MAINT_APPEND=-msse -mfpmath=sse +endif export DEB_LDFLAGS_MAINT_APPEND=-Wl,--no-undefined -Wl,--as-needed export DEB_BUILD_MAINT_OPTIONS=hardening=+all @@ -18,6 +22,7 @@ dh_auto_configure -- \ -DUSE_SYSTEM_SLV2_LIBRARY=ON \ -DWANT_MP3_ENCODE=ON \ + -DDETECT_HOST_CPU_FEATURES=OFF \ $(cmake_extra_args) override_dh_install: --- End Message --- --- Begin Message --- Source: traverso Source-Version: 0.49.6-1 We believe that the bug you reported is fixed in the latest version of traverso, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated traverso package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Sep 2019 21:31:48 +0200 Source: traverso Architecture: source Version: 0.49.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 916286 939684 Changes: traverso (0.49.6-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org * d/changelog: Remove trailing whitespaces . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Dmitry Eremin-Solenikov ] * d/rules: fix baseline CPU instructions violation (Closes: #916286) * d/rules: stop overriding dh_install . [ Olivier Humbert ] * debian/control: http -> https. * debian/copyright: adding myself to the debian packaging copyright field. * debian/traverso.desktop: adding comments and French. . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release * debian/control: - Bump Standards-Version - Bump debhelper compat to 12 * debi
Bug#915329: marked as done (gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1)
Your message dated Wed, 11 Sep 2019 17:35:00 +
with message-id
and subject line Bug#915329: fixed in gigedit 1.1.1-1
has caused the Debian Bug report #915329,
regarding gigedit FTBFS with libgtkmm-3.0-dev 3.24.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
915329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gigedit
Version: 1.1.0-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gigedit.html
...
In file included from builtinpix.cpp:2:
../compat.h: In constructor 'HBox::HBox()':
../compat.h:140:41: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
HBox() : Gtk::Box(Gtk::Orientation::HORIZONTAL) {}
^~
../compat.h: In constructor 'VBox::VBox()':
../compat.h:145:41: error: 'VERTICAL' is not a member of 'Gtk::Orientation'
VBox() : Gtk::Box(Gtk::Orientation::VERTICAL) {}
^~~~
../compat.h: In constructor 'HButtonBox::HButtonBox()':
../compat.h:150:53: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
HButtonBox() : Gtk::ButtonBox(Gtk::Orientation::HORIZONTAL) {}
^~
../compat.h: In constructor 'HScale::HScale()':
../compat.h:155:45: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
HScale() : Gtk::Scale(Gtk::Orientation::HORIZONTAL) {}
^~
../compat.h: In constructor 'HScale::HScale(const
Glib::RefPtr&)':
../compat.h:156:104: error: 'HORIZONTAL' is not a member of 'Gtk::Orientation'
HScale(const Glib::RefPtr& adjustment) :
Gtk::Scale(adjustment, Gtk::Orientation::HORIZONTAL)
...
--- End Message ---
--- Begin Message ---
Source: gigedit
Source-Version: 1.1.1-1
We believe that the bug you reported is fixed in the latest version of
gigedit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 915...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated gigedit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 11 Sep 2019 19:07:13 +0200
Source: gigedit
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 915329
Changes:
gigedit (1.1.1-1) unstable; urgency=medium
.
[ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* Use debhelper-compat instead of debian/compat
.
[ Felipe Sateler ]
* Change maintainer address to debian-multime...@lists.debian.org
.
[ Sebastian Ramacher ]
* New upstream release
- Fix build against newer versions of libgtkmm. (Closes: #915329)
* debian/control:
- Bump debhelper compat to 12.
- Bump Standards-Version
- Add autoconf-archive to B-Ds to link with pthread
- Bump libgig-dev B-D to >= 4.2
* debian/patches:
- Refreshed.
- Link with pthreads.
Checksums-Sha1:
e1eecf77e3e69618bde3a77d0002ee23b799063f 2115 gigedit_1.1.1-1.dsc
4c626af9cb3da2ba5dc142612d0b537c72d4e90d 1146369 gigedit_1.1.1.orig.tar.bz2
cc71133ceb127b1fd1d092f9d96ecf85bc1d0dea 6604 gigedit_1.1.1-1.debian.tar.xz
Checksums-Sha256:
a4a4b71de76d49ded1bcec9bc2ddd2987d6b2e6722ce4010ae4f7c4e587cec0a 2115
gigedit_1.1.1-1.dsc
2b77069302f8721fd614ae4e3ca364f1977731deb166bf5af00d389e9908ab21 1146369
gigedit_1.1.1.orig.tar.bz2
bd48e6cc9d180f6b837096f963b5f2bb4c35ece6f6e82f2698a25464b4ab3353 6604
gigedit_1.1.1-1.debian.tar.xz
Files:
a094cbd56d8c096129df10c4ddd5238c 2115 sound optional gigedit_1.1.1-1.dsc
2597cfddbceb28f5e764929e6c9755ab 1146369 sound optional
gigedit_1.1.1.orig.tar.bz2
d36b0c62cdfb4203a6e10f1adb30f591 6604 sound optional
gigedit_1.1.1-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6
Bug#914901: marked as done (qsampler FTCBFS: uses the build architecture qmake)
Your message dated Wed, 11 Sep 2019 18:34:15 + with message-id and subject line Bug#914901: fixed in qsampler 0.5.6-1 has caused the Debian Bug report #914901, regarding qsampler FTCBFS: uses the build architecture qmake to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 914901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qsampler Version: 0.5.0-1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap qsampler fails to cross build from source, because its ./configure discovers the build architecture qmake. That's due to using AC_PATH_PROG rather than AC_PATH_TOOL. The attached patch fixes that and makes qsampler cross buildable. Please consider applying the attached patch. Helmut --- qsampler-0.5.0.orig/configure.ac +++ qsampler-0.5.0/configure.ac @@ -202,12 +202,12 @@ ac_errmsg="not found in current PATH. Maybe QT development environment isn't available." if test "x$ac_qt4" = "xyes"; then - AC_PATH_PROG(ac_qmake, qmake-qt4, [no], $ac_path) + AC_PATH_TOOL(ac_qmake, qmake-qt4, [no], $ac_path) else - AC_PATH_PROG(ac_qmake, qmake-qt5, [no], $ac_path) + AC_PATH_TOOL(ac_qmake, qmake-qt5, [no], $ac_path) fi if test "x$ac_qmake" = "xno"; then - AC_PATH_PROG(ac_cv_qmake, qmake, [no], $ac_path) + AC_PATH_TOOL(ac_cv_qmake, qmake, [no], $ac_path) ac_qmake=$ac_cv_qmake fi if test "x$ac_qmake" = "xno"; then --- End Message --- --- Begin Message --- Source: qsampler Source-Version: 0.5.6-1 We believe that the bug you reported is fixed in the latest version of qsampler, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated qsampler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 11 Sep 2019 20:11:03 +0200 Source: qsampler Architecture: source Version: 0.5.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 914901 Changes: qsampler (0.5.6-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release. - Use AC_PATH_TOOL (Closes: #914901) * debian/control: - Bump debhelper compat to 12 - Bump Standards-Version * debian/copyright: Add appdata paragraph. Checksums-Sha1: 9665a327a4037c7335fa3f43a9f62412d6e28609 2129 qsampler_0.5.6-1.dsc 8a8d386790204db883fbd9bbe18496040301c3fe 260607 qsampler_0.5.6.orig.tar.gz f8a9cdb5370130ee19511b2c9755bc03db2d5c24 4864 qsampler_0.5.6-1.debian.tar.xz Checksums-Sha256: d33154932bd54201c763aa042a3fa7a2483c40f0097b0a245befc3f8fa268833 2129 qsampler_0.5.6-1.dsc 7a41f9a168dc8a316520377aea28b040de0fd54217b9b71d9f4c56a9fcafa253 260607 qsampler_0.5.6.orig.tar.gz 844ea263871762da8a75ed7d2c4482941705644b7d1f4a81c77b2e87e3c4696b 4864 qsampler_0.5.6-1.debian.tar.xz Files: b040465165b7eadcd6977fa78322c2db 2129 sound optional qsampler_0.5.6-1.dsc 169401d29fb3b3d438dce5bb094efe08 260607 sound optional qsampler_0.5.6.orig.tar.gz 117c0f818a4600d2d823f023bbe99cdd 4864 sound optional qsampler_0.5.6-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl15OhAACgkQafL8UW6n GZMrKQ//Q6OKiXJojUsf71XHuFa3dz2TkbJQWal/ZngqYANZyWQaCuT+wX+CrKLJ ptHw7fzDRYO21r0bcAw7/yy6+cSiikBMFxnZJpsLBATzyWfdTksCYIZwfPHw627P dvuqRi+5EfLsbWfpz24H/Gncy2ZRtGbUjyrcEESluyxAY4tJ+GkAtmaXRMnXwAtg oFrjEQMjXNYXXZchfM/UW6AHB6xExkF8rE/nF8tC7sxWDmOlKxPYUCZcZwzxEgBm jSgCQ3aZ6+pwAuUZAj0WcoYYowRDmDm5zw8NT9VVhSlQR8w191ocnvueLBdne+pN +bygRyI1KLRsaKOyUGzWsaTQ4Ks5KjuwJmZiclILNIMwH5mwm5Gq6kIiQh9WxV8D BOAaaMY8X8QbXoLDn9iEqeTWmQacmyIxdE3K7XKpxBTWEZsMXF0KAzelTtZw9eb1 den5aIfQNJQNfVmBKFRKO
Processed: Bug#875047 marked as pending in midisnoop
Processing control commands: > tag -1 pending Bug #875047 [src:midisnoop] [midisnoop] Future Qt4 removal from Buster Added tag(s) pending. -- 875047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#937045 marked as pending in midisnoop
Processing control commands: > tag -1 pending Bug #937045 [src:midisnoop] midisnoop: Python2 removal in sid/bullseye Added tag(s) pending. -- 937045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: revert libclalsadrv-dev back to Architecture: any
Processing control commands: > affects -1 + src:aliki src:ams Bug #940148 [libclalsadrv-dev] revert libclalsadrv-dev back to Architecture: any Added indication that 940148 affects src:aliki and src:ams -- 940148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#875168: marked as done ([radium-compressor] Future Qt4 removal from Buster)
Your message dated Sun, 15 Sep 2019 19:34:08 + with message-id and subject line Bug#875168: fixed in radium-compressor 0.5.1+git20190909-1 has caused the Debian Bug report #875168, regarding [radium-compressor] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 875168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: radium-compressor Version: 0.5.1-3 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: radium-compressor Source-Version: 0.5.1+git20190909-1 We believe that the bug you reported is fixed in the latest version of radium-compressor, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated radium-compressor package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 15 Sep 2019 21:16:38 +0200 Source: radium-compressor Architecture: source Version: 0.5.1+git20190909-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 875168 Changes: radium-compressor (0.5.1+git20190909-1) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream snapshot - Switch to Qt 5 (Closes: #875168) * debian/: Bump debhelper compat to 12 * debian/control: - Bump Standards-Version - Add B-Ds on ladspa-sdk and liblo-dev Checksums-Sha1: 21948aec9e6f32f182031372558954c5244a03ce 2188 radium-compressor_0.5.1+git20190909-1.dsc 9be42d47bc8c895a5f15c01b0c6360e7abc6d1b2 161184 radium-compressor_0.5.1+git20190909.orig.tar.gz d294de49f01ae6a8320bbf8bdea5886a2e70b410 3040 radium-compressor_0.5.1+git20190909-1.debian.tar.xz Checksums-Sha256: 2c0f9e918100b0c4286f7be30d17e2eac567bbe5887c4223e658f3869355a449 2188 radium-compressor_0.5.1+git20190909-1.dsc 9b40e48dd86a36ff9cdcbab71e88add8a2ae0b4b8
Processed: Re: [stretchplayer] Future Qt4 removal from Buster
Processing control commands: > tags -1 + patch Bug #875195 [src:stretchplayer] [stretchplayer] Future Qt4 removal from Buster Added tag(s) patch. -- 875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#875195 marked as pending in stretchplayer
Processing control commands: > tag -1 pending Bug #875195 [src:stretchplayer] [stretchplayer] Future Qt4 removal from Buster Added tag(s) pending. -- 875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed (with 1 error): guile-2.0 will be removed from bullseye
Processing commands for cont...@bugs.debian.org: > # These bugs have been open for years. While I may not, I may try to > # get guile-2.0 removed as soon as a month or two from now -- it's > # unfortunate that we had to keep it in buster. Please do something > # soon if you can. > # Broken Depends: > # autogen: autogen > severity 885189 serious Bug #885189 [src:autogen] autogen: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # denemo: denemo > severity 885190 serious Bug #885190 [src:denemo] denemo: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # geda-gaf: geda-gattrib > # geda-gnetlist > # geda-gschem > # geda-gsymcheck > # geda-utils > # libgeda-dev > # libgeda42 > severity 885195 serious Bug #885195 [src:geda-gaf] geda-gaf: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # graphviz: libgv-guile > severity 885198 serious Failed to set severity of Bug 885198 to serious: Not altering archived bugs; see unarchive. > # make-dfsg: make-guile > severity 885213 serious Bug #885213 [src:make-dfsg] make-dfsg: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # mcron: mcron > severity 885215 serious Bug #885215 [src:mcron] mcron: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # remake: remake > severity 885237 serious Bug #885237 [src:remake] remake: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # rumor: rumor > severity 885238 serious Bug #885238 [src:rumor] rumor: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # weechat: weechat-guile > severity 885235 serious Bug #885235 [src:weechat] weechat: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # xbindkeys: xbindkeys > severity 885239 serious Bug #885239 [src:xbindkeys] xbindkeys: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # Broken Build-Depends: > # freehdl: guile-2.0 > severity 885188 serious Bug #885188 [src:freehdl] freehdl: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > # libmatheval: guile-2.0-dev > severity 885212 serious Bug #885212 [src:libmatheval] libmatheval: please migrate to guile-2.2 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 885188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885188 885189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885189 885190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885190 885195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885195 885212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885212 885213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885213 885215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885215 885235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885235 885237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885237 885238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885238 885239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885239 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging 885189, tagging 885190, found 885190 in 2.2.0-1, found 885195 in 1:1.8.2-11, tagging 885195 ...
Processing commands for cont...@bugs.debian.org:
> tags 885189 + sid bullseye experimental
Bug #885189 {Done: Andreas Metzler } [src:autogen]
autogen: please migrate to guile-2.2
Added tag(s) sid, experimental, and bullseye.
> tags 885190 + sid bullseye
Bug #885190 [src:denemo] denemo: please migrate to guile-2.2
Added tag(s) bullseye and sid.
> found 885190 2.2.0-1
Bug #885190 [src:denemo] denemo: please migrate to guile-2.2
Marked as found in versions denemo/2.2.0-1.
> found 885195 1:1.8.2-11
Bug #885195 [src:geda-gaf] geda-gaf: please migrate to guile-2.2
Marked as found in versions geda-gaf/1:1.8.2-11.
> tags 885195 + sid bullseye
Bug #885195 [src:geda-gaf] geda-gaf: please migrate to guile-2.2
Added tag(s) sid and bullseye.
> found 885215 1.0.8-1
Bug #885215 [src:mcron] mcron: please migrate to guile-2.2
Marked as found in versions mcron/1.0.8-1.
> tags 885215 + sid bullseye
Bug #885215 [src:mcron] mcron: please migrate to guile-2.2
Added tag(s) sid and bullseye.
> found 885213 4.2.1-1.2
Bug #885213 [src:make-dfsg] make-dfsg: please migrate to guile-2.2
Marked as found in versions make-dfsg/4.2.1-1.2.
> tags 885213 + sid bullseye
Bug #885213 [src:make-dfsg] make-dfsg: please migrate to guile-2.2
Added tag(s) bullseye and sid.
> found 885238 1.0.5-2.1
Bug #885238 [src:rumor] rumor: please migrate to guile-2.2
Marked as found in versions rumor/1.0.5-2.1.
> tags 885238 + sid bullseye
Bug #885238 [src:rumor] rumor: please migrate to guile-2.2
Added tag(s) sid and bullseye.
> found 885237 4.1+dbg1.3~dfsg.1-2
Bug #885237 {Done: Dima Kogan } [src:remake] remake: please
migrate to guile-2.2
Marked as found in versions remake/4.1+dbg1.3~dfsg.1-2.
> tags 885237 + sid bullseye
Bug #885237 {Done: Dima Kogan } [src:remake] remake: please
migrate to guile-2.2
Added tag(s) bullseye and sid.
> found 885235 2.3-1
Bug #885235 [src:weechat] weechat: please migrate to guile-2.2
Marked as found in versions weechat/2.3-1.
> tags 885235 + sid bullseye
Bug #885235 [src:weechat] weechat: please migrate to guile-2.2
Added tag(s) bullseye and sid.
> found 885239 1.8.6-1
Bug #885239 [src:xbindkeys] xbindkeys: please migrate to guile-2.2
Marked as found in versions xbindkeys/1.8.6-1.
> tags 885239 + sid bullseye
Bug #885239 [src:xbindkeys] xbindkeys: please migrate to guile-2.2
Added tag(s) bullseye and sid.
> found 885188 0.0.8-2.2
Bug #885188 [src:freehdl] freehdl: please migrate to guile-2.2
Marked as found in versions freehdl/0.0.8-2.2.
> tags 885188 + sid bullseye
Bug #885188 [src:freehdl] freehdl: please migrate to guile-2.2
Added tag(s) bullseye and sid.
> found 885212 1.1.11+dfsg-3
Bug #885212 [src:libmatheval] libmatheval: please migrate to guile-2.2
Marked as found in versions libmatheval/1.1.11+dfsg-3.
> tags 885212 + sid bullseye
Bug #885212 [src:libmatheval] libmatheval: please migrate to guile-2.2
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
885188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885188
885189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885189
885190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885190
885195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885195
885212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885212
885213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885213
885215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885215
885235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885235
885237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885237
885238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885238
885239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#875195: marked as done ([stretchplayer] Future Qt4 removal from Buster)
Your message dated Mon, 23 Sep 2019 21:37:04 + with message-id and subject line Bug#875195: fixed in stretchplayer 0.503-4 has caused the Debian Bug report #875195, regarding [stretchplayer] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 875195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stretchplayer Version: 0.503-3 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: stretchplayer Source-Version: 0.503-4 We believe that the bug you reported is fixed in the latest version of stretchplayer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Muehlenhoff (supplier of updated stretchplayer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Sep 2019 22:58:56 +0200 Source: stretchplayer Architecture: source Version: 0.503-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Moritz Muehlenhoff Closes: 875195 Changes: stretchplayer (0.503-4) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Change Format URL to correct one * d/control: Deprecating priority extra as per policy 4.0.1 * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Reiner Herrmann ] * Port to Qt5 (Closes: #875195) . [ Moritz Mühlenhoff ] * Debhelper 10, standards version 4.4.0 Checksums-Sha1: 4c1e4d78300729a4a9f37d5d948662fad9d55f8f 2116 stretchplayer_0.503-4.dsc 8dcc1f34f13f57b6d0a2bcde9ce54f816119012f 3912 stretchplayer_0.503-4.debian.tar.xz 9d76b7c1d96f7cb254273b02ffcbb16c3bf8cf2e 11951 stretchplayer_0.503-4_amd64.buildinfo Checksums-Sha256: 9b05f8c11681c6a3f74a933903b6bcc89dbfcac4c541612e955ebc91751aa130 2116 stretchplayer_0.503-4.dsc f757819b16ab101b28dedfe1957f41f27994e126a3d592973dd7793f19fc0b56 3912 stretchplayer_0.503-4.debian.tar.xz 0c521512c7b5685bc268722f5635e83ddb08a2b842eeb666a1427aed6221654d 11951 stretchplayer_0.503-4_amd64.buildinfo Files: 0bf48cdb8b10aea30641857780b6b324 2116 sound optional stretchplayer_0.503-4.dsc b009648334e33b
Processed: Bug#875047 marked as pending in midisnoop
Processing control commands: > tag -1 pending Bug #875047 [src:midisnoop] [midisnoop] Future Qt4 removal from Buster Ignoring request to alter tags of bug #875047 to the same tags previously set -- 875047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#937045 marked as pending in midisnoop
Processing control commands: > tag -1 pending Bug #937045 [src:midisnoop] midisnoop: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #937045 to the same tags previously set -- 937045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#875047: marked as done ([midisnoop] Future Qt4 removal from Buster)
Your message dated Sun, 29 Sep 2019 13:04:05 + with message-id and subject line Bug#875047: fixed in midisnoop 0.1.2+git20141108.bc30f600187e-1 has caused the Debian Bug report #875047, regarding [midisnoop] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 875047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875047 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: midisnoop Version: 0.1.2~repack0-5 Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt4-removal Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 as [announced] in: [announced] <https://lists.debian.org/debian-devel-announce/2017/08/msg6.html> Currently Qt4 has been dead upstream and we are starting to have problems maintaining it, like for example in the [OpenSSL 1.1 support] case. [OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522> In order to make this move, all packages directly or indirectly depending on the Qt4 libraries have to either get ported to Qt5 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a Qt5 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a Qt5 port that is not yet packaged, consider packaging it - if both the Qt4 and the Qt5 versions already coexist in the Debian archives, consider removing the Qt4 version = Porting = Some of us where involved in various Qt4 to Qt5 migrations [migration] and we know for sure that porting stuff from Qt4 to Qt5 is much much easier and less painful than it was from Qt3 to Qt4. We also understand that there is still a lot of software still using Qt4. Don't forget to take a look at the C++ API changes page [apichanges] whenever you start porting your application. [migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html [apichanges] http://doc.qt.io/qt-5/sourcebreaks.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org The removal is being tracked in <https://wiki.debian.org/Qt4Removal> Lisandro, on behalf of the Qt4 maintainers --- End Message --- --- Begin Message --- Source: midisnoop Source-Version: 0.1.2+git20141108.bc30f600187e-1 We believe that the bug you reported is fixed in the latest version of midisnoop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 875...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Eremin-Solenikov (supplier of updated midisnoop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Sep 2019 14:40:54 +0300 Source: midisnoop Architecture: source Version: 0.1.2+git20141108.bc30f600187e-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dmitry Eremin-Solenikov Closes: 875047 937045 Changes: midisnoop (0.1.2+git20141108.bc30f600187e-1) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Dmitry Eremin-Solenikov ] * New upstream version 0.1.2+git20141108.bc30f600187e * Update to qt5 (Closes: #875047) * Refresh debian patches * Add 0005-src-engine.h-another-qt5-fix.patch to fix compilation with qt5 * d/gbp.conf: disable pristine tar for snapshot builds * d/control: Bump Standards-Version to 4.4.0 (no changes needed) * Switch to python3 (Closes: #937045) * d/control: add myself to uploaders Checksums-Sha1: 42614790221f6900b57a1980376b41d8820a6e2b 2264 midisnoop_0.1.2+git20141108.bc30f600187e-1.dsc 0001b6cb5b64b1fbc59ae318425af6b92324e659 47663 midisnoop_0.1.2+git20141108.bc30f600187e.orig.tar.gz 41996dd7816e3b8eb92c99354ff5353998493ff3 5628 midisnoop_0.1.2+git
Bug#937045: marked as done (midisnoop: Python2 removal in sid/bullseye)
Your message dated Sun, 29 Sep 2019 13:04:05 + with message-id and subject line Bug#937045: fixed in midisnoop 0.1.2+git20141108.bc30f600187e-1 has caused the Debian Bug report #937045, regarding midisnoop: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 937045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937045 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:midisnoop Version: 0.1.2~repack0-7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:midisnoop If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: midisnoop Source-Version: 0.1.2+git20141108.bc30f600187e-1 We believe that the bug you reported is fixed in the latest version of midisnoop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Eremin-Solenikov (supplier of updated midisnoop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Sep 2019 14:40:54 +0300 Source: midisnoop Architecture: source Version: 0.1.2+git20141108.bc30f600187e-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Dmitry Eremin-Solenikov Closes: 875047 937045 Changes: midisnoop (0.1.2+git20141108.bc30f600187e-1) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Set Vcs-* to salsa.debian.org . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Dmitry Eremin-Solenikov ] * New upstream version 0.1.2+git20141108.bc30f600187e * Update to qt5 (Closes: #875047) * Refresh debian patches * Add 0005-src-engine.h-another-qt5-fix.patch to fix compilation with qt5
Processed: closing 894012
Processing commands for cont...@bugs.debian.org: > close 894012 0.1.2~repack0-7 Bug #894012 [midisnoop] Midisnoop package in stable contains no binary. Marked as fixed in versions midisnoop/0.1.2~repack0-7. Bug #894012 [midisnoop] Midisnoop package in stable contains no binary. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 894012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#922026: marked as done (fasttracker2 -- Not fit for next release)
Your message dated Tue, 01 Oct 2019 09:04:06 + with message-id and subject line Bug#922026: fixed in fasttracker2 1.00-1 has caused the Debian Bug report #922026, regarding fasttracker2 -- Not fit for next release to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 922026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fasttracker2 Severity: critical Pseudo-Bug to keep fasttracker2 out of testing so it does not end up in the next release. Upstream author finds the software too buggy yet for release, so we'll wait until he agrees to have it released as stable. --- End Message --- --- Begin Message --- Source: fasttracker2 Source-Version: 1.00-1 We believe that the bug you reported is fixed in the latest version of fasttracker2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 922...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gürkan Myczko (supplier of updated fasttracker2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 01 Oct 2019 09:32:45 +0200 Source: fasttracker2 Architecture: source Version: 1.00-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Gürkan Myczko Closes: 922026 Changes: fasttracker2 (1.00-1) unstable; urgency=medium . * New upstream version. (Closes: #922026) Checksums-Sha1: 39da09091a72fe12cd61ef249badb652b397ccd4 1898 fasttracker2_1.00-1.dsc 2338dae347eb8487c19a887f0f2b9e8dddb68201 337520 fasttracker2_1.00.orig.tar.xz fdbfbf81193810aeed1ccf4662f8652af87922ba 10560 fasttracker2_1.00-1.debian.tar.xz c0ebafb50a943591a01978422aa7e5b5b052f575 5391 fasttracker2_1.00-1_source.buildinfo Checksums-Sha256: d53763d499ff3039fd48918bdd14c774b86b130c9c5e1cd296aa494a710c493c 1898 fasttracker2_1.00-1.dsc 6240c3bca7eecd6156b85b4019c3342cbef28416e8665ab2395e099731dcbc54 337520 fasttracker2_1.00.orig.tar.xz bd794499d3188252bcfdb0720230708e569aebd075564d45093a94d515f18dae 10560 fasttracker2_1.00-1.debian.tar.xz 2c0119c989329b21900a1cd5d7ae03e1dc4f8918b499ffd9b0c1e7ca51392f83 5391 fasttracker2_1.00-1_source.buildinfo Files: c1614c94bb97dcbf506639453520fa31 1898 non-free/sound optional fasttracker2_1.00-1.dsc a1038e468e41afbcead5f61b10fa788e 337520 non-free/sound optional fasttracker2_1.00.orig.tar.xz 82abe169772eb9e20f0daf72ea1a9e2a 10560 non-free/sound optional fasttracker2_1.00-1.debian.tar.xz 77540c98a0fcf974ddd453a527c09443 5391 non-free/sound optional fasttracker2_1.00-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl2TE6kACgkQweDZLphv fH4qQA/+PEW+BktLyI4wilw7q9jP2QP0abL2tDnlIYWSsCCfHAg240WppwwdGuIF E/pcjx73esyBZcSpEsN8O52GPyHevyzJSN41d9NjkyTDQsr5PPiYUPyY8IKh9uT3 k3eWMtMJS1qiv5mPkOsNwfenaeAdKn/vRgvRRCNt+NT+M5/a8Ecedpk94dUtezOy nuvZoncr+ZnET5wHCyLkQiM+2Bl/pFE7u2THEOaumtjt8CyhXEilUKTSspmzgZ7W PC8dDk+kXcEBH8zItwcNxZALuxkLiAa8z17d/MFUi1+ZuErfwI4e5uzR8135peLe W6KgZNDoFVXcv6f0q9ODG0iujy/Xs03Q3qYdqaeU0B7xHz+O7eMJLHjGawBdYN64 D2CBsisjPyWvP6yYU1zX7Pxg/djEU679medE8upHLTXqWB5CmriwigUpSnwoybnL xucb6kAegDSNI0vn4pHa+Q1c7vSYYgedRmbFGJONhRZgScZJ6atsaSEMpuE51Rgj Rj07o44V83eg7syHNpRUugAvh75GjxaEsli7ZufV+CGBMVTEngOGOgBc+7Zzg4aP 76Y8hR1GtdJcXjdehek9woWnDwvJHaryAqb6jo6CcLCwbBPNq1/18jUsUBlncnpp Y2o/CLkieruySBj1PqjTfJZygnjW+aufaKWpFWflAvIfhoWF2gU= =1nK6 -END PGP SIGNATURE End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: Bug#941559 marked as pending in xvidcore
Processing control commands: > tag -1 pending Bug #941559 [libxvidcore4] libxvidcore4: immediately crashes on amd64 since binNMU Added tag(s) pending. -- 941559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#941559: marked as done (libxvidcore4: immediately crashes on amd64 since binNMU)
Your message dated Thu, 03 Oct 2019 20:38:41 +
with message-id
and subject line Bug#941559: fixed in xvidcore 2:1.3.5-2
has caused the Debian Bug report #941559,
regarding libxvidcore4: immediately crashes on amd64 since binNMU
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
941559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxvidcore4
Version: 2:1.3.5-1
Severity: grave
Tags: sid bullseye
Hi,
Just over a month ago xvidcore was binNMUed and this seems to have
triggered a bug somewhere and now any application which tries to
initialize libxvidcore will segfault.
Test app:
#include
#include
int main(void)
{
xvid_gbl_init_t init = {
.version = XVID_VERSION,
.cpu_flags = 0,
.debug = 0,
};
xvid_global(NULL, XVID_GBL_INIT, &init, NULL);
return 0;
}
$ gcc -o xvid-test xvid-test.c -lxvidcore
$ ./xvid-test
Segmentation fault (core dumped)
The crash happens here:
Program received signal SIGSEGV, Segmentation fault.
0x77f22940 in check_cpu_features () from
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4
(gdb) bt
#0 0x77f22940 in check_cpu_features () from
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4
#1 0x77e9c15b in detect_cpu_flags () at ../../src/xvid.c:156
#2 0x77e9d265 in xvid_gbl_init (init=0x7fffdee4,
init=0x7fffdee4) at ../../src/xvid.c:793
#3 xvid_global (handle=, opt=,
param1=0x7fffdee4, param2=) at ../../src/xvid.c:816
#4 0x516d in main ()
Which in turn seems to happen because the check_cpu_features function is
in a non-executable read only memory region.
$ /proc/4658/maps
[...]
77e87000-77e8b000 rw-p 00:00 0
77e8b000-77e8d000 r--p fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
77e8d000-77ef5000 r-xp 2000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
[vvv]
77ef5000-77f2b000 r--p 0006a000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
[^^^]
77f2b000-77f2c000 r--p 0009f000 fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
77f2c000-77f36000 rw-p 000a fd:00 954232
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
77f36000-77fa1000 rw-p 00:00 0
[...]
Indeed readelf contains some non-executable program headers in
2:1.3.5-1+b1 which do not appear in 2:1.3.5-1 in buster. The
".rotext" section sounds suspicious.
2:1.3.5-1+b1:
$ readelf -l /usr/lib/x86_64-linux-gnu/libxvidcore.so.4
[...]
Program Headers:
Type Offset VirtAddr PhysAddr
FileSizMemSiz Flags Align
LOAD 0x 0x 0x
0x18a8 0x18a8 R 0x1000
LOAD 0x2000 0x2000 0x2000
0x000673c9 0x000673c9 R E0x1000
LOAD 0x0006a000 0x0006a000 0x0006a000
0x00035088 0x00035088 R 0x1000
LOAD 0x0009fb90 0x000a0b90 0x000a0b90
0x98d0 0x00073138 RW 0x1000
[...]
00 .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version
.gnu.version_r .rela.dyn .rela.plt
01 .init .plt .plt.got .text .fini
02 .rodata .rotext .eh_frame_hdr .eh_frame
03 .init_array .fini_array .data.rel.ro .dynamic .got .data .bss
2:1.3.5-1:
$ readelf -l /usr/lib/x86_64-linux-gnu/libxvidcore.so.4
[...]
Program Headers:
Type Offset VirtAddr PhysAddr
FileSizMemSiz Flags Align
LOAD 0x 0x 0x
0x0009da50 0x0009da50 R E0x20
LOAD 0x0009db90 0x0029db90 0x0029db90
0x98d0 0x00073138 RW 0x20
[...]
00 .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version
.gnu.version_r .rela.dyn .rela.plt .init .plt .plt.got .text .fini .rodata
.rotext .eh_frame_hdr .eh_frame
01 .init_array .fini_array .data.rel.ro .dynamic .got .data .bss
James
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: xvidcore
Source-Version:
Bug#906153: marked as done (jnoisemeter FTCBFS: upstream Makefile hard codes build architecture g++ in one place)
Your message dated Thu, 03 Oct 2019 21:19:39 + with message-id and subject line Bug#906153: fixed in jnoisemeter 0.2.2-1 has caused the Debian Bug report #906153, regarding jnoisemeter FTCBFS: upstream Makefile hard codes build architecture g++ in one place to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 906153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jnoisemeter Version: 0.1.0-4 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap jnoisemeter fails to cross build from source, because there is one bare g++ invocation left in the upstream Makefile. After making it substitutable, jnoisemeter cross builds successfully. Please consider applying the attached patch. Helmut --- jnoisemeter-0.1.0.orig/source/Makefile +++ jnoisemeter-0.1.0/source/Makefile @@ -35,7 +35,7 @@ jnoisemeter: LDLIBS += -lclthreads -lclxclient -lpthread -ljack -lXft -lpng -lX11 -lrt jnoisemeter: LDFLAGS += -L$(PREFIX)/$(LIBDIR) -L/usr/X11R6/$(LIBDIR) jnoisemeter: $(JNOISEMETER_O) - g++ $(LDFLAGS) -o $@ $(JNOISEMETER_O) $(LDLIBS) + $(CXX) $(LDFLAGS) -o $@ $(JNOISEMETER_O) $(LDLIBS) $(JNOISEMETER_O): -include $(JNOISEMETER_O:%.o=%.d) --- End Message --- --- Begin Message --- Source: jnoisemeter Source-Version: 0.2.2-1 We believe that the bug you reported is fixed in the latest version of jnoisemeter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 906...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated jnoisemeter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 03 Oct 2019 22:52:11 +0200 Source: jnoisemeter Architecture: source Version: 0.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 906153 Changes: jnoisemeter (0.2.2-1) unstable; urgency=medium . * Team upload. . [ Olivier Humbert ] * d/jnoisemeter.desktop: - add French GenericName and Comment * d/copyright: - add myself . [ Ondřej Nový ] * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * New upstream release - Honor CXX (Closes: #906153) * debian/patches: Refresh patche * debian/control: - Update Standards-Version - Set RRR: no - Bump debhelper compat to 12 - Build-Depend on pkg-config * debian/copyright: Update copyright years Checksums-Sha1: 12d825d26e4a2c4debc504fc7ca41ecea0155a18 2083 jnoisemeter_0.2.2-1.dsc 8ba7239b88baab61b9a1c8caf2616d0ebf978fd8 16786 jnoisemeter_0.2.2.orig.tar.bz2 90e0aa7650d1e715f43cbf51a7c676dc992880c0 6140 jnoisemeter_0.2.2-1.debian.tar.xz Checksums-Sha256: c3639a75729a1695954b25f5ee045ab4592d85e710c380022f6fe13c14b10d54 2083 jnoisemeter_0.2.2-1.dsc e749eedee54cab55432a6f7c38510306491f9605edc106a8eeeb4d2078bdf015 16786 jnoisemeter_0.2.2.orig.tar.bz2 44ce38290fc1615f3436f2548c5b9ee9409b74f27e651843794d4eac93daf9b2 6140 jnoisemeter_0.2.2-1.debian.tar.xz Files: e00591481d5d4cbc690f3bb28119caee 2083 sound optional jnoisemeter_0.2.2-1.dsc d93b4f055e40b4cf47c2e0ffe8241a01 16786 sound optional jnoisemeter_0.2.2.orig.tar.bz2 4bc2552555a978d5fb0588d63a29f186 6140 sound optional jnoisemeter_0.2.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl2WX+IACgkQafL8UW6n GZMeAw/9GAXtUULcN9D85/i0Y51ljEJ9PAM6RDJOFQWW/fdmx5k88w89N+eWDQnd //cHbuABSFVuSVZG8DLXFCRz1a+Ehhdq/H6iwAQHMSdvFe5u84JkJfdd5YXbnbuB FojmTDHhbFeJyKRhI2ImmpOjfVYNMVxsKNeKYVeFkf+8mqvJaeaukLKnIA1hncmL x8Mfu1XzzNIeTReXuG5Z0vizZX220Xt2/fpJK6REz85mL5tWDslGgtA8exzklhYf Edf260U9JkmVe8WpBYNoLxB6v5NjayLoVEwaoCp353Xr2kK9H8ek4yyVnw5IVFhS NUIYwX2m2GpdSl0VByhO9aJyEjkc2a/prz4YUu3Bo35IJ+YhIJgsJzbdGc8VzPG3 ANHFwAtTULKg4dQDxVLlXL2q1J8iDHBRnlVYubgcyVjqCbF8eAUvXJsSIRAtMTsg T2RNEYl7FJHyc1m94S5YdTIGtr8rOz+zaFbYLcL3W84dyJoj425Zh+Di28VegOvn loE/3lS8ydLracKiDh7mJX/iCwLVE1ZDidVNcFI8nubcO+bB7vxmS3np49u91Au8 lJJ58vEzLLrmm+kNE/V6pH0PpxXq1aERdm8oKxymyp0Q+QhQFld0yzjkqiV/+evH oTLlBIMNUp/BULkgHfjyJVtkIvKq6oY0qyv8gB7QWz2f6VQSSq8= =s5Um -END PGP
Bug#686919: marked as done (gjacktransport: Grammer Error ("allows to") in control file (package description) W/ Patch)
Your message dated Thu, 03 Oct 2019 21:34:20 +
with message-id
and subject line Bug#686919: fixed in gjacktransport 0.6.4-1
has caused the Debian Bug report #686919,
regarding gjacktransport: Grammer Error ("allows to") in control file (package
description) W/ Patch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
686919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gjacktransport
Version: 0.5.3-1
Severity: minor
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu quantal ubuntu-patch
Dear Maintainer,
* Grammer Fix ("allows to" >> "allows one to") in control file (package
description)
Thanks for considering the patch.
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)
Kernel: Linux 3.5.3-030503-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'
=== modified file 'debian/control'
--- debian/control 2012-06-03 00:40:33 +
+++ debian/control 2012-09-07 06:57:09 +
@@ -29,7 +29,7 @@
to the Jack Audio Connection Kit's, JACK transport mechanism via a
dynamic graphical slider.
.
- In other words: this software allows to seek Audio/Video media
+ In other words: this software allows one to seek Audio/Video media
files when they are played along jack transport. Intended for
audio-engineers or A/V editors that work with Ardour, Ecasound,
Hydrogen, Xjadeo, etc.
--- End Message ---
--- Begin Message ---
Source: gjacktransport
Source-Version: 0.6.4-1
We believe that the bug you reported is fixed in the latest version of
gjacktransport, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 686...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sebastian Ramacher (supplier of updated gjacktransport
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 03 Oct 2019 23:06:53 +0200
Source: gjacktransport
Architecture: source
Version: 0.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Sebastian Ramacher
Closes: 686919
Changes:
gjacktransport (0.6.4-1) unstable; urgency=medium
.
* Team upload.
.
[ Ondřej Nový ]
* d/copyright: Use https protocol in Format field
* d/control: Set Vcs-* to salsa.debian.org
.
[ Felipe Sateler ]
* Change maintainer address to debian-multime...@lists.debian.org
.
[ Ondřej Nový ]
* d/watch: Use https protocol
.
[ Sebastian Ramacher ]
* New upstream release
* debian/: Bump debhelper compat to 12.
* debian/control:
- Update Standards-Version
Remove menu file in favor of desktop files
- Set RRR: no
- Fix grammar in description. Thanks to cc11rocks for the patch (Closes:
#686919)
Checksums-Sha1:
0587ed7aba07592ca6f925dfca1af2cd38d972df 2081 gjacktransport_0.6.4-1.dsc
302e1c00755625439a3943046116c64d688382f5 177539
gjacktransport_0.6.4.orig.tar.gz
87f84986d8655a8859e2f5b92f9196143468fd69 2592
gjacktransport_0.6.4-1.debian.tar.xz
Checksums-Sha256:
082b1e3467a93c013a5a695505788288b23789ea6c65b55261d1dd8ac7f0b285 2081
gjacktransport_0.6.4-1.dsc
4b713389fba75ebb23515f3da515190b43d0b93fc72cd72b6c256edd875e53f7 177539
gjacktransport_0.6.4.orig.tar.gz
87c128630673739e255b684359d3d726e0b331a5321890e75b38e49c19cf5532 2592
gjacktransport_0.6.4-1.debian.tar.xz
Files:
800bb5760745e94e9a7662cf349aebb5 2081 sound optional gjacktransport_0.6.4-1.dsc
96102577be683f32732bf368a6f44c06 177539 sound optional
gjacktransport_0.6.4.orig.tar.gz
c5aeed248fd893b58906d17aa2150367 2592 sound optional
gjacktransport_0.6.4-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl2WZAwACgkQafL8UW6n
GZNlhQ/+LYz9Xz88C58VVRNE1seA
Processed: Raising severity of wxwidgets3.0-gtk transition blockers
> severity 933473 serious Bug #933473 [bossa] bossa: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933474 serious Bug #933474 [cubicsdr] cubicsdr: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933475 serious Bug #933475 [wxastrocapture] wxastrocapture: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933476 serious Bug #933476 [stx-btree] stx-btree: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933478 serious Bug #933478 [ucblogo] ucblogo: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933479 serious Bug #933479 [objcryst-fox] objcryst-fox: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 934096 serious Bug #934096 [codelite] codelite: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 934097 serious Bug #934097 [maitreya] maitreya: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 934098 serious Bug #934098 [3depict] 3depict: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933439 serious Bug #933439 [amule] amule: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > severity 933458 serious Bug #933458 [bochs] bochs: Please rebuild against wxWidgets GTK 3 package Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 933407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933407 933408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933408 933411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933411 933412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933412 933415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933415 933416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933416 933419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933419 933424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933424 933425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933425 933426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933426 933427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933427 933431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933431 933433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933433 933434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933434 933435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933435 933438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933438 933439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933439 933440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933440 933441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933441 933442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933442 933445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933445 933451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933451 933457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933457 933458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933458 933459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933459 933462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933462 933463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933463 933465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933465 933466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933466 933469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933469 933473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933473 933474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933474 933475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933475 933476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933476 933478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933478 933479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933479 934096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934096 934097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934097 934098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#920813: marked as done (sooperlooper does not show GUI)
Your message dated Fri, 4 Oct 2019 17:22:10 +1300 with message-id <20191004042210.ga15...@survex.com> and subject line Re: Bug#920813: sooperlooper does not show GUI has caused the Debian Bug report #920813, regarding sooperlooper does not show GUI to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 920813: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920813 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sooperlooper Version: 1.7.3~dfsg0-3+b1 Severity: important Dear Maintainer, I wanted to use sooperlooper in my debian/sid (already tested in ubuntu studio) and IU faced this problem: sooperloper starts (I can see read/write clients in jack connection, but no GUI is displayed. If started from terminal, I got the following message (doesn't seem to contain any error or warning): SooperLooper 1.7.3 Copyright 2007 Jesse Chappell Jack: JackClient::SetupDriverSync driver sem in flush mode Jack: JackLinuxFutex::Connect name = jack_sem.1000_default_sooperlooper Jack: Clock source : system clock via clock_gettime Jack: JackLibClient::Open name = sooperlooper refnum = 6 Jack: jack_set_graph_order_callback ext_client 519b3cd0 client 519b3cd0 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:common_in_1 type = 32 bit float mono audio port_index = 21 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:common_out_1 type = 32 bit float mono audio port_index = 22 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:common_in_2 type = 32 bit float mono audio port_index = 23 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:common_out_2 type = 32 bit float mono audio port_index = 24 OSC server URI (network) is: osc.udp://XXX.XXX.XXX.XXX.XXX:9951/ [__host and address removed for security__] Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 4 Jack: JackGraphManager::GetTotalLatency port_index = 21 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 22 total latency = 0 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:loop0_in_1 type = 32 bit float mono audio port_index = 25 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:loop0_out_1 type = 32 bit float mono audio port_index = 26 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:loop0_in_2 type = 32 bit float mono audio port_index = 27 Jack: JackClient::PortRegister ref = 6 name = sooperlooper:loop0_out_2 type = 32 bit float mono audio port_index = 28 Jack: JackClient::Activate Jack: JackPosixThread::StartImp : create non RT thread Jack: JackPosixThread::ThreadHandler : start Jack: JackClient::kBufferSizeCallback buffer_size = 128 Jack: JackClient::Init : period = 2902 computation = 300 constraint = 2902 Jack: JackPosixThread::AcquireRealTimeImp priority = 5 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 2 Jack: JackClient::kActivateClient name = sooperlooper ref = 6 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 18 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 18 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 4 Jack: JackClient::kGraphOrderCallback Jack: JackGraphManager::GetTotalLatency port_index = 25 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 21 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 26 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 22 total latency = 0 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 18 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 18 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 4 Jack: JackClient::kGraphOrderCallback Jack: JackGraphManager::GetTotalLatency port_index = 25 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 21 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 26 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 22 total latency = 0 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 18 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 18 Jack: JackClient::ClientNotify ref = 6 name = sooperlooper notify = 4 Jack: JackClient::kGraphOrderCallback Jack: JackGraphManager::GetTotalLatency port_index = 25 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 21 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 26 total latency = 0 Jack: JackGraphManager::GetTotalLatency port_index = 22 total latency = 0 -- System Information: Deb
Processed: Re: Bug#836232: sooperlooper: upon initialization, slgui fails an assertion with SetTitle
Processing control commands: > tags -1 + unreproducible Bug #836232 [sooperlooper] sooperlooper: upon initialization, slgui fails an assertion with SetTitle Added tag(s) unreproducible. -- 836232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#596392: marked as done (sooperlooper: Reproducible segmentation fault)
Your message dated Fri, 4 Oct 2019 17:33:32 +1300 with message-id <20191004043332.ga15...@survex.com> and subject line Re: sooperlooper: Reproducible segmentation fault has caused the Debian Bug report #596392, regarding sooperlooper: Reproducible segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 596392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596392 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sooperlooper Version: 1.6.14+dfsg-1+b1 Severity: normal While I was trying to figure out how to control SooperLooper using 'oscsend' in the liblo-tools package, I noticed that the following command will cause SooperLooper to segfault every time: $ oscsend localhost 9951 /ping ss return_url return_path SooperLooper prints the following: tmac@asus ~$ sooperlooper SooperLooper 1.6.14 Copyright 2007 Jesse Chappell OSC server URI (network) is: osc.udp://asus.home.org:9951/ liblo: protocol '(null)' not supported by this version Segmentation fault tmac@asus ~$ Best regards Torquil Sørensen -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.35.4 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sooperlooper depends on: ii libasound21.0.23-1 shared library for ALSA applicatio ii libc6 2.11.2-5 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-14 GCC support library ii libjack-jackd2-0 [libjack 1.9.5~dfsg-19 JACK Audio Connection Kit (librari ii liblo70.26~repack-5 Lightweight OSC library ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii librubberband21.3-1.1+b1 an audio time-stretching and pitch ii libsamplerate00.1.7-3Audio sample rate conversion libra ii libsigc++-1.2-5c2 1.2.7-2type-safe Signal Framework for C++ ii libsndfile1 1.0.21-3 Library for reading/writing audio ii libstdc++64.4.4-14 The GNU Standard C++ Library v3 ii libwxbase2.8-02.8.10.1-3+b1 wxBase library (runtime) - non-GUI ii libwxgtk2.8-0 2.8.10.1-3+b1 wxWidgets Cross-platform C++ GUI t ii libxml2 2.7.7.dfsg-4 GNOME XML library sooperlooper recommends no packages. sooperlooper suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Wed, Aug 07, 2013 at 08:39:23PM +0200, Jaromír Mikeš wrote: > fixed 596392 1.7.0 This was marked as fixed 6 years ago, but not closed. Closing now as even oldoldstable has a version > 1.7.0. Cheers, Olly--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#941340: marked as done (sooperlooper: Should sooperlooper be removed from Debian?)
Your message dated Fri, 4 Oct 2019 17:39:40 +1300 with message-id <20191004043940.ga14...@survex.com> and subject line Re: Bug#941340: sooperlooper: Should sooperlooper be removed from Debian? has caused the Debian Bug report #941340, regarding sooperlooper: Should sooperlooper be removed from Debian? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sooperlooper Version: 1.7.3~dfsg0-3 Severity: normal I think it's time to remove the sooperlooper package: * last upstream release was nearly 5 years ago * last package update was more than 2.5 years ago * has low popcon - inst:223 vote:20 * has no reverse dependencies (according to dak rm) * 4 open bugs, only the one from 2010 has any maintainer response * a blocker for the current wxwidgets3.0-gtk3 transition. If there are no objections within two weeks, I'll turn this into an RM bug. Cheers, Olly --- End Message --- --- Begin Message --- On Thu, Oct 03, 2019 at 07:41:50PM +0200, Olivier Humbert wrote: > I've had a look to the outstanding bugs. > 1. one is just a user using the wrong binary to launch sooperlooper > (#920813) OK, I've closed that one. > 2. one is probably something coming from the time stretch was in dev > (#836232) and I can't reproduce it now on Stretch or Buster. I've cc-ed the submitter to see if they can (note that the BTS doesn't automatically send replies to the submitter). > 3. one is from a very old version of sooperlooper : 1.6.14 dating back from > 2009 (see http://essej.net/sooperlooper/), so should probably be closed if > unreproducible nowadays (#596392) Hmm, and it was also marked as fixed by one of the maintainers 6 years ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596392;msg=43 I assume they failed to notice that setting a fixed version doesn't close the bug. Now closed. > 4. the last one is about building against gtk3 wx instead of gtk wx and it > is the case nowadays if I'm not wrong reading at > https://salsa.debian.org/multimedia-team/sooperlooper/blob/master/debian/control > so should probably be closed as well (#933425) No, that still says "libwxgtk3.0-dev" - it needs to be changed to "libwxgtk3.0-gtk3-dev" for the transition. > I've been talking with upstream those last few days and he might be willing > to release a new version including a bunch of different fixes. See > https://github.com/essej/sooperlooper/pull/13 Yes, that would be good. And thanks for helping to deal with the bug backlog. > It could then be wise to keep it in Debian regarding all of that. OK - I won't push for removal from Debian. Closing this bug. The lack of any evidence of an active maintainer for the Debian package still seems problematic, unless you and/or Nicolas are part of the Debian Multimedia Maintainers team? Also note that the package will get autoremoved from testing unless the maintainers take action since the wxwidgets transition bugs are now RC (but it'll automatically return if/when it's updated for the transition). Cheers, Olly--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: tagging bugs as not affecting stable
3depict: Please rebuild against wxWidgets GTK 3 package Added tag(s) sid and bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 933407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933407 933408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933408 933411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933411 933412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933412 933415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933415 933416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933416 933419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933419 933425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933425 933426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933426 933427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933427 933431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933431 933433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933433 933434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933434 933438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933438 933440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933440 933441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933441 933442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933442 933445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933445 933451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933451 933457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933457 933458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933458 933459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933459 933462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933462 933463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933463 933465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933465 933466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933466 933469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933469 933473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933473 933474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933474 933475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933475 933476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933476 933478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933478 934096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934096 934097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934097 934098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#868833: marked as done (Updating the flake Uploaders list)
Your message dated Sun, 06 Oct 2019 18:49:14 + with message-id and subject line Bug#868833: fixed in flake 0.11-4 has caused the Debian Bug report #868833, regarding Updating the flake Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 868833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flake Version: 0.11-3 Severity: minor Joost Yervante Damad has retired, so can't work on the flake package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. --- End Message --- --- Begin Message --- Source: flake Source-Version: 0.11-4 We believe that the bug you reported is fixed in the latest version of flake, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 868...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated flake package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 06 Oct 2019 20:20:07 +0200 Source: flake Architecture: source Version: 0.11-4 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 868833 Changes: flake (0.11-4) unstable; urgency=medium . * Team upload. . [ Ondřej Nový ] * Remove Joost Yervante Damad from uploader list (Closes: #868833) * d/control: Set Vcs-* to salsa.debian.org * d/control: Remove trailing whitespaces . [ Felipe Sateler ] * Change maintainer address to debian-multime...@lists.debian.org . [ Ondřej Nový ] * d/watch: Use https protocol * Use debhelper-compat instead of debian/compat . [ Sebastian Ramacher ] * debian/control: - Bump Standards-Version - Bump debhelper compat to 12 - Set RRR: no * debian/rules: Merge make invocations Checksums-Sha1: 311ffc0b0cc920b3072c2e03d974b76c7f6a6e6d 2000 flake_0.11-4.dsc 90ecaedf62fb27fe2d18244d263f2c0084e24228 4076 flake_0.11-4.debian.tar.xz Checksums-Sha256: 9fd0a843e2b4d24fd0e8eed51da542a69a1c4032d33b90beb4d39b2a88c38a76 2000 flake_0.11-4.dsc 788639694b7c557126388b13790f14618dfb76f887b20e9224d380518b4f7efa 4076 flake_0.11-4.debian.tar.xz Files: 83b015724dbf5075bb775a64e8e55159 2000 sound optional flake_0.11-4.dsc 72af56049cf09f2a6f52e6cd38e33644 4076 sound optional flake_0.11-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl2aMNYACgkQafL8UW6n GZN22w//dZDWg2ZhIZ3c7Mgahf+3bvWSBfdLRG1B5OuYWS4CqxbV4ER5BG/BxXwk 6V+3pqTle6NonlgIKqJuSbKO4aDsAEZrS20s3t7C47acqC+m4gkk2+R4W7NW5hvb qNOE4GBm6V+j7/U9JZ/Qzc6YQw7XoXN5Dn4/Q+oqPTTKWksJ2ZCYVJLAKxq06/g+ JGjDgFQnx2/5mEs7RvJHKYOACzrDXlNnzPRhEjdlkjn6fwkjo/i6cGFJG1IyIZSh UEiFkVMymWqfozeTRxnu8gtiSXwoY8xtEgNd+D2HmteOHN02/qpDHYxVVC9h2ZPl fhijgUlLP5eUloSoDgTFl1WkQAtgIgfewkzqJkC9Gif9FOJCZc6ZfihNHTQaQq10 yTJG1de/rCn+6ssiwsNmdm8/kd4YlhpRbxZDIXOoT4/FwFWj3/IdGQr1PeXJhHhJ PabIPzUd5ZU9O7MItb9xOse+Wx81qq8I9eVF6VPWSjxgV+omtBAW65XQ+DbMiwlo 1YAki/7IRwSaoHj/6jEy0MAFtxg4bZbx1T71wN3kCpPJQNcAebaV3Zq8X3sx4g/4 +1J/KbIFaS5nPav1QP+FNK9wbUW0XtVDYPA8j4bKTWqTMRyPzc879Vvk2ksjLOPC YZtkzntckceV17dmie3qTsshX9dZcr+rUu48GXfnQszyF3nJIqA= =OGEA -END PGP SIGNATURE End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: bumping severity of pygtk bugs
Processing control commands: > severity -1 serious Bug #885302 [src:gtklick] gtklick: Depends on unmaintained pygtk Severity set to 'serious' from 'important' > tags -1 -buster Bug #885302 [src:gtklick] gtklick: Depends on unmaintained pygtk Removed tag(s) buster. -- 885302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Processed: bumping severity of pygtk bugs
Processing control commands: > severity -1 serious Bug #885309 [src:jack-mixer] jack-mixer: Depends on unmaintained pygtk Severity set to 'serious' from 'important' > tags -1 -buster Bug #885309 [src:jack-mixer] jack-mixer: Depends on unmaintained pygtk Removed tag(s) buster. -- 885309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#845048: marked as done (gmusicbrowser freezes after pulseaudio restart)
Your message dated Thu, 10 Oct 2019 06:04:28 + with message-id and subject line Bug#942001: Removed package(s) from unstable has caused the Debian Bug report #845048, regarding gmusicbrowser freezes after pulseaudio restart to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 845048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845048 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gmusicbrowser Version: 1.1.15~ds0-1 Severity: normal gmusicbrowser freezes and has to be killed when pulseaudio has been restarted and you're trying to play a song afterwards. In steps: 1. Open gmusicbrowser 2. kill/restart pulseaudio 3. hit play in gmusicbrowser -> gmusicbrowser will freeze (without playing anything) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gmusicbrowser depends on: ii gir1.2-gstreamer-1.0 1.10.0-2 ii libglib-object-introspection-perl 0.040-2+b1 ii libgtk2-perl 2:1.2499-1 ii libgtk2.0-02.24.31-1 pn perl:any Versions of packages gmusicbrowser recommends: ii libcairo-perl 1.106-1+b2 ii libdigest-crc-perl 0.21-1+b2 ii libgtk2-notify-perl0.05-4+b3 ii libgtk2-trayicon-perl 0.06-2+b3 ii libhtml-parser-perl3.72-2+b1 ii libintl-perl 1.26-2 ii liblocale-gettext-perl 1.07-3+b1 ii libnet-dbus-perl 1.1.0-4+b1 ii libperl5.24 [libio-compress-perl] 5.24.1~rc3-3 Versions of packages gmusicbrowser suggests: ii alsa-utils 1.1.2-1 ii libgnome2-wnck-perl0.16-3+b3 pn libgtk2-appindicator-perl pn libgtk2-mozembed-perl pn mpg321 | flac123 | ogg123 pn mplayer | mpv ii vorbis-tools 1.4.0-10 -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1.15~ds0-1+rm Dear submitter, as the package gmusicbrowser has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942001 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#858245: marked as done (gmusicbrowser: Search-as-you-type causes crash)
Your message dated Thu, 10 Oct 2019 06:04:28 + with message-id and subject line Bug#942001: Removed package(s) from unstable has caused the Debian Bug report #858245, regarding gmusicbrowser: Search-as-you-type causes crash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gmusicbrowser Version: 1.1.15~ds0-1 Severity: normal Dear Maintainer, Invoking search in any list in gmusicbrowser crashes the program. Stderr for different situations: In main list: invalid iter -- stamp -1875915568 does not match requested 94319900871888 at /usr/bin/../share/gmusicbrowser/gmusicbrowser_list.pm line 1491, line 51. Segmentation fault In search list: invalid iter -- stamp -681055048 does not match requested 94140707105976 at /usr/bin/../share/gmusicbrowser/gmusicbrowser_list.pm line 1491. Segmentation fault In queue: invalid iter -- stamp -1328951024 does not match requested 94457886789904 at /usr/bin/../share/gmusicbrowser/gmusicbrowser_list.pm line 1491, line 78. Segmentation fault Upstream bug: https://github.com/squentin/gmusicbrowser/issues/141 There is a suspicion that some dependencies' build flags may cause this. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (900, 'testing'), (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gmusicbrowser depends on: ii gir1.2-gstreamer-1.0 1.10.4-1 ii libglib-object-introspection-perl 0.042-1 ii libgtk2-perl 2:1.2499-1 ii libgtk2.0-0 2.24.31-2 pn perl:any Versions of packages gmusicbrowser recommends: ii libcairo-perl 1.106-1+b2 pn libdigest-crc-perl pn libgtk2-notify-perl pn libgtk2-trayicon-perl ii libhtml-parser-perl 3.72-3 ii libintl-perl 1.26-2 ii liblocale-gettext-perl 1.07-3+b1 ii libnet-dbus-perl 1.1.0-4+b1 ii libperl5.24 [libio-compress-perl] 5.24.1-1 Versions of packages gmusicbrowser suggests: ii alsa-utils 1.1.3-1 pn libgnome2-wnck-perl pn libgtk2-appindicator-perl pn libgtk2-mozembed-perl pn mpg321 | flac123 | ogg123 ii mpv 0.23.0-2+b2 ii vorbis-tools 1.4.0-10+b1 -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1.15~ds0-1+rm Dear submitter, as the package gmusicbrowser has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942001 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#930580: marked as done (gmusicbrowser maxes volume on play with gstreamer 1.x and default settings)
Your message dated Thu, 10 Oct 2019 06:04:28 + with message-id and subject line Bug#942001: Removed package(s) from unstable has caused the Debian Bug report #930580, regarding gmusicbrowser maxes volume on play with gstreamer 1.x and default settings to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 930580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gmusicbrowser Version: 1.1.15~ds0-1 Severity: normal Dear Maintainer, gstreamer maximizes volume on play using gstreamer 1.x and the defeault "auto detect" for audio output. Selecting another option such as mpv does not have this effect. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gmusicbrowser depends on: ii gir1.2-gstreamer-1.0 1.14.4-1 ii libglib-object-introspection-perl 0.047-1 ii libgtk2-perl 2:1.24992-1+b2 ii libgtk2.0-02.24.32-3 ii perl 5.28.1-6 Versions of packages gmusicbrowser recommends: ii libcairo-perl 1.106-3+b1 ii libdigest-crc-perl 0.22.2-1+b1 pn libgtk2-notify-perl pn libgtk2-trayicon-perl ii libhtml-parser-perl 3.72-3+b3 ii libintl-perl1.26-2 pn libio-compress-perl ii liblocale-gettext-perl 1.07-3+b4 ii libnet-dbus-perl1.1.0-5+b1 Versions of packages gmusicbrowser suggests: ii alsa-utils 1.1.8-2 pn libgnome2-wnck-perl pn libgtk2-appindicator-perl pn libgtk2-mozembed-perl pn mpg321 | flac123 | ogg123 ii mpv0.29.1-1 ii vorbis-tools 1.4.0-11 -- no debconf information --- End Message --- --- Begin Message --- Version: 1.1.15~ds0-1+rm Dear submitter, as the package gmusicbrowser has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942001 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#912882: marked as done (gmusicbrowser: Depends on libgtk2-perl, that won't be part of Bullseye)
Your message dated Thu, 10 Oct 2019 06:04:28 + with message-id and subject line Bug#942001: Removed package(s) from unstable has caused the Debian Bug report #912882, regarding gmusicbrowser: Depends on libgtk2-perl, that won't be part of Bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 912882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmusicbrowser Severity: normal User: debian-p...@lists.debian.org Usertags: gtk2-removal Hi! This package depends on libgtk2-perl, that I intend to remove from testing soon after the Buster release, and then from sid at some later point during the Bullseye development cycle: https://bugs.debian.org/912860 FTR this port has been requested upstream back in 2013: https://github.com/squentin/gmusicbrowser/issues/57 Cheers! -- intrigeri --- End Message --- --- Begin Message --- Version: 1.1.15~ds0-1+rm Dear submitter, as the package gmusicbrowser has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942001 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message --- ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
