Received: from mail-40141.protonmail.ch (mail-40141.protonmail.ch [185.70.40.141]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 9F63B781040 for <~alpine/devel@lists.alpinelinux.org>; Wed, 6 Jul 2022 12:48:57 +0000 (UTC) Date: Wed, 06 Jul 2022 12:48:49 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1657111736; x=1657370936; bh=eNMCF51kflaH/A40+vja2D8hfjXznOy7hdnpDDANtGc=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=SAeXIZo4IhUQ5lR6qiguxTGqj5apLKJprgLWNMV3QHWdyzD3Oh440/RHdKD7UgB3B zWOzIjBmhNtnP7Ez/udiecnDUgWIgv8Pc2mRvpQXVssvgMBWNRW7rUX7HtQ/6MbNJZ VYMpD9V67L/EpGvbcAf2KnkBsinJt23jS01yx3i/BggjwZgKRq8wVtyaFTspz6P6Lx v8bbsn1jTdNdnlki9mf67TSCIUXTlXS3f056JC1DF3rxKenzAJNxBKVYHw4V6tDq/z 3Yoh4x1qzpZXPGPndtvjNqe8Imb0rnbnf76T4NvVQlXRaoHK30E6oovqb0hASAmmZ3 suzOd+0wEm0hw== To: alice From: Mogens Jensen Cc: Jakub Jirutka , "~alpine/devel@lists.alpinelinux.org" <~alpine/devel@lists.alpinelinux.org> Reply-To: Mogens Jensen Subject: Re: Downgrading of x264-libs? Message-ID: <0uFUzhn5PLBzdJI879dbvirqcqxEio66ZZaf_R6rRRvu9Mv3ldQiRaOcIeRS6OqXk8pORvbhAKAjiMHVk1WvHW_wP8UYMAcH7kUMlLT8wDA=@protonmail.com> In-Reply-To: References: <6dfb7ed6-abec-e1e0-e85c-6724efb98f6b@jirutka.cz> Feedback-ID: 6903854:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Indeed there is no issue with the functionality of the system, but I do like to deduce a hypothesis when "weird" stuff happens on the systems I manage. If I understand correctly, the only scenario where apk could "downgrade" is if the previous x264-libs pkgver was 20210613 or lower? If version 20210613-r0 was installed when the following was committed: community/x264: change version number to include ABI version https://gitlab.alpinelinux.org/alpine/aports/-/commit/a180db09f3b271548ca42= 478f2c6d27c2abe2f70 Is it 100% sure that the package should have been upgraded on the system after that? Of course, normally a new version in pkgver would make apk upgrade the package, but maybe because of the change in version number scheme, the pkgrel should also have been set to 1 for apk to upgrade? I have tried to manually install x264-libs-20210613-r0.apk on an edge system with all repositories enabled, remove the string appended to package name in /etc/apk/world and run "apk update && apk upgrade -v". The result is that x264-libs is NOT upgraded. Even after running "apk add -v --upgrade x264-libs" apk still shows no updates. With the following commit, pgrel was set to 1: community/x264: enable lto https://gitlab.alpinelinux.org/alpine/aports/-/commit/eecb4709387b5c56b5e4d= fc8d28cf4923c754b24 I know for a fact that this was the version installed on the systems I updated yesterday, that did not "downgrade" x264-libs. So maybe last time I updated these system, it was in the short window while x264-libs-0.163_git20210613-r1.apk was available on the mirror, which made apk upgrade from x264-libs-20210613-r0, that's why no "downgrade" happened on these yesterday. I see that ffmpeg4-libs-4.4.2-r2 and ffmpeg-libs-5.0.1-r3 depends on x264-libs-0.164_git20220602-r0, so maybe updating ffmpeg4-libs and ffmpeg-libs was the cause of x264-libs-20210613-r0 finally being upgraded to x264-libs-0.164_git20220602-r0 which caused the "Downgrading" message on this single system. Does that sounds plausible? I know there have been some work on adding log file functionality to apk, does anyone know the status of that? Best regards, Mogens Jensen