Bug#1072766: rust-alacritty: FTBFS: unsatisfiable 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 >

Bug#1066261: lintian: FTBFS: hello.c:9:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration]

gt; > | ^~ > > 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 issues. This is also available as MR!496 on Salsa. Cheers, -- James

Bug#1065731: marked as pending in libvterm

/1e77b861739a56510aa1afa6e3ea1b24ab0cbd56 Add Breaks against neovim and emacs-libvterm Closes: #1065731 Signed-off-by: James McCoy (this message was generated automatically

Bug#1065731: libvterm0: Missing Breaks for rdeps that were built against libvterm 0.1

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,

Bug#1064680: subversion: FTBFS: :86:in `require': /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/li

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): > >

Bug#1062674: lua-compat53: NMU diff for 64-bit time_t transition

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 >

Bug#1063254: lua-luv: identified for time_t transition but no ABI in shlibs

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

Bug#1052945: marked as pending in neovim

) Signed-off-by: James McCoy Closes: #1052945 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052945

Bug#1052799: closing 1052799

close 1052799 1.2.2-1 thanks rust-xcb (1.2.2-1) unstable; urgency=medium

Bug#1051063: vim-scripts: no license assumption must be non-free

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 >

Bug#1050396: RM: pangoterm -- RoQA; low popcon; depends on gtk2

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

Bug#1034875: marked as pending in kitty

/537cabca710f64b838d3b8b1dc986db596fb29d4 Closes: #1034875 Signed-off-by: James McCoy (this message was generated automatically) -- Greetings https://bugs.debian.org/1034875

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

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

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

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

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

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

Bug#1028442: vim-ultisnips: autopkgtest fails if Vim has non-contiguous patch ranges applied

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

Bug#1027824: FTBFS: hanging testsuite: build killed after time of inactivity on buildds

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

Bug#1027793: closed by Debian FTP Masters (reply to James McCoy ) (Bug#1027766: fixed in vim 2:9.0.1000-3)

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 have no

Bug#1027766: marked as pending in vim

/7bdf6feff01b77304c2d1a8af335bd57689b4c66 Fix substitution of VIMCUR in vim-common.install Closes: #1027766 Signed-off-by: James McCoy (this message was generated automatically

Bug#1027566: marked as pending in neovim

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

Bug#1023529: marked as pending in subversion

