nical Foundations Team (canonical-foundations) => Mathieu
Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is shown in plain text on t
Rebuilds in PPA have all passed -- the failures for efitools are exactly
the same as they previously were and due to EFI not being available (or
sbsigntool, efivar, etc.) on those architectures:
https://launchpad.net/~cyphermox/+archive/ubuntu/rebuild-tests/+packages
In any case, amd64 (the only
Verification-done for shim, shim-signed on bionic:
shim 15+1533136590.3beb971-0ubuntu1
shim-signed 1.37~18.04.1+15+1533136590.3beb971-0ubuntu1
System is booting as expected with the new shim, and mokutil allows for
importing a certificate and enabling validation at the same time (or any
multiple
This confirms the system boots and is in Secure Boot mode. Do you have
time to run through the other test cases using mokutil?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708245
Title:
shim
Verification-done on bionic with initramfs-tools 0.130ubuntu3.3:
Verified that with the SRU applied, the initramfs configured to use
MODULES=dep can still determine that the root is over ZFS, and
accordingly add the files needed in the initramfs.
** Description changed:
[Impact]
- Ubuntu
Verification-done for bionic with initramfs-tools 0.130ubuntu3.3:
Verified that at boot the system does get the additional config for
netplan in /run/netplan and that it forces systemd-networkd not to
release the IP lease.
** Tags removed: verification-needed verification-needed-artful
: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Status: New => In Progress
** Changed in: grub2-signed (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Committed
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: grub2-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785033
Title:
GRUB needs to support 64-bit efi linear frame buffer
shim and shim-signed 15 / 1.37 are already in Cosmic.
** Also affects: shim (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: shim (Ubuntu Cosmic)
Importance: Undecided
Status:
** Description changed:
[Impact]
All users on UEFI systems.
Gnu-efi needs to be backported everywhere to support new shim releases.
This applies to bionic, xenial, and trusty.
This is to properly build the new shim releases on these releases of
Ubuntu.
-
[Test cases]
--
Public bug reported:
[Impact]
All UEFI users.
[Test case]
== shim ==
1) Enable Secure Boot in firmware.
2) Update to new shim and shim-signed packages (shim 15+, shim-signed 1.37~)
3) Validate that the system still boots and validates the shim image as well as
the grub binary.
== MokManager
lso affects: syslinux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: syslinux (Ubuntu)
Status: New => In Progress
** Changed in: syslinux (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: syslinux (Ubuntu)
I
Public bug reported:
[Impact]
All users on UEFI systems.
Gnu-efi needs to be backported everywhere to support new shim releases.
This applies to bionic, xenial, and trusty.
This is to properly build the new shim releases on these releases of
Ubuntu.
[Test cases]
-- build tests --
Validate
Please include the *.network, *.netdev, *.link files from
/etc/systemd/network or /run/systemd/network as well for the
configuration, after making sure you sanitized them if there are any
information (IPs?) that you don't want public.
Thanks!
** Changed in: systemd (Ubuntu)
Status: New =>
MIR approved.
** Changed in: intel-processor-trace (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782977
Title:
[MIR] intel-processor-trace: new
** Changed in: shim-signed (Ubuntu)
Status: New => Fix Released
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789743
Title:
1.37 manual testing
To manage
Public bug reported:
15+1533136590.3beb971-0ubuntu1
** Affects: shim-signed (Ubuntu)
Importance: Undecided
Status: New
** Tags: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On cosmic as of 2018-08-29:
qemu-system-$arch packages appear to Recommend qemu-system-gui.
In turn, this means qemu-system-gui pulls in libgtk-3-0, which will pull
in icon themes and all kinds of other things that probably shouldn't
have to be on a server:
If anything, TBH it's unlikely to be shim /or/ grub; seeing as
netbooting on hardware just works; but we should have a good look at
shim and grub anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can reproduce. This looks to be something in grub that shim doesn't
appear to like.
** No longer affects: ipxe (Ubuntu)
** Package changed: shim-signed (Ubuntu) => grub2 (Ubuntu)
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
So, what is the failure mode here? Just not finding the binaries?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789319
Title:
Unable to load shimx64.efi using iPXE over UEFI
To manage
At the end of the install you still have a file in /etc/netplan. Did you
also remove that? That could definitely explain the delay, as the
installer wrote config for you (with how you configured the interface in
the installer), and that config will be attempted at boot.
** Changed in: netplan.io
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789130
Title:
Well, we do use loop devices and do expect them to be listed for
building the images. I'm not sure if there'll be a way to differentiate
between the image build case and normal case to be able to pass some
parameter (--skip-loopback, whatever) as appropriate. Let's look into
that.
** Changed in:
All that patch would do is show a pretty error message earlier, not
actually make sure the problem is fixed -- upgrades would still fail;
installs would still fail on RAID.
This has to do with grub not grokking the metadata format on disk, which
is avoidable by using metadata 0.90.
--
You
@John, I've uploaded initramfs-tools with your patch to both cosmic and
18.04. Now, for the process of stable release updates [1]; we do need
test cases and what is likely to break in case of a regression. I've
added this to the best of my knowledge, but I don't have any systems
with ZFS -- given
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661629
Title:
upgrade of kernel fails with mkinitramfs: failed to
Repurposing this bug now to track the feature work for a specific
activation mode option in netplan to keep interfaces administratively
down (or manually configured)
** Changed in: nplan (Ubuntu)
Status: Confirmed => In Progress
** Changed in: nplan (Ubuntu Xenial)
Status: Fix
Let's get a code review for mecab by the security team. It parses data
to re-encode...
** Changed in: mecab (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
mecab-ipadic reviewed; it's basically only data in EUC-JP format, with
an additional package that builds from that into UTF-8 format at install
time. While that seems to be suboptimal to me, there's no particular
objection.
MIR approved for mecab-ipadic.
** Changed in: mecab-ipadic (Ubuntu)
These packages appear to be missing a subscribing team, as is required
for MIRs.
Have you discussed including these packages in main with the server
team? I've subscribed them to this bug to have their opinion on whether
they are okay with the added effort of looking after mecab, mecab-
ipadic,
This package is straightforward, appears to be well-maintained in
Debian, and unlikely to require a significant maintenance effort in
Ubuntu. Extensive tests are part of the build, and the code looks good.
MIR approved.
** Changed in: sortedcontainers (Ubuntu)
Status: In Progress => Fix
** Changed in: oath-toolkit (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: oath-toolkit (Ubuntu)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This package does show some signs of age, and would probably really
benefit (maintainability-wise) from having some cleanup/modernizing of
the packaging, for instance to update debhelper usage, replace cdbs,
etc.
Assigning to the Security team since this includes a PAM module and is
generally
** Changed in: oath-toolkit (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: oath-toolkit (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sortedcontainers (Ubuntu)
Status: New => In Progress
** Changed in: sortedcontainers (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We need to clarify whether the other bug really is a verification-
failed. I don't think it actually fails, it's just an incomplete fix
given that there's existing config that we can't easily change post-
install.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Manual testing done, both UEFI and legacy work.
** Changed in: grub2 (Ubuntu)
Status: New => Fix Released
** Changed in: grub2-signed (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Already covered in ubiquity since artful. ubiquity upload in progress to
address this on xenial.
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
cyphermox tested that grub2_2.02-2ubuntu13's reloc patch to grub-mkimage
do generate a bootable image on UEFI.
Needs a smoke-test to make sure we also have working legacy boot (grub-
pc) images generated from grub-mkimage.
** Affects: grub2 (Ubuntu)
Importance:
** Description changed:
[Impact]
All Ubuntu users.
[Test case]
Run 'sudo update-grub'. The message is shown at the beginning.
[Regression potential]
- Changes to the default config options may adversely impact boot behavior for
the systems. Systems could start to always show the
** Description changed:
+ [Impact]
+ All Ubuntu users.
+
+ [Test case]
+ Run 'sudo update-grub'. The message is shown at the beginning.
+
+ [Regression potential]
+ Changes to the default config options may adversely impact boot behavior for
the systems. Systems could start to always show the
** Description changed:
+ [Impact]
+ All users of third-party modules on Ubuntu.
+
+ [Test cases]
+ 1) Install Ubuntu on an UEFI system
+ 2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf
/var/lib/shim-signed/mok/*"
+ 3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms"
+
@Hans,
Could you help verifying that this fix is working? I don't have access
to any NVMe hardware.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771845
Title:
grub-installer raid
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771704
Title:
support for ipv4 link-local addressing
To manage
Verification done on xenial with partman-auto/134ubuntu1.3:
Installed on a 320G disk with LVM (so that a boot partition gets created
at all); /boot is generated with a size of 766MB. Obviously, exact size
of the /boot partition will depend on the overall disk size, since the
recipe depends on the
I've tested this on a system while testing the other SRU that goes with
this upload (bug 1769682). I don't have any delays with the SRU
installed, and see no lvmetad warnings. I do have an /etc/initramfs-
tools/conf.d/resume file that points to my swap partition, but that
doesn't seem to adversely
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716999
Title:
installer creates rather small /boot partition
To manage
Verification-done on xenial: nplan/0.32~16.04.6:
http://autopkgtest.ubuntu.com/packages/nplan lists the autopkgtest
results on xenial. The tests that were flaky are now passing at first
run (so no longer flaky), and are reproducible on the command-line.
arm64, s390x are permanent failures for an
** Changed in: fusiondirectory (Ubuntu Xenial)
Status: New => In Progress
** Changed in: fusiondirectory (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: fusiondirectory (Ubuntu Bionic)
Status: New => In Progress
--
You
Verification-done for xenial with initramfs-tools/0.122ubuntu8.12:
critical: true is correctly written into /run/netplan/$interface.yaml;
which makes networkd not bring down the interface when restarting, which
avoids crashing the system.
** Tags removed: verification-needed-xenial
** Tags
Assigning to debian-installer for now -- this might be an issue where
ca-certificates is missing (since it needs to be there before you go get
it from an https mirror, hopefully).
That said, is this issue reproducible using the standard iso image; the
one available on
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258597
Title:
[Patch] Setting GRUB_TIMEOUT to a
** Changed in: fusiondirectory (Ubuntu)
Status: New => In Progress
** Changed in: fusiondirectory (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
s: New => In Progress
** Changed in: dovecot (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780996
Title:
Conv
** Changed in: dovecot (Ubuntu)
Status: New => In Progress
** Changed in: dovecot (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780606
I'd be a bit surprised if there really was a regression due to the
change, we're more likely seeing something going down due to the DHCP
server being slow to respond, possibly because it already responded
before?
What does the 'networkctl' command show immediately after boot?
Let's continue
** Description changed:
- The installer (in 16.04 and 17.10) creates a separate /boot partition,
- when required, of only 487M. This ends up being rather small when you
- using the following equation to estimate a minimal size allowing for
- reasonable room for further growth.
+ [Impact]
+ All
** Description changed:
+ [Impact]
+ Installs on NVMe hardware, on RAID deployments (RAID made of NVMe devices).
+
+ [Test case]
+ - Install Ubuntu on NVMe drives, configure the drives in RAID.
+
+ [Regression potential]
+ Attention should be taken to the behavior of installs, especially on
Why is this targetted to 18.04 too? It was fixed in artful, do we still
need to further increase /boot size?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716999
Title:
installer creates rather
** Description changed:
+ [Impact]
+ Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
+
+ [Test case]
+ - Write a new netplan YAML (adjusting for current system as necessary):
+ network:
+ version: 2
+ ethernets:
+ ens3:
+
** Description changed:
+ [Impact]
+ autopkgtests gating the netplan releases in the Ubuntu archive.
+
+ [Test case]
+ Validate that the tests are passing; specifically test_eth_* and
test_bond_resend_igmp.
+
+ [Regression potential]
+ Given that this is limited to the test suite, there is
Verification-done on artful, using update-manager 1:17.10.15:
Verified that the application does not take 100% CPU while waiting for
input at the "computer needs restart" dialog; and the expected code
changes are applied on the python modules on disk. Applying updates
completed without issues.
MIR approved.
Please make sure to move the packaging source to someplace other than
~rbalint's own tree; it probably should be modifiable by others.
** Changed in: gce-compute-image-packages (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a
** Changed in: installation-guide (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
** Summary changed:
- adjust the s390x parts of the 16.04 install guide
+ adjust the s390x parts of the install guide
--
You received this bug notification because you are a member of Ubuntu
** Also affects: nplan (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Verification-done on bionic with shim-signed/1.34.9.1:
update-secureboot-policy now properly accepts passwords with spaces, and
passes them cleanly to mokutil.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug
Verification-done on bionic with shim-signed/1.34.9.1:
I checked that you can no longer backtrack in the GNOME debconf frontend
from the "enable secure boot" question to cause the dialog to fail.
Backtracking is no longer accepted, only allowed as part of the password
handling steps.
** Tags
** Tags removed: verification-done-artful verification-done-bionic
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769682
Title:
NFS-based remote root hangs when running
Verification-done with update-manager/1:18.04.11.2 on bionic:
I verified that the restart CPU does not show 100% CPU usage, and it
does show without crashing update-manager. AFAICT this is fixed
correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Verification-done with update-manager/1:18.04.11.2 on bionic:
Verified that the restart CPU does not show 100% CPU usage, and it does
show without crashing update-manager. AFAICT this is fixed correctly.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
Hi,
Could you please run the following commands and report their full
output?
sudo efibootmgr -v
sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
(the backslashes there matter, we are building a path in EFI mode)
Thanks!
--
You received this bug notification because you are a
Hi,
Could you please run the following commands and report their full
output?
sudo efibootmgr -v
sudo efibootmgr -v -c -L ubuntu -l \\EFI\\ubuntu\\shimx64.efi
(the backslashes there matter, we are building a path in EFI mode)
Thanks!
** Changed in: ubuntu-release-upgrader (Ubuntu)
Marking verification-done since it was verified as fixed in comments
#10, #11.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ubuntu@AcerAspire:~$ sudo ethtool -i enp2s0
driver: tg3
version: 3.137
firmware-version: sb
expansion-rom-version:
bus-info: :02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
I am unable to reproduce this with
What daily image are we talking about?
How does "stuck in grub" present? Do you get thrown into a grub prompt,
or do you just see nothing after the grub menu disappears?
** Changed in: grub2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
This issue was reported prior to 18.04 GA, using an older version of
netplan.io. Have you tested the same with a newer version of netplan?
It seems to work just fine here -- with two network interfaces connected
to the system, I connect using ens6; then modify the netplan
configuration to move
Setting verification-done -- validation of the livecd-rootfs changes was
done with 2.408.33 as per the previous comment.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
+ [Impact]
+ Any user of Secure Boot with DKMS modules having the GNOME debconf frontend
enabled or other debconf frontends that are not Dialog or readline.
+
+ [Test case]
+ 1) Delete /var/lib/shim-signed/mok/MOK.* if exists.
+ 2) Run 'sudo update-secureboot-policy
** Description changed:
- This happens when I tried to setup boot key during 18.04 upgrade.
+ [Impact]
+ Any user of third-party (dkms) modules with Secure Boot enabled, who uses a
space in the mok password.
+
+ [Test case]
+ 1) Delete /var/lib/shim-signed/mok/MOK.* if exists.
+ 2) Run 'sudo
MIR approved, please add the bug subscriber.
** Changed in: dwz (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775768
Title:
[MIR] dwz - new dependency
- AIUI usually desktop-bugs should be subscribed -- has the team
situation for which teams you guys are looking at the bugs for been
clarified?
- tests exists, and are "run" but all are skipped: please fix this to
actually run the tests properly, or explain why they can only be
skipped.
As
Why does this require a MIR? It doesn't seem like there are any packages
depending on it, in any flavour. Whether libappindicator FTBFS or not
has no bearing on this.
** Changed in: libayatana-appindicator (Ubuntu)
Status: New => Incomplete
** Changed in: libayatana-appindicator (Ubuntu)
This is a complex javascript package, and there seems to be a heavy
history of XSS issues with openstack dashboards. I'd be more confident
if this was reviewed by the Security Team. They can optionally decide
that I'm just being too paranoid ;)
** Changed in: heat-dashboard (Ubuntu)
Setting this to Fix Committed.
There has been feedback from the Security team, feedback was addressed,
and it seems that in any case bundling of Go dependencies in trusty is
more or less "unavoidable".
MIR team ACK on promoting snapd to main in trusty.
** Changed in: snapd (Ubuntu)
James,
This hasn't been addressed yet (fixing BINDNOW and tests as per Tyler's
comment in comment #4). Please fix ASAP.
** Changed in: python-scrypt (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This MIR has been completed, but squashfuse is still not in main (and
apparently not Depend-ed on by snapd).
None of the referenced bugs mentions squashfuse, what is the status of
this?
** Changed in: snapd (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: snappy
Status: In
Unsubscribing ~ubuntu-mir: the MIR for geoclue-2.0 and iio-sensor-prxoy
are done, geoclue needs looking at (it's assigned, as per Steve's
comment). The MIR team does not need any additional visibility on this
since geoclue has already been demoted to universe.
--
You received this bug
Unsubscribing ~ubuntu-mir: the MIR for geoclue-2.0 and iio-sensor-prxoy
are done, geoclue needs looking at (it's assigned, as per Steve's
comment). The MIR team does not need any additional visibility on this
since geoclue has already been demoted to universe.
--
You received this bug
This one is just pending promotion based on something "pulling it" in
main -- probably should be in some "supported" seed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572539
Title:
[MIR]
Dependency on py3dns was dropped from python-formencode; as such, this
MIR appears to no longer be needed.
Closing as Invalid; please reopen or open a new MIR if py3dns should be
in main for another reason.
Thanks!
** Changed in: py3dns (Ubuntu)
Status: Incomplete => Invalid
--
You
James, is there still interest in python-pykmip in main? This package
had some issues identified that should be fixed prior to promotion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543754
Title:
Unsubscribing ~ubuntu-mir; this package was promoted, and later removed
from the archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488425
Title:
[MIR] ubuntu-download-manager
To manage
This already has been reviewed and was in main in artful; if you need it
back in main (and to stay there), you will also need to have something
Depends on it, or have it listed in a seed.
Setting back to Fix Committed -- no further review necessary.
** Changed in: neutron-vpnaas (Ubuntu)
Closing as Invalid, there appears to be nothing depending on it, and the
request was made for build-dependencies (testing) of unity components.
Please don't hesitate to reopen if this turns out to be needed by
something else.
** Changed in: gmenuharness (Ubuntu)
Status: Fix Committed =>
Closing as Invalid as this was open as a MIR for build-dependencies when
such a process was still needed. If it turns out that libxml-xpath-perl
becomes needed for a binary dep in main, please reopen (or file a new
MIR)
** Changed in: libxml-xpath-perl (Ubuntu)
Status: Incomplete =>
Closing as Fix Released, angular.js is already in main but the bug
wasn't closed...
** Changed in: angular.js (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
801 - 900 of 8586 matches
Mail list logo
