unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Rodriguez <yewscion@gmail.com>
To: 56346@debbugs.gnu.org
Subject: bug#56346: [BUG] emacs-parsebib and emacs-ebib out of sync
Date: Fri, 01 Jul 2022 18:40:10 -0400	[thread overview]
Message-ID: <87czeobg5b.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]


Hello,

The emacs-ebib package has been updated recently to depend upon new
functionality in the emacs-parsebib package, however there has not been
a release to allow emacs-parsebib to be updated, causing things to break
on a purely-guix install of these packages.

There has not been an upstream release tag created for emacs-parsebib
since 2021-12-08 (which was version 3.1.0). However, 11 days ago, the
actual library's version info was bumped to 4.1.0. This indicates that
there was a breaking change (which there apparently was).

I have commented on the commit bumping the internal version number[1]
and I opened an issue to the same effect[2]. I am also in the process of
recompiling the packages in my declaration that rely on emac-parsebib to
rely on the commit mentioned above.

So long as that works, I'll send a patch updating the Guix version of
this package to this more-recent 'release' of emacs-ebib.


[1]: https://github.com/joostkremers/parsebib/commit/185239020f878cfbe1036270e6c3d1026ba8f255
[2]: https://github.com/joostkremers/parsebib/issues/24

--

Christopher Rodriguez

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

             reply	other threads:[~2022-07-01 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 22:40 Christopher Rodriguez [this message]
2022-07-05  8:11 ` bug#56346: [BUG] emacs-parsebib and emacs-ebib out of sync Nicolas Goaziou

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=87czeobg5b.fsf@gmail.com \
    --to=yewscion@gmail.com \
    --cc=56346@debbugs.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).