A bizarre closed user-tracking schism is rebased from shaky grounds to an unexisting target. It is sad to see this continous decline due to unchallenged decisions.
I've provided a new patch #701061 for
lintian to warn about font packages that are not marked as Multi-Arch
foreign or allowed. Its already included in the lintian by Neils
Thykier and will be part of version
2.5.12. The following tag has been implemented
font-package-not-multi-arch-foreign
Here by I request all font package maintainers to consider marking their packages as Multi-Arch foreign. I also request people to join us on pkg-fonts-devel and help us doing this for all font packages maintained by the team, we really lack people in the team.
I just received a WD 500GB Blue, to replace the hard drive of my wife's computer. First thing after unpacking: start to test. And I was right to do it... there are bad blocks on it.
The story: I tend to do proactive replacement of hard drive, to avoid losing too much data or be in hurry when the current one fails. There are two ways to monitor a hard drive:
Jan 24 18:16:08 foo kernel: [ 1965.343980] ata5.00: exception Emask 0x50 SAct 0x39 SErr 0x800 action 0x6 frozen Jan 24 18:16:08 foo kernel: [ 1965.343991] ata5.00: irq_stat 0x08000000, interface fatal error Jan 24 18:16:08 foo kernel: [ 1965.344001] ata5: SError: HostInt Jan 24 18:16:08 foo kernel: [ 1965.344036] ata5.00: failed command: READ FPDMA QUEUED Jan 24 18:16:08 foo kernel: [ 1965.344055] ata5.00: cmd 60/08:00:18:31:44/00:00:1a:00:00/40 tag 0 ncq 4096 in Jan 24 18:16:08 foo kernel: [ 1965.344059] res 40/00:2c:e6:c2:fd/00:00:26:00:00/40 Emask 0x50 (ATA bus error) Jan 24 18:16:08 foo kernel: [ 1965.344071] ata5.00: status: DRDY Jan 24 18:16:08 foo kernel: [ 1965.344081] ata5.00: failed command: WRITE FPDMA QUEUEDIt is a good time to think about changing your hardrive -- but it is maybe too late. Smartmontools (aka smartd) is dedicated tool to monitor hard drives and do a good job. I think it is not installed by default in Debian, but it should be. It scans your hard drive for SMART capabilities and monitor the health of the HD using internal tools. In the case of bad blocks, you will start to see entry like that:
Feb 17 14:05:17 bar smartd[1268]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors Feb 17 14:35:17 bar smartd[1268]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectorsObviously when you see this log, it is also a good time to change your hard drive. In the case of my wife's HD, I just got data from logcheck. It means that the error is not that important (transient failure, something is wrong but the HD can cope with it). But I still decided to get a new one for my wife. Whenever, I receive a new drive, the first thing I do is to check it for errors. You can do that using the program badblocks in write mode. It takes ages to test (count up to 1 day for 1TB on USB), but at the end you know that you have a good candidate -- where it is worth install your data. You just have to follow this procedure
The following warning/error was logged by the smartd daemon: Device: /dev/sda [SAT], 15 Currently unreadable (pending) sectorssyslog entries:
Mar 2 20:52:57 foo kernel: [ 8317.419715] ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Mar 2 20:52:57 foo kernel: [ 8317.419724] ata4.00: irq_stat 0x40000008 Mar 2 20:52:57 foo kernel: [ 8317.419732] ata4.00: failed command: READ FPDMA QUEUED Mar 2 20:52:57 foo kernel: [ 8317.419747] ata4.00: cmd 60/80:00:00:af:08/00:00:28:00:00/40 tag 0 ncq 65536 in Mar 2 20:52:57 foo kernel: [ 8317.419750] res 41/40:00:65:af:08/00:00:28:00:00/40 Emask 0x409 (media error) <F> Mar 2 20:52:57 foo kernel: [ 8317.419758] ata4.00: status: DRDY ERR Mar 2 20:52:57 foo kernel: [ 8317.419764] ata4.00: error: UNC Mar 2 20:52:57 foo kernel: [ 8317.423959] ata4.00: configured for UDMA/133I am not blaming any particular brand (like Western Digital), all computer parts I have ever bought had to follow the same procedure and it is a known fact that computer parts as a non-zero percentage of chance to be DOA (dead on arrival) or after a few weeks. But as a consumer you should be aware of that and take action to avoid spending 10h configuring your computer to see it failing after a week... The waste of time to test is a win on the long term.
Alas. The blogosphere has been slammed with discontent.
Count me as one of them.
It s been a long time since the last position (I ve held) of significance in Ubuntu, a LoCo Council Member, which I left with a heavy heart.
I felt, at the time, that Ubuntu, The Community was no longer in control of Ubuntu The Distro .
Technical opinions of Ubuntu community members started to get disregarded (starting with the gawd-awful Yahoo search switch), and it continued to get worse as Canonical stopped becoming a contributor to Ubuntu and started becoming it s sole guiding force.
In comes the mess called Ubuntu One which, for the record, is a wrong name, it s not Ubuntu in any sense, it s not Community driven, it just uses Ubuntu as one of it s platforms.
Trading on Ubuntu s good name started this mess.
Slowly, like the ship of theseus, Canonical started to swap out bit by bit until nothing was left without Canonical assignment.
I always assumed it was so that selling the code for another company to use the code for non-free purpose was the reason. Oh well.
Look at us now: Starting off on an ill-thought out path because others are unwilling to say they just didn t understand the whole problem.
This is a long way of saying:
Ex-Ubuntu ers: You re welcome in Debian. I ve set up #ubuntu-expats on oftc. Please join us. You re welcome there.
Working in Debian has been an absolute dream; it feels like contributing to Ubuntu in the early days.
Come. Have a say. Re-join a Community that isn t just Like us on Facebook .
I still consider myself an Ubuntu Community Member, but I don t think there s any community left.
Mark Shuttleworth recently critized Jonathan Riddell for proposing Xubuntu and others join the Kubuntu community. I thought I could make a few amendments to Mark s writing:
Jonathan Mark says that Canonical Kubuntu is not taking care of the Ubuntu community.
Consider for a minute, Jonathan Mark, the difference between our actions.
Canonical Kubuntu, as one stakeholder in the Ubuntu community, is spending a large amount of energy to evaluate how its actions might impact on all the other stakeholders, and offering to do chunks of work in support of those other stakeholder needs.
You, as one stakeholder in the Ubuntu community, are inviting people to contribute less to the broader project [all the X and Wayland -based desktops], and more to one stakeholder [Unity and Mir].
Hmm. Just because you may not get what you want is no basis for divisive leadership.
Yes, you should figure out what s important to Kubuntu Ubuntu Unity and Mir, and yes, you should motivate folks to help you achieve those goals. But it s simply wrong to suggest that Canonical Kubuntu isn t hugely accommodating to the needs of others, or that it s not possible to contribute or participate in the parts of Ubuntu which Canonical Kubuntu has a particularly strong interest in. Witness the fantastic work being done on both the system and the apps to bring Ubuntu Plasma to the phone and tablet. That may not be your cup of tea, but it s tremendously motivating and exciting and energetic.
See Mark? I only needed to do a little search and replace on your words and suddenly, meaning is completely reversed!
Canonical started looking only after its own a couple of years ago and totally dumped the community. Many people have noticed this and written about this in the past two years.
How dare you say Jonathan or anyone from Kubuntu is proposing contributing less to the broader community? The broader community uses X and/or Wayland.
Canonical recently came with Mir, a replacement for X and Wayland, out of thin air. Incompatible with X and Wayland.
No mention of it at all to anyone from X or Wayland.
No mention of it at FOSDEM one month ago, even though I, as the organizer of the Cross Desktop DevRoom, had been stalking your guy for months because we wanted diversity (and we got it: Gnome, KDE, Razor, XFCE, Enlightenment, etc, we even invided OpenBox, FVWM, CDE and others!). I even wrote a mail to you personally warning you Unity was going to lose its opportunity to be on the stand at FOSDEM. You never answered, of course.
Don t you think Mir, a whole new replacement for X and Wayland, which has been in development for 8 months, deserved a mention at the largest open source event in Europe?
Come on, man.
It is perfectly fine to say yes, Canonical is not so interested in the community. It s our way or the highway .
But do not pretend it s anything else or someone else is a bad guy.
In fact, is there any bad guy in this story at all!? I think there is not, it s just people with different visions and chosen paths to achieve them.
Maybe Mir and Unity are great ideas, much better than X and Wayland. But that s not what we are talking about. We are talking about community, and Canonical has been steadily destroying it for a long time already. If you cannot or do not want to see that, you ve got a huge problem going on.
git rebase --interactiveand rewrite it all into a single sensible set of commits. Also please do remember to develop on a branch, or if you did not
git pull --rebaseis your friend to avoid unnecessary merges.
$ wget http://git.netsurf-browser.org/netsurf.git/plain/Docs/env.sh
$ less env.sh
$ source env.sh
$ ns-apt-get-install
$ source env.sh
$ ns-clone
$ ns-make-libs install
This frontend supports the cocoa, the windowing system of MacOS X, on both PPC (version 10.5) and X86 (10.6 or later). The port is usefully functional and is integrated into the CI system, built natively on Mac mini systems as a jenkins slave. The port is written in objective C and currently has no active maintainer. $ source env.sh
$ ns-make -C $ TARGET_WORKSPACE /$ NS_BROWSER TARGET=gtk
$ source env.sh
$ cd $ TARGET_WORKSPACE /$ NS_BROWSER
$ ns-make
$ ./nsgtk
Many libraries build a GObject introspection repository (*.gir) these days which allows the library to be used from many scripting (Python, JavaScript, Perl, etc.) and other (e. g. Vala) languages without the need for manually writing bindings for each of those.
One issue that I hear surprisingly often is there is zero documentation for those bindings . Tools for building documentation out of a .gir have existed for a long time already, just far too many people seem to not know about them.
For example, to build Yelp XML documentation out of the libnotify bindings for Python:
$ g-ir-doc-tool --language=Python -o /tmp/notify-doc /usr/share/gir-1.0/Notify-0.7.girThen you can call
yelp /tmp/notify-doc to browse the documentation. You can of course also use the standard Mallard tools to convert them to HTML for sticking them on a website:
$ cd /tmp/notify-doc $ yelp-build html .Admittedly they are far from pretty, and there are still lots of refinements that should be done for the documentation itself (like adding language specific examples) and also for the generated result (prettification, dynamic search, and what not), but it s certainly far from nothign , and a good start. If you are interested in working on this, please show up in
#introspection or discuss it on bugzilla, desktop-devel-list@, or the library specific lists/bug trackers.
This is the first freeze in which I'm involved with upload rights. And it turned out to be a quite interesting ride so far, so I thought it would be nice to write about it.
When Francesca started her DPL game, I too started think about possible candidates. Here is my shortlist of dream candidates:
when francesca started her DPL game, I also started
thinking about people I'd like to encourage to stand as a DPL candidate.
unfortunately my initial "short list" contained 18 names, which doesn't fit
the game's rules very well.
after waiting a bit, 9 of them were mentioned by others already, so I can
leave them out here (which also means no public hug,
sorry, please complain to the inventor of the game!). from the remaining 9,
I've now chosen my Fantastic Four (in alphabtic order of first names):
in my opinion, the DPL task is mostly about managing, & those four
people are in my experience all very good at organising projects &
dealing with people, & are therefore well suited for this task.
let's see if they feel motivated to take on the challenge!
(the nomination period has already started,
so don't hestitate!)
This is my monthly summary of my free software related activities. If you re among the people who made a donation to support my work (78.31 , thanks everybody!), then you can learn how I spent your money. Otherwise it s just an interesting status update on my various projects.
Debian packaging
I wanted to update publican to the latest upstream release but I stopped after a few hours of work during which I filed two bugs that a modicum of testing should have caught before release. So I decided to wait for the next minor release.
I uploaded python-django 1.4.4 and 1.4.5, new upstream maintenance and security releases which thus went into wheezy. I also prepared a stable update of Django (1.2.3-3+squeeze5) which required me to backport the last 2 sets of security patches.
I uploaded a new revision of wordpress to fix a problem with TinyMCE (#700289) and to update/add many translation files (#697208).
Bug reporting and misc fixes
Live-build issue. I experienced some intermittent failures when building HDD live images with live-build on armel. Daniel Baumann directed me to the problematic piece of code (the oversizing of the image size was not enough) so I committed a small fix by increasing the oversizing factor to 6%.
Live-config issue. I also reported another issue that I diagnosed in live-config (#701788), namely that the script which setups sudo was failing when the default user is root.
git-buildpackage issue. I filed #700411 after noticing that git-import-orig imported the debian directory provided by upstream. Those directories are not used with 3.0 (quilt) source package and their presence in the upstream branch is thus harmful: any change to the upstream debian directory will result in conflicts when you merge a new upstream release in your packaging branch.
rubygems integration. Later I had to package a bunch of ruby applications that were using Bundler and I wanted to reuse as many packaged ruby modules that I could. But for this, those modules had to provide the required rubygems meta-information. I filed #700419 to request those on rake-compiler and with the help of C dric Boutillier (and others on #debian-ruby), we identified a bunch of ruby modules which could get those with a simple recompilation. I filed bin-nmu requests in #700605.
Misc bugs. simple-cdd offers to select profiles to install but I noticed that the associated debconf template was not translated (#700915). The startup scripts (provided by initscripts) in charge of activating the swap are supposed to handle a noswap kernel command line option to disable swap. In #701301, I reported that the option was not working correctly if quiet was present first in the command line due to spurious break statements.
Debian France
Administrative work. We were late for some legal procedures so I wrote the report of the last general assembly and sent it to the Tribunal d instance of Sarreguemines to record the changes in the administrative board. I also completed the special register of the association, it s a notebook that is legally required and that must document any important change in the governance structure of the association (new members of the board, headquarters change, new bylaws, etc.).
Galette developments. Debian France is funding a few enhancements to the Galette free software that we re using to manage the association. I am in touch with the Galette developer to answer his questions and ensure that his work will meet our needs.
Librement
I have been looking for talented developers who have a genuine interest in my Librement project. I want to fund the initial development of the project but I don t have the means to fund it entirely. So I really wanted to find developers who would find an interest beside the money that I would pay.
I got in touch with the team of developers from Scopyleft and they look like very good candidates. But they re heavy users of the Scrum development method and asked me to play the role of product owner . So I started to describe the project with user stories (i.e. create the backlog in the Scrum jargon), you can have a look at them here on trello.com. If you re interested by the topic of free software funding, feel free to review and to send me your comments.
My goal is clearly to have a minimal viable product with the first iteration(s) that I fund and then use the platform itself to fund further developments of the project.
Thanks
See you next month for a new summary of my activities.
5 comments Liked this article? Click here. My blog is Flattr-enabled.
LDAP supports syntax and comparator methods. The syntax specifies how the entry should look. Usually this is some form of text, but numbers or stuff like telephone numbers are supported as well. The comparators specifies how the values are compared. Most of the text comparators are defined to apply the handling of insignificant spaces. Insignificant space handling normalizes the use of spaces. First all leading and trailing spaces are removed. All the internal spaces are normalized to at most two spaces. At the end all strings starts and ends with one space to allow proper sub-string matches. The resulting strings are used for comparisons. This behavior makes sense most of the time. If the user want to find something in the directory, he usually don't cares about spaces, but about content. But I found one occurrence where this produces some grieve. Postfix supports LDAP since some time. And lets say, it does not care about spaces in its queries. This is no problem as e-mail addresses do not contain spaces. Or do they?
Yes, e-mail addresses can contain spaces. This is not widely known, but still allowed. This addresses are quoted and the command looks like RCPT TO:<" test"@example.com>. The local part is quoted and contains a space at the beginning. And this is where the problem starts. Postfix sanitizes the address. It uses a simplified internal representation of the address for all lookups. So the address gets test@example.com. This form is used in all table lookups. The LDAP table uses the internal form of the address. This address is copied verbatim into the query. This query may look this way (mail= test@example.com). It is sent to the server this way. The LDAP server applies the insignificant space modifications. The query is now interpreted and the comparator specified modifications are applied. The query gets effectively changed to (mail=test@example.com). And this is where the fun starts. Postfix accepts undeliverable mails. Depending on the setup, such LDAP queries may be used to check for valid addresses. Because of the space handling, the sender can add spaces to the beginning of the address and it will still be considered valid. In later steps this addresses are not longer valid. Addresses starting with spaces are considered invalid in some locations of Postfix. What surprised me a bit is that virtual alias handling did not map them. The unmodified addressed showed up on the LMTP backend server. That's why they showed up my radar. I would say Postfix is wrong in this case. The LDAP server applies the spec correctly and defines spaces in e-mail addresses as insignificant. Postfix on the other side considers them significant. The easiest fix would be to not allow any spaces in the LDAP table.
tmux helper by Joerg Jaspert <joerg@ganneff.de>
Call as: tm CMD [host]...
CMD is one of
ls List running sessions
s Open ssh session to host
ms Open multi ssh sessions to hosts, synchronizing input
$anything Either plain tmux session with name of $anything or
session according to TMDIR file
TMDIR file:
Each file in $TMDIR defines a tmux session.
Filename is the commandline option $anything
Content is defined as:
First line: Session name
Second line: extra tmux options
Any following line: A hostname to open a shell with in the normal
ssh syntax. (ie [user@]hostname)
Environment variables recognized by this script:
TMPDIR - Where tmux stores its session information
DEFAULT: If unset: /tmp
TMSORT - Should ms sort the hostnames, so it always opens the same
session, no matter in which order hostnames are presented
DEFAULT: true
TMOPTS - Extra options to give to the tmux call
Note that this ONLY affects the final tmux call to attach
to the session, not to the earlier ones creating it
DEFAULT: -2
TMDIR - Where are session information files stored
DEFAULT: $ HOME /.tmux.d
TMWIN - Where does your tmux starts numbering its windows?
This script tries to find the information in your config,
but as it only checks $HOME/.tmux.conf it might fail.
So if your window numbers start at anything different to 0,
like mine do at 1, then you can set TMWIN to 1
tm ls is shorter than tmux ls
More interestingly, tm s HOSTNAME opens a tmux session with the first
window being a ssh shell to HOSTNAME. Should you later type tm s
HOSTNAME again, it will attach to the existing session.
But the real kicker for me (and colleagues) actually is the ms
subcommand of it. ms being short for multi-session, it is my way of
no-longer using clusterssh. Basically you type tm ms HOST1 user@HOST2
and it opens a session with one tmux window consisting of two
panes. Showing you host1 and host2 at the same time. And the input
to both is synchronized, that is - all your input is send to both of
them. You aren t limited to just two hosts, do as many as you wish.
Actually, I have no idea if tmux has an upper limit, but I did already
have more than 100 hosts open at once. The major limitation there is
not tmux - but simply the available screenspace, as all hosts are shown
in ONE window! (The one advantage of clusterssh, it uses one xterm per host)
This is quite helpful in all kinds of administration work involving
clusters - imaging installing a package on 5 hosts of a cluster, you
usually want it on all of them - or any kind of situations where one
wants to run one command on many systems.
As I m already said, I m lazy. And so there is a way to easily define
multisessions that one uses regulary, by creating files inside the
directory behind $TMDIR, usually $ HOME /.tmux.d. They are simple
text files and let you easily define sessions you can then (re)open
with a simple tm whateveritsname.
And if you want the whole script by now: tm
Boot-Class-Path: oncrpc-1.0.7.jar gmetric4j-1.0.2.jar
-Xbootclasspath/a:/opt/ganglia/jmxetric/gmetric4j-1.0.3.jar
$ mkdir ~/opt
$ cd ~/opt
$ tar xzf ~/Downloads/jboss-as-7.1.0.Final.tar.gz
$ mkdir -p ~/opt/ganglia/jmxetric
$ cd ~/opt/ganglia/jmxetric
$ wget http://search.maven.org/remotecontent?filepath=info/ganglia/jmxetric/jmxetric/1.0.2/jmxetric-1.0.2.jar
$ wget http://search.maven.org/remotecontent?filepath=info/ganglia/gmetric4j/gmetric4j/1.0.2/gmetric4j-1.0.2.jar
$ wget http://search.maven.org/remotecontent?filepath=org/acplt/oncrpc/1.0.7/oncrpc-1.0.7.jar
$ mkdir -p ~/opt/ganglia/jmxetric/etc
$ cd ~/opt/ganglia/jmxetric/etc
$ wget https://raw.github.com/ganglia/jmxetric/master/etc/jmxetric.xml
$ cp jmxetric.xml jmxetric-jboss.xml
$ vi jmxetric-jboss.xml
<!-- report web server request count --> <mbean name="jboss.as:subsystem=web,connector=http" pname="http"> <attribute name="requestCount" type="int32"/> </mbean>Finally, tell JBoss about the agent:
$ cd ~/opt/jboss-as-7.1.0.Final
$ vi bin/standalone.conf
--- bin/standalone.conf
+++ ../jboss-as-7.1.0.Final.for-jmxetric/bin/standalone.conf
@@ -4,6 +4,7 @@
## ##
##############################################################################
+JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager"
#
# This file is optional; it may be removed if not needed.
#
@@ -48,6 +49,8 @@
#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
+ JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/main/jboss-logmanager-1.2.2.GA.jar -Xbootclasspath/p:$JBOSS_HOME/modules/org/jboss/logmanager/log4j/main/jboss-logmanager-log4j-1.0.0.GA.jar -Xbootclasspath/p:$JBOSS_HOME/modules/org/apache/log4j/main/log4j-1.2.16.jar"
+ JAVA_OPTS="$JAVA_OPTS -javaagent:$HOME/opt/ganglia/jmxetric/jmxetric-1.0.2.jar=host=jboss-host.example.org,port=8649,wireformat31x=true,config=$HOME/opt/ganglia/jmxetric/etc/jmxetric-jboss.xml"
JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
JAVA_OPTS="$JAVA_OPTS -Djboss.server.default.config=standalone.xml"
else
Note that we are adding some of the core JBoss logging code to the boot classpath - that is because JMXetric depends on the logger, and like many monitoring agents, it is impacted by JBoss bug AS-3681. Adding these extra classpath settings is the workaround.
Now go ahead and start JBoss, you should see a log message informing you that JMXetric is operational:
$ cd ~/opt/jboss-as-7.1.0.Final $ chmod a+x bin/*.sh $ bin/standalone.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: ... . . . ========================================================================= JMXetricAgent instrumented JVM, see https://github.com/ganglia/jmxetric 12:59:34,395 INFO [info.ganglia.gmetric4j.GMonitor] Setting up 1 samplers 12:59:34,536 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA 12:59:34,617 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA 12:59:34,653 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting . . .I hope this example is useful for you. Please feel free to share recipes you develop for collecting useful JVM metrics, and also any custom charts/reports through collaboration with the Ganglia community mailing list, the Ganglia wiki or your own blog.
Next.