Bug#574302: fso-abyss

2010-06-08 Thread Dr. Michael Lauer
Am 08.06.2010 um 09:11 schrieb Heiko Stuebner:
> does someone still work on abyss or is it completly dead?

Well, since fso-abyss is just a standalone version of libgsm0710mux,
which I still maintain, we can consider it being alive, although somewhat
deprecated, since we no longer use the pty redirection in fsogsmd.

> As I was updating my fso-abyss build the whole new config handling was 
> included 
> and I was not able to create a working config again.
> 
> I moved abyss.conf to /etc/freesmartphone/conf/GTA02/fso-abyss.conf which 
> resulted in abyss finding it again but I can't figure out how the config 
> sections 
> and params should look now for the new libgsm0710mux versions.

You can take the libgsm0710mux section from any fsogsmd.conf, e.g. use:

[libgsm0710mux]
log_level = INFO
log_to = file
log_destination = /var/log/libgsm0710mux.log

# Set to 1, when the first AllocChannel request should open a new MUX session
muxer_autoopen = 1
# Set to 1, when the last ReleaseChannel closes the MUX session
muxer_autoclose = 1

# Communication means
device_type = serial
# Communication port
device_port = /dev/ttySAC0
# Port speed
device_speed = 115200
# MUX mode, set to 0 for 07.10 basic multiplexing, to 1 for advanced mode
device_mux_mode = 1
# set maximum 07.10 frame size
device_mux_framesize = 89

# Set wakeup threshold for device (in seconds) or 0 to disable
device_wakeup_threshold = 5
# Set wakeup time for device (in milliseconds)
device_wakeup_waitms = 250

# DEBUG: Whether to ignore MUX mode
session_debug_leave_mux_alone = 0
# DEBUG: Whether to ignore FC mode
session_debug_leave_fc_alone = 0

Cheers,

:M:




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



Bug#574302: fso-abyss

2010-06-08 Thread Heiko Stuebner
Hi,

does someone still work on abyss or is it completly dead?

As I was updating my fso-abyss build the whole new config handling was included 
and I was not able to create a working config again.

I moved abyss.conf to /etc/freesmartphone/conf/GTA02/fso-abyss.conf which 
resulted in abyss finding it again but I can't figure out how the config 
sections 
and params should look now for the new libgsm0710mux versions.

Thanks
Heiko



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



Bug#574302: fso-abyss: FTBFS: src/server.vala:99.61-99.69: error: Argument 4: Cannot convert from `int' to `string'

2010-03-17 Thread Lucas Nussbaum
Source: fso-abyss
Version: 0.9.0-1
Severity: serious
Tags: squeeze sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20100316 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory 
> `/build/user-fso-abyss_0.9.0-1-amd64-KAodQG/fso-abyss-0.9.0'
> /usr/bin/valac -C --vapidir vapi --pkg posix --pkg gsm0710mux-1.0 --pkg 
> fsobasics-2.0 --pkg dbus-glib-1 --save-temps --basedir . src/consts.vala 
> src/server.vala src/main.vala
> src/server.vala:66.20-66.54: warning: unhandled error `DBus.Error'
> conn = DBus.Bus.get( DBus.BusType.SYSTEM );
>^^^
> src/server.vala:99.61-99.69: error: Argument 4: Cannot convert from `int' to 
> `string'
> manager.openSession( advanced, framesize, port, portspeed );
> ^
> src/server.vala:108.17-108.24: warning: unhandled error 
> `Gsm0710mux.MuxerError'
> throw e;
> 
> src/server.vala:129.18-129.41: error: use `new' operator to create new objects
> var ci = Gsm0710mux.ChannelInfo();
>  
> src/server.vala:129.13-129.41: error: var declaration not allowed with 
> non-typed initializer
> var ci = Gsm0710mux.ChannelInfo();
> ^
> src/server.vala:130.9-130.10: error: The name `ci' does not exist in the 
> context of `Server.AllocChannel'
> ci.type = Gsm0710mux.ChannelType.PTY;
> ^^
> src/server.vala:131.9-131.10: error: The name `ci' does not exist in the 
> context of `Server.AllocChannel'
> ci.consumer = name;
> ^^
> src/server.vala:132.9-132.10: error: The name `ci' does not exist in the 
> context of `Server.AllocChannel'
> ci.number = channel;
> ^^
> src/server.vala:136.39-136.40: error: The name `ci' does not exist in the 
> context of `Server.AllocChannel'
> manager.allocChannel( ref ci );
>   ^^
> src/server.vala:149.16-149.17: error: The name `ci' does not exist in the 
> context of `Server.AllocChannel'
> path = ci.transport;
>^^
> src/server.vala:150.29-150.30: error: The name `ci' does not exist in the 
> context of `Server.AllocChannel'
> allocated_channel = ci.number;
> ^^
> src/server.vala:146.18-146.25: warning: unhandled error 
> `Gsm0710mux.MuxerError'
> else throw e;
>  
> src/server.vala:166.17-166.24: warning: unhandled error 
> `Gsm0710mux.MuxerError'
> throw e;
> 
> src/server.vala:172.9-172.53: warning: unhandled error `Gsm0710mux.MuxerError'
> manager.setWakeupThreshold( seconds, waitms );
> ^
> src/server.vala:188.17-188.24: warning: unhandled error 
> `Gsm0710mux.MuxerError'
> throw e;
> 
> src/server.vala:205.17-205.24: warning: unhandled error 
> `Gsm0710mux.MuxerError'
> throw e;
> 
> Compilation failed: 9 error(s), 7 warning(s)
> make[1]: *** [src/.vala.stamp] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2010/03/16/fso-abyss_0.9.0-1_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |



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