Re: Why NOARCH packages aren't available on all architectures?

2022-08-04 Thread Yuri
On 8/4/22 20:37, Tatsuki Makino wrote: It seems to require cmake and ninja. This shouldn't affect NOARCH packages. Once such package is built on one architecture it should be promoted to all architectures, even to ones where some build dependencies might not be available. However, it doesn

Re: Why NOARCH packages aren't available on all architectures?

2022-08-04 Thread Mehmet Erol Sanliturk
On Fri, Aug 5, 2022 at 5:15 AM Yuri wrote: > Hi, > > > When I look at the xsimd package's Fresh ports page > https://www.freshports.org/devel/xsimd - it shows that xsimd package is > available on some architectures but on others. > > For example it isn't available on FreeBSD:13:armv6. > > > Shoul

Re: Why NOARCH packages aren't available on all architectures?

2022-08-04 Thread Tatsuki Makino
Hello. It seems to require cmake and ninja. However, it doesn't seem to exist because those builds have probably stopped. My internet connection is not set up to see the official poudriere logs, though :) Regards. Yuri wrote on 2022/08/05 10:51: > When I look at the xsimd package's Fresh ports

Why NOARCH packages aren't available on all architectures?

2022-08-04 Thread Yuri
Hi, When I look at the xsimd package's Fresh ports page https://www.freshports.org/devel/xsimd - it shows that xsimd package is available on some architectures but on others. For example it isn't available on FreeBSD:13:armv6. Shouldn't packages which are NOARCH be equally available on all

Re: ports-mgmt/pkg: pkg query -e %#r condition doesn't match properly

2022-08-04 Thread Tatsuki Makino
Thank you very much for committing. ... Also, I'll shorten the subject :) Regards. Baptiste Daroussin wrote on 2022/08/04 20:58: > Good catch, thanks, pushed in the repo: > https://github.com/freebsd/pkg/commit/a1f6f620b4671d924f5fad3f24c2d7abc3b229cb > > Will be in the next release of pkg!!

Unmaintained FreeBSD ports which are out of date

2022-08-04 Thread portscout
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. Please consider also adopting this po

[NEWS] GitLab plans to delete dormant projects in free accounts

2022-08-04 Thread Yuri
Hi, This article may be of interest to some because many ported projects are hosted on GitLab. https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/ Yuri

Re: MegaCLI port is ports-only -- how would you deploy it?

2022-08-04 Thread Ruslan Makhmatkhanov
  03.08.2022, 02:07, "Dan Mahoney" :Hey there all,At the dayjob we have a fleet of Dell Poweredge servers that can use either mptsas or mrsas -- if you use mptsas, you use mptutil (in base) to check the state of the card.If you use mrsas, you need megacli, which is only in ports, and the port hasn'

Re: poudriere overlay: passing down git ENV variables (problem: self signed certificates)

2022-08-04 Thread FreeBSD User
Am Thu, 4 Aug 2022 07:37:48 +0900 Tatsuki Makino schrieb: > Hello. > > In git-2.37.1/http.c... > >    ︙ > if (!curl_ssl_verify) { > curl_easy_setopt(result, CURLOPT_SSL_VERIFYPEER, 0); > curl_easy_setopt(result, CURLOPT_SSL_VERIFYHOST, 0); > }

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Andrea Venturoli
On 8/4/22 14:55, Helge Oldach wrote: Use security/clamav-lts instead - until it's getting deprecated. I've considered that. For some reasons (internal packages with dependencies, Salt states, differences between machines, etc...) it will be more of an hussle than recompiling the kernel.

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Robert Huff
On 8/4/22 14:18, Andrea Venturoli wrote: > >> I'm suprised if 0.105.1 worked fine without COMPAT_FREEBSD11. > > P.S. > Could I suggest a warning in pkg-message, then? > I would have avoided the noise... Considering the number of things being affected by the larger issue. _I'

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Andrea Venturoli
On 8/4/22 14:18, Andrea Venturoli wrote: I'm suprised if 0.105.1 worked fine without COMPAT_FREEBSD11. P.S. Could I suggest a warning in pkg-message, then? I would have avoided the noise...

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Andrea Venturoli
On 8/4/22 13:45, Yasuhiro Kimura wrote: Commit updating security/clamav to 0.105.1,1 isn't merged to current (2022Q3) quarterly branch. Sure. I cherry-picked it myself. (Since it's a *security* update, I think it should go into quarterly, but that's irrelevant). * Your rchitecture am

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Robert Huff
Quoting Piotr Kubaj: > please have a look at https://github.com/rust-lang/rust/issues/89058 Hope this helps. As a former developer: would someone please explain what is so useful about Rust that so many seemingly unrelated things are being re-written using it? It feel

Re: ports-mgmt/pkg: pkg query -e %#r condition doesn't match properly

2022-08-04 Thread Baptiste Daroussin
On Thu, Aug 04, 2022 at 04:17:49PM +0900, Tatsuki Makino wrote: > Looking at "pkg shell .dump | grep \ deps\ " results, it seems that origin > without @flavor is not unique. > However, ports that use FLAVORS are modified to make the PKGNAME unique. > > So, the following patch is applied and it se

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Yasuhiro Kimura
From: Yasuhiro Kimura Subject: Re: ClamAV requiring COMPAT_FREEBSD11 Date: Thu, 04 Aug 2022 20:08:34 +0900 (JST) > From: Andrea Venturoli > Subject: ClamAV requiring COMPAT_FREEBSD11 > Date: Thu, 4 Aug 2022 12:49:11 +0200 > >> >> Hello. >> >> I build clamav-0.105.1,1 (from quarterly branch) i

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Milan Obuch
On Thu, 4 Aug 2022 12:49:11 +0200 Andrea Venturoli wrote: > Hello. > > I build clamav-0.105.1,1 (from quarterly branch) in Poudriere and > I've always used it without problems. > > Suddenly last night freshclam started dying on a few machines: it > turn out it prints "bad system call", due to t

Re: ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Yasuhiro Kimura
From: Andrea Venturoli Subject: ClamAV requiring COMPAT_FREEBSD11 Date: Thu, 4 Aug 2022 12:49:11 +0200 > > Hello. > > I build clamav-0.105.1,1 (from quarterly branch) in Poudriere and I've > always used it without problems. > > Suddenly last night freshclam started dying on a few machines: it

ClamAV requiring COMPAT_FREEBSD11

2022-08-04 Thread Andrea Venturoli
Hello. I build clamav-0.105.1,1 (from quarterly branch) in Poudriere and I've always used it without problems. Suddenly last night freshclam started dying on a few machines: it turn out it prints "bad system call", due to the lack of COMPAT_FREEBSD11 in the kernel. Strangely it's been wor

nextcloudclient and QNetwork

2022-08-04 Thread Per olof Ljungmark
Hello, Again this problem returned, the client stop syncing after a short time and logs: 2022-08-03 15:43:42:861 [ warning nextcloud.sync.networkjob /usr/ports/deskutils/nextcloudclient/work/desktop-3.5.2/src/libsync/abstractnetworkjob.cpp:224 ]: QNetworkReply::HostNotFoundError "Host not f

Re: ports-mgmt/pkg: pkg query -e %#r condition doesn't match properly

2022-08-04 Thread Tatsuki Makino
Looking at "pkg shell .dump | grep \ deps\ " results, it seems that origin without @flavor is not unique. However, ports that use FLAVORS are modified to make the PKGNAME unique. So, the following patch is applied and it seems to be working properly. The commands used in the tests are as follows.