Bug#725183: [witty] package build errors

2013-10-29 Thread Rutger ter Borg


The initial error is caused by the main CMakeLists.txt, around line 454

IF(NOT EXISTS ${DESTDIR}${CONFIGDIR}/wt_config.xml)
  INSTALL(FILES ${WT_BINARY_DIR}/wt_config.xml DESTINATION 
${DESTDIR}${CONFIGDIR})

ENDIF (NOT EXISTS ${DESTDIR}${CONFIGDIR}/wt_config.xml)

when having a previous version of Wt installed at the time of building a 
new package, this section is skipped. It checks if /etc/wt/wt_config.xml 
exists, which is true when the package is installed. This condition is 
apparently not reevaluated when setting DESTDIR when installing.


To remedy the situation above, I've added an INSTALL_CONFIG option,

OPTION(INSTALL_CONFIG Install configuration files ON)

and rewrote the section above to

IF(INSTALL_CONFIG)
  INSTALL(FILES ${WT_BINARY_DIR}/wt_config.xml DESTINATION 
${DESTDIR}${CONFIGDIR})

ENDIF (INSTALL_CONFIG)

which fixes the situation.

The other error is caused by the jquery.min.js file which is brought in 
by the package by default. When running dpkg-buildpackage without 
cleaning (-nc), the original file is not deleted, and the symlink not 
created because that file exists.



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



Bug#725183: [witty] package build errors

2013-10-02 Thread Rutger ter Borg

Package: witty
Version: 3.3.0
Severity: normal

--- Please enter the report below this line. ---

Linking against libwt from the witty packages cause segfaults, because 
they require an older boost version (1.49). See below. To upgrade the 
packages to using Boost 1.54, I've tried to build the witty packages 
from source. Unfortunately, without success.


 * apt-get source witty  cd witty-3.3.0  dpkg-buildpackage 
-rfakeroot -uc -b after compiling everything, it halts on not finding 
wt_config.xml:


dh_installchangelogs Changelog
dh_installdocs
dh_installexamples
dh_install --sourcedir=debian/tmp/
cp: cannot stat ‘debian/tmp//etc/wt/wt_config.xml’: No such file or 
directory
dh_install: cp -a debian/tmp//etc/wt/wt_config.xml 
debian/libwt-common//etc/wt/ returned exit code 1

make: *** [binary-arch] Error 2
d

 * when retrying to build with dpkg-buildpackage, the process is 
aborted earlier, because jquery.min.js is not present anymore:


CMake Error in src/CMakeLists.txt:
  Cannot find source file:

/.../witty-3.3.0/src/web/skeleton/jquery.min.js

  Tried extensions .c .C .c++ .cc .cpp .cxx .m .M .mm .h .hh .h++ .hm .hpp
  .hxx .in .txx


-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_CC_COMPILER
CMAKE_MODULE_LINKER_FLAGS
WT_CMAKE_FINDER_INSTALL_DIR


-- Build files have been written to: 
/home/rutger/development/witty-3.3.0/build-shared

make: *** [build-shared/Makefile] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Boost-version-related linker errors:

/usr/bin/ld.bfd.real: warning: libboost_thread.so.1.49.0, needed by 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libwt.so, may conflict 
with libboost_thread.so.1.54.0
/usr/bin/ld.bfd.real: warning: libboost_signals.so.1.49.0, needed by 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libwt.so, may conflict 
with libboost_signals.so.1.54.0
/usr/bin/ld.bfd.real: warning: libboost_system.so.1.49.0, needed by 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libwt.so, may conflict 
with libboost_system.so.1.54.0
/usr/bin/ld.bfd.real: warning: libboost_program_options.so.1.49.0, 
needed by 
/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libwthttp.so, may 
conflict with libboost_program_options.so.1.54.0




--- System information. ---
Architecture: amd64
Kernel: Linux 3.10-3-amd64

Debian Release: jessie/sid
500 unstable ftp.nl.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.


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



Bug#635982: fix

2012-05-29 Thread Rutger ter Borg


although this bug is filed as fixed, to really work, cmake needs a file 
called

wt-config.cmake in /usr/lib/wt/cmake; it's as easy as renaming

/usr/lib/wt/cmake/FindWt.cmake to /usr/lib/wt/cmake/wt-config.cmake

(adding a softlink worked for me)

Regards,

