[Pkg-netatalk-devel] netatalk

[Brian Campbell]

On Mon, Feb 10, 2014 at 8:11 PM, Jonas Smedegaard <dr at jones.dk> wrote:
> Welcome, Chris and Brian, to the Netatalk team!
>
> I have prepared a new release here:
>
>   git://anonscm.debian.org/git/pkg-netatalk/netatalk

Looks like you've been busy! That is looking pretty good.

I needed to make the following change to get it to work; there's no
need to patch our own changelog during the build.

diff --git a/debian/patches/103_fix_typos.patch b/debian/patches/103_fix_typos.p
index a286419..7bd57e1 100644
--- a/debian/patches/103_fix_typos.patch
+++ b/debian/patches/103_fix_typos.patch
@@ -134,17 +134,6 @@
  #####

  PAPDEST="`lpstat -D -p "${printer}" | grep -i descrip | sed 's/.*Description:.
---- a/debian/changelog
-+++ b/debian/changelog
-@@ -7,7 +7,7 @@
-     + Based on Unicode 6.1.0.
-     + Update experimental systemd service files to always run both afpd
-       and cnid_metad (unsuitable for 2.x: lack AppleTalk support).
--    + Update afpd to ensure our umask is not altered by eg pam_umask.
-+    + Update afpd to ensure our umask is not altered by e.g. pam_umask.
-     + Update  afpd to use GSS_C_NO_NAME as server principal when
-       Kerberos options -fqdn and -krb5service are not set.
-     + Update afpd CNID handling for TimeMachine volumes.
 --- a/doc/DEVELOPER
 +++ b/doc/DEVELOPER
 @@ -173,7 +173,7 @@

Before I push, however, I have a few questions about Debian packaging
workflow; as I said, I'm new to it. For one, when updating the
changelog, do you generally update the version number while it's in
development? I noticed that it was still 2.2.2-2, instead of 2.2.5-1.
Also, when doing a collaborative release like this, do I change the
changelog trailer to include my name and email? That's the most
convenient since I use Debian Changelog mode in Emacs, which doesn't
allow you to add more items until you "unfinalize" the changelog
entry, and finalizing it again puts my own information in the trailer.

And second, any time I tried to build this with simply "gbp
buildpackage -us -uc" I got the following error; however, if I use
"--export-dir=../netatalk-build" it works fine. Is this supposed to
work with just a plain "gbp buildpackage"? Do you have a particular
configuration of "git-buildpackage" that avoids this issue, or do you
simply always use an export dir?

 dpkg-source -i -I -b netatalk
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building netatalk using existing ./netatalk_2.2.5.orig.tar.gz
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/config/AppleVolumes.default.tmpl
|+++ b/config/AppleVolumes.default.tmpl
--------------------------
No file to patch.  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: fuzz is not allowed when applying patches
dpkg-source: info: if patch '101_drop_bogus_cfgfile_warning.patch' is
correctly applied by quilt, use 'quilt refresh' to update it
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -g0 -E
-b -B .pc/101_drop_bogus_cfgfile_warning.patch/ --reject-file=- <
netatalk.orig.QErPQB/debian/patches/101_drop_bogus_cfgfile_warning.patch
gave error exit status 1
dpkg-buildpackage: error: dpkg-source -i -I -b netatalk gave error exit status 2
debuild: fatal error at line 1364:
dpkg-buildpackage -rfakeroot -D -us -uc -i -I failed
gbp:error: Couldn't run 'debuild -i -I -us -uc': debuild -i -I returned 29

>
> If you haven't already then please establish ssh access to Alioth as
> described here: https://wiki.debian.org/Alioth/Git
>
> Then you should have write access by swapping above URL with this:
>
>   git+ssh://git.debian.org/git/pkg-netatalk/netatalk

Yep, SSH keys uploaded and seem to work.

> or, if your local account don't match your Alioth account, and you don't
> want to correlate using ~/.ssh/config:
>
>   git+ssh://${alioth-login}@git.debian.org/git/pkg-netatalk/netatalk
>
> I am heading for bed now - let's talk more tomorrow!

Thanks, will do!

-- Brian