Update documentation about Debian

README.md

@@ -41,10 +41,8 @@ https://aur.archlinux.org/packages/telegram-purple/
 
 #### Debian
 
-At the time of writing, the package hasn't been accepted yet.
-Please first check if it's already available to you: `sudo apt-get install telegram-purple`
-
-If this doesn't work because the package doesn't exist (yet), please build it from source.
+You can build it from source (see following section) or build a `.deb` file
+for your package manager.
 
 
 Building From Source
@@ -85,12 +83,6 @@ this indicates that this version is in fact much further than just
 
 ##### Debian / Ubuntu
 
-We are working on a Debian package! Please first check if it's already available to you: `sudo apt-get install telegram-purple`
-
-If the above works, then you should stop here: It is now installed.
-
-If the above fails: Don't worry, just continue building it by yourself. Next you need to install these dependencies:
-
         sudo apt-get install libgcrypt20-dev libpurple-dev libwebp-dev gettext build-essential
 
 
@@ -223,17 +215,16 @@ Building the Debian Package
 If you just need a `.deb`, simply do:
 
     sudo apt-get install debhelper
-    git checkout debian-master
-    git submodule update --recursive
     fakeroot ./debian/rules binary
 
-And you're done! The `.deb` is in the directory at which you started.
+And you're done!  The `telegram-purple_….deb` and `telegram-purple-dbgsym_….deb` files
+are in the parent directory.
 To show some info about it, try this:
 
     dpkg --info telegram-purple_*.deb
 
-`debian-master` always points to a version that was submitted to Debian. (Note that this doesn't exist yet, as we haven't released to Debian yet.)
-`debian-develop` is the candidate for the next submission.
+Please note that installing the debugging symbols (`dbgsym`)
+help a lot in troubleshooting, so please do install them, too!
 
 #### Debian Maintainers ####
 
@@ -244,16 +235,15 @@ Here's how you can generate a `.orig.tar.gz`:
 
     make dist
 
-Note that these are incompatible with the old `debian/genorigtar.sh`
-tarballs, and can't be made compatible easily. If you need the tarball
-from "back then", see the documentation there.
-
-This command requires the original tar to exist (and will fail otherwise,
-although the error message will be misleading) will build all further files,
+The following command requires the original tar to exist,
+and will build all further files,
 specifically `.debian.tar.xz`, `.dsc`, `.deb`, and `.changes`:
 
     dpkg-buildpackage
 
+If this fails with a cryptic error message,
+first make sure that the `….orig.tar` really is in place.
+
 For the upload, you should use `pbuilder` and similar to build the package
 in a more minimalistic environment. That covers the official part of the work-flow.
 
@@ -265,6 +255,8 @@ and `.dsc` files, do this:
     false # Move tar to parent directory, by hand
     dpkg-source -b .
 
+Note that we no longer actively try to get it into the Debian repository.
+
 1.3.0
 -----
 

debian/.gitignore

@@ -1,3 +1,8 @@
 /files
 /telegram-purple/
 /telegram-purple.*
+
+/.debhelper/
+/autoreconf.after
+/autoreconf.before
+/debhelper-build-stamp

debian/changelog

@@ -1,3 +1,11 @@
+telegram-purple (1.3.1-1) UNRELEASED; urgency=medium
+
+  * New upstream release
+  * No longer actively try to push it into Debian: too unstable.
+    If you really want a .deb file, see README.md in the toplevel directory.
+
+ -- Ben Wiederhake <Ben.Wiederhake@gmail.com>  Mon, 10 Apr 2017 23:31:32 +0200
+
 telegram-purple (1.3.0-1) unstable; urgency=medium
 
   [ Hugues Morisset ]