do_rootfs error due to package installation

do_rootfs error due to package installation

[John Schluechtermann]

[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]

I have a custom image that I am trying to pick up and get working that was setup and used by an individual no longer with the company.

The image creation is failing in the do_rootfs portion and appears to be due to a package not being installed in the image.  I have verified that the package is being created which it is.  I am not sure if I need to modify an IMAGE_INSTALL commend in a recipe or not since I do not understand how the first package (packagegroup-base-extended) is being included.

The error message that occurs is:

The following packages have unmet dependencies:
packagegroup-base-extended : Depends: packagegroup-base-nfc but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

So if I understanding this correctly it is placing the packagegroup-base-extended package in the image but it for some reason cannot do that with the packagegroup-base-nfc.  Is this an order issue or something else.  I do not know where to look at the moment so any guidance on that would be greatly appreciated.

Thanks,

-          John
The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you.

[-- Attachment #2: Type: text/html, Size: 3507 bytes --]

Re: do_rootfs error due to package installation

[John Schluechtermann]

[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]

Some additional information in regards to this.  In the troubleshooting of it I turned on the build history by adding the following to my local.conf,
          INHERIT += "buildhistory"
          BUILDHISTORY_COMMIT = "1"

With that added to the local.conf the image creation would complete successfully, it was also repeatable if I removed it I would then get the error message about the unmet dependencies, replacing it allowed the build to complete.  What do I not have setup correctly?


-          John


I have a custom image that I am trying to pick up and get working that was setup and used by an individual no longer with the company.

The image creation is failing in the do_rootfs portion and appears to be due to a package not being installed in the image.  I have verified that the package is being created which it is.  I am not sure if I need to modify an IMAGE_INSTALL commend in a recipe or not since I do not understand how the first package (packagegroup-base-extended) is being included.

The error message that occurs is:

The following packages have unmet dependencies:
packagegroup-base-extended : Depends: packagegroup-base-nfc but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

So if I understanding this correctly it is placing the packagegroup-base-extended package in the image but it for some reason cannot do that with the packagegroup-base-nfc.  Is this an order issue or something else.  I do not know where to look at the moment so any guidance on that would be greatly appreciated.

Thanks,

-          John
The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you.

[-- Attachment #2: Type: text/html, Size: 5424 bytes --]

Re: do_rootfs error due to package installation

[Khem Raj]

[-- Attachment #1.1: Type: text/plain, Size: 2824 bytes --]

These two seems unrelated. look under deploy/ipk folder and see if you have an ipk sounding with same name as missing package
it might be that its empty and deleted but the dependency remains

> On Jan 7, 2016, at 1:29 PM, John Schluechtermann <JSchluechtermann@FORCEAmerica.com> wrote:
> 
> Some additional information in regards to this.  In the troubleshooting of it I turned on the build history by adding the following to my local.conf,
>           INHERIT += “buildhistory”
>           BUILDHISTORY_COMMIT = “1”
> 
> With that added to the local.conf the image creation would complete successfully, it was also repeatable if I removed it I would then get the error message about the unmet dependencies, replacing it allowed the build to complete.  What do I not have setup correctly?
> 
> -          John
> 
> 
> I have a custom image that I am trying to pick up and get working that was setup and used by an individual no longer with the company.
> 
> The image creation is failing in the do_rootfs portion and appears to be due to a package not being installed in the image.  I have verified that the package is being created which it is.  I am not sure if I need to modify an IMAGE_INSTALL commend in a recipe or not since I do not understand how the first package (packagegroup-base-extended) is being included.
> 
> The error message that occurs is:
> 
> The following packages have unmet dependencies:
> packagegroup-base-extended : Depends: packagegroup-base-nfc but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> So if I understanding this correctly it is placing the packagegroup-base-extended package in the image but it for some reason cannot do that with the packagegroup-base-nfc.  Is this an order issue or something else.  I do not know where to look at the moment so any guidance on that would be greatly appreciated.
> 
> Thanks,
> -          John
> The information contained in this message and any attachment may be proprietary, confidential, and privileged or subject to the work product doctrine and thus protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to this message and deleting it and all copies and backups thereof. Thank you.
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto>

[-- Attachment #1.2: Type: text/html, Size: 10918 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]