dave-mccraw / emon-repo Goto Github PK

Based on the discussion here and I guess FAO @TrystanLea

We should ideally not instruct users to connect directly to my AWS bucket (although I have no problem with this), as it means we'll have to get them all to change their apt.sources path if we want to change from http://emon-repo.s3.amazonaws.com to something else (i.e. to host the repo as part of the project itself, or to mirror it).

Instead, perhaps a subdomain such as apt.openenergymonitor.org could be set up to forward to http://emon-repo.s3.amazonaws.com, that way we can just change the forwarding to update the location of the physical repo?

We really need some kind of script associated with this repo which takes a .deb and makes sure it's available for each distro the repo is configured to serve. If not, it's too easy to forget and push a new version to wheezy only (I think it will then have removed the package from all other distros, leaving nothing in its place).

Hey Dave
Haven't you on the forum or emonhub much so I assume you're busy elsewhere.

There's a post on forum by a new user trying to use apt-get on a amd64 in Debian7 wheezy., I'd like to help the guy out in your absence but think it's a repo issue rather than something he is doing.

At the repo the amd64 file sizes all look pretty small and only the log4php deb ends "_all.deb" all of the emon* debs end "armhf.deb"

Did the support for non-Pi platforms get dropped intentionally pending some changes or something ? or is it meant to be available?

I see the emon-repo README.md also states "armhf.deb" in the reprepro command.

If it does just need redoing with "_all.deb" and you are busy would it help if I attempt to follow your readme and submit a pull request here?

Paul