Processed: Re: Bug#1038630: cinnamon: depends on obsolete policykit-1-gnome

[Debian Bug Tracking System]

tags -1 - fixed-upstream

Bug #1038630 [cinnamon] cinnamon: depends on obsolete policykit-1-gnome
Removed tag(s) fixed-upstream.

[Fabio Fantoni]

Control: tags -1 - fixed-upstream

the upstream bug linked was closed 2 years ago when upstream had chosen
to continue to use policykit-1-gnome "as solution" but now that
policykit-1-gnome will be remove can't be considered as "fixed upstream"

[Debian Bug Tracking System]

tags -1 + fixed-upstream

Bug #1038630 [cinnamon] cinnamon: depends on obsolete policykit-1-gnome
Added tag(s) fixed-upstream.

[Debian Bug Tracking System]

tag -1 pending

Bug #1038630 [cinnamon] cinnamon: depends on obsolete policykit-1-gnome
Added tag(s) pending.

[Fabio Fantoni]

Control: tag -1 pending

Hello,

Bug #1038630 in cinnamon reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/cinnamon-team/cinnamon/-/commit/ea8cfe84662590cb84c558291db23eee86689a15

------------------------------------------------------------------------
d/control: remove policykit-1-gnome from deps

6.4 use internal polkit agent by default for all sessions

Closes: #1038630
------------------------------------------------------------------------

(this message was generated automatically)

[Debian Bug Tracking System]

Your message dated Sun, 19 Jan 2025 18:04:31 +0000
with message-id <E1tZZex-00Buec-***@fasolo.debian.org>
and subject line Bug#1038630: fixed in cinnamon 6.4.5-1
has caused the Debian Bug report #1038630,
regarding cinnamon: depends on obsolete policykit-1-gnome
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 ***@bugs.debian.org
immediately.)