[Bug 250285] Re: pykdeuic4 missing in python-kde4-dev

2008-09-13 Thread Launchpad Bug Tracker
This bug was fixed in the package kde4bindings - 4:4.1.1-0ubuntu3 --- kde4bindings (4:4.1.1-0ubuntu3) intrepid; urgency=low * Add conflicts/replaces libqt0-ruby1.8 to libqt4-ruby1.8 (LP: #262869) * Fix typo in qyoto-examples long description * Add libmono-dev to buid-dep to fix

[Bug 250285] Re: pykdeuic4 missing in python-kde4-dev

2008-09-05 Thread Scott Kitterman
** Changed in: kde4bindings (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Scott Kitterman (kitterman) Status: Confirmed = In Progress -- pykdeuic4 missing in python-kde4-dev https://bugs.launchpad.net/bugs/250285 You received this bug notification because you

Re: [Bug 250285] Re: pykdeuic4 missing in python-kde4-dev

2008-07-23 Thread Adeodato Simó
Is this with Hardy? I fixed this bug in the PPA packages some time yesterday, so you should update if you're using Hardy. No, this is in the intrepid packages (version 4:4.0.98-0ubuntu1). -- pykdeuic4 missing in python-kde4-dev https://bugs.launchpad.net/bugs/250285 You received this bug

[Bug 250285] Re: pykdeuic4 missing in python-kde4-dev

2008-07-23 Thread Jonathan Thomas
** Changed in: kde4bindings (Ubuntu) Status: Fix Released = Confirmed -- pykdeuic4 missing in python-kde4-dev https://bugs.launchpad.net/bugs/250285 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 250285] Re: pykdeuic4 missing in python-kde4-dev

2008-07-23 Thread Jonathan Thomas
Is this with Hardy? I fixed this bug in the PPA packages some time yesterday, so you should update if you're using Hardy. ** Changed in: kde4bindings (Ubuntu) Status: New = Fix Released -- pykdeuic4 missing in python-kde4-dev https://bugs.launchpad.net/bugs/250285 You received this bug

[Bug 250285] Re: pykdeuic4 missing in python-kde4-dev

2008-07-20 Thread Nathan Handler
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at [WWW]