On Tue, 2012-05-22 at 11:31 +0200, Mateusz Marzantowicz wrote: > Adam Williamson: > > On Tue, 2012-05-22 at 09:07 +0200, Mateusz Marzantowicz wrote: > > > >> I've played just with Fedora 17 beta Live for a while and it looks like > >> everything is working out of the box. I'm beginning to think the problem > >> was cause by updates of samba related packages in recent testing version > >> of Fedora. It might not be worth to drill this deeper. > > Actually, if that were the case, it would be worth it, because the point > > of updates-testing is to catch problematic updates! So you could try > > rolling back related packages and see if they change anything, I > > suppose. > Could you please point me to some information about tracking such things > in Fedora? I'm evaluating switching from other Linux distro to Fedora > and I have only a minor experience with yum and Fedora QA process but > I'm willing to check if there is something I can find about this problem. Well, you can track the update history of a package just by going to https://admin.fedoraproject.org/updates/ and searching for the package by name (note SRPM name, not binary RPM name). Each update page has links to the Koji (buildsystem) page for the build, from which you could download older builds, and install them with 'yum downgrade XXX.rpm' to try them out. Just try downgrading possibly-related packages and see if it starts working. You can use 'yum history' to see what packages were changed in a given update, if you can narrow it down to a specific update that you think broke things: 'yum history list' gives a list of yum transactions, and 'yum history info (number)' will give you the packages that changed in a specific transaction. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
