> From: "Tonet Jallo" <tonet666p@xxxxxxxxx> > In Peru i have the same problem, my ISP is implememtating NAT 3 in its > networks and i found more dnf hangs in some networks with NAT 3, but when i > try use dnf in other ISP network dnf works perfectly, the degmbug results > say some thing like "banned client by web server" but i not remember > exactly. > > On Tue, Jun 9, 2015 at 9:41 AM, Richard Fearn < richardfearn@xxxxxxxxx > > wrote: > > I've experienced the same problem with a F22 VM running in VirtualBox. > > (Is yours a VM?) Disabling IPv6 seemed to help a bit, but the problem > > never went away completely. > > > > There a few bugs that talk about similar issues, e.g.: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1206878 > > https://bugzilla.redhat.com/show_bug.cgi?id=1214538 > > > > There are various ideas out there for how to fix this, e.g. `dnf clean > > all`, or using LIBREPO_DEBUG=1. But none of these worked definitively > > for my VM. > > > > Regards, > > > > Richard Hi, these bugs should be fixed in dnf-1.0.1-2.fc22 (in testing now). Can anyone of you confirm? > From: "Zdenek Kabelac" <zkabelac@xxxxxxxxxx> > > count me in - > > https://bugzilla.redhat.com/show_bug.cgi?id=1223803 > > Zdenek Zdenek, this stops during transaction -> different bug. I am assuming this is packaging problem. Probably scriplet of some package is executing rpm inside and lead to deadlock. Can you see any of these scriplets in the last installed package in the transaction? Thanks, Honza -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
