I won't forget to do it with the 7.3 upload, and would rather have the
bug open until it's actually fixed.
** Changed in: openssh (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Sorry, I mean OpenSSH in general of course, not just the client.
And yes, the other end ought to be able to cope with stronger primes.
But that's not what this bug is about: it specifically says "The alleged
problem is the reference to /etc/ssh/primes instead of /etc/ssh/moduli".
--
You
Sigh. No. It's a perfectly obvious bug in the OpenSSH client, it's
just mostly cosmetic (i.e. it's checking two files but then only warning
about one). Please read the original bug description carefully before
closing this or arguing further about whether it's valid.
** Changed in: openssh
I intend to as soon as that's possible, yes (slowed down by the Debian
archive publisher being broken at the moment).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1558576
Title:
Public bug reported:
Running xenial, after upgrading to lxc 2.0.0~rc11-0ubuntu1, I can't
start containers any more:
$ sudo lxc-start -F -n precise-lptest-base
ln: failed to create symbolic link
'/usr/lib/x86_64-linux-gnu/lxc/sys/fs/cgroup/cpu/cpu,cpuacct': Read-only file
system
** Bug watch added: Debian Bug tracker #817870
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817870
** Also affects: openssh (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817870
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Yep, that's my take on it too. Synced, thanks!
** Changed in: openssh (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member of Ubuntu
Serve
Public bug reported:
I'd like to upgrade OpenSSH to 7.2p1 in xenial, on the general principle
that keeping OpenSSH as up to date as possible is a good plan. There
are a few more changes to default crypto algorithms and some new
features, but they're relatively minor compared to 7.0/7.1.
IRC speculation is that this might be due to
https://launchpad.net/ubuntu/+source/init-system-helpers/1.29ubuntu1,
although that isn't enough to determine whether it's a regression in
i-s-h or something that openssh is doing wrong that was just exposed by
that upload.
--
You received this bug
We don't modify this in Debian/Ubuntu. The default was changed to
"UseDNS no" in OpenSSH 6.8p1, which is in Ubuntu 15.10 and later.
** Changed in: openssh (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Please can you provide as much information as you have? For example,
"the ctl status is failed 255" is clearly a paraphrase of something that
you're seeing; it would be more useful if you could please copy and
paste the original text of the error messages.
Forum research is probably leading you
We're now building armhf/arm64 packages on real arm64 hardware in
Launchpad, so, while this problem may well still exist in qemu, it no
longer applies to Launchpad builds.
** Changed in: launchpad-buildd
Status: Triaged => Won't Fix
--
You received this bug notification because you are a
Specifically, the local configuration problem here is in the LSB header
of /etc/init.d/smfpd. This file isn't shipped by Ubuntu, so you will
have to work out how to correct it locally or refer to whoever maintains
the package containing it.
It's unfortunate that this takes out unrelated
The key_load_public bits are a red herring; it loads id_rsa(.pub)
successfully (you can tell because it says "type 1", not "type -1"), and
the immediately-subsequent error pertains to id_rsa-cert(.pub) instead.
So it's successfully loaded the available identity file.
I think the next steps here
** Changed in: samba (Ubuntu)
Status: Fix Released => Confirmed
--
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/1315565
Title:
nss-winbind is returing -1 for supplemental
Public bug reported:
Preconfiguring packages ...
Selecting previously unselected package bacula-common.
(Reading database ... 1208575 files and directories currently installed.)
Unpacking bacula-common (from .../bacula-common_5.2.5-0ubuntu6.2_amd64.deb) ...
Adding user 'bacula'... Ok.
Selecting
All moved to main. I moved the python3-heatclient binary as well, since
python-senlinclient build-depends on it.
** Changed in: python-keystoneauth1 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: python-openstacksdk (Ubuntu)
Status: Fix Committed => Fix Released
**
Moved to main.
** Changed in: dnspython3 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnspython3 in Ubuntu.
https://bugs.launchpad.net/bugs/1518800
Title:
[MIR] dnspython3
** Changed in: openssh (Ubuntu)
Status: New => Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
OK, thanks. I've just pushed a patch to fix up the "Subsystem sftp"
line in the example sshd_config file, too.
** Changed in: openssh (Ubuntu)
Status: Incomplete => Fix Committed
** Summary changed:
- Default sshd_config file has bad path to sftp-server. Should be
This is peculiar, because I don't believe we've ever written it out with
the upstream libexec path. Yes, the examples file shows it as libexec,
but we've written out "Subsystem sftp /usr/lib/openssh/sftp-server" for
new installations since 2005.
Is it possible that you had hand-edited your
** Changed in: openssh (Ubuntu)
Status: New => Fix Committed
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You received this bug notification because you are a member
I'll drop this patch in the next xenial upload.
** Changed in: openssh (Ubuntu)
Importance: Undecided => High
** Changed in: openssh (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
You
Public bug reported:
After upgrading to lxc 1.1.5-0ubuntu1, lxc-start fails like this:
lxc-start: start.c: preserve_ns: 149 Permission denied - failed to open
'/proc/7170/ns/mnt'
lxc-start: start.c: lxc_spawn: 993 failed to store namespace references
lxc-start: start.c: __lxc_start: 1192 failed
** Attachment added: "config"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1516037/+attachment/4518324/+files/config
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516037
** Attachment added: "fstab"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1516037/+attachment/4518325/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516037
Title:
But I should also note that the same thing happened with a freshly-
created container, using "sudo lxc-create -n trusty-test -t ubuntu -- -r
trusty". So I don't think my custom apparmor hack there can be at
fault.
--
You received this bug notification because you are a member of Ubuntu
Server
My host is xenial amd64; the guest is i386 because a million lines of
Python is rather more memory-efficient that way. :-)
Yes, lxc and liblxc1 are at the same version.
Kernel is linux-image-4.2.0-17-generic 4.2.0-17.21, though this also
happened with 4.2.0-16.19 (I rebooted to see if that
** Attachment added: "strace"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1516037/+attachment/4518284/+files/lxc-start.trace
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Public bug reported:
Last night I began the process of upgrading my laptop from vivid to
wily. I edited /etc/apt/sources.list and replaced vivid with wily, ran
"apt-get update", and then went off to do some other things while it
chewed on the network. Unfortunately one of those other things
Backporting algorithm tightening may make sense, but I don't want to end
up in a situation where users are trying to deal with interoperability
issues but none of the upstream docs make sense. If we're advocating
specific changes that upstream aren't currently already considering, we
should take
Not yet. I'm actively working on the relevant bits of Launchpad
infrastructure, and will upgrade to OpenSSH 7.1p1 after that. I *don't*
intend to vary algorithm choices from upstream configuration, but 7.1 is
already a fair bit better.
--
You received this bug notification because you are a
I don't recall that patch ever being in Debian OpenSSH packages, so it
would be helpful to track it down and link to it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1501966
Title:
On Mon, Sep 28, 2015 at 07:51:47AM -, Tim Penhey wrote:
> We do test a number of upgrade combinations, and I'm curious as to why
> you say it is impossible to upgrade? What exactly is the situation you
> are attempting?
It's just about version numbers, as Seth says. The constraint that
I've tested 1.0.6-2ubuntu0.14.04.4 for several hours and the problem is
fixed, I can't reproduce this at all.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP
Tested with vivid 1.0.6-3ubuntu1.1, bug is fixed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP ProLiant m400 Server crashes with unhandled level 3 translation
Andrew, I'm still testing it for vivid, will be done in a few hours.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
HP ProLiant m400 Server crashes with unhandled
Tested with wily 1.0.6-3ubuntu3, bug fixed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
https://bugs.launchpad.net/bugs/1469214
Title:
** Changed in: fuel
Assignee: Registry Administrators (registry) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1316812
Title:
ubuntu qemu-kvm package
Hi there,
I need access to the machine to test this, any hints on the machine
name and how to access it would be useful. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to irqbalance in Ubuntu.
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: openssh (Ubuntu)
Status: Triaged => In Progress
** Changed in: openssh (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification be
Moved to main.
** Changed in: python-mistralclient (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-mistralclient in Ubuntu.
https://bugs.launchpad.net/bugs/1487118
Title:
** Changed in: python-automaton (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-automaton in Ubuntu.
https://bugs.launchpad.net/bugs/1487196
Title:
[MIR] python-automaton
Moved to main.
** Changed in: python-pymysql (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pymysql in Ubuntu.
https://bugs.launchpad.net/bugs/1477668
Title:
[MIR]
Both moved to main, along with the python3-dogpile.cache binary.
** Changed in: python-oslo.cache (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-oslo.reports (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a
Moved to main.
** Changed in: bandit (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bandit in Ubuntu.
https://bugs.launchpad.net/bugs/1486568
Title:
[MIR] bandit
To manage
It makes a difference for me, but CanonicalizeHostname has to be in the
right part of the file (not inside an inapplicable Host block; note that
indentation doesn't actually matter). Perhaps I could see your whole
.ssh/config?
--
You received this bug notification because you are a member of
Moved to main.
** Changed in: python-fasteners (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-fasteners in Ubuntu.
https://bugs.launchpad.net/bugs/1481247
Title:
[MIR]
I think this was deliberate upstream, probably this:
- ssh(1): Tweak config re-parsing with host canonicalisation - make the
second pass through the config files always run when host name
canonicalisation is enabled (and not whenever the host name changes)
In fact this was not
This is done in OpenSSH 7.0, but I plan to hold off on that for at least
a while to see if we can get Twisted Conch beaten into shape to support
SHA-2; the idea of spending months supporting people having to cope with
configuration changes from the default Ubuntu installation in order to
access
This patch is unnecessary with OpenSSH 6.5p1 and newer, because
kbdint_alloc now uses xcalloc rather than xmalloc and thus zeroes the
entire structure. The regression fix was thus only needed for precise
and not for later releases; I'll drop it from wily shortly when
resyncing with unstable, in
All moved to main.
** Changed in: python-funcsigs (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-linecache2 (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-traceback2 (Ubuntu)
Status: Fix Committed = Fix Released
--
You received
Both moved to main.
** Changed in: python-cachetools (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-futurist (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Moved to main.
** Changed in: contextlib2 (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to contextlib2 in Ubuntu.
https://bugs.launchpad.net/bugs/1473485
Title:
[MIR]
Moved to main.
** Changed in: python-os-brick (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-os-brick in Ubuntu.
https://bugs.launchpad.net/bugs/1472582
Title:
[MIR]
Both moved to main.
** Changed in: python-monotonic (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-oslo.service (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Moved to main.
** Changed in: requests-aws (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to requests-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1472971
Title:
[MIR]
All moved to main.
** Changed in: python-designateclient (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-manilaclient (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: python-zaqarclient (Ubuntu)
Status: Fix Committed = Fix Released
--
You
Moved to main.
** Changed in: zzzeeksphinx (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zzzeeksphinx in Ubuntu.
https://bugs.launchpad.net/bugs/1472392
Title:
[MIR]
Moved to main.
** Changed in: python-openstackclient (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-openstackclient in Ubuntu.
https://bugs.launchpad.net/bugs/1459157
Moved to main.
** Changed in: python-pathlib (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-pathlib in Ubuntu.
https://bugs.launchpad.net/bugs/1470070
Title:
[MIR]
** Project changed: launchpad = neutron (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1463377
Title:
The neutron-plugin-openvswitch-agetn.conf file, /etc/init.d and
This was a casualty of an infrastructure incident that went on long
enough to trip over a few should never happen conditions elsewhere,
causing a few architecture-independent packages to get lost from the
archive index files. I've restored this now, so openvswitch-pki should
be installable again.
** Changed in: installation-report (Ubuntu)
Assignee: Colin Watson (cjwatson) = (unassigned)
** Changed in: installation-report (Ubuntu)
Status: In Progress = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh
The verification of the Stable Release Update for juju-core has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for juju-core has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for juju-core has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
https://launchpad.net/ubuntu/+source/ruby-bdb/0.6.6-1
** Changed in: ruby-bdb (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ruby1.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1303358
We found that syslinux-common has been reverted to Architecture: all in
unstable, so I'm going to cherry-pick that change.
** Package changed: maas (Ubuntu) = syslinux (Ubuntu)
** Changed in: syslinux (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
--
You received this bug
After discussion with Steve, I'm withdrawing this FFe request. It's
just too late for 14.10, and in particular it's too late for us to be
changing the default cipher and MAC lists; I think they're good changes,
but we should be discovering any new interoperability problems more than
a week out
What is the value of $SSH_AUTH_SOCK before you attempt to override it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1380084
Title:
SSH client requires SSH_AUTH_SOCK=0 will not
The autopkgtests pass in Debian:
http://ci.debian.net/packages/o/openssh/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1379727
Title:
FFe: openssh 6.7p1
To manage
time, and the rest of it under autopkgtest.
-- Colin Watson cjwat...@debian.org Thu, 09 Oct 2014 14:05:56 +0100
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
I'm also having issues with libvirt/kvm guests becoming unresponsive and
they were all using cirrus as their video model. I've tried switching
some to vga to see if that helps.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in
The GRUB maintainer scripts won't run update-grub unless
/boot/grub/grub.cfg already exists, so your installation script must run
it. It shouldn't be particularly slow unless os-prober has to go out to
lots of slow disks.
--
You received this bug notification because you are a member of Ubuntu
Hello Chris, or anyone else affected,
Accepted seabios into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/seabios/1.7.4-4ubuntu0.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for crmsh has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Ack. Sync accepted.
** Package changed: ubuntu = python-xstatic-angular-cookies (Ubuntu)
** Changed in: python-xstatic-angular-cookies (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the
Ack. Sync accepted.
** Package changed: ubuntu = python-xstatic-jquery-ui (Ubuntu)
** Changed in: python-xstatic-jquery-ui (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Ack. Sync accepted.
** Package changed: ubuntu = python-hurry.filesize (Ubuntu)
** Changed in: python-hurry.filesize (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Ack. Sync accepted.
** Package changed: ubuntu = python-xstatic-angular-mock (Ubuntu)
** Changed in: python-xstatic-angular-mock (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug
Ack. Sync accepted.
** Package changed: ubuntu = python-xstatic-jquery.quicksearch (Ubuntu)
** Changed in: python-xstatic-jquery.quicksearch (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Ack. Sync accepted.
** Package changed: ubuntu = python-xstatic-bootstrap-datepicker
(Ubuntu)
** Changed in: python-xstatic-bootstrap-datepicker (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
The verification of the Stable Release Update for irqbalance has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Changed in: gfs2-utils (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: gfs2-utils (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gfs2-utils in Ubuntu.
https
Peter: While this is true, is it actually likely to happen? I thought
in our conversations in the past (when I previously attempted to
escalate this class of problems via Linaro) it had been fairly clear
that this was a very difficult task that isn't likely to be scheduled
for the foreseeable
Right, I can absolutely understand that. The question would I suppose
be whether you think this is a completely unreasonable thing to put in a
distro patch; I think SUSE are doing so for basically the same reason we
would be, that is, a setup such as PPAs where virtualisation isn't
available
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Moved to main.
** Changed in: python-mccabe (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-mccabe in Ubuntu.
https://bugs.launchpad.net/bugs/1331467
Title:
[MIR]
The verification of the Stable Release Update for debian-installer-utils
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
Moved to main.
** Changed in: python-termstyle (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-termstyle in Ubuntu.
https://bugs.launchpad.net/bugs/1337894
Title:
[MIR]
Moved to main.
** Changed in: python-rednose (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-rednose in Ubuntu.
https://bugs.launchpad.net/bugs/1333686
Title:
[MIR]
The verification of the Stable Release Update for pacemaker has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for corosync has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Hello Leonardo, or anyone else affected,
Accepted debian-installer into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu136.18 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Hello Leonardo, or anyone else affected,
Accepted debian-installer into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/debian-
installer/20101020ubuntu136.19 in a few hours, and then in the -proposed
repository.
Please help us by testing this
** Changed in: debian-installer-utils (Ubuntu Precise)
Milestone: None = ubuntu-12.04.5
** Changed in: debian-installer (Ubuntu Precise)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: debian-installer-utils (Ubuntu Precise)
Assignee: (unassigned) = Colin Watson (cjwatson
** Changed in: debian-installer-utils (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer
** Changed in: kickseed (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not support
** Changed in: rootskel (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/833994
Title:
debian-installer does not support
1 - 100 of 815 matches
Mail list logo
