<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>5890</bug_id>
          
          <creation_ts>2014-02-27 00:13:59 +0000</creation_ts>
          <short_desc>package arch selection logic in rootfs creation is broken</short_desc>
          <delta_ts>2014-08-14 10:43:48 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>configuration</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>TC needed</status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>1.6 M4</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Nitin Kamble">nitin.a.kamble</reporter>
          <assigned_to name="Laurentiu Palcu">laurentiu.palcu</assigned_to>
          <cc>alexandru.c.georgescu</cc>
    
    <cc>sgw</cc>
          
          <qa_contact name="Lucian Musat">georgex.l.musat</qa_contact>
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>40720</commentid>
    <comment_count>0</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2014-02-27 00:13:59 +0000</bug_when>
    <thetext>When building multiple BSPs in a single build directory, the package arch selection is going wrong. For example in the log seen below, the alsa-state package is available in 3 flavors viz @core2_64, @corei7_64 and @intel_corei7_64. But for the intel_corei7_64 machine, the package alsa-state@corei7-64 is installed instead of the desired package: alsa-state-0.2.0-r3@intel_corei7_64.

Currently the recipes reproducing this issue are not up-streamed yet because of this issue. the commits for meta-intel to reproduce this issue are available here: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=nitin/bsp-ng2

To reproduce build multiple BSPs in a single build directory in this sequence: sugarbay crownbay intel-core2-32 intel-corei7-64


log:

nitin@yocto-hm1:~/build-test-bsps/build-common/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0&gt; grep -r alsa-state *
Binary file core-image-sato-1.0/iso/rootfs.img matches
Binary file core-image-sato-1.0/hddimg/rootfs.img matches
installed_pkgs.txt:alsa-state corei7-64
installed_pkgs.txt:alsa-states corei7-64
Binary file pseudo/files.db matches
rootfs/etc/init.d/alsa-state:# Filename: alsa-state
rootfs/etc/init.d/alsa-state:    echo &quot;Usage: /etc/init.d/alsa-state {start|stop|status}&quot;
Binary file rootfs/var/lib/rpm/Nvra matches
Binary file rootfs/var/lib/rpm/Requirename matches
Binary file rootfs/var/lib/rpm/Name matches
Binary file rootfs/var/lib/rpm/log/log.0000000003 matches
Binary file rootfs/var/lib/rpm/Providename matches
Binary file rootfs/var/lib/rpm/Filepaths matches
Binary file rootfs/var/lib/rpm/Packages matches
Binary file rootfs/var/lib/rpm/Basenames matches
temp/log.do_rootfs.70297:Output from alsa-state-0.2.0-r3@corei7_64:
temp/log.do_rootfs.70297: Removing any system startup links for alsa-state ...
temp/log.do_rootfs.70297: Adding system startup for /srv/home/nitin/build-test-bsps/build-common/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/init.d/alsa-state.
temp/log.do_rootfs.70297:  alsa-state                                                                    
temp/log.do_rootfs.70297:  alsa-states                                                                   
temp/log.do_rootfs.70297:  25:Installing alsa-states     ######################################## [  3%]
temp/log.do_rootfs.70297: 178:Installing alsa-state      ######################################## [ 23%]
temp/log.do_rootfs.44565:Output from alsa-state-0.2.0-r3@corei7_64:
temp/log.do_rootfs.44565: Removing any system startup links for alsa-state ...
temp/log.do_rootfs.44565: Adding system startup for /srv/home/nitin/build-test-bsps/build-common/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/init.d/alsa-state.
temp/log.do_rootfs.44565:  alsa-state                                                                    
temp/log.do_rootfs.44565:  alsa-states                                                                   
temp/log.do_rootfs.44565:  25:Installing alsa-states     ######################################## [  3%]
temp/log.do_rootfs.44565: 168:Installing alsa-state      ######################################## [ 22%]
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r3@core2_64
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r3@corei7_64
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r3@intel_corei7_64
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r3@core2_64
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r3@corei7_64
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r3@intel_corei7_64
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r3@core2_64
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r3@corei7_64
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r3@intel_corei7_64
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r3@core2_64
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r3@corei7_64
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r3@intel_corei7_64</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40730</commentid>
    <comment_count>1</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2014-02-27 09:24:38 +0000</bug_when>
    <thetext>Do you think it would be possible, in the future, that you provide: poky commit used to replicate the problem, package manager backend used, local.conf and/or bblayers.conf settings? So that I don&apos;t have to deduce them all?

