From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin-apps@cygwin.com
Subject: Re: Where have svt-av1 1.8.0-2 gone?
Date: Sat, 16 Mar 2024 17:49:30 +0000 [thread overview]
Message-ID: <ad78338a-ea01-4c7a-96a9-edc4dd15b393@dronecode.org.uk> (raw)
In-Reply-To: <20240316094813.eda0fbc36dc487c84c18d794@nifty.ne.jp>
On 16/03/2024 00:48, Takashi Yano via Cygwin-apps wrote:
> On Sat, 16 Mar 2024 09:39:33 +0900
> Takashi Yano wrote:
[...]
>>
>> This expected:
>> 1.8.0-1 -> 1.8.0-2 -> 2.0.0-1
>> libsvtav1(1.8.0-1) -> libsvtav1enc1(1.8.0-2) + libsvtav1dec0(1.8.0-2)
>> -> libsvt1enc1(1.8.0-2) + libsvtav1dec0(2.0.0-2)
>>
>> However, this does not seem to work as I expected.
What unexpected thing happens?
I guess you only get one of libsvtav1enc1 or libsvtav1dec0 (since if
these both are marked "obsoletes: libsvtav1", to the dependency solver
that mean that either of can replace libsvtav1, and provides everything
that it provides.
So maybe the best solution is:
libsvtav1dec0_OBSOLETES=libsvtav1
libsvtav1dec0_REQUIRES=libsvtav1enc1
So libsvtav1 is replaced by both libsvtav1dec0 and libsvtav1enc1
>> My expectation was that both libsvtav1enc1(1.8.0-2) and libsvtav1dec0(1.8.0-2)
>> are installed for upgrading libsvtav1(1.8.0-1).
>>
>> Instead, I found
>>
>> 1.8.0-2:
>> libsvtav1_CATEGORY="_obsolete"
>> libsvtav1_REQUIRES="libsvtav1enc1 libsvtav1dec0"
>> libsvtav1enc1_CONTENTS="usr/bin/cygSvtAv1Enc-1.dll"
>> libsvtav1dec0_CONTENTS="usr/bin/cygSvtAv1Dec-0.dll"
Yeah, this should work, but is not longer preferred because you end up
with an empty libsvtav1 hanging around forever...
>> works as expected.
>> Is it possible to change it like this now?
I've tweaked the existing dependencies based on my reasoning above.
Please let me know if this still isn't working right.
next prev parent reply other threads:[~2024-03-16 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 9:15 Takashi Yano
2024-03-15 13:14 ` Jon Turney
2024-03-15 13:31 ` Takashi Yano
2024-03-15 16:58 ` Jon Turney
2024-03-16 0:39 ` Takashi Yano
2024-03-16 0:48 ` Takashi Yano
2024-03-16 17:49 ` Jon Turney [this message]
2024-03-17 1:06 ` Takashi Yano
2024-03-17 1:43 ` Takashi Yano
2024-04-05 12:46 ` Jon Turney
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=ad78338a-ea01-4c7a-96a9-edc4dd15b393@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).