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
> On 14. Mar 2024, at 23:59, Daniel Engberg
> wrote:
> On 2024-03-14T23:27:53.000+01:00, Tomoaki AOKI
> wrote:
>> On Thu, 14 Mar 2024 22:17:39 +0100
>> Daniel Engberg wrote:
>>
>>
>>> On 2024-03-14T21:49:46.000+01:00, Michael Gmelin
>>> wrote:
>On 14. Mar 2024, at 21:38,
Miroslav Lachman wrote on 2024/03/15 07:24:
> And this line should explain the order of patch and fix-shebang
> _PATCH_REAL_SEQ = ${:Uask-license} ${:Upatch-message} ${:Upatch-depends}
> ${:Ufix-shebang} ${:Udo-patch}
Regarding this, the use of :U out of the blue without a variable name doesn't
On 2024-03-14T23:27:53.000+01:00, Tomoaki AOKI
wrote:
> On Thu, 14 Mar 2024 22:17:39 +0100
> Daniel Engberg wrote:
>
>
> >On 2024-03-14T21:49:46.000+01:00, Michael Gmelin
> > wrote:
> >
> > >
> > >
> > > > On 14. Mar 2024, at 21:38, Daniel Engberg
> > > > wrote:
> > >
On Thu, 14 Mar 2024 22:17:39 +0100
Daniel Engberg wrote:
> On 2024-03-14T21:49:46.000+01:00, Michael Gmelin wrote:
> >
> > >On 14. Mar 2024, at 21:38, Daniel Engberg
> > > wrote:
> > >
> > > On 2024-03-12T15:15:49.000+01:00, Eugene Grosbein
> > > wrote:
> > >
> > > >12.03.2024
On 14/03/2024 22:03, Tatsuki Makino wrote:
Hello.
Various answers have already been given, however, here is a command that can
produce interesting values on this.
make -C /usr/ports/ports-mgmt/pkg -V _TARGETS_STAGES
make -C /usr/ports/ports-mgmt/pkg -V _SANITY_SEQ -V _PKG_SEQ -V _FETCH_SEQ -V
On 14/03/2024 22:20, Moin Rahman wrote:
On Mar 14, 2024, at 10:08 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
On 14/03/2024 20:59, Moin Rahman wrote:
On Mar 14, 2024, at 8:57 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
On 14/03/2024 20:35, Moin Rahman wrote:
On Mar 14, 2024, at 7:55 P
Hello.
Various answers have already been given, however, here is a command that can
produce interesting values on this.
make -C /usr/ports/ports-mgmt/pkg -V _TARGETS_STAGES
make -C /usr/ports/ports-mgmt/pkg -V _SANITY_SEQ -V _PKG_SEQ -V _FETCH_SEQ -V
_EXTRACT_SEQ -V OMITTED_HEREAFTER:P
The -d
Daniel Engberg wrote:
On 2024-03-14T21:49:46.000+01:00, Michael Gmelin wrote:
On 14. Mar 2024, at 21:38, Daniel Engberg
wrote:
Given that we seem to agree on these points in general why should such ports
still be kept in the tree? We don't have such tooling available and it wont
li
> On Mar 14, 2024, at 10:08 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> On 14/03/2024 20:59, Moin Rahman wrote:
>>> On Mar 14, 2024, at 8:57 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>>> On 14/03/2024 20:35, Moin Rahman wrote:
> On Mar 14, 2024, at 7:55 PM, Miroslav Lachman <000.
On 2024-03-14T21:49:46.000+01:00, Michael Gmelin wrote:
>
> >On 14. Mar 2024, at 21:38, Daniel Engberg
> > wrote:
> >
> > On 2024-03-12T15:15:49.000+01:00, Eugene Grosbein
> > wrote:
> >
> > >12.03.2024 3:24, Daniel Engberg пишет:
> > >
> > > [skip]
> > >
> > >
> > >
> >
On 14/03/2024 20:59, Moin Rahman wrote:
On Mar 14, 2024, at 8:57 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
On 14/03/2024 20:35, Moin Rahman wrote:
On Mar 14, 2024, at 7:55 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
Is there a way to see the order of the executed steps by "make"?
tl;dr
> On 14. Mar 2024, at 21:38, Daniel Engberg
> wrote:
>
> On 2024-03-12T15:15:49.000+01:00, Eugene Grosbein wrote:
>> 12.03.2024 3:24, Daniel Engberg пишет:
>>
>> [skip]
>>
>>
>>> Another possible option would be to add something to the port's matedata
>>> that makes pkg aware and easy
On 2024-03-12T15:15:49.000+01:00, Eugene Grosbein wrote:
> 12.03.2024 3:24, Daniel Engberg пишет:
>
> [skip]
>
>
> >Another possible option would be to add something to the port's matedata
> > that makes pkg aware and easy notiable
> > like using a specific color for portname and related
> On Mar 14, 2024, at 8:57 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> On 14/03/2024 20:35, Moin Rahman wrote:
>>> On Mar 14, 2024, at 7:55 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>>>
>>> Is there a way to see the order of the executed steps by "make"?
>>>
>>> tl;dr: I know "make
On 14/03/2024 20:35, Moin Rahman wrote:
On Mar 14, 2024, at 7:55 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
Is there a way to see the order of the executed steps by "make"?
tl;dr: I know "make" will run many targets like fetch, checksum, extract, patch... but I
would like to see some ve
Hi,
can someone please take a look at ticket 276817
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276817).Attached to this
ticket is a patch that updates mod_security to version 3.0.12, which fixes a
CVE.
Thank you in advance,
Wolfgang
On 14/03/2024 20:24, Hubert Tournier wrote:
Hello,
Check this link:
https://docs.freebsd.org/en/books/porters-handbook/slow-porting/#slow-work
From what I have seen, shebangfix is done during the patch target. You
use SHEBANG_FILES to specify which files it needs to affect
I spent a lot of
On Thu, Mar 14, 2024 at 9:55 PM Miroslav Lachman <000.f...@quip.cz> wrote:
>
> Is there a way to see the order of the executed steps by "make"?
>
> tl;dr: I know "make" will run many targets like fetch, checksum,
> extract, patch... but I would like to see some verbose info about these
> steps, mai
> On Mar 14, 2024, at 7:55 PM, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> Is there a way to see the order of the executed steps by "make"?
>
> tl;dr: I know "make" will run many targets like fetch, checksum, extract,
> patch... but I would like to see some verbose info about these steps, m
On Thu, Mar 14, 2024 at 07:44:47PM +0100, Emmanuel Vadot wrote:
>
> Hi David,
>
> On Thu, 14 Mar 2024 06:49:18 -0700
> David Wolfskill wrote:
>
> > This is on my laptop, during a source-based update from
> > main-n268772-906521f8176b to main-n268800-6a6ec90681cf, in the "make
> ...
> > The fat
Hello,
Check this link:
https://docs.freebsd.org/en/books/porters-handbook/slow-porting/#slow-work
From what I have seen, shebangfix is done during the patch target. You
use SHEBANG_FILES to specify which files it needs to affect
Best regards,
Hubert
Le 14/03/2024 à 19:55, Miroslav Lachman
Is there a way to see the order of the executed steps by "make"?
tl;dr: I know "make" will run many targets like fetch, checksum,
extract, patch... but I would like to see some verbose info about these
steps, mainly what is the order of the steps when I run "make".
I tried to create some patch
Hi David,
On Thu, 14 Mar 2024 06:49:18 -0700
David Wolfskill wrote:
> This is on my laptop, during a source-based update from
> main-n268772-906521f8176b to main-n268800-6a6ec90681cf, in the "make
> buildkernel" phase, as a result of:
>
> g1-70(15.0-C)[3] grep PORT /etc/src.conf
> PORTS_MODU
Hello.
This is on 14.0 through Poudriere (2024Q1 tree).
Build fails ending in:
/usr/local/libexec/ccache/c++
-I/wrkdirs/usr/ports/devel/libcuckoo/work/libcuckoo-0.3.1/tests/Catch/single_include
-I/wrkdirs/usr/ports/devel/libcuckoo/work/libcuckoo-0.3.1 -O2 -pipe
-fstack-protector-strong -fno
While I'm not using 515, I needed something like this patch to build
drm-61 after the BUS_RELEASE_RESOURCE changes in commit 9dbf5b0:
--- drivers/gpu/drm/i915/intel_freebsd.c.orig 2024-02-24 10:15:24 UTC
+++ drivers/gpu/drm/i915/intel_freebsd.c
@@ -74,9 +74,9 @@ bsd_intel_pci_bus_release_mem(de
This is on my laptop, during a source-based update from
main-n268772-906521f8176b to main-n268800-6a6ec90681cf, in the "make
buildkernel" phase, as a result of:
g1-70(15.0-C)[3] grep PORT /etc/src.conf
PORTS_MODULES+=x11/nvidia-driver-390
PORTS_MODULES+=graphics/drm-515-kmod
(which has been there
Hello.
:On began to be used to expand the variable PATCHES in readline-8.2.10.
This determined that porttree itself would not support versions with older
make, such as 12.4-STABLE :)
However, it seems that the indexer for INDEX-12 is still at work, creating a
broken index.
The following result i
I think our main challenge still is:
Patches on top of patches.
Best regards,
Jussi Korkala
> On 14. Mar 2024, at 10.53, Felix Palmen wrote:
>
> * Alexey Vyskubov [20240314 10:26]:
>> Can someone have a look at it, please? Thank you!
>
> Self-assigned and reviewed,
* Alexey Vyskubov [20240314 10:26]:
> Can someone have a look at it, please? Thank you!
Self-assigned and reviewed, thanks!
I think there are some issues to sort out though, but thanks for the
effort to keep a port alive :)
--
Felix Palmen {private} fe...@palmen-it.de
-- po
Hello,
There is an unmaintained port of x11/wmctrl which can no longer be built
because it points to non-existing upstream.
More than two weeks ago I have created a github fork of the source, and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277348, containing
the patch, which makes the port
31 matches
Mail list logo
