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

Bug#649713: marked as done (Please Build-Depend on ghostscript, not gs-common.)

Your message dated Tue, 20 Dec 2011 20:08:13 +0100
with message-id <20111220190813.GA9919@jwilk.net>
and subject line Re: Bug#649713: Please Build-Depend on ghostscript, not gs-common.
has caused the Debian Bug report #649713,
regarding Please Build-Depend on ghostscript, not gs-common.
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.)


-- 
649713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649713
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: flite
Version: 1.4-release-3
Severity: important
User: debian-printing@lists.debian.org
Usertags: drop-gs-common

Hi, 

flite currently Build-Depends on gs-common, which is a transitional package.
The next upload of ghostscript (currently) plans to drop both gs-common and
the ghostscript "Provides: gs-common". As soon as that upload happens, it
will make flite FTBFS.

Please replace the Build-Depends on gs-common to a Build-Depends on ghostscript.

(The severity of this bug will be raised after the ghostscript upload.)

Cheers,

OdyX

--- End Message ---
--- Begin Message --- 
Version: 1.4-release-4

* Didier Raboud <odyx@debian.org>, 2011-11-23, 12:20:
flite currently Build-Depends on gs-common, which is a transitional package. The next upload of ghostscript (currently) plans to drop both gs-common and the ghostscript "Provides: gs-common". As soon as that upload happens, it will make flite FTBFS.
This was fixed in the recent upload. (The bug wasn't closed automatically because of a typo in the changelog.) 

--
Jakub Wilk

--- End Message ---
Reply to: