Package Details: virtualbox-ext-vnc-svn 102693-2

Git Clone URL: https://aur.archlinux.org/virtualbox-svn.git (read-only, click to copy)
Package Base: virtualbox-svn
Description: VirtualBox VNC extension pack
Upstream URL: http://virtualbox.org
Keywords: oracle virtualbox vm
Licenses: GPL, custom:CDDL
Conflicts: virtualbox-ext-vnc
Provides: virtualbox-ext-vnc
Submitter: heavysink
Maintainer: heavysink (lilac)
Last Packager: lilac
Votes: 2
Popularity: 0.25
First Submitted: 2017-09-16 02:27 (UTC)
Last Updated: 2023-12-30 04:35 (UTC)

Pinned Comments

Latest Comments

1 2 Next › Last »

dreieck commented on 2024-11-22 15:23 (UTC) (edited on 2024-11-24 14:17 (UTC) by dreieck)

According to this comment from VirtualBox upstream:

We do not officially support CLANG on Linux host (only GCC is supported).

clang compiled Linux kernels are not supported by the VirtualBox host kernel modules.

And I experience kernel freeze when I actually do that.

So I suggest to add some logic that this module only gets build for Linux kernels compiled with gcc, not with clang.

↗ Here is a report with more context to Arch Linux' official virtualbox-host-dkms package with a patch for that package.

Regards!

fermino commented on 2024-03-26 14:32 (UTC) (edited on 2024-03-26 14:33 (UTC) by fermino)

Hi :)

Perhaps it would be good to add subversion as a dependency.

yurikoles commented on 2023-12-30 15:03 (UTC)

Dear lilac,

I noticed a misuse of the pkgrel field in this package update history.

From wiki/PKGBUILD#pkgrel

The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1. In exceptional cases other formats can be found in use, such as major.minor.

From PKGBUILD(5):

This is the release number specific to the distribution. This allows package maintainers to make updates to the package’s configure flags, for example. This is typically set to 1 for each new upstream software release and incremented for intermediate PKGBUILD updates. The variable is a positive integer, with an optional subrelease level specified by adding another positive integer separated by a period (i.e. in the form x.y).

Davius commented on 2023-12-06 11:58 (UTC)

Hi maintener

patching file src/VBox/Additions/x11/Installer/98vboxadd-xclient Hunk #1 FAILED at 31.

MarsSeed commented on 2023-07-23 21:05 (UTC)

Thank you for adding these latest refinements, @heavysink!

MarsSeed commented on 2023-07-22 14:59 (UTC)

@heavysink, thank you.

Please also kindly add a conflicts entry for 'virtualbox-guest-dkms-svn' to the following subpackages:

Because apparently some people still have the dropped dkms-svn module installed despite the Arch Linux kernels already containing the virtualbox-guest-modules.

That is possible because the listed subpackages only conflict with 'virtualbox-guest-dkms', but the former virtualbox-guest-dkms-svn never provided the non-svn equivalent.

heavysink commented on 2023-07-22 14:31 (UTC)

@MarsSeed

Corrected

MarsSeed commented on 2022-05-16 15:32 (UTC) (edited on 2023-07-21 22:48 (UTC) by MarsSeed)

'VIRTUALBOX-GUEST-MODULES-SVN' does not exist - that is a dependency of virtualbox-guest-utils-svn and virtualbox-guest-utils-nox-svn.

These packages should now depend on 'VIRTUALBOX-GUEST-MODULES' provided by the Linux kernel (see here for an example).

carlosnewmusic commented on 2021-05-08 02:51 (UTC)

/var/tmp/pamac-build-user/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom/nsISupportsImpl.h:345:3: nota: en expansión de macro ‘NS_IMPL_QUERY_BODY_AMBIGUOUS’ 345 | NS_IMPL_QUERY_BODY_AMBIGUOUS(_interface, _implClass) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ /var/tmp/pamac-build-user/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom/nsISupportsImpl.h:374:5: nota: en expansión de macro ‘NS_INTERFACE_MAP_ENTRY_AMBIGUOUS’ 374 | NS_INTERFACE_MAP_ENTRY_AMBIGUOUS(nsISupports, _i1) \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /var/tmp/pamac-build-user/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom/nsISupportsImpl.h:485:46: nota: en expansión de macro ‘NS_IMPL_QUERY_INTERFACE3’ 485 | #define NS_IMPL_THREADSAFE_QUERY_INTERFACE3 NS_IMPL_QUERY_INTERFACE3 | ^~~~~~~~~~~~~~~~~~~~~~~~ /var/tmp/pamac-build-user/virtualbox-svn/src/VirtualBox/out/linux.amd64/release/bin/sdk/bindings/xpcom/include/xpcom/nsISupportsImpl.h:826:3: nota: en expansión de macro ‘NS_IMPL_THREADSAFE_QUERY_INTERFACE3’ 826 | NS_IMPL_THREADSAFE_QUERY_INTERFACE3(_class, _i1, _i2, _i3) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /var/tmp/pamac-build-user/virtualbox-svn/src/VirtualBox/src/libs/xpcom18a4/ipc/ipcd/extensions/dconnect/src/ipcDConnectService.cpp:3441:1: nota: en expansión de macro ‘NS_IMPL_THREADSAFE_ISUPPORTS3’ 3441 | NS_IMPL_THREADSAFE_ISUPPORTS3(ipcDConnectService, ipcIDConnectService, | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ kmk: *** Exiting with status 2 ==> ERROR: Se produjo un fallo en build().

shillshocked commented on 2019-06-07 00:16 (UTC)

Why on earth does this package unpack to 8 GB on the tmp drive?

1 2 Next › Last »