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?
View 1 Repliesis 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.
View 2 Replies View RelatedI 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 --
[code]....
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.
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.
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:
[Code]...
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?
View 5 Replies View RelatedI 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 running a Postgres server and after I did the whole installation I realized the Postgres data was set in /usr/pgsql/data. Sda1 is just 10 Gig so I decided to re-organize the partitions to be able to move /usr to say /dev/sda7 with a mount point as /usr. The / partition is on the only primary partition and the rest is on an extended partition. When I tried to resize the primary partition GParted did not give me that possibilty so I decided to move /usr
Original partitions:
sda1 / 10 G on primary partition this includes /usr /var and all others
sda5 swap 2 G on extended partition
sda6 /home 140 G on extended partition
So I did create another partition using Knoppix and Gparted the disk:here is the new picture:
sda1 / 10 G on primary partition this includes /usr /var and all others
code....
I did rsync to copy all the file to /dev/sda7/usr and then mv /dev/sda7/usr* /dev/sda7. I stop the postgres database and services then I mv /dev/sda1/usr to dev/sda1/poufusr . When I rebooted it reports errors from kbd files on /etc File not found. It brings me to a terminal (No GUI) I did a check with :#mount: nothing is reported about sda7
What am I missing ?
Just re-installed Wheezy to ssd-drive and noticed that everything works much faster than before. For the older install I made some changes to /etc/fstab (I think) which I found from the web. I don't remember exactly what changes.
Question is: what's the situatation with Wheezys beta4-release and ssd-drive? Do I have to edit something at the moment, or does the installer notice ssd-drive and make everything needed?
I searched the forum about installing the liquorix kernel but I cannot understand why the file /etc/apt/sources.list is not mentioned to invoke the liquorix repository.
Instead, I found: Alternative Performance Kernel for Debian wrote:For anyone interested, just add the following to a sources file (/etc/apt/sources.list.d/liquorix.list): deb [url] or for you scripters, echo "deb [url]
I already have a Notebook with windows (for some reason it needs 3 partitions..) and wheezy. When I installed wheezy I create 2 logical partition inside a primary one: one logical for /home and the other one for filesystem. Now I would like to overwrite wheezy and get get jessie, but without touching windows and home.
I already try to upgrading and it went wrong, so I prefer overwrite, what I have to do during "manual installation" phase?
I upgraded one of my Squeeze installations to Wheezy, but after selecting it in grub, nothing is displayed on screen: no CLI and no GUI. I tried Ctrl + Alt + F[1-7] and I got nothing. My laptop is Acer Aspire 7715Z. I am attributing this to module as there seems to be disk activity, but without a screen, I cannot be certain.
View 14 Replies View RelatedI added the following line to my sources.list
Code: Select alldeb [URL] ..... wheezy main non-free
and then after:
Code: Select allapt-get update
I run:
Code: Select allapt-get install nautilus-dropbox
but I got stuck (console freeze) and I had to reboot hoping to sort out somehow...
After reboot I try to apt-get again but I got the following message (my traslation)
Code: Select allE: dpkg was interrupted.
It's necessary to do "sudo dpkg --configure -a" for correcting the problem
So I went in the console again for that command and I get
Code: Select allConfigurazione di nautilus-dropbox (1.4.0-3)...
Dropbox is the easiest way to share and store your files online. [URL] ....
but nothing fruitful seems to happen; and now how to proceed?
I am installing Whezzy and the installer failed to install grub on the MBR of /dev/sda
My disks are
- /dev/sda : the flash drive with the debian ISO
- /dev/sbd : a small SSD for the / partition (sdb1)
- /dev/sdc + /dev/sdd : a software RAID-1 array with LVM for /home, ...
Grub fails to install on /dev/sda which makes sense since this is the flash drive containing the Debian ISO so no MBR.
I already tried to run grub-update manually on /dev/sdb (with chroot /target grub-install --no-floppy --force "/dev/sdb" ).
It works but the system is not directly bootable. I had access to a second PC to read the grub documentation so was able to boot and to fix my system but this is annoying.
Is it normal to see my flash drive as /dev/sda? Could it be that my flash drive is incorrectly detected as a HD?
Is there a way to force the installer to install grub on /dev/sdb?
I have a server in which I'm trying to install Debian into. There's no BIOS, only EFI boot. The vendor locked it down so there's no way to see it or get into it.
The Wheezy 7.8 netinst CD has EFI boot parameters and works on everything I throw it in, except this one server. Booting it up, the code doesn't see the EFI and boots into normal mode, negating every chance to install it (dozens upon dozens of failed installs).
During boot, I press the [TAB] at the Debian Linux installer menu and get the load parameters (/install.amd/vmlinuz vga=788 etc). What parameter can I add to this line to get it to run in UEFI mode so we can install it?
I have a laptop primarily used for a client work. It is running Debian Wheezy, and wish to keep it intact in case I need to do more work for client.
I would like to install Ubuntu 14.04 alongside Debian, and use Ubuntu as a bit of a play/experiment area, etc... HD has lots of space (600GB free), and as far as I can tell Grub is installed in MBR.
I did some searches, and from what I can tell, it sounds like I can just install Ubuntu from ISO file, specify how much space to use (say 400GB), and that's it. This sounds almost too easy. Once I install and restart machine, will there be selection for what Distro to boot.
Without knowing the consequences I added the Sid repository to Wheezy (installed version) in order to install some software. Only much later I discovered that this generated me some mess which does not allow now to install additional software due to library conflicts.
I tried to install some packages needed to build the PhantomJS but here is what I got:
Code: Select allReading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version.
g++ is already the newest version.
g++ set to manually installed.
[Code] ....
Is there a way to clean up the mess that Sid introduced and revert back to the Wheezy versions?
I have an old backup, so it would take me much more time to reinstall/reconfigure certain software, so I am looking to alternatives.
Is there a way to check all the packages and find all the potential conflicts and then a way to restore the original Wheezy content?
I have just installed Wheezy after repartitioning and had to set up my sources list myself as (most of it) was not done for me. I have just added the main official repository,security updates and the multimedia repository. To be honest I'm not sure if any of them are working when I do an update in aptitude, I think the multimedia one might be. The CD ROM isn't even working despite the fact I have done apt-cdrom add.I am getting the following when run aptitude update:
Ign cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot i386 CD Binary-1 20110328-05:16] wheezy InRelease
Ign cdrom://[Debian GNU/Linux testing _Wheezy_ - Official Snapshot i386 CD Binary-1
[code]....
I am using Wheezy netinstall on a USB stick. The machine has an Intel DH57JG motherboard, USB keyboard, and no optical drive. The installer loads to the initial screen OK, but the keyboard is not active. This problem has been reported for several years and was supposed to be fixed by kernel 2.6.32, yet here it is. What can I do?
One suggestion has been to disable/enable USB legacy support in the BIOS. It is enabled by default. If I disable it, the installer doesn't load. This keyboard works fine on other Linux machines and on the BIOS in this machine. I read there was a problem with Cherry keyboards and the Squeeze installer. This keyboard is not a Cherry but does have Cherry keyswitches.
I've created my own wheezy live usb-hdd using:# lb config -a i386 --mode debian --distribution wheezy --linux-flavours 686 -b usb-hdd --bootloader syslinux --memtest none -p xfce
P: Considering defaults defined in /etc/live/build.conf
P: Creating config tree
# lb build
The binary.img was created.
Now if I try to boot from this image using qemu, I get a message "No bootable device"
If I check this main partition using gparted, the flag is "lba" instead of "boot".
Even doesn't work if try to change to "boot".
How to solve this problem?
I'm trying to install Wheezy (amd64) from the daily netinst image with the text-based installer. The PC will lock up randomly at some point in the process (usually after about 5-10 minutes). The video signal cuts out, keyboard lights are unresponsive, and I have to hard-reset the machine.I was previously trying to install Linux Mint Debian Edition and had the same problem. Another user reports that this is due to a bug in the nouveau nVidia driver, but I can't confirm it.URL...
I assume the Debian text installer isn't using nouveau, so it seems unlikely that would be the problem. The random timing does suggest an overheating problem, though, and the fact that the video signal drops out would seem to implicate the video card. I had no lockups at all with the OS that was previously installed (Ubuntu 11.04).
I'm trying to install adobe flash player on wheezy (7.4). I've downloaded the package since adobe thinks apt works in a browser (it doesn't on my laptop). Anyway, I've tried installing the adobe flash player package via gdebi and it complains binutils is not installed. fine, I go to synaptic to find binutils and synaptic cannot find it. I'm not even sure why it is not installed. How to get binutils?
Here is my sources.list:
Code: Select all#
# deb cdrom:[Debian GNU/Linux 7.3.0 _Wheezy_ - Official i386 NETINST Binary-1 20131215-03:38]/ wheezy main
# deb cdrom:[Debian GNU/Linux 7.3.0 _Wheezy_ - Official i386 NETINST Binary-1 20131215-03:38]/ wheezy main
# deb http://ftp.us.debian.org/debian/ wheezy main
# deb-src http://ftp.us.debian.org/debian/ wheezy main
[Code] .....
I upgraded from deb7 to deb8, but am no longer able to boot. After passing the grub boot menu, the following messages are displayed:
Code:
Select allLoading, please wait...
[ 6.065713] systemd-fsck[148]: /dev/sda1: clean, 428644/1310720 files, 410616
9/52442880 blocks
[ 7.480551] Error: Driver 'pcspkr' is already registered, aborting...
[ 8.692700] systemd-fsck[341]: /dev/sda5: clean, 145485/6176768 files, 17407409/24695552 blocks
[ 18.066215] Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead
_
The screen then clears and an underscore is displayed as the sole character at the top left position of the screen. The system hangs at this point. During installation, I rejected two changed files: /etc/init.d/bootlogd and /etc/libreoffice/sofficerc. For both, I opted to keep the installed version (the default choice of the installer) rather than replacing with the new version. The first might be related to the problem, although it seems to be responsible only for logging the boot process, and I would not expect this to compromise booting.
In case this information is useful, sda1 is mounted at /, sda2 is swap space, sda3 is extended, and sda5 is a logical partition mounted at /home.
I am able to boot into rescue mode, but other than that the system is not usable. Unfortunately, no useful error messages are given to aid in diagnosing the problem.
After installing KDE USB keyboard and mouse won't work. They are added to /proc/bus/input/devices though.
I also tried to install Gnome; same thing.
I took #usb-devices and they were there also..
But #usbhid-dump did not generate anything to screen.
I love using wheezy but i keep having to take my computer downstairs to hook it up to router through ethernet, i need it to connect through wifi and stay connected.
heres my problem, if i use live image and connect to network its fine but during installation process it gets to the network configuration, it will keep disconnecting at dhcp and if i try and continue it gives me the error packages broken due to it not staying connected.
MY WIFI CARD IS A TP-LINK WDN 4800
if i try and just do a net install then it doesnt show my wifi network.
it uses in both cases ar93xx atheros driver for installing, i just need to know how i can try and keep a stable connection over wifi so it can install over wifi so i dont have to keep taking pc downstairs to install it.
i done something that stopped me being able to login into wheezy i was left at black screen with blinking command line, i have reverted to mint debian until i can get a stable connection over wifi to install wheezy again.
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, forum-admin@forums.debian.net 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.
I've changed my /etc/apt/sources.lst file to use "jessie" repositories instead of "wheezy". I then ran synaptic and updated everything (there were loads of packages, something like 2000 to update).
After this I rebooted. The grub menu shows as usual with the background image I'd set and the operating systems as usual (including Windows 7) however there is no longer a 5 second countdown and when I select *any* menu option, it asks for a username and password.
I don't know what username and password it's asking for as I never used to have one set!!! I did have a username and password set up so that if you wanted to edit a grub menu option so I tried that but to no avail.
I'm using MBR/BIOS not EFI.
Recently I upgraded my machine from wheezy to jessie.
Everything went smooth until the point that I restarted the node.
During startup I'm getting the following message which is flooding the screen:
Code: Select allsystemd-journald[296]: Failed to forward syslog message: Connection refused
After waiting a long time (the message above still continues to flood the screen), I'm being prompted with the following:
Code: Select allGive root password for maintenance (or type Control-D to continue):
If I press Ctrl+D the boot process continues and finally boots normally.
What I can do to avoid pressing Ctrl+D during the boot process?
I'm assuming that it must be a startup service which is failing but I'm unable to trace which exactly is that.
I'm attaching the full log [URL] ....
I posted this same issue in the Xfce support forums this morning. So far, no replies. This morning, using Synaptic, I finally upgraded my main Wheezy Xfce 4.6 computer to Xfce 4.8. There were 225 upgrades, plus 33 new things to be installed. It has been about 2 weeks since I last fully upgraded that system, so I'm sure that not all of today's upgrades were directly related to Xfce 4.8.
I waited to upgrade as long as I did because Wheezy's been getting a steady stream of Xfce 4.8 upgrades for the past several days -- I wanted to wait until that stream stopped, to reduce the chances that I would run into an upgrade problem that was on the verge of being fixed.
The only issue I had was that, in the middle of the configuration step (for lib6, I think), it asked me to either stop or restart xscreensaver before continuing (so that I wouldn't get locked out of the current session), so I completely stopped xscreensaver.