Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dexuan Cui <dexuan.cui@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] patches to fix deb packaging: bug 1070
Date: Tue,  6 Sep 2011 21:08:34 +0800	[thread overview]
Message-ID: <cover.1315313790.git.dexuan.cui@intel.com> (raw)

The DEB packaging for core-image-sato-sdk(previously called poky-image-sdk) and
meta-toolchain-gmae(previously called meta-toolchain-sdk) has been broken for
quite a long period of time -- at least it was broken in Oct 2010 (I didn't try
to test older commits).

The patches try to improve the situation.

With the patches, core-image-sato-sdk for qemu{x86, x86-64, ppc, mips} can
build fine, but qemuarm still has a do_rootfs issue:
| The following packages have unmet dependencies:
|   task-base-extended: Depends: task-base but it is not going to be installed

And, meta-toolchain-gmae is still broken. The error is:
| + apt-get install task-sdk-host-nativesdk --force-yes --allow-unauthenticated
| Reading package lists...
| Building dependency tree...
| Reading state information...
| E: Couldn't find package task-sdk-host-nativesdk

I'm working on the left issues.

Does anybody know if OE has the similar issue or not?
Any comment/suggestions for the patch and left isseus are appreciated.

Thanks!

-- Dexuan

The following changes since commit 41b7c955cfdc7b4d5c667c8a8742237d5edaca4f:

  icu-3.6: fix building with big make -j (2011-09-05 20:38:50 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dcui/distro
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dcui/distro

Dexuan Cui (5):
  populate_sdk_deb.bbclass: add the missing parameter - for tar
  package_deb.bbclass: put the stderr into log.do_xxx-attemptonly.xxx
  dpkg, dpkg-native: fix DEPENDS, RDEPENDS and pkg_postinst_dpkg
  opkg: it should Rdepend on update-alternatives-cworth
  default-providers.inc: define update-alternatives and -native
    properly

 meta/classes/package_deb.bbclass               |    2 +-
 meta/classes/populate_sdk_deb.bbclass          |    2 +-
 meta/conf/distro/include/default-providers.inc |    5 ++---
 meta/recipes-devtools/dpkg/dpkg.inc            |   23 ++++++++++-------------
 meta/recipes-devtools/opkg/opkg_0.1.8.bb       |    4 ++--
 meta/recipes-devtools/opkg/opkg_svn.bb         |    4 ++--
 6 files changed, 18 insertions(+), 22 deletions(-)

-- 
1.7.6




             reply	other threads:[~2011-09-06 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 13:08 Dexuan Cui [this message]
2011-09-06 13:08 ` [PATCH 1/5] populate_sdk_deb.bbclass: add the missing parameter - for tar Dexuan Cui
2011-09-06 13:08 ` [PATCH 2/5] package_deb.bbclass: put the stderr into log.do_xxx-attemptonly.xxx Dexuan Cui
2011-09-06 13:08 ` [PATCH 3/5] dpkg, dpkg-native: fix DEPENDS, RDEPENDS and pkg_postinst_dpkg Dexuan Cui
2011-09-06 13:08 ` [PATCH 4/5] opkg: it should Rdepend on update-alternatives-cworth Dexuan Cui
2011-09-06 13:08 ` [PATCH 5/5] default-providers.inc: define update-alternatives and -native properly Dexuan Cui
2011-09-07  0:23 ` [PATCH 0/5] patches to fix deb packaging: bug 1070 Saul Wold
2011-09-07  4:06   ` Cui, Dexuan
2011-09-08  3:47 ` 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=cover.1315313790.git.dexuan.cui@intel.com \
    --to=dexuan.cui@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