On Sun, Jun 30, 2013 at 11:46:10AM +0200, Ivo De Decker wrote: > On Sun, Jun 30, 2013 at 09:26:38AM +0200, Guido Günther wrote: > > Hi Guido, > > > On Sat, Jun 29, 2013 at 11:55:51PM +0200, Ivo De Decker wrote: > > man "git-import-orig" still works as exected since the manpage has: > > > > .SH NAME > > git-import-orig, gbp-import-orig \- Import an upstream source into a git > > repository > > .SH SYNOPSIS > > > > so there's no need to ship the manpage. Please explain why we should > > ship the old pages? > > I wasn't suggesting to ship the old manpages. I was suggesting that 'man > git-import-orig' should show the new manpage for gbp-import-orig, so we agree > on that. The problem is that it doesn't seem to work (on an up-to-date > unstable system): > > ivo@unstable:~$ man git-import-orig > No manual entry for git-import-orig > See 'man 7 undocumented' for help when manual pages are not available. > ivo@unstable:~$ man gbp-import-orig > GBP-IMPORT-ORIG(1) git-buildpackage Manual > GBP-IMPORT-ORIG(1) > > > > NAME > git-import-orig, gbp-import-orig - Import an upstream source into a > git repository > > [...] > > > Does 'man git-import-orig' work on your system?
Sure it does. Otherwise I'd agree that there is a bug: $ apropos git-import-orig gbp-import-orig (1) - Import an upstream source into a git repository I'm using man-db: $ dpkg-query -s man-db | grep ^Version: Version: 2.6.5-2 We could "fix" this by adding the symlinks but I'd rather understand the root cause of the problem. Cheers, -- Guido -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
