Re: [DNG] Devuan Jessie -> ASCII successful upgrade reports
On Sat, Dec 23, 2017 at 05:46:05PM -0600, Don Wright wrote: > Might as well start a thread for those of us who /didn't/ have significant > issues upgrading from Devuan Jessie to ASCII as our part of the sprint, just > to provide some balance to the problem-oriented bug database and other > reports. I'll reply separately with my own narrative. I copied my jessie system and got it to run just in case, but I haven't had to go back to it. No problems upgrading, except I had to dist-upgrade twice to get everything done. Only one package broke -- lprng. It ended up bing only partially installed. Its job is to talk to my printer. But, partially installed or not, it seems to work, and I have no difficulty printing. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] initial elogind package ready / RFC
On Sat, Jan 06, 2018 at 04:41:57PM +0300, Hleb Valoshka wrote: > On 2018-01-05 20:08, Andreas Messer wrote: > > If anyone like to try it out, checkout branch suites/experimental > > from https://git.devuan.org/amesser/elogind.git and build with > > debbuild. This is my first package, comments are welcome. (Note: in the comments below, my opinions are those of a Debian Developer who's not active in Devuan. I'm these days the second most active package reviewer, though, so probably they're worth some heed. I did not even look at the package yet, though.) > -> d/changelog > elogind (234.4-devuan1) experimental; urgency=medium > > This package is native to Devuan, so it's version should be 234.4-1 or > 234.4-1~exp1. I believe that it's still better to mark it as Devuan specific, especially that it's wanted for Debian as well. Less confusion this way. > -> d/control & d/libelogind-data.install > > libelogind-data contains only l10n files, so there is no need for a > separate package, merge libelogind-data into libelogind. It's a bad idea to mix arch-indep files with arch-specific. Even worse, if this library is to be ever used by programs other than elogind itself (and if it were not, it shouldn't be a library), it would make it impossible to multiarchize it. > And I suppose there is no need to check for upstart, abandoned and > unsupported afair in Dev1 sustem. And in any maintained derivative. (I'd comment more once I get around to looking at the package itself.) Meow! -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable And Non-Discriminatory prices. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] consolekit2
On Sat, Jan 06, 2018 at 08:46:03PM +0300, Hleb Valoshka wrote: > Do we need consolekit2 packaged? I think yes. consolekit (without 2) seems to have issues with ck-lauch-session in combination with displaymanagers like sddm. This was actually the reason for me to package elogind in the hope it will work better with sddm. But in order for elogind tobe useful, other packages need to be adjusted (udisks...) These issues seem to be fixed in consolekit2. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] initial elogind package ready / RFC
On Sat, Jan 06, 2018 at 04:41:57PM +0300, Hleb Valoshka wrote: > On 2018-01-05 20:08, Andreas Messer wrote: > > If anyone like to try it out, checkout branch suites/experimental > > from https://git.devuan.org/amesser/elogind.git and build with > > debbuild. This is my first package, comments are welcome. First of all thank you for your elaborate review. I agree with most of your comments and adjusted accordingly. > [...] > dh $@ --builddirectory=build --with autoreconf --parallel > ``` > > Remove `--builddirectory=build` as you set it in override_dh_auto_configure > and --parallell, afaik dh is clever enough to enable it automatically. > [...] `--builddirectory` is needed for all dh_* commands. Otherwise they don't know where the build folder is and wont find the files. `--parallel` is on by default for debian/compat>=10 only. Currently I don't see any need to require debhelper>=10 when 9 is sufficient. I also found a workaround to shutdown/reboot and mounting issues with KDE5/Gnome 3: Just don't enable elogind's PAM module. In that case ck-list-session shows the session again and everything works as expected. Of course, the session is not registered with elogind now. I tried reordering pam_elogind.so and pam_ck_connector.so before that but this didn't help. For me this is very obscure - why does Gnome 3 depend on logind if it works without having the session registered with logind? Anyway, I have now changed the libpam-elogind to disabled the pam module by default. Can be manually enabled with `pam-auth-update`. cheers, Andreas -- gnuPG keyid: 8C2BAF51 fingerprint: 28EE 8438 E688 D992 3661 C753 90B3 BAAA 8C2B AF51 signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Meltdown and linux kernel KPTI patch
On Fri, Jan 05, 2018 at 09:52:48PM +0100, viverna wrote: > When the KPTI patch will be in ascii and jessie? > With AMD processor is possible to ignore patch? The patched kernel is already in ascii, if you have ascii-security enabled, and comes directly from stretch. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] consolekit2
Do we need consolekit2 packaged? I've spent a few hours to make initial packaging and installed it instead of old consolekit. So far so good, I'm able suspend my pc and mount usb drives from Thunar. If dev1 needs it I can afford a bit more time to polish it and prepare for uploading. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] initial elogind package ready / RFC
On 2018-01-05 20:08, Andreas Messer wrote: > If anyone like to try it out, checkout branch suites/experimental > from https://git.devuan.org/amesser/elogind.git and build with > debbuild. This is my first package, comments are welcome. -> d/changelog elogind (234.4-devuan1) experimental; urgency=medium This package is native to Devuan, so it's version should be 234.4-1 or 234.4-1~exp1. -> d/control & d/libelogind-data.install libelogind-data contains only l10n files, so there is no need for a separate package, merge libelogind-data into libelogind. Build-Depends: debhelper, Add minimal debhelper version (>= 9) as in d/compat you have 9. -> d/elogind.init A lot of `--pidfile /run/elogin.pid' you'd better define a variable ELOGIND_PID=elogin.pid and use it instead. run_by_init() is not used anywhere. And I suppose there is no need to check for upstart, abandoned and unsupported afair in Dev1 sustem. -> d/libpam-elogind.postinst Extra newlines. -> d/libpam-elogind.prerm Extra newlines. "pam-auth-update --package --remove consolekit" s/consolekit/elogind/ -> d/elogind.install Lines looking like some/dir/* can be simplified just to some/dir/ -> libelogind-dev.install add lib/*/libelogind.so remove all *.la files usr/include/elogind/* + usr/include/elogind/systemd/* = usr/include/elogind/ -> d/rules DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) Can be safely removed as you depend on debhelper >= 9 --enable-kdbus \ KDBus is not here, please remove. ``` autoreconf: ./autogen.sh override_dh_autoreconf: dh_autoreconf debian/rules -- autoreconf ``` It doesn't look that you need to run autogen.sh, so these targets can be safely removed. In case you really need to run autogen.sh, use the following: ``` override_dh_autoreconf: dh_autoreconf ./autogen.sh ``` ``` dh $@ --builddirectory=build --with autoreconf --parallel ``` Remove `--builddirectory=build` as you set it in override_dh_auto_configure and --parallell, afaik dh is clever enough to enable it automatically. > There are some things with package file structure which might > be improved. I'm building elogind with the options recommended > in autogen.sh. But this implies that commands and libs are > installed to /bin and /lib and some very obscure thing, elogind > itself is installed to /lib/elogind/elogind. I suggest to install > it to /usr/bin, /usr/sbin and /usr/lib as usual and dropping that > weird /lib/elogind folder? Oppinions? Agree, but lib/elogind/elogind-cgroups-agent should go to /usr/lib/elogind/elogind-cgroups-agent ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
