Problems with Debian Repository (Writing more...)

Questions about Wine on Linux
Post Reply
3d0
Newbie
Newbie
Posts: 1
Joined: Tue Apr 10, 2018 12:58 pm

Problems with Debian Repository (Writing more...)

Post by 3d0 » Tue Apr 10, 2018 1:04 pm

I'm having trouble adding the debian stretch repository, it yields a Writing more data than expected

I used the wiki configuration:

cat /etc/apt/sources.list.d/wine.list

Code: Select all

deb https://dl.winehq.org/wine-builds/debian/ stretch main
#deb https://dl.winehq.org/wine-builds/debian/ unstable main
apt update partial output

Code: Select all

Get:16 https://dl.winehq.org/wine-builds/debian stretch/main i386 Packages [3,320 B]
Err:16 https://dl.winehq.org/wine-builds/debian stretch/main i386 Packages
  Writing more data than expected (4963 > 3320)
  Hashes of expected file:
   - Filesize:3320 [weak]
   - SHA256:25e230111da5beac9ade32f7b730be7c50caaf15e3f1cd3548575a95754fbb42
   - SHA1:ee359f159553144cec689b7ef93b0c741096e60b [weak]
   - MD5Sum:3f219664545343f7a221b2b6a469563f [weak]
  Release file created at: Sat, 31 Mar 2018 21:53:40 +0000
Get:17 https://dl.winehq.org/wine-builds/debian stretch/main amd64 Packages [3,324 B]
Err:17 https://dl.winehq.org/wine-builds/debian stretch/main amd64 Packages
Fetched 4,701 B in 2s (1,880 B/s)
Reading package lists... Done
E: Failed to fetch https://dl.winehq.org/wine-builds/debian/dists/stretch/main/binary-i386/Packages.xz  Writing more data than expected (4963 > 3320)
   Hashes of expected file:
    - Filesize:3320 [weak]
    - SHA256:25e230111da5beac9ade32f7b730be7c50caaf15e3f1cd3548575a95754fbb42
    - SHA1:ee359f159553144cec689b7ef93b0c741096e60b [weak]
    - MD5Sum:3f219664545343f7a221b2b6a469563f [weak]
   Release file created at: Sat, 31 Mar 2018 21:53:40 +0000
E: Failed to fetch https://dl.winehq.org/wine-builds/debian/dists/stretch/main/binary-amd64/Packages.xz  
E: Some index files failed to download. They have been ignored, or old ones used instead.
Thanks

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

Re: Problems with Debian Repository (Writing more...)

Post by dimesio » Tue Apr 10, 2018 3:32 pm

Another user has reported the same problem; one of you should file a bug.

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

Re: Problems with Debian Repository (Writing more...)

Post by dimesio » Tue Apr 10, 2018 3:58 pm


User avatar
Bob Wya
Level 12
Level 12
Posts: 2884
Joined: Sat Oct 16, 2010 7:40 pm
Location: Scotland
Contact:

Re: Problems with Debian Repository (Writing more...)

Post by Bob Wya » Tue Apr 10, 2018 3:59 pm

This was discussed on the #winehq irc channel this afternoon...

Code: Select all

 <duboisj>  someone in a CW channel is asking why the winehq download for debian points to https://repos.wine-staging.com/alesliehughes/debian/
      <zf>  duboisj: plain or staging?
 <duboisj>  I don't know how it normally works.  It's one of our customers who normally isn't in this channel, I just saw messages in both
       -*-  duboisj playing telephone again
 <duboisj>  but this looks like staging: https://dl.winehq.org/wine-builds/
      <zf>  hmm, yes
 <duboisj>  This looks like a winehq page: https://dl.winehq.org/wine-builds/android
 <duboisj>  I guess this is the source of nsivov's problem
<julliard>  looks like spurious index.html files got uploaded
<julliard>  nsivov: is it working now?
  <nsivov>  no, same error
  <nsivov>  aptitude shows: ... NO_PUBKEY <key>
 <duboisj>  the guy in our channel points out that this: https://dl.winehq.org/wine-builds/debian/dists/ still points to staging
      <zf>  duboisj: hmm, it seems to work for me?
  <nsivov>  this one https://dl.winehq.org/wine-builds/debian/dists/buster/InRelease changed probably - Label: alistairs-wine
      <zf>  ah, I take it back, then
Bob

Seda
Level 2
Level 2
Posts: 16
Joined: Tue Jan 07, 2014 9:47 am

Re: Problems with Debian Repository (Writing more...)

Post by Seda » Tue Apr 10, 2018 4:09 pm

dimesio wrote:Someone filed a bug: https://bugs.winehq.org/show_bug.cgi?id=44955.
That'd be me. I waited quite a while because it looked like it was simply being moved/adjustments were being made to set the build system up differently. It's been broken for approximately 20h that I'm aware of.

I've spent quite some time making sure my apt-cacher-ng/https-remap wasn't the cause to hopefully avoid looking stupid :p

Post Reply