M3 Package Update List

M3 Package Update List

[Saul Wold]

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


Folks,

Please find attached the list of M3 Recipe Updates, our goal for 1.0 M3 
release is to complete the update process we started in 0.9 and 1.0 M2. 
There are about 150 recipes in this list, some people may have more and 
if there is a need to request help, please let me know.  If you plan on 
helping, please let the current owner know that you will be updating a 
recipe.

Unless I hear otherwise, I will work to update the "None" maintained 
list, but I believe some of these are owned by people and the distro 
tracking information needs to be updated.

Thanks again to the team for the hard work during 0.9 and M2, we will 
always have updates to do, but they will get easier with our gained 
experience and expertise.

Happy Holidays and Happy New Year to all.

-- 
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System


[-- Attachment #2: M3_Updates.ods --]
[-- Type: application/vnd.oasis.opendocument.spreadsheet, Size: 110314 bytes --]

Re: [yocto] M3 Package Update List

[Kamble, Nitin A]

Saul,
   The python newer version detected by the tool is not correct. The latest stable is 2.7.1

Thanks,
Nitin

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Saul Wold
> Sent: Saturday, December 25, 2010 10:27 PM
> To: Yocto Project Discussion; poky@yoctoproject.org
> Subject: [yocto] M3 Package Update List
> 
> 
> Folks,
> 
> Please find attached the list of M3 Recipe Updates, our goal for 1.0 M3
> release is to complete the update process we started in 0.9 and 1.0 M2.
> There are about 150 recipes in this list, some people may have more and
> if there is a need to request help, please let me know.  If you plan on
> helping, please let the current owner know that you will be updating a
> recipe.
> 
> Unless I hear otherwise, I will work to update the "None" maintained
> list, but I believe some of these are owned by people and the distro
> tracking information needs to be updated.
> 
> Thanks again to the team for the hard work during 0.9 and M2, we will
> always have updates to do, but they will get easier with our gained
> experience and expertise.
> 
> Happy Holidays and Happy New Year to all.
> 
> --
>      Sau!
> 
> Saul Wold
> Yocto Component Wrangler @ Intel
> Yocto Project / Poky Build System

Re: M3 Package Update List

[Kamble, Nitin A]

Saul,
   The python newer version detected by the tool is not correct. The latest stable is 2.7.1

Thanks,
Nitin

> -----Original Message-----
> From: yocto-bounces@yoctoproject.org [mailto:yocto-
> bounces@yoctoproject.org] On Behalf Of Saul Wold
> Sent: Saturday, December 25, 2010 10:27 PM
> To: Yocto Project Discussion; poky@yoctoproject.org
> Subject: [yocto] M3 Package Update List
> 
> 
> Folks,
> 
> Please find attached the list of M3 Recipe Updates, our goal for 1.0 M3
> release is to complete the update process we started in 0.9 and 1.0 M2.
> There are about 150 recipes in this list, some people may have more and
> if there is a need to request help, please let me know.  If you plan on
> helping, please let the current owner know that you will be updating a
> recipe.
> 
> Unless I hear otherwise, I will work to update the "None" maintained
> list, but I believe some of these are owned by people and the distro
> tracking information needs to be updated.
> 
> Thanks again to the team for the hard work during 0.9 and M2, we will
> always have updates to do, but they will get easier with our gained
> experience and expertise.
> 
> Happy Holidays and Happy New Year to all.
> 
> --
>      Sau!
> 
> Saul Wold
> Yocto Component Wrangler @ Intel
> Yocto Project / Poky Build System

Re: [yocto] M3 Package Update List

[Xu, Dongxiao]

Hi Saul,

Here is an update for recipes in the list under my name.

I upgraded most of the recipes except:

1) upstream check error, actually they are up to date.
Speex, net-tools, libid3tag, libgsmd

2) git development tree:
Mtd-utils

3) dependency on other recipes:
Clutter-gst (depend on latest version of clutter).

Thanks,
Dongxiao

Saul Wold wrote:
> Folks,
> 
> Please find attached the list of M3 Recipe Updates, our goal for 1.0
> M3 release is to complete the update process we started in 0.9 and
> 1.0 M2.  
> There are about 150 recipes in this list, some people may have more
> and if there is a need to request help, please let me know.  If you
> plan on helping, please let the current owner know that you will be
> updating a recipe.   
> 
> Unless I hear otherwise, I will work to update the "None" maintained
> list, but I believe some of these are owned by people and the distro
> tracking information needs to be updated.  
> 
> Thanks again to the team for the hard work during 0.9 and M2, we will
> always have updates to do, but they will get easier with our gained
> experience and expertise.  
> 
> Happy Holidays and Happy New Year to all.

Re: M3 Package Update List

[Xu, Dongxiao]

Hi Saul,

Here is an update for recipes in the list under my name.

I upgraded most of the recipes except:

1) upstream check error, actually they are up to date.
Speex, net-tools, libid3tag, libgsmd

2) git development tree:
Mtd-utils

