[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#863357: marked as done ('winetricks allfonts' fails on Baekmuk)

Your message dated Thu, 1 Feb 2018 22:31:25 +0100
with message-id <1c62a62e-2b2b-02f0-5793-b4802db788bd@gmail.com>
and subject line Re: Bug#863357: 'winetricks allfonts' fails on Baekmuk
has caused the Debian Bug report #863357,
regarding 'winetricks allfonts' fails on Baekmuk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
863357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863357
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: winetricks
Version: 0.0+20141009+svn1208-2

The font package ttf-baekmuk has been renamed to fonts-baekmuk in Debian, but winetricks still has it listed as the former. As such, it can't download it and fails when trying to execute 'winetricks allfonts'. The included diff patch fixes it.

7750c7750
<     w_download http://ftp.debian.org/debian/pool/main/t/ttf-baekmuk/ttf-baekmuk_2.2.orig.tar.gz afdee34f700007de6ea87b43c92a88b7385ba65b
---
>     w_download http://ftp.debian.org/debian/pool/main/f/fonts-baekmuk/fonts-baekmuk_2.2.orig.tar.gz afdee34f700007de6ea87b43c92a88b7385ba65b
7752c7752
<     gunzip -dc "$W_CACHE/baekmuk/ttf-baekmuk_2.2.orig.tar.gz" | tar -xf -
---
>     gunzip -dc "$W_CACHE/baekmuk/fonts-baekmuk_2.2.orig.tar.gz" | tar -xf -

--- End Message ---
--- Begin Message --- 
Version: 0.0+20160425-1

Hi,

this was fixed upstream in version 20160311.  So current stable Debian
(stretch) and newer have fixed versions.

I doubt we'll fix it in oldstable (jessie) which has the version you
reported this bug against.  There are just too many issues with changed
URLs, which would need to be addressed.

Greets
jre

--- End Message ---
Reply to: