You're absolutely right, I will allocate time this week to put together
a new upstream release.
Serge, would have have time to help me test and provide feedback?
Jon
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubu
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net
Hi Loic,
> Since some time, libvirt-bin fails upgrading at the time "start
libvirt-bin" is run during upgrades; I have start_libvirtd="no" in
/etc/default/libvirt-bin.
This is should be independent of the libvirt-cgconfig-wait job. That
doesn't actually explicitly start libvirt-bin. Are you on
The manpage talks about:
-T, --local-ttl=
When replying with information from /etc/hosts or the DHCP leases
file dnsmasq by default sets the time-to-live field to zero,
meaning that the requestor should not itself cache the
information. This is the correct thing to d
** Changed in: puppet (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/891071
Title:
puppet lucid backport doesn't support upstart
To manage
Public bug reported:
Network Manager now fires up a dedicate dnsmaq process for DNS
resolution.
This dnsmasq process does not notice changes to '/etc/hosts', requiring
one to jump through hops when this file is changed.
Ideally dnsmasq should purge itself when '/etc/hosts' is changed.
** Affect
** Changed in: puppet (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/793632
Title:
puppetmaster and puppet have clashing logrotate c
Actually last comment was wrong, testing confirms that sleep *gets*
killed when the stop condition is met.
I still don't know what happens with my libvirt-bin startup issue, but
at least the cgred-wait changes seem correct since the other -wait is
also using a different syntax.
--
You received t
/etc/init/libvirt-cgconfig-wait.conf will immediately exit if cgconfig
is already considered "running"; however if that's not the case, it will
go into a "sleep" case which wont be interrupted even when cgconfig
actually starts: AIUI, the stop statement only prevents startup, but
wont kill a runnin
Fixed upstream in puppet 0.25.5
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/532132
Title:
Unit test failure:
Fixed upstream in puppet 0.25.5
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/532203
Title:
Unit test failure:
Fixed upstream in puppet 0.25.5
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/532291
Title:
Unit test failure:
Aha, during my last upgrade libvirt-bin started after two minutes, which
seems to be exactly the TIMEOUT set in /etc/init/libvirt-cgconfig-
wait.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libcgroup in Ubuntu.
https://bugs.lau
Public bug reported:
Hi,
Since some time, libvirt-bin fails upgrading at the time "start libvirt-
bin" is run during upgrades; I have start_libvirtd="no" in /etc/default
/libvirt-bin.
Looking a bit into this, I tried understanding the structure of the
upstart jobs around cgred/cgconfig/*-wait et
Fixed upstream in puppet 0.25.5
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/532127
Title:
Unit test failure:
Fixed upstream in puppet 0.25.5
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/532126
Title:
Unit test failure:
Fixed upstream
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/564301
Title:
Spec tests failing
To manage notif
This was fixed upstream
** Changed in: puppet (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/532129
Title:
Unit test failure: test_sy
Precise now has 2.7.11
** Changed in: puppet (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/937941
Title:
Upstream have withdrawn
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vsftpd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vsftpd in Ubuntu.
https://bugs.launchpad.net/bugs/8044
This is still a valid issue. If the ftp group is present outside of
/etc/group (such as in LDAP), then the installation of vsftpd fails.
Simply saying "add the group ftp" is not a valid response - the group is
already present in the directory.
The problem is with the post-installation script assu
** Bug watch added: Debian Bug tracker #662243
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662243
** Also affects: samba via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662243
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a me
Thank you for reviewing my patch. I will report the bug and fix upstream
soon, and we'll see what happens :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/902339
Title:
samba(7) refe
The new version 2.7 pushed in bug #922600 lost the patch applied by this
bug, introducing the problem again.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/913464
Title:
rab
The new version lost the fix introduced in bug #913464. The rabbitmq
user appears in connected users and prevents desktop machine from
shutting down.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bug
The packages
libapache2-mod-php5 (PHP Version 5.3.2-1ubuntu4.14)
php5-xdebug (2.0.5-1ubuntu1)
delivered with Ubuntu 10.04 LTS don't work properly. Xdebug provides an
interface to IDEs like netbeans or eclipse. This interface is broken.
Normally it is possible to display the values of variables wi
One other thing: There is no /etc/resolvconf/resolv.conf.d/original,
just the "head" and "base" files, on my installation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/933723
Title:
I get the exact same behavior on the Kubuntu Precise desktop beta,
though bind9 is not installed. I end up with the resolv.conf posted by
the OP with 127.0.0.1 as the nameserver. I cannot override this even
with static DNS settings in Kubuntu's network configuration. When the
network starts, the
** Changed in: genshi (Ubuntu Precise)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to genshi in Ubuntu.
https://bugs.launchpad.net/bugs/935516
Title:
genshi version 0.6-2 FTBFS on i386 in precise
** Attachment added: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/946137/+attachment/2810268/+files/ThreadStacktrace.txt
** Tags added: apport-failed-retrace
** Tags removed: need-i386-retrace
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
30 matches
Mail list logo
