-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
names of flatpak packages are replaced by author #356
Comments
for a complete list of IDs, bauh could check if the name is unique and take one more part otherwise, etc. Maybe some common parts (like The above example |
It's a possibility, but as you mentioned the problem relies on the software packager as well. Doe the info ( |
in the info is no field providing an app name (apart from the Id). It's interesting, that But I would guess, the index is not up to date, but the version is 1.1.18 and it was Husky with 1.1.16, so enough time... |
surprisingly,
but
so all fields have the same value (for the same field), but the title is constructed differently. |
if I search |
exactly... bauh tries to delegate to the backend whenever possible (see https://github.com/vinifmor/bauh/blob/master/bauh/gems/flatpak/flatpak.py#L330). As you suggested: bauh could check if there are duplicated names among the results (if so, display the id instead to prevent confusion) |
the main point in my sentence was the difference between info from "search" and "installed", only the search result contains the package label. My idea was, bauh could use the search result instead of the info from the installed package. But the correct way would be to fix it on flatpak side... I guess at some point either the search results will also switch... or the installed packages will switch back. |
on my system I have 57 flatpak app packages
I count 25 packages that have the developer_name as the name in info and list commands (I think I missed one of them). This command lists the names for these packages:
[EDIT: there were 27 lines, but these come from 25 files, because the same file seems to be located inside the installation:
Maybe it could contain multiple components, I guess then the type=desktop(-application) component would be the one to choose. A command like:
shows a lot more output, because the name may be given for each supported language. The *.desktop file could also be a good candidate. It should contain the name relevant to a user. And some of the metainfos also contain the developers. |
the path must be exact, because name can also be an element below another one:
|
and this lists all names: assuming the first Name entry is the main entry.
|
I added an issue to the flatpak repo: |
the issue is already solved in flatpak: From my flatpak issue:
My tests confirmed that it is dependent on the flatpak version at installation time of a package. |
Hi @hg42 sorry for the late response. Thank you for reporting the issue there (and here as well). |
LOL, no response was necessary :-) The whole issue was kind of vaporware. |
Describe the bug
The name column of many updated flatpaks now contains the author.
I think, it's not really a bug of bauh, but the strategy to determine a name seems to rely on something undefined.
I"m not sure why this changes, but it's happening with lots of flatpak packages.
E.g. the
Flatseal
package changed it's name toMartin Abente Lahaye
when updated to 2.1.2 (from 2.1.1).I see the same change in
flatpak list
:Unfortunately the ID isn't structured consistently.
Usually the package name is the last one, but there are packages like
org.gnome.Platform
where this is not exactly the case.At least something like
Platform
is not a good name,gnome
would be the better name here.Actually only the full ID would be sufficient for all cases, because even if the last part is the usual package name, it could be duplicated, e.g. for a different platform.
e.g.
org.gnome.Platform.XXX
could also exist asorg.kde.Platform.XXX
or similar.While I see this as a problem of those packages (or how they are created), it's difficult to see which package it is, if I don't know the author and the description is not sufficient.
Software Environment
bauh version: 0.10.7
O.S: Debian
Installation method: appimage
The text was updated successfully, but these errors were encountered: