On Thursday, October 16, 2014 07:39:25 AM Harald Sitter wrote:
> dear madam or sir,
> 
> I wish to inform you that y'all are not updating symbols files correctly :P
> 
> This is upload ppa3/amd64, it has missing symbols, oh my:
> https://launchpadlibrarian.net/186658670/buildlog_ubuntu-utopic-amd64.kconfi
> g_5.3.0-0ubuntu1~ubuntu14.10~ppa3_UPLOADING.txt.gz
> 
> Looking at ppa3/i386 we can see that it does not have missing symbols:
> https://launchpadlibrarian.net/186658727/buildlog_ubuntu-utopic-i386.kconfig
> _5.3.0-0ubuntu1~ubuntu14.10~ppa3_UPLOADING.txt.gz
> 
> ^ I'll come out and say that this means the symbols in question are
> arch specific ;)
> 
> Now this is the change that came out of this:
> http://anonscm.debian.org/cgit/pkg-kde/frameworks/kconfig.git/commit/?h=kubu
> ntu_utopic_next&id=77d2781293e38ed25a10d73c3fbc349e8ceea1ba
> 
> The symbols file knowledgable reader might notice that it is in fact
> not declaring the new symbols as arch specific.
> 
> So what happened in ppa4/amd64 was that the missing symbols went away
> (hooray):
> https://launchpadlibrarian.net/186664133/buildlog_ubuntu-utopic-amd64.kconf
> ig_5.3.0-0ubuntu1~ubuntu14.10~ppa4_UPLOADING.txt.gz
> 
> BUT in ppa4/i386 they now show up because the symbol was not marked
> arch specific:
> https://launchpadlibrarian.net/186664114/buildlog_ubuntu-utopic-i386.kconfig
> _5.3.0-0ubuntu1~ubuntu14.10~ppa4_UPLOADING.txt.gz
> 
> I am reasonable certain that all of us would make exactly this
> mistake. So, to have us not do this anymore here's why:
> 
> pkgkde-symbolshelper can only know that the symbol is arch specific if
> you show it *both* logs. This in particular applies to new symbols,
> existing arch-specific ones are not marked as missing if they are
> missing on an arch they were not there on to begin with.
> 
> The way you do this is actually really straight forward.
> 
> 1) get all arch logs available
> 2) pkgkde-symbolshelper batchpatch -v VERSION -c i386,amd64
> buildlog_ubuntu-*
Will do.
> 
> All should be well now.
> 
> PS if it worked you should see this in the output:
> > pkgkde-symbolshelper: info: architecture set changed for the symbols 
below:
> PPS if ppa-status actually marked kconfig as green the script might be
> busted WRT symbols
> 
> PPPS there is pkgkde-getbuildlogs in debian helping with downloading
> all logs, perhaps something like that would be good to have on our
> side as well
This sounds like something that would be very helpful.
> 
> PPPPS our jenkins automatically updates symbols but also makes this
> mistake, so new symbols in unstable might in fact not have proper
> architecture markers either
> 
> HS

-- 
Scarlett Clark
Kubuntu & KDE Contributor
sgcl...@kubuntu.org

Attachment: signature.asc
Description: This is a digitally signed message part.

-- 
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Reply via email to