Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: openembedded-core@lists.openembedded.org,
	openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Paul Gortmaker : linux-firmware: update to main repo on kernel.org
Date: Wed, 4 Jul 2012 19:27:15 +0200	[thread overview]
Message-ID: <20120704172715.GH15100@jama.jama.net> (raw)
In-Reply-To: <20120628192018.GB5532@localhost.jama.net>

[-- Attachment #1: Type: text/plain, Size: 6154 bytes --]

On Thu, Jun 28, 2012 at 09:20:18PM +0200, Martin Jansa wrote:
> On Mon, Jun 25, 2012 at 03:33:28PM +0000, git@git.openembedded.org wrote:
> > Module: openembedded-core.git
> > Branch: master
> > Commit: b9d42ec94dfcbe92ce2a857045a0e3678c05c26c
> > URL:    http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=b9d42ec94dfcbe92ce2a857045a0e3678c05c26c
> > 
> > Author: Paul Gortmaker <paul.gortmaker@windriver.com>
> > Date:   Fri Jun 22 10:15:07 2012 -0400
> > 
> > linux-firmware: update to main repo on kernel.org
> > 
> > This is now the authoratative repository, taking updates.
> > The latest has a couple updated license files, vs. the previous
> > srcrev that was used.
> > 
> > Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> > 
> > ---
> > 
> >  .../linux-firmware/linux-firmware_git.bb           |   10 +++++-----
> >  1 files changed, 5 insertions(+), 5 deletions(-)
> > 
> > diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> > index 3675978..8aacce4 100644
> > --- a/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> > +++ b/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb
> > @@ -7,23 +7,23 @@ SECTION = "kernel"
> >  
> >  LICENSE = "Proprietary"
> >  
> > -LIC_FILES_CHKSUM = "file://LICENSE.radeon_rlc;md5=4c243f7854d2884b483abda991adef43 \
> > +LIC_FILES_CHKSUM = "file://LICENSE.radeon;md5=e56b405656593a0c97e478513051ea0e \
> >                      file://LICENSE.dib0700;md5=f7411825c8a555a1a3e5eab9ca773431 \
> >                      file://LICENCE.xc5000;md5=1e170c13175323c32c7f4d0998d53f66 \
> >                      file://LICENCE.ralink-firmware.txt;md5=ab2c269277c45476fb449673911a2dfd \
> >                      file://LICENCE.qla2xxx;md5=4005328a134054f0fa077bdc37aa64f2 \
> > -                    file://LICENCE.iwlwifi_firmware;md5=311cc823df5b1be4f00fbf0f17d96a6b \
> > +                    file://LICENCE.iwlwifi_firmware;md5=11545778abf78c43d7644d4f171ea1c7 \
> >                      file://LICENCE.i2400m;md5=14b901969e23c41881327c0d9e4b7d36 \
> >                      file://LICENCE.atheros_firmware;md5=30a14c7823beedac9fa39c64fdd01a13 \
> >                      file://LICENCE.agere;md5=af0133de6b4a9b2522defd5f188afd31 \
> >                      file://LICENCE.rtlwifi_firmware.txt;md5=00d06cfd3eddd5a2698948ead2ad54a5 \
> >                     "
> >  
> > -SRCREV = "15888a2eab052ac3d3f49334e4f6f05f347a516e"
> > +SRCREV = "e98750f0d68d0037ce5a186f7f863a9c13bf773a"
> >  PV = "0.0+git${SRCPV}"
> > -PR = "r1"
> > +PR = "r2"
> >  
> > -SRC_URI = "git://git.infradead.org/users/dwmw2/linux-firmware.git;protocol=git"
> > +SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git;protocol=git"
> 
> changing git URL (or even just branch) in recipe with SRCPV in PV resets LOCALCOUNT to zero..
> so breaks upgrade path.
> 
> Bump PE or PV to fix that!

Ping,

> NOTE: package linux-firmware-0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2: task do_package: Started
> ERROR: Package version for package linux-firmware-sd8686 went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-rtl8192cu went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-rtl8192ce went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-rtl8192su went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-wl12xx went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-dbg went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-staticdev went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-dev went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-doc went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware-locale went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> ERROR: Package version for package linux-firmware went backwards which would break package feeds from (0:0.0+git2+15888a2eab052ac3d3f49334e4f6f05f347a516e-r1 to 0:0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2)
> NOTE: package linux-firmware-0.0+git1+e98750f0d68d0037ce5a186f7f863a9c13bf773a-r2: task do_package: Succeeded
> 
> Cheers,
> 
> >  
> >  S = "${WORKDIR}/git"
> >  
> > 
> > 
> > _______________________________________________
> > Openembedded-commits mailing list
> > Openembedded-commits@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-commits
> 
> -- 
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-07-04 17:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120625153328.B76A81033A@opal>
2012-06-28 19:20 ` [oe-commits] Paul Gortmaker : linux-firmware: update to main repo on kernel.org Martin Jansa
2012-07-04 17:27   ` Martin Jansa [this message]
2012-07-04 17:33     ` [PATCH] linux-firware: bump PE because git SRC_URI was changed resulting in LOCALCOUNT reset Martin Jansa
2012-07-05 17:21       ` Saul Wold
2012-07-05 15:55     ` [oe-commits] Paul Gortmaker : linux-firmware: update to main repo on kernel.org Paul Gortmaker
2012-07-05 16:01       ` Martin Jansa

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=20120704172715.GH15100@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-commits@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.gortmaker@windriver.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