WineHQ Repository Server: Incorrectly Configured

Post issues, bugs, and feature requests about the various WineHQ websites to this forum.
Locked
teward
Level 1
Level 1
Posts: 6
Joined: Sat Nov 04, 2017 10:56 am

WineHQ Repository Server: Incorrectly Configured

Post by teward » Thu Dec 20, 2018 2:35 pm

The signing key was updated yesterday, but now these errors come out of WineHQ's repositories for Ubuntu:

Code: Select all

N: Repository 'https://dl.winehq.org/wine-builds/ubuntu bionic InRelease' changed its 'Version' value from '18.04' to ''
E: Repository 'https://dl.winehq.org/wine-builds/ubuntu bionic InRelease' changed its 'Codename' value from 'bionic' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Y'all misconfigured your repository servers.

User avatar
dimesio
Moderator
Moderator
Posts: 12675
Joined: Tue Mar 25, 2008 10:30 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by dimesio » Thu Dec 20, 2018 8:37 pm

I googled that message about explicitly accepting the changes, and came up with https://askubuntu.com/questions/989906/ ... -ppa-label.

Are you still using apt-get? That's been deprecated for some time; use apt. Installing from the current repository works fine here.

teward
Level 1
Level 1
Posts: 6
Joined: Sat Nov 04, 2017 10:56 am

Re: WineHQ Repository Server: Incorrectly Configured

Post by teward » Thu Dec 20, 2018 9:17 pm

dimesio wrote:I googled that message about explicitly accepting the changes, and came up with https://askubuntu.com/questions/989906/ ... -ppa-label.

Are you still using apt-get? That's been deprecated for some time; use apt. Installing from the current repository works fine here.
This was in the automatic update logs from the Ubuntu automatic updater. This uses a direct backend to apt and I can't confirm whether it is or isn't using `apt-get` or not. This said, if it is using `apt-get` that's because `apt-get` can be more usable in scriptable environments by automatic updates.

I pulled log data here directly from the system logs that the update system sent to me upon the error cases.

User avatar
dimesio
Moderator
Moderator
Posts: 12675
Joined: Tue Mar 25, 2008 10:30 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by dimesio » Thu Dec 20, 2018 9:53 pm

The repository is not misconfigured, but it has changed, and the changes are intentional. Using apt directly on the command line works without any problem.

As to how to straighten out the updater app, I'd try using apt on the command line and see if that straightens it out, and if it doesn't, ask on the Ubuntu forum what to do.

teward
Level 1
Level 1
Posts: 6
Joined: Sat Nov 04, 2017 10:56 am

Re: WineHQ Repository Server: Incorrectly Configured

Post by teward » Thu Dec 20, 2018 10:01 pm

Nope, pretty sure it's misconfigured. Especially since `apt-get` is not yet deprecated. (These lack of items break basic package repo policy including Debian's I'm surprised you don't get them coming around and complaining more, but eh, end users vs. power users)

`apt-get` has not yet been deprecated by *any* of the developers in Ubuntu or Debian, therefore stating that it's 'deprecated' is an incorrect statement.

(FYI: I'm an Ubuntu Developer with the Server Team, so I'm well aware of whether apt-get is deprecated or not - and it is not)

jkfloris
Level 6
Level 6
Posts: 658
Joined: Thu Aug 14, 2014 10:10 am

Re: WineHQ Repository Server: Incorrectly Configured

Post by jkfloris » Fri Dec 21, 2018 7:58 am

