Bug 638140 – x11-wm/awesome-4.2-r2 stable request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Rob 2017-11-19 14:53:26 UTC]

The entire awesome 3.x series is years old, and retired by upstream. Furthermore upstream would prefer that distributions cease providing 3.x. The project has gone through bug fixes since 4.0 and their 4.2 release is considered stable.

Therefore 4.2 should be moved to stable. Many more prominent bugs have already been fixed, and subsequent reports will most likely be rejected coming from versions older than 4.2.

Reproducible: Always

[Comment 1 Maxim Koltsov (RETIRED) 2018-03-14 21:24:13 UTC]

I'm going to fix remaining 4.x bugs and then proceed with stabilisation. I hope to get this done soon.

[Comment 2 Larry the Git Cow 2018-03-25 22:04:38 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0a5197761857d97984d472ac3df6f81a9d3d450d

commit 0a5197761857d97984d472ac3df6f81a9d3d450d
Author:     Maxim Koltsov <[e-mail]>
AuthorDate: 2018-03-25 22:02:54 +0000
Commit:     Maxim Koltsov <[e-mail]>
CommitDate: 2018-03-25 22:04:25 +0000

    x11-wm/awesome: several improvements in 4.x branch
    
    - Add luajit to RDEPEND and DEPEND
    - Fix documentation installation paths (bug 628024)
    - Add xvfb-based test suite
    - Re-add dropeed x86-fbsd keyword
    
    Bug: https://bugs.gentoo.org/638140
    Closes: https://bugs.gentoo.org/628024
    Package-Manager: Portage-2.3.24, Repoman-2.3.6

 x11-wm/awesome/awesome-4.2-r2.ebuild | 144 +++++++++++++++++++++++++++++++++++
 1 file changed, 144 insertions(+)}

[Comment 3 Maxim Koltsov (RETIRED) 2018-04-21 17:31:25 UTC]

Okay, let's do amd64 and x86 first. Please don't close the bug afterwards.

[Comment 4 Stabilization helper bot 2018-04-21 18:00:07 UTC]

An automated check of this bug failed - the following atoms are unknown:

dev-lua/luafilesystem
dev-lua/ldoc
dev-lua/luachek

Please verify the atom list.

[Comment 5 Stabilization helper bot 2018-04-21 19:00:06 UTC]

An automated check of this bug failed - the following atom is unknown:

dev-lua/luachek-0.20.0

Please verify the atom list.

[Comment 6 Stabilization helper bot 2018-04-21 20:00:55 UTC]

An automated check of this bug succeeded - the previous repoman errors are now resolved.

[Comment 7 Larry the Git Cow 2018-04-21 22:55:58 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=974f70814563e9d46c840296cb3d5b6f150521bc

commit 974f70814563e9d46c840296cb3d5b6f150521bc
Author:     Aaron Bauman <[e-mail]>
AuthorDate: 2018-04-21 22:54:48 +0000
Commit:     Aaron Bauman <[e-mail]>
CommitDate: 2018-04-21 22:54:48 +0000

    dev-lua/luacheck: amd64 stable wrt bug #638140
    
    Bug: https://bugs.gentoo.org/638140
    Package-Manager: Portage-2.3.31, Repoman-2.3.9

 dev-lua/luacheck/luacheck-0.20.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=842cedd0b9c8d99e97976e146fa55d59e72b8a2d

commit 842cedd0b9c8d99e97976e146fa55d59e72b8a2d
Author:     Aaron Bauman <[e-mail]>
AuthorDate: 2018-04-21 22:53:54 +0000
Commit:     Aaron Bauman <[e-mail]>
CommitDate: 2018-04-21 22:53:54 +0000

    x11-wm/awesome: amd64 stable wrt bug #638140
    
    Bug: https://bugs.gentoo.org/638140
    Package-Manager: Portage-2.3.31, Repoman-2.3.9

 x11-wm/awesome/awesome-4.2-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0a191545b7c7101aef10cbf4dd4407f1a84b3332

commit 0a191545b7c7101aef10cbf4dd4407f1a84b3332
Author:     Aaron Bauman <[e-mail]>
AuthorDate: 2018-04-21 22:51:08 +0000
Commit:     Aaron Bauman <[e-mail]>
CommitDate: 2018-04-21 22:51:08 +0000

    dev-lua/ldoc: amd64 stable wrt bug #638140
    
    Bug: https://bugs.gentoo.org/638140
    Package-Manager: Portage-2.3.31, Repoman-2.3.9

 dev-lua/ldoc/ldoc-1.4.6.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=04a81448c4439d7a22b5705aa6d9048ae45a759a

commit 04a81448c4439d7a22b5705aa6d9048ae45a759a
Author:     Aaron Bauman <[e-mail]>
AuthorDate: 2018-04-21 22:50:49 +0000
Commit:     Aaron Bauman <[e-mail]>
CommitDate: 2018-04-21 22:50:49 +0000

    dev-lua/luafilesystem: amd64 stable wrt bug #638140
    
    Bug: https://bugs.gentoo.org/638140
    Package-Manager: Portage-2.3.31, Repoman-2.3.9

 dev-lua/luafilesystem/luafilesystem-1.6.3.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)}