Rutger




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



Bug#666180: [libwt-dev] libwt-dev should depend on latest boost libraries

2012-03-29 Thread Rutger ter Borg

Package: libwt-dev
Version: 3.1.10-1
Severity: normal

--- Please enter the report below this line. ---

When developing with both Wt libraries and Boost libraries, the linker will

give a warning of a conflict with an older Boost version, like, e.g.,

/usr/bin/ld: warning: libboost_thread.so.1.46.1, needed by

/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libwt.so, may conflict 
with


libboost_thread.so.1.49.0

/usr/bin/ld: warning: libboost_system.so.1.46.1, needed by

/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libwt.so, may conflict 
with


libboost_system.so.1.49.0

/usr/bin/ld: warning: libboost_program_options.so.1.46.1, needed by

/usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libwthttp.so, may 
conflict


with libboost_program_options.so.1.49.0


although it links, the program crashes. I guess the warning mentioned above

should not appear. It is not possible to compile a program for different 
Boost


versions at the same time.


--- System information. ---
Architecture: amd64
Kernel: Linux 3.2.0-2-amd64

Debian Release: wheezy/sid
500 unstable ftp.nl.debian.org
500 stable ceph.newdream.net

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.





Bug#590626: kdm starts too early

2010-09-23 Thread Rutger ter Borg


Same here, with a NVidia 9600M. When failing, syslog shows

Sep 23 08:58:49 gonzo kdm[1694]: X server startup timeout, terminating
Sep 23 08:58:51 gonzo kdm[1694]: X server for display :0 cannot be 
started, session disabled


whereas X is starting just fine.

Sometimes the machine starts just fast enough, and starts into kdm, and 
sometimes it is not.  This leads to unpredictable behavior.






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



Bug#590626: kdm starts too early

2010-09-23 Thread Rutger ter Borg

On 2010-09-23 13:50, Frederik Schwarzer wrote:

Please also refer to:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597699
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524751
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583336
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583312

https://bugs.kde.org/show_bug.cgi?id=252055- Contains a workaround

It seems to be a rather general problem.

   
Thanks for pointing to a workaround. I guess the cause of all this is 
the introduction of concurrency in the startup system, having kdm being 
started during the time that other stuff  is bein started, too.


Regards,

Rutger




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



Bug#580195: [uncrustify] Segfault on incorrect input

2010-05-04 Thread Rutger ter Borg
Package: uncrustify
Version: 0.56-1
Severity: normal

--- Please enter the report below this line. ---

The following one-liner (with incorrect code) will cause a segfault for 
uncrustify,

$ echo typedef; | uncrustify -c /usr/share/uncrustify/defaults.cfg -L CPP


--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.32-3-amd64

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.nl.debian.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends   (Version) | Installed
===-+-=
libc6(= 2.2.5) | 2.10.2-7
libgcc1(= 1:4.1.1) | 1:4.4.4-1
libstdc++6   (= 4.1.1) | 4.4.4-1


Package's Recommends field is empty.

Package's Suggests field is empty.






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



Bug#575727: [linux-2.6] kernel bug after unmounting a cifs share

2010-05-03 Thread Rutger ter Borg
On Sunday 02 May 2010 19:48:34 Moritz Muehlenhoff wrote:

 Rutger, did you report this upstream?
 
 Cheers,
 Moritz


No, I haven't done this (yet). If you find the opportunity, please go ahead.

Cheers,

Rutger




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



Bug#575727: [linux-2.6] kernel bug after unmounting a cifs share

2010-05-03 Thread Rutger ter Borg
On Monday 03 May 2010 15:19:31 Ben Hutchings wrote:
 
 We need you to do this, so that any questions by the upstream developers
 will go directly to you and not to us.
 
 Ben.
 

Search on kerneloops.org is not working for me. My upstream bug report is at  
https://bugzilla.samba.org/show_bug.cgi?id=7405

Cheers,

Rutger




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



Bug#575727: [linux-2.6] kernel bug after unmounting a cifs share

2010-03-29 Thread Rutger ter Borg
On Monday 29 March 2010 02:37:44 Ben Hutchings wrote:

 Please test whether this bug is still present in a current kernel
 version, 2.6.32-9 (testing) or preferably 2.6.32-10 (unstable).


I guess I got confused with the package name and package version. It's -9, 
please see below.

Regards,

