I should mention that this package is a dependency for the Apache::ConfigParser
module which I will upload into Ubuntu after libfile-fnmatch-perl is uploaded.
The package is now in REVU:
http://revu.tauware.de/details.py?package=libfile-fnmatch-perl
--
[needs-packaging] File::FnMatch
https://bu
Public bug reported:
Package request for the Perl File::FnMatch package.
File::FnMatch provides Perl bindings to the system's fnmatch(3) call.
URL: http://search.cpan.org/dist/File-FnMatch/
License: Same as Perl's
** Affects: ubuntu
Importance: Undecided
Assignee: BlairZa
I installed Hardy i386 using the alternative ISO into Parallels and that
worked.
I was able to get the Ubunutu server install to boot by going into a shell
(alt-F2)
at the end of the install and 'chroot /target bash' and apt-get
linux-image-generic
and removing the server kernel.
--
VirtualBox
I got the exact same error using the Hardy RC server build inside
Parallels 3.0 build 5584.
The install proceeded fine then upon the first reboot, it failed.
--
VirtualBox - Can't install hardy server as guest - inappropriate kernel error
https://bugs.launchpad.net/bugs/216784
You received this
Public bug reported:
Binary package hint: python2.5
I did an apt-get dist-upgrade on edgy today and saw the new
Python 2.5 go in.
If you run the python2.5-config, then it fails unless python2.5-dev
is installed:
$ /usr/bin/python2.5-config --prefix
Traceback (most recent call last):
File "/us
Works for me fine on dapper with debianutils 2.15.2.
I still get the failure on breezy with debianutils 2.14.1-ubuntu2.
Blair
--
run-parts regex failure with --lsbsysinit
https://launchpad.net/bugs/24003
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
Public bug reported:
Going through a server-expert install using Knot3's CD on an i386
box, when I get to the launguage environment page, the menu
flows past the bottom of the screen and you can't see the OK,
Cancel or Back buttons, nor even if they exist there :)
Easy to reproduce:
Boot off the
kurti wrote:
> apache2's initscript has code to handle this:
>
> # /var/run and /var/lock could be on a tmpfs
> [ ! -d /var/run/apache2 ] && mkdir /var/run/apache2
> [ ! -d /var/lock/apache2 ] && mkdir /var/lock/apache2
> # Make sure
Public bug reported:
Binary package hint: smokeping
With the /var/run now being a tmpfs, after a reboot, smokeping cannot
find the /var/run/smokeping directory, which is an error reported when
you go to view the web pages:
Software error:
ERROR: /etc/smokeping/config, line 15: Directory '/var/r
