El diumenge, 20 de gener de 2019, a les 4:40:35 CET, Jack va escriure: > On 1/19/19 8:49 PM, Albert Astals Cid wrote: > > El diumenge, 20 de gener de 2019, a les 0:27:42 CET, Jack va escriure: > >> Sorry to reply to my own post so soon, but I did find something. > >> > >> On 2019.01.19 18:18, Jack Ostroff wrote: > >>> Hello all, > >>> > >>> relicenseupdate.pl is a script in the kde-dev-scripts repository. It > >>> is referred to on the page > >>> https://techbase.kde.org/Projects/KDE_Relicensing. Unfortunately, it > >>> is not really clear how this is supposed to work. I posted a > >>> question on the Discussion page for that page last January, but no > >>> response. It turns out the problem I was having last year was that I > >>> had checked out the repository with the anon link. However, I just > >>> cloned it again with my dev account, but I still get an error trying > >>> to push my commit: "fatal: remote error: access denied or repository > >>> not exported: /kde-dev-scripts.git" > >>> > >>> Is this just a permission issue, am I doing something wrong, or are > >>> the instructions just wrong? Is there actually somewhere else I > >>> should raise this issue?
This really looks like you're trying to push to an anongit or similar, but looking at git i think you fixed it. right? > >>> > >>> As a separate issue, when I run that script against the KMyMoney > >>> repository, it complains about not finding an email address in the > >>> accounts list. I identified the first one as being someone who used > >>> one email for most commits, but a separate one for just a few. The > >>> next one it found - I have not yet even found the commit made by that > >>> email address, so I'm sort of stuck on how to proceed. > >> The email the script is complaining about is someone who authored an > >> update (actually updated screen shots for the manual) but the commit > >> was done by someone else. Even if I get that person's permission to > >> add him to relicensecheck.pl, that script will continue to complain > >> about his email address, since it will not be in the accounts file, > >> unless he does get a developer account. Entries in the script are by > >> username, not email, so I don't see any way around this, unless a file > >> is added to accounts and disabled-accounts, such as > >> non-committing-authors (or some shorter version). > >>> Thanks for any suggestions. > >> Still true. > > What is that you're trying to achieve by running the script? i.e. do you > > want to relicense something? What? Why? > > > > On a side note, the script is just a way to know if there's some stuff you > > need to double check, you don't need to have "a clean run" of the script > > before doing relicensing, what you need to do before doing relicensing is > > making sure you can do it. > > > > Also, why send this question to the user documentation mailing list? Seems > > a bit off topic (unless what you want to relicense is some documentation i > > guess) > > > > Cheers, > > Albert > > Hello Albert, > > You may remember that about a year ago, I tried to redo the licensing of > the KMyMoney documentation files, but in fact, didn't actually have all > the necessary permissions. As part of that effort, I was trying to add > myself to the script. In addition, I want to get the list of > contributors to KMyMoney, in case I might get some of them to agree to > be added to the script. So - I have a few separate questions. I posted > here since my starting point was the documentation for KMyMoney. As I > said, I'd be happy to be redirected to whoever is actually more > responsible for the script itself, since it deals with code as well as > documentation. My understanding is that the script will provide a full > list of contributors, and what additional permissions any of them would > need to grant in order to relicense - whether for code or documentation, Yes, that is correct, the script should tell you if anyone is missing, do you still have a problem running the script? Cheers, Albert > > > Jack > >
