Re: pango1.0.sh exit code 1

2013-08-05 Thread Larry Hall (Cygwin)
On 8/5/2013 1:30 AM, Martin Baute wrote: Am 31.07.2013 13:23, schrieb Martin Baute: Hi there, I've mailed this to cygwin-ports-general on 2013-01-23, and got it confirmed, but today realized this bug does still persist. Since I now know that libpango is part of the basic Cygwin package, I'll re

Re: pango1.0.sh exit code 1

2013-08-04 Thread Martin Baute
Hello? Anyone? Am 31.07.2013 13:23, schrieb Martin Baute: > Hi there, > > I've mailed this to cygwin-ports-general on 2013-01-23, and > got it confirmed, but today realized this bug does still > persist. Since I now know that libpango is part of the basic > Cygwin package, I'll report it here, a

Re: pango1.0.sh exit code 1

2013-08-01 Thread Gary Johnson
On 2013-08-01, Angelo Graziosi wrote: > Martin Baute wrote: > >The libpango1.0 postinstall script fails with exit code 1 > > Same here on a W7 box (cygwin32). Same workaround. > > Strangely, on XP it worked fine some time ago (probably in the 2009).. As I reported in an earlier thread ("Recent C

Re: pango1.0.sh exit code 1

2013-08-01 Thread Angelo Graziosi
Martin Baute wrote: The libpango1.0 postinstall script fails with exit code 1 Same here on a W7 box (cygwin32). Same workaround. Strangely, on XP it worked fine some time ago (probably in the 2009).. Ciao, Angelo. -- Problem reports: http://cygwin.com/problems.html FAQ:

pango1.0.sh exit code 1

2013-07-31 Thread Martin Baute
Hi there, I've mailed this to cygwin-ports-general on 2013-01-23, and got it confirmed, but today realized this bug does still persist. Since I now know that libpango is part of the basic Cygwin package, I'll report it here, again: The libpango1.0 postinstall script fails with exit code 1. Some

Re: Package: libpango1.0_0 pango1.0.sh exit code 1

2013-05-07 Thread roadworrier
Thanks for the solution, this fixed the same problem I encountered after installing X11. Andrey Repin-3 wrote > Greetings, All! > > I was installing ImageMagick for first time, and Setup.exe hit the > abovementioned error. > Setup.log.full contains these relevant lines: > > 2013/02/16 21:31:27