please also apply the patch?
thanks!
Il giovedì 17 ottobre 2019, 13:30:38 CEST, Frank Batschulat
ha scritto:
Gianfranco, pls. refer to
https://www.virtualbox.org/ticket/18869
On 17.10.19 12:51, Gianfranco Costamagna wrote:
> Hello, this patch was already acked but seems to h
why should it be a fork?
its made by upstream sources..
g.
Il martedì 15 ottobre 2019, 23:23:00 CEST, Kalogrianitis Socratis
ha scritto:
> On 15/Οκτ/2019, at 18:39, Sérgio Basto wrote:
>
> AFAIK Debian have VirtualBox [1]
>
> [1]
> https://tracker.debian.org/pkg/virtualbox
Yes.
Hello, this patch was scheduled for merging some time ago, but never hit newer
releases...Can you please give another try?
MIT licensed, as usual
Description: add python 3.7m as a supported version
Author: Michael Hudson-Doyle
Origin: vendor
Last-Update: 2018-07-12
---
This patch header follows
Hello, this patch was already acked but seems to have missed the 6.0.14 release
Bug-Debian: https://bugs.debian.org/934483
Last-Update: 2019-08-21
--- virtualbox-6.0.10-dfsg.orig/src/VBox/Additions/linux/drm/vbox_ttm.c
+++ virtualbox-6.0.10-dfsg/src/VBox/Additions/linux/drm/vbox_ttm.c
@@ -33,7
Hello, for some reasons, see [1] virtualbox doesn't build its kernel modules
correctly on some configurations...The following patch fixes the issue
+--- virtualbox-6.0.10-dfsg.orig/src/VBox/Additions/linux/drm/vbox_ttm.c
virtualbox-6.0.10-dfsg/src/VBox/Additions/linux/drm/vbox_ttm.c
+@@
Hello,sorry for not stepping in before, I crafted a patch one week ago, that
seems to be working so far
https://salsa.debian.org/pkg-virtualbox-team/virtualbox/blob/master/debian/patches/new-kernel-5.2.patch
MIT attached(I already sent it over irc as soon as I did it)
HTH
G.
Il giovedì 30
Hello,
>Probably me and probably not intentional. The question is, is there a
>reason to prefer one or the other, given that both work?
please don't forget about the automatic downloader that debian and ubuntu are
nfranco
Description: Fix build failure with new kernel 4.18
Author: Gianfranco Costamagna
diff --git a/src/VBox/Additions/linux/sharedfolders/utils.c b/src/VBox/Additions/linux/sharedfolders/utils.c
index 187ba2eff..11ff49a3a 100644
--- a/src/VBox/Additions/linux/sharedfolders/utils.c
+++ b/
Hello,
>As I'm a packager and part of one Linux distribution (Fedora / EPEL 7),
>I'm curious, if we have any change to do ? or what we have new ? or
>what changed ?
1) a build fix I had to do in Debian is now upstream
Hello,
I really don't know what happened here, but I found a probably working patch
for ticket:
https://www.virtualbox.org/ticket/17851
based on the comment I found on debian tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902897#159
basically, the patch is to do exactly the same
Hello, I crafted a patch to detect system libraries to enable again videorec
when OSE is enabled and the system version
of opus is found.
MIT attached patch
G.Index: virtualbox/configure
===
--- virtualbox.orig/configure
+++
Hello Dusan, I'm forwarding to vbox-dev list,
I had an issue with virtualbox-qt since some version after 5.1.18 (5.1.18was
the latest version I was using without that issue). The issue was that
when virtual machine is set to fullscreen, minitoolbar was missing/hidden
even that minitoolbar was
Hello, for reference in case in the future I get again the same problem:
>Hmm... I run into this when I was trying to compile an experimental build of
>VirtualBox with the Qt5.7 toolkit on OSX 10.9. It was complaining that the
>compiler >wasn't C++11 compatible (which it completely is). But, no
hello, it worked, after adding -std=c++11 to the qt linking flags
thanks!
G.
Il Sabato 9 Dicembre 2017 13:04, Perry Halbert <phalb...@cox.net> ha scritto:
Install qt56. It has worked for me for years now.
On 12/08/2017 05:00 PM, Gianfranco Costamagna wrote:
Hello, problem is:
Hello, problem is: xenial has qt 5.5.1, vbox needs 5.5.3
how to fix this? relaxing the dependency results in a build failure, but you
have somehow managed to build the deb in the website...
What is your solution?
thanks
G.
___
vbox-dev mailing list
Hello,
>I had that part. It fails build because the parameter of
>rtTimerLinuxStdCallback() needs to be "struct timer_list *t". The part I have
>not gotten right is how one uses that "t" to get the correct value of
>pSubTimer
>from "t" using the from_timer() macro.
indeed...
maybe something
Hello,
I'm attaching a MIT released, really untested patch
(result of some git log -p on kernel branch, I don't even know if this builds
and is sane)
feedback appreciated :)
G.
patch
Description: Binary data
___
vbox-dev mailing list
Hello,
>>If you are the developer that has been modifying _really recently_ the
>source files, mainly the license text (example:
>>https://www.virtualbox.org/changeset/69279/vbox), so as to introduce two (2)
>spaces (" ") after a period (".") at the end of a sentence (what was wrong
>with
Hello,
I got two bug reports:
bugs.debian.org/879940
bugs.debian.org/879895
one is because of a missing file included in the host build
(including a private header available only in the previous directory).
I quick-and-dirty fixed by including it with "../foo.h"
the other one is about a
Hello,
>VBOX_USE_SYSTEM_XORG_HEADERS, VBOX_USE_SYSTEM_GL_HEADERS
>VBOX_NO_LEGACY_XORG_X11 last 2 options only available on 5.2 ! .
I was already adding the XORG_X11 one, because cherry-picking that upstream
fix already in 5.1 branch :)
added the GL one, thanks!
G.
Hello, following the trivial patch
https://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/plain/debian/patches/37-python-3.6-support.patch?id=0cdbffcbaf0ea57b82ddd9e955b9107745cdec58
(MIT licensed even if it is not "licensable", please take care of the
authorship, it is not mine)
Hello,
thanks for the release, but unfortunately it doesn't seem to build from
source...
kmk: *** No rule to make target
`/<>/out/obj/VMMR3LazyImp/VMMR3LazyLoad.asm', needed by
`/<>/out/obj/VMMR3LazyImp/gen/VMMR3LazyLoad.o'. Stop.
kmk: *** Waiting for unfinished jobs
did you forget to
e time consuming, this is why I'm waiting for the next
drop
(I could import the RC into my debian packaging and use dkms, but I prefer to
stick with
the official iso image until the 5.2.* is released and then package it)
G.
16.10.2017 08:38, Gianfranco Costamagna wrote:
> Hello Michael,
&
Hello Michael,
>Hans was faster than me. Here is the same fix against our internal tree
>in case you are interested in sanity testing that.
the kernel one worked in Ubuntu too, and on the next RC I'll be happy to test
your one!
G.
___
vbox-dev
Hello,
>Attached is a fix, which I've already submitted for inclusion into the
>mainline kernel. I believe this fix should also be applied to the VirtualBox
>5.2 Guest Additions version of the driver too, as the bug seems to originally
>come from there and to be present there too.
I'm already
Hello,
>I haven't taken a look at the in-kernel version, but in RC1 the reason
>was that the arguments to out*() calls got swapped: the Linux kernel
>reverses them compared to everyone else I know of, and I failed to do
>that during clean-up to match kernel style. Will be committing soon.
control: found -1 5.1.28-dfsg-1
On Sun, 01 Oct 2017 11:20:09 +0200 ermac god wrote:
> Package: virtualbox
> Version: 5.1.28-dfsg-1~bpo9+1 (and the original oracle package)
>
> After upgrade from virtualbox version 5.1.26 to 5.1.28 on the guest os
> (debian 9 x64) the
Hello, as said on irc, I had to quickly fix the Debian/Ubuntu packages, because
now systemd has dropped that hacky conflict.
Please add
"Conflicts=systemd-timesyncd.service" to your Unit section of the guest service
file.
I release the above with MIT license, even if it isn't needed.
>
>lspci -nn shows
>00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-H HD
> Audio [8086:a170] (rev 31)
>01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:10f0]
> (rev a1)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877385
I got a similar bug report (with a
Hello Michael,
>Thanks for the heads-up. I am gradually adjusting our in-tree code to
>match vboxvideo in staging, so at some point, when things stop turning
>up to stop me, I will probably hit the crucial difference. Gianfranco,
>if you have time could you please give the Additions from the
Hello, we tried in Ubuntu to use the new shiny vboxvideo mainline kernel driver
with the new shiny CONFIG_DRM_VBOXVIDEO config key, and we had to quickly
disable
it to use the old working kernel module.
Reason: it breaks with wayland.
see:
Hello Michael
>
"Ack" as in something you are likely to implement when you have time?
sure, maybe not for 5.1.24 or whatever, but for a 5.2 or so
(this is because I don't want to SRU this change into a stable ubuntu release,
specially because I have no idea about a possible implementation in
>The kernel modules are not currently a problem - we use depmod's
>override feature to give our ones priority over pre-installed ones. We
>had an additional option for handling this - relying on distributions to
>provide up-to-date Additions.
ack
>Currently, our installation script aborts if
Hi Michael
>That is roughly what we had until recently, minus printing the exact
>command. Seamlessly switching would be a big usability plus though. My
>original idea was to make it possible to have two versions (distribution
>and ours) installed at once, and set symbolic links in /usr/bin and
Hello,
>And here we come back to the original problem. If it were just a case
>of Debian, but our installer is designed to work with any distribution,
>and it becomes a case of knowing the magical incantations for each,
>rather than just executing a script which contains "apt-get remove
Hello Michael
>I am not aware of anyone other than us having implemented this yet. I
>seem to recall that we discussed this on IRC and came to the conclusion
>that you could simply refuse to install if that file was found. I
Yep I remember that quick discussion :)
Refusing to install is
Hello,
>Hello all (especially distribution package maintainers),
>Hans de Goede from Redhat suggested a nice simple solution for stopping
>our Additions and distribution Additions packages from treading on each
>other's feet: a well-known file -
>/usr/sbin/vbox-uninstall-guest-additions -
Hello Frank
>but this changeset was not yet backported to 5.1. Done now. Regarding the
>'gcc-7 -dumpversion' problem: See
>
> https://www.virtualbox.org/changeset/66931/vbox
thanks! it is clear now :)
G.
___
vbox-dev mailing list
Hello list,
configure:
-log_failure "gcc version $cc_maj.$cc_min found, expected gcc 4.x, gcc 5.x or
gcc 6.x"
+log_failure "gcc version $cc_maj.$cc_min found, expected gcc 4.x, gcc 5.x or
gcc 7.x"
BTW gcc -dumpversion in debian experimental returns "7" and no minor version,
so the cc_min
hello
>http://download.virtualbox.org/virtualbox/5.1.20/VirtualBox-5.1.20a.tar.bz2
or just grab them via patch I crafted when I faced the same issue this morning
(I downloaded the tarball and extracted it)
Hi
>The problem with HAL (and with most of the packages I listed) is that it
>is not recognized by the 'configure' script.
>So, without installing it (or changing the script), the process will stop.
>
>I guess the script should be updated as well.
in my Debian directory you can find rules
(bouncing from my yahoo mail address)
Il Lunedì 20 Febbraio 2017 17:25, Gianfranco Costamagna
<locutusofb...@debian.org> ha scritto:
Hello,
>- libhal-dev: this package is no longer available in the Ubuntu repositories.
>It used to be replaced by some other package, but this is
Hello,
>Hm... How about those notices that at least Debian shows prior to
>actual package upgrade? I saw those quite a number of times in cases
>where some breaking change was introduced. In particular the upgrade of
>ca-certificates package will often trigger the screen being presented.
>
>Best
Hello Larry
>Is not the "please make sure you have terminated all VMs and upgraded any
>extension packs" message sufficient?
I'm really not sure, unfortunately people are complaining about this,
and I don't have any easy solution.
Changing the colour, increasing the font size, I don't know
Hello vbox developers, as said I get bug reports about failures due to:
"VERR_PDM_DEVHLPR3_VERSION_MISMATCH", maybe can we have some better error
message?
I'm not sure how better might it be, but I get a lot of reports due to this
problem...
Maybe refusing to start when an incompatible ext-pack
it worth an investigation, because it might be a
dh_python bug
G.
,
On Freitag, 21. Oktober 2016 15:34:01 CEST Gianfranco Costamagna wrote:> Hi,
>
> FYI, seems that the Python3 switch is causing troubles at least in Debian,
> I'm forwarding this bug report for other maintainers, w
Hi,
>today Oracle released VirtualBox 5.1.8, a maintenance release of
changelog claims fully Python3 porting, but the build still fails on i386
sdk/bindings/xpcom/include/xpcom
-I/<>/out/bin/sdk/bindings/xpcom/include/ipcd
-I/<>/src/libs/xpcom18a4/python
-I/<>/out/obj/VBoxPython3_5m/dtrace
G.
On 2016-09-07 10:00 AM, Gianfranco Costamagna wrote:
> Hi VirtualBox Developers!
>
> (feel free to forward to kbuild folks, I don't remember/know how to reach
> them)
>
> Seems that the current kbuild source contains some GPL-2 only code, that
> comes from
> virtualbox
Hi VirtualBox Developers!
(feel free to forward to kbuild folks, I don't remember/know how to reach them)
Seems that the current kbuild source contains some GPL-2 only code, that comes
from
virtualbox and oracle guys
https://www.gnu.org/licenses/gpl-faq.html#v2v3Compatibility
a GPL-3+
Hi,
>Right, and Microsoft's policy change will make the already difficult
>build of VirtualBox yet again significantly harder on Windows. This is
>relevant for people working on contributions on Windows host. Sad that
>they're effectively crushing open source software.
just to know if I remember
Hi, code says:
-o \( $cc_maj -eq 5 -a $cc_min -gt 3 \) \
log_failure "gcc version $cc_maj.$cc_min found, expected gcc 3.x with x>1 or
gcc 4.x with 01 or gcc 4.x with
, Gianfranco Costamagna
<costamagnagianfra...@yahoo.it> ha scritto:
Hi Michael and Sérgio
>Without updated ( VirtualBox-5.0.17-r106108-r106114.patch ), X started
>and 3D works but kernel ooops on boot.
>With last patch update (VirtualBox-5.0.17-r106108-r106114.patch), X not
>started b
Hi Sam and VBox developers,
I'm forwarding the following mail to VirtualBox Developers's list
can you please release it under MIT license, to allow them review and possibly
apply it?
cheers,
Gianfranco
Il Giovedì 10 Marzo 2016 19:18, Sam Morris ha scritto:
Here's a
Hi is tails Debian based?
If so please tell kernel, gcc versions
And thendget
-uhttp://http.debian.net/debian/pool/contrib/v/virtualbox/virtualbox_5.0.12-dfsg-2.dsc
dpkg-buildpackage
I suspect you will need a newer kbuild too.
Cheers
G.
BTW I got no reports about a bad wheezy and Jessie security
Hi!
actually I don't see the problem.
quoting the ticket
"it will be part of the next maintenance release"
you opened against 5.0.10, and it was fixed some days ago
"
comment:3 Changed 5 days ago by frank
Status changed from new to closed
Resolution set to fixed
It is.
"
virtualbox 5.0.12
Hi,
>The original spec actually says 172.16.0.0/12 or 192.168.0.0/16. See
>RFC1918, Private IP addresses.
>But yes, most users use 172.16.0.0/16 and 192.168.0.0/24.
you are completely right, it is just that if you use /12 and /16 you can't have
different networks :)
but yes, you are right!
Hi,
>Use 10.0.0.0/8 if you need such a big subnet, else go with
> 172.16.0.0/12 or 192.168.0.0/16
mmm I guess it is 172.16.0.0/16 and 192.168.0.0/24 ;)
cheers,
G.
On 01/12/15 13:43, george.va...@wipro.com wrote:
Hi,
We are having our test topology running multiple VMs on a server.
The
Hi Michael,
(sending again because the Debian address is not allowed to post)
>On 09.11.2015 11:46, Michael Thayer wrote:
>> Dear All (especially maintainers of distributions Additions packages),
>>
>> I have been thinking again about our old problem with the Guest
>> Additions, namely how a
Hi,
>think that on systems running systemd, /sbin/init (if it exists at all)
>is always a symbolic link with "systemd" in the target. Would you be
>able to give me feedback for any Linux systems you have readily
>available running systemd if this is indeed the case, and if so what the
>link
Hi, I can confirm this on Debian
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=virtualbox=no=pending-fixed=fixed=done=critical=grave=serious=no
we are currently getting rid of the root need for X, and I got the same issue.
Fortunately we have a xserver-xorg-legacy package, but a proper fix
Hi Klaus
>Uninstalling an extpack expects to do a rename() syscall for the extpack
>directory name successfully, but instead gets EXDEV. This means that the
>filesystem structure is very unexpected.
>
>Either the Debian live setup uses a non-posix compliant union filesystem
>or it stitches
Hi folks, as said, "--force" is not implemented, and the call exits with
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to uninstall "Oracle VM VirtualBox Extension Pack"
VBoxManage: error: The installer failed with exit code 2: VBoxExtPackHelperApp:
error: Unknown option: '--forced'
Hi Sérgio, I don't have this problem in debian unstable...
but I remember some error like that before, could you look at the Debian
packaging and tell me if it fixes your issue?
(it might be in rules or LocalConfig.mk files, I'm on mobile sorry if I can't
help)
cheers,
G.
Sent from
Hi Folks, I'm forwarding a German Typo in Virtualbox 5.0.2
s/Andern/Ändern
(file-virtual media manager)
following the ubuntu bug report
Il Sabato 22 Agosto 2015 9:35, Sworddragon 1487...@bugs.launchpad.net ha
scritto:
Public bug reported:
I'm using Ubuntu 15.10 dev with virtualbox
Hi Frank,
could you post the AutoConfig.kmk file which is generated during the build?
And do you have a LocalConfig.kmk file as well? I would like to see both
because I assume that you are using settings different from our build boxes.
Sure:
this is the build invocation
. out/env.sh
Hi folks,
the latest vbox 5.0.2 failed to build on Debian unstable i386.
Build failure is located at [1] and I'm putting a snip log just below
tstDeviceStructSize: error! VGASTATE::GCPhysVRAM offset=0x12d64 (77156)
expected alignment 0x8, meaning 0x4 (4) off
tstDeviceStructSize: error!
Hi virtualbox developers,
today I noticed the above CVE in Debian.
We are packaging right now 4.3.30 and 5.0.0 that should fix the CVE, but I
would like to know if a minimal patch is available, in order to do the security
uploads for Debian and Ubuntu stable releases.
Can you please share
Hi Stéphane,
Just for your information you can use some sort of qemu-arm-static for
virtualizing arm support.
HTH
Gianfranco
Il Domenica 28 Giugno 2015 6:38, Stéphane Charette stephanechare...@gmail.com
ha scritto:
Been playing around with other hardware lately for work. Raspberry Pi
Yes, that is what I was trying to use earlier tonight. But after years of
using VirtualBox and the great GUI it has for setting things up correctly and
launching VMs, I found QEMU to be more difficult than I cared for. In the
end, I never did figure out tonight how to correctly start my ARM
Hi Alexey,
please do *not* fork :)
Upstream Developers are really responsive with virtualbox patches (at least
this is my opinion) and with support.
I suggest you to work with them and to integrate (whenever possible) your
patches into the mainline code.
Forking such an huge project might be
Hi Frank, are you sure the bug is really fixed?
the qemu patch seems to be different from the virtualbox one, and seems that
the affected code is not fixed
Hi Debian security team, can we please followup with the two uploads then?
I'm attaching the two debdiffs,
chers,
Gianfranco
Il Martedì 19 Maggio 2015 11:27, Frank Mehnert frank.mehn...@oracle.com ha
scritto:
Hi Gianfranco,
On Tuesday 19 May 2015 09:17:13 Gianfranco Costamagna wrote:
Hi
Hi Frank, as usual thanks a lot for the patch and the answer!
keep up the good work!
cheers,
G.
Il Lunedì 18 Maggio 2015 10:05, Frank Mehnert frank.mehn...@oracle.com ha
scritto:
Hi Maxime,
On Friday 15 May 2015 11:23:15 Maxime Dor wrote:
Could an experienced dev validate that this
Hi folks,in my ongoing effort to fix Debian/Ubuntu packages, I would like to
understand how and if virtualbox is affected, and if a patch is available for
download.
thanks
cheers,
Gianfranco
Il Venerdì 15 Maggio 2015 11:31, Maxime Dor m...@kamax.io ha scritto:
Hi,
Could an experienced
Hi Frank,
can you please update the LATEST-BETA link too?
http://dlc-cdn.sun.com/virtualbox/LATEST-BETA.TXT
still shows BETA2
thanks!
Gianfranco
Il Giovedì 7 Maggio 2015 21:52, Frank Mehnert frank.mehn...@oracle.com ha
scritto:
Please do NOT use this VirtualBox Beta release on production
Hi Virtualbox/kbuild developers,
I would like to share you some Debian patches, not Debian specific, that would
be nice to address upstream too.
You can find them here [1]. They should be all GPL-3+ code, since our copyright
file states so.
01_gnukfreebsd.diff -- kfreebsd port
02_sh4.diff --
-dprintf.patch
and
kBuild-0.1.3-escape.patch
because they seem to be not useful for Debian...
thanks again!
Gianfranco
Il Mercoledì 13 Maggio 2015 16:25, Sérgio Basto ser...@serjux.com ha scritto:
On Qua, 2015-05-13 at 10:48 +, Gianfranco Costamagna wrote:
08_no_o3_optimization.diff -- disable 03
I actually went to the website and triggered the unsubscribe mail with his mail
address :)
cheers,
G.
Sent from Yahoo Mail on Android
From:François Revol re...@free.fr
Date:Wed, 6 May, 2015 at 13:10
Subject:Re: [vbox-dev] unsubscribe
Hello,
On 06/05/2015 11:46, Daniel Dreibrodt wrote:
Hi Alexey, Debian Maintainer here.
I just read your mail, but I didn't look/download the code.
Do you think such addon would be ready/useful for Debian? is it stable? which
license does it have? do you plan to maintain it?
I would like to understand if a pakaging would be useful for the
Hi Frank,
we have upgraded src/VBox/RDP/client to rdesktop version 1.8.3. The change
is already visible in the public repository. We didn't change config.sub /
config.guess as they come from upstream.
thanks I obviously missed that!
Opened a ticket on
Hi Frank,
3) a build failure that goes away without the -O flag, but needs to be
fixed :) (I do not have time/knowledge/resources to properly fix this)
[...]
/virtualbox-4.3.22-dfsg/src/libs/xpcom18a4/xpcom/reflect/xptcall/src/md/uni
x/xptcinvoke_x86_64_linux.cpp:211:1: error: unable to
Hi Frank, there are a couple more typos
I: virtualbox-guest-utils: spelling-error-in-binary usr/sbin/VBoxControl
targetting targeting
I: virtualbox-guest-utils: spelling-error-in-binary usr/sbin/VBoxService
targetting targeting
I: virtualbox: spelling-error-in-binary
Hi Frank,
thanks. Fixed most places.
thanks to you!
Done.
thanks again!
This comes from using 'ld --as-needed' and I don't see a reason to drop
this linker flag...
I'm aware of the --as-needed flag, wow, providing a library that uses *no* libc
symbols
(hence dropped by as-needed flag) is
are harder to fix because
they come from a different repository or from 3rd-party source code.
Sorry but currently I have more important things on my TODO list :-)
Frank
On Wednesday 08 April 2015 14:40:30 Gianfranco Costamagna wrote:
Hi Frank, there are a couple more typos
I: virtualbox
Hi Developers,
some minor source code issues (Virtualbox 5.0.0_BETA1):
1) can you please sed s/targetting/targeting/g on the source tree?
2) can you please add a Keywords entry in your desktop file?
3) E: virtualbox: library-not-linked-against-libc
Hi Virtualbox developers, can you please update the config.sub and config.guess
files on
src/VBox/RDP/client directory?
thanks
Gianfranco
___
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
Hi Frank, I was mostly sure about an april fool joke :) but it seems not!
do you have any schedule for the release? I would like to update the debian
packaging as soon as you are confortable with a release.
(consider that Debian will be probably released in a month, so we are right now
Hi,
can't you try with a newer vbox version, such as 4.3.26?
cheers,
G.
Il Lunedì 23 Marzo 2015 11:25, Rūdolfs Bundulis rudolfs.bundu...@gmail.com ha
scritto:
Hi,
I'm porting my existing frontend from Windows (COM) to Linux (XPCOM). I was
able to successfully plug all the XPCOM stuff
I guess this bug might be fixed in 4.3.24.
Please wait for the debian and the ubuntu upload, in the meanwhile please open
an ubuntu bug.
cheers,
Gianfranco
Il Mercoledì 4 Marzo 2015 17:20, las las laska...@gmail.com ha scritto:
Could anybody please help?
-- Forwarded message
Sorry for the noise, I just answer the question
Hi, you might find useful some code I contributed to the killerbee project
https://code.google.com/p/killerbee/source/browse/branches/bleeding/tools/zbinterface
it should work with TinyOS IIRC, and it gives you a virtual interface bridged
with
Hi Michael and virtualbox developers
I found the (proper) solution for this problem.
First *thanks* Michael for giving me the correct hint with the filter-out
patch (that part is from you, so is released as your preferred license).
The problem is a bad number in the define, it was driving
Hi virtualbox developers,
I'm sending you a patch to make virtualbox build against gcc-5
(upcoming release, not yet stable.)
As usual my work has to be considered MIT licensed.
I'm not quite confortable with the patch, but I'm happy to share it with you
(I don't attach a file because as said
, Gianfranco Costamagna
costamagnagianfra...@yahoo.it ha scritto:
Hi folks, your recent changes to the vboxvideo Makefile broke the build when
VBOX_USE_SYSTEM_XORG_HEADERS is defined (debian)
the following trivial patch makes the build succeed again.
diff --git a/src/VBox/Additions/x11/vboxvideo
93 matches
Mail list logo