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#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 d

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

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

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#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

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-debcherry

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

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 <james...@debian.org> Date: Tue, 16 Jan 2018 07:31:37 -0500 Subject: [PATCH]

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

Package: wnpp Severity: wishlist Owner: James McCoy <james...@debian.org> * Package name: libtickit Version : 0.2 Upstream Author : Paul Evans <leon...@leonerd.org.uk> * URL : http://www.leonerd.org.uk/code/libtickit/ * License : MIT Program

Bug#886230: vim: highlight for two more debian/control fields

On Wed, Jan 03, 2018 at 11:17:51AM +0100, Mattia Rizzolo wrote: > There are two more fields that slipped off of deb-src-control(5), but > are going to be added in the next dpkg upload, please add them to the > highlighter rules. Thanks for the heads up. > For some reason "Testsuite" is not

Bug#885936: vim-runtime: please support TeX and YAML syntax highlighting within syntax/markdown.vim

On Mon, Jan 01, 2018 at 11:38:42AM +0100, Francesco Poli wrote: > On Sun, 31 Dec 2017 23:38:36 -0500 James McCoy wrote: > > On Sun, Dec 31, 2017 at 03:50:01PM +0100, Francesco Poli (wintermute) wrote: > > > File runtime/syntax/markdown.vim supports highlighting the markdown >

Bug#885936: vim-runtime: please support TeX and YAML syntax highlighting within syntax/markdown.vim

Control: tag -1 upstream Control: tag -1 - patch On Sun, Dec 31, 2017 at 03:50:01PM +0100, Francesco Poli (wintermute) wrote: > File runtime/syntax/markdown.vim supports highlighting the markdown > syntax, but fails to support a pair of useful extensions of the > markdown language: the [TeX Math]

Bug#885938: Parameter substitution highlighting when dash provides /bin/sh

Hi Charles, Given this shell script #!/bin/sh echo ${FOO#bar} the # is highlighted as an error when /bin/sh is provided by dash. This is a similar issue to one I had reported before with process substitution. That was fixed by adding an '|| exists("b:is_posix")' check before defining

Bug#884798: lintian could complain about pkg-config uses that fail to use $ac_tool_prefix

On Tue, Dec 19, 2017 at 08:56:20PM +0100, Helmut Grohne wrote: > A slightly better way would be using AC_PATH_TOOL (with the same > arguments) and the only difference here is considering $ac_tool_prefix. > The recommended way is using the PKG_PROG_PKG_CONFIG macro from > pkg-config tough. This

Bug#884495: vim: please support 'javascript' as a valid Debian section in the highligher rules