3) dependency on other recipes:
Clutter-gst (depend on latest version of clutter).

Thanks,
Dongxiao

Saul Wold wrote:
> Folks,
> 
> Please find attached the list of M3 Recipe Updates, our goal for 1.0
> M3 release is to complete the update process we started in 0.9 and
> 1.0 M2.  
> There are about 150 recipes in this list, some people may have more
> and if there is a need to request help, please let me know.  If you
> plan on helping, please let the current owner know that you will be
> updating a recipe.   
> 
> Unless I hear otherwise, I will work to update the "None" maintained
> list, but I believe some of these are owned by people and the distro
> tracking information needs to be updated.  
> 
> Thanks again to the team for the hard work during 0.9 and M2, we will
> always have updates to do, but they will get easier with our gained
> experience and expertise.  
> 
> Happy Holidays and Happy New Year to all.

Re: [yocto] M3 Package Update List

[Cui, Dexuan]

Saul Wold wrote:
> Folks,
> 
> Please find attached the list of M3 Recipe Updates, our goal for 1.0
> M3 release is to complete the update process we started in 0.9 and
> 1.0 M2. There are about 150 recipes in this list, some people may
> have more and if there is a need to request help, please let me know.
> If you plan on helping, please let the current owner know that you
> will be updating a recipe.
> 
> Unless I hear otherwise, I will work to update the "None" maintained
> list, but I believe some of these are owned by people and the distro
> tracking information needs to be updated.
> 
> Thanks again to the team for the hard work during 0.9 and M2, we will
> always have updates to do, but they will get easier with our gained
> experience and expertise.
> 
> Happy Holidays and Happy New Year to all.

Hi Saul,
Here is the update for recipes in the list with me as the owner:

There are 18 recipes in total: 
1) I have upgraded 14 ones:
renderproto
inputproto
libdmx
lttng-viewer
liburcu
libxxf86misc
compositeproto
resourceproto
xproto
gnome-doc-utils
scrnsaverproto
lttng-ust
librsvg
pixman: upgraded from 0.20.0 to 0.21.2 and later downgraded to 0.20.2 since 0.21.x is development release.

2) I decided to not upgrade these 2 ones and upgraded RECIPE_NO_UPDATE_REASON:
libunique: Do not upgrade to version: 2.91.4 because it requires gtk+ >= 2.90.0 and the stable version of gtk+ used by poky is 2.2x.x
liberation-fonts:  Do not upgrade to version: 1.06.0.20100721 because before doing that, we need adding new native packages like libungif_4.1.3, libspiro and fontforge first

3) These 2 ones doesn't need upgrade at present:
lttng-control: acutally not newer release is available. The script detecting new release thought 0.88-09242010 are different from 0.88.  Mei Lei has fixed that.
tcf-agent: as Lianhao said, the upstream is re-orging the code, so we can only wait for now. Previously the script detecting new release simply printed a useless svn number "998".

Thanks,
-- Dexuan

Re: M3 Package Update List

[Cui, Dexuan]

Saul Wold wrote:
> Folks,
> 
> Please find attached the list of M3 Recipe Updates, our goal for 1.0
> M3 release is to complete the update process we started in 0.9 and
> 1.0 M2. There are about 150 recipes in this list, some people may
> have more and if there is a need to request help, please let me know.
> If you plan on helping, please let the current owner know that you
> will be updating a recipe.
> 
> Unless I hear otherwise, I will work to update the "None" maintained
> list, but I believe some of these are owned by people and the distro
> tracking information needs to be updated.
> 
> Thanks again to the team for the hard work during 0.9 and M2, we will
> always have updates to do, but they will get easier with our gained
> experience and expertise.
> 
> Happy Holidays and Happy New Year to all.

Hi Saul,
Here is the update for recipes in the list with me as the owner:

There are 18 recipes in total: 
1) I have upgraded 14 ones:
renderproto
inputproto
libdmx
lttng-viewer
liburcu
libxxf86misc
compositeproto
resourceproto
xproto
gnome-doc-utils
scrnsaverproto
lttng-ust
librsvg
pixman: upgraded from 0.20.0 to 0.21.2 and later downgraded to 0.20.2 since 0.21.x is development release.

2) I decided to not upgrade these 2 ones and upgraded RECIPE_NO_UPDATE_REASON:
libunique: Do not upgrade to version: 2.91.4 because it requires gtk+ >= 2.90.0 and the stable version of gtk+ used by poky is 2.2x.x
liberation-fonts:  Do not upgrade to version: 1.06.0.20100721 because before doing that, we need adding new native packages like libungif_4.1.3, libspiro and fontforge first

3) These 2 ones doesn't need upgrade at present:
lttng-control: acutally not newer release is available. The script detecting new release thought 0.88-09242010 are different from 0.88.  Mei Lei has fixed that.
tcf-agent: as Lianhao said, the upstream is re-orging the code, so we can only wait for now. Previously the script detecting new release simply printed a useless svn number "998".

Thanks,
-- Dexuan