Rutger


# dpkg --status linux-image-2.6.32-3-amd64
Package: linux-image-2.6.32-3-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 97216
Maintainer: Debian Kernel Team debian-ker...@lists.debian.org
Architecture: amd64
Source: linux-2.6
Version: 2.6.32-9




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



Bug#575727: [linux-2.6] kernel bug after unmounting a cifs share

2010-03-28 Thread Rutger ter Borg
Package: linux-2.6
Version: 2.6.32-3
Severity: normal

--- Please enter the report below this line. ---

kernel crashes after unmounting a cifs share. I've pasted the syslog dump 
below. 

Mar 28 21:44:48 gonzo kernel: [11826.437106] BUG: Dentry 
8800bf5cea80{i=80,n=/} still in use (1) [unmount of cifs cifs]
Mar 28 21:44:48 gonzo kernel: [11826.437133] [ cut here 
]
Mar 28 21:44:48 gonzo kernel: [11826.437134] kernel BUG at /build/mattems-
linux-2.6_2.6.32-9-amd64-
NYTFdD/linux-2.6-2.6.32-9/debian/build/source_amd64_none/fs/dcache.c:670!
Mar 28 21:44:48 gonzo kernel: [11826.437137] invalid opcode:  [#1] SMP
Mar 28 21:44:48 gonzo kernel: [11826.437140] last sysfs file: 
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/charge_full
Mar 28 21:44:48 gonzo kernel: [11826.437142] CPU 1
Mar 28 21:44:48 gonzo kernel: [11826.437143] Modules linked in: nls_utf8 cifs 
usb_storage cryptd aes_x86_64 aes_generic ppdev lp parport sco bridge stp bnep 
rfcomm l2cap crc16 fuse ext3 jbd mbcache loop snd_hda_codec_nvhdmi 
snd_hda_codec_realtek snd_hda_intel snd_hda_codec btusb bluetooth snd_hwdep 
snd_pcm_oss snd_mixer_oss arc4 snd_pcm ecb snd_seq_midi snd_rawmidi 
dvb_usb_af9015 dvb_usb iwlagn joydev snd_seq_midi_event uvcvideo videodev 
v4l1_compat iwlcore snd_seq i2c_i801 acer_wmi v4l2_compat_ioctl32 pcspkr 
dvb_core nvidia(P) psmouse led_class ac snd_timer serio_raw snd_seq_device 
mac80211 processor i2c_core battery snd wmi evdev soundcore snd_page_alloc 
cfg80211 rfkill usbhid hid xfs exportfs sg sr_mod sd_mod crc_t10dif cdrom 
uhci_hcd ahci libata video output atl1e intel_agp ehci_hcd button scsi_mod 
usbcore nls_base thermal fan thermal_sys [last unloaded: scsi_wait_scan]
Mar 28 21:44:48 gonzo kernel: [11826.437196] Pid: 6174, comm: umount Tainted: 
P   2.6.32-3-amd64 #1 Aspire 6935
Mar 28 21:44:48 gonzo kernel: [11826.437198] RIP: 0010:[810fc7c2]  
[810fc7c2] shrink_dcache_for_umount_subtree+0x185/0x251
Mar 28 21:44:48 gonzo kernel: [11826.437206] RSP: 0018:880119fe9e78  
EFLAGS: 
00010292
Mar 28 21:44:48 gonzo kernel: [11826.437208] RAX: 0064 RBX: 
8800bf5cea80 RCX: e9f4
Mar 28 21:44:48 gonzo kernel: [11826.437210] RDX:  RSI: 
0092 RDI: 0246
Mar 28 21:44:48 gonzo kernel: [11826.437212] RBP: 8800bf5cea80 R08: 
0002 R09: 81399d7f
Mar 28 21:44:48 gonzo kernel: [11826.437214] R10:  R11: 
000186a0 R12: 00010bd0
Mar 28 21:44:48 gonzo kernel: [11826.437215] R13: 8800bf5ced20 R14: 
 R15: 
Mar 28 21:44:48 gonzo kernel: [11826.437218] FS:  7f8f8aeb1730() 
GS:88000528() knlGS:
Mar 28 21:44:48 gonzo kernel: [11826.437220] CS:  0010 DS:  ES:  CR0: 
8005003b
Mar 28 21:44:48 gonzo kernel: [11826.437222] CR2: 006d8fa8 CR3: 
00010214b000 CR4: 06e0
Mar 28 21:44:48 gonzo kernel: [11826.437224] DR0:  DR1: 
 DR2: 
Mar 28 21:44:48 gonzo kernel: [11826.437226] DR3:  DR6: 
0ff0 DR7: 0400
Mar 28 21:44:48 gonzo kernel: [11826.437228] Process umount (pid: 6174, 
threadinfo 880119fe8000, task 8800bdffaa60)
Mar 28 21:44:48 gonzo kernel: [11826.437229] Stack:
Mar 28 21:44:48 gonzo kernel: [11826.437230]  88012f29ca60 88012f29c800 
a0d2ef30 880101dd2a30
Mar 28 21:44:48 gonzo kernel: [11826.437233] 0 880101dd2a00 
810fc8bd 
88012f29c800 810ef30a
Mar 28 21:44:48 gonzo kernel: [11826.437237] 0 a0d49720 
0013 
a0d49720 810ef422
Mar 28 21:44:48 gonzo kernel: [11826.437240] Call Trace:
Mar 28 21:44:48 gonzo kernel: [11826.437244]  [810fc8bd] ? 
shrink_dcache_for_umount+0x2f/0x3d
Mar 28 21:44:48 gonzo kernel: [11826.437247]  [810ef30a] ? 
generic_shutdown_super+0x19/0xee
Mar 28 21:44:48 gonzo kernel: [11826.437250]  [810ef422] ? 
kill_anon_super+0x9/0x40
Mar 28 21:44:48 gonzo kernel: [11826.437252]  [810efad2] ? 
deactivate_super+0x60/0x7a
Mar 28 21:44:48 gonzo kernel: [11826.437256]  [81102127] ? 
sys_umount+0x2c3/0x2f2
Mar 28 21:44:48 gonzo kernel: [11826.437260]  [81010b42] ? 
system_call_fastpath+0x16/0x1b
Mar 28 21:44:48 gonzo kernel: [11826.437261] Code: 8b 08 48 8b 45 10 48 85 c0 
74 04 48 8b 50 40 48 8d 86 60 02 00 00 48 c7 c7 87 e6 3a 81 48 89 ee 48 89 04 
24 31 c0 e8 42 0c 1f 00 0f 0b eb fe 48 8b 5d 28 48 39 dd 75 04 31 db eb 03 
f0 ff 0b 48
Mar 28 21:44:48 gonzo kernel: [11826.437285] RIP  [810fc7c2] 
shrink_dcache_for_umount_subtree+0x185/0x251
Mar 28 21:44:48 gonzo kernel: [11826.437288]  RSP 880119fe9e78
Mar 28 21:44:48 gonzo kernel: [11826.437290] ---[ end trace c5440e8e073c604d 
]---

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.32-3-amd64

Debian Release: squeeze/sid
  

Bug#571331: [network-manager] stale state file disables networking (after suspend)

2010-02-25 Thread Rutger ter Borg
Package: network-manager
Version: 0.8-1
Severity: normal

--- Please enter the report below this line. ---

Hello, I see there are numerous bugs covering suspend, but this one seems to 
be more generic. Apparently (due to battery loss) the state file in 
/var/lib/NetworkManager/NetworkManager.state contained the text

NetworkingEnabled=false

which caused the network to remain in a disabled state. This didn't change 
over reboot, and also isn't changeable from recent docked GUI-tools such as 
KDE's control module for network-manager (which just showed networking 
disabled).

