fix(rockspec): updated paths to lumen-oss github org

[mats852]

Description

The organization https://github.com/nvim-neorocks is now Lumen Labs https://github.com/lumen-oss

I'm currently overriding this path in the lazy configuration.

require("lazy").setup({
  -- ...
}, {
  rocks = {
    server = "https://lumen-oss.github.io/rocks-binaries/",
  },
})

Related Issue(s)

• Fixes bug: nvim-neorocks organization renamed to lumen-oss #2059

Screenshots

[cabreraam]

Can confirm; this fixed the problem for me.

Tested out by modifying the default lazy.lua file:

local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
if not (vim.uv or vim.loop).fs_stat(lazypath) then
-  local lazyrepo = "https://github.com/folke/lazy.nvim.git"
+  local lazyrepo = "https://github.com/mats852/lazy.nvim.git"
-  local out = vim.fn.system({ "git", "clone", "--filter=blob:none", "--branch=stable", lazyrepo, lazypath })
+  local out = vim.fn.system({ "git", "clone", "--filter=blob:none", "--branch=bugfix/nvim-neorocks-to-lumen-oss", lazyrepo, lazypath })  
  if vim.v.shell_error ~= 0 then
    vim.api.nvim_echo({
      { "Failed to clone lazy.nvim:\n", "ErrorMsg" },
      { out, "WarningMsg" },
      { "\nPress any key to exit..." },
    }, true, {})
    vim.fn.getchar()
    os.exit(1)
  end
end
vim.opt.rtp:prepend(lazypath)
...

and it fixed my issue.

[pbakiewicz]

Hi guys, when should we expect merge?

[folke]

those changes to the generated file should not be included

[xarthurx]

Hi @mats852 , would you please able to update the PR?
There're quite some people facing the same issue:
https://www.reddit.com/r/neovim/comments/1nw8luw/failures_installing_nvimdappython/

And I think as long as the generated file is removed, this PR seems good to be merged.