On Sat, Feb 16, 2013 at 7:24 PM, Max Pyziur <pyz@xxxxxxxxx> wrote:
Greetings,
Currently, I'm on my third F18 experience:
Experience #1 - off-lease Dell D630 dual-core laptop w/ no pre-installed OS, installed from DVD. The installation went smoothly; the issues that remain are getting co-ordinated postgis 2.0/postgresql 9.2 packages, and some Xfce UI considerations (the former means that there is a frail eco-system for working on F18 PostGIS 2.0 things, while the latter is an RTFM thing).
Experience #2 - upgrade creaky and (relatively) slow Dell 600m Inspiron Laptop from F17 to F18. FedUp worked smoothly, but since this was over a DSL network connection, it took some time. Same outstanding issues as #1 (PostGIS/GDAL/Postgresql software ecosystem is shaky in F18; and UI Xfce annoyances).
Experience #3 - upgrade a home-assembled dual core box from F17 to F18 using FedUp.
After issueing the following command:
fedup-cli --network 18 --debuglog /var/log/fedupdebug.log
The following burp showed up:
Traceback (most recent call last):
File "/bin/fedup-cli", line 330, in <module>
main(args)
File "/bin/fedup-cli", line 275, in main
pkgs = download_packages(f)
File "/bin/fedup-cli", line 57, in download_packages
updates = f.build_update_transaction(callback=output.DepsolveCallback(f))
File "/usr/lib/python2.7/site-packages/fedup/download.py", line 185, in build_update_transaction
(rv, msgs) = self.buildTransaction(unfinished_transactions_check=False)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 1124, in buildTransaction
(rescode, restring) = self.resolveDeps()
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 897, in resolveDeps
(checkdep, errormsgs) = self._processConflict(*conflict)
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 759, in _processConflict
self._dscb_procConflict(po, niceformatneed)
File "/usr/lib/python2.7/site-packages/yum/depsolve.py", line 745, in _dscb_procConflict
self.dsCallback.procConflictPo(po, niceformatneed)
File "/usr/lib/python2.7/site-packages/fedup/callback.py", line 142, in procConflictPo
self.log.debug('CONFLICT: %s → %s', po, formatted_conflict)
NameError: global name 'po' is not defined
General guidence in remarks retrieved Google say to wait for the FedUp
upgrade, which is in testing, from fedup-0.7.2-1.fc17.noarch to
Comments were found here:
https://ask.fedoraproject.org/question/3519/error-update-from-fedora-17-to-fedora-18-via-fedup
The latest Fedup in F17 test is:
fedup-0.7.3-0.git20130128.fc17.noarch.rpm 56.6 kB 1/31/13 11:37:00am
Checking koji for project status, I see:
http://koji.fedoraproject.org/koji/buildinfo?buildID=381043
Any further guidence from other users?
Much thanks,
Max Pyziur
pyz@xxxxxxxxx
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Sorry to hear it is not working out Max, I hope it will be addressed soon.
Is there a particular reason you feel you need to go through the trouble to upgrade to F18 though? I was planning to, but after all the horror stories that have made the rounds here, I am seriously considering waiting for F19 unless I absolutely need F18. At the moment, I have F17 running as solid as a rock on my box, and there is little reason to change that.
Best,
Christopher Svanefalk
mob: +46762628251
skype: csvanefalk
Resume (LinkedIn): http://www.linkedin.com/in/csvanefalk
-- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