(Just my 2 cents)
apt is the program for the end-user. It has the most common options and is user-friendly.
"Power users" still can use apt-get (there are options that aren't available in apt),
and probably they know how to accept changes in the repository InRelease file.

Code: Select all

apt-get update -y --allow-releaseinfo-change
A couple of months ago Google had the same, when they changed their name from "Google, Inc"' to "Google LLC"
https://stackoverflow.com/questions/509 ... a/50942354

User avatar
dimesio
Moderator
Moderator
Posts: 12675
Joined: Tue Mar 25, 2008 10:30 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by dimesio » Fri Dec 21, 2018 9:40 am

(FYI: I'm an Ubuntu Developer with the Server Team, so I'm well aware of whether apt-get is deprecated or not - and it is not)
Well then you should know far more than I about how to explicitly accept the changes as the updater app is demanding. As for the repository itself, as I said, it has changed. Ordinary users don't seem to be having a problem with it once they download the new key.

User avatar
dimesio
Moderator
Moderator
Posts: 12675
Joined: Tue Mar 25, 2008 10:30 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by dimesio » Fri Dec 21, 2018 10:50 am

FYI (for power users who pay attention to things like repository structure), the WineHQ Debian and Ubuntu repositories no longer follow Debian structure. Instead, they use a flat structure to match the OBS repository structure. This may not be readily apparent when browsing the directories, because the old packages are still there in their old locations.

ctrlbru
Newbie
Newbie
Posts: 2
Joined: Sat Dec 22, 2018 1:54 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by ctrlbru » Sat Dec 22, 2018 1:58 pm

I get a different error now: the bionic Packages file seems to be partial (57840 bytes instead of 62840) and the hashes of course don't compare. This is the italian error:

Code: Select all

Scaricamento di:25 https://dl.winehq.org/wine-builds/ubuntu bionic/main i386 Packages [62,8 kB]
Errore:25 https://dl.winehq.org/wine-builds/ubuntu bionic/main i386 Packages
  Il file ha una dimensione non attesa (57840 != 62840). Sincronizzazione del mirror in corso? [IP: 151.101.194.217 443]
  Hashes of expected file:
   - Filesize:62840 [weak]
   - SHA512:4cb1c34f18f98a221daadd61b682590f17fb0035f460dbe9a66b3679993d1191c9e0bbd3254c48639b100bfc876417772d66b74d57006c0e34229414a7ec2ad0
   - SHA256:374e0b85f8ea916855810162869fd731d181420d0b1a258c979615890134912e
   - SHA1:f88ae95169d615462add9644633901274a1c1f68 [weak]
   - MD5Sum:d5d365efc28b7e5b04bc6f18b598c6e6 [weak]
  Release file created at: Sat, 22 Dec 2018 18:24:00 +0000

User avatar
dimesio
Moderator
Moderator
Posts: 12675
Joined: Tue Mar 25, 2008 10:30 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by dimesio » Sat Dec 22, 2018 3:46 pm

Well, Google translate tells me that "Sincronizzazione del mirror in corso?" means "Mirror synchronization in progress?", and looking at the timestamp of the error message, that's my guess what happened. So try again, if you haven't already.

ctrlbru
Newbie
Newbie
Posts: 2
Joined: Sat Dec 22, 2018 1:54 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by ctrlbru » Sat Dec 22, 2018 3:52 pm

Yes now it works, since the file had been partial for over 2 hours I thought it was simply broken.

Thanks

teward
Level 1
Level 1
Posts: 6
Joined: Sat Nov 04, 2017 10:56 am

Re: WineHQ Repository Server: Incorrectly Configured

Post by teward » Sat Dec 22, 2018 10:07 pm

Just to comment about "APT Works!"... it doesn't.

Code: Select all

N: Repository 'https://dl.winehq.org/wine-builds/ubuntu bionic InRelease' changed its 'Version' value from '18.04' to ''
E: Repository 'https://dl.winehq.org/wine-builds/ubuntu bionic InRelease' changed its 'Codename' value from 'bionic' to ''
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] 
It lets us *bypass* the error, but the error still exists (it's still bound by apt-secure).

I would suggest that you update the wiki pages for the Ubuntu repos and such accordingly to make a notice about this. Because Mint, Ubuntu, Debian, etc. users will all have this problem whether using apt or not.

User avatar
dimesio
Moderator
Moderator
Posts: 12675
Joined: Tue Mar 25, 2008 10:30 pm

Re: WineHQ Repository Server: Incorrectly Configured

Post by dimesio » Sat Dec 22, 2018 10:29 pm

The instructions already tell users to run apt update. Are you saying that the message persists even after the changes are accepted through apt update?

I also wouldn't call it an error message. The information that the repository has changed is correct, and users already know that, because they had to download a new key. All the message does is ask them to confirm their acceptance.

Locked