Bug#809623: RFS: telegram-purple/1.2.5
Hello,
sorry for the long wait, real life happened. Also, note the version bump
in the subject from 1.2.3 to 1.2.5.
Seems like it, true, but sadly is necessary. The package is in version
control, and unless we provide pre-bundled origtars somewhere (which
won't happen), this has to build the origtar by invoking "make dist" in
the source tree.
why you cant provide pre-bundled origtars? I know some project that does exactly the same.
We now bundle the origtar, and listen for it in d/watch
Now this is getting absurd: the whole point of dh get-orig-source is to >support people for who "git pull" is too complicated. But suddenly I can
assume that git is installed, although git is not pulled by build-essential?
Resolved.
Long explanation:
Back then, I (wanted to) implement dh get-orig-source by:
- git clone-ing the repository
- git checkout the required version
- recreate origtar from that
... which is error-prone and unnecessarily complex.
Starting with 1.2.5, the orig-tar is part of the release, so we can just
use uupdate.
Now I come with a question.
You want to maintain the package only in Debian? or in all linux distro around the globe?
I would like to see this work helping all Debian-derivatives.
A month ago, before I went inactive for a month, (long before Ubuntu's
DebianImportFreeze), I hoped that telegram-purple would make it into
Debian unstable and therefore into Ubuntu 2016-04.
Well, that didn't work. Also, see below. As it turns out, pushing 1.2.5
into Debian right now would be a bad idea.
you are doing the repack work as Debian work, this means that other linux derivatives
won't ever gain from the work, and they will need to do it again.
Thanks to the published origtar, this should become a bit easier in the
future.
Pushing the tarball (complete and reduced) upstream, will save a lot of work for everybody
and simplify a lot the Debian packaging
(just a simple watch file, with no repack at all).
Signed :)
Due to Telegram cranking out unexpected features that break everything,
we won't push 1.2.5 into Debian anyway, so that's why I don't bother
with another RFS yet.
Regards,
Ben
Reply to: