Hi, I see your "build from source" seems to mean "build from the Debian source package". (Normally, build from source is from the upstream source. Debian package is patched)
On Tue, Jan 06, 2015 at 03:27:47PM +0100, Willy De la Court wrote: > Not effective. > Installed courier-authdaemon, courier-authlib,courier-authlib-dev,courier- > authlib-mysql and maildrop packages from the repo > > Using the maildrop package from the repository does not connect to the > authdaemon and use the configure and the running authdaemon. > > Effective. > Rebuild maildrop from the source package WITHOUT changes > installed the newly build package solves the problem that maildrop does not > connect to the authdaemon. OK. But what is your environment. sid? chroot under pbuilder? > > > Installed courier-authdaemon, courier-authlib,courier-authlib-dev, > > > courier-authlib-mysql and rebuild the maildrop package. > > Please read the question again and address all the points. > > > > > * What was the outcome of this action? > > > > > > After the rebuild from source and installing the build maildrop package > > > it worked. > > Rebuild maildrop from the source package WITHOUT changes installed the > newly build package solves the problem that maildrop does not connect > to the authdaemon. I suspect that the rebuild picked up on the > courier-authlib-dev and configured the package differently to include > the authlib support. OK. Now I see what you mean. Can you do the following. $ cd tmp $ mkdir maildrop $ cd maildrop $ dget maildrop dget: retrieving http://ftp.jp.debian.org/debian/pool/main/m/maildrop/maildrop_2.7.1-2_amd64.deb $ mv maildrop_2.7.1-2_amd64.deb maildrop_2.7.1-2_amd64x.deb $ apt-get source maildrop $ sudo apt-get build-dep maildrop $ cd maildrop-2.7.1 $ debuild $ cd .. $ debdiff maildrop_2.7.1-2_amd64x.deb maildrop_2.7.1-2_amd64.deb File lists identical (after any substitutions) Control files: lines which differ (wdiff format) ------------------------------------------------ Depends: libc6 (>= 2.15), libgcc1 (>= 1:4.1.1), libgdbm3 (>= 1.8.3), libpcre3 (>= [-8.10),-] {+1:8.35),+} libstdc++6 (>= 4.4.0) What I am after is the difference in package you have and one in archive. Hmmm... possibly library bug is fixed???. I may need to bin NMU. I do not see 8.10 in changelog of pcre3 ... strange Show me your case. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
