unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 48213@debbugs.gnu.org
Subject: bug#48213: offlineimap build fails
Date: Thu, 27 May 2021 22:55:10 +0200	[thread overview]
Message-ID: <86lf7znbgx.fsf@gmail.com> (raw)
In-Reply-To: <87y2cumdwt.fsf@netris.org> (Mark H. Weaver's message of "Tue, 04 May 2021 16:39:19 -0400")

Hi,

On Tue, 04 May 2021 at 16:39, Mark H Weaver <mhw@netris.org> wrote:

>From the command line, you can simply do this:
>
>   guix build offlineimap --without-tests=python2-rfc6555
>
> Within an OS configuration, or within a profile "manifest" file (if you
> use "guix package --manifest", which is highly recommended), you can use
> the following Scheme expression in place of 'offlineimap':
>
>   (let ((transform (options->transformation
>                     '((without-tests . "python2-rfc6555")))))
>     (transform offlineimap))

The package offlineimap will go sooner or later since Python 2 is EOL.
The migration from Py2 to Py3 is not clear [1] and the README [2] says:

  > As one of the maintainer of OfflineIMAP, I'd like to put my efforts into
  > [imapfw](http://github.com/OfflineIMAP/imapfw). **imapfw** is software in
  > development that I intend to replace OfflineIMAP with in the long term.
  >
  > That's why I'm not going to continue OfflineIMAP development. I'll continue
  > to maintain OfflineIMAP (fixing small bugs, reviewing patches and merging,
  > and rolling out new releases), but that's all.
  >
  > While I keep tracking issues for OfflineIMAP, you should not expect future support.
  >
  > You won't be left at the side. OfflineIMAP's community is large enough so that
  > you'll find people for most of your issues.
  >
  > Get news from the [blog][blog].
  >
  >                                  Nicolas Sebrecht. ,-)

IMHO, the transformation is the easiest to still have the package and
let the time to switch (to Offlinemap or something else).  For instance,

<https://github.com/OfflineIMAP/offlineimap3>

Note the package should always be available via inferiors.

All the best,
simon

1: <https://github.com/OfflineIMAP/offlineimap/issues/670>
2: <https://raw.githubusercontent.com/OfflineIMAP/offlineimap/master/README.md>





  parent reply	other threads:[~2021-05-27 20:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04  1:11 bug#48213: offlineimap build fails Bone Baboon via Bug reports for GNU Guix
2021-05-04  9:08 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2021-05-05  1:35   ` Bone Baboon via Bug reports for GNU Guix
2021-05-06  3:32   ` Bone Baboon via Bug reports for GNU Guix
2021-05-04 20:39 ` Mark H Weaver
2021-05-11 14:53   ` Bone Baboon via Bug reports for GNU Guix
2021-05-27 20:55   ` zimoun [this message]
2021-05-30 19:27     ` Mark H Weaver
2021-07-02 16:42       ` zimoun
2021-07-13  8:24     ` zimoun
2021-08-17 21:20       ` zimoun

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=86lf7znbgx.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=48213@debbugs.gnu.org \
    --cc=mhw@netris.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).