From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] zlib: update SRC_URI to fix fetching
Date: Fri, 13 Jan 2017 13:54:04 +0000 [thread overview]
Message-ID: <1484315644.3828.3.camel@linux.intel.com> (raw)
In-Reply-To: <1b59a012-5943-d763-975f-764a6247121b@linux.intel.com>
> On Fri, 2017-01-13 at 15:00 +0200, Alexander Kanavin wrote:
> On 01/09/2017 02:56 PM, Alexander Kanavin wrote:
> > On 01/05/2017 06:34 PM, Joshua Lock wrote:
> > > Upstream have removed the file from zlib.net as a new version has
> > > been released, switch to fetching from the official sourceforge
> > > mirror.
> > >
> > > [YOCTO #10879]
> >
> > If a new version has been released, you should also update to that
> > version. Also, does upstream version check (-c checkpkg) still work
> > with
> > the new SRC_URI?
>
> Actually it doesn't, accordingly we have no way of knowing if zlib
> has a
> new version upstream. Please do check these things when you update
> SRC_URI.
Noted, thanks. Do we maintain a list of things we'd like people to
check, and how to do it, when making updates to recipes?
checkpkg isn't available by default (had to add distrodata to INHERITS)
and it took me a while to realise the results are written to a file I
have to check. If we expect people to run these checks before
submitting updates we'd best make it as easy as possible to know what
the checks are and how to run them.
The only reference I can find to checkpkg on the OE and YP wikis is
here:
https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_ensure_that_I_a
m_using_the_latest_upstream_version_of_the_package.3F
Joshua
next prev parent reply other threads:[~2017-01-13 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 16:34 [PATCH] zlib: update SRC_URI to fix fetching Joshua Lock
2017-01-09 12:56 ` Alexander Kanavin
2017-01-13 13:00 ` Alexander Kanavin
2017-01-13 13:54 ` Joshua Lock [this message]
[not found] ` <1484315514.3828.2.camel@intel.com>
2017-01-13 14:18 ` Alexander Kanavin
2017-01-13 15:36 ` Joshua Lock
2017-01-13 15:53 ` Alexander Kanavin
2017-02-08 14:23 ` Joshua Lock
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=1484315644.3828.3.camel@linux.intel.com \
--to=joshua.g.lock@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