Hi,
The 2021Q4 branch has been created. It means that the next update on the
quarterly packages will be on the 2021Q4 branch.
A lot of things happened in the last three months:
- pkg 1.17.2
- New USES:angr, mlt
- Default version of FPC switched to 3.2.2
- Default version of GL switched to
Simon Wright wrote:
> Hi all,
>
> Here is the new py-cryptography build log with no libressl and no ccache.
>
How recent is your ports tree? I've committed a further fix that
converts all patches to conditionals, specifically on FreeBSD 11 with
base OpenSSL or any system using LibreSSL.
> It
On 20/05/2021 12:32 pm, Kubilay Kocak wrote:
On 20/05/2021 2:17 pm, Simon Wright wrote:
On 20/05/2021 12:00 pm, Kubilay Kocak wrote:
On 20/05/2021 1:21 pm, Simon Wright wrote:
Hi all,
I've been unable to build security/py-cryptography for about 10 days
now. The build in Poudriere under
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
On 22/05/2021 12:31 am, Dan Langille wrote:
On Fri, May 21, 2021, at 10:29 AM, Dan Langille wrote:
On Thu, May 20, 2021, at 7:18 PM, Simon Wright wrote:
Thanks Kubs, I'm travelling at the moment and will check further when I'm
back home. The original build log was with libressl and ccache.
On Fri, May 21, 2021, at 10:29 AM, Dan Langille wrote:
> On Thu, May 20, 2021, at 7:18 PM, Simon Wright wrote:
> > Thanks Kubs, I'm travelling at the moment and will check further when I'm
> > back home. The original build log was with libressl and ccache. I'll
> > repeat without both and attach
On Thu, May 20, 2021, at 7:18 PM, Simon Wright wrote:
> Thanks Kubs, I'm travelling at the moment and will check further when I'm
> back home. The original build log was with libressl and ccache. I'll
> repeat without both and attach a new build log.
FYI, I have build failures here today, based
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
Thanks Kubs, I'm travelling at the moment and will check further when I'm
back home. The original build log was with libressl and ccache. I'll
repeat without both and attach a new build log.
Apologies for the top post.
Regards,
Simon.
20 May 2021 13:50:54 Kubilay Kocak :
On 20/05/2021
On 2021-May-20, at 21:10, Chris wrote:
> On 2021-05-20 13:47, Mark Millard wrote:
>> Chris portmaster at bsdforge.com wrote on
>> Thu May 20 20:09:29 UTC 2021 :
>>> On 2021-05-20 12:21, Kevin Oberman wrote:
>>> > . . .
>>> >>
>>> > You can greatly reduce the build-time for devel/llvm* by
On 2021-05-20 13:47, Mark Millard wrote:
Chris portmaster at bsdforge.com wrote on
Thu May 20 20:09:29 UTC 2021 :
On 2021-05-20 12:21, Kevin Oberman wrote:
> . . .
>>
> You can greatly reduce the build-time for devel/llvm* by changing the
> config to BE_NATIVE to avoid building backends for
On Thu, May 20, 2021 at 03:09:32PM -0700, Mark Millard wrote:
> Kevin Oberman rkoberman at gmail.com wrote on
> Thu May 20 21:37:28 UTC 2021 :
>
> > On Thu, May 20, 2021 at 12:48 PM Mark Millard wrote:
> >
> > > Kevin Oberman rkoberman at gmail.com wrote on
> > > Thu May 20 19:21:24 UTC 2021 :
Thanks Kubs, I'm travelling at the moment and will check further when I'm
back home. The original build log was with libressl and ccache. I'll
repeat without both and attach a new build log.
Apologies for the top post.
Regards,
Simon.
20 May 2021 13:50:54 Kubilay Kocak :
On 20/05/2021
Kevin Oberman rkoberman at gmail.com wrote on
Thu May 20 21:37:28 UTC 2021 :
> On Thu, May 20, 2021 at 12:48 PM Mark Millard wrote:
>
> > Kevin Oberman rkoberman at gmail.com wrote on
> > Thu May 20 19:21:24 UTC 2021 :
> >
> > > You can greatly reduce the build-time for devel/llvm* by changing
On Thu, May 20, 2021 at 12:48 PM Mark Millard wrote:
> Kevin Oberman rkoberman at gmail.com wrote on
> Thu May 20 19:21:24 UTC 2021 :
>
> > You can greatly reduce the build-time for devel/llvm* by changing the
> > config to BE_NATIVE to avoid building backends for all FreeBSD supported
> >
Chris portmaster at bsdforge.com wrote on
Thu May 20 20:09:29 UTC 2021 :
> On 2021-05-20 12:21, Kevin Oberman wrote:
> > . . .
> >>
> > You can greatly reduce the build-time for devel/llvm* by changing the
> > config to BE_NATIVE to avoid building backends for all FreeBSD supported
> >
On 2021-05-20 12:21, Kevin Oberman wrote:
On Thu, May 20, 2021 at 8:08 AM Chris wrote:
On 2021-05-20 06:15, Ronald Klop wrote:
> On 5/20/21 2:47 PM, Fernando Apesteguía wrote:
>> El jue., 20 may. 2021 14:45, Alexis Praga
>> escribió:
>>
>>>
>>> Hi guys,
>>>
>>> I've recently been using
Kevin Oberman rkoberman at gmail.com wrote on
Thu May 20 19:21:24 UTC 2021 :
> You can greatly reduce the build-time for devel/llvm* by changing the
> config to BE_NATIVE to avoid building backends for all FreeBSD supported
> platforms. Obviously this is not acceptable for many cases, but if you
On Thu, May 20, 2021 at 8:08 AM Chris wrote:
> On 2021-05-20 06:15, Ronald Klop wrote:
> > On 5/20/21 2:47 PM, Fernando Apesteguía wrote:
> >> El jue., 20 may. 2021 14:45, Alexis Praga
> >> escribió:
> >>
> >>>
> >>> Hi guys,
> >>>
> >>> I've recently been using poudriere to test news ports but
On 2021-May-20, at 11:11, Mark Millard wrote:
> Andrea Venturoli ml at netfence.it wrote on
> Thu May 20 14:54:50 UTC 2021 :
>
>> On 5/20/21 4:11 PM, Alexis Praga wrote:
>>>
>>> Thanks for the suggestions.
>>>
At least, if your machine is powerful enough, you can edit your
On 20/05/2021 12:00 pm, Kubilay Kocak wrote:
On 20/05/2021 1:21 pm, Simon Wright wrote:
Hi all,
I've been unable to build security/py-cryptography for about 10 days
now. The build in Poudriere under 12.2 and 13.0 fail with a
"Bad_C++_code" error.
I tried removing the libressl dependency but
Andrea Venturoli ml at netfence.it wrote on
Thu May 20 14:54:50 UTC 2021 :
> On 5/20/21 4:11 PM, Alexis Praga wrote:
> >
> > Thanks for the suggestions.
> >
> >> At least, if your machine is powerful enough, you can edit your
> >> /usr/local/etc/poudriere.conf and list these big ports in
> >>
On 2021-05-20 06:15, Ronald Klop wrote:
On 5/20/21 2:47 PM, Fernando Apesteguía wrote:
El jue., 20 may. 2021 14:45, Alexis Praga
escribió:
Hi guys,
I've recently been using poudriere to test news ports but this resulted in
building two large ports, namely:
- devel/llvm [1]
- lang/rust [2]
On 2021-05-20 05:47, Fernando Apesteguía wrote:
El jue., 20 may. 2021 14:45, Alexis Praga escribió:
Hi guys,
I've recently been using poudriere to test news ports but this resulted in
building two large ports, namely:
- devel/llvm [1]
- lang/rust [2]
Now, lang/rust takes 2 hourse to
On 5/20/21 4:11 PM, Alexis Praga wrote:
Thanks for the suggestions.
At least, if your machine is powerful enough, you can edit your
/usr/local/etc/poudriere.conf and list these big ports in
ALLOW_MAKE_JOBS_PACKAGES.
I'm using ALLOW_MAKE_JOBS=yes already so it won't help unfortunately, I
On Thu, 20 May 2021 16:11:21 +0200, Alexis Praga stated:
>Thanks for the suggestions.
>
>> At least, if your machine is powerful enough, you can edit your
>> /usr/local/etc/poudriere.conf and list these big ports in
>> ALLOW_MAKE_JOBS_PACKAGES.
>I'm using ALLOW_MAKE_JOBS=yes already so it won't
Thanks for the suggestions.
> At least, if your machine is powerful enough, you can edit your
> /usr/local/etc/poudriere.conf and list these big ports in
> ALLOW_MAKE_JOBS_PACKAGES.
I'm using ALLOW_MAKE_JOBS=yes already so it won't help unfortunately, I think.
> You can manually put the
Le jeu. 20 mai 21 à 14:47:35 +0200, Fernando Apesteguía
écrivait :
> > Hi guys,
Hello,
> > I've recently been using poudriere to test news ports but this resulted in
> > building two large ports, namely:
> > - devel/llvm [1]
> > - lang/rust [2]
> >
> > Now, lang/rust takes 2 hourse to
On 5/20/21 2:47 PM, Fernando Apesteguía wrote:
El jue., 20 may. 2021 14:45, Alexis Praga escribió:
Hi guys,
I've recently been using poudriere to test news ports but this resulted in
building two large ports, namely:
- devel/llvm [1]
- lang/rust [2]
Now, lang/rust takes 2 hourse to
El jue., 20 may. 2021 14:45, Alexis Praga escribió:
>
> Hi guys,
>
> I've recently been using poudriere to test news ports but this resulted in
> building two large ports, namely:
> - devel/llvm [1]
> - lang/rust [2]
>
> Now, lang/rust takes 2 hourse to compile. So testing for 13.0, 12.2 and
>
Hi guys,
I've recently been using poudriere to test news ports but this resulted in
building two large ports, namely:
- devel/llvm [1]
- lang/rust [2]
Now, lang/rust takes 2 hourse to compile. So testing for 13.0, 12.2 and
11.4 means around 6 hours in total, a lot of time for my desktop
On 5/20/21 10:48 AM, Ronald Klop wrote:
Hi,
Somebody changed the LICENSE* stuff in my net/ldapbrowser port. It does not
compile anymore.
This change fixes it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255752
I mailed mat@ about his change breaking my port, but did not hear anything
On Mon, May 17, 2021 at 03:44:15PM -0700, Chris wrote:
> I'd like to subscribe to the commit messages
> ( dev-commits-ports-all )
> but only receive messages that affect me -- the
> ports I currently maintain. Is it possible? Or
> am I just dreaming? ;-)
>
> Thanks in advance for any insight into
Hi,
Somebody changed the LICENSE* stuff in my net/ldapbrowser port. It does not
compile anymore.
This change fixes it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255752
I mailed mat@ about his change breaking my port, but did not hear anything from
him for about ten days. (no offense)
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
On 20/05/2021 2:17 pm, Simon Wright wrote:
On 20/05/2021 12:00 pm, Kubilay Kocak wrote:
On 20/05/2021 1:21 pm, Simon Wright wrote:
Hi all,
I've been unable to build security/py-cryptography for about 10 days
now. The build in Poudriere under 12.2 and 13.0 fail with a
"Bad_C++_code" error.
I
On 20/05/2021 12:00 pm, Kubilay Kocak wrote:
On 20/05/2021 1:21 pm, Simon Wright wrote:
Hi all,
I've been unable to build security/py-cryptography for about 10 days
now. The build in Poudriere under 12.2 and 13.0 fail with a
"Bad_C++_code" error.
I tried removing the libressl dependency but
On 20/05/2021 1:21 pm, Simon Wright wrote:
Hi all,
I've been unable to build security/py-cryptography for about 10 days
now. The build in Poudriere under 12.2 and 13.0 fail with a
"Bad_C++_code" error.
I tried removing the libressl dependency but that made no difference. Is
anyone else seeing
I was doing a poudriere pkgclean under:
# uname -apKU
FreeBSD CA72_16Gp_ZFS 13.0-RELEASE FreeBSD 13.0-RELEASE #0
releng/13.0-n244733-ea31abc261ff-dirty: Thu Apr 29 21:53:20 PDT 2021
root@CA72_4c8G_ZFS:/usr/obj/BUILDs/13_0R-CA72-nodbg-clang/usr/13_0R-src/arm64.aarch64/sys/GENERIC-NODBG-CA72
Hi all,
I've been unable to build security/py-cryptography for about 10 days
now. The build in Poudriere under 12.2 and 13.0 fail with a
"Bad_C++_code" error.
I tried removing the libressl dependency but that made no difference. Is
anyone else seeing this and can anyone point me in the right
On 2021-May-19, at 14:17, Mark Millard wrote:
> On 2021-May-19, at 10:29, Mark Millard wrote:
>
>> bob prohaska fbsd at www.zefox.net wrote on
>> Wed May 19 16:09:32 UTC 2021 :
>>
>>> On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
>>>
>>> [portmaster background omitted]
On 20/05/2021 1:54 am, Xavier Humbert wrote:
Hi,
I got trouble with python 3.8.10 at reinstall stage :
===> Registering installation for python38-3.8.10
pkg-static: Unable to access file
/usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_asyncio.cpython-38.so:No
such
On 2021-May-19, at 10:29, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Wed May 19 16:09:32 UTC 2021 :
>
>> On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
>>>
>>
>> [portmaster background omitted]
>>
>>> If you want to give the attached port a try, it
bob prohaska fbsd at www.zefox.net wrote on
Wed May 19 16:09:32 UTC 2021 :
> On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
> >
>
> [portmaster background omitted]
>
> > If you want to give the attached port a try, it will install LUA and some
>
>
> I tried
On 2021-05-19 03:45, Willem Jan Withagen wrote:
On 18-5-2021 03:56, Chris wrote:
On 2021-05-17 18:17, Julian H. Stacey wrote:
Chris wrote:
On 2021-05-17 16:30, Jan Beich wrote:
> Chris writes:
>
>> I'd like to subscribe to the commit messages
>> ( dev-commits-ports-all )
>> but only receive
On 19/05/2021 19:10, Gleb Popov wrote:
Just a guess - are you building with WITH_DEBUG=yes ?
Actually, no
Xavier
--
Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer
https://www.amdh.fr
___
freebsd-ports@freebsd.org mailing list
On Wed, May 19, 2021 at 6:55 PM Xavier Humbert wrote:
> Hi,
>
> I got trouble with python 3.8.10 at reinstall stage :
>
> > ===> Registering installation for python38-3.8.10
> > pkg-static: Unable to access file
> >
>
On 2021-05-19 01:42, Nuno Teixeira wrote:
Hello,
I'm working in a port that have several files/patches like:
--- NsCDE/bin/nscde.orig2021-05-02 07:33:53 UTC
+++ NsCDE/bin/nscde
@@ -42,16 +42,11 @@ fi
# Set main NSCDE and FVWM variables. Most of the things later
# depends on this core
On Tue, May 18, 2021 at 09:24:00AM +0200, Stefan Esser wrote:
>
[portmaster background omitted]
> If you want to give the attached port a try, it will install LUA and some
I tried ports-mgmt/portmaster, it got stuck the same as make.
Unless the new version behaves very differently I'm
On 19/05/2021 17:54, Xavier Humbert wrote:
Hi,
I got trouble with python 3.8.10 at reinstall stage :
===> Registering installation for python38-3.8.10
pkg-static: Unable to access file
/usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_asyncio.cpython-38.so:No
such
Hi,
I got trouble with python 3.8.10 at reinstall stage :
===> Registering installation for python38-3.8.10
pkg-static: Unable to access file
/usr/ports/lang/python38/work/stage/usr/local/lib/python3.8/lib-dynload/_asyncio.cpython-38.so:No
such file or directory
pkg-static: Unable to
On 18-5-2021 03:56, Chris wrote:
On 2021-05-17 18:17, Julian H. Stacey wrote:
Chris wrote:
On 2021-05-17 16:30, Jan Beich wrote:
> Chris writes:
>
>> I'd like to subscribe to the commit messages
>> ( dev-commits-ports-all )
>> but only receive messages that affect me -- the
>> ports I
(...)
# PREFIX- Where *this* port installs its files.
# Default: ${LINUXBASE} if USE_LINUX_PREFIX
is set,
# otherwise ${LOCALBASE}
# LOCALBASE - Where ports install things.
#
Hello,
I'm working in a port that have several files/patches like:
--- NsCDE/bin/nscde.orig2021-05-02 07:33:53 UTC
+++ NsCDE/bin/nscde
@@ -42,16 +42,11 @@ fi
# Set main NSCDE and FVWM variables. Most of the things later
# depends on this core variables.
export
On 2021-05-18 09:27, Julian H. Stacey wrote:
Dave Horsfall wrote:
On Tue, 18 May 2021, Julian H. Stacey wrote:
> I'd use /usr/ports/mail/procmail
I wouldn't; it's an unsupported and obscure scripting language just asking
for bugs, and actually has several CVEs against it.
URLs please ?
None
Le mar. 18 mai 21 à 18:27:09 +0200, Julian H. Stacey
écrivait :
> Dave Horsfall wrote:
> > On Tue, 18 May 2021, Julian H. Stacey wrote:
> >
> > > I'd use /usr/ports/mail/procmail
> >
> > I wouldn't; it's an unsupported and obscure scripting language just asking
> > for bugs, and actually has
Dave Horsfall wrote:
> On Tue, 18 May 2021, Julian H. Stacey wrote:
>
> > I'd use /usr/ports/mail/procmail
>
> I wouldn't; it's an unsupported and obscure scripting language just asking
> for bugs, and actually has several CVEs against it.
URLs please ?
None on
Jan Beich writes:
> -fuse-ld=lld should work fine on 11.4 aarch64/amd64/armv6/armv7/i386 as
> it uses clang as /usr/bin/cc and has /usr/bin/ld.lld but may[1] break
> 11.4 powerpc/powerpc64 which still has gcc as /usr/bin/cc. I've used
> -fuse-ld=lld in a number of ports to unbreak -flto[2] or
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
On 2021-05-17 20:23, Li-Wen Hsu wrote:
Another possible way is "watch" the ports you maintained with
FreshPorts: https://www.freshports.org/
Thanks for the pointer, Li-Wen.
I'm already subscribed to the ports-commit list. So I'm not
sure this can quite hit the mark tho. I'll have to look
On 2021-05-17 23:46, Michael Gmelin wrote:
On Tue, 18 May 2021 03:17:03 +0200
"Julian H. Stacey" wrote:
Chris wrote:
> On 2021-05-17 16:30, Jan Beich wrote:
> > Chris writes:
> >
> >> I'd like to subscribe to the commit messages
> >> ( dev-commits-ports-all )
> >> but only receive messages
On Tue, 18 May 2021 03:17:03 +0200
"Julian H. Stacey" wrote:
> Chris wrote:
> > On 2021-05-17 16:30, Jan Beich wrote:
> > > Chris writes:
> > >
> > >> I'd like to subscribe to the commit messages
> > >> ( dev-commits-ports-all )
> > >> but only receive messages that affect me -- the
> >
Another possible way is "watch" the ports you maintained with
FreshPorts: https://www.freshports.org/
Li-Wen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
bob prohaska fbsd at www.zefox.net wrote on
Mon May 17 23:46:38 UTC 2021 :
> On Mon, May 17, 2021 at 12:28:24PM -0700, Mark Millard via freebsd-ports
> wrote:
> > bob prohaska fbsd at www.zefox.net wrote on
> > Mon May 17 15:55:21 UTC 2021 :
> >
> > > The existing conflict between versions of
On 2021-05-17 18:17, Julian H. Stacey wrote:
Chris wrote:
On 2021-05-17 16:30, Jan Beich wrote:
> Chris writes:
>
>> I'd like to subscribe to the commit messages
>> ( dev-commits-ports-all )
>> but only receive messages that affect me -- the
>> ports I currently maintain. Is it possible? Or
>>
On Tue, 18 May 2021, Julian H. Stacey wrote:
I'd use /usr/ports/mail/procmail
I wouldn't; it's an unsupported and obscure scripting language just asking
for bugs, and actually has several CVEs against it.
Better filters exist, such as "sieve" etc.
-- Dave
Chris wrote:
> On 2021-05-17 16:30, Jan Beich wrote:
> > Chris writes:
> >
> >> I'd like to subscribe to the commit messages
> >> ( dev-commits-ports-all )
> >> but only receive messages that affect me -- the
> >> ports I currently maintain. Is it possible? Or
> >> am I just dreaming? ;-)
> >
>
On 2021-05-17 16:30, Jan Beich wrote:
Chris writes:
I'd like to subscribe to the commit messages
( dev-commits-ports-all )
but only receive messages that affect me -- the
ports I currently maintain. Is it possible? Or
am I just dreaming? ;-)
No clue but I use Herald rules for something
On Mon, May 17, 2021 at 12:28:24PM -0700, Mark Millard via freebsd-ports wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Mon May 17 15:55:21 UTC 2021 :
>
> > The existing conflict between versions of python strikes me as more of a
> > planning problem than a software bug. It may be naive,
Chris writes:
> I'd like to subscribe to the commit messages
> ( dev-commits-ports-all )
> but only receive messages that affect me -- the
> ports I currently maintain. Is it possible? Or
> am I just dreaming? ;-)
No clue but I use Herald rules for something similar.
Alexis Praga writes:
> Hi guys,
>
> Thanks to Li-Wen Hsu [1], I now know the new version does not build on 11.4
> with :
> /usr/bin/ld: unrecognized option '-plugin'
> Which seems due to the '-flto' flag according to this issue :
>
I'd like to subscribe to the commit messages
( dev-commits-ports-all )
but only receive messages that affect me -- the
ports I currently maintain. Is it possible? Or
am I just dreaming? ;-)
Thanks in advance for any insight into this.
--Chris
___
bob prohaska fbsd at www.zefox.net wrote on
Mon May 17 15:55:21 UTC 2021 :
> The existing conflict between versions of python strikes me as more of a
> planning problem than a software bug. It may be naive, but I don't see
> why python37 and python38 can't use distinct names for files placed in
Hi guys,
Thanks to Li-Wen Hsu [1], I now know the new version does not build on 11.4
with :
/usr/bin/ld: unrecognized option '-plugin'
Which seems due to the '-flto' flag according to this issue :
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230137
I've tried the fix mentioned
On Mon, May 17, 2021 at 09:37:07AM -0400, George Mitchell wrote:
> On 5/16/21 10:19 PM, bob prohaska wrote:
> > [...]
> > I'd like to see the ports system keep working as it has in the past, but
> > that seemingly
> > requires a kind of machine intelligence that hasn't evolved yet. Poudriere
> >
On 5/16/21 10:19 PM, bob prohaska wrote:
[...]
I'd like to see the ports system keep working as it has in the past, but that
seemingly
requires a kind of machine intelligence that hasn't evolved yet. Poudriere
seems like
a brute force approach. [...]
You'll find quite a few remaining fans of
Hi all,
I've rewritten the suggested port for kitty which was waiting here :
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010.
With newer versions, porting is much easier and I have a functional
kitty on my system.
As I'm new to porting files, any guidance or advice is appreciated.
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
On Mon, May 17, 2021 at 04:44:04AM +, Thomas Mueller wrote:
>
> My question, Bob, is, if you are dissatisfied with poudriere, what do you use
> for FreeBSD ports?
I'm not dissatisfied, I'm overwhelmed.
Usually, a simple
make -DBATCH > make.log &
works.
hth,
bob prohaska
> No real favorites. In emergencies I tend to pick up the telephone.
> This doesn't seem like an emergency, and in any case the phone is a poor
> medium for a problem like this. There are some ports under /usr/ports/irc,
> if you have suggestions I could try one or more. If a phone call
On Sun, May 16, 2021 at 12:24:49PM +1000, Kubilay Kocak wrote:
> On 15/05/2021 2:35 am, bob prohaska wrote:
> >
> > I've never used IRC, is it somehow better than this list?
>
> Quicker isolation of root causes over async back and forth. Happy to go over
> it with you at your favourite
On 2021-May-16, at 15:33, Tatsuki Makino wrote:
> Mark Millard wrote on 2021/05/16 17:11:
>> On 2021-May-16, at 00:16, Tatsuki Makino
>> wrote:
>>
>>> poudriere jail -c -j main -m 'src=/usr/src' -v `make -C /usr/src/release/
>>> -V VERSION VERSION=\$\{REVISION:Q\}-\$\{BRANCH:Q\}`
>>>
>> Bob
Mark Millard wrote on 2021/05/16 17:11:
> On 2021-May-16, at 00:16, Tatsuki Makino
> wrote:
>
>> poudriere jail -c -j main -m 'src=/usr/src' -v `make -C /usr/src/release/ -V
>> VERSION VERSION=\$\{REVISION:Q\}-\$\{BRANCH:Q\}`
>>
> Bob already does a buildworld based on /usr/src for other
>
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
On 2021-May-16, at 00:16, Tatsuki Makino wrote:
> Mark Millard via freebsd-ports wrote on 2021/05/16 10:57:
>> In the form that I use poudriere I use something
>> like the following. I presume here that /usr/src
>> is populated and has the source for the system
>> involved. (I do not remember
Mark Millard via freebsd-ports wrote on 2021/05/16 10:57:
> In the form that I use poudriere I use something
> like the following. I presume here that /usr/src
> is populated and has the source for the system
> involved. (I do not remember your describing its
> status.)
(Omitted below)
I was just
Something I've not asked about or otherwise referenced
is if you use non-default port options for any of the
ports that you build.
There is:
poudriere options -jmain -c -f ~root/origins/main-origins.txt
or:
poudriere options -jmain -C -f ~root/origins/main-origins.txt
where -c vs. -C is:
On 15/05/2021 2:35 am, bob prohaska wrote:
On Fri, May 14, 2021 at 12:24:06PM +1000, Kubilay Kocak wrote:
happy to help identify the root cause if you can jump on IRC
(#freebsd-python @ freenode)
If sorting out the conflict between python versions helps the
community in general I'm willing
On 2021-May-15, at 16:37, bob prohaska wrote:
> On Fri, May 14, 2021 at 07:29:15PM -0700, Mark Millard wrote:
>> bob prohaska fbsd at www.zefox.net wrote on
>> Fri May 14 01:35:28 UTC 2021 :
>>
>>> Would use of poudriere help with this sort of problem?
>>> It isn't trivial to configure, but
On Fri, May 14, 2021 at 07:29:15PM -0700, Mark Millard wrote:
> bob prohaska fbsd at www.zefox.net wrote on
> Fri May 14 01:35:28 UTC 2021 :
>
> > Would use of poudriere help with this sort of problem?
> > It isn't trivial to configure, but this sort of difficulty
> > has been growing ever worse.
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
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. If any ports have already been updated,
Am 13.05.21 um 17:39 schrieb bob prohaska:
> On Thu, May 13, 2021 at 08:13:07AM +0200, Jan Beich wrote:
>>>
>>> Moving to /usr/ports/json-glib and using
>>> make -DBATCH MAKE_JOBS_UNSAFE=yes MAKE_JOBS_NUMBER=4
>>> DISABLE_VULNERABILITIES=yes > make.log
>>> reports several instances of
>>>
bob prohaska fbsd at www.zefox.net wrote on
Fri May 14 01:35:28 UTC 2021 :
> On Thu, May 13, 2021 at 01:35:50PM -0700, Mark Millard wrote:
> > You have apparently chosen to build/update ports via a
> > technique that requires you to manage the dependencies, at
> > least some of the time. (Not
On 2021-05-14 15:15, Christoph Moench-Tegeder wrote:
## Chris (portmas...@bsdforge.com):
The problem I'm addressing in this case; is that the following as
*always* worked for licenses which carried a copy in
${WRKSRC}/LICENSE_NAME:
The problem you're trying to address is only a consecutive
## Chris (portmas...@bsdforge.com):
> The problem I'm addressing in this case; is that the following as
> *always* worked for licenses which carried a copy in
> ${WRKSRC}/LICENSE_NAME:
The problem you're trying to address is only a consecutive error and
not the real problem.
As I wrote in my
On 2021-05-14 14:19, Christoph Moench-Tegeder wrote:
## Chris (portmas...@bsdforge.com):
> but the way it currently interacts
> with your port is not that fine: in the very least, it overwrites
> your LICENSE variables, which cannot be your intention. (Try
> "make -V LICENSE" in
## Chris (portmas...@bsdforge.com):
> > but the way it currently interacts
> > with your port is not that fine: in the very least, it overwrites
> > your LICENSE variables, which cannot be your intention. (Try
> > "make -V LICENSE" in kde-icons-nuovoext2).
> Sorry. My bad. LGPL3 is now included
On Fri, May 14, 2021 at 12:24:06PM +1000, Kubilay Kocak wrote:
>
> happy to help identify the root cause if you can jump on IRC
> (#freebsd-python @ freenode)
If sorting out the conflict between python versions helps the
community in general I'm willing to try. I simply use make in
the ports
On 14/05/2021 11:35 am, bob prohaska wrote:
On Thu, May 13, 2021 at 01:35:50PM -0700, Mark Millard wrote:
You have apparently chosen to build/update ports via a
technique that requires you to manage the dependencies, at
least some of the time. (Not that when is necessarily
obvious up front.)
On Thu, May 13, 2021 at 01:35:50PM -0700, Mark Millard wrote:
> You have apparently chosen to build/update ports via a
> technique that requires you to manage the dependencies, at
> least some of the time. (Not that when is necessarily
> obvious up front.)
>
You give me too much credit 8-)
>
1 - 100 of 80872 matches
Mail list logo
