Post F38 upgrade/fresh install: printing text files via paps (a Postscript converter) prints raw postscript

[Max Pyziur]

Greetings,

My F38 upgrade on my desktop and my fresh install on my laptop (because of 
an upgrade crash) are taking place in less than stellar fashion. But given 
that things have been going very well in this regard since F27 (circa late 
2017) something like this shouldn't be unexpected.

Trying to focus on one problem at a time, I am now dealing with printing 
text files.

For the last ten or so years, I've relied on enscript and then paps. I 
think that I switched to paps because enscript at the time didn't support 
utf-8.

paps has worked as designed for me until the upgrade/fresh install. My 
sole availabe printer is an HP P3015. On my desktop, I use the HP 
Postscript driver; on my laptop I use the HP LaserJet p3010 Series hpijs 
pcl3, 3.22.10 driver for the printer.

When printing from a web browser (firefox of brave), libreoffice, evince, 
AcroRead, or gedit, the results are correct.

But now with the flip to F38, and issuing a paps command like this (which 
I've run for a decade):
paps --columns=3 --landscape --paper=letter --font="Monospace 6" 
/path/to/some/textfile | lpr -P lp3

the printer prints raw postscript.

(lp3 is the name that I use for the HP printer)

I suspect that I am part of a small community of paps users. But I would 
very much like to continue either using paps or something similar.

Could it be pango (required by paps)? some other possible dependency? Are 
there alternatives? Is there some nuance in configuring the printer?

I'd appreciate any advice here.

Much thanks,

Max
pyz(a)brama.com

[Max Pyziur]

Greetings,

Working directly with the paps developer on github 
(https://github.com/dov/paps/discussions/63)

We've come across a bug.

Current F37 version is:
paps-0.7.1-5.fc37

Current F38 version is:
paps-0.7.9-1.fc38

Latest stable version is
paps-0.8.x

This needs to be reported Fedora maintainers and a new paps release needs 
to be made available.

I'm like a rooster tap-dancing in golashes here. How does this get 
reported to Fedora maintainers?

Max
pyz(a)brama.com






On Mon, 1 May 2023, Max Pyziur wrote:

>
> Greetings,
>
> My F38 upgrade on my desktop and my fresh install on my laptop (because of an 
> upgrade crash) are taking place in less than stellar fashion. But given that 
> things have been going very well in this regard since F27 (circa late 2017) 
> something like this shouldn't be unexpected.
>
> Trying to focus on one problem at a time, I am now dealing with printing text 
> files.
>
> For the last ten or so years, I've relied on enscript and then paps. I think 
> that I switched to paps because enscript at the time didn't support utf-8.
>
> paps has worked as designed for me until the upgrade/fresh install. My sole 
> availabe printer is an HP P3015. On my desktop, I use the HP Postscript 
> driver; on my laptop I use the HP LaserJet p3010 Series hpijs pcl3, 3.22.10 
> driver for the printer.
>
> When printing from a web browser (firefox of brave), libreoffice, evince, 
> AcroRead, or gedit, the results are correct.
>
> But now with the flip to F38, and issuing a paps command like this (which 
> I've run for a decade):
> paps --columns=3 --landscape --paper=letter --font="Monospace 6" 
> /path/to/some/textfile | lpr -P lp3
>
> the printer prints raw postscript.
>
> (lp3 is the name that I use for the HP printer)
>
> I suspect that I am part of a small community of paps users. But I would very 
> much like to continue either using paps or something similar.
>
> Could it be pango (required by paps)? some other possible dependency? Are 
> there alternatives? Is there some nuance in configuring the printer?
>
> I'd appreciate any advice here.
>
> Much thanks,
>
> Max
> pyz(a)brama.com
>

[Todd Zullinger]

Max Pyziur wrote:
>  Working directly with the paps developer on github
>  (https://github.com/dov/paps/discussions/63)
>  
>  We've come across a bug.
>  
>  Current F37 version is:
>  paps-0.7.1-5.fc37
>  
>  Current F38 version is:
>  paps-0.7.9-1.fc38
>  
>  Latest stable version is
>  paps-0.8.x
>  
>  This needs to be reported Fedora maintainers and a new paps release needs to
>  be made available.
>  
>  I'm like a rooster tap-dancing in golashes here. How does this get reported
>  to Fedora maintainers? 
This would be reported at https://bugzilla.redhat.com.

There is (rather copious) documentation for the process at:
https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/

It looks like there aren't a lot of changes between the
0.7.9 and 0.8.0 release.  The maintainer has already updated
the package in rawhide (what will be Fedora 39).

If the changes don't cause any breaking changes, then
updating to 0.8.0 in stable Fedora release would be
reasonable.

-- 
Todd

[stan]

On Tue, 2 May 2023 11:20:44 -0400 (EDT)
Max Pyziur <pyz(a)brama.com&gt; wrote:
>  Working directly with the paps developer on github 
>  (https://github.com/dov/paps/discussions/63)
>  
>  We've come across a bug.
>  
>  Current F37 version is:
>  paps-0.7.1-5.fc37
>  
>  Current F38 version is:
>  paps-0.7.9-1.fc38
>  
>  Latest stable version is
>  paps-0.8.x
>  
>  This needs to be reported Fedora maintainers and a new paps release
>  needs to be made available. 
That would be through the bugzilla:
https://bugzilla.redhat.com/
You will need to set up an account, and then follow the fedora links
after you select 'New' or 'File a Bug'.  I checked, and there isn't
already a bug opened for this.

But, why is this a bug?  Stable versions are often at lower release
versions for rpms than newer versions.  And when I look in koji, I see
that newer versions are already built for F38 and F39 (rawhide).  They
were built yesterday, so should be showing up in updates testing today,
and in stable in a few days. You could go to koji,
https://koji.fedoraproject.org/koji/buildinfo?buildID=2161630
and grab the latest rpm and install it locally using
dnf -C install [package name]
to see if it fixes your issue.

[Todd Zullinger]

stan via users wrote:
>  But, why is this a bug?  Stable versions are often at
>  lower release versions for rpms than newer versions. 
The bug is that 0.8.0 includes a fix which 0.7.9 lacks.
That context was only in the github link which Max posted.
Until I read that, I had the same reaction. :)

-- 
Todd

[stan]

On Tue, 2 May 2023 11:52:47 -0400
Todd Zullinger <tmz(a)pobox.com&gt; wrote:

>  stan via users wrote:
>  > But, why is this a bug?  Stable versions are often at
>  > lower release versions for rpms than newer versions.  
>  
>  The bug is that 0.8.0 includes a fix which 0.7.9 lacks.
>  That context was only in the github link which Max posted.
>  Until I read that, I had the same reaction. :) 
Caught!  I didn't visit the link.  :-)

[Solved, partially] Re: Post F38 upgrade/fresh install: printing text files via paps (a Postscript converter) prints raw postscript

[Max Pyziur]

On Tue, 2 May 2023, stan via users wrote:

>  On Tue, 2 May 2023 11:52:47 -0400
>  Todd Zullinger <tmz(a)pobox.com&gt; wrote:
>
> > stan via users wrote:
> >> But, why is this a bug?  Stable versions are often at
> >> lower release versions for rpms than newer versions.
> >
> > The bug is that 0.8.0 includes a fix which 0.7.9 lacks.
> > That context was only in the github link which Max posted.
> > Until I read that, I had the same reaction. :)
>
>  Caught!  I didn't visit the link.  :-) 
Until the fixed version is approved and pushed out, one way to continue 
using paps is to downgrade to the F37 version located 
here:
https://dl.fedoraproject.org/pub/fedora/linux/releases/37/Everything/x86_...

fyi,

MP
pyz(a)brama.com

[Max Pyziur]

On Tue, 2 May 2023, stan via users wrote:

>  On Tue, 2 May 2023 11:20:44 -0400 (EDT)
>  Max Pyziur <pyz(a)brama.com&gt; wrote:
> > Working directly with the paps developer on github
> > (https://github.com/dov/paps/discussions/63)
> >
> > We've come across a bug.
> >
> > Current F37 version is:
> > paps-0.7.1-5.fc37
> >
> > Current F38 version is:
> > paps-0.7.9-1.fc38
> >
> > Latest stable version is
> > paps-0.8.x
> >
> > This needs to be reported Fedora maintainers and a new paps release
> > needs to be made available.
>
>  That would be through the bugzilla:
>  https://bugzilla.redhat.com/
>  You will need to set up an account, and then follow the fedora links
>  after you select 'New' or 'File a Bug'.  I checked, and there isn't
>  already a bug opened for this. 
Thank you. Just stubled through a bugzilla report.
https://bugzilla.redhat.com/show_bug.cgi?id=2192645

>  But, why is this a bug?  Stable versions are often at lower release
I'm just a motorhead (dutiful Fedora user).

>  versions for rpms than newer versions.  And when I look in koji, I
> see
>  that newer versions are already built for F38 and F39 (rawhide).  They
>  were built yesterday, so should be showing up in updates testing today,
>  and in stable in a few days. You could go to koji,
>  https://koji.fedoraproject.org/koji/buildinfo?buildID=2161630
>  and grab the latest rpm and install it locally using
>  dnf -C install [package name]
>  to see if it fixes your issue. 
Great, looking forward to updating to the new version.

Max