debian-packaging
v1
Closes #31.
02aff43e7f
build: docs venv
venv:
I recommend you don't manually set this up and instead add a builddep on https://packages.debian.org/buster/dh-virtualenv
Ooh interesting, I'll take a look.
install:
@# Prepare the virtualenv to be moved (dangerous!)
@# Make sure you don't have '|' in your paths
grep -IRl $(CURDIR)/venv venv | \
Why not define this directly in debian/rules?
debian/rules
Good idea.
To build unsigned packages:
```sh
gbp buildpackage --git-ignore-new --git-upstream-tree=BRANCH --git-upstream-branch=master -uc -us
You can avoid a bunch of these CLI flags by adding a gbp.conf, ala https://salsa.debian.org/clojure-team/clojure/-/blob/main/debian/gbp.conf
Thanks, I'll give it a try.
Section: admin
Priority: optional
Standards-Version: 4.3.0
Vcs-Git: https://git.csclub.uwaterloo.ca/public/pyceo.git
If you care about a policy-compliant control file, lintian would catch that you're missing Vcs-Browser
Vcs-Browser
Good catch.
Package: ceo
Architecture: amd64
Replaces: ceo-python, ceo-clients
Conflicts: ceo-python, ceo-clients
Why does this have Replaces/Conflicts? Do these packages actually exist?
Yes, there are the old ceo client packages. We want to make sure that they're removed before installing the new one.
No due date set.
No dependencies set.
Deleting a branch is permanent. It CANNOT be undone. Continue?
Closes #31.
02aff43e7finto v1 1 year agobuild: docs venvvenv:I recommend you don't manually set this up and instead add a builddep on https://packages.debian.org/buster/dh-virtualenv
Ooh interesting, I'll take a look.
install:@# Prepare the virtualenv to be moved (dangerous!)@# Make sure you don't have '|' in your pathsgrep -IRl $(CURDIR)/venv venv | \Why not define this directly in
debian/rules?Good idea.
To build unsigned packages:```shgbp buildpackage --git-ignore-new --git-upstream-tree=BRANCH --git-upstream-branch=master -uc -usYou can avoid a bunch of these CLI flags by adding a gbp.conf, ala https://salsa.debian.org/clojure-team/clojure/-/blob/main/debian/gbp.conf
Thanks, I'll give it a try.
Section: adminPriority: optionalStandards-Version: 4.3.0Vcs-Git: https://git.csclub.uwaterloo.ca/public/pyceo.gitIf you care about a policy-compliant control file, lintian would catch that you're missing
Vcs-BrowserGood catch.
Package: ceoArchitecture: amd64Replaces: ceo-python, ceo-clientsConflicts: ceo-python, ceo-clientsWhy does this have Replaces/Conflicts? Do these packages actually exist?
Yes, there are the old ceo client packages. We want to make sure that they're removed before installing the new one.
02aff43e7f.