On Fri, Dec 15, 2017 at 10:07:44PM +0100, Mattia Rizzolo wrote: > 'Section: javascript' in d/control is currently marked as half an error > ('java' being right, and 'script' being error), see the attached > screenshot. I botched that again? :-( I see the problem. I'll get it fixed soon.

Bug#883610: git-hub: Please package new upstream version

Package: git-hub Version: 0.11.1-1 Severity: wishlist I attempted to use "git hub pull checkout ##" in a repo and ran into an ugly traceback. After doing some investigation, this turned out to be fixed by , which is included in v0.11.2 and

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:

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 an oversigh

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

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

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

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

(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 <james...@jamessan.com> Date: Fri, 20 Oct 2017 15:40:02 -0400 Subjec

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#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

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

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#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

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

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 + + -- James McCoy <james...@debian.org>

Bug#867720: marked as pending

On Sep 30, 2017 08:00, "Salvatore Bonaccorso" <car...@debian.org> 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 > > --

Bug#866791: libdata-messagepack-perl: FTBFS against msgpack-c 2.x

Control: severity -1 serious Control: tag -1 patch On Sat, Jul 01, 2017 at 02:11:20PM -0400, James McCoy wrote: > While performing rebuilds of packages which Build-Depend on libmsgpack-dev > with > the 2.x version in experimental, I found that libdata-messagepack-perl FTBFS: >

Bug#866796: ring: FTBFS against msgpack-c 2.x

Control: severity -1 serious Control: tag -1 patch On Mon, Aug 21, 2017 at 09:43:25PM -0400, James McCoy wrote: > On Sat, Jul 01, 2017 at 03:14:05PM -0400, James McCoy wrote: > > While performing rebuilds of packages which Build-Depend on > > libmsgpack-dev with the 2.x version in

Bug#875976: luajit: Please enable mips64el packages

Source: luajit Version: 2.1.0~beta3+dfsg-2 Severity: normal libluajit-5.1-dev and libluajit-5.1-2 are currently missing mips64el in their Architecture list. I was able to successfully build the package on eller.d.o, modulo a new symbol. Is there anything preventing this from being enabled? ...

Bug#875677: devscripts: mk-build-deps creates the build-dep package in the wrong directory

Control: reassign -1 equivs 2.1.0 Control: affects -1 + devscripts On Wed, Sep 13, 2017 at 02:26:55PM +0200, Jiri Palecek wrote: > while making a build-dep package, mk-build-deps writes: > > dpkg-deb: vytvářím balík ,,kwin-build-deps" v > ,,../kwin-build-deps_5.10.5-2_i386.deb". > > The

Bug#873755: vim-runtime: Perl plugin breaks Python keyword highlighting

Control: tag -1 fixed-upstream On Wed, Aug 30, 2017 at 07:06:33PM +0200, Jakub Wilk wrote: > The Perl filetype plugin breaks Python keyword highlighting. > To reproduce, run: > >vim -u NONE -U NONE -c 'syntax on' -c 'filetype plugin indent on' -c 'e > foo.pm' -c 'split bar.py' > > Notice

Bug#807754: suspicious-source: prejudiced against Emacs Lisp

On Sat, Dec 12, 2015 at 08:57:56AM -0400, David Bremner wrote: > Common is obviously subjective, but since there are probably a few > million lines of emacs lisp source in Debian, it probably qualifies as > common-enough. > > Anyway, it certainly is the preferred form of modification. Do you

Bug#874029: uscan: please support signature file containing list of signatures

On Sat, Sep 02, 2017 at 09:58:43AM +0200, Jérémy Lal wrote: > The typical example i have under the hand is: > https://nodejs.org/dist/v6.3.1/ > https://nodejs.org/dist/v6.3.1/SHASUMS256.txt > https://nodejs.org/dist/v6.3.1/SHASUMS256.txt.asc The subject confused me a bit. This appears to be a

Bug#872514: devscripts: Please add script to report on reproducibility status of installed packages

On Aug 31, 2017 05:09, "Chris Lamb" wrote: Hi, > Updated patch attached Any update? ACK to push? :) Yeah, that's fine with me. Cheers, James

Bug#872514: devscripts: Please add script to report on reproducibility status of installed packages

On Sun, Aug 27, 2017 at 02:01:13AM -0700, Chris Lamb wrote: > Hi Paul & James, > > Thanks for the review :) > > Updated patch attached: > diff --git a/debian/copyright b/debian/copyright > index c22addad..95550dc7 100644 > --- a/debian/copyright > +++ b/debian/copyright > @@ -68,6 +68,12 @@

Bug#698240: build-rdeps also fails with lz4'd sources

On Fri, Aug 25, 2017 at 08:21:58PM +0100, solo-debianb...@goeswhere.com wrote: > build-rdeps also fails with lz4'd sources, which appears to have become > the default in sid at some point? It's the case in the "official" > debian:sid Docker images, without any config I can see set. I've started

Bug#872514: devscripts: Please add script to report on reproducibility status of installed packages

On Sun, Aug 20, 2017 at 11:19:08AM -0700, Chris Lamb wrote: > Hi, > > > devscripts: Please add script to report on reproducibility > > status of installed packages > > Updated patch attached that adds the correct line to debian/control. Thanks for working on the new script! I had looked at it

Bug#872942: vim-python: neovim missed

On Wed, Aug 23, 2017 at 01:34:47PM +0300, Adrian Bunk wrote: > reassign 872942 neovim Looping in python-neovim folks, since it might be better to have the Provides there. Without python(3)-neovim installed, there is no python support. It's probably also worth having those "Recommends: neovim",

Bug#856434: sbuild: Fails to build anything in Debian chroots, Ubuntu ones work fine

On Fri, Mar 03, 2017 at 04:17:50PM +0100, Johannes Schauer wrote: > Hi, > > On Wed, 1 Mar 2017 01:28:53 +0100 Julian Andres Klode wrote: > > On Wed, Mar 01, 2017 at 01:21:22AM +0100, Julian Andres Klode wrote: > > > Fails with a lot of errors for Debian chroots, but it works

