On 03/07/2025 13:28, Andriy Gapon wrote:
# /bin/sh /usr/ports/Mk/Scripts/check_have_symbols.sh /wrkdirs/usr/ports/
multimedia/ffmpeg/work/stage /usr/local/lib/libavcodec.so
+ set -eu
+ set -o pipefail
+ STAGEDIR=/wrkdirs/usr/ports/multimedia/ffmpeg/work/stage
+ shift
+ ret=0
+ failed='&#x
imedia/ffmpeg/work/stage
+ shift
+ ret=0
+ failed=''
+ /usr/bin/readelf -V
/wrkdirs/usr/ports/multimedia/ffmpeg/work/stage/usr/local/lib/libavcodec.so
+ awk 'BEGIN { ret=1 } $10 == "Name:" || $10 == "vda_name:" { ret=0; exit 0 }
END { exit ret }'
+ [ '' '!=' '' ]
+ exit 0
Does anyone have any idea what could be going on here?
It seems like perhaps some sort of a race but what could it be?
--
Andriy Gapon
2024 perl is still not cross build
friendly and last I checked python wasn't either.
I guess that's also the reason why nvidia driver packages are not built for the
kmod repo?
Because they bundle kernel and userland code in the same port?
--
Andriy Gapon
On 28/11/2024 13:42, Dag-Erling Smørgrav wrote:
Andriy Gapon writes:
FWIW, I am not sure if it's relevant but I am seeing a similar pattern
of corruption on tmpfs although in a different context, on FreeBSD
13.3.
Not relevant at all. In this case the file is not actually corrupte
if it's relevant but I am seeing a similar pattern of
corruption on tmpfs although in a different context, on FreeBSD 13.3.
Details: https://lists.freebsd.org/archives/freebsd-fs/2024-November/003855.html
--
Andriy Gapon
be another revision bump is required again.
Miroslav,
did you notice
https://cgit.freebsd.org/ports/commit/?id=1876b07e4fcf269a1c57ac401ab57e4337bcf465 ?
--
Andriy Gapon
0
svt-av1: 2.2.0 -> 2.3.0
Number of packages to be installed: 2
Number of packages to be upgraded: 9
I do have my own poudriere setup, but I don't think I have any custom
settings at this point. I can doublecheck if anyone is curious, though.
Anyone else seen this? Or should I file a bug report?
--
Andriy Gapon
hat a piece of software is abandoned,
unused and troublesome.
I agree to deprecated it.
It still builds and works fine (at least for now).
I've been using it for years and would like to be able to continue.
--
Andriy Gapon
On 22/12/2021 13:13, Andriy Gapon wrote:
I also collected some logs from pkg -dd upgrade.
Here are all lines that mention nvidia-driver:
I've just noticed and found it curious that the log does not mention
nvidia-driver without any suffix (that is, nvidia-driver-470.86) at all until
On 07/12/2021 19:10, Andriy Gapon wrote:
I have nvidia-driver-470.86 installed, but every time I run pkg upgrade or pkg
install it wants to install nvidia-driver-390. That obviously fails because of
conflicts with the installed driver.
That does not cause me too much trouble, but I am
: 100%
--
Andriy Gapon
As a general observation, there is a concept of "too big to fail".
As we can see, it applies not only to companies but to ports as well.
Or in other words, quod licet Iovi, non licet bovi.
And that's reasonable.
--
Andriy Gapon
On 19/11/2021 10:47, Baptiste Daroussin wrote:
On Fri, Nov 19, 2021 at 10:31:37AM +0200, Andriy Gapon wrote:
Is there an option to limit pkg audit to report security problems only?
Right now the corresponding periodic script reports a lot of (what I
consider to be) noise every night. It&#
cause 90% of reported
packages are not actually going to be removed (e.g., kmail, korganizer, etc).
So, I would like to be getting a security focused report useful for end users.
Is that possible?
Thank you!
--
Andriy Gapon
14 matches
Mail list logo
