Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Ryan Tandy]

On Fri, Aug 12, 2016 at 12:08:43AM +0200, Julian Andres Klode wrote:

Hey, it's been 3 months, what's your status on this?


Oh, man. Time flies, eh? :(

Last status was this:

http://lists.alioth.debian.org/pipermail/pkg-openldap-devel/2016-June/006723.html

and it's still current.

I want to say I might be able to upload something (maybe just the 
pending RC fixes) "soon", but given I haven't found time in the past 3 
months to move anything forward at all, that seems unwise...

Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Julian Andres Klode]

On Tue, May 10, 2016 at 12:50:19PM -0700, Ryan Tandy wrote:
> On Tue, May 10, 2016 at 09:21:56PM +0200, Helmut Grohne wrote:
> > Control: severity -1 serious
> > Control: tags -1 + patch
> 
> Thanks for the update and patch. I'm dropping Russ from CC because he is no
> longer actively involved in maintaining openldap. I will try to get this
> uploaded ASAP.

Hey, it's been 3 months, what's your status on this?

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev

When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to (`inline'). Thank you.

Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Ryan Tandy]

On Tue, May 10, 2016 at 09:21:56PM +0200, Helmut Grohne wrote:

Control: severity -1 serious
Control: tags -1 + patch


Thanks for the update and patch. I'm dropping Russ from CC because he is 
no longer actively involved in maintaining openldap. I will try to get 
this uploaded ASAP.

Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Helmut Grohne]

Control: severity -1 serious
Control: tags -1 + patch

On Sun, Jul 13, 2008 at 07:47:31PM -0700, Russ Allbery wrote:
> I see that we're indeed still shipping /etc/ldap/ldap.conf in the library
> package.  This is a Policy violation (8.2); we really should do something
> about it.

I confirm that this is indeed a policy violation and raise the severity
accordingly.

> All values are commented-out in the default version and the library seems
> to run fine if the file is missing entirely.  I propose we just move the
> file into /usr/share/doc/libldap-2.4-2/examples and mention it in
> README.Debian.  Any objections?

In your later mail, you proposed to move it to libldap-common. I
implemented the move of the config file and the manual page in the
attached patch and verified it using piuparts.

Helmut
--- openldap-2.4.42+dfsg/debian/changelog
+++ openldap-2.4.42+dfsg/debian/changelog
@@ -1,3 +1,11 @@
+openldap (2.4.42+dfsg-2.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Fix policy 8.2 violation (Closes: #330695)
++ Move /etc/ldap/ldap.conf and manpage to new package libldap-common.
+
+ -- Helmut Grohne   Tue, 10 May 2016 17:41:23 +0200
+
 openldap (2.4.42+dfsg-2) unstable; urgency=medium
 
   [ Ryan Tandy ]
--- openldap-2.4.42+dfsg/debian/control
+++ openldap-2.4.42+dfsg/debian/control
@@ -86,12 +86,22 @@
 Multi-Arch: same
 Conflicts: ldap-utils (<= 2.1.23-1)
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libldap-common (= 
${source:Version})
 Replaces: libldap2, libldap-2.3-0
 Description: OpenLDAP libraries 
  These are the run-time libraries for the OpenLDAP (Lightweight Directory
  Access Protocol) servers and clients.
 
+Package: libldap-common
+Section: libs
+Priority: standard
+Architecture: all
+Multi-Arch: foreign
+Replaces: libldap-2.4-2 (<< 2.4.42+dfsg-2.1)
+Description: OpenLDAP common files for libraries
+ These are common files for the run-time libraries for the OpenLDAP
+ (Lightweight Directory Access Protocol) servers and clients.
+
 Package: libldap-2.4-2-dbg
 Section: debug
 Priority: extra
--- openldap-2.4.42+dfsg/debian/libldap-2.4-2.install
+++ openldap-2.4.42+dfsg/debian/libldap-2.4-2.install
@@ -2,4 +2,3 @@
 usr/lib/*/liblber-2.4.so.2.*.*
 usr/lib/*/libldap_r-2.4.so.2
 usr/lib/*/libldap_r-2.4.so.2.*.*
-etc/ldap/ldap.conf
--- openldap-2.4.42+dfsg/debian/libldap-2.4-2.manpages
+++ openldap-2.4.42+dfsg/debian/libldap-2.4-2.manpages
@@ -1 +0,0 @@
-debian/tmp/usr/share/man/man5/ldap.conf.5
--- openldap-2.4.42+dfsg/debian/libldap-common.install
+++ openldap-2.4.42+dfsg/debian/libldap-common.install
@@ -0,0 +1 @@
+etc/ldap/ldap.conf
--- openldap-2.4.42+dfsg/debian/libldap-common.manpages
+++ openldap-2.4.42+dfsg/debian/libldap-common.manpages
@@ -0,0 +1 @@
+debian/tmp/usr/share/man/man5/ldap.conf.5

Bug#330695: [Pkg-openldap-devel] Bug#330695: Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Russ Allbery]

Steve Langasek [EMAIL PROTECTED] writes:

 I'm concerned that not shipping the default config file in a package
 somewhere would make this less discoverable for users; and while I don't
 think we want to ship a completely separate binary package just for the
 ldap.conf(5) manpage, if we don't also split the manpage out then we'll
 still have problems for multiarch, AFAICS.

 So I think having a small -common package of some sort is ultimately the
 better answer.

Good point.

Do we want to call it libldap-common or libldap-config?  (-runtime,
-tools, and -utils aren't appropriate in this case.)

I can make this change and add the new package for the next release, or we
can wait until after one more upload to get some more bug fixes before it
sits in NEW; not sure what the best approach is.

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Steve Langasek]

On Sun, Jul 13, 2008 at 07:47:31PM -0700, Russ Allbery wrote:
 Goswin von Brederlow [EMAIL PROTECTED] writes:

  If you write the file in postinst (then probably using ucf) you would
  have to remove the file in postrm on purge. But if lidldap2 and libldap3
  are installed and libldap2 is purged the conffile must remain. Same
  under multiarch if libldap2:i386 and libldap2:amd64 are installed and
  one is purged.

  Currently a file just can't belong to 2 packages without causing
  problems.

 I see that we're indeed still shipping /etc/ldap/ldap.conf in the library
 package.  This is a Policy violation (8.2); we really should do something
 about it.

 All values are commented-out in the default version and the library seems
 to run fine if the file is missing entirely.  I propose we just move the
 file into /usr/share/doc/libldap-2.4-2/examples and mention it in
 README.Debian.  Any objections?

I'm concerned that not shipping the default config file in a package
somewhere would make this less discoverable for users; and while I don't
think we want to ship a completely separate binary package just for the
ldap.conf(5) manpage, if we don't also split the manpage out then we'll
still have problems for multiarch, AFAICS.

So I think having a small -common package of some sort is ultimately the
better answer.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Russ Allbery]

Goswin von Brederlow [EMAIL PROTECTED] writes:

 If you write the file in postinst (then probably using ucf) you would
 have to remove the file in postrm on purge. But if lidldap2 and libldap3
 are installed and libldap2 is purged the conffile must remain. Same
 under multiarch if libldap2:i386 and libldap2:amd64 are installed and
 one is purged.

 Currently a file just can't belong to 2 packages without causing
 problems.

I see that we're indeed still shipping /etc/ldap/ldap.conf in the library
package.  This is a Policy violation (8.2); we really should do something
about it.

All values are commented-out in the default version and the library seems
to run fine if the file is missing entirely.  I propose we just move the
file into /usr/share/doc/libldap-2.4-2/examples and mention it in
README.Debian.  Any objections?

-- 
Russ Allbery ([EMAIL PROTECTED])   http://www.eyrie.org/~eagle/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Goswin von Brederlow]

Package: libldap2
Version: 2.1.30-8
Severity: normal

Hi,

when trying to use libldap2 under biarch/multiarch I get the following error:

Unpacking libldap2 (from .../libldap2_2.1.30-8_i386.deb) ...
dpkg: error processing 
/data/deb-amd64/debian/pool/main/o/openldap2/libldap2_2.1.30-8_i386.deb 
(--unpack):
 trying to overwrite `/etc/ldap/ldap.conf', which is also in package lib64ldap2

While multiarch is still experimental the same problem will appear if there is
a soname change. libldap3 would have to conflict with libldap2 which would be
rarther bad for obvious reasons.

A clean way to handle this would be a ldap2-common package that handles the
conffile.

MfG
Goswin

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.4.27-rc5+skas3+acl
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libldap2 depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libgnutls11 1.0.16-13.1  GNU TLS library - runtime library
ii  libsasl22.1.19-1.5   Authentication abstraction library

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Torsten Landschoff]

