Date: Thu, 13 Jun 2019 19:36:16 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 238548] devel/dbus: non-default TMPDIR pollutes build products Message-ID: <bug-238548-6497@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238548 Bug ID: 238548 Summary: devel/dbus: non-default TMPDIR pollutes build products Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: gnome@FreeBSD.org Reporter: jcfyecrayz@liamekaens.com Flags: maintainer-feedback?(gnome@FreeBSD.org) Assignee: gnome@FreeBSD.org Created attachment 205039 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=205039&action=edit [patch] fix for non-default TMPDIR leakage If you have a TMPDIR in your environment that points to an existing directory other than /tmp (e.g., TMPDIR=/bigfilesystem/tmp), when you build devel/dbus, a couple files get built with that value. The affected files are share/dbus-1/session.conf and bin/dbus-cleanup-sockets. When the package is installed on a target system that may not have the non-default TMPDIR used at build time, then you will get run-time errors. Such as: % dbus-launch sh Failed to start message bus: Failed to bind socket "/bigfilesystem/tmp/dbus-1nT4MYueXb": No such file or directory EOF in dbus-launch reading address from bus daemon Attached is a patch to insulate the build from non-default TMPDIR in the build environment. This should not change the package at all if the build host did not have a non-default TMPDIR, so there's no great need to bump PORTREVISION, but you could. -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238548-6497>