(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

Bug#1022711: subversion: "svn --non-interactive status -v svn-md5" started by emacs hangs

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

Bug#1022783: closing 1022783

close 1022783 0.9.4-2 thanks -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

Bug#1019981: subversion: "svn propedit" loses changes in case of a network failure / remote attack

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 svn,

Bug#1019981: subversion: "svn propedit" loses changes in case of a network failure / remote attack

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

Bug#1019555: elan: Update dirs dependency

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

Bug#1006928: librust-phf-shared+uncased-dev depends on package that is not in Debian.

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

Bug#1002164: rust-alacritty-terminal: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev

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.

Bug#981823: librust-alacritty-terminal-dev is not installable

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

Bug#982684: subversion: FTBFS on armhf, mips64el: test failure

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

Bug#982464: subversion: CVE-2020-17525: Remote unauthenticated denial-of-service in Subversion mod_authz_svn

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

Bug#981823: librust-alacritty-terminal-dev is not installable

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

Bug#982464: subversion: CVE-2020-17525: Remote unauthenticated denial-of-service in Subversion mod_authz_svn

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

Bug#982464: subversion: CVE-2020-17525: Remote unauthenticated denial-of-service in Subversion mod_authz_svn

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

Bug#978353: marked as pending in serf

/17baa8f922362010416a91dadbcada79c2c2d447 Include upstream patch to fix OpenSSL 1.1.1i compat Closes: #978353 Signed-off-by: James McCoy (this message was generated automatically

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

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

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

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

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

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

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

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

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

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

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

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

Bug#975087: Not relevant to msgpack itself, therefore

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

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

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

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

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

Bug#957592: neovim: ftbfs with GCC-10

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'; >

Bug#965301: opendht FTBFS in unstable.

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

Bug#956007: marked as pending in mercurial

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

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

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

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

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

Bug#954866: marked as pending in subversion

will be re-enabled then. Closes: #954866 Signed-off-by: James McCoy (this message was generated automatically) -- Greetings https://bugs.debian.org/954866

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

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

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

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 plea

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

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

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

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

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

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

Bug#951893: marked as pending in subversion

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 message

Bug#951893: subversion FTBFS with swig 4.0.1

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

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

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

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

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

Bug#951893: subversion FTBFS with swig 4.0.1

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 >

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

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

Bug#948770: marked as pending in subversion

/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

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

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

Bug#945605: closing 914963, closing 945605

# 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

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

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

Bug#930020: 8.1.* patches

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 correct

Bug#920042: lua-nvim: autopkgtest times out since 2019-01-10

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 --embed" waits for a U

Bug#919341: libtool-bin: amd64 /usr/bin/libtool is a zero byte file

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

Bug#911944: neovim FTBFS: tests fail

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

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

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

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

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

Bug#911944: neovim FTBFS: tests fail

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:

Bug#911944: neovim FTBFS: tests fail

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:

Bug#912061: Bug #912061 in msgpack-c marked as pending

, 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

Bug#911714: Bug #911714 in serf marked as pending

/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: James

Bug#911714: serf FTBFS: ssl tests fail

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:

Bug#910233: Bug #910233 in subversion marked as pending

/a0d1bdf1e3f809e9244f74c8146f286f3d7262dd libsvn-{java,dev}: Use absolute target path for symlink_to_dir calls Closes: #910233 Signed-off-by: James McCoy (this message

Bug#910233: Bug #910233 in subversion marked as pending

/5ed1d9dfd96277d55e8e96eec6fe0c74d840254c libsvn-{java,dev}: Use absolute target path for symlink_to_dir calls Closes: #910233 Signed-off-by: James McCoy (this message

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

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

Bug#910233: libsvn-{dev,java}: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

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

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

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/

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

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 build s

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

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

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

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

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

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

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

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

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

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

Bug#870367: marked as pending

e65e6a9d6f574e8ec3fb45724aaf38b6a19fe53c Author: James McCoy <james...@debian.org> Date: Tue Aug 1 21:06:51 2017 -0400 Backport big-endian integer options fix Signed-off-by: James McCoy <james...@debian.org> diff --git a/debian/changelog b/debian/changelog index a568ba6..faae08a 100644 --- a/debian/cha

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#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#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#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#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#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#848230: reassign 848230 to python-neovim, closing 848230

reassign 848230 python-neovim 0.1.9-1 close 848230 0.1.13-1 thanks

Bug#852918: marked as pending

00a3307137b96cc2d8789d70b988ae0a9d34ea04 Author: James McCoy <james...@debian.org> Date: Mon Jan 30 23:30:38 2017 -0500 test_package_lifecycle: Ignore debhelper's create-stamp logs Signed-off-by: James McCoy <james...@debian.org> diff --git a/debian/changelog b/debian/changelog index 9cc40cf..0a

Bug#850845: marked as pending

67a38dae69c12bf4bfb769dfd0d3970b99f02041 Author: James McCoy <james...@debian.org> Date: Tue Jan 10 22:10:17 2017 -0500 dget: Verify/propagate errors when processing a dsc Check exit status of “dpkg-source -x” fails and use exec to run dpkg-buildpackage, so we can properly report failures.

Bug#846711: marked as pending

602d25c02c4bc4ace2bfd646bec1dbb55e07f616 Author: James McCoy <james...@debian.org> Date: Thu Dec 8 23:12:04 2016 -0500 debuild: Run lintian (and hook) directly When the running of lintian was moved to dpkg-buildpackage, that removed the ability to ignore the return code. While it's generally

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

  1   2   >