Skip to contentSkip to conversation

wrong rpm name qt package

DISCUSSION Gerard van den Bosch 3 participants 10 messages May 26, 2011 – May 27, 2011

lore
Share & tools
lore
#0 lore raw

Hello,

I have developed a shared library using Qt, it compiles without any problems but it goes wrong with rpm packaging. When it packages it should create a rpm package with the name "libxmlpcpqt" but it creates a package with "libxmlpcpqt1". My question is where does the '1' come from?

The install part from the recipe is as follows:

do_install() {
     install -d ${D}${libdir}
     install -m 0755 ${S}/${PN}.so ${D}${libdir}
}

In the /tmp/work/armv7a-poky-linux-gnueabi/libxmlpcpqt-0.1-r1/image/usr/lib the libxmlpcpqt.so file correctly exists.

Regards,
Gerard

#1 lore raw
Quoted 6 lines · Gerard van den Bosch

I have developed a shared library using Qt, it compiles without any problems but it goes wrong with rpm packaging.
When it packages it should create a rpm package with the name "libxmlpcpqt" but it creates a package with "libxmlpcpqt1". My question is where does the '1' come from?

Quoted 8 lines

The install part from the recipe is as follows:

do_install() {
     install -d ${D}${libdir}
     install -m 0755 ${S}/${PN}.so ${D}${libdir}
}

In
the /tmp/work/armv7a-poky-linux-gnueabi/libxmlpcpqt-0.1-r1/image/usr/lib the libxmlpcpqt.so file correctly exists.

This happens as debian style package naming is enabled (debian.bbclass is inherited).

Cheers,

Richard

#2 lore raw
Quoted 13 lines · Richard Purdie
Quoted 12 lines · Gerard van den Bosch

I have developed a shared library using Qt, it compiles without any problems but it goes wrong with rpm packaging.
When it packages it should create a rpm package with the name "libxmlpcpqt" but it creates a package with "libxmlpcpqt1". My question is where does the '1' come from?

The install part from the recipe is as follows:

do_install() {
      install -d ${D}${libdir}
      install -m 0755 ${S}/${PN}.so ${D}${libdir}
}
Quoted 9 lines
Quoted 2 lines

In
the /tmp/work/armv7a-poky-linux-gnueabi/libxmlpcpqt-0.1-r1/image/usr/lib the libxmlpcpqt.so file correctly exists.

This happens as debian style package naming is enabled (debian.bbclass is inherited).

Cheers,

Richard

I tried removing debian from the INHERITS+= variable in the poky.conf but then it printed it couldn't find the function that is inside debian.bbclass and didn't create the package. Modifying debian.bbclass would be too drastic so I work around it like this:
Added PACKAGES+= ${PN}1 to my recipe
Modified the IMAGE_INSTALL+= variable from libxmlpcpqt to libxmlpcpqt1
This resulted in a working solution.

Regards,
Gerard

#3 lore raw
Quoted 23 lines · Gerard van den Bosch
Quoted 13 lines · Richard Purdie
Quoted 12 lines · Gerard van den Bosch

I have developed a shared library using Qt, it compiles without any problems but it goes wrong with rpm packaging.
When it packages it should create a rpm package with the name "libxmlpcpqt" but it creates a package with "libxmlpcpqt1". My question is where does the '1' come from?

The install part from the recipe is as follows:

do_install() {
      install -d ${D}${libdir}
      install -m 0755 ${S}/${PN}.so ${D}${libdir}
}
Quoted 9 lines
Quoted 2 lines

In
the /tmp/work/armv7a-poky-linux-gnueabi/libxmlpcpqt-0.1-r1/image/usr/lib the libxmlpcpqt.so file correctly exists.

This happens as debian style package naming is enabled (debian.bbclass is inherited).

Cheers,

Richard

Quoted 8 lines

I tried removing debian from the INHERITS+= variable in the poky.conf but then it printed it couldn't find the function that is inside debian.bbclass and didn't create the package.
Modifying debian.bbclass would be too drastic so I work around it like this:
Added PACKAGES+= ${PN}1 to my recipe
Modified the IMAGE_INSTALL+= variable from libxmlpcpqt to libxmlpcpqt1 This resulted in a working solution.

This is a bug and you should never need to do this. IMAGE_INSTALL should be getting remapped to the new names. The code that is meant to do that is at the top of image.bbclass:

# If we don't do this we try and run the mapping hooks while parsing which is slow # bitbake should really provide something to let us know this...
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)

Can you check that the code is being called? I suspect something to do with the BB_WORKERCONTEXT variable has been broken. We should be doing this in a better way anyhow...

Cheers,

Richard

#4 lore raw
Quoted 42 lines · Richard Purdie
Quoted 23 lines · Gerard van den Bosch
Quoted 13 lines · Richard Purdie
Quoted 12 lines · Gerard van den Bosch

I have developed a shared library using Qt, it compiles without any problems but it goes wrong with rpm packaging.
When it packages it should create a rpm package with the name "libxmlpcpqt" but it creates a package with "libxmlpcpqt1". My question is where does the '1' come from?

The install part from the recipe is as follows:

do_install() {
       install -d ${D}${libdir}
       install -m 0755 ${S}/${PN}.so ${D}${libdir}
}
Quoted 9 lines
Quoted 2 lines

In
the /tmp/work/armv7a-poky-linux-gnueabi/libxmlpcpqt-0.1-r1/image/usr/lib the libxmlpcpqt.so file correctly exists.

This happens as debian style package naming is enabled (debian.bbclass is inherited).

Cheers,

Richard

Quoted 8 lines

I tried removing debian from the INHERITS+= variable in the poky.conf but then it printed it couldn't find the function that is inside debian.bbclass and didn't create the package.
Modifying debian.bbclass would be too drastic so I work around it like this:
Added PACKAGES+= ${PN}1 to my recipe
Modified the IMAGE_INSTALL+= variable from libxmlpcpqt to libxmlpcpqt1 This resulted in a working solution.

This is a bug and you should never need to do this. IMAGE_INSTALL should be getting remapped to the new names. The code that is meant to do that is at the top of image.bbclass:

# If we don't do this we try and run the mapping hooks while parsing which is slow # bitbake should really provide something to let us know this...
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)

Quoted 8 lines

Can you check that the code is being called? I suspect something to do with the BB_WORKERCONTEXT variable has been broken. We should be doing this in a better way anyhow...

Cheers,

Richard

Ok, I am still using the Laverne release so maybe that's the problem, I will try to compile it on a system where I have the Bernard release tonight to ensure that the bug isn't fixed already. If the problem still occurs there, I will check the suggested.
I will send an update as soon as possible.

Regards,
Gerard

#5 lore raw
In reply to Richard Purdie
Quoted 42 lines · Richard Purdie
Quoted 23 lines · Gerard van den Bosch
Quoted 13 lines · Richard Purdie
Quoted 12 lines · Gerard van den Bosch

I have developed a shared library using Qt, it compiles without any problems but it goes wrong with rpm packaging.
When it packages it should create a rpm package with the name "libxmlpcpqt" but it creates a package with "libxmlpcpqt1". My question is where does the '1' come from?

The install part from the recipe is as follows:

do_install() {
       install -d ${D}${libdir}
       install -m 0755 ${S}/${PN}.so ${D}${libdir}
}
Quoted 9 lines
Quoted 2 lines

In
the /tmp/work/armv7a-poky-linux-gnueabi/libxmlpcpqt-0.1-r1/image/usr/lib the libxmlpcpqt.so file correctly exists.

This happens as debian style package naming is enabled (debian.bbclass is inherited).

Cheers,

Richard

Quoted 8 lines

I tried removing debian from the INHERITS+= variable in the poky.conf but then it printed it couldn't find the function that is inside debian.bbclass and didn't create the package.
Modifying debian.bbclass would be too drastic so I work around it like this:
Added PACKAGES+= ${PN}1 to my recipe
Modified the IMAGE_INSTALL+= variable from libxmlpcpqt to libxmlpcpqt1 This resulted in a working solution.

This is a bug and you should never need to do this. IMAGE_INSTALL should be getting remapped to the new names. The code that is meant to do that is at the top of image.bbclass:

