Bug#987753: closed by Debian FTP Masters (reply to Unit 193 ) (Bug#987753: fixed in yt-dlp 2023.09.24-1)
G'day, On Mon, 9 Oct 2023, Christoph Anton Mitterer wrote: Hey Unit 193. Just a heads up: I recently filed https://github.com/yt-dlp/yt-dlp/issues/8193 and it was implemented via: https://github.com/yt-dlp/yt-dlp/pull/8205 So in future versions you can drop the Recommends on: python3-xattr | python3-pyxattr | attr probably altogether. Nice going! Thanks very much for the heads-up, it's quite easy to lose track of deprecated dependencies so this note is quite useful. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1052527: nagios4: New upstream release available
Source: nagios4 Severity: wishlist Dear Maintainer, Please update nagios4 in Debian as, at the time of this writing, 4.4.14 is available upstream and Debian is on 4.4.6. If the added depend of openssl is a concern, nowdays openssl is apache licensed so compatible with this package (which also has apache licensed code) Thanks! ~Unit 193 Unit193 @ OFTC Unit193 @ Libera -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (300, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1043242: highlight: new upstream version
Howdy,
Actually at the time of this writing, 4.7 is the current release. I had
gone ahead and jumped to the latest version a while ago, mainly to unify
my system on one Lua version, and I've attached the debdiff (debian/ only)
to this message.
Use it, don't use it, or laugh at it. I don't care about attribution so
just claim it even if you want.
Note: The only place I use highlight is with cgit.
Regards,
~Unit 193
Unit193 @ Libera
Unit193 @ OFTCdiff -Nur highlight-3.41/debian/changelog highlight-4.7/debian/changelog
--- highlight-3.41/debian/changelog 2018-07-27 05:25:44.0 -0400
+++ highlight-4.7/debian/changelog 2023-08-07 17:21:57.862529038 -0400
@@ -1,3 +1,27 @@
+highlight (4.7-0) UNRELEASED; urgency=medium
+
+ * New upstream release.
+- Refresh patches.
+ * d/compat, d/control: Replace d/compat with debhelper-compat, bump to 13.
+ * d/control:
+- R³: no.
+- Replace Lua Build-Depend to liblua5.4-dev.
+ * d/docs: Update paths and drop TODO.
+ * d/highlight-common.install: Update paths and install plugins, completions.
+ * d/highlight.(examples,install): Update paths.
+ * d/libhighlight-perl.(examples,install): Ditto.
+ * d/highlight.manpages: Update name and add filetypes.conf.5.
+ * d/not-installed: Add otherwise installed and extraneous files.
+ * d/rules:
+- Drop get-orig-source target.
+- Override dh_installchangelogs to install ChangeLog.adoc.
+- Enable all hardening options.
+- Pass LUA_LIBS=-llua5.4.
+ * Update Standards-Version to 4.6.2.
+ * Remove trailing whitespace from previous changelog entries.
+
+ -- Unit 193 Thu, 03 Aug 2023 20:57:55 -0400
+
highlight (3.41-2) unstable; urgency=medium
* Fix location of examples (Closes: #904727).
@@ -171,7 +195,7 @@
* New upstream version
- restores @highlight pass-through
-
+
-- David Bremner Wed, 29 Dec 2010 16:16:12 -0400
highlight (3.2+svn19-1) experimental; urgency=low
@@ -221,7 +245,7 @@
* New Upstream 2.14
* convert to 3.0 (quilt) source format to support tar.bz2 upstream
-
+
-- David Bremner Mon, 15 Feb 2010 08:55:16 -0400
highlight (2.12-1) unstable; urgency=low
@@ -236,7 +260,7 @@
* New upstream version.
* Change from co-maintainer/uploader to maintainer (Closes: #541332)
* Update standards version to 3.8.3 (no changes)
-
+
-- David Bremner Thu, 27 Aug 2009 22:45:19 -0300
highlight (2.10-1) unstable; urgency=low
@@ -318,7 +342,7 @@
highlight (2.2.6-2) unstable; urgency=low
- * applied patch to fix amd64 building error using gcc-4.0
+ * applied patch to fix amd64 building error using gcc-4.0
Thanks to Andreas Jochens (closes: #286352)
-- Ayman Negm Tue, 21 Dec 2004 21:09:35 +0100
@@ -386,5 +410,3 @@
* Initial Release (closes: #218144).
-- Ayman Negm Fri, 20 Feb 2004 09:40:57 +0100
-
-
diff -Nur highlight-3.41/debian/compat highlight-4.7/debian/compat
--- highlight-3.41/debian/compat2018-07-27 05:25:44.0 -0400
+++ highlight-4.7/debian/compat 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-10
diff -Nur highlight-3.41/debian/control highlight-4.7/debian/control
--- highlight-3.41/debian/control 2018-07-27 05:25:44.0 -0400
+++ highlight-4.7/debian/control2023-03-16 20:59:16.0 -0400
@@ -2,12 +2,13 @@
Section: devel
Priority: optional
Maintainer: David Bremner
-Build-Depends: debhelper (>= 10), swig, liblua5.2-dev, libboost-dev,
- pkg-config
-Standards-Version: 4.0.0
+Build-Depends: debhelper-compat (= 13), swig, liblua5.4-dev, libboost-dev,
+ pkg-config
+Rules-Requires-Root: no
+Standards-Version: 4.6.2
Homepage: http://www.andre-simon.de
Vcs-Git: https://salsa.debian.org/bremner/highlight.git
-Vcs-Browser: https://salsa.debian.org/bremner/highlight.git
+Vcs-Browser: https://salsa.debian.org/bremner/highlight
Package: highlight
@@ -23,7 +24,7 @@
Package: highlight-common
Architecture: all
-Depends: ${misc:Depends}
+Depends: ${misc:Depends}
Breaks: highlight (<<3.2), libhighlight-perl (<<3.2), gtk-doc-tools (<< 1.17-2)
Replaces: highlight (<<2.9)
Description: source code to formatted text converter (architecture independent
files)
diff -Nur highlight-3.41/debian/docs highlight-4.7/debian/docs
--- highlight-3.41/debian/docs 2018-07-27 05:25:44.0 -0400
+++ highlight-4.7/debian/docs 2021-02-13 01:54:21.0 -0500
@@ -1,5 +1 @@
-README
-README_DE
-README_LANGLIST
-README_REGEX
-TODO
+usr/share/doc/highlight/README*
diff -Nur highlight-3.41/debian/highlight-common.install
highlight-4.7/debian/highlight-common.install
--- highlight-3.41/debian/highlight-common.install 2018-07-27
05:25:44.0 -0400
+++ highlight-4.7/debian/highlight-common.install 2022-10-15
20:51:55.0 -0400
@@ -1,4 +1,7 @@
-usr/share/highlight/langDefs/* usr/share/highlight/langDefs
-etc/highlight/*etc/hig
Bug#1041517: sendemail: diff for NMU version 1.56-5.2
Package: sendemail
Version: 1.56-5.1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for sendemail (versioned as 1.56-5.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru sendemail-1.56/debian/changelog sendemail-1.56/debian/changelog
--- sendemail-1.56/debian/changelog 2021-01-01 10:47:46.0 -0500
+++ sendemail-1.56/debian/changelog 2023-08-04 17:32:05.0 -0400
@@ -1,3 +1,12 @@
+sendemail (1.56-5.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/p/fix_tls_hostname_verification.patch: Fix TLS hostname verification.
+Closes: #1041517.
+ * d/control, Update 'homepage' field. (Closes: #884459)
+
+ -- Unit 193 Fri, 04 Aug 2023 17:32:05 -0400
+
sendemail (1.56-5.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru sendemail-1.56/debian/control sendemail-1.56/debian/control
--- sendemail-1.56/debian/control 2013-09-01 09:20:32.0 -0400
+++ sendemail-1.56/debian/control 2023-08-04 17:31:54.0 -0400
@@ -4,7 +4,7 @@
Maintainer: Alejandro Garrido Mota
Build-Depends: debhelper (>= 9)
Standards-Version: 3.9.4
-Homepage: http://www.caspian.dotconf.net/menu/Software/SendEmail/
+Homepage: http://caspian.dotconf.net/menu/Software/SendEmail/
Vcs-Git: git://github.com/mogaal/sendemail.git
Vcs-Browser: https://github.com/mogaal/sendemail
diff -Nru sendemail-1.56/debian/patches/fix_tls_hostname_verification.patch
sendemail-1.56/debian/patches/fix_tls_hostname_verification.patch
--- sendemail-1.56/debian/patches/fix_tls_hostname_verification.patch
1969-12-31 19:00:00.0 -0500
+++ sendemail-1.56/debian/patches/fix_tls_hostname_verification.patch
2023-08-04 17:31:54.0 -0400
@@ -0,0 +1,23 @@
+Description: Fix TLS hostname verification.
+Author: Unit 193
+Forwarded: no
+Bug: #1041517
+
+---
+ sendEmail |5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+--- a/sendEmail
b/sendEmail
+@@ -1930,7 +1930,10 @@ if( $conf{'use_sendmail'} ) {
+ if ($conf{'tls_server'} == 1 and $conf{'tls_client'} == 1 and
$opt{'tls'} =~ /^(yes|auto)$/) {
+ printmsg("DEBUG => Starting TLS", 2);
+ if (SMTPchat('STARTTLS')) { quit($conf{'error'}, 1); }
+-if (! IO::Socket::SSL->start_SSL($SERVER, SSL_version =>
'SSLv23:!SSLv2')) {
++if (! IO::Socket::SSL->start_SSL($SERVER,
++ SSL_version => 'TLSv12:!SSLv2',
++ SSL_verifycn_scheme => 'smtp',
++ SSL_verifycn_name => $conf{'server'})) {
+ quit("ERROR => TLS setup failed: " .
IO::Socket::SSL::errstr(), 1);
+ }
+ printmsg("DEBUG => TLS: Using cipher: ". $SERVER->get_cipher(),
3);
diff -Nru sendemail-1.56/debian/patches/series
sendemail-1.56/debian/patches/series
--- sendemail-1.56/debian/patches/series2013-09-01 09:20:32.0
-0400
+++ sendemail-1.56/debian/patches/series2023-08-04 17:31:54.0
-0400
@@ -1,3 +1,4 @@
fix_ssl_version.patch
add-ipv6-support.patch
local-sendmail.patch
+fix_tls_hostname_verification.patch
Bug#1040011: mate-polkit: Allow mate-polkit to be used in Xfce, Cinnamon, and other desktops
Source: mate-polkit Severity: wishlist Dear Maintainer, As policykit-1-gnome is slated for removal from Trixie (#990271), and it's the most generic policykit agent, it would be quite useful if mate-polkit could be utilized on other desktops. In https://bugs.debian.org/990259 there was a discussion where mate-polkit could be useful to Cinnamon, and I would find it useful on an Xfce desktop. Below is a patch to mate-polkit's desktop file to allow it to run on other desktops, of course you may prefer to expand the whitelist rather than simply blacklisting KDE and GNOME. Thanks! ~Unit 193 Unit193 @ OFTC Unit193 @ Libera Description: Allow mate-polkit to be used in Xfce, Cinnamon, etc. --- src/polkit-mate-authentication-agent-1.desktop.in.in |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/src/polkit-mate-authentication-agent-1.desktop.in.in +++ b/src/polkit-mate-authentication-agent-1.desktop.in.in @@ -5,5 +5,5 @@ Exec=@FULL_LIBEXECDIR@/polkit-mate-authe Terminal=false Type=Application NoDisplay=true -OnlyShowIn=MATE; +NotShowIn=GNOME;KDE; X-MATE-AutoRestart=true
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#1032320: yt-dlp: Please include built manpage into package
Howdy, On Sat, 4 Mar 2023, debian.fab@erine.email wrote: Hmm, my bad, this only appears on the backported package: % dpkg -c yt-dlp_2023.02.17-1_all.deb | grep -F yt-dlp.1 -rw-r--r-- root/root    39545 2023-02-18 00:37 /usr/share/man/man1/yt-dlp.1.gz % dpkg -c yt-dlp_2023.02.17-1\~bpo11+1_all.deb | grep -F yt-dlp.1 -rw-r--r-- root/root   133597 2023-02-28 06:30 /usr/lib/python3/dist-packages/share/man/man1/yt-dlp.1 Maybe the build tools are behaving differently on Bullseye. The patch I suggested makes the man available on the backported deb file built on Bullseye. Do you think applying it would make the man available in both cases? Ah interesting! I didn't see that. Interestingly, the current release that's in unstable doesn't appear to have this problem when rebuilt for stable: drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/lib/python3/dist-packages/yt_dlp-2023.3.4.dist-info/ drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/share/fish/ drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/share/fish/vendor_completions.d/ -rw-r--r-- root/root 49319 2023-03-08 04:50 ./usr/share/fish/vendor_completions.d/yt-dlp.fish drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/share/man/ drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/share/man/man1/ -rw-r--r-- root/root 40205 2023-03-08 04:50 ./usr/share/man/man1/yt-dlp.1.gz drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/share/zsh/ drwxr-xr-x root/root 0 2023-03-08 04:50 ./usr/share/zsh/site-functions/ -rw-r--r-- root/root 6170 2023-03-08 04:50 ./usr/share/zsh/site-functions/_yt-dlp So unless something differs in my stable chroot (or pbuilder), this appears to be something that's now fixed! At this point, with bookworm right around the corner, yt-dlp backports are soon to stop for bullseye anyway. Regards, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC Thanks, Fab On 04/03/2023 01:00, Unit 193 - unit...@unit193.net wrote: Howdy, On Fri, 3 Mar 2023, Fab wrote: Package: yt-dlp Version: 2023.02.17-1 Severity: normal Tags: patch X-Debbugs-Cc: debian.fab@erine.email Hello, provided patch just adds the debian/yt-dlp.manpages The file only contains "yt-dlp.1" (built in the root dir). This allows one to use `man yt-dlp`. Umm. Did you try that now? Perhaps you should. unit193@Loki:~$ dpkg -L yt-dlp | grep man1/yt-dlp /usr/share/man/man1/yt-dlp.1.gz unit193@Loki:~$ man yt-dlp | wc -l 2462 unit193@Loki:~$ apt-cache policy yt-dlp yt-dlp:  Installed: 2023.02.17-1  Candidate: 2023.02.17-1  Version table:  *** 2023.02.17-1 500        100 http://deb.debian.org/debian unstable/main amd64 Packages        100 /var/lib/dpkg/status As you can see here, the package already ships a manpage. Perhaps you installed from somewhere else? You can also view it online: https://manpages.debian.org/testing/yt-dlp/yt-dlp.1.en.html ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1032320: yt-dlp: Please include built manpage into package
Howdy, On Fri, 3 Mar 2023, Fab wrote: Package: yt-dlp Version: 2023.02.17-1 Severity: normal Tags: patch X-Debbugs-Cc: debian.fab@erine.email Hello, provided patch just adds the debian/yt-dlp.manpages The file only contains "yt-dlp.1" (built in the root dir). This allows one to use `man yt-dlp`. Umm. Did you try that now? Perhaps you should. unit193@Loki:~$ dpkg -L yt-dlp | grep man1/yt-dlp /usr/share/man/man1/yt-dlp.1.gz unit193@Loki:~$ man yt-dlp | wc -l 2462 unit193@Loki:~$ apt-cache policy yt-dlp yt-dlp: Installed: 2023.02.17-1 Candidate: 2023.02.17-1 Version table: *** 2023.02.17-1 500 100 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status As you can see here, the package already ships a manpage. Perhaps you installed from somewhere else? You can also view it online: https://manpages.debian.org/testing/yt-dlp/yt-dlp.1.en.html ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1031775: yt-dlp prompts for the user to download PhantomJS
Howdy, On Wed, 22 Feb 2023, Daniel Kahn Gillmor wrote: Package: yt-dlp Version: 2023.01.06-1 Severity: minor using yt-dlp to fetch a local copy of a youtube URL like so: $ yt-dlp https://youtu.be/XXX i see this warning: - [youtube] XXX: Downloading player 11e3a4ec WARNING: [youtube] XXX: nsig extraction failed: You may experience throttling for some formats Install PhantomJS to workaround the issue. Please download it from https://phantomjs.org/download.html - This is just noting that it works, but some formats may get throttled with the hardcoded python js scraper and that use of an actual parser (which yt-dlp supports) could make matters a little better there. If PhantomJS is DFSG-free (i haven't checked), then it should be put in debian, and yt-dlp should Recommend: it at least. Then this warning should be patched to say "apt install phantomjs" instead. It is, or I presume so since it was in Debian. It was removed in #962061 with the deprecation of python2. Since it seems rather inactive upstream (no commits since 2020) and the python2 issue still stands[0], I wouldn't imagine someone would want to re-introduce it. But there's nothing preventing anyone from doing so either. [0]: https://github.com/ariya/phantomjs/issues/15414 If it is not DFSG-free, it seems inappropriate for a debian package to directly encourage the user to download non-free software in the course of basic operations. Well it could still be useful as a hint for those that run into throttling, or the inability to fetch the video, that yt-dlp works with that too. However since I most often use yt-dlp with sites other than YouTube, or use mpv's support for yt-dlp, I don't see the message as much and don't find it as much of a nuisance as others might. Thanks for maintaining yt-dlp in debian! It is a very useful tool for those of us who don't want to be connected to the Internet at all times. Glad you find a use for it. ~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#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#1018985: RM: xfce4-statusnotifier-plugin -- ROM; Obsolete upstream, functionality merged into systray plugin
Package: ftp.debian.org Severity: normal Howdy, xfce4-statusnotifier-plugin was made obsolete and merged into the systray plugin of xfce4-panel[0], thus this plugin has no use anymore. [0]: https://docs.xfce.org/panel-plugins/xfce4-statusnotifier-plugin/start ~Unit 193 Unit193 @ OFTC Unit193 @ Libera
Bug#1016003: yt-dlp: little script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, This concept sounds like a great idea to share in #994151 as they try to decide what to do with the youtube-dl package. Given some[0] responses[1] on youtube-dl's bug tracker, I don't imagine picking up new versions will be an option any time soon. Regards, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC [0]: https://github.com/ytdl-org/youtube-dl/issues/31190 [1]: https://github.com/ytdl-org/youtube-dl/issues/28859#issuecomment-1158188788 On Mon, 01 Aug 2022 20:10:42 +0200 michel wrote: I fleshed out the proposal a bit more. The simplest possibillity is to make symlinks, of both the executable and module, to pretend they are youtube-dl and the module youyube_dl. This way, also python programs that load the module could work. A little bit better is this little wraper. you link the exec and module to it. -- #!/usr/bin/python3 import sys from yt_dlp import * if __name__ == "__main__": args=sys.argv.copy() args.pop(0) args=['--compat-options','youtube-dl']+args main(args) The compat options should improve the compatibility. Also, by using the cli options, it would risk less of breaking over time and keeping a fix stupid proof. Maybe a final improvement, would be to initialise the appropriate variable for the compatibility options, so that they are active in the module also. This would have a higher risk of breaking. I tested this with pafy(has an unrelated bug) and mpv on stable. This should stay relevent, for a whille. -BEGIN PGP SIGNATURE- iQJIBAEBCQAyFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmMNRzkUHHVuaXQxOTNA dW5pdDE5My5uZXQACgkQUAHhsJqjdEsf/g//aAwJxAOk0ag1UATT2Qui85kUA2x0 BA+WQ6F4EijSjkmze1qhakR8Qlxc2BDJf5T7r/RMnagcqzRqrM+2j2smoNbTcxHd fJfV9I2yPYgtAW+ieydqacWOSFHg+P1atG+MAgHJdV7klWAeyCFDnX4Bh2GvQeZF PsXHPFHyK6WdsGXUiZyUz9workcW4w/wFVljp2mQi63aLDj835E9AZDMJgtJdfZV x71H5hRoAGxvmjgp69C7D9bhVzJeFVw1I8KDII1Uga84hW5gPVrv8+tWElDVankm fgOoc6pJ/nWDOaUulk/+DFztZ2CF+HoTn0i9yZt3Sz7XDJPV+ldY9O7Hz2iK77FL 5g+XzEJcK1cLsFDjjcLbLbf0HHU4inwl+ZzYkLuWR04TnzVMXSivFkDZF/JO+LtC b3ASX37jKT8sV311hUxGzociyYFBVhrfj5N1hj2pUY5AUU2GkW/dOo5SVW4tyyKr gPlJ9HgjwknPlKtTfJXgJvqqUuzdCvzdbsbDcrB77kLQfZI3Meb6XCQeT6yedavM p4JRSdpM/3Q5GeyjNBQPM1B9QByNu2vyUwN3wsZmFjHSmUGDTtHf2IexGRxHhGzI 5tL1jDP2IEkv3sTDOCRJPWkXDYehPzwM6uzvuRY5wA80mJAS8cWI/NwzPSK7iZVn rxInIT6l005IxwQ= =pMQh -END PGP SIGNATURE-
Bug#1017767: RM: wireguard-linux-compat -- ROM; As noted in #991768, useless in bullseye, in mainline kernel since linux 5.6
Package: ftp.debian.org Severity: normal Howdy, Arguably, wireguard-dkms could be useful if one is using a kernel which does not enable wireguard, but that's not the case for Debian (and deriv) kernels. It could also be useful with -backports-sloppy, but as that's not happened I'm requesting removal. Thanks, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1016714: arch-install-scripts: Include pacstrap in arch-install-scripts since pacman is now in Debian
Howdy, On Fri, 5 Aug 2022, Ben Westover wrote: Dear Maintainer, pacstrap is currently not included in the arch-install-scripts package for Debian, which makes sense since it uses pacman. However, pacman as of today is in Debian as the package pacman-package-manager, so now it should be possible for pacstrap to be added. Version 26 of arch-install-scripts was also released last week, so it's currently a good time to update and include pacstrap at the same time. Yep, that's the plan. I was waiting on pacman-package-manager to pass NEW before I did the changes, so I haven't picked up the new version yet. I plan to only have pacman-package-manager in suggests though as that's not what I use arch-install-scripts for myself, and I presume others likewise. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1001776: yt-dlp: error message
Howdy, On Mon, 1 Aug 2022, michel wrote: Package: yt-dlp Version: 2022.07.18-1~bpo11+1 Followup-For: Bug #1001776 X-Debbugs-Cc: okgomdjgbm...@gmail.com Dear Maintainer, I don't know if you care about this, but an error message asks to do a "yt-dlp -U" please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U I wouldn't say that I wouldn't care, but yes my goal is to greatly limit patches added to yt-dlp. That being said, I don't think it's even needed here at all. When you run `yt-dlp -U` it checks online if you're running the current version and will print out the latest version online and your local version. If you install via pip/package manager, it detects this and tells you to upgrade using those methods: Latest version: 2022.07.18, Current version: 2022.07.17 ERROR: It looks like you installed yt-dlp with a package manager, pip or setup.py; Use that to update As such, the initial error message basically just tells you to check your local version and that it matches the current release, which seems ideal to me. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1001776: yt-dlp: further improve 0002-Disable-upstream-s-autoupdate-mechanism.patch
Howdy, On closer review, this patch isn't actually needed at all since 2012[0][1], so I'm not really sure why it's there in the first place. The output now without the patch (and not updating to the latest) is: Latest version: 2022.05.18, Current version: 2022.04.08 ERROR: It looks like you installed yt-dlp with a package manager, pip or setup.py; Use that to update Which seems more useful than the current text anyway, as it tells you the latest version. One could argue that it "phones home", but with -U you already to do just that anyway. I may just drop the patch instead. [0]: https://github.com/ytdl-org/youtube-dl/commit/cb6ff87fbb05e421f77b57a79699c647866ceb09#diff-fce3fb374a1c20a703ac379c9a2f3c39ee0fe8d155d8c05a07b6b41450215869 [1]: https://github.com/ytdl-org/youtube-dl/commit/f9bd64c09897ebbd3a3278fe21e7ae798c6fc140 ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1001776: yt-dlp: further improve 0002-Disable-upstream-s-autoupdate-mechanism.patch
Howdy, Might be useful to note that this was never sent to me, the BTS doesn't actually send replies by default. On Fri, 31 Dec 2021 20:18:14 +0100, Christoph Anton Mitterer wrote: Hey Uni 193. First, thanks for maintaining this. Are you going to do that in https://salsa.debian.org/debian/yt-dlp ? No. As the Vcs-* show, I don't have this on salsa.debian.org. I'd have written an update to 0002-Disable-upstream-s-autoupdate- mechanism.patch, which completely removes the run_update and update_self functions... (better not have it in the code at all, so it cannot be "accidentally" called by some other place in the code). Bit hard to review a patch I can't see, but functionally how will this change things? So far it sounds like it just enlarges it (thus increasing the likelihood of conflicts) without much of a benefit. If you wanted to adapt the patch, dropping the current __init__.py changes and then only modify run_update to exit with the message (or one like it) that's in parser.error now, that would seem to be about equal to the current changes but fulfill your desire to neuter run_update completely. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#992344: wireguard-tools ought not depend on linux-image-rt-amd64
Howdy, wireguard-tools does not actually depend on linux-image-rt-amd64, but it recommends 'wireguard-modules | wireguard-dkms' since all but the most unusual cases you'll want to be able to actually run WireGuard. The former tries to pull in a kernel that supports WireGuard. In your setup, rather than running `apt install -y wireguard-tools` you should instead try running `apt install --no-install-recommends -y wireguard-tools` and this problem should go away, since wireguard-modules is only recommended and not a hard depend. Does this solve your problem? Thanks! ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#993985: wireguard should not depend on wireguard-dkms now that wireguard is in mainline
Howdy, The 'wireguard' package is a metapackage that depends on wireguard-tools and 'wireguard-modules | wireguard-dkms', and the current Debian kernels provide the former. This means that if you install the metapackage and have a current kernel, then only the wireguard-tools package is installed. If you for some reason don't have a Debian kernel installed, or on a much older release, then -dkms is pulled in. This seems to be working as expected, and isn't pulling in -dkms on current systems. Is there a bug in this somewhere? Thanks, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#894889: mini-dinstall: please allow creating MD5 checksums for packages
Howdy, I presume now that stable has aptly 1.0, which finally supports more than just MD5, this is a moot point? There's been a push to deprecate md5sum, and even sha1 in some places, so I think at this point turning md5sum back on doesn't really make sense. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1004324: yt-dlp gives wrong version info.
On Mon, 24 Jan 2022, shirish शिरीष wrote: Package: yt-dlp Version: 2022.01.21-1 Severity: normal Dear Maintainer, I updated today and got the new version - $ apt-cache policy yt-dlp yt-dlp: Installed: 2022.01.21-1 Candidate: 2022.01.21-1 Version table: *** 2022.01.21-1 900 900 http://deb.debian.org/debian testing/main amd64 Packages 100 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status But when I asked it it's version number, that is what it replied - $ yt-dlp --version 2021.12.27 There seems to be confusion in yt-dlp as to what version it is. Please fix. Do you also have this installed by some other method, such as pip, that would be giving you an old version? If you remove the Debian package, can you still call yt-dlp? unit193@Loki:~$ yt-dlp --version 2022.01.21 unit193@Loki:~$ which yt-dlp /usr/bin/yt-dlp unit193@Loki:~$ cat /usr/lib/python3/dist-packages/yt_dlp/version.py # Autogenerated by devscripts/update-version.py __version__ = '2022.01.21' RELEASE_GIT_HEAD = 'f20d607b0' unit193@Loki:~$ apt-cache policy yt-dlp yt-dlp: Installed: 2022.01.21-1 Candidate: 2022.01.21-1 Version table: *** 2022.01.21-1 500 500 http://deb.debian.org/debian testing/main amd64 Packages 100 http://deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1003555: : php-geoip -- ROM; PHP 8 not supported
Howdy, Perhaps not in any released version, but there's a commit[0] upstream that makes it work with php8(.1). I have this in a local package and it continues to work well. While libgeoip is the deprecated library, it still is in use in quite a few places, and one can find databases online[1] for it. Regardless, I still use php-geoip with 8.1. [0]: https://svn.php.net/viewvc?view=revision=351082 [1]: https://mailfud.org/geoip-legacy/ ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1003471: yt-dlp: Convenience package with symlink pointing youtube-dl to yt-dlp
Howdy, While I understand the thought process, I wouldn't be too inclined to do so as doing so would imply some form of guarantee that it's binary compatible with all options an application or user may use. Also, to use the provides, it'd also have to work when something did 'import youtube_dl' which further complicates things. You mention mpv, in unstable that supports yt-dlp and I poked the team member taking care of it, so it's already in the alternate recommends at least. As for SMPlayer, looks like the latest version[0] supports yt-dlp so that should help there as well. Thanks! [0] https://www.smplayer.info/en/changes ~Unit 193 Unit193 @ Libera Unit193 @ OFTC On Mon, 10 Jan 2022, /dev/fra wrote: Package: yt-dlp Version: 2021.12.27-1 Severity: wishlist Dear Maintainer, Some applications using youtube-dl do not support yet yt-dlp. That is the case, for example, of SMPlayer in Debian Testing/Sid and Stable, and of mpv in Debian Stable. A convenience package similar to, say, python-is-python3, providing a symlink to point /usr/bin/youtube-dl to /usr/bin/yt-dlp, might come in handy. Is it something you might consider preparing? Cheers
Bug#1003491: winetricks: Please allow co-installation with wine-staging
Package: winetricks Severity: wishlist Dear Maintainer, While it's a third-party repo and they should perhaps declare a provides on 'wine', even though it's installed in /opt, it would be very useful to have winetricks installed with wine-staging from winehq's repo. Thanks! ~Unit 193 Unit193 @ Libera Unit193 @ OFTC -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1002488: barrier not longer start after programstart
Howdy, On Thu, 23 Dec 2021, Jörg Frings-Fürst wrote: Hello, since the last update barrier does not start after programstart. Does going to the main interface and clicking Barrier →Change settings → " Start Barrier on Startup" Help? On the local machine this is just a nuisance, but on the remote machines without their own keyboard and/or mouse it is a significant error. For further questions I am available. ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
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#1001933: RFP: yt-dlp -- youtube-dl fork with additional features and fixes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Hello, On Tue, 21 Dec 2021, Andreas Tille wrote: Hi, Am Mon, Dec 20, 2021 at 11:38:46PM -0500 schrieb Unit 193: External to Debian, I've been maintaining this since August of this year, so if it ends up not working out to get this team maintained, I'd be up to maintain it myself. Is this a kind of "I'd like to turn this into an ITP"? Would you mind using some non-annonymous ID if this is the case and do you want access to the Salsa repository (if so what is your Salsa login)? More that if your current plan falls though, I can just upload what I have. I'm a DD, in Debian I'm known as Unit 193 with the account unit193, you should be able to find me on db.debian.org. Since I am a DD and yt-dlp is in debian/, I should already have access if needed. Thanks, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJhwYeWAAoJEFAB4bCao3RL4rYP/09HRWpJbO9qZSpHvn4X/5JL +EN+jZF/Ybs5nfcqvoeXTt0gkS6Hx4pns0XRCk89RBEzuhCWfFdxd11VwV3BeVfD 4oUTUTE9slefLcNDkqhyGJLzh+/rDnw29hJHSSZu/am2BM3vjjpzmQaQAOCbBnlw ITpWxnXfXeE/X5KGrhjmZwflCwXaxg2oKjRSFO4OlS7yLbIA7Fco0LaxEPmtUH6e nV1Ip4dpyGmtUuwOWuepzP+F19paAGFQ9xvTRrOBSZqtppZydpZ2QBNh0aJbAotJ pqMWWfrPq9kCBYROIretiO6zAllWVnpYC4rttr6vYFbxLnCUVuM3URR0o9kBfhEk b7k5NMafCebhjMy2CxoLmRQb25GThlq+n5wxdSHQNhdn0D5s26ocdE+pD3QL6FFK 7JHPATAKe8PkwjvCvZzQTy6Uynd1KVzt5x5boo6kUCq3LsfM5lIpLxGVf/7TFjUw IRaNeiwmc2XP3RXGZ6vGqfIRPsufAOEHUMQjE2o6CFGn9vhQCjUC3jgIsfOijjMl vI8GCkC47N4n/A1t82LVDoNmRlCOZ5w0tq2c+P0nQtJ9XgfCVH7cSYerM81H6UAn N4W/ug4DSlFuH230XoBWJBrV8r1mZnjCUw+w4h+bHOu8vlPW1xeA1IVD2Yy0xrOe GlnNafOw8w23iP9v0sBO =B/pH -END PGP SIGNATURE-
Bug#1001933: RFP: yt-dlp -- youtube-dl fork with additional features and fixes
Howdy, External to Debian, I've been maintaining this since August of this year, so if it ends up not working out to get this team maintained, I'd be up to maintain it myself. Cheers! ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#990434: tinyproxy segfaults on onion address with socks4
Source: tinyproxy Severity: important Dear Maintainer, When setting a socks4 proxy as upstream to use with Tor, once you visit an onion address tinyproxy will crash. I helped upstream debug this, and it was fixed in the following two commits: https://github.com/tinyproxy/tinyproxy/commit/7ea9f80d3f31c85a4729854b47977e282632e6ed https://github.com/tinyproxy/tinyproxy/commit/563978a3ea4e8b51fcf547298dfdafc516e04526 An example debdiff: diff --git a/debian/changelog b/debian/changelog index 97d959e..d219c28 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +tinyproxy (1.10.0-5) unstable; urgency=medium + + * d/p/0001_fix-segfault-with-socks4.patch: +- Grab an upstream patch to fix a segfault when using socks4 with tor. + + -- Unit 193 Fri, 25 Jun 2021 00:59:55 -0400 + tinyproxy (1.10.0-4) unstable; urgency=medium * debian/tinyproxy.init: diff --git a/debian/patches/0001_fix-segfault-with-socks4.patch b/debian/patches/0001_fix-segfault-with-socks4.patch new file mode 100644 index 000..e69a8ca --- /dev/null +++ b/debian/patches/0001_fix-segfault-with-socks4.patch @@ -0,0 +1,51 @@ +From 7ea9f80d3f31c85a4729854b47977e282632e6ed Mon Sep 17 00:00:00 2001 +From: rofl0r +Date: Fri, 25 Jun 2021 02:43:00 +0100 +Subject: [PATCH] fix segfault in socks4 upstream with unresolvable hostname + +using a socks4 tor upstream with an .onion url resulted in +gethostbyname() returning NULL and a subsequent segfault. +not only did the code not check the return value of gethostbyname(), +that resolver API itself isn't threadsafe. + +as pure SOCKS4 supports only IPv4 addresses, and the main SOCKS4 +user to this date is tor, we just use SOCKS4a unconditionally and +pass the hostname to the proxy without trying to do any local name +resolving. + +i suspect in 2021 almost all SOCKS4 proxy servers in existence use +SOCKS4a extension, but should i be wrong on this, i prefer issue +reports to show up and implement plain SOCKS4 fallback only when +i see it is actually used in practice. +--- + src/reqs.c | 12 +++- + 1 file changed, 7 insertions(+), 5 deletions(-) + +--- a/src/reqs.c 2021-06-25 01:00:13.026080096 -0400 b/src/reqs.c 2021-06-25 01:00:13.026080096 -0400 +@@ -1287,7 +1287,6 @@ + unsigned short port; + size_t ulen, passlen; + +- struct hostent *host; + struct upstream *cur_upstream = connptr->upstream_proxy; + + ulen = cur_upstream->ua.user ? strlen(cur_upstream->ua.user) : 0; +@@ -1304,10 +1303,13 @@ + buff[1] = 1; /* connect command */ + port = htons(request->port); + memcpy([2], , 2); /* dest port */ +- host = gethostbyname(request->host); +- memcpy([4], host->h_addr_list[0], 4); /* dest ip */ +- buff[8] = 0; /* user */ +- if (9 != safe_write(connptr->server_fd, buff, 9)) ++ memcpy([4], "\0\0\0\1" /* socks4a fake ip */ ++ "\0" /* user */, 5); ++ len = strlen(request->host); ++ if(len>255) ++ return -1; ++ memcpy([9], request->host, len+1); ++ if (9+len+1 != safe_write(connptr->server_fd, buff, 9+len+1)) + return -1; + if (8 != safe_read(connptr->server_fd, buff, 8)) + return -1; diff --git a/debian/patches/series b/debian/patches/series index 2093e6b..dd8047b 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1,3 +1,4 @@ 1001_fix-select.patch 1002_fix-ftbfs-on-Hurd.patch 1003_fix-rereading-filter-conf-when-unprivileged.patch +0001_fix-segfault-with-socks4.patch -- System Information: Debian Release: 11.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-5-amd64 (SMP w/2 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#844455: Use local packages for source build
Howdy,
I ran into this issue a couple years ago, I made a quick and dirty edit (thanks
to this being in Python!) that solved the issue for me and I've carried ever
since. It may not be the proper upstream fix, but if someone else runs into
this then it may be useful.
autopkgtest_args.py |3 ---
1 file changed, 3 deletions(-)
--- /usr/share/autopkgtest/lib/autopkgtest_args.py 2018-04-22
09:55:27.0 -0400
+++ /usr/share/autopkgtest/lib/autopkgtest_args.py 2019-05-04
07:42:01.432510378 -0400
@@ -133,9 +133,6 @@
if not debsrc_action and not has_clicksrc and not has_click:
parser.error('You must specify source or click package to test')
-if has_debs or has_click:
-args.built_binaries = False
-
if debsrc_action:
# some actions above disable built binaries, for the rest use the CLI
option
if debsrc_action[2] is None:
~Unit 193
Unit193 @ freenode
Unit193 @ OFTC
Bug#982061: package-update-indicator throws GLib-ERROR and does not run
Howdy, I just tried the glib2.0 2.66.7-1 which was just uploaded and it fixed the problem for me. Can you give it a try and see if you can confirm this? Thanks! ~Unit 193 Unit193 @ freenode Unit193 @ OFTC On Sun, 7 Feb 2021, Gökalp Çelik wrote: I tested with 2.66.4 package from bullseye and package-update-indicator came back however those older packages also suffer from a vulnerability that later sid packages don't. So it seems that there is a problem with package-update-indicator implementation as well. On Sun, Feb 7, 2021 at 1:15 AM Unit 193 wrote: Howdy, The exact error message seen is: GLib-ERROR **: 17:08:39.264: ../../../glib/gmem.c:112: failed to allocate 93955162462643 bytes This actually started happening with an update of glib2.0 to 2.66.6-1, though 2.67.3-1 is also affected. To work around such problem, I have downgraded the library to 2.66.5-1 which solved the issue for now. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC -- Gökalp Çelik Biyoinformatik Hizmetleri Intergen Genetik Hastalıklar Tanı Merkezi [uc?id=13PckZnCcbyy6hUEAlkK1HhWiF33n9za0=download] Tel: +90 (312) 428 48 14 / +90 (312) 428 36 90 Fax: +90 (312) 428 26 93 Web: www.intergen.com.tr - @Mail: gokalpce...@intergen.com.tr
Bug#982061: package-update-indicator throws GLib-ERROR and does not run
Howdy, The exact error message seen is: GLib-ERROR **: 17:08:39.264: ../../../glib/gmem.c:112: failed to allocate 93955162462643 bytes This actually started happening with an update of glib2.0 to 2.66.6-1, though 2.67.3-1 is also affected. To work around such problem, I have downgraded the library to 2.66.5-1 which solved the issue for now. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#978439: closed by Debian FTP Masters (reply to Unit 193 ) (Bug#978439: fixed in arch-install-scripts 23-3)
On Thu, 7 Jan 2021, Holger Levsen wrote: On Thu, Jan 07, 2021 at 02:36:03AM +, Debian Bug Tracking System wrote: Changes: arch-install-scripts (23-3) unstable; urgency=medium . * d/install, d/p/policy.d_no_autostart.patch, d/policy-rc.d: - Drop setting up policy-rc.d. * d/control: Update description, thanks MTecknology. (Closes: #978439) In any case thanks for fixing this! I while I'm not sure what MTecknology did here, I just thought I'd mention it, even though it's definitly not important, but I filed #978439... :) Yes, it's rather clear who files bug reports. MTTech quite nicely provided a changed description for me to use. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#948214: barriers sometimes runs with high load and use all memory
Howdy, One pull request upstream that's likely worth a shot was merged[0] back in Feb and is referenced from several issues relating to memory and CPU usage. If you do check to see if that matches your issue, and solves it, I'd like to hear the results. [0]: https://github.com/debauchee/barrier/pull/557 ~Unit 193 Unit193 @ freenode Unit193 @ OFTC On Mon, 20 Jan 2020, Jörg Frings-Fürst wrote: tag 948214 - moreinfo thanks Hello, Am Samstag, den 18.01.2020, 00:51 -0500 schrieb Unit 193: 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. It is not obvious to me which trigger is used to trigger the error. Sometimes the error occurs after 15 minutes, sometimes only after more than 20 hours. The conf-file and xsession-errors ist attached.
Bug#959481: alpine: does not connect with TLS to smtp/imap server
Howdy, I noticed that your initial report claims that you're running buster, but the version you are comparing the buster backport to is from oldstable. This means that rather than linking against the same version of openssl, the older version of alpine you're running is linked against openssl1.0 which is no longer in Debian. If you really are on buster, can you also try alpine 2.21 from the buster repos? One larger change with buster was that openssl changed the default minimum TLS version from TLSv1 to TLSv1.2. For full information see /usr/share/doc/libssl1.1/NEWS.Debian.gz ~Unit 193 Unit193 @ freenode Unit193 @ OFTC On Mon, 11 May 2020, Eduardo Chappa wrote: On Mon, 11 May 2020, Βασίλειος A. Ζοῦκος wrote: Thanks for the informative responses. More information on the subject: 1. The variable Encryption Protocol Range appears only in alpine ver. 2.22 with the assignment: Encryption Protocol Range = Yes, and since you have not modified it, nor Debian did, that means that your version of Alpine supports all the encryption protocols supported by the underlying version of openssl. Now it is the job of the Debian maintainer to investigate which protocols were used to compile each of the versions of Openssl that were used to link against each version of Alpine. Let us wait for that report, and we can figure out what the next action will be. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#959481: alpine: does not connect with TLS to smtp/imap server
Howdy, On Sun, 3 May 2020, Βασίλειος A. Ζοῦκος wrote: To be more precise: On the same machine with the same debian distribution, I retain two executable versions for alpine: 1. alpine ver. 2.20 2. alpine ver. 2.22 Using the same alpine configuration (for ver 2.20, 2.22): 1. I am able to connect via TLS to imap/smtp servers and perform all the e-mail tasks using alpine ver. 2.20 2. I can't connect via TLS to the same imap/smtp servers using alpine 2.22. Attached are parts of the pine-debug files produced by the command: alpine_2_XX -d 9 (XX=20,22) Many thanks, Thank you for including logs! The important line from the latter is as follows: sslfailure: host=imap.otenet.gr reason=SSL negotiation failed Unfortunately that's not a lot of detail, so it's useful to use testssl or `openssl s_client` to check what's going on here. From that, I got routines:ssl_choose_client_version:unsupported protocol:../ssl/statem/statem_lib.c:1929: as well as testssl noting a few things that weren't favorable, such as a SHA1 cert, offering SSLv3 and TLSv1, etc. Alpine had a bunch of changes with regards to TLS in the last release, namely for me it added SNI support, and I wonder if it's now more strict. This sounds like something one might want to contact upstream about, I don't think I've noticed anything on the list regarding an issue like this, though I could have missed it. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#959481: alpine: does not connect with TLS to smtp/imap server
severity -1 normal tags -1 + unreproducible stop Howdy, When filing bugs, please at the very least take the time to fill out the the template additionally providing any details that may be used to assist with your problem. I have been using this version of alpine for some time now (indeed, it fixes SNI issues) and have no problems connecting to TLS sources. Perhaps take a minute to review your configuration and see if there's any oddities preventing you from connecting, and if at all possible provide any details that might further shed light on the problem. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#952662: debdiff for passwdqc as uploaded to DELAYED/7
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, I have now uploaded this to DELAYED/7, as specified in the Debian policy[0]. debdiff attached. [0]: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#how-to-salvage-a-package ~Unit 193 Unit193 @ OFTC Unit193 @ freenode -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJegSJCAAoJEFAB4bCao3RLsn0QAO2Q04I9Iyt+QWQ8UOfNXjJs KDFxJyGzOqe5Hlw89evswxG2qUZ/ezM93KNaAlKzwEbYJLd8Pvqewl+PwxnEiFMs ErQAUq7Jt6RA8i2ML5tWN6umGdTqDbEODI6VFh+Ec7YEO+hznxvHMFjYYvPXxqEE eIBgBoc0Si1nZl/a8HSP4rqItmtm1PC2ON7Ysl7R/3O+JHL2D0o+b1vq9j+y+ab1 ON+2GNCqkZfy7fCyqchsIuhv4Zu+mPNllJOTsm6XGohQWRDrvzuS9EWIHPvdMVAO 84icTpZcTGnVZrIna8d3w+mQQMLq5bLLf2Yf1cLTq9BfwJ0tjGkjVnuw0nnsSm5P GNb8IFs8+79Eb2Xp5elSDy01qXSpnXKPrDMlH2KvsLIPc+Op5ukzYYlGBLhvTvSN K6aYDPNinpqq2o9tfzfvHyTKGEtsDuRmHacLZ9uMZ8QjLEj+sM+O7tjkjtay3DwW iOYLV6kQIGKrvoJPQZduCzzprN2YFkYwz5C/ZJDuY19NLE2wD4NA2WcLoAnSXy3A qhQqCFycNqkCVkonojrjUuahC9OURxoClfJ0lN1IwB4bim4R7vhLrfpRwkRxBzf4 SVHXYIBKc0cwneCFChZh60NtKJ4RUNdcO9AdqL9T/IQdnMcgWdPGClRNzXeEpci2 lz4o4YIMXAZATlLlxBvF =kESX -END PGP SIGNATURE-diff -Nru passwdqc-1.3.0/concat.c passwdqc-1.4.0/concat.c --- passwdqc-1.3.0/concat.c 2009-09-28 19:00:19.0 -0400 +++ passwdqc-1.4.0/concat.c 2019-12-09 18:00:54.0 -0500 @@ -9,11 +9,6 @@ * * Written by Solar Designer and placed in the * public domain. - * - * Originally written for and currently maintained as a part of popa3d, - * a POP3 server: - * - * http://www.openwall.com/popa3d/ */ #include @@ -27,7 +22,7 @@ va_list args; const char *s; char *p, *result; - unsigned long l, m, n; + size_t l, m, n; m = n = strlen(s1); va_start(args, s1); diff -Nru passwdqc-1.3.0/debian/changelog passwdqc-1.4.0/debian/changelog --- passwdqc-1.3.0/debian/changelog 2013-08-29 06:08:00.0 -0400 +++ passwdqc-1.4.0/debian/changelog 2020-03-29 18:19:10.0 -0400 @@ -1,8 +1,47 @@ +passwdqc (1.4.0-1) unstable; urgency=medium + + * Salvage package into Security Tools team. (Closes: #952662) + * Remove trailing whitespace. + * New upstream version 1.4.0. +- Drop patches applied upstream. +- With "non-unix", initialize the pw_dir field in fake_pw now that (since + passwdqc 1.1.3 in 2009) passwdqc_check.c uses that field. + Closes: #831356 +- Clarified in the man pages that /etc/passwdqc.conf is not read unless + this suggested file location is specified with the config= option. + Closes: #774990 + * d/compat, d/control: +- Drop d/compat in favor of debhelper-compat, bump to 12. + * d/control: +- Mark libpasswdqc-dev Architecture: any. +- Mark library packages Multi-Arch: same +- Add Samuel Henrique and myself to uploaders. +- Tighten libpasswdqc-dev's dependency on libpasswdqc0. +- Add Vcs-* fields. +- R³: no. + * d/control, d/copyright, d/watch: Use https where possible. + * d/copyright: Correct a couple license names. + * d/lib*.install: Update for multiarch locations. + * d/libpam-passwdqc.dirs, d/README.source: Drop. + * d/rules: +- Remove DH_OPTIONS export. +- Trim DEB_LDFLAGS_MAINT_APPEND to '-Wl,--as-needed' +- Include /usr/share/dpkg/default.mk +- Pack CFLAGS, CPPFLAGS and LDFLAGS into dh_auto_build. (Closes: #724278) +- Pack install directories into dh_auto_install. + * Include password-strength.txt in debian/ rather than patching it in. + * Update Standards-Version to 4.5.0. + + [ Samuel Henrique ] + * Add gbp.conf + + -- Unit 193 Sun, 29 Mar 2020 18:19:10 -0400 + passwdqc (1.3.0-1) unstable; urgency=low * Set myself as maintainer. closes: #719106 * Update debian/watch. - * New upstream release. + * New upstream release. * Update to standards version 3.9.4. closes: #676290 * Generate symbols @@ -71,5 +110,5 @@ pam-passwdqc (0.7-1) unstable; urgency=low * Initial packaging for Debian (closes: #138631) - + -- Tollef Fog Heen Tue, 24 Sep 2002 17:15:33 +0200 diff -Nru passwdqc-1.3.0/debian/compat passwdqc-1.4.0/debian/compat --- passwdqc-1.3.0/debian/compat2013-08-09 21:17:16.0 -0400 +++ passwdqc-1.4.0/debian/compat1969-12-31 19:00:00.0 -0500 @@ -1 +0,0 @@ -9 diff -Nru passwdqc-1.3.0/debian/control passwdqc-1.4.0/debian/control --- passwdqc-1.3.0/debian/control 2013-08-09 22:45:39.0 -0400 +++ passwdqc-1.4.0/debian/control 2020-03-24 03:14:14.0 -0400 @@ -1,10 +1,15 @@ Source: passwdqc Section: admin Priority: optional -Maintainer: Jackson Doak -Build-Depends: debhelper (>= 9), libpam-dev -Standards-Version: 3.9.4 -Homepage: http://www.openwall.com/passwdqc/ +Maintainer: Debian Security Tools +Uploaders: Samuel Henrique , + Unit 193 +Build-Depends: debhelper-compat (= 12), libpam-dev +Rules-Requires-Root: no +Standards-Version: 4.5.0 +Homepage: https://www.openwall.com/passwdqc/ +Vcs-Browser: https://salsa.debian.org
Bug#954745: cgit: Please package the new upstream version
Source: cgit Severity: wishlist Dear Maintainer, Please update cgit to 1.2.3. 1.2.2 brings the ability to configure blame per repo, and 1.2.3 brings zstd support. You might want to add a suggest on lua-luaossl too, fwiw. Release announcements below: == 1.2.2 == In terms of features, this release adds support for per-repository overrides of the enable-blame command, since git-blame can be expensive on huge repos. We also fix numerous bugs, update our lua dependencies, and bump to git version 2.25. == 1.2.3 == This patch updates us to git 2.25.1, augments our tests, adds support for lzip and zstd, and fixes a crash in when following logs.
Bug#952662: ITS: passwdqc
Source: passwdqc Severity: important Dear Maintainer, I am hereby offering to co-maintain/salvage the package passwdqc, applying the following criteria: * Package maintainance seems to have been incative for more than a year. * There are several new releases available. - Most if not all open bugs could be closed with the new versions. * Direct emails to the maintainer have gone unanswered for many months. I intend to maintain it under the pkg-security team. My latest work is available in my git repo[0]. [0]: https://git.unit193.net/cgit/users/unit193/passwdqc.git/ ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#949787: ITP: python-certbot-dns-gandi -- Gandi LiveDNS plugin for Certbot
Package: wnpp Severity: wishlist Owner: Unit 193 * Package name: python-certbot-dns-gandi Version : 1.2.5 Upstream Author : Yohann Leon * URL : https://github.com/obynio/certbot-plugin-gandi/ * License : Expat Programming Lang: Python Description : Gandi LiveDNS plugin for Certbot The objective of Certbot, Let's Encrypt, and the ACME (Automated Certificate Management Environment) protocol is to make it possible to set up an HTTPS server and have it automatically obtain a browser-trusted certificate, without any human intervention. This is accomplished by running a certificate management agent on the web server. . This is a plugin for Certbot that uses the Gandi LiveDNS API to allow Gandi customers to prove control of a domain name.
Bug#936058: Missing binary package for armhf
Howdy, At the time of buster's release, it seems that the version failed to build on armhf. There's not really anything one can do at this point except backport the latest version to Buster. I don't use this in buster, just unstable, but if you desire I could backport this to buster. ~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#947941: alpine: New Upstream
Howdy, It seems upstream has moved again, now to https://repo.or.cz/alpine.git That's not a new home, that's just where the git repository lives. The current home is still http://alpine.x10host.com/alpine/ There is active development there from Eduadro, including two tagged releases since what's in Debian currently (though from the numbering and the contents of the pine.hlp file in the repo, these may be intended as rc/pre-releases). Yes, as you can see on the release[1] page[2], Debian has the current released version and the only available releases are development builds. It looks like from the mailing list there will be a release later this month though[3]. [1]: http://alpine.x10host.com/alpine/release/ [2]: http://alpine.x10host.com/alpine/alpha/release/ [3]: http://mailman13.u.washington.edu/pipermail/alpine-info/2020-January/008717.html From a cursory examination of the log, I see several commits that look like they would fix open bugs in Debian. There seems to be a few bugs that will be fixed, SNI support for one. If you have a list of bugs matched to the associated upstream changelog entries, I wouldn't mind having those though. :) ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#941049: lua-luaossl: Newer releases available upstream
Package: lua-luaossl Severity: wishlist Howdy, There appears to be quite a few new versions available from upstream's GitHub releases[0]. It might be a good idea to update the watch file and upload the latest release. [0]: https://github.com/wahern/luaossl/releases ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#940142: RM: libmowgli-2 -- RoQA; Orphaned, no reverse dependencies of this library
Package: ftp.debian.org Severity: normal Howdy, libmowgli is part of atheme-services and was extracted such that it could be used in other applications. It was thus packaged, but since it never ended up used in anything else eventually atheme-services went back to using the built-in version. Now, if one wanted to submit a patch to atheme upstream and if one has libmowgli-2 installed atheme will fail to builid as libmowgli-2 is not maintained in Debian. I therefore request the removal of this package as it provides no use, and if anything gets in the way. ~Unit 193 Unit193 @ OFTC Unit193 @ freenode
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#921222: nautilus-dropbox 2019.02.14-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, So I did some work on this package for my own benefit back in May, the Debianized version of that I just uploaded to mentors[0] if that helps. [0] dget https://mentors.debian.net/debian/pool/non-free/n/nautilus-dropbox/nautilus-dropbox_2019.02.14-1.dsc ~Unit 193 Unit193 @ OFTC Unit193 @ freenode -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJdJYvqAAoJEFAB4bCao3RLMJ0QAKB/wFeqdUQdWSQw3zQhURrr 3NsV2ryGLLrZi10Tkb32UDivl8exeSQhq2A/+iOpTtgkrSEZwEXV7eKkPtdkwLqe vk3oit4lJxxwKegV154XtQ9pSPhMeXq/uCFuotcFg2h6nkRSbXiwAKFAv0NFJALP uvax5ClPALdGp/WVxKAUrTAe5wXJZIPhlzai98dL9wnqE2sWBnoWI8kf/oDRKSqn aVQtBfhj9FSDLxp4HtJw9obOi1qQ8x+31iYhvRwBmCfbjnmbw/QVHCwQ0LnEuwCe K76xL9zui8wS8FWAQBJ6Z9mZY2oUL/K3rg5ctjHaAIbdTd7sk9++7y2Jpl9pDBqg kZPkNgylbzMC9y3dc6EHX08DS0j5pCTNRXOFKvBD20kyGt1SY4hSnI6uCVTEYdvo zHQr964EC+PCwheA14BjhcqfIXBblDFd3uejXHKUDQyDaE2wpxpcqxAwjcyD7EKN vdYliOi0MDDrRqGoVSF9wa8QR1dgzU1PHXYdc8QXf80j94muTnY22nFS8m5hoakw Du1dYdSmGPVowI/0FGT2B1vjgFNlN4ZMq1l0E1YwHN9KxJnPO0Zaryr4Ty7F+LDO jdPNIp2YDgqMqbYEkgB912TzzW+EO9Hvy0lzDl6MXxCmAIQLcEZCAIxl5BtDluWT BaJTG8Ls6K/6Xa7c9LvE =YV5e -END PGP SIGNATURE-
Bug#927912: unblock: gcalcli/4.0.4-2 (pre-approval)
Control: tags -1 moreinfo Howdy, I've uploaded the package and it should be in unstable now. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC On Fri, 26 Apr 2019, Niels Thykier wrote: Control: tags -1 moreinfo confirmed Unit 193: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Howdy, Pending approval, I'm uploading a version of gcalcli which contains an upstream patch to fix the reliance on the Google shortening service. If a user invokes one of the subcommands with '--details url', the application hits traceback issues as the service has been shut down. See https://github.com/insanum/gcalcli/issues/440 for more details of the problem. The changelog reads: gcalcli (4.0.4-2) unstable; urgency=medium * d/p/remove_url_shortening.patch: Remove the deprecated goo.gl service. -- Unit 193 Wed, 24 Apr 2019 19:46:16 -0400 And debdiff: [...] Please go ahead with the upload and remove the moreinfo tag when it is in unstable and ready to be unblocked. Thanks, ~Niels
Bug#927912: unblock: gcalcli/4.0.4-2 (pre-approval)
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Howdy,
Pending approval, I'm uploading a version of gcalcli which contains an upstream
patch to fix the reliance on the Google shortening service.
If a user invokes one of the subcommands with '--details url', the application
hits traceback issues as the service has been shut down.
See https://github.com/insanum/gcalcli/issues/440 for more details of the
problem.
The changelog reads:
gcalcli (4.0.4-2) unstable; urgency=medium
* d/p/remove_url_shortening.patch: Remove the deprecated goo.gl service.
-- Unit 193 Wed, 24 Apr 2019 19:46:16 -0400
And debdiff:
diff --git a/debian/changelog b/debian/changelog
index 868a5db..f6bd57b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+gcalcli (4.0.4-2) unstable; urgency=medium
+
+ * d/p/remove_url_shortening.patch: Remove the deprecated goo.gl service.
+
+ -- Unit 193 Wed, 24 Apr 2019 19:46:16 -0400
+
gcalcli (4.0.4-1) unstable; urgency=medium
* New upstream version 4.0.4
diff --git a/debian/patches/remove_url_shortening.patch
b/debian/patches/remove_url_shortening.patch
new file mode 100644
index 000..74a3c44
--- /dev/null
+++ b/debian/patches/remove_url_shortening.patch
@@ -0,0 +1,225 @@
+From 428378a88f89d154c8d4046deb9bdb5eb4e81019 Mon Sep 17 00:00:00 2001
+From: Joshua Crowgey
+Date: Mon, 15 Apr 2019 21:07:49 -0700
+Subject: [PATCH] Remove URL Shortening [fixes #440] (#443)
+
+Google has removed the urlshortening service. After some discussion,
+it was decided to remove the shortening facilities instead of trying to
+integrate with a separate provider. This makes our code simpler and
+folks who need url shortening can hopefully layer on what they need.
+---
+ ChangeLog|3 +++
+ gcalcli/argparsers.py| 16 +---
+ gcalcli/gcal.py | 39 +--
+ setup.py |2 +-
+ tests/test_argparsers.py |9 ++---
+ 5 files changed, 20 insertions(+), 49 deletions(-)
+
+Index: gcalcli/ChangeLog
+===
+--- gcalcli.orig/ChangeLog
gcalcli/ChangeLog
+@@ -1,3 +1,6 @@
++v4.1.0
++ * Removed url shortening due to Google deprecation #440
++
+ v4.0.4
+ * Minor bugfixes: conky colors, issues with setup.py
+
+Index: gcalcli/gcalcli/argparsers.py
+===
+--- gcalcli.orig/gcalcli/argparsers.py
gcalcli/gcalcli/argparsers.py
+@@ -7,11 +7,9 @@ from gcalcli.printer import valid_color_
+ from oauth2client import tools
+ import copy as _copy
+
+-DETAILS = ['all', 'calendar', 'location', 'length', 'reminders',
'description',
+- 'longurl', 'shorturl', 'url', 'attendees', 'email', 'attachments']
++DETAILS = ['calendar', 'location', 'length', 'reminders', 'description',
++ 'url', 'attendees', 'email', 'attachments']
+
+-BOOL_DETAILS = ['calendar', 'location', 'length', 'reminders', 'description',
+-'attendees', 'email', 'attachments']
+
+ PROGRAM_OPTIONS = {
+ '--client-id': {'default': gcalcli.__API_CLIENT_ID__,
+@@ -60,13 +58,9 @@ class DetailsAction(argparse._AppendActi
+ details = _copy.copy(getattr(namespace, self.dest, {}))
+
+ if value == 'all':
+-details = {d: True for d in BOOL_DETAILS}
+-elif value in BOOL_DETAILS:
++details = {d: True for d in DETAILS}
++else:
+ details[value] = True
+-elif value in ['shorturl', 'url']:
+-details['url'] = 'short'
+-elif value == 'longurl':
+-details['url'] = 'long'
+
+ setattr(namespace, self.dest, details)
+
+@@ -90,7 +84,7 @@ def get_details_parser():
+ details_parser = argparse.ArgumentParser(add_help=False)
+ details_parser.add_argument(
+ '--details', default={}, action=DetailsAction,
+-choices=DETAILS,
++choices=DETAILS + ['all'],
+ help='Which parts to display, can be: ' + ', '.join(DETAILS))
+ return details_parser
+
+Index: gcalcli/gcalcli/gcal.py
+===
+--- gcalcli.orig/gcalcli/gcal.py
gcalcli/gcalcli/gcal.py
+@@ -47,7 +47,6 @@ class GoogleCalendarInterface:
+ max_retries = 5
+ auth_http = None
+ cal_service = None
+-url_service = None
+
+ ACCESS_OWNER = 'owner'
+ ACCESS_WRITER = 'writer'
+@@ -140,8 +139,7 @@ class GoogleCalendarInterface:
+ OAuth2WebServerFlow(
+ client_id=self.options['client_id'],
+ client_secret=self.options['client_secret'],
+-scope=['https://www.googleapis.com/auth/calendar',
+-
'https://www.googleapis.com/auth/urlshortener'],
++scope=['https://www.googleapis.com/auth
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#894174: gcalcli: --nodeclined error
Howdy, Can you take a look and see if you can still reproduce this issue with 4.0.4-1? This looks to me as if it should be fixed, and I did not get any traceback when I tried using the aforementioned option. ~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#913687: RM: ruby-rbnacl -- ROM; no longer needed by ruby-net-ssh; no other rev-deps
Package: ftp.debian.org Severity: normal Howdy, This package was required by ruby-net-ssh for Ed25519 support, that feature is now covered by ruby-ed25519 so this package is no longer useful. This package is not used by anything else in Debian, and has a rapidly declining popcon count since its replacement. I would thank you to remove this package from the archive. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
Bug#910716: ITP: barrier -- Share mouse, keyboard and clipboard over the network
Package: wnpp Severity: wishlist Owner: Unit 193 * Package name: barrier Version : 2.1.2 Upstream Author : Debauchee Open Source Group * URL : https://github.com/debauchee/barrier/ * License : GPL-2 (with OpenSSL exception) Programming Lang: C++ Description : Share mouse, keyboard and clipboard over the network Barrier lets you easily share a single mouse and keyboard between multiple computers with different operating systems, each with its own display, without special hardware. It's intended for users with multiple computers on their desk since each system uses its own display. . Redirecting the mouse and keyboard is as simple as moving the mouse off the edge of your screen. Barrier also merges the clipboards of all the systems into one, allowing cut-and-paste between systems. Furthermore, it synchronizes screen savers so they all start and stop together and, if screen locking is enabled, only one screen requires a password to unlock them all. This is a fork of Synergy, as that has gone closed source.
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#909065: ITP: xfce4-statusnotifier-plugin -- plugin to display status notifiers in the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Unit 193 * Package name: xfce4-statusnotifier-plugin Version : 0.2.1 Upstream Author : Viktor Odintsev * URL : https://goodies.xfce.org/projects/panel-plugins/xfce4-statusnotifier-plugin * License : GPL-2+ Programming Lang: C Description : plugin to display status notifiers in the Xfce4 panel A small plugin to display status notifiers, including application indicators, in the Xfce4 panel as described in freedesktop.org StatusNotifierItem specification. Status notifiers are a modern alternative to the system tray. This provides a nice way in Xfce to display indicators in the panel. There may be other panel plugins that do a similar thing, but this is an official project of Xfce.
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#894481: nmu diff
Howdy, A solution to this problem is in the debdiff attached, it is easily backported as it leaves support for the old location of laptop-detect, but otherwise will use the new location. This is also what has been uploaded to Ubuntu. ~Unit 193 Unit193 @ OFTC Unit193 @ freenodediff -Nru numlockx-1.2/debian/55numlockx numlockx-1.2/debian/55numlockx --- numlockx-1.2/debian/55numlockx 2014-08-11 06:08:41.0 -0400 +++ numlockx-1.2/debian/55numlockx 2018-05-20 11:44:06.0 -0400 @@ -20,7 +20,11 @@ ;; *) NUMLOCK=on -ltd=/usr/sbin/laptop-detect +if [ -x /usr/sbin/laptop-detect ];then +ltd=/usr/sbin/laptop-detect +else +ltd=/usr/bin/laptop-detect +fi [ ! -x $ltd ] || ! $ltd || NUMLOCK=off # Enable numlock for USB keyboard on laptop if [ -f /bin/udevadm ] ; then diff -Nru numlockx-1.2/debian/changelog numlockx-1.2/debian/changelog --- numlockx-1.2/debian/changelog 2014-08-11 06:08:41.0 -0400 +++ numlockx-1.2/debian/changelog 2018-05-20 11:47:27.0 -0400 @@ -1,3 +1,11 @@ +numlockx (1.2-7.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * d/55numlockx: Adjust to find laptop-detect after move to /usr/bin +(Closes: #894481) + + -- Unit 193 <unit...@ubuntu.com> Sun, 20 May 2018 13:44:27 -0400 + numlockx (1.2-7) unstable; urgency=medium * Rewrite USB keyboard detection using pure udev (Closes: #757475).
Bug#898387: Patch: Please port to python 3
Package: mini-dinstall Severity: normal Dear Maintainer, As python 2 is nearing end of life, it's likely time to move on to python 3. To that end, we've ported mini-dinstall to python 3 (and I've been running it for a little bit now). You're generally going to want to pick all 5 commits, or at least pick up sections from them and test. [0]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=23ac25c0b388b5ffebf66154b12a3950b89b977a [1]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=dc580be8f9ef38a1c0903820b04e1b5c7217da16 [2]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=11bda2c49979375ab7cdea5deac04f4bcb2a5dae [3]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=1cd7d0f0248e2fe317b2e3da9f597059cf30b4d9 [4]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=946753d96692846ffe47487abf450251cad23538 ~Unit 193 Unit193 @ OFTC Unit193 @ freenode
Bug#898386: Patch: Support installing upstream detached signatures.
Package: mini-dinstall Severity: normal Dear Maintainer, For a while, now, dpkg has had support for including detached sigs with signed tarballs. These are included in the dsc so if you dget them, they will complain about a missing file. This patch[0] adds basic support for installing them. [0]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=9883708468224628f9e0e577162fb5345fe20eb4 ~Unit 193 Unit193 @ OFTC Unit193 @ freenode
Bug#898385: Patch: sign-release.sh: Add support for gpg2.
Package: mini-dinstall Severity: normal Dear Maintainer, The provided example script for signing releases currently supports gpg1, though this is on the way out in Debian. Thusly, I have added support for gpg2[0]. I would greatly appreciate if I could share this benefit with others. [0]: https://loki.unit193.net/cgit/users/unit193/mini-dinstall.git/commit/?id=8ba508e724e9e02675c3673b5bed725ef9bf3b85 ~Unit 193 Unit193 @ OFTC Unit193 @ freenode
Bug#898382: deluge-gtk: Please add support for Ayatana indicators
Package: deluge-gtk Severity: wishlist Dear Maintainer, Please add support for using the supported Ayatana indicators, instead of the fairly unmaintained Ubuntu ones. I've been using deluge with the Ayatana indicators by way of a couple of patches[0][1], though at this point I'd highly recommend enabling the indicators in Debian by default and not restricting it to Ubuntu. Thanks for maintaining Deluge! [0]: https://loki.unit193.net/cgit/users/unit193/deluge.git/commit/?id=358afd4b33125818f84c3d62bc3a3fe5d53ec67d [1]: https://loki.unit193.net/cgit/users/unit193/deluge.git/commit/?id=8a5169b1021d021492ee4e4502f596bc71507b0f ~Unit 193 Unit193 @ OFTC Unit193 @ freenode
Bug#898378: oidentd: Please switch to the new upstream and update to the latest version
Package: oidentd Severity: normal Dear Maintainer, According to the homepage, oidentd has been handed off to a new maintainer. I've been running this for a little, and it has some bug fixes I'm certainly interested in. I have uploaded a trimmed down version[0] of my package to mentors[1] in the hopes that my efforts will be of value to you. Upstream also plans to re-write the manpage, to be able to get away from the current license. [0]: https://mentors.debian.net/debian/pool/main/o/oidentd/oidentd_2.2.3-1.dsc [1]: https://mentors.debian.net/package/oidentd ~Unit 193 Unit193 @ freenode Unit193 @ OFTC
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#898364: znc: Please consider enabling tests at build time
Package: znc Severity: wishlist Dear Maintainer, While looking into updating the packaging for the alpha releases, I noticed that it'd be trivial to enable the tests. If you're interested, the below patch would achieve said task. diff --git a/debian/changelog b/debian/changelog index 052197e..c60ab70 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +znc (1.7.0-2) unstable; urgency=medium + + * d/control: Build-depend on google-mock and googletest. + * d/rules: +- Drop DEB_BUILD_OPTIONS+=nocheck, enabling tests. +- Update configure flags to find system gmock and gtest. + + -- Unit 193 <unit...@ubuntu.com> Thu, 10 May 2018 16:12:13 -0400 + znc (1.7.0-1) unstable; urgency=high * New upstream release. diff --git a/debian/control b/debian/control index a8dc9ed..22864a3 100644 --- a/debian/control +++ b/debian/control @@ -11,6 +11,8 @@ Build-Depends: debhelper (>= 11), libsasl2-dev, swig3.0, dh-python, + google-mock, + googletest, python3-dev Maintainer: Patrick Matthäi <pmatth...@debian.org> Standards-Version: 4.1.4 diff --git a/debian/rules b/debian/rules index e61e968..c1fba08 100755 --- a/debian/rules +++ b/debian/rules @@ -1,7 +1,6 @@ #!/usr/bin/make -f export DEB_BUILD_MAINT_OPTIONS = hardening=+all -export DEB_BUILD_OPTIONS+=nocheck DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) @@ -15,7 +14,9 @@ DEB_CONFIGURE_EXTRA_FLAGS := \ --enable-tcl \ --enable-cyrus \ --enable-perl \ - --enable-python + --enable-python \ + --with-gtest=/usr/src/googletest/googletest \ + --with-gmock=/usr/src/googletest/googlemock %: dh $@ --with python3 ~Unit 193 Unit193 @ OFTC Unit193 @ freenode
Bug#896862: ITP: ruby-ed25519 -- efficient digital signature library providing the Ed25519 algorithm
Package: wnpp Severity: wishlist Owner: Unit 193 <unit...@ubuntu.com> * Package name: ruby-ed25519 Version : 1.2.4 Upstream Author : Tony Arcieri <tony.arci...@gmail.com> * URL : https://github.com/crypto-rb/ed25519 * License : Expat Programming Lang: Ruby Description : efficient digital signature library providing the Ed25519 algorithm A Ruby binding to the Ed25519 elliptic curve public-key signature system described in RFC 8032. . Ed25519 is a modern implementation of a Schnorr signature system using elliptic curve groups. . Ed25519 provides a 128-bit security level, that is to say, all known attacks take at least 2^128 operations, providing the same security level as AES-128, NIST P-256, and RSA-3072. This package will be required for newer versions of ruby-net-ssh.
Bug#894481: numlockx: `laptop-detect` has moved from /usr/sbin to /usr/bin
Package: numlockx Severity: normal Dear Maintainer, In debian/55numlockx (on installed systems, /etc/X11/Xsession.d/55numlockx) you call /usr/sbin/laptop-detect, but in version 0.14 of laptop-detect the binary was moved from /usr/sbin to /usr/bin thus rendering the check unable to complete. ~Unit 193 Unit193 @ freenode Unit193 @ OFTC -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.14.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages numlockx depends on: ii libc6 2.27-2 ii libx11-6 2:1.6.5-1 ii libxext6 2:1.3.3-1+b2 pn libxtst6 numlockx recommends no packages. Versions of packages numlockx suggests: pn x-display-manager
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#893746: dh-autoreconf: Consider adding support for Xfce packages (via xdt-autogen)
Package: dh-autoreconf
Version: 16
Severity: wishlist
Dear Maintainer,
Please consider adding support for packages which make use of XDT_* features,
using xdt-autogen.
As it stands, any Xfce package using dh 10 or above must override dh_autoreconf
with 'NOCONFIGURE=1 dh_autoreconf xdt-autogen' which is not known by all DDs
and may lead to bugs such as #870420.
An functional example patch inline below.
--- a/dh_autoreconf 2017-03-31 12:13:10.0 -0400
+++ b/dh_autoreconf 2018-02-14 18:36:41.665562722 -0500
@@ -154,9 +154,17 @@
eval {
# Run autoreconf to recreate the needed files.
my $pwd = getcwd();
+my $dir = '.';
chdir $opt_sourcedir if (defined($opt_sourcedir) && !compat(9));
-@ARGV ? doit(@ARGV, @{$dh{U_PARAMS}}) : doit('autoreconf', '-f', '-i',
@directories);
+if (@ARGV) {
+doit(@ARGV, @{$dh{U_PARAMS}});
+} elsif (complex_doit("grep -q '^XDT_' ${dir}/configure.ac
${dir}/configure.in")) {
+$ENV{NOCONFIGURE}='1';
+doit('xdt-autogen', @directories);
+} else {
+doit('autoreconf', '-f', '-i', @directories);
+};
chdir $pwd;
1;
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.14.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dh-autoreconf depends on:
ii autoconf 2.69-11
ii automake 1:1.15.1-3
ii autopoint 0.19.8.1-4
ii debhelper 11.1.5
ii libtool2.4.6-2
ii perl 5.26.1-5
dh-autoreconf recommends no packages.
dh-autoreconf suggests no packages.
-- no debconf information
Bug#883147: New upstream available, with python3 port
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Howdy, There's an active upstream that has already done the work to port to Python 3, though drops the GUI. * https://github.com/effigies/BitTornado - From going through the patches, the following may still apply: 06_README_portchange.dpatch 11_sorthashcheck.dpatch 16_fix_ipv6_in_SocketHandler.dpatch 17_fix_NatCheck_bufferlen_error.dpatch 18_fix_launchmany_encrypter.dpatch 24_clarify_ip_parameter.dpatch 25_errors_in_error_handling.dpatch 31_fix_for_compact_reqd_off.dpatch I have a local package already if you are interested in (co-)maintaining this. ~Unit 193 Unit193 @ Freenode Unit193 @ OFTC -BEGIN PGP SIGNATURE- iQIcBAEBCQAGBQJaIRwdAAoJEFAB4bCao3RLpNMQAKP41vj+xqk4TNrBzC0Q+/ZT DzdE+Wi/qqTV/B/BnGE9FLg5/AtNbA1x7o1jPzwKR4yx75xO9zpa+RTV5ZFjTlZ8 GFGjxOdfALb5scZ0K2Lukx6aa4lpWvOnQ64bRCNt5YlI+/MfwgKkZO7ouMb1McvE 2sXO8MdjycCAvvayL3LhxtFxlCezsjYAh1wg4B74aCgvf0xNpj9icOnaxX53oEnT /lEwW2K0t5CK+IwPQlpbkPM0FmQ734DTD68dudLmFuJi9PdwkE7WY+VWf2H4RqBq dZ5KsmF0pCvMBlYUPHJeTEFH4BS4X5lP0VbjBw6IcnNxpD3wCSO9Ohg0C1cPNmeb bC9gjM5mmbrt0bcC4fMU20ncmhjPbUBBxC/v/BLLkhrLFsVjkA8yFa5+RmATdGSP rB+bnR301+2Xc3/BEgN7DVHGAtjkgWV18aKW3c5XcMsdlbwPRk/VsZsCxrhipKrB RdB8LzCtLn7HjUrB91CO5av2n7xb7llrOUbsvCE4kA7g1hWfWqik052Afl/qyRfP dyPijriCcmAIbcbCIYOVZFBczHQyVf0XVVEorB97nV5Dt96qkTPoRQuWV9Rts29o 4+tXK0ZURFJ0UEbFtXDGXRUzzxJ8UwMO08qglElK9LzsJFcI/4PYDDU++L3HNunq 0trBIYEiKMZRofCjet+R =u/Jh -END PGP SIGNATURE-
Bug#872963: apt-ftparchive: Passes through hashes even when explictly disabled.
Package: apt-utils Version: 1.5~beta1 Severity: normal Dear Maintainer, When passing options such as APT::FTPArchive::SHA1=false to ftparchive, hashes for the source and Debian tarballs are still added to Sources and only the dsc is skipped. This causes warnings from eg, the census tools. I'd expect when a hash type is disabled, then none of the hashes of that type are generated. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.11.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-utils depends on: ii apt 1.5~beta1 ii libapt-inst2.0 1.5~beta1 ii libapt-pkg5.0 1.5~beta1 ii libc6 2.24-14 ii libdb5.35.3.28-13 ii libgcc1 1:7.1.0-13 ii libstdc++6 7.1.0-13 apt-utils recommends no packages. apt-utils suggests no packages. -- no debconf information
Bug#872687: xfce4-pulseaudio-plugin: Unable to click or use volume slider
Howdy, This is not a bug specific to xfce4-pulseaudio-plugin but to GTK+3. You can see upstream reports in GTK+3[1], Xfce[2], and even one over at Arch[3]. If you apply the simple patch by Carlos Garnacho and rebuild GTK+3 you will no longer have this issue. [1]: https://bugzilla.gnome.org/show_bug.cgi?id=786029 [2]: https://bugzilla.xfce.org/show_bug.cgi?id=13770 [3]: https://bugs.archlinux.org/task/55114 ~Unit 193 Unit193 @ Freenode Unit193 @ OFTC
Bug#868070: gocryptfs: '--version' option is useless, containing only 'gocryptfs'
Package: gocryptfs
Version: 1.3-1
Severity: normal
Dear Maintainer,
When you call `gocryptfs --version`, the only info you get back is 'gocryptfs'.
This is because the required vars aren't set at build time, with the below
patch I get 'gocryptfs 1.3; go-fuse 0.0~git20170609.0.5690be4-1; 2017-06-17
go1.7.6'
--- gocryptfs-1.3/debian/rules 2017-06-05 21:03:20.0 -0400
+++ gocryptfs-1.3/debian/rules 2017-06-16 20:14:57.253417564 -0400
@@ -3,6 +3,10 @@
PKD = $(word 1,$(abspath $(dir $(MAKEFILE_LIST
PKG = $(shell dpkg-parsechangelog -l$(PKD)/changelog --show-field=Source)
VER ?= $(shell (dpkg-parsechangelog -l$(PKD)/changelog | grep Version | sed
's/Version..//' | sed 's/-.\+//'))
+include /usr/share/dpkg/default.mk
+export DEB_BUILD_MAINT_OPTIONS=hardening=+all
+FUSEVER = $(shell dpkg-query --showformat='$${Version}' -W
golang-github-hanwen-go-fuse-dev)
+DEB_LDFLAGS = -X main.GitVersion=$(DEB_VERSION_UPSTREAM) -X
main.BuildTime=$(SOURCE_DATE_EPOCH) -X main.GitVersionFuse=$(FUSEVER)
%:
dh $@ --buildsystem=golang --with=golang
@@ -11,7 +15,7 @@
DT = $(shell date -d "${CHDATE}" "+%Y-%m-%d")
override_dh_auto_build:
- GOPATH=$(shell ls -d $(CURDIR)/obj*) go install -v
github.com/rfjakob/gocryptfs
+ GOPATH=$(shell ls -d $(CURDIR)/obj*) go install
-ldflags="$(DEB_LDFLAGS)" -v github.com/rfjakob/gocryptfs
pandoc Documentation/MANPAGE.md -s -t man -o debian/gocryptfs.1
override_dh_auto_clean:
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gocryptfs depends on:
ii libc6 2.24-12
ii libfuse2 2.9.7-1
ii libssl1.1 1.1.0f-3
gocryptfs recommends no packages.
gocryptfs suggests no packages.
-- no debconf information
Bug#867512: python-ayatana-appindicator: Traceback when trying to import
Package: python-ayatana-appindicator Version: 0.5.0-1 Severity: important Dear Maintainer, When trying to import ayatana_appindicator I get traceback: >>> import ayatana_appindicator Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/ayatana_appindicator/__init__.py", line 27, in from _ayatana_appindicator import * ImportError: /usr/lib/python2.7/dist-packages/ayatana_appindicator/_ayatana_appindicator.i386-linux-gnu.so: undefined symbol: pyappindicator_functions -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-ayatana-appindicator depends on: ii ayatana-indicator-application 0.5.1-1 ii ayatana-indicator-common 0.6.0-1 ii libayatana-appindicator1 0.5.0-1 ii libayatana-appindicator3-1 0.5.0-1 ii libayatana-indicator3-7:i386 0.6.0-1 ii libayatana-indicator7:i386 0.6.0-1 ii python-ayatana-appindicator0.5.0-1 python-ayatana-appindicator recommends no packages. python-ayatana-appindicator suggests no packages.
Bug#861722: Example packaging
Howdy, Lucas requested I post my example packaging to this bug. There's a couple FIXMEs, but everything else should be pretty decent for the support in ruby-net-ssh (If you grab the source tarball of that from GH releases, you'll get all the tests which pass too.) dget https://mentors.debian.net/debian/pool/main/r/ruby-bcrypt-pbkdf/ruby-bcrypt-pbkdf_1.0.0-1.dsc dget https://mentors.debian.net/debian/pool/main/r/ruby-rbnacl/ruby-rbnacl_5.0.0-1.dsc ~Unit 193 Unit193 @ Freenode Unit193 @ OFTC
Bug#809781: (no subject)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Howdy,
I noticed the uscan reports have been dead a while as well, though it might be
a slightly different issue. If one were to apply the attached patch to the pts,
it'd start picking them up again. I have verified this locally.
~Unit 193
Unit193 @ Freenode
Unit193 @ OFTC
-BEGIN PGP SIGNATURE-
iQIcBAEBCQAGBQJZWLaKAAoJEFAB4bCao3RLPbYP/0TyBdZCAgB9iL2jLCqViD7X
l++VA13atgEXWViK6+2Up4boxwmzrwpbE12+roVGqmZ4rJ8BxYanK5wDhx1fo7zV
LMbJ1HRstQ0RRyZXbsMNeB0GOv6EfDdl/fUp1bcPsIyhNt1e9lx9RkzL+fHssux2
h+cORrF3jU5zHBY7sGsM/KvB9nxrg6+5mSqJy7x8/puvQYRcpmVM2r50QOU3tkA5
lCVUC/BNT3Yw0rG4q7fsLXiJk/1YC7YVSDgFWHJ4LkCwh9tsxO2AYIG22ydjMCu7
WGDZ4DiaQwSvoWstfSjTg7mekvyIGR8GIdobxiPnsaOiPt4dRsKiGbrYuSgubcRW
HmNmI+bQb9ROZKl1qfueB6kK1nGIDzdB2CYgtqQOYKg7Wl+/BGdyZkYw6wW21Yz0
i4Wsu2mWOC+5tzpuiokfXeDiiHXeulftTLC1L9LjDaO0WlgpWxrMg9+W5F49z+JM
e3jI8pXjfOfYoewRvm2ARGpS8/iutyjo+Xmic2qMlJPH2Fr8ZOgjhqtaCRxJviI2
MCzoLryNmacnhTBvK3xdXsqy50lXO9gRqf7vFprtWNZGRUJP9gyat9wdeo/0Rr9q
MeAbQja6+zZwnkU2bN6bFAgLGVfPMUhV9m94hyHI6hO2nHhr+fzWqF8i40wtVHCI
1jljGLyW8IgU1Xvn7LbX
=9t4F
-END PGP SIGNATURE-Index: www/bin/other_to_xml.py
===
--- www/bin/other_to_xml.py (revision 3633)
+++ www/bin/other_to_xml.py (working copy)
@@ -534,18 +534,19 @@
pass # Silent failure
# read info gathered from watch file scanner
-data = yaml.load(file(os.path.join(dir, "dehs.yaml")), yaml.CSafeLoader)
+with open(os.path.join(dir, "dehs.json")) as data_file:
+data = json.load(data_file)
if not data:
data = []
dehs = {}
for entry in data:
pkgname = entry["package"]
-if "status" in entry and "Newer version" in entry["status"]:
+if "status" in entry and "newer package" in entry["status"]:
if pkgname not in dehs:
dehs[pkgname] = {}
dehs[pkgname]["newer"] = str(entry["upstream-version"])
dehs[pkgname]["url"] = entry["upstream-url"]
-if "warnings" in entry:
+if entry["warnings"] and "more than one main upstream tarballs listed." not in entry["warnings"]:
if pkgname not in dehs:
dehs[pkgname] = {}
dehs[pkgname]["error"] = entry["warnings"]
Index: www/bin/update_incoming.sh
===
--- www/bin/update_incoming.sh (revision 3633)
+++ www/bin/update_incoming.sh (working copy)
@@ -219,7 +219,7 @@
#svnbuildstat_list.txt
# download watch file information
-get https://udd.debian.org/cgi-bin/upstream-status.json.cgi dehs.yaml
+get https://udd.debian.org/cgi-bin/upstream-status.json.cgi dehs.json
# needs UDD replacement:
#get https://qa.debian.org/watch/watch-avail.txt watch-avail.txt
#get https://qa.debian.org/watch/watch-broken.txt watch-broken.txt
Bug#864740: ITP: ruby-roo -- can access the contents of various spreadsheet files
Package: wnpp Severity: wishlist Owner: Unit 193 <unit...@ubuntu.com> * Package name: ruby-roo Version : 2.7.1 Upstream Author : Thomas Preymesser, Ben Woosley * URL : http://github.com/roo-rb/roo * License : Expat Programming Lang: Ruby Description : can access the contents of various spreadsheet files Roo can access the contents of various spreadsheet files. It can handle * OpenOffice * Excelx * LibreOffice * CSV While there are other Ruby gems to work with spreadsheets, they didn't handle ods files. Another benefit is that this gem is activly maintained (last release Jan 2017.)
Bug#863288: (no subject)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Alternativly, if you didn't want to recommend python-appindicator in Debian you
could still make the package syncable with the attached patch.
~Unit 193
Unit193 @ Freenode
Unit193 @ OFTC
-BEGIN PGP SIGNATURE-
iQIcBAEBCQAGBQJZJ2JZAAoJEFAB4bCao3RLrkcP+QHiuJkbve/ufbcXnCSzLAnF
BPDrt+GOCqVrnyltxNM710a/S+uEmW4qkbJAYbyBsV+1tZUf27OemD3SelBdjTQe
KZZwza8PvKy2iTLb96hPpHEKeTGsleguC4Q/Ci0gtgEpyhcSOkqiJgzVmrjcAY/w
sO+NhgoV8xk+kyY++GaAEN7euCrO8EUJTnSmqWoQe5JW09MWF3ADwUtpgFgnSKHv
foP8eBOeasm+KaR5Wx3Z9WD/JsAcp1QswG5Csl3EGrOKn7aAH0YVi/+EnbcMEEna
+yTFzj5M1Vlc2wz9qM9tvOdcl3l7F3900WyJSc5tCO27RZ/SHERFzhRs9ZnaMG33
YKOshN6NS20Wk+k9IU1vcuKjAn4kBhhqWZKDAJVOhQW3OrZN0vB+FM04JTSWwuXa
xB7nOGTSAwSOV6Cu55+51LA+BjuYRmen4WRshfnzQK3ITYgB8ZfJgK4WocmQrIBI
lrhixmGXi4iar1rGTJ/Jz7N/YE2l3pYy7QFZIpiXTqgGMP1nZzotNaVb7qqFhKRN
Dl1Y1edYyq0cZs6j+a0ynPTylt/ftfD5yqSG8z9oxHtj4khU3G5SWiZXEZKa54wy
5mT3mMy8yS6tQ/3HrmghIepXM5MV79+Bb6W1SpH40kura0hb12hnwgZA8UwgV2md
RK4qFr5VuDfJF5GmnpG/
=EC48
-END PGP SIGNATURE-From d65670c15990838b8b1b1447ac99ca5f5194fd23 Mon Sep 17 00:00:00 2001
From: Unit 193 <unit...@ubuntu.com>
Date: Fri, 29 Apr 2016 00:18:31 -0400
Subject: d/control, d/rules: Override dh_gencontrol to recommend
python-appindicator if on Ubuntu.
---
debian/control | 2 +-
debian/rules | 7 +++
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/debian/control b/debian/control
index 482624a..029f4b8 100644
--- a/debian/control
+++ b/debian/control
@@ -108,7 +108,7 @@ Depends: ${misc:Depends}, ${python:Depends},
xdg-utils
Breaks: deluge (<< 1.2.0-1)
Replaces: deluge (<< 1.2.0-1)
-Recommends: python-pygame
+Recommends: ${dist:Recommends}, python-pygame
Description: bittorrent client written in Python/PyGTK (GTK+ ui)
Deluge is a full-featured, multi-platform, multi-interface BitTorrent client
using libtorrent-rasterbar in it's backend and featuring multiple
diff --git a/debian/rules b/debian/rules
index 48ac68d..e2e3dec 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,5 +1,9 @@
#!/usr/bin/make -f
+ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)
+ SUBSTVARS = -Vdist:Recommends="python-appindicator"
+endif
+
%:
dh $@ --with python2
@@ -20,3 +24,6 @@ override_dh_auto_clean:
dh_auto_clean
find . -type d -name '*.egg-info' | xargs rm -rf
rm -f deluge/data/share/applications/deluge.desktop
+
+override_dh_gencontrol:
+ dh_gencontrol -- $(SUBSTVARS)
--
cgit v0.12
Bug#861722: ruby-net-ssh: Please enable optional support for Ed25519 keys
Package: ruby-net-ssh Severity: normal As of version 4.0, ruby-net-ssh added support for Ed25519 ssh keys via ruby-bcrypt-pbkdf and ruby-rbnacl, I've been using this feature for a while and would greatly like to see this support in the Debian packages.
Bug#861509: lintian: Please support 'devel' as an Ubuntu release
Package: lintian Version: 2.5.50.1 Severity: normal Dear Maintainer, In Ubuntu, 'devel' is an alias to the current development release, it would be nice if changes-file/known-dists reflected this. diff --git a/vendors/ubuntu/main/data/changes-file/known-dists b/vendors/ubuntu/main/data/changes-file/known-dists index bf8f163..70f7250 100644 --- a/vendors/ubuntu/main/data/changes-file/known-dists +++ b/vendors/ubuntu/main/data/changes-file/known-dists @@ -1,5 +1,8 @@ # List of ubuntu distributions +# Alias +devel + dapper hardy karmic
Bug#827236: ITP: sqlitestudio -- SQLite database manager
Package: wnpp Severity: wishlist Owner: Unit 193 <unit...@ubuntu.com> * Package name: sqlitestudio Version : 3.1.0 Upstream Author : SalSoft <supp...@salsoft.com.pl> : Paweł Salawa * URL : http://sqlitestudio.pl/ * License : GPL-3 Programming Lang: C++, C Description : SQLite database manager SQLiteStudio is a comprehensive and reliable SQLite database manager that provides you with a simple means of managing the contents of each database, including tables, triggers and views.
Bug#680782:
I've been using this patch for a while and I don't recall seeing any issues with it.
Bug#680782: [PATCH 1/8] Allow re-installing same version packages.
---
mini-dinstall | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mini-dinstall b/mini-dinstall
index 6e0ea84..db6938f 100755
--- a/mini-dinstall
+++ b/mini-dinstall
@@ -1127,7 +1127,7 @@ class ArchiveDirIndexer(threading.Thread):
if nodb_mode:
cmdline = ['apt-ftparchive', type, dir]
else:
-cmdline = ['apt-ftparchive', type, dir, '--db', '%s.db' %dir]
+cmdline = ['apt-ftparchive', type, dir, '-o',
'APT::FTPArchive::AlwaysStat=true', '--db', '%s.db' %dir]
self._logger.debug("Running: " + string.join(cmdline, ' '))
if no_act:
--
2.7.4
Bug#822649: devscripts: uscan: Please add an option for not displaying output if upstream == debian and no errors occur
Package: devscripts Version: 2.16.2 Severity: normal Dear Maintainer, uscan has now started being much more verbose after 2.16 when checking for newer versions, this is nice I'm sure if you're only scanning a couple of packages, but if you have any number then it's hard to see the trees through the forest. Please add an option less verbose than --no-verbose such that only errors or warnings appear if the local version of the package is the latest upstream too. -- Package-specific info: --- /etc/devscripts.conf --- -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.4.0-1-686-pae (SMP w/2 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) Versions of packages devscripts depends on: ii dpkg-dev 1.18.4 ii libc62.22-7 ii perl 5.22.1-10 pn python3:any Versions of packages devscripts recommends: ii apt 1.2.10 ii at 3.1.18-2 ii curl7.47.0-1 ii dctrl-tools 2.24-2 pn debian-keyring ii dput0.9.6.4 pn equivs ii fakeroot1.20.2-1 ii file1:5.25-2 ii gnupg 1.4.20-6 ii gnupg2 2.1.11-7 pn libdistro-info-perl ii libencode-locale-perl 1.05-1 ii liblwp-protocol-https-perl 6.06-2 pn libsoap-lite-perl ii liburi-perl 1.71-1 ii libwww-perl 6.15-1 ii lintian 2.5.43 ii man-db 2.7.5-1 ii patch 2.7.5-1 ii patchutils 0.3.4-1 ii python3-debian 0.1.27 ii python3-magic 1:5.25-2 ii sensible-utils 0.0.9 ii strace 4.10-3 ii unzip 6.0-20 pn wdiff ii wget1.17.1-1+b1 ii xz-utils5.1.1alpha+20120614-2.1 Versions of packages devscripts suggests: ii bsd-mailx [mailx]8.1.2-0.20160123cvs-2 ii build-essential 11.7 pn cvs-buildpackage pn devscripts-el pn diffoscope pn dose-extra pn gnuplot ii gpgv 1.4.20-6 ii libauthen-sasl-perl 2.1600-1 ii libfile-desktopentry-perl0.22-1 ii libnet-smtp-ssl-perl 1.03-1 pn libterm-size-perl ii libtimedate-perl 2.3000-2 ii libyaml-syck-perl1.29-1+b1 pn mozilla-devscripts pn mutt ii openssh-client [ssh-client] 1:7.2p2-4 pn svn-buildpackage ii w3m 0.5.3-27 -- no debconf information
Bug#822633: debsums: No longer bails when there's 'Too many levels of symbolic links', just eats CPU like the cookie monster with cookies
Package: debsums Version: 2.1.2 Severity: important Dear Maintainer, This regression is introduced in a01dbf49d7ccfc8d518b5218b0dee51eb5aa3ecc and will occur when a file is a symlink to itself. To reproduce, try creating /usr/share/doc/libfm-extra4/changelog.Debian.gz -> ../libfm-extra4/changelog.Debian.gz I have no idea what caused this in the package, but was also reported downstream: https://launchpad.net/bugs/1522563 -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.4.0-1-686-pae (SMP w/2 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) Versions of packages debsums depends on: ii dpkg 1.18.4 ii libdpkg-perl 1.18.4 ii libfile-fnmatch-perl 0.02-2+b2 ii perl 5.22.1-10 ii ucf 3.0036 debsums recommends no packages. debsums suggests no packages. -- no debconf information
Bug#820560: apt-file doesn't account for contents generated with apt-ftparchive (missing section)
Package: apt-file Version: 3.0 Severity: normal Dear Maintainer, When a contents file is generated using `apt-ftparchive contents directory`, apt-file is unable to list files by package name, though is able to report package if given a file. Example contents file: usr/lib/debug/.build-id/e9/d3d8f6f6fc4cc31dddab43815b425aac241c09.debug libcryptx-perl-dbgsym usr/lib/i386-linux-gnu/perl5/5.22/Crypt/AuthEnc.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/AuthEnc/CCM.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/AuthEnc/EAX.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/AuthEnc/GCM.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/AuthEnc/OCB.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/AES.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Anubis.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Blowfish.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/CAST5.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Camellia.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/DES.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/DES_EDE.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/KASUMI.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Khazad.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/MULTI2.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Noekeon.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/RC2.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/RC5.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/RC6.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/SAFERP.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/SAFER_K128.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/SAFER_K64.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/SAFER_SK128.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/SAFER_SK64.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/SEED.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Skipjack.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/Twofish.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Cipher/XTEA.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/CHAES.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/MD2.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/MD4.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/MD5.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/RIPEMD128.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/RIPEMD160.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/RIPEMD256.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/RIPEMD320.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA1.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA224.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA256.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA384.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA512.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA512_224.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/SHA512_256.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/Tiger192.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Digest/Whirlpool.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/KeyDerivation.pmlibcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac/F9.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac/HMAC.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac/OMAC.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac/PMAC.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac/Pelican.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mac/XCBC.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mode.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mode/CBC.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mode/CFB.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mode/CTR.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mode/ECB.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/Mode/OFB.pm libcryptx-perl usr/lib/i386-linux-gnu/perl5/5.22/Crypt/PK.pm
Bug#799011: ITP: biblesync -- multicast protocol to support Bible co-navigation
Package: wnpp Severity: wishlist Owner: Unit 193 <unit...@ubuntu.com> * Package name: biblesync Version : 1.1.2 Upstream Author : Karl Kleinpaste <charc...@users.sf.net> * URL : https://github.com/karlkleinpaste/biblesync * License : public-domain Programming Lang: C++ Description : multicast protocol to support Bible co-navigation This is a C++ single class library encapsulating a protocol conduit. The premise is that there is a local network over which to multicast Bible navigation, and someone, possibly several someones, will transmit, and others will receive. The choices for when you decide to xmit and what to do when you recv are up to you as the application designer. This package is a new build-dep for Xiphos. https://anonscm.debian.org/cgit/pkg-crosswire/biblesync.git/
Bug#793439: ITP: virtualbox-ext-pack -- support for USB 2.0 devices, VirtualBox RDP and PXE boot for Intel cards
Package: wnpp Severity: wishlist Owner: Unit 193 unit...@ubuntu.com * Package name: virtualbox-ext-pack Version : 5.0.0 Upstream Author : Oracle Corporation * URL : https://www.virtualbox.org/ * License : VirtualBox PUEL Description : support for USB 2.0 devices, VirtualBox RDP and PXE boot for Intel cards VirtualBox requires an extension pack in order to provide support for RDP, as well as USB 2.0 and PXE booting for Intel network cards, etc. This PUEL licensed extension pack is free for personal use. This package enhances VirtualBox as packaged in Debian. This is a downloader package, doesn't contain the actual extension pack in order to comply with the license. The current packaging is sitting in http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox-ext-pack.git -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789253: Incompatibilities with python-oauth2client
Howdy, Checked with the new upstream (1.4.1) and it was still present, and there seems to be no tracker on it. I fixed it with the following: diff --git a/googleapiclient/discovery.py b/googleapiclient/discovery.py index 4109865..0373dc0 100644 --- a/googleapiclient/discovery.py +++ b/googleapiclient/discovery.py @@ -64,7 +64,7 @@ from googleapiclient.model import JsonModel from googleapiclient.model import MediaModel from googleapiclient.model import RawModel from googleapiclient.schema import Schemas -from oauth2client.client import GoogleCredentials +from oauth2client.client import Credentials from oauth2client.util import _add_query_parameter from oauth2client.util import positional ~Unit 193 Unit193 @ Freenode, OFTC. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787144: VESA(0): Cannot read int vect
Package: xserver-xorg-core Version: 2:1.17.1-2 Severity: normal Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=89353 Dear Maintainer, Trying to boot Debian in virtualbox or qemu with vesa results in xorg bailing out. The upstream fix is: http://cgit.freedesktop.org/xorg/xserver/patch/?id=0a78b599b34cc8b5fe6fe82f90e90234e8ab7a56 And there is a downstream bug (and fix): https://launchpad.net/bugs/1433198 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 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) Versions of packages xserver-xorg-core depends on: ii keyboard-configuration 1.127 pn libaudit0 none ii libc6 2.19-18 ii libdrm2 2.4.60-3 pn libgcrypt11 none ii libpciaccess0 0.13.3-1 ii libpixman-1-0 0.32.6-3 ii libselinux1 2.3-2 pn libudev0none ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 pn libxfont1 none ii udev215-18 pn xserver-common none Versions of packages xserver-xorg-core recommends: ii libgl1-mesa-dri 10.5.5-1 Versions of packages xserver-xorg-core suggests: pn xfonts-100dpi | xfonts-75dpi none pn xfonts-scalable none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751104: Initial cmst packaging
Howdy, So I was checking out connman a little bit ago and found cmst as well, so I packaged it. I don't expect I'll be using connman long, so I'm not really looking to be the maintainer, but threw what I had up on collab-maint in case someone else wanted a starting point. http://anonscm.debian.org/gitweb/?p=collab-maint/cmst.git If you'd like the repo space, just take it (though a ping would be nice), and if you'd like to use this as a starting point, just swap out my name in all places for your own. Regards, Unit 193 Unit193 @ irc.freenode.net Unit193 @ irc.oftc.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735403: pepperflashplugin-nonfree: Please support configuration in /etc/chromium-browser/ in addition to /etc/chromium/
Package: pepperflashplugin-nonfree Severity: wishlist Dear Maintainer, Please consider having the package installation check for /etc/chromium-browser/ in addition to /etc/chromium/ as some derivatives have the configuration there. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
