** Changed in: beagle
Importance: Unknown = Critical
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
The fixed version arrived in the mirror I use just a few hours after I
changed the bug status. Setting as fix-released.
** Changed in: beagle (Ubuntu)
Status: Fix Committed = Fix Released
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification
The fix is only upstream, but not in Ubuntu yet.
** Changed in: beagle (Ubuntu)
Status: Fix Committed = Confirmed
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
That's why it's marked as fix committed.
** Changed in: beagle (Ubuntu)
Status: Confirmed = Fix Committed
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I know, my questions is, will the new upstream version make it into Gutsy
final or will it be broken still when Gutsy ships?
On 9/20/07, Pedro Villavicencio [EMAIL PROTECTED] wrote:
That's why it's marked as fix committed.
** Changed in: beagle (Ubuntu)
Status: Confirmed = Fix
I checked and found 0.2.18 (the upstream package) was uploaded for
Gutsy.
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I noticed this new version hasn't made it into debian or ubuntu yet,
will it be there before release? If so, do we know when it will be
released into main?
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop
Great! Thanks much!
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
I see a status of fix-released, I don't show that this has made it into
a build yet, do we know why?
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing
the fix-released status is for the upstream report. there's a tarball[1]
it now need to be packaged. that's it.
1- http://ftp.gnome.org/pub/GNOME/sources/beagle/0.2/
** Changed in: beagle (Ubuntu)
Status: Triaged = Fix Committed
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
** Changed in: beagle
Status: New = Fix Released
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: beagle (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: New = Triaged
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
There seems to be a fix/work-around for this bug:
http://bugzilla.gnome.org/show_bug.cgi?id=452494
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
13 matches
Mail list logo
