FTBFS (dh_link fails)

Bug #7420 reported by Debian Bug Importer
4
Affects Status Importance Assigned to Milestone
libbonobo (Debian)
Fix Released
Unknown
libbonobo (Ubuntu)
Invalid
High
Unassigned

Bug Description

Automatically imported from Debian bug report #265414 http://bugs.debian.org/265414

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #265414 http://bugs.debian.org/265414

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Fri, 13 Aug 2004 04:17:14 +0200
From: Robert Millan <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: FTBFS (dh_link fails)

Package: libbonobo
Severity: serious

[...]
dh_link -plibbonobo2-dev
dh_link: link destination debian/libbonobo2-dev/usr/share/doc/libbonobo2-dev is a directory
make: *** [binary-install/libbonobo2-dev] Error 1

I could reproduce this with either -B, -b or full compile.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to C)

Revision history for this message
In , Florian Ernst (florian-uni-hd) wrote :

This is most probably due to the newer cdbs which changed the order of
some calls, see #264668 for reference.

Cheers,
Flo

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <20040813163658.GD15360@live>
Date: Fri, 13 Aug 2004 18:36:58 +0200
From: Florian Ernst <email address hidden>
To: <email address hidden>
Subject: Re: FTBFS (dh_link fails)

--J5MfuwkIyy7RmF4Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

This is most probably due to the newer cdbs which changed the order of
some calls, see #264668 for reference.

Cheers,
Flo

--J5MfuwkIyy7RmF4Q
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBHO4qs3U+TVFLPnwRAmVfAJ97yk363y9RQLQzQGi+SpMMWKDJYwCfTEKI
sEpXuIyZkVXmrH9SPdfR9cU=
=mi5c
-----END PGP SIGNATURE-----

--J5MfuwkIyy7RmF4Q--

Revision history for this message
In , Robert Millan (rmh) wrote : dh_link failure

Hi Joey,

Please could you have a look at #265414 ? Looks to me like dh_link is too
restrictive. Did you add the directory check recently?

--
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 02:22:01 +0200
From: Robert Millan <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: dh_link failure

Hi Joey,

Please could you have a look at #265414 ? Looks to me like dh_link is too
restrictive. Did you add the directory check recently?

--
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))

Revision history for this message
In , Joey Hess (joeyh) wrote :

Robert Millan wrote:
> Please could you have a look at #265414 ? Looks to me like dh_link is too
> restrictive. Did you add the directory check recently?

dh_link has never supported a destination that is an existing directory
because the correct behavior is unclear. Some users expect the existing
directory to be rm -rf'd and replaced with a symlink. Some expect a
symlink to land inside the destination directory. The latter behavior
was the behavior of dh_link until 4.1.67, when I learned that the
behavior existed, and was broken, and disabled it. The behavior you want
has never been the behavior of dh_link. It is closer to correct
behavior, but given than there could still be packages that expect the
old behavior, I prefer to leave the error message in for a while to give
them time to be fixed.

--
see shy jo

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 09:30:34 +0100
From: Joey Hess <email address hidden>
To: Robert Millan <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: dh_link failure

--FL5UXtIhxfXey3p5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Robert Millan wrote:
> Please could you have a look at #265414 ? Looks to me like dh_link is too
> restrictive. Did you add the directory check recently?

dh_link has never supported a destination that is an existing directory
because the correct behavior is unclear. Some users expect the existing
directory to be rm -rf'd and replaced with a symlink. Some expect a
symlink to land inside the destination directory. The latter behavior
was the behavior of dh_link until 4.1.67, when I learned that the
behavior existed, and was broken, and disabled it. The behavior you want
has never been the behavior of dh_link. It is closer to correct
behavior, but given than there could still be packages that expect the
old behavior, I prefer to leave the error message in for a while to give
them time to be fixed.

--=20
see shy jo

--FL5UXtIhxfXey3p5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBIxOpd8HHehbQuO8RAr+cAKDI2DG/pT8sNRzwaHLBzLkmwNDjSACfc9dN
Hx0TdOAieqY+w6XxDzzo6Aw=
=Gv9W
-----END PGP SIGNATURE-----

