Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH 1/1] classes/package_deb: create .gz index instead of .bz2
Date: Wed, 11 Apr 2012 08:16:26 -0700	[thread overview]
Message-ID: <4F85A04A.1010100@linux.intel.com> (raw)
In-Reply-To: <43ee4f8a379076a147644e6b933d3d0a0ab93361.1334098277.git.paul.eggleton@linux.intel.com>

On 04/10/2012 03:52 PM, Paul Eggleton wrote:
> apt is looking for Packages.gz files instead of the .bz2 files we are
> currently creating and failing when they cannot be found. It is not
> immediately obvious how to make the current version use the .bz2
> indexes; thus create .gz indexes for now which allows us to
> successfully create images.
>
> Tested on both a Fedora 14 and an Ubuntu 11.10 host machine.
>
> Fixes [YOCTO #1858].
>
> Signed-off-by: Paul Eggleton<paul.eggleton@linux.intel.com>
> ---
>   meta/classes/package_deb.bbclass |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/package_deb.bbclass b/meta/classes/package_deb.bbclass
> index 9880258..dc0f963 100644
> --- a/meta/classes/package_deb.bbclass
> +++ b/meta/classes/package_deb.bbclass
> @@ -83,7 +83,7 @@ package_update_index_deb () {
>   			continue;
>   		fi
>   		cd ${DEPLOY_DIR_DEB}/$arch
> -		dpkg-scanpackages . | bzip2>  Packages.bz2
> +		dpkg-scanpackages . | gzip>  Packages.gz
>   		echo "Label: $arch">  Release
>   	done
>   }

Merged into OE-Core

Thanks
	Sau!




      reply	other threads:[~2012-04-11 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 22:52 [PATCH 0/1] Fix deb rootfs generation Paul Eggleton
2012-04-10 22:52 ` [PATCH 1/1] classes/package_deb: create .gz index instead of .bz2 Paul Eggleton
2012-04-11 15:16   ` Saul Wold [this message]

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=4F85A04A.1010100@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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