Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #187415 > unrolled thread

virtualbox - missing packages

Back to article view | Back to linux.debian.user

Contents

  virtualbox - missing packages Tamas Hegedus <biohegedus@gmail.com> - 2017-09-30 07:40 +0200
    Re: virtualbox - missing packages Hans <hans.ullrich@loop.de> - 2017-09-30 09:20 +0200
      Re: virtualbox - missing packages Sven Hoexter <sven@timegate.de> - 2017-09-30 09:40 +0200
        Re: virtualbox - missing packages Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-30 14:30 +0200
          Re: virtualbox - missing packages Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-30 14:40 +0200
    Re: virtualbox - missing packages Tamas Hegedus <biohegedus@gmail.com> - 2017-09-30 17:50 +0200
    Re: virtualbox - missing packages Patrick Bartek <nemommxiv@gmail.com> - 2017-09-30 20:30 +0200

#187415 — virtualbox - missing packages

Hi,

A few weeks ago I could install virtualbox on stretch w/o any problem.
Now I try to install on a different computer and have the broken 
packages error shown below.

At the same time I have installed:
i   libssl1.0.2                                               - Secure 
Sockets Layer toolkit - shared libraries
i   libssl1.1                                                 - Secure 
Sockets Layer toolkit - shared libraries

I also installed vpx-tools

I also have

i   linux-image-amd64                                         - Linux 
for 64-bit PCs (meta-package)

What can I do?
Thanks a lot for your help in advance.

Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable
                   Depends: libvpx3 (>= 1.5.0) but it is not installable
                   Recommends: linux-image but it is not installable
E: Unable to correct problems, you have held broken packages.

[toc] | [next] | [standalone]

#187417

Am Samstag, 30. September 2017, 07:33:50 CEST schrieb Tamas Hegedus:
Hi,

maybe you need to add this entry in sources.list:

deb http://download.virtualbox.org/virtualbox/debian stretch contrib

See this doku:

https://wiki.debian.org/VirtualBox#Debian_9_.22Stretch.22

Hope this helps.
Good luck!

Best

Hans
> Hi,
> 
> A few weeks ago I could install virtualbox on stretch w/o any problem.
> Now I try to install on a different computer and have the broken
> packages error shown below.
> 
> At the same time I have installed:
> i   libssl1.0.2                                               - Secure
> Sockets Layer toolkit - shared libraries
> i   libssl1.1                                                 - Secure
> Sockets Layer toolkit - shared libraries
> 
> I also installed vpx-tools
> 
> I also have
> 
> i   linux-image-amd64                                         - Linux
> for 64-bit PCs (meta-package)
> 
> What can I do?
> Thanks a lot for your help in advance.
> 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable
> Depends: libvpx3 (>= 1.5.0) but it is not installable Recommends:
> linux-image but it is not installable E: Unable to correct problems, you
> have held broken packages.

[toc] | [prev] | [next] | [standalone]

#187418

On Sat, Sep 30, 2017 at 09:16:59AM +0200, Hans wrote:

Hi,

> maybe you need to add this entry in sources.list:
> 
> deb http://download.virtualbox.org/virtualbox/debian stretch contrib

Or you just use the packages from stretch-backports? Those should be the
best fit for now.
https://backports.debian.org/Instructions/

The original error message looked a bit like OP tried to use the
packages from testing/unstable in stretch which actually worked for
some time.

Sven

[toc] | [prev] | [next] | [standalone]

#187421

On 9/30/17, Sven Hoexter <sven@timegate.de> wrote:
> On Sat, Sep 30, 2017 at 09:16:59AM +0200, Hans wrote:
>
>> maybe you need to add this entry in sources.list:
>>
>> deb http://download.virtualbox.org/virtualbox/debian stretch contrib
>
> Or you just use the packages from stretch-backports? Those should be the
> best fit for now.
> https://backports.debian.org/Instructions/
>
> The original error message looked a bit like OP tried to use the
> packages from testing/unstable in stretch which actually worked for
> some time.


I've unfortunately lost track of my personal notes on this so I'm
winging it. There's this option:

apt-get install --fix-missing

You run it generically just like that. I'm encountering references to
something like "dpkg-reconfigure --all" and dpkg-reconfigure
[package-name].

"dpkg-reconfigure --all" that pops up in search engine inquiries
didn't work at all *for me*. Instead, it kept suggesting other
options.

"dpkg-reconfigure [package-name]" appeared to function. Was tested on
a normally functioning package so there wasn't much to learn from that
beyond that it *appeared* to be the right command (because it didn't
complain and offer alternative flags).

"dpkg-reconfigure --force [package-name] is rolling around out there,
too. Feels like I've tried that one, but it's a go at your own risk
kind of thing. In cases like this thread, I like the sound of that
"--force" flag. :)

It feels like I'm missing one that I've even shared on this list, but
it's not coming to mind this morning *if* there is another one.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#187422

