[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#792779: marked as done (nmu: android-platform-frameworks-base_21-2)

Your message dated Fri, 08 Jan 2016 21:13:28 +0100
with message-id <1452284008.20085.1.camel@debian.org>
and subject line Re: Bug#792779: nmu: android-platform-frameworks-base_21-2
has caused the Debian Bug report #792779,
regarding nmu: android-platform-frameworks-base_21-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
792779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792779
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

Something weird happened on the buildd build of
android-platform-frameworks-base/i386:
* /usr/bin/aapt wants libhost.so instead of libhost.so.0
* the aapt package has no dependency on android-libhost
==> #786943: aapt: error while loading shared libraries: libhost.so:
             cannot open shared object file: No such file or directory

I cannot reproduce this weird build result in neither sid nor jessie, so
binNMUs for jessie and sid (should probably get +b2 to be newer than
the one in jessie) are sufficient to fix this.

It picks up the android-libhost dependency:

$ debdiff aapt_21-2_i386.deb jessie-i386/aapt_21-2_i386.deb
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)
------------------------------------------------
Depends: android-libcutils, {+android-libhost,+} android-liblog,
android-libutils, libc6 (>= 2.7), libexpat1 (>= 2.0.1), libgcc1 (>=
1:4.1.1), libpng12-0 (>= 1.2.13-4), libstdc++6 (>= 4.1.1), zlib1g (>=
1:1.1.4), android-libandroidfw

and ldd output looks sane, too:

# ldd /usr/bin/aapt
        linux-gate.so.1 (0xf7705000)
        librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf76f7000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76f2000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76d6000)
        libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xf76b9000)
        libexpat.so.1 => /lib/i386-linux-gnu/libexpat.so.1 (0xf7690000)
        libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xf7663000)
        libcutils.so.0 => /usr/lib/android/libcutils.so.0 (0xf7654000)
        libhost.so.0 => /usr/lib/android/libhost.so.0 (0xf764e000)
        liblog.so.0 => /usr/lib/android/liblog.so.0 (0xf7645000)
        libutils.so.0 => /usr/lib/android/libutils.so.0 (0xf7612000)
        libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf7511000)
        libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf74cc000)
        libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf74ae000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf733d000)
        /lib/ld-linux.so.2 (0xf7708000)
        libbsd.so.0 => /lib/i386-linux-gnu/libbsd.so.0 (0xf732b000)


nmu android-platform-frameworks-base_21-2 . i386 . jessie-proposed-updates . -m "Rebuild to pick up a dependency on android-libhost."
nmu $UNDOCUMENTED_OPTION_TO_USE_PLUSb2 android-platform-frameworks-base_21-2 . i386 . -m "Rebuild to pick up a dependency on android-libhost."

Or would the jessie one use just 'jessie'?
I remember seeing it mentioned once that there is an option to set the
binNMU number.


Andreas

--- End Message ---
--- Begin Message --- 
On Sat, 12 Sep 2015 19:17:40 +0200 Andreas Beckmann <anbe@debian.org>
wrote:
> On 2015-07-19 23:27, Jonathan Wiltshire wrote:
> > It does indeed look like amd64 (a maintainer upload) was different
to i386
> > as built by wanna-build, and a rebuild is an appropriate fix.
Scheduled in
> > sid with +b2, I'll leave the Jessie rebuild until it's migrated.
> 
> The first binNMU attempt got stuck somehow and when it was retried 
> later, it got entangled in some c++11 transition bits ... which is 
> still reproducible:
> 
> 
> g++ -fPIC -Wl,-rpath=/usr/lib/android -Wl,-z,relro -o aapt
AaptAssets.o Command.o CrunchCache.o FileFinder.o Main.o Package.o
StringPool.o XMLNode.o ResourceFilter.o ResourceTable.o Images.o
Resource.o SourcePos.o ZipEntry.o ZipFile.o -lrt -ldl -lpthread -lz
-lexpat -lpng -L/usr/lib/android  -lcutils -lhost -llog -lutils
-L../../libs/androidfw  -landroidfw 
> XMLNode.o: In function `parseStyledString(Bundle*, char const*,
android::ResXMLTree*, android::String16 const&, android::String16*,
android::Vector<StringPool::entry_style_span>*, bool, bool)':
> /tmp/buildd/android-platform-frameworks-base-
21/tools/aapt/XMLNode.cpp:214: undefined reference to
`pseudolocalize_string(std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&)'
> collect2: error: ld returned 1 exit status
> 
> 
> Andreas
> 

I just did a sourceful (NMU) upload of both packages, 
android-platform-frameworks-base and 
android-platform-build

so this binNMU should not be needed anymore.

-- 
tobi

--- End Message ---
Reply to: