Re: /etc/localtime symlink in poudriere jails
Dag-Erling Smørgrav escreveu (quarta, 11/12/2024 à(s) 09:37): > Nuno Teixeira writes: > > I'm trying to find why there is no /etc/localtime in poudriere jails > > and I need to create manually a symlink for some R-cran tests inside > > interactive jail. > > This shouldn't matter. The correct behavior if /etc/localtime is > missing is to assume UTC; if the tests don't do that then they are > broken and need to be fixed. Can you provide logs, or a step-by-step > procedure to reproduce the problem? > > DES > -- > Dag-Erling Smørgrav - d...@freebsd.org > Hello des and sorry for delay. I have a nice example of a failing test when no /etc/localtime exists (tested under poudriere jail) Update ports and make sure that you have https://cgit.freebsd.org/ports/commit/?id=2a132052a96744d4032b6bd8e707e13f87de9e7d $ poudriere testport -i > su > make test Cheers -- Nuno Teixeira FreeBSD UNIX: Web: https://FreeBSD.org
Help in adding flavor support to sysutils/vimpager
Hi. I want to add flavors support to sysutils/vimpager but i am unable to do it. I need to use x11 flavor of editors/vim because I need clipboard support which isn't available in console (default) flavor of editors/vim. What I want to do is, When I install vimpager's x11 or any other flavor of vimpager, it should pick up editors/vim's x11 flavor, not console flavor. Currently, it doesn't work that way, it only picks up editors/vim console flavor. So, both flavors of editors/vim and sysutils/vimpager should match to each other. I don't know if it's possible but I guess it is. Any help appreciated, thanks in advance and happy new year! Here is the bugzilla report URL: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283220
sliming down devel/llvm11
In an effort to reduce build times a little prior to devel/llvm20 coming in the next month or so I took a look at devel/llvm11. AFACT there isn't a good path to remove it entierly due to dependencies in lang/ghc810 and lang/ghc92 (at least on armv7 and maybe aarch64). For now I've put together a set of patches to remove other references to it in ports and in the USES framework and then slim it down to just building the LLVM core which is what I think GHC needs. Those patches are at https://github.com/freebsd/freebsd-ports/pull/337 I've CC'd maintainers of everything I've touched. I'm willing to submit them another way if that is prefered, but this rolls them all up in one place and most are trivial. Please let me know what you'd like me to do about the various patches. Thanks, Brooks
Re: Why does it take so long to build some Python ports
On Fri, 3 Jan 2025 08:41:08 +0100 Xavier Humbert wrote: > Some, but not all python ports spend a long time in building eggs > > Ex : > > running egg_info > writing src/charset_normalizer.egg-info/PKG-INFO > writing dependency_links to > src/charset_normalizer.egg-info/dependency_links.txt > writing entry points to > src/charset_normalizer.egg-info/entry_points.txt writing requirements > to src/charset_normalizer.egg-info/requires.txt writing top-level > names to src/charset_normalizer.egg-info/top_level.txt > > *pstree -w *shows : > > | | \-+- 64353 root /usr/local/bin/python3.11 -m build > --no-isolation --wheel > | | \-+- 64468 root /usr/local/bin/python3.11 > /usr/local/lib/python3.11/site-packages/pyproject_hooks/_in_process/_in_process.py > > build_wheel /tmp/tmptnbyl41r > | | \--- 64471 root git archive --prefix > /usr/ports/ HEAD > > What is the purpose of *git archive* ? There is no invocation of "git archive" in /usr/ports/Mk/Uses/py* Python port mechanism, in fact neither in the whole subtree of /usr/ports/Mk. Which means this is not ports that make use of it, but rather upstream tooling. I suspect what you are observing is actually a code if the py-setuptools-scm package: Name : py311-setuptools-scm Version: 8.0.4 Origin : devel/py-setuptools-scm WWW: https://github.com/pypa/setuptools_scm Comment: Setuptools plugin to manage your versions by scm tags Description: Handles managing your python package versions in scm metadata instead of declaring them as the version argument or in a scm managed file. HTH, -- Piotr Smyrak
Unmaintained FreeBSD ports which are out of date
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 port. If any ports have already been updated, you can safely ignore the entry. An e-mail will not be sent again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ emulators/wine-devel| 10.0-rc3| 10.0-rc4 +-+ net/ladvd | 1.1.2 | v1.1.4 +-+ sysutils/rshim-user-space | 2.0.9 | rshim-2.2.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
