Bug#650541: libsmbclient uses internal symbol krb5_locate_kdc
Package: samba Version: 2:3.6.1-2 Followup-For: Bug #650541 Dear Maintainer, *** Please consider answering these questions, where appropriate *** # apt-get dist-upgrade -u Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: cups-driver-gutenprint gcj-jre-headless grass libgmerlin-avdec1 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Setting up samba (2:3.6.1-2) ... Starting Samba daemons: nmbd/usr/sbin/nmbd: relocation error: /usr/sbin/nmbd: symbol krb5_locate_kdc, version krb5_3_MIT not defined in file libkrb5.so.3 with link time reference failed! invoke-rc.d: initscript samba, action "start" failed. dpkg: error processing samba (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of swat: swat depends on samba (= 2:3.6.1-2); however: Package samba is not configured yet. dpkg: error processing swat (--configure): dependency problems - leaving unconfigured configured to not write apport reports configured to not write apport reports Errors were encountered while processing: samba swat E: Sub-process /usr/bin/dpkg returned an error code (1) *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-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/bash Versions of packages samba depends on: ii adduser3.113 ii debconf [debconf-2.0] 1.5.41 ii libacl12.2.51-4 ii libattr1 1:2.4.46-3 ii libc6 2.13-21 ii libcap21:2.22-1 ii libcomerr2 1.42-1 ii libcups2 1.5.0-12 ii libgssapi-krb5-2 1.10+dfsg~alpha1-5 ii libk5crypto3 1.10+dfsg~alpha1-5 ii libkrb5-3 1.10+dfsg~alpha1-5 ii libldap-2.4-2 2.4.25-4+b1 ii libpam-modules 1.1.3-6 ii libpam-runtime 1.1.3-6 ii libpam0g 1.1.3-6 ii libpopt0 1.16-1 ii libtalloc2 2.0.7-3 ii libtdb11.2.9-4+b1 ii libwbclient0 2:3.6.1-2 ii lsb-base 3.2-28 ii procps 1:3.3.0-1 ii samba-common 2:3.6.1-2 ii update-inetd 4.41 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages samba recommends: pn logrotate 3.7.8-6 pn tdb-tools Versions of packages samba suggests: pn ctdb pn ldb-tools pn openbsd-inetd [inet-superserver] 0.20091229-1 pn smbldap-tools -- debconf information: samba/tdbsam: false samba/generate_smbpasswd: true samba/run_mode: daemons samba-common/title: -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#493742: Conflict with python-babel
Adam C Powell IV wrote: On Tue, 2008-09-23 at 14:41 -0700, Tom Epperly wrote: Adam C Powell IV wrote: Hi again, I know it's been a while... So to do this right, I'd just change 'setup(name="babel",' to 'setup(name="babel.sidl",' in setup.py and sidlsetup.py, right? I am trying a "make distcheck" on the main trunk with the attached patch (relative to the svn main trunk). This changes the name to "llnl_babel" for sidlsetup.py and to "llnl_babel__" for a Babel run that produces code in packages pkg1 and pkg2. I think have a period in the name might produce pain on some file systems. Great. I had just patched [sidl]setup.py and wondered why it didn't take... I discovered more changes are necessary. Hold for more patches. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493742: Conflict with python-babel
Adam C Powell IV wrote:
Hi again,
I know it's been a while...
So to do this right, I'd just change 'setup(name="babel",' to
'setup(name="babel.sidl",' in setup.py and sidlsetup.py, right?
I am trying a "make distcheck" on the main trunk with the attached patch
(relative to the svn main trunk). This changes the name to "llnl_babel"
for sidlsetup.py and to "llnl_babel__" for a Babel run that
produces code in packages pkg1 and pkg2. I think have a period in the
name might produce pain on some file systems.
By the way, I am still working on getting proper permission (in the form
of some kind of license) for the Babel documentation and its source. It
has been a chaotic year here due to our change in management.
Tom
-Adam
On Wed, 2008-08-06 at 16:51 -0700, Ben Allan wrote:
I'll just note that fortunately for us the openbabel project
(bio/chemical) went with pybel rather than babel in the python
hierarchy.
I'd vote for proper subnaming in python sidl.babel., sidl., sidlx., etc
which it seems (in typographical terms) Tom is ok with.
Not sure what the full directory structure implications are.
ben
On Wed, Aug 06, 2008 at 06:55:52PM -0400, Adam C Powell IV wrote:
Greetings,
There's a python-babel package for internationalization, which has a
Python namespace conflict with the Python runtime bindings for the SIDL
Babel.
As a possible resolution, how much stuff would I break by changing
"babel" to "sidl" in [sidl]setup.py? I'm afraid I don't know a whole
lot about Python, so I'm out of my league here...
[Please include all of the CC addresses in your reply.]
Cheers,
-Adam
Index: runtime/python/sidlsetup.py
===
--- runtime/python/sidlsetup.py (revision 6527)
+++ runtime/python/sidlsetup.py (working copy)
@@ -52,7 +52,7 @@
else:
sys.argv.append(i)
-setup(name="babel",
+setup(name="llnl_babel",
author="Tom Epperly",
version="1.2.1",
description="Build Python support extension modules for sidl",
Index: compiler/gov/llnl/babel/backend/python/SetupGenerator.java
===
--- compiler/gov/llnl/babel/backend/python/SetupGenerator.java (revision 6527)
+++ compiler/gov/llnl/babel/backend/python/SetupGenerator.java (working copy)
@@ -123,6 +123,22 @@
}
/**
+ * Generate an extended name.
+ */
+ private String nameExt() {
+StringBuffer result = new StringBuffer();
+Iterator i = d_packages().iterator();
+while (i.hasNext()) {
+ String pkg = (String)i.next();
+ if (pkg.indexOf('.') < 0) {
+result.append('_');
+result.append(pkg);
+ }
+}
+return result.toString();
+ }
+
+ /**
* Generate the setup.py to build the Python extension modules.
*
* @exception java.io.IOException this is a exception that contains
@@ -167,7 +183,7 @@
lw.println("from re import compile");
lw.println("from distutils.core import setup, Extension");
processArgs(lw);
- lw.println("setup(name='babel',");
+ lw.println("setup(name='llnl_babel" + nameExt() + "',");
lw.tab();
lw.println("include_dirs=inc_dirs,");
// writeList(lw, "py_modules", d_pymodules.iterator());
Bug#493742: Conflict with python-babel
Adam C Powell IV wrote: Greetings, There's a python-babel package for internationalization, which has a Python namespace conflict with the Python runtime bindings for the SIDL Babel. As a possible resolution, how much stuff would I break by changing "babel" to "sidl" in [sidl]setup.py? I'm afraid I don't know a whole lot about Python, so I'm out of my league here... [Please include all of the CC addresses in your reply.] Cheers, -Adam I am not really sure. I would probably go with something like "sidlbabel", "babelsidl", "sidl_babel", or "babel_sidl" if we're going to change it to make sure we don't have to change it again. In general, we don't install our Python extension modules in the Python system directory. Babel users have to specify a PYTHONPATH, and I think changing the name in [sidl]setup.py would change the directory name in the PYTHONPATH. Do any current Babel users want to chime in? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432182: Seems to be resolved
I've been using the most recent kernel from Debian unstable for a few weeks without any problems, so I agree that this bug can be closed. Thanks, Tom On Thu, Apr 10, 2008 at 10:48 AM, Lapse of Reason <[EMAIL PROTECTED]> wrote: > Hi, > I've recently upgraded to kernel 2.6.24 as it moved into testing and > installed the nvidia driver version 169.12 from unstable. So far, I > have experienced no more freezes. > > Can you please see if the new kernel and the new version of the nvidia > driver fix your problem too? I think this bug can be closed (and I > hope nvidia finally gets into testing again...), but please feel free > to speak up if the problem persists for you! > > > > -- > To unsubscribe, send mail to [EMAIL PROTECTED] >
Bug#432182: Any idea whether this bug still occurs in 100.14.19-1?
I ran for an evening with nvidia-glx 169.07-02 nvidia-kernel-2.6.22-3-amd64169.07-2+2.6.2 without crashing. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432182: FYI
I reported this upstream to [EMAIL PROTECTED] on 7/18/2007, and I mentioned it again now. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432182: Any idea whether this bug still occurs in 100.14.19-1?
Does this bug still appear in 100.14.19-1? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426012: Patch makes python-scipy buildable
Tom Epperly wrote: I tried applying this patch to the Debian python-scipy source package, and it makes the packable buildable (can't vouch for whether it runs correctly): http://mirrors.usc.edu/pub/linux/distributions/gentoo/sci-libs/scipy/files/scipy-0.5.2-getpath.patch I made a 0.5.2-7+b2 using the patch above. I also need to edit montecarlo.py to move the line from __future__ import division before __author__ = "Ed Schofield" in Lib/sandbox/montecarlo/montecarlo.py to fix this error: dpkg --install python-scipy_0.5.2-7+b2_i386.deb (Reading database ... 379477 files and directories currently installed.) Preparing to replace python-scipy 0.5.2-7+b2 (using python-scipy_0.5.2-7+b2_i386.deb) ... Unpacking replacement python-scipy ... Setting up python-scipy (0.5.2-7+b2) ... Compiling /usr/lib/python2.5/site-packages/scipy/sandbox/montecarlo/montecarlo.py ... File "/usr/lib/python2.5/site-packages/scipy/sandbox/montecarlo/montecarlo.py", line 8 from __future__ import division SyntaxError: from __future__ imports must occur at the beginning of the file pycentral: pycentral pkginstall: error byte-compiling files (882) pycentral pkginstall: error byte-compiling files (882) dpkg: error processing python-scipy (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: python-scipy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426012: Patch makes python-scipy buildable
I tried applying this patch to the Debian python-scipy source package, and it makes the packable buildable (can't vouch for whether it runs correctly): http://mirrors.usc.edu/pub/linux/distributions/gentoo/sci-libs/scipy/files/scipy-0.5.2-getpath.patch -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#426012: Anyone know why NumPy 1:1.0.3-1 conflicts with SciPy 0.5.2-7+b1?
I am wondering if I can just build SciPy by hand. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365797: evolution is using lots of CPU
On Wed, 2006-05-03 at 13:40 +0200, Øystein Gisnås wrote: > Can you guys check and report which dbus version you are running, and if > it's installed at all. There is probably some package down the > dependency chain that should depend on the correct version of dbus. faerun:/home/tepperly/usb_content# dpkg --list '*dbus*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)||/ Name VersionDescription +++-==-==- un dbus(no description available) ii dbus-1 0.23.4-8 simple interprocess messaging system pn dbus-glib-1 (no description available) un dbus-qt-1 (no description available) rc dbus-qt-1c20.23.4-8 simple interprocess messaging system (Qt-bas ii libdbus-1-20.61-5 simple interprocess messaging system ii libdbus-1-cil 0.61-5 CLI binding for D-BUS interprocess messaging pn libdbus-cil (no description available) ii libdbus-glib-1 0.61-5 simple interprocess messaging system (GLib-b un libdbus-glib0 (no description available) un libdbus-qt-1-1 (no description available) ii libdbus-qt-1-1 0.61-5 simple interprocess messaging system (Qt-bas un libdbus0(no description available) faerun:/home/tepperly/usb_content# ps aux | grep dbus 108 4451 21.8 0.0 2196 704 ?Rs 18:59 0:49 /usr/bin/dbus-daemon-1 --system root 5277 0.0 0.0 1948 636 pts/1S+ 19:03 0:00 grep dbus If I run evolution from a gnome-terminal, I see the following message repeated over and over and over... libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.NoReply raised: No reply within specified time > > If you have dbus-1 (from "stable") installed, you might have this kind > of problem because it is not compatible with the newer dbus (0.61-5 is > in unstable). > > About the .xsession-errors problem, that's a bit weird. My error file > always stops growing at 200KiB. > > Thanks, > Øystein -- Tom Epperly <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
