March 2013 - Arch-dev-public - lists.archlinux.org

[arch-dev-public] move dosfstools to [core]?
by Tobias Powalowski 05 Mar '13

05 Mar '13

Hi, https://bugs.archlinux.org/task/33973 due to the need of FAT support for UEFI this request was made. any objections in moving this to [core] repository? greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

1 0

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 05 Mar '13

05 Mar '13

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 8 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 11 fully signed off packages * 44 packages missing signoffs * 6 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (8 total) == * linux-3.8.2-1 (i686) * linux-lts-3.0.68-1 (i686) * openldap-2.4.34-1 (i686) * linux-3.8.2-1 (x86_64) * linux-lts-3.0.68-1 (x86_64) * openldap-2.4.34-1 (x86_64) * lsof-4.87-1 (i686) * lsof-4.87-1 (x86_64) == Incomplete signoffs for [core] (11 total) == * file-5.13-1 (i686) 1/2 signoffs * krb5-1.11.1-1 (i686) 1/2 signoffs * linux-3.8.2-1 (i686) 1/2 signoffs * linux-lts-3.0.68-1 (i686) 0/2 signoffs * logrotate-3.8.3-1 (i686) 0/2 signoffs * openldap-2.4.34-1 (i686) 0/2 signoffs * rp-pppoe-3.11-2 (i686) 0/2 signoffs * wpa_actiond-1.4-1 (i686) 0/2 signoffs * linux-lts-3.0.68-1 (x86_64) 1/2 signoffs * openldap-2.4.34-1 (x86_64) 1/2 signoffs * rp-pppoe-3.11-2 (x86_64) 0/2 signoffs == Incomplete signoffs for [extra] (30 total) == * django-1.5-1 (any) 0/2 signoffs * efilinux-efi-1.0-6 (any) 0/2 signoffs * gummiboot-efi-23-3 (any) 0/2 signoffs * gnu-efi-libs-3.0t-2 (i686) 0/2 signoffs * intel-tbb-4.1_20130116-1 (i686) 0/2 signoffs * lirc-1:0.9.0-38 (i686) 0/2 signoffs * lsof-4.87-1 (i686) 0/2 signoffs * network-manager-applet-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-openconnect-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-openvpn-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-pptp-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-vpnc-0.9.8.0-1 (i686) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-2 (i686) 0/2 signoffs * nvidia-313.18-4 (i686) 0/2 signoffs * nvidia-304xx-304.64-5 (i686) 0/2 signoffs * qemu-1.4.0-1 (i686) 0/2 signoffs * gnu-efi-libs-3.0t-2 (x86_64) 0/2 signoffs * intel-tbb-4.1_20130116-1 (x86_64) 0/2 signoffs * lirc-1:0.9.0-38 (x86_64) 0/2 signoffs * lsof-4.87-1 (x86_64) 0/2 signoffs * network-manager-applet-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-openconnect-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-openvpn-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-pptp-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-vpnc-0.9.8.0-1 (x86_64) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-2 (x86_64) 0/2 signoffs * nvidia-304xx-304.64-5 (x86_64) 0/2 signoffs * qemu-1.4.0-1 (x86_64) 1/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * netctl-0.6-1 (any) 0/2 signoffs * gummiboot-24-1 (i686) 0/2 signoffs * gummiboot-24-1 (x86_64) 0/2 signoffs == Completed signoffs (11 total) == * tzdata-2013a-1 (any) * dhcpcd-5.6.7-1 (i686) * syslinux-5.01-2 (i686) * dhcpcd-5.6.7-1 (x86_64) * file-5.13-1 (x86_64) * krb5-1.11.1-1 (x86_64) * linux-3.8.2-1 (x86_64) * logrotate-3.8.3-1 (x86_64) * syslinux-5.01-2 (x86_64) * wpa_actiond-1.4-1 (x86_64) * nvidia-313.18-4 (x86_64) == All packages in [testing] for more than 14 days (6 total) == * intel-tbb-4.1_20130116-1 (i686), since 2013-02-15 * intel-tbb-4.1_20130116-1 (x86_64), since 2013-02-15 * logrotate-3.8.3-1 (i686), since 2013-02-15 * logrotate-3.8.3-1 (x86_64), since 2013-02-15 * dhcpcd-5.6.7-1 (x86_64), since 2013-02-16 * dhcpcd-5.6.7-1 (i686), since 2013-02-16 == Top five in signoffs in last 24 hours == 1. bisson - 3 signoffs 2. pierre - 2 signoffs 3. ibiru - 2 signoffs 4. foutrelis - 1 signoffs

