Date: Wed, 2 Nov 2022 11:29:56 -0500 From: Kyle Evans <kevans@freebsd.org> To: Doug Rabson <dfr@rabson.org> Cc: Guido Falsi <mad@madpilot.net>, freebsd-pkgbase@freebsd.org Subject: Re: New conflict on if_wg.h in runtime package Message-ID: <CACNAnaHW%2Bn2ZjZZsQmknxSAXcp4a=xdsCEhR5L0fRUOw8gFwrA@mail.gmail.com> In-Reply-To: <CACA0VUhU2NjaU=tJhvXqcrO0%2BBcgSA_cGrkeYTy3upKzucw1uQ@mail.gmail.com> References: <edc66854-7f9e-9383-643a-7ffb76b60890@madpilot.net> <CACA0VUiU8zvWgiwcUs8-sg6PmcQiMGGu-1v8j0HBGQPj2_VFzA@mail.gmail.com> <c1e4cdb7-51b0-7a6b-7ada-fd22cb8d94f7@madpilot.net> <CACA0VUhU2NjaU=tJhvXqcrO0%2BBcgSA_cGrkeYTy3upKzucw1uQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 2, 2022 at 11:21 AM Doug Rabson <dfr@rabson.org> wrote: > > > > On Wed, 2 Nov 2022 at 16:07, Guido Falsi <mad@madpilot.net> wrote: >> >> On 02/11/22 16:32, Doug Rabson wrote: >> > >> > >> > On Wed, 2 Nov 2022 at 13:54, Guido Falsi <mad@madpilot.net >> > <mailto:mad@madpilot.net>> wrote: >> > >> > Hi! >> > >> > I am trying to upgrade head using packaged base and I'm getting this >> > error now: >> > >> > pkg: FreeBSD-runtime-dev-14.snap20221102095743 conflicts with >> > FreeBSD-runtime-14.snap20221102095743 (installs files into the same >> > place). Problematic file: /usr/include/dev/wg/if_wg.h >> > >> > Looks like for some reason if_wg.h ended up in both packages. >> > >> > Am I doing something wrong and can I work around this or should this be >> > fixed in the sources? >> > >> > >> > This seems to be a problem in pkgbase. Packages are built using the >> > metalog generated from the various install commands during the build - >> > if_wg.h has two entries in the metalog, one with >> > tags=package=runtime,dev and one with tags=package=runtime. Can you open >> > a bug on bugs.freebsd.org <http://bugs.freebsd.org>? >> > >> > >> >> >> sure! > > > I think the problem is caused by the 'copies' target in src/include which is where the second metalog entry happens. From my limited understanding, this target shouldn't create metalog entries but I'm not sure how to stop it. >> It's via ${INSTALL}, which uses ${INSTALLFLAGS} that includes metalog bits. The problem is we're using the global ${TAG_ARGS} for those, but that's wrong on a number of levels. All of the headers need, at a minimum, a version of ${TAG_ARGS} that has ,dev, but also a lot of these have their own *PACKAGE that they should go to instead.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaHW%2Bn2ZjZZsQmknxSAXcp4a=xdsCEhR5L0fRUOw8gFwrA>