onefang | I'm about to update or create a new PGP key. My old one is truly ancient, and was never really used. The main email address on it is obsolete. It did have the advantage of having been signed by some well known people. | 14:58 |
---|---|---|
onefang | Do we have any best practices? My PGP knowledge is about as old as that key. lol | 14:58 |
onefang | 2004, it's older than I thought. lol | 15:13 |
fsmithred | 4096 RSA | 15:27 |
fsmithred | sign it with your old key to keep the web of trust intact | 15:28 |
fsmithred | you can edit a key to change the email address | 15:28 |
onefang | Cool, thanks. | 15:29 |
fsmithred | I need to find out how to get the key to do encrypted email. In the past, I don't recall having to do anything special for that. But current key only does signing. | 15:30 |
onefang | I'm using NeoMutt these days, it says it supports that sort of thing. I'l find out sooner or later. | 15:31 |
fsmithred | yeah, the problem isn't the mail client, it's the key | 15:31 |
fsmithred | another recommended practice is to have one key that you only use to sign subkeys, and you keep the main key locked away in a safe place. | 15:34 |
fsmithred | along with your revocation certificates | 15:35 |
bgstack15 | I am finally getting around to trying a local debuild of lightdm with the applied workarounds | 18:51 |
bgstack15 | Two lightdm results found: https://git.devuan.org/search?utf8=%E2%9C%93&search=lightdm&group_id=&project_id=&repository_ref= | 18:52 |
bgstack15 | So I just grabbed the salsa one... | 18:52 |
LeePen | I would start from https://git.devuan.org/devuan-packages/lightdm | 19:09 |
bgstack15 | That one's 5 years old; shall I try to merge in everything from salsa, or how shall I proceed? | 19:09 |
LeePen | It is very out of date, so merge current Debian unstable/testing: 1.26.0-7 | 19:10 |
bgstack15 | also quilt is being quite the pain... | 19:10 |
LeePen | In what way? | 19:12 |
bgstack15 | After "quilt pop -a" and make a new patch with quilt new 99_devuanize.patch, quilt edit the files, quilt refresh, | 19:13 |
bgstack15 | quilt push -a (reverse the push and pops here) | 19:13 |
bgstack15 | and then try to debuild, I get a fuzz error | 19:14 |
bgstack15 | dpkg-source: info: if patch '99_devuanize.patch' is correctly applied by quilt, use 'quilt refresh' to update it | 19:14 |
bgstack15 | dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/99_devuanize.patch/ --reject-file=- < lightdm.orig.KRwRpa/debian/patches/99_devuanize.patch subprocess returned exit status 1 | 19:14 |
bgstack15 | dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 | 19:14 |
bgstack15 | it's probably related to the fact that patch 05_debianize-pam.patch edits the same two files... but I wrote my patch for after 05_debianize in the series. | 19:15 |
LeePen | Have you updated to current Debian yet? | 19:15 |
LeePen | I would do that first and do the patching right at the end. | 19:16 |
bgstack15 | That was on a fresh branch from branch debian/master | 19:17 |
LeePen | Also it is worth setting up git-buildpackage and pbuilder. | 19:17 |
LeePen | That is the way jenkins does the final builds and it keeps your tree clean. | 19:17 |
bgstack15 | I know extremely little about how Debian packages are actually built, so I'm going to have to learn about these new terms. | 19:18 |
LeePen | I was thinking of writing a devuan packaging guide. Maybe you could be the target tester? | 19:19 |
bgstack15 | sure | 19:19 |
LeePen | There are lots of ways to build. debuild, sbuild, pbuilder buildd or just ./debian/rules. | 19:20 |
bgstack15 | I know debuild. | 19:20 |
LeePen | git-buildpackage ensures the tree is clean with no extraneous patches. | 19:20 |
LeePen | And it is what our jenkins pipeline uses, so it will be bets to learn that. | 19:21 |
LeePen | I'll get something outlined this evening. | 19:21 |
bgstack15 | but a lower-level question that is hopefully within my current ability to understand the answer: | 19:22 |
LeePen | Maybe have a read of this. https://wiki.debian.org/PackagingWithGit | 19:22 |
bgstack15 | the above git.devuan.org link for lightdm, has only 4 commits total, and not even on top of the then-current debian branch. Did you want me to git rebase to get those four commits on top of the current debian/master branch from salsa? | 19:23 |
bgstack15 | Also, will my lack of thorough programming understanding be a hindrance to my goal of packaging up current lightdm with the two patched files we want? | 19:24 |
LeePen | Looking at those commits, we will need something like the d/control changes in f57ed15. | 19:25 |
LeePen | But even they are out of date. | 19:25 |
LeePen | So you could just branch from debian/1.26.0-7. | 19:26 |
LeePen | The branch should be suites/unstable | 19:26 |
LeePen | We only need a PAM config change, so I think you will be fine. | 19:27 |
bgstack15 | The release notes shared during the Meet (https://termbin.com/260r) show pam, and lightdm.conf workarounds | 19:29 |
bgstack15 | Would you like me to only patch the pam config change? | 19:29 |
LeePen | Yes, but they are either/or. | 19:29 |
bgstack15 | OK, I didn't read the Debian bug reports, so I didn't realize they were connected. | 19:30 |
LeePen | I suggest branch from debian/1.26.0-7. Get your build environment working so you can build that version with gbp and pbuilder and then we can work on the changes. | 19:31 |
LeePen | I am afk now. | 19:31 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!