Debian :: Change Repos From Squeeze To Testing And Just Keep Updating
May 16, 2010
so, if i change my repos from squeeze to testing and just keep updating after squeeze goes stable would i be asking for trouble?
i ask because when i dist-upgraded from lenny to squeeze i had some breakage - i figure if i just stay with testing i'm thinking it'll just update gradually.
I'm running Testing and am wondering why didn't Firefox/Iceweasel hit this repo yet? I know that I can download it from another source but I prefer to follow the default repos. I'm not complaining, just asking where I can find more details about the delay and if some has an when it'll be pushed.
I'm running Debian Testing and since some time ago I'm getting the following messages:Any ideas how to solve this warnings?
(gtk-update-icon-cache:9204): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Processing triggers for gconf2 ...
I've been trying out a distribution based on Debian Squeeze, but what I'd really like to try is a minimal Debian distribution I can build from the ground up and customize as needed. I heard a lot of positive things about using netinst on machines that are usually hard to get regular installation disks to work on. Downloaded netinst for i386 this week from a link at [URL].. and attempted to install from scratch on my machine. I got past formatting my disk and was at the base install step. It keeps complaining about corrupt programs it can't install. I ran a check of the CD disk from the menu and it says there are no issues with the disk itself. I can see some basic directories and cdebootstrap installed on my hard disk. Would like to jump to installing kernel and grub or something and attempt to download some of the other programs later, but it won't let me bypass the step. Saw some articles about a Debian from Scratch project on the Internet, but doesn't look like it's active any more. What's the best way to get a minimal Debian distribution based on Squeeze installed to a hard drive? Should I just wait until the official release?
just installed testing on my netbook. my sources.list file all say wheezy. it was my impression that debian testings nickname was squeeze. are wheezy and squeeze the same thing?
Just switched from stable to testing. To run a pure testing, can someone tell me if I have all the necessary repos below?
deb http://www.debian-multimedia.org testing main non-free deb http://getswiftfox.com/builds/debian unstable non-free deb http://ftp.debian.org/debian testing main contrib non-free deb http://security.debian.org/ testing/updates main contrib non-free deb http://www.debian-multimedia.org testing main non-free deb http://mozilla.debian.net/ squeeze-backports iceweasel-4.0
I'm wondering about this because I'm considering doing this myself. Specifically, I'd like to know if your wireless configurations survived the upgrade or not. Meaning, where they removed, altered, or hopefully, where they preserved as they where?
Also if anyone knows of a good link regarding this particular upgrade, by all means please share. I have only been able to dig up a bit of dirt on the topic but they were concerning older Debian releases. Maybe theres not much difference?
I have an older system that has been running testing for about 4 years. Originally I was running testing for several packages that were not yet available in stable. However, now that this system has a more crucial role in the network I have considered moving it to stable in hopes that it I can gain some insurance on it's uptime. It is important to note that I have never had a problem with the testing distribution and would be quite content to continue running it; I do want to know my options though.
I have not yet updated the system since the stable release of squeeze, I am considering to change my sources from testing to stable and just let apt take care of the rest. Anyone have any experience with such a thing? After searching Google I have found some solutions to force a downgrade, but that is really not what needs to be done here. I suppose I should have switched my sources to squeeze some time ago and this probably would have worked itself out.
A similar question is what happens a couple of years from now when another release happens. Have you had good luck updating from old stable to stable? I've run testing on several machines now for several years and have went through freezes and dist-upgrades several times with no major problems at all. Will I see the same stability if I move to the stable distribution?
I am still getting the error that no kernel modules are found when trying to load components from the CD on the multi-arch version of Squeeze. Are these even tested prior to releasing them? I mean I know it's testing but I thought we were reaching a release-date and the installer is 100% broken and has been for months. I have a pile of useless multi-arch CDs for Squeeze that won't install on 64bit or 32bit machines due to not finding the kernel modules. Can we get some testing on the installer portion of Squeeze?
For anyone using Blueman with Testing (Squeeze), todays Python upgrade to version 2.6 stops it from working due to a Blueman bug. This has been fixed in blueman version 1.21-4, which you can install from SID if you don't want to wait the 10 days for the normal migration.
Is Java running in your browsers properly? I just want to make sure I'm not alone. I'm sure a recent update caused the problem. A future update will probably fix it.
Java applets have stopped working on my main desktop and laptop. The server running stable/lenny works fine. Fedora and Ubuntu installed on the laptop also work fine.
Java applications such as JAlbum work without any problems.
Only Java applets in the browsers fail. Iceweasel, Epiphany, and Opera all fail.
It fails on my internal site.
I get the same error at Test Your Java Version And How do I test whether Java is working
Choising an hardware in LINUX is not easy since one has to check before whether it is supported. A large hardware base is supported , but not everything.
Which webcam is sponsored by DEBIAN TESTING that works surely with just a plug and play (skype / camorama...) ?
Could someone give me the steps to installing/enabling the newest Flash 10 in Debian Testing/Squeeze?I want to install via the steps one would do from Adobe's website.IT DOES NOT WORK.IT DIDN'T WORK FOR ME.I just want to install the routine way that is usually done in Linux but when I downloaded it, I was asked to extract it and I have no idea where it got extracted to.Can anyone help?I don't mind starting from scratch.I don't remember how to do this method.I'm used to the 'non-free' package in the repo but Flash 10 is no longer working so I want to use the 'sure' method.
When updating from the last Debian Live image (Squeeze) to the current Debian testing, apt announces a lot of packages being not required:
The following packages were automatically installed and are no longer required: openoffice.org-draw libpcsclite1 libwpd8c2a usb-modeswitch gtk2-engines-smooth dnsmasq-base tomboy libmono-security2.0-cil libgsf-1-common update-notifier-common libndesk-dbus1.0-cil libmtp8 libmono-addins-gui0.2-cil gnome-js-common pnm2ppa libavutil49 libhal-storage1 libmono-system2.0-cil update-notifier python-mako openoffice.org-officebean openoffice.org-emailmerge network-manager-gnome openoffice.org-impress gdebi libgpod-common
[Code]...
These include some important packages, like network-manager-gnome for example. Was it really intended to be removed? Without it, it's impossible to manage network connections from Gnome (only manual option of editing interfaces config is left). Is it a bug, or some incomplete intention? apt suggests to autoremove these packages. Should they all be retained, or only some of them, or it's supposed to be none? Removing some of them makes sense for me (like Epiphany for example), but some not at all.
I have just updated Debian Squeeze and my mouse cursor is invisible. However, it still functions... I can right click and get a menu, clock on things and get the normal functions.
I have filed a bug report and found one other bug report on this but haven't found a fix or any other info.
This happened when I was reloading my repos using synaptic on Ubuntu 10.10. How do I fix this?
Code: W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://extras.ubuntu.com maverick Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DB141E2302FDF932
W: Failed to fetch http://extras.ubuntu.com/ubuntu/dists/maverick/Release W: Some index files failed to download, they have been ignored, or old ones used instead.
For some reason I installed Volatile, as opposed to Testing... I have tried the change all Volatile to Testing process, and every time I do so, I end up with a non-working system. Is there some process I am missing in this? Here is my sources list:
The strangest thing happened. I installed Debian testing with the "squeeze Alpha1" netinstall cd. All seemed to go well and the installer made me pick a root password and create a normal user account. However, after the first boot my user account did not work and I could also not login as root, it looked liked I forgot the passwords for both accounts. When rebooted in recovery mode, I got Code: sulogin: root account is locked and I was automatically logged in as root without being asked for a password. Then I found out that the normal user account does not exist. I created a user acount and logged into it. I did passwd to set a password, but I got Code: passwd: Authentication token manipulation error Also, there was no home directory for the new user.
I have just installed squeeze and I changed my source.list from squeeze to testing then did dist-upgrade/upgrade.After using for a while, I notice that apt tells me there are many packages no longer requires, all of them are default packages in Debian GNOME. If I use 'apt-get autoremove', of course, I lose almost everything in my GNOME desktop.Why apt tells me those packages are no longer required? It's ok or something is broken in my system? I switched from stable repo to testing repo several times before, but this is the first time I face this problem
I installed Debian Squeeze with Gnome today. I'm unable to change from the default icon theme. I can change themes, but the icon theme remains default.Things I've tried:
- I've made a new user account.
- .gtkrc-2.0 in my home is auto-generated, .gtkrc.mine does not exist.
# -- THEME AUTO-WRITTEN DO NOT EDIT include "/usr/share/themes/Darklooks/gtk-2.0/gtkrc" include "/home/haunted/.gtkrc.mine"
# -- THEME AUTO-WRITTEN DO NOT EDIT
- I've tried installing a theme into my /home/.themes.
I looked into my shell 'profile' on my running lenny and copied the PS1 definition over to my [virtual] new squeeze machine, but astoundingly, the prompt does not change!
The prompt always remains to be like this:${debian_chroot:+($debian_chroot)}u@h:w$
This does definitively not stem from 'profile' and I cannot find, where it is defined and how I can override this. If I do it interactively, in a terminal [terminal running in Gnome], it works like expected. In that script, even if I use 'unset PS1',followed by PS1= ... / export PS1, it does not change,Someone with the knowledge and/or a good idea would be great!
How to change login theme on squeeze? BTW on lenny I can easy change using System -> Administration -> Login Window, but cannot find this option on squeeze.
I am a ubuntu user but I want to go to the next level to use debian because what I heard of it, but I get confused to what to install on my computer do I install debian testing or debain stable with testing repositories.
- I want to use this system to the home use only. - I want to use the newest packages because the stable packages is too old to use. - What about using more than one repository i.e stable with testing with unstable at the same time (the same sourcelist) - Is the testing and unstable sid packages good enough for the home use?
I'm trying to do is protect the computer against housemates. The standard procedure I do with Lenny:
1. Password protect BIOS.
2. In BIOS, always boot from hard drive. Disable booting from any other device such as USB or CD-ROM.
3. Password protect Grub (v1) using the "password --md5 $1$9MuaA/$5TDLgvmcEiCWNr5W9VaMK1" syntax in my menu.lst file.
With the above precautions in place, [I think] the only way to gain root access to the system is to take the case lid off and proceed to do stuff physically (like set jumpers and/or take out the hard drive). Am I correct? My reasoning for this is, the computer boots -> must boot from HD -> must load Grub -> must go to default menu item since others are protected, and cannot command prompt in Grub without password.
Anyhow, In Squeeze, I was a bit disappointed to find out, after doing a bit of Google-research, that Grub v2 (which is standard on Squeeze now) does not easily support password protecting the Grub menu. Am I correct? Will this issue perhaps be addressed in the Squeeze final release? Is this feature dumb anyways because the Grub password is of no use (i.e. my paragraph above is complete horseradish)?
Another thing I would like to do is change the console font and size back to something more "normal" or "classic", not some crazy tiny font that's only found in totally bleeding edge Linux distrubutions <gasp!>. I found that the Squeeze console font (e.g. when I type Ctrl+Alt+F1) is wicked tiny. I wanna change it to "normal". Grub v2 password and console font config?
As I have 15 repo's enabled in Yast it a bit tedious changing them in the package manager, is there an easier way to bulk change them? Something like doing a kfilereplace on the /etc/zypp/repos.d/ folder and changing all occurances of 11.3 to 11.4 (in all *repo, which are all the files in the folder). Will this work?
I have local repo as well the debian official repos enabled in the apt sources.list, but when i run the aptitude to install some packages, it doesn't use the local repo and downloading the same version of package again that is already present in the local repo, this is my local repo url: [URL]