Re: Issues updating step-certificates

Am 09.07.22 um 13:55 schrieb Markus Wipp: Hi all, I’m the maintainer of step-certificates and currently face some issues with this. I updated the ports Makefile for the newest version (see below). When I now try to make this e.g. with “make clean makes stage” it fails with the following erro

Re: problem with "make index"

Am 15.07.22 um 14:19 schrieb Robert Huff: Hello: On a system runing: 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-d6327ae8c1: Sun Jan 24 14:16:54 EST 2021 amd64 with the ports tree updated nightly, "make index" stops with: --- describe.x11-toolkits --- --- describe.x11-wm

Re: problem with "make index"

Am 15.07.22 um 23:38 schrieb Robert Huff: Steffan Esser: Am 15.07.22 um 14:19 schrieb Robert Huff: > > Hello: > On a system runing: > > 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-d6327ae8c1: > Sun Jan 24 14:16:54 EST 2021 amd64 > > with the por

Re: problem with "make index"

weeks since then, with the last update of the proposed patch ten days ago. Stefan Esser wrote: I have just committed a port for LLVM 14. It is build tested, but I did not have time to perform any run tests. First mistake. The entire WASI toolchain has to be updated, since this is LLVM and no API

Re: problem with "make index"

Am 17.07.22 um 00:27 schrieb Charlie Li: Stefan Esser wrote: The reason that I have committed the port at this time was that "make index" is broken with LLVM_DEFAULT set to 14. I have considered this a fix of the port system, but forgot to mention that detail in the commit log. No

Re: svgalib build fail with portmaster

Am 20.07.22 um 14:55 schrieb Tomoaki AOKI: [...] Looking into commit log at cgit [1], the problematic file is already there at the first commit and unchanged afterwards. So the file should be there when you installed (or previously updated). See my reply to the OP, this is a port that removes f

Re: svgalib build fail with portmaster

Am 20.07.22 um 17:34 schrieb s...@freebsd.org: [...] I'll commit an update to the svgalib port when I succeed in locating the line that issues the "rm -f" command that deletes those files. I cn see "unlink" system calls being issued to remove them and I see the PID of the rm command (or rather s

Re: Why NOARCH packages aren't available on all architectures?

Am 06.08.22 um 09:40 schrieb Tatsuki Makino: Hmmm, it seems to me that this is a problem due to the difference between noarch being a tag-like classification and packages being provided in a tree-like classification for each architecture. Yes, this is the result of how NO_ARCH packages are be

Re: [NEWS] GitLab plans to delete dormant projects in free accounts

Am 04.08.22 um 19:19 schrieb Yuri: Hi, This article may be of interest to some because many ported projects are hosted on GitLab. https://www.theregister.com/2022/08/04/gitlab_data_retention_policy/ Old news ... :-) https://www.theregister.com/2022/08/05/gitlab_reverses_deletion_policy/ S

HEADS-UP: Upcoming move of WWW definitions in all ports

PortMgr has just accepted a change that has been in the making for some time: The move of the "WWW:" entries at the end of the ports' pkg-descr files into the ports' Makefiles in the form of "WWW=" definitions. The WWW lines will be put into the maintainer block, immediately following the MAINTA

Re: HEADS-UP: Upcoming move of WWW definitions in all ports

Am 06.09.22 um 20:31 schrieb Steve Kargl: On Tue, Sep 06, 2022 at 08:09:24PM +0200, Stefan Esser wrote: PortMgr has just accepted a change that has been in the making for some time: The move of the "WWW:" entries at the end of the ports' pkg-descr files into the ports' Make

Re: HEADS-UP: Upcoming move of WWW definitions in all ports

Am 06.09.22 um 21:32 schrieb Moin Rahman: On 9/6/22 9:04 PM, Stefan Esser wrote: [...] The idea to move the WWW entry from the pkg-descr to the Makefile has come up multiple times in the past, back in 2015 for the first time that I know of, see https://reviews.freebsd.org/D2949. It's r

Re: HEADS-UP: Upcoming move of WWW definitions in all ports

Am 06.09.22 um 21:08 schrieb Shawn Webb: On Tue, Sep 06, 2022 at 08:09:24PM +0200, Stefan Esser wrote: PortMgr has just accepted a change that has been in the making for some time: The move of the "WWW:" entries at the end of the ports' pkg-descr files into the ports' Make

Fwd: Move of WWW to Makefiles is rejected by the repository

