On 01/16/2014 06:19 AM, Robert J. Clay wrote: > Something I've found that seems to be true, at least if the > access_compat module is available (like it appears to be in Debian > Testing); if the v2.2 compatible file is left in conf.d and no 2.2 > compatible version is enabled in conf-available, it does appear to > work. This I found on a test system that was updated from wheezy to > jessie, which also updated the ledgersmb install to 1.3.25.
What does "no 2.2 compatible version is enabled in conf-available" mean? Same as, "no apache2.2 version is installed? My conf-available: john@toolbench:/etc/apache2$ ll conf-available total 24 -rw-r--r-- 1 root root 315 Jul 20 15:44 charset.conf -rw-r--r-- 1 root root 127 Jul 29 09:42 javascript-common.conf -rw-r--r-- 1 root root 3224 Jul 20 15:44 localized-error-pages.conf -rw-r--r-- 1 root root 189 Jul 20 15:44 other-vhosts-access-log.conf -rw-r--r-- 1 root root 2190 Jul 20 15:44 security.conf -rw-r--r-- 1 root root 458 Jul 20 15:44 serve-cgi-bin.conf https://wiki.debian.org/Apache2Transition is fairly confusing.. I need a practical install on a local machine soon so I can enter business data... Any suggestions appreciated. Maybe I need to simply try to get 1.3.25 working as a debian package before doing 1.3.35 or 36 fro source... ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Ledger-smb-users mailing list Ledger-smb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
