apt-get does not find the uploaded deb package about deb-s3

[pccowboy]

@krobertson bumping @sodabrew 's question, is this closable?

[krobertson]

What is the output of apt-get update? Sometimes it won't error, but it will print that it is ignoring a repository for a reason.

Also, just to confirm, you're on a 32bit machine and not a 64bit? The release file only has i386and not amd64.

[joscarsson]

First of all thanks for a great repo! I was so happy when I found it, it was exactly what I was looking for! Also, thanks a lot for answering on this issue!

Below is the output you asked for:

pi@homeki:~$ sudo apt-get update
[sudo] password for pi: 
Get:1 http://mirrordirector.raspbian.org wheezy Release.gpg [490 B]
Get:2 http://mirrordirector.raspbian.org wheezy Release [14.4 kB]                                            
Hit http://archive.raspberrypi.org wheezy Release.gpg                                                                     
Hit http://archive.raspberrypi.org wheezy Release                                                                         
Hit http://repository.homeki.com unstable Release.gpg                          
Hit http://repository.homeki.com unstable Release                              
Get:3 http://mirrordirector.raspbian.org wheezy/main Sources [6,071 kB]
Hit http://archive.raspberrypi.org wheezy/main armhf Packages                  
Ign http://archive.raspberrypi.org wheezy/main Translation-en_US               
Ign http://archive.raspberrypi.org wheezy/main Translation-en
Hit http://repository.homeki.com unstable/main armhf Packages
Ign http://repository.homeki.com unstable/main Translation-en_US
Ign http://repository.homeki.com unstable/main Translation-en
Get:4 http://mirrordirector.raspbian.org wheezy/main armhf Packages [6,891 kB]
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en_US                                                                                         
Ign http://mirrordirector.raspbian.org wheezy/main Translation-en                                                                                            
Fetched 13.0 MB in 1min 3s (204 kB/s)                                                                                                                        
Reading package lists... Done

From the output above it does say Hit for repository.homeki.com, but nothing is downloaded as I have already ran apt-get update and I haven't changed the repository (I think that's why anyway).

I am on a armhf machine (Raspberry Pi), but I have also tried from a amd64 machine. Where do you only see i386? In the Release file I posted it says Architectures: all amd64 i386 armhf. Are you looking somewhere else?

(The repo is also publicly available in case you want to look at a specific file/try it youself)

[joscarsson]

@krobertson: I think I know what the issue is. I compared with the old repository I used, and the difference I see is that for the old repository packages uploaded to the all architecture have its metadata available in Packages not only in the binary-all directory, but also in each arch-specific directory binary-amd64, binary-armhf, etc.

So in my case, the metadata for homeki should not only be present in http://repository.homeki.com/packages/dists/unstable/main/binary-all/Packages (which it is), but also in http://repository.homeki.com/packages/dists/unstable/main/binary-armhf/Packages and in http://repository.homeki.com/packages/dists/unstable/main/binary-amd64/Packages, etc.

I'm not sure if this is the correct behaviour, but this was how my old repository worked. As my armhf debian will only look at the http://repository.homeki.com/packages/dists/unstable/main/binary-armhf/Packages it will not find the all package.

Do you know if this might be an issue in deb-s3, or if it is something wrong on the apt-get "clients"?

[joscarsson]

@krobertson My issue above is fixed in b5efb34, but it seems that is not released yet (I don't get that fix if I use Gemfile with gem 'deb-s3', '~> 0.6.2'. Could you please release a new version?

[sodabrew]

deb-s3 versions 0.7.0 and higher include the noted fix commit. Can the issue be closed?

[joscarsson]

@sodabrew @pccowboy: I think this can be closed, yes. Thanks!