To remedy the problem, I just deleted the stale state file and rebooted.

Kind regards,

Rutger


--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.32-2-amd64

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.nl.debian.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends   (Version) | Installed
===-+-==
libc6  (= 2.4) | 2.10.2-6
libdbus-1-3  (= 1.0.2) | 1.2.20-2
libdbus-glib-1-2  (= 0.78) | 0.84-1
libgcrypt11  (= 1.4.2) | 1.4.5-2
libglib2.0-0(= 2.18.0) | 2.22.4-1
libgnutls26   (= 2.7.14-0) | 2.8.5-2
libgudev-1.0-0 (= 146) | 151-2
libnl1 (= 1.1) | 1.1-5
libnm-glib2(= 0.7.999) | 0.8-1
libnm-util1(= 0.7.999) | 0.8-1
libpolkit-gobject-1-0 (= 0.94) | 0.96-1
libuuid1  (= 2.16) | 2.16.2-0
lsb-base(= 3.2-14) | 3.2-23
wpasupplicant  (= 0.6.2-1) | 0.6.10-1
dbus (= 1.1.2) | 1.2.20-2
udev| 151-2
ifupdown| 0.6.9
adduser | 3.112
dhcp3-client| 3.1.3-2


Recommends (Version) | Installed
-+-===
network-manager-gnome| 
 OR network-manager-kde  | 1:0.9~svn1088283-1
