Hi,
I tested and submitted a patch via PR 236113 to unbreak sssd. Is there a
committer that can commit the patch?
—
Rick
--
Take care
Rick Miller
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
## Andrea Venturoli (m...@netfence.it):
> > Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels,
> > blurry?)?
> More "something blocky, vaguely, *really* vaguely, resembling the
> indended text": something you can read only if you already know what
> it says.
That sounds
## Torfinn Ingolfsen (tin...@gmail.com):
> updated the ports tree again, and tried upgrading the FreeCAD port,
> but the build fails as before.
> I've put the build output and CMakeOutput.log (there is no
> CMakeError.log) at
> https://sites.google.com/site/tingox/asus_m5a78l_usb3_freebsd
> in
Christoph Moench-Tegeder writes:
> ## Andrea Venturoli (m...@netfence.it):
>
>> > Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels,
>> > blurry?)?
>> More "something blocky, vaguely, *really* vaguely, resembling the
>> indended text": something you can read only if you
On 3/17/19 7:03 PM, Christoph Moench-Tegeder wrote:
Uh, define "illegible crap". Wrong glyphs? Bad rendering (blocky pixels,
blurry?)?
More "something blocky, vaguely, *really* vaguely, resembling the
indended text": something you can read only if you already know what it
says.
My
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 Sun, Mar 17, 2019 at 10:48:12AM +, Dima Pasechnik wrote:
>
> I just got an email from portscout about
> www/squidclamav/ port. Indeed, it has no maintainer:
> https://www.freshports.org/www/squidclamav/
>
> but the point of this email is a total mystery, probably just an
> error, no? I