--FL5UXtIhxfXey3p5--

Revision history for this message
In , Robert Millan (rmh) wrote :

On Wed, Aug 18, 2004 at 09:30:34AM +0100, Joey Hess wrote:
> Robert Millan wrote:
> > Please could you have a look at #265414 ? Looks to me like dh_link is too
> > restrictive. Did you add the directory check recently?
>
> dh_link has never supported a destination that is an existing directory
> because the correct behavior is unclear. Some users expect the existing
> directory to be rm -rf'd and replaced with a symlink. Some expect a
> symlink to land inside the destination directory. The latter behavior
> was the behavior of dh_link until 4.1.67, when I learned that the
> behavior existed, and was broken, and disabled it. The behavior you want
> has never been the behavior of dh_link. It is closer to correct
> behavior, but given than there could still be packages that expect the
> old behavior, I prefer to leave the error message in for a while to give
> them time to be fixed.

Ok that was pretty clarifying. Could you document this with your explanation?
I suggest adding a note to the manpage and refer to it in the error message.

--
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 13:37:16 +0200
From: Robert Millan <email address hidden>
To: Joey Hess <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: dh_link failure

On Wed, Aug 18, 2004 at 09:30:34AM +0100, Joey Hess wrote:
> Robert Millan wrote:
> > Please could you have a look at #265414 ? Looks to me like dh_link is too
> > restrictive. Did you add the directory check recently?
>
> dh_link has never supported a destination that is an existing directory
> because the correct behavior is unclear. Some users expect the existing
> directory to be rm -rf'd and replaced with a symlink. Some expect a
> symlink to land inside the destination directory. The latter behavior
> was the behavior of dh_link until 4.1.67, when I learned that the
> behavior existed, and was broken, and disabled it. The behavior you want
> has never been the behavior of dh_link. It is closer to correct
> behavior, but given than there could still be packages that expect the
> old behavior, I prefer to leave the error message in for a while to give
> them time to be fixed.

Ok that was pretty clarifying. Could you document this with your explanation?
I suggest adding a note to the manpage and refer to it in the error message.

--
Robert Millan

