** Changed in: maas (Ubuntu)
Importance: Undecided => Critical
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Raphaël Badin (rvb)
--
You received this bug notification because you are a member of Ubuntu
Serve
On Tuesday 22 Jul 2014 07:09:59 you wrote:
> jsenum is *not* in provisioningserver, as I said above it's in
> src/maasserver/utils/, where it should be. The problem is that it's
> *using things* (well, one thing: map_enum) from provisioningserver
Yeah my bad. Serves me right for replying when I
> jsenum has no place in provisioning server, can't you extract that
part?
jsenum is *not* in provisioningserver, as I said above it's in
src/maasserver/utils/, where it should be. The problem is that it's
*using things* (well, one thing: map_enum) from provisioningserver
** Branch linked: lp:~r
jsenum has no place in provisioning server, can't you extract that part?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1346279
Title:
Building the MAAS package fails with "ImportError
The logical place for map_enum really is
src/provisioningserver/utils/__init__.py since it's used by both
maasserver and pserv so I really don't want to put it somewhere else.
Since jsenum is special in the sense that it's used by the packaging,
I'd favor option 3: add a copy of map_enum (it's just
