On Wed, 11 Dec 2019 06:21:29 +0100 Jan Beich jbe...@freebsd.org said
Chris writes:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew everything off the disk, and started
> from scratch. Which only repeats what happened yesterday. Is
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,
Chris writes:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew everything off the disk, and started
> from scratch. Which only repeats what happened yesterday. Is python
> multiplicity no longer available? Or?
See bug 233723 or bug
On Tue, 10 Dec 2019 16:53:38 -0800 s...@troutmask.apl.washington.edu said
Thank you very much for taking the time to reply.
On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew
On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew everything off the disk, and started
> from scratch. Which only repeats what happened yesterday. Is python
> multiplicity no longer
I've spent the past 2 days attempting a fresh build/install
of world/kernel && preferred ports/applications. The world/kernel
worked to perfection. But I can *not* get the ports to build,
and install. All *fatal* errors stem from python.
So after booting into a new world/kernel; I proceed to
Hi freebsd-current@, freebsd-ports@ mailing lists,
When I updated my laptop to r355560, I could boot into GDM, but logging
into GNOME led to a coredump and brought me back to GDM.
I tried KDE, but logging in via SDDM also led to a crash.
I noted a lot of changes to the VM subsystem have
On 2019-12-02 15:16, Andrea Venturoli wrote:
On 2019-12-01 17:56, Boris Samorodov wrote:
What is the output of "sysctl kern.sugid_coredump"
command?
# sysctl kern.sugid_coredump
kern.sugid_coredump: 0
I've put kern.sugid_coredump=1 now; I'll see if this helps.
I confirm I can get dumps
