Bug#351331: dvipdfmx NMU broke fontmapsx
On Sun, Feb 05, 2006 at 09:49:48AM +0900, Junichi Uekawa wrote: Hi, Why it needs another config file? Is there any reason that ptex-jisfonts package can't use dvipdfmx.cfg file? It's a known interface provided by dvipdfmx Debian package. If you're breaking it, take both parts. Is there any other package that uses the config file? If there is no reason that ptex-jisfonts package can't use default configuration file, it's a bug of ptex-jisfonts package. Please make it use default config file or report a bug for that package. I think we need update-dvipdfmx or something like that. To properly fix the problem at hand, dvipdfmx should probably have a directory where it reads all configuration sequentially from. I think update-dvipdfmx can do that. The Debian maintainer of dvipdfmx decided to patch dvipdfmx to support it. See Bug#271468. Looking at your diff.gz[1], it looks to me you just packaged the new upstream version without any consideration for backwards compatibility or Debian integration. That kind of worries me. I checked the patchs before NMU the package. But the patch was only for Japanese-TeX related package. If the patch make dvipdfmx read all configuration files from some directory, we can apply the patch because it can be used globally. But L10N patchs must not be applied to debian main package. Remember debian is not a project only for Japanese. Although the maintainer of dvipdfmx decided to apply L10N patch, I thought that's wrong. That's why I didn't apply the patch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
To properly fix the problem at hand, dvipdfmx should probably have a directory where it reads all configuration sequentially from. I think update-dvipdfmx can do that. Where is it? The Debian maintainer of dvipdfmx decided to patch dvipdfmx to support it. See Bug#271468. Looking at your diff.gz[1], it looks to me you just packaged the new upstream version without any consideration for backwards compatibility or Debian integration. That kind of worries me. I checked the patchs before NMU the package. But the patch was only for Japanese-TeX related package. If the patch make dvipdfmx read all configuration files from some directory, we can apply the patch because it can be used globally. But L10N patchs must not be applied to debian main package. Remember debian is not a project only for Japanese. Although the maintainer of dvipdfmx decided to apply L10N patch, I thought that's wrong. That's why I didn't apply the patch. It's not a L10n patch. It's a configuration patch for extensible framework. Currently your NMU'd dvipdfmx does not provide a extention framework without touching dvipdfmx conffile. Which means, if I modify its configuration, dpkg will warn you. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
On Sun, Feb 05, 2006 at 10:50:38PM +0900, Junichi Uekawa wrote: To properly fix the problem at hand, dvipdfmx should probably have a directory where it reads all configuration sequentially from. I think update-dvipdfmx can do that. Where is it? The Debian maintainer of dvipdfmx decided to patch dvipdfmx to support it. See Bug#271468. Looking at your diff.gz[1], it looks to me you just packaged the new upstream version without any consideration for backwards compatibility or Debian integration. That kind of worries me. I checked the patchs before NMU the package. But the patch was only for Japanese-TeX related package. If the patch make dvipdfmx read all configuration files from some directory, we can apply the patch because it can be used globally. But L10N patchs must not be applied to debian main package. Remember debian is not a project only for Japanese. Although the maintainer of dvipdfmx decided to apply L10N patch, I thought that's wrong. That's why I didn't apply the patch. It's not a L10n patch. It's a configuration patch for extensible framework. Currently your NMU'd dvipdfmx does not provide a extention framework without touching dvipdfmx conffile. Which means, if I modify its configuration, dpkg will warn you. The old version of dvipdfmx contains only Japanese related configurations. Why only Japanese? It's L10N. Do you think dvipdfmx have to contain all the configurations for all the related packages in debian? It's impossible. I think dvipdfmx have to provide update-dvipdfmx or something like that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
Hi, It's not a L10n patch. It's a configuration patch for extensible framework. Currently your NMU'd dvipdfmx does not provide a extention framework without touching dvipdfmx conffile. Which means, if I modify its configuration, dpkg will warn you. The old version of dvipdfmx contains only Japanese related configurations. Why only Japanese? It's L10N. Do you think dvipdfmx have to contain all the configurations for all the related packages in debian? It's impossible. No, it's not only japanese related configurations. It contained at least Chinese and Japanese. Korean fonts were probably not included due to lack of input or lack of free font. No idea. I think dvipdfmx have to provide update-dvipdfmx or something like that. Yes. I agree. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
Why it needs another config file? Is there any reason that ptex-jisfonts package can't use dvipdfmx.cfg file? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
Hi, Why it needs another config file? Is there any reason that ptex-jisfonts package can't use dvipdfmx.cfg file? It's a known interface provided by dvipdfmx Debian package. If you're breaking it, take both parts. Keep the feature or fix both parts, please. Do NMUs sensibly. regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
On Sun, Feb 05, 2006 at 12:23:55AM +0900, Junichi Uekawa wrote: Hi, Why it needs another config file? Is there any reason that ptex-jisfonts package can't use dvipdfmx.cfg file? It's a known interface provided by dvipdfmx Debian package. If you're breaking it, take both parts. Is there any other package that uses the config file? If there is no reason that ptex-jisfonts package can't use default configuration file, it's a bug of ptex-jisfonts package. Please make it use default config file or report a bug for that package. I think we need update-dvipdfmx or something like that. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
Hi, Why it needs another config file? Is there any reason that ptex-jisfonts package can't use dvipdfmx.cfg file? It's a known interface provided by dvipdfmx Debian package. If you're breaking it, take both parts. Is there any other package that uses the config file? If there is no reason that ptex-jisfonts package can't use default configuration file, it's a bug of ptex-jisfonts package. Please make it use default config file or report a bug for that package. I think we need update-dvipdfmx or something like that. To properly fix the problem at hand, dvipdfmx should probably have a directory where it reads all configuration sequentially from. The Debian maintainer of dvipdfmx decided to patch dvipdfmx to support it. See Bug#271468. Looking at your diff.gz[1], it looks to me you just packaged the new upstream version without any consideration for backwards compatibility or Debian integration. That kind of worries me. Note that files in debian/patch seems to be unused. [1] $ diffstat *diff.gz config.guess| 1465 ++ config.sub | 1569 data/config/dvipdfmx.cfg|2 debian/80DVIPDFMx.cnf |3 debian/changelog| 184 +++ debian/control | 22 debian/copyright| 32 debian/dirs |5 debian/docs |2 debian/patch/arphic.diff| 20 debian/patch/fontmappsx.diff| 10 debian/patch/libpaper.patch | 66 + debian/patch/wrong_assumption_on_char.patch | 28 debian/postinst | 18 debian/postrm | 13 debian/rules| 104 + regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351331: dvipdfmx NMU broke fontmapsx
Package: dvipdfmx Version: 1:20050831-0.1 Severity: grave Justification, breaks other packages /etc/texmf/dvipdfm/fontmapsx isn't being read by dvipdfmx anymore, which breaks Japanese fonts, ptex-jisfonts package This is a regression of 271468 which is probably: debian/patch/fontmappsx.diff regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
