dist-upgrade failure,could not download repository indexes

Bug #193879 reported by pokkets on 2008-02-21
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Undecided
Unassigned

Bug Description

 I'm running ubuntu ultimate 1.7, with gnome,and kde. I have had a previous upgrade failure, which was upgrading many kde packages, which worked after I unticked 3rd party sources I had the box 3rd party, plus the kde 7.10 disk. Today I added debian-40r2-disk-1 to the 3rd party, and there was a bad md5sum, but the packages were listed, and there was an immediate 2 file update. Many repository indexes fail to download, an archive bin meta index file said malformed package file, and a repoubuntu.info/dists/gutsy/binary/i386Packages.gz was forbidden. When I include the update sources files related to them are included. when I looked in lib/apt/lists there were the files that were listed also seemed to have a .gpg file with the same title. There were some backsports updates listed, which seemed clear to install, but now while listed, they are masked - libxine-1,mpeg,gnome,and plugins. I'm attaching /var/log/dist-upgrade/apt-log

pokkets (pokkets1) wrote :

I have an idea what happened. I just added debian-40r2-i386 disk 2 to 3rd party sources. There may have been some programs updated, without dependencies which were on one of the other disks. When I installed 2 there were 40 files updated, including the some of the backports in holding. I'm going to getting 1 with a good md5sum, and I'll wait until I've finished with three and the fix CD before I worry about bugs. I hope that will make the apt.log a bit clearer.

pokkets (pokkets1) wrote :

There is another thing I that I think I contributed to the failure When I added Kubuntu and Edubuntu to 3rd party they offered upgrades. I'm sure I upgraded with edubuntu, but when I added kubuntu I didn't upgrade. The system and disks have all been 7.10, but since there hasn't been an upgrade, as it is seen as a source now.
in var/lib/apt/cdrom.list.distUpgrade Kubuntu is mentioned.
CD::e032efd736b74e8c1b9387dca955a778-2 "Ubuntu 7.10 _Gutsy Gibbon_ - Release i386 (20071016)";
CD::e032efd736b74e8c1b9387dca955a778-2::Label "Ubuntu 7.10 _Gutsy Gibbon_ - Release i386 (20071016)";
CD::8aaf4197d875581ff2ee8404b51d9932-2 "Kubuntu 7.10 _Gutsy Gibbon_ - Release i386 (20071016.1)";
CD::8aaf4197d875581ff2ee8404b51d9932-2::Label "Kubuntu 7.10 _Gutsy Gibbon_ - Release i386
(20071016.1)";
in software sources, the release number was quoted, and said upgrades from CD cannot be downloaded
I went to terminal /media/ apt-cdrom add which was suggested in the box which came up after I reloaded software and the kubuntu disc number was included. I think the update manager is trying upgrade, when I might have to work out how to do it in terminal. I might get out of Xscript and go into a kde session . Since I added debian40r2 Synaptic has dropped its 23000 packages, and when the disks are unmarked, there are about 3000. There are over 20,000 on the disks, so the only worry is that some of the packages that can't be downloaded are in security and updates I think Etch has replaced the download sources out of the box.-There would have been a lot of doubling up otherwise. So far it hasn't caused any problems as far as I know, but I like to play around, knowing there isn't too much trouble reinstalling the system if i have root tar I'll attach the latest /var/log/distUpgrade

pokkets (pokkets1) wrote :

There was a failure with the Kubuntu upgrade. I did a backup.tgz excluding etc/apt, and var/lib/apt, and reinstalled the system. The Edubuntu upgrade was good Then Kubuntu failed. 20071016.1 worked, 20071016 didn't It may have been an upgrade for feisty or it may have conflicted with the kde on 1.7. When I added the disk to sources the upgrade option came up I now know this was another program.Since I've gone to terminal added the disks at the prompt, and added edubuntu, Kubuntu, and the 4 debian etch disks. synaptic had 24000 packages, but in sources there was trouble getting a lock. I didn't know why it wouldn't fix on the lock, but I thought maybe it was because I added disks in terminal before I used software sources. I deleted the lock figuring debian may have changed it and pulled a lock out of an early sbackup. it seemed to work.
It had trouble finding a server, but that may have been the connection. I'm going to forget about kubuntu Ultimate 1.7 has a kde environment, and if I find debian etch conflicts, I'll just pull the packages out of the pool and set up a personal repository on another partition. I'm not sure if it was a bug as much as operator error, but I was curious about the kind of disks that could be added, and maybe Kubuntu upgrade was designed for feisty, not when introduced to a gutsy system. If it helps This is the disk that I used and the isp url
http://files.bigpond.com/library/index.php?go=cat&id=812&order=time+DESC
Kubuntu v7.10 (Gutsy Gibbon) i386 DVD ISO,
File Date: 22-10-07
File Size: 4595.80 MB
Filename: kubuntu-7.10-dvd-i386.iso

