Bug#419180: gs-esp fails while processing a file prepared for printing

2011-02-10 Thread Jonathan Nieder
Alexei Ustyuzhaninov wrote: > Please find the files attached. > > I've just tried to re-execute this command with current ghostscript > (8.71~dfsg2-6) and it failed again, but without segmentation fault. > I will investigate this more carefully on weekend. Thanks, Alexei. I tried with 8.71~dfsg2

Bug#423918: marked as done (gs-esp doesnt rasterize postscript file)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 21:49:58 +0100 with message-id <201102102149.58357.stefan.schwar...@ipm.fraunhofer.de> and subject line has caused the Debian Bug report #423918, regarding gs-esp doesnt rasterize postscript file to be marked as done. This means that you claim that the problem

Bug#342598: marked as done (Package: foomatic-db)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 16:45:52 +0100 with message-id <201102101645.59624.o...@debian.org> and subject line Re: Package: foomatic-db has caused the Debian Bug report #342598, regarding Package: foomatic-db to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#598248: foomatic-db-engine: Takes a long time to spool/print after recent upgrade

2011-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 598248 zathura 0.0.8.1-2 Bug #598248 [foomatic-db-engine] foomatic-db-engine: Takes a long time to spool/print after recent upgrade Bug reassigned from package 'foomatic-db-engine' to 'zathura'. Bug No longer marked as found in versions

Bug#598248: foomatic-db-engine: Takes a long time to spool/print after recent upgrade

2011-02-10 Thread Didier 'OdyX' Raboud
reassign 598248 zathura 0.0.8.1-2 thanks Le Tuesday 28 September 2010 15:41:13 synt...@gmail.com, vous avez écrit : > Please reassign to zathura. Sorry to have filed this against > foomatic-db-engine. > > Thanks Hi Michel, as you asked, I'm hereby reassigning your bug to zathura's version in S

Bug#598078: marked as done (foomatic-db-engine: My printer doesn't work after the upgrade)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 15:41:26 +0100 with message-id <201102101541.30203.o...@debian.org> and subject line Re: The problem was caused by something else has caused the Debian Bug report #598078, regarding foomatic-db-engine: My printer doesn't work after the upgrade to be marked as don

Processed: Re:#509189: foomatic-db-engine: device-uri is mixed up with printers

2011-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > package foomatic-db-engine Limiting to bugs with field 'package' containing at least one of 'foomatic-db-engine' Limit currently set to 'package':'foomatic-db-engine' > tags 509189 +moreinfo Bug #509189 [foomatic-db-engine] foomatic-db-engine: d

Bug#509189: #509189: foomatic-db-engine: device-uri is mixed up with printers

2011-02-10 Thread Didier 'OdyX' Raboud
package foomatic-db-engine tags 509189 +moreinfo thanks Le Friday 19 December 2008 14:31:37 Steffen Joeris, vous avez écrit : > Package: foomatic-db-engine > Version: 3.0.2-20080211-1 > Severity: important > > Hi > > I have the problem that my printers are both detected (I am using a > modified

Bug#384185: marked as done (foomatic-db-engine: foomatic-configure may eat up all memory)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 15:25:14 +0100 with message-id <201102101525.15870.o...@debian.org> and subject line Not eating memory anymore: Closing has caused the Debian Bug report #384185, regarding foomatic-db-engine: foomatic-configure may eat up all memory to be marked as done. This me

Bug#319284: marked as done (foomatic-db-gutenprint: Unable to read printer database)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 14:55:41 +0100 with message-id <201102101455.42875.o...@debian.org> and subject line Not crashing anymore, closing has caused the Debian Bug report #319284, regarding foomatic-db-gutenprint: Unable to read printer database to be marked as done. This means that y

Bug#308734: marked as done (foomatic-db: annoying perl warning - uninitialized value in numeric gt, line 1896 DB.pm)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 14:49:55 +0100 with message-id <201102101449.58151.o...@debian.org> and subject line Reported as "not-a-bug", closing has caused the Debian Bug report #261662, regarding foomatic-db: annoying perl warning - uninitialized value in numeric gt, line 1896 DB.pm to b

Bug#261662: marked as done (foomatic-gui: Use of uninitialized value in numeric gt (>) at /usr/share/perl5/Foomatic/DB.pm line 1895.)

2011-02-10 Thread Debian Bug Tracking System
Your message dated Thu, 10 Feb 2011 14:49:55 +0100 with message-id <201102101449.58151.o...@debian.org> and subject line Reported as "not-a-bug", closing has caused the Debian Bug report #261662, regarding foomatic-gui: Use of uninitialized value in numeric gt (>) at /usr/share/perl5/Foomatic/DB.p

Processed: Re: Bug#253612: Use of uninitialized value in string eq at /usr/bin/foomatic-configure line 332.

2011-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > package foomatic-db-engine Limiting to bugs with field 'package' containing at least one of 'foomatic-db-engine' Limit currently set to 'package':'foomatic-db-engine' > tag 253612 +unreproducible +moreinfo +upstream Bug #253612 [foomatic-db-engi

Bug#253612: Use of uninitialized value in string eq at /usr/bin/foomatic-configure line 332.

2011-02-10 Thread Didier 'OdyX' Raboud
package foomatic-db-engine tag 253612 +unreproducible +moreinfo +upstream thanks Le Thursday 10 June 2004 15:01:52 Bill Allombert, vous avez écrit : > I tried the following command: > ~# foomatic-configure -p Epson-Stylus_Photo_EX -d gimp-print -s lpd -n lp > -c file:/dev/lp0 and I got: > Use of u

Bug#496070: [ghostscript] opentypefont

2011-02-10 Thread Fabian Greffrath
Dear Valek, thanks for your quick response. Am 10.02.2011 13:34, schrieb Valek Filippov: Unless you are going to add TrueType instructions, TTF version generated automatically would look at best not better than Type1. I don't know if the fault is at pango, fontconfig or libfreetype (or anyth

Bug#496070: [ghostscript] opentypefont

2011-02-10 Thread Bastien ROUCARIES
Thanks but I will prefer to have the source... Bastien On Thu, Feb 10, 2011 at 11:11 AM, Fabian Greffrath wrote: > I have minimized my proposed debdiff and updated against the current package > version in unstable. > > -- To UNSUBSCRIBE, email to debian-printing-requ...@lists.debian.org with

Olga, Olga un Evija suuta Tev sensualas buchas

2011-02-10 Thread Glenda
Ieguustamaas princesites Marite, Dace un Nina sniedz Tev draudzigus sveicienus 14. februarii (nu tak Valentiindiena!) Protams, vinas gaida Tevi ciemos! http://www.lady-lande.info : spied uz hiperlinka un uzzini vairaak! Tava privata masiere, Dace -- To UNSUBSCRIBE, email to debian-printing-

Bug#496070: [ghostscript] opentypefont

2011-02-10 Thread Fabian Greffrath
I have minimized my proposed debdiff and updated against the current package version in unstable. diff -u gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog --- gsfonts-8.11+urwcyr1.0.7~pre44/debian/changelog +++ gsfonts-8.11+urwcyr1.0.7~pre44/debian/

Bug#612736: ijs should include the changes made in the ghostscript tree

2011-02-10 Thread Roger Leigh
Package: ijs Version: 0.35-7 Severity: normal Hi, ijs was included in the ghostscript tree as a static library, and accumulated some bugfixes and/or improvements over the years. Now that gs is using the external ijs, the changes made to the gs copy should ideally be reviewed and incorporated into

Re: Ghostscript 9.01 final

2011-02-10 Thread Roger Leigh
On Thu, Feb 10, 2011 at 08:00:52AM +0100, Jonas Smedegaard wrote: > On Thu, Feb 10, 2011 at 12:45:11AM +, Roger Leigh wrote: > >On Thu, Feb 10, 2011 at 12:32:06AM +0100, Till Kamppeter wrote: > >>I am packaging GS 9.01 final now (official release tomorrow). Simply > >>updating the source code o

Bug#419180: gs-esp fails while processing a file prepared for printing

2011-02-10 Thread Jonathan Nieder
Hi Alexei, Three years ago, you wrote: > I can't print an openoffice document on a cups printer. Some > investigation shows that the problem occurs when gs-esp processes a > postscript file prepared for printing The situation may be modelled with > the following command: > > $ cat prt.ps | /usr/b