Bug 29600

Summary:	fvwm2 is obsolete
Product:	Mageia	Reporter:	Ken Arromdee <arromdee2>
Component:	RPM Packages	Assignee:	Chris Denice <eatdirt>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	release_blocker	CC:	fri
Version:	8
Target Milestone:	Mageia 9
Hardware:	All
OS:	Linux
See Also:	https://bugs.mageia.org/show_bug.cgi?id=29588
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Ken Arromdee 2021-10-28 10:18:23 CEST

As pointed out in #29588, fvwm2 is obsolete and development has switched to fvwm3 (which is already in Mageia).  Unless there are use cases I'm unaware of (entirely possible), it should be removed from the next Mageia.  See https://github.com/fvwmorg/fvwm:

> Please note that FVWM2 is in maintenance mode. This means it won't be receiving any new features. Bug fixes will be to the core of FVWM2 only. Any problems found in modules will be to fix segfaults only.

>All users are hereforth encouraged to use fvwm3, and to report any bugs.

Also, /bin/RunWM (xinitrc-2.4.21-31.1.mga8) understands fvwm2 but not fvwm3, although it is unclear whether this script is of any real use at all.  It may be cruft hanging around in X from years ago that doesn't deserve to be fixed.

Morgan Leijström 2021-10-28 11:26:37 CEST

Target Milestone: --- => Mageia 9
CC: (none) => fri

Lewis Smith 2021-10-28 20:04:45 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=29588

Comment 1 Lewis Smith 2021-10-28 20:07:43 CEST

This being a follow-on from the other bug referenced, assigning it similarly to ChrisD.

Assignee: bugsquad => eatdirt

David Walser 2021-10-28 21:11:31 CEST

Priority: Normal => release_blocker

Comment 2 Chris Denice 2021-10-31 13:12:55 CET

No it is not obsoleted. fvwm2 devel is frozen, and fvwm3 is in full devel, many things are broken in fvwm3 and many things running on fvwm2 are not yet ported, and possibly will never be ported,  as the developer himself claims.

We have kept fvwm1 for more than 20 years in parallel as fvwm2, already in mandrake.

Now we are going to do the same, both versions are going to co-exist while fvwm2 will be really obsoleted and everything else ported to fvwm3. For instance, fvwm-crystal is based on fvwm2 etc...

Anyway, I am in charge here, so don't hesitate to report bugs, for both versions, especially possible conflicts.

Status: NEW => RESOLVED
Resolution: (none) => INVALID