Verfasst von jah am So, 02/06/2022 - 11:22
[trisquel-app-install] upgrade encountered python error
Projekt: | Trisquel |
Version: | 9.0 |
Komponente: | Packages |
Kategorie: | Fehlerbericht |
Priorität: | normal |
Zugewiesen: | Ark74 |
Status: | closed |
Gehe zu:
Beschreibung
$ sudo aptitude full-upgrade
The following packages will be upgraded:
trisquel-app-install
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/607 kB of archives. After unpacking 158 kB will be used.
Do you want to continue? [Y/n/?] y
(Reading database ... 318902 files and directories currently installed.)
Preparing to unpack .../trisquel-app-install_0.6.4_all.deb ...
Unpacking trisquel-app-install (0.6.4) over (0.6.0-3) ...
Setting up trisquel-app-install (0.6.4) ...
Caching application data...
Traceback (most recent call last):
File "/usr/sbin/update-app-install", line 6, in
main()
File "/usr/lib/python3/dist-packages/AppInstall/update.py", line 111, in main
generate_menu_cache(options.desktop_dir, options.cache_dir)
File "/usr/lib/python3/dist-packages/AppInstall/update.py", line 72, in generate_menu_cache
menu.createMenuCache(cache_dir)
File "/usr/lib/python3/dist-packages/AppInstall/CoreMenu.py", line 98, in createMenuCache
self._populateFromEntry(menu)
File "/usr/lib/python3/dist-packages/AppInstall/CoreMenu.py", line 114, in _populateFromEntry
for entry in node.getEntries(show_hidden=True):
TypeError: getEntries() got an unexpected keyword argument 'show_hidden'
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.2+9.0trisquel1) ...
Processing triggers for libglib2.0-0:amd64 (2.56.4-0ubuntu0.18.04.9) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Current status: 0 (-1) upgradable.
- Anmelden oder Registrieren um Kommentare zu schreiben
Thank for reporting.
Seems like latest changes from upstream broke our customization, I'll take a look.
Regards
Now fixed.
Please update using normal update-manager before full-upgrade.
Regards.
My bad, I was fixing update-manager. Reopening.
Fixed on latest update.
Thanks for reporting.
Automatically closed -- issue fixed for 2 weeks with no activity.