xmonad update in testing

[Jens-Ulrik Petersen]

If you use Fedora's xmonad package then please help to test
the latest update for F16 and F17 which is now in testing.

It should fix issues with broken shared libs when upgrading, e.g.:
- xmonad 0.9.2 -> 0.10 dyn shared lib bump (F16)
- F16 -> F17 libgmp soname bump

https://admin.fedoraproject.org/updates/FEDORA-2012-8438/xmonad-0.10-9.fc17
https://admin.fedoraproject.org/updates/FEDORA-2012-8484/xmonad-0.10-3.5....

Basically I just added a check to xmonad-start and if there are shared libs "not
found"
and then it forces a recompile of one's xmonad user binary.

It seems to work for me anyway but more testing would be appreciated.
It would be nice if the xmonad update for F17 would be available
when F17 is released tomorrow, since the gmp bump means
all F16 binaries will break on upgrade.

Thanks, Jens

[Michel Alexandre Salim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jens,

On 05/28/2012 10:49 AM, Jens Petersen wrote:
>  If you use Fedora's xmonad package then please help to test the 
>  latest update for F16 and F17 which is now in testing.
>  
>  It should fix issues with broken shared libs when upgrading, e.g.:
>   - xmonad 0.9.2 -> 0.10 dyn shared lib bump (F16) - F16 -> F17 
>  libgmp soname bump
>   
Is there a way for testing if I'm already on the F-17 branch -- would
installing the version not in updates-testing and then upgrading be
sufficient, or does one need to start from F-16?

Thanks,

- -- 
Michel Alexandre Salim
Fedora Project Contributor: http://fedoraproject.org/

Email:  salimma(a)fedoraproject.org  | GPG key ID: A36A937A
Jabber: hircus(a)jabber.ccc.de       | IRC: hircus(a)irc.freenode.net

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPwxCwAAoJEEr1VKujapN6soEH/RbUw61L85eUFLmat3hc9SVi
> fGAo9HX+uRyMdFP8gORupHRktH1PoKxbbnbwhcYoucIhckWSv2wa16WkWNmJm5ze
> ccXl/Ei9fpGJmUUcYGZ/DQ37V71PN8e38/yv82kQcY3/lM7PNRuTnWNNiBsChttm
> jj+Y5JZR9Y6PibMQvwhJsWueEWKqjOgYlBEH0iaKtJwn2lho+P8+19GzFag3Y24Z
> 1m1qz2rGvQmLpz9bvj1JdU7gLe+iXF2NR9Ros9t5siIEgqGFcaRqxrF0pqC1MGGM
> JU0GPCo9IZlyZCRbpcvdXHA2kB6GxReRopTw2y5Wcv+JYn0+Q4k9LTHXNApCgLE=
> =9alx
> -----END PGP SIGNATURE-----

[Jens-Ulrik Petersen]

Hi Michel, thanks for your mail.

>  > It should fix issues with broken shared libs when upgrading,
> e.g.:
>  >  - xmonad 0.9.2 -> 0.10 dyn shared lib bump (F16); - F16 -> F17
>  > libgmp soname bump
>  > 
>  Is there a way for testing if I'm already on the F-17 branch -- would
>  installing the version not in updates-testing and then upgrading be
>  sufficient, or does one need to start from F-16? 
Ah yes good question.  Basically not - if you're already using F17
or installed F17 instead of upgrading then it is hard to reproduce.
I guess at least you can check that the new xmonad-start still
works for you.

I suppose I could upload example xmonad-$(arch)-linux files to
my people a/c or if you have an F16 still around it should be
easy to make one yourself.

Also I only tested x86_64 so far.  Can someone tell me if
i686 binary is called ~/.xmonad/xmonad-i686-linux or xmonad-i386-linux?
If it is the latter I think I might need to respin the updates.

Jens

[Michel Alexandre Salim]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jens,

On 05/28/2012 01:24 PM, Jens Petersen wrote:
>  Hi Michel, thanks for your mail.
>  
> >> It should fix issues with broken shared libs when upgrading,
> >> e.g.: - xmonad 0.9.2 -> 0.10 dyn shared lib bump (F16); - F16
> >> -> F17 libgmp soname bump
> >> 
> > Is there a way for testing if I'm already on the F-17 branch --
> > would installing the version not in updates-testing and then
> > upgrading be sufficient, or does one need to start from F-16?
>  
>  Ah yes good question.  Basically not - if you're already using F17 
>  or installed F17 instead of upgrading then it is hard to
>  reproduce. I guess at least you can check that the new xmonad-start
>  still works for you.
>   
The new one works, yes. I'll leave a karma for the update.
>  
>  Also I only tested x86_64 so far.  Can someone tell me if i686
>  binary is called ~/.xmonad/xmonad-i686-linux or xmonad-i386-linux? 
>  If it is the latter I think I might need to respin the updates.
>   
I've also only tested x86_64 :/

Thanks,

- -- 
Michel Alexandre Salim
Fedora Project Contributor: http://fedoraproject.org/

Email:  salimma(a)fedoraproject.org  | GPG key ID: A36A937A
Jabber: hircus(a)jabber.ccc.de       | IRC: hircus(a)irc.freenode.net

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJPw1/qAAoJEEr1VKujapN64+QH/AgS8C5W71wimzBu6THFXhh5
> Nkx6xmqg4v1yLZDnaScPQUlo+ZbFtQqIaOVCeGYZBu/SJuBUF/G1u35cDS529imS
> /zrrEc9OJ6+ShLY2dXgt6tfcdN9MKuCNqZ7Z4uKoKUi2J7rPDOgpZM0n+mhQTCSd
> f5u7MmNXAO3WN0wHmh4pjTJYdkF2EkMrSpLgTvvsRsKEapKw9hLdiqvsSr6ANIfB
> m5q/DBqvrLNK1oiexjiE9CiQm1n6VGsTrhbkrRibyLVMpUo7df0p1ZDsYHXUHLFj
> kMgjSz+tV7BjBHODudPRVnsZ8ABJWY3JmVRD1pzkQSHQcBsAFF3HSO1YtsIk9pI=
> =bIAh
> -----END PGP SIGNATURE-----

[Jens-Ulrik Petersen]

>  The new one works, yes. I'll leave a karma for the update.
Thanks!

>  > Also I only tested x86_64 so far.  Can someone tell me if i686
>  > binary is called ~/.xmonad/xmonad-i686-linux or xmonad-i386-linux?
>  > If it is the latter I think I might need to respin the updates. 
Well I did a quick check yesterday: booted F17 i686 Live and installed xmonad-core
and tried to run xmonad and it complained about missing xmonad-i386-linux...
so I will respin the updates and use "uname -i" to set the platform arch for
recompiling of 32bit user binaries instead.


Jens