@EliahKagan wow it got called 4 times? So complicated

@Zanna It's using dpkg in a lower-level way than most of would manually use it, using separate calls for each of the major steps of installing a deb package. Incidentally, it seems APT cannot be made to use busybox dpkg, which doesn't support options like --status-fd. I had to restore /usr/bin/dpkg by manually unpacking the downloaded .deb file for it with ar x (and then unpacking data.tar.xz with tar xf) and copying that specific file.

← 17 messages moved from Raiders of the Lost Downboat

@Zanna What problems did you have?

The path has to have a / in it to be recognized as such, so where dpkg -i foo.deb and gdebi foo.deb would work, you'd have to use apt install ./foo.deb.

@EliahKagan * most of us

@EliahKagan I can't remember exactly what happened, but I'm pretty sure I used the correct syntax

@EliahKagan in any case, I think I should rethink again

possibly after more practice

@Zanna I think in your use case with the recipes that it's reasonable to keep the testing recipes in the master branch. You might still branch for particular changes (though in your use case it may be reasonable to develop on master). I think this is like having a program with a whole bunch of official plugins that ship as part of it and are developed in the same repository, where plugins that are less stable are in a separate directory and not enabled by default but still shipped.

@Zanna Do you want to continue with that? If so, what's the current state of your local hello-world repository? Is master up to date with the remote repository?

(I think you were going to check if it was safe to delete the local short branch. If origin/short was merged into origin/master upstream through the GitHub interface, then even though you've already pruned origin/short locally, I think pulling or manually fetching and merging master may let you remove short with git branch -d. If not, then you'll want to examine the differences before using the scary -D option.)

@EliahKagan Hmm 🤔

@EliahKagan For example, I don't think the ability to install from a path to a .deb file is documented anywhere in the apt man page.

it's not? I think I read about that on AU

I didn't find it in the man pages when I checked earlier today. That doesn't mean it's not there, only that I don't think it's there.

(The weird self-reply--not that self-replies are weird in general, I mean just that one--is for continuity in case we end up moving the APT-specific parts of the conversation to the Island.)

the apt man page is short compared to the apt-get man page iirc

I checked that too.

@Zanna It occurred to me that you might be interested in CodinGame, which I learned about from a recent episode of .NET Rocks. It has Python, among other languages. (I was surprised to find that it has Bash!)

cool!

I'll check it out

I have tidied up my recipes directory

Cool.

Tidied in what way?

I wrote all the new files (emptying my mental list*) and merged all the branches and moved all the untested recipe files into TO-TEST (262 files!)

So now everything of interest is in master?

* I say mental list but it was obviously not actually only in my head which is too leaky for such purposes

@EliahKagan yes

everything is there

In that case, I guess you don't need to backport that individual file to master (since the branch that contained it was merged).

yeah

that would have been a good task

but it was bothering me that so many things needed doing

my a and d keys are barely working

It's good to be comfortable checking out individual files from another branch or commit than the one you're on, which would've probably been the best way to do that if the branch had to stay unmerged. You could just try that now if you want. But it's not done all that often. I'd be interested to move on to, and/or to continue, other things. But it's up to you.

I can't type properly

Does a reboot fix that or is it a hardware problem that's just gradually worsening?

Yeah, it's a hardware problem I think. Been getting worse for a while

If worse comes to worse, you could type mostly in lower-case and use upper case Q for a and A and upper-case E for d and D.

I mean for chat. That wouldn't just automatically work in the terminal. :)

hQhQhQ XE

:)

A while ago, I had two laptop keyboards (same laptop, same keyboard or so I thought when I bought the second one but now I'm not sure) where the W key become mostly unusable because it was the key I pressed (and often held) to walk or run forward in video games.

lol

Do you wanna deal with short in hello-world?

Also, did you end up setting up a remote for the recipes repo and, if not, do you wan to?

I want to set up a remote for it

Do you want to host it on GitHub?

I want to fix hello-world. I'll try that

@EliahKagan sure

Or do you want to learn how to host the remote yourself?

(Those are obviously not the only two options.)

Since it's a repo you use for actual stuff, I suggest hosting it however you want to for that stuff.

Repos can have multiple remotes so you're not really closing off any options.

@EliahKagan yeah!

I think making a bare repo on a machine of your own that you clone from and fetch/pull from and push to offers valuable insights.

But it might or might not be something you actually want to use for anything.

yes

I have a completely new RPi in its box with basic accessories

have not even assembled

idk if this is relevant XD

Oh nice. I think that's perfect for this. (Though you can also use your own machine. Your "remote" can even be another directory--the "URL" for a remote can just be a traditional Unix-style path if you really want.)

@EliahKagan I have fixed it and deleted the short branch without getting all uppercase

Would you want your remote accessible from the Internet? If so, you'll have to forward a port, which idk if your Internet connection supports but most do (or use something like UPnP to forward it automatically, which I don't know how to do for an SSH server, but it's possible, if your router or ISP supports it).

@Zanna Awesome!

it would be great if I could learn some networking stuff

@Zanna I'm glad you were able to do that while your d key was still working. :)

I never seem to find a way into it

@EliahKagan haha deleting branches could get tricky in future

@Zanna In that case, you might be unhappy to hear that running your own SSH server on which you have Git repositories does not require much sophisticated networking knowledge.

:)

