Re: what makes mail/aerc conflit with net/samba419?

2024-03-05 Thread Gleb Popov
On Wed, Mar 6, 2024 at 10:16 AM Hiroo Ono wrote: > > Hello, > > Trying to install mail/aerc, pkg says it conflicts with net/samba419. > > Installed packages to be REMOVED: > samba419: 4.19.5_1 It looks like you're building your own repo using poudriere and then installing from it? In thi

Re: math/sage misc/xiphos

2024-03-05 Thread Hiroo Ono
On Sun, 3 Mar 2024 12:05:30 -1000 bruce wrote: > What has happened to math/sage?  The port still exists but hasn't > built in well over a year.  Also misc/xiphos. The ports' Makefile says: BROKEN= hoping to fix it with Python-3.9 Looking here: https://github.com/sagemath/sage/pull/35404

what makes mail/aerc conflit with net/samba419?

2024-03-05 Thread Hiroo Ono
Hello, Trying to install mail/aerc, pkg says it conflicts with net/samba419. Installed packages to be REMOVED: samba419: 4.19.5_1

Re: PORTEPOCH reset when PKGNAMESUFFIX changes?

2024-03-05 Thread Mathieu Arnold
On Wed, Mar 06, 2024 at 07:50:43AM +0100, Alexander Leidinger wrote: > Hi, > > Does poudriere/pkg take the PKGNAMESUFFIX into account for a given origin? > > The context of the question is: > I have a patch for a php-using port which flavourizes it. It will go from no > PKGNAMESUFFIX to the usual

PORTEPOCH reset when PKGNAMESUFFIX changes?

2024-03-05 Thread Alexander Leidinger
Hi, Does poudriere/pkg take the PKGNAMESUFFIX into account for a given origin? The context of the question is: I have a patch for a php-using port which flavourizes it. It will go from no PKGNAMESUFFIX to the usual php version as PKGNAMESUFFIX. So the package name will change from abc-1.2.3_

Unmaintained FreeBSD ports which are out of date

2024-03-05 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

Re: FreeBSD ports community is broken [port building configuration notes]

2024-03-05 Thread Mark Millard
[I noticed that my SWAP figures were not self consistent for the armv7.] On Feb 18, 2024, at 09:50, Mark Millard wrote: > [I also forgot to mention an important FreeBSD configuration setting > as well. It is not specific to poudriere use.] > >> On Feb 18, 2024, at 09:13, Mark Millard wrote: >>

Re: Call for help: moving manpages to share/man

2024-03-05 Thread Moin Rahman
> On Mar 1, 2024, at 7:25 PM, Gleb Popov wrote: > > A small update: we're down to 705 ports failing and 342 skipped > according to the latest build run by bofh@ > > The updated list of failed ports can be obtained from the same URL as > before [1]. > > It is also worth mentioning that portmgr

Re: compiling for other architecture [armv6 targeting specifically]

2024-03-05 Thread Mark Millard
Mathieu Arnold wrote on Date: Tue, 05 Mar 2024 15:37:08 UTC : > I don't think you need to do much of the things you are saying, cross > building can't really work because most ports will compile something and > then try to run it, which won't work because an armv6 binary won't run > on a x86_64 m

Re: compiling for other architecture

2024-03-05 Thread Mathieu Arnold
Hi, I don't think you need to do much of the things you are saying, cross building can't really work because most ports will compile something and then try to run it, which won't work because an armv6 binary won't run on a x86_64 machine. What works on the other hand is using poudriere and qemu-u