How is the Fvwm3 package developed in Debian? For example, when Trixie is released, which development version of Fvwm3 will it be based on? Debian names it fvwm3 (1.1.1+ds-1).
Trixie will have whatever package is in debian at the time of the freeze, which will probably be 1.1.1.
I hope that fvwm3 1.1.2 (1.1.1-4) or above will be included. It has what common single monitor users require. Debian 1.0.6a+ds-1 was based on limited development. For the next stable Debian release, one has to wait for two years.
Not really; there’s always backports.
Backport and test repo are not convenient for a common user or someone who wants to try for the first time. I would like the Debian package to include this solved bug issue FvwmPage update. It was solved one day after 1.1.1 was released. For 1.0.6 release, the following day, there was a bug fix 1.0.6a that was included in Debian.
That bug is very minor, there is no reason to push it into a new release. This is also not the correct form to talk about the debian package. I am not going to make a new package just to fix a very minor bug, and if it is regularly an issue for you, don’t launch a new pager every time you want to see one.
Right — so actually, you’re not talking about newer releases being available to later Stable releases of Debian via back ports, but rather more of a rolling release.
That’s not how Debian works, as I’m sure you realise.
In terms of the 1.0.6a release that was down to a major bug which had not been spotted in the 1.0.6 release.
What you’re describing with the FvwmPager bug fix is no different from all the other commits which accumulate between the last release and the yet-to-be-released next version of fvwm3.
In other words, please wait.
You can always track the git version of fvwm3 if you’re completely desperate—and build your own Debian package while you’re at it.
It is not about “me @rasat” or how Debian works. I am using the latest git version 1.1.2 (1.1.1-23). It’s for the Debian users who would like to try or start using Fvwm3. It would be good to have the visible front-end bugs solved before the Debian release. As I wrote earlier, 1.1.2 (1.1.1-4) and above are fine for common users.
That would require me to release 1.1.2 – I’m not. Or for packagers in general (and I’m not just talking about Debian here), to include such commits from git as patches to a released version.