On Mon, Mar 17, 2025 at 07:50:43PM +0100, Vincent Lefevre wrote:
On 2025-03-17 14:35:47 -0400, James McCoy wrote:
Not sure why you're upgrading to the version from experimental, when
there's a newer version in unstable that already fixed this problem.
No, experimental was not inv
On Wed, Mar 12, 2025 at 10:12:34AM +0100, intrigeri wrote:
Emacs uses tree-sitter for syntax highlighting.
Today, using the consult-git-grep Emacs command reliably crashes my Emacs if
I have the python language grammar compiled and installed in
~/.cache/emacs/tree-sitter/:
Mar 12 09:59:57 mant
Control: tag -1 confirmed upstream
On Wed, Mar 12, 2025 at 04:33:08PM +, Santiago Vila wrote:
During a rebuild of all packages in unstable, your package failed to build:
[...]
==
Control: severity -1 important
Control: notfound -1 2:9.0.1378-2+deb12u1
On Mon, Feb 03, 2025 at 02:33:30PM -0500, James McCoy wrote:
> On Sun, Feb 02, 2025 at 07:29:50PM +0100, Thorsten Glaser wrote:
> > severity 1085065 serious
> > found 1085065 2:9.0.1378-2+deb12u1
> > th
On Sun, Feb 02, 2025 at 07:29:50PM +0100, Thorsten Glaser wrote:
> severity 1085065 serious
> found 1085065 2:9.0.1378-2+deb12u1
> thanks
>
> This is now affecting stable-security builds.
Are you sure? To me it looks like a new test that was added as part of
the security update is getting hung, r
On Thu, Jan 16, 2025 at 09:23:11AM +0100, Jonas Smedegaard wrote:
> The package librust-tree-sitter-cli-dev failes to build, like this:
>
> error: couldn't read
> `/build/turtlefmt-0.1.2/debian/cargo_registry/tree-sitter-cli-0.22.6/src/generate/./templates/.editorconfig`:
> No such file or direc
On Mon, Dec 09, 2024 at 03:41:39AM +0100, Guillem Jover wrote:
> This is a consequence of the switch from gpg to gpgv, which has now
> surfaced issues in how the certificates are stored in the Linux
> packaging (and while checking this also in the certificates themselves).
> The first issue is that
Control: unmerge 1089506
Control: reassign 1089506 lua-json
Control: retitle 1089506 lua-json needs to handle API change in lua-lpeg
Control: severity 1089506 important
Control: retitle 1088842 Add breaks against lua-json versions that don't handle
lua-lpeg API change
Control: severity 1088842 ser
/60fbed06a027faaed40bbeb1654330f0e70e3d2c
vim-patch:9.1.0776: test_strftime may fail because of missing TZ data (#30780)
Problem: test_strftime may fail because of missing TZ data
Solution: Use GMT offsets to validate timezone differences (James McCoy
Control: reassign -1 gcc-14 14.1.0-1
Control: retitle -1 gcc-14: miscompiles code on s390x at -O2
Control: tag -1 upstream
Control: severity -1 normal
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116799
On Wed, Sep 18, 2024 at 02:40:11PM GMT, James McCoy wrote:
> On Wed,
On Wed, Sep 18, 2024 at 05:27:55PM GMT, Niko Tyni wrote:
> This package failed to build from source on the s390x buildd, preventing
> testing migration as it has built successfully in the past.
>
>
> https://buildd.debian.org/status/fetch.php?pkg=vim&arch=s390x&ver=2%3A9.1.0709-1&stamp=172633881
Control: tag -1 pending
On Tue, Oct 24, 2023 at 05:43:10PM GMT, David (Plasma) Paul wrote:
> My patch addresses this issue by moving the
>
> ```
> from devscripts.test import SCRIPTS
> ```
>
> line to later in the scripts/setup.py script after the __init__.py file
> at scripts/devscripts/ has be
On Sat, Aug 31, 2024 at 08:08:02AM GMT, Paul Gevers wrote:
> Hi,
>
> On 31-08-2024 02:48, James McCoy wrote:
> > I wasn't able to reproduce this on amdahl. I attempted to reproduce it
> > locally via qemu and also couldn't reproduce it there.
>
> It seems it&
On Thu, Aug 29, 2024 at 10:36:27AM GMT, Paul Gevers wrote:
> Your package has an autopkgtest, great. However, it started to fail on arm64
> with a segfault. Can you please investigate the situation and fix it? I
> copied some of the output at the bottom of this report.
Nothing changed in the packa
On Thu, Aug 22, 2024 at 11:41:40PM GMT, Peter Green wrote:
> I presume this was triggered by an update of rustc,
> but I'm not sure exactly which one. Looking at the
> dates of the tests in testing and unstable and comparing
> them to rustc's history on the tracker it looks like the
> last successf
On Wed, Jul 24, 2024 at 12:50:20PM GMT, Santiago Vila wrote:
> During a rebuild of all packages in unstable, your package failed to build:
>
>
> [...]
> debian/rules binary
> dh binary
>dh_update_autotools_config
On Sun, Jun 16, 2024 at 03:17:54PM GMT, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > +--+
> > | Install package build dependencies
> >|
> > +
On Fri, Jun 07, 2024 at 05:23:32PM GMT, Santiago Vila wrote:
>
> [...]
> Install main build dependencies (apt-based resolver)
>
>
> Installing build dependencies
>
atch]
> > 9 | strcpy(buf, string);
> > | ^~
> > hello.c:9:5: note: include '' or provide a declaration of 'strcpy'
> > cc1: some warnings being treated as errors
> > make[2]: *** [Makefile:11: all] Error 1
Attached patch fixes these i
/1e77b861739a56510aa1afa6e3ea1b24ab0cbd56
Add Breaks against neovim and emacs-libvterm
Closes: #1065731
Signed-off-by: James McCoy
(this message was generated automatically
Package: libvterm0
Version: 0.3.3-2
Severity: serious
Justification: Policy 8.6.2
The missing Breaks can allow partial upgrades and therefore break
the package, since the ABI changed.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-deb
Control: reassign -1 swig/4.2.0-1
Control: affects -1 src:subversion
Control: forwarded -1 https://github.com/swig/swig/issues/2751
Control: retitle -1 SWIG_snprintf not defined for ruby/tcl bindings
On Sun, Feb 25, 2024 at 08:33:47PM +0100, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > m
On Fri, Feb 02, 2024 at 04:18:01PM +, Graham Inggs wrote:
> If you have any concerns about this patch, please reach out ASAP. Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we begin uploads to unstable; so if information
>
On Mon, Feb 05, 2024 at 01:38:47PM -0800, Steve Langasek wrote:
> However, lua-luv's shlibs file declares a dependency on a library package
> name that contains no ABI information:
>
> $ cat DEBIAN/shlibs
> liblua5.1-luv 0 lua-luv (>= 1.44.2-0)
> liblua5.2-luv 0 lua-luv (>= 1.44.2-0)
> liblua5.3-l
om commit 9afbfb4d646cd240e97dbaae109f12bfc853112c)
Signed-off-by: James McCoy
Closes: #1052945
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1052945
close 1052799 1.2.2-1
thanks
rust-xcb (1.2.2-1) unstable; urgency=medium
On Fri, Sep 01, 2023 at 11:04:44PM +0200, Bastian Germann wrote:
> In vim-script's copyright file, the following assumption is written:
>
> "Summary of license information of each script is reported below. For scripts
> which license is "no license" it is assumed in good faith that having being
>
Control: forcemerge 967680 -1
On Thu, Aug 24, 2023 at 01:49:47AM +0200, Bastian Germann wrote:
> pangoterm does not seem to be used a lot and is unmaintained upstream.
It's not unmaintained upstream.
> I intend to file a RM bug.
> If you have any reasons to keep it in Debian please voice them he
ommit/537cabca710f64b838d3b8b1dc986db596fb29d4
Closes: #1034875
Signed-off-by: James McCoy
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1034875
On Wed, Apr 26, 2023 at 02:50:47PM +0200, Raphael Hertzog wrote:
> Executing the script as default open action is IMO a very bad idea
> because what you get by email is largely to not be trusted so I would
> suggest that kitty be modified to not execute scripts in its URL
> launcher mode (or that i
On Sat, May 06, 2023 at 04:07:56PM +0200, Gabriel Corona wrote:
> Hi,
>
> > In the mean time, it's probably a good idea to drop
> > "application/x-sh;application/x-shellscript" from the list of supported
> > mime type to limit the risk. (I assume that even with "text/plain" and a
> > .sh file exte
Keeping the full text for Kovid's benefit.
On Wed, Apr 26, 2023 at 02:50:47PM +0200, Raphael Hertzog wrote:
> Package: kitty
> Version: 0.26.5-4
> Severity: serious
> Tags: security
> X-Debbugs-Cc: Debian Security Team
>
> Hello,
>
> I was reading https://lists.debian.org/20230425190728.ga1471.
Source: vim-ultisnips
Version: 3.2-1
Severity: serious
Tags: upstream
Justification: RT
Bookworm's Vim now has a non-contiguous set of patches applied:
% vim --version | grep Included
Included patches: 1-1000, 1087, 1117-1118, 1129
This is causing the "with-vim" autopkgtests to fail to parse the
Control: forwarded -1 https://github.com/vim/vim/issues/11782
On Tue, Jan 03, 2023 at 10:39:02PM +0200, Adrian Bunk wrote:
> On Tue, Jan 03, 2023 at 09:15:03PM +0100, Salvatore Bonaccorso wrote:
> > Looking at the older build failures from
> > https://buildd.debian.org/status/logs.php?pkg=vim&arch
7793: vim: insert mode: Backspace doesn't do anything
> >
> > It has been closed by Debian FTP Masters
> > (reply to James McCoy ).
> >
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you ha
/7bdf6feff01b77304c2d1a8af335bd57689b4c66
Fix substitution of VIMCUR in vim-common.install
Closes: #1027766
Signed-off-by: James McCoy
(this message was generated automatically
a new enough lua-nvim when running with
these changes.
Closes: #1027566
Signed-off-by: James McCoy
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1027566
(schueller {_AT_} phimeca.com) [2]
[1] https://github.com/swig/swig/commit/a343b7e254567a64761bc1be7dc55b7b7424ec52
[2] https://github.com/swig/swig/issues/2373#issuecomment-1250997124
git-svn-id: https://svn.apache.org/repos/asf/subversion/trunk@1904167
13f79535-47bb-0310-9956-ffa450edef68
Signed-off
Control: merge 1016889 1022711
Control: severity 1016889 important
On Mon, Oct 24, 2022 at 02:48:17PM +0200, Vincent Lefevre wrote:
> Control: retitle -1 svn tries to read a directory on a different filesystem
> and hangs
> Control: severity -1 grave
> Control: tags -1 security
>
> On 2022-10-24
close 1022783 0.9.4-2
thanks
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Control: severity -1 normal
Control: tag -1 - security
On Mon, Sep 19, 2022 at 02:53:24AM +0200, Vincent Lefevre wrote:
> On 2022-09-18 14:40:36 -0400, James McCoy wrote:
> > You're saying that the change you were preparing was lost, but nothing
> > was actually changed in
On Sun, Sep 18, 2022 at 02:18:22AM +0200, Vincent Lefevre wrote:
> (The "critical" severity is in part because the data loss was
> triggered by a remote attack, though the data loss may occur
> with any kind of network failure.)
>
> I wanted to edit a log message with
>
> svn pe --revprop svn:l
Source: elan
Version: 1.4.1-1
Severity: serious
Tags: ftbfs, patch
Justification: fails to build from source (but built successfully in the past)
I've uploaded rust-dirs 4.0.0, which will cause elan to FTBFS. Attached
is an updated dependencies patch which built successfully locally.
-- System
Control: tag -1 pending
On Tue, Mar 08, 2022 at 11:40:21AM +, peter green wrote:
> The most recent upload of rust-phf-shared added a new feature package,
> librust-phf-shared+uncased-dev which depends on librust-uncased-0.9-dev
>
> rust-uncased is not in Debian and I cannot find any evidence
On Tue, Dec 21, 2021 at 05:09:44PM +0100, Lucas Nussbaum wrote:
> > The following packages have unmet dependencies:
> > librust-signal-hook-dev : Depends:
> > librust-signal-hook-registry-1.2+default-dev but it is not installable
> > E: Unable to correct problems, you have held broken packages.
>
On Sat, Aug 28, 2021, 15:39 Steve Langasek
wrote:
> Note that although rust-alacritty-terminal may no longer need
> rust-terminfo,
> if it still depends on rust-vte, then the package is still not buildable
> because the only version of rust-vte in the archive is 0.3 and
> rust-alacritty-terminal
Control: forwarded -1
https://mail-archives.apache.org/mod_mbox/subversion-dev/202102.mbox/%3C20210212173613.2qji5xpfmcybulyl%40localhost%3E
On Sat, Feb 13, 2021 at 01:23:05PM +, Ivo De Decker wrote:
> The latest upload of subversion to unstable fails on armhf and mips64el:
>
> https://build
On Thu, Feb 11, 2021 at 06:21:08AM +0100, Salvatore Bonaccorso wrote:
> Hi James,
>
> On Wed, Feb 10, 2021 at 08:49:39PM -0500, James McCoy wrote:
> > On Wed, Feb 10, 2021 at 09:21:54PM +0100, Salvatore Bonaccorso wrote:
> > > Hi James,
> > >
> > > On We
On Thu, Feb 04, 2021 at 01:23:33PM +0200, Adrian Bunk wrote:
> The following packages have unmet dependencies:
> librust-alacritty-terminal-dev : Depends: librust-terminfo-0.7+default-dev
> (>= 0.7.1-~~) but it is not installable
> Depends: librust-vte-0.8-dev bu
On Wed, Feb 10, 2021 at 09:21:54PM +0100, Salvatore Bonaccorso wrote:
> Hi James,
>
> On Wed, Feb 10, 2021 at 03:20:22PM -0500, James McCoy wrote:
> > On Wed, Feb 10, 2021 at 03:36:11PM +0100, Salvatore Bonaccorso wrote:
> > > The following vulnerability was
On Wed, Feb 10, 2021 at 03:36:11PM +0100, Salvatore Bonaccorso wrote:
> The following vulnerability was published for subversion.
>
> CVE-2020-17525[0]:
> | Remote unauthenticated denial-of-service in Subversion mod_authz_svn
I'll have uploads ready for this tonight to both sid and buster. I'll
/17baa8f922362010416a91dadbcada79c2c2d447
Include upstream patch to fix OpenSSL 1.1.1i compat
Closes: #978353
Signed-off-by: James McCoy
(this message was generated automatically
On Fri, Jan 15, 2021 at 08:36:22AM -0500, Justin Erenkrantz wrote:
> Sadly, my Debian sid box ran into other issues and is currently inaccessible.
>
> I *think* that this would address the 1.3.x test issues, but 1.3.x doesn't
> build on Mac OS for me for other reasons...so, let me know how it goes
Happy New Year!
On Wed, Dec 30, 2020 at 10:39:28PM -0500, James McCoy wrote:
> On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote:
> > The OpenSSL devs intended this to be a breaking change - but it's not
> > documented anywhere. Sigh.
> >
> > I&
On Tue, Dec 29, 2020 at 02:35:11PM -0500, Justin Erenkrantz wrote:
> The OpenSSL devs intended this to be a breaking change - but it's not
> documented anywhere. Sigh.
>
> I've got a WIP patch against trunk that causes test_ssl to pass - see below.
> It also seems to work with OpenSSL 1.1.1h as
On Sun, Dec 27, 2020 at 10:46:24AM -0500, Justin Erenkrantz wrote:
> Thanks. I expect that this might be due to the last change - erroring out on
> an expired self-signed root cert. Though I thought we didn’t check in a root
> cert for our test chain...could Debian’s packaging be including a cert
On Sat, Dec 26, 2020 at 11:09:41PM +0100, Lucas Nussbaum wrote:
> Source: serf
> Version: 1.3.9-8
> [...]
> > Trailer-Test: f
> > ...F..
> >
> > There was 1 failure:
> > 1) test_ssl_handshake: test/test_util.c:456: expected <0> but was <1
Control: forcemerge 975237 -1
On Thu, Nov 19, 2020 at 12:56:31PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > collecting ... collected 68 items
> >
> > test/test_buffer.py::test_repr PASSED
Control: reopen -1
On Thu, Nov 19, 2020 at 12:32:53AM +0100, Thomas Goirand wrote:
> Since James McCoy says it's fixed in python-pynvim 0.4.2, I'm closing
> this bug for msgpack.
I was referring to the upstream version, which has not been packaged
yet. Also, this bug was fil
On Wed, Nov 18, 2020, 15:21 Paul Gevers wrote:
> Source: python-msgpack, python-pynvim
> Control: found -1 python-msgpack/1.0.0-4
> Control: found -1 python-pynvim/0.4.1-2
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> User
On Tue, Nov 17, 2020 at 02:43:55PM -0300, Antonio Terceiro wrote:
> On Mon, Nov 16, 2020 at 07:04:26PM -0500, James McCoy wrote:
> > On Mon, Nov 16, 2020 at 08:41:57PM -0300, Antonio Terceiro wrote:
> > > The new vim-scripts breaks existing usage with vim-addon-manager.
> >
On Fri, Apr 17, 2020 at 11:07:04AM +, Matthias Klose wrote:
> [...]
> /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/sign.c.o (symbol from plugin): in
> function `init_signs':
> (.text+0x0): multiple definition of `ListLenSpecials';
> src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.genera
On Sun, Jul 19, 2020 at 03:30:18AM +0100, peter green wrote:
> Secondly on architectures where the build can be attempted it is failing
> with
>
> > [ 3%] Building CXX object CMakeFiles/opendht-static.dir/src/utils.cpp.o
> > /usr/bin/c++ -DASIO_STANDALONE -DOPENDHT_LOG=true -DOPENDHT_PEER_DISCOV
On Thu, Jun 25, 2020, 06:54 Julien Cristau wrote:
>
>
> https://salsa.debian.org/python-team/applications/mercurial/-/commit/306a0553aa60103c40bd0a89de6e2d67f3b851ff
>
>
> Remove python-subversion from autopkgtest dependenci
On Thu, Apr 23, 2020 at 02:09:35PM +0200, Paul Gevers wrote:
> I
> suggest you apply the same fix you already did here [2] and stop
> building the python package for now if that works.
Done and uploaded, however that now makes mercurial FTBFS, as I had
notified them earlier this month (#956007).
On Thu, Apr 23, 2020 at 10:13:15AM +0200, Paul Gevers wrote:
> It seems the ruby2.5 removal transition [1] is stalled by subversion
> [2]. Can the fix for 954866 please be uploaded to unstable such that
> subversion can migrate and we can finish the removal of ruby2.5 in testing?
I'd rather not up
will be re-enabled then.
Closes: #954866
Signed-off-by: James McCoy
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/954866
Control: severity -1 normal
On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> [...]
> > Trailer-Test: f
> > 140691743627136:error:14095126:SSL routines:ssl3_read_n:un
On Mon, Mar 30, 2020 at 07:00:46PM -0400, James McCoy wrote:
> On Mon, Mar 30, 2020 at 02:53:40PM -0400, Justin Erenkrantz wrote:
> > Here's a tentative patch that causes the test cases to pass with OpenSSL
> > 1.1.1e+ for me on Debian Sid.
> >
> > James, can you
On Mon, Mar 30, 2020 at 02:53:40PM -0400, Justin Erenkrantz wrote:
> Here's a tentative patch that causes the test cases to pass with OpenSSL
> 1.1.1e+ for me on Debian Sid.
>
> James, can you please give it a go and confirm that it works for you?
The package does build and pass tests with the pa
On Fri, Mar 27, 2020 at 05:15:24PM -0400, Justin Erenkrantz wrote:
> James,
>
> I finally got a Debian sid environment up. However, I'm seeing a different
> sets of test failures right now against vanilla serf 1.4.x and trunk (which
> works with the scons/python3 in sid without a patch AFAICT) -
On Wed, Mar 25, 2020 at 08:57:14AM -0400, Justin Erenkrantz wrote:
> James,
>
> Thanks for the bug report. For reference, the upstream OpenSSL commit looks
> to
> be:
>
> https://github.com/openssl/openssl/commit/
> d924dbf4ae127c68463bcbece04b6e06abc58928
>
> I strongly suspect that the patch
oming in the next subversion release, but are too
invasive to backport.
Explicitly build with swig3.0 for now to work around the problem, and
unblock various transitions.
Closes: #951893
Signed-off-by: James McCoy
(this me
On Mon, Mar 23, 2020 at 12:50:42PM -0300, Lucas Kanashiro wrote:
> diff -Nru subversion-1.13.0/debian/control
> subversion-1.13.0.new/debian/control
> --- subversion-1.13.0/debian/control 2020-01-19 10:59:14.0 -0300
> +++ subversion-1.13.0.new/debian/control 2020-03-23 11:39:46.47467
Looping in upstream:
On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote:
> Version: 1.3.9-8
This is the same version of the serf package that's been in Debian since
2019/12/31, so something else seems to have changed.
> [...]
> During a rebuild of all packages in sid, your package fa
On Thu, Mar 12, 2020 at 08:28:19PM +, Ivo De Decker wrote:
> The latest upload of vim to unstable fails on armel, armhf, i386, mips64el,
> mipsel, s390x:
>
> https://buildd.debian.org/status/package.php?p=vim
At least the 32-bit arch failures are understood and I've already given
upstream a
On Sat, Feb 22, 2020 at 08:19:30PM +0200, Adrian Bunk wrote:
> ...
> /usr/bin/swig -I/build/1st/subversion-1.13.0/BUILD/subversion
> -I/build/1st/subversion-1.13.0/subversion/include
> -I/build/1st/subversion-1.13.0/subversion/bindings/swig
> -I/build/1st/subversion-1.13.0/subversion/bindings/sw
Control: tag -1 fixed-upstream
On Sun, Feb 02, 2020 at 04:47:26PM +0100, Andreas Beckmann wrote:
> msgpack-c/experimental on all 32-bit architectures:
> https://buildd.debian.org/status/package.php?p=msgpack-c&suite=experimental
Yes, that and #950460 are the main reasons I haven't uploaded this t
/6196c3e30966fee3f58663eeeaae6d39d306b5c7
use python2 as the interpreter now for tests, not python
/usr/bin/python is no longer guaranteed to exist, per PEP 394. Use
python2 instead for compatibility.
Closes: #948770
Signed-off-by: James McCoy
On Mon, Jan 06, 2020 at 12:19:21PM +0100, Christoph Biedl wrote:
> Additionally, I always upload new upstream versions of src:file to
> experimental first to avoid situations like this. If anybody wishes to
> receive a notification to start tests, drop me a line with your e-mail
> address, preferab
# These were fixed with upstream's 0.4.0 release, but I forgot to include the
# Closes entries in the changelog
#
# * New upstream version 0.4.0
#- Fix FTBFS with neovim >= 0.4 (Closes: #945605)
#- Renamed to python-pynvim (Closes: #914963)
close 914963 python-pynvim/0.4.0-1
close 945605 p
On Mon, Dec 23, 2019 at 12:36:25PM +0200, Adrian Bunk wrote:
> I've prepared an NMU for python-neovim (versioned as 0.3.0-1.1) and
> uploaded it to DELAYED/15. Please feel free to tell me if I should
> cancel it.
I've uploaded the new upstream version (0.4.0) which contains these
fixes. It's go
On Fri, Jun 14, 2019 at 02:38:57PM +0800, Alastair Irvine wrote:
> On Thu, Jun 06, 2019 at 22:13:22 -0400, James McCoy wrote:
> > Unfortunately, the update isn't going to be as simple for
> > Jessie/Stretch. The functionality relied upon for check_secure() to
> > work co
1BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
>From 24fe448aa406b0aa2267044a9858e3d2e5963b61 Mon Sep 17 00:00:00 2001
From: James McCoy
Date: Sun, 3 Mar 2019 11:49:54 -0500
Subject: [PATCH] Use --embed --headless for Socket/TcpStream session tests
After neovim/neovim#9024, "nvim --embe
Package: libtool-bin
Version: 2.4.6-7
Severity: serious
File: /usr/bin/libtool
The amd64 package, the only one not built on a buildd, contains a
zero-byte /usr/bin/libtool. This makes it completely non-functional.
$ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
drwxr-xr-x root/root 0 2019-01
Version: 0.3.2-1
On Sat, Nov 10, 2018 at 03:36:08PM -0500, James McCoy wrote:
> On Sat, Nov 10, 2018 at 04:09:55PM +0100, Helmut Grohne wrote:
> > I also tried in pbuilder and there I only got the utf_char2bytes
> > failure, not the ones with check_cores. This hints that somethi
On Sun, Dec 30, 2018 at 09:30:34PM -0500, James McCoy wrote:
> Dropping debhelper and related bug, since this is just about libtermkey.
>
> On Sun, Dec 30, 2018 at 08:22:00PM +, Niels Thykier wrote:
> > Anyhow, on to the details I have found:
> >
> > * Only te
Dropping debhelper and related bug, since this is just about libtermkey.
On Sun, Dec 30, 2018 at 08:22:00PM +, Niels Thykier wrote:
> Anyhow, on to the details I have found:
>
> * Only test case 05flags.t fails and only if stdin is a *readable*
>non-tty (e.g. /dev/null, an empty file or
On Sat, Nov 10, 2018 at 04:09:55PM +0100, Helmut Grohne wrote:
> On Sat, Nov 10, 2018 at 09:29:42AM -0500, James McCoy wrote:
> > On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote:
> > > Looking to reproducible builds, the failure pattern looks quite random:
On Fri, Oct 26, 2018 at 03:30:54PM +0200, Helmut Grohne wrote:
> neovim fails to build from source in unstable.
>
> | [ ERROR ] 6 errors, listed below:
> | [ ERROR ] test/functional/helpers.lua @ 743: after_each
> | test/helpers.lua:289: crash detected (see above)
> |
> | stack traceback:
>
, explicitly use the option to avoid building
gmock.
Closes: #912061
Signed-off-by: James McCoy
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/912061
/de771b25106e14d961931cc84a91d533f1b550a0
Backport create_certs.py from upstream to generate certs at test time
The certs used for testing expire 1 year after they're generated, which
causes a timebomb for stable releases.
Closes: #911714
Signed-off-by:
On Tue, Oct 23, 2018 at 10:15:28PM +0200, Helmut Grohne wrote:
> serf fails to build from source in unstable e.g. on i386:
>
> https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/serf_1.3.9-6.rbuild.log.gz
>
> | There were 14 failures:
> | 1) test_ssl_trust_rootca: test/test_util.c:
/a0d1bdf1e3f809e9244f74c8146f286f3d7262dd
libsvn-{java,dev}: Use absolute target path for symlink_to_dir calls
Closes: #910233
Signed-off-by: James McCoy
(this message was
/5ed1d9dfd96277d55e8e96eec6fe0c74d840254c
libsvn-{java,dev}: Use absolute target path for symlink_to_dir calls
Closes: #910233
Signed-off-by: James McCoy
(this message was
On Thu, Oct 04, 2018 at 06:56:45AM +0200, Andreas Beckmann wrote:
> On 2018-10-04 02:53, James McCoy wrote:
> > On Wed, Oct 03, 2018 at 07:49:35PM +0200, Andreas Beckmann wrote:
> >> an upgrade test with piuparts revealed that your package installs files
> >> over exi
On Wed, Oct 03, 2018 at 07:49:35PM +0200, Andreas Beckmann wrote:
> an upgrade test with piuparts revealed that your package installs files
> over existing symlinks and possibly overwrites files owned by other
> packages. This usually means an old version of the package shipped a
> symlink but that
On Thu, Jun 14, 2018 at 08:49:53PM +0300, Niko Tyni wrote:
> On Wed, May 16, 2018 at 08:33:58AM -0400, James McCoy wrote:
> > On Fri, May 11, 2018 at 04:27:39PM +0200, Emmanuel Bourg wrote:
> > > Control: tags -1 + patch
> > >
> > > Le 06/05/2018 à 02:13, Jam
On Fri, May 11, 2018 at 04:27:39PM +0200, Emmanuel Bourg wrote:
> Control: tags -1 + patch
>
> Le 06/05/2018 à 02:13, James McCoy a écrit :
>
> > It looks like that will do the right thing. Now I just need to figure
> > out the larger issue of adapting upstream's bu
On Thu, May 03, 2018 at 11:25:03PM +0200, Emmanuel Bourg wrote:
> On Wed, 2 May 2018 22:11:49 -0400 James McCoy wrote:
>
> > Ah, that's because the javah command was removed in Java 10, to be
> > replaced by running "javac -h".
> >
> > It would have
1 - 100 of 204 matches
Mail list logo