pokkets (pokkets1) wrote :
Download full text (5.3 KiB)

This comment is fairly 'verbose' and strays from the original bug report a fair bit, but the bug seems to have been self inflicted. I know there is the basic warning 'read the help files' , but I would rather learn, than be educated. I hope it can tie up some loose ends. When decided to go Linux, I also decided to get a new laptop, so it didn't matter if I ruined any part of it, even the hardware. Having since learned that is unlikely, if the original install disks are available. and some key programs are kept on a flash drive (an ndiswrapper that works with the particular Kernel and inf files, for example) I also thought while learning the 'hard way' can be very annoying, that fact usually made the lessons clearer. I've guessed wrong a lot, but usually the screw up has helped me find the place to look in the ubuntu community pages for the answer.
 I may also have come up with some conclusions now that are wrong, but I hope someone can point them out in case any new users consider them to be advice. The problem dawned on me this morning . I probably threw a spanner in the Kernel. Edubuntu probably upgraded the Kernel (backwards?) There had been an upgrade to ultimate 1.7 since it was installed. Still, by trial and error I learned a few things.
 1)Before any upgrade unmark any 3rd party sources. I had heard that before but was reminded when the Edubuntu upgrade disabled them automatically. However now I have Edubuntu in the session list, and the toolbar under system - 'about Edubuntu' (20071017?) and perhaps that is a sign I have a lot to learn.
 2) When adding a source disk, if the disk is inserted before the 'add' tab in software sources is clicked, or return is hit in terminal apt-cdrom add, the option to upgrade is offered. (If there is a different kernel on the disk?) There is also the option to open with package manager, but so far the other place I have tried to add with the most recent reinstallation was within synaptic, which may be the same thing. Press return, or add and then it asks for the disk to be inserted. I don't know if it can degrade the kernel, but kubuntu would also have tried to upgrade the kernel. Upgrade and add are two completely different programs.
It helps if the kernel is both more recent, and compatible with the system.
3) When all else fails backup home/settings with sbackup, and and start from scratch with a reinstall.
 It helps to get a root tar file from before trying something new and reinstall the system. etc, var, and usb local are in the defaults in sbackup, and I know the var apt cache has debian packages but games are in usr games and after a restore with srestore some of the titles were included as installed but the applications hadn't been restored. Add/remove programs couldn't find them to remove them but synaptic solved the problem after I removed them completely. and reinstalled. I may only have had to reinstall a lot of them. The restores seemed to hang, maybe I cut restore too early but after 12 hours I thought there may have been a problem. The tar backup.tgz in terminal is verbose, so it can be clear when the restore has finished Now I try and have a root back upon it's own par...

Read more...

pokkets (pokkets1) wrote :

I just got another partial upgrade notification
5 packages were listed, and one could not be installed
kaffeine0.8.5 to-0ubuntu1 to 0.8.6-ubuntu3~gutsy1
I went to synaptic and found the package I had and tried the upgrade from there. It said
kaffeine-xine and ichthux desktop would be removed. There has been conflict between ichthux-desktop, and kde before.
This was in google.
Bug #151601 in ichthux-meta (Ubuntu): ags: gutsy
Ichthux-desktop currently requires xkeyboard-config which is a transitional package, and thus no longer needed. Please remove xkeyboard-config from the requirements for ichthux-desktop.
 Ralph Janke wrote on 2007-12-28: (permalink)
Confirmed on gutsy
 Ralph Janke wrote on 2007-12-28: (permalink)
Will be fixed in hardy
It may be one the sources of the problem,
I keep finding there always seems to be more to it. suppose thats bugs

pokkets (pokkets1) wrote :

I went into a kde session, and saw aptitude. I thought all upgrades were done in the xscript by update manager. Aptitude did an upgrade but it also removed ichthux desktop and xine. I went back into xscript, restored an earlier etc/apt var/log/apt and tried to update kubuntu again.
The error was "System was unable to get the prerequisites for the upgrade" and suggested I send the folder var/log/dist-upgrade I found an error on the disk, and have it in the tar file with the var/log/apt folder. I might try gnome for a while