[Comment 8 Marek Szuba 2018-04-24 14:43:16 UTC]

I have just reverted stabilisation of x11-wm/awesome-4.2-r2 on amd64. To all arch testers: please refrain from stabilising >=x11-wm/awesome-4.0 for the time being. Awesome 4 is NOT backwards-compatible with 3.5 configuration files, meaning that everyone who has even got a copy of the stock rc.lua in ~/.config/awesome/ - let's not even mention customised - will end up with a broken WM after the upgrade. Please see here for more information on the API changes and to get an idea of how much work porting awesome3 configuration and libraries to awesome4 requires:

https://awesomewm.org/apidoc/documentation/89-NEWS.md.html#v4
https://awesomewm.org/apidoc/documentation/17-porting-tips.md.html#v4

This means that at the very least, maintainers of x11-wm/awesome should prepare a news item warning the users about an upcoming breaking change.

[Comment 9 Maxim Koltsov (RETIRED) 2018-04-24 17:07:21 UTC]

(In reply to Marek Szuba from comment #8)
> I have just reverted stabilisation of x11-wm/awesome-4.2-r2 on amd64. To all
> arch testers: please refrain from stabilising >=x11-wm/awesome-4.0 for the
> time being. Awesome 4 is NOT backwards-compatible with 3.5 configuration
> files, meaning that everyone who has even got a copy of the stock rc.lua in
> ~/.config/awesome/ - let's not even mention customised - will end up with a
> broken WM after the upgrade. Please see here for more information on the API
> changes and to get an idea of how much work porting awesome3 configuration
> and libraries to awesome4 requires:
> 
> https://awesomewm.org/apidoc/documentation/89-NEWS.md.html#v4
> https://awesomewm.org/apidoc/documentation/17-porting-tips.md.html#v4
> 
> This means that at the very least, maintainers of x11-wm/awesome should
> prepare a news item warning the users about an upcoming breaking change.

Please don't touch other people's packages. Awesome-4 has been around for almost 1.5 years now (released on 2016-12-25) and I'm pretty sure almost every one has already switched. Moreover, I _do_have_ a warning message in pkg_postinst, see https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-wm/awesome/awesome-4.2-r2.ebuild#n134
Did you check the ebuild before reverting?

[Comment 10 Larry the Git Cow 2018-04-24 17:24:45 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=578d6887f52824f04bbed8f89d637c9c03a39804

commit 578d6887f52824f04bbed8f89d637c9c03a39804
Author:     Mikle Kolyada <[e-mail]>
AuthorDate: 2018-04-24 17:24:07 +0000
Commit:     Mikle Kolyada <[e-mail]>
CommitDate: 2018-04-24 17:24:34 +0000

    x11-wm/awesome: amd64 stabla back
    
    See #c9 of the bug for more info
    
    Bug: https://bugs.gentoo.org/638140
    
    Acked-by: Maxim Koltsov <[e-mail]>
    Package-Manager: Portage-2.3.24, Repoman-2.3.6

 x11-wm/awesome/awesome-4.2-r2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)}

[Comment 11 Thomas Deutschmann (RETIRED) 2018-04-25 16:19:51 UTC]

x86 stopped stabilization due to bug 654084. Please tell x86 how to proceed.

[Comment 12 Andreas Sturmlechner 2019-05-11 08:32:53 UTC]

What about arm, ppc, ppc64?

