squid3-3.5.12-1ubuntu3 uploaded already by stgraber handled using the
dpkg-maintscript-helper to clean up the old /etc/init.d/squid3 file.
This debdiff handles the second task of removing the check on how to
restart squid and just calls invoke-rc.d squid restart unconditionally.
I've tested this
Now with less libaio-dev in control file for no AIO. Thanks for
catching my mistake
** Patch added: "old_ubuntu-new_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616629/+files/old_ubuntu-new_ubuntu.debdiff
--
You received this bug notification becau
On Tue, Mar 29, 2016 at 9:05 PM, Steve Langasek <
steve.langa...@canonical.com> wrote:
> Ryan, for ease of review and sponsorship please provide an incremental
> debdiff against the package that's already in xenial-proposed.
>
I actually did in comment 18, but I didn't know that was sufficient an
As far as I can see, the entire versioned code block here is wrong, and
> you should *only* be restarting squid.
>
>
The block (without my addition) is from debian itself. The original block
that's
present in debian:
update-rc.d squid defaults 30 >/dev/null
if test -d /etc/squid3 && dpkg --compa
I've attached new debdiff integrating the change to the squid.postinst
fix. We would like to get this build uploaded into proposed (and locked
as the current one is) to continue wider testing of the new squid.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Old Ubuntu to New Ubuntu debdiff
** Patch added: "old-ubuntu-to-new-ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4616441/+files/old-ubuntu-to-new-ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Old Ubuntu to New Debian debdiff
** Patch added: "old-ubuntu-to-new-debian.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+attachment/4616440/+files/old-ubuntu-to-new-debian.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Dropped AIO enablement; while the feature was isolated, we've had no
testing on the aio backend; we can always enable it later if we get
enough testing to ensure proper functionality. Therefore dropping the
FFE and just requesting a merge with Debian.
** Changed in: tgt (Ubuntu)
Status: In
Old Ubuntu -> New Debian debdiff
** Patch added: "old_ubuntu-new_debian.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616323/+files/old_ubuntu-new_debian.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Old Ubuntu to New Ubuntu
** Patch added: "old_ubuntu-new_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4616324/+files/old_ubuntu-new_ubuntu.debdiff
** Summary changed:
- [FFE] Please merge tgt 1.0.63 from Debian (unstable)
+ Please merge tgt 1.0.63 fr
Kick,
Thanks for the thorough upgrade test. I was able to recreate and debug
the proposed package install script. It appears that the squid.postinst
expects to find a /etc/init.d/squid3 service script if we also have an
existing /etc/squid3 directory. However, in my testing, we do have the
/etc
This error was unrelated to libvirt-bin itself, rather the locales
package from glibc in Xenial had an issue with generating locales (and
locale-archive); This was fixed in a new release (on 3/23) and
subsequent cloud builds after 3/22 which have newer glibc locales
package do not experience this
Linking against libaio allows tgt to use libaio as a backend for submitting IO
to the backing device.
The default backend uses pread64/pwrite64. Adding an additional backed does
not change this default
For users to consume the aio backend, they must specify the backend type
via command line swi
Discussion from #ubuntu-release
rharper: As for the AIO thing, as you understand the code, what are
the odds this could have a negative impact on users of other backends if the
AIO stuff is broken?
rharper: If you're 99% confident that the change is meaningless for
people who don't use the fe
Here's my initial test with the merged multipath-tools test.
I had the FCP devices enabled with the 0.5.0+git-1ubuntu2 package
installed from the merges ppa and rebooted the system.
After booting, I confirmed the paths were up, then used a vmcp command to
disconnect the devices.
I then queried
** Changed in: exim4 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/1550646
Title:
package exim4-daemon-light 4.86-3ubuntu1 failed to install
Install log of tgt 1.0.63-1ubuntu1 under lxd machine container.
** Attachment added: "install.log"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595176/+files/install.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
sbuild build log of 1.0.63-1ubuntu1 on amd64
** Attachment added: "tgt_1.0.63-1ubuntu1_amd64-20160309-1702.build"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595175/+files/tgt_1.0.63-1ubuntu1_amd64-20160309-1702.build
--
You received this bug notification because
debdiff (old/ubuntu) 1.0.62-1ubuntu1 to (new/ubuntu) 1.0.63-1ubuntu1
** Patch added: "old_ubuntu-new_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595174/+files/old_ubuntu-new_ubuntu.debdiff
--
You received this bug notification because you are a mem
debdiff (old/ubuntu) 1.0.62-1ubuntu1 to (new/debian) 1.0.63-1
** Patch added: "old_ubuntu-new_debian.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1555700/+attachment/4595173/+files/old_ubuntu-new_debian.debdiff
--
You received this bug notification because you are a member of
Public bug reported:
New Upstream release which incorporates one outstanding patch in 1.0.62
and adds support for AIO backend for tgt.
** Affects: tgt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, w
Thorsten,
Here's my PPA with the merged multipath-tools package for s390x:
https://launchpad.net/~raharper/+archive/ubuntu/merges/
You can add it via:
sudo add-apt-repository ppa:raharper/merges
sudo apt-get update
sudo apt-cache policy multipath-tools
The last command should show you a newer
Hi Thorsten,
We're going to merge with upstream debian. That work is tracked under
bug 1551952.
I'm now working on getting an s390x build of the package and reproducing on one
of the systems to
help test that the merge addresses this bug (and doesn't regress anything as
well).
--
You receive
dpkg install of kpartx and multipath-tools on Xenial amd64 kvm VM.
** Attachment added: "install.log"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594203/+files/install.log
--
You received this bug notification because you are a member of Ubuntu
Server
debdiff old/ubuntu (0.5.0-7ubuntu16 ) to new/debian
(0.5.0+git1.656f8865-5)
** Patch added: "old_ubuntu-new_debian.debdiff"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594201/+files/old_ubuntu-new_debian.debdiff
--
You received this bug notification be
I've run the package under adt-run and it passes.
After installing and running in a VM using virtio-scsi configured as
multipath, I can successfully find the devices configure.
ubuntu@mp1:~$ dpkg --list | grep multipath-tools
ii multipath-tools 0.5.0+git1.656f8865-5ubuntu2
sbuild log of updated multipath-tools
** Attachment added:
"multipath-tools_0.5.0+git1.656f8865-5ubuntu2_amd64-20160309-1159.build"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594202/+files/multipath-tools_0.5.0+git1.656f8865-5ubuntu2_amd64-20160309-115
debdiff from old/ubuntu (0.5.0-7ubuntu16) to new/ubuntu
(0.5.0+git1.656f8865-5ubuntu1)
** Patch added: "old_ubuntu-new_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4594200/+files/old_ubuntu-new_ubuntu.debdiff
--
You received this bug not
On Mon, Mar 7, 2016 at 5:40 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> This appears to have fixed the nvme partition problem but, I'm sure
> there are nicer ways to do it.
>
>
Hi Rob!
Thanks for confirming a workaround.
> root@maas1:~# diff -u
> /usr/lib/python3/dist-p
On Mon, Mar 7, 2016 at 1:50 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> Thanks, let me know if you need me to make any changes or run through
> any tests.
>
> A quick question if I may: How is the config generated when the node is
> deploying? I have found that storage con
On Mon, Mar 7, 2016 at 2:15 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> Here you go
>
> /var/lib/cloud/instance/scripts/part-001 extract
>
> cd curtin
>
> cat configs/config-000.cfg
> #cloud-config
> …
> ...
> partitioning_commands:
> builtin: [curtin, block-meta, custom
One more try, lets specify the partition "number" as 'p1' instead.
- {device: nvme0n1, id: nvme0n1p1, name: nvme0n1p1, number: 'p1', offset:
4194304B, size: 128026935296B, type: partition, uuid:
e66f2d9d-963a-4cb9-b2b5-472d491e768b, wipe: superblock}
On Mon, Mar 7
OK; thanks. I need to work with nvme devices on Xenial; it looks like the
storage naming rules for partitions are different for NVME devices (p1, p2,
p3) versus other disks (1, 2, 3 4);
On Mon, Mar 7, 2016 at 12:54 PM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi Ryan,
>
> I have tri
Yeah, looks like the mkfs code is expecting you to include label: 'some
label' in the format dictionary.
Can you try injecting a label into the format dictionary:
- {fstype: ext4, id: nvme0n1-part1_format, label: 'SOME_LABEL_HERE', type:
format, uuid: 6a47f95c-40b6-478a-aefa-ca84a509d877,
vo
On Sat, Mar 5, 2016 at 3:56 AM, Rob Sanderson <1401...@bugs.launchpad.net>
wrote:
> Hi,
>
> I'm still seeing this issue on Xenial.
>
> root@maas1:~# cat /etc/lsb-release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=16.04
> DISTRIB_CODENAME=xenial
> DISTRIB_DESCRIPTION="Ubuntu Xenial Xerus (development br
** Attachment added: "Changelog from 0.5.0 to version in Debian unstable;
dropped "fix" entries and other non-features."
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1551952/+attachment/4585938/+files/Changelog-0.5.0..656f8865.txt
--
You received this bug notification becau
Public bug reported:
Upstream hasn't released a new version, but there are a large number of
new features available in the version included in Debian unstable.
This version from Debian has been confirmed to fix bug 1540407
The new version of the package will be tested with:
- MAAS driven Power
On Tue, Mar 1, 2016 at 3:00 AM, bugproxy wrote:
> --- Comment From thorsten.di...@de.ibm.com 2016-03-01 03:58 EDT---
> (In reply to comment #19)
> > As already promised, I will continue some long term tests (cable pull and
> > other path loosing scenarios) on a 4.4.0-8 system with
> > mul
Hi Thorsten,
Thanks for the update. I'll attempt to find out if I can force a detach
on the host-side to recreate the issue on x86 while I'm waiting for a Z
system with FCP devices.
Could you attempt to use the Debian package from Sid on top of the
Ubuntu system? This will help rule out kernel
Hi Thorsten,
The latest version of the multipath-tools package is 0.5.0-7ubuntu14.
Can you confirm you're still seeing the issue?
Meanwhile, I'm hoping to recreate this issue on zKVM shortly. In the
meantime I'm testing this on in an x86 VM with multipath via virtio-
scsi, using the same multip
This fix has been released in Xenial, as tgt 1:1.0.62-1ubuntu2
** Changed in: tgt (Ubuntu)
Status: In Progress => Fix Released
** Changed in: tgt (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => (unassigned)
--
You received this bug notification because you are a member of
** Patch added: "debdiff netween debian 5.3.5-1 and ubuntu 5.3.5-1ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+attachment/4573963/+files/debian-5.3.5-1-to-5.3.5-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team
** Patch added: "Ubuntu debdiff between 5.1.2-0ubuntu8 and 5.3.5-1ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1535951/+attachment/4573962/+files/ubuntu-5.1.2-0ubuntu8-to-5.3.5-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Serv
I've pushed the latest revisions into the PPA:
strongswan (5.3.5-1ubuntu7) xenial; urgency=medium
* debian/{rules,control,libstrongswan-extra-plugins.install}
Enable bliss plugin
* debian/patches/increase-bliss-test-timeout.patch
Under QEMU/KVM for autopkgtest bliss test takes a bit l
** 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 the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage not
owpan-test-tools
lowpan-tools
neard
neard-tools
ntrack-module-libnl-0
plainbox-provider-resource-generic
sssd-common
wpasupplicant
** Changed in: libnl3 (Ubuntu Trusty)
Assignee: Ryan Harper (raharper) => (unassigned)
--
You received this bug notification because you are a member of
On Tue, Feb 16, 2016 at 8:46 AM, mrq1 wrote:
> it looks like strongswan is faking a nat situation if the kernel-libipsec
> is used, so there are only problems with transport & beet mode ..
>
It sounds like it could be confusing. I'd prefer not to have a one-off for
just this
package but if it'
On Sun, Feb 14, 2016 at 3:36 AM, mrq1 wrote:
> looks good so far :-)
>
> i think the kernel-libipsec plugin should not be loaded by default
>
> the plugin works only with UDP encapsulated packets
>
> (look here: https://wiki.strongswan.org/projects/strongswan/wiki/Kernel-
> libipsec)
>
> and thi
On Sun, Feb 14, 2016 at 2:12 AM, mrq1 wrote:
> thanks for the fast pace!
>
> > should be ready in a bit with the new plugin
>
> NOPE. still no chapoly & ntru plugin included
>
chapoly and ntru are part of libstrongswan-extra-plugins
>
> # ipsec statusall
> Status of IKE charon daemon (strongSw
On Sat, Feb 13, 2016 at 7:51 PM, Simon Déziel <1535...@bugs.launchpad.net>
wrote:
> On 2016-02-13 05:09 PM, Ryan Harper wrote:
> > On Sat, Feb 13, 2016 at 12:27 PM, mrq1 wrote:
> >
> >> great! starts now :-)
> >>
> >> what about the chapoly plugin?
Excellent! I had forgotten about that. I'll update.
On Sat, Feb 13, 2016 at 7:00 PM, Simon Déziel <1535...@bugs.launchpad.net>
wrote:
> On 2016-02-13 12:39 PM, Ryan Harper wrote:
> > The extra-plugins package need some more privs for the charon binary
> > in the
** Bug watch added: Debian Bug tracker #803787
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803787
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to strongswan in Ubuntu.
https://bugs.launchpad.net/bugs/1535951
Title:
Please mer
On Sat, Feb 13, 2016 at 12:27 PM, mrq1 wrote:
> great! starts now :-)
>
> what about the chapoly plugin? can you enable it in the extra package?
> it would be very important for me!
>
I can look at enabling it. It's new in 5.3.5. If enabled, can you test
and confirm it works?
Looks like someth
Ah, yes. I've a fix for that; I hadn't pushed my latest update in to the
ppa. The extra-plugins package need some more privs for the charon binary
in the apparmor profile.
Look for 1ubuntu5 in the ppa in just a bit and see if that fixes up the
issue with the extras plugins.
On Sat, Feb 13, 20
Yes, quite close. I'll handle the FFE if needed but I feel on-track.
I'm preparing the merge debdiff for review.
Threads:
https://lists.ubuntu.com/archives/ubuntu-devel/2016-January/039144.html
https://lists.ubuntu.com/archives/ubuntu-devel/2016-February/039201.html
Please give the test-package
v3 debdiff
- Removed unneeded spaces in debian/control Breaks entry
- Fixed up libnl-3-200.symbols file to tag private symbols as optional
(removes dpkg-gensymbols warning)
- Removed invalid use of Closes() for Debian bugs; instead use LP: #
** Patch added: "lp_1511735_libnl3_v3.diff"
I've updated the debdiff to include a Breaks: network-manager (<<
0.9.8.8-0ubuntu7.3) to ensure that users are forced to use the newer
network-manager (ie, this libnl won't install unless user has already
updated their network-manager) Thanks Mathew for the suggestion.
I've built and tested thi
This has not been released; this version is only available in trusty-
proposed. It's not been verified at this point.
** Changed in: libnl3 (Ubuntu Trusty)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
I've retagged this as verification-needed since we've had one regression
(NetworkManager, a bug there) and we'd like to request other users of
libnl to test out the version included in proposed so we can ensure
we're flushing out other applications that may be exposed due to the
behavior changed in
*** This bug is a duplicate of bug 1539634 ***
https://bugs.launchpad.net/bugs/1539634
** This bug has been marked a duplicate of bug 1539634
network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Server Team
Blueprint changed by Ryan Harper:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
** Bug watch added: Debian Bug tracker #813368
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813368
** Also affects: tgt (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813368
Importance: Unknown
Status: Unknown
--
You received this bug notification because you a
Forwarded patch to upstream via: https://github.com/fujita/tgt/pull/17
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1518440
Title:
tgt fails to install in LXD
To manage notification
Updated debdiff:
- Fix spelling of attempt
- replace spaces with tabs in patch.
** Patch added: "tgt_fix_lp1518440_v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1518440/+attachment/4560974/+files/tgt_fix_lp1518440_v3.debdiff
--
You received this bug notification because
Hi Nick,
We've not built a new NetworkManager package with the fix. For now,
you'll need to downgrade your libnl-3 packages:
% apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-
route-3-200=3.2.21-1
And you may need to apply a hold until a fix for NetworkManager can be
releas
This bug is related to an attempted SRU for libnl here:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735
The updated package exposes a bug in NetworkManager, which we're testing
a fix:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634
--
You received this bug
I've filed
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634 to track
the updated needed there.
I attached a debdeff in the NM bug after applying the patches from comment #24.
I tested the updated NM with proposed libnl-3 and it works as expected.
1. Download 14.04.03 De
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage not
Thanks Nicolas. I'm working on fixing up NetworkManager; we'll need
that fix as well to go out at the sametime.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: f
Looks like the changes in libnl exposed a bug in the N-M 0.98 code:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf
--
You r
Hi Jakub,
Thanks for testing the new package. It would be helpful to collect any
core files and backtraces.
apport-collect -p network-manager 1511735
Should collect the info for this bug report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
Nicolas,
Thanks for the ping. I'm looking for a sponsor to review the update.
If approved, then it'll get uploaded and continue through the SRU
process.
Thanks again for following up on this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
Public bug reported:
Please merge strongswan 5.3.5-1 (main) from Debian unstable (main)
** Affects: strongswan (Ubuntu)
Importance: Undecided
Assignee: Ryan Harper (raharper)
Status: New
** Changed in: strongswan (Ubuntu)
Assignee: (unassigned) => Ryan Harper (rahar
Blueprint changed by Ryan Harper:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: DONE
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
[raharper] : tgt merge (bug 1524982): DONE
[racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
No; it should go upstream AFAICT.
I can regen with tabs; my fault for not checking what the source file
used.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1518440
Title:
tgt fails
Can we publish some test images? Instead of guessing at this, we can
benchmark this.
In general swapping ram-based for what is almost always disk-based is
going to impact applications/deployments using tmp and expecting enough
space there. It's not uncommon for large ISO or other image downloads
https://lists.debian.org/debian-kernel/2015/10/msg00332.html
common threads 4.2 kernel and UEFI mode of kvm.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1532571
Title:
kvm crashes h
Blueprint changed by Ryan Harper:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: TODO
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
- [raharper] : tgt merge (bug 1524982): INPROGRESS
+ [raharper] : tgt merge (bug 1524982): DONE
[racb] nagios
On Wed, Dec 16, 2015 at 11:29 AM, Nicolas Dichtel wrote:
> Thank you.
>
> Note that the last three patches are not included in libnl 3.2.26, which
> is the version of ubuntu 16.04 /Xenial (
> https://launchpad.net/ubuntu/+source/libnl3/3.2.26-1).
>
Thank you for mentioning this.
> Should I mak
Tarball of the test-case used to confirm failure and fix.
** Attachment added: "lp_1511735_test.tar"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4535781/+files/lp_1511735_test.tar
** Description changed:
- The following upstream patches are needed in order to av
Attaching debdiff with changes needed to resolve the bug.
** Patch added: "lp_1511735_libnl3.diff"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4535780/+files/lp_1511735_libnl3.diff
--
You received this bug notification because you are a member of Ubuntu
Server T
debdiff between current ubuntu (1.0.57-1ubuntu2) and new ubuntu version
(1.0.62-1ubuntu1).
** Patch added: "ubuntu_merge_upgrade_v2.diff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1524982/+attachment/4535288/+files/ubuntu_merge_upgrade_v2.diff
** Changed in: tgt (Ubuntu)
Statu
debdiff between previous ubuntu version (1.0.57-1ubuntu2) and upstream
debian unstable (1.0.62-1).
** Patch added: "debdiff_ubuntu_1.0.57-1ubuntu2_to_debian_1.0.62-1.diff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1524982/+attachment/4535287/+files/debdiff_ubuntu_1.0.57-1ubuntu2_to_de
Sorry missed the notification, I'll remerge 1.0.62.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1524982
Title:
Please merge tgt 1.0.61-1 (main) from Debian unstable (main)
To manag
Hi,
Thanks for the quick update. I've applied the 4 patches and built a new
test package with the changes.The example test does indeed fail on
the current version and passes on the new version as well.
I went looking for any other libnl3 tests we might run to catch any
possible regression th
Initial look at the patches results in the following assessment:
The first 2 patches apply fine to the version included in Ubuntu Trusty
027157898708 lib/socket: don't fail if no more local ports can be assigned in
nl_socket_alloc
http://git.infradead.org/users/tgr/libnl.git/commitdiff/027157898
Blueprint changed by Ryan Harper:
Work items changed:
Work items for ubuntu-15.11:
[serge-hallyn] etckeeper: TODO
[paelzer] NIS merge: DONE
Work items for ubuntu-15.12:
- [raharper] : tgt merge: TODO
+ [raharper] : tgt merge (bug 1524982): INPROGRESS
[racb] nagios-plugins/monitoring
debdiff between current ubuntu (1.0.57-1ubuntu2) and new ubuntu version
(1.0.61-1ubuntu1).
** Patch added: "ubuntu_merge_upgrade.diff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1524982/+attachment/4532801/+files/ubuntu_merge_upgrade.diff
** Changed in: tgt (Ubuntu)
Status: In
Public bug reported:
Please merge tgt 1.0.61-1 (main) from Debian unstable (main)
** Affects: tgt (Ubuntu)
Importance: Wishlist
Status: Confirmed
** Changed in: tgt (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: tgt (Ubuntu)
Status: New => In Progress
--
You
debdiff between previous ubuntu version (1.0.57-1ubuntu2) and upstream
debian (1.0.61-1).
** Patch added: "debdiff_ubuntu_1.0.57-1ubuntu2_to_debian_1.0.61-1.diff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1524982/+attachment/4532800/+files/debdiff_ubuntu_1.0.57-1ubuntu2_to_debian_1.0.
Tested on Xenial/amd64
1. sudo apt-get install lxd
2. lxd-images import ubuntu xenial amd64 --alias ubuntu-xenial --alias
ubuntu/xenial
3. lxd launch ubuntu-xenial x1
4. lxc exec x1 /bin/bash
# Inside xenial LXD container
5. apt-get install tgt
... fails as per comment #2
After rebuilding tgt
Resolving this by cherry picking check on uid, and also allowing EACCES failure
due to username space.
The cherry pick could be dropped if we were to rebase on debian dev version
(tgt_1.0.61).
** Patch added: "tgt_fix_lp1518440.diff"
https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1518440
https://lists.linuxcontainers.org/pipermail/lxc-
devel/2015-October/012630.html
--
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/1510619
Title:
Wily: add machine fails using kvm and lxcbr
Currently looking at updatin lxc package to have lxc-net run After
=network-online.target which should ensure that ifup on auto interfaces
has run, meaning ethX interfaces will have obtained and IP and at that
point then lxc-net can check if something is squating on 10.0.3.X
network and switch to a
Applied the upstream patch (not yet committed) to the wily qemu package.
Builds OK, needs testing. Will post link to PPA with packages once it is
complete.
** Patch added: "lp1508466_apply_upstream_curses_fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1508466/+attachment/45
Looks like a patch was just submitted to address this:
http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg04319.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1508466
Title
Public bug reported:
As of 3.19+, overlayfs supports multiple lowerdir mount points to enable
merging multiple read-only layers together which is useful for composing
multiple layers together and then imposing an specific upper layer (say
tmpfs).
>From the kernel documentation[1]
| Multiple low
I've tested[1] the proposed package and it passes[2] the testcase in
the SRU justification.
1. uvt-simplestreams-libvirt sync release=trusty arch=amd64
uvt-kvm create --cpu 2--disk 10 t1 release=trusty arch=amd64
uvt-kvm wait --insecure t1
uvt-kvm ssh --insecure t1
# inside trusty
debdiff includes an updated apparmor profile for libvirt-qemu for
libraries provided by qemu-block-extra
** Patch added: "libvirt_qemu_block_extra_apparmor_update.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1495895/+attachment/4466889/+files/libvirt_qemu_block_extra_apparmor_u
This bug requires a fix to libvirt's apparmor profile as well.
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Importance: Undecided => High
** Changed in: libvirt (Ubuntu)
Status: New => Confirmed
** Changed in: qemu (Ubun
1 - 100 of 171 matches
Mail list logo