Hi Goswin, 

On Thu, Sep 29, 2005 at 10:39:23AM +, Goswin von Brederlow wrote:
 
 A clean way to handle this would be a ldap2-common package that handles the
 conffile.
 
I don't like having a package for just a single config file. If
multiarch is the way we are going I'll surely support it as well. Maybe
it would make even more sense not to ship the config file at all but
write in from postinst or something...

Greetings

Torsten


signature.asc
Description: Digital signature

Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Goswin von Brederlow]

Torsten Landschoff [EMAIL PROTECTED] writes:

 Hi Goswin, 

 On Thu, Sep 29, 2005 at 10:39:23AM +, Goswin von Brederlow wrote:
  
 A clean way to handle this would be a ldap2-common package that handles the
 conffile.
  
 I don't like having a package for just a single config file. If
 multiarch is the way we are going I'll surely support it as well. Maybe
 it would make even more sense not to ship the config file at all but
 write in from postinst or something...

 Greetings

   Torsten

It is indeed ugly but I don't see any other way. And as I said you
need this for soname changes anyway.

If you write the file in postinst (then probably using ucf) you would
have to remove the file in postrm on purge. But if lidldap2 and
libldap3 are installed and libldap2 is purged the conffile must
remain. Same under multiarch if libldap2:i386 and libldap2:amd64 are
installed and one is purged.

Currently a file just can't belong to 2 packages without causing
problems.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]