All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: "Can't install krb5-dev-1.13.6-r0@ppc7400: no package provides krb5 = 1.13.6-r0"
Date: Mon, 20 Feb 2017 13:19:15 +0100	[thread overview]
Message-ID: <20170220121915.GC3266@jama> (raw)
In-Reply-To: <alpine.LFD.2.20.1702200709170.28884@localhost.localdomain>

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

On Mon, Feb 20, 2017 at 07:10:56AM -0500, Robert P. J. Day wrote:
> On Mon, 20 Feb 2017, Robert P. J. Day wrote:
> 
> >   ok, i hope this issue is not trivially simple. i'm building
> > core-image-minimal for qemuppc, and tossing in a bunch of other
> > recipes, everything builds until:
> >
> > ///// start /////
> > ERROR: core-image-minimal-1.0-r0 do_rootfs: Unable to install
> > packages. Command
> > '/home/rpjday/oe/builds/qemuppc_oe_small/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/smart
> > --log-level=info
> > --data-dir=/home/rpjday/oe/builds/qemuppc_oe_small/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/smart
> > install -y packagegroup-core-boot@qemuppc rpm@ppc7400
> > packagegroup-wrl-regular-recipes@all smartpm@ppc7400
> > run-postinsts@all' returned 1:
> > Loading cache...
> > Updating cache...
> > ######################################## [100%]
> >
> > Computing transaction...error: Can't install
> > krb5-dev-1.13.6-r0@ppc7400: no package provides krb5 = 1.13.6-r0
> >
> >
> > ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
> > ERROR: Logfile of failure stored in:
> > /home/rpjday/oe/builds/qemuppc_oe_small/tmp/work/qemuppc-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.22573
> > ERROR: Task
> > (/home/rpjday/oe/dist/layers/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs)
> > failed with exit code '1'
> > ///// end /////
> 
>   a simple solution was to add the line:
> 
> ALLOW_EMPTY_krb5 = "1"
> 
> to my local.conf. is that really the proper fix?

Removing the runtime dependency on krb5 from krb5-dev is usually
preferred, search ML it was discussed few times.

> 
> rday
> 
> -- 
> 
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2017-02-20 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 11:47 "Can't install krb5-dev-1.13.6-r0@ppc7400: no package provides krb5 = 1.13.6-r0" Robert P. J. Day
2017-02-20 12:10 ` Robert P. J. Day
2017-02-20 12:19   ` Martin Jansa [this message]
2017-02-20 12:35     ` Robert P. J. Day

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170220121915.GC3266@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.