# If we don't do this we try and run the mapping hooks while parsing which is slow # bitbake should really provide something to let us know this...
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)

Quoted 8 lines

Can you check that the code is being called? I suspect something to do with the BB_WORKERCONTEXT variable has been broken. We should be doing this in a better way anyhow...

Cheers,

Richard

Ok, I have tried the following with the Bernard release:

print "hello"
print bb.data.getVar('BB_WORKERCONTEXT', d, True)
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
print "hello2" runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)

The "hello" gets printed, and the variable outputs "None", the "hello2" doesn't get printed because the variable is None.

In the laverne release I use here it checks on something else namely:
if bb.data.getVar('__RUNQUEUE_DO_NOT_USE_EXTERNALLY', d, True) is not None:
I can't add print commands there because it gives ident errors, found that has something todo with spaces but couldn't get it working.

I tried searching some further, I see in this commit that the if is added, that is in the laverne release:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=4e0ee648b4c18b770aba11921370258f3e2aaeef

Then a few commits later it is changed to the BB_WORKERCONTEXT:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=e427f251a457f3015c4b1cdf1648c53a9acc646d

Thus I tried to figure out what sets the BB_WORKERCONTEXT, I found it in two files in bitbake namely cooker.py and runqueue.py. Eventually it leads to the loading of the configuration file and something set BB_WORKERCONTEXT then but I couldn't figure out what sets the variable.

I looked up the commits where it is added to bitbake:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/runqueue.py?id=1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584 <http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/runqueue.py?id=1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584>
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/cooker.py?id=ca09a6f08cc29f79f9742058d737deaef9d6d5ef <http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/cooker.py?id=ca09a6f08cc29f79f9742058d737deaef9d6d5ef>

But I couldn't figure out what the changes did and I did not come further than this. If I need to try something else out, let me know.

Regards,
Gerard

#6 lore raw
Quoted 23 lines · Gerard van den Bosch

Ok, I have tried the following with the Bernard release:

print "hello"
print bb.data.getVar('BB_WORKERCONTEXT', d, True)
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
print "hello2"
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)
The "hello" gets printed, and the variable outputs "None", the "hello2" doesn't get printed because the variable is None.

In the laverne release I use here it checks on something else namely:
if bb.data.getVar('__RUNQUEUE_DO_NOT_USE_EXTERNALLY', d, True) is not None:
I can't add print commands there because it gives ident errors, found that has something todo with spaces but couldn't get it working.

I tried searching some further, I see in this commit that the if is added, that is in the laverne release:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=4e0ee648b4c18b770aba11921370258f3e2aaeef

Then a few commits later it is changed to the BB_WORKERCONTEXT:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=e427f251a457f3015c4b1cdf1648c53a9acc646d

Thus I tried to figure out what sets the BB_WORKERCONTEXT, I found it in two files in bitbake namely cooker.py and runqueue.py. Eventually it leads to the loading of the configuration file and something set BB_WORKERCONTEXT then but I couldn't figure out what sets the variable.

Quoted 6 lines

I looked up the commits where it is added to bitbake:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/runqueue.py?id=1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/cooker.py?id=ca09a6f08cc29f79f9742058d737deaef9d6d5ef

But I couldn't figure out what the changes did and I did not come further than this. If I need to try something else out, let me know.

This code only triggers at rootfs generation time. I've discovered this broken in master at least. To test I did:

bitbake -b /path/to/some-image.bb -c rootfs

and then saw:

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Start package mapping
ERROR: Found package mapping
NOTE: Running task 10 of 10 (ID: 6, /media/build2/builds/rptest/meta/recipes-core/images/core-image-minimal.bb, do_rootfs)
NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Started
^C

with the following in image.bbclass:

bb.error("Start package mapping")
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
bb.error("Found package mapping") runtime_mapping_rename("PACKAGE_INSTALL", d)

when I'd fixed the underlying problem.

Cheers,

Richard

#7 lore raw
Quoted 53 lines · Richard Purdie
Quoted 23 lines · Gerard van den Bosch

Ok, I have tried the following with the Bernard release:

