[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#348978: marked as done (Lintian shouldn't warn about hardlinks if they are all inside /usr/share/<package> or /usr/lib/<package>)

Your message dated Thu, 16 Mar 2006 04:47:15 +0100
with message-id <20060316034715.GO6811@A-Eskwadraat.nl>
and subject line Bug#348978: Lintian shouldn't warn about hardlinks if they are all inside /usr/share/<package> or /usr/lib/<package>
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: lintian
Version: 1.23.14
Severity: normal

While working on a new version of sql-ledger we decided to use hardlinks
(and not symlinks) between several files inside /usr/lib/sql-ledger/.
The upstream author prefers hardlinks over symlinks because they are
better handled by suexec. And since this is a web-app, it's a legitimate
concern.

I believe that there's no risk that directories below /usr/lib/sql-ledger/
will be mounted on separate partitions, thus this can be done without
problems.

IMHO, the warning shouldn't be emitted if the hardlinked files are (both)
below /usr/lib/<package> or /usr/share/<package>.

For reference, here's the warning that I'm referring to.

W: sql-ledger: package-contains-hardlink usr/lib/sql-ledger/bin/mozilla/admin.pl -> usr/lib/sql-ledger/bin/lynx/admin.pl
N:
N:   The package contains a hardlink in /etc or across different
N:   directories. This might not work at all if directories are on
N:   different filesystems (which can happen anytime as the system
N:   administrator sees fit), certain filesystems such as AFS don't even
N:   support cross-directory hardlinks at all.
N:
N:   For configuration files, certain editors might break hardlinks, and so
N:   does dpkg in certain cases.
N:
N:   A better solution might be using symlinks here.
N:

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-10-386
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages lintian depends on:
ii  binutils             2.16.1cvs20051214-1 The GNU assembler, linker and bina
ii  diffstat             1.41-1              produces graph of changes introduc
ii  dpkg-dev             1.13.11.1           package building tools for Debian
ii  file                 4.15-2              Determines file type using "magic"
ii  gettext              0.14.5-2            GNU Internationalization utilities
ii  intltool-debian      0.34.1+20050828     Help i18n of RFC822 compliant conf
ii  libparse-debianchang 1.0-1               parse Debian changelogs and output
ii  man-db               2.4.3-3             The on-line manual pager
ii  perl [libdigest-md5- 5.8.7-10            Larry Wall's Practical Extraction 

lintian recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Fri, Jan 20, 2006 at 08:24:09AM +0000, Raphael Hertzog wrote:
> While working on a new version of sql-ledger we decided to use hardlinks
> (and not symlinks) between several files inside /usr/lib/sql-ledger/.
> The upstream author prefers hardlinks over symlinks because they are
> better handled by suexec. And since this is a web-app, it's a legitimate
> concern.
> 
> I believe that there's no risk that directories below /usr/lib/sql-ledger/
> will be mounted on separate partitions, thus this can be done without
> problems.

There is a risk: some filesystems do not support hardlinks contained in
different directories, such as AFS, which is stated in the explanation.

I think the warning is ok, there really isn't a very good reason to
really use hardlinks here, right? They *are*, after all, sort of tricky
to deal with: it's hard for a user/sysadmin to see whether something is
a hardlink, and even more difficult to find out what links to what.

Override the warning if you really feel your package should ignore this
warning, but I'd suggest against. In any case, the warning will remain
in lintian as far as I'm concerned

--Jeroen

-- 
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl

--- End Message ---
Reply to: