LeePen | Centurion_Dan: thanks very much. | 00:23 |
---|---|---|
onefang | Centurion_Dan: on this side of the planet, we are always a day early. B-) | 02:07 |
onefang | Though I can't turn up to meetings these days, it conflicts with some of my volunteer work. | 02:10 |
golinux | <Centurion_Dan> golinux: It looks ok, but it would be nice to see it in context with the rest of the theme. | 07:01 |
golinux | Well, here's my first stab at it: https://dev1galaxy.org/files/462B25.png | 07:02 |
golinux | Will look better when the icons are recolored and there's a proper title bar. | 07:04 |
Centurion_Dan | onefang: pity... it is my volunteer work... | 07:59 |
Centurion_Dan | LeePen: I've been asking if libelogind0 is abi compatible with libsystemd0. If it is, then debian doesn't need to build a patched polkit at all, and instead replaces libsystemd0 with libelogind0, and for Devuan we do the same. So can you patch your latest elogind package to create symlinks from libelogind0 to libsystemd0 paths and setup replaces, conflicts etc? | 09:22 |
golinux | Centurion_Dan: The stock gnome icons look quite nice on Clearlooks-Phenix-Cinnabar until I can recolor them. | 09:32 |
Centurion_Dan | cool | 09:32 |
KatolaZ | I see you've been busy :) | 09:53 |
KatolaZ | good stuff :) | 09:53 |
KatolaZ | Centurion_Dan: I guess that's not gonna happen in Debian | 09:54 |
_moep_ | o/ | 09:54 |
KatolaZ | why should systemd packagers take the burden of packaging elogind? | 09:54 |
Centurion_Dan | they don't. but libelogind0 is supposedly abi compatible, so we can use it as a replacement for libsystemd0. | 10:02 |
KatolaZ | as we | 10:03 |
Centurion_Dan | for Debian libelogind can replace libsystemd where they are not using systemd as init. | 10:03 |
KatolaZ | Centurion_Dan: in the end libelogind IS libsystemd... | 10:04 |
Centurion_Dan | it's not, it uses the ABI, but the api is different. | 10:05 |
Centurion_Dan | it handles some things differently. | 10:05 |
Centurion_Dan | but because it's abi compatable we can simply setup symlinks to the locations of libsystemd0 and put a provides, conflcts and breaks libsytemd0, as an alternative (or replacement) for libsystemd0 (which we then could ban too). | 10:08 |
Centurion_Dan | elogind does the work... | 10:09 |
KatolaZ | let's build it for experimental then | 10:11 |
Centurion_Dan | I'll see if I can prod LeePen to do it, seen he has just today uploaded and built a new elogind for experimental ;-) | 10:17 |
KatolaZ | yeah I saw that :) | 10:39 |
KatolaZ | 09:56 <+KatolaZ> I see you've been busy :) | 10:39 |
KatolaZ | ^^ | 10:39 |
KatolaZ | that's great | 10:39 |
KatolaZ | Centurion_Dan: I would migrate the new packages we built for unstable straight into beowulf | 10:41 |
KatolaZ | this might create some breakage, but at least we have a slightly larger user base to test them | 10:42 |
Centurion_Dan | bewulf is so broken, I'm not recommending it anyway. | 10:47 |
KatolaZ | uh? | 10:50 |
KatolaZ | why do you say that? | 10:50 |
KatolaZ | I have been using it for about 8 months now | 10:50 |
KatolaZ | not a single problem | 10:50 |
KatolaZ | if "so broken" is the missing buttons to reboot/shutdown, then that's another story | 10:51 |
KatolaZ | but it's not at all broken | 10:51 |
KatolaZ | and we should start moving packages there | 10:51 |
KatolaZ | otherwise it will never been released | 10:51 |
KatolaZ | ... | 10:51 |
KatolaZ | simple equation | 10:51 |
KatolaZ | :D | 10:51 |
KatolaZ | unstable is frozen at some point in 2016 | 10:52 |
Centurion_Dan | I agree we should start moving packages. | 10:53 |
KatolaZ | ok | 10:55 |
KatolaZ | please have a look at my proposal in beowulf_todos | 10:55 |
Centurion_Dan | If you get a chance can you move consolekit2 from experimental to unstable (I need it to build slim) and also move the current elogind to unstable and we can test the version with the patch for replacing libsystemd0 in experimental. | 10:55 |
KatolaZ | Centurion_Dan: if it's in experimental you don't need it in unstable to build for experimental | 10:56 |
KatolaZ | I can move consolekit2 | 10:56 |
KatolaZ | Centurion_Dan: there is no binary for consolekit2 in experimental | 10:57 |
Centurion_Dan | the binaries are consolekit. | 10:58 |
KatolaZ | ok | 10:58 |
KatolaZ | and we don't have any consolekit in unstable, right? | 10:59 |
KatolaZ | or do we? | 10:59 |
Centurion_Dan | probably should fix it to either be consolekit (it's a direct continuation but with a new upstream) | 10:59 |
KatolaZ | I guess that's fine | 11:00 |
Centurion_Dan | or to use consolekit2 in the binary and lib names and set Provides to the equivalent consolekit package. | 11:00 |
KatolaZ | let's keep it like that for now | 11:00 |
Centurion_Dan | ok... I'll fix it in the next round... | 11:01 |
Centurion_Dan | we may need to patch and rebuild policykit to use consolekit2 anyway | 11:02 |
KatolaZ | consolekit2 is in unstable | 11:03 |
KatolaZ | will be available in a couple of minutes from pkgmaster | 11:03 |
Centurion_Dan | KatolaZ: I don't think our experimental builds have access to experimental | 11:03 |
KatolaZ | yes they do | 11:03 |
KatolaZ | :) | 11:03 |
KatolaZ | look at the binary job | 11:03 |
KatolaZ | if it's built for experimental, the experimental repo is added by default | 11:04 |
Centurion_Dan | (I have a set of pending issues for jdg to fix this using vendor profiles were we can set all these mappings properly. | 11:04 |
Centurion_Dan | ) | 11:04 |
KatolaZ | anyway, I can move also elogind to unstable | 11:04 |
KatolaZ | this will probably break things, but it's unstable | 11:04 |
KatolaZ | shall I? | 11:05 |
Centurion_Dan | You've pushed elogind from unstable into beowulf, or doesn't it have any yet? | 11:05 |
KatolaZ | nope | 11:07 |
KatolaZ | I haven't touched elogind at all | 11:07 |
KatolaZ | there is only a version in ascii | 11:07 |
KatolaZ | one in ascii-proposed | 11:07 |
Centurion_Dan | I'm more keen to push consolekit2 - that way we can get slim | 11:07 |
KatolaZ | and one in experimental | 11:07 |
KatolaZ | Centurion_Dan: we will have both in the end | 11:07 |
Centurion_Dan | push the experimental one to unstable then | 11:08 |
KatolaZ | ok | 11:08 |
Centurion_Dan | and if it doesn't result in howls of anguish in the next couple of days, we can promote to beowulf too. | 11:08 |
KatolaZ | moving now | 11:09 |
KatolaZ | done | 11:09 |
KatolaZ | will hit the repo soon | 11:09 |
KatolaZ | in theory we should rebuild those unstable packages every week | 11:09 |
KatolaZ | this would be part of the unstable/testing/stable pipeline | 11:10 |
KatolaZ | I guess we'll get there as soon as unstable is updated | 11:10 |
LeePen | Morning! | 11:14 |
LeePen | AFAIK, there are some extra bits in libsystemd over libelogind. That is why | 11:15 |
LeePen | debian didn't want their pam_elogind to provide pam_systemd. | 11:16 |
Centurion_Dan | yes, but only in the functionality related specifically to systemd and not the abi. That has been left untouched and provides empty stuns (I think). | 11:20 |
Centurion_Dan | *stubs | 11:20 |
Centurion_Dan | debian shouldn't care provided it's abi compatible and is only installed when systemd is not used. | 11:22 |
Centurion_Dan | LeePen: And the benefit is Debian won't have to fork and rebuild packages to support elogind. | 11:23 |
LeePen | Yes I agree. maybe they shouldn't but they did, which is why we have ended up with the -compat package in Debian. | 11:23 |
Centurion_Dan | Anyway, for debian elogind should provide all the functionality we need and we can easier be modified to our needs. | 11:24 |
Centurion_Dan | s/Devuan/debian/ | 11:24 |
Centurion_Dan | dooh! | 11:25 |
LeePen | :D | 11:25 |
Centurion_Dan | what I meant to say was: | 11:25 |
Centurion_Dan | Anyway, for Devuan elogind should provide all the functionality we need and we can easier be modified to our needs. | 11:25 |
LeePen | Yes. Ultimately, once elogind is in debian (it is still waiting in incoming) | 11:26 |
LeePen | the way I see this is | 11:26 |
LeePen | Devuan uses elogind directly from debian and | 11:26 |
Centurion_Dan | so a simple patch to add the symlinks and control file changes. | 11:26 |
LeePen | we have a compatibility package that we control to manage the symlinks and dependencies | 11:27 |
Centurion_Dan | Why. Debian will need it's own special case, lets not bother waiting for their butt hurt maintainers who see systemd utopia slipping away to finally let go... | 11:27 |
Centurion_Dan | :-P | 11:28 |
KatolaZ | anyway, I guess we need a working polkit series of packages in unstable | 11:29 |
Centurion_Dan | forget compat packages in Devuan. When Debian get there shit together they can either fork and patch our packages. | 11:29 |
LeePen | OK. Have you tried a libsystemd/elogind symlink? Does it work or break anything? | 11:29 |
Centurion_Dan | ... or do it on their own. | 11:29 |
Centurion_Dan | Not yet. | 11:30 |
LeePen | I have tried a pam_systemd/pam_elogind symlink and I think it was OK. That is also in the -compat package we have got on Debian. | 11:30 |
Centurion_Dan | KatolaZ has moved your elogind package to unstable so we can build for experimental and test from there. | 11:30 |
LeePen | Great. Thanks to you both. | 11:31 |
Centurion_Dan | Thanks to you for taking on a package | 11:31 |
* Centurion_Dan high fives LeePen | 11:32 | |
LeePen | It is good to help | 11:32 |
Centurion_Dan | Anyway I need an earlier night... too many runs past 2am already this week.. | 11:33 |
LeePen | OK. Sleep well. Morning here. | 11:34 |
Centurion_Dan | LeePen: btw, if you create an issue with the subject "build" and assign it to autobuild and set a label: "experimental" then that will kick off a build ;-) | 11:46 |
LeePen | Thanks. I will try it next time. | 11:47 |
Centurion_Dan | for packages where you are maintainer in git.d.o | 11:47 |
LeePen | Does it work if you are only Uploader? | 11:48 |
KatolaZ | don't think so, unless it has been fixed | 12:10 |
LeePen | No worries. | 12:16 |
KatolaZ | try that anyway | 12:19 |
LeePen | I will next time. | 12:30 |
KatolaZ | oki | 12:30 |
plasma41 | ping parazyd | 19:05 |
plasma41 | https://lists.dyne.org/lurker/message/20181121.164811.f1e54e85.en.html | 19:06 |
KatolaZ | plasma41: jessie cannot start on pi3B release 2017 | 19:07 |
KatolaZ | since jessie was released before that model was put on the market... | 19:07 |
KatolaZ | :D | 19:07 |
plasma41 | I tested the Raspberry PI 2 image in question and I can concur that the OS doesn't start, no video other than a black screen. | 19:08 |
plasma41 | KatolaZ: I'm corroborating the report about the RP2 ASCII image. | 19:10 |
KatolaZ | ok great | 19:11 |
KatolaZ | that needs to be fixed | 19:11 |
plasma41 | I'm frankly astounded this wasn't caught sooner. | 19:13 |
KatolaZ | it looks strange to me as well, TBH | 19:14 |
golinux | Could someone who understands the bug please respond thanking him for letting us know? | 19:18 |
plasma41 | I suppose I can do that. | 19:24 |
golinux | plasma41: Thanks! | 19:39 |
plasma41 | parazyd KatolaZ: I just tested the RP2 ASCII Release Candidate image and it suffers the same issue. | 19:55 |
KatolaZ | plasma41: there are two versions of rpi2B | 19:57 |
KatolaZ | one is 32bit | 19:57 |
KatolaZ | the other one is 64bits | 19:57 |
plasma41 | I thought the first pi to support 64 bit was the 3 | 19:58 |
KatolaZ | nope | 19:58 |
KatolaZ | rpi2b ver 1.2 has the same processor as the rpi3 | 19:58 |
plasma41 | My Pi 2s are both V1.1 | 19:59 |
KatolaZ | eh | 19:59 |
KatolaZ | I guess parazyd built the image for the ver 1.2 | 19:59 |
KatolaZ | which is the newer one | 19:59 |
plasma41 | :-/ | 19:59 |
KatolaZ | (just guessing) | 19:59 |
KatolaZ | anyway, you could use the rpi1 image there | 19:59 |
parazyd | The pi2 image always booted on my Pis | 20:00 |
plasma41 | rpi1 image doesn't support hard float | 20:00 |
KatolaZ | yeah parazyd | 20:00 |
KatolaZ | it must be a ver 1.2 | 20:00 |
parazyd | Try getting a serial console and read what's up. | 20:00 |
KatolaZ | probably | 20:00 |
plasma41 | hello parazyd | 20:00 |
parazyd | o/ | 20:01 |
KatolaZ | o/ | 20:01 |
KatolaZ | \o/ | 20:01 |
KatolaZ | \o\ | 20:01 |
KatolaZ | /o/ | 20:01 |
KatolaZ | |o| | 20:01 |
KatolaZ | /o\ | 20:02 |
KatolaZ | /.\ | 20:02 |
plasma41 | parazyd: I don't have a serial cable for the pi | 20:02 |
plasma41 | The ASCII Beta rpi2 image boots on my pi | 20:04 |
parazyd | And the current one does not? | 20:07 |
plasma41 | Correct | 20:07 |
plasma41 | <KatolaZ> rpi2b ver 1.2 has the same processor as the rpi3 | 20:09 |
plasma41 | <KatolaZ> I guess parazyd built the image for the ver 1.2 | 20:09 |
parazyd | What revision of the board do you have? | 20:09 |
plasma41 | parazyd: is that right ^ | 20:09 |
plasma41 | 1.1 | 20:09 |
parazyd | I don't build the stuff for any specific rev. | 20:10 |
parazyd | plasma41: Do you know the date of the beta image? | 20:11 |
plasma41 | 2018-02-28 | 20:13 |
plasma41 | Is when I downloaded it | 20:13 |
parazyd | Thanks | 20:13 |
plasma41 | The beta released on Valentines Day if memory serves | 20:13 |
parazyd | Literally nothing changed except the kernel version... | 20:15 |
parazyd | Hmm | 20:15 |
parazyd | I can build a new one for you tomorrow if you like. | 20:16 |
parazyd | Then we can debug it. I have some Pi2 somewhere as well. | 20:16 |
plasma41 | You didn't accidentally start compiling the image as 64bit perhaps? That would work fine on V1.2 but not on V1.1 | 20:18 |
parazyd | Nope | 20:18 |
plasma41 | parazyd: What version is your rpi2? | 20:19 |
parazyd | https://git.devuan.org/sdk/arm-sdk/blob/master/boards/raspberry-pi2.sh#L28 | 20:19 |
parazyd | plasma41: I'll have to check | 20:19 |
parazyd | It's not at my house. | 20:19 |
KatolaZ | parazyd: we also need to add "--no-merged-usr" to the debootstrap options in devuan-sdk | 20:21 |
KatolaZ | the latest debootstrap in unstable has --merged-usr enabled by default... | 20:22 |
parazyd | ACK | 20:28 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!