Someone's got to help me. I can't figure out how to make this thing
patch the rostests directory.
Le 31/10/2016 à 11:15, buildbot(a)reactos.org a écrit :
> The Buildbot has detected a failed build on builder Build GCCLin_x86 while building ReactOS.
> Full details are available at:
> https://build.reactos.org/builders/Build%20GCCLin_x86/builds/16201
>
> Buildbot URL: https://build.reactos.org/
>
> Buildslave for this Build: HotelLux
>
> Build Reason: A build was forced by 'jgardou <jgardou@localhost>': Test ROSTESTS-155
> Build Source Stamp: HEAD
> Blamelist:
>
> BUILD FAILED: failed patching
>
> sincerely,
> -The Buildbot
>
>
>
>
>
Hello,
Let me invite you to the monthly status meeting taking place today, 27th
of October, 19:00 UTC.
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
Alternatively we'll do it in #reactos-meeting on Freenode, depending on
our admins mood.
Please send agenda proposals to me before the meeting so we don't waste
time trying to setup the agenda directly during the meeting.
Regards,
Aleksey Bragin
On 2016-10-27 00:06, hbelusca(a)svn.reactos.org wrote:
> - /* Sundry checkboxes */
> + /* Other checkboxes */
Not sure how this "fixes" anything? Those are synonyms?
Hi all,
Thanks to Dmitry Chapyshev's generous donation of rare FB-DIMM memory
modules, our Buildserver has enough RAM for the Win7 buildslave VM now.
I've fired it up and while builds are much slower than before, they are
at least being done again!
Note that Doxygen, ISO hosting, and all three buildslaves are on a
single HDD-backed server right now, so don't expect any performance
miracles.
I'm counting on Aleksey here to get us our remaining servers back this
month :)
Unfortunately, our HDDs were also lacking space, so I had to move the
public "bootcd_old" folder from iso.reactos.org to another (private)
place. It contained BootCD ISOs from 2009 to 2012, totalling 421GB.
Any idea how to deal with them in the long run? I can basically think of
4 possibilities:
* We remove ISOs older than 4 years, because nobody would really do
regression-testing with them.
* We buy additional HDDs every year and continue to host them ourselves
just next to the newer ISOs.
* We find a free file hosting service for OSS projects that can cope
with these amounts of data. Not sure SF.net is the right choice here..
* We choose a paid data storage service like Amazon AWS.
As always, comments are very welcome!
- Colin
Hi all!
For those of you who experienced Login problems with ReactOS Services
such as BuildBot, Mumble or SVN, I have cleaned up and applied some
fixes to our LDAP directory today. All known problems should be fixed now!
If you still experience such problems, please reply to this mail.
- Colin
Hi all,
For implementing the RpcBindingServerFromClient rpcrt4.dll API function
needed by my Printing Stack, I need to know how to retrieve the computer
name of a named pipe client.
Vista and later implement GetNamedPipeClientComputerName in kernel32.dll
which does exactly this, but this is neither supported under Windows
Server 2003 nor implemented in ReactOS and WINE.
Determining client information is a basic feature of network
communication, so it should be possible under Windows 2003 as well.
Additionally, RpcBindingServerFromClient returns the proper computer
name of the client, when using named pipes over the ncacn_np transport.
It must have got it somehow.
Hoping for some ideas from your side!
Colin