[Bug 243906] emulators/qemu-user-static: Update to 3.1, Deprecate emulators/qemu-sbruno

2020-04-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243906

--- Comment #7 from Kyle Evans  ---
@koobs: I'd like to go ahead and proceed with this this weekend. Am I OK to
commit the following + svn rm emulators/qemu-user-static; then revert this diff
and do the repocopy from emulators/qemu-user-static-devel in the next commit?

So two (2) commits total: one +MOVED and removing it from emulators/, and the
next commit re-adding it and killing off the MOVED entry. I believe this would
keep `make index` intact and cause the least amount of friction, given that
zapping the anti-replacement commit hook isn't an option. clusteradm@ updates
their repo at 2AM Pacific Time which is about ~4AM CDT, I'll plan to do it just
a couple hours later so that there's plenty of time prior to their next build
in case something unexpected comes up.

Index: MOVED
===
--- MOVED   (revision 532685)
+++ MOVED   (working copy)
@@ -14550,3 +14550,4 @@
 security/suricata5|security/suricata|2020-04-20|Has expired: security/suricata
is already at version 5
 finance/py-ebaysdk-python|finance/py-ebaysdk|2020-04-21|Renamed to match Pypy
package
 emulators/qemu30|emulators/qemu31|2020-04-21|Has expired: No longer maintained
by upstream
+emulators/qemu-user-static||2020-04-25|Slave port being replaced by a copy of
qemu-user-static-devel
Index: emulators/Makefile
===
--- emulators/Makefile  (revision 532685)
+++ emulators/Makefile  (working copy)
@@ -110,7 +110,6 @@
 SUBDIR += qemu-devel
 SUBDIR += qemu-powernv
 SUBDIR += qemu-sbruno
-SUBDIR += qemu-user-static
 SUBDIR += qemu-user-static-devel
 SUBDIR += qemu-utils
 SUBDIR += qemu31

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"


[Bug 245641] emulators/virtualbox-ose guest crashes whilst running some types of application with webcam or audio input on USB

2020-04-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245641

Graham Perrin  changed:

   What|Removed |Added

 Attachment #213739|text/x-log  |text/plain
  mime type||

--- Comment #5 from Graham Perrin  ---
Created attachment 213739
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=213739&action=edit
Attempted to use the integral webcam with 5.2.34

Tried to use SteelSeries Siberia 350, not detected by Teams, so I performed a
soft disconnect. 

Tried to use the integral webcam, crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"


[Bug 245865] emulators/virtualbox-ose-additions doesn't let go of files placed on a Windows host shared folder

2020-04-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245865

Bug ID: 245865
   Summary: emulators/virtualbox-ose-additions doesn't let go of
files placed on a Windows host shared folder
   Product: Ports & Packages
   Version: Latest
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: Individual Port(s)
  Assignee: v...@freebsd.org
  Reporter: ilau...@bigpond.net.au
 Flags: maintainer-feedback?(v...@freebsd.org)
  Assignee: v...@freebsd.org

virtualbox-ose-additions doesn't seem to want to let go of files placed on a
Windows host shared folder.  

My host is Win8.1, VirtualBox is 6.1.6, my FreeBSD is 12.1-RELEASE-p3 and my
GUI in FreeBSD is Xfce 4.14.

Not sure if this is an issue with FreeBSD or Linux hosts.

Minimal steps to highlight issue:

1. Mount Windows shared folder, for example: sudo mount -t vboxvfs -w
Development ~/host
2. Go there in the file manager.
3. Right click "Create Document" -> "Empty File".
4. Then try to delete it.  It cannot be deleted.

If you try to delete the file from the command line:

$ rm dog
rm: dog: Text file busy

In fact it cannot be deleted even on the Windows host until the VM shuts down,
it's as if the file is still open for writing or something.

This issue came to light running some code that creates lock files, but when
done the code was unable to delete the lock files, leaving things in a locked
state.  Needless to say this is rather annoying.

Derived distros like FuryBSD exhibit the same problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"


maintainer-feedback requested: [Bug 245865] emulators/virtualbox-ose-additions doesn't let go of files placed on a Windows host shared folder

2020-04-23 Thread bugzilla-noreply
Bugzilla Automation  has asked v...@freebsd.org for
maintainer-feedback:
Bug 245865: emulators/virtualbox-ose-additions doesn't let go of files placed
on a Windows host shared folder
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245865



--- Description ---
virtualbox-ose-additions doesn't seem to want to let go of files placed on a
Windows host shared folder.  

My host is Win8.1, VirtualBox is 6.1.6, my FreeBSD is 12.1-RELEASE-p3 and my
GUI in FreeBSD is Xfce 4.14.

Not sure if this is an issue with FreeBSD or Linux hosts.

Minimal steps to highlight issue:

1. Mount Windows shared folder, for example: sudo mount -t vboxvfs -w
Development ~/host
2. Go there in the file manager.
3. Right click "Create Document" -> "Empty File".
4. Then try to delete it.  It cannot be deleted.

If you try to delete the file from the command line:

$ rm dog
rm: dog: Text file busy

In fact it cannot be deleted even on the Windows host until the VM shuts down,
it's as if the file is still open for writing or something.

This issue came to light running some code that creates lock files, but when
done the code was unable to delete the lock files, leaving things in a locked
state.  Needless to say this is rather annoying.

Derived distros like FuryBSD exhibit the same problem.
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"