Bug#866796: ring: FTBFS against msgpack-c 2.x

On Sat, Jul 01, 2017 at 03:14:05PM -0400, James McCoy wrote: > While performing rebuilds of packages which Build-Depend on > libmsgpack-dev with the 2.x version in experimental, I found that ring > FTBFS: > > […] > > I haven't looked into ring's code, but there were some A

Bug#871444: transition: msgpack-c

On Tue, Aug 15, 2017 at 10:11:36PM +0200, Emilio Pozuelo Monfort wrote: > On 08/08/17 03:56, James McCoy wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > I'd like

Bug#872164: vim: Unable to install vim due to versions to be installed

On Mon, Aug 14, 2017 at 02:01:08PM -0400, debianuser wrote: >* What led up to the situation? I did a dist-upgrade which removed >vim-tiny, tried to install vim and was met with errors The problem here is that there are some upstream bugs in the current version which prevented the package

Bug#869965: vim: please add syntax highlighting for debian/copyright files

On Fri, Jul 28, 2017 at 09:10:57AM +0100, Chris Lamb wrote: > A patch is attached that adds simple syntax highlighting for > DEP-5 debian/copyright files. Thanks! > diff --git a/runtime/syntax/debcopyright.vim b/runtime/syntax/debcopyright.vim > new file mode 100644 > index 000..dd34be4 >

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

Control: forwarded -1 https://github.com/equalsraf/neovim-qt/issues/289 On Fri, Jun 02, 2017 at 07:27:36PM -0400, James McCoy wrote: > On Fri, Jun 02, 2017 at 05:39:34PM -0400, Aaron M. Ucko wrote: > > "Aaron M. Ucko" <a...@alum.mit.edu> writes: > > > > Than

Bug#778662: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#871627: Removed package(s) from unstable)

Control: reassign -1 emacs25 24.4+1-4.1 Control: found -1 25.2+1-5 On Fri, Aug 11, 2017 at 06:46:30PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the emacs24 package: > > #778662: emacs should not return 0 when

Bug#739790: update on Python3 support?

On Fri, Aug 04, 2017 at 09:20:01AM -0400, Matthias Klose wrote: > the original report was filed some years ago. Are there any upstream changes > at > this time? No, there haven't been. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

Bug#871444: transition: msgpack-c

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition I'd like to upload the new msgpack-c to unstable. I did a test rebuild in July and filed bugs[0] against the packages which fail to build with the new API changes. [0]:

Bug#857256: /usr/bin/nvim: Neovim says it is not an optimized build

Version: 0.2.0-1 On Thu, Mar 09, 2017 at 10:41:07AM +0100, Ulrik wrote: > :CheckHealth in neovim has the following output for the performance > section, so it claims to not be optimized. > > > ## Performance > - INFO: Build type: None > - WARNING: Non-optimized build-type. Nvim will be

Bug#870367: neovim FTBFS on big endian: Test_get_buf_options line 3: Expected 8 but got 0

Control: tag -1 fixed-upstream On Aug 1, 2017 09:09, "Adrian Bunk" wrote: ... >From test_bufwintabinfo.vim: Found errors in Test_get_buf_options(): function RunTheTest[9]..Test_get_buf_options line 3: Expected 8 but got 0 I'll backport the fix from upstream soon. Cheers,

Bug#869842: bts: see also += devscripts.conf(5)

On Wed, Jul 26, 2017 at 11:22:08PM +, Daniel Shahaf wrote: > I was skimming bts(1) to see what its dotfile was called, and the SEE > ALSO section did not have the answer. +1. Feel free to commit straight-forward fixes like this. It's in collab-maint for a reason. :) Cheers, -- James GPG

Bug#869397: O: github-backup -- backs up data from GitHub

Package: wnpp Severity: normal I intend to orphan the github-backup package. The package description is: github-backup is a simple tool you run in a git repository you cloned from GitHub. It backs up everything GitHub publishes about the repository, including other forks, issues, comments,

Bug#864074: defaults.vim: broken configuration

