Re: Bug#461440: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0-0

2008-01-18 Thread Sven Joachim
reopen 461440 thanks On 2008-01-18 22:21 +0100, Loïc Minier wrote: > On Fri, Jan 18, 2008, Russ Allbery wrote: >> The reason for the Policy requirement is the copyright file, so I don't >> think this can be relaxed without running the risk of getting the legal >> material for the package wrong.

Re: Bug#461440: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0-0

2008-01-18 Thread Loïc Minier
On Fri, Jan 18, 2008, Russ Allbery wrote: > The reason for the Policy requirement is the copyright file, so I don't > think this can be relaxed without running the risk of getting the legal > material for the package wrong. Suppose, for instance, that someone had > an old version of one package in

Re: Bug#461440: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0-0

2008-01-18 Thread Russ Allbery
Loïc Minier <[EMAIL PROTECTED]> writes: > I'd rather have this relaxed in policy; would it be possible to drop > the strict versionning requirements for symlinks? The reason for the Policy requirement is the copyright file, so I don't think this can be relaxed without running the risk of gettin

Processed: Re: Bug#461440: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0-0

2008-01-18 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > clone 461440 -1 Bug#461440: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0-0 Bug 461440 cloned as bug 461443. > reassign -1 debian-policy 3.7.3.0 Bug#461443: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0

Re: Bug#461440: libgtk2.0-0: Must not use a symlink for /usr/share/doc/libgtk2.0-0

2008-01-18 Thread Loïc Minier
clone 461440 -1 reassign -1 debian-policy 3.7.3.0 stop On Fri, Jan 18, 2008, Sven Joachim wrote: > In this version, libgtk2.0-0 no longer has a versioned dependency on > libgtk2.0-common. That means that you must not symlink > /usr/share/doc/libgtk2.0-0 to libgtk2.0-common, see policy section 12.