On Tuesday 20 December 2016 04:11 PM, Hans-Christoph Steiner wrote:
> what about the sid and stretch instances? Do they also have the package
> version mismatch?
No they won't, since it is a fresh installation of sid and stretch
within a qemu device on top of jessie host.
--
Senthil Kumaran
what about the sid and stretch instances? Do they also have the package
version mismatch?
On Tuesday 20 December 2016 03:05 PM, Hans-Christoph Steiner wrote:
> Do the LAVA instances with the URLs have the same problem?
The instance ie., staging02.lavalab runs jessie as seen below:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux
Do the LAVA instances with the URLs have the same problem?
We need to add versioned Depends: to packages like adb. Right now adb
just "Depends: android-libadb" which is problematic. It should be
"Depends: android-libadb (>= 7.0.0+r1~).
On Tuesday 20 December 2016 02:51 PM, Hans-Christoph Steiner wrote:
> I can't reproduce these on my stretch amd64 chroot, adb works fine for
> me. So we'll need to figure how what in the environment is triggering
> the issue. Are all the machines mentioned here ARM? Or what arches?
All these
I can't reproduce these on my stretch amd64 chroot, adb works fine for
me. So we'll need to figure how what in the environment is triggering
the issue. Are all the machines mentioned here ARM? Or what arches?
For "adb: symbol lookup error: adb: undefined symbol: kFeatureShell2",
my guess is
Package: adb
Version: 1:7.0.0+r1-1
Severity: normal
Dear Maintainer,
I upgraded to the latest version of adb in my machine and while trying to use
adb command I get the following error:
stylesen@harshu:~$ adb devices
adb: symbol lookup error: adb: undefined symbol: kFeatureShell2
7 matches
Mail list logo
