Re: KDE Frameworks 5.37.0
¡Hola KDE! El 2017-08-14 a las 14:49 +0200, Maximiliano Curia escribió: El 2017-08-14 a las 10:40 +0200, Maximiliano Curia escribió: El 2017-08-06 a las 23:41 +0200, David Faure escribió: KDE Frameworks 5.37.0 has been uploaded to the usual place. Thanks for the release, could you also push the tags the v5.37.0 tags in the git repos? Thanks, I see that they are available now, except for kirigami, can you also push the tag for kirigami? Thanks, I got it now, I'm not sure if git was stubbornly not fetching the tag or if you pushed it just before I tried calling fetch --tags. Happy hacking, -- "Don't let what you cannot do interfere with what you can do." -- Wooden's Rule Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Re: KDE Frameworks 5.37.0
¡Hola KDE! El 2017-08-14 a las 10:40 +0200, Maximiliano Curia escribió: El 2017-08-06 a las 23:41 +0200, David Faure escribió: KDE Frameworks 5.37.0 has been uploaded to the usual place. Thanks for the release, could you also push the tags the v5.37.0 tags in the git repos? Thanks, I see that they are available now, except for kirigami, can you also push the tag for kirigami? Happy hacking, -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." -- Rich Cook Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Re: KDE Frameworks 5.37.0
On lundi 14 août 2017 10:40:23 CEST Maximiliano Curia wrote: > ¡Hola David! > > El 2017-08-06 a las 23:41 +0200, David Faure escribió: > > KDE Frameworks 5.37.0 has been uploaded to the usual place. > > Thanks for the release, could you also push the tags the v5.37.0 tags in the > git repos? Ah, I thought I had done that, but it failed because I was requested to gpg- sign the tags, and the config wasn't set up appropriately for that. All fixed now. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KDE Frameworks 5.37.0
¡Hola David! El 2017-08-06 a las 23:41 +0200, David Faure escribió: KDE Frameworks 5.37.0 has been uploaded to the usual place. Thanks for the release, could you also push the tags the v5.37.0 tags in the git repos? Happy hacking, -- "The most important thing in the programming language is the name. A language will not succeed without a good name. I have recently invented a very good name and now I am looking for a suitable language." -- Donald Knuth Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature
Re: KDE Frameworks 5.37.0
On samedi 12 août 2017 22:54:51 CEST Andreas Sturmlechner wrote: > On 10 August 2017 at 23:18, David Faurewrote: > > Hmm. What's the headache, if the framework name is simply "kirigami2", > > just > > like kcoreaddons is kcoreaddons? Now that my scripts have hacks, yours > > shouldn't need any... > > It's a minor inconvenience that repo name and tarball differ, since > our packages are based on the former. No big deal, just two lines of > custom code - I was just surprised this happened so late with > everything in place already. Yep, my fault for not reacting to the problem earlier, sorry about that. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KDE Frameworks 5.37.0
On 10 August 2017 at 23:18, David Faurewrote: > Hmm. What's the headache, if the framework name is simply "kirigami2", just > like kcoreaddons is kcoreaddons? Now that my scripts have hacks, yours > shouldn't need any... It's a minor inconvenience that repo name and tarball differ, since our packages are based on the former. No big deal, just two lines of custom code - I was just surprised this happened so late with everything in place already.
Re: KDE Frameworks 5.37.0
On jeudi 10 août 2017 21:49:38 CEST Andreas Sturmlechner wrote: > On Thursday, 10 August 2017 at 21:16, Rik Mills wrote: > > Indeed it would. For example I have kirigami (v1) and kirigami2 source > > packages in ubuntu, so human level confusion aside, now renaming > > kirigami2 tarballs to just kirigami is going to give scripting and > > tooling a headache. > > Gah, I thought that had been settled already in a previous discussion and > only Ubuntu had raised some doubts - _someone_'s tooling will always have a > headache. I won't rename kirigami and just re-add the hacks to fetch the *2 > tarball... Hmm. What's the headache, if the framework name is simply "kirigami2", just like kcoreaddons is kcoreaddons? Now that my scripts have hacks, yours shouldn't need any... -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: Re: KDE Frameworks 5.37.0
On Thursday, 10 August 2017 at 21:16, Rik Mills wrote: > Indeed it would. For example I have kirigami (v1) and kirigami2 source > packages in ubuntu, so human level confusion aside, now renaming > kirigami2 tarballs to just kirigami is going to give scripting and > tooling a headache. Gah, I thought that had been settled already in a previous discussion and only Ubuntu had raised some doubts - _someone_'s tooling will always have a headache. I won't rename kirigami and just re-add the hacks to fetch the *2 tarball...
Re: KDE Frameworks 5.37.0
Seems good so far. Thank you. On 10/08/17 20:30, David Faure wrote: > OK, I don't like having to add hacks to the release scripts, but it looks > like it's the only way here, short of renaming the git repo. > > I fixed the version numbers and repacked kirigami, now as kirigami2. > Please double-check closely that everything is as it should... > > kirigami v5.37.0-rc2 > 89ac5784a78269d6715941de7fdf4aec95d6413a > ad252c1ff20060f1de5afd41fade9b86e046bc9a7da38af6ca507f8ba2ce82fc > sources/kirigami2-5.37.0.tar.xz > > Cheers, > David. > > On jeudi 10 août 2017 21:16:25 CEST Rik Mills wrote: >> Indeed it would. For example I have kirigami (v1) and kirigami2 source >> packages in ubuntu, so human level confusion aside, now renaming >> kirigami2 tarballs to just kirigami is going to give scripting and >> tooling a headache. >> >> On 10/08/17 20:09, Tobias C. Berner wrote: >>> Also, given that this was previously called kirigami2, and still >>> installs stuff to .../cmake/KF5Kirigami2/..., .../kirigami.2/... and so >>> respectively, wouldn't it be less confusing to call this still kirigami2? >>> >>> >>> mfg Tobias >>> >>> On 10 August 2017 at 20:52, Andreas Sturmlechner >>>> >>> >>> wrote: >>> On Sunday, 6 August 2017 at 23:41, David Faure wrote: >>> > KDE Frameworks 5.37.0 has been uploaded to the usual place. >>> > >>> > New frameworks: kirigami. >>> >>> Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION >>> 5.35.0, I >>> don't think that's intentional? >>> >>> Regards > >
Re: KDE Frameworks 5.37.0
On my end looks good. if you think that renaming the repo is the least ugly way to go, i would be fine with that On Thu, Aug 10, 2017 at 9:30 PM, David Faurewrote: > OK, I don't like having to add hacks to the release scripts, but it looks > like it's the only way here, short of renaming the git repo. > > I fixed the version numbers and repacked kirigami, now as kirigami2. > Please double-check closely that everything is as it should... > > kirigami v5.37.0-rc2 > 89ac5784a78269d6715941de7fdf4aec95d6413a > ad252c1ff20060f1de5afd41fade9b86e046bc9a7da38af6ca507f8ba2ce82fc > sources/kirigami2-5.37.0.tar.xz > > Cheers, > David. > > On jeudi 10 août 2017 21:16:25 CEST Rik Mills wrote: >> Indeed it would. For example I have kirigami (v1) and kirigami2 source >> packages in ubuntu, so human level confusion aside, now renaming >> kirigami2 tarballs to just kirigami is going to give scripting and >> tooling a headache. >> >> On 10/08/17 20:09, Tobias C. Berner wrote: >> > Also, given that this was previously called kirigami2, and still >> > installs stuff to .../cmake/KF5Kirigami2/..., .../kirigami.2/... and so >> > respectively, wouldn't it be less confusing to call this still kirigami2? >> > >> > >> > mfg Tobias >> > >> > On 10 August 2017 at 20:52, Andreas Sturmlechner >> > > >> > >> > wrote: >> > On Sunday, 6 August 2017 at 23:41, David Faure wrote: >> > > KDE Frameworks 5.37.0 has been uploaded to the usual place. >> > > >> > > New frameworks: kirigami. >> > >> > Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION >> > 5.35.0, I >> > don't think that's intentional? >> > >> > Regards > > > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Working on KDE Frameworks 5 >
Re: KDE Frameworks 5.37.0
OK, I don't like having to add hacks to the release scripts, but it looks like it's the only way here, short of renaming the git repo. I fixed the version numbers and repacked kirigami, now as kirigami2. Please double-check closely that everything is as it should... kirigami v5.37.0-rc2 89ac5784a78269d6715941de7fdf4aec95d6413a ad252c1ff20060f1de5afd41fade9b86e046bc9a7da38af6ca507f8ba2ce82fc sources/kirigami2-5.37.0.tar.xz Cheers, David. On jeudi 10 août 2017 21:16:25 CEST Rik Mills wrote: > Indeed it would. For example I have kirigami (v1) and kirigami2 source > packages in ubuntu, so human level confusion aside, now renaming > kirigami2 tarballs to just kirigami is going to give scripting and > tooling a headache. > > On 10/08/17 20:09, Tobias C. Berner wrote: > > Also, given that this was previously called kirigami2, and still > > installs stuff to .../cmake/KF5Kirigami2/..., .../kirigami.2/... and so > > respectively, wouldn't it be less confusing to call this still kirigami2? > > > > > > mfg Tobias > > > > On 10 August 2017 at 20:52, Andreas Sturmlechner > >> > > > > wrote: > > On Sunday, 6 August 2017 at 23:41, David Faure wrote: > > > KDE Frameworks 5.37.0 has been uploaded to the usual place. > > > > > > New frameworks: kirigami. > > > > Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION > > 5.35.0, I > > don't think that's intentional? > > > > Regards -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5
Re: KDE Frameworks 5.37.0
Indeed it would. For example I have kirigami (v1) and kirigami2 source packages in ubuntu, so human level confusion aside, now renaming kirigami2 tarballs to just kirigami is going to give scripting and tooling a headache. On 10/08/17 20:09, Tobias C. Berner wrote: > Also, given that this was previously called kirigami2, and still > installs stuff to .../cmake/KF5Kirigami2/..., .../kirigami.2/... and so > respectively, wouldn't it be less confusing to call this still kirigami2? > > > mfg Tobias > > On 10 August 2017 at 20:52, Andreas Sturmlechner >> > wrote: > > On Sunday, 6 August 2017 at 23:41, David Faure wrote: > > KDE Frameworks 5.37.0 has been uploaded to the usual place. > > > > New frameworks: kirigami. > > Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION > 5.35.0, I > don't think that's intentional? > > Regards > >
Re: KDE Frameworks 5.37.0
Also, given that this was previously called kirigami2, and still installs stuff to .../cmake/KF5Kirigami2/..., .../kirigami.2/... and so respectively, wouldn't it be less confusing to call this still kirigami2? mfg Tobias On 10 August 2017 at 20:52, Andreas Sturmlechner < andreas.sturmlech...@gmail.com> wrote: > On Sunday, 6 August 2017 at 23:41, David Faure wrote: > > KDE Frameworks 5.37.0 has been uploaded to the usual place. > > > > New frameworks: kirigami. > > Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION 5.35.0, > I > don't think that's intentional? > > Regards > >
Re: KDE Frameworks 5.37.0
On Sunday, 6 August 2017 at 23:41, David Faure wrote: > KDE Frameworks 5.37.0 has been uploaded to the usual place. > > New frameworks: kirigami. Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION 5.35.0, I don't think that's intentional? Regards