print "hello"
print bb.data.getVar('BB_WORKERCONTEXT', d, True)
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
print "hello2"
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)
The "hello" gets printed, and the variable outputs "None", the "hello2" doesn't get printed because the variable is None.

In the laverne release I use here it checks on something else namely:
if bb.data.getVar('__RUNQUEUE_DO_NOT_USE_EXTERNALLY', d, True) is not None:
I can't add print commands there because it gives ident errors, found that has something todo with spaces but couldn't get it working.

I tried searching some further, I see in this commit that the if is added, that is in the laverne release:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=4e0ee648b4c18b770aba11921370258f3e2aaeef

Then a few commits later it is changed to the BB_WORKERCONTEXT:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=e427f251a457f3015c4b1cdf1648c53a9acc646d

Thus I tried to figure out what sets the BB_WORKERCONTEXT, I found it in two files in bitbake namely cooker.py and runqueue.py. Eventually it leads to the loading of the configuration file and something set BB_WORKERCONTEXT then but I couldn't figure out what sets the variable.

Quoted 6 lines

I looked up the commits where it is added to bitbake:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/runqueue.py?id=1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/cooker.py?id=ca09a6f08cc29f79f9742058d737deaef9d6d5ef

But I couldn't figure out what the changes did and I did not come further than this. If I need to try something else out, let me know.

This code only triggers at rootfs generation time. I've discovered this broken in master at least. To test I did:

bitbake -b /path/to/some-image.bb -c rootfs

and then saw:

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Start package mapping
ERROR: Found package mapping
NOTE: Running task 10 of 10 (ID: 6, /media/build2/builds/rptest/meta/recipes-core/images/core-image-minimal.bb, do_rootfs)
NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Started
^C

with the following in image.bbclass:

bb.error("Start package mapping")
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
bb.error("Found package mapping") runtime_mapping_rename("PACKAGE_INSTALL", d)

Quoted 6 lines

when I'd fixed the underlying problem.

Cheers,

Richard

If I understand correctly, you have fixed something to get it working? or does it work and am I doing something wrong? Because when I add the bb.error commands I am only seeing the "Start package mapping" with the suggested bitbake command.

Regards,
Gerard

#8 lore raw
Quoted 55 lines · Gerard van den Bosch
Quoted 53 lines · Richard Purdie
Quoted 23 lines · Gerard van den Bosch

Ok, I have tried the following with the Bernard release:

print "hello"
print bb.data.getVar('BB_WORKERCONTEXT', d, True)
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
print "hello2"
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)
The "hello" gets printed, and the variable outputs "None", the "hello2" doesn't get printed because the variable is None.

In the laverne release I use here it checks on something else namely:
if bb.data.getVar('__RUNQUEUE_DO_NOT_USE_EXTERNALLY', d, True) is not None:
I can't add print commands there because it gives ident errors, found that has something todo with spaces but couldn't get it working.

I tried searching some further, I see in this commit that the if is added, that is in the laverne release:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=4e0ee648b4c18b770aba11921370258f3e2aaeef

Then a few commits later it is changed to the BB_WORKERCONTEXT:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=e427f251a457f3015c4b1cdf1648c53a9acc646d

Thus I tried to figure out what sets the BB_WORKERCONTEXT, I found it in two files in bitbake namely cooker.py and runqueue.py. Eventually it leads to the loading of the configuration file and something set BB_WORKERCONTEXT then but I couldn't figure out what sets the variable.

Quoted 6 lines

I looked up the commits where it is added to bitbake:
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/runqueue.py?id=1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/cooker.py?id=ca09a6f08cc29f79f9742058d737deaef9d6d5ef

But I couldn't figure out what the changes did and I did not come further than this. If I need to try something else out, let me know.

This code only triggers at rootfs generation time. I've discovered this broken in master at least. To test I did:

bitbake -b /path/to/some-image.bb -c rootfs

and then saw:

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Start package mapping
ERROR: Found package mapping
NOTE: Running task 10 of 10 (ID: 6, /media/build2/builds/rptest/meta/recipes-core/images/core-image-minimal.bb, do_rootfs)
NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Started
^C

with the following in image.bbclass:

