| socomm | when running 'apt-get update I get " STDERR: W: Failed to fetch http://ppa.launchpad.net/ondrej/php5-5.6/ubuntu/dists/trusty/main/binary-amd64/Packages 404 Not Found | 02:41 |
|---|---|---|
| socomm | when I visit the url it appears as if it is indeed 404, any ideas how to resolve this? | 02:41 |
| cjwatson | socomm: PPAs are generally maintained by their owner (in this case https://launchpad.net/~ondrej), not by us | 02:43 |
| cjwatson | Looking at that I guess perhaps https://launchpad.net/~ondrej/+archive/ubuntu/php might be of some use, but I don't really know | 02:44 |
| socomm | cjwatson: thank you | 02:45 |
| teward | socomm: that PPA you are looking at i think was replaced, by the one cjwatson points at, but you may need some package reinstalls. | 02:46 |
| socomm | teward: ah gotcha, thank you | 02:47 |
| teward | (I keep a bit of an eye on the PHP PPA every once in a while lol) | 02:48 |
| === chihchun_afk is now known as chihchun | ||
| === PaulW2U_ is now known as PaulW2U | ||
| === maclin1 is now known as maclin | ||
| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| iliv | hi cjwatson. last time we chatted you said I should be using git refs in order to import code for several program versions all located in one git repo. so, I looked around and read up on git refs (not a git expert) and I am wondering which ref type you meant exactly. those are ranging from heads to remotes to tags. | 15:58 |
| cjwatson | iliv: heads | 16:00 |
| cjwatson | iliv: or just "branches" colloquially (which I maybe should have said in the first place) | 16:01 |
| iliv | thought so (it is explicitly mentioned in notes under Repo URL field) | 16:02 |
| iliv | okay | 16:02 |
| iliv | so if I have multiple versions of the same app in one repo each version has to be in its own branch | 16:02 |
| iliv | hmm | 16:02 |
| cjwatson | yes | 16:03 |
| iliv | is this the only way to do it? | 16:04 |
| iliv | oh, and it only applies to bazaar | 16:06 |
| cjwatson | given that snapcraft only looks at snapcraft.yaml and doesn't take an option to look at a different file, it's not clear how we would do otherwise really | 16:07 |
| cjwatson | and I'm not sure what you mean by "and it only applies to bazaar" | 16:07 |
| iliv | I'm reading this: "For imports to Bazaar, the HEAD branch will be imported by default, but you can import different branches by appending ',branch=$name' to the URL. For imports to Git, the entire repository will be imported." | 16:11 |
| cjwatson | imports are a red herring | 16:11 |
| cjwatson | the exact same properties about branches vs. snapcraft would hold if you were pushing your git repository directly to Launchpad rather than going through code imports | 16:11 |
| cjwatson | the description you quote from our UI is about how git and bzr are mapped to each other, but doesn't really have any bearing on how either one interacts with building snaps | 16:12 |
| cjwatson | different stages of the process | 16:12 |
| === chihchun is now known as chihchun_afk | ||
| === JanC_ is now known as JanC | ||
| cjwatson | iliv: the source URL for your postgresql-snap git-to-git import should literally just be "https://github.com/iliv/postgresql-snap" | 18:01 |
| cjwatson | forget all the ,branch= stuff for an import that targets git | 18:01 |
| cjwatson | iliv: and definitely don't include /tree/blah on the end | 18:01 |
| iliv | I think I tried that first. It didn't work then, it doesn't work now :) I gather because of what you said about branches above. If it's git-to-git a remote git repo is expected to host just one app (snapcraft.yaml), right? | 18:10 |
| cjwatson | No | 18:10 |
| iliv | And if it's multiple snapcraft.yaml files, as is true in my case, it has to be git-to-bzr | 18:10 |
| cjwatson | Please try it again and then leave it there so I can look at it | 18:10 |
| cjwatson | No, that's entirely wrong, sorry | 18:10 |
| iliv | oh boy | 18:11 |
| iliv | okay | 18:11 |
| cjwatson | I've obviously confused you in some way | 18:11 |
| cjwatson | It has to be multiple branches, yes, but those multiple branches can reside within a single git repository | 18:11 |
| cjwatson | And there is no reason why going via bzr would help matters | 18:11 |
| iliv | it worked this time (as you pointed out it should be set up) | 18:11 |
| iliv | perhaps I did it differently, after all | 18:12 |
| cjwatson | right, so that import is fine, and you can create a snap from either https://code.launchpad.net/~commandpromptinc/postgresql-93/+git/9.3.14/+ref/master or https://code.launchpad.net/~commandpromptinc/postgresql-93/+git/9.3.14/+ref/9.3.14 | 18:12 |
| cjwatson | though it's oddly named, I'd have called the repository "postgresql-snap" rather than "9.3.14" to match the github repository name | 18:13 |
| cjwatson | we need some better defaults here | 18:13 |
| iliv | I'm just figuring out how this thing works | 18:13 |
| iliv | I'll make sure it is more meaningful when I get a handle on the entire process | 18:14 |
| === chrisccoulson_ is now known as chrisccoulson | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!