Here's what I've got rolled up for 0.42.1 so far:
* src/dialogs/stroke-style.cpp: backport bulia's fix for stroke width spin button [bug number??] * src/text-editing.cpp: backport bulia's fix for text crash [bug 1247066] * src/libnrtype/Layout-TNG-OutIter.cpp: backport cyreve fix for crash on delete in virgin flowtext [bug 1245842] * configure.ac: Kees fix for libgc detection w/dlopen [bug number??]
Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak.
-mental
On Thu, Jul 28, 2005 at 10:23:40PM -0400, MenTaLguY wrote:
Here's what I've got rolled up for 0.42.1 so far:
[...list snipped...]
Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak.
Obviously any translation updates; I believe there's been at least one translation patch since 0.42.
I think the change to the `distro' script can go in. (Not at all important, but it is safe.)
Nothing else I know of.
Packagers might have changes they'd like to go in.
pjrm.
On Fri, 2005-07-29 at 14:25 +1000, Peter Moulder wrote:
On Thu, Jul 28, 2005 at 10:23:40PM -0400, MenTaLguY wrote:
Here's what I've got rolled up for 0.42.1 so far:
[...list snipped...]
Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak.
Obviously any translation updates; I believe there's been at least one translation patch since 0.42.
I think the change to the `distro' script can go in. (Not at all important, but it is safe.)
Could you please give me either patches for these, or filenames+revision numbers in CVS?
[for single-file changes, a filename+revision number pair is the easiest for me to work with -- I can just do this in the branch:
cvs -z3 update -j <old rev> -j <new rev> filename
]
-mental
On 7/29/05, Peter Moulder <Peter.Moulder@...38...> wrote:
On Thu, Jul 28, 2005 at 10:23:40PM -0400, MenTaLguY wrote:
Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak.
Obviously any translation updates; I believe there's been at least one translation patch since 0.42.
And not only /po but /share/tutorials as well.
Mental,
here's another crash bug for 42.1 (bug 1249899)
On 7/28/05, MenTaLguY <mental@...3...> wrote:
Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak.
I'd just like to urge the devs to postpone their projects a bit and go through our burgeoning bug tracker. One of the best results of the slashdotting and the insane number of downloads is the healthy stream of bug reports. Let's take advantage of that to deliver a worthy 0.42.1.
At least, we need all help we can use to revise the reports and consolidate duplicates.
And here are my candidates for MUST FIX bugs for 0.42.1:
- Naturally, the open dialog crash on win98 - it's been independently reported: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1247061...
- the bug where installing 0.42 over 0.41 on Windows makes it crash on start: https://sourceforge.net/tracker/index.php?func=detail&aid=1247068&gr.... To fix this the installer must uninstall previous version or simply clear all dlls from the installation directory.
- The freezes and crashes on OSX - I assume these are already fixed?
- The libgc dependency problem with RPMs - I assume it's already fixed?
- Probably some other of the reported crashes, which I haven't figured out yet.
On Friday 29 July 2005 12:08, bulia byak wrote:
On 7/28/05, MenTaLguY <mental@...3...> wrote:
Anyone got anything else for me? At the moment I'm thinking of aiming for 0.42.1 by early next weak.
I'd just like to urge the devs to postpone their projects a bit and go through our burgeoning bug tracker. One of the best results of the slashdotting and the insane number of downloads is the healthy stream of bug reports. Let's take advantage of that to deliver a worthy 0.42.1.
At least, we need all help we can use to revise the reports and consolidate duplicates.
And here are my candidates for MUST FIX bugs for 0.42.1:
- Naturally, the open dialog crash on win98 - it's been
independently reported: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=124706 1&group_id=93438
- the bug where installing 0.42 over 0.41 on Windows makes it crash
on start: https://sourceforge.net/tracker/index.php?func=detail&aid=1247068&g roup_id=93438&atid=604306. To fix this the installer must uninstall previous version or simply clear all dlls from the installation directory.
The freezes and crashes on OSX - I assume these are already fixed?
The libgc dependency problem with RPMs - I assume it's already
fixed?
No, it only lead to other dependencies on my FC2 system, starting with a way too old glib here... Dependencies I assume that FC4 might fix, but FC4 is, IMNSHO, terminally busted. In about 10 installs on another machine here, it actually worked 3 times long enough to be destroyed utterly and totally by turning yum loose to fix all the stuff updated since the FC4-final was released. Those disks went out with the trash Wednesday morning. Lifes too short to fight losing battles like that.
- Probably some other of the reported crashes, which I haven't
figured out yet.
- Naturally, the open dialog crash on win98 - it's been independently
reported: https://sourceforge.net/tracker/?func=detail&atid=604306&aid=1247061...
cyreve mentioned this could be the same as the font caching bug.
ralf
On Fri, 2005-07-29 at 22:24 +0200, Adib Taraben wrote:
bulia byak schrieb:
... And here are my candidates for MUST FIX bugs for 0.42.1: ...
I am a little bit confused about version numbering
tar has 0.42 win32 0.42-1 rpm 0.42-0.1 rpm 64b 0.42-1
what will then a interims version will be ?
0.42.1
The extra -1 is added to distinguish between multiple versions of a package of the same upstream version.
When 0.42.1 is released you can expect to see:
tar: 0.42.1 win32: 0.42.1-1 rpm: 0.42.1-0.1 rpm 64b: 0.42.1-1
-mental
Mental, here's a small and safe patch for bug 1247658. I want this in 0.42.1.
On Fri, Jul 29, 2005 at 10:24:30PM +0200, Adib Taraben wrote:
bulia byak schrieb:
... And here are my candidates for MUST FIX bugs for 0.42.1: ...
I am a little bit confused about version numbering
tar has 0.42 win32 0.42-1 rpm 0.42-0.1 rpm 64b 0.42-1
what will then a interims version will be ?
Yes, release numbering can be a bit confusing, but this is what a release number is made up of:
0.42.2-3
The part before the dash is the "version number":
0 - this part is the "major version number". This number is incremented very infrequently and is generally used to mark a major compatibility change, such as a switch to a different file or protocol format.
42 - this part is the "minor version number". This is the number that is normally incremented when we have a main release.
2 - this part is the "point version number". This is used to number small incremental releases off of the main code branch, usually for bug fixes and other non-feature enhancements.
These three numbers are used to tag the official source code release, which is done as a tarball. We always drop the point version number if it is zero, so you'd never see 0.42.0. Note that this shouldn't be considered a floating point number - 0.4 and 0.40 do not mean the same thing (the first means release number four, the second is release number forty.)
The part after the dash is used only by the packagers:
3 - this is the "package patch number". This is used by the packagers to denote new releases of the package. They might do this if an earlier version was packaged wrongly or if they wish to include some special patches that are not part of the version release. Note that package patch numbers always start from 1, rather than from 0 as the version numbers do. I don't know why this is, but it's convention.
Hopefully this explains the strange numbers that pop up with releases. I don't know what '0.42-0.1' is; it might be a mistake. However, sometimes some distros use somewhat different schemes for doing their package patch number.
Bryce
participants (7)
-
Adib Taraben -
Bryce Harrington -
bulia byak -
Gene Heskett -
MenTaLguY -
Peter Moulder -
Ralf Stephan