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 8. Mar 2020, at 00:04, Greg 'groggy' Lehey wrote:
>
> On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote:
>
> [More irrelevant text deleted, also dropping current@]
>
> Is it really so difficult to trim your replies?
>
>> On 7. Mar 2020, at 23:39, Greg 'groggy'
On Saturday, 7 March 2020 at 23:55:33 +0100, Michael Gmelin wrote:
[More irrelevant text deleted, also dropping current@]
Is it really so difficult to trim your replies?
>> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote:
>>
>> ???On Saturday, 7 March 2020 at 16:46:58 +0100, Michael
> On 7. Mar 2020, at 23:39, Greg 'groggy' Lehey wrote:
>
> On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote:
>
> [much irrelevant text deleted]
>
> People, please trim your replies. Only relevant text should remain
>
>>> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble
On Saturday, 7 March 2020 at 16:46:58 +0100, Michael Gmelin wrote:
[much irrelevant text deleted]
People, please trim your replies. Only relevant text should remain
> On Sat, 07 Mar 2020 11:30:58 -0400 Waitman Gobble wrote:
>>
>> I installed 12.1 on a new laptop yesterday, I have not
Hi,
On 3/7/20 9:49 PM, Yuri wrote:
I got a feedback that such use of 'Reported by' might be incorrect.
I've never received any negative feedback about it. In fact, I believe
it is a nice way of giving credits to some really useful services.
Mateusz
El sáb., 7 mar. 2020 21:50, Yuri escribió:
> I got a feedback that such use of 'Reported by' might be incorrect.
>
>
> Opinions?
>
I don't know if it is incorrect, but I often use "Reported by: portscout".
Never had negative feedback.
Cheers
>
> Yuri
>
>
I got a feedback that such use of 'Reported by' might be incorrect.
Opinions?
Yuri
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
> On 7 Mar 2020, at 12:23, Adam Jimerson wrote:
>
>
> On 3/7/20 6:56 AM, Michael Gmelin wrote:
>>
>> I worked around the situation locally by setting ALTABI
>> on `pkg update':
>>
>> # ALTABI=FreeBSD:12.0:amd64 pkg update -f
>>
>> This allowed me to run
>>
>> # pkg upgrade
>>
>>
On Sat, 07 Mar 2020 11:30:58 -0400
Waitman Gobble wrote:
> On 2020-03-07 05:10, Ronald Klop wrote:
> > On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey
> > wrote:
> >
> >> On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote:
> >>> On Wed, Mar 04, 2020 at 03:16:14PM
On Sat, 07 Mar 2020 10:48:05 +0100
"Ronald Klop" wrote:
> On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin
> wrote:
>
> >
> >
> >> On 5. Mar 2020, at 14:46, Ronald Klop wrote:
> >>
> >> Hi,
> >>
> >> I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse
> >> to "hardware
On Tue, Feb 25, 2020 at 10:38:19AM +0400, Gleb Popov wrote:
> On Tue, Feb 25, 2020 at 12:00 AM Torfinn Ingolfsen wrote:
>
> > Hello,
> > Is anyone working on a Python3 supported port of xpra?
> > The homepage mentions that Python3 support was completed late
> > September last year
> >
>
> You
On 3/7/20 6:56 AM, Michael Gmelin wrote:
>
> I worked around the situation locally by setting ALTABI
> on `pkg update':
>
> # ALTABI=FreeBSD:12.0:amd64 pkg update -f
>
> This allowed me to run
>
> # pkg upgrade
>
> without any issues, so I assume none of the about 30 packages I updated
>
On 3/7/20 12:53 PM, Stefan Bethke wrote:
I'm working on updating the Gitea port to 1.11, and I need to download the
source archive off the release page, instead of an archive of the Github repo.
The source archive on the release page contains additional files that are
needed for the build (Go
On Sat, 07 Mar 2020 10:10:43 +0100
"Ronald Klop" wrote:
> On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey
> wrote:
>
> > On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote:
> >> On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey
> >> wrote:
> >>>
> >>> Any
I'm working on updating the Gitea port to 1.11, and I need to download the
source archive off the release page, instead of an archive of the Github repo.
The source archive on the release page contains additional files that are
needed for the build (Go and node modules that would need to be
Am 07.03.2020 um 08:50 schrieb sth...@nethelp.no:
>
> I think a lot of people are waiting for some kind of guidance on how
> to fix these problems, if the repos are supposed to be okay now.
It would be really great if someone in the know would send something to
-announce or similar, with an
Le sam. 7 mars 20 à 1:38:55 +0100, Greg 'groggy' Lehey
écrivait :
> > Still broken for me on 12.1.
Still broken for me on 12.1-STABLE, but with a different error:
"size mismatch, fetching from remote" and then
"size mismatch, cannot continue" for the first package being fetched.
Same after
> On 7. Mar 2020, at 10:48, Ronald Klop wrote:
>
> On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin wrote:
>
>>
>>
On 5. Mar 2020, at 14:46, Ronald Klop wrote:
>>>
>>> Hi,
>>>
>>> I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse to
>>> "hardware mouse". That
On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin wrote:
On 5. Mar 2020, at 14:46, Ronald Klop wrote:
Hi,
I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse to
"hardware mouse". That fixed mouse integration with VirtualBox.
Still have weird behaviour. Two finger
On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey
wrote:
On Friday, 6 March 2020 at 12:29:44 +0100, Lars Engels wrote:
On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote:
Any workarounds in the meantime? This must affect a lot of people,
including those who use
21 matches
Mail list logo
