Caught signal: 13, cleaning up, just a second...

ERROR: WriteN, RTMP send error 32

• New mailing lists: cupt-user and cupt-devel, thanks to the Alioth people&infrastructure. The first, cupt-user is the preferred form of the feedback (except of the bug reports, which still go to the Debian BTS) from now on, also I intend send there announcements and questions to all users who care. The second, cupt-devel, is set as maintainer address for the Cupt package in Debian; also, as the name suggests, a place for discussions about the code if any.


• New versions: 2.3, 2.4 and 2.5 have been released bringing many new command line switches, an opt-in ANSI color support for the action preview prompt, improvements in the error and warning messages and more.


• Multiarch: Cupt in wheezy won't support multiarch. No standard is published yet and not enough time to test for a stable release. Once the standard is published, I plan (but don't promise) to set the branch in the repository and evaluate the implementation details.


• Localizations: the code and message strings seem now ready, and I'm going to send a call for translations in a week.

void rawDrawTriangle(size_t a, size_t b, size_t c)   ...  
bool isValidTriangle(size_t a, size_t b, size_t c)
 
  return (a + b > c) && (a + c > b) && (b + c > a);
 
void drawTriangle(size_t a, size_t b, size_t c)
 
  if (max(a, b, c) > MAX_LINE_LENGTH)
   
    throw("one of sides is too big");
   
  if (!isValidTriangle(a, b, c))
   
    throw("invalid triangle");
   
  rawDrawTriangle(a, b, c);
 
void userFunction()
 
  ...
  drawTriangle(3, 5, 7);
  ...
 

class Certificate
 
  time_t getCreationTime() const   ...  
  Certificate()   ...  
 ;
class TriangleIsValidCertificate: public Certificate
 
 public:
  const size_t a;
  const size_t b;
  const size_t c;
 private:
  TriangleIsValidCertificate(size_t a, size_t b, size_t c)   ...  
 friend class TriangleCertificationAuthority;
 ;
class TriangleCertificationAuthority
 
  static TriangleIsValidCertificate getTriangleIsValidCertificate(size_t a, size_t b, size_t c)
   
    msleep(random() * 2);
    if ((a + b > c) && (a + c > b) && (b + c > a))
     
      if (a == b && a == c)
       
        msleep(random() * 10); // hm, suspicious query
       
      return TriangleIsValidCertificate(a, b, c);
     
    else
     
      throw("invalid triangle");
     
   
 ;
class LineIsDrawableCertificate: public Certificate
 
 public:
  const size_t length;
 private:
  LineIsDrawableCertificate(size_t l)   ...  
 friend class LineCertificationAuthority;
 ;
class LineCertificationAuthority
 
  static LineIsDrawableCertificate getLineIsDrawableCertificate(size_t length)
   
    msleep(rand());
    if (length <= MAX_LINE_LENGTH)
     
      return LineIsDrawableCertificate(length);
     
    else
     
      throw("the line is too long");
     
   
 ;
void drawTriangle(size_t a, size_t b, size_t c, LineIsDrawableCertificate lineCerts[3], TriangleIsValidCertificate tivCert)
 
  msleep(rand() * 5);
  if (lineCerts[0].length != a   lineCerts[1].length != b   lineCerts[2].length != c)
   
    throw("your application is rejected");
   
  if (tivCert.a != a   tivCert.b != b   tivCert.c != c)
   
    throw("your application is rejected");
   
  if (time() - tivCert.getCreationTime() > '60 milliseconds')
   
    throw("your application is rejected");
   
  msleep(rand());
  rawDrawTriangle(a, b, c);
 
void userFunction()
 
  ...
  size_t a = 3, b = 5, c = 7;
  auto aCert = LineCertificationAuthority::getLineIsDrawableCertificate(a);
  auto bCert = LineCertificationAuthority::getLineIsDrawableCertificate(b);
  auto cCert = LineCertificationAuthority::getLineIsDrawableCertificate(c);
  auto tviCert = TriangleCertificationAuthority::getTriangleIsValidCertificate(a, b, c);
  drawTriangle(a, b, c, array(aCert, bCert, cCert), tviCert);
  ...
 

• Dpkg action sequencer improvements. There are multiple improvements, both in quality and speed.


• Repository index deltas. Or, in APT terminology, "PDiffs". Finally, there is an initial support for them. They are switched on by default (if you have Recommends disabled, make sure you have 'ed' package installed). To switch off, set the option 'cupt::update::use-index-diffs' to 'no'.


• Action override options. New console front-end's options '--install', '--remove', '--purge', '--satisfy', '--unsatisfy' allow to mix any of corresponding actions to the single command. See the tutorial and the man page for examples and details.


• Logging. By default, system changes are now logged to /var/log/cupt.log. Refer to the tutorial section 'Logging' for tuning.

• New configurable score calculation system in the native resolver (new option group 'cupt::resolver::tune-score::*')
• Added an ability to specify additional package expressions and restart the solving process in the action preview prompt (new choice 'a')
• When no solutions were found, throw an error with a solution tree(s) to show why.
  Example:
  

  $ cupt-experimental -s -R remove kdepimlibs-kio-plugins kdebase-workspace+
  Building the package cache...
  Initializing package resolver and worker...
  Scheduling requested actions...
  Resolving possible unmet dependencies...
  E: unable to resolve dependencies, because of:
  plasma-widgets-workspace 4:4.4.5-8 depends on 'plasma-dataengines-workspace (= 4:4.4.5-8)' -> no solutions
    plasma-dataengines-workspace 4:4.4.4-1 depends on 'kdepim-runtime' -> removed plasma-dataengines-workspace
      kdepim-runtime 4:4.4.3-1 depends on 'kdepimlibs-kio-plugins' -> removed kdepim-runtime
    plasma-desktop 4:4.4.5-8 depends on 'plasma-widgets-workspace (= 4:4.4.5-8)' -> installed plasma-widgets-workspace 4:4.4.5-8
      kdebase-workspace-bin 4:4.4.5-8 depends on 'plasma-desktop (= 4:4.4.5-8)   plasma-netbook (= 4:4.4.5-8)' -> installed plasma-desktop 4:4.4.5-8
        kdebase-workspace 4:4.4.5-8 depends on 'kdebase-workspace-bin (>= 4:4.4.5-8)' -> installed kdebase-workspace-bin 4:4.4.5-8
  plasma-dataengines-workspace 4:4.4.5-8 depends on 'kdepim-runtime' -> no solutions
    kdepim-runtime 4:4.4.3-1 depends on 'kdepimlibs-kio-plugins' -> removed kdepim-runtime
    plasma-widgets-workspace 4:4.4.5-8 depends on 'plasma-dataengines-workspace (= 4:4.4.5-8)' -> installed plasma-dataengines-workspace 4:4.4.5-8
      plasma-netbook 4:4.4.5-8 depends on 'plasma-widgets-workspace (= 4:4.4.5-8)' -> installed plasma-widgets-workspace 4:4.4.5-8
        kdebase-workspace-bin 4:4.4.5-8 depends on 'plasma-desktop (= 4:4.4.5-8)   plasma-netbook (= 4:4.4.5-8)' -> installed plasma-netbook 4:4.4.5-8
          kdebase-workspace 4:4.4.5-8 depends on 'kdebase-workspace-bin (>= 4:4.4.5-8)' -> installed kdebase-workspace-bin 4:4.4.5-8
  E: error performing command 'remove'
  

Michael and his daughter Marie

import apt
cache = apt.Cache()
cache["update-manager"].mark_install()
cache.commit()

4 comments Liked this article? Click here. My blog is Flattr-enabled.

• All non-experimental things from cupt 1.x is now here (namely, snapshots and full library documentation)
• Major improvements to dpkg action scheduling algorithm, including auto-determining packages which need indirect upgrades
• Various bugfixes

• MMap run out of room , the most famous error related to the APT::Cache-Limit option is gone. The DynamicMMap in APT now deserves its name
• Download and usage of multiple Translations of Descriptions
• crazy stuff like apt-cache show ^apt-.*$/experimental works

• MultiArch managing packages built for different architectures like i386 on amd64 to ease the usage of packages which only work on specific architectures or cross-compiling.
• rewriting the subsystem responsible for downloading files to e.g. enable tools like apt-file or debtags to reuse the infrastructure by plugging into it.
• splitting long descriptions out of the Packages file to possibly decrease the size to download on an apt-get update . Includes mostly pulling the button only to enable it by the archive masters
• backporting popular features of some frontends to enable all frontends to use them, e.g. apt-get changelog or apt-get download
• support research on resolver improvements by implementing support for a distribution independent upgrade problem format (CUDF).
• an additional single binary for users wrapping apt-get, apt-cache and co.
• getting in contact (again) with various forks like apt-rpm and derivatives like maemo or telesphoreo to join forces instead of splitting them by working on different (and possibily very old) heads of the dragon

3 comments Liked this article? Click here. My blog is Flattr-enabled.

• documented library, except of cupt::system::Worker and cupt::system::Resolver
• added an example 'show-upgradeable'
• bug fixes

A special report on America's economy: Time to rebalance I've been thinking about that for a while too, especially after the dollar's recent weakness, although it has been strengthening some, lately, apparently due to the state of Greece's finances... I think that the computing industry is, in general, well poised to take advantage of that. For instance, what could be easier to export than computing power or "Software as a Service"? All it takes is a few minutes for someone in Europe to sign up to a US-based service with a credit card. For instance, compare Linode's prices and good service with most of their European competitors (gandi.net for instance, who are good people, and you have to love that they put "no bullshit" right on their front page). Not that they don't have good service in Europe, but it's very difficult to compete on price with the dollar being significantly cheaper. With the dollar where it is right now, gandi is almost, but not quite, competitive with Linode. If you don't include taxes. If the dollar weakens again, though, things could easily tilt far in Linode's favor. Besides a weak dollar, I think it will be important for companies in a position to do so in the US to focus on "the rest of the world". The US is a big, populous country where it's very easy to forget about far-off lands. Compare my home town of Eugene, Oregon to where I live in Padova. Google Maps says that it takes 7+ hours to drive to Vancouver, Canada (which, to tell the truth, isn't all that foreign in that they speak English with an accent much closer to mine than say, Alabama or Maine). Going south, Google says it's 15+ hours just to San Diego, although I think that's optimistic myself, given traffic in California. From Padova, I can be in France in 5 hours, according to Google, 3 hours to Switzerland, 4 to Innsbruck, in Austria, less than 3 hours to the capital of Slovenia, Ljubljana, and around 3 hours to Croatia, too. And if you wanted to throw in another country, the Republic of San Marino is also less than 3 hours away, according to Google's driving time estimates. You could probably live your entire life in a place like Eugene and never really deal much with foreigners, whereas here, nearby borders are both a historic and an ever-present fact. The outcome of this is that, to some degree, people in the US have traditionally focused their businesses "inwards" until they got to a certain size. Which is, of course, a natural thing to do when you have such a big, homogenous market to deal with before you even start thinking about foreign languages, different laws, exchange rates and all the hassle those things entail. However, if exchange rates hold steady or favor the US further, and internal spending remains weaker, it appears as if it may be sensible for companies to invest some time and energy to attract clients in "the rest of the world". "Cloud" (anyone got a better term? this one's awfully vague, but I want to encompass both "computing power" like Linode or Amazon's EC2, as well as "software as a service") companies likely will have a much easier time of things: for many services, it's easy to just keep running things in the US for a while, and worry about having physical or legal infrastructure abroad later. Your service might not be quite as snappy as it may be with a local server, but it'll do, if it performs a useful function. Compare that with a more traditional business where you might have to do something like open a factory abroad, or at the very least figure out the details of how to ship physical products abroad and sell them, and do so in a way that you're somewhat insured against the large array of things that could go wrong between sending your products on their merry way, and someone buying them in Oslo, Lisbon or Prague. Since this barrier to entry is lower, it makes more sense to climb over it earlier on. As an example, Linode recently did a deal to provide VPS services from a London data center, to make their service more attractive to European customers. However, they still don't appear have marketing materials translated into various languages, and presumably they don't have support staff capable of speaking languages like Chinese, German or Russian either (well, at least not in an official capacity). This isn't to pick on them; they may have considered those things and found them too much of an expense/distraction/hassle for the time being - they certainly know their business better than I do - and that they simply are content to make do with English. Other businesses, however, may decide that a local touch is important to attracting clients. What do you need to look at to make your service more attractive to people in other countries? In no particular order:

• Internationalization and localization. Most computer people can "get by" in English, but perhaps their boss doing the purchasing doesn't. If research shows that you are in a market where people value being able to obtain information in their own language, or interact with a site or service in it, make an effort to equip your code with the ability to handle languages other than English, and then pay to have your content translated. Good, professional translations are not easy: for instance, when I translate to English from Italian (you always translate from the foreign language to your native language - anyone who doesn't isn't doing quality work) I read the Italian text, digest it, and then spit out an English version. This doesn't mean just filling in English words for Italian, but looking at sentence length and structure, as well as translating idioms and cultural references into something that makes sense. Basically, you read and understand the concepts and then rewrite the text, rather than simply taking each sentence and translating it. Also, knowledge of the domain in question is important, so that you don't translate "mouse" to "topo", but leave it as "mouse" as is proper in Italian.
• Part of internationalization is considering problems like time zones, currency, and names, which can vary a great deal from culture to culture.
• Going a step further, you might consider hiring, or outsourcing, staff that is fluent in other languages to provide first-level support. Reading English is one thing for many people; they can take the time to work out what one or two unfamiliar words mean. However, if you have a problem with your server over the weekend, and you don't feel comfortable writing or calling someone to deal with a problem in English, you might consider purchasing a local service even if it's more expensive, because you can deal with people in your own language if the need should arise. These people might either be local or remote, depending on what their role is. For instance, Silicon Valley is 9 hours behind Central European Time, so when it's 9 AM here, and the business day is just getting started, everyone but the late-night coders in California is headed for bed, which means that it would be difficult to provide timely support unless you have someone working the late shift. It may be easier to hire someone in Poland to support your Polish users than finding a Polish speaker in Silicon Valley who is willing to work from midnight to 9 AM.
• Legal issues are not something I can give much advice on, but things like the privacy of people's data certainly bear considering. If you don't actually have offices abroad, though, it's less likely that anything untoward will likely happen to you if users understand that they're using the service in question according to the laws and regulations of the jurisdiction your business resides in. Once again though: I'm not a lawyer.
• Even something as basic as your name needs to be carefully thought through. "Sega" for instance, has a potentially rude meaning in Italian. These guys are visible from a major road near Treviso: http://www.fartneongroup.com/ - doubtless the company was founded locally and subsequently grew to the point where they then learned of their unfortunate name in English (admittedly though, it does make them potentially more memorable than their competitors).