pokkets (pokkets1) wrote :

I know the var/log/dist-upgrade/apt.log is getting to around 11,000 lines now and while it no doubt repeats it's self a fair bit, No doubt I'm telling you a lot you already know, butI hope the additional comments will help the trace, but I'm just trying to work out where the root of the bug is by a process of elimination. If I caused it, it will help me to avoid repeating the mistake. The binary-i386 file was from kubuntu-disk/dists/stable/main/dist-upgrader, and the same file was in Edubuntu which upgraded.
.
The errors were "Conflicts with installed package dpkg" same with the I don't know if that will show up on the file I sent if it doesn't have access to my system, could be in apt.log somewhere
Another problem that might be solved when I get a new laptop.
"WARNING:root:envy detected, trying to workaround"
 right at the bottom paragraph.
 I have an 'obsolete' Windows graphics card that is locked into the laptop it can't be upgraded. Micrisoft are doing their utmost to get a monopoly-but that's an entirely different bug.
Envy came out of the box with ultimate 1.7, and the drivers wont install without nvidia, or ati . I thought I'd taken it out, but I just did so. It can wait until I get a dual core with a decent graphics card.
 While you can't serve two masters, a server can have two masters - Perhaps Ubuntu and Mandriva. As long as one of them isn't microsoft They want to keep peoples minds in the box. Mr gates is getting old isn't he, and it get's harder to teach an old dog new tricks - but as he said One minute you're at the top of the Christmas tree, next minute your a falling star - or something like that.

pokkets (pokkets1) wrote :

Maybe this is more than one bug, but I'll leave that with you.
This time debian 4.0r2etch was involved
I've another solved part of the problem I think Xscript can upgrade kde packages unless something in conflict has to be removed, however adept will in a kde session. Adept won't upgrade gnome for the same reason. xscript doesn't want to get involved. I may have invited this with alien upgrades,
Default session is Xscript
This is how it went today
Tried kubuntu upgrade again, after removing envy. It said there was no upgrade, but there were no errors.
reinstalled disks to sources. Left disk sources ticked got another update, packages weren't ticked. 11 I think. Went to kde session, some packages upgraded in adept, reported some packages failed to upgrade. Went into gnome session. 7 packages ticked, busybox, sysvinit, brightside, initramfs-tools, initscripts sysvinit-utils
 sysvinit failed to upgrade, because it tried to overwrite /usr/share/man/man1/mesg.1.gz which is also in package sysvutils
Terminal details:
Errors were encountered while processing /cdrom/pool/main/sysvinit-utils_2.86.ds1_i386.deb
E: Sub-process /usr/bin/dpkg returned error code (1)
the update failed.
Tried again when unmarking svsvinit it auto unmarked sysvinit-utils and init scripts.
Busybox, brightside, and initramfs-tools were updated.
The packages from the debian disk seem to conflict with each other, but I don't need them on my system, they probably aren't supposed to be there.
Once the third party sources are unmarked, the system is up to date

pokkets (pokkets1) wrote :

 I knew I could have been asking for trouble with debian 40r2 on ubuntu, but I wanted to know if I could use it as a source if I lost my internet connection Something I hadn't noticed because I was busy going between sessions. Shut down was on the main toolbar, and it went to the logon screen. it stopped at suspend. So I give it the 5 second death count. After the grub screen, I found out busybox wasn't as good as I thought it would be, got stuck at busybox, with an initramfs prompt. Restored and repeated the misery and lost shut down again, I hadn't checked if I got it back. but when I went to sources I found three new entries.
http://archive.dogfood.launchpad.net/ ubuntu feisty-backport and two unsupported feisty update sources. I know the archive.dogfood is at launchpad, I had to check, but I don't know where they came from. Maybe I missed them while I was going around in circles. (well..so does a hard drive) I've always got hardyA4 and kde4 on VMplayer. I just noticed KDE4 was at my ISP list. When I noticed the archive.dogfood source, My dog was reminding me I'd been spending too much time on the computer. apt.log wont help it's at the restore date.
I know gutsy is getting old. I might wait until I see what I can screw up with hardy, and debian4.0r3

pokkets (pokkets1) wrote :

