Ubuntu

[MIR] juju-core, golang

Reported by James Page on 2013-10-23
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
golang (Ubuntu)
High
Unassigned
Trusty
High
Unassigned
juju-core (Ubuntu)
High
Unassigned
Trusty
High
Unassigned

Bug Description

MIR for juju-core and toolchain for Trusty

James Page (james-page) on 2013-10-23
Changed in golang (Ubuntu Trusty):
importance: Undecided → High
Changed in juju-core (Ubuntu Trusty):
importance: Undecided → High
Dave Cheney (dave-cheney) wrote :

Go 1.2 will be released 1 December. When that happens the 1.1 series will be EOL. Is it possible to have 1.2 included in Trusty ?

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in golang (Ubuntu):
status: New → Confirmed
Changed in juju-core (Ubuntu):
status: New → Confirmed
James Page (james-page) on 2014-01-09
Changed in juju-core (Ubuntu Trusty):
status: Confirmed → Won't Fix
Changed in golang (Ubuntu Trusty):
status: Confirmed → Won't Fix

Hi James,

What do these status messages mean ?

Cheers

Dave

On Fri, Jan 10, 2014 at 12:40 AM, James Page <email address hidden> wrote:

> ** Changed in: juju-core (Ubuntu Trusty)
> Status: Confirmed => Won't Fix
>
> ** Changed in: golang (Ubuntu Trusty)
> Status: Confirmed => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1243762
>
> Title:
> [MIR] juju-core, golang
>
> Status in “golang” package in Ubuntu:
> Confirmed
> Status in “juju-core” package in Ubuntu:
> Confirmed
> Status in “golang” source package in Trusty:
> Won't Fix
> Status in “juju-core” source package in Trusty:
> Won't Fix
>
> Bug description:
> MIR for juju-core and toolchain for Trusty
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1243762/+subscriptions
>

Curtis Hovey (sinzui) wrote :

Hi James

I think the status of juju-core is incorrect, or maybe we are tracking the effort to put juju-core in main with bug 1267393.

I understand that plan is to switch to gccgo for all the arch we build. (I have taken steps to build the window's juju client on windows to avoid cross-compilation risks,) We Still want juju-core is main. If bug 1267393 is tracking juju-core in main, then maybe we should make this entire bug wont-fix.

James Page (james-page) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 13/01/14 23:26, Curtis Hovey wrote:
> I think the status of juju-core is incorrect, or maybe we are
> tracking the effort to put juju-core in main with bug 1267393.
>
> I understand that plan is to switch to gccgo for all the arch we
> build. (I have taken steps to build the window's juju client on
> windows to avoid cross-compilation risks,) We Still want juju-core
> is main. If bug 1267393 is tracking juju-core in main, then maybe
> we should make this entire bug wont-fix.

Sorry - I raised another MIR bug by mistake - marked this one a duplicate.

- --
James Page
Ubuntu and Debian Developer
<email address hidden>
<email address hidden>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS1SZRAAoJEL/srsug59jD/fIP/AuNGtKlWeOEo7z08sQNStIX
PNdKCanqTO6xhqptJ7xazoxdQY5Zr/9w2o1E+5IvnqrXF0x6vaGRXvyAtorAUWfH
T8n/4TRXpQhcMEHcWTIO8yZ3CMHUeetnicGVBCojOyPCyp/lyoESbgzryr21CJzI
kZFGHev7Ixq699sJaNgvNPsy1kQXmD+mSepN0q6thxP73nhHnOOxyK2TkQU84i3t
+xIdqJ06osViKR7qx1CkOZASuCVdiRQc1jV4Ym4KylhOILDQcEXGat/2EMoN625Q
BQbjzH6t4PTJJNLySK1l7kgxfPoxQCkBSWjN2S4CnJf8UCjS59vyzAKa9fuk5WsK
ei9KrGDVnSmmKyWmGBGo52TcvqC1O4hFyjjKv/qnG8yxVnDxOlAwHnmOQH7Z1tMK
H8EcTnptIfCoOWFwBJzEFKyJMmn1pVSPqL1nLEcOBtfP6krsSG2ymYsr5kiGUHak
z6vrFlR4du2VIuFXRo2ZlSOA2Z/lVZGLBxUfdgU/yGwdLneMyb/htec7BGEtp+B6
ezJIUlyoN9LsLiJZEbsNzvnFJoOAvBAAzCpK8x8SvzGB6DJMRtvtkFNEEOHLjbde
eE9ePWaQePI7hhWocQHIyw11MH0kfvjLAtkl2f1Ny0NT+ZxCty/eRTDEu4I8Wjxi
uYgQkMjIqfsBOwR4PSWg
=tHW7
-----END PGP SIGNATURE-----

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers