Github messages for voidlinux
 help / color / mirror / Atom feed
From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package newer python-language-server and remove the old one
Date: Sun, 06 Mar 2022 16:45:33 +0100	[thread overview]
Message-ID: <20220306154533.XEITxqoLFs9L1I9XxcgfDAq7p0K5YaCuViVLTQrUBn0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34192@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

New comment by Duncaen on void-packages repository

https://github.com/void-linux/void-packages/issues/34192#issuecomment-1059986053

Comment:
> Also, why is renaming packages a pain? Isn't there a `replaces=` field in templates?

This just makes xbps replace the other package if the replacing package is being installed, i.e. through a dependency.
If you've manually installed `python3-foo` and nothing depends on it that would pull in the new package with the `replaces` directive into the xbps transaction it will never be installed or replace any package.

This can not be changed as this is also used by some packages that act as an alternative for another package, i.e. nvidia used to replace the mesa libgl implementations, so by installing nvidia you can replace the open source implementation, without having to force break and uninstall the opensource implementation first.

The only alternative to this is to use "transaction dummy packages", i.e. a meta package with the old name and a higher version that depends on the new package name which then in turn replaces the old name.
But this is kinda buggy in the current xbps release and drops the manual/automatic install mode sometimes.

But that is also not a nice solution and would require us to ship 937 dummy packages for who knows how long until everyone updated their system.

Its simply not worth it with the current solutions to rename all those packages.

  parent reply	other threads:[~2022-03-06 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22  0:53 [ISSUE] " jgarte
2021-11-23  0:56 ` foopub
2021-11-23  2:12 ` jgarte
2021-11-23  2:14 ` jgarte
2022-03-06  1:49 ` camoz
2022-03-06 11:20 ` paper42
2022-03-06 14:07 ` camoz
2022-03-06 14:36 ` Duncaen
2022-03-06 15:24 ` camoz
2022-03-06 15:43 ` Duncaen
2022-03-06 15:45 ` Duncaen [this message]
2022-03-06 16:54 ` camoz
2022-04-06 21:34 ` [ISSUE] [CLOSED] " leahneukirchen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220306154533.XEITxqoLFs9L1I9XxcgfDAq7p0K5YaCuViVLTQrUBn0@z \
    --to=duncaen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).