From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: python skills and bug 2412
Date: Tue, 27 Nov 2007 12:22:35 +0000 [thread overview]
Message-ID: <1196166155.6780.11.camel@localhost.localdomain> (raw)
In-Reply-To: <474AFA66.30509@gmx.net>
On Mon, 2007-11-26 at 17:55 +0100, Robert Schuster wrote:
> Hi
> Rodigo and me are suffering from bug 2412[0]. We talked a bit about the
> issue and I provided an idea on how to fix it. Unfortunately I lack the
> python experience to do it. I do not understand how the name conversion
> in debian.bbclass is actually done and where I could add code to replace
> slashes with hyphens.
>
> Can anyone who has a better understanding of this help us out?
>
> Regards
> Robert
>
> [0] - http://bugs.openembedded.org/show_bug.cgi?id=2412
I commented on the bug but I will repeat here for wider exposure.
"The real problem here is that virtual/libx11 should not be appearing in
the package manager namespace. RPROVIDES = "virtual/libx11" is plain
wrong and is the real bug."
I've discussed this on the mailing list in the past, virtual/* shouldn't
ever be ending up in the runtime namespaces :/.
Cheers,
Richard
next prev parent reply other threads:[~2007-11-27 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 16:55 python skills and bug 2412 Robert Schuster
2007-11-27 12:22 ` Richard Purdie [this message]
2007-11-27 13:43 ` Paul Sokolovsky
2007-11-27 14:03 ` Richard Purdie
2007-11-27 14:17 ` Paul Sokolovsky
2007-11-27 15:05 ` Richard Purdie
2007-11-27 15:19 ` Build-time vs run-time virtuals, was: " Paul Sokolovsky
2007-11-28 11:30 ` Richard Purdie
2007-11-27 19:53 ` Matt Hoosier
2007-11-28 11:28 ` Richard Purdie
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=1196166155.6780.11.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--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.