I’m getting update errors on my Ubuntu machine this morning:
Err:8 http://maven.xwiki.org stable/ Release
403 Forbidden [IP: 92.222.135.198 80]
Reading package lists… Done
E: The repository ‘http://maven.xwiki.org 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.
Is something broken on the repository, or something changed? Thanks.
-Alan
Unable to reproduce it. It is working fine here:
Get:1 http://maven.xwiki.org stable/ xwiki-tomcat9-mysql 16.7.0 [1,530 B]
Get:2 http://maven.xwiki.org stable/ xwiki-mysql-common 16.7.0 [5,662 B]
Get:3 http://maven.xwiki.org stable/ xwiki-tomcat9-common 16.7.0 [3,344 B]
Get:4 http://maven.xwiki.org stable/ xwiki-common 16.7.0 [315 MB]
51% [4 xwiki-common 142 MB/315 MB 45%] 253 kB/s 11min 26s^52% [4 xwiki-common 148 MB/315 MB 47%] 340 kB/s 8min 13s^Fetched 315 MB in 18min 22s (286 kB/s)
(Reading database ... 311712 files and directories currently installed.)
Preparing to unpack .../xwiki-tomcat9-mysql_16.7.0_all.deb ...
Unpacking xwiki-tomcat9-mysql (16.7.0) over (16.6.0) ...
Preparing to unpack .../xwiki-mysql-common_16.7.0_all.deb ...
Unpacking xwiki-mysql-common (16.7.0) over (16.6.0) ...
Preparing to unpack .../xwiki-tomcat9-common_16.7.0_all.deb ...
Unpacking xwiki-tomcat9-common (16.7.0) over (16.6.0) ...
Preparing to unpack .../xwiki-common_16.7.0_all.deb ...
Unpacking xwiki-common (16.7.0) over (16.6.0) ...
Setting up xwiki-common (16.7.0) ...
Installing new version of config file /etc/xwiki/version.properties ...
Setting up xwiki-mysql-common (16.7.0) ...
Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/xwiki.conf
dbconfig-common: flushing administrative password
Setting up xwiki-tomcat9-common (16.7.0) ...
Setting up xwiki-tomcat9-mysql (16.7.0) ...
Slow on getting xwiki-common
, though.
Thanks for checking… it’s working today. Maybe someone was working on or updating the repo then.
Never mind…
-Alan