<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Feb 16, 2013 at 7:24 PM, Max Pyziur <span dir="ltr"><<a href="mailto:pyz@brama.com" target="_blank">pyz@brama.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Greetings,<br>
<br>
Currently, I'm on my third F18 experience:<br>
<br>
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).<br>
<br>
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).<br>
<br>
Experience #3 - upgrade a home-assembled dual core box from F17 to F18 using FedUp.<br>
<br>
After issueing the following command:<br>
fedup-cli --network 18 --debuglog /var/log/fedupdebug.log<br>
<br>
The following burp showed up:<br>
Traceback (most recent call last):<br>
File "/bin/fedup-cli", line 330, in <module><br>
main(args)<br>
File "/bin/fedup-cli", line 275, in main<br>
pkgs = download_packages(f)<br>
File "/bin/fedup-cli", line 57, in download_packages<br>
updates = f.build_update_transaction(<u></u>callback=output.<u></u>DepsolveCallback(f))<br>
File "/usr/lib/python2.7/site-<u></u>packages/fedup/download.py", line 185, in build_update_transaction<br>
(rv, msgs) = self.buildTransaction(<u></u>unfinished_transactions_check=<u></u>False)<br>
File "/usr/lib/python2.7/site-<u></u>packages/yum/__init__.py", line 1124, in buildTransaction<br>
(rescode, restring) = self.resolveDeps()<br>
File "/usr/lib/python2.7/site-<u></u>packages/yum/depsolve.py", line 897, in resolveDeps<br>
(checkdep, errormsgs) = self._processConflict(*<u></u>conflict)<br>
File "/usr/lib/python2.7/site-<u></u>packages/yum/depsolve.py", line 759, in _processConflict<br>
self._dscb_procConflict(po, niceformatneed)<br>
File "/usr/lib/python2.7/site-<u></u>packages/yum/depsolve.py", line 745, in _dscb_procConflict<br>
self.dsCallback.<u></u>procConflictPo(po, niceformatneed)<br>
File "/usr/lib/python2.7/site-<u></u>packages/fedup/callback.py", line 142, in procConflictPo<br>
self.log.debug('CONFLICT: %s → %s', po, formatted_conflict)<br>
NameError: global name 'po' is not defined<br>
<br>
<br>
General guidence in remarks retrieved Google say to wait for the FedUp<br>
upgrade, which is in testing, from fedup-0.7.2-1.fc17.noarch to<br>
<br>
Comments were found here:<br>
<a href="https://ask.fedoraproject.org/question/3519/error-update-from-fedora-17-to-fedora-18-via-fedup" target="_blank">https://ask.fedoraproject.org/<u></u>question/3519/error-update-<u></u>from-fedora-17-to-fedora-18-<u></u>via-fedup</a><br>
<br>
The latest Fedup in F17 test is:<br>
fedup-0.7.3-0.git20130128.<u></u>fc17.noarch.rpm 56.6 kB 1/31/13 11:37:00am<br>
<br>
Checking koji for project status, I see:<br>
<a href="http://koji.fedoraproject.org/koji/buildinfo?buildID=381043" target="_blank">http://koji.fedoraproject.org/<u></u>koji/buildinfo?buildID=381043</a><br>
<br>
Any further guidence from other users?<br>
<br>
Much thanks,<br>
<br>
Max Pyziur<br>
<a href="mailto:pyz@brama.com" target="_blank">pyz@brama.com</a><br>--<br>
users mailing list<br>
<a href="mailto:users@lists.fedoraproject.org">users@lists.fedoraproject.org</a><br>
To unsubscribe or change subscription options:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/users" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/users</a><br>
Guidelines: <a href="http://fedoraproject.org/wiki/Mailing_list_guidelines" target="_blank">http://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
Have a question? Ask away: <a href="http://ask.fedoraproject.org" target="_blank">http://ask.fedoraproject.org</a><br>
<br></blockquote></div><br>Sorry to hear it is not working out Max, I hope it will be addressed soon.<br><br>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.<br clear="all">
<div><br></div>-- <br><div dir="ltr">Best,<div><br></div><div>Christopher Svanefalk</div><div><br></div><div>mob: +46762628251</div><div>skype: csvanefalk</div><div>Resume (LinkedIn): <a href="http://www.linkedin.com/in/csvanefalk" target="_blank">http://www.linkedin.com/in/csvanefalk</a><br>
</div></div>
</div></div>