Public bug reported:
Binary package hint: lm-sensors
Description:Ubuntu hardy (development branch)
Release:8.04
lm-sensors:
Installed: 1:3.0.0-4ubuntu1
Candidate: 1:3.0.0-4ubuntu1
My system uses an Intel Core2Duo Mobile T9300 CPU (Penryn). When I run
'sensors-detect', I get the
I have taken over the maintainer role from Harald Welte and made a first
release of dfu-util. Works fine on my 64bit machines here.
You can find it now here: http://dfu-util.gnumonks.org/ where it lives
inside a new git repo instead deeply inside the Openmoko SVN.
If you run into any packaging pr
It seems to me to Uwe maintains it in Ubuntu as well as in Debian. I
wrote him a mail already letting him know about the maintainership
change and the new release.
Lets hope he finds soem time to update the packge and sync it between
debian and ubuntu.
--
upgrade to latest version (0.1+svn5912)
I second that notion.
Please note that due to the packet cache, that has been tested
extensively with PowerDNS server, the recursor will now answer frequent
queries even faster thus resulting in even better performance in ISP
scenarios.
It's probably wise to use a packet-cache-ttl default of 10 o
Public bug reported:
The llvm package should create a llvm-lib symlink (linking /usr/bin
/llvm-link to /usr/lib/llvm-6.0/bin/llvm-lib, in my case), but it's
missing. This makes llvm-lib only reachable via the version suffix
(llvm-lib-6.0), in contrast to the other llvm-* binaries (llvm-ar etc.).
How is this a fix? "apt install llvm" still gives users the broken
version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846275
Title:
llvm package is missing llvm-lib symlink
To manage notificat
I explicitly wrote "gives users the broken version", not "gives me the broken
version". I don't use Ubuntu, and I don't need to use third-party packages.
There are people who do use Ubuntu, though, and it is for their sake that I'm
reporting this (especially since some of them are involved in the
Public bug reported:
Binary package hint: wammu
--- System information
Platform linux2
Python 2.6.5
wxPython 2.8.10.1
Wammu0.32.1
python-gammu 1.26.1
Gammu1.26.1
BluetoothNone
locales de_DE (UTF8)
connection at
device /d
I'm not too sure if it is the obligation of the receiving end of a zone
transfer to quote,
can you show us the results of a dig axfr for that zone?
Also please note that whitespaces are not allowed characters in dns
labels, so i wonder why you think that PowerDNS needs to be able to
handle those.
