How to format a link in /etc/apt/sources.list
Example, here is what I would like to include in my sources.list file:
http://ports.ubuntu.com/dists/saucy/main/binary-armhf/Packages.gz I'm not sure how this needs to be broken up when putting in the sources.list file. Here's one way I tried, out of several: Code:
deb http://ports.ubuntu.com/dists/ saucy/main/binary-armhf Packages.gz Also I just tried the above link, in the browser, and I get a 404 error, even though the file is there. You can click on it and download it manually. The link works up to this point: http://ports.ubuntu.com/dists/saucy/main/binary-armhf/ Thanks! |
You don't say what version of Ubuntu you are using but assuming it is 13.10 the link below will show you what the sources.list file should look like and several ways to add more repos.
http://ubuntuguide.org/wiki/Ubuntu:S...a_Repositories You should keep in mind that if you intend to do a version upgrade in the future any additional repos will complicate that version upgrade and greatly increase the possiblilty of failure. Start reading where the link opens and you will know more about things. The sample list is further down. The "apt-add-repository" command is probably the best way to do it but direct editing should work too. |
Super, thank you! Yes, I have managed to upgrade to Ubuntu 13.10 . I'll try using just the official sources.
Here is a summary of the state of the OS at this point: Code:
~$ lsb_release -a Some progress ------------- The sources list now looks like this (all the previous attempts commented out): Code:
$ cat sources.list Code:
Need to get 27.3 MB of archives. Code:
$ lsb_release -a |
One thing you should know is that there is no Ubuntu 13.1. That would be, under Ubuntu numbering procol, a version number that is not possible.
Ubuntu is released in April and October; months 04 and 10. So you have, released in 2013; 13.04 and 13.10. That is interesting output for that command. But without some notion of what your hardware is, what you version upgraded from there is no way to determine that something is wrong. Output for. Code:
$ uname -a Code:
$ apt-cache stats LSB is not well implemented, as far as I know, in any distro so I am not sure that any statement on the condition of your system will be accurately reflected by that command. Note also that Ubuntu gets packages from many sources and modifies them for their repos. While they, in theory, base non LTS versions on Debian Sid many packages may come from elsewhere. This will cause some confusion. This is a snippet from the end of the man page for lsb_release under my Sid install here; Quote:
|
Hi widget, I still need to re-read your post, but in the meantime, here is the output from the two commands:
Code:
$ uname -a You mention to very carefully the sources.list and make sure it is correct before adding or removing repos. I have to admit that the only measure I know of, at the moment, is if update and upgrade work without errors. I have also read that it's dangerous to just change the entries, it could break your system, but so far I have been lucky (apparently). I have just spent the last couple of days putting in trial and error entries. The distribution that was installed originally was Linaro lubuntu-desktop-nand.img. Here is a backup copy of the original sources.list: Code:
$ cat sources.list.old |
The standard command for a version upgrade, which is what gui applications invoke with scripts and you can invoke on the cli for Debian based (APT using distros);
Code:
sed -i 's/squeeze/wheezy/g' /etc/apt/sources.list && apt-get update && apt-get dist-upgrade The spaces all indicate a change in instruction. So you have the tool to be invoked, what you want it to do (edit in place), what text you want edited, what file you want edited. && indicates the end of that command and the start of another to also be carried out. That really is how the process works. People do not understand the package management system and gui tools feed this ignorance. I have nothing against gui tools, at least ones that are dependable, at all. I am a gui kind of guy myself. But calling something an Udate Manager is extremely misleading. Your sources.list is the heart of this system. It tells the system what repos to connect to. When you run "apt-get update" this updates your available package list. This is a list of all packages in all repos enabled in the sources.list. This is an update. When you run "apt-get upgrade" dpkg (the backend and actual package management work horse) compares the package list with the packages installed on your system. Where the package list has packages with a newer version than the one installed they are marked for being upgraded. Sometimes packages will be "held back" this is becuase to upgrade them there needs to be some package or packages removed and/or added. Added is more likely. These are new depends almost always. To upgrade the held back packages your use "apt-get dist-upgrade". This is because you are changing your distribution. You are changing it by adding or removing packages. This has nothing to do with version upgrades. The upgrade and dist-upgrade commands are what give you an up to date system. This is a package upgrade, not an update. One way to do a version upgrade is to manually edit your sources.list to point to the new version. Then run apt-get update to get the new package list. Then run apt-get upgrade to fine how many hundreds of packages can be upgraded and how many need removed and how many are held back for a future dist-upgrade command. The combined command I started this with just edits the sources.list, gets the new package list, and runs dist-upgrade. I prefer to run upgrade and watch it for errors before doing the remaining packages simply because it limits the number of packages to check for errors. Most gui text editors like pluma, gedit and kate have a function that will search for text and also one that will search for and replace text. The last basically invoking sed. But you can do it in the text editor very easily. This is a much better option than doing it manually yourself. It will be more reliable in maintaining any white spaces that are so very important. There are other scripts used in Update Mangler when doing a version upgrade. If you use the option to watch terminal output (a small window opens on top of UM when you do this and shows roughly what is going on) you will see "cleaning up" or something close to that at the end which sits there a long time. This is running, several times, some dpkg commands to configure reluctant packages and broken packages. While this is a handy tool having scripts make desissions for your system is probably not the best idea in the world. Particularly on "strange" hardware. What is this cubieboard2 thing? |
Good morning widget, thanks for the detailed explanation. Duly cut and pasted into my notes.
I did wonder about the 'held back' packages. I don't think I have those any more, but at one point I did. Here is something else that gave me intermittent trouble with 'duplicate sources' errors during apt-get update. This file: /var/lib/apt/lists/ Had no choice but to erase everything inside (sudo rm -r *). It fixed the 'duplicate entry' errors, and it was also updated with new information on the next cycle of apt-get update/install. Don't know if this is ok/safe to do. Finally, here is a nice source of information about other files that could be involved in storing repository information: http://en.wikipedia.org/wiki/Advanced_Packaging_Tool Section on 'Configuration and files'. I had some in /etc/apt/sources.list.d/ as well, which I backed up somewhere else (now I can't find them!). --- Here is a link to the manufacturer's cubieboard2 page: http://linux-sunxi.org/Cubietech_Cubieboard2 When you get the board it has 4gb of nand memory, split up into 3 sections: Code:
$ cat /proc/partitions Code:
$ sudo mount /dev/nanda /mnt/tmp Code:
$ cat /mnt/tmp/uEnv.txt It looks to me like it just has a minimal Linux system on nanda, then the boot process moves to /dev/sda1. Apparently it doesn't care what OS you have, and changing the Linux distribution (on /dev/sda1) does not seem to mess with the original hardware drivers. PS Last night I was able to upgrade from 13.10 to 14.10, this time very easily with just a distribution upgrade command. Many things need a tweak though: mplayer, vncserver and possibly other things. A lot of the very light applications, from Lubuntu are now orphans and need to be replaced. Thanks again. |
I don't quite understand why you would need to remove the lists in /var/lib/apt/lists. Have heard of folks doing it before though.
If you run into that problem again, before going to that solution, try; Code:
# dpkg --clear-avail Duplicate sources should always be found in the sources.list or sources.list.d. Once those are fixed and you run "apt-get update" the problem should, in theory anyway, be fixed. That sources.list.d is a handy place because you can actually have some repos that are duplicates of those in sources.list without getting that error. There is an application; apt-spy that will search for fast mirrors if you have some slow connections. It will pick the fastest and install it in sources.list.d. All repos enabled there and in sources.list will be checked. If you watch the output when upgrading you will see some repos will be from one and others from the other address. Kind of interesting to watch. Just goes with the first one to respond. I hope you went from 13.10 to 14.04 rather than 14.10. If it was 14.10 you got lucky. You can do LTS to LTS because this is set up before the next LTS even comes out with some packages added to the old one and so forth to help build the upgraded system. On the "regular" releases this is not done. They are based on Sid which is Debian unstable and jumping a release is just asking for problems. Looks like an interesting piece of hardware. Don't have too much fun. What the hell, have too much fun. If that is even possible. I might look into one of those mini board deals someday. To much on my plate with wanting to build a home server that I can't afford right now without just buying things to have fun on. Thanks for the link. Is one I have not looked at before. Getting to be a lot of them. I can think of some interesting things to do with them too. |
Hi widget, all I can say about /var/lib/apt/lists is that sudo-apt update was complaining about duplicates. After clearing out that folder 'update' quit complaining. Beyond that I know nothing at the moment, although I suspect this:
Adding repositories to /etc/apt/sources.list changes the information in /var/lib/apt/lists. Removing repositories from /etc/apt/sources.list does not undo the changes in /var/lib/apt/lists dpkg --clear-avail Sounded a bit dangerous, but wanted to try it with a safety net. A few weeks ago I started learning git, so I put it to use here: In root directory /$ sudo git init /$ sudo git add /var/lib/apt /$ sudo git add /etc/apt /$ sudo git commit -m 'initial apt commit' /$ sudo dpkg --clear-avail /$ git status ... nothing happened. I may be using git wrong, but all apt files seem to be unchanged. About the switch to 14.10 instead of 14.04, I can't remember what the selections were, if any, after the dist-upgrade command (from saucy). I've since read that 14.04 seems to be preferred and it's also going to be supported for longer. It may have been that there were no 'armf' versions of 14.04. Haven't checked yet. These little boards are great for getting started in Linux. In hindsight, I can see why the official Linux images are a bit behind relative to mainstream os releases. They are small, fast and everything (sort of) works. Just an example: On the original Linaro/quantal release for this board, the root directory was around 2 gig. Mplayer worked great, although can't remember if I had to add it myself. 14.10 Is using over 6 gig. Had to throw out mplayer, it just didn't work. Currently using vlc player, which only kind of works: if you resize to full screen cpu usage goes to over 100% from around 60%, switching back to non full screen doesn't reduce cpu usage to what it was. Only solution is to shut it down and restart. The original small and simple mplayer used 30-40% cpu and you could resize it any way you wanted without trouble. It's possible I have something messed up with my desktop setup. Lots of things to explore, but I do miss the simple LUbuntu/quantal and may go back to it. |
The changes in the sources.list should change the content of /var/lib/apt/lists. This seems to be a problem more with Ubuntu than with Debian and other Debian based distros. Have no idea why. There were several fellow Ubuntu testers that had this problem but I never did.
You, may, on your desktop want to give some other distros a whack. While most stable versions are "behind" what is available you need to also consider that what is available, even if released as "stable" will be more buggy. This is simply a product of development being done in virtual environments with no direct interaction with the hardware and then being exposed to the chaos of diverse hardware. Some of it will need fine tuned to actually work well. Canonical bases, roughly, their normal (non LTS) versions on Debian unstable (always Sid) and the LTS versions on Debian testing (currently Jessie). They have a different definition of "stable" a term which is extremely subjective. I quit using Ubuntu for other reasons than stability. But I can say that, at least in my opinion and on my hardware, Debian Sid is more reliable than Ubuntu. It is not stable but it is pretty close to the leading edge of what is being released. This is not quite as true right now as testing is in freeze and all packages headed for testing start in Sid and then migrate to testing. As the package major version numbers are frozen and basically all that is being done is bug work there is nothing new coming in. I wanted to check out the new LibreOffice, the 4.4 version, because there are some significant changes. This is not available in the repos, and not liking to go outside the repos I got it from the Debian experimental repo. It is not quite the version that the LibreOffice folks have out as a beta but is very close. I have a couple throw away installs VictimT (testing) and VictimS (Sid) on which I make sure that package upgrades don't break my installs before running them on the installs I actually use. And where I will install non native and experimental repo packages. One package that is no longer, Ubuntu 8.04 was the last to have it, in Ubuntu is apt-listbugs. This is a handy tool. It checks for bugs filed against a package and lists them for you when you attempt to upgrade to the buggy version or install the buggy version. Some people don't like it because it does list all bugs filed on the package. The architecture that is effected my be what you are using on your cubieboard and have nothing at all to do with my desktop with AMD 6 core cpu. A bug may be reported by one person with a very custom setup and effect no one else at all. But it does let you know the bug is filed, gives the number so you can check it out. It is still very possible that you are the lucky person to discover a bug, prehaps a system breaking bug. None the less I really think it is a great tool that Canonical should have kept. Debian based systems seem to work well on the miniboards. You may want to check out Sid on your desktop and see if you want to give that a whack. The way I install is using a netinstall or netboot image and not use it to install everything with meta packages. I finish the installs after configuring APT to not install recommends automatically and editing the sources.list to be exactly what I want. Most people using testing and Sid use the netinstall image for what ever Debian version is stable and upgrade it, with no additions to the very base install, to the version they want to use before finishing the install. Your board really wants a pretty special customized system and this would be the way to go. Ubuntu does have a netinstall image too so you may want to look into that. One thing Ubuntu has, in all images including server editions, is a package called ubuntu-minimal. This meta package calls in all sorts of depends to make the release really Ubuntu. Some of them, to a lot of us, make little sense. Plymouth may be one of your favorite packages but is it really sensible to install it on a server? Should the package mountall depend on plymouth? Plymouth is available in the Debian repos but mountall most surely doesn't depend on it. So simply by using Ubuntu you get a larger system, with no ability to change that easily, than with some other distro that is not Ubuntu based (respins of respins make no sense to me at all). I would think that on small factor hardware this would be something of a concern even with the addition of a hard drive. I run boinc (distributed computing application) on here and have it set to use 85% of my cpu power. On this box I don't even notice any performance change between running or not running it. But I have a pretty good sized cpu. Your VLC/mplayer problem is interesting to say the least. You may want to check into something based on libxine like gxine or xine-console. I haven't used them but xine-console is run from the cli and may not use nearly the resources. I think it should support most file formats. |
Hi widget, your detailed posts are very much appreciated.
Funny you should mention giving something else a whack. This morning I installed 'Cubier mini 20140305'. From the read-me file: Quote:
Some quirks: Typing in Code:
$ exec openbox-session When the monitor goes to sleep, it will not wake up again. Moving the mouse generates several lines of "<something> requests probe deferral.." . Can't be more specific at the moment because the monitor has gone to sleep. Anyways, if I don't get the desktop system running soon, I'll give this one a try: Debieez v1.01 Debian Wheezie kernel 3.4.79 Release date : Around 2014-02 Features Lightdm, LXDE Linux-3.4 Kernel But, I seem to notice things when replying to your posts, this says exactly what's needed: Lightdm, LXDE . I tried LXDE last night, on Ubuntu 14.10, and didn't like it much. Pause a bit while I download lightdm and try again... This is taking a while sorry.. will get back in a bit. Thanks again! |
You have commands that are for the firmware on the board and I am not in the least familiar with them. So I am can't be much help there.
OB is pretty nice once you learn to use it. I have used Lxde which is built on OB and find that, for me, OB is actually easier and more convenient to to use. Pretty good sized learning curve though which would be a lot easier on a regular box. Takes some time to learn what tools you want installed and so forth. I don't use sudo. Don't like the way it is configured by default at all. This was not what it was designed for. Someday I am going to learn to configure it in a more appropriate manner but until then I am really happy with it not being on my installs at all. Looked at the image you are thinking of using. Should be pretty good. Wheezy is boringly reliable on a desktop or laptop. Hopefully this carries over. You will find the sources.list a bit simpler than the one used by Ubuntu. You may be shocked. You have to have all of 3 lines enabled. It is a wee tad easier to administer. Even in mine where I have the Code:
## debian multimedia Handbrake is only available through that repo and there are a couple of VLC packages also. Used to be you had to get a lot of packages from there but the legal and code issues are rapidly deminishing. Not needed for most uses. The flash from there is needed on this box to get BBC videos to play in mozilla based browsers (flashplayer-mozilla). I had to look that up in my /mnt directory where Wheezy is mounted so I can keep it up to date in chroot rather than actually go there and do the update/upgrade cycles. Have it and Squeeze installed on here. They don't get visited much. Main purpose is for use when I need better security setup than I use on Sid or testing or if I actually suceed in breaking both testing and Sid production installs. Had to use Squeeze for a whole week once in the Wheezy-testing cycle. Real bummer. This Jessie cycle I have suceeded in forgetting the passwords to both Sqeeze and Wheezy. Had to chroot in and change the buggers. Been tryiing to log in more often to avoid that embarrassment. |
Hi widget, I'm still at it!
By some Linux magic, at least in this case, the hardware does not seem to matter at all. I'm just following the generic Linux instruction I find online. I'm sure later on there will be a few things that do not quite work, for example, is Wheezy using both A20 processors, or is any video hardware acceleration being used.. I don't know at the moment. SSH Works, the hard drive still works, HDMI output works. I stuck with base debian 7.4, and have downloaded almost all the software I need. Not present yet is a browser, and LaTex. Watching the BBC sounds good, I'd like that as well. So far the most challenging package to find has been a decent pdf viewer. Went for the lightweight, stable ones but they are just a bit to crude: xpdf, gv. I am currently downloading okular. It's a bit big, but hopefully it's nicer. Gnome mplayer is working way better. There is still a resizing problem though. Maybe that could be a hardware problem? As you resize it, the video remains the same size, but it makes copies of itself and stacks them on top of each other, staggered in the direction you are growing the window. If you leave it alone it works fine. Okular has finished downloading, and it looks much better. Don't have a pdf file handy at the moment though. Here is my sources list: Quote:
Had to look up what Handbrake and SID are. Doesn't sound exactly like video editing, but that's what came to mind. Last time I tried to edit a video it was maybe 7 years ago on Windows xp. It seemed like a fun thing to try, but turned out not to be. Maybe I should try it again on Linux. I may try, and should, VLC player again, just to see how it runs. I'm fine with mplayer though, if I can just get it to resize the video. Will be needing a browser as well, and as much as everyone seems to rave about Mozilla, my experience with it on windows is that it just hogs memory. Love the interface and ease of use though, makes all other browsers look lifeless. If they could just make it use less memory. Off to install Latex, and that should be it for tonight. Good night... |
Most custom distros based on Debian add those repos.
Debian policy is to have the default install completely FOSS. The FSF (Free Software Foundation) doesn't certify Debian as "free" because they host the non-free repos. But Debian really does make the effort to make sure that their default install is completely free software. In the case of your hardware I would assume that there is a need for, at least, firmware that doesn't meet that standard. On my old Dell box I had to have the "firmware-linux-nonfree" package installed to boot to a gui. No video would work without it. Had to boot to the tty prompt, edit the sources.list and install from there. The image you got is made for that hardware. This is helpful. You may want to generate a list of packages that are installed so you can figure out what it requires. That sources.list is a bit easier to read than your Ubuntu one isn't it. I am wondering a bit why the other standard repo for Debian Stable isn't in there. Code:
deb ftp://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free I have no idea how video is handled on that board. Sounds like you need to do a bit of research on that. Like what is the default resolution set at? And how does this compare to the resolution of the monitor you are using. The tiling proliferation of windows sounds like some sort of locked resolution trying to be accomodated along with your wish for more screen space for the video output. Do you have something that works for a monitor other than the one you are using? If so plug into it and boot up. If it is a different make and it works more the way you want then the system may be having trouble properly detecting the resolution for the one you are using. There may be some firmware for that in the repos. There may be some settings that need tweeked. |
Hi widget, I just realized last night, of course the hardware is working, the distribution was made for this board. Was starting to wonder if Linux had some magical powers.
Also, since both vlc and mplayer misbehave after resizing, it does point to something wrong in the system. I'll check out the resolution settings in Linux. Although, the monitor APEX LE1912 (only one available for now), seems to automatically set itself to whatever resolution and frequency is being fed to it. My suspicion is still a missing desktop component. I have openbox, lightdm, and for a task bar I used tint2. Had to install tint2, because without it if you minimized a window it just disappeared :). Something in the middle, between the output of the player, and desktop, is missing... maybe. Or just hardware setting as you mentioned. This line that I have in sources.list: Code:
deb http://security.debian.org/wheezy/updates main contrib non-free Code:
deb ftp://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free I'll add yours right now and do an update/upgrade. Thanks! PS I guess there was a reason they didn't include the ftp wheezy-updates repository. Broke a few things: sound, and gnome-disk-utility no longer work. For the disk utility it says it can no longer find 'palimpsest'. Not a problem. Thanks for pointing that out anyway, we learn by breaking things. Will mess with it later, and after some more reading up on video-to-desktop topics I will probably want to start clean from the beginning. I have been checking storage memory, while installing and purging packages (especially while looking for a good pdf reader). I noticed that, after purging a package (then apt-get autoremove), storage space never quite goes back up to where it was. The difference seems to be quite a bit more than what might be needed for, possibly, updating a history log in some file. |
All times are GMT -5. The time now is 07:33 PM. |