All of lore.kernel.org
 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>
Subject: Re: [Patch] Update dpkg to one available
Date: Fri, 04 May 2012 09:06:55 -0700	[thread overview]
Message-ID: <4FA3FE9F.8050903@linux.intel.com> (raw)
In-Reply-To: <CAF6bG8ekrGh8V3dbkarox=d3sDWvioRxEKUCYXMfK529+CU+mw@mail.gmail.com>

On 05/04/2012 04:29 AM, Marko Lindqvist wrote:
>   I'm trying to make my first openembedded-core build. That failed due
> to dpkg-1.15.8.5 being not available for download any more.
>
This should be still available on our MIRROR.

>   Attached patch allowed me to get past that point (updating dpkg
> recipe to use latest (1.16.3) dpkg), but as I'm just learning my way
> around, this has not been subject to any real testing.
>
>   - Changes equivalent to dpkg-deb-avoid-fflush.patch seem now to be in
> upstream (probably this exact patch applied)
>   - I just adjusted perllibdir.patch, but I'm not sure if it's needed
> at all any more. It was used to remove unconditional PERL_LIBDIR
> assignment, but now the assignment is conditional in upstream anyway
>

Thanks for creating this update, we would like to take this, but if you
could you please re-format this and send a proper patch to the list, 
best to use either the "git format-patch" with "git send-email or the 
scripts create-pull-request/send-pull-request, also review the commit 
message guidelines at

http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

Thanks for the patch!

>
>   - ML
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



      reply	other threads:[~2012-05-04 16:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 11:29 [Patch] Update dpkg to one available Marko Lindqvist
2012-05-04 16:06 ` 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=4FA3FE9F.8050903@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 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.