This package has reached the xenial release pocket; manually closing the
bug.
** Changed in: juju-mongodb2.6 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: juju-mongodb (Ubuntu) => juju-mongodb2.6 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557830
Title:
[needs-packaging] juju-mongodb2.6 in xenial, wily, and trusty
To
> So please base any packaging against what's the archive rather than
your tree.
Badly worded, sorry. I mean: please base any future packaging changes
against what's in the archive at that point, rather than your tree.
--
You received this bug notification because you are a member of Ubuntu
Uploaded 2.6.10-0ubuntu1. Now awaiting NEW review from an archive admin.
Curtis, please note that I had made some further changes. So please base
any packaging against what's the archive rather than your tree. For
reference my changes are in https://git.launchpad.net/~racb/+git/juju-
Also, following a brief IRC conversation, I decided to make the package
Arch: any. I understand that this is the convention since it makes
porting easier for anyone who wants to focus on a particular
architecture. I understand that Juju upstream have no plans to support
armhf for this package
I pushed a small change to the changelog
* New upstream release (LP #1557830).
at
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
I pushed a small change to the changelog
* New upstream release (LP #1557830).
at
lp:~sinzui/ubuntu/xenial/juju-mongodb2.6/xenial-mongodb-2.6'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
Hi Robie. Juju2 will *not* support 32 bit archs. As this package is only
used to upgrade to 2.0, it will not be used on armhf and i386 archs.
Per point 2 to in comment 4, Ubuntu accepts FTBFS, where as the Juju team
prefers to be clear about what is not supported:
maybe we want
Architecture:
Everything looks good now, but my test build failed on armhf:
https://launchpad.net/~racb/+archive/ubuntu/experimental/+build/9394477
Looks like a segfault (Bus error) stops mongodb from starting.
rbasak: I think we should care about it
rbasak: I don't think I have the expertise to fix a mongo
Everything looks good now, but my test build failed on armhf:
https://launchpad.net/~racb/+archive/ubuntu/experimental/+build/9394477
Looks like a segfault (Bus error) stops mongodb from starting.
rbasak: I think we should care about it
rbasak: I don't think I have the expertise to fix a mongo
> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't
> carried this forward. Is this expected (not described in changelog)? Perhaps
> it
> is because of --disable-scripting but I'm not sure.
Indeed. We have always built juju-mongodb without the javascript engine
because
> Ubuntu mongodb 1:2.6.10-0ubuntu1 introduced --use-system-v8, but you haven't
> carried this forward. Is this expected (not described in changelog)? Perhaps
> it
> is because of --disable-scripting but I'm not sure.
Indeed. We have always built juju-mongodb without the javascript engine
because
Thanks, this looks good.
AFAICS, the quilt patches in Ubuntu mongodb 1:2.6.10-0ubuntu1 apply with
only offset, not fuzz. This is allowed, so refreshing wasn't necessary.
I can see that your refresh (and one line of series being moved) is
effectively a no-op but it would be easier for me if we
No need to give me any changes. Just let me know what you think we
should do on these two points, and I'll upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557830
Title:
[needs-packaging]
Thanks, this looks good.
AFAICS, the quilt patches in Ubuntu mongodb 1:2.6.10-0ubuntu1 apply with
only offset, not fuzz. This is allowed, so refreshing wasn't necessary.
I can see that your refresh (and one line of series being moved) is
effectively a no-op but it would be easier for me if we
No need to give me any changes. Just let me know what you think we
should do on these two points, and I'll upload.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1557830
Title:
Hi Curtis,
This looks good. A few minor things:
1. Please run update-maintainer so as not to make the Debian mongodb
maintainer appear to be responsible for this package.
2. Architecture list in d/control: we prefer to just say "Architecture:
any" and let things FTBFS on architectures we are
Hi Robie, Dimitri
Attached is a diff of my changes per the review.
1. I corrected the maintainer
2. I updated the changelog to state I synced the patches with mongodb 2.6.10.
Note I refreshed the patches so that they apply without fuzzy.
3, I then reverted the archs to match what juju-core
Hi Robie, Dimitri
Attached is a diff of my changes per the review.
1. I corrected the maintainer
2. I updated the changelog to state I synced the patches with mongodb 2.6.10.
Note I refreshed the patches so that they apply without fuzzy.
3, I then reverted the archs to match what juju-core
Hi Curtis,
This looks good. A few minor things:
1. Please run update-maintainer so as not to make the Debian mongodb
maintainer appear to be responsible for this package.
2. Architecture list in d/control: we prefer to just say "Architecture:
any" and let things FTBFS on architectures we are
This diff from the mongodb_2.6 package debian/ to the juju-mongodb2.6
debian dir shows a lot of change. The crux of the diff is that it shows
the d/patches in the ne package are identical to the ubunti package.
** Patch added: "mongodb_2.6-to-juju-mongodb2.6.diff"
a diff of just the changes to d/patches. The patches are from mongodb
1:2.6.10-0ubuntu1
** Patch added: "juju-mongodb2.6-patches-from mongodb2.6.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+attachment/4600661/+files/juju-mongodb2.6-patches-from%20mongodb2.6.diff
This diff from the mongodb_2.6 package debian/ to the juju-mongodb2.6
debian dir shows a lot of change. The crux of the diff is that it shows
the d/patches in the ne package are identical to the ubunti package.
** Patch added: "mongodb_2.6-to-juju-mongodb2.6.diff"
a diff of just the changes to d/patches. The patches are from mongodb
1:2.6.10-0ubuntu1
** Patch added: "juju-mongodb2.6-patches-from mongodb2.6.diff"
https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1557830/+attachment/4600661/+files/juju-mongodb2.6-patches-from%20mongodb2.6.diff
25 matches
Mail list logo