Please remove tuskar from utopic

Bug #1381601 reported by James Page
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tuskar (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

As the Debian maintainer is going to request its removal from Jessie, I suggest we remove tuskar from Utopic - its a bit experimental still.

<jamespage> zigo, I'll tweak tuskar for ubuntu versions; we'll talk about epoch alignment next cycle
<infinity> mlankhorst: How does "setting a more sane CPU" make it not a bug anymore?
 mlankhorst: Not all i386 machines are as new as the one you're now emulating.
<-- BinLi has quit (Quit: WeeChat 1.0.1)
<zigo> jamespage: So you need to fix tuskar's depends when importing it because of that epoc?
 jamespage: FYI, I'm planning on removing Tuskar from Jessie when it gets frozen.
<Laney> The current problem is that booting an i386 vm (with "qemu-system-i386 -enable-kvm -monitor stdio -m 1024 -cdrom utopic-desktop-i386.iso", for example) fails to bring up unity7 and logs have the same 'cannot split operator' message.
<jamespage> zigo, oh - not good then?
<zigo> jamespage: As well as all TripleO stuff, Designate and probably more.
<jamespage> I might just request it removed
<zigo> jamespage: I don't think it's production ready, and I'm sure I wont get upstream support for long enough.
 jamespage: Yeah, just ask it to get removed.
 jamespage: Oh, and Ironic too ...
 jamespage: But that's stuff from Icehouse.

Revision history for this message
Matthias Klose (doko) wrote :

Removing packages from utopic-proposed:
 tuskar 0.4.2-2 in utopic
Comment: lp: #1381601, remove tuskar, not ready for release
1 package successfully removed.

Changed in tuskar (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.