docker / docker/packaging

deb: machine-readable copyright (DEP5) file is incomplete

Open
#326 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
35
Forks
38
Avg merge
1d 18h
Merged PRs (30d)
14

Description

The copyright file (DEP5 https://dep-team.pages.debian.net/deps/dep5/, https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/) currently only lists containerd as upstream, but the containerd.io package also contains runc, which should probably be included as a separate entry.

Currently it uses files: *, which may have to be more granular; https://github.com/docker/containerd-packaging/blob/d6a7e6e2f349710e71a409a6cf2527f48b12e864/debian/copyright#L5-L7

The copyright holder may also have to be updated to match upstream; https://github.com/containerd/containerd/blob/c3efa0cb339ffc2d6c9f03d7fb4e5e6577d0194b/cmd/containerd/main.go#L1-L15

/*
   Copyright The containerd Authors.

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
*/

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with debian/copyright and review the DEP5 format. Compare the package contents for containerd and runc with the upstream copyright information in cmd/containerd/main.go, using the linked packaging references for context. Done means the copyright file has accurate, appropriately scoped entries for the included components.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, go
Domain
build-system
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.