Hi all, transmission fails to build/install with the following:
# make -C /usr/ports/net-p2p/transmission install clean
..
===> Staging for transmission-default-4.0.4_1
===> transmission-default-4.0.4_1 depends on file:
/usr/local/lib/libcrypto.so.11 - found
===> Generating temporary pack
Hi all, I've just upgraded bind916 which brought half my system down since
it suddenly required a mountain of python packages and rust which needed
around 13GB (and hours) to build - space which I didn't have nor have ever
remotely expected to need for a ports build.
My bind configuration options
Hi all, since sysutils/devcpu-data has been deprecated what is the process
to upgrade to sysutils/cpu-microcode ?
Should devcpu-data be removed (or left as is) and then cpu-microcode installed?
Presumably this will just change the firmware file to be loaded at boot time
and not affect the current
On 25/09/23 17:06, Gareth de Vaux wrote:
Hi all, I've just upgraded bind916 which brought half my system down since
it suddenly required a mountain of python packages and rust which needed
around 13GB (and hours) to build - space which I didn't have nor have ever
remotely expected to need for a p
On 25/09/23 17:07, Gareth de Vaux wrote:
Hi all, since sysutils/devcpu-data has been deprecated what is the process
to upgrade to sysutils/cpu-microcode ?
Should devcpu-data be removed (or left as is) and then cpu-microcode installed?
Presumably this will just change the firmware file to be loa
On Mon 2023-09-25 (18:03), Robert Clausecker wrote:
> This is related to bug #274025. A patch for this bug was pushed
> yesterday. Please update your ports tree and try again.
Thanks, confirmed working in 4.0.4_2.
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
> UPDATING entry 20230906 has all the details.
UPDATING entry 20230906 is the reason for the question - it does not say how
to safely migrate - do you uninstall devcpu-data and then install cpu-microcode?
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
> This one, which calls in py-cryptography which requires rust.
Thanks
> There is a more general aspect to this. In the rest of the unix world
> software is now almost universally build using CI systems and buildboxes,
> people use binary packages alm
You might also try:
echo "CONFIGURE_ARGS+=--without-python --disable-linux-caps" >>
/usr/ports/dns/bind916
before building. Heads-up as these CONFIGURE_ARGS won't persist a "make
config".
Roger Marquis
Hi all, I've just upgraded bind916 which brought half my system down since
it sudden
On 25/09/23 19:35, Gareth de Vaux wrote:
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
UPDATING entry 20230906 has all the details.
UPDATING entry 20230906 is the reason for the question - it does not say how
to safely migrate - do you uninstall devcpu-data and then install cpu-microcode?
Y
On 25/09/23 19:50, Gareth de Vaux wrote:
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
This one, which calls in py-cryptography which requires rust.
Thanks
There is a more general aspect to this. In the rest of the unix world
software is now almost universally build using CI systems and buil
On 25/09/23 20:33, Guido Falsi wrote:
On 25/09/23 19:50, Gareth de Vaux wrote:
On Mon 2023-09-25 (17:38), Guido Falsi wrote:
This one, which calls in py-cryptography which requires rust.
Thanks
There is a more general aspect to this. In the rest of the unix world
software is now almost univ
On 9/25/23 11:38, Guido Falsi wrote:
[...]
There is a more general aspect to this. In the rest of the unix world
software is now almost universally build using CI systems and
buildboxes, people use binary packages almost all the time in linux.
Developers don't care to keep low overhead in thei
Hi all,
> Am 25.09.2023 um 22:21 schrieb George Mitchell :
>
> On 9/25/23 11:38, Guido Falsi wrote:
>> [...]
>> There is a more general aspect to this. In the rest of the unix world
>> software is now almost universally build using CI systems and buildboxes,
>> people use binary packages almost
On 25/09/23 22:21, George Mitchell wrote:
On 9/25/23 11:38, Guido Falsi wrote:
[...]
There is a more general aspect to this. In the rest of the unix world
software is now almost universally build using CI systems and
buildboxes, people use binary packages almost all the time in linux.
Develop
On 9/25/23 16:29, Patrick M. Hausen wrote:
[...]
really not intending to be the wise guy, but if you have any significant
number of machines to manage and special package requirements,
please by all means run poudriere. It's a marvelous piece of software.
We went that way early 2017 and never lo
On 9/25/23 16:39, George Mitchell wrote:
[...] partmaster [...]
I meant portmaster, of course. -- George
George Mitchell wrote:
On 9/25/23 16:29, Patrick M. Hausen wrote:
[...]
really not intending to be the wise guy, but if you have any significant
number of machines to manage and special package requirements,
please by all means run poudriere. It's a marvelous piece of software.
We went that way
On 9/25/23 13:39, George Mitchell wrote:
On 9/25/23 16:29, Patrick M. Hausen wrote:
[...]
really not intending to be the wise guy, but if you have any significant
number of machines to manage and special package requirements,
please by all means run poudriere. It's a marvelous piece of software.
Am Mon, Sep 25, 2023 at 02:15:19PM -0700 schrieb Edward Sanford Sutton, III:
> Poudriere still causes crashes in my experience depending on hardware,
> poudriere configuration, and what you tell it to build; I have to change
> defaults to use it and then it is fine. With only 32GB of RAM, if I ha
> On Sep 25, 2023, at 14:41, Robert Clausecker wrote:
>
> Am Mon, Sep 25, 2023 at 02:15:19PM -0700 schrieb Edward Sanford Sutton, III:
>> Poudriere still causes crashes in my experience depending on hardware,
>> poudriere configuration, and what you tell it to build; I have to change
>> defau
On Mon, 25 Sep 2023, Guido Falsi wrote:
> Anyway building from ports on live machines has always been bad practice
> for a lot of reasons.
That's fine if you can afford a spare system just for building...
-- Dave
Hi Dan,
Am Mon, Sep 25, 2023 at 02:58:23PM -0700 schrieb Dan Mahoney:
> I really, really wish the ports tree supported the option of:
>
> "I am building package X, but it requires dependency A, B, and C,
> which I will build as completely standard, so pretty friggin please,
> just pkg install the
On 9/25/23 18:06, Dave Horsfall wrote:
On Mon, 25 Sep 2023, Guido Falsi wrote:
Anyway building from ports on live machines has always been bad practice
for a lot of reasons.
That's fine if you can afford a spare system just for building...
.. and identical architectures, specifications and
## Matthias Apitz (g...@unixarea.de):
> Creating enum POD...
> Can't find 'boot_Gtk2' symbol in blib/arch/auto/Gtk2/Gtk2.so
> at tools/podifystockitems.pl line 0.
That's fallout from devel/pkgconf - it got botched in 8e3a5d951e,
fixed in 4a1614a51d and broken again in 041cacb90b (same problem
as
Dan Mahoney wrote on
Date: Mon, 25 Sep 2023 21:58:23 UTC :
> > . . .
>
> I really, really wish the ports tree supported the option of:
>
> "I am building package X, but it requires dependency A, B, and C, which I
> will build as completely standard, so pretty friggin please, just pkg install
On Mon, 25 Sep 2023, Mark Millard wrote:
... it takes so long to build (and distribute) the 30,000+
packages (or any large incremental subset or subset that
involves huge builds) that a fair number ports have had
updates before the distribution completes and starts being
Even just getting the p
Dave Horsfall wrote:
Anyway building from ports on live machines has always been bad practice
That's fine if you can afford a spare system just for building...
Or $5/mo for a Digitalocean VM.
Roger
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
29 matches
Mail list logo