bb.error("Start package mapping")
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
bb.error("Found package mapping") runtime_mapping_rename("PACKAGE_INSTALL", d)

Quoted 7 lines
Quoted 6 lines

when I'd fixed the underlying problem.

Cheers,

Richard

If I understand correctly, you have fixed something to get it working?

Yes, I need to merge this:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/bb2&id=5b5f6e9d221c7cfcf1b4d9c4c76f38c03203ec49

Quoted 3 lines

or does it work and am I doing something wrong?
Because when I add the bb.error commands I am only seeing the "Start package mapping" with the suggested bitbake command.

Correct, it is broken until the above fix is applied :(

Cheers,

Richard

#9 lore raw
Quoted 87 lines · Richard Purdie
Quoted 5 lines · Gerard van den Bosch
Quoted 3 lines · Richard Purdie
Quoted 2 lines · Gerard van den Bosch

Ok, I have tried the following with the Bernard release:

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

print "hello"
print bb.data.getVar('BB_WORKERCONTEXT', d, True)
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
print "hello2" runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)
The "hello" gets printed, and the variable outputs "None", the

"hello2" doesn't get printed because the variable is None.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

In the laverne release I use here it checks on something else namely:
if bb.data.getVar('__RUNQUEUE_DO_NOT_USE_EXTERNALLY', d, True) is not

None:

Quoted 1 line
Quoted 1 line
Quoted 1 line

I can't add print commands there because it gives ident errors, found

that has something todo with spaces but couldn't get it working.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I tried searching some further, I see in this commit that the if is

added, that is in the laverne release:

Quoted 1 line
Quoted 1 line
Quoted 1 line

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=4e0ee648b4c18b770aba11921370258f3e2aaeef

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

Then a few commits later it is changed to the BB_WORKERCONTEXT:

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?id=e427f251a457f3015c4b1cdf1648c53a9acc646d

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Thus I tried to figure out what sets the BB_WORKERCONTEXT, I found it

in two files in bitbake namely cooker.py and runqueue.py.

Quoted 1 line
Quoted 1 line
Quoted 1 line

Eventually it leads to the loading of the configuration file and

something set BB_WORKERCONTEXT then but I couldn't figure out what sets the variable.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

I looked up the commits where it is added to bitbake:

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/runqueue.py?id=1f3e313fd5cc5ae8ea838bf8fcdedace3cb72584

Quoted 1 line
Quoted 1 line
Quoted 1 line

http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/bitbake/lib/bb/cooker.py?id=ca09a6f08cc29f79f9742058d737deaef9d6d5ef

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

But I couldn't figure out what the changes did and I did not come

further than this.

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

If I need to try something else out, let me know.

This code only triggers at rootfs generation time. I've discovered this broken in master at least. To test I did:

bitbake -b /path/to/some-image.bb -c rootfs

Quoted 8 lines
Quoted 8 lines

and then saw:

NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Start package mapping
ERROR: Found package mapping
NOTE: Running task 10 of 10 (ID: 6,

/media/build2/builds/rptest/meta/recipes-core/images/core-image-minimal.bb, do_rootfs)

Quoted 10 lines
Quoted 10 lines

NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Started ^C

with the following in image.bbclass:

bb.error("Start package mapping")
if bb.data.getVar('BB_WORKERCONTEXT', d, True) is not None:
bb.error("Found package mapping") runtime_mapping_rename("PACKAGE_INSTALL", d)

Quoted 7 lines
Quoted 6 lines

when I'd fixed the underlying problem.

Cheers,

Richard

If I understand correctly, you have fixed something to get it working?

Yes, I need to merge this:

http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/bb2&id=5b5f6e9d221c7cfcf1b4d9c4c76f38c03203ec49

Quoted 3 lines

or does it work and am I doing something wrong?
Because when I add the bb.error commands I am only seeing the "Start package mapping" with the suggested bitbake command.

Quoted 7 lines

Correct, it is broken until the above fix is applied :(

Cheers,

Richard

Richard, I have manually added your fix into my Bernard release and I am happy to inform you it works :)
My image builds without problems now, thank you very much for the fix.

Regards,
Gerard