ed it from the staging area, not that it would remove it from the repository. Reagrds, STefan Weitergeleitete Nachricht Betreff: Move of WWW to Makefiles is rejected by the repository Datum: Wed, 7 Sep 2022 22:44:32 +0200 Von: Stefan Esser An: portmgr My attempt to push the u

Re: HEADS-UP: Upcoming move of WWW definitions in all ports

Am 08.09.22 um 03:59 schrieb Kubilay Kocak: On 7/09/2022 4:09 am, Stefan Esser wrote: PortMgr has just accepted a change that has been in the making for some time: The move of the "WWW:" entries at the end of the ports' pkg-descr files into the ports' Makefiles

Re: make index is broken

Am 08.09.22 um 09:41 schrieb Vasily Postnicov: Hi! My port tree is on commit 9c85fa7 and my FreeBSD version is 13.1-RELEASE. It seems that after recent changes to the ports (moving of WWW entries to Makefiles) `make index` has become broken. Here are the last lines of `make index`: --- describ

Re: Python version dependencies in pkg

Am 29.09.22 um 08:39 schrieb Alexander Leidinger: Quoting Rainer Hurling (from Thu, 29 Sep 2022 06:43:49 +0200): Hi Dan, Am 28.09.22 um 23:01 schrieb Dan Mahoney: [...] Okay, so in either the package file, or the repo file, is there a bit that says "whatever is the default" or that explicit

Re: Python version dependencies in pkg

Am 29.09.22 um 21:52 schrieb Dan Mahoney:>> On Sep 28, 2022, at 23:39, Alexander Leidinger wrote: Quoting Rainer Hurling (from Thu, 29 Sep 2022 06:43:49 +0200): Hi Dan, Am 28.09.22 um 23:01 schrieb Dan Mahoney: On Sep 26, 2022, at 20:22, Kevin Oberman mailto:rkober...@gmail.com>> wrote:

This is going to break port building without poudriere! (was: Subpackage explanations)

Am 24.01.24 um 10:28 schrieb Luca Pizzamiglio: Hi porters! At the beginning of January, we merged the support to subpackages in the framework. Subpackage is the feature to create multiple packages from one build of one port. In other words, now it's possible to group files into multiple packag

Re: This is going to break port building without poudriere!

Am 25.01.24 um 20:57 schrieb Luca Pizzamiglio: Hi Stefan, I did reply to your first email, but not to your second one. I preferred (in agreement with portmgr@) to open the discussion with everyone, instead of keeping it just between you and me. As you can read in the email you have linked, I

Re: This is going to break port building without poudriere!

Am 26.01.24 um 11:23 schrieb Gleb Popov: On Fri, Jan 26, 2024 at 12:55 PM Chris wrote: I really appreciate the write up! Makes for a nice overview. The differential at first glance was a bit daunting. Will flavors and all still remain? Or will subpackages subsume options/flavors? I don't know

Re: Subpackage explanations

Am 25.01.24 um 04:46 schrieb Shane Ambler: On 24/1/24 19:58, Luca Pizzamiglio wrote: Hi porters! At the beginning of January, we merged the support to subpackages in the framework. Sounds like some good work in the right direction. *Use cases we want to tackle* The first use case we want to

Re: Synth status and failure to install some packages

Am 01.06.21 um 08:03 schrieb Mark Millard via freebsd-ports: > > Some basic commands for installing/updating packages are: > > pkg install (see man pkg-install) > pkg upgrade (see man pkg-upgrade) > pkg delete (see man pkg-delete) [...] > "pkg install" will install run-depencencies. > It will no

Add support for -c to sha256sum to fix port build failures

The sha256 et.al. programs have recently been extended to provide GNU compatible features if invoked as sha256sum. This does now lead to port build issues, since there are ports that assume that the -c option is implemented and that treat an error exit of sha256sum -c as an indication of corrupted

Re: Bind 9.16.17 update built for packages?

Am 21.06.21 um 09:49 schrieb Simon Wright: > Indeed "these things they do 'appen!" :) Is it possible/worth adding a > note to UPDATING to not upgrade to 9.16.17? > > Something like this: > > > 20210621: > AFFECTS: users of bind916 9.16.17 > > ISC have issued a warning to users to no

security/rkhunter without hashes after recent STABLE-13 update

Am 07.07.21 um 22:24 schrieb Michael Grimm: > Warner Losh wrote: >> >> On Wed, Jul 7, 2021 at 12:47 PM Michael Grimm wrote: >>> Warner Losh wrote: > Sorry for any hassle this work is causing. >>> >>> No big deal for rkhunter, a workaround exists ;-) >> >> I think the reason is that it auto

Re: security/rkhunter without hashes after recent STABLE-13 update

Am 09.07.21 um 01:51 schrieb Łukasz Wąsikowski: > W dniu 2021-07-08 o 14:16, Michael Grimm via freebsd-stable pisze: > >> I can confirm that your patch works perfectly well. >> No more workaround needed, now rkhunter calculates sha256 hashes as usual. >> >> Thanks for that. >> >> Now, Łukasz need'

Re: Lots of skips on python3[78].

Am 30.12.21 um 19:47 schrieb Larry Rosenman: > https://home.lerctr.org:/build.html?mastername=live-host-ports&build=2021-12-30_11h08m50s > > Can someone look? This is fall-out from my commit aiming to reduce incompatibilities of macros defined in sys/cpuset.h with those expected by programs w

Re: Lots of skips on python3[78].

Am 31.12.21 um 20:20 schrieb Larry Rosenman: > On 12/31/2021 4:07 am, Stefan Esser wrote: >> Am 30.12.21 um 19:47 schrieb Larry Rosenman: >>> https://home.lerctr.org:/build.html?mastername=live-host-ports&build=2021-12-30_11h08m50s >>> >>> >>>

Multiple ports install (conflicting) /usr/local/LICENSE files

While checking for port install conflicts I noticed a number of ports that each install a file ${LOCALBASE}/LICENSE. Maintainer Port --- amd...@freebsd.org devel/py-pytest-datadir cont...@kanazuchi.com textproc/py-tran

Re: pkgbase checksums

Am 13.01.22 um 10:36 schrieb Henrik Rosenke: > Hello, > > what is the correct way to handle pkg checksum mismatches in pkgbase? (pkg > check -sa) > For example after installing bash or editing /etc/hosts there are checksum > mismatches: > >     FreeBSD-clibs-12.2.s20220105232846: checksum mismatc

Re: p5-dbd-pg

Am 20.01.22 um 14:01 schrieb Dan Mahoney: > > >> On Jan 20, 2022, at 3:54 AM, Kurt Jaeger wrote: >> >> Hello, >> >> [postgres flavors] >>> This feels like the ideal kind of port that could be flavored so >>> it works with any installed postgres version. I'm willing to submit >>> patches, how ha

Re: Portlint check seems to be broken, endless loop

Am 20.01.22 um 13:29 schrieb Matthias Fechner: > Dear all, > > I saw a problem arising many weeks ago, but now I want to report it. > You can easily trigger it with: > poudriere testport -j 130amd64 www/gitlab-ce > > You will see: > > [00:00:33] Removing old packages > [00:00:33] Portlint check

Re: service management and upgrades

Am 21.01.22 um 10:03 schrieb marco+free...@crowdsec.net: > Hello! > > I have a doubt about service management in the context of my ports. > > We develop a couple of daemons, we can call them agent and bouncer. > They work in cooperation and the pkg-message explains how to enable and run > them >

Re: [HEADSUP] Deprecation of the ftp support in pkg

Am 23.01.22 um 18:12 schrieb Jose Quinteiro: > On 1/23/22 09:06, tech-lists wrote: >> On Sun, Jan 23, 2022 at 08:55:09AM -0800, Jose Quinteiro wrote: >> >>> You can run HTTP on a non-standard port. For example, 8080 is commonly >>> used. As an added bonus, this means that the HTTP server need not r

Re: [HEADSUP] Deprecation of the ftp support in pkg

Am 23.01.22 um 22:41 schrieb Mehmet Erol Sanliturk:> On Sun, Jan 23, 2022 at 11:27 PM Stefan Esser <mailto:s...@freebsd.org>> wrote: > > Am 23.01.22 um 18:12 schrieb Jose Quinteiro: > > On 1/23/22 09:06, tech-lists wrote: > >> On Sun, Jan 23, 2022 at

Re: FreeBSD Port: wine-devel-7.1,1 error Registering (13-stable)

Am 07.02.22 um 17:17 schrieb Alex V. Petrov: > > Compressing man pages (compress-man) > ===>   Installing ldconfig configuration file > ===>  Installing for wine-devel-7.1,1 > ===>  Checking if wine-devel is already installed > ===>   Registering installation for wine-devel-7.1,1 > Installing w

Re: FreeBSD Port: wine-devel-7.1,1 error Registering (13-stable)

Am 07.02.22 um 22:25 schrieb Alex V. Petrov: > 08.02.2022 02:24, Stefan Esser пишет: >> Am 07.02.22 um 17:17 schrieb Alex V. Petrov: >>> > Compressing man pages (compress-man) >>> ===>   Installing ldconfig configuration file >>> ===>  Installing fo

Re: graphics/jasper failed again !!!

Am 28.02.22 um 11:47 schrieb KIRIYAMA Kazuhiko: > Hi, list > > graphics/jasper failed again at same point before : Hi, do you have pkg-config (pkgconf package) installed? I was about to create a PR, since there have been a number of ports that fail if pkg-config is found during the port's confi

Re: graphics/jasper failed again !!!

Am 28.02.22 um 22:08 schrieb Tatsuki Makino: > Hello. > > The problem is described here. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260878 > It appears to have been closed, to be upgraded to 3.0.x. > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262039 > > A workaround for this probl

Re: How to port a PHP application that uses Composer?

Am 17.05.22 um 06:19 schrieb Mel Pilgrim: > On 2022-05-16 20:14, Peter Beckman wrote: [...] >> Consider that it is something the installer needs to do, or build the >> package as a deterministic set of packages already installed. > > Yes, that's exactly the point I'm stuck on.  The fetch-extract-f

Re: NO_TEST, do-test: and TEST_DEPENDS?

Am 21.05.22 um 16:37 schrieb Bjoern A. Zeeb: > Hi, > > I just grabbed a random example and made put the NO_TEST into the Makefile to > make things clear. Hi Bjoern, I'm not sure I understand the goal of your request. Do you want to have a switch that prevents the execution of tests when "make t

Re: NO_TEST, do-test: and TEST_DEPENDS?

Am 24.05.22 um 17:27 schrieb Bjoern A. Zeeb:> On Sun, 22 May 2022, Stefan Esser wrote: > >> I'm not sure I understand the goal of your request. > > the goal is to cut down dependencies and build time. As long as you do not invoke the tests (with "make test"), n

HOWTO: specify a run dependency on a port without a single executable?

I'm trying to update the devel/pmdk port and found 2 issues due to dependency checks that are not alignment with reality: 1) The port wants the ports version of ncurses. But the following definition does not work: LIP_DEPENDS= libncurses.so:devel/libncurses The reason is that lib/l

Re: unknown flavor py37

Am 04.06.22 um 01:02 schrieb Kubilay Kocak: > BUILD_ALL_PYTHON_FLAVORS was implemented in the reverse of what it should have > been (DONT_BUILD_ALL_PYTHON_FLAVORS or other). > > It was implemented ostensibly as a convenience for poudriere, such that the > default was for poudriere *not* build all

Re: Difference between LIB_DEPENDS and RUN_DEPENDS

Am 10.06.22 um 14:03 schrieb jbo@insane.engineer: > Hello folks, > > Maybe an unusual request but could somebody elaborate on the difference > between > LIB_DEPENDS and RUN_DEPENDS? > I read the corresponding handbook section thrice and it's not clear to me when > to use which - I must be missing

Re: sysutils/lsof: help!

Am 11.06.22 um 16:20 schrieb Larry Rosenman: > greetings, >     I'm having trouble getting anyone to care about lsof anymore.  If anyone > can help fix these merge conflicts, I'd be most > appreciative, and will merge and make a new FreeBSD release as soon as we get > it fixed: > https://github.com

Re: sysutils/lsof: help!

Am 12.06.22 um 22:48 schrieb Larry Rosenman: > On 06/12/2022 3:29 pm, Stefan Esser wrote: [...] >> On a kernel built with D34184 and D34323 applied I get output >> like this: >> >> COMMAND  PID USER   FD   TYPE    DEVICE SIZE/OFF   NODE NAME >&

Re: sysutils/lsof: help!

Am 13.06.22 um 03:01 schrieb Damjan Jovanovic: > >> PS: A patch that applies the ZFS fixes to sysutils/lsof can be > >>     fetched from: > >> > >>     https://people.freebsd.org/~se/ports/lsof-port-zfs-patch.diff >

Re: devel/gindent compile issues on 13.1

Am 21.06.22 um 05:09 schrieb Jim Pazarena: > I did not file a bug report . > But I had hopes that after a month passed , someone , perhaps even the > maintainer , this issue would have been corrected . > > Alas . > > I can't be the only one that wants to pretty up their source , and uses > ginde