May 2009 - binary-builders - NTG Mailing Lists

[Context] [Bug 379146] [NEW] mtxrun
by Mojca Miklavec 11 Jun '11

11 Jun '11

Public bug reported: from Alan BRASLAU, untested I did a fresh install of the minimals today and observed a fleeting, obscure mtxrun bug: $ context myfile did not find the script mtx-context.lua $ mtxrun --script /usr/local/context/tex/texmf-context/\ scripts/context/lua/mtx-context.lua myfile ran fine, as now does all subsequent runs of "context myfile". So something gets initialized, but is not found by default. You will only notice this upon a (totally) fresh install. ** Affects: context Importance: Undecided Status: New -- mtxrun https://bugs.launchpad.net/bugs/379146 You received this bug notification because you are a member of ConTeXt distribution team, which is the registrant for ConTeXt distribution. Status in ConTeXt distribution: New Bug description: from Alan BRASLAU, untested I did a fresh install of the minimals today and observed a fleeting, obscure mtxrun bug: $ context myfile did not find the script mtx-context.lua $ mtxrun --script /usr/local/context/tex/texmf-context/\ scripts/context/lua/mtx-context.lua myfile ran fine, as now does all subsequent runs of "context myfile". So something gets initialized, but is not found by default. You will only notice this upon a (totally) fresh install.

6 8

Re: [Context] [NTG-context] updates without rsync
by Mojca Miklavec 30 May '09

30 May '09

[patrick - only (2) is for you] On Fri, May 29, 2009 at 18:07, Diego Depaoli <trebestie(a)gmail.com> wrote: > 2009/5/29 Peter Münster <pmlists(a)free.fr>: >> If this is not possible, perhaps the firewall is open for http? Then >> someone else with a Windows PC could prepare for you an archive and put it >> on an http-server? > Why not do it directly on minimals.contextgarden.net? > > [OT - for binaries maintainer] Even sources should be packaged in a zip file. > After recent Mojca's changes I rsynced for a whiiiiiiiiiiiiiiiiiiiiiiiiiiiiile > [OT - for binaries maintainer] Even sources should be packaged in a zip file. > After recent Mojca's changes I rsynced for a whiiiiiiiiiiiiiiiiiiiiiiiiiiiiile 1.) packaging sources as zip files would mean having to download everything every time when the most tiny bit changes. 2.) There used to be problems with download speed on Taco's server (I don't know if that's still the case). But now that there's some more space on garden, we could put those file on the garden instead if that would help. It seems to be only 300 MB, so that's minor in comparison to all other stuff that eats space on the server. (Patrick: I forgot if I replied you, but you definitely may remove the old copy from the old server.) 3.) We take svn version of XeTeX and pdfTeX. There are usually no problems with those as only a single file changes. But LuaTeX and metapost come from "tags". Whenever Taco makes a new "tag", svn has a brilliant feature to "copy the files" and all the files get a recent timestamp. Consequently all the timestamps of all files change (isn't that nice?) every time when a new luatex version is released. 4.) This update was an exceptional case. Maybe I did a mistake by not issuing "svn change repositoryname" (the syntax is different, don't know it by heart), but by deleting and fetching all the files from scratch, just to make sure that everything still works fine. But I'm almost sure that all the timestamps got changed. 5.) I added a -c switch to fetching the updates. This makes updating (negotiating which files to fetch) slower, but skips updating files whose timestamps differ (and not contents). It calculates the checksum of every file before asking server what to fetch. I'll leave that switch there for a while to see what difference it makes. Mojca

3 2

Re: [Context] [dev-context] Supelec is back
by Mojca Miklavec 29 May '09

29 May '09

On Mon, May 18, 2009 at 23:07, Taco Hoekwater wrote: > Hi all, > > For those of you who have not noticed yet: the foundry.supelec.fr > server is back online with new hardware and software, and is running > better than ever. > > There is a small snag that some of you may have noticed already: > you will have to delete your current checkouts of all subversion > projects, because the machine now solely talks DAV (and besides > that, the repository UUIDs have changed as well). Taco, thanks for the notice. So let me fix and test the scripts and repositories first before you rerun the building scripts. Fresh checkouts seem to run forever ... (I forgot that I should not be fetching the whole luatex with all the tags.) I'll notify you once binary building will be ready again. (Maybe it works now, but there's probably no need to build right away anyway.) Mojca

1 1

[Context] [Bug 381437] [NEW] return a nice error for rsync connectivity problems
by Mojca Miklavec 28 May '09

28 May '09

Public bug reported: If user is behind firewall or network is down, return error rather than trying to call rsync dozens of times. ** Affects: context Importance: Undecided Status: New -- return a nice error for rsync connectivity problems https://bugs.launchpad.net/bugs/381437 You received this bug notification because you are a member of ConTeXt distribution team, which is the registrant for ConTeXt distribution. Status in ConTeXt distribution: New Bug description: If user is behind firewall or network is down, return error rather than trying to call rsync dozens of times.

1 0

[Context] some changes in binary compilation
by Mojca Miklavec 05 May '09

05 May '09

Hello, I'm going to change some aspects of binary compilation in order to enable storing multiple versions of luatex. I have to watch out to make the changes more or less simultaneous. There has been a recent change/patch in pdftex, but assuming that Taco is not going to release the next version of LuaTeX or metapost in the next few days ... I just wanted to warn you that compiling the binaries until my next notice might fail if you start compiling in the wrong moment during transition. After that I will ask you to update build-binaries script to account for the changes. Mojca

1 2

[Context] TL repositories on contextgarden
by Mojca Miklavec 05 May '09

05 May '09

Hello Norbert, I finally arrived home (despite oversleeping the station in Wien it all turned out ok :) I'm reading your conversation from TL list (online, not subscribed as it was distracting me too much to read all the TeX-related lists). I noticed the problem of updates (apparently the version). I tried to set the version to 100000, but I made a typo, so it didn't help. Apparently the version in TL got update for whatever reason and I didn't put the repository into cron (probably I should, I was just waiting for the patch). I'm thinking about the following: - if ConTeXt version gets updated, call the script that only updates ConTeXt - if repository with binaries updates, run the script and update all the luatex-s I know that I should try this before asking, but just curious: if I run the script and version gets updated by one - will the clients compare md5sum or will the clients update just because the version has been updated by one? In any case it probably makes sense if there have been any updates before unconditionally increasing the version by one. I will most probably decide to make sure that the version gets updated to at least 1000 above TL since users that updated from garden once probably don't intend their updates to be reverted next time when they update the rest of the packages without specifying garden repository explicitely. Assuming that I can parse the version of context and luatex before creating TL package - what's the most appropriate field/position to put the version information there? Thanks a lot, Mojca

2 2

[Context] solaris to be removed
by Mojca Miklavec 02 May '09

02 May '09

Hello, Most binaries for Solaris (intel and sparc) are outdated. I'm going to remove files for solaris from server unless someone is willing to catch up and send recent binaries. Mojca

1 0