policykit-1  | 0.96-1
ppp  | 2.4.4rel-10.1
dnsmasq-base | 2.52-1
iptables | 1.4.6-2
modemmanager | 0.3-1


Suggests   (Version) | Installed
-+-===
avahi-autoipd| 







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



Bug#568912: confirmed

2010-02-08 Thread Rutger ter Borg

Confirmed, I'm having exactly the same problem.

Feb  8 20:25:01 gonzo wpa_supplicant[1892]: CTRL-EVENT-SCAN-RESULTS
Feb  8 20:25:21 gonzo NetworkManager: WARN  wait_for_connection_expired(): 
Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to 
activate (timeout): (0) Connection was not provided by any settings service




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



Bug#565906: Bugreport may be closed

2010-01-20 Thread Rutger ter Borg

This is not a bug, my script was missing tool options... Sorry for the noise.

Regards,

Rutger




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



Bug#565906: [waf] Waf's qt4 tool crashes

2010-01-19 Thread Rutger ter Borg
Package: waf
Version: 1.5.10+dfsg-1
Severity: normal

--- Please enter the report below this line. ---

A minimal wscript containing

APPNAME = 'hello_world'
srcdir = '.'
blddir = 'build'

def configure(conf):
conf.check_tool( 'qt4' )

def build( bld ):
pass

will give the following:

waf configure
Checking for program qmake-qt4   : ok /usr/bin/qmake-qt4
Checking for program qmake4  : not found
Checking for program qmake   : ok /usr/bin/qmake
Checking for program uic-qt3 : not found
Checking for program uic3: ok /usr/bin/uic3
Checking for program uic-qt4 : ok /usr/bin/uic-qt4
Checking for uic version : ok (version 4.5.3)
Checking for program moc-qt4 : ok /usr/bin/moc-qt4
Checking for program rcc : ok /usr/bin/rcc
Checking for program lrelease-qt4: ok /usr/bin/lrelease-qt4
Checking for program lupdate-qt4 : ok /usr/bin/lupdate-qt4
Checking for QtCore_debug: not found
Checking for QtGui_debug : not found
Checking for QtUiTools_debug : not found
Checking for QtNetwork_debug : not found
Checking for QtOpenGL_debug  : not found
Checking for QtSql_debug : not found
Checking for QtSvg_debug : not found
Checking for QtTest_debug: not found
Checking for QtXml_debug : not found
Checking for QtWebKit_debug  : not found
Checking for Qt3Support_debug: not found
Checking for QtCore  : ok
Checking for QtGui   : ok
Checking for QtUiTools   : ok
Checking for QtNetwork   : ok
Checking for QtOpenGL: ok
Checking for QtSql   : ok
Checking for QtSvg   : ok
Checking for QtTest  : ok
Checking for QtXml   : ok
Checking for QtWebKit: ok
Checking for Qt3Support  : ok
Traceback (most recent call last):
  File /usr/bin/waf, line 153, in module
Scripting.prepare(t, cwd, VERSION, wafdir)
  File /usr/share/waf/wafadmin/Scripting.py, line 145, in prepare
prepare_impl(t, cwd, ver, wafdir)
  File /usr/share/waf/wafadmin/Scripting.py, line 135, in prepare_impl
main()
  File /usr/share/waf/wafadmin/Scripting.py, line 190, in main
fun(ctx)
  File /usr/share/waf/wafadmin/Scripting.py, line 242, in configure
conf.sub_config([''])
  File /usr/share/waf/wafadmin/Configure.py, line 178, in sub_config
self.recurse(k, name='configure')
  File /usr/share/waf/wafadmin/Utils.py, line 611, in recurse
f(self)
  File string, line 17, in configure
  File /usr/share/waf/wafadmin/Configure.py, line 171, in check_tool
if type(func) is type(find_file): func(self)
  File /usr/share/waf/wafadmin/Tools/qt4.py, line 459, in detect
detect_qt4(conf)
  File /usr/share/waf/wafadmin/Tools/qt4.py, line 439, in detect_qt4
if Options.options.want_rpath:
AttributeError: Values instance has no attribute 'want_rpath'


--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.32-trunk-amd64

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.nl.debian.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends  (Version) | Installed
==-+-
python(= 2.4) | 2.5.4-5
python-support (= 0.90.0) | 1.0.6


Package's Recommends field is empty.

Suggests  (Version) | Installed
===-+-===
waf-doc | 1.5.10+dfsg-1







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



Bug#564085: [kwrite] Kwrite crashes on triple clicks

2010-01-07 Thread Rutger ter Borg
Package: kwrite
Version: 4:4.3.4-1
Severity: serious

--- Please enter the report below this line. ---

Reproduce with:

1) start kwrite or kate
2) quickly click three times anywhere in the (empty) text area
3) crash

Also see below.

Application: KWrite (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x7fe5e6c3c240 in ?? () from /usr/lib/kde4/katepart.so
#6  0x7fe5e6c392aa in ?? () from /usr/lib/kde4/katepart.so
#7  0x7fe5e6c39881 in ?? () from /usr/lib/kde4/katepart.so
#8  0x7fe5e6c8ca69 in ?? () from /usr/lib/kde4/katepart.so
#9  0x7fe5e6c8d129 in ?? () from /usr/lib/kde4/katepart.so
#10 0x7fe5e6c9135d in ?? () from /usr/lib/kde4/katepart.so
#11 0x7fe5f32e2556 in QWidget::event(QEvent*) () from 
/usr/lib/libQtGui.so.4
#12 0x7fe5f329201d in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) () from /usr/lib/libQtGui.so.4
#13 0x7fe5f329a7ca in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libQtGui.so.4
#14 0x7fe5f3ee9e06 in KApplication::notify(QObject*, QEvent*) () from 
/usr/lib/libkdeui.so.5
#15 0x7fe5f5311c9c in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/libQtCore.so.4
#16 0x7fe5f3299a78 in QApplicationPrivate::sendMouseEvent(QWidget*, 
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointerQWidget) () from 
/usr/lib/libQtGui.so.4
#17 0x7fe5f3302659 in ?? () from /usr/lib/libQtGui.so.4
#18 0x7fe5f330140f in QApplication::x11ProcessEvent(_XEvent*) () from 
/usr/lib/libQtGui.so.4
#19 0x7fe5f332976c in ?? () from /usr/lib/libQtGui.so.4
#20 0x7fe5f21a88fe in g_main_context_dispatch () from 
/lib/libglib-2.0.so.0
#21 0x7fe5f21ac2b8 in ?? () from /lib/libglib-2.0.so.0
#22 0x7fe5f21ac3e0 in g_main_context_iteration () from 
/lib/libglib-2.0.so.0
#23 0x7fe5f533a39c in 
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/libQtCore.so.4
#24 0x7fe5f3328f1f in ?? () from /usr/lib/libQtGui.so.4
#25 0x7fe5f5310562 in 
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/libQtCore.so.4
#26 0x7fe5f5310934 in 
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/libQtCore.so.4
#27 0x7fe5f5312ba4 in QCoreApplication::exec() () from 
/usr/lib/libQtCore.so.4
#28 0x7fe5e922f02d in kdemain () from /usr/lib/libkdeinit4_kwrite.so
#29 0x00406e9e in _start ()

--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.32-trunk-amd64

Debian Release: squeeze/sid
  500 unstablewww.debian-multimedia.org 
  500 unstableftp.nl.debian.org 
  500 stable  deb.opera.com 

--- Package information. ---
Depends(Version) | Installed
-+-=
kdebase-runtime (= 4:4.3.0) | 4:4.3.4-2
kdelibs5(= 4:4.3.4) | 4:4.3.4-1
libc6 (= 2.2.5) | 2.10.2-4
libqtcore4  (= 4:4.5.3) | 4:4.5.3-4
libqtgui4   (= 4:4.5.3) | 4:4.5.3-4
libstdc++6(= 4.1.1) | 4.4.2-8


Package's Recommends field is empty.

Package's Suggests field is empty.






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



