On Wed, Nov 14, 2018 at 07:07:35PM +1100, Angus Lees wrote:
> Suggestions welcome - I imagine this is not a unique situation. I think
> our options are:
> - no rust-gdb manpage at all
> - a .so stub or symlink to gdb.1 (current situation)
Note that gdb.1 is in non-free and not in the gdb package.
On 11/14/18 9:07 AM, Angus Lees wrote:
> Suggestions welcome - I imagine this is not a unique situation. I think
> our options are:
> - no rust-gdb manpage at all
> - a .so stub or symlink to gdb.1 (current situation)
> - a manually-created stub manpage that just refers the reader to
> gdb-doc/gdb
I think I am responsible for this dangling symlink :)
The issue is that the symlink target is _not_ in the 'rust-doc' package,
but in the 'gdb-doc' package which has nothing to do with the rust src
package, nor the rust maintainers. Moving the rust-gdb symlink into
gdb-doc is not appropriate.
Ba
G. Branden Robinson:
> [..]
> $ man rust-gdb
> /usr/bin/man: warning: /usr/share/man/man1/rust-gdb.1.gz is a dangling symlink
> No manual entry for rust-gdb
> See 'man 7 undocumented' for help when manual pages are not available.
>
>> The man page is available in the rust-doc package which is alre
G. Branden Robinson writes ("Re: Shouldn't shipping broken symlinks be against
policy?"):
> At 2018-11-13T17:02:49+, Ian Jackson wrote:
> > I guess the maintainer will also think this is a bug.
>
> No; he closed it, and cited Policy's lack of a prohibition of shipping
> broken symlinks in sup
At 2018-11-13T17:02:49+, Ian Jackson wrote:
> G. Branden Robinson writes ("Shouldn't shipping broken symlinks be against
> policy?"):
> > Not reopening, but I have some questions for the Policy team.
> ...
> > I could have sworn you were incorrect, but sure enough, I read §10.5
> > carefully a
G. Branden Robinson writes ("Shouldn't shipping broken symlinks be against
policy?"):
> Not reopening, but I have some questions for the Policy team.
...
> I could have sworn you were incorrect, but sure enough, I read §10.5
> carefully and grepped the rest of the policy manual and could find no
>
Not reopening, but I have some questions for the Policy team.
At 2018-11-13T16:26:00+, Ximin Luo wrote:
> Control: notfound -1 1.28.0+dfsg1-2
>
> Closing, as far as I can tell it is not against Policy to ship a
> broken symlink,
I could have sworn you were incorrect, but sure enough, I read
8 matches
Mail list logo
