hi, On 2/6/19 1:09 AM, Sean Whitton wrote: > Hello Birger, > > There is a new release of sway out, and it moves swayidle and swaylock > into separate source packages. > > Those are all going to have to pass through NEW. Do you have time to > prepare separate source packages for all these? We might as well do it > now rather than later.
i've updated the package to 1.0-rc1 and pushed to the git repo. Changes since beta2: * New upstream release * Remove swaylock and swayidle: they are now separate packages * Clean up d/sway.install * Specify versioned build-dependencies and add libelogind and libsystemd build-dep * Remove references to swaygrab * Update Recommends and Suggests * Make versioned run dependency on libwlroots0 explicit There are new lintian warnings: I: sway: file-references-package-build-path usr/bin/sway I: sway: file-references-package-build-path usr/bin/swaybar I: sway: file-references-package-build-path usr/bin/swaybg I: sway: file-references-package-build-path usr/bin/swaymsg I: sway: file-references-package-build-path usr/bin/swaynag I think this refers to the occurrence of strings like: ../sway/commands/exec.c in the binaries. This is a relative path and the lintian warning is about reproducability, so i think this is a false negative? cheers, Birger
signature.asc
Description: OpenPGP digital signature