update devel/py-setuptools itself,
which will specify devel/py-wheel as both {BUILD,RUN}_DEPENDS, you will
need to also specify the latter in each setuptools PEP-517 consumer.
I will update the documentation (mostly the wiki?) accordingly.
--
Charlie Li
...nope, still don't have a
Charlie Li wrote:
Daniel Engberg wrote:
On 2024-12-31T17:26:55.000+01:00, Pavel Timofeev
wrote:
Hello
I'm wondering if anybody has been working on spidermonkey115 port.
I need it for lang/cjs in scope of my bring latest cinnamon 6.4
effort.
I can create a port on m
per major version with SONAMEs reflecting such. cjs syncs with
gjs every so often but always lags behind. I will take care of this.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
ses were to
support desktop@ software builds and development.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
on this didn't show the answer)
Not sure if you figured it out or got your answer yet, but the
maintainer's bugzilla account email needs to match the MAINTAINER line
for that part of the automation to work. I see that the automation did
fire a mail to the listed MAINTAINER though.
--
sabled
this is moot.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
be used for major ports that involve lang/rust use.
No. Not something upstream encourages by default even if support exists,
especially because the default upstream builds use the bundled LLVM
which is what most consumers qualify with.
--
Charlie Li
...nope, still don't have
j...@chen.org.nz wrote:
Hi,
Can a committer please review/commit the following PR?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281253
Done.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
rything else in your diff seems fine as long as it runs as intended.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
py39-recommonmark-0.5.0_2 py39-sphinx-5.3.0_1,1 py39-requests-2.31.0
py39-urllib3-1.26.18,1
You need to disable SSL from net/py-urllib3. The option has been
disabled by default for like half a year now.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Descri
any of this as suggesting ports be a software museum. We
are not in the business of coercing users to change their workflows all
because a project's activity falls below some arbitrary threshold for
our purposes.
We do not need another dns/djbdns debacle. That was horrendous.
--
Florian Smeets wrote:
On 28.02.24 22:09, Charlie Li wrote:
Florian Smeets wrote:
This policy should give some guidance on when ports can or should be
removed. In general ports should not be removed without reason but if
a port blocks progress it should be deprecated and subsequently
removed
OL dependencies.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Yuri wrote:
On 2/15/24 22:48, Charlie Li wrote:
This distinction does not practically exist; any Python package, even
if primarily a program, can be specified and imported as a library in
another as a dependency. See meson, which had to grow flavours when
meson-python came about.
This
t the default flavour for those
cases can be considered however.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
This isn't really a policy issue, rather a
technical one.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Yuri wrote:
Hi,
More and more Python packages require Python versions higher than 3.9.
The next bump will be to 3.11, in keeping with the n-1 cadence. 3.12 is
not ready yet, not without the setuptools overhaul amongst other things.
--
Charlie Li
...nope, still don't have an exit
id=274284
This method of building had been deprecated and current upstream
versions removed it entirely. Currently prepping an update.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
rts commit
761dc8a9f4ddef2adad122a57a477e65457582fb. It was an OPTION that should
not have been default for other reasons.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature.asc
Description: OpenPGP digital signature
I have no clue about).
The port's patches simply change from using network sockets to Unix
domain sockets. They are quick and dirty and would need to be
re-architected for submission upstream, where a big consideration was
given (and actively used) towards using cloud storage for cached
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 diff
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
/reference/linkage.html
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
, which they are happy to
consider.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
egacy
in make.conf fixed this BS for me. Beware of the dogs, you might get
bitten by software that requires the new py-cryptography - I did stumble
over py-certbot and py-awscli for example.
Because the APIs for the non-SSL/TLS bits changed drastically with the
Rust code.
--
Charlie Li
...nope,
tched from C to Rust for the non-SSL/TLS bits like
X.509. There were good technical reasons for the change from their point
of view despite all the ensuing backlash.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
thod, you will eventually need to figure
out environment isolation for port builds; poudriere simply automates
much of the FreeBSD bits. Many threads on these mailing lists stem
precisely from not having isolated and clean build environments.
--
Charlie Li
...nope, still don't have an e
ave a choice
but to build rust every time.
--
Charlie Li
...nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
vides/requires code beginning with
https://github.com/freebsd/pkg/commit/cbd6eecd61ea7712aae3fb814fcd4a15936eb4d0
was more I/O and CPU-heavy than expected. Such have been reverted with
1.20.4.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
d/pkg/issues/2156 to track this.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
h glib-based applications.
In some cases
> > it is feasible to fix the callback function to have the correct
> > signature, in other cases you can slap a cast in place. Or,
if the
> > affected code is vala-generated (also happens), the big
hammer is to
> > suppress the warning(s).
> >
> > -Dimitry
> >
> Not a glib expert here, but you can try this
https://pastebin.com/ty8hLjVU <https://pastebin.com/ty8hLjVU>
>
>
>
> --
> Nuno Teixeira
> FreeBSD Committer (ports)
--
Nuno Teixeira
FreeBSD Committer (ports)
--
Nuno Teixeira
FreeBSD Committer (ports)
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
KIRIYAMA Kazuhiko wrote:
On Wed, 21 Jun 2023 20:52:20 +0900,
Charlie Li wrote:
[1 Re: x11/nvidia-driver build failed at devel/py-importlib-metadata
]
[1.1 ]
KIRIYAMA Kazuhiko wrote:
Hi, list
x11/nvidia-driver build failed at devel/py-importlib-metadata:
Copying importlib_metadata.egg-info
/msrvkx/textproc/py-markdown
*** Error code 1
Make sure your tree is fully updated, since it appears you have a very
old version of importlib-metadata. Partial tree updates are not, will
not and never have been supported.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signa
ur Python ports.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
and not a
feature knob, encapsulating both setuptools{,_scm} can be considered.
Still have reservations even for this however.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
the Python package side.
I have 7.1.0 working locally, PEP-517-ified and all.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
sumers have
to be rebuilt (and PORTREVISIONs are bumped accordingly). Namely, it
appears that you didn't rebuild ImageMagick6.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
gt; on 192.168.1.254:53: write udp 127.0.0.1:65047->192.168.1.254:53: write: can't assign requested address
There is absolutely no network access allowed outside the do-fetch
phase. You need to specify all your module dependencies and have them
checksummed beforehand. Take a look at other
LLVM sources.
But that doesn't address an even bigger issue that's still being
figured out: how to make this whole situation, LTO or not, less
fragile to deal with.
I see - do you want me to revert this commit?
Please do.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
ue that's still being figured
out: how to make this whole situation, LTO or not, less fragile to deal
with.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
matic when
poudriere is set to enable non-static ccache, ie the jail adds
devel/ccache to BUILD_DEPENDS automatically.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
or the maintainer is busy with other things.
To add, we have to do this for *every* boost update because the API is
not stable between versions.
We have an overlay repository [0] if anyone would like to help move it
along.
[0] https://github.com/fluffykhv/freebsd-ports-boost
--
Charlie Li
…nope,
g-message. This zoom client is light and work fine on my
laptop.
I was started `pulseaudio -v --start' and run `zoom' then
pulseaudio crashed and could not use audio. All information
on termial was as follows :
pkg-message specifically mentions the Linux PulseAudio package, not the
Free
default
flavour that by default enables everything but GNU Radio Companion (GRC,
a GUI tool), grc to explicitly also enable GRC and headless to exclude
all GUI-related components, meant for running existing flowgraphs.
Patches, comments, etc are welcome!
--
Charlie Li
…nope, still don't have an
gets detected. However, when switching from a
port to base, it appears that a dependency is removed. This is why you
cannot mix and match options like you did, especially in a panic.
--
Charlie Li
…nope, still don't have an exit line.
OpenPGP_signature
Description: OpenPGP digital signature
Tatsuki Makino wrote:
> I haven't followed everything, but have you tried to rebuild libressl?
>
Rebuilding LibreSSL itself doesn't help anything in this case. Consumers
are a different story since there is an apparent SSL_DEFAULT mismatch in
the same pkg repository.
--
Charlie
probably another couple of hours),
> if it succeeds I'll update all my boxes with the new ports using base
> openssl instead of libressl then update the ports tree and start another
> build with libressl to see how it goes with your commit.
>
I recommend that you do not pass go an
48 matches
Mail list logo