On Fri, Jul 21, 2017 at 02:25:46PM +0200, Igor Sverkos wrote: > Hi, > > On Thu, 20 Jul 2017 22:24:01 -0400 James McCoy <james...@debian.org> wrote: > > > There's no need to disable defaults.vim. As I have also suggested (in > > this very bug report), you ca

Bug#864074: defaults.vim: broken configuration

On Thu, Jul 20, 2017 at 03:46:39PM -0700, Adam Waite wrote: > As mentioned on other bug reports, this is an order-of-inclusion issue.  > >   1: /usr/share/vim/vimrc >   2: /usr/share/vim/vim80/debian.vim >   3: /etc/vim/vimrc.local >   4: /usr/share/vim/vim80/defaults.vim >   [snip] > >

Bug#869087: devscripts: [uscan] Files excluded without a matching pattern in debian/copyright's Files-Excluded

Control: reassign -1 tar 1.29b-1.1 Control: affects -1 devscripts Control: retitle -1 tar corrupts filenames when using --delete On Thu, Jul 20, 2017 at 02:01:00PM +0200, Emmanuel Bourg wrote: > While updating plexus-archiver I noticed that uscan filters more files > than expected. > > The watch

Bug#864074: defaults.vim: broken configuration

On Sat, Jul 08, 2017 at 11:36:07PM +0200, Martin Steigerwald wrote: > James McCoy - 05.07.17, 21:09: > > This _is_ the behavior. The _only_ way that defaults.vim is used is > > when $HOME/.vimrc doesn't exist. > > > > Note that /etc/vim/vimrc.local is

Bug#864074: defaults.vim: broken configuration

> James McCoy - 18.07.17, 20:21: > > On Sat, Jul 08, 2017 at 11:36:07PM +0200, Martin Steigerwald wrote: > > > James McCoy - 05.07.17, 21:09: > […] > > > My order wasn´t complete. I think it should be: > > > > > > 1. Global vim configuration &g

Bug#865820: vim-common: Change of behaviour for default value of mouse is annoying

On Tue, Jul 18, 2017 at 02:50:52PM -0700, Matt Taggart wrote: > Is there another way to accomplish those things? Adding 'set mouse=' to > /etc/vim/vimrc doesn't seem to work. " Explicitly source defaults.vim to get the recommended settings source $VIMRUNTIME/defaults.vim " Then

Bug#868767: Please backport upstream patch 8.0.0698

On Jul 18, 2017 09:25, "Elimar Riesebieter" <riese...@lxtec.de> wrote: * James McCoy <james...@debian.org> [2017-07-18 07:54 -0400]: [...] > > Upstream patches get merged periodically. However, I haven't been able > to make an upload of them because

Bug#868767: Please backport upstream patch 8.0.0698

On Tue, Jul 18, 2017 at 12:32:26PM +0100, Malcolm Rowe wrote: > Upstream's patch 8.0.0698 fixes a crash on exit when using Python > functions within a timer. Recent versions of e.g. YouCompleteMe > (http://valloric.github.io/YouCompleteMe/) appear to trigger this > reliably, so it would be nice to

Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1

On Thu, Jul 13, 2017 at 10:09:46AM +0100, Adam D. Barratt wrote: > On 2017-07-12 3:27, James McCoy wrote: > > * debchange: > > + Target stretch-backports with --bpo. Closes: #867662 > > + Support $codename{,-{proposed-updates,security}} as well. > > I think there's

Bug#868260: devscripts: phantom script debdiff-apply

On Thu, Jul 13, 2017 at 10:59:43PM +0200, gregor herrmann wrote: > I looked at the source package, without finding anything obvious. > And rebuilding the package fails without internet access in the > chroot (and/or with http_proxy set in the chroot). It certainly shouldn't require internet

Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1

{,-{proposed-updates,security}} as well. + * bts: ++ Add patch from Samuel Thibault <sthiba...@debian.org> to add support for + the new 'a11y' tag. Closes: #867416 + + -- James McCoy <james...@debian.org> Tue, 11 Jul 2017 22:06:17 -0400 + devscripts (2.17.6) unstable; ur

Bug#814570: debdiff: [PATCH 0/4] Correctly match filesystem entries for different options.

On Fri, Jul 07, 2017 at 12:39:01PM +1000, Ben Finney wrote: > On 14-May-2016, Ben Finney wrote: > > I will attempt fixing this. > > This patch series alters the Bash command competion script for > ‘debdiff(1)’, to allow matching filesystem entries and options as > needed. Seems good to me.

