Processed: fixed 699383 in projectm/3.1.3-1, closing 699383

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 699383 projectm/3.1.3-1 Bug #699383 [projectm-data] libprojectm2: unlisted dependency on package ttf-bitstream-vera Bug #833489 [projectm-data] projectm-pulseaudio: ttf-dejavu-core dependency not listed Bug #961971 [projectm-data]

Processed: fixed 893926 in projectm/3.1.3-1, closing 893926

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 893926 projectm/3.1.3-1 Bug #893926 [projectm-data] mark projectm-data Multi-Arch: foreign Bug #908856 [projectm-data] mark projectm-data Multi-Arch: foreign Marked as fixed in versions projectm/3.1.3-1. Marked as fixed in versions

Processed: reassign 699383 to projectm-data, reassign 961971 to projectm-data, reassign 833489 to projectm-data ...

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 699383 projectm-data 2.1.0+dfsg-1 Bug #699383 [libprojectm2] libprojectm2: unlisted dependency on package ttf-bitstream-vera Bug reassigned from package 'libprojectm2' to 'projectm-data'. No longer marked as found in versions

Processed: fixed 909977 in projectm/3.1.3-1, closing 909977

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 909977 projectm/3.1.3-1 Bug #909977 [src:projectm] projectm: upstream has moved Marked as fixed in versions projectm/3.1.3-1. > close 909977 Bug #909977 [src:projectm] projectm: upstream has moved Marked Bug as done > thanks Stopping

Processed (with 1 error): forcibly merging 699383 833489

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 699383 833489 Bug #699383 [libprojectm2] libprojectm2: unlisted dependency on package ttf-bitstream-vera Unable to merge bugs because: package of #833489 is 'projectm-pulseaudio' not 'libprojectm2' Failed to forcibly merge 699383: Did

Processed: forcibly merging 893926 908856

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 893926 908856 Bug #893926 [projectm-data] mark projectm-data Multi-Arch: foreign Bug #908856 [projectm-data] mark projectm-data Multi-Arch: foreign Added indication that 908856 affects src:qmmp,src:clementine Marked as found in

Processed: closing 924925

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 924925 Bug #924925 [projectm-pulseaudio] projectm-pulseaudio crashes after a few seconds Bug #931900 [projectm-pulseaudio] Program crashes with message "free(): double free detected in tcache 2" Marked Bug as done Marked Bug as done >

Processed: fixed 875112 in projectm/3.1.3-1, closing 875112

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 875112 projectm/3.1.3-1 Bug #875112 [src:projectm] [projectm] Future Qt4 removal from Buster Marked as fixed in versions projectm/3.1.3-1. > close 875112 Bug #875112 [src:projectm] [projectm] Future Qt4 removal from Buster Marked Bug as

Processed: fixed 924925 in projectm-pulseaudio/3.1.3-1

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 924925 projectm-pulseaudio/3.1.3-1 Bug #924925 [projectm-pulseaudio] projectm-pulseaudio crashes after a few seconds Bug #931900 [projectm-pulseaudio] Program crashes with message "free(): double free detected in tcache 2" The source

Processed (with 1 error): unarchiving 875112, reopening 875112, unarchiving 924925, reopening 924925, unarchiving 621789 ...

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # src:projectm was reintroduced: > https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org > unarchive 875112 Bug #875112 {Done: Debian FTP Masters } [src:projectm] [projectm] Future Qt4 removal from

libopenshot-audio_0.2.0+dfsg1-4~exp1_amd64.changes is NEW

2020-06-26 Thread Debian FTP Masters
binary:libopenshot-audio-test-sound is NEW. binary:libopenshot-audio-test-sound is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be

Processing of libopenshot-audio_0.2.0+dfsg1-4~exp1_amd64.changes

2020-06-26 Thread Debian FTP Masters
libopenshot-audio_0.2.0+dfsg1-4~exp1_amd64.changes uploaded successfully to localhost along with the files: libopenshot-audio_0.2.0+dfsg1-4~exp1.dsc libopenshot-audio_0.2.0+dfsg1-4~exp1.debian.tar.xz libopenshot-audio-dev_0.2.0+dfsg1-4~exp1_amd64.deb

Bug#963205:

2020-06-26 Thread Thomas Orgis
OK, I introduced the additional wrapper now with svn commit 4743 on svn://scm.orgis.org/mpg123 . You can test by using current https://mpg123.org/snapshot or by applying the attached patch. Test reports before I release (this weekend?) are welcome. Alrighty then, Thomas Index: NEWS

Re: chromium (83.0.4103.116-1) and ffmpeg (7:4.3-2)

2020-06-26 Thread Sedat Dilek
[1] says: From: Bastian Germann To: 963...@bugs.debian.org Subject: chromium: patch for ffmpeg 4.3 Date: Thu, 25 Jun 2020 20:34:56 +0200 A patch from Gentoo is enclosed that fixes the problem. Additionally, the Conflicts marker in debian/control would have to be removed.

Processed: found 963726 in 3.1.3-1, severity of 963726 is serious

2020-06-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 963726 3.1.3-1 Bug #963726 [projectm-data] projectm-data should conflict with libprojectm2v5 Marked as found in versions projectm/3.1.3-1. > severity 963726 serious Bug #963726 [projectm-data] projectm-data should conflict with

Bug#963205: Now … what should I do?

2020-06-26 Thread Thomas Orgis
Am Thu, 25 Jun 2020 22:55:36 +0200 schrieb Sebastian Ramacher : > Other than x32, I'm not aware of any 32-bit arch that doesn't have > 32-bit off_t if _FILE_OFFSET_BITS is not set. So maybe architecture A sure-fire ruleset is different … > specific handling could be enough: if