Bug#929666: ITP: conmon -- An OCI container runtime monitor
X-Debbugs-CC: bir...@rantanplan.org, ja...@ivyleav.es Control: forcemerge -1 930898 Hi Birger ! Thanks for your interest in getting conmon packaged. :) Jamie (in CC) and myself are also interested in seeing it land in Debian, as it's a dependency of podman (that we are packaging), and started working on this under podman-team on Salsa. I uploaded (our version of) conmon/0.3.0-1 2 days ago, and it's currently in the NEW review queue. Sorry for missing your ITP (and some related ones): it seems like wnpp.d.n is currently broken, it doesn't list results when searching for conmon or other packages with recent ITPs... As a result, I opened my own (#930898) but this mail should merge it back with yours. In any case, I would love to join efforts with you, and I will send you an invite to podman-team. I would add you as a co-uploader on the package, help you with reviews and sponsored uploads, and (if you want) work with you towards becoming a DM (or a DD) so you can maintain the package independently. Best, nicoo On Tue, May 28, 2019 at 10:10:00AM +0200, Birger Schacht wrote: > Package: wnpp > Severity: wishlist > Owner: Birger Schacht > > * Package name: conmon > Version : 0.2.0 > Upstream Author : Peter Hunt > * URL : https://github.com/containers/conmon > * License : Apache-2.0 > Programming Lang: C > Description : An OCI container runtime monitor. > > Conmon is a monitoring program and communication tool between a > container manager (like podman or CRI-O) and an OCI runtime (like runc > or crun) for a single container. > It is a run dependency for podman. signature.asc Description: PGP signature
Bug#929666: ITP: conmon -- An OCI container runtime monitor
Hi Reinhard, On 6/1/19 5:17 PM, Reinhard Tartler wrote: > I think think that separation is not helping me at all, and I'd really > prefer the standard layout that gbp-buildpackage suggests: > http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.intro.html#gbp.repository > Note that the 'upstream' branch regularily gets merged into the packaging > branch. This seems to be different with your packaging style. merging the > upstream sources enables using tools such as license-reconcile, dgit, and > similar. > Thanks for your understanding. I've now merged the upstream tag into master. There was also a new release a couple of days ago fixing the copyright issue, and I've updated the package accordingly. cheers, Birger
Bug#929666: ITP: conmon -- An OCI container runtime monitor
I think think that separation is not helping me at all, and I'd really prefer the standard layout that gbp-buildpackage suggests: http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.intro.html#gbp.repository Note that the 'upstream' branch regularily gets merged into the packaging branch. This seems to be different with your packaging style. merging the upstream sources enables using tools such as license-reconcile, dgit, and similar. Thanks for your understanding. On Thu, May 30, 2019, 06:14 Birger Schacht wrote:. > > Other than that there is only > https://github.com/containers/conmon/issues/30 that keeps the package > from being uploaded. > > Yeah, that's an issue. Let's hope upstream reacts on that soon. Best, -rt
Bug#929666: ITP: conmon -- An OCI container runtime monitor
Hi Reinhard, On 5/29/19 3:07 PM, Reinhard Tartler wrote: > On Tue, May 28, 2019 at 2:18 PM Birger Schacht > wrote: >> I maintain the source package on >> https://salsa.debian.org/bisco-guest/conmon - but conmon is not a golang >> project, it is C. But if there is another team that package fits, I'd be >> happy to team maintain ;) >> > > Thanks for the clarification. > > I notice that you chose a packaging style that does not include > the upstream sources, which is not my personal preference. Actually the current upstream source is in the upstream/0.2.0 tag- gbp buildpackage looks there for the upstream sources. Is it not possible to use dgit with having upstream sources in a separate branch? > Any chance to convince you to use a style that makes it possible > to use dgit(1)? If so, I'd be happy to help you with moving this > package to the "debian" namespace (formerly known as collab-maint) > which provides access to a audience and thus makes collaboration > easier, and to sponsor uploads as necessary. Well, I like having the upstream sources and the debian/ directory separated from another, but if it makes it easier for you I can merge the upstream/0.2.0 tag into master. Other than that there is only https://github.com/containers/conmon/issues/30 that keeps the package from being uploaded. cheers, Birger
Bug#929666: ITP: conmon -- An OCI container runtime monitor
On Tue, May 28, 2019 at 2:18 PM Birger Schacht wrote: > On 5/28/19 6:49 PM, Reinhard Tartler wrote: > > Thanks for working on this package. > > > > Do you plan to have this package team maintained in the golang team? If > so, > > please let us know where on salsa you maintain the source package. I may > be > > able to help out. > > I maintain the source package on > https://salsa.debian.org/bisco-guest/conmon - but conmon is not a golang > project, it is C. But if there is another team that package fits, I'd be > happy to team maintain ;) > Thanks for the clarification. I notice that you chose a packaging style that does not include the upstream sources, which is not my personal preference. Any chance to convince you to use a style that makes it possible to use dgit(1)? If so, I'd be happy to help you with moving this package to the "debian" namespace (formerly known as collab-maint) which provides access to a audience and thus makes collaboration easier, and to sponsor uploads as necessary. Best, -rt -- regards, Reinhard
Bug#929666: ITP: conmon -- An OCI container runtime monitor
Hi Reinhard, On 5/28/19 6:49 PM, Reinhard Tartler wrote: > Thanks for working on this package. > > Do you plan to have this package team maintained in the golang team? If so, > please let us know where on salsa you maintain the source package. I may be > able to help out. I maintain the source package on https://salsa.debian.org/bisco-guest/conmon - but conmon is not a golang project, it is C. But if there is another team that package fits, I'd be happy to team maintain ;) cheers, Birger
Bug#929666: ITP: conmon -- An OCI container runtime monitor
Thanks for working on this package. Do you plan to have this package team maintained in the golang team? If so, please let us know where on salsa you maintain the source package. I may be able to help out. Best regards, -rt On Tue, May 28, 2019, 04:12 Birger Schacht wrote: > Package: wnpp > Severity: wishlist > Owner: Birger Schacht > > * Package name: conmon > Version : 0.2.0 > Upstream Author : Peter Hunt > * URL : https://github.com/containers/conmon > * License : Apache-2.0 > Programming Lang: C > Description : An OCI container runtime monitor. > > Conmon is a monitoring program and communication tool between a > container manager (like podman or CRI-O) and an OCI runtime (like runc > or crun) for a single container. > It is a run dependency for podman. > >
