Re: RKWard 0.7.0 release candidate is available for packaging
On Mon, 16 Apr 2018 09:26:48 +0200 Thomas Friedrichsmeier wrote: > On Sun, 15 Apr 2018 13:05:57 +0200 > meik michalke wrote: > > Am Sonntag, 15. April 2018, 12:49:59 CEST schrieb Thomas > > Friedrichsmeier: > > > Something similar happened to me before, and I simply uploaded > > > with a different name (the name can then be fixed while > > > publishing). > > > > ok, i've successfully upload as > > > > RKWard-binary-0.7.0_OSX10.11_KF5-5.42.0_needs_CRAN_R-3.4.4_.pkg > > > > instead (additional underscore at the end)! :: m. > > > > Thanks. All files are now on download.kde.org. Could you check > https://rkward.kde.org/RKWard_on_Mac for any necessary documentation > updates (such as version of MacOS; what do we require now?)? D'uh, it states the required version of OSX in the filename, but well, please take a quick look at the other info on that page. Regards Thomas pgpdlA6D9l7Kw.pgp Description: OpenPGP digital signature
Re: RKWard 0.7.0 release candidate is available for packaging
On Sun, 15 Apr 2018 13:05:57 +0200 meik michalke wrote: > Am Sonntag, 15. April 2018, 12:49:59 CEST schrieb Thomas > Friedrichsmeier: > > Something similar happened to me before, and I simply uploaded with > > a different name (the name can then be fixed while publishing). > > ok, i've successfully upload as > > RKWard-binary-0.7.0_OSX10.11_KF5-5.42.0_needs_CRAN_R-3.4.4_.pkg > > instead (additional underscore at the end)! :: m. > Thanks. All files are now on download.kde.org. Could you check https://rkward.kde.org/RKWard_on_Mac for any necessary documentation updates (such as version of MacOS; what do we require now?)? Regards Thomas pgpNxrqBNe5QC.pgp Description: OpenPGP digital signature
Re: RKWard 0.7.0 release candidate is available for packaging
Am Sonntag, 15. April 2018, 12:49:59 CEST schrieb Thomas Friedrichsmeier: > Something similar happened to me before, and I simply uploaded with a > different name (the name can then be fixed while publishing). ok, i've successfully upload as RKWard-binary-0.7.0_OSX10.11_KF5-5.42.0_needs_CRAN_R-3.4.4_.pkg instead (additional underscore at the end)! :: m. -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf signature.asc Description: This is a digitally signed message part.
Re: RKWard 0.7.0 release candidate is available for packaging
On Sun, 15 Apr 2018 12:45:42 +0200 meik michalke wrote: > unfortunately, my first upload attempt of the *.pkg file was > interrupted. now there's a stub of a file in incoming and i can't > overwrite it with the full file. who can i ask to remove the partial > file, or must you do that? I think only sysadmin can do that. Something similar happened to me before, and I simply uploaded with a different name (the name can then be fixed while publishing). Regards Thomas pgpPM1xbqXpom.pgp Description: OpenPGP digital signature
Re: RKWard 0.7.0 release candidate is available for packaging
hi, Am Samstag, 14. April 2018, 21:05:35 CEST schrieb Thomas Friedrichsmeier: > > if it's ok, i've a ready built package i could already upload to > > incoming. > > The good thing about building those packages ourselves is that we don't > have to worry about bureaucracy, too much. So, yes, that's totally > fine. I'm building the Windows package like that, too. uploading both *.pkg and *.src now: RKWard-binary-0.7.0_OSX10.11_KF5-5.42.0_needs_CRAN_R-3.4.4.pkg: SHA1: 29e5bc10637d728d2a5b2a24621326090f79d751 SHA256: 2a56f6ee41ec7e57b81eb375ca113e5d111269979729fea9d3db8dd10b7c0fe2 SHA512: 87b6ba34a4c8bc84ceb6bc0e6ad025dcdf7fe9256f3f2be78d5f6a344ac9d8a5f621dab4161e02129b42852e29f83a6cc553349a9f7de8f60726f49f48f8bb1d RKWard-binary-0.7.0_OSX10.11_KF5-5.42.0_src.tar: SHA1: 98a35c48da89416af4e0b4dcdce0b61a1af2b106 SHA256: 004314dacd7815392a7a76e493f240c7dafb484f195e11ed5b535f8c7a7addc1 SHA512: dd0b54e097cbcdb8d248fe0bc8566ac98f60739af834a590a39f9710ffdb450f4c8c8ffadcca1c3d36daa626173a9283fcf8e2c144698638ad77f96f563e2d41 unfortunately, my first upload attempt of the *.pkg file was interrupted. now there's a stub of a file in incoming and i can't overwrite it with the full file. who can i ask to remove the partial file, or must you do that? viele grüße :: m.eik -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf signature.asc Description: This is a digitally signed message part.
Re: RKWard 0.7.0 release candidate is available for packaging
hi, Am Samstag, 14. April 2018, 21:05:35 CEST schrieb Thomas Friedrichsmeier: > meik michalke wrote: > > i've configured the portfile to use the "releases/0.7.0" branch from > > git, is that ok, too, or should i rather use the tarball and checksum? > > > > if it's ok, i've a ready built package i could already upload to > > incoming. > > The good thing about building those packages ourselves is that we don't > have to worry about bureaucracy, too much. So, yes, that's totally > fine. I'm building the Windows package like that, too. > > I've built the tarball from revision > d68da587775f4a795cfc00fbe78f64b5d8c9fb43. The only change since then is > in directories that are not part of the tarball. (I'll add a tag in a > minute). what just crossed my mind: i should have merged the update to the portfile for the final release, as the one included looks like 0.7.0 doesn't have a release candidate: https://cgit.kde.org/rkward.git/tree/macports/kf5/kf5-rkward-binary/Portfile? h=v0.7.0 see https://cgit.kde.org/rkward.git/commit/? id=d0829218a3a75829327c315e20fba3ab3083a3c6 damn. viele grüße :: m.eik -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf signature.asc Description: This is a digitally signed message part.
Re: RKWard 0.7.0 release candidate is available for packaging
On Sat, 14 Apr 2018 19:59:15 +0200 meik michalke wrote: > i've configured the portfile to use the "releases/0.7.0" branch from > git, is that ok, too, or should i rather use the tarball and checksum? > > if it's ok, i've a ready built package i could already upload to > incoming. The good thing about building those packages ourselves is that we don't have to worry about bureaucracy, too much. So, yes, that's totally fine. I'm building the Windows package like that, too. I've built the tarball from revision d68da587775f4a795cfc00fbe78f64b5d8c9fb43. The only change since then is in directories that are not part of the tarball. (I'll add a tag in a minute). Regards Thomas pgpAHHoQ44u4k.pgp Description: OpenPGP digital signature
Re: RKWard 0.7.0 release candidate is available for packaging
Am Freitag, 13. April 2018, 22:12:57 CEST schrieb Thomas Friedrichsmeier: > The sources for RKWard 0.7.0 have been finalized (hopefully), and the > release candidate is at > http://files.kde.org/rkward/testing/for_packaging/ . i've configured the portfile to use the "releases/0.7.0" branch from git, is that ok, too, or should i rather use the tarball and checksum? if it's ok, i've a ready built package i could already upload to incoming. viele grüße :: m.eik -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf signature.asc Description: This is a digitally signed message part.
