Re: [xubuntu-users] Upgrade from 15.10 to 16.04 got aborted
On 01/03/2017 09:17 PM, Peter Flynn wrote: [snip] > so I'm asking the same here: what do the 'rc' flags really mean (ie on > what criteria are they based) and can they be trusted? The actual list > is below... Belay that question. Turns out that these are obsolete *config* files only, not the actual packages. Nevertheless, using the script posted in that page, I seem to have recovered to a stable point, and recouped about 10GB of disk space. We now return you to your regular scheduled discussion... ///Peter -- xubuntu-users mailing list xubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
Re: [xubuntu-users] Upgrade from 15.10 to 16.04 got aborted
On 01/02/2017 03:20 PM, Dave Dodge wrote:
> I recently upgraded a machine directly from 14.04.5 to 16.10 and ran
> into a lot of trouble along the way, ranging from dependency conflicts
> to pre-script failures to a cat stepping on the reset button while I
> was trying to fix things.
cat(1) needs a --nopaws option...
> According to my notes, I eventually got it all the way through, mainly
> by repeatedly forcing it every time it quit because of too many
> errors:
Mine never got that bad, fortunately.
I did find this page
http://askubuntu.com/questions/539235/how-to-remove-obsolete-packages-after-failed-release-upgrade-via-do-release-upgrade
which looks like what I want (get rid of the old packages that would
have been removed if the installer hadn't aborted). I just commented on
that page:
> [...] when I use dpkg -l|grep "^rc"|awk '{print $2}', it lists 342
> packages, including many that I use constantly (like aptitude,
> biblatex, tidy, xchat) as well as lots of libs I've never heard of. I
> guess I can always reinstall stuff I want, but is it likely that
> trusting the 'rc' flags might result in an unusable system?
so I'm asking the same here: what do the 'rc' flags really mean (ie on
what criteria are they based) and can they be trusted? The actual list
is below...
///Peter
--
# dpkg -l|grep "^rc"|awk '{print $2}'
aptitude
biblatex
css-mode
dict
emacs-goodies-el
foomatic-filters
gnus
hplip
html-helper-mode
icedtea-netx-common
kdepim-runtime
kdepimlibs-kio-plugins
kmail
latex-sanskrit
libaccounts-qt1:i386
libakonadi-calendar4
libakonadi-contact4
libakonadi-kabc4
libakonadi-kcal4
libakonadi-kde4
libakonadi-kmime4
libakonadi-notes4
libakonadi-socialutils4
libakonadiprotocolinternals1
libamd2.2.0
libass4:i386
libatkmm-1.6-1:i386
libaudclient2:i386
libaudcore1:i386
libavcodec53:i386
libavcodec54:i386
libavdevice53:i386
libavfilter3:i386
libavformat53:i386
libavformat54:i386
libavresample1:i386
libavutil51:i386
libavutil52:i386
libbaloocore4
libbaloofiles4
libbaloowidgets4
libbalooxapian4
libbinio1ldbl:i386
libboost-date-time1.53.0:i386
libboost-date-time1.54.0:i386
libboost-iostreams1.53.0:i386
libboost-iostreams1.54.0:i386
libboost-program-options1.53.0:i386
libboost-program-options1.54.0:i386
libboost-python1.53.0
libboost-python1.54.0:i386
libboost-regex1.53.0:i386
libboost-regex1.54.0:i386
libboost-signals1.53.0:i386
libboost-signals1.54.0:i386
libboost-system1.53.0:i386
libboost-system1.54.0:i386
libboost-thread1.53.0:i386
libboost-thread1.54.0:i386
libcairomm-1.0-1:i386
libcalendarsupport4
libcamel-1.2-43
libcdr-0.0-0
libcdr-0.1-1v5
libcdt4
libcgraph5
libcheese-gtk23:i386
libcheese7:i386
libclucene-contribs1:i386
libclucene-core1:i386
libcmis-0.3-3
libcmis-0.4-4
libcogl-pango12:i386
libcogl-pango15:i386
libcogl12:i386
libcogl15:i386
libcolamd2.7.1
libcwidget3
libdirac-encoder0:i386
libdns99
libdotconf1.0
libecal-1.2-18
libedata-cal-1.2-27
libedataserver-1.2-17
libept1.4.12:i386
libetpan15
libexchangemapi-1.0-0
libfm-gtk-bin
libfm-gtk3
libfm3
libgcj14:i386
libgconfmm-2.6-1c2
libgdome2-cpp-smart0c2a
libgif4:i386
libglademm-2.4-1c2a
libglibmm-2.4-1c2a:i386
libgnome-control-center1
libgnome-desktop-3-10:i386
libgnutlsxx27:i386
libgoa-1.0-0:i386
libgpgme++2
libgrantlee-core0
libgrantlee-gui0
libgraph4
libgsl0ldbl:i386
libgtkmm-2.4-1c2a:i386
libgtkmm-3.0-1:i386
libgvc5
libgvpr1
libharfbuzz0a:i386
libhdb9-heimdal:i386
libhpmud0
libical1
libicu48:i386
libicu52:i386
libid3-3.8.3c2a
libidl0:i386
libincidenceeditorsng4
libjffi-jni
libjsoncpp0v5:i386
libkabc4
libkactivities-models1
libkadm5clnt-mit8:i386
libkalarmcal2
libkcal4
libkcalcore4
libkcalutils4
libkdb5-6:i386
libkdb5-7:i386
libkdc2-heimdal:i386
libkdepim4
libkdepimdbusinterfaces4
libkdgantt2-0
libkexiv2-11
libkfbapi1
libkfilemetadata4
libkgapi2-2:i386
libkholidays4
libkimap4
libkldap4
libkleo4
libkmanagesieve4
libkmbox4
libkmime4
libkolab0
libkolabxml0
libkolabxml1
libkontactinterface4
libkpgp4
libkpimidentities4
libkpimtextedit4
libkpimutils4
libkresources4
libkscreen1
libksieve4
libksieveui4
libktnef4
libkubuntu0
libkyotocabinet16:i386
liblept4
libllvm3.4:i386
libmaa3:i386
libmagick++5:i386
libmagickcore5:i386
libmagickwand5:i386
libmailcommon4
libmailimporter4
libmailtransport4
libmapi0:i386
libmbim-glib0:i386
libmessagecomposer4
libmessagecore4
libmessagelist4
libmessageviewer4
libmicroblog4
libmng1:i386
libmowgli2:i386
libmspub-0.0-0
libmusicbrainz3-6
libmwaw-0.3-3v5
libmysqlclient18:i386
libnepomuk4
libnepomukcleaner4
libnepomukcore4abi1
libnepomukquery4a
libnepomukutils4
libnepomukwidgets4
libnettle4:i386
libntdb1:i386
libodfgen-0.1-1v5
libokularcore3
libokularcore4
libopenjpeg2:i386
libopenobex1
liborcus-0.6-0
libosmgpsmap-1.0-0:i386
libosmgpsmap2:i386
libpangomm-1.4-1:i386
libpcrecpp0:i386
libpgm-5.1-0:i386
libpimactivity4
libpimcommon4
libpod-latex-perl
libpodofo0.9.0
libpoppler43:i386
libpoppler44:i386
libpostproc52
libprison0:i386
libprocps0:i386
libprocps3:i386
libproxy1:i386
libpstoedit0v5
libpth20:i386
libpython3.3:i386
libpython3.
Re: [xubuntu-users] Upgrade from 15.10 to 16.04 got aborted
On Mon, Jan 02, 2017 at 12:56:57PM +, Peter Flynn wrote: > I just upgraded my Dell Latitude D810 from 15.10 to 16.04_01 using > update-manager (the last of my machines to update this cycle). All went > well except for two things: I recently upgraded a machine directly from 14.04.5 to 16.10 and ran into a lot of trouble along the way, ranging from dependency conflicts to pre-script failures to a cat stepping on the reset button while I was trying to fix things. According to my notes, I eventually got it all the way through, mainly by repeatedly forcing it every time it quit because of too many errors: sudo apt-get dist-upgrade -f and when it complained about broken dependencies I'd force that to continue as well: sudo apt-get install -f When it got stuck because of disagreement over which version of a package owns a file, I used this with the newer version of the package: sudo dpkg -i --force-overwrite /var/cache/apt/archives/PACKAGE.deb The pre-install script for ppp failed because of a "broken LSB comment header" or something like that. Basically the script it was complaining about in /etc/init.d was missing an "### END" comment (I just looked at other scripts to see what it should look like). After reboot it was using the old NVIDIA driver and only working at low resoution, but switching it to the new one fixed that. There was also a jpeg turbo package that kept failing to upgrade, but removing and re-installing worked. After all that the system seemed to think everything was in place, though I admittedly haven't used it much since then so I don't know how stable it really is. -Dave Dodge/dodo...@dododge.net -- xubuntu-users mailing list xubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
[xubuntu-users] Upgrade from 15.10 to 16.04 got aborted
I just upgraded my Dell Latitude D810 from 15.10 to 16.04_01 using update-manager (the last of my machines to update this cycle). All went well except for two things: a) as usual, it halted several times to ask if I wanted to keep the config file in etc/somewhere/or/other/something.rc, claiming it had "been modified". My apologies for not noting down each of these as they occurred, I'll do so next time. I clicked OK, because these are files that always get queried, that I have never touched (largely because I don't know what they are). Obviously Ubuntu believes these files to have been modified, so it must be using an incorrect test somewhere. It has no effect on operation anyway, so next time I really will note down the filenames...but I wondered if this is a common occurrence for others to have the installer query config files that had never been modified, claiming that they had? b) more serious, the installer got into a twisty loop claiming it couldn't install emacs24 and emacs-goodies-el because it couldn't configure xemacs21 and xemacs21-mule :-) I never use xemacs because it wrecks my head, my keybindings, and my scripts, but I suspect I *did* once install it many years ago in order to demonstrate what it was doing wrong...and then forgot to delete it. No problem as such: I deleted all xemacs* and emacs* packages and then reinstalled GNU Emacs once I had rebooted. BUT...the actual 16.04.01 install process treated this business with xemacs as so serious that it aborted the installation. Fortunately it seems to have been far enough down the road (very close to the end) that everything else appears to have worked, but I'm now using a LOT more disk space than before, and I suspect the cleanup of old 15.10 packages never occurred. How do I get that part of the install to run independently and finish up properly? ///Peter -- xubuntu-users mailing list xubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
