Custom Query (1145 matches)
Results (196 - 198 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #624 | fixed | send announce e-mail about cluster upgrade, 64-bit | geofft | |
| Description |
We should probably send an e-mail to debathena-announce (and possibly other lists like software-announce, locker-maintainers, maybe itpartners?) about the cluster upgrade and specifically the change to 64-bit. |
|||
| #1444 | duplicate | See if we can finally get rid of the pam/schroot hack in reactivate | jdreed | |
| Description |
In snapshot-run, we write out KRB5CCNAME to a file to be parsed by pam_env. Comments in snapshot-run say we only needed that until pam-afs-session 2.4. We tried removing it for the Precise release (in 362cef) and had to added it back (59af91). We should see if Trusty will let us kill it once and for all. |
|||
| #903 | fixed | See if Pharos can support raw PostScript | geofft | |
| Description |
It's reported that it's currently the case that with -o raw, you can have CUPS not convert your input file, and so you can have the local cupsd send PostScript? to the remote cupsd, which will send PostScript? to the printer, and never convert it to PJL or the like. There are a couple of applications of this involving particular page sizes and formatting and alignment and the like. It's also reported that Pharos does not accept PostScript?, and the printer will print the text of your PostScript? document. We should test both of these claims, and if both true see if something can be done re Pharos. |
|||
