Just to make it stupidly explicit so no one is caught by this unaware,
with this commit, the key used to sign packages for the 1.1 release has
changed.  All of the packages in the repo have been resigned with the new
key.  The old key cannot be used to validate packages for MeeGo 1.1
anymore.

This should all take place automatically behind the scenes.  However, keep
this in mind.

Ryan

On 10/19/10 8:57 AM, "Peter Zhu" <[email protected]> wrote:

>Hi Peter Zhu,
>The following change has been accepted. See the changelog below.
>
>Comments:
>    thank you
>
>Thanks,
>MeeGo Release Engineering Team
>
>[This message was auto-generated]
>---
>Request #8633:
>
>  submit:   MeeGo:1.1:Core:Testing/meego-release(r5) ->
>MeeGo:1.1:Core/meego-release
>
>
>Message:
>    * Mon Oct 18 2010 Ryan R Ware <[email protected]> - 1.0.99
>- Falling back to a single key until we understand signing issues with OBS
>* Sat Oct 16 2010 Anas Nashif <[email protected]> - 1.0.99
>- Fixed link to primary key
>* Fri Oct 15 2010 Ryan R Ware <[email protected]> - 1.0.99
>- Removed the generic OBS key (RPM-GPG-KEY-meego) and added
>the two 1.1 release keys (RPM-GPG-KEY-meego01 & RPM-GPG-KEY-meego02).
>
>State:   accepted     2010-10-19T08:57:02 peter
>Comment: thank you
>
>
>History: new          2010-10-19T05:22:25 peter
>_______________________________________________
>Meego-commits mailing list
>[email protected]
>http://lists.meego.com/listinfo/meego-commits

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to