Debian Configuration :: Moving From Testing To Squeeze?
Feb 9, 2011
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?
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.
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?
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 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?
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'm wondering I've read in some places that if people would like to move from a stable branch of Debian to the testing you can usually just replace the lines in sources.list with the testing release and update and then dist-upgrade. Is this true...and if so is it safe?
(==) Log file: "/var/log/Xorg.0.log", Time: xx (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) open /dev/fb0: No such file or directory
[Code].....
My usual aptitude safe-upgrade routine has not throw any errors. I do remember a libxcb-* package updating (or installing?) on the last run. This is the only relevant package I can recall.
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I'm trying to set up my Intel Wireless 3945ABG (which is supported in the kernel) and I don't understand where to start if I want to use systemd to do this.
I've installed my Debian (Stretch Alpha4) base system using the wireless to download the necessary components but when I boot into the system I need to set up the wireless card separately.
I would prefer to be able to install wireless without the requirement of connecting via ethernet so no package installs other than what is downloaded by the installer.
I can't even find documentation on this specific issue because everyone seems to reference /etc/network/interfaces which AFAIK is not supported in systemd. How do I configure a wireless card using only systemd?
After the latest update of network-manager-gnome to version 1.1.90-3 , I see that I have to start the nm-applet in Testing from a terminal, otherwise I can't bring up my wired connection.
The usual nmcli networking on command is failing to connect, also restarting the network-manager.service with systemctl doesn't do anything, the only way to connect at this time is indeed to manually start the nm-applet from a terminal.
I've also spotted this message in the logs:
Code: Select alltraps: nm-applet[1105] general protection ip error:0 in libgobject-2.0.so.0.4600.2
Could it be something wrong with my configuration (although , it worked before this update) or is it some bug in network-manager-gnome 1.1.90 ?
I've been working on the setup of a FTP server on my Debian system for the whole afternoon. But I can't get it straight! Normally I get it working in just a second, but it's been a while I guess.
I installed only proftpd-basic and it's default dependencies. Should be enough right?
My configuration files are as follows:
I created the user zeitgeist, gave it a password, group and a homedir. Group of the user is nogroup and the homedir is correct with the 755 permission. My port 21 for FTP is open I tested it with nmap -p 21 [ip-address].
My Filezilla client tells me that at first he is connecting, then the connection is established, And then the connection is closed by server.
I am running testing (with fluxbox) and my keyboard periodically freezes, meaning whatever I type in it doesn't respond. This lasts a few seconds (can be 2-3 or sometimes even more like 10) and one's it comes back I get all the keystrokes I was typing during the freeze. The frequency of the freezes can be like 4-5 times every hour and are very annoying. I can't seem to relate them to anything, they can occur during heavy usage but also when the box is doing absolutely nothing but waiting lazily for me to type some google search terms.
Can anybody help me track this problem down? At the moment I am using a wireless keyboard but this must be unrelated since I tested a couple of other keyboards (both wireless and wired) and the problem persists.
can't use catalyst driver, virtualbox refuse to run, selinux problems,I want to know if its possible to install only this new kernel 2.6.38 without "contaminating" the rest of my installation with unstable packages?
After doing a aptitude full-upgrade I no longer have the Debian menu showing in the Openbox menu. According to Obmenu, Debian is listed; it's just not showing when I right click. The upgrade brought a new version of Openbox so I assume that has something to do with it.
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'm trying to install Debian-testing to an ASUS 1018P netbook on which I have successfully installed Arch in the past. I'm installing from an external DVD drive and when I get to the point of network configuration it fails. I'm connected via Ethernet via eth0 which is recognized. Here is the last part of the ouput:
kernel: [ 1807.932848] atl1c 0000:01:00.0: irq 29 for MSI/MSI-X kernel: [ 1807.933453] ADDRCONF(NETDEV_UP): eth0: link is not ready dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval is 8 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval is 15 code....
I've installed the latest testing version, which has 2.6.32 kernel perfect for me. I was very amazed when check system monitor and saw it runs with 90MB RAM, meanwhile my ubuntu desktop takes only 400, and the pocket version of ubuntu on vmware has 180MB RAM.
The questions is: Debian runs on vmware 7. Could the amount of RAM change when switching to a normal environment? Or I have to test and see what is happening..What problems could occur when using a testing version?
but I have been literally banging my head against the wall.I am trying to configure skype on my system (testing, x86) but unsuccessfully.Let me say that I am now using skype (static) as downloaded from skype website.
$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04)
I have been trying to install fglrx drivers for my ATI card with Debian testing (x86) but without any luck. I have tried what it says here http://wiki.debian.org/ATIProprietary but I only come up with a blank screen (and also invoke-rc.d gdm stop does not work either?) I have also followed the directions at [URL]....html and that doesn't work either (make error 127). I must be doing something totally wrong.
AMD 64 Upgrade to testing last night killed my internet connection. The lan works, I can ping the dns server from my IP, however no mail, browser possible. Is something in testing broken again?
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 recently just installed Squeeze on an ia64 system and was having some troubles with running VNC.I get the following error, more specifically for some reason I get a malloc - memory corruption error:
Xtightvnc(9165): unaligned access to 0x60000000001ea06c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea074, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea07c, ip=0x4000000000268280 Xtightvnc(9165): unaligned access to 0x60000000001ea084, ip=0x4000000000268280
[code]...
After display all the code above, it just stops. The port 5901 is still closed - if it runs properly, would it open automatically?Is there something that is incompatible? Or am I missing some system configuration component?
