From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: removed-packages: remove mozjs*.
Date: Wed, 17 Feb 2021 19:21:24 +0100 [thread overview]
Message-ID: <20210217182124.vfV0XjL95alHKB7YJeSGCT0yEglsI-vL-EKr1SxceQM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28824@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/28824#issuecomment-780750695
Comment:
> > future unresolved shlib errors
>
> how do the problematic situation look like?
Basically the same, but that its something obsolete the user has installed which depends on some shared library that is being updated in the transaction.
The user just has to uninstall the package in this case.
Anything more complicated should be handled by replaces on the right packages.
Edit:
I guess in same cases the uninstall is not easy i.e. a scenario would be:
`foo-1_1` depends on `old-1_1`, the dependency is removed in `foo-2_1` and a shared library `old-1_1` depends on is updated in the same transaction, now `old` blocks the `foo-2_1` update.
Then the issue is that you can't simply uninstall `old`, because `foo-1_1` still depends on it.
next prev parent reply other threads:[~2021-02-17 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 17:52 [PR PATCH] " ericonr
2021-02-17 18:02 ` [PR PATCH] [Updated] " ericonr
2021-02-17 18:04 ` ericonr
2021-02-17 18:07 ` Duncaen
2021-02-17 18:07 ` Duncaen
2021-02-17 18:07 ` Duncaen
2021-02-17 18:10 ` ericonr
2021-02-17 18:11 ` ericonr
2021-02-17 18:11 ` Duncaen
2021-02-17 18:14 ` Chocimier
2021-02-17 18:17 ` Duncaen
2021-02-17 18:21 ` Duncaen [this message]
2021-02-17 18:21 ` Duncaen
2021-02-17 19:18 ` [PR PATCH] [Merged]: " Chocimier
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=20210217182124.vfV0XjL95alHKB7YJeSGCT0yEglsI-vL-EKr1SxceQM@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).