Thanks a lot! I know that 4.x is a maintenance release, which is great
for an LTS. It's working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517161
Title:
virtualbox SRU for CVE
To manage
Amr, my pleasure! Yes, I hope I'll continue updating it now that the SRU
policy has been relaxed.
Please note anyway that you might want to use the newer 5.0 version of
virtualbox, 4.x is only a maintenance release (only bug fixes and CVE
fixes)
--
You received this bug notification because you
Thanks a lot for updating VB in Trusty. It's a very important piece of
software, especially for LTS releases to test other OS. I hope to always
keep up-to-date with maintenance releases of VB in Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Tyler, no need to be sorry! Better to double check rather than
uploading broken packages!
And honestly I did try the upgrade path, but never the install path and
never on the old 3.2 kernel.
So, thanks for giving me the opportunity to test it a little bit more!
Keep up the hard work!
--
You
Hi again Tyler,
Installed ubuntu-12.04.5-desktop-amd64.iso
apt-get update
apt-get dist-upgrade
remove kernel 3.13 and install kernel 3.2.0-94
apt-add-repository ppa:ubuntu-security-proposed
apt-get update apt-get install virtualbox
everything is good too
http://pastebin.com/9sDHPekC
I also
Hi Tyler,
Installed ubuntu-14.04.3-desktop-amd64.iso
apt-get update
apt-get dist-upgrade
apt-add-repository ppa:ubuntu-security-proposed/ppa
apt-get update apt-get install virtualbox
everything is good.
http://pastebin.com/qcQCUjag
cat dkms.log |grep virtualbox
(note I later installed the guest
Hello! I'm really sorry about that. We have a script that pulls down the
binary packages, for a given source package, from a ppa and stores them
in a local apt repository that testing VMs then use. It looks like the
script didn't pull down all of the virtualbox related packages, causing
the
This bug was fixed in the package virtualbox - 5.0.10-dfsg-2ubuntu1
---
virtualbox (5.0.10-dfsg-2ubuntu1) wily-security; urgency=medium
* Update wily to fix CVEs. (LP: #1517161)
* Drop xserver-xorg-legacy runtime package, it is not needed
and not available to wily.
* Fix
This bug was fixed in the package virtualbox -
4.1.44-dfsg-1+deb7u1ubuntu1
---
virtualbox (4.1.44-dfsg-1+deb7u1ubuntu1) precise-security; urgency=medium
* New upstream release. (LP: #1517161)
- drop patches and rebase with debian wheezy-security upload
- all CVEs are fixed
12.04 install failure. Note that I was running the 3.2 kernel which,
according to our IRC conversation, should work.
** Attachment added: "12.04-install-failure.txt"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1517161/+attachment/4524825/+files/12.04-install-failure.txt
--
You
14.04 install failure.
** Attachment added: "14.04-install-failure.txt"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1517161/+attachment/4524822/+files/14.04-install-failure.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi - I got a little uneasy about all of the changes to the packaging and
decided to do some quick install testing of my own (install, not
upgrade). It looks like the updates break `apt-get install virtualbox`
in 14.04 and 12.04. I tested the packages in the security-proposed ppa:
Hi Tyler, well, I would like if possible to trash the ubuntu changelog,
and start from the exact debian security changelog + the ubuntu change.
e.g. for vivid I started from the trusty changelog, but vivid has an
ubuntu1 and ubuntu2 delta (that is already part of Debian changelogs)
I would
Hello - Big thanks for these updates!
Can you comment on the level of testing performed? There were quite a
few packaging changes so I'd like to hear that they've all been
thoroughly installation and upgrade tested.
I'm going to adjust the versioning of the vivid update to
Hi Seth, for Vivid you can use the trusty package, anyway, I added a
fake changelog entry and uploaded on the same ppa.
>Trusty sounds difficult. There are multiple supported kernels for 14.04 LTS;
>3.13 kernel in 14.04.1
>3.16 kernel from 14.04.2 (linux-generic-lts-utopic)
>3.19 kernel from
>> I'm not happy with this request, but well, I monitor for bugs, and I
>> guess I'll continue doing my best in keeping virtualbox working
>> correctly (I couldn't before because I was forced by the MRE updates
>> impossibility)
>
>Is there anything that could be done to help?
updating virtualbox
wily is also available in my ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517161
Title:
virtualbox SRU for CVE
To manage notifications about this bug go to:
PLEASE ASK BEFORE UPLOAD!
I did some changes in changelog
http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/?h=jessie=9e8c88dc9bac94c24b839d1d552a375a0a5c783b
because since the CVE-2015-7183 I would like to upload in Debian and use
that changelog for ubuntu too, to keep track
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517161
Title:
virtualbox SRU for CVE
To manage notifications about this bug go to:
wily needs to comment xorg-legacy package from runtime depenencies,
available only in xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517161
Title:
virtualbox SRU for CVE
To manage
** Changed in: virtualbox (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517161
Title:
virtualbox SRU for CVE
To manage notifications about this bug go
21 matches
Mail list logo
