Mark, I'll try to answer your question: it is important to understand that the kohadevbox installs the koha-common package, creates a 'kohadev' instance and then gitifies it. So the configuration files are those shipped by the used packages. And then, it will depend on when Mirko builds the so-called nightly packages [1] but theoretically, 'vagrant destroy && vagrant up' should get you an updated koha-common package and create the instance with updated config files. There can be some usual issues too, like falling to have koha-conf.xml out of sync from source install, and the like. It is not that common, but can happen. BTW: WyTF is a t/ test requiring koha-conf.xml? That's certainly breaking the build process. Hope it clarifies [1] Sometimes we break packages building and it is not Mirko's fault, but the nightly's don't get updated as fast as expected. El mar., 3 de ene. de 2017 2:21 PM, Mark Tompsett <mtompset@hotmail.com> escribió:

Greetings,

prove t/SMS.t C4/SMS.pm line 98

GPML, Mark Tompsett

*From:* Jonathan Druart <jonathan.druart@bugs.koha-community.org> *Sent:* Tuesday, January 03, 2017 2:37 AM *To:* Koha-devel <koha-devel@lists.koha-community.org> *Subject:* Re: [Koha-devel] KohaDevBox question...

Hi Mark, on which test is the warning raised?

On Tue, 3 Jan 2017 at 01:52 Mark Tompsett <mtompset@hotmail.com> wrote:

Greetings,

I was running a ‘prove t’ on the kohadevbox which I just vagrant up jessie’d from scratch the other night. I encountered a message about an uninitialized variable which led me to bug 13029. This added a configuration item to the koha-conf.xml file. Will this auto-correct with a vagrant destroy and vagrant up in the near future (before 17.05’s release)? I can add the item manually myself, but I’d hate to have to remember this the next time I might destroy and up.

GPML, Mark Tompsett _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

------------------------------ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

Can we have a safe master packages repo in which only successful builds are included? We rely on the master packages fro recreating the devbox for our daily duties. El vie., 6 ene. 2017 a las 12:31, Mirko Tietgen (<mirko@abunchofthings.net>) escribió:

Hi,

Tomas Cohen Arazi schrieb am 03.01.2017

...

[1] Sometimes we break packages building and it is not Mirko's fault, but the nightly's don't get updated as fast as expected.

Apologies, they are broken at the moment. There is a project or two I have to finish before I can look into it, but I hope to fix it this month.

Cheers,

Mirko _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F