All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] Packages broken URL
Date: Tue, 15 May 2012 20:09:32 +0100	[thread overview]
Message-ID: <1337108972.2711.51.camel@ted> (raw)
In-Reply-To: <CAF6bG8fj59QFg7QqZjOoGBCPwg-D=Ba-wLsGU38X8+n83tZUZQ@mail.gmail.com>

On Tue, 2012-05-15 at 16:13 +0300, Marko Lindqvist wrote:
> On 15 May 2012 16:06, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Tue, May 15, 2012 at 03:02:37PM +0200, Giuseppe Condorelli wrote:
> >> Hi All,
> >>
> >> there are a number of packages having a broken SRC_URI, for example git.
> >> Has someone met this issue?
> >> For sure we can correct those links adding a dedicated .bbappend file for
> >> each failing package but
> >> I think we could also update the main package fixing the errors.
> >
> > This should go to oe-core ML:
> > openembedded-core@lists.openembedded.org
> >
> > And yes it should be fixed in original recipe.
> 
>  Is there some way to disable automatic MIRROR usage that one could
> use to find out all source fetching problems?

PREMIRRORS = ""
MIRRORS = ""

Cheers,

Richard




  reply	other threads:[~2012-05-15 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 13:02 [oe-core] Packages broken URL Giuseppe Condorelli
2012-05-15 13:06 ` [oe] " Martin Jansa
2012-05-15 13:06   ` [oe-core] " Martin Jansa
2012-05-15 13:13   ` [oe] " Marko Lindqvist
2012-05-15 19:09     ` Richard Purdie [this message]
2012-05-15 13:49   ` [oe-core] " Apelete Seketeli
2012-05-15 13:17 ` Gary Thomas
2012-05-15 13:19   ` Giuseppe Condorelli
2012-05-15 13:30     ` Gary Thomas
2012-05-15 13:36       ` Giuseppe Condorelli
2012-05-15 13:45         ` [oe] " Paul Eggleton
2012-05-15 13:45           ` [oe-core] " 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=1337108972.2711.51.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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.