From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Upgrading packages with breaking changes
Date: Sat, 10 Dec 2022 22:06:02 +0100 [thread overview]
Message-ID: <20221210210602.XSgKSpZmFw2rsNkznhfAfncAbGc6Qn5uy9-1LSqke6I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40998@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
Closed issue by zlice on void-packages repository
https://github.com/void-linux/void-packages/issues/40998
Description:
Wanted to test something in ffmpeg 5.1.2 out. Upgrading `shlibs` and the `template` work, however it appears that `libavresample` was deprecated. And xbps complains about trying to upgrade anything with `libavutil` that relied on it.
```
xbps-install -fu --repository=.
libavutil-5.1.2_1 in transaction breaks installed pkg `libavresample-4.4.3_2'
libavutil-5.1.2_1 in transaction breaks installed pkg `libavresample-32bit-4.4.3_2'
Transaction aborted due to unresolved dependencies.
```
Is there a good way to upgrade? I could force dependency removal but that doesn't seem clean or like what a common update would do.
I only see ffmpeg packages directly used by this on a remove so I'm not sure if anything using ffmpeg relies on it.
next prev parent reply other threads:[~2022-12-10 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 18:03 [ISSUE] " zlice
2022-12-10 20:20 ` paper42
2022-12-10 20:49 ` zlice
2022-12-10 20:50 ` zlice
2022-12-10 20:51 ` zlice
2022-12-10 21:02 ` paper42
2022-12-10 21:06 ` zlice [this message]
2022-12-11 17:45 ` zlice
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=20221210210602.XSgKSpZmFw2rsNkznhfAfncAbGc6Qn5uy9-1LSqke6I@z \
--to=zlice@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).