On Sat, Mar 19, 2022 at 10:02:07AM +, Adam D. Barratt wrote:
> On Sat, 2021-12-25 at 10:53 -0500, James McCoy wrote:
> > On Sat, Dec 25, 2021 at 11:41:29AM +, Adam D. Barratt wrote:
> [...]
> > > Unfortunately the builds failed everywhere with a test suite issue:
>
Source: mira
Version: 4.9.6-5
Severity: normal
xxd has been its own package since 2016-09-10, so it's no longer
necessary to Build-Depend on vim-common.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500
Source: rna-star
Version: 2.7.10a+dfsg-1
Severity: normal
xxd has been its own package since 2016-09-10, so it's no longer
necessary to Build-Depend on vim-common.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unsta
On Mon, Jul 04, 2022 at 02:08:15PM +0200, debb...@igor2.repo.hu wrote:
> Dear packager!
>
> This is biting me more and more often. It's real annoying that I have to
> compile from source with such extensive dependencies because of this one
> missing configure setting. For me, severity of this bu
On Sat, Jun 25, 2022 at 06:54:49AM +, Damyan Ivanov wrote:
> Please upgrade the libtickit package to version 0.4.2a, available from
> https://www.leonerd.org.uk/code/libtickit/
>
> It is needed for the new version of libtickit-perl.
I'll look into this over the next few days.
Cheers,
--
Ja
On Tue, Mar 01, 2022 at 05:45:35PM +0100, Nicolas Évrard wrote:
> * James McCoy [2021-12-17 22:31 +0100]:
> > On Thu, Dec 16, 2021 at 10:28:18AM +0100, Nicolas Évrard wrote:
> > > I am sorry for this bug report because it occurs on some rare occurence
> > > and I
>
On Sun, Jul 17, 2022 at 02:21:24PM +0300, Nicholas Guriev wrote:
> On 17.07.2022 00:30:45 MSK Antonio Terceiro wrote:
> > Did you also, or are you planning to, report bugs against all packages
> > that currently rely on vim-addon-manager? e.g.
>
> Yeah, I have a template for mass-bug(1). And I am
On Thu, Jul 21, 2022 at 06:05:21PM +0900, Osamu Aoki wrote:
> neovim support modern pasting now.
>
> In light of this updating dependency further with following packages may
> be good idea.
>
> * "wl-clipboard" (this is even higher priority than "xclip")
That depends on the user. If they're usi
On Fri, Jul 29, 2022, 08:15 Wesley Schwengle wrote:
> The kitty release of 0.21.2 is from a year ago (release 2021-06-28) per
> https://sw.kovidgoyal.net/kitty/changelog/
>
> Could we get a bump to 0.25.2 released 2022-06-07?
>
The same issues I already mentioned still apply. The new version has
On Sat, May 28, 2022 at 04:45:43PM +0200, Helge Kreutzmann wrote:
> On Fri, May 27, 2022 at 05:01:00PM -0400, James McCoy wrote:
> > This is mentioned at the top of /etc/vim/vimrc:
> >
> >
> > " Vim will load $VIMRUNTIME/defaults.vim if the user does not
On Tue, May 17, 2022 at 04:25:19PM +0100, Peter Green wrote:
> It appears the cause is that librust-rpassword-dev contains a Cargo.lock file
> which
> was generated from the versions of packages in debian at the time of it's
> upload.
>
> Doing some poking around it appears that the Cargo.lock f
On Wed, Jun 01, 2022 at 07:00:37AM -0400, James McCoy wrote:
> On Tue, May 17, 2022 at 04:25:19PM +0100, Peter Green wrote:
> > It appears the cause is that librust-rpassword-dev contains a Cargo.lock
> > file which
> > was generated from the versions of packages in debia
On Mon, Oct 04, 2021 at 10:37:26PM -0400, James McCoy wrote:
> On Sun, Feb 07, 2021 at 09:09:52AM -0500, James McCoy wrote:
> > Control: owner -1 !
> > Control: retitle -1 ITP: alacritty -- A cross-platform, GPU-accelerated
> > terminal emulator
> >
> > On Sun,
Package: ftp.debian.org
Severity: normal
The functionality of these packages were consolidated into rust-tokio,
so they're no longer needed.
Cheers,
James
Control: retitle -1 RM: obsolete rust-tokio-* packages
On Sun, Jun 05, 2022 at 07:31:03PM -0400, James McCoy wrote:
> The functionality of these packages were consolidated into rust-tokio,
> so they're no longer needed.
Looking through the other rust-tokio-* packages, these should
On Mon, Jun 06, 2022 at 11:24:21AM +0200, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 6/6/22 02:55, James McCoy wrote:
> > Bug #986174 in subversion reported by you has been fixed in the
> > Git repository and is awaiting an upload. You can see the commit
> > message
On Tue, Jun 07, 2022 at 09:19:54AM +0200, Xavier Bestel wrote:
> Forgive me for my ignorance, but how can this bug be closed for more
> than a month if neovim is still at 0.6 in all repos ?
It's not closed. It's only marked pending. That means changes which
_would_ close this bug have been made,
Control: reassign -1 vim-tlib
Control: forcemerge 996477 -1
On Wed, Jun 08, 2022 at 03:25:42PM -0500, Tim McConnell wrote:
> What led up to the situation? Unknown, error just started appearing.
>
> What exactly did you do (or not do) that was effective (or ineffective)?
> Unknown if an update cau
Package: g++-9
Version: 9.3.0-13
Severity: important
Tags: upstream
Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95676
Control: affects -1 src:msgpack-c
msgpack-c's latest upload is failing a test on armhf:
--8<--
TEST(object_with_zone, system_clock_impl_min)
{
std::chrono::system_
Package: lintian
Version: 2.114.0
Severity: normal
See, for example, rust-ripgrep's Lintian page --
https://lintian.debian.org/sources/rust-ripgrep
superfluous-file-pattern ./complete/_rg [debian/copyright:10]
While the leading ./ isn't necessary, it is valid.
-- System Information:
Debian Rele
(and friends) which is not using
> > `vim-addon-manager` anymore.
> > This move has been recommended by James McCoy (who
> > sponsored the package).
> >
> > I guess you spotted a lack of documentation/policy for this new helper:
> > `dh-vim_addon`.
> > I ad
On Fri, Jul 10, 2020 at 03:28:22PM +, b0ns wrote:
> Hello,
>
> I always refrained from extrapolating feedback or a complaint about this
> issue but:
> It is now 3 years that i'm typing "set mouse=" every time I open a file with
> VIM on debian while swearing!
>
> Was this the intended resul
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 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
reassign -1 mime-support 3.64
retitle -1 update-mime should convert a .desktop file's TryExec to a test=
field for the mailcap entry
On Fri, Jul 03, 2020 at 04:29:24PM +1000, herb...@gondor.apana.org.au wrote:
> The vim-tiny package depends on vim-common, which contains the
> file /usr/share/appl
On Sat, Aug 22, 2020 at 07:43:19AM -0700, Scott Mcdermott wrote:
> On Fri, Aug 21, 2020 james...@debian.org wrote:
> > > and how is that "nox"?
> >
> > It doesn't pull in X libraries.
>
> It pulls in sound libraries and sound files. Those are only
> useful on desktop systems (those running X).
D
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
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
Source: mercurial
Version: 5.3.1-1
Severity: important
python-subversion can't be built with current src:swig, so I'm in the
process of removing it. Subversion's next upstream release will have
support for Python 3, but since src:subversion currently FTBFS I'm
removing the package early.
It appe
Control: forcemerge 958993 -1
On Fri, May 08, 2020 at 10:23:42PM +0200, Mattia Rizzolo wrote:
> This has been happening for quite some time, however I'm reporting it
> now.
May Mattia, I'd like you to meet April Mattia. He had the same problem.
:)
This should be fixed by my pending Vim upload.
On Sat, May 09, 2020 at 06:40:35PM +0300, Nicholas Guriev wrote:
> Is basic vim package required for addons? It looks I can use an addon with
> vim-gtk, vim-gtk3, or vim-nox, not having the vim package installed. I suggest
> to add these (and possibly vim-athena) to the ${vim-addon:Depends} substva
On Sat, May 09, 2020 at 07:31:51PM +0300, Nicholas Guriev wrote:
> It sounds good but does not seem to work. :( At least, apt wants to install
> the
> vim package despite vim-gtk3 already provides vim. Something strange is
> happening, and I need a bit more investigation.
Ok, I have an idea of wh
On Sun, May 10, 2020 at 08:35:53PM +0300, Nicholas Guriev wrote:
> It is me again, sorry for disturbance.
No worries. Thank you for using and providing feedback about
dh-vim-addon.
> It seems dh_vim-addon(1) does not
> generate tags for :help command because of incomplete $docdir. I daresay
> $t
Control: reassign -1 src:vim 2:8.1.0875-5
Control: retitle -1 Add versions to vim/gvim Provides
Control: affects -1 dh-vim-addon
On Sat, May 09, 2020 at 02:45:13PM -0400, James McCoy wrote:
> On Sat, May 09, 2020 at 07:31:51PM +0300, Nicholas Guriev wrote:
> > It sounds good but does no
On Fri, May 15, 2020 at 03:41:33PM -0700, Josh Triplett wrote:
> Steps to reproduce:
>
> Install the "mpv" package.
> Run nvim.
> Use :term to open a terminal.
> Within the terminal, run "mpv --quiet --vo=tct some-video-file.webm".
>
> The terminal will display garbage for a bit, then nvim will s
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 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
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
Control: reassign -1 libsvn1 1.10.4-1
Control: affects -1 git-svn
Control: tag -1 fixed-upstream
On Tue, Dec 10, 2019 at 07:11:59PM +0100, Bernhard Übelacker wrote:
> In [1] gets a temporary KAboutData object created, with
> string parameters created by QStringLiteral. Therefore
> it looks like QS
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 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 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
Package: lintian
Version: 2.87.0
Severity: normal
As seen in neovim 0.4.3-3, lintian is expecting globs in a single Files
paragraph to follow the same ordering expectations of globs in separate
Files paragraph.
E: neovim source: redundant-globbing-patterns [src/nvim/api/* src/nvim/*.lua]
for src
Package: lintian
Version: 2.87.0
Severity: normal
With neovim 0.4.3-3, lintian is reporting:
neovim source: wildcard-matches-nothing-in-dep5-copyright
scripts/check_urls.vim (line 13)
However, such a file does exist:
$ tar atf neovim_0.4.3.orig.tar.gz | grep check_urls
neovim-0.4.3/scripts/che
Control: retitle -1 vim-tiny: Incorrect size reported when invoked as vi on
32-bit architectures
Control: tag -1 + upstream confirmed
On Sat, Feb 15, 2020 at 12:28:24PM -0500, Tresi Arvizo wrote:
> When invoked as vi, vim.tiny incorrectly reports the file size being
> edited, reporting "898964 ch
On Sun, Feb 16, 2020 at 01:55:41PM -0500, James McCoy wrote:
> Control: retitle -1 vim-tiny: Incorrect size reported when invoked as vi on
> 32-bit architectures
> Control: tag -1 + upstream confirmed
>
> On Sat, Feb 15, 2020 at 12:28:24PM -0500, Tresi Arvizo wrote:
> &g
On Wed, Feb 05, 2020 at 09:46:36AM -0300, Lucas Kanashiro wrote:
> We are planning to start the ruby2.7 transition and your package failed
> to build against ruby2.7. Check the full build log here:
>
> https://people.debian.org/~kanashiro/ruby2.7/builds/5/vim/vim_8.1.2269-1+rebuild1580866890_amd64
On Sun, Feb 16, 2020 at 02:22:45PM -0500, James McCoy wrote:
> Interestingly, changing
>
> vim_snprintf((char *)p, IOSIZE - (p - IObuff),
> NGETTEXT("%lld character", "%lld characters", nchars),
> (long_long_T)nchars)
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
On Tue, Mar 12, 2019 at 12:25:51PM +0100, Arnaud Loonstra wrote:
> Running vim-tutor results in: E484: Can't open file
> /usr/share/nvim/runtime/tutor/tutor.vim
It looks like you've changed the vim alternative to use nvim. Neovim
has a different mechanism for running the tutor, so vimtutor isn't
Control: tag -1 + upstream
On Sun, Dec 25, 2022 at 11:37:23PM +0100, Francesco Poli (wintermute) wrote:
> Hello!
> Do I understand correctly that there's no syntax highlighting or indentation
> support for the [Nim] programming language in package vim-runtime?
The filetype itself is detected, but
On Wed, Dec 28, 2022 at 12:48:04PM +0100, Xavier Bestel wrote:
> Hi,
>
> > I may upload 0.8.0 to experimental
>
> Would it be possible to do so ?
I would need to patch things to not use tree sitter, which I'm reluctant
to do. It definitely wouldn't happen for an upload to sid.
> Popular neovim
On Fri, Dec 30, 2022 at 12:26:06PM +0100, Francesco Poli wrote:
> On Wed, 28 Dec 2022 11:41:12 -0500 James McCoy wrote:
> > That's not something that I would add specifically to the Debian
> > packaging.
>
> That's understandable.
> Is there an alternative strat
On Fri, Aug 04, 2023 at 01:18:15AM +0900, OHURA Makoto wrote:
> After upgrading emacs 29.1, psvn.el does not work fine. Emacs 29.1
> doesn't support the function, toggle-read-only. Use read-only-mode.
> I attach a patch to this e-mail.
Thanks for the patch!
> --- psvn.el.old 2023-08-04 01
On Thu, Jan 25, 2024 at 03:49:37PM +0100, Stephan Lachnit wrote:
> would it be possible to upload msgpack 6.1.0 to Debian unstable soon? It would
> be nice to have the v6 API in Ubuntu 24.04 LTS, for which the import freeze is
> on the 29th February.
Currently, this would break a number of package
On Fri, Jan 26, 2024 at 02:17:18PM +, Martin Bruset Solberg wrote:
>* What led up to the situation? Upgrading sway to latest (from
>trixie)
>* What exactly did you do (or not do) that was effective (or
> ineffective)? Start the app
>* What was the outcome of this action? Ap
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
X-Debbugs-Cc: rust-alacri...@packages.debian.org
Control: affects -1 + src:rust-alacritty
nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against
rust-smithay-client-toolkit 0.16.
Source: rocblas
Version: 5.5.1+dfsg-3
Severity: normal
Tags: patch
Control: block 1018679 by -1
Dear maintainer,
libmsgpack-dev's C++ bindings were split out to a separate binary
package -- libmsgpack-cxx-dev -- in 4.1.1-1 to follow upstream's
separation of the project. rocblas Build-Depends on l
Source: dials
Version: 3.17.0+dfsg3-1
Severity: normal
Tags: patch
Control: block 1018679 by -1
Dear maintainer,
libmsgpack-dev's C++ bindings were split out to a separate binary
package -- libmsgpack-cxx-dev -- in 4.1.1-1 to follow upstream's
separation of the project. dials Build-Depends on lib
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
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: pangot...@packages.debian.org
Control: affects -1 + src:pangoterm
Pangoterm was initially packaged mainly to test out libvterm. It
doesn't provide any particularly unique functionality
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
On Fri, Jan 26, 2024 at 10:16:50AM -0500, James McCoy wrote:
> nmu rust-alacritty_0.12.2-2 . ANY . unstable . -m "Rebuild against
> rust-smithay-client-toolkit 0.16.1"
>
> This is needed to fix #1061563 (crash with recent sway versions).
Ping? It'd be nice to get thi
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: libvt...@packages.debian.org
Control: affects -1 + src:libvterm
libvterm doesn't have a stable API/ABI yet, so although the SONAME
didn't change, this is a breaking update.
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, Oct 14, 2024 at 09:22:01AM -0700, Stefano Rivera wrote:
> This package failed build from source when test-built against a version of
> python3-defaults that includes 3.13 as a supported version.
>
> It looks like it's failing when running tests against Python 3.12, but I
> can't reproduce
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: 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 Tue, Oct 22, 2024 at 09:36:43PM +0200, Alejandro Colomar wrote:
> E340: Internal error; if you can reproduce please report a bug
> E438: u_undo: Line numbers wrong
>
> I'm just doing as said. It was in the middle of editing a mail in
> neomutt(1). I still have vim(1) open in that error sessio
Package: wnpp
Severity: wishlist
Owner: James McCoy
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-r...@lists.debian.org
* Package name: rust-dpi
Version : 0.1.1
Upstream Contact: the winit authors
* URL : https://github.com/rust-windowing/winit/
* License
On Sat, Nov 23, 2024 at 08:06:21PM +0100, Hilko Bengen wrote:
> I have just prepared and uploaded version 0.2.8-0.1 to DELAYED/5. The only
> package declaring a build dependency on tree-sitter-c-src seems to be
> neovim.
That package is exactly why I haven't uploaded a new tree-sitter-c.
Changes t
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
On Sun, Jan 05, 2025 at 08:58:07PM +0100, Salvatore Bonaccorso wrote:
> Given the window is closing very soon this weekend, if you see this in
> time, can you upload it if you are confident that it will be accepted
> as is by the SRM? The "improved workflow" allows to upload along with
> a release.
Package: vim-youcompleteme
Version: 0+20240827+gitb6e8c64+ds-3
Severity: important
Tags: upstream
https://ci.debian.net/packages/v/vim-youcompleteme/testing/amd64/55892686/
I'm working on bisecting the Vim change which broke the test to see if
anything needs to be changed on the Vim side, but I'm
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 Tue, Feb 04, 2025 at 03:49:40PM +0100, Andrea Pappacoda wrote:
> Hi, with patch 9.1.0895 Vim started defaulting to a history of 200 instead
> of 50. This was already the case when sourcing defaults.vim in one's vimrc,
> or when using no vimrc at all.
>
> What patch 9.1.0895 done was removing th
On Sun, Dec 08, 2024 at 05:23:02AM +0300, Aleksey wrote:
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> I ran the lua interpreter and executed the following simple command:
>
> > require("json")
>
>
>* What was the outcome of this acti
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 Thu, Jan 02, 2025 at 12:04:34PM +0100, David Kalnischkies wrote:
> Hi James,
>
> Am Mon, Dec 30, 2024 at 10:25:38AM -0500, schrieb James McCoy:
> > I'm working on bisecting the Vim change which broke the test to see if
> > anything needs to be changed on the Vim si
Source: rust-cairo-rs-0.18
Version: 0.18.5-2
Severity: normal
Tags: patch
rust-freetype-rs 0.36 is currently in experimental, but I'd like to
upload it to unstable soon. I've tested the build and autopkgtests with
the attached patch and they passed.
-- System Information:
Debian Release: trixie/
01
+ * Run davautocheck as part of the build time tests
+
+ -- James McCoy Fri, 03 Jan 2025 20:39:54 -0500
+
subversion (1.14.2-4) unstable; urgency=medium
* Backport patch to fix building with swig 4.1 (Closes: #1023529)
diff -Nru subversion-1.14.2/debian/control subversion-1.14.2/debian/co
On Fri, Jan 03, 2025 at 12:20:15PM +0100, Arnaud Ferraris wrote:
> Hi James,
>
> Le 03/01/2025 à 05:32, James McCoy a écrit :
> > rust-freetype-rs 0.36 is currently in experimental, but I'd like to
> > upload it to unstable soon. I've tested the build and autopkgte
Control: reassign -1 1082967 src:tree-sitter
Reassigning these bugs to src:tree-sitter since that's what produces the
respective binary packages now.
On Sat, Jan 11, 2025 at 06:23:35PM +0100, Jonas Smedegaard wrote:
> Please consider prioritizing release into unstable of branch v0.22.
>
> The He
On Tue, Jan 14, 2025 at 09:39:45PM +0100, Jonas Smedegaard wrote:
> a) librust-tree-sitter-cli-dev v0.22 does *not* exist
That was an oversight when collapsing everything into src:tree-sitter. I
didn't realize tree-sitter-cli was also exposed as a library.
> b) I now bogusly files a bugreport aga
On Wed, Jan 29, 2025 at 03:17:26PM +, Sean Whitton wrote:
> Fixes for eight CVEs, backported from upstream, all already in sid.
> Tested with Vim's existing extensive test suite, and some of the fixes add new
> tests, too. Everything passes.
>
> These are all simple CVEs caused by the usual s
Package: release.debian.org
Severity: important
X-Debbugs-Cc: tree-sit...@packages.debian.org
Control: affects -1 + src:tree-sitter
User: release.debian@packages.debian.org
Usertags: transition
The tree-sitter 0.22.6 packages in unstable accidentally included an ABI
break. This was noticed via
On Mon, Mar 24, 2025 at 07:53:20PM +0100, Chris Hofstaedtler wrote:
On Mon, Mar 24, 2025 at 07:43:27PM +0100, NoisyCoil wrote:
Control: tags -1 + moreinfo
Setting aside option 2 as it seems too involved for this situation, it seems
to me that option 1 goes explicitly against policy: the existen
On Mon, Mar 24, 2025 at 10:31:20PM +0100, NoisyCoil wrote:
On 24/03/25 19:53, Chris Hofstaedtler wrote:
AFAIK this is exactly the point of Recommends. Not all situations
require the package, and the user must change the defaults to not
get the dependency installed.
To me "alacritty (literally)
On Sun, Mar 16, 2025 at 08:42:28PM +0100, Sebastian Ramacher wrote:
Control: tags -1 confirmed
On 2025-03-15 13:33:13 -0400, James McCoy wrote:
Package: release.debian.org
Severity: important
X-Debbugs-Cc: tree-sit...@packages.debian.org
Control: affects -1 + src:tree-sitter
User
Package: dh-python
Version: 6.20250308
Severity: important
python3-pynvim 0.5.2-1 is missing a python3-greenlet dependency because
upstream made the requirement conditional on non-PyPy implementations.
Debug logs from the dh_python3 invocation:
D: dh_python3 dh_python3:180: version: 6.20250308
On Mon, Mar 24, 2025 at 08:48:12PM -0400, James McCoy wrote:
On Mon, Mar 24, 2025 at 10:31:20PM +0100, NoisyCoil wrote:
To me "alacritty (literally) crashes on X11 without
libxkbcommon-x11-0" reads much more strongly than "not all
situations require the package". One can
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
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 Mon, Apr 07, 2025 at 02:31:03PM +, Aleksandar Jelenak wrote:
Hi Helge,
Yes, you found me. I am very glad to hear that plugin is still very useful.
I choose the GPLv3 license. I hope this is the most permissive license, but if
not, tell me which one is better and I will gladly adopt it.
Control: severity -1 wishlist
On Wed, Apr 16, 2025 at 05:09:02PM +0200, martin f krafft wrote:
Unfortunately, Alacritty does not accept the -name command-line option, and
instead spews and error message. This is a problem when it is used as a drop-in
to x-terminal-emulator, which sometimes gets
On Sun, May 04, 2025 at 01:29:28PM +0800, Andrew Gunawan wrote:
I use an application called Junction (installed via flatpak) to prompt me for
which browser I
want to use to open a link, and it works fine when clicking links in
most apps.
However, I noticed that in Alacritty, when I click open a
On Fri, Jan 24, 2025 at 11:55:58PM +0100, Jonas Smedegaard wrote:
Quoting Jonas Smedegaard (2025-01-14 22:18:30)
Quoting James McCoy (2025-01-14 21:51:13)
> On Tue, Jan 14, 2025 at 09:39:45PM +0100, Jonas Smedegaard wrote:
> > a) librust-tree-sitter-cli-dev v0.22 does *not* exist
>
On Thu, Mar 13, 2025 at 01:27:37PM -0400, James McCoy wrote:
On Thu, Mar 13, 2025 at 05:48:09PM +0100, Emilio Pozuelo Monfort wrote:
It sounds like tree-sitter should get a SOVERSION bump. Can you
discuss that with upstream?
Yes, I already had plans to do that with them.
They're al
1201 - 1300 of 1314 matches
Mail list logo
