On Tuesday 14 February 2006 00:24, Filippo Giunchedi wrote:
> On Tue, Feb 14, 2006 at 12:02:18AM +0100, Hendrik Sattler wrote:
> > Am Montag, 13. Februar 2006 17:52 schrieb Filippo Giunchedi:
> > [...]
> >
> > The problem is in packaging in debian/bluez-utils.install. Change:
> > debian/tmp/etc/dbus/*
> >
> > to
> > debian/tmp/etc/dbus-1/*
> >
> > to fix this bug.
> >
> > One point down for cdbs as it is not using dh_install's full power (see
> > option
> > --fail-missing).
>
> good point! I would consider it a cdbs bug.
Use cdbs' rules/utils.mk It has a list-missing target.
Achim
> To prevent this issue to appear again I was wondering about a tool that lists
> debian/tmp/ and shows every file that isn't in at most one
> debian/$binary_package directory, this should prevent trivial error like this.
>
> >
> > Another downside of the dbus change: "bluez-pin --dbus" never shows up a
> > window. Something else that somewhere goes wrong but dbus is hard stuff to
> > look into while running :-/
>
> bluez-pin maintainer might be interested in this, CC'ing
>
> >
> > HS
> >
> > PS: The original bug report may not be valid anymore although it may be be
> > related to my report (although the effects are the same). The original bug
> > report may not be valid anymore, though, non-reproducable anyway (things
> > that
> > stay for 5+ years and finally get deleted).
>
> I'm quite confident it isn't because back in dec '04 dbus isn't likely to be a
> problem. Anyway it worked for you before the upgrade. I'll consider reopening
> and retitling the bug once it gets closed by 2.25-1 upload.
>
> (hint: next time please consider twice before retitling a bug that
> dramatically)
>
> filippo
> --
> Filippo Giunchedi
> PGP key: 0x6B79D401
> random quote follows:
>
> Either this man is dead or my watch has stopped.
> -- Groucho Marx
>
--
To me vi is Zen. To use vi is to practice zen. Every command is
a koan. Profound to the user, unintelligible to the uninitiated.
You discover truth everytime you use it.
-- [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
