urs. (Not least because
there are things I'd rather be doing instead.) Sorry for the downtime.
Philip [clusteradm troublemaker]
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
On 2022-07-27 10:23:16 (+0800), Philip Paeps wrote:
The hardware pkg-status.freebsd.org lives on has been deeply unhappy
for a while. I'm moving it to a different machine today. I usually
try to do these things so they go unnoticed ... unfortunately, that
didn't work out this time
than to the builders
directly. They've changed that yesterday.
Philip [hat: clusteradm]
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
27;t build on the package builders. Package builders only have
internet access during the "make fetch" stage. The ports framework will
want to check the checksums listed in distinfo at that time.
Philip
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
No other email was affected.
Philip [hat: postmaster]
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
On 2024-01-26 08:51:32 (+0800), Tom Rushworth wrote:
Something's eating the first '.' in the envelope address on my emails
to Cy
Schubert, but NOT eating them when I send to the ports list. I think
I've
probably annoyed the ports list enough for today with this weird
non-ports
problem, so I'
On 2024-04-18 23:02:30 (+0800), Mark Millard wrote:
void wrote on
Date: Thu, 18 Apr 2024 14:08:36 UTC :
Not sure where to post this..
The last bulk build for arm64 appears to have happened around
mid-March on ampere2. Is it broken?
main-armv7 building is broken and the last completed build
On 2024-04-24 02:12:41 (+0800), Mark Millard wrote:
On Apr 19, 2024, at 07:16, Philip Paeps wrote:
On 2024-04-18 23:02:30 (+0800), Mark Millard wrote:
void wrote on
Date: Thu, 18 Apr 2024 14:08:36 UTC :
Not sure where to post this..
The last bulk build for arm64 appears to have
On 2024-04-18 23:02:30 (+0800), Mark Millard wrote:
void wrote on
Date: Thu, 18 Apr 2024 14:08:36 UTC :
Not sure where to post this..
The last bulk build for arm64 appears to have happened around
mid-March on ampere2. Is it broken?
main-armv7 building is broken and the last completed build
On 2024-04-18 23:14:22 (+0800), Mark Millard wrote:
On Apr 18, 2024, at 08:02, Mark Millard wrote:
void wrote on
Date: Thu, 18 Apr 2024 14:08:36 UTC :
Not sure where to post this..
The last bulk build for arm64 appears to have happened around
mid-March on ampere2. Is it broken?
main-armv7
On 2024-05-08 23:53:57 (+0800), Mark Millard wrote:
On Apr 29, 2024, at 20:16, Mark Millard wrote:
On Apr 29, 2024, at 20:11, Mark Millard wrote:
On Apr 29, 2024, at 19:54, Mark Millard wrote:
On Apr 28, 2024, at 18:06, Philip Paeps wrote:
On 2024-04-18 23:14:22 (+0800), Mark
On 2024-05-29 11:37:04 (+0800), Mark Millard wrote:
In the mean time: The "IPv4 Proxy" buttons/links on the lines for
beefy2[012] at https://portsfallout.com/server allow looking at the
build activity on those machines. The lines also show which build
environment (such as "140amd64-default" or
On 2024-05-29 12:03:52 (+0800), Mark Millard wrote:
On May 28, 2024, at 20:45, Philip Paeps wrote:
On 2024-05-29 11:37:04 (+0800), Mark Millard wrote:
In the mean time: The "IPv4 Proxy" buttons/links on the lines for
beefy2[012] at https://portsfallout.com/server allow looking at
On 2024-07-03 15:21:33 (+0800), Milan Obuch wrote:
fatal: unable to access 'https://git.freebsd.org/ports.git/': The
requested URL returned error: 500
Anybody else or it is just for me?
This should be fixed.
A configuration file went missing on one of the mirrors.
Automation-fail.
;; AN
On 2024-07-26 22:46:57 (+0800), Mark Millard wrote:
So, it looks like updating the kernel and world on ampere2 and
enabling builds of main-armv7-default should no longer have
main-armv7-default hang-up during graphviz installation (or
analogous contexts). Hopefully, that means that
main-armv7-def
On 2024-08-10 17:29:57 (+0800), Ronald Klop wrote:
Looking at https://pkg-status.freebsd.org/builds?all=1&type=package
and search for “ampere” it seems that no arm64 builds have been
started since July.
Is this on purpose or is something broken?
Sorry. I broke something. I paused builds fo
On 2024-08-24 14:34:01 (+0800), Mark Millard wrote:
On Aug 19, 2024, at 20:17, Mark Millard wrote:
main-arm64-default p60a177caf143_s7a8d05ba19b
finished its last package build at: Aug 19 17:50:28 UTC 2024,
building 34197 of 35762 Queued
The next build to start on ampere2 was:
main-arm64-de
On 2024-08-25 14:01:09 (+0800), Philip Paeps wrote:
On 2024-08-24 14:34:01 (+0800), Mark Millard wrote:
On Aug 19, 2024, at 20:17, Mark Millard wrote:
main-arm64-default p60a177caf143_s7a8d05ba19b
finished its last package build at: Aug 19 17:50:28 UTC 2024,
building 34197 of 35762 Queued
On 2024-08-27 10:34:18 (+0800), Mark Millard wrote:
main-arm64-default on ampere2 has started building as of Tue, 27 Aug
2024 01:58:37 GMT. 14609 were queued.
So, unless that is stopped, it will likely be days before
main-armv7-default would be started.
The arm builds are currently scheduled
.
Meanwhile, if you have to downgrade, you can always do a pkg install
/var/db/pkg/openldap-version-that-worked.
Philip
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
On 2021-06-07 18:11:10 (+0800), Philip Paeps wrote:
On 2021-06-07 17:47:57 (+0800), Per olof Ljungmark wrote:
A bit urgent...
After updating to openldap-server 2.59 slapd refuses to start, how
can I revert to 2.57 with ports and git while troubleshooting the
update?
You're probably ru
On 2021-06-07 18:32:18 (+0800), Per olof Ljungmark wrote:
On 6/7/21 12:11 PM, Philip Paeps wrote:
On 2021-06-07 17:47:57 (+0800), Per olof Ljungmark wrote:
A bit urgent...
After updating to openldap-server 2.59 slapd refuses to start, how
can I revert to 2.57 with ports and git while
On 2024-10-22 16:52:26 (-0400), Ronald Klop wrote:
Ampere2 is building armv7 again
https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-armv7-default&build=p94c4ac6b071b_sc87b3f0006
BTW: I made a graph that shows how old a pkg repo is per
architecture.It shows that arm/aarch64 is s
On 2025-04-05 00:37:47 (+0800), Kevin Oberman wrote:
There appear to have been no successful package updates for FreeBSD
since
EOL for 14.1-AMD64. The only build for 142amd64-default that one
appears to
have crashed. As a result, I am seeing a growing list of packages that
are
not getting updat
On 2025-04-09 10:40:14 (+0800), Mark Millard wrote:
Re: FYI: beefy16's build of ko-ko.TeX-fonts-extra-0.1.0_6 has over 200
hrs elapsed and is still running patch [IGNORE THIS: I looked at an
old run]
Ah. I was going to write "wait, which builder?" :-)
Philip
On 2025-04-09 10:36:44 (+0800), Mark Millard wrote:
https://pkg-status.freebsd.org/beefy16/build.html?mastername=134amd64-default&build=da5207f3c65e
shows:
03 ko-ko.TeX-fonts-extra-0.1.0_6 korean/ko.TeX-fonts-extra patch
200:35:36
I'll note that the load averages are shown as: ( 1%) 0.16 0.1
On 2025-04-29 12:04:01 (+0800), Mark Millard wrote:
Issue #0 (general Quarterly issue):
Quarterly is still based on pkg 2.1.0 (the time consuming
version), not on the intended-improvement pkg 2.1.2 .
It is the large builds, such as "bulk -c -a" ones, that
likely end up being far more noticeabl
On 2025-05-07 22:50:35 (+0700), Mark Millard wrote:
> The below is visible in via:
>
> https://pkg-status.freebsd.org/builds?type=package&all=1
>
> (the normal Package Builds viewing area).
>
> Why are beefy8 and beefy7 suddenly both doing parallel
> builds of 142amd64-default with build names like
On 2025-07-19 00:35:27 (+0800), Mark Millard wrote:
> There was a problem with the ports tree that lead to ampere2, beefy15,
> beefy21, and beefy22 failing to even queue any packages.
>
> After the ports tree was fixed to not cause that, beefy15, beefy21,
> and beefy22 were restarted using a vintag
On 2025-07-10 22:20:33 (+0800), Mark Millard wrote:
> On Jul 3, 2025, at 13:18, Philip Paeps wrote:
>
>> On 2025-07-04 07:43:32 (+1200), Mark Millard wrote:
>>> Host OSVERSION: 1500038
>>> instead of the 1500035 shown on the other 2 ampere*'s.
>>> Howe
On 2025-07-04 07:30:49 (+1200), Mark Millard wrote:
https://pkg-status.freebsd.org/ampere1/build.html?mastername=142arm64-quarterly&build=d7951ee861c2
ampere1 panicked twice this week for no apparent reason.
Philip
On 2025-07-04 07:43:32 (+1200), Mark Millard wrote:
> Host OSVERSION: 1500038
> instead of the 1500035 shown on the other 2 ampere*'s.
> However, ampere1 has been that way starting with:
> Started 03 May 2025 03:10:51 GMT
> So its use of 1500038 is not new.
I haven't done an upgrade in a while.
I
32 matches
Mail list logo
