Hello.
All the packages I have had poudriere make and hold were ready this morning
(TZ=Asia/Tokyo :), 5 hours ago).
However, this equilibrium was broken by glib update 4 hours ago :)
232 ports are now queued again.
If only graphics/cairo is built manually first here, only 2 packages, glib and
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
On Tue, 24 Oct 2023, Dan Mahoney (Ports) wrote:
All,
I’ve lost another morning to a bad choice made by ports/pkg.
Maybe this is a dumb question/rant, but recently, a routine pkg upgrade
of the dayjob’s RT VM (which included an upgrade to perl) decided to
leave me with no ability to connect.
25.10.2023 21:20, Andrea Venturoli пишет:
Hello.
I'm experiencing a "make index" failure.
Problem seems to be www/tomcat-devel was MFH and requires Java 21+,
but 21 is not available in Q4.
(20 is the last present, but 18 is the last available from bsd.java.mk).
Nothing I can't solve locally
I've updated all packages on the system from the 13.2/latest ports
repository and now Firefox is crashing.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274719
Yuri
Hello.
I'm experiencing a "make index" failure.
Problem seems to be www/tomcat-devel was MFH and requires Java 21+, but
21 is not available in Q4.
(20 is the last present, but 18 is the last available from bsd.java.mk).
Nothing I can't solve locally (especially since I don't use tomcat-devel
On Tue, Oct 24, 2023 at 1:55 PM Brooks Davis wrote:
>
> I'll reply to LLVM specific suggestions
A big win would be to reduce the number of LLVMs required for common
desktop ports. Aside from the base system LLVM, my desktop system
seems to build llvm 12, 13, 15.
>
> On Tue, Oct 24, 2023 at
On Oct 25, 2023, at 04:37, 風來散人 wrote:
> Does anybody know what is the actual problem behind this? I had to switch
> quarterly to latest on 13.2 last week because perl5.32 didn't have EOL tag on
> quarterly. So I wasn't able to upgrade perl5 from perl5.32 to perl5.34
> smoothly by "pkg
Am 2023-10-25 11:57, schrieb DutchDaemon - FreeBSD Forums Administrator:
On 25/10/2023 11:12, Ronald Klop wrote:
And there are also other implementations of the ACME protocol in the
ports tree like security/acmetool. I have no experience with them but
they might fit your use case.
[Unsure who is best for reporting this to.]
http://ampere3.nyi.freebsd.org/build.html?mastername=132arm64-default=08943441f26e
shows it. The load averages are changing some, as is the Elapsed. The logs are
showing things like:
===
===>
I'm building 2200 ports on a Dell PowerEdge r210, 16GB RAM, 34GB swap, 8
CPU; system is 1400094 and ports from git October 14; and I use for rust
a single podriere job. The build time was:
...
===> Cleaning for rust-1.72.0
build of lang/rust | rust-1.72.0 ended at Sun Oct 15 03:04:41 CEST 2023
On 25/10/2023 11:12, Vidar Karlsen wrote:
On Wed, Oct 25, 2023 at 09:22:11AM +0200, Dutch Daemon - FreeBSD Forums
Administrator wrote:
On October 24, 2023 14:54:40 DutchDaemon - FreeBSD Forums Administrator
wrote:
Does anyone in 'port land' know what the current developments are wrt
CertBot
Cy Schubert writes:
> > > How much RAM does your machine have? How many CPU
> > cores/threads does i> t
> > > have?
> > >
> > I have 16 GB RAM, and 4 cores
>
> That should be plenty. I build it on a 4 core 8 GB machine.
>
> How much swap does it have?
Data point: I
Hi,
On Wed, Oct 25, 2023 at 08:38:54AM +0200, Xavier Humbert wrote:
Hi,
When building rust, all memory is eaten, leading to OOM killing almost
everything, eventually failing, and leading to an unstable system.
Is there a way to tell the compiler to avoid this behaviour ?
Are you building
On 25/10/2023 11:12, Ronald Klop wrote:
Hi,
I see that you are compiling certbot to openssl from ports. Apparently
you are running a not often used configuration of the port.
I'm not so sure about that. OpenSSL in ports is usually quite a lot
ahead of base system OpenSSL, which is why I
On 25/10/2023 11:12, Vidar Karlsen wrote:
On Wed, Oct 25, 2023 at 09:22:11AM +0200, Dutch Daemon - FreeBSD Forums
Administrator wrote:
On October 24, 2023 14:54:40 DutchDaemon - FreeBSD Forums Administrator
wrote:
Does anyone in 'port land' know what the current developments are wrt
CertBot
Hi,
I see that you are compiling certbot to openssl from ports. Apparently you are
running a not often used configuration of the port.
Did you try reaching out to the maintainer of the port (pyt...@freebsd.org)?
And there are also other implementations of the ACME protocol in the ports tree
On Wed, Oct 25, 2023 at 09:22:11AM +0200, Dutch Daemon - FreeBSD Forums
Administrator wrote:
> On October 24, 2023 14:54:40 DutchDaemon - FreeBSD Forums Administrator
> wrote:
> > Does anyone in 'port land' know what the current developments are wrt
> > CertBot (or py-crypto under its hood)?
> >
Le 10/25/23 09:18, Matthew Seaman a écrit :
* Stopping rust and some other large ports building on tmpfs
TMPFS_BLACKLIST='rust gcc* llvm* texlive-texmf'
TMPFS_BLACKLIST_TMPDIR=/usr/local/poudriere/data/cache/tmp
USE_TMPFS=yes
TMPFS_LIMIT=4
Tried this (in make.conf, I
On Wed, 25 Oct 2023 09:03:48 +0200
Xavier Humbert wrote:
> Le 10/25/23 09:01, Cy Schubert a écrit :
> > In message<5816a79c-9bd0-4c41-9520-eed853aa1...@groumpf.org>, Xavier
> > Humbert w
> > rites:
> >> Le 10/25/23 08:46, Cy Schubert a écrit :
> >>> In
On October 24, 2023 14:54:40 DutchDaemon - FreeBSD Forums Administrator
wrote:
Does anyone in 'port land' know what the current developments are wrt
CertBot (or py-crypto under its hood)?
CertBot is happily compiling against OpenSSL 3 from ports, but when running
'certbot', the crypto side of
On 25/10/2023 07:47, Xavier Humbert wrote:
Le 10/25/23 08:46, Cy Schubert a écrit :
In message <09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier
Humbert w
rites:
Hi,
When building rust, all memory is eaten, leading to OOM killing almost
everything, eventually failing, and leading to
Le 10/25/23 09:01, Cy Schubert a écrit :
In message<5816a79c-9bd0-4c41-9520-eed853aa1...@groumpf.org>, Xavier
Humbert w
rites:
Le 10/25/23 08:46, Cy Schubert a écrit :
In message<09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier
Humbert w
rites:
Hi,
When building rust, all memory is
In message <5816a79c-9bd0-4c41-9520-eed853aa1...@groumpf.org>, Xavier
Humbert w
rites:
> Le 10/25/23 08:46, Cy Schubert a écrit :
> > In message <09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier
> > Humbert w
> > rites:
> >> Hi,
> >>
> >> When building rust, all memory is eaten, leading
Le 10/25/23 08:46, Cy Schubert a écrit :
In message <09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier
Humbert w
rites:
Hi,
When building rust, all memory is eaten, leading to OOM killing almost
everything, eventually failing, and leading to an unstable system.
Is there a way to tell
In message <09a4bfb8-ba61-4e05-b646-973104337...@groumpf.org>, Xavier
Humbert w
rites:
> Hi,
>
> When building rust, all memory is eaten, leading to OOM killing almost
> everything, eventually failing, and leading to an unstable system.
>
> Is there a way to tell the compiler to avoid this
Hi,
When building rust, all memory is eaten, leading to OOM killing almost
everything, eventually failing, and leading to an unstable system.
Is there a way to tell the compiler to avoid this behaviour ?
Regards,
Xavier
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer
On Tue, Oct 24, 2023 at 9:12 PM Robert Clausecker wrote:
> The build times have gone up to the point where they are unsustainable.
> Frequent updates to key ports (like llvm*, rust, gcc*) make it so that
> basically every time I prepare a new batch of commits, I have to rebuild
> a variety of
28 matches
Mail list logo
