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 ft
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
> &
On Tue, Nov 01, 2016 at 03:09:55PM -0400, James McCoy wrote:
> 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
> >
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,
--
J
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
https://anonscm.debian.org/git/collab-maint
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 the
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
> >
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:
>
> https://sources.debian.net/src/cowsay/3.03%2Bdfsg2-3/
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
s files. (Closes: #859426)
+ * Add Artful 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.
+
+
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
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 &t_8f = "\[38:2:%lu:%lu:%lum"
> let &t_
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 **
6a7c6 & ad66826a from upstream to fix buffer overflows when
+reading corrupted undo files. (CVE-2017-6349 & CVE-2017-6350)
+
+ -- James McCoy 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.
d
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: /usr/share/locale/zh_CN.UTF
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:
> > >
> >
80x24). 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 (winte
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 docume
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 w
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:
> Una
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 tel
On Sat, Apr 01, 2017 at 02:21:25PM -0400, PICCORO McKAY Lenz wrote:
> 2017-04-01 13:53 GMT-04:00 James McCoy :
> makes the package in question unusable or mostly so, or causes data
> loss, or introduces a security hole allowing access to the accounts of
> users
On Sat, Apr 01, 2017 at 10:28:34AM -0400, PICCORO McKAY Lenz wrote:
> 2017-04-01 8:33 GMT-04:00 James McCoy :
>
> Given that there's an easy workaround (set http-chunked-requests to
> off) I'm lowering the severity of the bug.
>
>
> u lowering, but this
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 :
>
> This discussion is specifically talking about when a 411 status is
> returned, not a 413.
>
> the document only cited 41
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 the testing harness
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 d
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 work
chitectures: i386
Kernel: Linux 4.9.0-1-amd64 (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 Mc
9.0-1-amd64 (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 66aef6cf4c1bd2eb0a951df84c2ba185c4096ab7 Mon Sep 17 00:00:00 2001
From: James McCoy
Date: Wed, 22 Mar 2017 21:01:28 -0400
Subject
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 di
The .dsc file is 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
fixup_buildinfo serf/serf_1.3.9-1.dsc serf/serf_1.3.9-1_amd64.buildinfo
signfile buildinfo serf/serf
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
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
> &g
28.0 -0500
@@ -1,3 +1,11 @@
+vim (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 Mon, 06 Mar 20
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 m
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
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:
> > >
> > > https://anons
.local). In order
to disable the loading of defaults.vim, add
let g:skip_defaults_vim = 1
to /etc/vim/vimrc(.local).
-- James McCoy Tue, 04 Oct 2016 20:28:02 -0400
> However, the mouse was STILL being hijacked, and ":set mouse" showed
> that the setting in
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 Build-Depends
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 c
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
ter, since it's essentially a 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
Date: Fri, 24 Feb 2017 23:43:57 -0500
Subject: [PAT
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. It
t from pkg-create-dbgsym's dh_gencontrol 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&q
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.
>
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
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
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
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.
"nm-online
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,
--
Ja
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 62af10152433c45e5d83e442538fabf1f57
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 provid
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 would
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
str
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 .
> Mod
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,
ornado.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:09PM +010
On Thu, Dec 15, 2016 at 11:03:40PM -0500, Aaron M. Ucko wrote:
> James McCoy 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 time the onEr
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 Q
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 me.
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
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
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 a
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 a
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 unfo
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 --c
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 re
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 eas
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 from
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:
> >
> > [...]
> >
> > The --display-inf
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"?
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 ‘debian/tmp/debian/tmp/usr/share/man/ru/man
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: motioneye-dmo
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 (deb
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.
> >
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
> > &
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
> > Date: Wed Nov 23 12:53
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 --check-co
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:
> >> https://wiki.debian.org/LTS/Development#Buil
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)
> DEBUI
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 --pre
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
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,
> --source options
Sh
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)
--
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
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'
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'
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 t
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,
--
Ja
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 incl
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.), no
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
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 sc
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.
&
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
>
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.
I've yet to do tha
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
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 alr
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.
--
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
> >
> > Th
501 - 600 of 1267 matches
Mail list logo
