** Changed in: mongodb (Ubuntu)
Assignee: Robie Basak (racb) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756432
Title:
[FFe] Split out mongodb-server-core
To manage notifica
This bug was fixed in the package mongodb - 1:3.4.7-1ubuntu4
---
mongodb (1:3.4.7-1ubuntu4) bionic; urgency=medium
* d/p/disable-broken-ppc64el-altivec: disable buggy AltiVec optimisations on
ppc64el for now to fix FTBFS until upstream has a proper fix (LP:
#1758116). This m
** Changed in: mongodb (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756432
Title:
[FFe] Split out mongodb-server-core
To manage notifications about thi
Likely we should remove juju-mongodb3.2 from bionic once we actually have an
alternative and can trust that it actually works. It is my understanding that
3.2 FTBFS and nobody was willing to maintain it.
Given the option, yes we would prefer a 3.4 without the JS engine. My
understanding is that
On Wed, Mar 21, 2018 at 12:21:12AM -, Dimitri John Ledkov wrote:
> Before Feature Freeze, I was trying to get mongodb 3.6 building, but ran
> out of disk-space on official builders to successfully build it. Thus
> one more question - why move to 3.4, when 3.6 is the current stable
> series? May
the packaging splits are indeed good for the distro, in general.
but I also want to make sure Ubuntu is providing the best solutions for
Juju upstream, too. As one of the users of our platform.
Before Feature Freeze, I was trying to get mongodb 3.6 building, but ran
out of disk-space on official
Do we need to continue shipping juju-mongo-tools3.2 in bionic?
Do we need to continue shipping juju-mongodb3.2 in bionic?
Are you aware that juju-mongodb3.2, has JS engine turned off, and is
thus more secure than the monogdb source, which has JS engine compiled
in - and thus has all the security
> Do we need to continue shipping juju-mongo-tools3.2 in bionic?
> Do we need to continue shipping juju-mongodb3.2 in bionic?
These can presumably be removed, but let's wait for an upstream ack
after this change to src:mongodb has landed.
About the rest, what Juju upstream chooses to do has noth
I'm afraid of mongodb JS engine security vulnerabilities, impacting juju
security, even during the interim period whilst it is still in use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756432
Title
** Changed in: mongodb (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756432
Title:
[FFe] Split out mongodb-server-core
To manage notifications about this bug
** Bug watch added: Debian Bug tracker #893621
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893621
** Also affects: mongodb (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893621
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: mongodb (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756432
Title:
[FFe] Split out mongodb-server-core
To manage notifications
** Merge proposal linked:
https://code.launchpad.net/~racb/ubuntu/+source/mongodb/+git/mongodb/+merge/341727
** Changed in: mongodb (Ubuntu)
Status: New => In Progress
** Changed in: mongodb (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notificat
Thanks. You are correct. This is just playing with packaging; the source
is unchanged. I was thinking the same about not needing an FFe, but I
filed one anyway. If nothing else, it can provide clarity for anyone who
may have wondered why the split occurred.
--
You received this bug notification b
I don't mind the approach as it just sounds like splitting existing
binary packages in universe.
If I understand this correct, it's not actually causing the addition or
removal of a feature in Ubuntu, it's effectively purely cosmetic so I'm
not sure an FFe was even needed for this in the first pla
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756432
Title:
[FFe] Split out mongodb-server-core
To manage notifications about this bug go to:
https://bugs.l
16 matches
Mail list logo
