Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong file owners in deb package #23

Closed
robertauer opened this issue Sep 11, 2019 · 0 comments · Fixed by #24
Closed

Wrong file owners in deb package #23

robertauer opened this issue Sep 11, 2019 · 0 comments · Fixed by #24

Comments

@robertauer
Copy link
Member

robertauer commented Sep 11, 2019

TAR_ARGS:=--owner=cloudogu:1000 --group=cloudogu:1000 --mtime="$(LAST_COMMIT_DATE)" --sort=name

As the cloudogu user does not automatically exist in the CES and the user 1000 may change, these owner and group settings make no sense. Lintian shows errors like this:

E: ces-commons: wrong-file-owner-uid-or-gid etc/ 1000/1000
N: 
N:    The user or group ID of the owner of the file is invalid. The owner user
N:    and group IDs must be in the set of globally allocated IDs, because
N:    other IDs are dynamically allocated and might be used for varying
N:    purposes on different systems, or are reserved. The set of the allowed,
N:    globally allocated IDs consists of the ranges 0-99, 64000-64999 and
N:    65534.
N:    
N:    It's possible for a Policy-compliant package to trigger this tag if the
N:    user is created in the preinst maintainer script, but this is a very
N:    rare case and doesn't appear to be necessary. If you found yourself
N:    needing to create a package that works this way, please file a bug
N:    against Lintian to let the maintainers know.
N:    
N:    Refer to Debian Policy Manual section 9.2 (Users and groups) for
N:    details.
N:    
N:    Severity: serious, Certainty: certain
N:    
N:    Check: files, Type: binary, udeb
robertauer added a commit that referenced this issue Sep 11, 2019
Change owner and group to 0 when using tar

Resolves #23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant