Bug 429530 - [RFE] please update to the new xdvik-22.84.13-j1.35.patch.gz
Summary: [RFE] please update to the new xdvik-22.84.13-j1.35.patch.gz
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xdvik
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jonathan Underwood
QA Contact: Fedora Extras Quality Assurance
URL: http://sourceforge.jp/projects/xdvi/f...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-21 12:40 UTC by Jindrich Novy
Modified: 2013-07-02 23:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-02 23:29:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jindrich Novy 2008-01-21 12:40:00 UTC
Description of problem:
Please update xdvik japanese patch to the latest upstream:
http://sourceforge.jp/projects/xdvi/files/

Version-Release number of selected component (if applicable):
22.84.13

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jonathan Underwood 2008-01-21 23:28:02 UTC
Oddly, although the file is listed on that page, it isn't actually present on
the server. Guess I'll try again in a few days time, and if not, try and send an
email asking what's going on. My Japanese isn't too hot though.. :)

Comment 2 Jonathan Underwood 2008-02-02 23:29:34 UTC
OK, have now integrated xdvik-22.84.13-j1.36.patch.gz in 22.84.13-15.

By the way, in the process of doing this, I noticed that this macro in the spec
file:

%{!?_texmf_main: %define _texmf_main %{_datadir}/texmf}

no longer does what it is supposed to, leading to failures in the files
processing part of the build like:

Processing files: xdvik-22.84.13-14.fc9
error: File must begin with "/": %{_texmf_main}/xdvi/
error: File must begin with "/": %{_texmf_main}/pxdvi/

Hardcoding a 

%define _texmf_main %{_datadir}/texmf

fixes this, but I am not sure what is causing this problem. 


Note You need to log in before you can comment on or make changes to this bug.