Bug#841910: uscan behaviour on multiple signatures

On Thu, Jul 06, 2017 at 09:16:50AM +0200, Guido Günther wrote: > On Wed, Oct 26, 2016 at 06:08:28PM -0400, James McCoy wrote: > > On Mon, Oct 24, 2016 at 01:25:03PM +0200, Bernhard Schmidt wrote: > > > asterisk$ gpg --import < debian/upstream/signing-key.asc > >

Bug#864074: defaults.vim: broken configuration

On Wed, Jul 05, 2017 at 09:55:06PM +0200, Martin Steigerwald wrote: > Dear Maintainer. > > I know of this: > > > Vim will load $VIMRUNTIME/defaults.vim if the user does not have a vimrc. > > This happens after /etc/vim/vimrc(.local) are loaded, so it will override > > any settings in these

Bug#867307: syntax/debcontrol.vim: please provide value "javascript" for field "Section"

On Wed, Jul 05, 2017 at 06:02:29PM +0200, Johannes Schauer wrote: > Currently, the value "javascript" is not accepted by the syntax > highlighting for debian/control files for the "Section" field even > though "javascript" is a valid section name: That was supposed to be fixed in 2:8.0.0134-1,

Bug#866998: pgpmode=next/previous not working as expected?

On Mon, Jul 03, 2017 at 12:34:58PM +0200, Laurent Bigonville wrote: > With the following debian/watch file, it cannot verify the signature of > the tarball: > > version=4 > opts="pgpmode=next" \ > https://red.libssh.org/projects/libssh/files \ >

Bug#866802: neovim: FTBFS against msgpack-c 2.x

Source: neovim Version: 0.1.7-4 Severity: important Tags: upstream fixed-upstream User: msgpac...@packages.debian.org Usertags: msgpack-c-2.x Forwarded: https://github.com/neovim/neovim/pull/6406 While performing rebuilds of packages which Build-Depend on libmsgpack-dev with the 2.x version in

Bug#866796: ring: FTBFS against msgpack-c 2.x

Source: ring Version: 20170626.1.1335994~dfsg1-1 Severity: important Tags: upstream User: msgpac...@packages.debian.org Usertags: msgpack-c-2.x While performing rebuilds of packages which Build-Depend on libmsgpack-dev with the 2.x version in experimental, I found that ring FTBFS: make[5]:

Bug#866791: libdata-messagepack-perl: FTBFS against msgpack-c 2.x

Package: libdata-messagepack-perl Version: 1.00-1 Severity: important Tags: upstream User: msgpac...@packages.debian.org Usertags: msgpack-c-2.x Forwarded: https://github.com/msgpack/msgpack-perl/pull/36 While performing rebuilds of packages which Build-Depend on libmsgpack-dev with the 2.x

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

On Wed, Jun 28, 2017 at 02:30:00PM +, Ximin Luo wrote: > Ximin Luo: > > I have switched to using debian.changelog though, thanks for the tip. I > > also got rid of some dirty "this is already applied" logic and removed some > > arbitrary limits. > > > >

Bug#863992: neovim-qt: FTBFS on mipsel: tst_shell neovim crash

Control: severity -1 important On Fri, Jun 02, 2017 at 05:42:16PM -0400, Aaron M. Ucko wrote: > The experimental mipsel build of neovim-qt failed, as detailed in > https://buildd.debian.org/status/fetch.php?pkg=neovim-qt=mipsel=0.2.7-1=1496289160=0 > In particular, I observe > > 7/12 Test

Bug#865820: vim-common: Change of behaviour for default value of mouse is annoying

On Sat, Jun 24, 2017 at 11:38:03PM -0400, Louis-Philippe Véronneau wrote: > I don't feel suddenly changing this is a good move, even though it > respects what upstream does. To me, this breaks user space big time and > makes it harder to use vim. Then make your argument upstream. I did the same,

Bug#863037: subversion: description += _dav_svn;

On Sat, May 20, 2017 at 02:07:31PM +, Daniel Shahaf wrote: > Good morning James / *, o/ > The package description reads: > > > Description-en: Advanced version control system > > Apache Subversion, also known as svn, is a centralised version control > > system. Version control systems

