Public bug reported:
after upgrading a NATting firewall to 2.6.32-32-generic-pae, tcp
connections stall (thru timeout) after passing data each direction:
I see the threestep handshake, data going to the (http) server, an ack
with data coming back, which we ack, and then nothing (this per
2.87dsf-4ubuntu17.3 behaves as expected for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619246
Title:
invoke-rc.d don't return same anwswer when the variable RUNLEVEL is
setup at boot time
Public bug reported:
Binary package hint: debootstrap
since we seem to be releasing LTS updates to add support for new ubuntu
releases, it'd be good if we were to add oneiric support to the version
currently in lucid.
thanks,
lamont
** Affects: debootstrap (Ubuntu)
Importance: Undecided
And with the working compiler, this bug is finally put to rest. Thanks
Michael.
** Changed in: fpc (Ubuntu Oneiric)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Still fails to build as above in a current natty chroot (with underlying
lucid and maverick kernels), on bbg3, beaglexm, and panda.
lamont
** Changed in: fpc (Ubuntu Natty)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Mon, Mar 28, 2011 at 02:36:16PM -, Martin Pitt wrote:
If this issue is urgent, I recommend backporting the single fix for
this, as it's much safer and a lot quicker to test.
The single fix in this case consists of all the DNSSEC cleanup and
bugfixing since the lucid version. I'd be
On Mon, Mar 28, 2011 at 02:36:16PM -, Martin Pitt wrote:
If this issue is urgent, I recommend backporting the single fix for
this, as it's much safer and a lot quicker to test.
The single fix in this case consists of all the DNSSEC cleanup and
bugfixing since the lucid version. I'd be
In terms of supportability, I am FAR more comfortable supporting 9.7.3
than any attempt at backporting just the DNSSEC changes from 9.7.3 to
some previous 9.7 release. Upstream tends to be very good about only
putting fixes into fix-release version releases.
lamont
--
You received this bug
In terms of supportability, I am FAR more comfortable supporting 9.7.3
than any attempt at backporting just the DNSSEC changes from 9.7.3 to
some previous 9.7 release. Upstream tends to be very good about only
putting fixes into fix-release version releases.
lamont
--
You received this bug
Public bug reported:
Binary package hint: apt
In order to better publish the Ubuntu archive, we need lucid support in
apt-ftparchive for --arch=.
We are currently testing a patch, and will upload it once it is
confirmed to be sufficient for our needs. The change is minor and
isolated to
Works for me on lucid-userspace+maverick kernel, i386. Which is where I
first encountered the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598824
Title:
atd fails to start on new kernel
Public bug reported:
We have a couple of Intel Server System SR1600UR that would make very
nice ppa build machines for at least part of their time, except that we
need working xen in an LTS kernel, which means they run hardy. The
current hardy kernel lacks support for the ICH10 chipset used in
The proposed patch gets a hearty +1 from me.
Andy's kernel successfully discovered the disk on the machines in
question. Once we have this fix in a hardy kernel, we should be able to
use these machines as PPA builders much of the time.
--
You received this bug notification because you are a
Your response to
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/680657 is in
conflict with your assertion that users expect byobu to be installed
with screen, since they apparently don't even know it exists.
Fixed in 4.0.3-14ubuntu6
--
You received this bug notification because you are a
This was actually a bug in the mirroring setup, which has been resolved.
** Changed in: ubuntu-extras-keyring (Ubuntu)
Status: Triaged = Fix Released
** Changed in: ubuntu-extras-keyring (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
extras gpg key missing for natty
Public bug reported:
Binary package hint: screen
There is no reason on this planet for screen to Recommend: byobu.
Nothing in screen depends even slightly on byobu being present.
Looking at policy:
Recommends
This declares a strong, but not absolute, dependency.
The Recommends field
Fixed in launchpad-buildd rev 74, deployed today
** Changed in: launchpad-buildd
Status: Confirmed = Fix Released
--
Can't mount /dev/shm as tmpfs in the buildd
https://bugs.launchpad.net/bugs/671441
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This was actually an issue with the archive at old-releases.ubuntu.com,
which has been fixed.
** Changed in: apt (Ubuntu)
Status: Confirmed = Invalid
** Changed in: apt (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
Attempts to fetch non-existent file on old-releases
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu)
Status: Triaged = Fix Committed
--
bind9 1:9.7.2.dfsg.P2-1 FTBFS in natty
https://bugs.launchpad.net/bugs/674199
You received this bug notification because you are a member
actually, this is a slightly different bug than Debian 497959
** Bug watch added: Debian Bug tracker #497959
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497959
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497959
Importance: Unknown
Fixed in 1:9.7.2.dfsg.P2-2~build1 (and 1:9.7.2.dfsg.P2-2 in Debian/sid)
** Changed in: bind9 (Ubuntu)
Status: Fix Committed = Fix Released
--
bind9 1:9.7.2.dfsg.P2-1 FTBFS in natty
https://bugs.launchpad.net/bugs/674199
You received this bug notification because you are a member of
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu)
Status: Triaged = Fix Committed
--
bind9 1:9.7.2.dfsg.P2-1 FTBFS in natty
https://bugs.launchpad.net/bugs/674199
You received this bug notification because you are a member
actually, this is a slightly different bug than Debian 497959
** Bug watch added: Debian Bug tracker #497959
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497959
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497959
Importance: Unknown
Fixed in 1:9.7.2.dfsg.P2-2~build1 (and 1:9.7.2.dfsg.P2-2 in Debian/sid)
** Changed in: bind9 (Ubuntu)
Status: Fix Committed = Fix Released
--
bind9 1:9.7.2.dfsg.P2-1 FTBFS in natty
https://bugs.launchpad.net/bugs/674199
You received this bug notification because you are a member of
Successfully installed 2.5.1-0ubuntu0.10.04.1 on my lucid box, seems to
be working just fine (and not OOPSing that I can see.)
--
update AppArmor to 2.5.1 (for upstream and backported maverick kernels)
https://bugs.launchpad.net/bugs/660077
You received this bug notification because you are a
On 2010-09-15 Matthias Klose wrote:
On 15.09.2010 22:54, Matthias Klumpp wrote:
Strange... Why does it work for Debian, but not for Ubuntu?
it even does work on a babbage board running maverick
1. start with a bbg3 board running lucid and a 2.6.31-608-imx51 kernel.
2. bzr branch
crested:
processor : 1
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : AMD Opteron(tm) Processor 246
stepping: 8
cpu MHz : 1993.780
cache size : 1024 KB
fpu
Public bug reported:
If a group is defined in multiple places (such as /etc/group and libnss-db)
then getent fails. The operation of the system uses the union of the two
entries, getent returns the first.
% grep ^group /etc/nsswitch.conf
group: db compat
% getent group java-tck
Public bug reported:
Binary package hint: hdparm
After installing hdparm (ubuntu-server Depends: hdparm) onto my USB-
disk-as-root panda board, the machine fails to boot, getting timeouts
and read errors trying to access the USB drive. Removing hdparm makes
it all happy again.
** Affects:
just to clarify: ubuntu-standard Depends: hdparm... ubuntu-server isn't
a metapackage.
--
after installing hdparm, panda board fails to boot
https://bugs.launchpad.net/bugs/652873
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: lshw
On a panda board, any invocation of lshw dies with SIGBUS. dmesg has:
[40613.328338] Unhandled fault: external abort on non-linefetch (0x018) at
0x40155000
And strace lshw shows:
...
open(/dev/mem, O_RDONLY) = 3
Public bug reported:
Binary package hint: evince
If the document in question is read-only by way of having a password for
modify and no password for read (as are common on the net these days)
cannot be opened in evince, while windows has no issues reading them.
I'm guessing that the issue is
Public bug reported:
Binary package hint: network-manager
Since upgrading to maverick, network-manager adds a line at the top of
/etc/hosts when a connection comes up, and that line lacks anything
other than the first component of the FQDN, which breaks hostname -f.
How can I get
Public bug reported:
The linux package, as of lucid, has a disk footprint at build time in
excess of 23GB on amd64, and maverick crosses the 25GB threshold.
As a result, nearly all of the PPAs fail to build the package, because
they run out of disk space. The second largest package (to my
running 9.2 from lucid-proposed on an otherwise lucid (amd64) machine and the
test case in the initial report, the resulting Sources file shows:
==
...
4c8153d70c670b7a105108cb35ca325f 72366 appconfig_1.56-2.diff.gz
Checksums-Sha1: 89r94ÅÇ^?
9.3 works much better. +1 here in all my testing.
--
apt-ftparchive generates corrupt Sources stanzas for .dsc files without
Checksums-* fields
https://bugs.launchpad.net/bugs/633967
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Still fails (in a maverick chroot on a lucid bbg3 board).
http://paste.ubuntu.com/490040/ has the tail end of the error message.
lamont
--
Bootstrapping needed for fpc for armel
https://bugs.launchpad.net/bugs/67544
You received this bug notification because you are a member of Ubuntu
Bugs,
that is, a maverick chroot with the debs from deb
http://people.canonical.com/~doko/tmp/fpc-armel ./ used to satisfy
build-dependencies, in an interactive dpkg-buildpackage -B run.
--
Bootstrapping needed for fpc for armel
https://bugs.launchpad.net/bugs/67544
You received this bug notification
This appears to have been introduced somewhere after 1:1.2-1 and in or
before 1:1.3-1.1, since the karmic binary works just fine.
--
radvd terminates with segfault on startup
https://bugs.launchpad.net/bugs/567131
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
% sudo apt-get dist-upgrade -- installing bzr 2.2.0-1
...
% bzr commit
bzr: ERROR: Unable to determine your name.
Please, set your name with the 'whoami' command.
E.g. bzr whoami Your Name
of -2,
differing only in the changelog.
Changelog entries since current maverick version
1:9.7.1.dfsg.P2-2~build1:
bind9 (1:9.7.1.dfsg.P2-2) unstable; urgency=low
* Correct conflicts for bind9-host
-- LaMont Jones lam...@debian.org Fri, 16 Jul 2010 05:24:38 -0600
-BEGIN PGP SIGNATURE
of -2,
differing only in the changelog.
Changelog entries since current maverick version
1:9.7.1.dfsg.P2-2~build1:
bind9 (1:9.7.1.dfsg.P2-2) unstable; urgency=low
* Correct conflicts for bind9-host
-- LaMont Jones lam...@debian.org Fri, 16 Jul 2010 05:24:38 -0600
-BEGIN PGP SIGNATURE
)
Assignee: (unassigned) = LaMont Jones (lamont)
--
apparmor blocks journal creation for dnssec
https://bugs.launchpad.net/bugs/600106
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu
The stats file is written to /var/cache/bind/named.stats not to
/var/run/named... Not sure why you have it going to /var/run/named, but
that is the issue here, not the apparmor profile.
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu
)
Assignee: (unassigned) = LaMont Jones (lamont)
--
apparmor blocks journal creation for dnssec
https://bugs.launchpad.net/bugs/600106
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The stats file is written to /var/cache/bind/named.stats not to
/var/run/named... Not sure why you have it going to /var/run/named, but
that is the issue here, not the apparmor profile.
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu
:
bind9 (1:9.7.1.dfsg-2) unstable; urgency=low
[Regid Ichira]
* explicitly add nsupdate to dynamic updates in README.Debian.
Closes: #577398
[LaMont Jones]
* Cleanup bind9-host description. Closes: #579421
* switch to 3.0 (quilt) source format, but not to quilt. Closes: #578210
:
bind9 (1:9.7.1.dfsg-2) unstable; urgency=low
[Regid Ichira]
* explicitly add nsupdate to dynamic updates in README.Debian.
Closes: #577398
[LaMont Jones]
* Cleanup bind9-host description. Closes: #579421
* switch to 3.0 (quilt) source format, but not to quilt. Closes: #578210
Fixed in 1:9.7.1.dfsg-1
** Changed in: bind9 (Ubuntu)
Milestone: None = maverick-alpha-2
** Changed in: bind9 (Ubuntu)
Status: New = Fix Released
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
db.root needs update for i.root-servers.net
Fixed in 1:9.7.1.dfsg-1
** Changed in: bind9 (Ubuntu)
Milestone: None = maverick-alpha-2
** Changed in: bind9 (Ubuntu)
Status: New = Fix Released
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
db.root needs update for i.root-servers.net
Public bug reported:
The last bit of the build log before the sparc box (running hardy) falls
over is as below. after that, the machine is pingable, but that's all
she wrote.
===
make[3]: Entering directory
2.6.24-28-sparc64 kernel.
--
pygobject hates sparc, kills it
https://bugs.launchpad.net/bugs/591990
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: python2.6
We probably shouldn't see some of this output:
Setting up python2.6-minimal (2.6.5-1ubuntu6) ...
Linking and byte-compiling packages for runtime python2.6...
INFO: using unknown version '/usr/bin/python2.6' (debian_defaults not
up-to-date?)
Public bug reported:
Binary package hint: update-manager
Classful networking died in 1993 (see RFC1519), and very much should not
be assumed any more. pommerac (the machine below) is in a /24 network
block, and should under no circumstances be querying 10.255.255.255.
May 23 22:46:40 ...
(yes, it's very old hardware)
+printers 301 : grep '^MemTotal:[[:space:]]*' /proc/meminfo
MemTotal: 186140 kB
+printers 302 : cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 3
model name : Pentium II (Klamath)
stepping
I'm inclined to have hook give the option about named.conf, but report
the other information unconditionally. I'll add this during maverick.
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu)
Status: Triaged = In Progress
I'm inclined to have hook give the option about named.conf, but report
the other information unconditionally. I'll add this during maverick.
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
** Changed in: bind9 (Ubuntu)
Status: Triaged = In Progress
Public bug reported:
Binary package hint: openoffice.org
lzma on armel causes dpkg-deb for -core to take somewhere between 8.5
and 9.5 hours before to get to pkgstriptranslations (and output) which
times out the build. The build also takes 50 hours.
because oo.o is not on any release images
** Also affects: update-notifier
Importance: Undecided
Status: New
** Project changed: update-notifier = update-manager
** Changed in: update-manager
Status: New = Invalid
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Public bug reported:
Binary package hint: update-notifier
Because the files in update-motd.d are not listed as conffiles, removing
them just means that they get restored on the next upgrade of the
package.
This is WRONG. When I remove a symlink in /etc/update-motd.d, I want it
to STAY GONE.
I must concur that the old-n-busted dead code should be dead and gone,
rather than having every bug against it answered with use the PPA
version. That way does not lie happiness.
--
Update Terminator to 0.92
https://bugs.launchpad.net/bugs/557671
You received this bug notification because you
in my testing of 0.92ppa1 (installed from the ppa), it seems to be
working well for me.
** Package changed: ubuntu = terminator (Ubuntu)
--
Update Terminator to 0.92
https://bugs.launchpad.net/bugs/557671
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
During the test suite, the build of glib2.0 crashes sparc. The
specifics of the failure are that the machine is pingable, but does not
respond to anything on the network, nor to the console.
The current build log is from me killing the build before it killed the
buildd. If
Public bug reported:
During an initial test rebuild (parallel=4) of eglibc on a (single CPU)
armel v7 box:
Encountered progressions that don't match expected failures:
test-fpucw.out, Error 132
tst-cpuclock2.out, Error 1
tst-eintr1.out, Error 1
tst-timer.out, Error 139
make: ***
Public bug reported:
Binary package hint: squid
Not to be confused with bug 523621, we are outside in the real root in
this case, regression introduced in -1ubuntu9
-
The following NEW packages will be installed:
squid
0 upgraded, 1
It may be using upstart, but it's not starting. reproduced with
squid_2.7.STABLE7-1ubuntu9 on amd64:
-
The following NEW packages will be installed:
squid
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get
retitled the bug to include that it was in a chroot, filing a new bug
for it not starting outside of a chroot.
--
squid_2.7.STABLE7-1ubuntu5 fails to install with Unknown job: squid error in
a chroot
https://bugs.launchpad.net/bugs/523621
You received this bug notification because you are a
retitled the bug to include that it was in a chroot, filing a new bug
for it not starting outside of a chroot.
** Changed in: squid (Ubuntu)
Status: Confirmed = Won't Fix
--
squid_2.7.STABLE7-1ubuntu5 fails to install with Unknown job: squid error in
a chroot
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
--
Have a LTSP chroot built and placed on the Edubuntu DVD
https://bugs.launchpad.net/bugs/531546
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: squid
Not to be confused with bug 523621, we are outside in the real root in
this case, regression introduced in -1ubuntu9
-
The following NEW packages will be installed:
squid
0 upgraded, 1
retitled the bug to include that it was in a chroot, filing a new bug
for it not starting outside of a chroot.
** Changed in: squid (Ubuntu)
Status: Confirmed = Won't Fix
--
squid_2.7.STABLE7-1ubuntu5 fails to install with Unknown job: squid error in
a chroot
It may be using upstart, but it's not starting. reproduced with
squid_2.7.STABLE7-1ubuntu9 on amd64:
-
The following NEW packages will be installed:
squid
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get
retitled the bug to include that it was in a chroot, filing a new bug
for it not starting outside of a chroot.
--
squid_2.7.STABLE7-1ubuntu5 fails to install with Unknown job: squid error in
a chroot
https://bugs.launchpad.net/bugs/523621
You received this bug notification because you are a
Public bug reported:
Binary package hint: parted
Maybe I'm just totally blind, but I could not find any way to get the
installer to let me mount an existing filesystem as, say, /home, without
it formatting it. Fortunately, it was mostly backed up. If the option
does still exist, it needs to be
Public bug reported:
Binary package hint: parted
Attempting to install on an alternate root LV on the encrypted disk,
there is no way I could find to get the partitioner to open the existing
luks volume and vgscan/activate it.
Manually doing the luksOpen, vgscan, vgchange -a y results in an
Public bug reported:
Binary package hint: apparmor
during an upgrade to lucid (from karmic) apparmor_parser was freerunning
(100% CPU usage) and unkillable, while processing ntpd's profile. I do
still have the broken root tree available, please pester me if I haven't
already attached the
Public bug reported:
Binary package hint: nautilus
After upgrading to lucid, removable media does not automatically mount
Mar 22 20:39:33 mix kernel: [190139.165522] sd 20:0:0:0: [sdh] 256000 2048-byte
logical blocks: (524 MB/500 MiB)
Mar 22 20:39:33 mix kernel: [190139.166286] sd 20:0:0:0:
Public bug reported:
Binary package hint: update-manager
Upgrading a low-end box from hardy with 2.6.24-17-server to lucid, do-
release-upgrade chose linux-generic-pae as the kernel of choice.
The box in question is a PII/233 with 192MB of RAM (and 6GB of hard
drive). Once I fired that kernel
Public bug reported:
when I have wodim burn a disk (like say, the desktop CD), it finishes the burn,
then says it's ejecting it.
This provably works, since the tray opens and I remove the disk and label it...
wodim continues to claim to be trying to eject the disk. And in fact, closing
the
Public bug reported:
Binary package hint: virt-manager
If an IP other than 0.0.0.0 or 127.0.0.1 is used in the vm definition,
then virt-manager cannot connect to the display, because it assumes that
127.0.0.1 will work, rather than looking at the config. Note that it
happily shows the IP
Public bug reported:
Binary package hint: update-manager
On a server running hardy, I had Prompt=normal in /etc/update-manager
/release-upgrades.
No desktop, no automated update-manager running to prompt me to roll forward,
so I never have.
Now, it so happens that this server is able to
bind9 1:9.7.0.dfsg.P1-1 is current in sid, and addresses a DoS issue
with servers pointed at a stale anchor. This should get pulled into the
release.
** Summary changed:
- Please sync bind 9.7.0.dfsg-1 from debian
+ Please sync bind 9.7.0.dfsg.P1-1 from debian
--
Please sync bind
bind9 1:9.7.0.dfsg.P1-1 is current in sid, and addresses a DoS issue
with servers pointed at a stale anchor. This should get pulled into the
release.
** Summary changed:
- Please sync bind 9.7.0.dfsg-1 from debian
+ Please sync bind 9.7.0.dfsg.P1-1 from debian
--
Please sync bind
Public bug reported:
Binary package hint: livecd-rootfs
Right now, and for quite some time, there are a couple of places where
livecd.sh wgets files from people.ubuntu.com as part of the build.
These wget calls fail, and shouldn't be there in the first place.
lamont
** Affects: livecd-rootfs
Public bug reported:
Binary package hint: livecd-rootfs
as of 1.107, livecd-rootfs Depends: ltsp-server, which pulls in lots of
daemons. Once they have the package split, Depend: on the non-daemon-
dependent package.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Public bug reported:
livecd-rootfs needs to use ltsp-build-client and ltsp-update-image, but
really should not have all those daemons that ltsp-server Depends on.
Please split out a package with just ltsp-buildd-client, ltsp-update-
image, and any other such useful script into their own package,
the package also assumes that you are using /etc/bind, /var/cache/bind,
/var/run/named, and /etc/bind/rndc.key
How many things should we allow you to change before we can no longer
manage the package with the maintainer's idea of where things live??
What's the precise use case that leads you to
Fixed in bind9 1.7.0.dfsg-2~build1
** Changed in: bind9 (Ubuntu)
Status: Triaged = Fix Released
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
bind9 will not install on a clean system
https://bugs.launchpad.net/bugs/531854
You received this bug
** Changed in: bind9 (Ubuntu)
Status: Confirmed = Fix Committed
--
bind-dlz and ldap api: invalid use of % character
https://bugs.launchpad.net/bugs/227344
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
the package also assumes that you are using /etc/bind, /var/cache/bind,
/var/run/named, and /etc/bind/rndc.key
How many things should we allow you to change before we can no longer
manage the package with the maintainer's idea of where things live??
What's the precise use case that leads you to
Fixed in bind9 1.7.0.dfsg-2~build1
** Changed in: bind9 (Ubuntu)
Status: Triaged = Fix Released
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
bind9 will not install on a clean system
https://bugs.launchpad.net/bugs/531854
You received this bug
** Changed in: bind9 (Ubuntu)
Status: Confirmed = Fix Committed
--
bind-dlz and ldap api: invalid use of % character
https://bugs.launchpad.net/bugs/227344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: grub-installer
When I install lucid on a serial console, grub-installer fails to setup
the kernel options correctly.
On the machine in question, console=ttyS1,38400 - this is not what grub-
installer sets up.
After manually fixing default/grub and
Public bug reported:
Binary package hint: puppet
After installing and starting puppet, I removed the package. The state
of the machine after that illustrates two packaging bugs:
1. puppetd is still running, despite the binary (and package) having been
removed from the system.
2. the puppet
Public bug reported:
Binary package hint: puppet
After installing and starting puppet, I removed the package. The state
of the machine after that illustrates two packaging bugs:
1. puppetd is still running, despite the binary (and package) having been
removed from the system.
2. the puppet
we'll need to know what is in local. before we have a chance of
figuring this out.
** Changed in: bind9 (Ubuntu)
Status: New = Incomplete
--
host crashed with signal 7 in dst_lib_init()
https://bugs.launchpad.net/bugs/475183
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: bind9
BIND 9.7 released shortly before functional freeze, and I was diverted
by some archive issues that caused me to miss FF cutoff.
9.7 provides some vastly improved support for DNSSEC for the users, and
the history of BIND, combined with Lucid being
** Changed in: bind9 (Ubuntu)
Status: New = Fix Committed
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
Please sync bind 9.7.0.dfsg-1 from debian
https://bugs.launchpad.net/bugs/530107
You received this bug notification because you are a member
** Changed in: bind9 (Ubuntu)
Importance: Undecided = High
--
Please sync bind 9.7.0.dfsg-1 from debian
https://bugs.launchpad.net/bugs/530107
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) = LaMont Jones (lamont)
--
resolvconf update script should not produce error when main.cfg missing
https://bugs.launchpad.net/bugs/530323
You received this bug notification because you are a member of Ubuntu
Server Team, which
601 - 700 of 1183 matches
Mail list logo
