Date: Sun, 07 Dec 2014 21:38:00 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 195788] New: [either pkg or port bug] linux-f10-flashplugin has problem with /compat being a symlink Message-ID: <bug-195788-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195788 Bug ID: 195788 Summary: [either pkg or port bug] linux-f10-flashplugin has problem with /compat being a symlink Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Infrastructure Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: avg@FreeBSD.org hier(7) has the following information: ... /compat/ normally a link to /usr/compat. If not, then the /usr/compat comments apply ... /usr/ contains the majority of user utilities and applications ... compat/ files needed to support binary compatibility with other operating systems, such as Linux In my environment /compat is indeed a symlink to /usr/compat. With 1.4.0.rc2 when doing pkg upgrade I get the following: [322/394] Upgrading linux-f10-flashplugin from 11.2r202.418_2 to 11.2r202.418_4... [322/394] Extracting linux-f10-flashplugin-11.2r202.418_4: 100% pkg: cannot rename //compat.8U70sa3Hubr4 to //compat: Not a directory [322/394] Deleting files for linux-f10-flashplugin-11.2r202.418_4: 100% pkg: unlinkat(compat): Not a directory zsh: exit 3 I must note that the (earlier version of the) package was installed when pkg was at 1.3.8. I see that the corresponding port has the following line in pkg-plist: %NO_ALSA%@dir %COMPATDIR% So, not sure if the problem is caused by the port or by pkg... -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-195788-13>