Bug#862857: vim: LOG_ALERT unable to open gpm console, check your /dev filesystem!

Control: reassign -1 gpm 1.20.4-6.2 Control: merge 775443 -1 On Wed, May 17, 2017 at 05:12:55PM +, Alan Jenkins wrote: > This happens when running `vi` inside a systemd-nspawn container. > `vi` is able to run, but each time it logs three lines in > attention-getting RED (loglevel alert) in

Bug#849769: [mipsel]: string.sub sometimes returns incorrect slice

On Sat, Jan 14, 2017 at 02:55:22PM -0500, James McCoy wrote: > On Fri, Dec 30, 2016 at 02:25:27PM -0500, James McCoy wrote: > > Neovim's test suite was periodically failing on mipsel and after looking > > into it, it turns out that luajit sometimes incorrectly handles &

Bug#861168: qa.debian.org: msg parameter inserts extra line numbers

Control: retitle -1 [debsources] msg parameter displays extra line numbers when Javascript is disabled Control: tag -1 confirmed On Tue, Apr 25, 2017 at 05:57:48PM +0800, Paul Wise wrote: > Normally the cowsay code header looks like this: > >

Bug#860999: unblock: vim/2:8.0.0197-4 (pre-approval)

Control: tags -1 - moreinfo On Sun, Apr 23, 2017 at 03:57:05PM +0200, Ivo De Decker wrote: > On Sun, Apr 23, 2017 at 08:29:50AM -0400, James McCoy wrote: > > * Update Ubuntu release names in syntax highlighting files > > + Additionally, require word boundaries around re

Bug#860999: unblock: vim/2:8.0.0197-4 (pre-approval)

l Aardvark to deb{changelog,sources} syntax files. + * debsources.vim: Require word boundaries around distribution name. +(Closes: #859247) + * Set $TERM to a known sane value when running tests to avoid test failures +due to an unknown $TERM. + + -- James McCoy <james...@debian.org>

Bug#860242: unblock: neovim/0.1.7-4

On Thu, Apr 13, 2017 at 08:13:31AM -0400, James McCoy wrote: > Please unblock package neovim > > This upload includes fixes for CVE-2017-{5953,6349,6350}. > > unblock neovim/0.1.7-4 Ping? > diffstat for neovim-0.1.7 neovim-0.1

Bug#860723: vim-runtime: documentation bug in term.txt

On Wed, Apr 19, 2017 at 01:59:58PM +0200, Rhonda D'Vine wrote: > while trying to figure out why I don't get rgb color support in vim > inside tmux I stumbled upon a documentation bug. :) > > in term.txt there are these two lines: > > let _8f = "\[38:2:%lu:%lu:%lum" > let _8b

Bug#860263: gcc-7: False -Wimplicit-fallthrough when case has braces

