]> git.proxmox.com Git - debcargo-conf.git/blob - release.sh
remove stuff that we have uploaded
[debcargo-conf.git] / release.sh
1 #!/bin/sh
2
3 . ./vars.sh.frag
4
5 if test ! -d $PKGDIR_REL; then
6 abort 1 "Cannot find $PKGDIR_REL. Did you run ./new-package.sh before?"
7 fi
8
9 if test ! -f "$PKGDIR_REL/debian/changelog"; then
10 abort 1 "Cannot find $PKGDIR_REL/debian/changelog. Did you run ./new-package.sh before?"
11 fi
12
13 if git grep --quiet FIXME -- "$PKGDIR_REL" :^"$PKGDIR_REL/debian/*.debcargo.hint" :^"$PKGDIR_REL/debian/changelog"; then
14 abort 1 "FIXMEs remain in $PKGDIR_REL, fix and commit those first."
15 fi
16
17 git diff --quiet --cached || \
18 abort 1 "You have other pending changes to git, please complete it or stash it away and re-run this script."
19
20 git diff --quiet -- "$PKGDIR_REL" || \
21 abort 1 "Please git-add your changes to $PKGDIR_REL before running"
22
23 type dch >/dev/null || \
24 abort 1 "Install devscripts, we need to run dch."
25
26 RELBRANCH="pending-$PKGNAME"
27 git fetch origin --prune
28
29 if head -n1 "$PKGDIR/debian/changelog" | grep -qv UNRELEASED-FIXME-AUTOGENERATED-DEBCARGO; then
30 abort 0 "Package already released."
31 fi
32
33 PREVBRANCH="$(git rev-parse --abbrev-ref HEAD)"
34 case "$PREVBRANCH" in
35 pending-$PKGNAME) true;;
36 pending-*) abort 1 "You are on a pending-release branch for a package other than $PKGNAME, $0 can only be run on another branch, like master";;
37 *) if git rev-parse -q --verify "refs/heads/$RELBRANCH" >/dev/null || \
38 git rev-parse -q --verify "refs/remotes/origin/$RELBRANCH" >/dev/null; then
39 git checkout "$RELBRANCH"
40 else
41 git checkout -b "$RELBRANCH"
42 fi;;
43 esac
44
45 if head -n1 "$PKGDIR/debian/changelog" | grep -qv UNRELEASED-FIXME-AUTOGENERATED-DEBCARGO; then
46 git checkout "$PREVBRANCH"
47 abort 0 "Package already released on branch $RELBRANCH. If that was a mistake then run:\ngit branch -D $RELBRANCH\nAnd re-run this script ($0 $*). You might have to delete the remote branch too:\ngit push --delete origin $RELBRANCH"
48 fi
49
50 ( cd "$PKGDIR"
51 sed -i -e s/UNRELEASED-FIXME-AUTOGENERATED-DEBCARGO/UNRELEASED/ debian/changelog
52 dch -m -r -D unstable ""
53 git add debian/changelog
54 )
55
56 revert_git_changes() {
57 git reset
58 git checkout -- "$PKGDIR/debian/changelog"
59 git checkout "$PREVBRANCH"
60 git branch -d "$RELBRANCH"
61 }
62
63 if ! run_debcargo --changelog-ready; then
64 revert_git_changes
65 abort 1 "Release attempt failed to run debcargo, probably the package needs updating (./update.sh $*)"
66 fi
67
68 if ! git diff --exit-code -- "$PKGDIR_REL"; then
69 revert_git_changes
70 abort 1 "Release attempt resulted in git diffs to $PKGDIR_REL, probably the package needs updating (./update.sh $*)"
71 fi
72
73 if ! ( cd build && SOURCEONLY=1 ./build.sh "$CRATE" $VER ); then
74 revert_git_changes
75 abort 1 "Release attempt failed (see messages above), possible reasons are: " \
76 "- build-dependencies not in Debian => release those first." \
77 "- packaged version is out-of-date => run \`./update.sh $*\`"
78 fi
79
80 git commit -m "Release package $PKGNAME"
81
82 DEBVER=$(dpkg-parsechangelog -l $BUILDDIR/debian/changelog -SVersion)
83 DEBSRC=$(dpkg-parsechangelog -l $BUILDDIR/debian/changelog -SSource)
84 DEB_HOST_ARCH=$(dpkg-architecture -q DEB_HOST_ARCH)
85 cat >&2 <<eof
86 Release of $CRATE ready as a source package in ${BUILDDIR#$PWD/}. You need to
87 perform the following steps:
88
89 Build the package if necessary, and upload
90 ==========================================
91
92 If the source package is already in Debian and this version does not introduce
93 new binaries, then you can just go ahead and directly dput the source package.
94
95 cd build && dput ${DEBSRC}_${DEBVER}_source.changes
96
97 If this is a NEW source package or introduces NEW binary packages not already
98 in the Debian archive, you will need to build a binary package out of it. The
99 recommended way is to run something like:
100
101 cd build && ./build.sh $CRATE $VER && dput ${DEBSRC}_${DEBVER}_${DEB_HOST_ARCH}.changes
102
103 This assumes you followed the "DD instructions" in README.rst, for setting up
104 a build environment for release.
105
106 If the build fails e.g. due to missing Build-Dependencies you should revert
107 what I did (see below) and package those missing Build-Dependencies first.
108
109 Push this pending-release branch
110 ================================
111
112 After you have uploaded the package with dput(1), you should push $RELBRANCH so
113 that other people see it's been uploaded. Then, checkout another branch like
114 master to continue development on other packages.
115
116 git push origin $RELBRANCH && git checkout master
117
118 Merge the pending-release branch when ACCEPTED
119 ==============================================
120
121 When it's ACCEPTED by the Debian FTP masters, you may then merge this branch
122 back into the master branch, delete it, and push these updates to origin.
123
124 git checkout master && git merge $RELBRANCH && git branch -d $RELBRANCH
125 git push origin master :$RELBRANCH
126
127 ----
128
129 The above assumes you are a Debian Developer with upload rights. If not, you
130 should revert what I just did. To do that, run:
131
132 git checkout master && git branch -D $RELBRANCH
133
134 Then ask a Debian Developer to re-run me ($0 $*) on your behalf. Also add your
135 crate to the "Ready for upload" list in TODO.rst so it's easy to track.
136 eof