Hello, again.
I am replying here again because there are so many statements present that I
don't know where to hang.
My poudriere is collecting the time costs required to build the package by
means of an experiment.
Well, although it's simply the number of seconds it took to build :)
Sorting thr
(I have reduced some of my reply addresses and replied to them.)
Charlie Li wrote on 2023/09/27 20:11:
> Guido Falsi wrote:
>> On 27/09/23 12:57, Guido Falsi wrote:
>>> On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
> In poudriere, apart from t
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
Hello.
The following fix need to be made.
https://lists.freebsd.org/archives/freebsd-ports/2023-September/004440.html
Regards.
This was while the build host was running stable/12
(stable/12-n236282-b083794291d2). A subsequent attempt whlie it was
running stable/13 (stable/13-n256426-d03af6473e64) was OK.
Log is in https://www.catwhisker.org/~david/FreeBSD/ports/chromium/;
there's a compressed copy and an uncompressed one
On 9/27/23 01:42, Charlie Li wrote:
> Jose Quinteiro wrote:
>> The sudden appearance of a Rust requirement broke at least some CI
>> systems:
>> https://github.com/pyca/cryptography/issues/5771#issuecomment-774997087
>>
> And that's not py-cryptography's or anyone else's problem except for
> those
Alexander Leidinger wrote:
Am 2023-09-27 13:04, schrieb Guido Falsi:
I'm not completely sure we;re talking about the same thing. The
scccache version you're using is an older version with non standard
changes (as vishin pointed out, did not check it or the nature of the
changes or differences
Am 2023-09-27 13:04, schrieb Guido Falsi:
I'm not completely sure we;re talking about the same thing. The
scccache version you're using is an older version with non standard
changes (as vishin pointed out, did not check it or the nature of the
changes or differences with newer versions). Maybe
Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
ports-mgmt/sccache-overlay's functionality that allows it to work in a
poudriere/port build environment relies on code that was never
submitted upstream to sccache.
More than the mk file and the install into a different loca
Guido Falsi wrote:
On 27/09/23 12:57, Guido Falsi wrote:
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens on an IP that
does not necessar
On 27/09/23 13:00, Alexander Leidinger wrote:
Am 2023-09-27 12:57, schrieb Guido Falsi:
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens o
Am 2023-09-27 12:57, schrieb Guido Falsi:
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens on an IP that
does not necessarily exist that c
On 27/09/23 12:57, Guido Falsi wrote:
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens on an IP that
does not necessarily exist that clien
Hi!
> How is poudriere preventing network access outside the fetch phase?
I think by starting the builder jail without IP.
--
p...@freebsd.org +49 171 3101372 Now what ?
Am 2023-09-27 10:56, schrieb Charlie Li:
ports-mgmt/sccache-overlay's functionality that allows it to work in a
poudriere/port build environment relies on code that was never
submitted upstream to sccache.
More than the mk file and the install into a different location suitable
for the overl
On 27/09/23 12:54, Alexander Leidinger wrote:
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not
allowed by default so spawning a server that listens on an IP that
does not necessarily exist that clients, individual compiler
invocations, t
Am 2023-09-27 10:56, schrieb Charlie Li:
In poudriere, apart from the fetch phase, network access is not allowed
by default so spawning a server that listens on an IP that does not
necessarily exist that clients, individual compiler invocations, talk
to isn't tenable. At the very least, one wo
Tomoaki AOKI wrote:
On Tue, 26 Sep 2023 22:03:18 +0200
Thierry Thomas wrote:
This is true, but rust is very heavy, and it seems to be updated quiet
frequently.
Just an idea: maybe it could be possible to repocopy lang/rust to e.g.
lang/rust-devel (we already have rust-nightly), lang/rust being
Hello, everyone who doesn't want to rebuild the rust in poudriere many times :)
Although poudriere-devel exists the feature to download officially created
packages...
There is also a way to mix packages made elsewhere :)
# First, bring the package from somewhere else.
# package name should be es
Alexander Leidinger wrote:
Am 2023-09-26 14:06, schrieb Kurt Jaeger:
sccache-overlay upstream is at 0.5.4, the port is at 0.2.15 --
do you know why it diverges that much ?
devel/sccache is maintained by pizzamig@ (CCed) and at v0.5.4, whereas
the ports-mgmt/sccache-overlay port is maintained
Helge Oldach wrote:
Indeed, it's py-sphinx, requiring py-openssl at some stage, which is in
turn requiring py-cryptography which needs rust.
FWIW I disabled by default the part that actually pulls in
py-cryptography, the SSL option in net/py-urllib3.
DEFAULT_VERSIONS+=pycryptography=legacy
in
Jose Quinteiro wrote:
The sudden appearance of a Rust requirement broke at least some CI systems:
https://github.com/pyca/cryptography/issues/5771#issuecomment-774997087
And that's not py-cryptography's or anyone else's problem except for
those CI systems.
cryptography switched from C to Rust
On 27/09/23 02:28, Jose Quinteiro wrote:
On 9/26/23 09:14, Guido Falsi wrote:
(snip)
And yet I remember a proposal that would have prevented this requirement
on one of these lists. Separate base SSL from ports SSL. Force ports to
use ports SSL and prune back base SSL to the bare minimum require
23 matches
Mail list logo
