From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] [oe-core & yocto RC] Fix unfetchable zypp-related packages
Date: Tue, 20 Sep 2011 11:10:52 -0700 [thread overview]
Message-ID: <4E78D72C.2000709@linux.intel.com> (raw)
In-Reply-To: <cover.1316507540.git.anders@chargestorm.se>
On 09/20/2011 01:32 AM, Anders Darander wrote:
>
> openSUSE has moved several of it's projects from gitorious to github. Lately,
> these has become unfetchable from gitorius, thus the SRC_URI fixes are needed
> also for the upcoming yocto release.
>
> No other changes are included, SRCREV's are kept the same.
>
> The following changes since commit 81274f4488fbc4d68d150870735ec0181b60b451:
>
> freetype: disable bzip2 compressed font support (2011-09-19 13:14:03 +0100)
>
> are available in the git repository at:
> git://github.com/darander/oe-core opensuse-fixes
> https://github.com/darander/oe-core/tree/opensuse-fixes
>
> Anders Darander (3):
> libzypp: git repo moved to github
> sat-solver: git repo moved to github
> zypper: git repo moved to github
>
> meta/recipes-extended/libzypp/libzypp_git.bb | 2 +-
> meta/recipes-extended/sat-solver/sat-solver_git.bb | 2 +-
> meta/recipes-extended/zypper/zypper_git.bb | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
Do these need PR Bumps?
Sau!
next prev parent reply other threads:[~2011-09-20 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 8:32 [PATCH 0/3] [oe-core & yocto RC] Fix unfetchable zypp-related packages Anders Darander
2011-09-20 8:33 ` [PATCH 1/3] libzypp: git repo moved to github Anders Darander
2011-09-20 8:33 ` [PATCH 2/3] sat-solver: " Anders Darander
2011-09-20 8:33 ` [PATCH 3/3] zypper: " Anders Darander
2011-09-20 18:10 ` Saul Wold [this message]
2011-09-20 19:37 ` [PATCH 0/3] [oe-core & yocto RC] Fix unfetchable zypp-related packages Richard Purdie
2011-09-21 6:12 ` Anders Darander
2011-09-21 22:54 ` Saul Wold
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=4E78D72C.2000709@linux.intel.com \
--to=sgw@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox