News for hackers. Stuff that matters.
Re:Deb.haskell.org Security Breach by eikenberry on Sunday February 15, 2015 @10:23PM (#9055165)
You can host a dep/apt repo as a static list of files in S3. Did that myself before using reprepro to generate it, then pushed it up to S3. Nothing fancy, but it worked fine. Not sure where you got the idea is was more complicated.

I've also done it using apt-ftparchive using a simple script. Very bare bones, but easy enough.

Was looking at trying aptly next time I needed one. It looked interesting.

https://packages.debian.org/jessie/reprepro

https://packages.debian.org/jessie/apt-utils

https://packages.debian.org/jessie/aptly

[edit to include all links]

Re:Deb.haskell.org Security Breach by tdicola on Sunday February 15, 2015 @10:26PM (#9055172)
Yeah the problem is getting to that point. Check out the docs on setting up an apt repo: https://wiki.debian.org/HowToSetupADebianRepository Good luck figuring out the easy way of using reprepro and S3 from that page.
Re:Deb.haskell.org Security Breach by geofft on Sunday February 15, 2015 @11:11PM (#9055262)
The sad part is it's even easier than that, if your goal is hosting like two packages. Stick a bunch of debs in a directory, make sure your default GPG key is reasonable, then run `apt-ftparchive packages . > Packages`, `apt-ftparchive release . > Release`, and `gpg -ab < Release > Release.gpg`. Then toss the whole thing on a web server that supports plain HTTP. Honestly I bet GitHub Pages is good enough.

The syntax for sources.list is then "deb http://path/to/your/directory ./". Users can pick up your key by piping it into "sudo apt-key add -", or they can "sudo apt-key adv --keyserver... --recv-key..." with the usual GPG options (and check the fingerprint the same way).

The problem is that most serious users will quickly want tooling to do things like keep track of which versions of which packages are in the archive, not have two versions of the same package, support multiple distros/releases, support separate "test" and "production" areas, etc. And that's where the complexity shows up. (Also why you never see "./" sources.list lines in real life.)

But for "Hey, I built these three packages", it's kind of perfect.

Re:Deb.haskell.org Security Breach by e12e on Sunday February 15, 2015 @11:36PM (#9055320)
Let me just remind everyone that wiki.debian.org is, well, a wiki. I'm on a mobile right now, so I trying to consolidate the apt/repo-pages, trimming the obviously (too) old information - and adding a more visible "this is how simple this stuff can be, even with proper gpg-signing, and http support" -- is a little too cumbersome. But I've for a while now been intending to help out a bit -- the wiki is somewhat neglected (compared to, say the excellent arch linux wiki). Mostly I think the Debian wiki is in need of some pretty mundane wiki clean-up: consolidation, simplification and modernization (consentrate on documenting current stable and testing).

But more impirtant than me actually doing that, is convincing all of you to update the wiki whenever you encounter errors or missing information! :-)

(No affilation with the Debian project other than being a long time user of Debian)

Re:Deb.haskell.org Security Breach by geofft on Sunday February 15, 2015 @11:46PM (#9055351)
I feel appropriately chastened now. :-) But that page is huge, and apt-ftparchive is in fact listed halfway down, but it's marked as deprecated two places. And the thought of doing general cleanup on that page (which it can use) is a bit more difficult than just adding some docs, as is the thought of arguing about just how deprecated is deprecated.

But I will try to make some changes to that page.

Re:Deb.haskell.org Security Breach by voltagex_ on Sunday February 15, 2015 @11:56PM (#9055374)
Tried to create an account on the wiki, got error 919 and a message to contact the debian-www mailing list. Just hoping the list isn't members only now.

If anyone wants to collaborate on fixing that apt page then my email is in my profile. It should only take about an hour to clean up.

Re:Deb.haskell.org Security Breach by e12e on Monday February 16, 2015 @01:17PM (#9058240)
I just signed up without any problems. Did you try again?
Re:Deb.haskell.org Security Breach by voltagex_ on Monday February 16, 2015 @09:19PM (#9060329)
Yeah, got a reply that indicated I'd been caught in a spam filter (at $EMPLOYER, behind a proxy). All sorted now
Re:Deb.haskell.org Security Breach by voltagex_ on Sunday February 15, 2015 @11:45PM (#9055347)
What do you mean by the GPG key being reasonable?
Re:Deb.haskell.org Security Breach by geofft on Monday February 16, 2015 @12:00AM (#9055384)
It should exist, and it should be the one you want to use to sign the archive. If not, make another keypair and ... figure out how the GPG command line works. :)
Re:Deb.haskell.org Security Breach by JoshTriplett on Sunday February 15, 2015 @11:58PM (#9055380)
Making sure "gpg" with no options does something sane and references the key you want it to reference.
Re:Deb.haskell.org Security Breach by eikenberry on Sunday February 15, 2015 @10:30PM (#9055183)
Point taken.
Re:Deb.haskell.org Security Breach by vacri on Sunday February 15, 2015 @11:26PM (#9055294)
Aptly is a dream to use compared to the others, generally makes sense, and is well documented. Big thumbs up for aptly from me.

I started out with a reprepro archive, which is an abandoned project (or at least, had been for a couple of years early last year (edit: looks like I am in error, there are commits dating to last august... I must have been looking at the wrong repo)). The biggest problem with reprepro is that you can have only one package version per package - so no rollbacks.

But yeah, though you need software to calculate the index files, once they're done, an apt archive is just a static website, easily pushable to s3. Of course, if you want a private repo, it gets a bit more difficult...