FS#14314 - rebuild awesome

Attached to Project: Community Packages
Opened by Alexandre Bique (babali) - Friday, 17 April 2009, 08:08 GMT
Last edited by Ronald van Haren (pressh) - Monday, 20 April 2009, 13:47 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

the new libxcb broke binary compatibility, so we have to rebuild awesome.
This task depends upon

Closed by  Ronald van Haren (pressh)
Monday, 20 April 2009, 13:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  should be fixed by 3.2.1b which actually is todays git version
Comment by Andrea Scarpino (BaSh) - Friday, 17 April 2009, 09:36 GMT
  • Field changed: Attached to Project (Arch Linux → Community Packages)
  • Field changed: Severity (High → Medium)
  • Task assigned to Ronald van Haren (pressh)
moved to Community project

anyway, I think this is already solved because awesome 3.2.1-1 is in community.
what version are you using?
Comment by Ronald van Haren (pressh) - Friday, 17 April 2009, 09:57 GMT
what new libxcb package? Latest libxcb upgrade was back in february?
Closing, any rebuild needed would have been fixed by the 3.2.1-1 package.
Comment by Ronald van Haren (pressh) - Sunday, 19 April 2009, 20:05 GMT
re-opening. Seems it was xcb-utils you were talking about. Rebuilding does not help btw, we should wait until upstream provides a fix
Comment by Vincent (vinvin) - Monday, 20 April 2009, 10:17 GMT
I think a medium severity is quite underestimated since it prevents awesome from being launched/used.
See http://bbs.archlinux.org/viewtopic.php?pid=537560
xcb-utils has to be downgraded to run awesome.

Loading...