On Wed, 14 Apr 2021, Thierry Thomas wrote:
[...]
Note: it builds for the other languages, and only fails for Hungarian.
Well, somebody has to say it so it may as well be me: is your hovercraft
full of eels?
-- Dave
___
freebsd-ports@freebsd.org
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Hi,
As you have updated the patch the maintainer-timeout has been reset. And we
have to await 14 days for timeout unless there are severe bugfixes.
Kind Regards,
Moin
> On 15 Apr, 2021, at 03:09, Jonathan Chen wrote:
>
> Hi,
>
> I've got a PR sitting in the "New" state for a couple of
Hi,
I've got a PR sitting in the "New" state for a couple of weeks now.
Can a committer please take a look at it?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254646
Cheers.
--
Jonathan Chen
___
freebsd-ports@freebsd.org mailing list
On Wed, 14 Apr 2021 21:48:25 +0200, Kurt Jaeger stated:
>Hi!
>
>> I just switched from using 'portsnap' to 'git'. I removed everything
>> in the directory, then used 'git' to build it. That worked fine. I
>> had to manually recreate the 'distfiles' directory, but I expected
>> to have to do that.
Hi!
> I just switched from using 'portsnap' to 'git'. I removed everything in
> the directory, then used 'git' to build it. That worked fine. I had to
> manually recreate the 'distfiles' directory, but I expected to have to
> do that.
>
> Now, if I run a 'make search' in the directory, I receive
I just switched from using 'portsnap' to 'git'. I removed everything in
the directory, then used 'git' to build it. That worked fine. I had to
manually recreate the 'distfiles' directory, but I expected to have to
do that.
Now, if I run a 'make search' in the directory, I receive an error
message
Hi!
> Second:
>
> In trying to play with rclint both to validate the port I maintain, as
> well as some internal rc.d scripts we use at the day job, I'm finding
> *most* ports (and a good portion of base) don't pass rclint cleanly. Is
> this something worth pushing pr's (with patches) for, or
First:
With most of the move to git, portlint complains about a missing
#$FreeBSD line, and one of the missing features of git is that it just
doesn't support the usual tagging that cvs and svn gave us. Is this still
a useful requirement?
(For us, where we have rc scripts that will never be
On Sat, 10 Apr 2021 at 21:34, Peter Jeremy via freebsd-ports
wrote:
>
> gitup walks the destination tree (ie /usr/ports), hashing every file
> it finds (by reading the complete file into memory). Whilst the
> default gitup configuration ignores /usr/ports/packages and
> /usr/ports/distfiles, it
While attempting to compile www/firefox on an RPi4 running -current
the make process stopped with
Bad packet length 3554809687.
ssh_dispatch_run_fatal: Connection to 192.168.1.11 port 22: Connection corrupted
on the controlling terminal.
After updating to 14.0-CURRENT FreeBSD 14.0-CURRENT #15
On 2021-04-13 23:22, Stefan Esser wrote:
Am 14.04.21 um 02:43 schrieb Chris:
On 2021-04-13 15:53, Dave Horsfall wrote:
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to
run
"gc" - which is similarly extravagant
Le mer. 14 avr. 21 à 14:50:37 +0200, Jan Beich
écrivait :
> Thierry Thomas writes:
>
> > [dochtml] File
> > "/wrkdirs/usr/ports/math/sage/work/build/usr/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
> > line 2, in
> > [dochtml] main()
> > [dochtml] File
> >
Thierry Thomas writes:
> [dochtml] File
> "/wrkdirs/usr/ports/math/sage/work/build/usr/local/lib/python3.7/site-packages/sage_setup/docbuild/__main__.py",
> line 2, in
> [dochtml] main()
> [dochtml] File
>
Hello,
The port math/sage used to build on different releases of FreeBSD (when
there is no problem with some dependencies...), but since some days pkg-
fallout reports a strange error when building the doc:
[dochtml] [a_tour_of] The HTML pages are in
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 14/04/2021 2:46 pm, Ronald Klop wrote:
Van: Kevin Oberman
Datum: 14 april 2021 08:31
Aan: Simon Wright
CC: FreeBSD Ports ML
Onderwerp: Re: Access to detailed status info on package build servers
On Tue, Apr 13, 2021 at 11:02 PM Simon Wright
wrote:
> Hi all,
>
>
> I use a script to
Van: Kevin Oberman
Datum: 14 april 2021 08:31
Aan: Simon Wright
CC: FreeBSD Ports ML
Onderwerp: Re: Access to detailed status info on package build servers
On Tue, Apr 13, 2021 at 11:02 PM Simon Wright wrote:
> Hi all,
>
> As detailed in other threads, I have been tracking the latest
On Tue, Apr 13, 2021 at 11:02 PM Simon Wright wrote:
> Hi all,
>
> As detailed in other threads, I have been tracking the latest complete
> build information on the package build servers (actually on
> beefy6.ny.freebsd.org) in order to synchronise my ports tree with the
> ports tree used by the
Am 14.04.21 um 02:43 schrieb Chris:
On 2021-04-13 15:53, Dave Horsfall wrote:
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to
run
"gc" - which is similarly extravagant in memory usage. Last time I
found
one
Hi all,
As detailed in other threads, I have been tracking the latest complete
build information on the package build servers (actually on
beefy6.ny.freebsd.org) in order to synchronise my ports tree with the
ports tree used by the build servers. This is so that the packages that
I build locally
21 matches
Mail list logo
