[Bug 1819761] Re: [MIR] containerd

2020-03-04 Thread Steve Langasek
Override component to main containerd 1.3.3-0ubuntu1 in focal: universe/misc -> main containerd 1.3.3-0ubuntu1 in focal amd64: universe/admin/optional/100% -> main containerd 1.3.3-0ubuntu1 in focal arm64: universe/admin/optional/100% -> main containerd 1.3.3-0ubuntu1 in focal armhf: universe/admin

[Bug 1819761] Re: [MIR] containerd

2020-03-02 Thread Christian Ehrhardt 
Seed change approved and done, since this only is going to the supported seed but not getting a direct package/task dependency please help to let us later double check it actually shows up in component mismatches. ** Changed in: containerd (Ubuntu) Status: In Progress => Fix Committed --

[Bug 1819761] Re: [MIR] containerd

2020-03-02 Thread Christian Ehrhardt 
Seeed change MP opened: https://code.launchpad.net/~paelzer/ubuntu- seeds/+git/platform/+merge/380071 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819761 Title: [MIR] containerd To manage notific

[Bug 1819761] Re: [MIR] containerd

2020-03-02 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/380071 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819761 Title: [MIR] containerd To manage not

[Bug 1819761] Re: [MIR] containerd

2020-03-01 Thread Christian Ehrhardt 
Now ready for promotion together with runc in bug 1817336. We need to make a seed change to pull them in. ** Changed in: containerd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 1819761] Re: [MIR] containerd

2020-02-28 Thread Eduardo dos Santos Barretto
I reviewed containerd 1.3.1-0ubuntu1 as checked into focal. This shouldn't be considered a full audit but rather a quick gauge of maintainability. containerd is a daemon that manages the complete container lifecycle of its host system. Containerd controls runc. - No CVE History: - Build-Depends

[Bug 1819761] Re: [MIR] containerd

2020-01-14 Thread Christian Ehrhardt 
With above analysis done, in conjunction with the decisions in Paris and per the discussion in the MIR team meeting at [1] this is an ack. Please go forward with vendored dependencies, that applies to: 1. the security team which has this on its queue for review 2. the server team for an eventual u

[Bug 1819761] Re: [MIR] containerd

2020-01-14 Thread Lucas Kanashiro
# containerd - vendorized dependencies Here is an overall analysis of the vendorized deps in containerd version 1.3.1-0ubuntu1. ## Summary: - Total of 85 vendorized deps + None of them has a correspondent package in main - 18 vendorized deps without correspondent package in the archive - 28

[Bug 1819761] Re: [MIR] containerd

2019-09-22 Thread Christian Ehrhardt 
This is in the security Teams review queue (which is the proper next step). Thanks Seth for all your work on this already. I wanted to summarize after the discussion about Go-vendoring at the recent sprint: - we expect (as in Docker) to handle runc/containerd special for SRUs providing an upstrea

[Bug 1819761] Re: [MIR] containerd

2019-07-18 Thread Seth Arnold
There's a handful of text files that are marked executable: -rwxr-xr-x root/root 91142 2019-04-05 18:39 ./usr/share/gocode/src/github.com/containerd/containerd/api/1.0.pb.txt -rwxr-xr-x root/root 91089 2019-04-05 18:39 ./usr/share/gocode/src/github.com/containerd/containerd/api/1.1.pb.tx

[Bug 1819761] Re: [MIR] containerd

2019-07-18 Thread Seth Arnold
Andreas, yes; we'd like to you build using golang -dev packages and not build the vendored code. There's no need to repack the orig tarball and no need to switch to dynamic linking. (The golang -dev packages allow us to track when packages need rebuilding through the Built-Using mechanism.) Thank

[Bug 1819761] Re: [MIR] containerd

2019-07-18 Thread Andreas Hasenack
Thanks for the review, Seth. Just to be clear, you are asking for the golang vendored bits to be split into their own packages (if not already available in the archive), and switch to shared linking for them? -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1819761] Re: [MIR] containerd

2019-07-17 Thread Seth Arnold
There's roughly half-million lines of code in vendor/ -- we have asked for Go packages to have their vendored code split out into their own packages to simplify triage, fixing, and minimize rebuilding: https://wiki.ubuntu.com/MIRTeam#Embedded_sources_and_static_linking $ tokei vendor

[Bug 1819761] Re: [MIR] containerd

2019-07-17 Thread Seth Arnold
The lintian errors appear to have been drastically reduced in the interim: E: containerd source: missing-build-dependency-for-dh-addon systemd => debhelper (>= 9.20160709~) | debhelper-compat | dh-sequence-systemd || dh-systemd W: containerd source: vcs-obsolete-in-debian-infrastructure vcs-git

[Bug 1819761] Re: [MIR] containerd

2019-03-28 Thread Mathieu Trudel-Lapierre
I see no obvious issues with the package, but it's huge and would benefit the Security Team reviewing it as well. ** Changed in: containerd (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1819761] Re: [MIR] containerd

2019-03-18 Thread Joshua Powers
ubuntu-server is now subscribed to bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819761 Title: [MIR] containerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu