Bug#919627: kodi: Segfault at startup on computer that has been working with Kodi

Control: tags -1 moreinfo Hi Stephen, Stephen Paul Weber ezt írta (időpont: 2019. jan. 19., Szo, 8:21): > > >libdrm-nouveau2:amd64 (2.4.74-1, 2.4.95-1~bpo9+1) > > > >The libdrm-nouveau2 and related seem suspect, especially coming from > >backports. > > Confirmed. I downgraded libdrm-nouveau2 to

Processed: Re: Bug#919627: kodi: Segfault at startup on computer that has been working with Kodi

Processing control commands: > tags -1 moreinfo Bug #919627 [kodi] kodi: Segfault at startup on computer that has been working with Kodi Added tag(s) moreinfo. -- 919627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919627 Debian Bug Tracking System Contact ow...@bugs.debian.org with probl

Processing of amsynth_1.8.0-1_amd64.changes

amsynth_1.8.0-1_amd64.changes uploaded successfully to localhost along with the files: amsynth_1.8.0-1.dsc amsynth_1.8.0.orig.tar.gz amsynth_1.8.0-1.debian.tar.xz amsynth-dbgsym_1.8.0-1_amd64.deb amsynth_1.8.0-1_amd64.buildinfo amsynth_1.8.0-1_amd64.deb Greetings, Your Debian

amsynth_1.8.0-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Jan 2019 11:26:13 -0500 Source: amsynth Binary: amsynth Architecture: source amd64 Version: 1.8.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Tiago Bortoletto

Bug#919821: marked as done (New upstream version available)

Your message dated Sun, 20 Jan 2019 22:34:18 + with message-id and subject line Bug#919821: fixed in amsynth 1.8.0-1 has caused the Debian Bug report #919821, regarding New upstream version available to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#836878: (no subject)

user debian-rele...@lists.debian.org usertags 836878 + bsp-2019-01-ca-montreal thank you

Bug#919821: (no subject)

user debian-rele...@lists.debian.org usertags 919821 + bsp-2019-01-ca-montreal thank you

Bug#795442: (no subject)

user debian-rele...@lists.debian.org usertags 795442 + bsp-2019-01-ca-montreal thank you

mixxx_2.2.0~dfsg-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Jan 2019 22:25:18 +0100 Source: mixxx Binary: mixxx mixxx-data Architecture: source Version: 2.2.0~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Matteo F.

Processing of mixxx_2.2.0~dfsg-1_source.changes

mixxx_2.2.0~dfsg-1_source.changes uploaded successfully to localhost along with the files: mixxx_2.2.0~dfsg-1.dsc mixxx_2.2.0~dfsg.orig.tar.xz mixxx_2.2.0~dfsg-1.debian.tar.xz mixxx_2.2.0~dfsg-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org

Bug#919821: New upstream version available

user debian-rele...@lists.debian.org usertags 919821 + bsp-2019-01-ca-montreal thanks

Bug#919821: New upstream version available

usertags 919821 + bsp-2019-01-ca-montreal thanks

Bug#919939: ffmpeg: please use non-scientist-requiring units

Package: ffmpeg Version: 7:4.1-1 Severity: wishlist Tags: upstream size= 155373kB time=03:15:59.53 bitrate= 108.2kbits/s speed=2.76e+03x During: for x in *.@(mp4|m4a); do ffmpeg -i "$x" -vn -sn -c:a copy ./"${x%.@(mp4|m4a)}.wma"; done This is… probably correct, but “2760x” would be easier

Re: RFS: playerctl 2.0.1

On Sun, 20 Jan 2019 at 07:45, Nick Morrott wrote: > > Dear team, > > I have just pushed playerctl 2.0.1 to salsa [1], and am wondering if > someone would kindly review my changes for this release and, if happy > upload it. If there are any issues please let know and I'll rectify > them ASAP. My t

Processing of lmms_1.1.3-8_source.changes

lmms_1.1.3-8_source.changes uploaded successfully to localhost along with the files: lmms_1.1.3-8.dsc lmms_1.1.3-8.debian.tar.xz lmms_1.1.3-8_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

playerctl_2.0.1-1_multi.changes is NEW

binary:gir1.2-playerctl-2.0 is NEW. binary:libplayerctl2 is NEW. binary:libplayerctl2 is NEW. binary:gir1.2-playerctl-2.0 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

Processing of playerctl_2.0.1-1_multi.changes

playerctl_2.0.1-1_multi.changes uploaded successfully to localhost along with the files: playerctl_2.0.1-1.dsc playerctl_2.0.1.orig.tar.gz playerctl_2.0.1-1.debian.tar.xz gir1.2-playerctl-2.0_2.0.1-1_amd64.deb libplayerctl-dev_2.0.1-1_amd64.deb libplayerctl-doc_2.0.1-1_all.deb libplay

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 919821 +pending Bug #919821 [amsynth] New upstream version available Added tag(s) pending. > usertags 919821 +bsp-2019-01-ca-montreal User is t...@riseup.net There were no usertags set. Usertags are now: bsp-2019-01-ca-montreal. > thanks Stop

Bug#919529: CVE-2019-6256

On 2019-01-19 22:36:05, Salvatore Bonaccorso wrote: > Hey! > > On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote: > > Control: found -1 2016.11.28-1 > > > > On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote: > > > Source: liblivemedia > > > Severity: grave > > > Tags: security > >

Processed: bug 919529 is not forwarded

Processing commands for cont...@bugs.debian.org: > notforwarded 919529 Bug #919529 {Done: Sebastian Ramacher } [src:liblivemedia] CVE-2019-6256 Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 919529: https://bugs.debian.org/cgi-bin/

Re: Processed: tagging 919529, bug 919529 is forwarded to https://github.com/rgaufman/live555/issues/19

Hi On 2019-01-19 21:30:04, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > tags 919529 + upstream > Bug #919529 {Done: Sebastian Ramacher } > [src:liblivemedia] CVE-2019-6256 > Added tag(s) upstream. > > forwarded 919529 https://github.com/rgaufman/live