Opened 5 years ago

Closed 5 years ago

#8853 closed enhancement (fixed)

biber-2.7

Reported by: ken@… Owned by: ken@…
Priority: normal Milestone: 8.0
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

This was released in December, 2.6 is now in a versioned directory.

Treat this as two parts:

  1. Change the book to point to the versioned sourceforge directory for 2.6.
  1. Review altered dependencies for 2.7, including within the perl modules it needs. Given the size of previous changes, this might not get done for BLFS-8.0.

Change History (8)

comment:1 by ken@…, 5 years ago

Owner: changed from blfs-book@… to ken@…
Status: newassigned

comment:2 by ken@…, 5 years ago

Summary: biblatex-biber-2.7biber-2.7

Bruce noticed there are releases at github - switch to using those, they are called biber-2.6, biber-2.7. The 2.6 tarball is somewhat larger that before - a lot of files previously not in the releases (build scripts for various platforms), plus some more docs and testfiles.

comment:3 by ken@…, 5 years ago

Source changed to the github version of biber-2.6 at r18262, investigation of 2.7 to be done.

comment:4 by ken@…, 5 years ago

Oh Joy, the usual mass of changes from "Release early, release often" in some of the dependent modules. I have discovered I missed one low-level dependency when I did 2.6, will fix that tomorrow.

Meanwhile, I'm stalled at a test failure in a new module - I've raised an issue at github.

comment:5 by ken@…, 5 years ago

As usual with perl, mea culpa. Will continue tomorrow.

comment:6 by ken@…, 5 years ago

Done at r18296. Because of the changes in the low-down perl-modules needed by dependencies, particularly some of the DateTime modules, I have attempted to verify these with a build based on the deps for biber shown in the book, in that order. But I had already installed libwww-perl as part of my normal build, and there were a couple of fubars in my initial changes, so whilst this should be better than my previous attempts to update to a new biber it is still "buyer beware".

comment:7 by Douglas R. Reno, 5 years ago

Ken, did you forget to close the ticket?

in reply to:  7 comment:8 by ken@…, 5 years ago

Resolution: fixed
Status: assignedclosed

Replying to renodr:

Ken, did you forget to close the ticket?

Yes.

Note: See TracTickets for help on using tickets.