On Wednesday 08 August 2007 11:54:55 Lars Hansson wrote:
client-error-document-format-not-supported: Unsupported format
'application/postscript
Do you have ghostscript installed?
--
Antoine
On 8/8/07, Antoine Jacoutot [EMAIL PROTECTED] wrote:
Do you have ghostscript installed?
Yes:
$ pkg_info | grep ghost
ghostscript-8.54p1 GNU PostScript interpreter
ghostscript-fonts-8.11 35 standard PostScript fonts with Adobe name aliases
hpijs-1.5p0 HP Inkjet driver for ghostscript
Base system snapshot from August 2, xpp 1.5 dumps core on exit. If you
try to print something it will print it (ie send it to CUPS) but still
dump core on exit.
cups is 1.2.7p3.
---
Lars Hansson
Forgot: due to segmentation fault:
$ xpp
Segmentation fault (core dumped)
---
Lars Hansson
Also, not everything seems to be right with xpp itself (even though it
can print):
http://users.unet.net.ph/~lars/images/xpp.png
Apparently nothing is known about the printer even though it shows up
as ready in the CUPS web interface.
---
Lars Hansson
On Fri, Aug 03, 2007 at 08:06:08PM +0200, Tim van der Molen wrote:
I looked over esound, and the following patch is all I can see that
could even remotely be a problem with the audio interface.
I tested your patch using ogg123 and libao's esd module.
The stuttering is almost completely
Hi folks!
I've ported openocd (Open On-Chip Debugger, http://openocd.berlios.de/web/).
It works pretty well on OpenBSD now and allows me to flash/debug my AT91SAM7
using parallel port jtag wiggler.
However, only parallel adapters work for now.
This is a release of openocd svn revision 188.
On Wed, Aug 08, 2007 at 03:30:49PM +0400, Nickolay A. Burkov wrote:
I've ported openocd (Open On-Chip Debugger,
http://openocd.berlios.de/web/). It works pretty well on
OpenBSD now and allows me to flash/debug my AT91SAM7 using
parallel port jtag wiggler. However, only parallel adapters work
Hi there Kurt and ports@
I tried to build java on a clean snapshot today, and the xalan-j
checksums failed.
# make install
=== Checking files for jdk-1.5.0.12
`/usr/ports/distfiles/jdk-1_5_0_12-fcs-src-b04-jrl-02_may_2007.jar' is
up to date.
On 8/8/07, Kurt Miller [EMAIL PROTECTED] wrote:
Someone else reported this to me but I can't reproduce it. In
their case using wget to retrieve the xalan-j_2_7_0-bin.tar.gz
distfile resolved the issue of the server closing the connection
prematurely and borking the distfile.
I had the same
Hi All,
While trying to setup login_ldap, i stumbled on a somewhat misleading
phrase in the manpage:
x-ldap-binddn DN used by login_ldap to bind to the ldap server.
Can be (NULL) for anonymous bind.
x-ldap-bindpw Password used by login_ldap to bind to the ldap server.
Can be (NULL) for
On Wed, Aug 08, 2007 at 10:01:40AM -0400, Kurt Miller wrote:
Someone else reported this to me but I can't reproduce it. In
their case using wget to retrieve the xalan-j_2_7_0-bin.tar.gz
distfile resolved the issue of the server closing the connection
prematurely and borking the distfile.
On 08/08/2007, Kurt Miller [EMAIL PROTECTED] wrote:
Someone else reported this to me but I can't reproduce it. In
their case using wget to retrieve the xalan-j_2_7_0-bin.tar.gz
distfile resolved the issue of the server closing the connection
prematurely and borking the distfile.
How odd and
I hate to call Rui out in public but he is the maintainer here and very
non responsive to private emails about this.
Tor 1.1.x has BEEN DEPRECIATED from before the time 4.1 STABLE was
released (you were notified of this also Rui) and all version earlier
than 1.2.15 suffer a remote code
On Wed, Aug 08, 2007 at 11:47:56AM -0400, Peter Thoenen wrote:
I hate to call Rui out in public but he is the maintainer here and
very non responsive to private emails about this.
A fix (up to 0.1.2.16) was committed to -current yesterday; it was
MFCed this morning.
On 8/8/07, Peter Thoenen [EMAIL PROTECTED] wrote:
I hate to call Rui out in public but he is the maintainer here and very
non responsive to private emails about this.
Tor 1.1.x has BEEN DEPRECIATED from before the time 4.1 STABLE was
released (you were notified of this also Rui) and all
Hi,
I'm using an OpenBSD snapshot from 2007-08-06, and when I'm trying to update
pidgin, it ends up like this:
cc -O2 -pipe -o .libs/finch gntaccount.o gntblist.o gntconn.o gntconv.o
gntdebug.o gntft.o finch.o gntidle.o gntnotify.o gntplugin.o gntpounce.o
gntprefs.o gntrequest.o gntsound.o
On Wed, Aug 08, 2007 at 11:47:56AM -0400, Peter Thoenen wrote:
I hate to call Rui out in public but he is the maintainer here and very
non responsive to private emails about this.
Tor 1.1.x has BEEN DEPRECIATED from before the time 4.1 STABLE was
released (you were notified of this also Rui) and
I agree with you on this -current/-stable thingy. This ports tree
soft locking shit *how we care about -stable users* is bullshit,
when outdated/security vulnerable stuff is even in -current and
it takes ages to backport and make packages of needed security updates...
I see there no logic,
* Peter Thoenen [2007-08-08]:
Tor 1.1.x has BEEN DEPRECIATED from before the time 4.1 STABLE was
Tor 1.2 only came out around the release of 4.1 and no update was marked
a security update, so there was no reason to update the -stable ports.
We have our policies and we do have them for a good
On 08/08 04:30, steven mestdagh wrote:
Jeremy Evans [2007-08-07, 14:26:22]:
The attached patch fixes qtruby (part of kdebindings) so that it can
be used out of the box. Currently, when building kdebindings, .0.0
are added to the ruby .so extensions. Ruby assumes that .so
extensions
Mike Swanson [2007-08-08, 10:14:52]:
Hi,
I'm using an OpenBSD snapshot from 2007-08-06, and when I'm trying to update
pidgin, it ends up like this:
cc -O2 -pipe -o .libs/finch gntaccount.o gntblist.o gntconn.o gntconv.o
gntdebug.o gntft.o finch.o gntidle.o gntnotify.o gntplugin.o
I am sorry do get my hands dirty with a thread like that but I just can't
help my self.
The only thing I thought of when reading peters post was:
Why the hell didn't he send a patch to the maintainer?
-Julian
--
Lubarsky's Law of Cybernetic Entomology:
There's always one more bug.
Julian Frede wrote:
I am sorry do get my hands dirty with a thread like that but I just can't
help my self.
The only thing I thought of when reading peters post was:
Why the hell didn't he send a patch to the maintainer?
because he's busy sucking on a bag of dicks.
-Julian
--
Hi there,
On 03/08/2007, Joachim Schipper [EMAIL PROTECTED] wrote:
On Fri, Aug 03, 2007 at 11:11:57AM +0100, Edd Barrett wrote:
Whilst testing disc-cover-1.5.2p1 (-current) with texlive, I am unable
to have disc-cover read the cdrom drive. It has correctly guessed the
device node, but is
25 matches
Mail list logo
