On 02/04/16 07:58, Boruch Baum wrote:
> On 04/01/2016 02:31 PM, Adam Borowski wrote:
>> On Fri, Apr 01, 2016 at 12:58:23PM -0400, Boruch Baum wrote:
>>> Just looking at issues with the devuan default desktop's screensave, and
>>> its config file: ~/.xscreensaver file, posted here for the attention of
>>> the maintainers and the interest of members of the list.
>>>
>>> 1] Obnoxious nag messages - All logins to the devuan default desktop
>>> begin with not one but two separate nag messages from xscreensaver. The
>>> first "warns" the user that the version is out of date. The second
>>> "warns" the user that the sysadmin is doing a dis-service by keeping it
>>> out of date.
>>>
>>> 2] forced config screen - after the two obnoxious nag messages, one is
>>> forced to be confronted with the xscreensaver customization screen
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819703
>>
>> It's a time bomb by xscreensaver's upstream author. And like micq before,
>> it looks like xscreensaver needs to be replaced or forked. Obviously, using
>> gnome-screensaver is not an option as that pulls in a good part of Gnome3
>> including systemd.
>>
>
> I'm not one to jump to that kind of conclusion before looking at some
> alternatives first. It's possible that the solution has already been
> provided by the author - I haven't checked the packages MAKEFILE for
> possible build-time config options, or other compile-time options.
> Lacking that, its also possible and may be appropriate to use debian's
> 'quilt' system to patch the upstream. It's also possible that just
> contacting the author and making a request will effect a change.
>
gnome-screensaver depends on libsystemd0 directly as well as on
gnome-session-bin which also depends on libsystemd0

Are you volunteering to repackage them?

With regards to packaging core gnome packages, I have a current issue
with tracking all the from debian in our preferred git workflow because
it uses subversion for just the /debian folder of each package.

This means importing to git in a way that we are able to track both the
upstream source and debians vcs is hard. I have almost sorted the plan
for doing that so we can have a good process that will be easier to work
with in the long term and we will retain at our fingertips the full
development history from both upstream and debian.

regards,
    Daniel
-- 
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722