https://bugs.freedesktop.org/show_bug.cgi?id=63398
Lionel Elie Mamane <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Assignee|[email protected] |[email protected] |desktop.org | --- Comment #15 from Lionel Elie Mamane <[email protected]> --- (In reply to comment #14) > Having raised the issue I'm willing to try this, but I need to know how to > find out whether the fix is in a particular daily build or not. I've so far > failed to find the list. It is not yet in the LibreOffice 4.0 branch, only in master (4.1.0.alpha). You see that in the Whiteboard, which says "target:4.1.0". When it will be committed, the whiteboard will be updated with "target:4.0.4" and a comment similar to comment 13 will be posted to this bug. I submitted it for approval to LibreOffice 4.0 branch (we need approval by a second developer for release/bugfix branch), see https://gerrit.libreoffice.org/3863 > Further, in daily builds > (http://dev-builds.libreoffice.org/daily/libreoffice-4-0/) > I can see Win and Mac versions, but not Linux .deb versions. > What am I missing? These two have *both* rpm and deb packages (the .debs are packed in a .tar.gz): http://dev-builds.libreoffice.org/daily/libreoffice-4-0/Linux-x86_64@31-Release-Configuration-RHEL5-Baseline/current/ http://dev-builds.libreoffice.org/daily/libreoffice-4-0/Linux-x86@34-Release-Configuration-RHEL5-Baseline/current/ For the time being, you'll have to do the testing on a master daily. It would e very much appreciated if you could test it before we put in our release branch. Here's how to see if a particular commit/fix is in a daily build: Let's take for example http://dev-builds.libreoffice.org/daily/master/Linux-x86-64@8-SLED11/current/ The easiest is just to look at the date. Comment 13 says that the fix was committed to master on 2013-05-12 03:16:47 UTC, but right now the files there are of 03-May-2013, so no chance. Have to wait for a new build. If the time is close and you are unsure, the file "*_build_info.txt" contains in its first lines: tinderbox: git sha1s core:485b1ac04c567d9d11cd395cf0a62cc43cabd8ad The "core" line is the one you need. On http://cgit.freedesktop.org/libreoffice/core/commit/?id=485b1ac04c567d9d11cd395cf0a62cc43cabd8ad, you see the last commit that is included in this build, and you can look in "log" whether it is before or after the commit that fixes / is supposed to fix the bug. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