(Debra and Ian) (Gnu's Not (UNiplexed Information and Computing System))/\
(kernel of *(Berkeley Software Distribution))

Revision history for this message
LaMont Jones (lamont) wrote :

not a warty bug

Revision history for this message
In , Josselin Mouette (joss) wrote : Bug#265414: fixed in libbonobo 2.6.2-6

Source: libbonobo
Source-Version: 2.6.2-6

We believe that the bug you reported is fixed in the latest version of
libbonobo, which is due to be installed in the Debian FTP archive:

libbonobo2-0_2.6.2-6_i386.deb
  to pool/main/libb/libbonobo/libbonobo2-0_2.6.2-6_i386.deb
libbonobo2-common_2.6.2-6_i386.deb
  to pool/main/libb/libbonobo/libbonobo2-common_2.6.2-6_i386.deb
libbonobo2-dev_2.6.2-6_i386.deb
  to pool/main/libb/libbonobo/libbonobo2-dev_2.6.2-6_i386.deb
libbonobo_2.6.2-6.diff.gz
  to pool/main/libb/libbonobo/libbonobo_2.6.2-6.diff.gz
libbonobo_2.6.2-6.dsc
  to pool/main/libb/libbonobo/libbonobo_2.6.2-6.dsc

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <email address hidden> (supplier of updated libbonobo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 21 Aug 2004 12:22:18 +0200
Source: libbonobo
Binary: libbonobo2-dev libbonobo2-common libbonobo2-0
Architecture: source i386
Version: 2.6.2-6
Distribution: unstable
Urgency: high
Maintainer: Takuo KITAME <email address hidden>
Changed-By: Josselin Mouette <email address hidden>
Description:
 libbonobo2-0 - Bonobo CORBA interfaces library
 libbonobo2-common - Bonobo CORBA interfaces library -- support files
 libbonobo2-dev - Bonobo CORBA interfaces library -- development files
Closes: 265414
Changes:
 libbonobo (2.6.2-6) unstable; urgency=high
 .
   * debian/rules: don't run dh_installchangelogs for libbonobo2-0 and
     libbonobo2-dev (closes: #265414).
Files:
 7b4769c2d81c4e1f8b6ac623a5888074 1554 devel optional libbonobo_2.6.2-6.dsc
 d630107f9f31d60f49f18c76ebcd79d8 5357 devel optional libbonobo_2.6.2-6.diff.gz
 547e68376d898a58699d83332cf6926b 310202 devel optional libbonobo2-common_2.6.2-6_i386.deb
 9e2d977c4bc1eab3ef917e56880713c7 242444 libdevel optional libbonobo2-dev_2.6.2-6_i386.deb
 79bdddeb3cc0ec86af33a36729ae6919 146678 libs optional libbonobo2-0_2.6.2-6_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBJyR/rSla4ddfhTMRAj8hAKCOr3dwFtUl0pUOmcx4RPBZO3tp+ACg0ayp
dhCYmxjVX+h+ksNRHij5CwU=
=Rv2i
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Sat, 21 Aug 2004 06:47:13 -0400
From: Josselin Mouette <email address hidden>
To: <email address hidden>
Subject: Bug#265414: fixed in libbonobo 2.6.2-6

Source: libbonobo
Source-Version: 2.6.2-6

We believe that the bug you reported is fixed in the latest version of
libbonobo, which is due to be installed in the Debian FTP archive:

libbonobo2-0_2.6.2-6_i386.deb
  to pool/main/libb/libbonobo/libbonobo2-0_2.6.2-6_i386.deb
libbonobo2-common_2.6.2-6_i386.deb
  to pool/main/libb/libbonobo/libbonobo2-common_2.6.2-6_i386.deb
libbonobo2-dev_2.6.2-6_i386.deb
  to pool/main/libb/libbonobo/libbonobo2-dev_2.6.2-6_i386.deb
libbonobo_2.6.2-6.diff.gz
  to pool/main/libb/libbonobo/libbonobo_2.6.2-6.diff.gz
libbonobo_2.6.2-6.dsc
  to pool/main/libb/libbonobo/libbonobo_2.6.2-6.dsc

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <email address hidden> (supplier of updated libbonobo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 21 Aug 2004 12:22:18 +0200
Source: libbonobo
Binary: libbonobo2-dev libbonobo2-common libbonobo2-0
Architecture: source i386
Version: 2.6.2-6
Distribution: unstable
Urgency: high
Maintainer: Takuo KITAME <email address hidden>
Changed-By: Josselin Mouette <email address hidden>
Description:
 libbonobo2-0 - Bonobo CORBA interfaces library
 libbonobo2-common - Bonobo CORBA interfaces library -- support files
 libbonobo2-dev - Bonobo CORBA interfaces library -- development files
Closes: 265414
Changes:
 libbonobo (2.6.2-6) unstable; urgency=high
 .
   * debian/rules: don't run dh_installchangelogs for libbonobo2-0 and
     libbonobo2-dev (closes: #265414).
Files:
 7b4769c2d81c4e1f8b6ac623a5888074 1554 devel optional libbonobo_2.6.2-6.dsc
 d630107f9f31d60f49f18c76ebcd79d8 5357 devel optional libbonobo_2.6.2-6.diff.gz
 547e68376d898a58699d83332cf6926b 310202 devel optional libbonobo2-common_2.6.2-6_i386.deb
 9e2d977c4bc1eab3ef917e56880713c7 242444 libdevel optional libbonobo2-dev_2.6.2-6_i386.deb
 79bdddeb3cc0ec86af33a36729ae6919 146678 libs optional libbonobo2-0_2.6.2-6_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBJyR/rSla4ddfhTMRAj8hAKCOr3dwFtUl0pUOmcx4RPBZO3tp+ACg0ayp
dhCYmxjVX+h+ksNRHij5CwU=
=Rv2i
-----END PGP SIGNATURE-----

Changed in libbonobo:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.