Bug#870575: robotfindskitten: New upstream version: 2.7182818.701

2017-08-02 Thread Steve Pomeroy
Package: robotfindskitten
Version: 1.7320508.406-5+b1
Severity: normal

Dearest Esteemed Maintainer,

A new version of robotfindskitten awaits you in the off-world colonies.
Please send a self-addressed, stamped envelope to:

https://sourceforge.net/projects/rfk/

to retrieve a free game piece. Your mileage may vary. Please enter
2.7182818.701 at the prompt followed by the pound key. Past performance
is not indicative of future results.

Thank you and goodnight.

-Steve



Bug#861763: inkscape: Launching in tiling WM (Awesome) causes corrupt UI

2017-05-03 Thread Steve Pomeroy
Package: inkscape
Version: 0.92.1-1
Severity: normal

Dear Maintainer,

Using AwesomeWM as my window manager in one of the tiling modes causes
Inkscape's UI to be corrupted. If I use the floating mode (where
Inkscape can set its own size / position on the screen), everything
works normally.

When launching Inkscape in one of Awesome's tiling modes, the UI is
somewhat responsive some of the time, but doesn't appear to redraw the
entire window. For example, zooming in/out will redraw the ruler, but
not the editing area. Eventually Inkscape stops responding to UI input
(I
haven't been able to trace what causes it to stop responding).

This seems to only happen when launching Inkscape: if I start Inkscape
from the floating mode and I switch to a tiling mode, everything works
fine even if I resize the window.

My suspicion is that Inkscape and Awesome are fighting over window
sizes when originally creating the window and Inkscape is holding on to
the assumption that it got the size it requested.

In addition to this (which could be related?): Inkscape has the bad
habit of putting itself on my 2nd monitor after loading a file for no
obvious reason. For example, I can load up Inkscape on my primary
monitor, open another file and the new window will appear on the 2nd
monitor.

This is AwesomeWM 4.0.0.0~git63-g6896a0aa

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages inkscape depends on:
ii  libaspell150.60.7~20110707-3+b2
ii  libatk1.0-02.22.0-1
ii  libatkmm-1.6-1v5   2.24.2-2
ii  libc6  2.24-10
ii  libcairo2  1.14.8-1
ii  libcairomm-1.0-1v5 1.12.0-1+b1
ii  libcdr-0.1-1   0.1.3-3+b1
ii  libdbus-1-31.10.18-1
ii  libdbus-glib-1-2   0.108-2
ii  libfontconfig1 2.11.0-6.7+b1
ii  libfreetype6   2.6.3-3.2
ii  libgc1c2   1:7.4.2-8
ii  libgcc11:6.3.0-14
ii  libgdk-pixbuf2.0-0 2.36.5-2
ii  libglib2.0-0   2.50.3-2
ii  libglibmm-2.4-1v5  2.50.0-1
ii  libgomp1   6.3.0-14
ii  libgsl22.3+dfsg-1
ii  libgtk2.0-02.24.31-2
ii  libgtkmm-2.4-1v5   1:2.24.5-1
ii  libgtkspell0   2.0.16-1.1
ii  libjpeg62-turbo1:1.5.1-2
ii  liblcms2-2 2.8-4
ii  libmagick++-6.q16-78:6.9.7.4+dfsg-6
ii  libmagickcore-6.q16-3  8:6.9.7.4+dfsg-6
ii  libmagickwand-6.q16-3  8:6.9.7.4+dfsg-6
ii  libpango-1.0-0 1.40.5-1
ii  libpangocairo-1.0-01.40.5-1
ii  libpangoft2-1.0-0  1.40.5-1
ii  libpangomm-1.4-1v5 2.40.1-3
ii  libpng16-161.6.28-1
ii  libpoppler-glib8   0.48.0-2
ii  libpoppler64   0.48.0-2
ii  libpopt0   1.16-10+b2
ii  libpotrace01.13-3
ii  librevenge-0.0-0   0.0.4-6
ii  libsigc++-2.0-0v5  2.10.0-1
ii  libstdc++6 6.3.0-14
ii  libvisio-0.1-1 0.1.5-4+b1
ii  libwpg-0.3-3   0.3.1-3
ii  libx11-6   2:1.6.4-3
ii  libxml22.9.4+dfsg1-2.2
ii  libxslt1.1 1.1.29-2.1
pn  python:any 
ii  zlib1g 1:1.2.8.dfsg-5

Versions of packages inkscape recommends:
ii  aspell   0.60.7~20110707-3+b2
ii  fig2dev [transfig]   1:3.2.6a-2
ii  imagemagick  8:6.9.7.4+dfsg-6
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-6
ii  libimage-magick-perl 8:6.9.7.4+dfsg-6
ii  libwmf-bin   0.2.8.4-10.6
ii  python-lxml  3.7.1-1
ii  python-numpy 1:1.12.1-2
ii  python-scour 0.32-2
ii  transfig 1:3.2.6a-2

Versions of packages inkscape suggests:
ii  dia  0.97.3+git20160930-5
pn  libsvg-perl  
pn  libxml-xql-perl  
pn  pstoedit 
pn  python-uniconvertor  
ii  ruby 1:2.3.3

-- no debconf information



Bug#789215: astyle: new upstream version (2.05.1)

2015-06-18 Thread Steve Pomeroy
Package: astyle
Version: 2.04-1
Severity: normal

Dear Maintainer,

There is a new version of astyle available that fixes a number of
formatting issues that come up when formatting C++11 source. It also
adds a bunch of useful features, like dry-run.

-Steve Pomeroy


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#780046: DistributionNotFound: virtualenv==1.11.6 error

2015-04-15 Thread Steve Pomeroy
It seems as though virtualenv should depend on python3-pkg-resources =
5.5.1-1 (that's the version that worked for me).



signature.asc
Description: OpenPGP digital signature


Bug#738736: cryptmount: Placeholder @ETCDIR@ appears in /usr/sbin/cryptmount-setup

2014-02-12 Thread Steve Pomeroy
Package: cryptmount
Version: 4.5-1
Severity: important

Dear Maintainer,

The placeholder text @ETCDIR@ appears in /usr/sbin/cryptmount-setup
instead of the path /etc/cryptmount/ causing the cryptmount-setup
script to fail when it attempts to save the cmtab and key. Cheers.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cryptmount depends on:
ii  libc6   2.17-97
ii  libdevmapper1.02.1  2:1.02.83-1
ii  libgcrypt11 1.5.3-3
ii  libuuid12.20.1-5.6

Versions of packages cryptmount recommends:
ii  udev  204-6

Versions of packages cryptmount suggests:
ii  dmsetup  2:1.02.83-1
ii  openssl  1.0.1f-1

-- Configuration Files:
/etc/cryptmount/cmtab changed [not included]

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#735126: darktable: add LUA support

2014-01-12 Thread Steve Pomeroy
Package: darktable
Version: 1.4-1
Severity: minor

Dear Maintainer,

The new version of Darktable (1.4) introduces LUA support. In fact, the
release notes as shipped with this version in Debian mention that this
feature is available.

Is it possible to add LUA support or, if not, to put a note in somewhere
mentioning that it's been disabled? Hopefully this will help anyone
looking to try out this new feature.

Cheers,
Steve

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages darktable depends on:
ii  gtk2-engines  1:2.20.2-3
ii  libatk1.0-0   2.10.0-2
ii  libc6 2.17-97
ii  libcairo2 1.12.16-2
ii  libcolord11.0.5-1
ii  libcurl3-gnutls   7.34.0-1
ii  libexiv2-12   0.23-1
ii  libflickcurl0 1.24-1
ii  libgcc1   1:4.8.2-10
ii  libgdk-pixbuf2.0-02.28.2-1+b1
ii  libgl1-mesa-glx [libgl1]  9.2.2-1
ii  libglib2.0-0  2.36.4-1
ii  libglu1-mesa [libglu1]9.0.0-2
ii  libgnome-keyring0 3.4.1-1
ii  libgomp1  4.8.2-10
ii  libgphoto2-2  2.4.14-2.4
ii  libgphoto2-port0  2.4.14-2.4
ii  libgtk2.0-0   2.24.22-1
ii  libice6   2:1.0.8-2
ii  libilmbase6   1.0.1-6
ii  libjpeg8  8d-2
ii  libjs-prototype   1.7.1-3
ii  libjs-scriptaculous   1.9.0-2
ii  libjson-glib-1.0-00.16.2-1
ii  liblcms2-22.2+git20110628-2.3+b1
ii  liblensfun0   0.2.8-1
ii  libopenexr6   1.6.1-7
ii  libpango-1.0-01.36.0-1+b1
ii  libpangocairo-1.0-0   1.36.0-1+b1
ii  libpng12-01.2.49-5
ii  librsvg2-22.40.0-1
ii  libsdl1.2debian   1.2.15-8
ii  libsm62:1.2.1-2
ii  libsoup2.4-1  2.44.2-1
ii  libsqlite3-0  3.8.2-1
ii  libstdc++64.8.2-10
ii  libtiff5  4.0.3-7
ii  libx11-6  2:1.6.2-1
ii  libxext6  2:1.3.2-1
ii  libxml2   2.9.1+dfsg1-3
ii  zlib1g1:1.2.8.dfsg-1

darktable recommends no packages.

darktable suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#540206: ttf-mgopen: MgOpen Canonica hinting looks terrible

2009-08-06 Thread Steve Pomeroy
Package: ttf-mgopen
Version: 1.1-3
Severity: normal

The text rendering of the font MgOpen Canonica looks terrible at small
sizes (really, at any size below 20). I suspect this is due to broken
hinting.

An example of some characters at size 8:
http://staticfree.info/oldshots/scap-1249571981.png

Gnome font settings: 

Resolution: 106dpi
Smoothing: greyscale
Hinting: full
Rendering: best shapes

With hinting turned off, it becomes blurry, but the shapes make more
sense:
http://staticfree.info/oldshots/scap-1249572381.png

If this is only intended to be a print font, it would probably be a good
idea to make it so it isn't shown on the screen using some defoma rules.

To give a reference for what this looks like in body text, please see
the following: 
http://staticfree.info/oldshots/scap-1249572860.png

For whatever reason (I suspect torment), the author of the blog decided
to specify this font in particular in their CSS. It'd be nice if even
maliciously-intended CSS writers couldn't hurt users' eyes in this way.

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (900, 'stable'), (300, 'testing'), (150, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ttf-mgopen depends on:
ii  defoma   0.11.10-0.2 Debian Font Manager -- automatic f

Versions of packages ttf-mgopen recommends:
ii  fontconfig2.6.0-3generic font configuration library
ii  x-ttcidfont-conf  31 TrueType and CID fonts configurati

ttf-mgopen suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#524475: wishlist: include brief syntax reference in man page

2009-04-17 Thread Steve Pomeroy
Package: unison
Version: 2.13.16-5
Severity: wishlist


I always find myself needing to dig up the main unison documentation
when doing a sync over ssh, as the URI syntax is different than ssh/scp.
It would be nice if there were a brief syntax reference for the various
root types in the man page as a quick reminder. Perhaps:

Unison roots can be specified in the following way:

  root ::= [protocol:]//[u...@][host][:port][/path]
   |  path

  protocol ::= file
|  socket
|  ssh
|  rsh
 
Or perhaps a little more human-friendly way :-)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#486886: libapache2-modxslt: Removal of advertisement on documents generated with modxslt

2008-06-18 Thread Steve Pomeroy
Package: libapache2-modxslt
Version: 2005072700-2.2
Severity: minor

Modxslt adds a rather large commented out Generated by modxslt block
at the bottom of all the documents it generates. Normally, this isn't
too much of a problem as it just appears at the bottom of one's documents
and out of the way. However, I've been using mod xslt to process documents
that are included in other documents, which puts multiple copies of this
notice throughout my documents. As these are public on the web, this is
not really ideal.

I've included a very tiny patch that adds the appropriate define to
disable these notices.

--
Steve Pomeroy
diff -Naur modxslt-2005072700.orig/debian/rules modxslt-2005072700/debian/rules
--- modxslt-2005072700.orig/debian/rules	2008-06-18 14:56:55.0 -0400
+++ modxslt-2005072700/debian/rules	2008-06-18 14:47:11.0 -0400
@@ -15,7 +15,7 @@
 DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 
-CFLAGS = -Wall -g
+CFLAGS = -Wall -g -DMXSLT_DISABLE_SIGNATURE
 
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
 	CFLAGS += -O0


Bug#471230: drupal5: cron patch for multi site configuration

2008-05-05 Thread Steve Pomeroy
This patch works great on my system and it would be a big help if this
could go forward. I've turned the above solution into a proper patch if
that helps at all.

-- 
Steve Pomeroy
http://staticfree.info/
--- cron.sh.orig	2008-05-05 12:11:30.0 -0400
+++ cron.sh	2008-05-05 12:11:21.0 -0400
@@ -1,17 +1,17 @@
 #!/bin/sh
 # $Id: cron.sh 1878 2008-02-12 10:56:45Z luigi $
 
+BASE_URL=
 for site in /etc/drupal/5/sites/* ; do
-	BASE_URL=
-
 	for file in $site/baseurl.php $site/settings.php; do
 		[ -f $file ]  BASE_URL=`grep '^$base_url' $file | cut -d' -f2`
 		[ X$BASE_URL != X ]  break
 	done
 
-	if [ X$BASE_URL = X ] ; then
-		BASE_URL='http://localhost/drupal5'
-	fi
-
 	curl --silent --compressed --location $BASE_URL/cron.php
 done
+
+# no site found with base_url - fall back to localhost (only once)
+if [ X$BASE_URL = X ] ; then
+	BASE_URL='http://localhost/drupal5'
+fi


signature.asc
Description: Digital signature


Bug#471317: sjoerd's debs work on TP x61s

2008-03-25 Thread Steve Pomeroy
sjoerd's debs fix the problem on a ThinkPad X61s 2.6.24-1-amd64 with
debian/testing

-- 
Steve Pomeroy
http://staticfree.info/


signature.asc
Description: Digital signature


Bug#395487: me too

2007-10-02 Thread Steve Pomeroy
Just got bit by this bug, after installing a bunch of fonts in a batch.

I agree with all the previous posters: can this font be renamed? 
I don't wish this headache on anyone else.

-- 
Steve Pomeroy
http://staticfree.info/


signature.asc
Description: Digital signature


Bug#404845: ion3: dock gets focus

2006-12-28 Thread Steve Pomeroy
Package: ion3
Version: 20061029-3
Severity: normal

As mentioned by another person in this post:
http://www.mail-archive.com/ion-general@lists.berlios.de/msg01422.html

The dock receives focus when activated and thus causes any newly spawned 
windows to appear inside the dock. These windows cannot easily be
focused again without mouse gymnastics, making ion3 very unusable 
when the dock is enabled.

This was stated to be fixed in a version very near the version presently 
in testing, so hopefully it would be simple to patch before release.


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (600, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages ion3 depends on:
ii  gnome-terminal [x-terminal- 2.14.2-1 The GNOME 2 terminal emulator appl
ii  libc6   2.3.6.ds1-8  GNU C Library: Shared libraries
ii  libice6 1:1.0.1-2X11 Inter-Client Exchange library
ii  liblua5.1-0 5.1.1-2  Simple, extensible, embeddable pro
ii  libsm6  1:1.0.1-3X11 Session Management library
ii  libx11-62:1.0.3-4X11 client-side library
ii  libxext61:1.0.1-2X11 miscellaneous extension librar
ii  libxinerama11:1.0.1-4.1  X11 Xinerama extension library
ii  rxvt-unicode [x-terminal-em 7.9-2RXVT-like terminal emulator with U
ii  xfce4-terminal [x-terminal- 0.2.5.6rc1-2 Xfce terminal emulator

Versions of packages ion3 recommends:
ii  xfonts-100dpi 1:1.0.0-3  100 dpi fonts for X
ii  xfonts-75dpi  1:1.0.0-3  75 dpi fonts for X

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#364944: problem with X?

2006-04-28 Thread Steve Pomeroy
I get the exact same effect (although it doesn't lock up the computer,
just kills X) by doing this:

$ gconftool-2 --type list --list-type string --set
/desktop/gnome/peripherals/keyboard/kbd/options '[ctrl ctrl:nocaps]'

which obviously shouldn't result in a crash of X. I came up with this
value, as gnome-keyboard-properties tried to do the same thing.

Of course, no client activity should cause X to crash, so perhaps the
problem should be directed there.

I noticed that some of my other systems have
/desktop/gnome/peripherals/keyboard/xkb instead of
/desktop/gnome/peripherals/keyboard/kbd . Perhaps that's related?

for the record:

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (600, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages gnome-control-center depends on:
ii  capplets-data1:2.12.3-2  configuration applets for
GNOME 2
ii  desktop-file-utils   0.10-1  Utilities for .desktop files
ii  gnome-desktop-data   2.14.0-1Common files for GNOME 2
desktop a
ii  gnome-icon-theme 2.14.2-1GNOME Desktop icon theme
ii  gnome-menus  2.12.0-2.1  an implementation of the
freedeskt
ii  libart-2.0-2 2.3.17-1Library of functions for 2D
graphi
ii  libatk1.0-0  1.11.3-1The ATK accessibility toolkit
ii  libaudiofile00.2.6-6 Open-source version of
SGI's audio
ii  libavahi-client3 0.6.9-8 Avahi client library
ii  libavahi-common3 0.6.9-8 Avahi common library
ii  libavahi-compat-howl00.6.9-8 Avahi Howl compatibility
library
ii  libbonobo2-0 2.14.0-1Bonobo CORBA interfaces library
ii  libbonoboui2-0   2.14.0-1The Bonobo UI library
ii  libc62.3.6-7 GNU C Library: Shared libraries
ii  libcairo21.0.4-1+b1  The Cairo 2D vector
graphics libra
ii  libdbus-1-2  0.61-5  simple interprocess
messaging syst
ii  libebook1.2-51.4.2.1-2   Client library for
evolution addre
ii  libesd0  0.2.36-3Enlightened Sound Daemon -
Shared
ii  libfam0  2.7.0-9 Client library to control
the FAM
ii  libfontconfig1   2.3.2-5.1   generic font configuration
library
ii  libfreetype6 2.1.10-1FreeType 2 font engine,
shared lib
ii  libgconf2-4  2.14.0-1GNOME configuration
database syste
ii  libgcrypt11  1.2.2-1 LGPL Crypto library -
runtime libr
ii  libglade2-0  1:2.5.1-2   library to load .glade
files at ru
ii  libglib2.0-0 2.10.2-1The GLib library of C routines
ii  libgnome-desktop-2   2.14.0-1Utility library for loading
.deskt
ii  libgnome-keyring00.4.9-1 GNOME keyring services library
ii  libgnome-menu2   2.12.0-2.1  an implementation of the
freedeskt
ii  libgnome2-0  2.14.0-2The GNOME 2 library -
runtime file
ii  libgnomecanvas2-02.14.0-1A powerful object-oriented
display
ii  libgnomeui-0 2.14.0-1The GNOME 2 libraries (User
Interf
ii  libgnomevfs2-0   2.14.0-2GNOME virtual file-system
(runtime
ii  libgnutls11  1.0.16-14+b1GNU TLS library - runtime
library
ii  libgpg-error01.2-1   library for common error
values an
ii  libgstreamer-plugins0.8- 0.8.12-1Various GStreamer libraries
and li
ii  libgstreamer0.8-00.8.12-1Core GStreamer libraries,
plugins,
ii  libgtk2.0-0  2.8.16-1The GTK+ graphical user
interface
ii  libice6  6.9.0.dfsg.1-6  Inter-Client Exchange library
ii  libjpeg626b-12   The Independent JPEG
Group's JPEG
ii  libmetacity0 1:2.12.3-3  library of lightweight GTK2
based
ii  libnautilus-extension1   2.12.2-2libraries for nautilus
components
ii  liborbit21:2.14.0-1  libraries for ORBit2 - a
CORBA ORB
ii  libpango1.0-01.12.1-2Layout and rendering of
internatio
ii  libpng12-0   1.2.8rel-5  PNG library - runtime
ii  libpopt0 1.7-5   lib for parsing cmdline
parameters
ii  libsm6   6.9.0.dfsg.1-6  X Window System Session
Management
ii  libstartup-notification0 0.8-1   library for program launch
feedbac
ii  libtasn1-2   1:0.2.17-2  Manage ASN.1 structures
(runtime)
ii  libx11-6 6.9.0.dfsg.1-6  X Window System protocol
client li
ii  libxcursor1  1.1.3-1 X cursor management library
ii  libxext6 6.9.0.dfsg.1-6  X Window System
miscellaneous exte
ii  libxft2  2.1.8.2-5.1 FreeType-based font 

Bug#299697: fontconfig: Still unresolved

2006-04-21 Thread Steve Pomeroy
On Fri, Apr 21, 2006 at 09:24:50AM +0200, Josselin Mouette wrote:
 Le jeudi 20 avril 2006 à 19:41 -0400, Steve Pomeroy a écrit :
  Package: fontconfig
  Version: 2.3.2-5.1
  Followup-For: Bug #299697
  
  
  fontconfig just updated my /etc/fonts/font.conf file, reminding
  me that this bug is still unresolved.
  
  Does anyone have any further info on this issue? 
 
 There are lots of things in this bug report, so I'd like to make them
 clear.
 
 Most contributors to this thread noticed that the URW fonts had replaced
 the Bitstream fonts in Firefox/epiphany. This is caused by the Mozilla
 suite replacing the sans-serif and serif aliases by Helvetica and
 Times. We will not include a broken patch from Ubuntu for fontconfig
 when the bug is in Mozilla; it has been fixed in xulrunner 1.8.0.1-3. I
 don't know whether it has been fixed in firefox as well, but it is only
 a matter of porting the same patch.

Perhaps I'm mistaken, but the problem wasn't the default font for
Firefox, etc. but that websites would specify Helvetica and Times in
their CSS, which would then use the Nimbus fonts. That's certainly the
case for myself, anyhow. (My Firefox default has always been the 
generic 'sans', etc.)

Keith: I think your suggestions are much more sane than the current
default. I've been simply putting a ban on the Nimbus family, but I
imagine others are not so keen on that ;-)

Perhaps this is really a bug report for the Nimbus fonts themselves? I
mean, I can understand why a metric and shape compatible font is such
a good thing, but why does it have to render poorly in certain contexts?
In fact, what contexts *do* the render well?

 I'd like to know whether the original bug report (ugly fonts at small
 sizes) is the same. You can check the latest epiphany package, in which
 I'm sure the DejaVu fonts are correctly used by default. You can also
 try with removing the gsfonts-x11 package.

DejaVu has been recently rendering poorly as well, so I don't think that
helps much. But that's for another bug report ;-)

 Regards,
 -- 
  .''`.   Josselin Mouette/\./\
 : :' :   [EMAIL PROTECTED]
 `. `'[EMAIL PROTECTED]
`-  Debian GNU/Linux -- The power of freedom
 
 

-- 
Steve Pomeroy
http://staticfree.info/



Bug#299697: fontconfig: Still unresolved

2006-04-20 Thread Steve Pomeroy
Package: fontconfig
Version: 2.3.2-5.1
Followup-For: Bug #299697


fontconfig just updated my /etc/fonts/font.conf file, reminding
me that this bug is still unresolved.

Does anyone have any further info on this issue? 

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages fontconfig depends on:
ii  defoma0.11.8-0.1 Debian Font Manager -- automatic f
ii  fontconfig-config 2.3.2-5.1  generic font configuration library
ii  libc6 2.3.6-7GNU C Library: Shared libraries
ii  libfontconfig12.3.2-5.1  generic font configuration library

fontconfig recommends no packages.

-- debconf information:
  fontconfig/subpixel_rendering: Automatic
  fontconfig/enable_bitmaps: false
  fontconfig/hinting_type: Native


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#360925: INSTALL REPORT

2006-04-05 Thread Steve Pomeroy
Package: installation-reports

INSTALL REPORT

Debian-installer-version: 2006-04-04 from
http://cdimage.debian.org/debian-cd/3.1_r1/i386/iso-cd/debian-31r1a-i386-businesscard.iso
uname -a: Linux debian.example.com 2.6.8-2-686 #1 Tue Aug 16 13:22:48
UTC 2005 i686 GNU/Linux
Date: 2006-04-04 14:29:01 EDT
Method: booted from the CD-ROM, used 'linux26' from the boot prompt.
Mirror from http://debian.lcs.mit.edu/debian

Machine: HP ML370 G3
Processor: Intel(R) Pentium(R) III CPU family  1266MHz
Memory: MemTotal:  1816820 kB
Root Device: SCSI RAID, /dev/cciss/c0d0
Root Size/partition table:
major minor  #blocks  name

 104 0   17780640 cciss/c0d0
 104 1 273073 cciss/c0d0p1
 104 2  1 cciss/c0d0p2
 104 54883728 cciss/c0d0p5
 104 62931831 cciss/c0d0p6
 104 71180746 cciss/c0d0p7
 104 8 393561 cciss/c0d0p8
 104 98112793 cciss/c0d0p9

Output of lspci and lspci -n:
:00:00.0 Host bridge: ServerWorks CNB20HE Host Bridge (rev 23)
:00:00.1 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
:00:00.2 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
:00:00.3 Host bridge: ServerWorks CNB20HE Host Bridge (rev 01)
:00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
100] (rev 08)
:00:05.0 VGA compatible controller: ATI Technologies Inc Rage XL
(rev 27)
:00:06.0 System peripheral: Compaq Computer Corporation Advanced
System Management Controller
:00:0f.0 ISA bridge: ServerWorks OSB4 South Bridge (rev 51)
:00:0f.1 IDE interface: ServerWorks OSB4 IDE Controller
:07:03.0 RAID bus controller: Compaq Computer Corporation Smart
Array 5300 Controller (rev 02)
:07:07.0 PCI Hot-plug controller: Compaq Computer Corporation PCI
Hotplug Controller (rev 12)

:00:00.0 0600: 1166:0008 (rev 23)
:00:00.1 0600: 1166:0008 (rev 01)
:00:00.2 0600: 1166:0006 (rev 01)
:00:00.3 0600: 1166:0006 (rev 01)
:00:02.0 0200: 8086:1229 (rev 08)
:00:05.0 0300: 1002:4752 (rev 27)
:00:06.0 0880: 0e11:a0f0
:00:0f.0 0601: 1166:0200 (rev 51)
:00:0f.1 0101: 1166:0211
:07:03.0 0104: 0e11:b060 (rev 02)
:07:07.0 0804: 0e11:a0f7 (rev 12)

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[E]
Reboot: [O]

Comments/Problems:

There was an error installing grub to the boot sector of the
SCSI RAID (/dev/cciss/c0d0). I tried LILO instead, and that worked
on the first try.

The complete error with grub was (accepting all the defaults):
Apr  4 14:44:01 grub-installer: info: Installing grub on '(hd0)'
Apr  4 14:44:01 grub-installer: info: grub-install supports --no-floppy
Apr  4 14:44:01 grub-installer: info: Running chroot /target
/sbin/grub-install --recheck --no-floppy 
(hd0)
Apr  4 14:44:09 grub-installer: error: Running 'grub-install
--recheck --no-floppy (hd0)' failed.
Apr  4 14:44:48 main-menu[504]: WARNING **: Configuring
'grub-installer' failed with error code 1
Apr  4 14:44:48 main-menu[504]: WARNING **: Menu item
'grub-installer' failed.

I tried specifying the SCSI RAID by device, but that also failed:
Apr  4 14:47:28 grub-installer: info: Installing grub on
'/dev/cciss/c0d0'
Apr  4 14:47:28 grub-installer: info: grub-install supports --no-floppy
Apr  4 14:47:28 grub-installer: info: Running chroot /target
/sbin/grub-install --recheck --no-floppy 
/dev/cciss/c0d0
Apr  4 14:47:36 grub-installer: error: Running 'grub-install
--recheck --no-floppy /dev/cciss/c0d0' failed.
Apr  4 14:47:38 main-menu[504]: WARNING **: Configuring
'grub-installer' failed with error code 1
Apr  4 14:47:38 main-menu[504]: WARNING **: Menu item
'grub-installer' failed.

I installed LILO into the boot sector, which worked just fine.

I've been increasingly pleased with Debian's installer. I was able to
get a system with *very* minimal packages installed in about an hour, on
a machine that I had never worked with before. I was worried about the
RAID, but it was detected and used automagically (except for the above
weirdness).

The auto partitioner is one of my favorite new additions, as that was
always a step that took some manual computation.

Thanks Debian :-)

Install logs and other status info is available in
/var/log/debian-installer/.
Once you have filled out this report, mail it to [EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#340061: hnb: cannot manually recover from binary autosave

2005-11-20 Thread Steve Pomeroy
Package: hnb
Version: 1.9.18-3.1
Severity: normal

The default format for autosave is a binary dump of the working
document. Unfortunately, this does not always work very well and
occasionally the recovery file would be empty. Additionally, one could
not simply do a diff of the recover file and the save file in order to
check for differences.

Lastly, the autosave file uses a non-standard naming convention causing
CVS and Nautilus not ignore the recovery file. Something like 
#filename.hnb# would follow the more common naming convention.

Attached is a patch that:

* saves recovery files in hnb's native format to prevent binary
  corruption.
* names recovery files #file.hnb# instead of file.hnb_hnb_rescue

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages hnb depends on:
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  libncurses5   5.4-9  Shared libraries for terminal hand

hnb recommends no packages.

-- no debconf information
diff -Naur original/hnb-1.9.18/src/autosave.c hnb-1.9.18/src/autosave.c
--- original/hnb-1.9.18/src/autosave.c	2005-11-20 11:45:03.0 -0500
+++ hnb-1.9.18/src/autosave.c	2005-11-20 11:12:41.0 -0500
@@ -38,7 +38,7 @@
 		{
 			char buf[4096];
 			
-			sprintf (buf, export_binary %s_hnb_rescue, prefs.db_file);		
+			sprintf (buf, export_hnb #%s#, prefs.db_file);		
 			docmd (node_root(pos), buf);
 			cli_outfunf(autosaved, %i nodes changed\n,nodes_changed);
 		}
diff -Naur original/hnb-1.9.18/src/file.c hnb-1.9.18/src/file.c
--- original/hnb-1.9.18/src/file.c	2005-11-20 11:45:03.0 -0500
+++ hnb-1.9.18/src/file.c	2005-11-20 11:23:43.0 -0500
@@ -164,7 +164,7 @@
 			char buf[4096];
 			char swapfile[4096];
 
-			sprintf(swapfile,%s_hnb_rescue,prefs.db_file);
+			sprintf(swapfile,#%s#,prefs.db_file);
 			remove(swapfile);
 			docmd (pos, autosave_threshold_nodes_changed 0);
 
diff -Naur original/hnb-1.9.18/src/hnb.c hnb-1.9.18/src/hnb.c
--- original/hnb-1.9.18/src/hnb.c	2003-08-26 22:50:58.0 -0400
+++ hnb-1.9.18/src/hnb.c	2005-11-20 11:39:11.0 -0500
@@ -239,7 +239,7 @@
 	   	  stat(prefs.db_file, statbuf);
 		  file_modified=statbuf.st_ctime;
 		  
-		  sprintf(recovery_file, %s_hnb_rescue, prefs.db_file);
+		  sprintf(recovery_file, #%s#, prefs.db_file);
 		  tfile = fopen(recovery_file, r);
 		  if(tfile){
 			  char response[1024]=_;
@@ -314,7 +314,7 @@
 		{
 			char buf[4096];
 			if(recover)
-			sprintf (buf, import_binary %s, file_to_load);
+			sprintf (buf, import_hnb %s, file_to_load);
 			else
 			sprintf (buf, import_%s %s, prefs.format,  file_to_load);
 


Bug#339106: whereami: testap has inverted logic for madwifi test

2005-11-14 Thread Steve Pomeroy
Package: whereami
Version: 0.3.28
Severity: normal

The tests/testap script has two inverted string tests for the madwifi
detection. This causes whereami to not bring up the wireless interface
properly. Attached is a patch to correct the two lines.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (700, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages whereami depends on:
ii  debconf [debconf-2.0]   1.4.58   Debian configuration management sy
ii  dhcp-client 2.0pl5-19.1  DHCP Client
ii  iputils-ping3:20020927-3 Tools to test the reachability of 
ii  netbase 4.23 Basic TCP/IP networking system
ii  perl5.8.7-7  Larry Wall's Practical Extraction 

Versions of packages whereami recommends:
ii  iputils-arping  3:20020927-3 Tool to send ICMP echo requests to
ii  resolvconf  1.33 nameserver information handler
ii  wireless-tools  27+28pre10-1 Tools for manipulating Linux Wirel

-- debconf information:
* whereami/how_to_configure:
--- tests/testap2005-09-18 06:37:24.0 -0400
+++ /usr/share/whereami/tests/testap2005-11-14 17:45:43.0 -0500
@@ -81,7 +81,7 @@
 scan_for_ap()
 {
   MAXATTEMPTS=4
-  if [ ! -z $ISMADWIFI ] ; then
+  if [ ! -n $ISMADWIFI ] ; then
 # For reliable scanning, the interface needs to be down, and
 # then brought up for (at least) 4 seconds.
 # - true as at madwif + kernel 2.6.10, 29 December 2004
@@ -108,7 +108,7 @@
   done
 
 
-  if [ ! -z $ISMADWIFI ] ; then
+  if [ ! -n $ISMADWIFI ] ; then
 # Put the interface back how we found it...
 # except we won't do this on the MADWIFI, because the driver
 # doesn't seem to support a non-destructive scan anyway :-(