My apologizes. Thank you. I tried to file a new bug for
lirc-modules-source, but launchpad told me there was no such package.
Also I did not want to file a duplicate.
On Wed, 2008-01-09 at 09:19 +0000, laga wrote:
> darthanubis schrieb:
> <logs deleted>
> > Linux amd 2.6.24-3-server #1 SMP Thu Jan 3 23:20:57 UTC 2008 x86_64 GNU/Linux
> >
> > Why is the urgency low? There are google hits of this being broken since
> > EDGY!?!
> >
>
> Calm down, please.
> This bug has already been fixed ("Status: fix released"), you're
> encountering a new one - I gather this from your posting in bug #151957
> where you mentioned that the upgrade from 2.6.24.2-generic to
> 2.6.24-3-server broke it for you, but it's just a guess.
>
> Since bug #151957 is unrelated as well, please open a new bug report
> since your problem is a new one.
>
> Thanks for taking the time to report a bug! I'm sure it'll be fixed
> soon.
>
> Michael
>
> p.s.:
>
> > Still broken in Hardy, a LT release, cmon.
>
> Hardy hasn't been released yet. It's normal to expect broken packages.
>
--
darthanubis <email address hidden>
My apologizes. Thank you. I tried to file a new bug for source, but launchpad told me there was no such package.
lirc-modules-
Also I did not want to file a duplicate.
http:// groups. google. com/group/ linux.debian. bugs.dist/ browse_ thread/ thread/ 3ac8c4820de83e4 c/b28aa97db4555 24c
I also did not know if the above was related?
On Wed, 2008-01-09 at 09:19 +0000, laga wrote:
> darthanubis schrieb:
> <logs deleted>
> > Linux amd 2.6.24-3-server #1 SMP Thu Jan 3 23:20:57 UTC 2008 x86_64 GNU/Linux
> >
> > Why is the urgency low? There are google hits of this being broken since
> > EDGY!?!
> >
>
> Calm down, please.
> This bug has already been fixed ("Status: fix released"), you're
> encountering a new one - I gather this from your posting in bug #151957
> where you mentioned that the upgrade from 2.6.24.2-generic to
> 2.6.24-3-server broke it for you, but it's just a guess.
>
> Since bug #151957 is unrelated as well, please open a new bug report
> since your problem is a new one.
>
> Thanks for taking the time to report a bug! I'm sure it'll be fixed
> soon.
>
> Michael
>
> p.s.:
>
> > Still broken in Hardy, a LT release, cmon.
>
> Hardy hasn't been released yet. It's normal to expect broken packages.
>
--
darthanubis <email address hidden>