thanks</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40741</commentid>
    <comment_count>2</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2014-02-27 13:24:02 +0000</bug_when>
    <thetext>With the latest master and the meta-intel branch you specified, the &apos;MACHINE=intel-core2-32 bb -e core-image-sato&apos; fails to fetch the kernel, as below. It built just fine for sugarbay &amp; crownbay though...

Build Configuration:
BB_VERSION        = &quot;1.21.1&quot;
BUILD_SYS         = &quot;x86_64-linux&quot;
NATIVELSBSTRING   = &quot;Ubuntu-12.04&quot;
TARGET_SYS        = &quot;i586-poky-linux&quot;
MACHINE           = &quot;intel-core2-32&quot;
DISTRO            = &quot;poky&quot;
DISTRO_VERSION    = &quot;1.5+snapshot-20140227&quot;
TUNE_FEATURES     = &quot;m32 core2&quot;
TARGET_FPU        = &quot;&quot;
meta
meta-yocto
meta-yocto-bsp    = &quot;master:5ab9d7e28f987fba8bab03bb7851c263f746c208&quot;
meta-intel
meta-sugarbay
meta-crownbay     = &quot;test:00008bc26002354f89c377c3ec9732e4ff79aa56&quot;

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: Failed to fetch URL git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standard/base,meta;name=machine,meta, attempting MIRRORS if available
ERROR: Fetcher failure: Unable to find revision 29594404d7fe73cd80eaa4ee8c43dcc53970c60e in branch meta even from upstream
ERROR: Function failed: Fetcher failure for URL: &apos;git://git.pokylinux.org/linux-yocto-dev.git;nocheckout=1;branch=standard/base,meta;name=machine,meta&apos;. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /ssd/work/yp2/build/tmp/work/core2-32-intel-common-poky-linux/linux-yocto-dev/3.13++gitAUTOINC+29594404d7_29594404d7-r0/temp/log.do_fetch.22378
ERROR: Task 73 (/ssd/work/yp2/poky/meta/recipes-kernel/linux/linux-yocto-dev.bb, do_fetch) failed with exit code &apos;1&apos;
NOTE: Tasks Summary: Attempted 4845 tasks of which 4844 didn&apos;t need to be rerun and 1 failed.
No currently running tasks (237 of 4886)

Summary: 1 task failed:
  /ssd/work/yp2/poky/meta/recipes-kernel/linux/linux-yocto-dev.bb, do_fetch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40769</commentid>
    <comment_count>3</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2014-02-27 17:15:09 +0000</bug_when>
    <thetext>My git repository commits:
* poky.git:
** master: commit e47afff7d812c74f8091d85facfdf34d6a1b698e

* meta-intel.git
** nitin/bsp-ng2 commit 00008bc26002354f89c377c3ec9732e4ff79aa56


Additional lines in local.conf

EXTRA_IMAGE_FEATURES += &quot;tools-testapps&quot;
LICENSE_FLAGS_WHITELIST += &quot;commercial&quot;
SRCREV_machine = &quot;${AUTOREV}&quot;
SRCREV_meta = &quot;${AUTOREV}&quot;

I will try adding this kind of information in the future bugs.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40770</commentid>
    <comment_count>4</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2014-02-27 17:19:38 +0000</bug_when>
    <thetext>BTW when the BSP layers need to be setup properly. I see that in the comment #3 meta-sugarbay and meta-crownbay layers are included while building intel-core2-32 BSP, which is not right. These layer requirements are specified in the README files in the meta-intel layer.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40793</commentid>
    <comment_count>5</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2014-02-28 11:21:55 +0000</bug_when>
    <thetext>Reproduced it. Working on finding a proper fix.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40803</commentid>
    <comment_count>6</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2014-02-28 18:29:58 +0000</bug_when>
    <thetext>I think the problem is related to this commit:

