My Squeeze version is extension three and I had it loaded on my Seagate 1 TB SATA drive. Extension three Squeeze is still on the SATA drive. I loaded Wheezy on my 80 GB Western Digital IDE setup up as a master with my Plextor IDE CD/DVD ROM setup as the slave drive.
Squeeze on my version was LXDE and Wheezy on my version is Gnome gdm3. My Squeeze was loaded with Lilo 22.8 and my Wheezy worked with the regular bootloader. I am just wondering if I use Disk Utility to delete the extension three of Squeeze if it will make both versions unusable.
But when Squeeze goes from 'testing' to 'stable' in December... does Wheezy get promoted from 'sid/unstable' to 'testing' at the same time?.
I started my life in Linux with and currently use Ubuntu, and it runs decent(barely). However, I just upgraded to Ubuntu 10.10, and because of strange little issues and increasing bloatware, I have been forced to strongly consider the "mother OS": Debian.
The reason for my original question is that I want to run whatever the current "testing version" is. And if Wheezy gets promoted at the same time Squeeze does, then I will just wait the 4 weeks instead of slogging through another install(I prefer fresh installations vs upgrading within). I know the test versions of Debian are a bit more active than stable, but I have used Ubuntu for over 2 years, so I have some experience dealing with Terminal commands, package management, gnome, etc...I am also currently VirtualBoxing a copy of Squeeze.
I'm trying to compile the 2.6.38 kernel (from the Wheezy sources) on my Squeeze laptop and get the following error: "dpkg-buildpackage: error: debian/rules build gave error exit status 2" After doing apt-get build-dep linux-image-2.6.38-2-amd64 and apt-get source linux-image-2.6.38-2-amd64 I did dpkg-buildpackeg and here is what happened:
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?
I just upgraded my squeeze to wheezy only to have a bunch of problems. Now I want to downgrade back to squeeze. To upgrade I changed everything in my /etc/apt/sources.list from 'squeeze' to 'wheezy' and ran 'aptitude dist-upgrade'. Is it possible to go back without reinstalling?
is it possible to simulate upgrading a Squeeze installation to a Wheezy or Jessie installation, on a OVH server ?I would like simulate upgrading server, and if not problems, upgrading in real time.I don't do that manipulation, and I don't do mistakes on a production server.
I try to update the packages before upgrade to wheezy,looks like when I run apt-get update,it shows error as per below:
W: GPG error: http://fosiki.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379393E0AAEE96F6 rat:~# apt-key adv --keyserver keyserver.fosiki.com --recv-keys 379393E0AAEE96F6 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --
A few days ago I bought a Raspberry PI B with Debian Wheezy (7.0 - I think) on it. Before installing a media centre on it I wanted to do some basic configuration/upgrade and decided to upgrade to Debian Jessie. I followed the instructions provided on [URL] .....
Before moving to Jessie I have upgraded the original Wheezy; after the upgrade the version was 7.8. Everything went well till I executed "apt-get dist-upgrade". Errors where generated. As suggested I tried the "apt-get -f install"; but it did not go smoothly either. However, so far, I am accessing the desktop and everything seems fine (although I did not do anything fancy yet). The version recorded is 8.0. Thus, should I worry about the error messages generated?
Please find the log file here: [URL] ......
Note that I put the log file on Google Drive because each time I clicked on "add file" in the "Upload Attachment" tab when editing this message I got:
Internal Server Error: The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, firstname.lastname@example.org and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log.
im using deb squeeze after upgrading from lenny since upgrading, my pc hangs when trying to save any file with any program like gedit and firefox it hangs for about 2 minutes with a blank save as screen before finally showing the folders screen.
I'm running Lenny, and I've always used aptitude. The upgrade instructions on Debian's website say that apt-get is preferred for doing the upgrade to Squeeze, and also says that apt-get now provides equivalent functionality. So is there any reason to continue to use aptitude after upgrading to Squeeze, and if so, will there be any problems caused by having used apt-get for the upgrade? Or will there be problems caused by switching to apt-get after using aptitude before the upgrade?
since I'm new to the the forum and this is my first post I'd like to discuss a quite weird issue. Specifically, after upgrading my Debian system to Squeeze a few days ago, sound is completely lost. This means that I cannot hear any sound from anywhere (mp3, streming videos or anything else) except the system bell . I've done a research on the Internet, looking in other forums and discussions but still, nothing works for me. To begin with, I'm running Squeeze in an HP laptop with HDA Intel soundcard and chipset ALC268. When I'm running aplay -l I get this message:
Darkstar:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
I had a broken URL in my /etc/apt/sources.list file, apparently because the debian-multimedia.org site had some kind of server issue and they had to rebuild the site from the ground up. They must have changed their directory structure, because I began getting 404 Errors when upgrading packages. I eventually fixed the URL last week after it had been broken for three months, then I upgraded and rebooted. After that, sound stopped working, even system sounds. My speakers work, because I plugged them into another machine and they worked. I eventually discovered that the master volume was set to "mute", and so was the master volume in the alsamixer. However, even after changing it to 100% for both, sound still doesn't work. I even made sure to issue a "alsactl -store" command toeep the settings there after a reboot. I removed and reinstalled all the alsa and pulse audio packages, made sure that the emu10k1 driver was installed for my Soundblaster Audigy card, and made sure everything was unmuted. I have also tried a million other things that I've found on Google, but nothing seems to work. Any help would be greatly appreciated.
Actually, the /root- filesystem still gets mounted, for all the others I get the following message:
When I type
But this only happens when using my custom kernel (188.8.131.52). When I use the kernel which was automatically installed (2.6.32-5-amd64), the problem doesn't occur.
Is there a kernel option I should have turned on?
I checked the UUID-numbers from the error messages with the output of "blkid" - they match. The rootfs is on sda2 (which gets mounted without error) - so I tried applying the fstab mount options of sda2 to the other partitions - same problem still. what makes the root partition so special? Is it because it's defined by grub.cfg?
I'm in need of a bit of assistance from you Debian users. I have two servers that I thought were identical installations, both running Debian Lenny. Tonight I started the upgrade to Squeeze on both servers and one of them went smooth. The other one started out good but fails on the postconfiguration of openssh-server. I'm getting the following message:
I see that an update to 6.0.2 is scheduled for Sat, June 25, 2011: [URL] will I need to add "squeeze-proposed-updates" to my sources.list for 6.0.2, or will leaving "squeeze-updates" in place as is be sufficient? My current version and sources.list:
I'm looking to upgrade from Lenny to Squeeze and would like to check if there's anything special I need to do. Software-wise there's nothing out of the ordinary on the system but, while looking into upgrading, I've read some horror stories regarding encrypted systems. I've only previously installed from fresh.
Here is how my current partitions/filesystems are set out: . sda1/sdb1 > raid > ext2: boot . sda2/sdb2 > raid > luks > lvm > ext3: root . sda2/sdb2 > raid > luks > lvm > ext3: swap . sda2/sdb2 > raid > luks > lvm > xfs: data . sdc1/sdd1 > raid > luks > lvm > freespace: vms
Would this just be a standard upgrade, as per these? [URL]. I will be backing up important data before I attempt to upgrade.
I am still running the linux-image-2.6.32-5-686 kernel a computer with squeeze. I installed squeeze on it when it was unstable. I would like to bring up to the new stable state.Should I do apt-get install linux-image-2.6.32-5-686or should Iapt-get dist-upgrade
i have fresh installed debian wheezy xfce4, and using slim to start it but i can't get reboot, shutdown and thunar can't open flash and others volumes. i using .xinitrc (exec ck-launch-session startxfce4)
I got "stuck" with stable up to now and want to upgrade to Wheezy. But, although I've done this before, I'm having a dependency problem I wanted to ask about before breaking my system somehow. This is the /etc/apt/sources.list, ready for Wheezy:
So, I regularly use aptitude as my package manager. After updating the database with aptitude update, trying aptitude full-upgrade gives me a huge of conflicts.
But, if I use apt-get dist-upgrade, I get no conflicts. if I dist-upgrade with apt-get, will that affect my daily usage of aptitude (which I prefer)? I know APT is a single database and apt-get and aptitude are just different interfaces, but I guess differences might rise when marking packages as automatically or manually installed.
I dont want openjdk packages on my system, in Kubuntu I had a few troubles with them trying to make SqlDeveloper to work around. So this is what I see after a java -version:
Code: Select alledgardo@debian:~$ java -version java version "1.8.0_45" Java(TM) SE Runtime Environment (build 1.8.0_45-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode) edgardo@debian:~$
I've been uninstalling openjdk from synaptic and with other few commands on the terminal so far and I think I probably broke it. I have no /usr/lib/jvm folder only /usr/lib/java/jdk1.8.0_45.But everytime I wish to start up Eclipse it shows the logo for a few seconds and that's it.... never gets opened. And in /usr/bin$ I only have this symbolic link....
I've had a weird issue recently with Java/Spring. Basically, it would work on all machines but my trusty Debian box. Macs for devs, Ubuntu for production and some devs have it too. This annoyed me, because of course Debian is the greatest and it must work there too! Also, Java is based on the whole write once run anywhere concept, I have never really had a problem with code behaving differently on different Java installs of the same version, even on completely different OSs it seems to behave itself very well. URL....
I moved up to Jessie and the problem goes away. I can only conclude that some library that is called by Java got upgraded, somehow influences the order in which Spring resolves its dependencies. Probably the fact that other devs build on Ubuntu and have got it working there, and the upgrade to Jessie brings my libs more in line with what Ubuntu will be running has done the trick.
I am trying to install octave 4 in my debian wheezy, and I am getting following error after I have executed ./configure
checking for sgemm_ in -lmkl... (cached) no checking for sgemm_ in -framework vecLib... no checking for sgemm_ in -lcxml... (cached) no checking for sgemm_ in -ldxml... (cached) no checking for sgemm_ in -lscs... (cached) no checking for sgemm_ in -lcomplib.sgimath... (cached) no checking for sgemm_ in -lblas... (cached) no checking for sgemm_ in -lblas... (cached) no
configure: error: A BLAS library was detected but found incompatible with your Fortran 77 compiler settings.
I have tried to find a solution about issues installing octave 4 from binaries. I can not use octave from the repository as it is old for my studies.