Last modified: 2014-09-16 10:09:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71423, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69423 - androidsdk::dependencies doesn't work on Trusty
androidsdk::dependencies doesn't work on Trusty
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Low normal
: ---
Assigned To: Marc A. Pelletier
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-12 02:39 UTC by Tim Landscheidt
Modified: 2014-09-16 10:09 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Tim Landscheidt 2014-08-12 02:39:13 UTC
Some packages aren't there:

| scfc@tools-exec-12:~$ sudo apt-get install libgcc1:i386 libncurses5:i386 libsdl1.2debian:i386 libstdc++6:i386 zlib1g:i386
| Reading package lists... Done
| Building dependency tree       
| Reading state information... Done
| E: Unable to locate package libgcc1
| E: Unable to locate package libncurses5
| E: Unable to locate package libsdl1.2debian
| E: Couldn't find any package by regex 'libsdl1.2debian'
| E: Unable to locate package libstdc++6
| E: Couldn't find any package by regex 'libstdc++6'
| E: Unable to locate package zlib1g
| scfc@tools-exec-12:~$

However, the proper way to resolve this is probably not to find the equivalent Trusty packages, but what packages Android SDK actually needs to run on Trusty.
Comment 1 Antoine "hashar" Musso (WMF) 2014-08-12 11:42:45 UTC
The Android SDK I installed was on gallium which has Precise.  I guess the dependencies are slightly different now.
Comment 2 Marc A. Pelletier 2014-08-26 15:20:57 UTC
Please enumerate the dependencies you will actually need for a working SDK under Trusty.  Probably one of the best method to do so with certainty is to create a Trusty instance and try it there.
Comment 3 Antoine "hashar" Musso (WMF) 2014-09-16 08:34:42 UTC
Low priority, we no more build any Android app. Can be revisited later on.
Comment 4 Yuvi Panda 2014-09-16 10:09:20 UTC
I fixed this a while ago in I76c5b3dff7905d94adb4d46929f09250dff26bd7

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links