Source: gcc-7 Version: 7-20170407-1 Severity: normal $ gcc-7 -Wextra -o foo foo.c foo.c: In function 'main': foo.c:6:9: warning: this statement may fall through [-Wimplicit-fallthrough=] argc = 0; ~^~~~ foo.c:9:3: note: here default: ^~~ $ cat foo.c int main(int argc, char

Bug#860242: unblock: neovim/0.1.7-4

x buffer overflows when +reading corrupted undo files. (CVE-2017-6349 & CVE-2017-6350) + + -- James McCoy <james...@debian.org> Mon, 10 Apr 2017 08:15:38 -0400 + neovim (0.1.7-3) unstable; urgency=medium * Disable global_spec.lua since it's rather flaky. diff -Nru neovim-0.1.7/d

Bug#851629: neovim-runtime: Translation files in wrong path

On Tue, Jan 17, 2017 at 09:54:55AM +0800, Boyuan Yang wrote: > .mo files are placed in wrong directories and is not working correctly. > > Examples: > > Bad: /usr/share/locale/zh_TW.UTF-8/LC_MESSAGES/nvim.mo > Good: /usr/share/locale/zh_TW/LC_MESSAGES/nvim.mo > > Bad:

Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy

On Fri, Apr 07, 2017 at 07:23:39AM -0400, G. Branden Robinson wrote: > At 2017-04-06T21:56:13-0400, James McCoy wrote: > > On Fri, Apr 07, 2017 at 12:54:19AM +0200, Francesco Poli wrote: > > > On Thu, 6 Apr 2017 15:06:17 -0400 G. Branden Robinson wrote: > > > > >

Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy

). That causes the syntax highlighting in Vim to get a little confused and enable some bold highlighting, which then causes the visual bell to turn everything bold. > At 2017-04-05T22:03:50-0400, James McCoy wrote: > > On Mon, Mar 20, 2017 at 10:29:20PM +0100, Francesco Poli (wintermute

Bug#858304: vim-runtime: markdown syntax highlighting (and possibly others) goes crazy and drives the terminal crazy

Control: tag -1 confirmed Control: reassign -1 xterm Control: retitle -1 Terminal stays bold after visual bell with bold text displayed On Mon, Mar 20, 2017 at 10:29:20PM +0100, Francesco Poli (wintermute) wrote: > I have experienced this bug for a fairly long time, when editing > markdown

Bug#856920: vim-gtk does not refresh window in full-screen mode with a tiling window manager when multiple tabs are used.

On Mon, Mar 06, 2017 at 09:57:29AM +0100, Francesco Paolo Lovergine wrote: > Package: vim-gtk Is this reproducible with vim-gtk3? > In order to reproduce the bug: > > - use a tiled window manager (wm): i'm using awesome for that, not sure about > others. I'm using i3. > - load vim-gtk in a

Bug#859496: /usr/bin/debsnap: debsnap cannot download binary packages

On Tue, Apr 04, 2017 at 01:46:43PM +0300, Alberto Garcia wrote: > I'm trying to download a binary package with debsnap but it fails all > the time. Well, not all the time. That's why it happens to work when you try it manually. > $ debsnap -a amd64 xterm > debsnap: fatal error at line 271: >

Bug#859426: vim: Vim 8 cannot handle 'etags' format any more

On Mon, Apr 03, 2017 at 02:17:11PM +0200, Alexander Burger wrote: > When the file "tags" (or also "TAGS") was created with the 'etags' command, > e.g. > >$ etags file.c Which etags is this? There are various packages that provide the etags name. “update-alternatives --query etags” will

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

On Sat, Apr 01, 2017 at 02:21:25PM -0400, PICCORO McKAY Lenz wrote: > 2017-04-01 13:53 GMT-04:00 James McCoy <james...@debian.org>: >   makes the package in question unusable or mostly so, or causes data >   loss, or introduces a security hole allowing access

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

On Sat, Apr 01, 2017 at 10:28:34AM -0400, PICCORO McKAY Lenz wrote: > 2017-04-01 8:33 GMT-04:00 James McCoy <james...@debian.org>: > > Given that there's an easy workaround (set http-chunked-requests to > off) I'm lowering the severity of the bug. > > >

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

Control: severity -1 normal On Wed, Mar 29, 2017 at 08:21:23AM -0400, PICCORO McKAY Lenz wrote: > 2017-03-28 23:04 GMT-04:00 James McCoy <james...@debian.org>: > > This discussion is specifically talking about when a 411 status is > returned, not a 413. > > the

Bug#858671: bugs.debian.org: Handle "source" in {split,join}_status_fields

On Mar 31, 2017 10:25, "Don Armstrong" wrote: On Thu, 30 Mar 2017, Don Armstrong wrote: > I've tweaked that, which should fix this issue too. [In > master@7c98c4f499ca]. Could you test to see if this works now? [Unfortunately, testing the source versions is a bit difficult in

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

On Tue, Mar 28, 2017 at 10:50:20PM -0400, PICCORO McKAY Lenz wrote: > I cited why must be set for 1.8 and q.9 until 1.10 released: > > Users who wish to avoid the additional request may set that option to yes or  > no >  in order to short-circuit the additional request and avoid making it. This

Bug#858955: subversion: Error unable to retrieve any working copy after upgrade/install

On Tue, Mar 28, 2017 at 07:34:46PM -0400, PICCORO McKAY Lenz wrote: > Package: subversion > Version: 1.8.10-6+deb8u4 > Severity: grave > Justification: renders package unusable > > Dear Maintainer,the current package in debian are broken > i upgrade clients to jeesie > and now could'n chekout

Bug#858671: bugs.debian.org: Handle "source" in {split,join}_status_fields

4 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) >From cb8b389587012afb051c66705e082ac1873af519 Mon Sep 17 00:00:00 2001 From: James McCoy <james...@debian.org> Date: Fri, 24 Mar

Bug#858526: ublock-origin: Build the chromium extension

.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) From 66aef6cf4c1bd2eb0a951df84c2ba185c4096ab7 Mon Sep 17 00:00:00 2001 From: James McCoy <james...@debian.org> Date: Wed, 22 Mar 2017 21:01:28 -0400 Subject: [PATCH] Add support

Bug#857964: devscripts: debsign can't find buildinfo if changes file is not in $(pwd)

On Thu, Mar 16, 2017 at 10:31:00PM +0100, gregor herrmann wrote: > On Thu, 16 Mar 2017 18:32:07 +, Simon McVittie wrote: > > > Package: devscripts > > Version: 2.17.3 > > Severity: normal > > > > I'm using a build tool (vectis, #843486) that outputs all built files into a > > newly created

Bug#857964: devscripts: debsign can't find buildinfo if changes file is not in $(pwd)

already signed. Would you like to use the current signature? [Yn]n unsignfile serf/serf_1.3.9-1.dsc signfile dsc serf/serf_1.3.9-1.dsc James McCoy <james...@debian.org> fixup_buildinfo serf/serf_1.3.9-1.dsc serf/serf_1.3.9-1_amd64.buildinfo signfile buildinfo serf/

