https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40863 --- Comment #18 from David Cook <dcook@prosentient.com.au> --- (In reply to Victor Grousset/tuxayo from comment #11)
I installed Debian 12 on a virtual machine and installed the updated version of Koha, but indexing didn't work
ok then nothing related to Debian 13, right?
On Debian 12 with 25.05, what were the error messages? These? .error retrieving biblio 4246 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 778. .error retrieving biblio 4247 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 778. .error retrieving biblio 4248 at /usr/share/koha/bin/migration_tools/rebuild_zebra.pl line 778.
Nothing more in the logs? Does the first thing when lauching the reindex is "error retrieving biblio" ?
So let's look at this a bit more... git show v25.05.05-1:misc/migration_tools/rebuild_zebra.pl | vim - 764 sub get_raw_marc_record { 765 my ( $record_type, $record_number ) = @_; 766 767 my $marc; 768 if ( $record_type eq 'biblio' ) { 769 eval { 770 my $biblio = Koha::Biblios->find($record_number); 771 $marc = $biblio->metadata_record( { embed_items => 1 } ); 772 }; 773 if ( $@ || !$marc ) { 774 775 # here we do warn since catching an exception 776 # means that the bib was found but failed 777 # to be parsed 778 warn "error retrieving biblio $record_number"; 779 return; 780 } 781 } else { 782 eval { $marc = GetAuthority($record_number); }; 783 if ($@) { 784 warn "error retrieving authority $record_number"; 785 return; 786 } 787 } 788 return $marc; 789 } As I noted above there was a line change between versions: - $marc = $biblio->metadata->record({ embed_items => 1 }); + $marc = $biblio->metadata_record( { embed_items => 1 } ); Now "metadata_record" in Koha/Biblio.pm actually calls $biblio->metadata->record() instead itself and then performs some additional work. It looks like the problem you're facing is probably at the stage of the MARC interacting with Koha::RecordProcessor. It's possible there's a bug in it, but... I still think it's a strong possibility that there's some problems lurking in your MARC data or item data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.