it would still be progress for me haha

(If it's any use, here's my ISP's website)

You'll have to think about security. I mean, you already have to think about that, but I mean, you'll have to think about stuff like how anybody can connect to your SSH server and attempt to authenticate. So you need to keep it up to date, make sure all user accounts that can log in have good passwords and/or reconfigure sshd to allow only key-based authentication, that kind of stuff.

@Zanna I think I might have some trouble figuring out if you can forward ports, based on that website. You may be able to figure it out a lot easier.

Do you have a router?

@EliahKagan that's some stuff I'm interested in learning

@EliahKagan yes

Does your router have a web-based setup page that you can access through your local network?

You would access it by entering the IP address of your default gateway into the address bar.

yes

That's a good sign.

So, your router may have something for forwarding ports.

The person who did the installation showed me that

Also, there are some good resources on Super User about port forwarding. (We can still discuss it here, of course. I just want to link that.)

Actually I'll link...

haha great

@Zanna Showed you port forwarding in the router setup, or just showed you the setup page?

just showed me the setup page

Btw, idk how much you've done with remotes since we last worked with them here. But at that time, you'd only made changes to your repo through the GitHub interface. You'd fetched, and merged from a fetch, and done both by pulling (though under weird circumstances--you may want to try pulling when your branch exists and there's something unfetched to pull). But you hadn't actually pushed to a remote.

If you haven't tried pushing yet, I suggest learning about that before setting up your own bare repository and using it as a remote.

(Because when it comes to using remotes, pushing is one of the most essential operations.)

yes that was also on my mind

but now I'm thinking I need to do some essential things and go to sleep

I can't stop waking up at 5am lately

hopefully we can come back to this soon

Do you think you may want to continue this in the next twelve hours or so?

These days, I don't check Ask Ubuntu as much in the evening (where I am) as in the morning but I'd be pleased to check the chat tonight (where I am) if you think you may want to continue then.

← 6 messages moved from Raiders of the Lost Downboat

it is possible. I could try to make an early start on it :D

It's totally up to you. Note that I'm not promising or committing to being available, only predicting that I might be. You should not inconvenience yourself.

that's all good stuff

Btw, other things you could try without me (or with me) and that I recommend trying sometime soon-ish are:

(a) git mergetool to resolve merge conflicts using an external program (you can use your mergetool of choice, I suggest starting with meld)

(b) git difftool to display diffs with an external program (most mergetools are also difftools), and

(c) resolving a merge conflict between a local branch and its associated upstream (remote) branch that occurs when you run git pull or when you run git merge after running git fetch.

Also, you should try making a branch locally that doesn't exist on the remote and pushing it to the remote. After that, you might find it interesting to bring your short branch back from the dead, then push it to the remote, then try deleting it on the remote with git commands you run on your computer rather than through the GitHub interface.

There's other stuff I have in mind but this is lots of stuff so I'm going to stop saying stuff until later... or at least slow down. :)

> Unlike dpkg, apt-get does not understand .deb files, it works with the packages proper name and can only install .deb archives from a source specified in /etc/apt/sources.list.

What?

Is sudo apt-get install ./blabla.deb added recently?

@Kulfy More recently than that documentation, apparently.

> version 9.0, 17 November 2018

I should've said, more recently than that documentation was updated about it.

Though actually I don't know when apt-get and apt got that functionality. I've long used gdebi to install .deb files and still do.

I use dpkg :P

@Kulfy That's out of date in more ways than one. It claims that archives must be specified in /etc/apt/sources.list, but for quite some time they can also be specified in .list files in an /etc/apt/sources.list.d directory.

Braiam wrote 3 years back. May this is 3rd birthday of this functionality.

@EliahKagan Makes sense.

But it's not clear to me how APT actually works.