Bug#857716: devscripts: debsign -r doesn't work any more

On Tue, Mar 14, 2017 at 09:43:01AM +0100, Samuel Thibault wrote: > Since the upgrade to 2.17.2 (2.17.1 works fine), > > debsign -r mybox build/foo.changes > > doesn't even try to run scp, it immediately errors out: > > sed: can't read foo.changes: No such file or directory I'm working on a

Bug#855282: debsign: support .buildinfo files

On Mon, Mar 06, 2017 at 11:45:20PM -0500, James McCoy wrote: > On Thu, Feb 16, 2017 at 05:23:00PM +, Ximin Luo wrote: > > I've done an initial implementation here: > > > > https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debsign-buildinfo &

Bug#857041: jessie-pu: package vim/2:7.4.488-7+deb8u3

(2:7.4.488-7+deb8u3) jessie; urgency=medium + + * Backport upstream patches v8.0.0377 & v8.0.0378, to fix buffer overflows +when reading corrupted undo files. (Closes: #856266, CVE-2017-6349, +CVE-2017-6350) + + -- James McCoy <james...@debian.org> Mon, 06 Mar 2017 23:52:28 -0

Bug#855282: debsign: support .buildinfo files

On Thu, Feb 16, 2017 at 05:23:00PM +, Ximin Luo wrote: > I've done an initial implementation here: > > https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debsign-buildinfo > > Please review! This was merged and uploaded in 2.17.2. However, now I see that buildinfo files

Bug#857007: unblock: devscripts/2.17.2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package devscripts devscripts (2.17.2) unstable; urgency=medium [ James McCoy ] * deb-reversion: + Correct parsing of long-form --new-version switch. (Closes

Bug#855282: debsign: support .buildinfo files

On Wed, Mar 01, 2017 at 02:58:29AM +0100, Guillem Jover wrote: > Hi! > > On Fri, 2017-02-17 at 06:08:25 +0100, Guillem Jover wrote: > > On Thu, 2017-02-16 at 17:23:00 +, Ximin Luo wrote: > > > Control: tags + patch > > > > > I've done an initial implementation here: > > > > > >

Bug#856273: vim: explain how the various vimrc files are processed

l). In order to disable the loading of defaults.vim, add let g:skip_defaults_vim = 1 to /etc/vim/vimrc(.local). -- James McCoy <james...@debian.org> Tue, 04 Oct 2016 20:28:02 -0400 > However, the mouse was STILL being hijacked, and ":set mouse" sh

Bug#855433: devscripts: wrap-and-sort: Add missing build dependency fields

On Sun, Feb 26, 2017 at 08:07:30PM +0100, Dominique Dumont wrote: > On Saturday, 18 February 2017 01:56:37 CET Guillem Jover wrote: > > +"Build-Depends-Arch", > > I'm confused... > > Debian policy [1] mentions "There is no Build-Depends-Arch; this role is > essentially met with

Bug#856156: vim-gtk: launching gvim as root from terminal crashes X server

Control: reassign -1 xserver-xorg-core 2:1.19.1-4 Control: affects -1 vim-gtk Reassigning to xserver-xorg-core. Vim's gtk2 code hasn't changed significantly in some time, so it's more likely an issue with the glamor driver. On Sat, Feb 25, 2017 at 12:54:21PM -0500, Bruno Dantas wrote: > Either

Bug#855644: devscripts: grep-excuses doesn't work with maintainer name

On Fri, Feb 24, 2017 at 11:59:56PM -0500, James McCoy wrote: > I'm splitting this bug into two pieces. One, for the release team, to > fix the generation of the HTML so grep-excuses is fixed now, and another > for grep-excuses to start consuming YAML instead of parsing HTML. As far as u

Bug#855644: devscripts: grep-excuses doesn't work with maintainer name

rewrite of that part of grep-excuses. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB >From a04d730bb7ba63df17117c3bfc4afd93bab9f37c Mon Sep 17 00:00:00 2001 From: James McCoy <james...@debian.org> Date: Fri, 24 Feb 2017 23:43:57 -0500 Subject: [PATCH] excuse:

Bug#679645: devscripts: debuild does not properly forward coloured output

On Thu, Feb 23, 2017 at 11:55:04AM +, Martin-Éric Racine wrote: > Basically, if > dpkg-buildpackage finds the terminal and enables colors accordingly, > there is no reason for debuild to fail at finding the terminal and > asking dpkg to run in colorized mode. debuild isn't failing at that.

Bug#853920: unblock: devscripts/2.17.1

wrapper, pass + --set-envvar=NO_PKG_MANGLE=1 to debuild, and pass -U to debchange. + * debian/tests/control: ++ Depend on build-essential. + + [ James McCoy ] + * test_package_lifecycle: ++ Ignore debhelper's new "create-stamp" output to fix the test failure. + (Close

