Re: dnf is "broken"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Kevin,

did you try a 'dnf clean all'?

Then you didn't do any 'sudo pip intall ' on your machine or set the
PYTHONPATH? You can easily break your system whide packages by dooing
this.

Alexis.
Le lundi 31 décembre 2018 à 00:13 -0500, Kevin Cummings a écrit :
> I last updated my laptop on 12/26.  It is running fc28.x86_64
> 
> Today I tried to run dnf update:
> 
> > # dnf update
> > Traceback (most recent call last):
> >   File "/usr/bin/dnf", line 58, in <module>
> >     main.user_main(sys.argv[1:], exit_code=True)
> >   File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line
> > 179, in user_main
> >     errcode = main(args)
> >   File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 64,
> > in main
> >     return _main(base, args, cli_class, option_parser_class)
> >   File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line 99,
> > in _main
> >     return cli_run(cli, base)
> >   File "/usr/lib/python3.6/site-packages/dnf/cli/main.py", line
> > 115, in cli_run
> >     cli.run()
> >   File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line
> > 1015, in run
> >     self._process_demands()
> >   File "/usr/lib/python3.6/site-packages/dnf/cli/cli.py", line 768,
> > in _process_demands
> >     load_available_repos=self.demands.available_repos)
> >   File "/usr/lib/python3.6/site-packages/dnf/base.py", line 475, in
> > fill_sack
> >     self._add_repo_to_sack(r)
> >   File "/usr/lib/python3.6/site-packages/dnf/base.py", line 147, in
> > _add_repo_to_sack
> >     load_updateinfo=True)
> > _hawkey.Exception: repo_add_solv() has failed.
> 
> Is it Fedora 28?  dnf?  some dnf dependency?  or my laptop?  that is
> broken?
> 
> -- 
> Kevin J. Cummings
> cummings@xxxxxxxxxxxxxxxxxx
> cummings@xxxxxxxxxxxxxxxxxxxxxxx
> kjchome@xxxxxxxxxx
> Registered Linux User #1232 (http://www.linuxcounter.net/)
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux