Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2023-02-19 Thread Barak A. Pearlmutter
> >Failing on some inputs is not a justification for a `serious` severity. > > *Silently* failing, i.e. saying you succeed but not doing so, > however is Regardless of severity, does anyone have any good ideas for fixing this? Patches welcome! Feel free to just upload a fix if you have the urge.

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2023-02-19 Thread Thorsten Glaser
Antonio Terceiro dixit: >Failing on some inputs is not a justification for a `serious` severity. *Silently* failing, i.e. saying you succeed but not doing so, however is, in my book. If it at least aborted giving the error code, I’d accept that somewhat more easily. >Thus, I am downgrading this

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2023-02-19 Thread Antonio Terceiro
Control: severity -1 normal Failing on some inputs is not a justification for a `serious` severity. Thus, I am downgrading this bug to normal. signature.asc Description: PGP signature

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2022-04-03 Thread Thorsten Glaser
Hi Wolfgang, > The issue is caused because pdftops creates a PostScript file which > contains the whole drawing as a single bitmap image (don't know why). Oh, ouch. So, bug in poppler after all? >> $ pdf2ps test1.pdf test4-1.ps >> $ ps2eps test4-1.ps Hm, not just poppler? test4-1.ps has a

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2022-04-03 Thread Wolfgang Glunz
Hi Thorsten, The issue is caused because pdftops creates a PostScript file which contains the whole drawing as a single bitmap image (don't know why). And bitmap images are not supported by pstoedit for the mpost format. Regarding " (which is NOT documented, purifyeps says it takes PostScript

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2022-04-02 Thread Thorsten Glaser
Dixi quod… >Package: pstoedit >Version: 3.78-1 >Followup-For: Bug #1008280 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008280 for the full story and reproducer. With the help of http://www.calvina.de/pstoedit/pstoedit.htm#section_69 I may have found a workaround (which indicates a bug in

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2022-04-02 Thread Thorsten Glaser
Package: pstoedit Version: 3.78-1 Followup-For: Bug #1008280 X-Debbugs-Cc: t...@mirbsd.de This is reproducible on sid. It also occurs on buster, although with a different failure mode: -BEGIN cutting here may damage your screen surface- $ purifyeps test1-a.eps test1-b.eps pstoedit:

Bug#1008280: pstoedit: silently fails with success return for some purifyeps use cases

2022-03-25 Thread Thorsten Glaser
Package: pstoedit Version: 3.75-1 Severity: serious Justification: unusable by some users X-Debbugs-Cc: t...@mirbsd.de, hill...@web.de, debian-tex-ma...@lists.debian.org Control: affects -1 purifyeps I’ve noticed purifyeps (which is needed for Tₑχ/LᴬTᴇΧ to process .eps files) fails on some inputs