I've had a whack at the packaging. I started by switching over to use dh-golang more canonically, which gets some nice things like running the test suite as part of the build and help making a Built-Using header. But then I found that the upstream tests fail (https://github.com/mongodb/mongo-tools/issues/67) and odd things about the package mean that dh-golang's behaviour is not so useful. But I've whacked my way to something that builds, you can see it at https://code.launchpad.net/~mwhudson/+git/juju-mongo-tools3.2. You can get the orig from my branch with pristine-tar, but I just got r3.2.4.tgz from https://github.com/mongodb/mongo-tools/releases.
Are we going to be applying for an MIR for this package? If I was on the security team I'd have some .... questions, I think. (IMO, as mongo- tools at least claims to support multiple versions of mongo, I think aggressively tracking upstream is probably the best policy). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558336 Title: [needs-packaging] juju-mongo-tools3.2 in xenial, wily, and trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-mongodb/+bug/1558336/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
