Bug 164429 – x11-wm/wmii-20070116 snapshot fixes showstopper bugs

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Armando Di Cianno 2007-01-29 16:52:26 UTC]

From http://suckless.org/pipermail/wmii/2007-January/003105.html

Hello everyone!

I packed together a snapshot of the development version.

	http://suckless.org/snaps/wmii-20070116.tar.gz

It fixes two critical bugs (showstoppers) when trying to tag a frame
with more than one tag or with weird tag names. I highly recommend to
use this snapshot instead of the release version. Also, it contains
some additional events that are generated when a new column is made or
a client is destroyed.

Greetings
Denis

Reproducible: Always




wmii 3.5.1 had a number of bugs for me, this solves a couple of them.

Ebuild in coming next.

[Comment 1 Armando Di Cianno 2007-01-29 16:53:14 UTC]

Created attachment 108504 [details]
wmii-3.5.1.20070116 ebuild

wmii-3.5.1.20070116 ebuild

Pretty much only the URI changed.

[Comment 2 David Shakaryan (RETIRED) 2007-01-30 05:03:15 UTC]

Thanks for the bug report, Armando. I am a bit busy right now, so I'll try to test and commit it tomorrow. :)

[Comment 3 David Shakaryan (RETIRED) 2007-01-30 07:14:14 UTC]

Updated as promised, albeit a bit sooner. Hopefully everything went smooth.

[Comment 4 Roland Kammerer 2007-01-30 10:52:13 UTC]

Hi!

I have created a wmii-20070116-r1.ebuild which includes the "wmii-3.5-current-WMState.diff" patch. This patch makes it possible to rearrange tabs in mozilla firefox.

the original announcement and the patch can be found here:

http://groups.google.at/group/wmii/browse_thread/thread/71c5f3f010ca66ca

ebuild coming next

[Comment 5 Roland Kammerer 2007-01-30 10:54:39 UTC]

Created attachment 108605 [details]
wmii-3.5.1.20070116-r1.ebuild

[Comment 6 Roland Kammerer 2007-01-30 10:55:51 UTC]

Created attachment 108607 [details, diff]
files/wmii-3.5-current-WMState.diff

[Comment 7 Armando Di Cianno 2007-01-30 18:23:16 UTC]

omp -- just a suggestion but, wouldn't the snapshot be better named "wmii-3.5.1.20070116" as 20070116 > 3.5.2, but 3.5.1.20070116 would be less than 3.5.2?

[Comment 8 David Shakaryan (RETIRED) 2007-01-30 22:35:27 UTC]

(In reply to comment #7)
> omp -- just a suggestion but, wouldn't the snapshot be better named
> "wmii-3.5.1.20070116" as 20070116 > 3.5.2, but 3.5.1.20070116 would be less
> than 3.5.2?

It shouldn't really matter as I will be removing 20070116 when the next real version is released, since using 20070116 will be pointless then.

[Comment 9 David Shakaryan (RETIRED) 2007-01-30 23:09:30 UTC]

A 20070116-r1 with the patch has been added. Danke for the patch, Roland. :)

[Comment 10 Torsten Veller (RETIRED) 2007-01-31 06:23:51 UTC]

(In reply to comment #8)
> (In reply to comment #7)
> > omp -- just a suggestion but, wouldn't the snapshot be better named
> > "wmii-3.5.1.20070116" as 20070116 > 3.5.2, but 3.5.1.20070116 would be less
> > than 3.5.2?
> 
> It shouldn't really matter as I will be removing 20070116 when the next real
> version is released, since using 20070116 will be pointless then.

It still looks like a downgrade to the user. And of course it should be avoided. Well, if you downgrade now or later is likely a matter of taste. The version number was wrong in the beginning.

[Comment 11 David Shakaryan (RETIRED) 2007-01-31 08:08:08 UTC]

(In reply to comment #10)
> It still looks like a downgrade to the user. And of course it should be
> avoided. Well, if you downgrade now or later is likely a matter of taste. The
> version number was wrong in the beginning.

Hrm, but 3.5.1.20070116 is not right either as a 3.5.1.x might be released in the future. Using something along the lines of _alpha can also result in a similar problem as I do not know what version will be released next. _p again is prone to the same type of thing happening. I know these are less likely to result in a downgrade in the future, but that's beyond the point now that it is too late. What would you personally recommend is used in a scenario similar to this one?

[Comment 12 Torsten Veller (RETIRED) 2007-01-31 16:11:35 UTC]

(In reply to comment #11)
> Hrm, but 3.5.1.20070116 is not right either as a 3.5.1.x might be released in
> the future.

Yeah, that's exactly the problem with suckless stuff.
http://suckless.org/wmii/index.php?page=versioning
(Whatever $progress will be.)

> Using something along the lines of _alpha can also result in a
> similar problem as I do not know what version will be released next. _p again
> is prone to the same type of thing happening. I know these are less likely to
> result in a downgrade in the future, but that's beyond the point now that it is
> too late. What would you personally recommend is used in a scenario similar to
> this one?

I'd use _p# until they start using it too.
Well, it just sucks when a release is broken and one must highly recommend to use a snapshot.
(See also <https://bugs.gentoo.org/show_bug.cgi?id=157822#c2> for a rc that has some nasty bugs and one should use the hg repo.)


# snapshots: PV=3.5.1_p20070116 -- releases: PV=3.5.11
MY_PV="${PV##*_p}"
if [[ "${PV}" == "${MY_PV}" ]] ; then
        SRC_URI="http://suckless.org/download/${P}.tar.gz"
else
        SRC_URI="http://suckless.org/snaps/wmii-${MY_PV}.tar.gz"
fi
S="${WORKDIR}/${PN}-${MY_PV}