Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: latex fails to compile files that have white spaces in their path Version-Release number of selected component (if applicable): rubber-1.1-6.fc12.noarch How reproducible: Always Steps to Reproduce: 1.Create a latex file containing a white space in its path 2.Try to compile it 3.See the failure Actual results: compilation failure Expected results: normal compilation Additional info: the attached patch fixes the issue
Created attachment 380055 [details] Patch to fix the build issue for files containing white spaces in their path
Closing this bug
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
I still experience this bug with rubber-1.1-12.fc18.noarch on F18 x86_64 https://bugs.launchpad.net/rubber/+bug/639983/comments/6 claims it is fixed in trunk. The patch from https://live.gnome.org/Gedit/LaTeXPlugin/FAQ?action=AttachFile&do=view&target=rubber-1.1-spaces.patch works after adjusting the path after rebuilding rubber with the fixed patch, I was able to use it in a directory whose pathname contained spaces. Could you please consider either applying the fixed patch (I'll attach it) or doing like other distros have done and roll a 'rubber - 1.1+r417' (that is the latest in trunk and seems to be from 2011-07-02). While I can live with a version I patched myself, some of my colleagues in GPS use rubber and stumble over my pathnames, where I commonly have spaces, in a common VCS ;-)
Created attachment 736100 [details] adjust spec file to include rubber-1.1-spaces.patch ah, I had overlooked that Hicham HAOUARI had already cleaned the patch itself. Here's a patch to the spec file. I do not have write permission to pkgs.fedoraproject.org/rubber , otherwise I'd happily build in rawhide.
Patrick, I've pushed a build to Rawhide. http://koji.fedoraproject.org/koji/buildinfo?buildID=412016 Let's see what happens...
Thank you Sergio, much appreciated
rubber-1.1-13.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/rubber-1.1-13.fc18
rubber-1.1-14.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/rubber-1.1-14.fc19
rubber-1.1-14.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
rubber-1.1-13.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.