1 0

[arch-dev-public] Naming conventions for co-existing executables (was: qt4 replaces qt)
by Rashif Ray Rahman 05 Mar '13

05 Mar '13

On 4 March 2013 19:59, Andrea Scarpino <andrea(a)archlinux.org> wrote: > On Thursday 28 February 2013 00:14:55 you wrote: > > Please maintainers fix your PKGBUILDs so they build on systems with both > qt4 > > and qt5-base installed; when your PKGBUILD needs qt4 and: > > * use qmake, you can replace it with qmake4 > > * use cmake, you can add -DQT_QMAKE_EXECUTABLE=qmake4 to the cmake > options > > Just a note here: I had to remove the qmake4 symlink and use qmake-qt4 > instead > as the former was inconsistent with others distro. > When I did this change (1th March) qmake4 wasn't really used yet so I did > not > think to write this mail before. I'm sorry if this caused more confusion > here. I have wondered about this for a while. I think that is best convention to follow and we should apply that to all transitional packages from now on. That is, instead of: qt4-foo python2-foo or: foo4 foo2 or some other variant, we should have: foo-qt4 foo-python2 This applies to the executables only (and only when we're making the change, not upstream), and has nothing to do with the package name. It is intuitive because this way tab-completion or common sense shows you the possibilities in case you have upgraded. However, I am not sure how portable this convention is and whether other distros are likely to behave the same way. Still, 'foo4' is very misleading as the '4' is a version number of a dependency, and not of the program itself. -- GPG/PGP ID: C0711BF1

1 0

[arch-dev-public] [RFC] Migration to MariaDB
by Bartłomiej Piotrowski 04 Mar '13

04 Mar '13

Hello guys, Because Oracle is Oracle is Oracle(…) I would like to propose migration to MariaDB. Jokes aside, the biggest problem with MySQL situation is that it becomes more and more closed source. Oracle stopped publishing regression tests[1], informative security advisories, they even hide bug reports and not include them in release notes[2]. Very often their bzr repository is falling behind new releases[3]. On the other hand, MariaDB is truly open source (it doesn't have enterprise-only options) and has open development model. Security advisories are published first on the mailing list for packagers with a patch for current release and information when the bug will be fixed and when the information about security hole can be published (Another advantage for ricers -- some benchmarks show that MariaDB is faster.) From packaging side, MariaDB is (still) drop-in replacement for MySQL. Unfortunately they are not fully compatible[4] and I don't want to lie that I tested every package depending on MySQL before I pushed Maria to [community], but since April 2012 there has been no bug report about breakage. However I don't want to use replaces=, because clearly it won't work for everyone. Additionally switching now should be less problematic. MySQL 5.6 is already out and it is not as compatible with incoming MariaDB 10 as it was with 5.5 branch. While we keep Maria and MySQL branches in sync, it should be quite safe. To get back to the point… This is how I would see the migration plan: 1. Synchronize MariaDB and MySQL systemd units. 2. Move MariaDB to [extra]. 3. Rebuild packages depending on mysql/libmysqlclient/mysql-clients against its MariaDB counterparts. 4. Announce MySQL deprecation. 5. After month, drop MySQL to AUR. What do you think? Cheers, [1] http://blog.mariadb.org/disappearing-test-cases/ [2] http://ronaldbradford.com/blog/when-is-a-crashing-mysql-bug-not-a-bug-2012-… [3] http://www.mysqlperformanceblog.com/2012/08/16/where-to-get-a-bzr-tree-of-t… [4] https://kb.askmonty.org/en/mariadb-vs-mysql-compatibility -- Bartłomiej Piotrowski http://bpiotrowski.pl/

7 7

[arch-dev-public] qt4 replaces qt
by Andrea Scarpino 04 Mar '13

04 Mar '13

Hi all, a new qt4 package has hit [testing] and will replace the current qt package. qt4 doesn't provide 'qt'; you will need to rebuild EVERY package installed from AUR and replace qt with qt4 in the depends array. Also, I suggest to every maintainer in AUR to remove qt from the depends() array when there's qtwebkit or any package that needs qt: if you do that, this will require no rebuild as we updated every package in the official repositories to use qt4. Also, we ship the Qt 5.x series in [testing]. Qt 5.x is more modular than 4.x. This allow us to have these Qt 5.x packages: * qt5-base * qt5-declarative * qt5-graphicaleffects * qt5-imageformats * qt5-jsbackend * qt5-multimedia * qt5-quick1 * qt5-script * qt5-svg * qt5-tools * qt5-translations * qt5-webkit * qt5-xmlpatterns Generally you only need qt5-base. But, if you are a Qt developer or you want a full installation you can install the whole 'qt' group. When you install both qt5-base and qt4, qmake will refers to the 5.x version. To 'force' Qt 4.x, you can use the qmake4 symlink. There's also moc-qt4, uic- qt4 and rcc-qt4. We provide these symlinks as they are used by cmake and by the configure scripts to locate qt4. -- Andrea Arch Linux Developer

1 2

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 04 Mar '13

04 Mar '13

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 3 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 9 fully signed off packages * 42 packages missing signoffs * 6 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (3 total) == * tzdata-2013a-1 (any) * linux-lts-3.0.67-1 (i686) * linux-lts-3.0.67-1 (x86_64) == Incomplete signoffs for [core] (11 total) == * tzdata-2013a-1 (any) 1/2 signoffs * file-5.13-1 (i686) 1/2 signoffs * krb5-1.11.1-1 (i686) 1/2 signoffs * linux-3.8.1-1 (i686) 1/2 signoffs * linux-lts-3.0.67-1 (i686) 0/2 signoffs * logrotate-3.8.3-1 (i686) 0/2 signoffs * rp-pppoe-3.11-2 (i686) 0/2 signoffs * syslinux-5.01-2 (i686) 1/2 signoffs * wpa_actiond-1.4-1 (i686) 0/2 signoffs * linux-lts-3.0.67-1 (x86_64) 1/2 signoffs * rp-pppoe-3.11-2 (x86_64) 0/2 signoffs == Incomplete signoffs for [extra] (28 total) == * django-1.5-1 (any) 0/2 signoffs * efilinux-efi-1.0-6 (any) 0/2 signoffs * gummiboot-efi-23-3 (any) 0/2 signoffs * gnu-efi-libs-3.0t-2 (i686) 0/2 signoffs * intel-tbb-4.1_20130116-1 (i686) 0/2 signoffs * lirc-1:0.9.0-38 (i686) 0/2 signoffs * network-manager-applet-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-openconnect-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-openvpn-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-pptp-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-vpnc-0.9.8.0-1 (i686) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-2 (i686) 0/2 signoffs * nvidia-313.18-4 (i686) 0/2 signoffs * nvidia-304xx-304.64-5 (i686) 0/2 signoffs * qemu-1.4.0-1 (i686) 0/2 signoffs * gnu-efi-libs-3.0t-2 (x86_64) 0/2 signoffs * intel-tbb-4.1_20130116-1 (x86_64) 0/2 signoffs * lirc-1:0.9.0-38 (x86_64) 0/2 signoffs * network-manager-applet-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-openconnect-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-openvpn-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-pptp-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-vpnc-0.9.8.0-1 (x86_64) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-2 (x86_64) 0/2 signoffs * nvidia-304xx-304.64-5 (x86_64) 0/2 signoffs * qemu-1.4.0-1 (x86_64) 1/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * netctl-0.6-1 (any) 0/2 signoffs * gummiboot-24-1 (i686) 0/2 signoffs * gummiboot-24-1 (x86_64) 0/2 signoffs == Completed signoffs (9 total) == * dhcpcd-5.6.7-1 (i686) * dhcpcd-5.6.7-1 (x86_64) * file-5.13-1 (x86_64) * krb5-1.11.1-1 (x86_64) * linux-3.8.1-1 (x86_64) * logrotate-3.8.3-1 (x86_64) * syslinux-5.01-2 (x86_64) * wpa_actiond-1.4-1 (x86_64) * nvidia-313.18-4 (x86_64) == All packages in [testing] for more than 14 days (6 total) == * intel-tbb-4.1_20130116-1 (i686), since 2013-02-15 * intel-tbb-4.1_20130116-1 (x86_64), since 2013-02-15 * logrotate-3.8.3-1 (i686), since 2013-02-15 * logrotate-3.8.3-1 (x86_64), since 2013-02-15 * dhcpcd-5.6.7-1 (x86_64), since 2013-02-16 * dhcpcd-5.6.7-1 (i686), since 2013-02-16 == Top five in signoffs in last 24 hours == 1. foutrelis - 10 signoffs 2. dan - 2 signoffs

1 0

[arch-dev-public] cleaning up unneeded static libraries?
by Andreas Radke 03 Mar '13

03 Mar '13

Our packages in our repos by default don't need static libraries (random .a files all around). I think they are a waste of disc space and abuse bandwidth when uploading/mirroring packages. Most users will never need them. I suggest to drop all static libs by creating a ToDo list and install a rule to not ship static libraries anymore, maybe with some exceptions. Whenever users require static libs we should point to abs. Opinions? [andyrtr@workstation64 ~]$ pkgfile -v -g /usr/lib/\*.a | sort | wc -l 3417 There are probably more in other directories. -Andy

8 10

[arch-dev-public] Signoff report for [testing]
by Arch Website Notification 03 Mar '13

03 Mar '13

=== Signoff report for [testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 1 new package in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 13 fully signed off packages * 66 packages missing signoffs * 6 packages older than 14 days (Note: the word 'package' as used here refers to packages as grouped by pkgbase, architecture, and repository; e.g., one PKGBUILD produces one package per architecture, even if it is a split package.) == New packages in [testing] in last 24 hours (1 total) == * netctl-0.6-1 (any) == Incomplete signoffs for [core] (13 total) == * hwids-20130228-1 (any) 1/2 signoffs * file-5.13-1 (i686) 0/2 signoffs * krb5-1.11.1-1 (i686) 1/2 signoffs * libarchive-3.1.2-1 (i686) 0/2 signoffs * libgpg-error-1.11-1 (i686) 0/2 signoffs * linux-3.8.1-1 (i686) 1/2 signoffs * linux-lts-3.0.66-1 (i686) 0/2 signoffs * logrotate-3.8.3-1 (i686) 0/2 signoffs * pacman-4.0.3-7 (i686) 0/2 signoffs * rp-pppoe-3.11-2 (i686) 0/2 signoffs * syslinux-5.01-2 (i686) 0/2 signoffs * wpa_actiond-1.4-1 (i686) 0/2 signoffs * rp-pppoe-3.11-2 (x86_64) 0/2 signoffs == Incomplete signoffs for [extra] (50 total) == * django-1.5-1 (any) 0/2 signoffs * efilinux-efi-1.0-6 (any) 0/2 signoffs * gummiboot-efi-23-3 (any) 0/2 signoffs * claws-mail-extra-plugins-3.9.0-2 (i686) 0/2 signoffs * cmake-2.8.10.2-4 (i686) 0/2 signoffs * evince-3.6.1-2 (i686) 0/2 signoffs * file-roller-3.6.3-2 (i686) 0/2 signoffs * gnu-efi-libs-3.0t-2 (i686) 0/2 signoffs * gvfs-1.14.2-4 (i686) 0/2 signoffs * hydrogen-0.9.5.1-3 (i686) 0/2 signoffs * intel-tbb-4.1_20130116-1 (i686) 0/2 signoffs * kdeutils-ark-4.10.0-2 (i686) 0/2 signoffs * libgxps-0.2.2-2 (i686) 0/2 signoffs * lirc-1:0.9.0-38 (i686) 0/2 signoffs * network-manager-applet-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-openconnect-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-openvpn-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-pptp-0.9.8.0-1 (i686) 0/2 signoffs * networkmanager-vpnc-0.9.8.0-1 (i686) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-2 (i686) 0/2 signoffs * nvidia-313.18-4 (i686) 0/2 signoffs * nvidia-304xx-304.64-5 (i686) 0/2 signoffs * pkgfile-8-2 (i686) 0/2 signoffs * qemu-1.4.0-1 (i686) 0/2 signoffs * raptor-2.0.9-1 (i686) 0/2 signoffs * totem-plparser-3.4.3-2 (i686) 0/2 signoffs * claws-mail-extra-plugins-3.9.0-2 (x86_64) 0/2 signoffs * cmake-2.8.10.2-4 (x86_64) 0/2 signoffs * evince-3.6.1-2 (x86_64) 0/2 signoffs * file-roller-3.6.3-2 (x86_64) 0/2 signoffs * gnu-efi-libs-3.0t-2 (x86_64) 0/2 signoffs * gvfs-1.14.2-4 (x86_64) 0/2 signoffs * hydrogen-0.9.5.1-3 (x86_64) 0/2 signoffs * intel-tbb-4.1_20130116-1 (x86_64) 0/2 signoffs * kdeutils-ark-4.10.0-2 (x86_64) 0/2 signoffs * libgxps-0.2.2-2 (x86_64) 0/2 signoffs * lirc-1:0.9.0-38 (x86_64) 0/2 signoffs * network-manager-applet-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-openconnect-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-openvpn-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-pptp-0.9.8.0-1 (x86_64) 0/2 signoffs * networkmanager-vpnc-0.9.8.0-1 (x86_64) 0/2 signoffs * ntfs-3g_ntfsprogs-2013.1.13-2 (x86_64) 0/2 signoffs * nvidia-304xx-304.64-5 (x86_64) 0/2 signoffs * pkgfile-8-2 (x86_64) 0/2 signoffs * qemu-1.4.0-1 (x86_64) 1/2 signoffs * raptor-2.0.9-1 (x86_64) 0/2 signoffs * totem-plparser-3.4.3-2 (x86_64) 0/2 signoffs == Incomplete signoffs for [unknown] (3 total) == * netctl-0.6-1 (any) 0/2 signoffs * gummiboot-24-1 (i686) 0/2 signoffs * gummiboot-24-1 (x86_64) 0/2 signoffs == Completed signoffs (13 total) == * dhcpcd-5.6.7-1 (i686) * dhcpcd-5.6.7-1 (x86_64) * file-5.13-1 (x86_64) * krb5-1.11.1-1 (x86_64) * libarchive-3.1.2-1 (x86_64) * libgpg-error-1.11-1 (x86_64) * linux-3.8.1-1 (x86_64) * linux-lts-3.0.66-1 (x86_64) * logrotate-3.8.3-1 (x86_64) * pacman-4.0.3-7 (x86_64) * syslinux-5.01-2 (x86_64) * wpa_actiond-1.4-1 (x86_64) * nvidia-313.18-4 (x86_64) == All packages in [testing] for more than 14 days (6 total) == * intel-tbb-4.1_20130116-1 (i686), since 2013-02-15 * intel-tbb-4.1_20130116-1 (x86_64), since 2013-02-15 * logrotate-3.8.3-1 (i686), since 2013-02-15 * logrotate-3.8.3-1 (x86_64), since 2013-02-15 * dhcpcd-5.6.7-1 (x86_64), since 2013-02-16 * dhcpcd-5.6.7-1 (i686), since 2013-02-16 == Top five in signoffs in last 24 hours == 1. andyrtr - 3 signoffs

1 0

[arch-dev-public] [RFC] Add Wayland/Weston
by Sébastien Luttringer 03 Mar '13

03 Mar '13

Hello gentleman, Wayland is now in version 1.0.4[1]. I plan to move it to community to offer a first support of the wayland protocol into Archlinux. This will allow toolkit[2][3] packages to smoothly enable wayland support when maintainers wants and let users try this next-to-systemd-troll[4]. After Wayland I would add the demo compositor Weston to our community repositories. To do this we needs to: - enable wayland support into mesa ; - enable wayland support into cairo. If the both maintainers agreed to add support, we need to find a gentle developper which can move wayland to extra[5]. Cheers, [1] http://wayland.freedesktop.org/releases.html [2] http://wayland.freedesktop.org/qt5.html [3] http://wayland.freedesktop.org/gtk.html [4] I'm already existed by arch-general be closed again [5] Mesa and cairo are in extra and cannot depends of Wayland in community -- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A

8 14

Re: [arch-dev-public] [aur-general] Substitute nss_ldap/pam_ldap from [Extra] to nss-pam-ldapd
by Dave Reisner 02 Mar '13

02 Mar '13

On Sat, Mar 02, 2013 at 01:32:48PM -0300, Thiago Kenji Okada wrote: > nss-pam-ldapd is actively maintained while nss_ldap/pam_ldap are not > updated in a while. nss-pam-ldapd is more robust too (I had a similar > problem like https://bugs.archlinux.org/task/33672 that didn't occur with > nss-pam-ldapd; and according to that bug report actually a > nss_ldap/pam_ldap setup is simply broken). According to the author ( > http://arthurdejong.org/nss-pam-ldapd/) nss-pam-ldapd is faster and more > easily to debug (I didn't measured performance, but indeed nss-pam-ldapd is > easier to debug, since it's service nslcd have a nice log output). I think > Fedora and Mageia uses nss-pam-ldapd for default instead nss_ldap/pam_ldap. > Even our Wiki (https://wiki.archlinux.org/index.php/OpenLDAP_Authentication) > is recommending nss-pam-ldapd instead of nss_ldap/pam_ldap (actually, if > you follow our Wiki using nss_ldap/pam_ldap you will have a non-working > LDAP setup). > > So I suggest to drop nss_ldap/pam_ldap to AUR and put nss-pam-ldapd on > [Extra] repository. > -- > Thiago Kenji Okada <thiago.mast3r(a)gmail.com> > PGP Key: EEC09705 Looks like there's already a feature request: https://bugs.archlinux.org/task/32911 @Tom and Allan, you guys maintain the packages that would be replaced here -- either of you have an interest in adopting this? d

1 1