Bug#1077005: CFLAGS+=foo etc stopped working
Control: reassign -1 1076932 dpkg-dev Control: forcemerge -1 1076932 Control: affects -1 src:webdis On Fri, Jul 26, 2024 at 01:20:28PM GMT, Nicolas Boulenguez wrote: > The fact that the previous lazy evaluation mechanism, in which the > $(evals VAR=$(VAR)) trick is already present, did what you expect in > some contexts does not make CFLAGS+= a supported interface, and your > code could break in other contexts. > > Replacing > CFLAGS+= foo > with > DEB_CFLAGS_MAINT_APPEND := foo > in the broken packages seems more fruitful to me, and I would prefer > to help with that. I'm running into a similar problem with webdis (#1076932), however in that case we're doing CFLAGS += $(CPPFLAGS) I'm not sure how to do that with the DEB_CFLAGS_MAINT_APPEND. My naïve attempt at DEB_CFLAGS_MAINT_APPEND = $(CPPFLAGS) results in /usr/share/dpkg/buildflags.mk:51: *** Recursive variable 'dpkg_buildflags_run' references itself (eventually). Stop. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1076932: webdis: FTBFS: src/client.h:6:10: fatal error: http_parser.h: No such file or directory
On Wed, Jul 24, 2024 at 12:50:20PM GMT, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: > > > [...] > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > dh_auto_build > make -j2 "INSTALL=install --strip-program=true" > make[2]: Entering directory '/<>' > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DMSGPACK=1 -o src/webdis.o src/webdis.c > cc -c -g -O2 -Werror=implicit-function-declaration > -ffile-prefix-map=/<>=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -DMSGPACK=1 -o src/cmd.o src/cmd.c > In file included from src/cmd.c:4: > src/client.h:6:10: fatal error: http_parser.h: No such file or directory > 6 | #include "http_parser.h" > | ^~~ Nothing has changed in the packaging since it last successfully built, so I used debbisect to narrow down the problem to the dpkg 1.22.7 upload. With dpkg 1.22.6, webdis builds fine because the CFLAGS that are defined in debian/rules (in particular the -I options) are picked up by the upstream build: make -j6 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>' cc -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -Isrc -Isrc/http-parser -DMSGPACK=1 -o src/webdis.o src/webdis.c However, with dpkg 1.22.7 we see a very different command being used to compile: make -j2 "INSTALL=install --strip-program=true" make[2]: Entering directory '/<>' cc -c -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DMSGPACK=1 -o src/webdis.o src/webdis.c It's missing "-Wdate-time -D_FORTIFY_SOURCE=2" and the include directories. The relevant lines from debian/rules are export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow include /usr/share/dpkg/buildflags.mk CFLAGS += $(CPPFLAGS) export CFLAGS += -Isrc -Isrc/http-parser Maybe this package is trying to use the dpkg-provided build flags incorrectly, but I've seen this pattern in a number of places. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1075725: UDD/dmd: Make the header row of tables sticky/fixed
On Fri, Jul 05, 2024 at 10:53:04PM GMT, James McCoy wrote:
> Rather than go through all that mess, I poked around some more with some
> CSS adjustments and was able to put something together that didn't
> require updating anything related to datatables.
>
> https://salsa.debian.org/qa/udd/-/merge_requests/53
>
> I've also attached the patch.
Actually attached this time.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
>From 95b8c26ff0012f08ad86cf2d6b4bc7e18b0b578f Mon Sep 17 00:00:00 2001
From: James McCoy
Date: Fri, 5 Jul 2024 22:24:08 -0400
Subject: [PATCH] dmd: Make the first row/column of dmddetails table sticky
When dmddetails has many rows, it can be easy to lose track of what each
column represents. Similarly, since the table is wide, one can lose
track of what package a row corresponds to when scrolling to columns on
the right.
In order to keep them visible, a few more css rules are needed.
To keep the headers visible, the entire thead, rather than just the th,
needs to be sticky to the top of the viewport. This ensures both rows of
the table header are visible.
To keep the first column visible, change the first column in the tbody
to a th and mark it sticky to the left of the viewport. Since debian.css
makes th bold, also set these th back to normal font-weight.
In addition, the th in the first row of the table head needs to be
sticky to the left. We can't simply select the first th of the table
head because there are two rows and a rowspan involved.
Closes: #1075725
Signed-off-by: James McCoy
---
web/css/dmd.css | 21 +
web/templates/dmd.erb | 2 +-
2 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/web/css/dmd.css b/web/css/dmd.css
index 40dafef..c0829fd 100644
--- a/web/css/dmd.css
+++ b/web/css/dmd.css
@@ -26,3 +26,24 @@ table#todolist tbody td {
font-size: 14px;
overflow-wrap: anywhere;
}
+
+table#dmddetails thead {
+ position: sticky;
+ z-index: 1;
+ top: 0;
+ background: white;
+}
+
+table#dmddetails thead tr:first-child>th:first-child {
+ position: sticky;
+ z-index: 2;
+ left: 0;
+ background: white;
+}
+
+table#dmddetails tbody th {
+ position: sticky;
+ left: 0;
+ background: white;
+ font-weight: normal;
+}
diff --git a/web/templates/dmd.erb b/web/templates/dmd.erb
index 44997c0..329b605 100644
--- a/web/templates/dmd.erb
+++ b/web/templates/dmd.erb
@@ -185,7 +185,7 @@
%>
<% next if not uddd.versions.include?(src) %>
<% next if not uddd.versions[src].include?('debian') %>
-https://tracker.debian.org/<%= ERB::Util::url_encode(src) %>" title="<%= h[:reason] %>"><%= src %>
+https://tracker.debian.org/<%= ERB::Util::url_encode(src) %>" title="<%= h[:reason] %>"><%= src %>
<% h[:versions].each do |v| %>
<%= v %>
--
2.45.2
Bug#1075725: UDD/dmd: Make the header row of tables sticky/fixed
Control: tag -1 patch On Wed, Jul 03, 2024 at 03:40:23PM GMT, James McCoy wrote: > The todolist and dmddetails tables can be quite long, which makes it > difficult to keep track of what data each column is displaying. It would > be useful if the header row could be made sticky so it stays visible > when scrolling through the table. The todolist table is much more self-describing, so I left that as is. > The tables are using datatables[0] to format the data. It has an > extension called FixedHeader[1] which supports adding this > functionality. > > [0]: https://datatables.net/ > [1]: https://datatables.net/extensions/fixedheader/ > > I tested locally by downloading a new bundled datatables.css / > datatables.jss with fixedheader included and adjusting the dmd template > and javascript with the attached patch. Rather than go through all that mess, I poked around some more with some CSS adjustments and was able to put something together that didn't require updating anything related to datatables. https://salsa.debian.org/qa/udd/-/merge_requests/53 I've also attached the patch. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1075725: UDD/dmd: Make the header row of tables sticky/fixed
Package: qa.debian.org
Severity: wishlist
User: qa.debian@packages.debian.org
Usertags: udd
The todolist and dmddetails tables can be quite long, which makes it
difficult to keep track of what data each column is displaying. It would
be useful if the header row could be made sticky so it stays visible
when scrolling through the table.
The tables are using datatables[0] to format the data. It has an
extension called FixedHeader[1] which supports adding this
functionality.
[0]: https://datatables.net/
[1]: https://datatables.net/extensions/fixedheader/
I tested locally by downloading a new bundled datatables.css /
datatables.jss with fixedheader included and adjusting the dmd template
and javascript with the attached patch.
It does work nicely with the todolist table, but I think the colspan /
rowspan in the dmddetails table throws off the sizing of the header when
it becomes sticky. The header cells become larger and then don't align
with the actual columns of the table.
It would be nice if someone who understands web stuff better could turn
this a functional patch.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
diff --git i/web/js/dmd.js w/web/js/dmd.js
index 4925098..2fb12bf 100644
--- i/web/js/dmd.js
+++ w/web/js/dmd.js
@@ -32,7 +32,8 @@ $(document).ready(function() {
$('#todolist').DataTable( {
"paging": false,
-"info": false
+"info": false,
+ fixedHeader: true,
});
var dmddetails = $('#dmddetails').DataTable( {
@@ -40,6 +41,7 @@ var dmddetails = $('#dmddetails').DataTable( {
"paging": false,
"info": false,
"autoWidth": false,
+ fixedHeader: true,
stateSave: true,
buttons: [ {
extend: 'colvis',
diff --git i/web/templates/dmd.erb w/web/templates/dmd.erb
index 44997c0..45519b3 100644
--- i/web/templates/dmd.erb
+++ w/web/templates/dmd.erb
@@ -2,9 +2,7 @@
-
-
-
+
Debian Maintainer Dashboard
@@ -382,14 +380,10 @@
-
-
-
+
-
-
Bug#1074281: netavark: Drop unnecessary librust-simple-error-dev Build-Depends
Source: netavark Version: 1.4.0-4.1 Severity: normal Netavark added their own error handling in https://salsa.debian.org/debian/netavark/-/commit/6b42eb36ce3c05d17ab88601391e0c9d90be08d6 so this Build-Depends is obsolete. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#1074092: vim: Annoying visual bell in insert mode when pageing after upgrade to trixie
On Sun, Jun 23, 2024 at 08:37:59AM GMT, Helge Kreutzmann wrote: > Up until bookworm no visual bell was shown in vim on the console > with my configuration. Now in insert mode (only), when paging an annoying > visual > bell is shown. > > This is *not* occuring with --clean but from the Debian changes I > could not derive which settings fault it is. I would suggest first comparing the output of ":set" with "vim --clean" and "vim". That should help narrow down which options differ from the defaults and may affect this behavior. > As this is a (minor) regression, I'm reporting this. And if you have > any suggestion how to find out which setting this causes (except for > bisecting) I would be happy :-)) You could bisect your config by placing the "finish" command in your vimrc at various points to see what introduces the behavior. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1073451: wlgreet: FTBFS: unsatisfiable build-dependency: librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed
On Sun, Jun 16, 2024 at 03:17:54PM GMT, Lucas Nussbaum wrote: > Relevant part (hopefully): > > +--+ > > | Install package build dependencies > >| > > +--+ > > > > > > Setup apt archive > > - > > > > Merged Build-Depends: debhelper-compat (= 13), dh-cargo, > > librust-smithay-client-toolkit-dev (>= 0.16.1~), > > librust-smithay-client-toolkit-dev (<< 0.17~), librust-rusttype-dev (>= > > 0.9.2), librust-chrono-dev (>= 0.4), librust-nix-dev (>= 0.15), > > librust-memmap2-dev (>= 0.3), librust-os-pipe-dev (>= 0.8), > > librust-wayland-client-0.29-dev, librust-wayland-protocols-0.29-dev, > > librust-lazy-static-dev (>= 1.4), librust-serde-derive-dev (>= 1.0), > > librust-greetd-ipc+thiserror-dev (>= 0.10), librust-getopts-dev (>= 0.2), > > librust-toml-dev (>= 0.5), pkgconf, dh-exec, build-essential, fakeroot > > Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, > > librust-smithay-client-toolkit-dev (>= 0.16.1~), > > librust-smithay-client-toolkit-dev (<< 0.17~), librust-rusttype-dev (>= > > 0.9.2), librust-chrono-dev (>= 0.4), librust-nix-dev (>= 0.15), > > librust-memmap2-dev (>= 0.3), librust-os-pipe-dev (>= 0.8), > > librust-wayland-client-0.29-dev, librust-wayland-protocols-0.29-dev, > > librust-lazy-static-dev (>= 1.4), librust-serde-derive-dev (>= 1.0), > > librust-greetd-ipc+thiserror-dev (>= 0.10), librust-getopts-dev (>= 0.2), > > librust-toml-dev (>= 0.5), pkgconf, dh-exec, build-essential, fakeroot > > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > > Ign:1 copy:/<>/apt_archive ./ InRelease > > Get:2 copy:/<>/apt_archive ./ Release [615 B] > > Ign:3 copy:/<>/apt_archive ./ Release.gpg > > Get:4 copy:/<>/apt_archive ./ Sources [1129 B] > > Get:5 copy:/<>/apt_archive ./ Packages [1162 B] > > Fetched 2906 B in 0s (0 B/s) > > Reading package lists... > > Reading package lists... > > > > Install main build dependencies (apt-based resolver) > > > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > sbuild-build-depends-main-dummy : Depends: > > librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. I've uploaded rust-smithay-client-toolkit-0.16 to NEW, which will address this until wlgreet can be ported to newer versions. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1072766: rust-alacritty: FTBFS: unsatisfiable build-dependencies
On Fri, Jun 07, 2024 at 05:23:32PM GMT, Santiago Vila wrote: > > [...] > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-copypasta-0.8+wayland-dev > (>= 0.8.1-~~) but it is not installable >Depends: librust-copypasta-0.8+x11-dev (>= > 0.8.1-~~) but it is not installable >Depends: librust-copypasta-0.8-dev (>= > 0.8.1-~~) but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. > E: Package installation failed > Not removing build depends: cloned chroot in use > > I missed this relationship when updating copypasta. Rather than fix this directly in unstable's current alacritty package, I'm going to finish the work to get the version in experimental uploaded to unstable. This will address the issue, since experimental's alacritty uses copypasta 0.10. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1072839: rust-linemux: Upcoming rust-notify transition (5.x -> 6.x)
Source: rust-linemux Version: 0.3.0-5 Severity: normal rust-notify 6.x is in experimental. I plan on uploading it to unstable soon. Upstream made a no-change bump to 6.x, so it looks like debian/control just needs to be adjusted to accept a broader version range. https://github.com/jmagnuson/linemux/pull/68 -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#963688: neovim-qt: please make the build reproducible
On Thu, Jun 06, 2024 at 11:16:10AM -0700, Vagrant Cascadian wrote: > On 2020-06-25, Chris Lamb wrote: > > This is because it embeds the CFLAGS (via CMAKE_CXX_FLAGS) in an > > "About" dialogue, and this environment variable contains the build > > path via -ffile-prefix-map etc. > > This is still relevent, although tests.reproducible-builds.org no longer > tests varied build paths. I've raised the issue with upstream. I'd prefer not to carry a patch, especially if it's not actually affecting reproducible testing. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1070689: transition: msgpack-c
On Tue, Jun 04, 2024 at 06:44:36AM -0400, James McCoy wrote: > On Tue, Jun 04, 2024 at 09:27:28AM +0200, Emilio Pozuelo Monfort wrote: > > On 03/06/2024 03:25, James McCoy wrote: > > > On Sun, Jun 02, 2024 at 07:23:39PM -0400, James McCoy wrote: > > > > I know libdata-messagepack-stream-perl and tmate already have fixes > > > > sitting in the Vcs. The other two are straight forward fixes that I > > > > should be able to NMU in the next couple days. > > > > > > Also, binNMUs should use "--add-depends 'libmsgpack-c-dev (>= 6)'" to > > > ensure they rebuild with the new package. > > > > Can you instead provide a transitional package? That will help with the > > rdeps and especially with the reverse build-depends. Effectively once > > libmsgpack-dev is decrufted, those rdeps will be RC-buggy as they > > build-depend on a virtual package. > > ACK. Will do that ASAP. New msgpack-c with the transitional package is uploaded, as well as fixes for all the rdeps that FTBFS. Just binNMUs should be left. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1070689: transition: msgpack-c
On Tue, Jun 04, 2024 at 09:27:28AM +0200, Emilio Pozuelo Monfort wrote: > On 03/06/2024 03:25, James McCoy wrote: > > On Sun, Jun 02, 2024 at 07:23:39PM -0400, James McCoy wrote: > > > I know libdata-messagepack-stream-perl and tmate already have fixes > > > sitting in the Vcs. The other two are straight forward fixes that I > > > should be able to NMU in the next couple days. > > > > Also, binNMUs should use "--add-depends 'libmsgpack-c-dev (>= 6)'" to > > ensure they rebuild with the new package. > > Can you instead provide a transitional package? That will help with the > rdeps and especially with the reverse build-depends. Effectively once > libmsgpack-dev is decrufted, those rdeps will be RC-buggy as they > build-depend on a virtual package. ACK. Will do that ASAP. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1070689: transition: msgpack-c
On Sun, Jun 02, 2024 at 07:23:39PM -0400, James McCoy wrote: > I know libdata-messagepack-stream-perl and tmate already have fixes > sitting in the Vcs. The other two are straight forward fixes that I > should be able to NMU in the next couple days. Also, binNMUs should use "--add-depends 'libmsgpack-c-dev (>= 6)'" to ensure they rebuild with the new package. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1070689: transition: msgpack-c
On Sun, Jun 02, 2024 at 01:11:06PM +0200, Sebastian Ramacher wrote: > On 2024-05-07 06:26:04 -0400, James McCoy wrote: > > The following build dependencies will need fixes to build against the > > new msgpack-c version: > > > > * libdata-messagepack-stream-perl > > * tmate > > * tmate-ssh-server > > * webdis > > > > This is just related to how the packages detect whether msgpack is > > available, since the APIs/ABIs themselves did not change. > > Assuming that bugs have been filed for those packages, please go ahead. Yes, the bugs were filed and marked as blocking this bug. I've uploaded and upgraded the severity of those bugs to serious. I know libdata-messagepack-stream-perl and tmate already have fixes sitting in the Vcs. The other two are straight forward fixes that I should be able to NMU in the next couple days. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1072117: /usr/bin/keepassxc: KeePassXC stores its .lock/.socket file in /tmp
On Tue, May 28, 2024 at 04:25:54PM -0400, James McCoy wrote: > Especially given the recent change to have automated cleaning of /tmp at > runtime, keepassxc shouldn't be using /tmp to store these files. > > They should probably be under $XDG_RUNTIME_DIR. Until/unless this is resolved upstream, maybe it's a good idea to add a tmpfiles.d drop-in config x /tmp/keepassxc-*.lock x /tmp/keepassxc-*.socket Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1072117: /usr/bin/keepassxc: KeePassXC stores its .lock/.socket file in /tmp
Package: keepassxc-full Version: 2.7.7+dfsg.1-3 Severity: important File: /usr/bin/keepassxc Especially given the recent change to have automated cleaning of /tmp at runtime, keepassxc shouldn't be using /tmp to store these files. They should probably be under $XDG_RUNTIME_DIR. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages keepassxc-full depends on: ii libargon2-1 0~20190702+dfsg-4+b1 ii libbotan-2-19 2.19.4+dfsg-1 ii libc6 2.38-11 ii libgcc-s1 14.1.0-1 ii libminizip1t641:1.3.dfsg+really1.3.1-1 ii libpcsclite1 2.2.3-1 ii libqrencode4 4.1.1-1+b2 ii libqt5concurrent5t64 5.15.13+dfsg-2 ii libqt5core5t645.15.13+dfsg-2 ii libqt5dbus5t645.15.13+dfsg-2 ii libqt5gui5t64 5.15.13+dfsg-2 ii libqt5network5t64 5.15.13+dfsg-2 ii libqt5svg55.15.13-2 ii libqt5widgets5t64 5.15.13+dfsg-2 ii libqt5x11extras5 5.15.13-2 ii libreadline8t64 8.2-4 ii libstdc++614.1.0-1 ii libusb-1.0-0 2:1.0.27-1 ii libx11-6 2:1.8.7-1+b1 ii libxtst6 2:1.2.3-1.1+b1 ii libzxcvbn02.5+dfsg-2 ii zlib1g1:1.3.dfsg+really1.3.1-1 Versions of packages keepassxc-full recommends: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1 Versions of packages keepassxc-full suggests: ii webext-keepassxc-browser 1.9.0.5+repack1-1 ii xclip 0.13-4 -- no debconf information
Bug#1072003: ITP: tree-sitter-markdown -- Markdown parser for tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org Control: block 1071572 by -1 * Package name: tree-sitter-markdown Version : 0.2.3 Upstream Contact: Matthias Deiml * URL : https://github.com/MDeiml/tree-sitter-markdown/ * License : MIT Programming Lang: JavaScript, C, Rust Description : Markdown parser for tree-sitter This package provides a markdown parser for tree-sitter. It's required for the new upstream release of neovim and will be maintained in the tree-sitter team.
Bug#1072002: ITP: tree-sitter-bash -- Bash parser for Tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org Control: block 1071572 by -1 * Package name: tree-sitter-bash Version : 0.21.0 Upstream Contact: Max Brunsfeld * URL : https://github.com/tree-sitter/tree-sitter-bash/ * License : MIT Programming Lang: JavaScript, C, Rust Description : Bash parser for Tree-sitter This package provides a bash parser for tree-sitter. It's required for the new upstream release of neovim and will be maintained in the tree-sitter team.
Bug#1072001: ITP: tree-sitter-python -- Python parser for Tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org Control: block 1071572 by -1 * Package name: tree-sitter-python Version : 0.21.0 Upstream Contact: Max Brunsfeld * URL : https://github.com/tree-sitter/tree-sitter-python/ * License : MIT Programming Lang: JavaScript, C, Rust Description : Python parser for Tree-sitter This package provides a Python 2/3 parser for tree-sitter. It's required for the new upstream release of neovim and will be maintained in the tree-sitter team.
Bug#1070691: tmate-ssh-server: FTBFS with msgpack-c 6.x
Control: tag -1 patch
On Tue, May 07, 2024 at 06:28:00AM -0400, James McCoy wrote:
> tmate-ssh-server FTBFS with the 6.x version of the msgpack C library.
> Upstream renamed the library from libmsgpackc to libmsgpack-c and the
> pkg-config file from msgpack.pc to msgpack-c.pc, so any checks for
> the presence of the library at build time should handle both names.
Attached patch, ported from tmate, enables building against either
version of msgpack-c.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Description: Fix building with msgpack-c 6.x
The msgpack-c project changed the library name from msgpackc to msgpack-c
in the 6.0.0 release. Update configure.ac to detect the library both
pre- and post-rename.
Bug: https://github.com/tmate-io/tmate-ssh-server/issues/108
Forwarded: not-needed
---
--- a/configure.ac
+++ b/configure.ac
@@ -199,7 +199,18 @@ PKG_CHECK_MODULES(
LIBS="$MSGPACK_LIBS $LIBS"
found_msgpack=yes
],
- found_msgpack=no
+ [
+PKG_CHECK_MODULES(
+ MSGPACKC,
+ msgpack-c >= 6.0.0,
+ [
+CPPFLAGS="$MSGPACKC_CFLAGS $CPPFLAGS"
+LIBS="$MSGPACKC_LIBS $LIBS"
+found_msgpack=yes
+ ],
+ found_msgpack=no
+)
+ ]
)
if test "x$found_msgpack" = xno; then
AC_MSG_ERROR("msgpack >= 1.2.0 not found")
Bug#1070689: transition: msgpack-c
Package: release.debian.org Severity: normal X-Debbugs-Cc: msgpac...@packages.debian.org Control: affects -1 + src:msgpack-c User: release.debian@packages.debian.org Usertags: transition The msgpack-c upstream renamed their C library from libmsgpackc.so to libmsgpack-c.so. I've renamed the binary packages accordingly (libmsgpack-dev -> libmsgpack-c-dev, libmsgpackc2 -> libmsgpack-c2) and the former "Provides: libmsgpack-dev" to help ease the transition. The following build dependencies will need fixes to build against the new msgpack-c version: * libdata-messagepack-stream-perl * tmate * tmate-ssh-server * webdis This is just related to how the packages detect whether msgpack is available, since the APIs/ABIs themselves did not change. Ben file: title = "msgpack-c"; is_affected = .depends ~ "libmsgpackc2" | .depends ~ "libmsgpack-c2"; is_good = .depends ~ "libmsgpack-c2"; is_bad = .depends ~ "libmsgpackc2";
Bug#1068927: ITP: rust-event-listener-strategy -- block or poll on event_listener easily
On Sat, Apr 13, 2024 at 04:10:31PM +0200, Jonas Smedegaard wrote: > event-listener-strategy provides a strategy > for using the event-listener crate > in both blocking and non-blocking contexts. Matthias already packaged this and it's sitting in NEW. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1068645: RM: rust-lazy-regex-proc-macros -- ROM; content already present in rust-lazy-regex package
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: rust-lazy-regex-proc-mac...@packages.debian.org Control: affects -1 + src:rust-lazy-regex-proc-macros User: ftp.debian@packages.debian.org Usertags: remove rust-lazy-regex-proc-macros should not have been packaged, since it was already provided by the rust-lazy-regex package.
Bug#1001586: vim-gtk3: GVim sometimes freezes when receiving focus due to switching workspaces on Gnome (Wayland)
On Sun, Dec 12, 2021 at 04:03:21PM +0100, Mladen Mijatov wrote: > GVim will sometimes freeze when switching between workspaces fast and in the > midst of that main window receives focus. Just the interface will freeze but > changes in mouse cursor would indicate that process beneath it is working as > expected. > > Issue is reproducible but it doesn't happen every time making it very annoying > because it will randomly crash working environment causing loss of data. Has this still been an issue? If so, maybe the latest upload (9.1.0199-1) will help, since it has some native wayland support. See ":help gui-wayland". Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1001788: neovim: undoing changes results in a mix of old and new text
On Sat, Jul 16, 2022 at 10:53:01PM -0400, James McCoy wrote: > On Tue, Mar 01, 2022 at 05:45:35PM +0100, Nicolas Évrard wrote: > > * James McCoy [2021-12-17 22:31 +0100]: > > > On Thu, Dec 16, 2021 at 10:28:18AM +0100, Nicolas Évrard wrote: > > > > I am sorry for this bug report because it occurs on some rare occurence > > > > and I > > > > don't have a scenario to reproduce it. Yet it's annoying enough to > > > > deserve a > > > > bug report. Feel free to close it as unreproduceable ;). > > > > > > > > With the arrival of LSP I switched my configuration from ALE to the > > > > builtin LSP > > > > for linting and so on. I made this switch some days after the release > > > > of neovim > > > > 0.5.0 ; since that time I have remarked that sometimes (I'd say 2 or 3 > > > > times a > > > > month), when I undo my changes (not just one press of 'u' multiple > > > > presses), it > > > > results in a mix of old and new changes. > > > > > > There were a number of fixes in the LSP stuff for 0.6.0, so can you let > > > me know if you see this again after upgrading to that? > > > > Hello, > > > > So after a while I thought that it had indeed disappeared but I had it twice > > today :(. It seems to be a problem with the virtual text and treesitter. > > > > Here's a screenshot of the error in action. > > If you encounter this again, can you see if running ":redraw!" fixes it? > That would help confirm whether it's just a display issue or the buffer > is actually in a bad state. Is this something you're still running into? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1067496: Vertical splits no longer delineated by default
On Fri, Mar 22, 2024 at 01:42:41PM +, Josh Triplett wrote: > After upgrading to the new version of neovim, the highlight > `WinSeparator` (which links to `VertSplit`) no longer has any visible > setting by default. In previous versions, there was an inverse-video bar > between windows; now there's only a black bar the same color as normal > text background, which makes the windows blend together. Do you see the same issue if you run "nvim --clean"? Could you include some screenshots to help show what you're seeing? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1066261: lintian: FTBFS: hello.c:9:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration]
Control: tag -1 patch On Wed, Mar 13, 2024 at 12:42:03PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > This is most likely caused by a change in dpkg 1.22.6, that enabled > -Werror=implicit-function-declaration. For more information, see > https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration > > Relevant part (hopefully): > > cc -o strong \ > > -Wdate-time -D_FORTIFY_SOURCE=2 \ > > -g -O2 -Werror=implicit-function-declaration > > -ffile-prefix-map=/<>/debian/test-out/packages/checks/binaries/hardening/binaries-hardening/binaries-hardening-1.0=. > > -fstack-protector-strong -fstack-clash-protection -Wformat > > -Werror=format-security -fcf-protection \ > > -Wl,-z,relro -Wl,-z,now \ > > hello.c > > hello.c: In function 'report': > > hello.c:9:5: error: implicit declaration of function 'strcpy' > > [-Werror=implicit-function-declaration] > > 9 | strcpy(buf, string); > > | ^~ > > hello.c:2:1: note: include '' or provide a declaration of 'strcpy' > > 1 | #include > > +++ |+#include > > 2 | > > hello.c:9:5: warning: incompatible implicit declaration of built-in > > function 'strcpy' [-Wbuiltin-declaration-mismatch] > > 9 | strcpy(buf, string); > > | ^~ > > hello.c:9:5: note: include '' or provide a declaration of 'strcpy' > > cc1: some warnings being treated as errors > > make[2]: *** [Makefile:11: all] Error 1 Attached patch fixes these issues. This is also available as MR!496 on Salsa. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB >From 53dc310d4d5af6b0701d55577b30fb9a7e493bd1 Mon Sep 17 00:00:00 2001 From: James McCoy Date: Fri, 15 Mar 2024 12:31:42 -0400 Subject: [PATCH] t: Fix compilation failures with dpkg 1.22.6 Dpkg 1.22.6 enables -Werror=implicit-function-declaration by default. This causes various compilation failures in the tests, mainly due to missing includes. The remaining failures are due to newer GCC versions defaulting to the C11 standard, which doesn't expose the gets() function anymore. For these tests, explicitly compile with -std=c99 to re-expose the function. Closes: #1066261 Signed-off-by: James McCoy --- .../hardening/binaries-hardening/build-spec/orig/hello.c | 1 + .../binaries/static/binaries-golang/build-spec/orig/Makefile | 2 +- .../build-spec/orig/Makefile | 2 +- .../control-file-golang-built-using/build-spec/orig/Makefile | 2 +- .../built-using/binaries-golang/build-spec/orig/Makefile | 2 +- .../import-path/binaries-golang/build-spec/orig/Makefile | 2 +- .../control-file-golang-built-using/build-spec/orig/Makefile | 2 +- .../build-spec/orig/Makefile | 2 +- .../binaries-embedded-libs/build-spec/orig/hardening-trigger.h | 3 +++ 9 files changed, 11 insertions(+), 7 deletions(-) diff --git a/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c b/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c index 7b87bd737..0ee9099e1 100644 --- a/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c +++ b/t/recipes/checks/binaries/hardening/binaries-hardening/build-spec/orig/hello.c @@ -1,4 +1,5 @@ #include +#include void report(char *string) diff --git a/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile b/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile index f04b342de..66c9d6f3a 100644 --- a/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile +++ b/t/recipes/checks/binaries/static/binaries-golang/build-spec/orig/Makefile @@ -4,7 +4,7 @@ COMPILE:= $(CC) $(NOPIE_CFLAGS) $(CPPFLAGS) $(NOPIE_LDFLAGS) all: # static version - $(COMPILE) -static -o basic.static basic.c + $(COMPILE) -std=c99 -static -o basic.static basic.c install: install -d $(DESTDIR)/usr/lib/foo/ diff --git a/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile b/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile index 6047afb59..900ebadbe 100644 --- a/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile +++ b/t/recipes/checks/debian/control/field/adopted/control-file-golang-xs-go-import-path/build-spec/orig/Makefile @@ -4,7 +4,7 @@ COMPILE:= $(CC) $(NOPIE_CFLAGS) $(CPPFLAGS) $(NOPIE_LDFLAGS) all: # static version - $(COMPILE) -static -o static basic.c + $(COMPILE) -std=c99 -static -o static basic.c clean distclean: rm -f basic diff --git a/t/recipes/checks/debian/control/field/
Bug#1063308: transition: libvterm
On Mon, Mar 04, 2024 at 06:40:46AM -0500, James McCoy wrote: > On Mon, Feb 05, 2024 at 10:54:12PM -0500, James McCoy wrote: > > libvterm doesn't have a stable API/ABI yet, so although the SONAME > > didn't change, this is a breaking update. > > > > There are 3 packages which use libvterm: > > * pangoterm: I've filed #1063196 to RM the package, so it shouldn't > > block > > * emacs-libvterm: It supports building against either 0.1 or 0.3, so it > > just needs a binNMU > > * neovim: 0.7.2 (in unstable) only supports 0.1, but 0.9.5 (in > > experimental) supports 0.3. > > > > Ben file: > > > > title = "libvterm 0.1 -> 0.3"; > > is_affected = .build-depends ~ "libvterm-dev"; > > is_good = .depends ~ /libvterm0 \(>= 0\.[23]/; > > is_bad = .depends ~ /libvterm0 \(>= 0\.1/; > > This was ACKed on IRC, so I've uploaded libvterm and neovim. Now that cmake is available on arm* again, emacs-libvterm just needs a binNMU to finish this transition. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1066075: RM: lua-nvim -- ROM; unused
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: lua-n...@packages.debian.org Control: affects -1 + src:lua-nvim User: ftp.debian@packages.debian.org Usertags: remove The neovim package was the only user of this package (to run tests at build time), but as of the latest neovim upload it is no longer using it.
Bug#1063376: How to ask efficiently for removal of 32 bit architectures of about 40 packages (Was: reverse dependenc)
On Mon, Mar 11, 2024 at 09:12:30PM +0100, Andreas Tille wrote: > Hi, > > Am Mon, Mar 04, 2024 at 06:25:50PM + schrieb Thorsten Alteholz: > > Control: tags -1 + moreinfo > > > > please file one RM bug for each package that needs to be partially removed. > > This needs to be done even for dependencies of dependencies. > > Please remove the moreinfo tag once that is done. > > As Thorsten wrote above[1] every single package needs its own bug to > enable ftpmaster removing the binary packages of 32bit architectures for > about 40 packages (currently affected by testing removals). > > I hope there is some better solution than sending single bug reports > for those packages. Sounds like a use case for devscript's mass-bug(1). Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1065978: Handle listxattr failures better (upstream patch 9.1.0162)
On Sun, Mar 10, 2024 at 05:44:27PM -0400, Paul R. Tagliamonte wrote: > I sent a fix to upstream vim to handle a bug where vim would attempt > to allocate size_t max (for me, 0x aka > 18446744073709551615 bytes) when the filesystem responded with an > error on listxattr other than not supported. > > The upstream patch can be found at > 14759ded57447345ba11c11a99fd84344797862c[1] - I've exported that patch > for inclusion into sid. Thanks! I'll likely refresh against the ~latest upstream once things in the time_t land settle down some, so this will get pulled in then. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1065731: libvterm0: Missing Breaks for rdeps that were built against libvterm 0.1
Package: libvterm0 Version: 0.3.3-2 Severity: serious Justification: Policy 8.6.2 The missing Breaks can allow partial upgrades and therefore break the package, since the ABI changed. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvterm0 depends on: ii libc6 2.37-15.1 libvterm0 recommends no packages. libvterm0 suggests no packages. -- no debconf information
Bug#1063308: transition: libvterm
On Mon, Feb 05, 2024 at 10:54:12PM -0500, James McCoy wrote: > libvterm doesn't have a stable API/ABI yet, so although the SONAME > didn't change, this is a breaking update. > > There are 3 packages which use libvterm: > * pangoterm: I've filed #1063196 to RM the package, so it shouldn't > block > * emacs-libvterm: It supports building against either 0.1 or 0.3, so it > just needs a binNMU > * neovim: 0.7.2 (in unstable) only supports 0.1, but 0.9.5 (in > experimental) supports 0.3. > > Ben file: > > title = "libvterm 0.1 -> 0.3"; > is_affected = .build-depends ~ "libvterm-dev"; > is_good = .depends ~ /libvterm0 \(>= 0\.[23]/; > is_bad = .depends ~ /libvterm0 \(>= 0\.1/; This was ACKed on IRC, so I've uploaded libvterm and neovim. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1064680: subversion: FTBFS: :86:in `require': /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/li
Control: reassign -1 swig/4.2.0-1
Control: affects -1 src:subversion
Control: forwarded -1 https://github.com/swig/swig/issues/2751
Control: retitle -1 SWIG_snprintf not defined for ruby/tcl bindings
On Sun, Feb 25, 2024 at 08:33:47PM +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[3]: Entering directory '/<>'
> > make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make
> > rule.
> > if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in
> > /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby
> > /<>/BUILD/subversion/bindings/swig/ruby/../../../libsvn_*; do
> > if [ -n "$DYLD_LIBRARY_PATH" ]; then
> > LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$d/.libs"; else
> > LD_LIBRARY_PATH="$d/.libs"; fi; done; export LD_LIBRARY_PATH; fi; \
> > cd /<>/BUILD/subversion/bindings/swig/ruby; \
> > check_rb() { \
> > /usr/bin/ruby -I
> > /<>/BUILD/../subversion/bindings/swig/ruby
> > /<>/BUILD/../subversion/bindings/swig/ruby/test/run-test.rb
> > "$@"; \
> > }; \
> > if check_rb --help 2>&1 | grep -q -- --collector; then \
> > check_rb --collector=dir --verbose=normal; \
> > elif [ "3" -eq 1 -a "1" -lt 9 ] ; then \
> > check_rb --verbose=normal; \
> > else \
> > check_rb; \
> > fi
> > :86:in
> > `require':
> > /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/libsvn_swig_ruby-1.so.1:
> > undefined symbol: SWIG_snprintf -
> > /<>/BUILD/subversion/bindings/swig/ruby/.ext/svn/ext/core.so
> > (LoadError)
This is a bug in the bindings generated by SWIG, which is fixed in 4.2.1
but not yet uploaded. Reassigning.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1062674: lua-compat53: NMU diff for 64-bit time_t transition
On Fri, Feb 02, 2024 at 04:18:01PM +, Graham Inggs wrote: > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if information > becomes available that your package should not be included in the transition, > there is time for us to amend the planned uploads. The 53 in lua-compat53 isn't related to the ABI. This Lua module provides a Lua 5.3 API surface that can be used in previous Lua versions. Lua module packages aren't generally named according to the SONAME (for reasons I'm not clear on). Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1063308: transition: libvterm
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: libvt...@packages.debian.org Control: affects -1 + src:libvterm libvterm doesn't have a stable API/ABI yet, so although the SONAME didn't change, this is a breaking update. There are 3 packages which use libvterm: * pangoterm: I've filed #1063196 to RM the package, so it shouldn't block * emacs-libvterm: It supports building against either 0.1 or 0.3, so it just needs a binNMU * neovim: 0.7.2 (in unstable) only supports 0.1, but 0.9.5 (in experimental) supports 0.3. Ben file: title = "libvterm 0.1 -> 0.3"; is_affected = .build-depends ~ "libvterm-dev"; is_good = .depends ~ /libvterm0 \(>= 0\.[23]/; is_bad = .depends ~ /libvterm0 \(>= 0\.1/;
Bug#1061565: nmu: rust-alacritty_0.12.2-2
On Fri, Jan 26, 2024 at 10:16:50AM -0500, James McCoy wrote: > nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against > rust-smithay-client-toolkit 0.16.1" > > This is needed to fix #1061563 (crash with recent sway versions). Ping? It'd be nice to get this fixed, since other things are blocking an update of alacritty. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1063254: lua-luv: identified for time_t transition but no ABI in shlibs
On Mon, Feb 05, 2024 at 01:38:47PM -0800, Steve Langasek wrote: > However, lua-luv's shlibs file declares a dependency on a library package > name that contains no ABI information: > > $ cat DEBIAN/shlibs > liblua5.1-luv 0 lua-luv (>= 1.44.2-0) > liblua5.2-luv 0 lua-luv (>= 1.44.2-0) > liblua5.3-luv 0 lua-luv (>= 1.44.2-0) > liblua5.4-luv 0 lua-luv (>= 1.44.2-0) > $ > > It is therefore not obvious that we should rename the package to > 'lua-luvt64' as part of this transition. This is how most, if not all, of the lua modules are packaged. I see that lua-compat53 was renamed to lua-compat53t64, but the 53 isn't anything ABI related. The package is named that because it's providing a Lua 5.3-compatible API that can be used in Lua versions prior to 5.3. I'm not sure why Lua modules are packaged this way, but any "obvious" renamings of lua packages on your list are probably misleading. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1063196: RM: pangoterm -- ROM; low popcon, legacy toolkit
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: pangot...@packages.debian.org Control: affects -1 + src:pangoterm Pangoterm was initially packaged mainly to test out libvterm. It doesn't provide any particularly unique functionality, and receives little maintenance upstream. Since we have plenty of terminal emulators in Debian, and other packages using libvterm, I'm requesting removal of pangoterm.
Bug#1052020: rust-tree-sitter: enters infinite loop in certain scenarios
On Tue, Jan 30, 2024 at 06:10:43PM +0100, Jonas Smedegaard wrote: > Control: retitle -1 tree-sitter: enters infinite loop in certain scenarios > Control: notfound -1 0.20.9 > > Quoting Jonas Smedegaard (2023-09-16 09:07:24) > > - From accepted MR https://github.com/tree-sitter/tree-sitter/pull/2429: > > > `earlier_node` must be reset when backtracking up the tree or else > > > `ts_node__prev_child` may loop infinitely on a subtree which contains > > > zero-width tokens. > > > > Please consider cherry-picking that MR until a new upstream release > > comes out. > > Upstream has now issued a release with the bugfix included. And they caused a bit of chaos by no longer installing parser.h as part of the C library. This is going to have effects on the crates and currently packaged grammars. I'll try to get coordinated uploads of those done, as I have time and figure out how to best fix the fallout. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1061626: dials: Switch libmsgpack-dev to libmsgpack-cxx-dev
Source: dials Version: 3.17.0+dfsg3-1 Severity: normal Tags: patch Control: block 1018679 by -1 Dear maintainer, libmsgpack-dev's C++ bindings were split out to a separate binary package -- libmsgpack-cxx-dev -- in 4.1.1-1 to follow upstream's separation of the project. dials Build-Depends on libmsgpack-dev and uses the C++ library, so it needs to switch to libmsgpack-cxx-dev. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1061623: rocblas: Switch libmsgpack-dev to libmsgpack-cxx-dev
Source: rocblas Version: 5.5.1+dfsg-3 Severity: normal Tags: patch Control: block 1018679 by -1 Dear maintainer, libmsgpack-dev's C++ bindings were split out to a separate binary package -- libmsgpack-cxx-dev -- in 4.1.1-1 to follow upstream's separation of the project. rocblas Build-Depends on libmsgpack-dev and uses the C++ library, so it needs to switch to libmsgpack-cxx-dev. The pending 6.x version of msgpack-cxx (currently in experimental) also changed the CMake config name to msgpack-cxx. This has been accounted for upstream. I've attached a patch which addresses both of these points. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.6.13-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diffstat for rocblas-5.5.1+dfsg rocblas-5.5.1+dfsg control|2 - patches/0020-msgpack-names.patch | 22 patches/0021-msgpack-cxx-support.patch | 35 + patches/series |2 + 5 files changed, 67 insertions(+), 1 deletion(-) diff -Nru rocblas-5.5.1+dfsg/debian/control rocblas-5.5.1+dfsg/debian/control --- rocblas-5.5.1+dfsg/debian/control 2023-09-19 04:28:14.0 -0400 +++ rocblas-5.5.1+dfsg/debian/control 2024-01-27 09:04:18.0 -0500 @@ -21,7 +21,7 @@ rocminfo, patchelf, rocm-cmake (>= 5.3.0), - libmsgpack-dev, + libmsgpack-cxx-dev, libblas-dev, libgtest-dev Build-Depends-Indep: dh-sequence-sphinxdoc , diff -Nru rocblas-5.5.1+dfsg/debian/patches/0020-msgpack-names.patch rocblas-5.5.1+dfsg/debian/patches/0020-msgpack-names.patch --- rocblas-5.5.1+dfsg/debian/patches/0020-msgpack-names.patch 1969-12-31 19:00:00.0 -0500 +++ rocblas-5.5.1+dfsg/debian/patches/0020-msgpack-names.patch 2024-01-27 09:04:20.0 -0500 @@ -0,0 +1,22 @@ +From c1fa5b358d8cbe601754ef5ea4b695d895a34f62 Mon Sep 17 00:00:00 2001 +From: Torre Zuk <42548444+torre...@users.noreply.github.com> +Date: Tue, 28 Nov 2023 09:02:43 -0700 +Subject: [PATCH] fix for newer windows vcpkg msgpack (#1827) + +--- + Tensile/Source/lib/CMakeLists.txt | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/Tensile/Source/lib/CMakeLists.txt b/Tensile/Source/lib/CMakeLists.txt +index f8cc527c83..d3f4b697fb 100644 +--- a/tensile/Tensile/Source/lib/CMakeLists.txt b/tensile/Tensile/Source/lib/CMakeLists.txt +@@ -98,7 +98,7 @@ if(TENSILE_USE_LLVM OR TENSILE_USE_MSGPACK) + endif() + + if(TENSILE_USE_MSGPACK) +-find_package(msgpack REQUIRED) ++find_package(msgpack REQUIRED NAMES msgpack msgpack-c) + target_compile_definitions(TensileHost PUBLIC -DTENSILE_MSGPACK=1) + + if(TARGET msgpackc-cxx) diff -Nru rocblas-5.5.1+dfsg/debian/patches/0021-msgpack-cxx-support.patch rocblas-5.5.1+dfsg/debian/patches/0021-msgpack-cxx-support.patch --- rocblas-5.5.1+dfsg/debian/patches/0021-msgpack-cxx-support.patch 1969-12-31 19:00:00.0 -0500 +++ rocblas-5.5.1+dfsg/debian/patches/0021-msgpack-cxx-support.patch 2024-01-27 09:04:20.0 -0500 @@ -0,0 +1,35 @@ +From 0d942a6a8bfa8557171716dbcc1236adc806c9c5 Mon Sep 17 00:00:00 2001 +From: Torre Zuk <42548444+torre...@users.noreply.github.com> +Date: Wed, 6 Dec 2023 13:14:49 -0700 +Subject: [PATCH] another vcpkg version package name fix (#1836) + +* more vcpkg package options + +- + +Co-authored-by: Zuk +--- + Tensile/Source/lib/CMakeLists.txt | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/Tensile/Source/lib/CMakeLists.txt b/Tensile/Source/lib/CMakeLists.txt +index d3f4b697fb..3fa647d6ec 100644 +--- a/tensile/Tensile/Source/lib/CMakeLists.txt b/tensile/Tensile/Source/lib/CMakeLists.txt +@@ -98,13 +98,15 @@ if(TENSILE_USE_LLVM OR TENSILE_USE_MSGPACK) + endif() + + if(TENSILE_USE_MSGPACK) +-find_package(msgpack REQUIRED NAMES msgpack msgpack-c) ++find_package(msgpack REQUIRED NAMES msgpack msgpack-cxx msgpack-c) + target_compile_definitions(TensileHost PUBLIC -DTENSILE_MSGPACK=1) + + if(TARGET msgpackc-cxx) + get_target_property(msgpack_inc msgpackc-cxx INTERFACE_INCLUDE_DIRECTORIES) + elseif(TARGET msgpackc) + get_target_property(msgpack_inc msgpackc INTERFACE_INCLUDE_DIRECTORIES) ++elseif(TARGET msgpack-cxx) ++get_target_property(msgpack_inc msgpack-cxx INTERFACE_INCLUDE_DIRECTORIES) + endif() + + if(DEFINED msgpack_inc) diff -Nru rocblas-5.5.1+dfsg/debian/patches/series rocblas-5.5.1+dfsg/debian/patches/series --- rocblas-5.5.1+dfsg/debian/patches/series
Bug#1061565: nmu: rust-alacritty_0.12.2-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: rust-alacri...@packages.debian.org Control: affects -1 + src:rust-alacritty nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against rust-smithay-client-toolkit 0.16.1" This is needed to fix #1061563 (crash with recent sway versions).
Bug#1061563: alacritty: Crashes on sway (trixie)
On Fri, Jan 26, 2024 at 02:17:18PM +, Martin Bruset Solberg wrote: >* What led up to the situation? Upgrading sway to latest (from >trixie) >* What exactly did you do (or not do) that was effective (or > ineffective)? Start the app >* What was the outcome of this action? App freezes on startup >* What outcome did you expect instead? App starting > > App freezes on startup, throws: interface 'wl_surface' has no event 2 > > According to https://github.com/alacritty/alacritty/issues/7350, 0.12.3 > is needed to run on trixie sway. Nothing actually changed in that version of alacritty except that some dependencies were updated. The update of smithay-client-toolkit from 0.16.0 to 0.16.1 is the relevant change and we already have 0.16.1 sctk packaged. I'll see about getting a binNMU triggered for alacritty, which should address this. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1061497: msgpack-cxx: Please update to 6.1.0
On Thu, Jan 25, 2024 at 03:49:37PM +0100, Stephan Lachnit wrote: > would it be possible to upload msgpack 6.1.0 to Debian unstable soon? It would > be nice to have the v6 API in Ubuntu 24.04 LTS, for which the import freeze is > on the 29th February. Currently, this would break a number of packages. The reverse dependencies need to be updated to deal with both the msgpack-c / msgpack-cxx split (which most have) and also to deal with the CMake config renames that upstream did. The former is tracked by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018679 and looks like it's almost done. I should raise the severity of the blocking issues and double check others haven't crept in since I initially filed that. Another round of checks is also needed to see what the impact is for the CMake config rename. I'll look into creating a tracking bug for that and try to get some traction. > I can also upload it as NMU if you want. Please don't. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1061154: neovim: Enable luajit on arm64
On Fri, Jan 19, 2024 at 04:50:07PM +, Michael Fladischer wrote: > please enable luajit on arm64. > I did a test-build on my arm64 machine and it worked as expected with luajit > enabled. Thanks for testing. I know although LuaJIT was available on arm64 before, it didn't actually work well. Looks like the recent update may have resolved those issues. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1060697: ITP: rust-wayland-protocols-plasma -- Generated API for the Plasma wayland protocol extensions
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-wayland-protocols-plasma Version : 0.2.0 Upstream Contact: Elinor Berger * URL : https://github.com/smithay/wayland-rs * License : MIT Programming Lang: Rust Description : Generated API for the Plasma wayland protocol extensions This is a dependency of the new version of winit and will be maintained in the pkg-rust repo.
Bug#1060382: ITP: rust-xkbcommon-dl -- Dynamically loaded xkbcommon and xkbcommon-x11 Rust bindings
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-xkbcommon-dl Version : 0.4.1 Upstream Contact: Kirill Chibisov * URL : https://github.com/rust-windowing/xkbcommon-dl * License : MIT Programming Lang: Rust Description : Dynamically loaded xkbcommon and xkbcommon-x11 Rust bindings This is a dependency for the new version of rust-winit and will be maintained in the pkg-rust repo.
Bug#1060366: gnupg2: gnupg Recommands should use source:Version
Source: gnupg2
Version: 2.2.40-1.1
Severity: normal
Various Arch: any packages in src:gnupg2 Recommends: gnupg (=
${binary:Version}).
However, gnupg is an Arch: all package, so the relationship should use
"(= ${source:Version})" to play nicely with binNMUs.
Currently, "apt upgrade" won't update the gnupg packages but "apt
full-upgrade" will, because of this.
$ sudo apt upgrade -o Debug::pkgDepCache::Marker=true
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
MarkInstall gpg:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb > FU=0
gpg:amd64 Recommends on gnupg:amd64 < 2.2.40-1.1 @ii mK > (= 2.2.40-1.1+b1)
can't be satisfied! (dep)
MarkInstall gpg-wks-server:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb >
FU=0
gpg-wks-server:amd64 Recommends on gnupg:amd64 < 2.2.40-1.1 @ii mK > (=
2.2.40-1.1+b1) can't be satisfied! (dep)
MarkInstall gpg-agent:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb > FU=0
gpg-agent:amd64 Recommends on gnupg:amd64 < 2.2.40-1.1 @ii mK > (=
2.2.40-1.1+b1) can't be satisfied! (dep)
MarkInstall gpgsm:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb > FU=0
gpgsm:amd64 Recommends on gnupg:amd64 < 2.2.40-1.1 @ii mK > (=
2.2.40-1.1+b1) can't be satisfied! (dep)
MarkInstall dirmngr:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb > FU=0
dirmngr:amd64 Recommends on gnupg:amd64 < 2.2.40-1.1 @ii mK > (=
2.2.40-1.1+b1) can't be satisfied! (dep)
MarkInstall gpg-wks-client:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb >
FU=0
gpg-wks-client:amd64 Recommends on gnupg:amd64 < 2.2.40-1.1 @ii mK > (=
2.2.40-1.1+b1) can't be satisfied! (dep)
MarkKeep gpg:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU IPb > FU=0
MarkKeep gpgconf:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU > FU=0
MarkKeep gpg-agent:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU Ib > FU=0
MarkKeep gpgsm:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU Ib > FU=0
MarkKeep dirmngr:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU Ib > FU=0
MarkKeep gpg-wks-client:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU Ib > FU=0
MarkKeep gpg-wks-server:amd64 < 2.2.40-1.1 -> 2.2.40-1.1+b1 @ii umU Ib > FU=0
Calculating upgrade... Done
The following packages have been kept back:
dirmngr gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
$ sudo apt -V full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
dirmngr (2.2.40-1.1 => 2.2.40-1.1+b1)
gpg (2.2.40-1.1 => 2.2.40-1.1+b1)
gpg-agent (2.2.40-1.1 => 2.2.40-1.1+b1)
gpg-wks-client (2.2.40-1.1 => 2.2.40-1.1+b1)
gpg-wks-server (2.2.40-1.1 => 2.2.40-1.1+b1)
gpgconf (2.2.40-1.1 => 2.2.40-1.1+b1)
gpgsm (2.2.40-1.1 => 2.2.40-1.1+b1)
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,748 kB of archives.
After this operation, 31.7 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.6.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Bug#1059803: ITP: rust-xkeysym -- X11 keyboard symbol utilities for Rust
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-xkeysym Version : 0.2.0 Upstream Contact: John Nunley * URL : https://github.com/notgull/xkeysym * License : MIT or Apache-2.0 or Zlib Programming Lang: Rust Description : X11 keyboard symbol utilities for Rust This package is a dependency of the new smithay-client-toolkit release and will be maintained in the pkg-rust repo.
Bug#1059800: ITP: rust-wayland-protocols-wlr -- Generated API for the WLR wayland protocol extensions
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-wayland-protocols-wlr Version : 0.2.0 Upstream Contact: Elinor Berger * URL : https://github.com/smithay/wayland-rs * License : MIT Programming Lang: Rust Description : Generated API for the WLR wayland protocol extensions This a new dependency for the next version of smithay-client-toolkit and will be maintained in the pkg-rust repo.
Bug#1059798: ITP: rust-wayland-csd-frame -- rust interface for wayland client side decorations (CSD)
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-wayland-csd-frame Version : 0.3.0 Upstream Contact: Kirill Chibisov * URL : https://github.com/rust-windowing/wayland-csd-frame * License : MIT Programming Lang: Rust Description : rust interface for wayland client side decorations (CSD) This package is a dependency of the new smithay-client-toolkit release and will be maintained in the pkg-rust repo.
Bug#1059774: ITP: rust-as-raw-xcb-connection -- rust trait to interop with libxcb C API
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-as-raw-xcb-connection Version : 1.0.1 Upstream Contact: Uli Schlachter * URL : https://github.com/psychon/as-raw-xcb-connection * License : MIT or Apache-2.0 Programming Lang: Rust Description : rust trait to interop with libxcb C API This is needed for the new upstream release of x11rb and will be maintained in the pkg-rust team.
Bug#1059681: ITP: rust-calloop-wayland-source -- wayland-rs client event source for callloop
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-calloop-wayland-source Version : 0.2.0 Upstream Contact: Kirill Chibisov * URL : https://github.com/smithay/calloop-wayland-source * License : MIT Programming Lang: Rust Description : wayland-rs client event source for callloop This is needed for the new rust-smithay-client-toolkit release and will be maintained in the pkg-rust team.
Bug#1059470: ITP: rust-rustix-openpty -- safe rust bindings to "openpty" and related functions
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: rust-rustix-openpty Version : 0.1.1 Upstream Contact: Dan Gohman * URL : https://github.com/sunfishcode/rustix-openpty * License : Apache-2.0 with LLVM exception or Apache-2.0 or MIT Programming Lang: Rust Description : safe rust bindings to "openpty" and related functions This is a new dependency for the next alacritty release.
Bug#1058467: E575: viminfo: Illegal starting char in line: ¢<94><94>/()/g
On Tue, Dec 12, 2023 at 03:00:51PM +0100, y...@vienna.at wrote: >* What exactly did you do > Starting vim > > (or not do) > not using nano? > > that was effective (or > ineffective)? > Starting was enough > >* What was the outcome of this action? > the srring I sent > >* What outcome did you expect instead? > No nonsence Something got your viminfo file into an unexpected state, which Vim is warning you about. If you want, you can send the file to me so I can see if this is potentially something Vim did. Otherwise, there's not much to do about this bug report. Vim is behaving as expected when it encounters a malformed viminfo file. You can delete the file so a new one is created or remove that specific line. The viminfo file isn't critical to Vim's functioning. It just stores certain state (command history, buffer history, etc) across Vim runs. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1052045: ITP: rust-ed25519-dalek -- fast and efficient ed25519 EdDSA key handling
On Sat, Sep 16, 2023 at 04:09:20PM +0200, Jonas Smedegaard wrote: > * Package name: rust-ed25519-dalek > Version : 2.0.0 I notice that the package currently in NEW uses a source package version of 4+20231122+dfsg-2. This also leaks into the versioning of the binary packages: librust-curve25519-dalek-derive-dev (0.1.1+4+20231122+dfsg-2) Provides "librust-curve25519-dalek-derive-0.1+default-dev (= 0.1.1+4+20231122+dfsg-2)". What's the reasoning for this versioning format? When packaging a workspace, does the crate with the highest version get used as the basis for the source package versioning? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1056498: python-pynvim's autopkg tests fail with Python 3.12
On Wed, Nov 22, 2023 at 03:46:46PM +0100, Matthias Klose wrote: > python-pynvim's autopkg tests fail with Python 3.12: > > [...] > 400s autopkgtest [18:50:54]: test python3-pynvim: [--- > 401s ImportError while loading conftest > '/tmp/autopkgtest.jZbwTr/autopkgtest_tmp/test/conftest.py'. > 401s test/conftest.py:6: in > 401s import pynvim > 401s /usr/lib/python3/dist-packages/pynvim/__init__.py:9: in > 401s from pynvim.api import Nvim, NvimError > 401s /usr/lib/python3/dist-packages/pynvim/api/__init__.py:7: in > 401s from pynvim.api.buffer import Buffer > 401s /usr/lib/python3/dist-packages/pynvim/api/buffer.py:2: in > 401s from pynvim.api.common import Remote > 401s /usr/lib/python3/dist-packages/pynvim/api/common.py:6: in > 401s from pynvim.compat import unicode_errors_default > 401s /usr/lib/python3/dist-packages/pynvim/compat.py:5: in > 401s from imp import find_module as original_find_module > 401s E ModuleNotFoundError: No module named 'imp' I can backport some patches to fix that, but then it will be blocked because python-greenlet doesn't support 3.12 yet (#1055498). While waiting for greenlet, I'll poke upstream to see if they can get a new pynvim release out so backports aren't needed. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1056703: RM: rust-cache-padded -- ROM; Unmaintained upstream, replaced by rust-crossbeam-utils
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-cache-pad...@packages.debian.org Control: affects -1 + src:rust-cache-padded Please remove rust-cache-padded, since it's been deprecated in favor of rust-crossbeam-utils, as described in #1025488.
Bug#1056602: RM: rust-boxfnonce -- ROM; Unmaintained upstream, no more rdeps
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-boxfno...@packages.debian.org Control: affects -1 + src:rust-boxfnonce Please remove rust-boxfnonce. It's unmaintained upstream, as described in #104. There are no more reverse dependencies. Cheers
Bug#1028432: debcargo patch to build with clap 4.
On Tue, Jan 10, 2023 at 10:32:04PM +, Peter Michael Green wrote: > Package: rust-debcargo > > I've attached a patch which makes debcargo build with clap 4, debcargo > builds and it's cargo tests run succesfully, but I haven't actually done any > testing of the command line interface with this patch. debcargo was updated to clap 4 via https://salsa.debian.org/rust-team/debcargo/-/merge_requests/54. This is part of the 2.6.1 release. Debian package still needs to be updated, though. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1015936: notmuch-vim: remove strict dependency on vim-addon-manager(1) and migrate to dh_vim-addon(1)
Control: tags -1 + patch
On Sun, Jul 24, 2022 at 02:43:29PM +0300, guriev...@ya.ru wrote:
> The Vim team decided to declare vim-addon-manager(1) deprecated. Please
> remove the vim-addon-manager package from the Depends list. We advise to
> switch to modern dh_vim-addon(1) if you use Debhelper.
Attached patch implements this.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
>From e036a14aea3a4da8e254779cf85a9accfe275a59 Mon Sep 17 00:00:00 2001
From: James McCoy
Date: Wed, 8 Nov 2023 18:29:00 -0500
Subject: [PATCH] Convert notmuch-vim to Vim addon policy 2.0
The new Vim addon policy relies on Vim's native package functionality,
rather than the Debian-specific vim-addons tool. This allows the addon
to be immediately available when the package is installed, rather than
requiring extra setup by the user.
* Install notmuch-vim to its own /usr/share/notmuch-vim directory, so
the files are self-contained.
* Remove vim-addon-manager from notmuch-vim Depends
* Add ${vim-addon:Depends} to notmuch-vim Depends to ensure it has the
required relationships on Vim/Neovim.
* Build-Depend on dh-sequence-vim-addon to automatically setup the
required symlinks for Vim and Neovim to see the addon.
Signed-off-by: James McCoy
---
debian/control | 3 ++-
debian/notmuch-vim.dirs | 4
debian/notmuch-vim.install | 5 +
debian/notmuch-vim.neovim-addon | 1 +
debian/notmuch-vim.vim-addon| 1 +
debian/rules| 1 +
6 files changed, 6 insertions(+), 9 deletions(-)
delete mode 100644 debian/notmuch-vim.dirs
create mode 12 debian/notmuch-vim.neovim-addon
create mode 100644 debian/notmuch-vim.vim-addon
diff --git a/debian/control b/debian/control
index 135eb7ce..1866247a 100644
--- a/debian/control
+++ b/debian/control
@@ -14,6 +14,7 @@ Build-Depends:
debhelper-compat (= 13),
dh-elpa (>= 1.3),
dh-python,
+ dh-sequence-vim-addon,
desktop-file-utils,
doxygen,
dpkg-dev (>= 1.17.14),
@@ -208,9 +209,9 @@ Replaces:
Depends:
notmuch,
ruby-notmuch,
- vim-addon-manager,
vim-ruby,
${misc:Depends},
+ ${vim-addon:Depends},
Recommends:
ruby-mail,
Description: thread-based email index, search and tagging (vim interface)
diff --git a/debian/notmuch-vim.dirs b/debian/notmuch-vim.dirs
deleted file mode 100644
index 2b531314..
--- a/debian/notmuch-vim.dirs
+++ /dev/null
@@ -1,4 +0,0 @@
-usr/share/vim/addons/doc
-usr/share/vim/addons/plugin
-usr/share/vim/addons/syntax
-usr/share/vim/registry
diff --git a/debian/notmuch-vim.install b/debian/notmuch-vim.install
index cf898738..08096d37 100644
--- a/debian/notmuch-vim.install
+++ b/debian/notmuch-vim.install
@@ -1,4 +1 @@
-vim/notmuch.txt usr/share/vim/addons/doc
-vim/notmuch.vim usr/share/vim/addons/plugin
-vim/notmuch.yaml usr/share/vim/registry
-vim/syntax/notmuch-*.vim usr/share/vim/addons/syntax
+/usr/share/notmuch-vim
diff --git a/debian/notmuch-vim.neovim-addon b/debian/notmuch-vim.neovim-addon
new file mode 12
index ..a576db7c
--- /dev/null
+++ b/debian/notmuch-vim.neovim-addon
@@ -0,0 +1 @@
+notmuch-vim.vim-addon
\ No newline at end of file
diff --git a/debian/notmuch-vim.vim-addon b/debian/notmuch-vim.vim-addon
new file mode 100644
index ..9c23ba18
--- /dev/null
+++ b/debian/notmuch-vim.vim-addon
@@ -0,0 +1 @@
+/usr/share/notmuch-vim notmuch
diff --git a/debian/rules b/debian/rules
index a77ffa15..ecf09abc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -37,4 +37,5 @@ override_dh_auto_install:
PYBUILD_NAME=notmuch dh_auto_install --buildsystem=pybuild --sourcedirectory bindings/python
PYBUILD_NAME=notmuch2 dh_auto_install --buildsystem=pybuild --sourcedirectory bindings/python-cffi
$(MAKE) -C contrib/notmuch-mutt DESTDIR=$(CURDIR)/debian/tmp install
+ $(MAKE) -C vim prefix=/usr/share/notmuch-vim DESTDIR=$(CURDIR)/debian/tmp install
dh_auto_install --sourcedirectory bindings/ruby
--
2.42.0
Bug#1055623: ruby-neovim: Please Provide vim-ruby
Package: ruby-neovim Version: 0.9.1-2 Severity: wishlist Vim has various language interfaces and Provides a vim- for the binary packages that support the respective languages. Since neovim externalized that to providers, it's helpful for neovim users if the external providers Provide the vim- name (c.f, python3-pynvim Provides: vim-python3). -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ruby-neovim depends on: ii neovim 0.7.2-8 ii ruby 1:3.1 pn ruby-msgpack pn ruby-multi-json ruby-neovim recommends no packages. ruby-neovim suggests no packages.
Bug#1055347: ITA: kitty -- fast, featureful, GPU based terminal
On Tue, Nov 07, 2023 at 10:35:56PM +0530, Nilesh Patra wrote: > There's a patch in[1] that gets things moving. > > @James: Since you agreed to maintain this package as I offer my help for > the go stuff, do you think it makes sense to convert this into an RFH > instead of RFA/ITA? That offer was in the absence of someone else willing to take over primary maintenance. If Maytham is willing to do that, then maybe Mytham can work with you to maintain it going forward? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1037440: kitty: Integrating golang parts of the package
Switched to the "New upstream" bug, since that seems more relevant. On Sun, Nov 05, 2023 at 02:09:20AM +0530, Nilesh Patra wrote: > On Sat, Nov 04, 2023 at 02:25:47PM -0400, James McCoy wrote: > > We can try that for the now, but it would probably be good for someone > > else to eventually take over primary maintenance of the package. > > > > https://salsa.debian.org/debian/kitty/-/merge_requests/3 is what I have > > so far for the new upstream version. Feel free to hack around with > > that. > > Cool. I have one question though: how do you sync the repo to new > upstream? It does not seem to use gbp layout so wanted to know how > exactly you're tracking/pulling the commits? I just merge the upstream tags directly and use “git deborig” to produce the orig tarball (c.f. dgit-maint-merge(7)). > OTOH, I did take a look at the errors and I see two ways. Either patch > out all the go build related code and use debian's go build toolchain > (which takes care of a bunch of things) or hack around the way upstream > builds to somehow fit out usecase (this is consuming quite some cycles). > Definitely complicated since a bunch of different functionalities have > been mixed with different languages. The former is fine with me. I took a quick look at what Fedora is doing, and it looks like they just patch setup.py to return from build_static_kittens() just before the “go build -v” line. Adding a patch for that and then adapting the rest of the Debian side of the build to do it seems reasonable. This sounds like the packaging will be carrying around a patch for a while, so I would normally switch to dgit-maint-debrebase(7) here. However, maybe it's better to align with gbp if that's what you're more comfortable with. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1055347: RFA: kitty -- fast, featureful, GPU based terminal emulator
On Sat, Nov 04, 2023 at 11:36:21PM +0530, Nilesh Patra wrote: > Hi, > > On Sat, Nov 04, 2023 at 12:23:34PM -0400, James McCoy wrote: > > Package: wnpp > > Severity: normal > > X-Debbugs-Cc: ki...@packages.debian.org, debian-de...@lists.debian.org > > Control: affects -1 + src:kitty > > > > I request an adopter for the kitty package. I no longer use the package > > and don't have time to figure out how to deal with the new golang parts > > of the package. > > If you could commit to maintaining the overall package as such, I am offer > my help with the golang parts. We can try that for the now, but it would probably be good for someone else to eventually take over primary maintenance of the package. https://salsa.debian.org/debian/kitty/-/merge_requests/3 is what I have so far for the new upstream version. Feel free to hack around with that. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1037440: kitty: New upstream release
Control: block 1037440 by 1055347 On Mon, Jun 12, 2023 at 06:15:23PM -0400, James McCoy wrote: > Filing this to track new packages/package updates which are blocking an > update of kitty. All the dependencies are now packaged (as of kitty 0.30.1), but I don't have the time to figure out how to integrate the golang aspects into the build. The package is now up for adoption -- #1055347. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1055347: RFA: kitty -- fast, featureful, GPU based terminal emulator
Package: wnpp Severity: normal X-Debbugs-Cc: ki...@packages.debian.org, debian-de...@lists.debian.org Control: affects -1 + src:kitty I request an adopter for the kitty package. I no longer use the package and don't have time to figure out how to deal with the new golang parts of the package. The package description is: Kitty supports modern terminal features like: graphics, unicode, true-color, OpenType ligatures, mouse protocol, focus tracking, and bracketed paste. . Kitty has a framework for "kittens", small terminal programs that can be used to extend its functionality.
Bug#1053481: libdpkg-perl: dpkg-source fails to generate (complete) Testsuite-Triggers if test deps have :native qualifier
On Thu, Oct 26, 2023 at 01:10:46PM +0200, Guillem Jover wrote:
> On Wed, 2023-10-25 at 20:44:26 -0400, James McCoy wrote:
> > diff --git i/scripts/Dpkg/Deps/Simple.pm w/scripts/Dpkg/Deps/Simple.pm
> > index 431c93bb9..da7aedbd8 100644
> > --- i/scripts/Dpkg/Deps/Simple.pm
> > +++ w/scripts/Dpkg/Deps/Simple.pm
> > @@ -194,7 +194,6 @@ sub parse_string {
> >\s*$ # trailing spaces at end
> > }x;
> > if (defined $2) {
> > -return if $2 eq 'native' and not $self->{build_dep};
> > $self->{archqual} = $2;
> > }
> > $self->{package} = $1;
>
> …this would remove the check for run-time dependencies. What I had in
> mind was something like the attached patch, which I'll queue once I've
> updated the test suite to cope or to add unit tests.
Thanks! I'm looking to add a lot more arch-qualified test depends, so I
appreciate the effort.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1054565: RFP: golang-github-zeebo-xxh3 -- XXH3 algorithm in Go
Package: wnpp Severity: wishlist Control: block 1037440 by -1 * Package name: golang-github-zeebo-xxh3 Version : 1.0.2-1 Upstream Author : Jeff Wendling * URL : https://github.com/zeebo/xxh3 * License : BSD-2-clause Programming Lang: Go Description : XXH3 algorithm in Go XXH3 . GoDoc (https://godoc.org/github.com/zeebo/xxh3) Sourcegraph (https://sourcegraph.com/github.com/zeebo/xxh3?badge) Go Report Card (https://goreportcard.com/report/github.com/zeebo/xxh3) . This package is a port of the xxh3 (https://github.com/Cyan4973/xxHash) library to Go. . Upstream has fixed the output as of v0.8.0, and this package matches that. This is needed to package a new upstream version of kitty. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1053481: libdpkg-perl: dpkg-source fails to generate (complete) Testsuite-Triggers if test deps have :native qualifier
On Thu, Oct 05, 2023 at 07:11:32AM +0200, Guillem Jover wrote:
> Right, nice catch! Given that these fields are based on what might
> appear on build dependencies, I think it does make sense to consider
> them an overlay on top of those. So I'll make them allow anything that
> is allowed for build dependencies.
Would that just be the below patch?
diff --git i/scripts/Dpkg/Deps/Simple.pm w/scripts/Dpkg/Deps/Simple.pm
index 431c93bb9..da7aedbd8 100644
--- i/scripts/Dpkg/Deps/Simple.pm
+++ w/scripts/Dpkg/Deps/Simple.pm
@@ -194,7 +194,6 @@ sub parse_string {
\s*$ # trailing spaces at end
}x;
if (defined $2) {
-return if $2 eq 'native' and not $self->{build_dep};
$self->{archqual} = $2;
}
$self->{package} = $1;
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1053481: libdpkg-perl: dpkg-source fails to generate (complete) Testsuite-Triggers if test deps have :native qualifier
Package: libdpkg-perl Version: 1.18.8 Severity: normal Control: affects -1 src:zsh src:poppler src:libjodycode src:doxygen src:jemalloc src:jdupes src:libsdl2 src:iproute2 Any test stanza in a debian/tests/control file which contains a foo:native Depends will not have its dependencies translated into Testsuite-Triggers. This is due to an explicit check in Dpkg::Deps::Simple->parse_string() which only allows native qualified dependencies for build dependencies. As an example, running “dpkg-source -b .” for jdupes shows % dpkg-source -b . dpkg-source: warning: can't parse dependency tree:native dpkg-source: warning: can't parse dependency tree:native dpkg-source: warning: can't parse dependency tree:native dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building jdupes using existing ./jdupes_1.27.3.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: building jdupes in jdupes_1.27.3-2.debian.tar.xz dpkg-source: info: building jdupes in jdupes_1.27.3-2.dsc Three warnings, one for each of the tests. Since it does have a test without a native qualified dependency, Testsuite-Triggers is generated. % grep Depends debian/tests/control Depends: @, tree:native Depends: @, tree:native Depends: @, tree:native Depends: @, forensics-samples-files % grep Testsuite ../jdupes_1.27.3-2.dsc Testsuite: autopkgtest Testsuite-Triggers: forensics-samples-files As far as I can tell, this has been a problem since dpkg-source gained support for generating Testsuite-Triggers. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libdpkg-perl depends on: ii dpkg 1.22.0 ii perl 5.36.0-9 Versions of packages libdpkg-perl recommends: ii bzip2 1.0.8-5+b1 ii libfile-fcntllock-perl 0.22-4+b1 ii liblocale-gettext-perl 1.07-6 ii xz-utils5.4.4-0.1 Versions of packages libdpkg-perl suggests: ii binutils 2.41-5 ii brz [bzr] 3.3.4-1 ii clang-14 [c-compiler] 1:14.0.6-16 ii clang-16 [c-compiler] 1:16.0.6-15 ii debian-keyring 2023.09.24 ii gcc [c-compiler] 4:13.2.0-1 ii gcc-13 [c-compiler]13.2.0-4 ii git1:2.42.0-1 ii gnupg 2.2.40-1.1 ii gpgv 2.2.40-1.1 ii patch 2.7.6-7 ii sensible-utils 0.0.20 -- no debconf information
Bug#1051063: vim-scripts: no license assumption must be non-free
On Fri, Sep 01, 2023 at 11:04:44PM +0200, Bastian Germann wrote: > In vim-script's copyright file, the following assumption is written: > > "Summary of license information of each script is reported below. For scripts > which license is "no license" it is assumed in good faith that having being > posted on vim.org their licence is at least as free as the licence of Vim > itself." > > This assumption is wrong. International copyright agreements unfortunately > make > those files non-DFSG-free. > > Please move them affected files to a new source package with Section: > non-free/editors. Honestly, this package probably should just be removed. Most of the scripts aren't maintained upstream anymore and are of questionable utility. I had been intending to split the package up anyway, but I'll probably just package a couple of the more useful/maintained ones and then just RM vim-scripts. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1052204: ITP: tree-sitter-query -- Tree-sitter query parser for Tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: tree-sitter-query Version : 0.1.0 Upstream Contact: Neovim Treesitter Team * URL : https://github.com/nvim-treesitter/tree-sitter-query * License : Apache 2.0 Programming Lang: JavaScript, C, Rust Description : Tree-sitter query parser for Tree-sitter This package provides a tree-sitter queries parser for tree-sitter. This is needed for Neovim's tests and is one of the tree-sitter parsers expected to be available. It will be maintained in the tree-sitter team.
Bug#1052203: ITP: tree-sitter-vim -- Vimscript parser for Tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: tree-sitter-vim Version : 0.3.0 Upstream Contact: Thomas Vigouroux * URL : https://github.com/neovim/tree-sitter-vim/ * License : MIT Programming Lang: JavaScript, C, Rust Description : Vimscript parser for Tree-sitter This package provides a vimscript parser for tree-sitter. This is needed for Neovim's tests and is one of the tree-sitter parsers expected to be available. It will be maintained in the tree-sitter team.
Bug#1052202: ITP: tree-sitter-vimdoc -- Vim help file parser for tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: tree-sitter-vimdoc Version : 2.0.0 Upstream Contact: Thomas Vigouroux * URL : https://github.com/neovim/tree-sitter-vimdoc/ * License : Apache 2.0 Programming Lang: JavaScript, C, Rust Description : Vim help file parser for tree-sitter This package provides a tree-sitter parser for Vim's help files. This is needed for Neovim's tests and is one of the tree-sitter parsers expected to be available. It will be maintained in the tree-sitter team.
Bug#1021339: Offer to help with some neovim packaging
On Mon, Sep 18, 2023 at 09:55:48PM +, brian m. carlson wrote: > Is there a way I can contribute to packaging the necessary dependencies > or helping in some other way with the upgrade to a newer version of > Neovim? I have initial versions of the new dependencies packaged locally. I need to clean a few things up, get them through NEW, and then either skip or figure out what the test failures are that I'm hitting. This will all likely go to experimental first, since there are also a few library transitions that are involved. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1050396: RM: pangoterm -- RoQA; low popcon; depends on gtk2
Control: forcemerge 967680 -1 On Thu, Aug 24, 2023 at 01:49:47AM +0200, Bastian Germann wrote: > pangoterm does not seem to be used a lot and is unmaintained upstream. It's not unmaintained upstream. > I intend to file a RM bug. > If you have any reasons to keep it in Debian please voice them here. If more concrete plans develop to force gtk2 out of the archive, then this package can be removed along with those. Until then, leave it be. > To get people's attention, I am filing as a serious bug and will reassign to > the FTP team when the package is autoremoved from testing. There was already a bug noting that this still depends on gtk2. Merging with that one and keeping its Severity: normal. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1009230: RFP: difftastic -- diff that understands syntax
On Mon, Aug 21, 2023 at 07:53:46AM +0100, M Hickford wrote: > X-Debbugs-CC: debian-r...@lists.debian.org > > > Package: wnpp > > Severity: wishlist > > > > * Package name: difftastic > > Version : 0.25.0 > > Upstream Author : Wilfred Hughes > > * URL : https://github.com/Wilfred/difftastic > > * License : Expat > > Programming Lang: Rust > > Description : diff that understands syntax > > > > Difftastic is an experimental diff tool that compares files based on > > their syntax. > > > Hi. Anyone have the energy to package popular Rust application > difftastic? It's in other distributions such as Fedora but not yet > Debian. Blair Noctis has been looking into it. That's why they're marked as the Owner and the bug is now ITP instead of RFP. However, they're waiting on me getting some of the TreeSitter parsers packaged. > I have experience packaging Go applications if anyone would like to > exchange RFPs The kitty package is blocked on some new Go packages. See https://bugs.debian.org/1037440. :) Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1042979: subversion-tools: psvn.el does not work with emacs 29.1
On Fri, Aug 04, 2023 at 01:18:15AM +0900, OHURA Makoto wrote: > After upgrading emacs 29.1, psvn.el does not work fine. Emacs 29.1 > doesn't support the function, toggle-read-only. Use read-only-mode. > I attach a patch to this e-mail. Thanks for the patch! > --- psvn.el.old 2023-08-04 01:00:23.460477204 +0900 > +++ psvn.el 2023-08-04 00:28:50.764059785 +0900 > @@ -2248,7 +2248,7 @@ >(setq mode-line-process 'svn-status-mode-line-process) >(run-hooks 'svn-status-mode-hook) >(let ((view-read-only nil)) > -(toggle-read-only 1))) > +(read-only-mode 1))) If we make this change, then it won't work with older emacs versions. I'd like to send the fix upstream, but would need this resolved first. Is it possible to make these changes compatible with both old and new emacs? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1035736: neovim: Turning off the banner causes the cursor to flicker permanently and CPU usage goes up
On Sun, Jun 18, 2023 at 11:38:58AM +0200, Bastian Venthur wrote: > I think it is related to wl-copy, which is installed and used on all my > machines where this error occurs. More specifically, when browsing /tmp and > turning off the banner, I can actually see folders like > `wl-copy-buffer-X` appearing and disappearing in very quick succession. > I suspect this is related to that buggy behavior. Ah, that makes sense. Netrw fiddles with the clipboard, which is probably causing wl-copy to update files in /tmp, and therefore netrw tries to refresh its display. I thought neovim had patched out most/all of netrw's clipboard stuff, but maybe some got missed. As a workaround, it may be worth trying to setup autocommands to update 'clipboard' such that you don't have unnamedplus in use when you're in a netrw buffer. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1039952: alacritty: broken rendering with Source Code Pro
On Thu, Jun 29, 2023 at 09:47:26PM +, brian m. carlson wrote: > If the user has configured Source Code Pro as the terminal font, then > text is rendered very tiny and squashed at the top of the window. > > [...] > > I believe this is fixed in 0.12.0 and was tracked upstream at > https://github.com/alacritty/alacritty/issues/6048. This will probably > be fixed simply by updating Alacritty to the latest version, so it would > be great if that could happen. That discussion also suggests updating the version of Source Code Pro will fix the issue. Updating alacritty is going to require packaging/updating more crates, so updating the font may be a quicker solution for this particular problem. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#982972: dose-extra: option to exclude Extra-Source-Only packages for dose-ceve
On Wed, Feb 17, 2021 at 11:41:02PM +0800, Shengjing Zhu wrote: > Could you add an option for dose-ceve to ignore the Extra-Source-Only > packages. > > dose-ceve is used in ratt to find out the reverse build depends, however > sometimes it will pick up packages which are Extra-Source-Only. Would using "--latest 1" achieve the same result? Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1040187: ratt: Add a -shallow option to only build immediate reverse deps
Package: ratt Version: 0.0~git20190123.9e77a6d-1+b6 Severity: wishlist The current use of dose-ceve to determine the reverse deps finds all transitive reverse deps, too. For many packages, only the immediate reverse deps would actually be affected, so rebuilding all reverse deps is a waste of time. Experimentally, it seems dose-ceve's "--depth 2" would achieve this, but it might be good to confirm with someone that understands dose better than I. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ratt depends on: ii libc6 2.37-3 ii sbuild 0.85.2 Versions of packages ratt recommends: ii dose-extra 7.0.0-1+b2 ratt suggests no packages. -- no debconf information
Bug#1028231: unibilium: parse-terminfo test uses wrong terminfo directory
On Mon, Jun 19, 2023 at 09:42:39PM +0200, Sven Joachim wrote: > FYI, the ncurses-base package in experimental has moved the terminfo > files to /usr/share/terminfo, and indeed the parse-terminfo autopkgtest > does not do anything[1]. Maybe it is time to upload the pending fixes, > now that Bookworm has been released? Thanks for the reminder! I'll do that soon. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1035736: neovim: Turning off the banner causes the cursor to flicker permanently and CPU usage goes up
On Mon, May 08, 2023 at 03:13:41PM +0200, Bastian Venthur wrote: > Turning off the netrw's banner (netrw-I), via g:netrw_banner and or by > pressing > "I" in the Explorer causes the cursor to flicker permanently and the CPU usage > goes up to 50% or so. I can't reproduce this. “nvim --clean” followed by “:e .” and pressing I doesn't result in flickering or high CPU usage. If this “nvim --clean” works fine, then I'd suggest looking through your config and “:scriptnames” to see what may be affecting it. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1037446: RFP: golang-github-seancfoley-ipaddress-go -- Go library for handling IP addresses and subnets, both IPv4 and IPv6
Package: wnpp Severity: wishlist X-Debbugs-Cc: team+pkg...@tracker.debian.org Control: block 1037440 by -1 * Package name: golang-github-seancfoley-ipaddress-go Version : 1.5.4 Upstream Contact: Sean C Foley * URL : https://seancfoley.github.io/IPAddress/ * License : Apache-2.0 Programming Lang: Go Description : Go library for handling IP addresses and subnets, both IPv4 and IPv6 IP address and network manipulation, CIDR, operations, iterations, containment checks, longest prefix match, subnetting, and data structures, with polymorphic code This needed to package new upstream version of kitty.
Bug#1037445: RFP: golang-github-jamesruan-go-rfc1924 -- RFC1924 base85 encoding library for Go
Package: wnpp Severity: wishlist X-Debbugs-Cc: team+pkg...@tracker.debian.org Control: block 1037440 by -1 * Package name: golang-github-jamesruan-go-rfc1924 Version : 0.0~20170108144916.git2767ca7c638f Upstream Contact: James Ruan * URL : https://github.com/jamesruan/go-rfc1924 * License : Expat Programming Lang: Go Description : RFC1924 base85 encoding library for Go This is needed to package new upstream version of kitty.
Bug#1037441: RFP: golang-github-altree-bigfloat -- Additional operations for the standard library big.Float type
Package: wnpp Severity: wishlist X-Debbugs-Cc: team+pkg...@tracker.debian.org Control: block 1037440 by -1 * Package name: golang-github-altree-bigfloat Version : 0.0~20220102081255.git38c8b72a9924 Upstream Contact: Alberto Donizetti * URL : https://github.com/ALTree/bigfloat * License : Expat Programming Lang: Go Description : Additional operations for the standard library big.Float type Package bigfloat provides the implementation of a few additional operations (square root, exponentiation, natural logarithm, exponential function) for the standard library big.Float type. This is needed to package new upstream version of kitty.
Bug#1037440: kitty: New upstream release
Source: kitty Severity: wishlist Filing this to track new packages/package updates which are blocking an update of kitty. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-8-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#1036027: unblock: kitty/0.26.5-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ki...@packages.debian.org Control: affects -1 + src:kitty Please unblock package kitty [ Reason ] Kitty registers itself as a handler for various MIME types (via kitty-open.desktop), but some of those (e.g., application/x-sh) are unexpectedly executed instead of viewed. This upload removes the installation of the desktop file, instead providing it as an example. README.Debian is updated to explain how to enable the functionality as well as warning about the implications. [ Impact ] Untrusted files may be executed rather than viewed (e.g., trying to view a shell script attached to an email). [ Tests ] n/a [ Risks ] Trivial change in a leaf package. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock kitty/0.26.5-5
Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script
On Wed, Apr 26, 2023 at 02:50:47PM +0200, Raphael Hertzog wrote: > Executing the script as default open action is IMO a very bad idea > because what you get by email is largely to not be trusted so I would > suggest that kitty be modified to not execute scripts in its URL > launcher mode (or that it gets some interactive confirmation from the > user before executing it). Upstream has added support for prompting if a file is executable[0]. However, the current upstream version of kitty has rewritten all of its kittens in go, so the changes aren't trivially backported. For bookworm, I'm going to stop installing kitty-open.desktop, by default. Install, I will ship it under /usr/share/doc/kitty/examples and add a note to README.Debian about it. [0]: https://github.com/kovidgoyal/kitty/commit/537cabca710f64b838d3b8b1dc986db596fb29d4 Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script
On Sat, May 06, 2023 at 04:07:56PM +0200, Gabriel Corona wrote: > Hi, > > > In the mean time, it's probably a good idea to drop > > "application/x-sh;application/x-shellscript" from the list of supported > > mime type to limit the risk. (I assume that even with "text/plain" and a > > .sh file extension or a shebang, kitty might still decide to execute the > > script... so the issue is not entirely fixed, but it reduces the number > > of > > cases where "kitty +open" is invoked on shell scripts) > > Indeed, you can use a file with MIME type such as text/ascii or > x-scheme-handler/kitty and a .tool file extension and it will be executed > through kitty. > > Affected software include: mail clients (mutt, Thunderbird [3,4]), browsers > (Firefox [1,2]), PDF viewers (Okular [5]). > > [1] https://www.gabriel.urdhr.fr/img/kitty-firefox1.png > [2] https://www.gabriel.urdhr.fr/img/kitty-firefox2.png > [3] https://www.gabriel.urdhr.fr/img/kitty-thunderbird1.png > [4] https://www.gabriel.urdhr.fr/img/kitty-thunderbird2.png The above examples prompt the user, so they're making an explicit choice. That's less of an issue. > > Or it's the users responsibility to configure their system to > > view shell files rather than execute them, if they are in the habit of > > clicking exe's attached to emails or otherwise clicking untrusted shell > > scripts. > > Or it is our responsibility to ship with a secure by default configuration? I'm leaning towards shipping kitty-open.desktop under /usr/share/doc/kitty/examples and adding a note to README.Debian about how to install it and the implications. I've not used this particular functionality of Kitty, so I'm not sure how this will change the usual user experience. However, I think this is a safer default and provides more information to the user. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1035509: [pre-approval] unblock: vim/2:9.0.1378-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: v...@packages.debian.org Control: affects -1 + src:vim Please unblock package vim [ Reason ] - Fix for CVE-2023-2426 (using uninitialized memory) - Minor fix for indenting of Perl scripts (regression from bullseye) [ Impact ] - Shipping with a known CVE, whose fix was requested by the security team - Thousands of wasted keystrokes indenting Perl scripts [ Tests ] - New test was added upstream for the CVE, but its mainly useful for running under valgrind [ Risks ] Fixes are small and straight forward. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock vim/2:9.0.1378-2 diffstat for vim-9.0.1378 vim-9.0.1378 changelog| 7 patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch | 22 + patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch | 2 patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch | 147 ++ patches/series | 2 5 files changed, 179 insertions(+), 1 deletion(-) diff -Nru vim-9.0.1378/debian/changelog vim-9.0.1378/debian/changelog --- vim-9.0.1378/debian/changelog 2023-03-04 14:41:33.0 -0500 +++ vim-9.0.1378/debian/changelog 2023-05-04 06:24:44.0 -0400 @@ -1,3 +1,10 @@ +vim (2:9.0.1378-2) unstable; urgency=medium + + * Backport 9.0.1499 to fix CVE-2023-2426 (Closes: #1035323) + * Backport fix for indenting of Perl subroutines (Closes: #1034529) + + -- James McCoy Thu, 04 May 2023 06:24:44 -0400 + vim (2:9.0.1378-1) unstable; urgency=medium * Merge upstream patch v9.0.1378 diff -Nru vim-9.0.1378/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch vim-9.0.1378/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch --- vim-9.0.1378/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch 2023-03-04 14:41:33.0 -0500 +++ vim-9.0.1378/debian/patches/debian/Support-sourcing-a-vimrc.tiny-when-Vim-is-invoked-as-vi.patch 2023-05-04 06:24:44.0 -0400 @@ -86,7 +86,7 @@ # define SYS_VIMRC_FILE "$VIM/vimrc" #endif diff --git a/src/structs.h b/src/structs.h -index d020449..dbbecb4 100644 +index 46a71cb..ac661a6 100644 --- a/src/structs.h +++ b/src/structs.h @@ -4468,6 +4468,9 @@ typedef struct diff -Nru vim-9.0.1378/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch vim-9.0.1378/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch --- vim-9.0.1378/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch 1969-12-31 19:00:00.0 -0500 +++ vim-9.0.1378/debian/patches/Fix-GH-267-where-indent-after-a-sub-would-not-work.patch 2023-05-04 06:24:44.0 -0400 @@ -0,0 +1,22 @@ +From: Andy Lester +Date: Tue, 26 Apr 2022 20:07:43 -0500 +Subject: Fix GH#267 where indent after a sub would not work + +Closes: #1034529 +Signed-off-by: James McCoy +--- + runtime/indent/perl.vim | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/runtime/indent/perl.vim b/runtime/indent/perl.vim +index 4c91fa1..bd2a1a9 100644 +--- a/runtime/indent/perl.vim b/runtime/indent/perl.vim +@@ -133,6 +133,7 @@ function! GetPerlIndent() + \ || synid == "perlHereDoc" + \ || synid == "perlBraces" + \ || synid == "perlStatementIndirObj" ++\ || synid == "perlSubDeclaration" + \ || synid =~ "^perlFiledescStatement" + \ || synid =~ '^perl\(Sub\|Block\|Package\)Fold' + let brace = strpart(line, bracepos, 1) diff -Nru vim-9.0.1378/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch vim-9.0.1378/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch --- vim-9.0.1378/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch 1969-12-31 19:00:00.0 -0500 +++ vim-9.0.1378/debian/patches/patch-9.0.1499-using-uninitialized-memory-with-fuzzy-matc.patch 2023-05-04 06:24:44.0 -0400 @@ -0,0 +1,147 @@ +From: Bram Moolenaar +Date: Sat, 29 Apr 2023 21:38:04 +0100 +Subject: patch 9.0.1499: using uninitialized memory with fuzzy matching + +Problem:Using uninitialized memory with fuzzy matching. +Solution: Initialize the arrays used to store match positions. + +Closes: #1035323 +--- + src/quickfix.c | 5 - + src/search.c| 17 +++-- + src/testdir/test_matchfuzzy.vim | 27 +
Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script
Keeping the full text for Kovid's benefit. On Wed, Apr 26, 2023 at 02:50:47PM +0200, Raphael Hertzog wrote: > Package: kitty > Version: 0.26.5-4 > Severity: serious > Tags: security > X-Debbugs-Cc: Debian Security Team > > Hello, > > I was reading https://lists.debian.org/20230425190728.ga1471...@subdivi.de > in mutt and that mail contains 3 shell scripts as attachments > (application/x-sh). I wanted to have a look at the scripts and thus I > "opened" those attachments... that open operation has been handled by > Kitty due its MimeType declaration in > /usr/share/applications/kitty-open.desktop [1] and the shell script has > thus been fed to "kitty +open
Bug#1034529: vim-runtime: perl subroutine body fails to indent in bookworm (regression from bullseye)
Control: tag -1 upstream confirmed
On Mon, Apr 17, 2023 at 07:36:57PM +0200, Matthijs van Duin wrote:
> I noticed when editing perl code in vim that pressing enter after the
> opening brace of a subroutine no longer indents like you'd expect:
>
> // expected:
> sub foo {
> _<-- cursor here
>
> // actual:
> sub foo {
> _<-- cursor here
>
> This worked correctly in debian bullseye (vim 8.2).
This was reported upstream[0] too, and their fix was exactly as you
surmised.
[0]: https://github.com/vim-perl/vim-perl/issues/267
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1034075: ITP: tree-sitter-lua -- Lua grammar for tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: tree-sitter-lua Version : 0.0.14 Upstream Contact: Munif Tanjim * URL : https://github.com/MunifTanjim/tree-sitter-lua * License : MIT Programming Lang: JavaScript, C, Rust Description : Lua grammar for tree-sitter This package provides a tree-sitter parser for Lua. This is needed for Neovim's tests and is one of the tree-sitter parsers expected to be available. It will be maintained in the tree-sitter team.
Bug#1032556: neovim-qt: New upstream version available: 0.2.17 (2022-07-02)
On Wed, Mar 08, 2023 at 08:52:03PM +, Andrew Chadwick wrote: > There is a new version of neovim-qt available upstream. Please could the > Debian repos be updated with it when it’s convenient? > > https://github.com/equalsraf/neovim-qt/tags > https://github.com/equalsraf/neovim-qt/releases/tag/v0.2.17 For some reason I missed this and still thought the latest was 0.2.16.1, so thanks for the prod. Unfortunately, it's missed the cut off for the next Debian release. I'll likely upload this to experimental soon. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Bug#1030088: ITP: tree-sitter-c -- C grammar for tree-sitter
Package: wnpp Severity: wishlist Owner: James McCoy X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: tree-sitter-c Version : 0.20.2 Upstream Contact: Max Brunsfeld * URL : https://github.com/tree-sitter/tree-sitter-c * License : MIT Programming Lang: Javascript, C, Rust Description : C grammar for tree-sitter This package provides a tree-sitter parser for C99. This is needed for Neovim's tests and is one of the tree-sitter parsers expected to be available.