I had a look in var/lib/apt/lists
The package that had warned DO NOT INSTALL ON A REAL SYSTEM EVER was mentioned. release-upgrade-apt was in synaptic, but it wasn't installed. release-upgrade-dpkg wasn't there. ( I know better now than to get the bright idea to do install THAT.) Sources couldn't verify the signature. Still sometimes an experiment can blow up in your face, sometimes you get penicillin. I'm getting a new laptop in March. You probably know whats in the list, but I'll send a copy. I pasted the lists together on to the one text file. My dog wants a chewy bone.

pokkets (pokkets1) wrote :

I have no doubt you're rushing to get hardy ready, but what I write can be put in an archive for later or deleted. I'll try and make the attachments to the point.
 When I lost shut down I tried kubuntu upgrade again.There was a complete upgrade, and reboot I could shut down again. As far as I could tell the system was working I've had no reason to change my mind.
I backed up, and went update-manager -d.
There are another few bugs with upgrade failures, but my system has a few distros running in parallel, so I'll leave the decision as to whether this next one is a duplicate to someone with better judgment than myself.
 I'll attach a copy of a build-essential I did here, which seems to have a good summary of the failures, and start a new bug
Upgrade-manager reports were sent yesterday Feb29, but you may need more information to put them into context. If you need anything else, I have the restore in a tar backup, and can extract any details you want.
It was time to see how Hardy coped with my mongrel of a system. The only thing that really bothered me was being unable to connect the wireless I'm finishing this bug here The original problem seems to have been solved, and this was a gutsy bug. I'll leave a reference to this bug because my system had some unusual qualities. While upgrade-manager suggested I restore my system as it was likely to be unstable, I thought, so am I, .but I replaced it to get wireless back.

pokkets (pokkets1) wrote :

the other bug number is 197199

pokkets (pokkets1) wrote :

The session was Xclient script
This bug was solved with two steps
I Started from scratch on a usb to pinpoint the problem
with the same added sources I got an update icon when debian was added
Which gave a partial, then failed upgrade notification
I checked the list of upgrades, they were primarily the replacement of debian unstable packages with the ubuntu version. There were also packages listed which were not to be upgraded
I unmarked all added 3rd party sources. The prime culprit was debian Etch. When they were removed some irreconcilable upgrades were removed from the upgrade.
Any programs that were listed but not upgraded were upgraded in synaptic package manager, where some conflicts, and dependency issues could be resolved.
The upgrades for the irreconcilable programs would not upgrade in synaptic either, those were the programs that disappeared from the upgrade when the 3rd party sources were removed.

pokkets (pokkets1) wrote :

I am curious about an upgrade which failed which I continued in bug 197199 regarding the update-manager -d which I continued in another bug because it was a distro upgrade from gutsy to hardy.
This bug was said to be invalid because the distro I am using is Ubuntu Ultimate. As far as I can work out The upgrade was from gutsy to hardy, it was not an ultimate, upgrade. As far as I know one does not exist yet. I want to try and work the problem out because ubuntu update-manager will have a hardy distro upgrade in april, and I want to try and solve the entire problem before then. The Ultimate system seems to be a Ubuntu base, with packages added most of which are available in synaptic. The upgrade seems to have failed because the apparmor would not install cupsys, so there were associated dependency problems which were also ubuntu related. The Hardy system that 'failed is on USB, and there were problems loading wireless which I have not solved yet but seemed to be a problem with ndiswrapper.
Is apparmor necessary ? I know there is SELinux but I don't know enough about linux and ubuntu to configure it. I discovered this in bug 195661 which was also about a apparmour/cupsys upgrade failure filed by christer edwards, but it is listed as a cupsys bug.
I know when some universe and backport packages are added they can cause instability, The prime examples on my system have been ichthux, and Envy. Envy had a hardware problem no ati or nvidia card. Can packages that cause instability be identified before an upgrade is done? When I update-manager -d update-manager said my system was up to date. The USB upgrade has since upgraded to the hardy Alpha 6 kernel 2.6.24-11-generic which I managed with ethernet. cupsys still failed to configure, and crashed. I just got some new CDs so I'm going to burn a copy of hardy alpha 6 and install that. Maybe I can just do a kernel/apparmor/cupsys transplant. Perhaps that would be like giving it a brain transplant. While I may be learning the 'hard way' what I learn usually leads to another program entirely.
I figure with the number of people turning to Ubuntu there are bound to be some weird bugs submitted by people only just introduced linux and ubuntu. Perhaps some of what I write can nip some of them in the bug.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in update-manager:
status: New → Incomplete

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers