Please sync awesome 3.2-1 (universe) from Debian unstable (main)

Awesome 3.0rc1-1 has hit experimental in Debian:

http://packages.debian.org/experimental/awesome

I'll try later today building the package with my Intrepid install

I built awesome 3.0~rc6-1 from Debian experimental (along with its dependency, xcb-util >= 0.2.1). It seems to work fine.

Fixing this bug would additionally fix bug #267276.

how hard was it to build? can you explain how to do it?

awesome 3.0 final has been released. It relies on xcb-util 0.3.0.
Both can be built from Debian experimental. Pull down the 3 files from the source distribution, and run something like:

dpkg-source -x xxx.dsc
cd whatever_dir_just_got_made
debuild

(substituting the right .dsc filename and the right directory the source was extracted to from dpkg-source -x)

You can then install the .deb files when it successfully builds.

Note you will need to install the -dev packages from xcb-util before you attempt to build awesome 3.

I updated the description to require Awesome 3.0 for Jaunty. The 3.0 also needs xcb-util 0.3.0, which probably needs another ticket

We need to pick a stable version to submit the universe. Awesome's config file variables (which is what people use to customise their interface) change significantly over time. This is something critical for the package maintainer to look out for.

I think we should consider http://packages.debian.org/experimental/awesome per above.

3.2-rc3 is in debian unstable it would be nice to have it in Jaunty if it is not too late.

http://packages.debian.org/unstable/awesome
http://packages.debian.org/source/sid/xcb-util

It is not too late to get the new version into Jaunty. However, since we are past Feature Freeze, you will need to prepare a Freeze Exception request for it. Please read https://wiki.ubuntu.com/FreezeExceptionProcess for details.

It looks like it depends on xcb-utils => 0.3.3

I did the following to get thing running on Intrepid:

dget -u --build http://ftp.de.debian.org/debian/pool/main/x/xcb-util/xcb-util_0.3.3-2.dsc

sudo dpkg -i *.deb

dget -u --build http://ftp.de.debian.org/debian/pool/main/a/awesome/awesome_3.2~rc3-1.dsc

sudo dpkg -i awesome_3.2~rc3-1_i386.deb

This all seems to work.

On *Jaunty* I had to do a:

sudo apt-get install cdbs perf libtool check libdbus-1-dev

Also you may need to do:
sudo apt-get install xmlto asciidoc cmake luadoc libreadline-dev libev-dev liblua5.1 libimlib2-dev

dget -u --build https://launchpad.net/ubuntu/jaunty/+source/xcb-proto/1.3-1/+files/xcb-proto_1.3-1.dsc
sudo dpkg -i *.deb

dget -u --build https://launchpad.net/ubuntu/jaunty/+source/libxcb/1.1.93-0ubuntu3/+files/libxcb_1.1.93-0ubuntu3.dsc
sudo dpkg -i *.deb

dget -u --build http://ftp.de.debian.org/debian/pool/main/x/xcb-util/xcb-util_0.3.3-2.dsc
sudo dpkg -i *.deb

dget -u --build http://ftp.de.debian.org/debian/pool/main/a/awesome/awesome_3.2~rc4-1.dsc
sudo dpkg -i awesome_3.2~rc4-1_i386.deb

I got it running, make sure to do a

cp -r ~/.config/awesome ~/.config/awesome_old && rm -rf ~/.config/awesome && cp -r /etc/xdg/awesome ~/.config/

This, like other awesome feature releases, will require you to custom edit your current rc.lua. Also, the default one will be different.

Also, for more user configuration

cp -r /usr/share/awesome/themes/ ~/.config/awesome/

Then fire up your editor, open ~/.config/awesome/rc.lua and change

theme_path = /home/yourusername/.config/awesome/themes/default/theme

You can comment out the old default path with 2 hyphens. (--)

Proposal for Freeze Exception!'

Awesome 3.x packs many new features -and- is the current supported version. We are currently offered a version that is so old it may be trouble for even googlers to get help with it! The biggest reason is it may be hurtful to keep the old one in there, as being on the older version means documentation online is hopelessly incompatible.

The new features included in 3.x include more hooks (ways to configure) and support for extensions like Wicked (widgets), Beautiful (theming) functionality. It is more stable and popular than the 2.x series.

I believe that Jaunty should stay on the latest *stable* feature release, which is 3.2.

http://packages.debian.org/uk/sid/awesome In Debian Unstable, http://ftp.de.debian.org/debian/pool/main/a/awesome/awesome_3.2-1.dsc compiles and builds correctly. Furthermore, the ubuntu libraries in jaunty support this release.

I would appreciate seeing the Debian Sid package sync'd into the Universe. :D

Ah we may have an issue.

Instead of:
https://launchpad.net/ubuntu/jaunty/+source/xcb-util/0.2.1+git1-1/+files/xcb-util_0.2.1+git1-1.dsc

This library was used
http://ftp.de.debian.org/debian/pool/main/x/xcb-util/xcb-util_0.3.3-2.dsc

We need this xcb-util upgraded.

This following library is used by awesome and requires to be upgraded *along with* awesome.

Until we get the newer version of xcb-util in the repositories, we are unable to sync this version of awesome. Please test out xcb-util from Debian, and see if it is something that we can sync in Ubuntu. If it is, please file a FFe request. if and when xcb-util is synced, we can begin considering a FFe for awesome.

We need this libxcb sync'd from main!

This is bug #304384

Steve's comment in bug #304384 reflects my feeling about this one. Are there significant bugfixes or is it mainly a feature-based release? I think it's too late in the game to let this in, unless a good reason is found. Please work in bug #304384 to see if a good rationale exists first, but I think this should wait Karmic.

Due to the need to bring in xcb this is impossible for Jaunty. Awesome 3.2 is in Unstable now and will get automatically sync'ed for Karmic.