From: Arun Isaac <arunisaac@systemreboot.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>,
38149@debbugs.gnu.org, "Wiktor Żelazny" <wz@freeshell.de>
Subject: [bug#38149] [WIP] gnu: Add qgis.
Date: Thu, 26 Dec 2019 19:09:11 +0530 [thread overview]
Message-ID: <cu7y2uzi4u8.fsf@systemreboot.net> (raw)
In-Reply-To: <20191223075502.3d9cd692@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
>> Also, we should push some of the simpler patches (say, the simple
>> update patches) to master right away. That will help to declutter
>> this bug report a little bit. WDYT?
>
> Sure.
I have pushed the patches regarding geos, proj, libgeotiff, gdal,
postgis and libspatialindex.
> Also, I think the licenses can be added right now.
I am not sure of the licenses of qgis. They need to be double
checked. So, I think we should wait until then to push those license
patches.
> Likewise the package updates, but probably not the python 2.7
> modification, especially if python 3 also inherits it.
> The latter should go to some other branch.
That's right. The python modification would trigger too many
rebuilds. Do you know which branch I should push it to?
> What's up with libgeotiff's disabled tests?
That was a WIP patch where the tests were failing. In the patch I
pushed, I fixed the tests and enabled them.
> Also, I think we usually don't list the license of non-installed files
> (like the cmake includes).
Ok, I made this modification before pushing the patches.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-26 13:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 11:27 [bug#38149] [WIP] gnu: Add qgis Wiktor Żelazny
[not found] ` <cu7eey1kl1x.fsf@systemreboot.net>
[not found] ` <20191123104752.gp6gafhjrs47dath@wz.localdomain>
2019-12-01 18:13 ` Arun Isaac
2019-12-02 14:31 ` Wiktor Żelazny
2019-12-03 17:45 ` Arun Isaac
2019-12-05 11:19 ` Arun Isaac
2019-12-07 10:51 ` Wiktor Żelazny
2019-12-10 17:08 ` Arun Isaac
2019-12-30 15:40 ` Wiktor Żelazny
2019-12-18 6:21 ` Björn Höfling
2019-12-18 8:59 ` Björn Höfling
2019-12-18 9:07 ` Björn Höfling
2019-12-20 16:52 ` Arun Isaac
2019-12-23 6:55 ` Danny Milosavljevic
2019-12-26 13:39 ` Arun Isaac [this message]
2019-12-26 14:53 ` Marius Bakke
2019-12-27 2:06 ` Arun Isaac
2020-01-27 22:48 ` Marius Bakke
2020-01-28 5:05 ` Arun Isaac
2020-03-22 15:45 ` Guillaume Le Vaillant
2020-03-23 21:00 ` Arun Isaac
2020-03-24 10:52 ` Guillaume Le Vaillant
2020-03-24 11:46 ` bug#38149: " Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7y2uzi4u8.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=38149@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=dannym@scratchpost.org \
--cc=wz@freeshell.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).