October 2010 - binary-builders

[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

[Context] ConTeXt Minimals: some statistics of usage
by Mojca Miklavec 14 Oct '10

14 Oct '10

Hello, As I have promised some time ago here is some raw statistics from the last month (older statistics is not kept on server): There are 29917 different jobs. There are 379 different IP numbers. Bytes sent: 14,451,171,433 The following numbers represent unique IP numbers that have tried to download minimals for a specific platform: platform linux: 94 platform linux-64: 85 platform osx-64: 68 platform mswin: 65 platform osx-intel: 48 platform osx-ppc: 15 platform freebsd-amd64: 3 platform freebsd: 1 (missing: kfreebsd, linux-ppc, solaris) Mojca (I need to figure out how to use sqlite [and how to install the bindings] before we can start collecting more statistics over time :)

4 17

[Context] messing up with SVN
by Mojca Miklavec 11 Oct '10

11 Oct '10

Dear binary builders, I might mess up with SVN repository containing the binaries a bit today/tomorrow. So please don't run the updates yet. Once it's done, I will let you know. (I plan to drop building XeTeX and pdfTeX by default, though I will probably leave both source repositories there ... just in case that anyone *will* want to build or test them.) Mojca

4 5

[Context] tlcontrib
by Taco Hoekwater 08 Oct '10

08 Oct '10

Hi, I guess most of you are on dev-context as well, but in any case: Please, if you have moment to spare, have a good look at the TLContrib website and associated repository: http://tlcontrib.metatex.org/ The system should now be ready for the initial kickoff (I hope). The new repository already contains context 2010.07.30, luatex 0.63.0, metapost 1.502. However, many of the binary packages for luatex and metapost are still missing, even though they already exist in the context minimals. It would be nice to fill in at least the most obvious architectures (win32/macosx) before announcing tlcontrib on a larger scale. The unix luatex packages should contain the following: luatex texlua -> luatex symlink texluac -> luatex symlink dviluatex -> luatex symlink The unix metapost packages should contain: mpost dvitomp -> mpost symlink mfplain -> mpost symlink (win32 is a special case, all others use the same file structure) Missing to this date are the following: luatex.alpha-linux luatex.amd64-freebsd luatex.amd64-kfreebsd luatex.i386-cygwin luatex.i386-freebsd luatex.i386-kfreebsd luatex.i386-netbsd luatex.i386-solaris luatex.mips-irix luatex.powerpc-aix luatex.powerpc-linux luatex.sparc-linux luatex.sparc-solaris luatex.universal-darwin luatex.win32 luatex.x86_64-solaris metapost.alpha-linux metapost.amd64-freebsd metapost.amd64-kfreebsd metapost.i386-cygwin metapost.i386-freebsd metapost.i386-kfreebsd metapost.i386-netbsd metapost.i386-solaris metapost.mips-irix metapost.powerpc-aix metapost.powerpc-linux metapost.sparc-linux metapost.sparc-solaris metapost.universal-darwin metapost.win32 metapost.x86_64-darwin metapost.x86_64-solaris It would be really cool if the context minimals builders would go to the trouble of registering at tlcontrib.metatex.org and publishing the packages that match the binaries they take care of in the minimals. Best wishes, Taco

3 5

[Context] Launchpad Bugs Re-enabling Auto Expiring Bugs
by deryck.hodge＠canonical.com 05 Oct '10

05 Oct '10

Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project ConTeXt distribution at https://launchpad.net/context What's going to change ----------------------- Right now, the bug expiry option is enabled for ConTeXt distribution but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including ConTeXt distribution. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/context/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Note: You may have already received this notification. Please forgive the additional email if that is the case. We wanted to be sure we contacted all the approproiate people for your project. Also, the previous emails were sent before the changes to your project settings. You should double check to make sure the settings are now what you want for automatic bug expiry. Deryck Hodge Launchpad Bugs Team Lead

1 0

[Context] Launchpad Bugs Re-enabling Auto Expiring Bugs
by deryck.hodge＠canonical.com 05 Oct '10

05 Oct '10

Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project ConTeXt distribution at https://launchpad.net/context What's going to change ----------------------- Right now, the bug expiry option is enabled for ConTeXt distribution but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including ConTeXt distribution. What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/context/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead

1 0