The emacs mode is installed on my system as well, it just doesn't
autoload.
That is /usr/share/emacs23/site-lisp/puppet-el/puppet-mode.elc is there,
and if I load it manually ( M-x load-library -- puppet-mode) it works
perfectly but it doesn't load automatically when I open a .pp file.
Two ways
The emacs mode is installed on my system as well, it just doesn't
autoload.
That is /usr/share/emacs23/site-lisp/puppet-el/puppet-mode.elc is there,
and if I load it manually ( M-x load-library -- puppet-mode) it works
perfectly but it doesn't load automatically when I open a .pp file.
Two ways
Public bug reported:
Binary package hint: puppet
On a clean lucid install puppet-mode is no longer auto loaded in to
emacs.
In karmic the puppet package provided the file:
/etc/emacs/site-start.d/50puppet-mode-init.el
This file is no longer provided by any package.
After manually copying the
Public bug reported:
Binary package hint: puppet
On a clean lucid install puppet-mode is no longer auto loaded in to
emacs.
In karmic the puppet package provided the file:
/etc/emacs/site-start.d/50puppet-mode-init.el
This file is no longer provided by any package.
After manually copying the
@janvl
No this is not a ubuntu specific bug, it stems from the upstream kernel.
Somewhere at the top of this page there is a link to the relevant kernel bug (
http://bugzilla.kernel.org/show_bug.cgi?id=13411 ).
If I read that bug thread correctly someone is working on making that
blacklisting
@Hadmut Danisch
AFAIK it's not erroneous, the compagny (Tenx Technology) has chosen to give all
there products the same ID (that's the idProduct line from the output of lsusb
-v) and since usbhid uses idProduct and idVendor to identify devices it has
been blacklisted.
I doubt that that will
If it's fixed upstream, is there any chance that it will make it back to the
Hardy package (backports) ?
-- Jon
--
puppet client always exits on startup
https://bugs.launchpad.net/bugs/176113
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
My point excatly, I also work at a university, and we have also
specifically chosen a LTS version :)
Hope it's not the Dapper story all over again, once again! Once the distro
ships some developers and maintainer stop caring about it, and only work on the
next dist. This is perhaps acceptable
This looks a lot like bug #227189
It seems it's fixed in 4.2.0.dfsg-12, but that version is for Ubuntu 8.10
Intrepid only.
For some reason the fix has not made it back to Hardy (why?)
-- Jon
--
installation does not take into account server : always think it is 127.0.0.1
We do unattended installations, and sets most variables like this by preseeding
the debconf database from a script.
Like this:
echo hobbit-client hobbit-client/HOBBITSERVERS string
130.xxx.xxx.xxx| debconf-set-selections
Like in the manual installation this dos not make it into
It is definitly _not_ fixed under dapper (use that distro at work, and
we have that problem)
At home I use edgy and I have the same problem.
I have just downloaded and unpacked the actual aspell-da - .deb file.
Support for dictionaries-common is not included in the deb file.
A short google
11 matches
Mail list logo
