On Thu, May 19, 2005 at 09:26:43AM -0600, Sebastian Kuzminsky wrote:
> Cogito is a front-end matched with a back-end called GIT. The upstream
> package includes both Cogito and GIT. The GIT back-end wants to install a
> manpage called git(1), and the bug is that this conflicts with the manpage
>
Hi folks, I'm just got a bug report for my cogito package and I'd like
your input on the best way to fix it.
Cogito is a front-end matched with a back-end called GIT. The upstream
package includes both Cogito and GIT. The GIT back-end wants to install a
manpage called git(1), and the bug is tha
W liście z czw, 16-05-2002, godz. 22:09, Robert Bihlmeyer pisze:
> Alexandre <[EMAIL PROTECTED]> writes:
>
> > * having pyro and host conflict (but this annoys me since I need both
> > packages on my machine)
This is against Debian Policy. Look at http://bugs.debian.org/xnc for
example of such
Alexandre <[EMAIL PROTECTED]> writes:
> * having pyro and host conflict (but this annoys me since I need both
> packages on my machine)
Note that bind9-host also provides the "host" binary, but without the
"mx", "ns", "soa", etc. convenience symlinks (at least I guess they
are symlinks).
> *
Alexandre <[EMAIL PROTECTED]> writes:
> Hello,
Hi,
> What would be considered the best way to handle this ?
You can call it pyro.ns . I've already experienced such a case in one
of my packages.
Cheers,
--
Jérôme Marant
http://marant.org
--
To UNSUBSCRIBE, email to [
Hello,
I'm working on packaging pyro (http://pyro.sf.net), which is a
distributed obvject framework for Python. The directory service
daemon for pyro is called 'ns' (NamingService) which is quite
unfortunate because /usr/bin/ns is a file in the very useful host
package.
I've talked about this
6 matches
Mail list logo