Bug#516727: gcc segfaults on simple wrong c++ code

2009-02-23 Thread Rutger ter Borg

Package: g++ (Debian 4.3.3-4) 4.3.3

The current c++ compiler segfaults on the following simple code mistake, where 
a destructor doesn't have the same id as that the class.


template typename T 
class some_class {

some_class() {}

// segfault
~some() {}

// no segfault
// ~some_class() {}

};


Kind regards,

Rutger ter Borg




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



Bug#494832: Creating Boost.MPI packages

2009-01-08 Thread Rutger ter Borg

Dear Debian Boost Team,

I've managed to create Boost.MPI packages for 1.37 in conjunction with 
open-mpi, with the following restrictions

 * Boost.MPI's support for Python has to be commented out/deleted from 
libs/mpi/build/Jamfile.v2; Boost doesn't compile otherwise. Perhaps this is 
an upstream bug.
 * No specific naming is done (yet) for the openmpi variant

Please find attached my control and rules files, which creates the necessary 
files. I've tested it, and it works like a charm. 

Kind regards,

Rutger ter Borg
#! /usr/bin/make -f

# Uncomment this to turn on verbose mode.
export DH_VERBOSE=1

export DH_OPTIONS

include /usr/share/quilt/quilt.make

# set the number of build jobs
ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS)))
JOBS := -j$(patsubst parallel=%,%,$(filter 
parallel=%,$(DEB_BUILD_OPTIONS)))
endif

DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)

PKGVERSION = 1.37
SOVERSION = 1.37.0
SHLIBS_VERSION = (= 1.37.0-1)

# tags for library name decoration
boost_version = 1_37

# Boost libraries for which we want separate packages
boost_libs := date-time filesystem graph iostreams math mpi\
program-options python regex serialization signals system test \
thread wave

# these are special cases, where shared library has not the same name of the 
Boost library
boost_lib_math := math_c99 math_c99f math_tr1 math_tr1f
boost_lib_math_long_double := math_c99l math_tr1l
boost_lib_serialization := serialization wserialization
boost_lib_test := prg_exec_monitor unit_test_framework

# these are special cases for variants. normal cases have empty, -d, -mt, 
-mt-d variants
boost_variants_thread := -mt -mt-d

# These are special cases for suffixes.  Generally come from --buildid, so 
begin with a dash.
boost_suffixes_python := -py24 -py25

# Files that are generated by filtering a template
filtered_files = \
debian/libboost-dbg.postinst \
debian/libboost-dbg.prerm \
debian/libboost-doc.doc-base \
debian/libboost-python-dev.postinst \
debian/libboost-python-dev.prerm

# Function to map Boost component name to set of shared library names
# Input: Boost component name
# Return: shared library names for the given Boost library
boost_lib = $(if $(boost_lib_$(1)), $(boost_lib_$(1)), $(1))

# Function to map Boost component name to set of variants for the library
# Input: Boost component name
# Return: variants for the given Boost component
boost_variants = $(if $(boost_variants_$(1)), $(boost_variants_$(1)), -mt -mt-d)

# Function to map Boost component name to set of suffixes for the library
# Input: Boost component name
# Return: suffixes for the given Boost component
boost_suffixes = $(if $(boost_suffixes_$(1)), $(boost_suffixes_$(1)),)

# Helpers to make basic and decorated library names
# Input: library, variant, suffix
# Return: base library filename for short or full name
mk_base_name = usr/lib/libboost_$(subst -,_,$(1))$(2)$(3)

# Input: component, variant
# Return: package name for shared library or development
mk_pkg_lib = libboost$(if $(findstring 
-d,$(2)),$(PKGVERSION)-dbg,-$(1)$(SOVERSION))
mk_pkg_dev = libboost$(if $(findstring 
-d,$(2)),$(PKGVERSION)-dbg,-$(1)$(PKGVERSION)-dev)

# Helpers to generate debhelper input filenames.
# Input: component, variant
# Return: prefix to debhelper filenames
mk_deb_lib = debian/$(call mk_pkg_lib,$(1),$(2))
mk_deb_dev = debian/$(call mk_pkg_dev,$(1),$(2))