commit 12f47c23df8c109676f66d580d666a3147f3b046
Author: Laurentiu Palcu &lt;laurentiu.palcu@intel.com&gt;
Date:   Mon Feb 10 09:32:04 2014 +0200

    lib/oe/package_manager.py: RpmPM: fix issue with multilib builds
    
    Use python sets instead of lists, to avoid duplicates. When doing a
    multilib build, &quot;smart channel --add&quot; fails because it tries to add
    &apos;all&apos; channel twice.
    
    (From OE-Core rev: 730d675090eec5c03e444f0448d96a52035d0bef)

Apparently, converting a list to a set does not keep the order of the items, as they were in the list... So, reverting this commit should solve the ordering issue. The problem, however, is that I cannot reproduce the original problem that fix was meant for so I can find another fix for it...

So, please try reverting the commit for now and continue with your work.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40804</commentid>
    <comment_count>7</comment_count>
    <who name="Nitin Kamble">nitin.a.kamble</who>
    <bug_when>2014-02-28 19:23:41 +0000</bug_when>
    <thetext>Thanks for the update Laurentiu. I will try reverting the commit you mentioned to proceed with my work.

Nitin</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40834</commentid>
    <comment_count>8</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2014-03-03 13:49:20 +0000</bug_when>
    <thetext>Patches sent on the ML.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>40922</commentid>
    <comment_count>9</comment_count>
    <who name="Laurentiu Palcu">laurentiu.palcu</who>
    <bug_when>2014-03-06 15:30:53 +0000</bug_when>
    <thetext>Patches merged:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=61b8503f25ede654f33b44ff08591e3bd4b1c092
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=97289f7579b62080cc19dc2df7683c05afb026ae</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>44850</commentid>
    <comment_count>10</comment_count>
    <who name="Alexandru Georgescu">alexandru.c.georgescu</who>
    <bug_when>2014-07-31 10:58:59 +0000</bug_when>
    <thetext>Assinging this to Lucian for bug verification and TC creation. 
We need to add more this type of scenarios to our testing, e.g. building more bsp&apos;s using the same build directory.
As I see from Nitin&apos;s original problem, he used different arches to perform the build. Maybe a TC that builds machines with all the flavors @core2_64, @corei7_64, and the others should be sufficent.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>45119</commentid>
    <comment_count>11</comment_count>
    <who name="Lucian Musat">georgex.l.musat</who>
    <bug_when>2014-08-14 10:43:48 +0000</bug_when>
    <thetext>Tested this on sugarbay, crownbay, core2-32 and corei7-64. This is the result:

lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build$ cd tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0$ grep -r alsa-state *
Binary file core-image-sato-1.0/hddimg/rootfs.img matches
Binary file core-image-sato-1.0/iso/rootfs.img matches
installed_pkgs.txt:alsa-state corei7-64
installed_pkgs.txt:alsa-states corei7-64
Binary file pseudo/files.db matches
Binary file rootfs/var/lib/rpm/Requirename matches
Binary file rootfs/var/lib/rpm/Providename matches
Binary file rootfs/var/lib/rpm/Filedigests matches
Binary file rootfs/var/lib/rpm/Filepaths matches
Binary file rootfs/var/lib/rpm/Basenames matches
Binary file rootfs/var/lib/rpm/Nvra matches
Binary file rootfs/var/lib/rpm/log/log.0000000004 matches
Binary file rootfs/var/lib/rpm/Name matches
Binary file rootfs/var/lib/rpm/Packages matches
rootfs/etc/init.d/alsa-state:# Filename: alsa-state
rootfs/etc/init.d/alsa-state:    echo &quot;Usage: /etc/init.d/alsa-state {start|stop|status}&quot;
temp/log.do_rootfs.12350:  alsa-state                                                                    
temp/log.do_rootfs.12350:  alsa-states                                                                   
temp/log.do_rootfs.12350:  34:Installing alsa-states     ######################################## [  2%]
temp/log.do_rootfs.12350:Output from alsa-state-0.2.0-r5@corei7_64:
temp/log.do_rootfs.12350: Removing any system startup links for alsa-state ...
temp/log.do_rootfs.12350: 541:Installing alsa-state      ######################################## [ 47%]
temp/log.do_rootfs.12350: Adding system startup for /media/lucian/SSD/work/poky/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/init.d/alsa-state.
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r5@corei7_64
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r5@corei7_64
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r5@corei7_64
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r5@corei7_64
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0$ cd ../../../../

lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp$ cd work/intel_core2_32-poky-linux/core-image-sato/1.0-r0/
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/intel_core2_32-poky-linux/core-image-sato/1.0-r0$ grep -r alsa-state *
Binary file core-image-sato-1.0/hddimg/rootfs.img matches
Binary file core-image-sato-1.0/iso/rootfs.img matches
installed_pkgs.txt:alsa-state core2-32
installed_pkgs.txt:alsa-states core2-32
Binary file pseudo/files.db matches
Binary file rootfs/var/lib/rpm/Requirename matches
Binary file rootfs/var/lib/rpm/Providename matches
Binary file rootfs/var/lib/rpm/Filepaths matches
Binary file rootfs/var/lib/rpm/Basenames matches
Binary file rootfs/var/lib/rpm/Nvra matches
Binary file rootfs/var/lib/rpm/log/log.0000000004 matches
Binary file rootfs/var/lib/rpm/Name matches
Binary file rootfs/var/lib/rpm/Packages matches
rootfs/etc/init.d/alsa-state:# Filename: alsa-state
rootfs/etc/init.d/alsa-state:    echo &quot;Usage: /etc/init.d/alsa-state {start|stop|status}&quot;
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r5@core2_32
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r5@core2_32
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r5@core2_32
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r5@core2_32
temp/log.do_rootfs.20094:  alsa-state                                                                    
temp/log.do_rootfs.20094:  alsa-states                                                                   
temp/log.do_rootfs.20094:  33:Installing alsa-states     ######################################## [  2%]
temp/log.do_rootfs.20094:Output from alsa-state-0.2.0-r5@core2_32:
temp/log.do_rootfs.20094: Removing any system startup links for alsa-state ...
temp/log.do_rootfs.20094: 516:Installing alsa-state      ######################################## [ 39%]
temp/log.do_rootfs.20094: Adding system startup for /media/lucian/SSD/work/poky/build/tmp/work/intel_core2_32-poky-linux/core-image-sato/1.0-r0/rootfs/etc/init.d/alsa-state.
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/intel_core2_32-poky-linux/core-image-sato/1.0-r0$ cd ../../../

lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work$ cd 
all-poky-linux/                    corei7-64-intel-common-poky-linux/ intel_corei7_64-poky-linux/
core2-32-emgd-poky-linux/          corei7-64-poky-linux/              sugarbay-poky-linux/
core2-32-intel-common-poky-linux/  crownbay-poky-linux/               x86_64-linux/
core2-32-poky-linux/               intel_core2_32-poky-linux/         x86_64-poky-linux/
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work$ cd sugarbay-poky-linux/core-image-sato/1.0-r0/
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/sugarbay-poky-linux/core-image-sato/1.0-r0$ 
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/sugarbay-poky-linux/core-image-sato/1.0-r0$ 
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/sugarbay-poky-linux/core-image-sato/1.0-r0$ 
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/sugarbay-poky-linux/core-image-sato/1.0-r0$ grep -r alsa-state *
Binary file core-image-sato-1.0/hddimg/rootfs.img matches
Binary file core-image-sato-1.0/iso/rootfs.img matches
installed_pkgs.txt:alsa-state corei7-64
installed_pkgs.txt:alsa-states corei7-64
Binary file pseudo/files.db matches
Binary file rootfs/var/lib/rpm/Requirename matches
Binary file rootfs/var/lib/rpm/Providename matches
Binary file rootfs/var/lib/rpm/Filedigests matches
Binary file rootfs/var/lib/rpm/Filepaths matches
Binary file rootfs/var/lib/rpm/Basenames matches
Binary file rootfs/var/lib/rpm/Nvra matches
Binary file rootfs/var/lib/rpm/log/log.0000000004 matches
Binary file rootfs/var/lib/rpm/Name matches
Binary file rootfs/var/lib/rpm/Packages matches
rootfs/etc/init.d/alsa-state:# Filename: alsa-state
rootfs/etc/init.d/alsa-state:    echo &quot;Usage: /etc/init.d/alsa-state {start|stop|status}&quot;
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r5@corei7_64
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r5@corei7_64
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r5@corei7_64
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r5@corei7_64
temp/log.do_rootfs.11307:  alsa-state                                                                    
temp/log.do_rootfs.11307:  alsa-states                                                                   
temp/log.do_rootfs.11307:  25:Installing alsa-states     ######################################## [  2%]
temp/log.do_rootfs.11307:Output from alsa-state-0.2.0-r5@corei7_64:
temp/log.do_rootfs.11307: Removing any system startup links for alsa-state ...
temp/log.do_rootfs.11307: 716:Installing alsa-state      ######################################## [ 64%]
temp/log.do_rootfs.11307: Adding system startup for /media/lucian/SSD/work/poky/build/tmp/work/sugarbay-poky-linux/core-image-sato/1.0-r0/rootfs/etc/init.d/alsa-state.
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/sugarbay-poky-linux/core-image-sato/1.0-r0$ cd ../../../

lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work$ cd crownbay-poky-linux/core-image-sato/1.0-r0/
lucian@lucian-OptiPlex-7010:/media/lucian/SSD/work/poky/build/tmp/work/crownbay-poky-linux/core-image-sato/1.0-r0$ grep -r alsa-state *
Binary file core-image-sato-1.0/hddimg/rootfs.img matches
Binary file core-image-sato-1.0/iso/rootfs.img matches
installed_pkgs.txt:alsa-state core2-32
installed_pkgs.txt:alsa-states core2-32
Binary file pseudo/files.db matches
Binary file rootfs/var/lib/rpm/Requirename matches
Binary file rootfs/var/lib/rpm/Providename matches
Binary file rootfs/var/lib/rpm/Filepaths matches
Binary file rootfs/var/lib/rpm/Basenames matches
Binary file rootfs/var/lib/rpm/Nvra matches
Binary file rootfs/var/lib/rpm/log/log.0000000003 matches
Binary file rootfs/var/lib/rpm/Name matches
Binary file rootfs/var/lib/rpm/Packages matches
rootfs/etc/init.d/alsa-state:# Filename: alsa-state
rootfs/etc/init.d/alsa-state:    echo &quot;Usage: /etc/init.d/alsa-state {start|stop|status}&quot;
temp/saved/available_pkgs.txt:alsa-state-0.2.0-r5@core2_32
temp/saved/available_pkgs.txt:alsa-state-dbg-0.2.0-r5@core2_32
temp/saved/available_pkgs.txt:alsa-state-dev-0.2.0-r5@core2_32
temp/saved/available_pkgs.txt:alsa-states-0.2.0-r5@core2_32
temp/log.do_rootfs.12621:  alsa-state                                                                    
temp/log.do_rootfs.12621:  alsa-states                                                                   
temp/log.do_rootfs.12621:  24:Installing alsa-states     ######################################## [  3%]
temp/log.do_rootfs.12621:Output from alsa-state-0.2.0-r5@core2_32:
temp/log.do_rootfs.12621: Removing any system startup links for alsa-state ...
temp/log.do_rootfs.12621: 289:Installing alsa-state      ######################################## [ 42%]
temp/log.do_rootfs.12621: Adding system startup for /media/lucian/SSD/work/poky/build/tmp/work/crownbay-poky-linux/core-image-sato/1.0-r0/rootfs/etc/init.d/alsa-state.

It seems fine now so I am marking this as verified.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>