You are not logged in.
The maintainers had previously included experimental xcb support in cairo and as of the latest version (1.10.0) it has been removed. Some of us (awesome users for the most part) depended on the xcb support and had no expectation that it would suddenly be removed.
It would have been nice to have a heads up that a package upgrade was going to have a fundamental change from the previous version.
When a maintainer by default includes an experimental component of a package then what happened (bugs) should be expected. It's experimental... not guaranteed to work perfectly at all times. So if there was worry that it would ever cause issues, why was it ever included by default in the first place?
Kick out the jams! -- AUR
Offline
There was a heads up. It was announced on arch-dev-public and sat in [testing] for a month.
It was included in the first place as a long time ago it looked like that was the way of the future. Things change...
Offline
To reiterate, please subscribe to [arch-dev-public]. Can't expect heads-up from anyone if you're not subscribed to the proper mechanism. I knew about this issue (substantial thread in the ML) even though I have no clue what xcb is and about awesome in general.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
You have to install AUR cairo-xcb, which will replace cairo.
Now the problem is: is it "legal" for a community package like awesome to depend on a AUR package ? Or has cairo-xcb to be made available in community.
Offline
I have reported the issue on the bugtracker: https://bugs.archlinux.org/task/20996
Offline
removed awesome from community, so get it from AUR from now on.
Offline
There was a heads up. It was announced on arch-dev-public and sat in [testing] for a month.
I thought the ethos was to "read the news before upgrading", not "read every thread in the ML before upgrading"? Just want to avoid traing wrecks thats all.
Offline
Allan wrote:There was a heads up. It was announced on arch-dev-public and sat in [testing] for a month.
I thought the ethos was to "read the news before upgrading", not "read every thread in the ML before upgrading"? Just want to avoid traing wrecks thats all.
Think of [arch-dev-public] as a slightly more verbose form of news. Its not really that high-traffic, basically announcements that you can filter out based on whether you actually use any of the packages mentioned.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Think of [arch-dev-public] as a slightly more verbose form of news. Its not really that high-traffic, basically announcements that you can filter out based on whether you actually use any of the packages mentioned.
Excellent (subscribed). Also now that awesome is kicked from community the dependencies all make sense.
It was included in the first place as a long time ago it looked like that was the way of the future. Things change...
What a shame... perhaps it will make a comeback.
Thanks, all.
Kick out the jams! -- AUR
Offline
There is a chance of XCB support coming back in Cairo (the underlaying reason to "ban" awesome among other problems, like i3lock not supporting images). Please add your vote to this feature request:
Offline
There is a chance of XCB support coming back in Cairo
https://bugs.archlinux.org/task/20960?project=1
I guess the chances of that happening any time soon are pretty slim
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
You can use archlinux.fr repo which provides both cairo-xcb and awesome package by adding this to your pacman.conf
[archlinuxfr]
Server = http://repo.archlinux.fr/i686
Offline