:: Re: [devuan-dev] Why is mate-power-…
Forside
Slet denne besked
Besvar denne besked
Skribent: Michael Siegel
Dato:  
Til: devuan-dev
Emne: Re: [devuan-dev] Why is mate-power-manager banned?
I'd say it's a consistency issue. A package should never depend on
anything that you can definitely not install (because it's not in the
repos), should it?

Maybe AntoFox's version was not yet available when ASCII was released or
slipped through somehow. I don't know.


msi

Am 23.06.2018 um 22:53 schrieb Svante Signell:
> Michael,
>
> Yes, it depends on policykit-1 | systemd.
> But as you know both policykit-1 is available :)
> And as I wrote, it works fine in my ASCII-mate installation!
> Why bother about a second dependency on systemd?
> AntoFox??
>
> On Sat, 2018-06-23 at 22:34 +0200, Michael Siegel wrote:
>> I think that's because it depends on either systemd or consolekit.
>> The modified package from AntoFox will most certainly have this
>> dependency alternative removed and could therefore be integrated into
>> Devuan without problems, I guess.
>>
>> msi
>>
>> Am 23.06.2018 um 22:21 schrieb Svante Signell:
>>> Hi, that package is still banned. Why?
>>>
>>> On Tue, 2018-06-19 at 08:37 +0200, Svante Signell wrote:
>>>> Hi,
>>>>
>>>> looking at https://pkgmaster.devuan.org/bannedpackages.txt I find
>>>> that
>>>> mate-power-manager is banned:
>>>> ascii-backports,mate-power-manager
>>>> ascii,mate-power-manager
>>>> beowulf,mate-power-manager
>>>> jessie,mate-power-manager
>>>> unstable,mate-power-manager
>>>>
>>>> I have compiled and run 1.16.2-1+deb9u1 from stretch on ASCII and
>>>> it
>>>> works fine.
>>>> So at least
>>>> ascii-backports,mate-power-manager
>>>> ascii,mate-power-manager
>>>> should be removed.
>>>>
>>>> There is also a newer version 1.18.1-3~bpo9+1 from stretch-
>>>> backports
>>>> available but that version requires upgrading of mate-common and
>>>> libmate-panel-applet-dev to 1.18.1-3~bpo9+1, which would need an
>>>> upgrade of the whole mate-desktop-environment, and that is not
>>>> possible
>>>> currently. I have not investigated too deep into that matter
>>>> though.
>>>
>>> _______________________________________________
>>> devuan-dev internal mailing list
>>> devuan-dev@???
>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
>>>
>>
>> _______________________________________________
>> devuan-dev internal mailing list
>> devuan-dev@???
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
> _______________________________________________
> devuan-dev internal mailing list
> devuan-dev@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev
>