Bug#852815: /usr/bin/nm-online: "nm-online -x -q" always exits 1 (offline)

Control: tags -1 fixed-upstream On Fri, Jan 27, 2017 at 04:21:35PM -0500, James McCoy wrote: > On Fri, Jan 27, 2017 at 01:20:06PM -0500, James McCoy wrote: > > Attached patch explicitly returns from quit_if_connected after setting > > retval. This fixes the behavior for me. >

Bug#852815: /usr/bin/nm-online: "nm-online -x -q" always exits 1 (offline)

On Fri, Jan 27, 2017 at 01:20:06PM -0500, James McCoy wrote: > Attached patch explicitly returns from quit_if_connected after setting > retval. This fixes the behavior for me. I've forwarded the patch upstream, too. Just waiting for my message to be moderated. Cheers, -- James GPG Key:

Bug#852815: /usr/bin/nm-online: "nm-online -x -q" always exits 1 (offline)

Control: tags 852815 patch On Fri, Jan 27, 2017 at 12:31:59PM -0500, James McCoy wrote: > On Fri, Jan 27, 2017 at 10:12:18AM -0500, James McCoy wrote: > > I've been using "nm-online -x -q" as a test condition for a cron job, > > and as of the update to 1.6.0-1, this alwa

Bug#852815: /usr/bin/nm-online: "nm-online -x -q" always exits 1 (offline)

On Fri, Jan 27, 2017 at 10:12:18AM -0500, James McCoy wrote: > I've been using "nm-online -x -q" as a test condition for a cron job, > and as of the update to 1.6.0-1, this always exits with 1 even when > "nmcli general status" shows State=connected, Connectivity=full

Bug#852815: /usr/bin/nm-online: "nm-online -x -q" always exits 1 (offline)

Package: network-manager Version: 1.6.0-1 Severity: normal File: /usr/bin/nm-online I've been using "nm-online -x -q" as a test condition for a cron job, and as of the update to 1.6.0-1, this always exits with 1 even when "nmcli general status" shows State=connected, Connectivity=full.

Bug#835522: closed by Héctor Orón Martínez <zu...@debian.org> (Bug#835522: fixed in gdb 7.12-2)

Control: found -1 7.12-4 On Wed, Dec 14, 2016 at 11:57:14AM +, Debian Bug Tracking System wrote: > Changes: > gdb (7.12-2) unstable; urgency=medium > . >* debian/control*: > - add mipsel64 arch to gdbserver. This is actually spelled mips64el, so the bug isn't fixed. Cheers, --

Bug#849769: [mipsel]: string.sub sometimes returns incorrect slice

On Fri, Dec 30, 2016 at 02:25:27PM -0500, James McCoy wrote: > Neovim's test suite was periodically failing on mipsel and after looking > into it, it turns out that luajit sometimes incorrectly handles > str:sub(i, j). This was fixed upstream in 62af10152433c45e5d83e442538fabf1f57f189b

Bug#850684: devscripts: Remove ‘dcut’ Bash command completion script

On Mon, Jan 09, 2017 at 10:04:41PM +1100, Ben Finney wrote: > The Bash command completion script ‘dcut’ should rather be installed > by the package which provides the ‘dcut’ command. While I agree devscripts isn't the right place to provide the completion, src:dput isn't the only package to

Bug#845659: debpatch: New script, "Apply a debdiff to a Debian source package"

On Thu, Jan 05, 2017 at 04:18:00PM +, Ximin Luo wrote: > Ximin Luo: > > As part of the Reproducible Builds effort, I've written a tool called > > debpatch(1), see the branch here: > > [..] > > Hi devscripts team, > > Any news on this? Apologies for not giving this a review sooner. > I

Bug#849769: [mipsel]: string.sub sometimes returns incorrect slice

Package: luajit Version: 2.0.4+dfsg-1 Severity: important Dear Maintainer, Neovim's test suite was periodically failing on mipsel and after looking into it, it turns out that luajit sometimes incorrectly handles str:sub(i, j). I instrumented the test to log the i, j, and size of the returned

Bug#849465: bts version: check arguments

Control: merge 597928 -1 On Tue, Dec 27, 2016 at 09:10:28PM +0800, 積丹尼 Dan Jacobson wrote: > Perhaps check if the user has given extra arguments to version, and at > least return non-zero. > > $ bts version 99 1.2.3; echo $? > bts version 2.16.13 > Copyright (C) 2001-2003 by Joey Hess

Bug#848663: vim: sh syntax highlighting of command substitution $() is wrong

On Mon, Dec 19, 2016 at 11:55:50AM +0100, Bas Zoetekouw wrote: > Vim's currenr behaviour for syntax highlighting of shell scripts (with > #!/bin/sh and /bin/sh pointing to dash) is to mark command > substititions using the $(foo) construction as an error. Not that I can see. > This is incorrect,

