From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: something about gtk+-2.24.8.tar.bz2 that requires constant downloading?
Date: Wed, 06 Jun 2012 09:10:34 -0600 [thread overview]
Message-ID: <4FCF72EA.3030200@mlbassoc.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1206051100550.2774@oneiric>
On 2012-06-05 09:01, Robert P. J. Day wrote:
> On Tue, 5 Jun 2012, Wang, Shane wrote:
>
>> Robert P. J. Day wrote on 2012-06-05:
>
>>> at this point, has the problem been identified? or does this still
>>> require a bugzilla submission? it would appear that the issue
>>> involves any package with a "+" in the package name which, for now,
>>> appears to be just that gtk+ package. would any other special
>>> characters trigger this? that's the only package i've tripped over
>>> that caused this behaviour.
>>>
>>> rday
>>>
>>
>> Yes, it has been identified. If you can't submit a bug, I can do.
>> Yes, I believe other special characters will trigger that.
>>
>> Just because I am not familiar with all fetch code, I can fix it for
>> gtk+ now but I am not sure whether that fix will bring any
>> regression bugs. Give me more time.
>
> ok, i'll leave it in your capable hands and go find something else
> to nitpick.
Has someone filed a bug on this yet? It breaks all my builds now since
I always use BB_NO_NETWORK="1" :-(
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-06-06 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 22:02 something about gtk+-2.24.8.tar.bz2 that requires constant downloading? Robert P. J. Day
2012-06-04 8:39 ` Robert P. J. Day
2012-06-05 5:04 ` Wang, Shane
2012-06-05 6:56 ` Khem Raj
2012-06-05 7:37 ` Wang, Shane
2012-06-05 13:32 ` Robert P. J. Day
2012-06-05 14:50 ` Wang, Shane
2012-06-05 15:01 ` Robert P. J. Day
2012-06-06 15:10 ` Gary Thomas [this message]
2012-06-13 13:22 ` Paul Eggleton
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=4FCF72EA.3030200@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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.