Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote: > The OpenSSL devs intended this to be a breaking change - but it's not > documented anywhere.  Sigh. > > I've got a WIP patch against trunk that causes test_ssl to pass - see below.  > It also seems to work with OpenSSL 1.1.1h as

Bug#976003: RFP: tree-sitter -- incremental parsing system for programming tools

Control: retitle -1 ITP: tree-sitter -- incremental parsing system for programming tools Control: owner -1 ! On Fri, Nov 27, 2020 at 09:49:49PM -0500, James McCoy wrote: > Package: wnpp > Severity: wishlist > > * Package name: tree-sitter > Version : 0.17.3 >

Bug#972197: subversion b-d's on python3-all-dev, but only builds for the default python3 version

On Wed, Oct 14, 2020 at 10:22:50AM +0200, Matthias Klose wrote: > subversion b-d's on python3-all-dev, but only builds for the default python3 > version. It actually builds for all available versions, but the install is broken. This used to work with Python 2.x. It looks like the difference is t

Bug#958139: ITP: vim-gitgutter -- A Vim plugin which shows a git diff in the sign column

On Sat, Apr 18, 2020 at 10:24:28PM +0200, Raphael Medaer wrote: > This Vim plugin shows a git diff in the 'gutter' (sign column). It shows > which lines have been added, modified, or removed. You can also preview, > stage, and undo individual hunks; and stage partial hunks. The plugin also > provid

Bug#958139: ITP: vim-gitgutter -- A Vim plugin which shows a git diff in the sign column

