From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: Where have svt-av1 1.8.0-2 gone?
Date: Fri, 15 Mar 2024 22:31:20 +0900 [thread overview]
Message-ID: <20240315223120.300a9e4dfae6e4569ea87ccb@nifty.ne.jp> (raw)
In-Reply-To: <63fcce21-d8e7-40d8-b0db-7ae818ed2116@dronecode.org.uk>
On Fri, 15 Mar 2024 13:14:49 +0000
Jon Turney wrote:
> On 15/03/2024 09:15, Takashi Yano via Cygwin-apps wrote:
> > I uploaded svt-av1 1.8.0-2 few hours ago, however
> > it does not appear on the mirror servers so far.
> >
> > Was anything wrong?
>
> Sorry, things will be a little slower than usual (uploads may take up to
> 4 hours to get processed) until I get around to fixing up things for
> some changes made on sourceware to provide better isolation.
>
> I see that this upload was declined because svt-av1 2.0.0 already exists.
>
> I guess you really want to upload it, as it provides a different set of
> shared libraries to 2.0.0. Please let me know.
1.8.0-2 is necessary for changing packaging.
1.8.0-1: cygSvtAv1Enc-1.dll and cygSvtAv1Dec-0.dll are in libsvtav1,
However,
2.0.0-1: cygSvtAv1Enc-2.dll and cygSvtAv1Dec-0.dll are built.
So, I made
1.8.0-2: cygSvtAv1Enc-1.dll is in libsvtav1enc1 and cygSvtAv1Dec-0 is in libsvtav1dec0
both obsolete libsvtav1
for migration.
The first step I did was wrong, i.e. I should not have package which
includes dlls whose versions are diffrent. Sorry.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2024-03-15 13:31 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 [this message]
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
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=20240315223120.300a9e4dfae6e4569ea87ccb@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-apps@cygwin.com \
/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).