Override component to main
capnproto 0.5.3-2ubuntu1 in yakkety: universe/misc -> main
capnproto 0.5.3-2ubuntu1 in yakkety amd64: universe/devel/optional/100% -> main
capnproto 0.5.3-2ubuntu1 in yakkety arm64: universe/devel/optional/100% -> main
capnproto 0.5.3-2ubuntu1 in yakkety armhf:
LGTM
** Changed in: capnproto (Ubuntu)
Status: New => Fix Committed
** Changed in: capnproto (Ubuntu)
Assignee: Michael Terry (mterry) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in
** Changed in: capnproto (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1367551
Title:
[MIR] capnproto
I reviewed capnproto version 0.5.3-2ubuntu1 as checked into xenial. This
should not be considered a full security audit but rather a quick gauge of
maintainability.
- There are four CVEs: CVE-2015-2310 CVE-2015-2311 CVE-2015-2312 CVE-2015-2313
These were handled in what is perhaps the finest
** Changed in: capnproto (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1367551
Title:
[MIR] capnproto
Status in capnproto
** Changed in: capnproto (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1367551
Title:
That was fixed quite some time ago, so it should no longer be a problem.
(We are at 0.5.3 now; that's in yakkety, not sure about Vivid and
Xenial.) I never managed to reproduce the problem on arm.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
We're trying to land u8 in main, so I guess I ought to review this.
Michi, what about the integer overflow issue and broken arm tests from
comment #12?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
Lukasz and Pawel have been been working on getting the MIR for this
happening. I'm out of that loop though, so I don't know the details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
Hmmm... Unity8 won't build without unity-scopes-api. I would expect
Unity8 to be in main, at least eventually?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1367551
Yes, eventually. :)
Just not at the moment. When we want to promote it, we can do the whole
dep tree. No need to promote canproto until then.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
OK, that's fine with me.
Kenton pointed out that there was integer overflow issue in 0.4.0.
That's fixed in 0.4.2 and 0.5.2, but neither of these are available from
upstream yet. Apparently, there is an issue with the tests on armel.
I'll use the pbuilder box to see what's going wrong with the
So capnproto is a build-dependency of unity-scopes-api yes... But
unity-scopes-api isn't in main and doesn't have a MIR filed. So do we
actually need to promote this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Hi Michael, thanks for that! Hoping that the info below will be
sufficient.
libcapnp-0.4.0
libcapnp-dev
capnproto
---
Availability: Currently in universe
Rationale: Dependency for unity-scopes-api
Security: No security history.
Quality Assurance: Package works out of the box with
Thanks Tom for the background.
OK Michi, if Debian is NACK on symbols, don't worry about it for Ubuntu
either. But doko's original request to flesh this bug out with info
from https://wiki.ubuntu.com/MainInclusionProcess still stands. Doesn't
have to be back-breakingly comprehensive. See bug
I help maintain the capnproto Debian packages. Debian bug #720063 (the
original ITP) may be relevant to this discussion:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720063
C++ mangled symbols are arch dependent c++filt wasn't playing nice.
Then I stumbled across this part of the Debian
this is not a complete MIR. Please follow
https://wiki.ubuntu.com/MainInclusionProcess
at least a symbols file is missing
** Changed in: capnproto (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I had a look at the requirements, but they don't mention anything about
a symbols file. What do I need to do here?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1367551
Symbols files help maintainers notice when the API changes and helps
other packages know which minimum version of a library they need to
depend on.
See https://wiki.debian.org/UsingSymbolsFiles
Note that a lack of a symbols file isn't a blocker, but they are super
encouraged.
--
You received
Yes, I know what a symbols file is. But the requirements don't mention
one. So, what am I supposed to actually do? Build the library, run nm
over it and then post the symbols file here?
It's simply that I don't understand what I am expected to do.
--
You received this bug notification because
See the How to manage the content of symbols files section of
https://wiki.debian.org/UsingSymbolsFiles on how to generate a starting
symbols file.
But basically yes, build the library then run a tool to generate the
symbols file. Then please pass the patch to Debian because we don't
really want
21 matches
Mail list logo
