Hi all,
Our last 3 servers are finally being migrated on Friday morning (UTC).
Expect downtimes for the following services during this period:
* https://reactos.org
* https://jira.reactos.org
* https://lam.reactos.org
As always, I will try my best to keep the downtimes low and let you know
when everything is over.
Best regards,
Colin Finck
Hi all!
Another server has been migrated to new hardware and software today!
I'm talking about our Git/SVN Server, which also serves BuildBot,
Doxygen, download.reactos.org, etc.
The anticipated and actual downtime has been so low again that I didn't
even have to announce the migration in advance.
Some remarks though:
* If you had file server upload access to svn.reactos.org *and still
need it*, please let me know and I can recreate your account. Have your
SSH public key ready.
Note that I plan to set up an easier and more official file sharing
service for ReactOS soon.
* For obvious reasons, the Mumble server at mumble.reactos.org has not
been migrated and is now officially shut down. I'm looking forward to
finally set up the Mattermost instance once all existing VMs have been
migrated (5 done, 3 to go).
* git.reactos.org is no longer accessible via the git:// protocol.
If you have any URLs using that, please change them to https://.
Cheers,
Colin
I'm not sure I understand this commit, nor the PR that was merged before.
This is a synced module, for a Vista+ export... What's the point of this?
It would have been better to sync with Wine and have this patch upstream.
Le 18/11/2018 à 21:03, Hermès Bélusca-Maïto a écrit :
> https://git.reactos.org/?p=reactos.git;a=commitdiff;h=2d320f5a8daf4627458e8…
>
> commit 2d320f5a8daf4627458e81f0ffd51bdd8f60d120
> Author: Hermès Bélusca-Maïto <hermes.belusca-maito(a)reactos.org>
> AuthorDate: Sun Nov 18 21:05:32 2018 +0100
> Commit: Hermès Bélusca-Maïto <hermes.belusca-maito(a)reactos.org>
> CommitDate: Sun Nov 18 21:06:22 2018 +0100
>
> [OLE32] The CoDisconnectContext() stub added in 6a2f9673 (PR #1044) is actually Vista+. Caught by Thomas Faber.
> ---
> dll/win32/ole32/ole32.spec | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/dll/win32/ole32/ole32.spec b/dll/win32/ole32/ole32.spec
> index d4ed1163d4..97667918e9 100644
> --- a/dll/win32/ole32/ole32.spec
> +++ b/dll/win32/ole32/ole32.spec
> @@ -23,7 +23,7 @@
> # CoCreateObjectInContext
> # CoDeactivateObject
> @ stdcall -stub CoDisableCallCancellation(ptr)
> -@ stdcall -stub CoDisconnectContext(long)
> +@ stdcall -stub -version=0x600+ CoDisconnectContext(long)
> @ stdcall CoDisconnectObject(ptr long)
> @ stdcall CoDosDateTimeToFileTime(long long ptr) kernel32.DosDateTimeToFileTime
> @ stdcall -stub CoEnableCallCancellation(ptr)
>
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Hi all!
Having converted the last ReactOS SVN repository (press-media) to Git
today, we can finally call the entire Git migration done :)
Well, probably it felt done for you for a long time, but I still
struggled with that last repository until today.
As I'm also about to migrate the Git/SVN server soon, I can finally tell
you about the long-term availability of the old SVN repositories:
* Access to svn.reactos.org over the svn:// protocol will soon be suspended.
* Read-only access to the press-media, project-tools, reactos, and web
SVN repositories at https://svn.reactos.org will be maintained.
This allows you to continue looking up old SVN history whenever Git's
log has problems tracking a file move.
* Access to ViewVC at https://svn.reactos.org/svn and
https://svn.reactos.org/viewcvs will be suspended as well. One less tool
for us to maintain.
Of course, I will again let you know when the actual migration is
happening (or already over :)).
Cheers,
Colin
Hi,
I did not receive anny replies about my question to make reactos
accessible for the blind. I would really suggest to do that while building
the os, instead of doign it when the whole system is fully built.
Hi all!
Our mail server will be shut down for migration
TOMORROW, WEDNESDAY, NOVEMBER 14, AROUND 9:00 UTC
This will result in a temporary downtime for the following services:
* @reactos.org E-Mail addresses
* Mailing lists
* https://iserv.reactos.org
The migration has already been prepared and simulated, so I expect the
downtime to be low and the entire process to only take a few minutes.
I will let you know when everything is back up again.
We look forward to improve the performance, reliability, and especially
maintainability through this migration.
This probably just sounds like a pile of buzzwords to you, but there are
hardly other words to describe a move from HDDs to SSDs, data
replication on even more disks, and gaining independence from a single
hypervisor hardware ;)
Cheers,
Colin
Hello all.
Sorry if this mail is off topic of the mail-list, but am not sure which one is right for my question.
I am writing a program which needs to know exact environment in which it is running. In case of Windows I simply use GetVersionEx and then analyze dwMajorVersion + dwMinorVersion which is enough for my case (then I know which WIN API calls I should use). But I stuck how to recognize that my program runs in ReactOS. I failed to find any docs about it. Any help is appreciated.
P.S. I am not well experienced in WIN API, so if someone gives me an example it will be great.
Hello all,
I have just noticed that ReactOS, when in debug configuration, will only
boot if an output console is set up.
Won't boot if minicom (for example) is not running...
Is that expected?
hello all,
im planning to use ReactOS at a foundation here in Madrid, which is
dedicated to people with intellectual disabilities
he point is, they are using mostly Windows 10, so they are using Win10 apps
are bug reports about Win10 apps acceptable?