Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem

2006-09-24 Thread H. S.
On 9/22/06, Hamish Moffatt [EMAIL PROTECTED] wrote:
On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote: (here is the bug again here for geda-gschem, instead of for geda)Thanks. geda-gschem 20060906 should be in etch in a day or two. Can youtry it again then and see if the problem is solved?
I updated the geda packages last night. I have tried playing around with gschem for a while and the problems I was facing have gone.Here the versions I now have:$ dpkg -l *geda* | grep ^ii
ii geda 20060123-1 GNU EDA -- Electronics design softwareii geda-doc 20060906-1 Documentation for GNU EDA -- Electronics desii geda-examples 20060906-1 GNU EDA -- Electronics design software -- ex
ii geda-gattrib 20060906-1 GNU EDA -- Electronics design software -- atii geda-gnetlist 20060906-1 GNU EDA -- Electronics design software -- neii geda-gschem 20060906-1 GNU EDA -- Electronics design software -- sc
ii geda-gsymcheck 20060906-1 GNU EDA -- Electronics design software -- syii geda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design soii geda-utils 20060906-1 GNU EDA -- Electronics design software -- ut
ii libgdgeda6 2.0.15-3 GNU EDA -- Electronics design software -- gdii libgeda20 20060906-1 GNU EDA -- Electronics design software -- liThanks a ton for solving the problem. Your help is much appreciated.
regards,-HSsystem-gafrc is provided by geda-symbols, which is already updated in
etch. However system-gschemrc is not yet. I suspect the skew betweenthem is causing the problem. I will tighten the dependencies in thefuture. iigeda-gschem20060123-1 GNU EDA -- Electronics design software --
 sc iigeda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design sothanks,Hamish--Hamish Moffatt VK3SB [EMAIL PROTECTED]
 [EMAIL PROTECTED]


Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem

2006-09-22 Thread Steve Langasek
On Fri, Sep 22, 2006 at 03:22:17PM +1000, Hamish Moffatt wrote:
 On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote:
  (here is the bug again here for geda-gschem, instead of for geda)

 Thanks. geda-gschem 20060906 should be in etch in a day or two.

Not if this RC bug is open, it won't be.

 system-gafrc is provided by geda-symbols, which is already updated in
 etch. However system-gschemrc is not yet. I suspect the skew between
 them is causing the problem. I will tighten the dependencies in the
 future.

If you're certain that this is the cause, which package needs to be updated
with added conflicts -- geda-symbols or geda-gschem?  If it's geda-symbols,
could you please reassign this bug there?  If the change needs to be made to
geda-gschem, please say so and I'll override this RC bug for the update into
testing for now.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


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



Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem

2006-09-22 Thread Hamish Moffatt
reassign 388695 geda-symbols
thanks

On Thu, Sep 21, 2006 at 11:50:42PM -0700, Steve Langasek wrote:
 On Fri, Sep 22, 2006 at 03:22:17PM +1000, Hamish Moffatt wrote:
  On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote:
   (here is the bug again here for geda-gschem, instead of for geda)
  Thanks. geda-gschem 20060906 should be in etch in a day or two.
 Not if this RC bug is open, it won't be.

Good to know.

  system-gafrc is provided by geda-symbols, which is already updated in
  etch. However system-gschemrc is not yet. I suspect the skew between
  them is causing the problem. I will tighten the dependencies in the
  future.
 
 If you're certain that this is the cause, which package needs to be updated
 with added conflicts -- geda-symbols or geda-gschem?  If it's geda-symbols,
 could you please reassign this bug there?  If the change needs to be made to
 geda-gschem, please say so and I'll override this RC bug for the update into
 testing for now.

Well, upgrading geda-gschem will certainly get it working. As to where
the change belongs I'm not sure -- basically the two packages need to
have matched versions. So either geda-gschem (and geda-gnetlist,
gsymcheck, gattrib and possibly utils) conflict with a newer
geda-symbols, or symbols conflicts with old geda-*.

I think I prefer the latter solution, so I'll reassign.

thanks,
Hamish
-- 
Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]


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



Processed: Re: Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem

2006-09-22 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reassign 388695 geda-symbols
Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem
Bug reassigned from package `geda-gschem' to `geda-symbols'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem

2006-09-21 Thread H. S.
Package: geda-gschem
Version: 20060123-1
Severity: grave
Justification: renders package unusable

*** Please type your report below this line ***
Hello,

(here is the bug again here for geda-gschem, instead of for geda)

If I try to start gschem, I get these errors:
--
$ gschem
gEDA/gschem version 20060123
gEDA/gschem comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
This is free software, and you are welcome to redistribute it under certain
conditions; please see the COPYING file for more details.