On 9/30/17, Cindy-Sue Causey <butterflybytes@gmail.com> wrote:
> On 9/30/17, Sven Hoexter <sven@timegate.de> wrote:
>> On Sat, Sep 30, 2017 at 09:16:59AM +0200, Hans wrote:
>>
>>> maybe you need to add this entry in sources.list:
>>>
>>> deb http://download.virtualbox.org/virtualbox/debian stretch contrib
>>
>> Or you just use the packages from stretch-backports? Those should be the
>> best fit for now.
>> https://backports.debian.org/Instructions/
>>
>> The original error message looked a bit like OP tried to use the
>> packages from testing/unstable in stretch which actually worked for
>> some time.
>
>
> I've unfortunately lost track of my personal notes on this so I'm
> winging it. There's this option:
>
> apt-get install --fix-missing
>
> You run it generically just like that. I'm encountering references to
> something like "dpkg-reconfigure --all" and dpkg-reconfigure
> [package-name].
>
> "dpkg-reconfigure --all" that pops up in search engine inquiries
> didn't work at all *for me*. Instead, it kept suggesting other
> options.
>
> "dpkg-reconfigure [package-name]" appeared to function. Was tested on
> a normally functioning package so there wasn't much to learn from that
> beyond that it *appeared* to be the right command (because it didn't
> complain and offer alternative flags).
>
> "dpkg-reconfigure --force [package-name] is rolling around out there,
> too. Feels like I've tried that one, but it's a go at your own risk
> kind of thing. In cases like this thread, I like the sound of that
> "--force" flag. :)
>
> It feels like I'm missing one that I've even shared on this list, but
> it's not coming to mind this morning *if* there is another one.


*heh!* While closing out this thread's tab in my browser, the word
"broken" said let's try one more thing so I winged it again:

apt-get install --fix-broken

IT WORKS! I had checked "man dpkg" and "man dpkg-reconfigure" but
never thought to check "man apt-get". You might find yet more
possibilities by searching the output of "man apt-get", e.g. this one:

apt-get install --ignore-missing

I don't like that last one because it sounds like avoidance, sounds
like it's leaving a problem lingering. BUT something like that might
at least open the door to then fixing things as the NEXT step after
that one...

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#187426

Hi,

Thanks all the feed-backs, they helped in solving the problem.
A few weeks ago, when my virtualbox install was successful, it was an 
upgrade and not fresh debian 9 install.

Actually, finally I ended up to download the deb from virtualbox.org and 
it worked. However, it was only the install, I can not test it in the 
next days, since it is on a remote computer.

Thanks,
Tamas

On 09/30/2017 07:33 AM, Tamas Hegedus wrote:
> Hi,
>
> A few weeks ago I could install virtualbox on stretch w/o any problem.
> Now I try to install on a different computer and have the broken
> packages error shown below.
>
> At the same time I have installed:
> i   libssl1.0.2                                               - Secure
> Sockets Layer toolkit - shared libraries
> i   libssl1.1                                                 - Secure
> Sockets Layer toolkit - shared libraries
>
> I also installed vpx-tools
>
> I also have
>
> i   linux-image-amd64                                         - Linux
> for 64-bit PCs (meta-package)
>
> What can I do?
> Thanks a lot for your help in advance.
>
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not installable
>                   Depends: libvpx3 (>= 1.5.0) but it is not installable
>                   Recommends: linux-image but it is not installable
> E: Unable to correct problems, you have held broken packages.

[toc] | [prev] | [next] | [standalone]

#187431

On Sat, 30 Sep 2017 07:33:50 +0200 Tamas Hegedus <biohegedus@gmail.com>
wrote:

> Hi,
> 
> A few weeks ago I could install virtualbox on stretch w/o any problem.
> Now I try to install on a different computer and have the broken 
> packages error shown below.
> 
> At the same time I have installed:
> i   libssl1.0.2                                               -
> Secure Sockets Layer toolkit - shared libraries
> i   libssl1.1                                                 -
> Secure Sockets Layer toolkit - shared libraries
> 
> I also installed vpx-tools
> 
> I also have
> 
> i   linux-image-amd64                                         - Linux 
> for 64-bit PCs (meta-package)
> 
> What can I do?
> Thanks a lot for your help in advance.
> 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Note, selecting 'virtualbox-5.1' instead of 'virtualbox'
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>   virtualbox-5.1 : Depends: libssl1.0.0 (>= 1.0.0) but it is not
> installable Depends: libvpx3 (>= 1.5.0) but it is not installable
>                    Recommends: linux-image but it is not installable
> E: Unable to correct problems, you have held broken packages.
> 

I got similar errors last week or so after upgrading to Virtualbox
5.1.28 from 5.1.22 on my Wheezy 64-bit host.  None of my VMs would run
either. Turned out it was due to a mismatched VirtualBox Extension
Pack.  The new one (5.1.28) was downloaded, but not installed.  I was
still running 5.1.22.  I manually installed .28 and all is working.  I
also checked I had the correct matching Guest Additions installed,
too.

NOTE:  I use ONLY the VB versions from the VirtualBox repo.  NOT the
versions from the Debian repos or backports.

B

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web