Bug#1033517: yt-dlp: mpv fails to work with yt-dlp, after yt-dlp upgrade (uncoordinated API change?)
Severity: important Howdy On Sun, 26 Mar 2023, Francesco Poli (wintermute) wrote: Package: yt-dlp Version: 2023.03.04-1 Severity: grave Justification: renders package unusable This doesn't actually render the package unusuable, on the contrary it works around throttling. Instead, it hinders compatibility with another package. Hello and thanks for maintaining this useful package! After upgrading from yt-dlp/2023.02.17-1 to yt-dlp/2023.03.04-1, mpv is no longer able to use yt-dlp to play YouTube videos: This actually "only" happens when you use bestvideo, other formats such as '22' still work. Eg, `mpv --ytdl-format=22 https://www.youtube.com/watch?v=RZAq-_gz_W8` What's wrong? Did yt-dlp change API? If this is the case, the new version of yt-dlp Debian package should wait for an updated mpv Debian package, before migrating to testing... Not API, but yt-dlp made a change to solve widespread, severe throttling, to the point of being unusable really. I saw one report that had it going at an average speed of 30kb/s. mpv didn't cope well, but that has been fixed upstream in subsequent[0] commits[1]. [0]: https://github.com/mpv-player/mpv/commit/94c189dae76ba280d9883b16346c3dfb9720687e [1]: https://github.com/mpv-player/mpv/commit/362256edbc4f95c63e69c1fa8c8dce9cc6c44288 Or is it a bug in yt-dlp that shows up only when yt-dlp is called by mpv behind the scenes, and not when it is directly invoked from the user's command line? It's not really a bug in yt-dlp, but instead in mpv. Please fix this issue as soon as possible, or revert to the previous version (yt-dlp/2023.02.17-1), until this behavior has been properly investigated and solved. And here lies the problem. Seemingly one of the big fixes in 2023.03.03 is a workaround for the aforementioned throttling, to revert would mean to make yt-dlp unusably slow. But to leave it as is, mpv can't directly utilize yt-dlp with the default quality option. If we weren't so close to the freeze I'd say the right option would be to simply patch the yt-dlp hook in mpv and move on, but that's not precisely an option anymore either. So to sum up, at least for things I can do: 1. Break yt-dlp integration with mpv under the default options for one specific (granted, highly popular) site, but usable by itself and other tools. 2. Revert and break the ability to use yt-dlp to watch a video without first downloading, for all tools. Reverting also wouldn't cover backporting new releases to bookworm eventually either. Thanks for your time and patience! Regards, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1029661: Cannot authenticate with Google
Howdy, Google no longer allows gcalcli to authenticate. Upstream recommends manually creating a developer account and registering gcalcli as your own app. This is a *much* more cumbersome setup process, and the simple oauth2 workflow that gcalcli uses by default doesn't work with no indication of why. While it's certainly more complicated than it used to be, I switched auth methods back when gcalcli ran into API quota issues and it's been working fine ever since. I've seen others have issues where they have to re-authenticate after 7 days, but I haven't personally run into that problem. Then again I also have gcalcli run in conky so it may be run often enough to refresh the key. At a minimum, this should be documented and the flow for not having authenticated yet should give better guidance to the user and not try an authentication that won't work. Sure, I can nab the upstream commit[0] that documents the changes. This close to freeze I don't think upstream is going to find an ideal solution to the problem. [0]: https://github.com/insanum/gcalcli/commit/8c812e3da68ae6cbd220182517a64939df0c1b38 https://github.com/insanum/gcalcli/issues/580 ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1026743: closing 1026743
close 1026743 thanks Howdy, Given barrier continues to build in up to date chroots, lack of further detail, and release of bookworm approaching, I'm closing this bug. ~Unit 193
Bug#1025982: closing 1025982
close 1025982 0.3.3-8 thanks We believe that the bug you reported is fixed in the latest version of python-mitogen, 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 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Format: 1.8 Date: Tue, 13 Dec 2022 21:43:51 -0500 Source: python-mitogen Architecture: source Version: 0.3.3-8 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Unit 193 Changes: python-mitogen (0.3.3-8) unstable; urgency=medium . * Team upload. * d/p/ansible-6, d/control: Bump max ansible to 2.14/7. Checksums-Sha1: b928b64dba03bcd6ebfcc51d2f988c5188131565 2371 python-mitogen_0.3.3-8.dsc 5fd4c0d68fbaaac9a53188a25d215d8fd1cbaa2a 1260897 python-mitogen_0.3.3.orig.tar.gz 83b55242b10dccee7cfa1e8e9ba82dde622b1121 12008 python-mitogen_0.3.3-8.debian.tar.xz 844a2b744400792cb95665685fd0602e18ba23b2 6897 python-mitogen_0.3.3-8_amd64.buildinfo Checksums-Sha256: 3b71240060e665652c3d8c301b83a1fb44d5293573cecd768f9e11df416f8669 2371 python-mitogen_0.3.3-8.dsc 41d2c540a64ca4706f9413e6807c8d5d401918788ae7428d8273c80bb61ca216 1260897 python-mitogen_0.3.3.orig.tar.gz 21aa1719e3b80ccd2af944b6469d9abf8e764c666b060ca6be84ab2adda3e322 12008 python-mitogen_0.3.3-8.debian.tar.xz 2671f1c8a383d16d45d05dcc98397ab25d1eb40755e84db96f88cfa997305d99 6897 python-mitogen_0.3.3-8_amd64.buildinfo Files: fbb8286c43bfda33bb758cafc3ecc7f4 2371 python optional python-mitogen_0.3.3-8.dsc 0b15434520c5064784984336b6464f87 1260897 python optional python-mitogen_0.3.3.orig.tar.gz 6cf4cd212face4232b7eedc57676d2b5 12008 python optional python-mitogen_0.3.3-8.debian.tar.xz c583cd552ca7f5e30a265c106463fc03 6897 python optional python-mitogen_0.3.3-8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmOZOw0ACgkQUAHhsJqj dEtdgg/+Owb9nl8HHnlP+ONDDf4Zj/roOwhLDTjNkS/VvvDLfMqv0fBH4FgaVQcu 946I2I4jie6FXB7yWyr4+I6aOSuzKrg/kNkAegVLIWhFNbL1bVEFikd2VW0zCjZ9 FP0I1ERIXj/Hgc7vmiwkBAxauf3V3jbEqPiUbxuDatZxjf/YCwdJkDItcvfeWWAa cv/ttY0I7PBN/nxeP1uMExgBDG+5UHWt+tLaszB5zfJNvXcyXSoVnccQpsGO0E9Y 4CSrHeuoO6SnRsoLM+H0GBt7omrpbEg18BIskoWk9Z+csmlTBc1eyVpkrMzmS2uw 9CiacNbVnxxXjqpxRv9tOh066Lr9vO6I9iPWvYN+Kt7mAopup525dUpEVwd6vl6K C6EpP831gN6C85/tLygyGPRz2r5oZr8b/kSbZwr5VC0bFOa/FSuSIYIfdnDwSaoz Eytie3c91FiVQDG6t2/5G+m7tedZSFQGb9Hz7KrBxISOrqFxrAtKGzfAoBiRrG2S +aY0PD0fppdQNqrjXVNcNuJhW9dB3vFlhPLaZngGHZ86tSaQB+5cHb0Mo83d/e/s Rpnn23zZEM36nOZfLN0jQjlYXxaARedcQaabxR9CQmWwYGOj/NAwpuAdNQG8NAKc vE/qBsChnHftOqhvE7wiPbzndFYlISLBw8YpK41IIP9TETgIh1k= =LHsU -END PGP SIGNATURE-
Bug#1011686: closing 1011686
close 1011686 thanks Howdy, This was actually a bug in ruby-ntlm, which was fixed in 0.6.3-2. Closes: 1011676 Changes: ruby-ntlm (0.6.3-2) unstable; urgency=medium . * Team upload. * d/p/02_openssl3_compatibility.patch: - Grab an upstream PR to fix compatibility with openssl 3.0. (Closes: #1011676) * Update Standards-Version to 4.6.1. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1018717: orage: extra informations
Control: severity -1 normal Control: forwarded -1 https://gitlab.xfce.org/apps/orage/-/issues/2 Howdy, Thanks for providing some information and testing on unstable, I was about to close the bug report as it lacked any information and was clearly a FrankenDebian[0]. What you're seeing is due to the fact that orage doesn't yet support Wayland. As orage's target is the Xfce desktop (as shown by being an Xfce app, and the description has it all over) this is somewhat to be expected as Xfce itself doesn't have support for Wayland. This bug will likely be fixed in due time as different aspects of Xfce gain support for Wayland, and can be tracked on the upstream bug report[1]. [0]: https://wiki.debian.org/DontBreakDebian [1]: https://gitlab.xfce.org/apps/orage/-/issues/2 ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#806930: closing 806930
close 806930 thanks Howdy, My apoligies this wasn't addressed in a stable release of Debian, but as it's now fixed in all supported versions of Debian, and libcurl is used so it shouldn't happen again, I'm closing this report. Hopefully you still use pianobar, and hopefully you use something newer than oldoldoldstable. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1014305: closing 1014305
close 1014305 thanks This bug was fixed in the following upload: -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Format: 1.8 Date: Tue, 05 Jul 2022 20:28:34 -0400 Source: ruby-net-sftp Architecture: source Version: 1:3.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Unit 193 Changes: ruby-net-sftp (1:3.0.0-2) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on ruby-net-ssh. + ruby-net-sftp: Drop versioned constraint on ruby-net-ssh in Depends. . [ Unit 193 ] * Add patch to remove version cap on ruby-net-ssh. * Update Standards-Version to 4.6.1. Checksums-Sha1: 0312c471ba2f6987641154e244a31dbe8af4cc32 2122 ruby-net-sftp_3.0.0-2.dsc b44101d43d3a7ca01c60f6acecc09b9e54176d80 49188 ruby-net-sftp_3.0.0.orig.tar.gz ede00c04c923e3358da3b49d44b27b3c0b1ea456 18660 ruby-net-sftp_3.0.0-2.debian.tar.xz 00c961d28d14d1c8433ee3b262561fcef485e4cf 9223 ruby-net-sftp_3.0.0-2_amd64.buildinfo Checksums-Sha256: ea50e371a1594b52adff711857a3708cee30b4281ed7137872d07b621fdb61bd 2122 ruby-net-sftp_3.0.0-2.dsc 62513a956c3e48206245089485142c7ebc99f37f97e67db6e05a93c7d8bccdfd 49188 ruby-net-sftp_3.0.0.orig.tar.gz 0070e4acb92d254731621dfe2e9220afc1f52c32b2226aa7314515d1a5a3e6d1 18660 ruby-net-sftp_3.0.0-2.debian.tar.xz c2f2534c1aaa82b493b1e119825e9f3162ca36fc5b18f73d0e53032743800556 9223 ruby-net-sftp_3.0.0-2_amd64.buildinfo Files: eb5d8c4b66e20b98dcd0a7014feb2e76 2122 ruby optional ruby-net-sftp_3.0.0-2.dsc 98899c3d14a96095aaab4efc13038055 49188 ruby optional ruby-net-sftp_3.0.0.orig.tar.gz d9a08b7bd3fdc28c15828a5fb94d2c0a 18660 ruby optional ruby-net-sftp_3.0.0-2.debian.tar.xz 8145f817e9575127ec2fb7b8c611035c 9223 ruby optional ruby-net-sftp_3.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmLE3b8ACgkQUAHhsJqj dEv9HRAAwsD7iBn0xMKN0NLvwAl1/3X/4TWOMIpBIwphYGqDfXX03EOZ6B2BYJ9b CZeaAzVvjXqu+G3FFsfyDYN+LGKCwkpho//giQSXSJEb00DbpNVqwr13+av5hLoa NE1oUMTogPIQMtvW7aAfG9el0kbW/n5seDKxoUl1slJ0yWKED2uh/GOb9K2SfGp7 WzefL/rGIQoigfuCdhqpaMBXsmISq9VwGBBa+Us/LFvwHbb5ZpoVRv3Uhi7Orzq0 qXO51DZ1HzIzApm4tKruhCbdALD+dMaAylqrVbZQAbfvbl5G++cbAuSqJ13cT+ub w5dK82pVkdK2CZb3XDEKcSXOo8/2NAtIbHiKlVYLNmBJtTPVA7VxPX7X5D/fwSkE 4TgX1DjBXhNE2ihWWP0jj5z/jSOfMkbxjNQkFgaOPaV1ExAOXG9aO2qIi6m/DGRI YaI7Uy3rsm9oERiKJgN0Fyyt+zEqKg9PJM6GBEYfo5UVqQcn8Z+7VzoIkdNeXBWm ixnazo9MgWZWV8XstiW00LRP6LyuyNLeSBpbIHij7t270sMXHgaylxz/Kf4Q2Z2t qHa5+onvjUlpeyRTMzCo6qwn7ZdZOCRVCXG/sp96jGyr3W6i6t0gwg6MvxoIBVa2 PN6fFWO7Q4QheQy6hd+7j340zdc5Vn1wNFieXirUKBN509OzF/I= =oHMY -END PGP SIGNATURE-
Bug#1014380: closing 1014380
close 1014380 thanks This bug was fixed in the following upload: -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Format: 1.8 Date: Tue, 05 Jul 2022 20:28:34 -0400 Source: ruby-net-sftp Architecture: source Version: 1:3.0.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Unit 193 Changes: ruby-net-sftp (1:3.0.0-2) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on ruby-net-ssh. + ruby-net-sftp: Drop versioned constraint on ruby-net-ssh in Depends. . [ Unit 193 ] * Add patch to remove version cap on ruby-net-ssh. * Update Standards-Version to 4.6.1. Checksums-Sha1: 0312c471ba2f6987641154e244a31dbe8af4cc32 2122 ruby-net-sftp_3.0.0-2.dsc b44101d43d3a7ca01c60f6acecc09b9e54176d80 49188 ruby-net-sftp_3.0.0.orig.tar.gz ede00c04c923e3358da3b49d44b27b3c0b1ea456 18660 ruby-net-sftp_3.0.0-2.debian.tar.xz 00c961d28d14d1c8433ee3b262561fcef485e4cf 9223 ruby-net-sftp_3.0.0-2_amd64.buildinfo Checksums-Sha256: ea50e371a1594b52adff711857a3708cee30b4281ed7137872d07b621fdb61bd 2122 ruby-net-sftp_3.0.0-2.dsc 62513a956c3e48206245089485142c7ebc99f37f97e67db6e05a93c7d8bccdfd 49188 ruby-net-sftp_3.0.0.orig.tar.gz 0070e4acb92d254731621dfe2e9220afc1f52c32b2226aa7314515d1a5a3e6d1 18660 ruby-net-sftp_3.0.0-2.debian.tar.xz c2f2534c1aaa82b493b1e119825e9f3162ca36fc5b18f73d0e53032743800556 9223 ruby-net-sftp_3.0.0-2_amd64.buildinfo Files: eb5d8c4b66e20b98dcd0a7014feb2e76 2122 ruby optional ruby-net-sftp_3.0.0-2.dsc 98899c3d14a96095aaab4efc13038055 49188 ruby optional ruby-net-sftp_3.0.0.orig.tar.gz d9a08b7bd3fdc28c15828a5fb94d2c0a 18660 ruby optional ruby-net-sftp_3.0.0-2.debian.tar.xz 8145f817e9575127ec2fb7b8c611035c 9223 ruby optional ruby-net-sftp_3.0.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmLE3b8ACgkQUAHhsJqj dEv9HRAAwsD7iBn0xMKN0NLvwAl1/3X/4TWOMIpBIwphYGqDfXX03EOZ6B2BYJ9b CZeaAzVvjXqu+G3FFsfyDYN+LGKCwkpho//giQSXSJEb00DbpNVqwr13+av5hLoa NE1oUMTogPIQMtvW7aAfG9el0kbW/n5seDKxoUl1slJ0yWKED2uh/GOb9K2SfGp7 WzefL/rGIQoigfuCdhqpaMBXsmISq9VwGBBa+Us/LFvwHbb5ZpoVRv3Uhi7Orzq0 qXO51DZ1HzIzApm4tKruhCbdALD+dMaAylqrVbZQAbfvbl5G++cbAuSqJ13cT+ub w5dK82pVkdK2CZb3XDEKcSXOo8/2NAtIbHiKlVYLNmBJtTPVA7VxPX7X5D/fwSkE 4TgX1DjBXhNE2ihWWP0jj5z/jSOfMkbxjNQkFgaOPaV1ExAOXG9aO2qIi6m/DGRI YaI7Uy3rsm9oERiKJgN0Fyyt+zEqKg9PJM6GBEYfo5UVqQcn8Z+7VzoIkdNeXBWm ixnazo9MgWZWV8XstiW00LRP6LyuyNLeSBpbIHij7t270sMXHgaylxz/Kf4Q2Z2t qHa5+onvjUlpeyRTMzCo6qwn7ZdZOCRVCXG/sp96jGyr3W6i6t0gwg6MvxoIBVa2 PN6fFWO7Q4QheQy6hd+7j340zdc5Vn1wNFieXirUKBN509OzF/I= =oHMY -END PGP SIGNATURE-
Bug#1002193: package-update-indicator: FTBFS: package-update-indicator.c:25:10: fatal error: gtk/gtk.h: No such file or directory
Howdy, Can you retry that build? I'm not getting any error during build, but recently there was a problem with one of the development headers this package depends on, it did not depend on all packages listed in the .pc file. Can you ensure you try with libayatana-appindicator3-dev 0.5.90-5? -4 was broken. Thanks, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#978682: closing 978682
close 978682 2.0.1-1 thanks Howdy, I actually fixed this in my last upload, full changelog below: Changes: xfce4-verve-plugin (2.0.1-1) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 10 to 12. * Set debhelper-compat version in Build-Depends. * Apply multi-arch hints. + xfce4-verve-plugin: Add Multi-Arch: same. . [ Kentaro Hayashi ] * d/control: drop needless libdbus-glib-1-dev (Closes: #955856) . [ Unit 193 ] * d/watch: Update for mirrorbit and use uscan special strings. * New upstream version 2.0.1. - Fix build with panel 4.15 (Closes: #978190) * d/control: - Drop Build-Depends no longer needed: automake, libexo-1-dev, libtool, libstartup-notification0-dev, libxfce4ui-1-dev, libxml-parser-perl. - Remove Lionel Le Folgoc from Uploaders, thanks! - Add 'homepage' field. - R³: no. * d/docs: Install README.md. * d/manpages, d/verve-focus.1: Drop, the tool was removed. * Update Standards-Version to 4.5.1. Thanks! Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#978182: closing 978182
close 978182 0.5.2-1 thanks This bug was fixed in 0.5.2-1, changelog included: xfce4-smartbookmark-plugin (0.5.2-1) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Apply multi-arch hints. + xfce4-smartbookmark-plugin: Add Multi-Arch: same. . [ Unit 193 ] * d/watch: Update for mirrorbit and use uscan special strings. * New upstream version 0.5.2. * d/control: - Bump DH compat to 12. - Drop libgtk2.0-dev, libxml-parser-perl, libxml2-dev, and libxt-dev from Build-Depends. - Update 'Homepage' field, goodies.xfce â docs.xfce. - R³: no. * d/docs: Follow rename, README â README.md. * Update Standards-Version to 4.5.1. Upstream changelog: 0.5.2 == - Fix ISO C90 forbids mixed declarations and code - Update configure.ac.in syntax - Create README.md. Update configure.ac.in - Add basic GitLab pipeline - Update URLs from goodies.x.o to docs.x.o (Bug #16176) - Fix build with panel 4.15 - Make build less verbose - s/http/https - Translation Updates: Albanian, Belarusian, Bulgarian, Eastern Armenian, English (Canada), Estonian, Galician, Hebrew, Hindi, Icelandic, Slovak, Slovenian, Spanish, Turkish, Uyghur
Bug#936724: closing 936724
close 936724 3.0.0-1
thanks
This bug was fixed in 3.0.0 when it was ported to python 3. Changes below:
Changes:
ifupdown2 (3.0.0-1) unstable; urgency=medium
.
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with policy default
* New: ES bond with "es-sys-mac" attribute
* New: vxlan attribute: vxlan-mcastgrp-map
* New: support for "veth-peer-name" attribute
* New: dhcp policy: dhclient_retry_on_failure
* New: support for marking interfaces as mgmt interfaces
* New: bridge-vlan-vni-map attribute (single vxlan device)
* New: dhcp: skipping dhcp configuration if link-down yes
* New: vrf-slave: keep vlan down if lower device has "link-down yes"
* New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
* New: support for add ovs-ports-condone-regex attribute (openvswitch)
* Fix: dry-run exceptions
* Fix: bond enslavement ordering
* Fix: process MTU before addrgen
* Fix: set bridge MTU after bridge creation
* Fix: ifquery-running: incorrect displayed data
* Fix: tunnel configuration compatibility with ifupdown1
* Fix: start-networking script is back to handle mgmt & hotplug cases
* Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
* Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
* Removing python-argcomplete dependency
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#927134: closing 927134
close 927134 3.0.0-1
thanks
This bug was fixed in 3.0.0 when it was ported to python 3. Changes below:
Changes:
ifupdown2 (3.0.0-1) unstable; urgency=medium
.
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with policy default
* New: ES bond with "es-sys-mac" attribute
* New: vxlan attribute: vxlan-mcastgrp-map
* New: support for "veth-peer-name" attribute
* New: dhcp policy: dhclient_retry_on_failure
* New: support for marking interfaces as mgmt interfaces
* New: bridge-vlan-vni-map attribute (single vxlan device)
* New: dhcp: skipping dhcp configuration if link-down yes
* New: vrf-slave: keep vlan down if lower device has "link-down yes"
* New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
* New: support for add ovs-ports-condone-regex attribute (openvswitch)
* Fix: dry-run exceptions
* Fix: bond enslavement ordering
* Fix: process MTU before addrgen
* Fix: set bridge MTU after bridge creation
* Fix: ifquery-running: incorrect displayed data
* Fix: tunnel configuration compatibility with ifupdown1
* Fix: start-networking script is back to handle mgmt & hotplug cases
* Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
* Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
* Removing python-argcomplete dependency
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#967953: closing 967953
close 967953 3.0.0-1
thanks
This bug was fixed in 3.0.0 when it was ported to python 3. Changes below:
Changes:
ifupdown2 (3.0.0-1) unstable; urgency=medium
.
* New: python3 support
* New: attribute alias support
* New: bridge-always-up attribute
* New: set bridge mtu with policy default
* New: ES bond with "es-sys-mac" attribute
* New: vxlan attribute: vxlan-mcastgrp-map
* New: support for "veth-peer-name" attribute
* New: dhcp policy: dhclient_retry_on_failure
* New: support for marking interfaces as mgmt interfaces
* New: bridge-vlan-vni-map attribute (single vxlan device)
* New: dhcp: skipping dhcp configuration if link-down yes
* New: vrf-slave: keep vlan down if lower device has "link-down yes"
* New: vxlan: support for vxlan-svcnodeip6 and vxlan-mcastgrp6 (fixes #43)
* New: support for add ovs-ports-condone-regex attribute (openvswitch)
* Fix: dry-run exceptions
* Fix: bond enslavement ordering
* Fix: process MTU before addrgen
* Fix: set bridge MTU after bridge creation
* Fix: ifquery-running: incorrect displayed data
* Fix: tunnel configuration compatibility with ifupdown1
* Fix: start-networking script is back to handle mgmt & hotplug cases
* Fix: devices matching with ".{0,13}\-v" could get removed by ifreload
* Fix: mstpctl: check mstpctl-stp and bridge-stp and fix bridge cache update
* Removing python-argcomplete dependency
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#956992: closing 956992
close 956992 thanks Howdy, With the current version in Debian, this no longer seems to be an issue. Thanks, ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#960087: closing 960087
close 960087 thanks Howdy, This is a duplicate of bug 956869 and has been fixed in 1.0.20200429-2, then subsequently fixed when upstream moved from bc to pure bash in 1.0.20200506. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#948214: barriers sometimes runs with high load and use all memory
severity -1 normal , tag -1 moreinfo unreproducible thanks Howdy, some times the prozess barriers run with high load and use all memory: Can you be a little more precise as to how we can reproduce this? Perhaps some config, commandline options, state of machines in question, etc? There may be log output in ~/.xsession-errors as well. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#899495: marked as pending in ezstream
Control: tag -1 pending Hello, Bug #899495 in ezstream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/ezstream/commit/24e9d0715b8b27ab1175f55109b9d47384139d57 d/control: Change maintainer to Debian Multimedia Maintainers. Closes: #899495 (this message was generated automatically) -- Greetings https://bugs.debian.org/899495
Bug#923481: alpine: replies lose In-Reply-To and References headers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Control: severity -1 important Howdy, On Mon, 19 Aug 2019, Thorsten Glaser wrote: On Tue, 13 Aug 2019, Unit 193 wrote: Ah right. Though while looking through several of my recent sent items, it seems it preserved those fields as expected. I am using alpine 2.21. Please try this, from the original submission: I've confirmed this does indeed remove them. If I take a message, reply to it, then go to the Subject line, press ^K to remove the existing (possibly damaged) text and type new text (possibly to change the subthread subject), the eMail When just replying to a message without changing Subject, alpine indeed keeps the headers just fine. Given that it normally leaves the headers intact, and that the email client is still entirely usable even if you do hit this bug, I'm lowering the severity as it most certainly isn't RC worthy. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJdaZjPAAoJEFAB4bCao3RLlewP/i0i1bFwjq+ApIDXE8vI3rRe SqYn35l+v3o/RENmHIBJ+9DkJaRLkwwWr003Aeiup+/WdPzFV3QwWZDMoUQe9gu6 TwKwlIoA6dBscN448oUTK803B5uzRtOfFG0RVwes4EQD2qyh6BfyzlSrUtxEUWNB /SCenJ97B5pwH1NDMvgstVqctGlLrGXzGaiNbUxyWCYn2ZsJ2ovi8No5pOsvuOLV qHz4wxCa6VgYBdIVqUkVfZheihjQbZQ1I53X0+CvfyCB3KE41pb4NLANd06t+YAd m6Ygnu3SNk5ZN4+tcF0d7i3N0BH7zCqRGAQ/U2KjBcfDuMOndjUvNnk39/RZFkAA 4S4JqSaEgc8guuXzjJt6xg4hkAx8YGDJye1+l8D2vcs6hhhVYmeywMAQmV+m2vh3 x0WO3LLW8VJJPGjPCl9kYYNXv50+9Iq3YR/kIWtXrQ6sqWHST7grqnzFoY3/aWRm 6+vmKgUO1u4n/BOGv9tyAlTvqpe1lCzmbras8uy9x1qCxFtof2PC0OFLMg5Ro3vO Yj8026GBBTk26BzRExrToBjGMFazASTHMZsfftaCpEIF/AREmqui7QQkW2DnFfr6 7zrW4ysB+Gw63kMUFcRhpuFzZY4obpFINAEjuUCR3obPegc4X/UMsRi/eXnSfEta IYWC8wh3OJLVyINQMJrL =+IvI -END PGP SIGNATURE-
Bug#923084: Misuse of dh_python3
Howdy,
On Wed, 14 Aug 2019, Ben Finney wrote:
On 01-Apr-2019, Unit 193 wrote:
dh_python3 reads [its arguments such that] any path passed as an
argument is prefixed with 'debian/$package/', which in this case
ends up being 'debian/gandi-cli/debian/gandi-cli/...'
I can now confirm this difference.
The original described problem was that Debhelper was reading the
package control stanza's “Depends” field in the source package:
Depends: ${python3:Depends}, ${misc:Depends}
and incorrectly expanding its “python3:Depends” placeholder to an
empty dependency list in the binary package:
Depends:
When I change the ‘dh_python3’ arguments as Unit 193 describes, the
resulting “Depends” field in the binary package is:
Depends: python3-click (>= 7.0), python3-ipy,
python3-pkg-resources, python3-requests, python3-yaml,
python3:any
Unit 193, can you confirm that is correct to resolve this bug?
Just passing dh_python3 with no arguments does give me the expected value of
Depends: python3-click (>= 7.0), python3-ipy, python3-pkg-resources,
python3-requests, python3-yaml, python3:any
So yep, I can indeed confirm!
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#923481: alpine: replies lose In-Reply-To and References headers
Howdy, On Tue, 13 Aug 2019, Thorsten Glaser wrote: severity 923481 serious thanks (Please remember to Cc the bug submitter when replying.) On Sat, 9 Mar 2019, Unit 193 wrote: As I understand it, this is not a regression in alpine but a difference in how pine and alpine function, correct? No, this is definitively a serious loss of functionality, namely, message threading (which is expected to work correctly in contemporary MUAs excepting those from Redmond). Ah right. Though while looking through several of my recent sent items, it seems it preserved those fields as expected. I am using alpine 2.21. It seems I am unable to reproduce the results you're getting? ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#933731: marked as pending in audacity
Control: tag -1 pending Hello, Bug #933731 in audacity reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/audacity/commit/600d50b2ee5f0c0b31aa72c456b8bde4259776dd d/p/0006-Link-atomic-if-needed.patch: Link atomic if needed. Closes: #933731 (this message was generated automatically) -- Greetings https://bugs.debian.org/933731
Bug#923084: gandi-cli: Show ‘dh_python3’ where to find install requirements
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, On Sat, 20 Apr 2019, Ben Finney wrote: On 01-Apr-2019, Unit 193 wrote: dh_python3 reads the path as follows: Is this described anywhere in the ‘dh_python3’ manual page? The synopsis shows a ‘DIR’ parameter but that is never described. If it isn't in the manpage or /usr/share/doc/dh-python/* then I'd guess not. The excerpt above is from /usr/share/dh-python/dhpython/fs.py: Class Scan. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJcupDWAAoJEFAB4bCao3RLYWMQANl/iQL1/g3wGDRcnzFIfxtV wcPNyW/r87bSfTRoNKRDzD5jWmhL7NmPHEhvZzLpyIArP/xdvg2a4DCMmbaRhcAX yo4Ps2Wkyx4/3UyjxhDzSs2V7uASD6xc6l8Es/jzpuGGdLaz5CVuTTxoP1sM+2ao WBHbzN4zB99W/rFYg+n9wbobtViwK5RYY+v6Iq41eKR3SyIHZvIF5BNoBQL0yQBm 2eYAWn79p4302E20zQuLm1oRhWcOg2hYXofXxfjtupQeMLzBrb6ujJxN0ELL9EnQ CeTl0Koi4SHshZQv/n9HUGmVS5udl6XuCXk2sER297R8A1Rsk8SxXYaemJAMHbwI gv6yQ9SCtnIHrnSpOSUl9/N8+H/ThR3HUQmB9hN/kDEKipI0x+VBuj08M/gDynV2 V5D3LwBEhr6/VcZXBFVpXPrurmjArpmzdWoEN0ybGCgOMoaBcqsEAIRo7ieeH45M yURsPvLmbR08oHRpPGeeTx091PEQkQhps3DPW7FHZkpnVRfYk64+mF9D9LzO6TgO DhGOLLE2YwiHbTdVCoeQoq8rB/yJxPAC4Iullx5RfzGsvExntghzkiNZCNJvntm8 4lyyYNJ3Yb2Z17kdpvpDoKijt4duI1bNhJZst2uUzMi80VbxTzhWo8h/o/ML4+lB 2d0vnzPQxPvRwAp6IEph =Lh4X -END PGP SIGNATURE-
Bug#923084: Misuse of dh_python3
Howdy,
This problem occurs since dh_python3 is passed the Debian working directory as
follows:
dh_python3 -p ${APP_PACKAGE} ${working_dir}/${package_share_dir}/
Just trimming '${working_dir}' will solve this problem, though at this stage
dh_python3 could be called with no options and it would do the right thing.
dh_python3 reads the path as follows:
if not dpath:
self.proot = "debian/%s" % self.package
else:
dpath = dpath.strip('/')
self.proot = join('debian', self.package, dpath)
Meaning that any path passed as an argument is prefixed with
'debian/$package/', which in this case ends up being
'debian/gandi-cli/debian/gandi-cli/...'
As always, thanks for maintaining gandi-cli in Debian!
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#923481: alpine: replies lose In-Reply-To and References headers
Howdy, As I understand it, this is not a regression in alpine but a difference in how pine and alpine function, correct? ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#888163: closing 888163
close 888163 1:5.0.2-1 thanks Upstream fixed openssl incompatibilities. Debian changelog: ruby-net-ssh (1:5.0.2-1) unstable; urgency=medium . * Team upload. * New upstream version 5.0.2 - Drop patches, no longer needed. * d/compat, d/control: Bump dh compat to 11. * d/control: - Update Vcs-* fields, point to Salsa. - Replace ruby-rbnacl (build-)depend with ruby-ed25519. * Update Standards-Version to 4.1.4.
Bug#908609: gtkhash: diff for NMU version 1.1.1-3.1
Control: tags 908609 + patch
Control: tags 908609 + pending
Howdy,
I've prepared an NMU for gtkhash (versioned as 1.1.1-3.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
diff -Nru gtkhash-1.1.1/debian/changelog gtkhash-1.1.1/debian/changelog
--- gtkhash-1.1.1/debian/changelog 2018-07-16 07:46:10.0 -0400
+++ gtkhash-1.1.1/debian/changelog 2018-09-24 19:12:36.0 -0400
@@ -1,3 +1,13 @@
+gtkhash (1.1.1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Support thunarx-3 (Closes: #908609):
++ d/p/11-support-thunarx-3.patch: Add upstream commit to support thunarx-3.
++ d/control: Adjust build-dep: libthunarx-2-dev → libthunarx-3-dev.
++ d/thunar-gtkhash.install: Adapt to the thunarx-3 path.
+
+ -- Unit 193 Mon, 24 Sep 2018 19:12:36 -0400
+
gtkhash (1.1.1-3) unstable; urgency=medium
* Fix Vcs-*.
diff -Nru gtkhash-1.1.1/debian/control gtkhash-1.1.1/debian/control
--- gtkhash-1.1.1/debian/control2018-07-16 07:16:59.0 -0400
+++ gtkhash-1.1.1/debian/control2018-09-24 19:11:42.0 -0400
@@ -8,7 +8,7 @@
nettle-dev,
libgtk-3-dev (>= 3.0.0),
libnautilus-extension-dev (>= 3.0),
- libthunarx-2-dev,
+ libthunarx-3-dev,
libnemo-extension-dev,
libcaja-extension-dev,
intltool (>= 0.40.6),
diff -Nru gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch
gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch
--- gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 1969-12-31
19:00:00.0 -0500
+++ gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 2018-09-24
19:11:42.0 -0400
@@ -0,0 +1,54 @@
+From 9e35e3a0c248d57c62d064edbc14d3ed02c3bff8 Mon Sep 17 00:00:00 2001
+From: Tristan Heaven
+Date: Sun, 20 May 2018 18:02:05 +0100
+Subject: [PATCH] add --with-thunarx= configure option for selecting thunarx
+ version (fixes #21)
+
+---
+ configure.ac | 14 ++
+ 1 file changed, 10 insertions(+), 4 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 9b474f2..fd1f99c 100644
+--- a/configure.ac
b/configure.ac
+@@ -69,7 +69,7 @@ GLIB_GSETTINGS
+ # check for gtk+ {{{
+ AC_MSG_CHECKING([which GTK+ version to use])
+ AC_ARG_WITH([gtk],
+- [AS_HELP_STRING([--with-gtk=2.0|3.0], [GTK+ version to use [3.0]])],
++ [AS_HELP_STRING([--with-gtk=2.0|3.0], [GTK+ version to use
[default=3.0]])],
+ [with_gtk="${withval}"], [with_gtk="3.0"])
+ AC_MSG_RESULT([${with_gtk}])
+
+@@ -340,12 +340,18 @@ AC_ARG_ENABLE([thunar],
+ AC_MSG_RESULT([${enable_thunar}])
+ AM_CONDITIONAL([ENABLE_THUNAR], [test "${enable_thunar}" = "yes"])
+
++AC_MSG_CHECKING([which Thunarx version to use])
++AC_ARG_WITH([thunarx],
++ [AS_HELP_STRING([--with-thunarx=2|3], [Thunarx version to use
[default=3]])],
++ [with_thunar="${withval}"], [with_thunarx="3"])
++AC_MSG_RESULT([${with_thunarx}])
++
+ if test "${enable_thunar}" = "yes" ; then
+ # Check for thunar
+- PKG_CHECK_MODULES([THUNAR], [thunarx-2])
++ PKG_CHECK_MODULES([THUNAR], ["thunarx-${with_thunarx}"])
+ AC_SUBST([THUNAR_CFLAGS])
+ AC_SUBST([THUNAR_LIBS])
+- THUNAR_EXTENSION_DIR=`${PKG_CONFIG} --variable=extensionsdir thunarx-2`
++ THUNAR_EXTENSION_DIR=`${PKG_CONFIG} --variable=extensionsdir
"thunarx-${with_thunarx}"`
+ AC_SUBST([THUNAR_EXTENSION_DIR])
+ fi
+ # }}}
+@@ -392,7 +398,7 @@ echo " gtkhash: ${enable_gtkhash} (gtk+-${with_gtk})"
+ echo " gtkhash-caja: ${enable_caja}"
+ echo " gtkhash-nautilus: ${enable_nautilus}"
+ echo " gtkhash-nemo: ${enable_nemo}"
+-echo " gtkhash-thunar: ${enable_thunar}"
++echo " gtkhash-thunar: ${enable_thunar} (thunarx-${with_thunarx})"
+
+ blake2_funcs="
+ BLAKE2b BLAKE2s BLAKE2bp BLAKE2sp"
+
diff -Nru gtkhash-1.1.1/debian/patches/series
gtkhash-1.1.1/debian/patches/series
--- gtkhash-1.1.1/debian/patches/series 2018-07-16 07:14:44.0 -0400
+++ gtkhash-1.1.1/debian/patches/series 2018-09-24 19:11:42.0 -0400
@@ -2,3 +2,4 @@
20-fix-component-id.patch
30-add-image-screenshot.patch
40-fix-invalid-tags.patch
+50-support-thunarx-3.patch
diff -Nru gtkhash-1.1.1/debian/thunar-gtkhash.install
gtkhash-1.1.1/debian/thunar-gtkhash.install
--- gtkhash-1.1.1/debian/thunar-gtkhash.install 2017-12-19 02:45:34.0
-0500
+++ gtkhash-1.1.1/debian/thunar-gtkhash.install 2018-09-24 19:11:42.0
-0400
@@ -1,2 +1,2 @@
-usr/lib/*/thunarx-2/libgtkhash-properties-thunar.so
+usr/lib/*/thunarx-3/libgtkhash-properties-thunar.so
usr/share/appdata/thunar-gtkhash.metainfo.xml usr/share/metainfo
Bug#908609: gtkhash: cannot fulfill the build dependencies
Howdy,
A solution to the problem is to pull a commit from upstream and adjust the
packaging, patch attached.
~Unit 193
Unit193 @ freenode
Unit193 @ OFTCdiff -Nru gtkhash-1.1.1/debian/changelog gtkhash-1.1.1/debian/changelog
--- gtkhash-1.1.1/debian/changelog 2018-07-16 07:46:10.0 -0400
+++ gtkhash-1.1.1/debian/changelog 2018-09-11 17:30:43.0 -0400
@@ -1,3 +1,11 @@
+gtkhash (1.1.1-3.1) unstable; urgency=medium
+
+ * d/p/11-support-thunarx-3.patch: Add upstream commit to support thunarx-3.
+ * d/control: Adjust build-dep: libthunarx-2-dev → libthunarx-3-dev.
+ * d/thunar-gtkhash.install: Adapt to the thunarx-3 path.
+
+ -- Unit 193 Tue, 11 Sep 2018 17:30:43 -0400
+
gtkhash (1.1.1-3) unstable; urgency=medium
* Fix Vcs-*.
diff -Nru gtkhash-1.1.1/debian/control gtkhash-1.1.1/debian/control
--- gtkhash-1.1.1/debian/control2018-07-16 07:16:59.0 -0400
+++ gtkhash-1.1.1/debian/control2018-09-11 17:30:43.0 -0400
@@ -8,7 +8,7 @@
nettle-dev,
libgtk-3-dev (>= 3.0.0),
libnautilus-extension-dev (>= 3.0),
- libthunarx-2-dev,
+ libthunarx-3-dev,
libnemo-extension-dev,
libcaja-extension-dev,
intltool (>= 0.40.6),
diff -Nru gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch
gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch
--- gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 1969-12-31
19:00:00.0 -0500
+++ gtkhash-1.1.1/debian/patches/50-support-thunarx-3.patch 2018-09-11
17:30:43.0 -0400
@@ -0,0 +1,54 @@
+From 9e35e3a0c248d57c62d064edbc14d3ed02c3bff8 Mon Sep 17 00:00:00 2001
+From: Tristan Heaven
+Date: Sun, 20 May 2018 18:02:05 +0100
+Subject: [PATCH] add --with-thunarx= configure option for selecting thunarx
+ version (fixes #21)
+
+---
+ configure.ac | 14 ++
+ 1 file changed, 10 insertions(+), 4 deletions(-)
+
+diff --git a/configure.ac b/configure.ac
+index 9b474f2..fd1f99c 100644
+--- a/configure.ac
b/configure.ac
+@@ -69,7 +69,7 @@ GLIB_GSETTINGS
+ # check for gtk+ {{{
+ AC_MSG_CHECKING([which GTK+ version to use])
+ AC_ARG_WITH([gtk],
+- [AS_HELP_STRING([--with-gtk=2.0|3.0], [GTK+ version to use [3.0]])],
++ [AS_HELP_STRING([--with-gtk=2.0|3.0], [GTK+ version to use
[default=3.0]])],
+ [with_gtk="${withval}"], [with_gtk="3.0"])
+ AC_MSG_RESULT([${with_gtk}])
+
+@@ -340,12 +340,18 @@ AC_ARG_ENABLE([thunar],
+ AC_MSG_RESULT([${enable_thunar}])
+ AM_CONDITIONAL([ENABLE_THUNAR], [test "${enable_thunar}" = "yes"])
+
++AC_MSG_CHECKING([which Thunarx version to use])
++AC_ARG_WITH([thunarx],
++ [AS_HELP_STRING([--with-thunarx=2|3], [Thunarx version to use
[default=3]])],
++ [with_thunar="${withval}"], [with_thunarx="3"])
++AC_MSG_RESULT([${with_thunarx}])
++
+ if test "${enable_thunar}" = "yes" ; then
+ # Check for thunar
+- PKG_CHECK_MODULES([THUNAR], [thunarx-2])
++ PKG_CHECK_MODULES([THUNAR], ["thunarx-${with_thunarx}"])
+ AC_SUBST([THUNAR_CFLAGS])
+ AC_SUBST([THUNAR_LIBS])
+- THUNAR_EXTENSION_DIR=`${PKG_CONFIG} --variable=extensionsdir thunarx-2`
++ THUNAR_EXTENSION_DIR=`${PKG_CONFIG} --variable=extensionsdir
"thunarx-${with_thunarx}"`
+ AC_SUBST([THUNAR_EXTENSION_DIR])
+ fi
+ # }}}
+@@ -392,7 +398,7 @@ echo " gtkhash: ${enable_gtkhash} (gtk+-${with_gtk})"
+ echo " gtkhash-caja: ${enable_caja}"
+ echo " gtkhash-nautilus: ${enable_nautilus}"
+ echo " gtkhash-nemo: ${enable_nemo}"
+-echo " gtkhash-thunar: ${enable_thunar}"
++echo " gtkhash-thunar: ${enable_thunar} (thunarx-${with_thunarx})"
+
+ blake2_funcs="
+ BLAKE2b BLAKE2s BLAKE2bp BLAKE2sp"
+
diff -Nru gtkhash-1.1.1/debian/patches/series
gtkhash-1.1.1/debian/patches/series
--- gtkhash-1.1.1/debian/patches/series 2018-07-16 07:14:44.0 -0400
+++ gtkhash-1.1.1/debian/patches/series 2018-09-11 17:30:43.0 -0400
@@ -2,3 +2,4 @@
20-fix-component-id.patch
30-add-image-screenshot.patch
40-fix-invalid-tags.patch
+50-support-thunarx-3.patch
diff -Nru gtkhash-1.1.1/debian/thunar-gtkhash.install
gtkhash-1.1.1/debian/thunar-gtkhash.install
--- gtkhash-1.1.1/debian/thunar-gtkhash.install 2017-12-19 02:45:34.0
-0500
+++ gtkhash-1.1.1/debian/thunar-gtkhash.install 2018-06-05 17:29:28.0
-0400
@@ -1,2 +1,2 @@
-usr/lib/*/thunarx-2/libgtkhash-properties-thunar.so
+usr/lib/*/thunarx-3/libgtkhash-properties-thunar.so
usr/share/appdata/thunar-gtkhash.metainfo.xml usr/share/metainfo
Bug#851076: Merge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, I filed a merge request a couple of months ago that should fix this (and #887662) on salsa[0], Ubuntu seems to have picked it up and shipped it with their last release. [0]: https://salsa.debian.org/takaki/gvpe/merge_requests/1 ~Unit 193 Unit193 @ OFTC Unit193 @ freenode -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJa9LJ/AAoJEFAB4bCao3RLrvUP/2H3DIbCTSMDcCuyUmTz08NT oGjoApFOjVMYq1kpxOk1lryWUxZclmShWgeUsixJnv8XMDMcdzSVxmbZ6yR/C1wo ZkoJhDuaHXlsqqcTiYo44UmuaeVbdTmJjLKRrSDE8LaFfOfX/RhvuyY/T8ebc0u9 zpUsQOnnzTYgFoRemg0nO4ITJv8uQVizjZNEAKvVrWCVOZiIWvWZszpesEn5O5eD Pk+gjek1f5wBekvozjuTcN3P2skTIr+e1OAVD5/KOResIuvZGoHOYGTk75l3UpNj bMP3mGolpSfTEcLCH7V+2gTrOVGnml5AHT3bJgaq0WTR642+nCw2VIVjwMLcTxjl ilsOQXya51n5CwRtWmXulrvGcb9xzJjtxfFkoqKLwQtUB3YVePxAZ1t5w1RMmDmd ximbQUCm/b1UcyA8PT0oQ0AIdTSh+F/9uKL9wIRa225Xwx0PD1z9M+G3hfjc/MJx KczNF4Eg4DUie1VxOwB07vxBRlGA6vuYojMbiN+a/MZUfitWgiwFqyI/bnckxr0b L554m77upIl60IEaNb+PqWigYT48snhxftrZ6XMaT8Sg5iroED4VvTyriVHqc7OL nTJ8bhAWmH7PEXP9hd0OsgQk9d+EbgITMOoJ9Xvm2+WgCraqUzLVRfMJBOQRaw1Y VEtWManoMQln6oI3+ZzT =S31p -END PGP SIGNATURE-
Bug#886068: gtk-theme-config: raising severity of gconf dependency bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, As Simon indicated, gtk-theme-config won't really function properly anytime in the near future and has been removed from Xubuntu's seed. So as maintainer of the package I would gladly accept your offer to file the removal bug. Thank you for offering. On Tue, 27 Feb 2018, Jeremy Bicha wrote: On Tue, Feb 27, 2018 at 4:05 PM, Simon Steinbeiss <simon.steinbe...@gmail.com> wrote: So we will likely drop it from Xubuntu 18.04 and it will become deprecated. I guess Debian should drop it too, can't imagine anyone still uses it for anything (only the Gtk2 parts still work ok). I'd be happy to file a Debian removal bug for gtk-theme-config if that's what y'all want. (I'm not subscribed to the list so you'll probably need to moderate me through.) Thanks, Jeremy Bicha -- xubuntu-devel mailing list xubuntu-de...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel ~Unit 193 Unit193 @ freenode Unit193 @ OFTC -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJavMDlAAoJEFAB4bCao3RLMSMP/Ag5yf9AmRsyIP+OvPVPtVEe /69ZCCDSKaTaY5++YiatZ9DRRw/R6DltvnA4gaot0TdXHf8p5DLodWuh+Wy/ncJz UspZNi00fCsblBLLyTT0dbgU6j/be9ofKIe1gnUwiKEmstol2cNaIFwdS99ZdJL6 y9/SS+qaQ9a3JGBiLeTFtdTbXPIHECutqzIAVd/lU2hHnnY7pzm6GGqcMcfhiQLU 2lKsLmkLFJ0v2SKHx2gXxrGNYX1wZH5L6IGTg9yhGk0TAIGM1SZjaZXEl1jFsnND yJ9CwI0+Nm1LX6XCVGC+bskdAlou5dPywcDVbxZCbJ1F7J7WZyNR5QvJPIqI9Zxi 8xni3Kt+aoEJZUjFmIPD0PXYpud/m8TK+xXxh6lkflt9HN1F0pQpr8MHkvmA3Qix sWznMLo3Q6ENUWKNVYQwuRjKush3ZkTHiFICvkqpZpj5brh7kxZV3aDzE3E/7PA9 IdagE7+qzwiEIild4TtPnlEWv63y8N3F+u6+Wl4Zo5KatXWv7x3QBAawiDM6EWsV R4o3L2zM4SElR5LGwLJV9ZGBP/tnRWPtPFSbp72fu7CgVFzviZKFEi8uLN7x1ma2 247Mq4w5YWQ8ikdy5/S5co5TR+n6azRfAf4hQl2ITva8pGNfsoGxNRV2lAr4Hva8 fPyOcPwiqU2JL0HqUeev =DljL -END PGP SIGNATURE-
Bug#869176: closing 869176
close 869176 thanks This was due to an incompatibility in ruby-specinfra with net-ssh 4.x, this has been fixed and tests for itamae are passing now.
Bug#875965: marked as pending
tag 875965 pending thanks Hello, Bug #875965 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-net-ssh.git/commit/?id=df4cdb0 --- commit df4cdb09b73b09d99f19db8b459254e618027a99 Author: Unit 193 <unit...@ubuntu.com> Date: Sat Sep 23 20:47:57 2017 -0400 Update changelog for release. diff --git a/debian/changelog b/debian/changelog index ca6de79..a7197b8 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +ruby-net-ssh (1:4.2.0-2) unstable; urgency=medium + + * d/control, d/copyright: Use https in format and homepage fields. + * d/p/missing_logger.patch: Add a missing require on 'logger' to fix ftbfs. +(Closes: #875965) + + -- Unit 193 <unit...@ubuntu.com> Sat, 23 Sep 2017 20:47:13 -0400 + ruby-net-ssh (1:4.2.0-1) unstable; urgency=medium * Team upload.
Bug#871093: marked as pending
tag 871093 pending thanks Hello, Bug #871093 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-rbnacl.git/commit/?id=32baa0c --- commit 32baa0c0e186b5cf769338fc06304fc5229996f5 Author: Unit 193 <unit...@ubuntu.com> Date: Thu Aug 31 06:42:31 2017 -0400 Update changelog for release. diff --git a/debian/changelog b/debian/changelog index 206b291..a6896dc 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +ruby-rbnacl (5.0.0-2) unstable; urgency=medium + + * d/p/0006-fix-blake2b_state-struct-size.patch: +- Add patch from Ubuntu: pad blake2b_state struct declaration for libsodium + 1.0.13. Thanks to Steve Langasek for the patch. (Closes: #871093) + * Update Standards-Version to 4.1.0. + + -- Unit 193 <unit...@ubuntu.com> Thu, 31 Aug 2017 06:33:43 -0400 + ruby-rbnacl (5.0.0-1) unstable; urgency=medium * Team upload.
Bug#869179: marked as pending
tag 869179 pending thanks Hello, Bug #869179 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/chef.git/commit/?id=e3c5819 --- commit e3c58192c915f98983920799e4fb3c773fcd0139 Author: Unit 193 <unit...@ubuntu.com> Date: Mon Aug 7 05:17:43 2017 -0400 Update changelog. diff --git a/debian/changelog b/debian/changelog index ccbc2ee..f151847 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,8 @@ chef (12.14.60-3) UNRELEASED; urgency=medium + * Team upload. + + [ Stefano Rivera ] * Build-Depend on ruby-fuzzyurl, rather than relying on it's indirect presence via ohai -> ruby-chef-config. * Blacklist mount_spec and ifconfig_spec, as they require real root. @@ -9,7 +12,12 @@ chef (12.14.60-3) UNRELEASED; urgency=medium * Unset http[s]_proxy in the subversion spec, so it doesn't alter generated subversion commands. - -- Stefano Rivera <stefa...@debian.org> Tue, 15 Nov 2016 12:04:08 +0100 + [ Unit 193 ] + * Bump Standards-Version to 4.0.1. + * d/p/0004-Use-newer-net-ssh.patch: +- Relax dependency on ruby-net-ssh (Closes: #869179) + + -- Unit 193 <unit...@ubuntu.com> Mon, 07 Aug 2017 05:01:33 -0400 chef (12.14.60-2) unstable; urgency=medium
Bug#869174: marked as pending
tag 869174 pending thanks Hello, Bug #869174 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-net-sftp.git/commit/?id=cf6db01 --- commit cf6db01175775f58af04c1347af79f7d43a01b44 Author: Unit 193 <unit...@ubuntu.com> Date: Mon Jul 24 02:23:58 2017 -0400 d/p/add_net-ssh_4.0_compatibility.patch: Add an upstream commit to fix compatibility with net-ssh 4.x. diff --git a/debian/changelog b/debian/changelog index 41237f4..a28e542 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ruby-net-sftp (1:2.1.2-4) UNRELEASED; urgency=medium + + * d/p/add_net-ssh_4.0_compatibility.patch: (Closes: #869174) +- Add an upstream commit to fix compatibility with net-ssh 4.x. + + -- Unit 193 <unit...@ubuntu.com> Mon, 24 Jul 2017 02:14:23 -0400 + ruby-net-sftp (1:2.1.2-3) unstable; urgency=medium * Upload to unstable now that jessie is released.
Bug#790012: closing 790012
close 790012 thanks This was indeed a "dupe" of http://bugs.debian.org/789253 and has been fixed for a while now.