[Comment 13 Thomas Deutschmann (RETIRED) 2019-05-12 20:57:10 UTC]

x86 stable, closing

[Comment 14 Andreas Sturmlechner 2019-05-12 21:17:16 UTC]

(In reply to Maxim Koltsov from comment #3)
> Okay, let's do amd64 and x86 first. Please don't close the bug afterwards.

Re-opening. So what about the other arches?

[Comment 15 Stabilization helper bot 2019-05-15 09:01:56 UTC]

An automated check of this bug failed - repoman reported dependency errors (39 lines truncated): 

> dependency.bad dev-lua/busted/busted-2.0_rc12_p1.ebuild: RDEPEND: ppc(default/linux/powerpc/ppc32/17.0) ['>=dev-lua/lua_cliargs-3.0', '>=dev-lua/luasystem-0.2.0', '>=dev-lua/dkjson-2.1.0', '>=dev-lua/say-1.3', '>=dev-lua/luassert-1.7.8', '>=dev-lua/lua-term-0.1_p1', '>=dev-lua/penlight-1.3.2', '>=dev-lua/mediator_lua-1.1.1_p0']
> dependency.bad dev-lua/busted/busted-2.0_rc12_p1.ebuild: RDEPEND: ppc(default/linux/powerpc/ppc32/17.0/desktop) ['>=dev-lua/lua_cliargs-3.0', '>=dev-lua/luasystem-0.2.0', '>=dev-lua/dkjson-2.1.0', '>=dev-lua/say-1.3', '>=dev-lua/luassert-1.7.8', '>=dev-lua/lua-term-0.1_p1', '>=dev-lua/penlight-1.3.2', '>=dev-lua/mediator_lua-1.1.1_p0']
> dependency.bad dev-lua/busted/busted-2.0_rc12_p1.ebuild: RDEPEND: ppc(default/linux/powerpc/ppc32/17.0/desktop/gnome) ['>=dev-lua/lua_cliargs-3.0', '>=dev-lua/luasystem-0.2.0', '>=dev-lua/dkjson-2.1.0', '>=dev-lua/say-1.3', '>=dev-lua/luassert-1.7.8', '>=dev-lua/lua-term-0.1_p1', '>=dev-lua/penlight-1.3.2', '>=dev-lua/mediator_lua-1.1.1_p0']
> dependency.bad dev-lua/ldoc/ldoc-1.4.6.ebuild: DEPEND: ppc(default/linux/powerpc/ppc32/17.0) ['dev-lua/penlight']
> dependency.bad dev-lua/ldoc/ldoc-1.4.6.ebuild: RDEPEND: ppc(default/linux/powerpc/ppc32/17.0) ['dev-lua/penlight']
> dependency.bad dev-lua/ldoc/ldoc-1.4.6.ebuild: DEPEND: ppc(default/linux/powerpc/ppc32/17.0/desktop) ['dev-lua/penlight']

[Comment 16 Andreas Sturmlechner 2019-05-19 19:50:12 UTC]

Re-adding amd64 and x86 for these two packages:
dev-lua/say-1.3_p1-r1
dev-lua/luassert-1.7.10

[Comment 17 Stabilization helper bot 2019-05-19 20:00:26 UTC]

An automated check of this bug failed - the following atom is unknown:

dev-lua/luasystem-0.2.0

Please verify the atom list.

[Comment 18 ernsteiswuerfel 2019-05-21 21:03:49 UTC]

Created attachment 577534 [details]
tatt tests (ppc)

Looking good on ppc.

[Comment 19 ernsteiswuerfel 2019-05-21 22:05:14 UTC]

Created attachment 577538 [details]
tatt tests (ppc64)

Looking good on ppc64.

[Comment 20 Sergei Trofimovich (RETIRED) 2019-05-25 07:56:55 UTC]

ppc stable

[Comment 21 Sergei Trofimovich (RETIRED) 2019-05-25 08:01:49 UTC]

ppc64 stable

[Comment 22 Mikle Kolyada (RETIRED) 2019-05-25 08:34:49 UTC]

amd64 stable

[Comment 23 Thomas Deutschmann (RETIRED) 2019-05-26 22:28:15 UTC]

x86 stable

[Comment 24 Mikle Kolyada (RETIRED) 2019-07-29 14:41:15 UTC]

arm stable