@Biswapriyo That depends if you want to write actual graphical applications usable by an end user, or you just want to play around with programming and have graphical feedback.
@Biswapriyo The easiest (and probably the most fun) way to draw triangles, lines, shapes, etc., is with the Python "turtle" module.
@FaheemMitha I'm curious; why do you recommend Mercurial over Git?
if I have x.com and y.com, with two different applications running on port 443, can I host them from the same server?
simply pointing x/y.com to server and opening the applications on the same port won't work, because the applications can't both use the same port on the local machine
I'm sure this is possible, but not sure how
maybe a 3rd application running on 443 that looks at the address the clients are connected to, and acts as a proxy to other ports that those applications are running on? Can nginx or similar do that?
@towc This chat isn't a suitable place to dump random questions. You should ask questions on the site. If you've asked a question somewhere else, you could link to it.
Documentation
provides syntax to install specific version of docker-ce:
$ sudo apt-get install docker-ce=<VERSION_STRING> docker-ce-cli=<VERSION_STRING> containerd.io
On same lines, below dockerfile uses the above syntax:
FROM jenkins/jenkins:lts
ENV DEBIAN_FRONTEND=noninteractive
USER roo...
@overexchange if I'm understanding everything correctly, it's an Ubuntu issue, so is best asked at ... Ask Ubuntu. I'm not entirely sure I understand the actual problem -- whether that's a docker-specific error, or Ubuntu/apt error.
Documentation
provides syntax to install specific version of docker-ce:
$ sudo apt-get install docker-ce=<VERSION_STRING> docker-ce-cli=<VERSION_STRING> containerd.io
On same lines, below dockerfile uses the above syntax:
FROM jenkins/jenkins:lts
ENV DEBIAN_FRONTEND=noninteractive
USER r...
Below is the relevant snippet from jenkins image(2.190.2 version):
FROM jenkins/jenkins:lts
#......
# ......
# Add jenkins plugin
COPY plugins.txt /usr/share/jenkins/plugins.txt
RUN /usr/local/bin/plugins.sh /usr/share/jenkins/plugins.txt
where plugins.txt is:
git:latest
git-client:latest
...
@FaheemMitha reading up on comparisons between them. How accurate is this description re Mercurial? (It's accurate about the Git part.)
> I believe this is where mercurial has gone wrong. A head in mercurial is inferred... it's just a point on the DAG where there are no children. A branch is inferred to be inactive when it's not a head.
@Wildcard Very out of date. Mercurial has (at least) 4 different notions of branch. At least one of them didn't exist in 2008.
I haven't read the linked article yet.
From a technical POV Mercurial and Git are quite similar, I think. Though Mercurial is clearly out in front in terms of usability (in part because of Evolve), and is probably also more flexible (in part because of Python).
Git is slightly faster for most common operations, I think. They shoving Rust into the picture to reduce startup times and other things. Not sure how I feel about that.
Not sure what he means by that. History in both Git and Mercurial is a DAG. That aspect is virtually identical.
Though Mercurial provides local integral revision numbers. Which I personally like. I think it's a nice feature and miss it when I'm trying to use Git.
@FaheemMitha the article mentioned that. I'll take it with a grain of salt since it's such an old article, but:
> In both git and mercurial, the history is just a directed acyclic graph, but mercurial attempts to provide a linear history and this has a negative effect in a few places. For one, the rev number is displayed a lot and people try to use it, but it varies from repo to repo and probably does little more than cause confusion.
@JeffSchaller I actually have developed a training for Git. Delivered it at several different conferences, after refining it at meetups. If/when you ever decide to learn Git, let me know. :)
To a first approximation, Git and Mercurial are very similar in how they present themselves. They're both DVCS projects, started at approximately the same time, drawing inspiration from the same prior work, notably Monotone, and both founded by kernel people.
@FaheemMitha I'm thinking I probably should spend some time using Mercurial, just for the experience of it. But I'm surprised you find that section unclear. Do you know what a DAG is? Do you understand how it relates to version control history?
> git will show you from a particular point all of the changesets that led up to it by following the history backwards, but otherwise it represents what happens in the real world. From a given point, there's a change. That change may be desirable or may not be. It may have been at one point, but isn't any longer. The only thing that matters is a head.
I admit I haven't really used Git much, but I don't know what he means here.
> And I believe this is where mercurial has gone wrong. A head in mercurial is inferred... it's just a point on the DAG where there are no children. A branch is inferred to be inactive when it's not a head.
You can ask Mercurial where the heads are. Or just look at the graph. He he means heads can be topological, but presumably that's the same with Git too.
So when you run, for example, git log --graph --all, Git looks at all the heads to find the commit objects they reference, and then looks up the parents for those commits, etc.
@FaheemMitha the keynote is that in Git, you can create a branch starting from any arbitrary point in the history. Because a "branch" is really just a "branch head" or "head", and creating one only requires writing 40 bytes to a single file. It doesn't affect any other head. Which means that you could start from a cset that currently doesn't have children, and make more csets, and still leave some branch right where it was.
Finally, what I did is to manually type from scratch everything in this command and it worked.
Hence, it must have been some hidden characters that I was carrying with (and I could not see) - initially I was copy-pasting this command from a file instead of typing it manually.
P.S. Guys I was ex...
@terdon I'm probably not innocent in the matter, I often read my comments and think they are hostile even though I didn't originally intend them to be that way, although as soon as OP is asked for clarification on something and refuses to provide it I actually become hostile
So many people in the comments though were asking about/suggesting that there may be something wrong with the path and then OP answers their own question saying they figured it out and we were all of no help. Kind of ticked me off lol
@Jesse_b actually, they didn't figure it out, either. They just did something else that worked and then assumed that they now know why the other approach didn't work. They didn't bother to find out if their assumption is correct. Poor troubleshooting skills.
so anybody copying the command from their question couldn't see it
@Wildcard well, they said in their "answer" that re-typing it made it work. But the comments were full of people asking for a reproducible example, but if it was indeed a non-breaking space, they couldn't have provided one even if they tried to.
How they would have originally got that nbsp, that I don't know. I still have it in alt+space, so I sometimes get one after typing a | (because also behind alt)
@Wildcard a non-breaking space between the two paths, yes. then it would actually be just one path, not the two that scp expects. Additional regular spaces would just cause it to see more than two paths, but that wouldn't be an error since it can have more than one source file
Documentation
provides syntax to install specific version of docker-ce:
$ sudo apt-get install docker-ce=<VERSION_STRING> docker-ce-cli=<VERSION_STRING> containerd.io
On same lines, below dockerfile uses the above syntax:
FROM jenkins/jenkins:lts
ENV DEBIAN_FRONTEND=noninteractive
USER roo...