Bug#848591: wanna-build: Only enable --deb-emulate-sbuild for non-backports builds

kages/python-tornado.git/tree/debian/control#n24 > > python-tornado build-depends on missing: > - python3:arm64 (>= 3.5) > > So jessie-backports buildd have this "bug" too. On Sun, Dec 18, 2016 at 10:04:46AM -0500, James McCoy wrote: > On Sun, Dec 18, 2016 at 02:26:0

Bug#845685: neovim-qt: FTBFS on kFreeBSD: tst_neovimconnector fails

On Thu, Dec 15, 2016 at 11:03:40PM -0500, Aaron M. Ucko wrote: > James McCoy <james...@debian.org> writes: > > > As far as I can tell, what's happening is the async network connection > > that's started by the connectToNeovim call has already errored out by > > the t

Bug#845685: neovim-qt: FTBFS on kFreeBSD: tst_neovimconnector fails

On Fri, Nov 25, 2016 at 03:24:23PM -0500, Aaron M. Ucko wrote: > The kFreeBSD build of neovim-qt failed: > > Start 2: tst_neovimconnector >2/12 Test #2: tst_neovimconnector ..***Failed 15.12 sec > * Start testing of NeovimQt::Test * > Config: Using

Bug#848100: neovim-qt: Please install as alternative for "gvim"

On Wed, Dec 14, 2016 at 07:25:11AM +0100, Ph. Marek wrote: > Please install a gvim alternative: > # update-alternatives --install /usr/bin/gvim gvim /usr/bin/nvim-qt 50 Sounds reasonable. jpleau is looking into that. > BTW, the initial size of the nvim-qt window is ~9 by 4 characters for

Bug#846993: vim-gtk3: vimdiff does not compare last lines if editing changes lines

Control: tag -1 upstream patch Control: forwarded -1 https://github.com/vim/vim/pull/1329 On Tue, Dec 06, 2016 at 09:53:43PM +0100, Helge Kreutzmann wrote: > Hello James, > On Sun, Dec 04, 2016 at 08:22:34PM -0500, James McCoy wrote: > > On Sun, Dec 04, 2016 at 09:25:41PM +0100, Helg

Bug#847933: vim: please update supported Ubuntu series

On Mon, Dec 12, 2016 at 03:57:12PM +0200, Graham Inggs wrote: > Please consider the attached patch for dropping Vivid and Wily from the list > of supported Ubuntu series. I intentionally stopped doing that, actually. Those old release names aren't invalid, they're just not currently targeted for

Bug#847541: Update for new programming language sections

On Thu, Dec 08, 2016 at 08:51:39PM -0800, Josh Triplett wrote: > The attached patch provides an update with new archive sections for > programming > language packages. See https://bugs.debian.org/753480 and > https://bugs.debian.org/845576 for more on the new sections. ftpmaster has > approved

Bug#847539: Update for new programming language sections

On Thu, Dec 08, 2016 at 08:41:06PM -0800, Josh Triplett wrote: > The attached patch provides an update with new archive sections for > programming > language packages. See https://bugs.debian.org/753480 and > https://bugs.debian.org/845576 for more on the new sections. ftpmaster has > approved

Bug#847168: devscripts: debuild fails when lintian fails, regression since 2.16.9

On Tue, Dec 06, 2016 at 09:16:33AM +0100, Raphaël Hertzog wrote: > Since debuild now relies on dpkg-buildpackage's hook to run lintian, > a failing lintian fails the whole build process. This was not the case > before 2.16.9. So this is either a regression or a annoying new feature. It was an

Bug#846711: git-build-recipe: FTBFS: Tests failures

