Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/commit/08348593a2ec03767e92ff247f6279df76434194#commitcomment-12371179
Hi again @pdion891
That's my SSVM built upon the template 17th July
* SSVM Linux distro:
* root@s-2-VM:~# uname -a
* Linux s-2-VM 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u2 x86_64
GNU/Linux
* QCOW downloaded on 20th July:
* -rw-r--r--. 1 root root 325160960 Jul 20 13:26
f2f43a13-77d0-432e-82c2-49f585a8b5a7.qcow2
According to Debian Packages page, the lbnl1 is equivalent to lbnl-3-200
package. You cans ee it here:
* https://packages.debian.org/wheezy-backports/libnl-3-200
When I tried to install the lbnl1 from wheezy-backports, I got the
following:
root@s-2-VM:~# apt-get install -t wheezy-backports libnl1
Reading package lists... Done
Building dependency tree
Reading state information... Done
libnl1 is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
I then tried to install the package lbnl-3-200 and got the following:
root@s-2-VM:~# apt-get install -t wheezy-backports libnl-3-200
Reading package lists... Done
Building dependency tree
Reading state information... Done
libnl-3-200 is already the newest version.
libnl-3-200 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 33 not upgraded.
So, did the job configuration changed?
Cheers,
Wilder
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
