Compiling konsole on Windows via craft
Hi, there is an issue to compile Konsole on Windows. KPty is not found. A fix for Cantor (https://bugs.kde.org/show_bug.cgi?id=386787) was to remove it from the CMakeLists.txt. Can the same be done for Konsole? Full thread: https://mail.kde.org/pipermail/kde-windows/2020-April/011157.html Johnny
Re: Compiling konsole on Windows via craft
On 20.04.2020 11:03, Johnny Jazeix wrote: Hi, there is an issue to compile Konsole on Windows. KPty is not found. A fix for Cantor (https://bugs.kde.org/show_bug.cgi?id=386787) was to remove it from the CMakeLists.txt. Can the same be done for Konsole? Full thread: https://mail.kde.org/pipermail/kde-windows/2020-April/011157.html Johnny FWIW, I grepped for kpty over the Konsole sources, and CMakeLists.txt is not among the files where kpty is mentioned. It is however used in the Konsole code. When I look the fix you mentioned¹, I see they explain in the commit message that components that depend on kpty are simply not built for Windows platform. Offhand, I don't believe this is the case for Konsole. 1:https://cgit.kde.org/cantor.git/commit/?id=5700cc59da6f8bba503a38ba4c902877206a59cf
Re: Compiling konsole on Windows via craft
Hi, KPty is mentioned as Pty in the CMakeLists.txt (https://invent.kde.org/kde/konsole/-/blob/master/CMakeLists.txt#L50). Hannah mentioned on the KDE-Windows hread that KPty can't be compiled on Windows yet and is necessary for Konsole, so Konsole can't be compiled on Windows yet. Thanks for the quick reply, Johnny Le lun. 20 avr. 2020 à 10:52, Konstantin Kharlamov a écrit : > > On 20.04.2020 11:03, Johnny Jazeix wrote: > > Hi, > > > > there is an issue to compile Konsole on Windows. KPty is not found. A > > fix for Cantor (https://bugs.kde.org/show_bug.cgi?id=386787) was to > > remove it from the CMakeLists.txt. > > Can the same be done for Konsole? > > > > Full thread: > > https://mail.kde.org/pipermail/kde-windows/2020-April/011157.html > > > > Johnny > > FWIW, I grepped for kpty over the Konsole sources, and CMakeLists.txt is not > among the files where kpty is mentioned. It is however used in the Konsole > code. > > When I look the fix you mentioned¹, I see they explain in the commit message > that components that depend on kpty are simply not built for Windows > platform. Offhand, I don't believe this is the case for Konsole. > > 1:https://cgit.kde.org/cantor.git/commit/?id=5700cc59da6f8bba503a38ba4c902877206a59cf
Re: Proposal: "Noteworthy" label for Promo application updates
I think the easiest would be to use the GitLab tags. Hopefully, we will soon use Gitlab for everything and then it won't be a problem. For example, promo will just need to go to these two links to find all the information we need: * https://invent.kde.org/groups/kde/-/issues?label_name%5B%5D=Noteworthy * https://invent.kde.org/groups/kde/-/merge_requests?label_name%5B%5D=Noteworthy Carl ‐‐‐ Original Message ‐‐‐ Le dimanche, avril 19, 2020 9:15 AM, Ben Cooksley a écrit : > On Sun, Apr 19, 2020 at 8:34 PM XYQuadrat m...@xyquadrat.ch wrote: > > > If we implement such a system (that is, just resurrect what is already > > present), I definitely think it would be sensible to make guidelines on > > what commits we are interested in publicly available. > > The thing I'm not sure about is how easy it'd be to automate grabbing > > all the CHANGELOG commits from a given date range - can someone more > > experienced with our git/repo infrastructure shed some light here? > > That depends on whether you have local, up to date, clones of the > repositories in question. > If you have them locally it should be reasonably trivial with a bit of > scripting to get a list of commits and the repositories to which they > belong. > > If you don't, then the only other option you would have would be > Gitlab's APIs but that isn't ideal from an infrastructural point of > view. > > > Best regards, > > Julian / xyquadrat > > Cheers, > Ben > > > On 17.04.20 01:19, Johannes Zarl-Zierl wrote: > > > > > On Donnerstag, 16. April 2020 23:15:18 CEST Nate Graham wrote: > > > > > > > On 4/16/20 2:38 PM, Albert Astals Cid wrote: > > > > > > > > > It may make sense to highlight them a bit more somehow, suggestions > > > > > welcome i guess. > > > > > The promo people just need a list of all CHANGELOG entries in a > > > > > release > > > > > so they can rewrite it in more human-friendly terms. Right now this is > > > > > done manually by me and others by looking through commit logs and blog > > > > > posts and adding the equivalent of CHANGELOG text into an > > > > > etherpad/share.kde.org document. Automating that somehow would be > > > > > nice. > > > > > From a developer point of view, a tag in the commit itself seems like > > > > > a nice > > > > > interface. One thing I fear, though, is that people like me forget to > > > > > actually > > > > > add it to the commit before pushing, so maybe something that can be > > > > > added > > > > > later would definitely have its advantages. > > > > > > Personally, I'd like to have some clear guidelines from the promo team > > > on what > > > kind of features they are looking for. That way it's way easier for me to > > > match those expectations ;-) > > > Btw. isn't the DIGEST keyword as documented in the standard commit > > > template > > > basically the same idea? > > > Cheers, > > > Johannes publickey - carl@carlschwan.eu - 0x7F564CB5.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
I am not able to submit to svn.kde.org.
Hi, I can't submit changs to / fetch changes from svn.kde.org. Here is the verbose message: ``` Committing to svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW ... Can't create session: Unable to connect to a repository at URL 'svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW': To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. at /usr/lib/git-core/git-svn line 1015. ``` 1) The SSH public key in local is same as that one I've uploaded to identify.kde.org > The uploaded SSH Key is already present. 2) On my primary machine, when I do "ssh s...@svn.kde.org", it returns: ``` $ ssh s...@svn.kde.org "s...@svn.kde.org: Permission denied (publickey)." ``` 3) And I also tried on my another machine (uses same SSH key), but it looks like same. ``` pan93@DESKTOP-JN5TNJH ~ ssh s...@svn.kde.org The authenticity of host 'svn.kde.org (195.201.182.103)' can't be established. ECDSA key fingerprint is SHA256:UutSIkXdSGgyxQxL35dDEEAD2Owel+zEdKZ5I/JMqrA. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'svn.kde.org,195.201.182.103' (ECDSA) to the list of known hosts. s...@svn.kde.org: Permission denied (publickey). ``` 4) Some details: svn.kde.org is pointed to 195.201.182.103. My identify.kde.org account is "ppeter". Thanks! Yi-Jyun Pan.
Re: I am not able to submit to svn.kde.org.
Did you see these instructions? https://community.kde.org/Infrastructure/Subversion/2020_Changes ‐‐‐ Original Message ‐‐‐ Le lundi, avril 20, 2020 12:02 PM, a écrit : > Hi, > I can't submit changs to / fetch changes from svn.kde.org. Here is the > verbose message: > > `Committing to svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW ... > Can't create session: Unable to connect to a repository at URL > 'svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW': To better debug > SSH connection problems, remove the -q option from 'ssh' in the [tunnels] > section of your Subversion configuration file. at /usr/lib/git-core/git-svn > line 1015.` > > 1) The SSH public key in local is same as that one I've uploaded > to identify.kde.org > > The uploaded SSH Key is already present. > > 2) On my primary machine, when I do "ssh...@svn.kde.org", it returns: > `$ ssh s...@svn.kde.org "s...@svn.kde.org: Permission denied (publickey)."` > > 3) And I also tried on my another machine (uses same SSH key), but > it looks like same. > `pan93@DESKTOP-JN5TNJH ~ ssh s...@svn.kde.org The authenticity of host > 'svn.kde.org (195.201.182.103)' can't be established. ECDSA key fingerprint > is SHA256:UutSIkXdSGgyxQxL35dDEEAD2Owel+zEdKZ5I/JMqrA. Are you sure you want > to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added > 'svn.kde.org,195.201.182.103' (ECDSA) to the list of known hosts. > s...@svn.kde.org: Permission denied (publickey).` > > 4) Some details: > svn.kde.org is pointed to 195.201.182.103. > My identify.kde.org account is "ppeter". > > Thanks! > Yi-Jyun Pan. publickey - carl@carlschwan.eu - 0x7F564CB5.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Re: I am not able to submit to svn.kde.org.
Well, after I added my SSH key into there, I still got this error: $ ssh s...@svn.kde.orgs...@svn.kde.org: Permission denied (publickey). BTW, I’m in the permitted list. 寄件者: Carl Schwan傳送時間: 2020年4月20日 20:22:23收件者: kde-devel@kde.org主旨: Re: I am not able to submit to svn.kde.org. Did you see these instructions? https://community.kde.org/Infrastructure/Subversion/2020_Changes ‐‐‐ Original Message ‐‐‐Le lundi, avril 20, 2020 12:02 PM, a écrit : > Hi,> I can't submit changs to / fetch changes from svn.kde.org. Here is the> verbose message:> > `Committing to svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW ... Can't create session: Unable to connect to a repository at URL 'svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW': To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. at /usr/lib/git-core/git-svn line 1015.`> > 1) The SSH public key in local is same as that one I've uploaded> to identify.kde.org> > The uploaded SSH Key is already present.> > 2) On my primary machine, when I do "ssh...@svn.kde.org", it returns:> `$ ssh s...@svn.kde.org "s...@svn.kde.org: Permission denied (publickey)."`> > 3) And I also tried on my another machine (uses same SSH key), but> it looks like same.> `pan93@DESKTOP-JN5TNJH ~ ssh s...@svn.kde.org The authenticity of host 'svn.kde.org (195.201.182.103)' can't be established. ECDSA key fingerprint is SHA256:UutSIkXdSGgyxQxL35dDEEAD2Owel+zEdKZ5I/JMqrA. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added 'svn.kde.org,195.201.182.103' (ECDSA) to the list of known hosts. s...@svn.kde.org: Permission denied (publickey).`> > 4) Some details:> svn.kde.org is pointed to 195.201.182.103.> My identify.kde.org account is "ppeter".> > Thanks!> Yi-Jyun Pan.
Re: Polish translation of "Cancel"
Thanks for getting this done, Łukasz! Nate On 4/17/20 2:05 PM, Łukasz Wojniłowicz wrote: No problem but give me some time. I must schedule that but I'm not sure of Luigi's plans in that matter. -- Łukasz Dnia piątek, 17 kwietnia 2020 21:56:02 CEST Nate Graham pisze: Thanks! When it's done, can you close the bug report or let us know? Nate On 4/17/20 1:53 PM, Łukasz Wojniłowicz wrote: Nothing. I would do that myself. I see that's the only way to solve this tension. Dnia piątek, 17 kwietnia 2020 21:26:03 CEST Luigi Toscano pisze: Let me ask clearly: if I commit the patch from https://bugs.kde.org/show_bug.cgi?id=404286#c65 what will you do?
Re: Re: I am not able to submit to svn.kde.org.
On Tue, Apr 21, 2020 at 12:42 AM Pan Yi-Jyun wrote: > > Well, after I added my SSH key into there, I still got this error: > > > > $ ssh s...@svn.kde.org > > s...@svn.kde.org: Permission denied (publickey). > SSH Keys are only synced from invent.kde.org to svn.kde.org once per hour, so there is some delay between you logging in there and you being able to access svn.kde.org. Given it has been more than an hour, I'd recommend trying again. Cheers, Ben > > > BTW, I’m in the permitted list. > > > > 寄件者: Carl Schwan > 傳送時間: 2020年4月20日 20:22:23 > 收件者: kde-devel@kde.org > 主旨: Re: I am not able to submit to svn.kde.org. > > > > Did you see these instructions? > https://community.kde.org/Infrastructure/Subversion/2020_Changes > > > > ‐‐‐ Original Message ‐‐‐ > > Le lundi, avril 20, 2020 12:02 PM, a écrit : > > > > > Hi, > > > I can't submit changs to / fetch changes from svn.kde.org. Here is the > > > verbose message: > > > > > > > > `Committing to svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW ... > > Can't create session: Unable to connect to a repository at URL > > 'svn+ssh://s...@svn.kde.org/home/kde/trunk/l10n-kf5/zh_TW': To better debug > > SSH connection problems, remove the -q option from 'ssh' in the [tunnels] > > section of your Subversion configuration file. at /usr/lib/git-core/git-svn > > line 1015.` > > > > > > > > 1) The SSH public key in local is same as that one I've uploaded > > > to identify.kde.org > > > > The uploaded SSH Key is already present. > > > > > > > > 2) On my primary machine, when I do "ssh...@svn.kde.org", it returns: > > > `$ ssh s...@svn.kde.org "s...@svn.kde.org: Permission denied (publickey)."` > > > > > > > > 3) And I also tried on my another machine (uses same SSH key), but > > > it looks like same. > > > `pan93@DESKTOP-JN5TNJH ~ ssh s...@svn.kde.org The authenticity of host > > 'svn.kde.org (195.201.182.103)' can't be established. ECDSA key fingerprint > > is SHA256:UutSIkXdSGgyxQxL35dDEEAD2Owel+zEdKZ5I/JMqrA. Are you sure you > > want to continue connecting (yes/no/[fingerprint])? yes Warning: > > Permanently added 'svn.kde.org,195.201.182.103' (ECDSA) to the list of > > known hosts. s...@svn.kde.org: Permission denied (publickey).` > > > > > > > > 4) Some details: > > > svn.kde.org is pointed to 195.201.182.103. > > > My identify.kde.org account is "ppeter". > > > > > > > > Thanks! > > > Yi-Jyun Pan. > > > >
Re: Proposal: "Noteworthy" label for Promo application updates
On Montag, 20. April 2020 13:46:47 CEST Carl Schwan wrote: > I think the easiest would be to use the GitLab tags. Hopefully, we will soon > use Gitlab for everything and then it won't be a problem. > > For example, promo will just need to go to these two links to find all the > information we need: > > * https://invent.kde.org/groups/kde/-/issues?label_name%5B%5D=Noteworthy > * https://invent.kde.org/groups/kde/-/merge_requests? label_name%5B%5D=Noteworthy Actually this seems like a good approach. At KPhotoAlbum, we don't use the merge request workflow much, but use issues (well, currently Phabricator tasks) to track feature development. Having both issue and merge-request labels should fit most projects, I guess... Cheers, Johannes signature.asc Description: This is a digitally signed message part.
Re: Downtime for SVN - Action Required
Translations are still in SVN, they have not moved to Git. We only moved the SVN repository to a different server, and integrated SVN ssh key management with the GitLab website. -- Nicolás El lun., 20 de abr. de 2020 a la(s) 19:56, Agron Selimaj (as9902...@gmail.com) escribió: > > Guys I just need a little clarification for submitting translated file to the > gitlab repository. > > My first question is - is the migration over and can I submit translated > files? > > Second, with SVN all I did was commit (of course after compiling and other > tests). Now with Git, I fork + clone, translate and then send a merge > request? Right? Is there a guide for submitting po files? > > Third, I need a little git/kde geography. What path do I clone from, from > git? Is there an efficient path that concerns translations only or more > specifically albanian translations. > > Thanks, > //Agron > > > > > On Sat, Apr 18, 2020 at 6:36 AM Nicolás Alvarez wrote: >> >> El dom., 12 de abr. de 2020 a la(s) 05:57, Ben Cooksley >> (bcooks...@kde.org) escribió: >> > >> > Hi all, >> > >> > As you may be aware, KDE is currently undertaking a migration to Gitlab. >> > >> > As part of this, we also need to migrate our Subversion repository >> > from the server it currently resides on to the new system that also >> > hosts Gitlab. To simplify our systems we will also transition >> > management of SSH keys to Gitlab when we do this. >> > >> > It is intended at this time that we perform the migration of the >> > Subversion repository next weekend. >> > >> > We therefore need all holders of a Developer account, even if they >> > only use our Subversion repository, to login to Gitlab and upload >> > their SSH keys there. >> > >> > Our Gitlab instance can be found at https://invent.kde.org/ and you >> > should be able to login there using your KDE Identity >> > (identity.kde.org) details. >> > >> > Additionally, following this migration we will begin limiting access >> > to the Subversion repository to those actively using it. The list of >> > people whose access will be continued can be found at >> > https://cgit.kde.org/repo-management.git/tree/svn-ssh-keys/users-list >> > >> > Should you still need access to the repository, but are not on the >> > above list, please let us know by emailing sysad...@kde.org. >> > >> > If anyone has any questions on the above, please let us know. >> >> Hi all, >> >> I wanted to add that this server migration will also change the SSH >> host keys for "svn.kde.org". After we switch servers, you will get the >> nasty "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!" message from >> ssh when you use SVN. To avoid this, you should add the new keys to >> your ~/.ssh/known_hosts. You don't need to wait for the server switch, >> you can add it now (keeping both old and new keys in the file) and it >> will Just Work. >> >> I have added instructions for all these changes and the new ssh host >> keys to the wiki: >> https://community.kde.org/Infrastructure/Subversion/2020_Changes >> >> -- >> Nicolás >> KDE Sysadmin Team
Re: Proposal: "Noteworthy" label for Promo application updates
Given the impending GitLab transition, it might make more sense to just use GitLab's tags/labels feature, yeah. That solves the problem of people forgetting to use the keyword before committing since it can always be added later, and it makes it easy for promo people to find the relevant commits using the web interface so they don't have to check out every repo and use a script. Nate On 4/19/20 2:34 AM, XYQuadrat wrote: If we implement such a system (that is, just resurrect what is already present), I definitely think it would be sensible to make guidelines on what commits we are interested in publicly available. The thing I'm not sure about is how easy it'd be to automate grabbing all the CHANGELOG commits from a given date range - can someone more experienced with our git/repo infrastructure shed some light here? Best regards, Julian / xyquadrat On 17.04.20 01:19, Johannes Zarl-Zierl wrote: On Donnerstag, 16. April 2020 23:15:18 CEST Nate Graham wrote: On 4/16/20 2:38 PM, Albert Astals Cid wrote: It may make sense to highlight them a bit more somehow, suggestions welcome i guess. The promo people just need a list of all CHANGELOG entries in a release so they can rewrite it in more human-friendly terms. Right now this is done manually by me and others by looking through commit logs and blog posts and adding the equivalent of CHANGELOG text into an etherpad/share.kde.org document. Automating that somehow would be nice. From a developer point of view, a tag in the commit itself seems like a nice interface. One thing I fear, though, is that people like me forget to actually add it to the commit before pushing, so maybe something that can be added later would definitely have its advantages. Personally, I'd like to have some clear guidelines from the promo team on what kind of features they are looking for. That way it's way easier for me to match those expectations ;-) Btw. isn't the DIGEST keyword as documented in the standard commit template basically the same idea? Cheers, Johannes
