Bug#711933: additional information
Looks like this bug was discovered last year along with a patch. https://mail.gna.org/public/smbldap-tools-tech/2012-02/msg0.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711933: smbldap-tools: Some samba attributes are not added when using smbldap-useradd
We were also hit by this issue. Account created before the wheezy update. # smbldap-usershow sajulien | grep sambaHome sambaHomePath: \\ldap\sajulien sambaHomeDrive: I: Account created after. # smbldap-usershow e86723 | grep sambaHome We have defined these in our /etc/smbldap-tools/smbldap.conf userSmbHome="\\ldap\%U" userHomeDrive="I:" The recommended fix seems to address the issue: /usr/sbin/smbldap-useradd line 601 -my @adds = (); +@adds = (); -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679936: smbldap-tools: smbldap-useradd does not work with -M
# smbldap-useradd -a -m -G "cp,students" -M "Terry.Fox" -c "Terry Fox" foterry Use of qw(...) as parentheses is deprecated at /usr/share/perl5/smbldap_tools.pm line 1423, line 558. failed to add entry: modify/add: mail: value #0 already exists at /usr/sbin/smbldap-useradd line 627. However this works just fine. # smbldap-useradd -a -m -G "cp,students" -c "Terry Fox" foterry # smbldap-usermod -M "Terry.Fox" foterry The patch provided appears to resolve this issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606262: [pkg-bacula-devel] Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail
All that said, it maybe better 'fall mode' behavior, or at least present us with a better error message. Especially since dbc_dbadmin and dbc_dbname were set properly. The upgrade runs as dbc_dbuser as I understand though. It's an entirely moot point though, but in theory it could have run the upgrade as dbc_dbadmin rather than dbc_dbuser. Anyways, this is a separate issue and my bug that the upgrade script doesn't work was in error. On 04/20/2011 07:43 PM, Julien Savoie wrote: > This is how I created the script, by merging the > > /usr/share/dbconfig-common/data/bacula-director-mysq/upgrade/mysql/3.0.0 > and 5.0.0 scripts. > > I'm afraid I can see where this is probably my fault. Under > /etc/dbconfig-common/bacula-director-mysql.conf > I do not have the dbc_dbuser and dbc_dbpass properly populated. This is > because we setup bacula's database access without first going through > the dpkg-reconfigure bacula-director-mysql. > > I apologize, and I would like to close the ticket. This was an issue on > our end. > > On 04/20/2011 07:34 AM, Jan Hauke Rahm wrote: > >> On Thu, Apr 14, 2011 at 05:18:05PM +0200, Jan Hauke Rahm wrote: >> >> >>> Actually, our debian package already handles such upgrades. It simply >>> started off of a false premise, that is having db version 11 in lenny. >>> I'm still thinking about this but, if I'm not mistaken, the lenny >>> version just needs to run the upgrade script for 10->11 additionally to >>> the already set script for 11->12. And if that's so, it's basicall >>> uncommenting a line in debian/rules. >>> >>> >> That's nonsense. bacula-director-* ship sql upgrade files for 3.0.0 and >> 5.0.0 (which combined are the script Julien provided). Either >> dbconfig-common didn't catch up on both or something entirely different >> went wrong. >> >> Hauke >> >> >> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606262: [pkg-bacula-devel] Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail
This is how I created the script, by merging the /usr/share/dbconfig-common/data/bacula-director-mysq/upgrade/mysql/3.0.0 and 5.0.0 scripts. I'm afraid I can see where this is probably my fault. Under /etc/dbconfig-common/bacula-director-mysql.conf I do not have the dbc_dbuser and dbc_dbpass properly populated. This is because we setup bacula's database access without first going through the dpkg-reconfigure bacula-director-mysql. I apologize, and I would like to close the ticket. This was an issue on our end. On 04/20/2011 07:34 AM, Jan Hauke Rahm wrote: > On Thu, Apr 14, 2011 at 05:18:05PM +0200, Jan Hauke Rahm wrote: > >> Actually, our debian package already handles such upgrades. It simply >> started off of a false premise, that is having db version 11 in lenny. >> I'm still thinking about this but, if I'm not mistaken, the lenny >> version just needs to run the upgrade script for 10->11 additionally to >> the already set script for 11->12. And if that's so, it's basicall >> uncommenting a line in debian/rules. >> > That's nonsense. bacula-director-* ship sql upgrade files for 3.0.0 and > 5.0.0 (which combined are the script Julien provided). Either > dbconfig-common didn't catch up on both or something entirely different > went wrong. > > Hauke > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#612550: mrtg with perl 5.10.1 in squeeze
Package: mrtg Version: 2.16.3-3 When running mrtg with --user other than root, perlsec does the following in perl 5.10.1, "Perl automatically enables a set of special security checks, called taint mode, when it detects its program running with differing real and effective user or group IDs.". Meaning that mrtg will break with this error. Insecure dependency in exec while running with -T switch at /usr/bin/mrtg line 1135. *** Restarting after 10 seconds in an attempt to recover from the error above Problem is described here and includes a patch: http://oss.oetiker.ch/mrtg-trac/ticket/87 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606262: bacula-director-mysql lenny to squeeze database upgrade fail
Package: bacula-director-mysql Version: 5.0.2-2, 5.0.2-1 The included script upgrades from database format version 11 to version 12. Unfortunately Debian lenny has bacula 2.4.4, which is version 10. We were able to get around this by downloading the source to bacula 3.0 and running the version 10 to 11 script manually ourselves. /usr/share/bacula-director/update_mysql_tables echo " " echo "This script will update a Bacula MySQL database from version 11 to 12" echo " which is needed to convert from Bacula Enterprise 2.6 to 4.0 or " echo " Standard version 3.0 to 5.0" echo " " What is needed is a script that upgrades 10 to 12. I'm including the one I wrote. The upgrade for the bacula-director-mysql should really call this script or something similar. #!/bin/sh # # Shell script to update MySQL tables from version 2.0 to 5.0 # echo " " echo "This script will update a Bacula MySQL database from version 10 to 12" echo " which is needed to convert from Bacula version 2.0.x to 5.0" echo " " bind...@sql_bindir@ db_na...@db_name@ if $bindir/mysql $* -f <
