Debian Installation :: GPG Error When Update From Squeeze To Wheezy
Jan 7, 2016
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 --
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 have done a update from Lenny to Squeeze with the update manager within Gnome. And there was a error 126 and the update broke off leaving me with a non working system. The system does start into Debian Squeeze to the command line. Users are in place and a login is possible. X does not work and there a lot of broken and defect packages. I want to repair my system. Is a restore without losing the configuration possible?
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.
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:
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?
when I try to update my Debian, I have the following internal error:Error message:Fetch failed: W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?), W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?) , W:Failed to fetch [URL] Unable to find expected entry free/binary-i386/Packages in Meta-index file (malformed Release file?), E:Some index files failed to download, they have been ignored, or old ones used instead.
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.
Wheezy gets daily small updates.General things go smoothly - get the notification and install, job done.By occasionally it stalls - it says do partial or full updates and just sits there. For last week this persistent problem.Only way around is boot up and do manual update before notification kicks.As I type the update manager is sitting there doing nothing. Another reboot needed.
I tried to install Debian-Squeeze 64-bit from CD [URL] as I thought mistakenly my cpu has 64 bit support. Ofcurse proccess stoped as the kernel wasn't compatible, but only when I removed the 'quiet' parameter I could see the error, when the 'quiet' parameter was passed, process gave no visible error,just stop in the start screen of debian-installer.
Debian Bug report logs - #790498 iceweasel: upgrading from jessie makes all passwords in the password manager invalid.
The reporter noted this problem when he upgraded from version 37 to 38.causes listbug to block an update from iceweasel 38.01-2 bpo to iceweasel 39 (from wheezy-backports).
After the updating the synaptics driver in wheezy, I can no longer tap to click. This includes single-finger taps in the center and corners. Here is the relevant section from my xorg.conf
I cannot count how many times I have re-installed squeeze, and do all kinds of fixes to grub, but no joy. Every time, there is this ntoskrnl.exe error, and to re-install it. I thought my WIN XP may be corrupted, so I reinstalled it, and updated it with sp3 and all updates. Then I re-installed squeeze (reformatting all partitions). At the end, the installer ask if I want to install grub to mbr. I replied yes. After reboot, only the 2.6.32.3-amd64 and the recovery kernels show up on the grub screen, no winxp.OK, I booted into squeeze kernel and looked at the /boot/grub/grub.cfg file, and there winxp is not included in /etc/grub.d/30_os-prober section. In terminal, I typed
#os-propber and it found winxp in /dev/sda1 then I typed #update-grub
and now /etc/grub.d/30_os-prober now show winxp.I rebooted, and winxp shows on the grub screen, and I chose winxp.It came back with "ntoskrnl.exe ...error... re-install ntoskrnl..."Here are the details:
This is my specific solution to my specific problem. After updating to Squeeze from my prior Lenny distro (amd64 with whole disk encrytion using LVM2, dm-crypt, LUKS) everything went well - at first. I was duped like so many, thinking that all was well and I could remove the legacy-grub (aka: Grub1) and just use grub-pc (aka: Grub2). As soon as I removed the legacy-grub and rebooted my laptop, I was confronted with:
GRUB Loading stage1.5 GRUB loading, please wait..Error 15 At this point I wasn't sure if it was a Grub problem or a deeper encryption problem - especially after reading that some people had missing packages in Squeeze (lvm2, dm-setup, initramfs-tools, etc.)
Okay, the solution for me.
1. download and burn to disk: debian-live-6.0.0-amd64-rescue.iso[URL]..
2. scroll to and press enter/return on: text rescue
3. choose a root directory - for example: /dev/blah/root (I wrote down the list of possible /dev/.... for reference - this helped me remember where and what I had partitioned in Lenny)
4. choose: Execute a shell in /dev/blah/root
5. once in the shell, I discovered I needed to mount a few of those partitions that I had written down in order to get access to grub-probe, update-grub, grub-install, etc. You may not have to if your partitions are minimal. I you need to use other partitions, type (for example):
I was upgrading from lenny to squeeze. At the apt-get dist-upgrade step, at some point (after upgrading and configuring) it tried to create a new certificate for my mail server but creation of the certificate failed, dpkg reported an error and the whole process exited with error. So I rebooted the machine and issued again apt-get dist-upgrade but now the certificate was created successfully . After that it upgraded mysql-client and the process finished.
But I don't know if configuring of the upgraded packages has stopped at the point where dpkg stopped. I suppose so, because very few packages were configured at that point. Is the solution to run dpkg-reconfingure -a (or -u ?) or dpkg --confingure -a or something else ? (dpkg has the PACKAGE STATES)
dpkg --configure --pending gives me no package for configuration.PS: At least I hope that all packages were upgraded and a few were not configured. Is there a way to confirm that all packages were upgraded ?
I decided to update all the software on my computer. Fortunately, it upgraded kernel version 3.14 to 3.16. I was happy to learn that suspend now worked on my laptop by calling pm-suspend, but it did not worked by closing the lid. So I search and found on debian's website that installing systemd and adding some config lines in /etc/systemd/logind.conf would sove the issue. So I followed the procedure and did like instructed, to end up with a computer that boots on black screen.
The last verbrose line I see on boot up is "kvm disabled by bios" and then it shutdown down the screen. The computer works, as I can login and shutdown by doing those operation blindly.
I tried removing systemd but it still does not work. If I use the old kernel 3.14 I can boot without any problem, but if I use kernel 3.16, I boot to a black screen. I remember successfully booting in 3.16 before installing systemd.
I have a very strange problem; when trying to apt-get update or aptitude update I get time out errors. At first it was resolving ipv6 adresses:
Cannot initiate the connection to ftp.litnet.lt:80 (2001:778::87). - connect (101: Network is unreachable) [IP: 2001:778::87 80] Err [URL] Cannot initiate the connection to security.debian.org:80 (2001:a78:5:1:216:35ff:fe7f:6ceb). - connect (101: Network is unreachable) [IP: 2001:a78:5:1:216:35ff:fe7f:6ceb 80] As my host does not have normal ipv6 support, i just tried to disable ipv6: echo net.ipv6.conf.all.disable_ipv6=1 > /etc/sysctl.d/disableipv6.conf
I am running the commands as ROOT. I also tried: setserial /dev/ttyS3 irq 3 uart 16550A skip_test but I am getting the same stty: /dev/ttyS3: Input/output error
Output of:
Code: Select alldmesg | grep tty
Code: Select all[Â Â 0.000000] console [tty0] enabled [Â Â 0.952559] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [Â Â 0.953593] 0000:00:1e.3: ttyS1 at MMIO 0xd0810000 (irq = 19, base_baud = 2764800) is a 16550A [Â Â 0.954072] 0000:00:1e.4: ttyS2 at MMIO 0xd080e000 (irq = 19, base_baud = 2764800) is a 16550A [Â 27.740208] ttyS2 - failed to request DMA
[Code] .....
lsof /dev/ttyS3 doesn't return anything so it means there is nothing connected to ttyS3 I guess but I am not very skilled with linux so I might be mistaken
Why I can see 4 ttyS* in my Linux but physically I have only 2 physical Serial Ports on the board?
I recently did an update squeeze and the next day after I restarted there was only a blank screen.The laptop started, the system installed, the wifi connected but no gdm.I started in recovery mode and tried;
# invoke-rc.d gdm start, and got the response that it was an invalid command or words similar to that. # startx, gives me a blank screen with an unblinking cursor. # apt-get install gnome, tells me that the latest version is already installed.
If it has any bearing on the issue, I dual boot with Ubuntu and that works fine.Is there anything to be done to fix the problem?
Installed Wheezy. Audio players either stop with an error message about no sound, or they quietly play silence. Tried with gui and comand-line versions.
Mucking about with lspci indicates that I have two sound cards. News to me. I try "lspci | grep -i audio" and get 00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06) 00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio Controller (rev 04)
I have an offline machine and the full 8 DVD repository set and have added them to the system and they work fine to install packages. I used jigdo to download the update 6.0.1 DVD and the "packages" file and the one inside of "packages.gz" are empty files. This prevents the disk from working at all. I'm not sure who to report this to.
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?
The update that broke things contained some 400 packages.The problem is NOT hardware related. There are 2 other linux installs on the laptop that work the way they should.This is all related to using a wired network connection.The update removed the package network-config and did not replace it. Not sure that is the problem because that package is related to the gui and I can not get an ip in cli.
I am stuck at cli because the new kernel broke nvidia (pretty normal). There was also a new xserver, which tends to break nvidia, and as I recall a new kde. Anyway I am unable to rebuild the nvidia driver because I can not establish a network connection to my network to get the packages needed to fix it.
I cannot update my system either with Update Manager nor with Synaptic. The system tries to download the updates, and then generates an error message that I have broken packages. So, I click on Fix Broken Packages, etc., and when running get the following error message:
E: /var/cache/apt/archives/libavcodec52_5%3a0.6.3-0.0_i386.deb: short read on buffer copy for backend dpkg-deb during `./usr/lib/i686/cmov/libavcodec.so.52.72.2'
This appears to me to be a system bug. I'm running the 32-bit version of Squeeze. Re-install, or ?
I just did an update of my Debian system from lenny to squeeze as described here. I got some errors during the install, saying that glibc couldn't be updated. I did an apt-get -f install, which gives me the following warning: WARNING: this version of the GNU libc requires kernel version 2.6.18 or later. Please upgrade your kernel before installing glibc.
The installation of a 2.6 kernel could ask you to install a new libc first, this is NOT a bug, and should NOT be reported. In that case, please add lenny sources to your /etc/apt/sources.list and run: apt-get install -t lenny linux-image-2.6 Then reboot into this new kernel, and proceed with your upgrade dpkg: error processing /var/cache/apt/archives/libc6_2.10.2-2_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing:
While on the 32 bit version i haven't problem. I use different profile for the stable and the nigthly versions. Note: I use the binary taken directly from mozilla and update regulary it directly from the browser. On the attachment you can see what should be appear after the update.
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]