Probably parenthesis mismatch in /etc/gEDA/system-gafrc
Most recently read form: (postscript-prolog ${GEDADATA}/prolog.ps)
Probably parenthesis mismatch in /etc/gEDA/system-gschemrc
Most recently read form: ([EMAIL PROTECTED] ([EMAIL PROTECTED] [EMAIL PROTECTED]
/system-gafrc))
Probably parenthesis mismatch in /usr/share/gEDA/scheme/gschem.scm
Most recently read form: ([EMAIL PROTECTED] global-keymap (quote ()))
Tried to get an invalid color: 0
Tried to get an invalid color: 7
Tried to get an invalid color: 0
Tried to get an invalid color: 7
--

and if I start gschem with a .sch file, I get the above errors and the
schematic is not shown. In both cases, a window opens but it has no menus
on it. So I cannot open pre-existing files at all. If I open a new file,
in the add component dialogbox I cannot see the preview of the components
selected.

I haven't changed any config file.

This behaviour was shown right after installing these package on my Debian Etch
box. The versions that I have installed are:
$ dpkg -l geda* | grep ^ii
ii
geda
20060123-1 GNU EDA -- Electronics design
software
ii geda-doc
20060906-1 Documentation for GNU EDA --
Electronics des
ii geda-examples 20060906-1 GNU EDA -- Electronics design software -- ex
ii geda-gattrib 20060123-1 GNU EDA -- Electronics design software -- at
ii geda-gnetlist 20060123-1 GNU EDA -- Electronics design software -- ne
ii geda-gschem 20060123-1 GNU EDA -- Electronics design software -- sc
ii geda-gsymcheck 20060123-1 GNU EDA -- Electronics design software -- sy
ii geda-symbols 20060906-1 Symbols for GNU EDA -- Electronics design so
ii geda-utils 20060123-1 GNU EDA -- Electronics design software -- ut


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

Versions of packages geda-gschem depends on:
ii
geda-symbols
20060906-1 Symbols for GNU EDA -- Electronics
ii
guile-1.6-libs
1.6.8-4 Main Guile libraries
ii
libatk1.0-0
1.12.2-1 The ATK accessibility toolkit
ii
libc6
2.3.6.ds1-4 GNU C Library: Shared libraries
ii
libcairo2
1.2.4-1 The Cairo 2D vector graphics libra
ii
libfontconfig1
2.3.2-7 generic font configuration library
ii
libgdgeda6
2.0.15-3 GNU EDA -- Electronics design soft
ii libgeda20 [libgeda-25] 20060123-1 GNU EDA -- Electronics design soft
ii
libglib2.0-0
2.12.3-2 The GLib library of C routines
ii
libgtk2.0-0
2.8.20-1 The GTK+ graphical user interface
ii
libguile-ltdl-1
1.6.8-4 Guile's patched version of libtool
ii
libice6
1:1.0.1-2 X11 Inter-Client Exchange library
ii
libpango1.0-0
1.12.3-1+b1 Layout and rendering of internatio
ii
libpng12-0
1.2.8rel-5.2 PNG library - runtime
ii
libqthreads-12
1.6.8-4 QuickThreads library for Guile
ii
libsm6
1:1.0.1-2 X11 Session Management library
ii
libstroke0
0.5.1-5 mouse strokes library -- runtime f
ii
libx11-6
2:1.0.0-8 X11 client-side library
ii
libxcursor1
1.1.7-4 X cursor management library
ii
libxext6
1:1.0.1-2 X11 miscellaneous extension librar
ii
libxi6
1:1.0.1-3 X11 Input extension library
ii
libxinerama1
1:1.0.1-4.1 X11 Xinerama extension library
ii
libxrandr2
2:1.1.0.2-4 X11 RandR extension library
ii
libxrender1
1:0.9.1-3 X Rendering Extension client libra
ii
zlib1g
1:1.2.3-13 compression library - runtime

geda-gschem recommends no packages.

-- no debconf information



Bug#388695: geda-gschem: Probably parenthesis mismatch in errors in gschem

2006-09-21 Thread Hamish Moffatt
On Thu, Sep 21, 2006 at 11:12:42PM -0400, H. S. wrote:
 (here is the bug again here for geda-gschem, instead of for geda)

Thanks. geda-gschem 20060906 should be in etch in a day or two. Can you
try it again then and see if the problem is solved?

system-gafrc is provided by geda-symbols, which is already updated in
etch. However system-gschemrc is not yet. I suspect the skew between
them is causing the problem. I will tighten the dependencies in the
future.

 ii  geda-gschem20060123-1 GNU EDA -- Electronics design software --
 sc
 ii  geda-symbols   20060906-1 Symbols for GNU EDA -- Electronics design
 so

thanks,
Hamish
-- 
Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]


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