Bug#864465: autobahn-cpp: Fails to build against msgpack-c 2.x

Source: autobahn-cpp Version: 0.2.1-2 Severity: important Tags: upstream Forwarded: https://github.com/crossbario/autobahn-cpp/issues/149 msgpack-c's 2.0.0 release made some incompatible API changes, which cause autobahn-cpp to FTBFS. The attached build log is from building against the 2.1.1

Bug#864399: unblock: serf/1.3.9-3

) unstable; urgency=medium + + * Add libssl-dev to libserf-dev's Depends, otherwise pkg-config can't +provide information about serf. Thanks to Daniel Shahaf for noticing! + + -- James McCoy <james...@debian.org> Wed, 07 Jun 2017 23:09:48 -0400 + serf (1.3.9-2) unstable; urgency=

Bug#863521: unblock: devscripts/2.17.6

On Tue, Jun 06, 2017 at 11:49:36PM +0100, Jonathan Wiltshire wrote: > On Sat, Jun 03, 2017 at 03:01:40PM -0400, James McCoy wrote: > > This has now been uploaded. Updated debdiffs attached. > > Thanks, and sorry about the delay. No worries. I know you all have a lot to deal wit

Bug#864074: vim: 'set mouse=' in /etc/vim/vimrc.local is ignored unless ~/.vimrc exists

On Sun, Jun 04, 2017 at 02:10:08AM +0200, Andreas Beckmann wrote: > for me the default of 'set mouse=a' is a misfeature, so I want to > disable it globally (my mouse usage ends after marking + > middle-click pasting of text in the terminal, that works fine > without pressing shift). > >

Bug#863118: devscripts needs proper configuration file parsing

On Sun, Jun 04, 2017 at 10:21:39AM +0900, Osamu Aoki wrote: > Hi, > > On Sat, Jun 03, 2017 at 01:45:36PM -0400, James McCoy wrote: > > On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote: > > > OK, here is my try to do the following. Ugly, yes. But it seems to

Bug#863118: devscripts needs proper configuration file parsing

On Sat, Jun 03, 2017 at 11:37:15PM +0900, Osamu Aoki wrote: > OK, here is my try to do the following. Ugly, yes. But it seems to > catch most errors in friendly way. > > * "egrep" test to catch space after "=" > * "set -e" to detect command not found; >* space before "=" >* "false"

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

On Fri, Jun 02, 2017 at 05:39:34PM -0400, Aaron M. Ucko wrote: > "Aaron M. Ucko" writes: > > Thanks for looking into this bug. neovim-qt now builds successfully on > kfreebsd-amd64, but still fails on kfreebsd-i386, with nearly the same > error; per >

Bug#863910: haskell highlighting colors lines starting with # operator in red

On Thu, Jun 01, 2017 at 04:37:26PM -0400, Joey Hess wrote: > This in foo.hs will show the problem when loaded in vim with > no local ~/.vimrc or ~/.vim: > > main = print (munge "world hello,") > > munge = words > # reverse > # unwords > > (#) = flip (.) > According to ":help

Bug#863521: unblock: devscripts/2.17.6 (pre-approval)

On Sun, May 28, 2017 at 12:57:57AM -0400, James McCoy wrote: > On Sat, May 27, 2017 at 09:38:39PM -0400, James McCoy wrote: > > Additionally, there are changes to various scripts to make them work > > better when $HOME isn't set by using Perl's File::HomeDir, a new > > Depend

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

On Tue, Nov 01, 2016 at 03:09:55PM -0400, James McCoy wrote: > On Nov 1, 2016 11:33, "Lucas Nussbaum" <lu...@debian.org> 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 (i

Bug#863521: unblock: devscripts/2.17.6 (pre-approval)

On Sat, May 27, 2017 at 09:38:39PM -0400, James McCoy wrote: > Additionally, there are changes to various scripts to make them work > better when $HOME isn't set by using Perl's File::HomeDir, a new > Depends (56e38636, 3ff2f9db). And Build-Depends (7f47730a). Cheers, -- James GPG K

Bug#863521: unblock: devscripts/2.17.6 (pre-approval)

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package devscripts There are a few changes sitting in git right now that would be useful to make it into Stretch. The full log is

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:

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