Custom Query (204 matches)
Results (13 - 15 of 204)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#138 | fixed | wget: pathconf: No such file or directory error when proxy enabled | ||
Description |
Proxy is correctly configured in .wgetrc: http_proxy = http://localhost:3128/ use_proxy = on However, when retrieving with proxy enabled, the following (likely spurious) error is reported: wget http://some-url-with-existing-file pathconf: No such file or directory --2017-01-27 15:58:26-- http://some-url-with-existing-file Resolving localhost (localhost)... 127.0.0.1 Connecting to localhost (localhost)|127.0.0.1|:3128... connected. Proxy request sent, awaiting response... The download completes normally, apparently via the configured proxy. The same .wgetrc configuration does not throw the error with my homegrown wget 1.14 static build from 2013. The above occurs with: wget-1.18-2.oc00.pentium4 |
|||
#140 | fixed | SpliX: port request | ||
Description |
SpliX is a set of CUPS printer drivers for SPL (Samsung Printer Language) printers. From OpenPrinting:
When printing from CUPS to a Samsung printer, SpliX is a requirement to get full, native support from such a device. Suggested sources: https://gitlab.com/ScumCoder/splix (includes patches added by third parties through February 5, 2015). Sourceforge page (for reference): https://sourceforge.net/projects/splix/ Additional info: While SpliX is GPL, it does utilize JBIG, which was patented by IBM, Mitsubishi, and AT&T. The last of those expired in the US in 2012. SpliX does not appear to utilize JBIG2, so it should be unencumbered by any remaining software patents. |
|||
#151 | fixed | cups-filters: Fix symlinks to executables | ||
Description |
Turns out that cups makefiles creates a lot of symlinks to executables (e.g. Please note that it's enough to only fix the link's target — the link itself doesn't need an .exe extension in order to work from under sh. It's even desirable that the link itself doesn't have an .exe extension — this will avoid recognising it as an executable by native OS/2 tools like CMD.EXE that don't support kLIBC symlinks so they will fail to execute it anyway.
So, in the above case the fix is to make |