-
-
Notifications
You must be signed in to change notification settings - Fork 528
Conversation
Okay, I made a mistake when I set the architecture to |
No problem! I'll review it. |
From the archive contents it seems you are installing to |
That's a very simple change, but shouldn't deb packages install to |
# | ||
# Note that date will be empty if the tag at question is a lightweight | ||
# tag (i.e., non-annotated) because they don't carry any tagger | ||
# information; it that case we simply fall back to the committer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aww hell, typo... Feels really bad when I need to rebase for a typo... I'll push a fixup commit for now and only squash after review.
Let's keep it common to AUR. It depends on us, not the package manager. But I don't think we would complain if someday
|
Of course not... I've never tried to submit anything / watch others submit anything to Debian/Ubuntu though, nor do I fancy doing that. Have you? (Honestly I'm not a Debian/Ubuntu fan. Stability my ass... I like Arch much better.) |
I loved Lubuntu. Now I have a dual boot with Manjaro LXQt and Lubuntu. But Ubuntu it is for my wife. Perspectives differ, and so does user competence, you see... |
It'll take me sometime (by EoD my time) to test installation on Ubuntu 16.04 and Ubuntu 14.04. OK? Need the systems. :) |
Of course, I personally just can't tolerate the outdatedness of packages... Anyway, I do have a whole bunch of Ubuntu boxes. I have spun up five (with Vagrant) in the past two days...
No problem, this is by no means urgent. |
Installs with minor errors... you need to fill 2 more fields:
|
Runs fine. |
Also when I try to download the changelog from synaptic:
Please add a changelog file in the same pull request. we'll update it from the next release. |
If you look at the script, description and maintainer fields are there, and there is a changelog (just a pointer to the GitHub release page, I can't automatically generate a Debian-compliant changelog). And vagrant-ubuntu-wily-64 8:49:13 [/tmp] >>>
curl -LO https://github.com/zmwangx/googler/releases/download/v2.4-testdeb-2/googler_2.4-testdeb-2-1_all.deb
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 608 0 608 0 0 883 0 --:--:-- --:--:-- --:--:-- 883
100 18250 100 18250 0 0 12947 0 0:00:01 0:00:01 --:--:-- 36794
vagrant-ubuntu-wily-64 8:49:26 [/tmp] >>>
sudo dpkg -i googler_2.4-testdeb-2-1_all.deb
Selecting previously unselected package googler.
(Reading database ... 93513 files and directories currently installed.)
Preparing to unpack googler_2.4-testdeb-2-1_all.deb ...
Unpacking googler (2.4-testdeb-2-1) ...
Setting up googler (2.4-testdeb-2-1) ...
Processing triggers for man-db (2.7.4-1) ...
vagrant-ubuntu-wily-64 8:49:38 [/tmp] >>>
dpkg -s googler
Package: googler
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 36
Maintainer: Arun Prakash Jana <arun@tuxdiary.com>
Architecture: all
Version: 2.4-testdeb-2-1
Depends: python (>= 2.7)
Description: Google Search and News from the command-line
See https://github.com/jarun/googler#readme.
vagrant-ubuntu-wily-64 8:52:13 [/tmp] >>>
dpkg -L googler
/.
/usr
/usr/bin
/usr/bin/googler
/usr/share
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/googler.1.gz
/usr/share/doc
/usr/share/doc/googler
/usr/share/doc/googler/copyright
/usr/share/doc/googler/README.md.gz
/usr/share/doc/googler/changelog.Debian.gz
vagrant-ubuntu-wily-64 8:52:23 [/tmp] >>>
zcat /usr/share/doc/googler/changelog.Debian.gz
googler (2.4-testdeb-2-1) UNRELEASED; urgency=medium
* See full changelog at
https://github.com/jarun/googler/releases/tag/v2.4-testdeb-2
-- Arun Prakash Jana <arun@tuxdiary.com> Fri, 29 Apr 2016 02:24:17 +0530 ??? |
By the way, I thought about including a changelog in this PR, but vetoed that idea, because Debian's changelog format is very peculiar (see example above), and I see no reason why our changelog should follow Debian's format (you won't enjoy appending to those later). And if this ever acquires any more official status, our changelog will be pretty much useless anyway, it will need to be hand-crafted (to include ticket numbers and such). As an auto-generated deb I'm pretty happy with the current changelog I'm generating. |
Oh, so the package |
Re synaptic: I've no experience with that. What command did you run? Maybe it can't do anything because googler is from a standalone deb, not a repository? |
As we are not going follow Debian changelog format, don't worry about it. I'm checking what this package 'min' is :). |
Actually I am following the Debian changelog format. Just not incremental. |
min is https://palmeral.github.io/min/. |
👍 |
The changelog is correct format, however it's never going to work unless its added to the "offical" repos. Synaptic just provides a broken button on packages anyway. The feature always been a bit bleh. This goes for the screenshot bit as well. The deb packages generated are to spec (within reason) and I completely love this method. |
Make sense. |
And for the path for aur package, Archlinux's policy is to use /usr/, altho you'll find some people just don't care and do anything they want. Debian (unless it has changed) had a policy of using /usr/ for any packages such as this one. However /usr/local/ was reserved for the "sys admin" or local user. It all sounds very silly I'm sure. But I think both are fine choices, If everyone prefers /usr/local/ then it's ok. I can't foresee any huge issues with this, personally I'd go with /usr/ but I'm crazy. There are some cases with SOME distros that /usr/local/ isnt even in a users $PATH. |
Why? As for this one, the only reasonable argument against |
Guys! |
In the production environment we may only want to build deb for tags, although testing the build process doesn't hurt.
We already CI_FORCE_TEST. Add CI_SKIP_TEST for feature parity. But when would it be useful? When we're playing with other parts of the CI system and not concerned about testing.
It's impossible to check exit status of command substitutions inside heredocs, and saving command substitution results in variables before we enter heredocs is not very elegant, so we instead signal a C&C PID in the env var $NOTIFY_PID (if available) on error inside helper functions.
Rebased on master again. |
Done! Please verify once. |
@jarun Your credentials seem to be bad (see https://travis-ci.org/jarun/googler/jobs/127056857). Are you sure the token you used has the |
By the way, instead of pushing to master, let's work on another branch, say, |
I have temporarily set |
I'll try it again. |
Check now. |
Got it this time! https://travis-ci.org/jarun/googler/jobs/127063645 We can delete the tag once we verify that the deb works. |
Works for me on both wily64 and wily32. |
Worked fine here too! |
👍 Now we need to add instructions to README. I suggest that we also retro-publish a v2.3 deb package so that we can update README before 2.4. I built one from https://github.com/zmwangx/googler/releases/tag/v2.3deb, which is v2.3 plus cherry-picked dfe0476 (the Makefile patch to make packaging script work). The deb:
|
Please push directly. I can't keep my eyes open anymore. Have a great day! 👍 |
Good night. |
I added your info in man and program help. Hope that's fine with you. |
No problem, but now it looks like you didn't do anything in 2016... Which is not true. |
Hehehehe! I'll add some hyphens then :). |
Also, we (or rather, you) have rewritten most of the code, so I think "Modified" is unnecessary. A "Copyright" line like Henri's should do. |
Let's leave it with Henri ;) for the time being. I wish he knows his tool is being maintained well. :) |
Yeah, I'm just saying
is more accurate. |
Done :) |
Closing this as it's merged locally. |
I have improved my deb package building script and figured out uploading from Travis to GitHub releases. If you are interested in one more installation channel, this is almost ready to be integrated. (By the way, I doubt that googler could make its way into Debian's official repositories, so IMO either this or a PPA is the best we can do.)
My script can build a deb package off any commit-ish, and .travis.yml has been set up to upload the artifact to each pushed tag. Here is an example uploaded automatically from https://travis-ci.org/zmwangx/googler/jobs/126560102:
(Update: See #67 (comment) for something better.)
Note that this PR cannot be merged as is. All commits except the
.travis.yml
one are ready, but.travis.yml
needs to be adapted to use your API token and upload fromjarun/googler
instead ofzmwangx/googler
. I believe all you need to do is to create a token withpublic_repo
access, encrypt the token with Travis's CLI client:and replace the current ciphertext with the ciphertext you get.