On Tue, Dec 06, 2016 at 10:39:44AM +, Colin Watson wrote: > […] > subprocess.CalledProcessError: Command '['/usr/bin/debuild', '--tgz-check', > '-i', '-I', '-S', '-uc', '-us']' returned non-zero exit status 29 > }}} > > stdout: {{{ > dpkg-buildpackage -rfakeroot -us -uc -i -I -S

Bug#846312: vim package fails to build with missing man files

On Sun, Dec 04, 2016 at 11:07:28PM +, David Barnett wrote: > Turns out the problem was that I was building with make 3.81, which doesn't > support the trailing "=" syntax in "define VAR =" (and for some reason > silently > ignores the whole block?). Thanks for tracking that down! I didn't

Bug#846993: vim-gtk3: vimdiff does not compare last lines if editing changes lines

On Sun, Dec 04, 2016 at 09:25:41PM +0100, Helge Kreutzmann wrote: > The last two lines are now identical (they only contain the word > »rows«), but vimdiff (in the current version) does not show this. > > (This is an artifical case, ordinarily the last line contains many > words, so it is not

Bug#846788: neovim-runtime: man plugin breaks startup

On Sat, Dec 03, 2016 at 08:10:24PM +0100, Philipp Marek wrote: > Hmmm.. > I had a > > runtime ftplugin/man.vim > > in ~/.config/nvim/init.vim, but up to and including 0.1.6-5 that never > hurt. Commenting that line out makes 0.1.7 work too. > > I bind "K" to ":Man"; guess that I got it

Bug#846863: /usr/bin/debuild: debuild: pass lintian options to dpkg-buildpackage

On Sat, Dec 03, 2016 at 07:56:00PM +, Niels Thykier wrote: > On Sat, 03 Dec 2016 20:49:34 +0100 Vincent Danjean > wrote: > > debuild is passing lintian options to dpkg-buildpackage which, of course, > > do > > not recognize these options and fail: > > > > [...] > > >

Bug#846788: neovim-runtime: man plugin breaks startup

On Sat, Dec 03, 2016 at 12:59:20PM +0100, Ph. Marek wrote: > With this version, starting nvim with a file on the cmdline is broken. It works fine for me. Can you be more explicit about how you're running nvim? Is it only certain files that exhibit this behavior? What if you use "nvim -u NORC"?

Bug#846312: vim package fails to build with missing man files

On Wed, Nov 30, 2016 at 06:54:28AM +, David Barnett wrote: > When I try to build the v8.0.0095-1 tag from https://anonscm.debian.org/cgit/ > pkg-vim/vim.git using pbuilder, I get an error from the dh_install command: >   dh_install >   cp: cannot stat

Bug#846192: devscripts: lintian called from debuild always fail (gave error exit status 1)

On Tue, Nov 29, 2016 at 08:51:21AM +0100, Christian Marillat wrote: > From several sources I see this error : > > dpkg-buildpackage: info: full upload (original source is included) > dpkg-buildpackage: info: running hook check > lintian ../motioneye-dmo_0.35.1-dmo1_i386.changes > E:

Bug#845610: don't add 'New upstream release' to changelog when -b option is given

Control: merge 842468 -1 Control: retitle 842468 [uupdate] Omit 'New upstream release' entry when version matches changelog (with -b) On Fri, Nov 25, 2016 at 12:15:15PM +0530, Pirate Praveen wrote: > We commonly use uupdate -b in npm2deb to add generated debian folder > with upstream tarball

Bug#845628: devscripts: DEBUILD_LINTIAN_HOOK no more works (at least if it contains shell meta characters)

On Fri, Nov 25, 2016 at 06:09:02PM +0100, Guillem Jover wrote: > Hi! > > On Fri, 2016-11-25 at 12:32:18 +0100, Axel Beckert wrote: > > Package: devscripts > > Version: 2.16.9 > > File: /usr/bin/debuild > > > since the recent slimming of debuild, DEBUILD_LINTIAN_HOOK no more works > > for me. > >

Bug#789581: marked as pending

On Thu, Nov 24, 2016 at 01:37:05PM -0500, James McCoy wrote: > On Thu, Nov 24, 2016 at 05:41:21AM +0100, Guillem Jover wrote: > > Hi! > > > > On Wed, 2016-11-23 at 18:11:37 +, James McCoy wrote: > > > commit 607c5911b44ca61cf352e80397b5707ee23d9eec > > &

Bug#789581: marked as pending

On Thu, Nov 24, 2016 at 05:41:21AM +0100, Guillem Jover wrote: > Hi! > > On Wed, 2016-11-23 at 18:11:37 +0000, James McCoy wrote: > > commit 607c5911b44ca61cf352e80397b5707ee23d9eec > > Merge: 1f82d5b 064dc31 > > Author: James McCoy <james...@debian.org> > >

Bug#845566: devscripts: debclean is broken

On Thu, Nov 24, 2016 at 06:40:42PM +0100, Christian Marillat wrote: > I don't know who is the guilty (debuild or dpkg-buildpackage) but debclean > doesn't work : > > $ LANG=C debclean > Cleaning in directory . > dpkg-buildpackage -rfakeroot -us -uc -j10 clean

Bug#762715: updates to dch --lts

On Mon, Oct 31, 2016 at 12:10:37PM -0400, Antoine Beaupré wrote: > On 2016-10-28 20:10:43, Holger Levsen wrote: > >> Since this may change again in the future before this issue is resolved, > >> maybe it's better to just refer to the LTS notes here: > >>

Bug#834317: devscripts: please warn if DEBUILD_DPKG_BUILDPACKAGE_OPTS contains "-i -I" or similar

On Sun, Aug 14, 2016 at 01:43:27PM +0100, Chris Lamb wrote: > If you take a look at: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735377#44 > > Here, Holger hit a problem in the past because he had "-i -I" in the > DEBUILD_DPKG_BUILDPACKAGE_OPTS variable instead of in (I guess) >

Bug#844910: devscripts: FTBFS: Tests failures

Control: owner -1 ! On Sat, Nov 19, 2016 at 08:01:03AM +0100, Lucas Nussbaum wrote: > Relevant part (hopefully): > > test_dscextractChangelog > > test_debchange > > test_list_unreleased > > test_debuild2 > > ASSERT:standard output of debuild --no-conf --no-lintian > > --preserve-envvar=PATH

Bug#843470: mergechanges: doesn't know about new .buildinfo files

On Tue, Nov 22, 2016 at 08:32:21PM +, Simon McVittie wrote: > On Tue, 22 Nov 2016 at 15:05:10 -0500, James McCoy wrote: > > Shouldn't it always be kept in the resulting changes file? It's just > > build metadata like the changes/dsc files. > > Hmm. I think it would be

Bug#843470: mergechanges: doesn't know about new .buildinfo files

On Sun, Nov 20, 2016 at 05:05:16PM +, Simon McVittie wrote: > From 2d7b8d45f23eb59e32c2350fc66943db7431a96e Mon Sep 17 00:00:00 2001 > From: Simon McVittie > Date: Sun, 20 Nov 2016 16:32:53 + > Subject: [PATCH] mergechanges: treat *.buildinfo like *.deb for --indep, >

Bug#845273: /usr/bin/mbsync: Quiet mode is noisy after upgrade to 1.2.1

Package: isync Version: 1.2.1-2 Severity: normal File: /usr/bin/mbsync Since the upgrade, I now get one of two "errors" every time I run “mbsync -a -q”. Socket error: secure read from imap.gmail.com (ip.a.dd.r:993): Success Error decompressing data from imap.gmail.com (ip.a.dd.r:993): (null)

Bug#845066: libmsgpack-dev: please release new version 2.0.0 (release 2016-06-26)

On Sat, Nov 19, 2016 at 08:15:24PM -0500, Nick Black wrote: > msgpack-c version 2.0.0 was released in June 26th of this year (2016), > and provides several useful new interfaces, including > msgpack_unpacker_next_with_size(). It would be nice if we could get a > newer build, thanks! It would also

Bug#844286: grep: Non-deterministic behavior when output redirected to /dev/null

Control: severity -1 important On Sun, Nov 13, 2016 at 10:38:37PM -0500, James McCoy wrote: > On Sun, Nov 13, 2016 at 08:40:02PM -0500, James McCoy wrote: > > The relevant part of the script is just looking for whether patch > > numbers are applied or marked NA in neovim's src

Bug#844286: grep: Non-deterministic behavior when output redirected to /dev/null

On Sun, Nov 13, 2016 at 08:40:02PM -0500, James McCoy wrote: > The relevant part of the script is just looking for whether patch > numbers are applied or marked NA in neovim's src/nvim/version.c: > > is_missing="$(sed -n '/static int included_patches/,/}/p' > "${

Bug#844286: grep: Non-deterministic behavior when output redirected to /dev/null

Package: grep Version: 2.26-1 Severity: grave Tags: upstream Justification: renders package unusable Upstream commit af6af288 causes inconsistent results when output is redirected to /dev/null. I'm setting this to grave because grep is a very common glue and if its results aren't reliable, then

Bug#844164: vim: since version 8, vim ignores indentation settings in /etc/vim/vimrc.local

On Sat, Nov 12, 2016 at 11:12:09PM +0100, Mikulas Patocka wrote: > I see, but it is annoying to the users who upgrade the Debian distribution > and who are used to the old settings. That's why there's a NEWS entry to tell them about the change and how they can change the behavior. Cheers, --

Bug#842515: github-backup: FTBFS with newer directory

On Sat, Oct 29, 2016 at 10:46:24PM +, Clint Adams wrote: > Because we've updated GHC to 8.0, the version of the directory library > has also been updated, and you'll need something like > https://github.com/joeyh/github-backup/commit/848f6b64f75f4d267ba364405fb2a7b284969020 That's already

Bug#843146: /usr/bin/vim.gtk3: grey rectangle, no text shown or insertable

Control: reassign -1 libgtk-3-0 3.22.2-1 Control: forcemerge 842070 -1 On Fri, Nov 04, 2016 at 11:24:32AM +0100, Ph. Marek wrote: > # vim.gtk3 -g -u NONE -U NONE -N > gives me a window, but where the text should be only a grey rectangle is > visible. No text shown (expected version info etc.),

Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed

On Fri, Nov 04, 2016 at 01:39:35PM +, Steven Chamberlain wrote: > Hi, > > If you've no objection, I may build vim on the kfreebsd-* porterboxes > with DEB_BUILD_OPTIONS=nocheck, and binNMU the result. What about just disabling the Perl bindings on kfreebsd-any for now? Cheers, -- James GPG

Bug#842990: vim-gtk3: gvim has the smallest possible text window

Control: reassign -1 libgtk-3-0 3.22.2-1 Control: forcemerge 842070 -1 On Wed, Nov 02, 2016 at 09:11:13PM +0100, Ayke van Laethem wrote: > When running gvim (from the vim-gtk3 package), the whole text window is > invisible. It looks like it has shrunk so small to be unusable. See the > attached

Bug#842833: vim-gtk3: Default vim does not allow pasting with mouse as root

On Wed, Nov 02, 2016 at 06:43:07PM +0100, Helge Kreutzmann wrote: > Hello James, > On Tue, Nov 01, 2016 at 07:32:53PM -0400, James McCoy wrote: > > Please see ":help defaults.vim" for more information, including how to > > disable loading the file in the system vimrc. &

Bug#842819: vim-gtk3: gvim window is miss displayed

Control: reassign -1 libgtk-3-0 3.22.2-1 Control: forcemerge 842070 -1 On Tue, Nov 01, 2016 at 02:32:37PM +0100, gpe92 wrote: >* What led up to the situation? >launch gvim >* What was the outcome of this action? > >The gvim window is miss displayed an unusable (see attached >

Bug#842829: UDD/uscan: devscripts needs to be upgraded to avoid some failures

On Nov 1, 2016 11:33, "Lucas Nussbaum" wrote: > I tried with the first package listed. It works fine with devscripts > 2.16.8 (in testing), but not with 2.16.4~bpo8+1 (in stable-bpo, and > installed on ullmann.debian.org). > > To fix that, an update of that backport is needed.

Bug#842192: #842192: vim-gtk3: latest updates broke vim.gtk3

Control: reassign -1 libgtk-3-0 3.22.2-1 Control: forcemerge 842070 842192 On Sun, Oct 30, 2016 at 03:19:29AM +0100, Thilo Six wrote: > James McCoy schrieb/wrote: > -- -- > > > If you downgrade libgtk-3-0 to 3.22.1-1, does that fix the problem? > > Yes. > > Install

Bug#842622: libvterm: please make the build reproducible

On Sun, Oct 30, 2016 at 09:58:21PM +0100, Reiner Herrmann wrote: > While working on the "reproducible builds" effort [1], we have noticed > that libvterm could not be built reproducibly. > During build the object files are linked in random order. Thanks. I had sent a similar patch[0] upstream

Bug#842623: w3m: "stack smashing detected" crash when running "w3m -dump bar.html"

Package: w3m Version: 0.5.3-31 Severity: important Attached bar.html is a minimized version of the html file that original caused the crash when running "w3m -dump bar.html". Note that no crash occurs when running "w3m bar.html". Attached bt.txt.gz shows the full backtrace when this occurs. --

Bug#842192: #842192: vim-gtk3: latest updates broke vim.gtk3

On Sat, Oct 29, 2016 at 05:01:28PM +0200, Thilo Six wrote: > Hello Matteo, > Hello James-San, > > >> This looks like a duplicate of #842070. Can you confirm that you're seeing > >> the > >> same error messages when lauching gvim from a terminal? > >> > >> https://bugs.debian.org/842070 > > > >

Bug#841910: uscan behaviour on multiple signatures

Control: retitle -1 [uscan] Add an exit status to indicate gpgv failure On Mon, Oct 24, 2016 at 01:25:03PM +0200, Bernhard Schmidt wrote: > Asterisk upstream sources are signed by several keys, see for example > >

Bug#841311: mk-build-deps: Please mark dependencies as auto-installed

On Wed, Oct 19, 2016 at 04:30:00PM +0200, Michael Biebl wrote: > when installing build-dependencies of a package, I usually use > (sudo) mk-build-depends -i > > All the dependencies that are installed by that command are marked as > manually installed. They shouldn't be. That didn't happen with

Bug#841235: /etc/vim/vimrc: Remove some obsolete comments from /etc/vim/vimrc

On Tue, Oct 18, 2016 at 07:55:43PM +0100, Sam Morris wrote: > Here is a patch to remove some obsolete comments from /etc/vim/vimrc. I > have removed the lines that suggest the user enable things that have > already been enabled by defaults.vim. Well, defaults.vim is _only_ loaded if a user vimrc

Bug#841149: devscripts: Improvements for debrepro script

Thanks for the patches! I think the first patch is straight forward enough. I'll let Antonio comment on whether he wants to apply the other two. I just had one comment, inline. > From 607b2b8f5c12377efe9b81e4bdf8105a3f2a6c0c Mon Sep 17 00:00:00 2001 > From: Guillem Jover >

Bug#827319: vim: FTBFS[alpha,kfreebsd-*]: Test_tagcase() failed

Control: tag -1 help On Sun, Oct 16, 2016 at 12:27:13AM +0100, Steven Chamberlain wrote: > Hi! > > I was about finished for the night, but then I thought to recompile > option.c this way: > > $ cd src/vim-gtk > $ touch option.c > $ make PERL_CFLAGS="$(perl -MExtUtils::Embed -e ccopts) -g -O0 >

<    1   2   3   4   5   6   7   8   9   10   >