From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Tracking package submissions with Debbugs
Date: Tue, 06 Sep 2016 07:57:09 +0000 [thread overview]
Message-ID: <87oa411mwa.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <54128cc9-ce83-0e57-199d-14679419564e@uq.edu.au>
Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
> Hi ng0,
>
> On 06/09/16 09:17, ng0 wrote:
>>> Who wants to take on this? Any volunteers?
>> On second note, my server is intentionally very minimal, so I have to
>> look at if gitlab will be fully functional (email etc).
>
> Did you have any success working with Kallithea? It seems on the face of
> it to be the most free-software and appropriate of the tools listed at
> the below Wikipedia link, but I don't have any experience with it.
> https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities
>
> ben
I'm working
(https://gitlab.com/packaging-guix/guix-kallithea/commits/master) on it
and this
https://bitbucket.org/conservancy/kallithea/issues/244/license-issue-in-your-dependency-graph
is where I am stuck at the moment.
Also Kallithea does have an issues tracker on their roadmap, but it is
not being worked on at the moment (I asked in their irc channel).
At the same time I'm working on darcs, gogs and a go build-system and
all kinds of other things. From packaging I don't know what gitlab
wants as I have not looked at it. But gogs and kallithea both look
easy to handle... gogs just needs a go build-system to make it easier to
package the dependencies.
I'm personally working with SaaSs as mirror for some of my repositories
and using plain git daemon without any web index for the rest.
I don't know if this is what you asked about.
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-09-06 7:57 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 10:46 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-13 11:11 ` David Craven
2016-08-13 11:23 ` ng0
2016-08-14 5:41 ` Pjotr Prins
2016-08-14 9:14 ` ng0
2016-08-15 1:39 ` David Craven
2016-08-15 4:55 ` Pjotr Prins
2016-08-15 9:11 ` David Craven
2016-08-16 13:17 ` Ricardo Wurmus
2016-08-16 13:29 ` Pjotr Prins
2016-08-15 11:53 ` Hartmut Goebel
2016-08-15 13:30 ` Danny Milosavljevic
2016-08-15 15:18 ` Alex Vong
2016-08-16 7:20 ` Hartmut Goebel
2016-08-16 14:06 ` Alex Vong
2016-08-18 11:47 ` Hartmut Goebel
2016-09-01 6:32 ` ng0
2016-09-01 11:19 ` ng0
2016-09-02 0:27 ` John Darrington
2016-09-02 0:58 ` ng0
2016-09-02 5:50 ` Alex Vong
2016-09-02 8:21 ` ng0
2016-09-02 10:54 ` Alex Vong
2016-09-03 16:44 ` Pjotr Prins
2016-09-03 16:55 ` David Craven
2016-09-03 19:19 ` Brendan Tildesley
2016-09-03 19:53 ` David Craven
2016-09-03 20:42 ` Efraim Flashner
2016-09-02 12:39 ` Tracking package submissions with Debbugs Ludovic Courtès
2016-09-02 14:29 ` Ricardo Wurmus
2016-09-03 0:35 ` Alex Vong
2016-09-03 13:47 ` Ludovic Courtès
2016-09-04 2:21 ` Alex Vong
2016-09-03 21:00 ` Efraim Flashner
2016-09-04 2:37 ` Alex Vong
2016-09-04 7:05 ` Andreas Enge
2016-09-04 16:57 ` ng0
2016-09-04 17:00 ` ng0
2016-09-04 17:09 ` David Craven
2016-09-05 12:52 ` Alex Kost
2016-09-05 20:22 ` Ludovic Courtès
2016-09-05 20:39 ` David Craven
2016-09-05 23:12 ` ng0
2016-09-07 20:38 ` Ludovic Courtès
2016-09-05 23:17 ` ng0
2016-09-05 23:54 ` David Craven
2016-09-06 0:01 ` Ben Woodcroft
2016-09-06 7:57 ` ng0 [this message]
2016-09-06 11:26 ` David Craven
2016-09-06 1:24 ` Alex Vong
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=87oa411mwa.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
/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).