# Helpers that update debhelper .install or .links files
# Input: component, library, variant, suffix
# Output: none
mk_so_files = $(shell echo debian/tmp/$(call 
mk_base_name,$(2),$(3),$(4)).so.$(SOVERSION)  $(call 
mk_deb_lib,$(1),$(3)).install)
mk_a_files = $(shell echo debian/tmp/$(call mk_base_name,$(2),$(3),$(4)).a  
$(call mk_deb_dev,$(1),$(3)).install)
mk_ln_files = $(shell echo $(call mk_base_name,$(2),$(3),$(4)).so.$(SOVERSION) 
$(call mk_base_name,$(2),$(3),$(4)).so  $(call mk_deb_dev,$(1),$(3)).links)

# Function that updates debhelper files for a given library variant
# Input: component, library, variant, suffix
# Output: none
mk_files = $(foreach fn,a so ln,$(call mk_$(fn)_files,$(1),$(2),$(3),$(4)))

# helpers to make and install lintian override files

# Input: package, override
add_override = echo $(1): $(2)  debian/$(1).lintian-overrides;

# Input: override
add_dbg_override = $(call add_override,libboost$(PKGVERSION)-dbg,$(1))
add_dev_override = $(call add_override,libboost$(PKGVERSION)-dev,$(1))
add_doc_override = $(call add_override,libboost$(PKGVERSION)-doc,$(1))

# Input: component, variant, lintian-warning
add_lib_override = $(call add_override,$(call mk_pkg_lib,$(1),$(2)),$(3))
add_libdev_override = $(call add_override,$(call mk_pkg_dev,$(1),$(2)),$(3))

cp_debhelper = for s in doc-base examples postinst prerm README.Debian; do \
if test -f debian/$(1).$$s; then cp -f debian/$(1).$$s debian/$(2).$$s; 
fi; done

# Function that updates debhelper files for all library variants shipped

Bug#490959: linux-image-2.6.25-2-amd64: upgrade from 2.6.24 to 2.6.25 changes drive identities

2008-07-15 Thread Rutger ter Borg
Package: linux-image-2.6.25-2-amd64
Version: 2.6.25-6
Severity: important


When upgrading to 2.6.25, the linux kernel re-assigns drive letters with 
respect to how it is done in 2.6.24.
In my particular case, /dev/sdc is swapped with /dev/sdb. This will make a 
remote reboot unreliable and/or impossible, parameters
used by the boot loader and fstab must be updated and even then the system 
keeps complaining about special 
devices which should be normal devices.

This also happened, in reverse order, when upgrading from 2.6.18 to above. 

Nothing is changed in the BIOS. Booting into 2.6.24 says the root file system 
is on /dev/sdc, booting into 2.6.25 
says the root file system is on /dev/sdb.


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-amd64 depends on:
ii  debconf [debconf-2.0] 1.5.22 Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92e  tools for generating an initramfs
ii  module-init-tools 3.4-1  tools for managing Linux kernel mo

linux-image-2.6.25-2-amd64 recommends no packages.

-- debconf information:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.25-2-amd64/preinst/abort-overwrite-2.6.25-2-amd64:
  linux-image-2.6.25-2-amd64/prerm/removing-running-kernel-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/postinst/old-initrd-link-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/postinst/create-kimage-link-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/preinst/failed-to-move-modules-2.6.25-2-amd64:
  linux-image-2.6.25-2-amd64/preinst/abort-install-2.6.25-2-amd64:
  linux-image-2.6.25-2-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.25-2-amd64/postinst/depmod-error-2.6.25-2-amd64: false
  linux-image-2.6.25-2-amd64/postinst/bootloader-test-error-2.6.25-2-amd64:
  linux-image-2.6.25-2-amd64/postinst/old-system-map-link-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/prerm/would-invalidate-boot-loader-2.6.25-2-amd64: 
true
  linux-image-2.6.25-2-amd64/preinst/overwriting-modules-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/postinst/depmod-error-initrd-2.6.25-2-amd64: false
  linux-image-2.6.25-2-amd64/postinst/old-dir-initrd-link-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/preinst/elilo-initrd-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/postinst/bootloader-error-2.6.25-2-amd64:
  linux-image-2.6.25-2-amd64/preinst/lilo-initrd-2.6.25-2-amd64: true
  linux-image-2.6.25-2-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.25-2-amd64/preinst/initrd-2.6.25-2-amd64:
  linux-image-2.6.25-2-amd64/preinst/bootloader-initrd-2.6.25-2-amd64: true



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