- User Since
- Jul 17 2017, 4:00 PM (79 w, 1 d)
it's the value that we used for the other entries that were already in the file
the value on the right side is supposed to be a key name. Shouldn't this be something like KEYBOARD_KEY_56=backslash instead
See also https://dev.getsol.us/T6371
Upstream PR filed here:
@kyle.rankin Thanks for filing this. Should this also go upstream?
Very happy to take this. Indeed good call -- can you create a new, Librem 13v4-specific ticket for this and assign it to yours truly?
Sat, Jan 19
Ah, getcha. In that case, I suggest you checkout pristine-tar and the whole gbp-buildpackage flow in general. That will mean you have both worlds with no compromise. :)
Fri, Jan 18
Hey @jeremiah.foster I don't see your other branches, or I don't understand where your debian/ directory is..? :)
Mon, Jan 14
Tue, Dec 25
Mon, Dec 24
I'm going to go ahead and wontfix this as most of the changes are not appropriate to Debian and should be handled another way anyway, not via a "config package".
@kyle.rankin Okaley, so what's the next step here? This should have hit PureOS by now :)
Pinged upstream bug: https://gitlab.com/lamby/osinfo-db/merge_requests/1#note_127118132
Pinged Debian bug...
Dec 21 2018
This weather is far more of for smokey bourbon...
ACCEPTED in Debian.
Accepted in Debian. (Grr at your insistence of License-Grant! j/k)
Dec 18 2018
Dec 10 2018
As of this comment, we are at 84.5%. However:
Dec 6 2018
Followed up in: https://bugs.debian.org/906609#90
Sure thing. Guilhem's Librem Key has arrived and is playing with it. :)
Nov 26 2018
Indeed https://gist.githubusercontent.com/lamby/e45c7a221defe75db026ee529d00c789/raw no longer cleanly applies, will need to redo...
Nov 25 2018
and, as luck has it, we have movement there:
https://tracker.debian.org/news/1005629/accepted-cryptsetup-2205-2-source-amd64-all-into-unstable/ was just uploaded to Debian, closing https://bugs.debian.org/888916 and https://bugs.debian.org/903163
Nov 23 2018
ACK and I even looked at this ticket yesterday - we are still semi-blocking on the cryptroot and other refactorings in the Debian stuff but after that we will be able to merge this quickly. :)
Nov 22 2018
@kyle.rankin Thanks for adding me to this ticket and apologies that it took longer than anticipated to get around to replying; I not only had to read the extended discussion here, I also had to do some research in order to work out what the situation is.
Nov 21 2018
(Of course will keep this open; was just following-up here)
Pinged Debian bug...
FYI discussion and work on this is mostly happening on https://bugs.debian.org/903163
Nov 19 2018
This was uploaded a while ago and is now in Debian, so closing.. (no further obvious action here...)
Nov 9 2018
Nov 7 2018
Hi, any update for this? It's been many months and I would still dearly love this feature.
Oct 2 2018
https://bugs.debian.org/906609#30 segfault should be fixed...
Oct 1 2018
I'm going to go ahead and make the executive decision of un-assigning myself from this ticket - feel free to assign back if there is a "Next Action" for me of course, but I do not have an obvious step to proceed.
Sep 26 2018
Alas, I don't know who has bandwidth to do it and do not have control over their inbox. :)
(curious why this assigned to me, @mladen.pejakovic ?)
Sep 25 2018
(Now? Ie. with the openpgp-smartcard branch, no?)
Sep 19 2018
(Also needs python3-grpc package in Debian)
Sep 17 2018
Ah, of course. Thanks!
So, I can't exactly figure out exactly which USB device, etc. I need to disable this for (presumbly the "root hub", but I can't reproduce that bit).. plus I managed to reproduce this with the internal trackpad so I've gone ahead and disabled application of the Powertop profile for now in purism-power-optimisations version 0.5.3.
megadown is now in PureOS, so closing. Thanks. Let me know if you need to update a new version, naturally.
Great stuff; this helps in tracking it down. On it..
Sep 15 2018
Example logging output
Hi @johenry, thanks for filing this issue. Whilst I can't reproduce this, like
@mak I suspect this might be be the powertop parts of the purism-power-optmisations. After you reboot and you /cannot/ reproduce, can you try running powertop --auto-tune as root and let me know whether this causes the issue to return?
Sep 11 2018
Today I've gotten two different explanations
Sep 10 2018
Kyle, alas I think you are regrettably missing a lot of back-and-forth on this issue. The UK Librem 13 does have this issue in the sense that I needed to apply a /keyboard firmware/ update to fix it. No systemd patch could have possibly fixed it. There is nothing for me to apply now given that I applied the "BIOS"-level update.
Sep 9 2018
Sep 8 2018
Sep 7 2018
@mladen.pejakovic For what purpose? (What can he do here that I cannot?)
Sep 6 2018
Thanks @jonas.smedegaard. Want me to handle this? (I see I remain assigned..)
(NB. reply on that Debian bug report)
Tempted to close this issue as there is no clear "next action". Any objections?
@mladen.pejakovic Hey hey, what's the status of this? I'm just wondering what my next steps here — the ticket is currently assigned to me, but I have no obvious 'next action' as far as I can tell.
It's in debian testing now.
Sep 3 2018
Sep 2 2018
Testing migration can be tracked here:
Sep 1 2018
@kyle.rankin I have followed up to the bug (CC'd you)
Aug 28 2018
- I contacted another FTP team member so this has been ACCEPTED in good time.
Aug 27 2018
I just got confused because mentors.debian.net complains that 4.2.1 is too new
Just had a look - thanks! So, if you're running Lintian from sid then I don't understand why you still have:
@vivia.nikolaidou Please go ahead and drop the "contrib" etc. and let me know where I can do the review/upload. (Note that the very latest lintian is for 4.2.1... but I assume you are running Lintian from Debian sid...)
Aug 26 2018
@vivia.nikolaidou Gentle ping :)
Aug 22 2018
Also working on grpcio module packaging in the Python Modules team.
@vivia.nikolaidou What's the latest on this? Would love to get this settled up either way!
Aug 21 2018
(Feel free to re-use this ticket if there is not already one.)
Aug 18 2018
Blocked due to FBTFS in Debian on mips and s390x. Filed Debian bug.