On Thu, Jan 14, 2010 at 09:18:47PM -0600, Gunnar Wolf wrote:
> severity 565316 grave
> thanks
>
> Joaquín Aguirrezabalaga dijo [Thu, Jan 14, 2010 at 08:00:29PM +0100]:
> > The libcherokee-server0 package on i386 is missing the default Cherokee
> > plugins located in /usr/lib/cherokee.
> >
> > On a different computer using amd64 I can see a lot of plugins on
> > /usr/lib/cherokee included with the libcherokee-server0 package.
> >
> > The output of "dpkg -L libcherokee-server0" shows this plugins in the
> > packages for the amd64 architecture, but not on the i386 deb package.
>
> Ugh! This is grave indeed. I will look into it right away.
Hello Gunnar,
Something seems still wrong with 0.99.39-3:
$ debdiff libcherokee-server0_0.99.39-3_i386.deb
libcherokee-server0_0.99.39-3_amd64.deb
Files in first .deb but not in second
-------------------------------------
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_and.so
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_authlist.so
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_bind.so
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_cgi.so
...
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_url_arg.so
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_uwsgi.so
-rw-r--r-- root/root /usr/lib/cherokee/libplugin_wildcard.so
Control files: lines which differ (wdiff format)
------------------------------------------------
Architecture: [-i386-] {+amd64+}
Depends: libc6 (>= [-2.3.6-6~),-] {+2.2.5),+} libcherokee-base0,
[-libcherokee-client0, libcherokee-config0, libmysqlclient16-] {+libpcre3+} (>=
[-5.1.21-1), libpam0g (>= 0.99.7.1),-] {+7.7),+} libssl0.9.8 (>= [-0.9.8k-1),
zlib1g (>= 1:1.1.4)-] {+0.9.8k-1)+}
Installed-Size: [-1072-] {+560+}
So it looks like now it is the amd64 which is missing the plugin.
I suggest you add a check in debian/rules that abort the build if plugin
are not installed.
Also there is a circular dependency between libcherokee-config0 and
libcherokee-server0.
Cheers,
--
Bill. <[email protected]>
Imagine a large red swirl here.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
