Your message dated Fri, 07 Jun 2024 17:52:51 +0000
with message-id <[email protected]>
and subject line Bug#1072542: Removed package(s) from unstable
has caused the Debian Bug report #1050931,
regarding cutefish-core: please provide a cutefish-portals.conf for
xdg-desktop-portal
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1050931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050931
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cutefish-core
Severity: normal
Tags: trixie sid
User: [email protected]
Usertags: portals.conf
xdg-desktop-portal 1.17.x introduces a new way to select which portals will
be used for which desktop environments, modelled on mimeapps.list:
- each desktop environment should provide a file like
/usr/share/xdg-desktop-portal/cutefish-portals.conf
- the filename is ${DESKTOP}-portals.conf where ${DESKTOP} is the desktop
environment's entry in $XDG_CURRENT_DESKTOP (the same as the DesktopNames
from /usr/share/{x,wayland-}sessions/*.desktop), folded to lower case
- sysadmins and users can override this via files named portals.conf or
${DESKTOP}-portals.conf in various locations like /etc/xdg-desktop-portal
and ~/.config/xdg-desktop-portal
Please see portals.conf(5) or its source code
https://github.com/flatpak/xdg-desktop-portal/blob/main/doc/portals-conf.rst
for full details.
If I'm reading its code correctly, I think Cutefish intends to set
XDG_CURRENT_DESKTOP to "Cutefish"? (But if I'm wrong, please adjust my
suggestions accordingly.)
As a backwards-compatibility mechanism, x-d-p will fall back to trying to
guess the most appropriate portals from the portals' deprecated UseIn=
fields, but it will log warnings when it does that, and anyway Debian
doesn't currently ship any portal backends that are flagged as suitable
for Cutefish. Please add a cutefish-portals.conf to tell x-d-p
more explicitly what backends Cutefish is meant to be using by default.
At the moment x-d-p is hard-coded to fall back to the x-d-p-gtk backend
if nothing more suitable is found, but that's a short-term hack which
we should remove before trixie.
For example, if the intention is that Cutefish should be using the
x-d-p-gtk backend, the way to write that would be:
[preferred]
default=gtk;
The desktop environment (either cutefish-core or some larger
metapackage) should probably also have a Recommends, or at least a
Suggests, on whatever portals would be most appropriate for it.
Thanks,
smcv
--
This is part of a mass bug filing:
https://lists.debian.org/debian-devel/2023/08/msg00311.html
--- End Message ---
--- Begin Message ---
Version: 0.8-2+rm
Dear submitter,
as the package cutefish-core has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1072542
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