On Tue, Apr 21, 2020 at 11:01:00AM +0200, Raphael Medaer wrote: > Hi James, > > I did the changes you suggested > (https://salsa.debian.org/rmedaer/vim-gitgutter > /-/commit/8e9bd0944c7a9edb91dc7056996c8d16446a93fd) > The vim plugin is "optional". It means that users will have to add `packadd > g

Bug#958139: ITP: vim-gitgutter -- A Vim plugin which shows a git diff in the sign column

On Wed, Apr 22, 2020 at 02:26:54PM +0200, Raphael Medaer wrote: > Let me know if there is still something to change. For a brand new package, it's probably best to go with the current stable debhelper version (12). Similarly, it would be a good idea to ensure you're abiding by current Policy and

Bug#953881: Bug#954866: Bug#953881: transition: ruby2.7 only

On Thu, Apr 23, 2020 at 10:13:15AM +0200, Paul Gevers wrote: > It seems the ruby2.5 removal transition [1] is stalled by subversion > [2]. Can the fix for 954866 please be uploaded to unstable such that > subversion can migrate and we can finish the removal of ruby2.5 in testing? I'd rather not up

Bug#956007: mercurial: Remove use of python-subversion

Control: severity -1 serious On Sun, Apr 05, 2020 at 08:50:32PM -0400, James McCoy wrote: > python-subversion can't be built with current src:swig, so I'm in the > process of removing it. Subversion's next upstream release will have > support for Python 3, but since

Bug#953881: Bug#954866: Bug#953881: transition: ruby2.7 only

On Thu, Apr 23, 2020 at 02:09:35PM +0200, Paul Gevers wrote: > I > suggest you apply the same fix you already did here [2] and stop > building the python package for now if that works. Done and uploaded, however that now makes mercurial FTBFS, as I had notified them earlier this month (#956007).

Bug#980028: sudoedit runs editor as root

Package: sudo Version: 1.9.5-1 Severity: important Tags: upstream This is fixed in 1.9.5p1: * Fixed a regression introduced in sudo 1.9.5 where the editor run by sudoedit was set-user-ID root unless SELinux RBAC was in use. The editor is now run with the user's real and effective user-IDs.

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

Happy New Year! On Wed, Dec 30, 2020 at 10:39:28PM -0500, James McCoy wrote: > On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote: > > The OpenSSL devs intended this to be a breaking change - but it's not > > documented anywhere.  Sigh. > > > > I&

Bug#978353: serf: FTBFS: test_ssl_handshake fails with OpenSSL 1.1.1i

On Fri, Jan 15, 2021 at 08:36:22AM -0500, Justin Erenkrantz wrote: > Sadly, my Debian sid box ran into other issues and is currently inaccessible. > > I *think* that this would address the 1.3.x test issues, but 1.3.x doesn't > build on Mac OS for me for other reasons...so, let me know how it goes

Bug#980449: vim: Change in default vim config causes obnoxious behaviour.

On Tue, Jan 19, 2021 at 10:22:35AM +0100, Rens Houben wrote: > Since an update to /some/ part of vim on unstable sometime last weekend I've > encountered new default behaviour that's quite disruptive. > > For instance, when I started writing this, as well as every single time this > terminal wind

Bug#980449: vim: Change in default vim config causes obnoxious behaviour.

On Wed, Jan 20, 2021 at 08:47:42AM +0100, Rens Houben wrote: > In other news for Tue, Jan 19, 2021 at 09:14:59PM -0500, James McCoy has been > seen typing: > > On Tue, Jan 19, 2021 at 10:22:35AM +0100, Rens Houben wrote: > > > The terminal sends [I when focus comes back

Bug#973670: vim-athena: Vim Athena - E236: Font Unifont is not fixed width

On Mon, Nov 02, 2020 at 09:55:45PM -0300, DieSpinne wrote: > If I try to set GNU Unifont as my Gvim's font I get errors. Attempt: > > :set gfn=-*-unifont-*-*-*-*-*-*-*-*-c-*-*-* > > Errors raised: > > E236: Font "-*-unifont-*-*-*-*-*-*-*-*-c-*-*-*" is not fixed-width > E596: Inva

Bug#977429: vim-runtime: vim:spec.vim occurs Error let keyword is missing...

Control: reopen -1 On Wed, Dec 16, 2020 at 10:47:38AM +0900, Yukiharu YABUKI wrote: > Hi, maintainer > > This is the code which has issue > in /usr/share/vim/vim82/ftplugin/spec.vim > > line 113. You can check the source. > > > 103 if (chgline == -1) > 104

Bug#977526: vim-voom: Outdated/incorrect instructions for using vim-voom

Package: vim-voom Version: 5.3-7 Severity: normal I noticed two issues related to the vim-addon-manager → dh-vim-addon conversion in this package. 1. README.Debian still describes how to setup the package using vim-addon-manager 2. NEWS mentions adding "packadd! voom" to the vimrc. However, t

Bug#976003: RFP: tree-sitter -- incremental parsing system for programming tools

Package: wnpp Severity: wishlist * Package name: tree-sitter Version : 0.17.3 Upstream Author : Max Brunsfeld * URL : https://tree-sitter.github.io/tree-sitter/ * License : MIT Programming Lang: C, Rust Description : incremental parsing system for progr

Bug#974950: vim-scripts: missing vim-addon-manager registry file

On Tue, Nov 17, 2020 at 02:43:55PM -0300, Antonio Terceiro wrote: > On Mon, Nov 16, 2020 at 07:04:26PM -0500, James McCoy wrote: > > On Mon, Nov 16, 2020 at 08:41:57PM -0300, Antonio Terceiro wrote: > > > The new vim-scripts breaks existing usage with vim-addon-manager. > >

Bug#975087: python-msgpack breaks python-pynvim autopkgtest: times out after 2:47 hours

On Wed, Nov 18, 2020, 15:21 Paul Gevers wrote: > Source: python-msgpack, python-pynvim > Control: found -1 python-msgpack/1.0.0-4 > Control: found -1 python-pynvim/0.4.1-2 > Severity: serious > Tags: sid bullseye > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > User

Bug#975087: Not relevant to msgpack itself, therefore

Control: reopen -1 On Thu, Nov 19, 2020 at 12:32:53AM +0100, Thomas Goirand wrote: > Since James McCoy says it's fixed in python-pynvim 0.4.2, I'm closing > this bug for msgpack. I was referring to the upstream version, which has not been packaged yet. Also, this bug was fil

Bug#975239: python-pynvim: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

Control: forcemerge 975237 -1 On Thu, Nov 19, 2020 at 12:56:31PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > collecting ... collected 68 items > > > > test/test_buffer.py::test_repr PASSED

Bug#975336: Acknowledgement (vim-scripts: po.vim no longer works)

On Fri, Nov 20, 2020 at 05:10:08PM +0100, Helge Kreutzmann wrote: > Hello Maintainer, > I had a broken link in my local config to po.vim. After I fixed it > po.vim again works. > > Somehow this broken link was not causing trouble the last years but > only after this update. This is exactly what t

Bug#972197: subversion b-d's on python3-all-dev, but only builds for the default python3 version

On Wed, Oct 21, 2020 at 12:42:36PM +0200, Matthias Klose wrote: > On 10/21/20 1:13 AM, James McCoy wrote: > > On Wed, Oct 14, 2020 at 10:22:50AM +0200, Matthias Klose wrote: > >> subversion b-d's on python3-all-dev, but only builds for the default > >> python3 &g

Bug#972777: vim ftbfs with python3.9 (test failure)

On Fri, Oct 23, 2020 at 12:14:17PM +0200, Matthias Klose wrote: > Package: src:vim > Version: 8.2.0716-3 > Severity: important > Tags: sid bullseye ftbfs > User: debian-pyt...@lists.debian.org > Usertags: python3.9 > > vim ftbfs with python3.9 (test failure), python3-defaults from experimental > N

Bug#973548: vim-runtime: syntax/cabal.vim missing build-tool-depends

On Sun, Nov 1, 2020, 11:30 Clint Adams wrote: > Package: vim-runtime > Version: 2:8.1.0875-5 > Tags: patch > > This made it into > https://github.com/sdiehl/haskell-vim-proto/blob/master/vim/syntax/cabal.vim#L74 > three years ago but was apparently not incorporated into vim-runtime. Runtime fil

Bug#972777: vim ftbfs with python3.9 (test failure)

Control: clone -1 -2 Control: retitle -2 Test_compiler sporadically fails Control: fixed -1 vim/2:8.2.1913-1 On Sat, Nov 07, 2020 at 12:59:48PM +0200, Graham Inggs wrote: > Control: reopen -1 > > I still see a similar failure with 8.2.1913-1: > > https://people.debian.org/~ginggs/python3.9-defau

Bug#973943: Test_compiler sporadically fails

On Sat, Nov 07, 2020 at 09:33:22PM -0500, James McCoy wrote: > On Sat, Nov 07, 2020 at 12:59:48PM +0200, Graham Inggs wrote: > > /<>/src/vim-gtk3/testdir/runtest.vim[461]..function > > RunTheTest[39]..Test_compiler line 23: command did not fail: clist > > command line..

Bug#973943: Test_compiler sporadically fails

On Sun, Nov 08, 2020 at 10:30:15PM +0200, Graham Inggs wrote: > Hi James > > On Sun, 8 Nov 2020 at 20:12, James McCoy wrote: > > Would you be able to reproduce the failure with the attached patch > > applied? That should give more insight into what's going on. >

Bug#973943: Test_compiler sporadically fails

On Mon, Nov 09, 2020 at 09:10:54PM +0200, Graham Inggs wrote: > On Mon, 9 Nov 2020 at 19:49, James McCoy wrote: > > It's strange that Perl is looking at the individual LC_* settings > > when LANG (and LC_ALL with my local changes) are set in the environment. > > > >

Bug#973943: Test_compiler fails when locales are not available

Control: retitle -1 Test_compiler fails when locales are not available On Mon, Nov 09, 2020 at 11:22:14PM +0200, Graham Inggs wrote: > On Mon, 9 Nov 2020 at 21:25, James McCoy wrote: > > I mean I specifically set LANG (and LC_ALL in my local repo) to C.UTF-8 > > [1] when running

Bug#881633: Creation of vim-python3 virtual package

Thanks for starting the discussion, Victor. One thing I'd like to note is that none of the vim-$lang virtual packages are currently listed in Policy's set of virtual packages. That was an oversight on the Vim maintainers side when the package names were introduced, but maybe now would be a good t

Bug#881633: Creation of vim-python3 virtual package

On Wed, Nov 15, 2017 at 10:15:31AM -0700, Sean Whitton wrote: > On Wed, Nov 15 2017, James McCoy wrote: > > > One thing I'd like to note is that none of the vim-$lang virtual > > packages are currently listed in Policy's set of virtual packages. > > That was a

Bug#881906: devscripts: busters grep-excuses misses informatioon

On Thu, Nov 16, 2017 at 10:48:05AM +0100, Rene Engelhard wrote: > stretch: > > $ grep-excuses libreoffice > libreoffice (1:5.4.2-3 to 1:5.4.3-2) > Migration status: WAITING: Waiting for test results, another package or > too young (no action required now - check later) > Maintainer: Debia

Bug#894565: vim: FTBFS: Test failures if build user cannot open /dev/stdout

On Sun, Apr 01, 2018 at 07:49:05AM -0700, Daniel Schepler wrote: > From > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vim.html > (and I'm also seeing pretty much the same failure under pbuilder): > > ... > > Executing Test_z() > Executing Test_z_negative_lnum() > Executing

Bug#894565: vim: FTBFS: Test failures if build user cannot open /dev/stdout

On Mon, Apr 02, 2018 at 08:44:17PM -0700, Daniel Schepler wrote: > On Mon, Apr 2, 2018 at 7:21 PM, James McCoy wrote: > > Why is /dev/stdout missing? It's possible one of the attached patches > > will work around that issue, but I'm more curious why that's ha

Bug#894803: vim-airline: Vcs-Browser URL 404s

Source: vim-airline Version: 0.9-1 Severity: minor There's an extra ".git" in the URL. It should just be . -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable')

Bug#894803: vim-airline: Vcs-Browser URL 404s

On Wed, Apr 04, 2018 at 07:43:20AM -0400, James McCoy wrote: > There's an extra ".git" in the URL. It should just be > <https://salsa.debian.org/jcc/vim-airline/tree/master>. Also, I did give you access to vim-team on salsa (in case you requested it for vim-airline).

Bug#888206: /usr/bin/vim.basic: Wrong behavior of arrow keys and compose keys.

On Tue, Jan 23, 2018 at 11:18:49PM +0100, luciano wrote: > I connect to remote systems using ssh and use vi and vim on the remote > systems for all administrative tasks. Now I see that the arrow keys > and the compose keys- these are useful for characters as @ and # if > you use italian keyboard -

Bug#887963: git-debcherry: Exports incorrect patches when fed tags

On Sun, Jan 21, 2018 at 11:21:51PM -0500, James McCoy wrote: > TL;DR, git-debcherry (or maybe just gitpkg's invocation of it) should > likely force resolving the given treeish to a non-tag with ^{}. > > $ debcheckout neovim-qt && cd neovim-qt > … > $ git-debc

Bug#888566: vim FTBFS on alpha: vim segfaults in the build

On Sat, Jan 27, 2018 at 05:50:16PM +1300, Michael Cree wrote: > [snip useful details] > > Four of those bytes difference are due to the field b_ino in the > struct (of type ino_t). And indeed examining the build log [1] > one sees option.c is compiled with -DFILE_OFFSET_BITS=64 but > misc1.c is N

Bug#888566: vim FTBFS on alpha: vim segfaults in the build

On Sat, Jan 27, 2018 at 02:37:21PM -0500, James McCoy wrote: > On Sat, Jan 27, 2018 at 05:50:16PM +1300, Michael Cree wrote: > > [snip useful details] > > > > Four of those bytes difference are due to the field b_ino in the > > struct (of type ino_t). And indeed

Bug#846264: yacc/bison highlighting interprets semicolon in quotes as end of rule

Hi Charles, Given a simple file like %token SEMICOLON ";" %% iteration_statement: "do" statement "while" "(" expression_in ")" ";" | "while" "(" expression_in ")" statement ; The ";" in iteration_statement ends the syntax highlighting for the rule. Since it's quoted, it s

Bug#881654: vim: visible bracket matching broken in configure.ac files

Hi Christian, As described below, the highlighting performed by :MatchParen gets confused by the AC_MSG_* syntax region. On Mon, Nov 13, 2017 at 10:36:35PM +0100, Ferenc Wágner wrote: > Please create /tmp/configure.ac with the following contents: > > [AC_MSG_([yes])] > > and position the cursor

Bug#888566: vim FTBFS on alpha: vim segfaults in the build

Control: reassign -1 src:glibc 2.24-2 Control: affects -1 src:vim On Sat, Jan 27, 2018 at 02:37:21PM -0500, James McCoy wrote: > On Sat, Jan 27, 2018 at 05:50:16PM +1300, Michael Cree wrote: > > [snip useful details] > > > > Four of those bytes difference are due to t

Bug#886285: vim-runtime: tex syntax highlighting fails to enter math mode within align environment

On Wed, Jan 31, 2018 at 11:33:30PM +0100, Francesco Poli wrote: > On Mon, 29 Jan 2018 21:12:01 -0500 James McCoy wrote: > > > On Mon, Jan 29, 2018 at 07:33:40PM +0100, Francesco Poli wrote: > [...] > > > So I am puzzled: upstream dropped support for extended syntax

Bug#868252: vim-nox: pressing on last line of a foldmethod=manual behaves differently at end of file

On Thu, Jul 13, 2017 at 07:14:03PM +, Daniel Shahaf wrote: > I use foldmethod=manual. When I want to add a line following the last > line of a fold, I use «A» if I want the line new to be included in > the fold, and «o» if I want the new line not to be included in the fold. > > However, I fin

Bug#878218: libserf-1-1: Subversion error E120171 with libserf 1.3.9-3

On Wed, Oct 11, 2017 at 10:51:59AM +0200, Falko Matthies wrote: > I have a small issue. It looks like that the serf lib is the reason, why > subversion does not work anymore while > accessing HTTPS repositories. > > I am using > - the current debian testing (buster) amd64 > - subversion 1.9.7-2 (r

Bug#680125: subversion build still racy

On Tue, Sep 19, 2017 at 01:51:52PM +0100, Robert McQueen wrote: > Endless OS has been rebasing to Debian stretch and found that #680125 is > alive and well. We can't reproduce it locally but it happens every time > in our OBS. I hadn't been either until recently. Now I'm regularly hitting it. >

Bug#879232: qa.debian.org: [udd] Fix link for form in lintian template

: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) >From 557ec71b17b6ac17575ca08e75b0b2afa90714ff Mon Sep 17 00:00:00 2001 From: James McCoy Date: Fri, 20 Oct 2017 15:40:02

Bug#879562: ITP: dex -- OpenID Connect Identity (OIDC) and OAuth 2.0 Provider with Pluggable Connectors

On Sun, Oct 22, 2017 at 10:30:38PM +0200, Michael Stapelberg wrote: > * Package name: dex > Version : 2.7.1 > Upstream Author : CoreOS > * URL : https://github.com/coreos/dex > * License : Apache-2.0 > Programming Lang: Go > Description : OpenID Connect I

Bug#889873: vagrant: unable to download images (moved from atlas.hashicorp.com to app.vagrantup.com)

On Thu, Feb 08, 2018 at 09:02:03AM +0100, Lucas Nussbaum wrote: > It seems that Hashicorp decided to migrate from e.g. > https://atlas.hashicorp.com/alpine/alpine64 > to > https://app.vagrantup.com/alpine/boxes/alpine64 > > This breaks images download, making this package essentially > unfortunate

Bug#890232: devscripts: debsign fails to scp files with colon in name

On Mon, Feb 12, 2018 at 10:48:35AM +0100, Rafael Laboissière wrote: > The debsign script fails to scp files which contain a colon (":") in their > names. This is unfortunate because the colon is a valid character in the > version number of Debian packages. > > Please, find attached to this bug re

Bug#890316: neovim: cmd line shows special chars like":]2 q" instead of ":"

On Tue, Feb 13, 2018 at 12:11:47PM +0100, Luffah wrote: >When i open `nvim -u NONE` and i press ':' command line >shows special chars like":]2 q" instead of ":" . Quoting from upstream's [FAQ]: > This is a bug in your terminal emulator. It happens because Nvim sends > cursor-shape termcod

Bug#890642: vim: Please upload an updated version (to fix annoying disappearing cursor)

On Fri, Feb 16, 2018 at 09:55:56PM -0600, Andreas Kloeckner wrote: > Package: vim > Version: 2:8.0.0197-4+deb9u1 > I use the 'ale' lint engine, and the most recent version of vim in > Debian (8.0.1453) is affected by this issue: That's not the version you filed the bug about. Is 2:8.0.0197-4+deb

Bug#890897: transition: unibilium

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition There is an upstream SONAME bump due to support for terminfo's new wide format. The dependency chain revolves around neovim and everything rebuilds and tests fine with the new unibilium.

Bug#879895: virtualbox-guest-dkms: vboxvideo doesn't build for 4.13 kernel

Package: virtualbox-guest-dkms Version: 5.2.0-dfsg-1 Severity: important Now that virtualbox 5.2 is in unstable, I would expect it to build against the kernel that is in unstable. However, 5.2 explicitly disables building vboxvideo if drm_rect.h is present in the kernel that it's building against

Bug#887312: ITP: libtickit -- Terminal Interface Construction KIT

Package: wnpp Severity: wishlist Owner: James McCoy * Package name: libtickit Version : 0.2 Upstream Author : Paul Evans * URL : http://www.leonerd.org.uk/code/libtickit/ * License : MIT Programming Lang: C Description : Terminal Interface

Bug#887963: git-debcherry: Exports incorrect patches when fed tags

.2.8 v0.2.8-2 Cloning into '/tmp/git-debcherry.KYsPnT/clone'... done. $ cat ../bug/0001-Point-gbp-dch-to-the-correct-branch.patch From bacc7ba0767f29425a9083d1ae08390f93daede0 Mon Sep 17 00:00:00 2001 From: James McCoy Date: Tue, 16 Jan 2018 07:31:37 -0500 Subject: [PATCH] Point gbp-dc

Bug#897381: kitty: fails to start

On Tue, May 01, 2018 at 09:09:01PM +0300, Ulyanich Michael wrote: > $ kitty > [121 21:06:37.050428] [glfw error 65543]: GLX: Failed to create context: > GLXBadFBConfig > [121 21:06:37.050748] Failed to create a window at size: 640x400, using a > standard size instead. > [121 21:06:37.053618] [glfw

Bug#897555: subversion: FTBFS: /bin/bash: /usr/lib/jvm/default-java/bin/javah: No such file or directory

On Wed, May 02, 2018 at 11:02:02PM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part (hopefully): > > [snip] > > /usr/lib/jvm/default-java/bin/javah -force -d > > subversion/bindings/javahl/include -classpath > > su

Bug#897928: virtualbox-guest-dkms: vboxvideo module fails to build with 4.16 kernel

Package: virtualbox-guest-dkms Version: 5.2.10-dfsg-6 Severity: important Dear Maintainer, Upon installation of the recent 4.16 kernel, this module failed to build: DKMS make.log for virtualbox-guest-5.2.10 for kernel 4.16.0-1-amd64 (x86_64) Fri May 4 17:01:28 EDT 2018 make: Entering directory

Bug#897815: msgpack-c: ftbfs with GCC-8

Control: forwarded -1 https://github.com/msgpack/msgpack-c/pull/659 Control: tag -1 fixed-upstream On Fri, May 04, 2018 at 12:22:47PM +, Matthias Klose wrote: > [...] > from > /<>/example/cpp03/class_non_intrusive.cpp:16: > /<>/include/msgpack/v1/object.hpp: In function 'void

Bug#897555: subversion: FTBFS: /bin/bash: /usr/lib/jvm/default-java/bin/javah: No such file or directory

On Thu, May 03, 2018 at 11:25:03PM +0200, Emmanuel Bourg wrote: > On Wed, 2 May 2018 22:11:49 -0400 James McCoy wrote: > > > Ah, that's because the javah command was removed in Java 10, to be > > replaced by running "javac -h". > > > > It would have

Bug#898494: dgit: conventions for uploading to suites with semantics like *-backports

On Sat, May 12, 2018 at 10:18:55AM -0700, Sean Whitton wrote: > Here are two ways of managing uploads to -backports with dgit: > > 1. maintain a stretch-bpo branch, merge the debian/ tags for uploads >that have migrated to testing, `dch --bpo` and `dgit push-source` to >backports > [snip]

Bug#867720: marked as pending

On Sep 30, 2017 08:00, "Salvatore Bonaccorso" wrote: Hi On Sat, Sep 30, 2017 at 11:59:07AM +0200, Moritz Mühlenhoff wrote: > James McCoy wrote: > > diff --git a/debian/changelog b/debian/changelog > > index 978762c..8df2745 100644 > > --- a/debian/chang

Bug#877348: stretch-pu: package vim/8.0.0197-4+deb9u1

dium + + * Backport upstream patches to fix CVE-2017-11109 (Closes: #867720) ++ 8.0.0703: Illegal memory access with empty :doau command ++ 8.0.0706: Crash when cancelling the cmdline window in Ex mode ++ 8.0.0707: Freeing wrong memory when manipulating buffers in autocommands + + --

Bug#877262: proper shell indenting does not work anymore

Control: tag -1 fixed-upstream On Fri, Sep 29, 2017 at 10:13:03PM +0100, Klaus Ethgen wrote: > Usually (with 7.x) when writing in shell scripts "if ...\nthen" the then > start indented and gets not indented when the "n" is typed. With version > 8, that is not working anymore and the then stays int

Bug#877348: stretch-pu: package vim/8.0.0197-4+deb9u1

On Sat, Sep 30, 2017 at 09:42:14PM +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sat, 2017-09-30 at 14:48 -0400, James McCoy wrote: > > * Backport upstream patches to fix CVE-2017-11109  (Closes: #867720) > >   + 8.0.0703: Illegal memory access wit

Bug#895268: libtickit: Fix out-of-bounds write with FD_SET()

On Mon, Apr 09, 2018 at 12:21:32AM -0700, Steve Langasek wrote: > Hi James, Hey, > You filed https://bugs.launchpad.net/libtickit/+bug/1744933 about tests > reporting a buffer overflow in libtickit. It seems you worked around this > by disabling the hardening flags Yes, I was hoping to get time

Bug#895825: neovim: Package suggests python-neovim but there is no installation candidate.

On Mon, Apr 16, 2018 at 10:22:18AM -0400, Michael P. Soulier wrote: > When I attempt to install neovim, the python-neovim package is > suggested. But if I try to install that, I am told that there is no > installation candidate. That's because python(3)-neovim didn't make it into Stretch. There's

Bug#896010: lintian: FP for source-contains-empty-directory if directory isn't listed with trailing slash

Package: lintian Version: 2.5.82 Severity: normal While prepping the 1.10.0-1 subversion upload, I noticed that lintian flagged every single directory in the upstream tarball with "source-contains-empty-directory". Comparing this to other tarballs I have available, it appears this is due to the f

Bug#896010: lintian: FP for source-contains-empty-directory if directory isn't listed with trailing slash

On Wed, Apr 18, 2018 at 12:58:52PM -0400, James McCoy wrote: > While prepping the 1.10.0-1 subversion upload, I noticed that lintian > flagged every single directory in the upstream tarball with > "source-contains-empty-directory". > > Comparing this to other tarballs I h

Bug#896760: DDPO: add Salsa icon to VCS column

On Tue, Apr 24, 2018 at 10:27:47AM +0200, Daniel Pocock wrote: > When looking at a long list of packages it is hard to see if any have > been missed. The VCS URLs don't make it obvious because sometimes the > VCS has moved but there hasn't been a new upload of the package. How would one detect th

Bug#943328: vim: sensible-editor can no longer find vim

On Wed, Oct 23, 2019 at 02:24:59PM +0200, IOhannes m zmoelnig wrote: > in the latest upload i find the following in d/changelog: > > Move /usr/bin/vim.* into /usr/libexec/vim/ > > This little change undoes my choice of 'sensible-editor'. > Previously i ran 'select-editor' and chose "2. /usr/bin/vi

Bug#942225: vim: Looses editor alternative selection (due to move into /usr/libexec/vim/)

On Sat, Oct 12, 2019 at 08:09:46PM +0200, Salvatore Bonaccorso wrote: > On update to 2:8.1.2136-1 (possibly due to the /usr/libexec/vim move) > the editor selection for the alternatives is lost: This was an unintended side effect. There was some IRC discussion about this, and since there was alre

Bug#943967: /usr/share/vim/vim81/debian.vim: runtimepath overriden in debian.vim without /etc/vim path

On Fri, Nov 01, 2019 at 10:25:49PM +0100, Václav Ovsík wrote: > A directory /etc/vim is missing from the VIM runtimepath and so my > syntax file at /etc/vim/syntax/dhcpd.vim is not loaded after upgrade > to the Debian Buster release. > > You mentioned addition of /etc/vim into the default 'runtime

Bug#928630: unblock: vim/2:8.1.0875-3

2019-05-05 23:41:10.0 -0400 @@ -1,3 +1,10 @@ +vim (2:8.1.0875-3) unstable; urgency=medium + + * syntax/deb{changelog,sources}: Update release names for Debian/Ubuntu +(Closes: #927167) + + -- James McCoy Sun, 05 May 2019 23:41:10 -0400 + vim (2:8.1.0875-2) unstable; urgency=me

Bug#928693: clang-7: Using --coverage causes "/usr/bin/ld: …: hidden symbol `llvm_gcda_end_file'" error

Package: clang-7 Version: 1:7.0.1-8 Severity: normal This is easily demonstrated with the libvterm package. $ debcheckout libvterm … $ cd libvterm $ env CC=clang-7 CFLAGS=--coverage make VERBOSE=1 TBL src/encoding/DECdrawing.tbl TBL src/encoding/uk.tbl CC src/encoding.c libtool: compile: clang-7

Bug#948269: file: misdetection of shared libraries as statically linked - breaks dh_shlibdeps

On Mon, Jan 06, 2020 at 12:19:21PM +0100, Christoph Biedl wrote: > Additionally, I always upload new upstream versions of src:file to > experimental first to avoid situations like this. If anybody wishes to > receive a notification to start tests, drop me a line with your e-mail > address, preferab

Bug#953057: subversion: FTBFS against swig 4

Control: merge 951893 -1 On Tue, Mar 03, 2020 at 06:20:54PM -0300, Lucas Kanashiro wrote: > While trying to rebuild src:subversion in a clean unstable amd64 chroot > I got the following error: > > ... > Wrote subversion/bindings/swig/proxy/swig_python_external_runtime.swg > /usr/bin/swig -I/<>/BU

Bug#953742: vim: FTBFS on armel, armhf, i386, mips64el, mipsel, s390x

On Thu, Mar 12, 2020 at 08:28:19PM +, Ivo De Decker wrote: > The latest upload of vim to unstable fails on armel, armhf, i386, mips64el, > mipsel, s390x: > > https://buildd.debian.org/status/package.php?p=vim At least the 32-bit arch failures are understood and I've already given upstream a

Bug#953980: E117: Unknown function: vifm#globals#Init

On Sun, Mar 15, 2020 at 12:01:39PM +0100, Nomen Nescio wrote: > There is error E117 in vim after vim-addon-manager install vifm. > > Error detected while processing /var/lib/vim/addons/plugin/vifm.vim: > line 50: > E117: Unknown function: vifm#globals#Init > > /var/lib/vim/addons/plugin/vifm.vi

Bug#950730: vim: Fails to build against ruby2.7

On Wed, Mar 18, 2020 at 11:00:33PM +0100, Christian Göttsche wrote: > vim (in particular vim-nox) depends still on ruby 2.5: libruby2.5 (>= > 2.5.0~preview1) > Any plans? Vim Build-Depends on ruby and ruby-dev. Vim's configure script uses the default ruby interpreter to build. As of now, the def

Bug#812421: apt: "apt upgrade" exits with "E: Broken packages" instead of upgrading

On Thu, Oct 10, 2019 at 08:25:50AM -0400, James McCoy wrote: > On Thu, Oct 10, 2019 at 08:13:51AM -0400, James McCoy wrote: > > Control: found -1 1.8.4 > > > > On Sat, Jan 23, 2016 at 11:06:54AM -0500, James McCoy wrote: > > > "apt upgrade" is erroring ou

Bug#945605: python-neovim: diff for NMU version 0.3.0-1.1

On Mon, Dec 23, 2019 at 12:36:25PM +0200, Adrian Bunk wrote: > I've prepared an NMU for python-neovim (versioned as 0.3.0-1.1) and > uploaded it to DELAYED/15. Please feel free to tell me if I should > cancel it. I've uploaded the new upstream version (0.4.0) which contains these fixes. It's go

Bug#906403: python-neovim: FTBFS in buster (failing tests)

Control: notfixed -1 0.2.6-1 On Fri, Dec 27, 2019 at 01:40:59PM -0500, James McCoy wrote: > Version: 0.2.6-1 > > On Fri, Aug 17, 2018 at 11:21:20AM +, Santiago Vila wrote: > > =

Bug#950460: libdata-messagepack-perl: FTBFS with msgpack-c/3.2.1-1

a-messagepack-perl_1.00-2.dsc dpkg-source: info: extracting libdata-messagepack-perl in /<> dpkg-source: info: unpacking libdata-messagepack-perl_1.00.orig.tar.gz dpkg-source: info: unpacking libdata-messagepack-perl_1.00-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series

Bug#950496: msgpack-c: FTBFS on 32-bit: error: narrowing conversion of ‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’}

Control: tag -1 fixed-upstream On Sun, Feb 02, 2020 at 04:47:26PM +0100, Andreas Beckmann wrote: > msgpack-c/experimental on all 32-bit architectures: > https://buildd.debian.org/status/package.php?p=msgpack-c&suite=experimental Yes, that and #950460 are the main reasons I haven't uploaded this t

Bug#930576: vim: Gdk-CRITICAL IA__gdk_drawable_get_size: assertion 'GDK_IS_DRAWABLE (drawable)' failed

On Mon, Oct 07, 2019 at 12:55:55PM +0200, Antoni Marcinek wrote: > I am running Debian 10 (stable) and I obtain this same error message. I > vaguely > remember that I had a similar issue with sid few years back. Does it also happen with the vim-gtk3 package, or only with vim-gtk? Make sure you'r

Bug#812421: apt: "apt upgrade" exits with "E: Broken packages" instead of upgrading

Control: found -1 1.8.4 On Sat, Jan 23, 2016 at 11:06:54AM -0500, James McCoy wrote: > "apt upgrade" is erroring out instead of letting me upgrade packages > uninvolved with the qt packages. I'm running into this problem again. I have the old (now removed from the ar

Bug#812421: apt: "apt upgrade" exits with "E: Broken packages" instead of upgrading

On Thu, Oct 10, 2019 at 08:13:51AM -0400, James McCoy wrote: > Control: found -1 1.8.4 > > On Sat, Jan 23, 2016 at 11:06:54AM -0500, James McCoy wrote: > > "apt upgrade" is erroring out instead of letting me upgrade packages > > uninvolved with the qt packages. >

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

Dropping debhelper and related bug, since this is just about libtermkey. On Sun, Dec 30, 2018 at 08:22:00PM +, Niels Thykier wrote: > Anyhow, on to the details I have found: > > * Only test case 05flags.t fails and only if stdin is a *readable* >non-tty (e.g. /dev/null, an empty file or

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Mon, Dec 31, 2018 at 04:38:10AM +, Steve McIntyre wrote: > I've been doing a full rebuild of the Debian archive, building all > source packages targeting armel and armhf using arm64 hardware. We are > planning in future to move all of our 32-bit armel/armhf builds to > using arm64 machines,

Bug#917592: libterm-termkey-perl: FTBFS (failing tests)

On Sun, Dec 30, 2018 at 09:30:34PM -0500, James McCoy wrote: > Dropping debhelper and related bug, since this is just about libtermkey. > > On Sun, Dec 30, 2018 at 08:22:00PM +, Niels Thykier wrote: > > Anyhow, on to the details I have found: > > > > * Only te

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Wed, Jan 02, 2019 at 06:53:29PM +, Steve McIntyre wrote: > Hi James, and Happy New Year to you and yours! Thanks! > On Mon, Dec 31, 2018 at 10:50:25AM -0500, James McCoy wrote: > >The "Test_compiler line 24" one is odd. All that test does is create a > >file

Bug#918454: vim should not Build-Depends: libtool-bin

On Sun, Jan 06, 2019 at 10:51:54AM +0100, Helmut Grohne wrote: > I see that you added a build dependency on libtool-bin. That's > unfortunate as we want to remove libtool-bin (not libtool) from the > archive. > > I'm hoping that we can still revert this part and find a better solution > as the rea

Bug#911944: neovim FTBFS: tests fail

Version: 0.3.2-1 On Sat, Nov 10, 2018 at 03:36:08PM -0500, James McCoy wrote: > On Sat, Nov 10, 2018 at 04:09:55PM +0100, Helmut Grohne wrote: > > I also tried in pbuilder and there I only got the utf_char2bytes > > failure, not the ones with check_cores. This hints that somethi

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Mon, Jan 07, 2019 at 10:04:30AM +, Edmund Grimley Evans wrote: > I'd guess this is a problem with the locale. In my case an unknown > locale adds 8, rather than 10, additional lines, but still: > > $ LANG=C ./foo.pl > Global symbol "$foo" requires explicit package name at ./foo.pl line 3. >

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Mon, Jan 07, 2019 at 09:08:37PM -0500, James McCoy wrote: > On Mon, Jan 07, 2019 at 10:04:30AM +, Edmund Grimley Evans wrote: > > I'd guess this is a problem with the locale. In my case an unknown > > locale adds 8, rather than 10, additional lines, but still: > &

<    6   7   8   9   10   11   12   13   14   >