cdrtools-native: update 3.01 -> 3.02

The following changes since commit d0d260b0b85790ceb136dd6b0445e8e33d038f5e:

u-boot/beaglebone: Select Beaglebone Black target specifically. (2016-12-17 09:57:37 +0000)

are available in the git repository at:

git://git.openembedded.org/openembedded-core-contrib dengke/cdrtools-native-update-to-3.02
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=dengke/cdrtools-native-update-to-3.02

Dengke Du (1):
cdrtools-native: update 3.01 -> 3.02

 .../{cdrtools-native_3.01.bb => cdrtools-native_3.02.bb}       | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta/recipes-devtools/cdrtools/{cdrtools-native_3.01.bb => cdrtools-native_3.02.bb} (69%)

2.7.4

3.01a31 -> 3.02a07

---
 .../{cdrtools-native_3.01.bb => cdrtools-native_3.02.bb}       | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
 rename meta/recipes-devtools/cdrtools/{cdrtools-native_3.01.bb => cdrtools-native_3.02.bb} (69%)

similarity index 69%
rename from meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
rename to meta/recipes-devtools/cdrtools/cdrtools-native_3.02.bb
index ff4d5ac..f8b9386 100644
@@ -7,17 +7,17 @@ SECTION = "console/utils"
 LICENSE = "GPLv2 & CDDL-1.0 & LGPLv2.1+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=32f68170be424c2cd64804337726b312"
 
-SRC_URI = "${SOURCEFORGE_MIRROR}/project/cdrtools/cdrtools-${REALPV}.tar.bz2"
+SRC_URI = "${SOURCEFORGE_MIRROR}/project/cdrtools/alpha/cdrtools-${PV}.tar.bz2"
 
-SRC_URI[md5sum] = "7d45c5b7e1f78d85d1583b361aee6e8b"
-SRC_URI[sha256sum] = "ed282eb6276c4154ce6a0b5dee0bdb81940d0cbbfc7d03f769c4735ef5f5860f"
+SRC_URI[md5sum] = "ea362a6a42d8aa0d5fc154d195f47926"
+SRC_URI[sha256sum] = "49c1a67fa7ad3d7c0b05d41d18cb6677b40d4811faba111f0c01145d3ef0491b"
 
 EXTRA_OEMAKE = "-e MAKEFLAGS="
 
 inherit native
 
-PV = "3.01a31+really3.01"
-REALPV = "3.01"
+PV = "3.02a07"
+REALPV = "3.02"
 
 S = "${WORKDIR}/${BPN}-${REALPV}"
 

2.7.4

As the aXX releases are alpha releases for testing, is there a good reason to switch to an alpha? In general we ship releases, not previews.

Ross

OK, thanks, I get it.

This is incorrect. We actually ship the final 3.01 version, and previously agreed to wait for the final 3.02. The recipe says 'a31' because we didn't want to make the version go back when going from alpha 3.01 to final 3.01. The upstream seems to make regular 3.02 pre-releases, so the final version should hopefully appear soon.

Alex