Positively asserting that eprints will not move beyond Ubuntu 14x or that the apt repository will no longer be maintained is a little disconcerting. Is there a statement to that effect? If it’s just a matter of updating the repository with a signed release file that no one has gotten around to yet, that’s a different story. It shouldn’t take much to do that.

 

Also, there is an older method before the apt install method was introduced that used to work. Has anyone tried that with Ubuntu 16x? It involves installing the dependencies first and then the eprints from source. I’m a little pressed for time right now, but I have an older set of instructions that could be tried.

 

Ubuntu is arguably the most common go to distro these days. I’m surprised if the decision is made not to support it. That almost seems to indicate the end of life for eprints?

 

 

 

 

Yeah, I think the general rule for the time being is that EPrints is just not working on anything above 14.04. I’m not sure if there’s any kind of timescale for fixing that going forward. We were looking at bringing our repository (eprints.lincoln.ac.uk) onto a more modern Ubuntu install but we’ve had to cap it at 14.04 with the most recent EPrints on that.

 

 

I’ve given the root user a mysql password. That doesn’t resolve the release file issue with the apt repository now, though.

 

 

 

Hi Bruce,

I ran into similar issues with Ubuntu 16 and documented my work around here: http://www.eprints.org/tech.php/22140/attachment/message.html. There are other problems further down the chain, however.

The official line from Eprints Services that 14.04 is the highest supported version of Ubuntu for the software.

Andrew

Get Outlook for Android

 

From: Fulton, Bruce D - (bfulton)
Sent: Tuesday, 28 February, 21:23
Subject: [EP-tech] New ubuntu 16.x problem
To: eprints-tech@ecs.soton.ac.uk

Attempting to create a new eprints Ubuntu virtual machine (Ubuntu 16.04.2 LTS, VMware workstation) today, the process now breaks down at apt update with the following:

 

user1@eprints:~$ sudo apt update

[sudo] password for user1:

Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease

Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]

Hit:3 http://archive.canonical.com/ubuntu xenial InRelease

Get:4 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]

Ign:5 http://deb.eprints.org/3.3 stable/ InRelease

Get:6 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]

Ign:7 http://deb.eprints.org/3.3 source/ InRelease

Err:8 http://deb.eprints.org/3.3 stable/ Release

  404  Not Found [IP: 152.78.189.196 80]

Err:9 http://deb.eprints.org/3.3 source/ Release

  404  Not Found [IP: 152.78.189.196 80]

Reading package lists... Done

E: The repository 'http://deb.eprints.org/3.3 stable/ Release' does not have a Release file.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

E: The repository 'http://deb.eprints.org/3.3 source/ Release' does not have a Release file.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

user1@eprints:~$

 

According to the Man page, this seems to be a problem with a properly signed Release file for the repository, which apparently is now mandatory. If I’m reading this correctly, this will need to be fixed at EPrint’s end, unless someone knows of a workaround. I’ve verified earlier today that the 14.04 package is still working.

 

Bruce Fulton, MLIS, PhD
Assistant Professor, and
Certificate Coordinator
School of Information - University of Arizona
Harvill Building
1103 E 2^nd St #453A
Tucson, AZ 85721
Main   (520) 621-3565
Direct (520) 626-4631
Fax      (520) 621-3279
http://si.arizona.edu