From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: with regards to kallithea
Date: Fri, 31 Mar 2017 10:59:43 +0000 [thread overview]
Message-ID: <20170331105943.frlneckpps7wnijq@abyayala> (raw)
Hi,
I thought I'll send an update on the process of packaging kallithea.
When I got in contact with upstream, they told me that we could go ahead
and simply test wether new versions of the dependencies will work they
only know it for some of them.
Seems to be a problem not unique to Guix that people want new
dependencies and don't want to keep ancient versions around, I think
Ubuntu was mentioned as another recent bug similar to mine.
The other idea they mentioned was to just build from a git commit, which
would fix certain dependency versions already.
I should ping them on the status of the ticket, it's been a while but I
don't imply for myself that they have forgotten about it.
How shall we proceed?
reply other threads:[~2017-03-31 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170331105943.frlneckpps7wnijq@abyayala \
--to=contact.ng0@cryptolab.net \
--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).