Bug 16107 - Multiple repository copies are inconsistent
: Multiple repository copies are inconsistent
Status: RESOLVED WORKSFORME
Product: Logitech Media Server
Classification: Unclassified
Component: Debian
: 7.5.x
: PC Debian Linux
: P1 normal with 17 votes (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-21 14:00 UTC by Marc Auslander
Modified: 2011-01-24 09:35 UTC (History)
8 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Auslander 2010-04-21 14:00:40 UTC
as of now for testing:

8.12.192.126 Package is 30649,
198.78.200.126 is 30657
192.221.100.126 is 30663

these are all ip addresses associated with debian.slimdevices.com

The pools are similarly inconsistent.

The pretty much breaks the package updater - I've stopped trying.
Comment 1 Marc Sherman 2010-04-27 05:52:44 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 Marc Sherman 2010-04-27 05:55:18 UTC
This is a real mess. Even within some of the individual mirrors, the version listed in the Packages file doesn't match the version actually available in the pool directory (at least for the testing dist).

I tried eliminating the multiple mirrors problem from the equation (by hardcoding one of the ips in /etc/hosts), and still couldn't update because of this issue.
Comment 3 Jim McAtee 2010-05-15 23:19:23 UTC
Any progress being made on this?
Comment 4 A_Machils 2010-06-07 02:44:27 UTC
When I put this matter to Logitech Support, they answer back that it is a matter for Debian to fix and mark the ticket as 'solved'.... I'm not sure what Debian has to do with Logitech messing up their own repo. According to Logitech Support, the only supported downloads are on the website. This has been going on for weeks now and it's getting rediculous!
Comment 5 Marc Sherman 2010-06-07 04:52:20 UTC
This is fixed now -- it got fixed some time between the 21st and the 28th of may. I've had the source enabled in sources.list since the 28th, without a repeat failure.
Comment 6 Marc Sherman 2010-06-07 04:55:57 UTC
BTW, support initially tried to pull the same stunt with me, but I held my ground and explained that it was a problem with their corporate web site, not the software, and they re-opened my ticket. It's reasonable that the support drones wouldn't understand what this issue was about (they probably don't even know what debian is)....

What's unreasonable is that after claiming (incorrectly) the problem was fixed two times after I filed it, they then completely failed to contact me when it finally did get fixed -- I found out when, on the 28th, their ticket system went and automatically closed my ticket for inactivity (that's a nice way to keep your stats under control). I retested so that I could quote my test logs in my demand to re-open again, and lo and behold, the problem was resolved.
Comment 7 A_Machils 2010-06-07 05:45:35 UTC
# deb http://debian.slimdevices.com testing main is _not_ fixed yet. I got it working again by changing to deb http://debian-origin.slimdevices.com testing main.
At debian.slimdevices.com the package file says that "Version: 7.5.1~30779" is the latest, packages.gz says "Version: 7.5.1~30745", but the latest test version is squeezeboxserver_7.5.1~30844_all.deb on the site: http://debian.slimdevices.com/pool/main/s/squeezeboxserver
These inconsistencies make it impossible to update with the debian.slimdevices.com repo.
Comment 8 Marc Sherman 2010-06-07 05:53:17 UTC
Wow, you're right, it's still broken. I guess I got (un-)lucky that when I tested it, I randomly hit a consistent set of machines for the pacakges.gz file and the actual package upgrade, and it was a fairly recent build (30831), so since then I haven't hit a machine with a newer build on it, which means that my nightly run of apticron doesn't notice the problem and error out like it was before.

Thanks for the tip about debian-origin.
Comment 9 Chris Owens 2010-06-08 13:21:12 UTC
Matt, is this still your responsibility?  If not, do you know whose it is?  Thanks!
Comment 10 Michael Herger 2010-06-18 01:00:13 UTC
we fixed an issue with the CDN a few days ago. Do you still see this issue?
Comment 11 A_Machils 2010-06-18 02:08:40 UTC
(In reply to comment #10)
> we fixed an issue with the CDN a few days ago. Do you still see this issue?

Testing looks okay now, there is a 7.5.2-30889 package and this version is also stated in both the packages and in the packages.gz files!

Unstable seems to have a fault still: there is a 7.6.0-30890 package file to download, but in the packages and packages.gz file it says: 7.6.0-30918

This is for i386, I haven't checked x64!
Comment 12 A_Machils 2010-06-18 02:10:09 UTC
(In reply to comment #11)
> (In reply to comment #10)
> > we fixed an issue with the CDN a few days ago. Do you still see this issue?
> 
> Testing looks okay now, there is a 7.5.2-30889 package and this version is also
> stated in both the packages and in the packages.gz files!
> 
> Unstable seems to have a fault still: there is a 7.6.0-30890 package file to
> download, but in the packages and packages.gz file it says: 7.6.0-30918
> 
> This is for i386, I haven't checked x64!

Scrap the comment about Unstable, I just checked again, and now there is also version 30918 for download!
Comment 13 rmgmailbox-sqbox 2010-06-18 02:12:31 UTC
(In reply to comment #10)
> we fixed an issue with the CDN a few days ago. Do you still see this issue?

Tried testing and unstable repos today, both now work OK.  Thanks Michael
Comment 14 Bruce Miller 2010-06-26 17:28:14 UTC
As of 2010-06-26 0700 EDT (UTC -04), the testing repository has been broken for some days.

The relevant line from /etc/apt/sources.list is:
deb http://debian.slimdevices.com testing main

The following is from my conversation on the public support page:

********************

Hi bruce robert 

According to our Engineers the repositories should be working, as of June 18th. Could you comment on this bug and make them aware that it is not working?

https://bugs-archive.lyrion.org/show_bug.cgi?id=16107

Trevor F.
Squeezebox Technical Support Manager
 Customer (bruce robert miller)	06/26/2010 04:12 AM

********************

Update 2010-06-26 0700 EDT (UTC-04)

There continues to be a server-side problem with updating to the latest squeezeboxserver version:

Reading package lists... Done
Reading package lists... Done
Building dependency tree 
Reading state information... Done
Reading extended state information 
Initializing package states... Done
The following packages will be upgraded:
chromium-browser chromium-browser-inspector squeezeboxserver 
3 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 47.6MB of archives. After unpacking 16.4kB will be freed.
Do you want to continue? [Y/n/?] y
WARNING: untrusted versions of the following packages will be installed!

Untrusted packages could compromise your system's security.
You should only proceed with the installation if you are certain that
this is what you want to do.

squeezeboxserver 

Do you want to ignore this warning and proceed anyway?
To continue, enter "Yes"; to abort, enter "No": Yes
Writing extended state information... Done
Get:1 http://debian.slimdevices.com/ testing/main squeezeboxserver 7.5.2~30934 [33.7MB]
Get:2 http://ppa.launchpad.net/chromium-daily/ppa/ubuntu/ lucid/main chromium-browser-inspector 6.0.450.0~svn20100626r50920-0ubuntu1~ucd1~lucid [621kB]
Get:3 http://ppa.launchpad.net/chromium-daily/ppa/ubuntu/ lucid/main chromium-browser 6.0.450.0~svn20100626r50920-0ubuntu1~ucd1~lucid [13.3MB]
Fetched 47.6MB in 41s (1,136kB/s) 
(Reading database ... 201244 files and directories currently installed.)
Preparing to replace chromium-browser-inspector 6.0.450.0~svn20100625r50809-0ubuntu1~ucd2~lucid (using .../chromium-browser-inspector_6.0.450.0~svn20100626r50920-0ubuntu1~ucd1~lucid_all.deb) ...
Unpacking replacement chromium-browser-inspector ...
Preparing to replace chromium-browser 6.0.450.0~svn20100625r50809-0ubuntu1~ucd2~lucid (using .../chromium-browser_6.0.450.0~svn20100626r50920-0ubuntu1~ucd1~lucid_amd64.deb) ...
Unpacking replacement chromium-browser ...
Processing triggers for man-db ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Setting up chromium-browser-inspector (6.0.450.0~svn20100626r50920-0ubuntu1~ucd1~lucid) ...
Setting up chromium-browser (6.0.450.0~svn20100626r50920-0ubuntu1~ucd1~lucid) ...

E: Failed to fetch http://debian.slimdevices.com/pool/main/s/squeezeboxserver/squeezeboxserver_7.5.2~30934_all.deb: Size mismatch
Reading package lists... Done 
Building dependency tree 
Reading state information... Done
Reading extended state information 
Initializing package states... Done

Current status: 1 update [-2].

********************

 Customer (bruce robert miller)	06/25/2010 05:23 PM
There is a server-side problem with your latest testing version of squeezeboxserver. The error message has varied, but I have been unable to download the latest version for several days:

E: Failed to fetch http://debian.slimdevices.com/pool/main/s/squeezeboxserver/squeezeboxserver_7.5.2~30934_all.deb: The HTTP server sent an invalid Content-Range header [IP: 192.221.110.126 80]
Comment 15 A_Machils 2010-06-27 12:17:32 UTC
(In reply to comment #14)

> According to our Engineers the repositories should be working, as of June 
> 18th.
> Could you comment on this bug and make them aware that it is not working?

As far as I can tell the original problem which started this bug has been fixed and still is working properly. The error-message you're giving is also different from the original problem!
Comment 16 Adam Slim 2010-07-10 12:53:16 UTC
I usually get this:
W: Failed to fetch http://debian.slimdevices.com/pool/main/s/squeezeboxserver/squeezeboxserver_7.5.2~30934_all.deb
  Size mismatch

Although sometimes I get this:
W: Failed to fetch http://debian.slimdevices.com/pool/main/s/squeezeboxserver/squeezeboxserver_7.5.2~30934_all.deb
  The HTTP server sent an invalid Content-Range header [IP: 207.123.33.126 80]

While I agree it is a new bug, I am unsure of the protocol - should I open a new one?  Anyway, it needs fixing!
Comment 17 Jim McAtee 2010-07-10 13:07:23 UTC
Workaround:

Use the server at http://debian-origin.slimdevices.com.  This bypasses the content delivery network that has been broken since the day it was brought online.

Is a CDN necessary for the amount of traffic that this server gets?  If Logitech can't get this to work then just disable the DNS kludges being used to distribute the traffic among all the broken servers.
Comment 18 Chris Owens 2010-07-12 10:07:14 UTC
Adding Brandon to the cc list
Comment 19 Mickey Gee 2011-01-24 09:35:02 UTC
Please reopen if there are still issue.