Bug#814218: lua-ldap: Add support for Lua 5.2
On Wed, Jan 04, 2017 at 11:04:32PM +0100, Luca Capello wrote: > tags 814218 + moreinfo > thanks > > Hi there, > > sorry for the delay, mostly due to real life and the fact that the > servers (with Prosody + lua-ldap) I administer are still on wheezy. > > On Tue, 09 Feb 2016 14:33:53 +0530, Avinash Sultanpur wrote: > > The pdns-recursor is compiled with liblua5.2-0 and this package does > > not have support for Lua 5.2 which makes it unusable with Power DNS. > > > > There are a couple of open pull requests on Github which add support > > for Lua 5.2. Please merge them in order to support Lua 5.2. > > > > https://github.com/luaforge/lualdap/pulls > > I am sorry, but after having tried for 2 weeks now I have given up > trying to understand where the lualdap sources reside, here some > comments: Since reporting this bug, I've been using the pdns-recursor package from Fedora 23 running under Docker and it has worked well with lua-ldap which ships with the distribution along with Lua 5.3. Would this link be of any help? http://pkgs.fedoraproject.org/cgit/rpms/lua-ldap.git
Bug#814218: lua-ldap: Add support for Lua 5.2
Package: lua-ldap Version: 1.1.0-1-geeac494-6 Severity: normal Dear Maintainer, The pdns-recursor is compiled with liblua5.2-0 and this package does not have support for Lua 5.2 which makes it unusable with Power DNS. There are a couple of open pull requests on Github which add support for Lua 5.2. Please merge them in order to support Lua 5.2. https://github.com/luaforge/lualdap/pulls Cheers, Avinash. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_IN.utf8, LC_CTYPE=en_IN.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lua-ldap depends on: ii libc6 2.19-18+deb8u2 ii libldap-2.4-2 2.4.40+dfsg-1+deb8u2 ii multiarch-support 2.19-18+deb8u2 lua-ldap recommends no packages. lua-ldap suggests no packages. -- no debconf information
Bug#738954: salt-minion: file.find crashes on dangling symlinks
Package: salt-minion Version: 0.16.4-2~bpo70+1 Severity: important salt-call throws up an error when it encounters a dangling symlink. The bug was fixed upstream: https://github.com/saltstack/salt/issues/2830 $ sudo salt-call -l quiet --local file.find /tmp type=d Traceback (most recent call last): File "/usr/bin/salt-call", line 11, in salt_call() File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 76, in salt_call client.run() File "/usr/lib/python2.7/dist-packages/salt/cli/__init__.py", line 265, in run caller.run() File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 132, in run ret = self.call() File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 73, in call ret['return'] = func(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/salt/modules/file.py", line 480, in find ret = [p for p in finder.find(path)] File "/usr/lib/python2.7/dist-packages/salt/utils/find.py", line 555, in find fstat = os.stat(fullpath) OSError: [Errno 13] Permission denied: '/tmp/link' Please include the fix in the deb. -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages salt-minion depends on: ii dctrl-tools 2.22.2 ii python2.7.3-4+deb7u1 ii python-pkg-resources 0.6.24-1 ii salt-common 0.16.4-2~bpo70+1 Versions of packages salt-minion recommends: ii dmidecode 2.11-9 Versions of packages salt-minion suggests: pn python-augeas -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#400711: python-jinja: Typo in package description
Package: python-jinja Version: 0.9-2 Severity: minor There is a typo in the package description. "The syntax and parts of the code where taken from..." should be changed to "The syntax and parts of the code *were* taken from..." Cheers Avinash. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.9-betsi Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Versions of packages python-jinja depends on: ii python2.4.3-11 An interactive high-level object-o ii python-central0.5.11 register and build utility for Pyt Versions of packages python-jinja recommends: ii python-markdown 1.4-2 text-to-HTML conversion library/to ii python-setuptools 0.6c3-1Python Distutils Enhancements ii python-textile2.0.10-3.1 Python parser for the Textile mark ii python-xml0.8.4-5XML tools for Python -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394959: courier-mta doesn't work as expected with maildrop
Package: courier-mta Version: 0.53.2-3 Severity: important I changed the default delivery mode of Courier MTA by uncommenting the following line in /etc/courier/courierd DEFAULTDELIVERY="| /usr/bin/maildrop" and in the same file I have, by default, MAILDROPDEFAULT=./Maildir But the above setting will not affect the maildrop command given by the maildrop package. maildrop will keep delivering mails to /var/spool/mail instead of ~/Maildir because it will not read the environment variables set by courier. I can of course set the DEFAULT variable in /etc/maildroprc or install the courier-maildrop package to get this to work as expected. But inorder to avoid this confusion, I think it is good to introduce a conflict in the courier-mta package with the maildrop and add courier-maildrop to the Suggests/Recommends list. Racke, I would also like to refer to the mail sent in resopose to your query by Sam on the courier-user list. http://www.mail-archive.com/courier-users@lists.sourceforge.net/msg27350.html Cheers Avinash. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.9-betsi Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Versions of packages courier-mta depends on: ii courier-base 0.53.2-3Courier Mail Server - Base system ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-13 GCC support library ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime ii libperl5.8 5.8.8-6.1 Shared Perl library ii libstdc++6 4.1.1-13The GNU Standard C++ Library v3 courier-mta recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#390081: Typo in /etc/init.d/courier-ldap
Package: courier-ldap Version: 0.53.2-3 Severity: minor In /etc/init.d/courier-ldap, the comment in the stop section says # Stop PCP daemon It should be "Stop Courier LDAP Alias daemon" And in the same file, the indentation of the "echo done." command is wrong. Cheers Avinash. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.9-betsi Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Versions of packages courier-ldap depends on: ii courier-authlib-ldap0.58-4 LDAP support for the Courier authe ii courier-base0.53.2-3 Courier Mail Server - Base system ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libldap22.1.30-13+b1 OpenLDAP libraries courier-ldap recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387695: zope-securemailhost: Typo in package description
Package: zope-securemailhost Version: 1.0.4-1 Severity: minor The package description contains a couple of spelling mistakes * "fance HTML..." should be "fancy HTML..." * "blin carbon copy" should be "blind carbon copy" cheers Avinash. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.9-betsi Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Versions of packages zope-securemailhost depends on: ii zope-common 0.5.24 common settings and scripts for zo ii zope2.8 2.8.8-2Open Source Web Application Server ii zope2.9 2.9.4-1Open Source Web Application Server zope-securemailhost recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372307: courier-mta: Cannot open /var/lib/courier/track
Package: courier-mta Version: 0.53.2-2 Severity: normal I upgraded courier-mta from 0.47 to 0.53 after which I have been getting the following errors in my mail.log. Jun 9 17:44:30 x courierd: Cannot open /var/lib/courier/track Jun 9 17:44:30 x courierd: No such file or directory I have been using this version for about a month without any problems but I am just concerned about those lines in the log file. Avinash. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.11 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages courier-mta depends on: ii courier-base 0.53.2-2 Courier Mail Server - Base system ii libc6 2.3.6-7GNU C Library: Shared libraries ii libgcc1 1:4.1.0-1 GCC support library ii libgdbm3 1.8.3-3GNU dbm database routines (runtime ii libperl5.85.8.8-4Shared Perl library ii libstdc++64.1.0-1The GNU Standard C++ Library v3 courier-mta recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
