snd is marked for autoremoval from testing
snd 22.1-1 is marked for autoremoval from testing on 2022-03-31 It (build-)depends on packages with these RC bugs: 1005778: pypandoc: fails to migrate to testing for too long: autopkgtest failure https://bugs.debian.org/1005778 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
snd_22.2-1_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 14 Mar 2022 22:05:40 +0100 Source: snd Architecture: source Version: 22.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Changes: snd (22.2-1) unstable; urgency=medium . * New upstream version 22.2 + Update d/upstream-changelog Checksums-Sha1: 521c313fa1101e66c98f34c2de4a779dd0ad263d 2730 snd_22.2-1.dsc 6060c72c24f53dfd70d9a4d7c1c2289f9544bd70 14647710 snd_22.2.orig.tar.gz 8ae35ddc564be05287601592e202ae0ea1570970 78192 snd_22.2-1.debian.tar.xz Checksums-Sha256: 22154745272b61566ed765cace0611414f72dfdce6fcbe3e3990a778bc2730d4 2730 snd_22.2-1.dsc 319f159bf77ed2bed8b1777248a707e6ba97061e2214bc947b8e0b04e0f9f04d 14647710 snd_22.2.orig.tar.gz e27a3d1ceb0ce91ab1c28acc2682c17ce20d52db55a4bed34a6fe76fe2e143c5 78192 snd_22.2-1.debian.tar.xz Files: 5cf02adc5f42265da634811471054cdc 2730 sound optional snd_22.2-1.dsc c8af8ddee73ead145b1aa7da8906d7d0 14647710 sound optional snd_22.2.orig.tar.gz ada11ed1d145e0e9c22ffe7d7c74bff3 78192 sound optional snd_22.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAmIvxFwWHGZvcnVtQHVt bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+HReEACQaqAk2+TFeojnooYPiDeHofq0 TARTqyDN9McaDN7suPt1iWEEfD8Zq4XREAMiWU8HDezDD7cE8LoFMyx/zLOgWvYH 5+qHvHG3FxOwskNnPrrtNT60wmZNipg90sp4a730wAv6HyQ0P0zKPtbtsU2oZoqe VY0Zk8F3NBJ13F+qRRvcradfiddCepbXiPvI210w4efcibD2n1WMz87Xa9fcphAe te7grJsLbwHC4UbErachfSycma7E5eugpfyeHfVHe+oQcbugL837rhymeNnXnvug CgYgIKCuZ5+gd5dFwu1aLeEUgZYk7LHFrmvOZ3+IaxL7QudmePohddH0LYlDYlcl JpQgm04wZo3sfy8MokUqVDLEyt93PO+RELWGZq5r35NT+/MMoBMJMmfzinYeEvuA AlRy5UArelrSh41hzRyk/aiPro2GZCzVwcIPKY1kuLmyeTTlRmd3iY7lov2GOnCN bw2J+AhyiVKbqUodtK27Y/7hQEP27amW6QmpsBYWp2TqoGNsPSLNVv3iQ4Ni0OxO VGzPoPOAJ1M4AS2my8lT/n7gP6DUncvRwnxMJg+NoTTk7zuhwwxqcZNAZliFXmxi Z89o9fyGdG9ah7465JbZQ8HLwm3d9inR/pAY274Crx95pKXxBjpFlMlpw8mlA6y8 tHOb+WvJG9+YGAJcfw== =gUlu -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of snd_22.2-1_source.changes
snd_22.2-1_source.changes uploaded successfully to localhost along with the files: snd_22.2-1.dsc snd_22.2.orig.tar.gz snd_22.2-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)
qpwgraph_0.2.3-1_amd64.changes is NEW
binary:qpwgraph is NEW. binary:qpwgraph is NEW. source:qpwgraph 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 patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports
Processing of qpwgraph_0.2.3-1_amd64.changes
qpwgraph_0.2.3-1_amd64.changes uploaded successfully to localhost along with the files: qpwgraph_0.2.3-1.dsc qpwgraph_0.2.3.orig.tar.gz qpwgraph_0.2.3-1.debian.tar.xz qpwgraph-dbgsym_0.2.3-1_amd64.deb qpwgraph_0.2.3-1_amd64.buildinfo qpwgraph_0.2.3-1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
Re: Bug#1007108: Fwd: ITP: qpwgraph -- User interface for controlling the PipeWire Graph
Hi Chris, Le sam. 12 mars 2022 à 11:39, Christopher Obbard a écrit : > > > - salsa-ci.yml is not needed anymore as we can directly use the config > > file from the salsa team: > >> https://salsa.debian.org/salsa-ci-team/pipeline/blob/master/README.md#basic-use > > Right, I initially used dh_make which generated that salsa-ci.yml file. > I've now removed it from the repo. > > Do you think it is worth opening a bug/merge request there to either > remove the generated file or add a comment about it not being needed any > more? This file can be useful is you want to custom the salsa pipeline, but keeping the default one is not needed. dh_make is doing the right thing by proposing a template of the pipeline config file. > > - Is there a specific reason to target the upstream dev website > > instead of the gitlab repo in the d/watch file? I guess he can forget > > to update it contrary to its gitlab repo. > > I did think about that, but most other packages I have seen target the > upstream's website in the watch file. > > For the record, the upstream tarball on the author's website doesn't > include the gitlab-ci file or some other bits, so they're not the same > archive as what you would download from gitlab. Okay it is up to you :-) Targeting github or gitlab is not a problem, a lot of packages do it. > > - The history of your master and upstream branches is uncommon, I > > think you cloned the upstream repo and then imported the upstream > > tarball with gbp? It would be cleaner to just create these branches > > using gbp import-orig. > > Right, I wanted to experiment with keeping the upstream git history > (like the pipewire packaging) rather than just importing all of the > files in a single commit like how import-orig would in the usual case. I > did that by: > > $ git init > $ git remote add upstream g...@gitlab.freedesktop.org:rncbc/qpwgraph.git > $ git checkout -b upstream v0.2.2 > $ gbp import-orig --upstream-vcs-tag v0.2.2 --pristine-tar > ../qpwgraph-0.2.2.tar.gz Both way are fine, it is up to the preferences of the maintainer or to the team policy. If you want to keep the upstream git history, you don't need to use gbp import-orig, this modifies the upstream branch and we should not do that :-). But, you can populate the pristine-tar branch with: $ pristine-tar commit ../qpwgraph-0.2.2.tar.gz I just sent the package to the NEW queue. Thanks for your work! Best, Dylan
Bug#1007253: obs-studio: produces unplayable h264 videos
Package: obs-studio Version: 27.2.3+dfsg1-1 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I have tried several different sources, including a webcam, window / screen share, and "Color Source". All of them produce the same results, where the video channel is unplayable, unless I switch to lossless compression, which seems to work. I am using the software h264 encoder. I will try to attach a sample video, one advantage of apparently having no video channel is that they are pretty small. - -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages obs-studio depends on: ii libavcodec58 7:4.4.1-3 ii libavdevice58 7:4.4.1-3 ii libavformat58 7:4.4.1-3 ii libavutil567:4.4.1-3 ii libc6 2.33-7 ii libcurl3-gnutls7.81.0-1 ii libfontconfig1 2.13.1-4.4 ii libfreetype6 2.11.1+dfsg-1 ii libgcc-s1 12-20220302-1 ii libglib2.0-0 2.70.4-1 ii libjansson42.13.1-1.1 ii libluajit-5.1-22.1.0~beta3+dfsg-6 ii libmbedcrypto7 2.28.0-1 ii libmbedtls14 2.28.0-1 ii libmbedx509-1 2.28.0-1 ii libobs027.2.3+dfsg1-1 ii libpci31:3.7.0-6 ii libpipewire-0.3-0 0.3.48-1 ii libpulse0 15.0+dfsg1-4 ii libpython3.9 3.9.10-2 ii libqt5core5a 5.15.2+dfsg-15 ii libqt5gui5 5.15.2+dfsg-15 ii libqt5network5 5.15.2+dfsg-15 ii libqt5svg5 5.15.2-4 ii libqt5widgets5 5.15.2+dfsg-15 ii libqt5xml5 5.15.2+dfsg-15 ii libspeexdsp1 1.2~rc1.2-2 ii libstdc++6 12-20220302-1 ii libswscale57:4.4.1-3 ii libudev1 250.3-2 ii libv4l-0 1.22.1-2 ii libx11-6 2:1.7.2-2+b1 ii libx264-1632:0.163.3060+git5db6aa6-2 ii libxcb-randr0 1.14-3 ii libxcb-shm01.14-3 ii libxcb-xfixes0 1.14-3 ii libxcb-xinerama0 1.14-3 ii libxcb11.14-3 ii libxcomposite1 1:0.4.5-1 ii libxfixes3 1:6.0.0-1 ii python33.9.8-1 ii python3.9 3.9.10-2 Versions of packages obs-studio recommends: ii obs-plugins 27.2.3+dfsg1-1 Versions of packages obs-studio suggests: ii policykit-10.105-33 ii v4l2loopback-dkms 0.12.5-1 - -- no debconf information -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmIvitAACgkQA0U5G1Wq FSF0mw//YEIcMIAsyt9QR/mmXoPbC5OjRjtzXB6k4jYAr3J6BFVpVOTbYIK7kaIF 0zdDZPXdo60ZsGTHvdKPkAEPi/ZnO0CUiI60NNNEfnjbnuAGRuYAxBshtj5Chpfi 5FLEGAs0FGnyo0hSU4ElDJ9T2ahrus5Ooq34G/XNahmWBfNxEsgfZW299cFwCHdE vjt6oye6PrUKgAJdYq15PwvOGE8Q/tbn+thCnEQN1xBPBDI1AKGaqUEzMdtDTCMM k0OJpSve920c1ICom1C98se0YVuqiwoaQlBEx+9KOKr6csoKy+UIConYv4dz/2JB Zo7ybUvgIvJTJSHrLYkM7jBJpKetd105GSQhUwKkIHU1hWSD6wUQKFVjZfT9bWsO ktXt5HZFh9Gbr9VfctPG0zVIFhzA8wWPAT1ghpA28zzNLL87kbhmzM6VdDSthNnO dzOdG7ciwfM3pfYyqk3Bg5TQV3B3wXcQYc0VBTzW9F8vdyDfjozVOXQ7mw3whlVH NbefFklb+5MLzY59+ETzm7zlu0CAXviEC7FZL0HFzxo4VZUex5JfQPZFE2Lzabn7 xKt7LWGL6hu+lK24lJ9vxId8GJEZEi6d5nj0FLL/u/q52MmcA7gZ25nanlkac7s3 da+ujd/6vemmPdBKb0exASi2uVC1Gx9l8JO+6lhDam+2zZJK+xQ= =N/gg -END PGP SIGNATURE- 2022-03-14_15-24-49.mkv Description: video/matroska
[bts-link] source package src:stk
# # bts-link upstream status pull for source package src:stk # 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 # remote status report for #759190 (http://bugs.debian.org/759190) # Bug title: csound: The STKSitar opcode can create a buildup of clipped samples as illustrated by the attached csd file # * https://github.com/thestk/stk/issues/117 # * remote status changed: open -> closed # * closed upstream tags 759190 + fixed-upstream usertags 759190 - status-open usertags 759190 + status-closed thanks
Processed: [bts-link] source package src:stk
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:stk > # 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 #759190 (http://bugs.debian.org/759190) > # Bug title: csound: The STKSitar opcode can create a buildup of clipped > samples as illustrated by the attached csd file > # * https://github.com/thestk/stk/issues/117 > # * remote status changed: open -> closed > # * closed upstream > tags 759190 + fixed-upstream Bug #759190 [src:stk] csound: The STKSitar opcode can create a buildup of clipped samples as illustrated by the attached csd file Added tag(s) fixed-upstream. > usertags 759190 - status-open Usertags were: status-open. There are now no usertags set. > usertags 759190 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 759190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
