All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: The tzdata package and a bug with tzdata-dbg
Date: Wed, 19 Mar 2008 11:57:05 +0100	[thread overview]
Message-ID: <frqri1$9l5$1@ger.gmane.org> (raw)
In-Reply-To: <200803191143.05167.zecke@selfish.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Holger Freyther schreef:
| On Tuesday 18 March 2008 23:32:18 Koen Kooi wrote:
| Hey Koen,
| thanks for the fast answer
|
|
|> Yes: Change RPROVIDES = "foo" to RPROVIDES_<package> and bump PR.
| Yes, this part is obvious. Now to the hard part tzdata-dbg has no
content, now
| that the RPROVIDES are different the tzdata-dbg package will be gone.

It won't, unless you removed this from bitbake.conf:

ALLOW_EMPTY_${PN}-dbg = "1"

| The
| tricky question is:
|
| 	ipkg update
| 	ipkg upgrade

opkg ;)

|
|
| tzdata-dbg should be gone, tzdata should be installed. How to achieve
this? My
| attempt was to have an empty tzdata-dbg package that is not providing
tzdata
| anymore, so on update ipkg should try to install tzdata again....

That should work with opkg. But in your case (OM), bump PR on eds-dbus
to make sure tzdata gets pulled in.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH4PGBMkyGM64RGpERAgpUAJ9nDVIXVXSJnHr3iWJw4de8RrLVPwCgkAX1
scmEducy/7eUqpLJkCn7Zdo=
=Xw9a
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-03-19 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 22:11 The tzdata package and a bug with tzdata-dbg Holger Freyther
2008-03-18 22:32 ` Koen Kooi
2008-03-19 10:43   ` Holger Freyther
2008-03-19 10:57     ` Koen Kooi [this message]
2008-03-19 11:48       ` Andrea Adami
2008-03-19 12:22         ` Koen Kooi
2008-03-19 15:10       ` Holger Freyther

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='frqri1$9l5$1@ger.gmane.org' \
    --to=koen@dominion.kabel.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.