[Group.of.nepali.translators] [Bug 1667105] Re: SRU tracker 2.22.6
** Also affects: snapd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Trusty) Importance: Undecided Status: New ** Description changed: - WIP + New bugfix release of snapd 2.22. + + [Impact] + * There are a small number systems in the wild that misbehave on upgrades. To track down the root cause we added better debugging and support to report errors to errrors.ubuntu.com + + [Test case] + * A test for regressions is sufficient. The full testsuite with >100 integration tests is run automatically. + + [Regression potential] + * little, pretty much all changes happen in code that is already a failure condition -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667105 Title: SRU tracker 2.22.6 Status in snapd package in Ubuntu: New Status in snapd source package in Trusty: New Status in snapd source package in Xenial: New Status in snapd source package in Yakkety: New Bug description: New bugfix release of snapd 2.22. [Impact] * There are a small number systems in the wild that misbehave on upgrades. To track down the root cause we added better debugging and support to report errors to errrors.ubuntu.com [Test case] * A test for regressions is sufficient. The full testsuite with >100 integration tests is run automatically. [Regression potential] * little, pretty much all changes happen in code that is already a failure condition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1667105/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1663376] Re: php7.0-snmp generates many warnings without snmp installed.
** Changed in: php7.0 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1663376
Title:
php7.0-snmp generates many warnings without snmp installed.
Status in php7.0 package in Ubuntu:
Confirmed
Status in php7.0 source package in Xenial:
Confirmed
Status in php7.0 source package in Yakkety:
Confirmed
Status in php7.0 package in Debian:
Fix Released
Bug description:
Somehow, the php7.0-snmp generates many warnings about missing
"things" until I install `snmp`. Maybe snmp should be a dependency?
A couple of references of people mentioning the problem:
https://www.digitalocean.com/community/questions/installed-php-7-0
-now-returns-errors
http://stackoverflow.com/questions/21257589/ubuntu-typing-php-in-
terminal-shows-a-lot-of-errors
The following is the output of starting a PHP CLI session without
`snmp` installed. After installing `snmp`, all those errors/warnings
disappear. So this is why I would suggest making `snmp` a dependency
of the `php7.0-snmp` package. Although if setting uip the
`/etc/snmp/snmp.conf` package would be enough (it turns off the MIB
search) maybe making the snmp library react as that was the default
could be better. Only it may be harder to get the snmp library owner
to do such.
$ php -a
MIB search path:
/home/alexis/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Cannot find module (SNMPv2-MIB): At line 1 in (none)
Cannot find module (IF-MIB): At line 1 in (none)
Cannot find module (IP-MIB): At line 1 in (none)
Cannot find module (TCP-MIB): At line 1 in (none)
Cannot find module (UDP-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)
Cannot find module (MTA-MIB): At line 1 in (none)
Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)
Cannot find module (SNMPv2-TC): At line 15 in
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-SMI): At line 34 in
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 37 in
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'enterprises' in module #-1
(/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'DisplayString' in module #-1
(/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'TruthValue' in module #-1
(/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Unlinked OID in UCD-SNMP-MIB: ucdavis ::= { enterprises 2021 }
Undefined identifier: enterprises near line 39 of
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'DisplayString' in module #-1
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Unlinked OID in UCD-DISKIO-MIB: ucdDiskIOMIB ::= { ucdExperimental 15 }
Undefined identifier: ucdExperimental near line 19 of
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-TC): At line 10 in
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Did not find 'DisplayString' in module #-1
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Unlinked OID in UCD-DLMOD-MIB: ucdDlmodMIB ::= { ucdExperimental 14 }
Undefined identifier: ucdExperimental near line 13 of
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Cannot find module (SNMPv2-TC): At line 15 in
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'DisplayString' in module #-1
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Unlinked OID in LM-SENSORS-MIB: lmSensors ::= { ucdExperimental 16 }
Undefined identifier: ucdExperimental near line 32 of
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'ucdavis' in module UCD-SNMP-MIB
(/usr/share/snmp/mibs/UCD-DEMO-MIB.txt)
Unlinked OID in UCD-DEMO-MIB: ucdDemoMIB ::= { ucdavis 14 }
Undefined identifier: ucdavis near line 7 of
/usr/share/snmp/mibs/UCD-DEMO-MIB.txt
Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 9 in
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Cannot find module (SNMPv2-SMI): At line 8 in
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Did not find 'enterprises' in module #-1
(/usr/share/snmp/mibs/NET-SNMP-MIB.txt)
Unlinked OID in NET-SNMP-MIB: netSnmp ::= { enterprises 8072 }
Undefined identifier: enterprises near line 10 of
[Group.of.nepali.translators] [Bug 1617098] Re: Add support for option max-routes
Sponsored the SRU. This does not need a fix in zesty as the fix is already applied there (via newer upstream release). Adam Collard, please update the bug description to follow the SRU procedures (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure). You will want to subscribe ~ubuntu-sru when the bug report description is ready. ** Also affects: network-manager-openvpn (Ubuntu Zesty) Importance: Wishlist Status: Triaged ** Also affects: network-manager-openvpn (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: network-manager-openvpn (Ubuntu Zesty) Status: Triaged => Fix Released ** Changed in: network-manager-openvpn (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: network-manager-openvpn (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1617098 Title: Add support for option max-routes Status in NetworkManager-OpenVPN: Fix Released Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-openvpn source package in Xenial: In Progress Status in network-manager-openvpn source package in Zesty: Fix Released Bug description: Hi, Currently in Ubuntu 16.04 network-manager-openvpn does not support the openvpn --max-routes switch. This means that per omission the VPN connection supports 100 routes that can be pushed by the openvpn server to the client. If the openvpn server pushes more 100 routes, which can happen in some cases, the VPN establishment fails. From OpenVPN manual: "--max-routes n Allow a maximum number of n --route options to be specified, either in the local configuration file, or pulled from an OpenVPN server. By default, n=100." Can you do one of the following? - Fully support max-routes in the GUI, with an option to choose the value of the max-routes or, simpler: - Do not implement the max-routes in the GUI but add '--max-routes 500' for example for all openvpn connection establishments. I mean increase the number of maximum routes for all openvpn connections with network-manager. There is also a gnome bugzilla related to this issue which was recently closed with a patch: https://bugzilla.gnome.org/show_bug.cgi?id=720097 When can we have the max-route implementation on network-manager- openvpn in ubuntu? mm:~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 mm:~$ apt-cache policy network-manager-openvpn network-manager-openvpn: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/statusThanks, mm:~$ apt-cache policy network-manager-openvpn-gnome network-manager-openvpn-gnome: Installed: 1.1.93-1ubuntu1 Candidate: 1.1.93-1ubuntu1 Version table: *** 1.1.93-1ubuntu1 500 500 http://pt.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status mm:~$ apt-cache policy openvpn openvpn: Installed: 2.3.10-1ubuntu2 Candidate: 2.3.10-1ubuntu2 Version table: *** 2.3.10-1ubuntu2 500 500 http://pt.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Regards, Marco To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1617098/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1638306] Re: [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error)
Hello Markus, or anyone else affected, Accepted zypper into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zypper/1.12.4-1build0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: zypper (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed ** Changed in: zypper (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1638306 Title: [SRU] zypper binary shipped w/ Ubuntu Xenial requires rebuild (relocation error) Status in zypper package in Ubuntu: Fix Released Status in zypper source package in Xenial: Fix Committed Bug description: [IMPACT] zypper is not usable at all. $ zypper -V zypper: relocation error: zypper: symbol _ZN4zypp5CpeId11NoThrowType13lastMalformedE, version ZYPP_plain not defined in file libzypp.so.1503 with link time reference [TEST CASE] * run: zypper -V [Regression Potential] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zypper/+bug/1638306/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
Thank you Dan, for the analysis. Per comment #23, I'll mark Won't Fix for xenial. ** Changed in: ifupdown (Ubuntu Xenial) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Won't Fix Status in ifupdown package in Debian: Fix Released Bug description: [Impact] When using dhcpv6 configured via ifupdown, the interface's dhcp client fails to start at boot with the error: Can't bind to dhcp address: Cannot assign requested address This is because ifupdown doesn't wait, after bringing the interface up, for it to complete its link-local Duplicate Address Detection (DAD), and the dhcp client can't bind to the link-local address because it's still in "tentative" state (until DAD completes). This is fixed upstream in debian ifupdown in version 0.8.11 by adding '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the script was only waiting for the link-local address to appear, now it waits until the link-local address appears and is not in 'tentative' state. [Test Case] Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 dhcp) and reboot. It will fail to get a dhcp address during boot. [Regression Potential] None [Other Info] After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. Related Bugs: * bug 1633479: dhclient does not wait for ipv6 dad (duplicate address detection) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1447715/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1641532] Re: machine-types trusty and utopic are not unique (depend on the qemu version)
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu5.3 --- qemu (1:2.6.1+dfsg-0ubuntu5.3) yakkety; urgency=medium * fix ambiguous machine trusty and utopic machine types (LP: #1641532) - d/p/ubuntu/define-ubuntu-machine-types.patch update type definitions - d/qemu-system-x86.NEWS to describe the issue -- Christian Ehrhardt Mon, 30 Jan 2017 08:07:06 +0100 ** Changed in: qemu (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1641532 Title: machine-types trusty and utopic are not unique (depend on the qemu version) Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive liberty series: In Progress Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Yakkety: Fix Released Status in qemu source package in Zesty: Fix Released Bug description: [Impact] * Guests that were created with the Trusty (or Utopic) machine type are not unique. Due to that on migrations between the qemu versions of multiple Ubuntu releases migrations fail * Many migrations work just by luck, one that fails is the Utopic Type on Cloud-Archive Liberty to Xenial. * The further one migrates that old guest the more breakage this accumulates. E.g. a Trusty guest (qemu 2.0) migrated to Xenial (thinks it is qemu 2.5 type) and from there migrating to Yakkety (which expects it to be a 2.6 type). * The fix is minimal and makes the types definition stable across releases as they were intended [Test Case] * Spawn a Guest of Type Utopic (the easiest still supported is Trusty + Cloud Archive Liberty). And then migrate it to Xenial. Without the patch migration fail, with the patches it works as both now agree what the guest definition means. Please do note that both ends of the migrations have to be fixed to get it working. * Similar a Guest of type Trusty can with the fixes applied be migrated X->Y->Z and back to X, while without the fix any backward way (and probably a future forward way) will fail. * Note: This is complex and there are many potential combinations - the testlogs (comment #15) attached have various permutations of those. It has shown that not only the Utopic type issue that was reported gets fixed, but several backward migrations as well. [Regression Potential] * While it fixes the cases that we know, and as testing showed also several cases that we didn't know before there are two things we can not avoid. 1. People have to restart the source guests so that the new fixed definition will take effect. But Trusty guests that were already migrated to a Host that has the error will have to be restarted before they can be migrated further. Note: no one has to restart guests on Trusty without Cloud Archive; there the Trusty type is ok - it is a 2.0 which after the fix Xenial/Yakkety agree. 2. Restarting the guests after the fix will "downgrade" the virtual hardware. One can think of the machine types as the HW-revision of the virtual HW. A Guest that was created as e.g. Trusty these days on Xenial as incorrectly "too new" virtual HW, restarting the guest will fix that - but as part of that new attributes that it incorrectly gained when migrating/moving to the new host will be taken away (to match the definition the guest had when it was started) This is actually a fix, but might appear as a regression to somebody without knowing what was going on. Also anybody that "wants" the new HW can just upgrade the machine type to get it, which is actually recommended anyway [1]. [Other Info] * This is a complex issue, please catch me (cpaelzer) on IRC if you need/want to go into detail. Or for Cloud Archive questions coreycb. [1]: https://wiki.ubuntu.com/QemuKVMMigration#Upgrade_machine_type --- original description --- Hi, I'm currently live-migrating many VMs from an old server to a new one, and some VM can't be live migrated. The source host is trusty with qemu-system-x86 1:2.3+dfsg-5ubuntu9.4~cloud2 The destination host is xenial with qemu-system-x86 1:2.5+dfsg-5ubuntu10.6 When the issue occurs, the destination host raises an error [1] and stop the migration process. The only difference I see between VMs where live migration works and those were it doesn't work is a different machine type. * migration works when VM have been created with pc-i440fx-vivid * migration doesn't work when VM have been created with pc-i440fx-utopic [1] the qemu error repor
[Group.of.nepali.translators] [Bug 1641592] Re: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles
This bug was fixed in the package nano - 2.5.3-2ubuntu2 --- nano (2.5.3-2ubuntu2) xenial-proposed; urgency=medium * Apply upstream patch to allocate enough space for the prompt when finding a lock file. (LP: #1641592) -- Brian Murray Tue, 14 Feb 2017 15:10:03 -0800 ** Changed in: nano (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1641592 Title: nano 2.5.3-2 on Xenial crashes with long paths on lockfiles Status in nano package in Ubuntu: Fix Released Status in nano source package in Xenial: Fix Released Bug description: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt-cache policy nano nano: Installed: 2.5.3-2 Candidate: 2.5.3-2 Reproducer: 1. # nano -G 999 2. 3. # nano -G 999 4. 5. Quick dissection: Looking at function do_lockfile in files.c, it seems that promptstr is statically allocated to 128 characters. Now with a sufficiently long filename, the following sprintf() call will overflow the allocated promptstr buffer and corrupt memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1641592/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1641532] Re: machine-types trusty and utopic are not unique (depend on the qemu version)
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.9 --- qemu (1:2.5+dfsg-5ubuntu10.9) xenial; urgency=medium * fix ambiguous machine trusty and utopic machine types (LP: #1641532) - d/p/ubuntu/define-ubuntu-machine-types.patch update type definitions - d/qemu-system-x86.NEWS to describe the issue -- Christian Ehrhardt Mon, 30 Jan 2017 08:04:27 +0100 ** Changed in: qemu (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1641532 Title: machine-types trusty and utopic are not unique (depend on the qemu version) Status in Ubuntu Cloud Archive: Fix Committed Status in Ubuntu Cloud Archive liberty series: In Progress Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Yakkety: Fix Released Status in qemu source package in Zesty: Fix Released Bug description: [Impact] * Guests that were created with the Trusty (or Utopic) machine type are not unique. Due to that on migrations between the qemu versions of multiple Ubuntu releases migrations fail * Many migrations work just by luck, one that fails is the Utopic Type on Cloud-Archive Liberty to Xenial. * The further one migrates that old guest the more breakage this accumulates. E.g. a Trusty guest (qemu 2.0) migrated to Xenial (thinks it is qemu 2.5 type) and from there migrating to Yakkety (which expects it to be a 2.6 type). * The fix is minimal and makes the types definition stable across releases as they were intended [Test Case] * Spawn a Guest of Type Utopic (the easiest still supported is Trusty + Cloud Archive Liberty). And then migrate it to Xenial. Without the patch migration fail, with the patches it works as both now agree what the guest definition means. Please do note that both ends of the migrations have to be fixed to get it working. * Similar a Guest of type Trusty can with the fixes applied be migrated X->Y->Z and back to X, while without the fix any backward way (and probably a future forward way) will fail. * Note: This is complex and there are many potential combinations - the testlogs (comment #15) attached have various permutations of those. It has shown that not only the Utopic type issue that was reported gets fixed, but several backward migrations as well. [Regression Potential] * While it fixes the cases that we know, and as testing showed also several cases that we didn't know before there are two things we can not avoid. 1. People have to restart the source guests so that the new fixed definition will take effect. But Trusty guests that were already migrated to a Host that has the error will have to be restarted before they can be migrated further. Note: no one has to restart guests on Trusty without Cloud Archive; there the Trusty type is ok - it is a 2.0 which after the fix Xenial/Yakkety agree. 2. Restarting the guests after the fix will "downgrade" the virtual hardware. One can think of the machine types as the HW-revision of the virtual HW. A Guest that was created as e.g. Trusty these days on Xenial as incorrectly "too new" virtual HW, restarting the guest will fix that - but as part of that new attributes that it incorrectly gained when migrating/moving to the new host will be taken away (to match the definition the guest had when it was started) This is actually a fix, but might appear as a regression to somebody without knowing what was going on. Also anybody that "wants" the new HW can just upgrade the machine type to get it, which is actually recommended anyway [1]. [Other Info] * This is a complex issue, please catch me (cpaelzer) on IRC if you need/want to go into detail. Or for Cloud Archive questions coreycb. [1]: https://wiki.ubuntu.com/QemuKVMMigration#Upgrade_machine_type --- original description --- Hi, I'm currently live-migrating many VMs from an old server to a new one, and some VM can't be live migrated. The source host is trusty with qemu-system-x86 1:2.3+dfsg-5ubuntu9.4~cloud2 The destination host is xenial with qemu-system-x86 1:2.5+dfsg-5ubuntu10.6 When the issue occurs, the destination host raises an error [1] and stop the migration process. The only difference I see between VMs where live migration works and those were it doesn't work is a different machine type. * migration works when VM have been created with pc-i440fx-vivid * migration doesn't work when VM have been created with pc-i440fx-utopic [1] the qemu error report by
[Group.of.nepali.translators] [Bug 1662491] Re: gce-compute-image-packages dropped udev rules that were present in gce-utils
This bug was fixed in the package gce-compute-image-packages - 20160930-0ubuntu5~16.04.0 --- gce-compute-image-packages (20160930-0ubuntu5~16.04.0) xenial; urgency=medium * Backport to xenial. gce-compute-image-packages (20160930-0ubuntu5) zesty; urgency=medium * Install upstream-provided rsyslog configuration so that daemons can log to the serial console. (LP: #1664949) gce-compute-image-packages (20160930-0ubuntu4) zesty; urgency=medium * Reintroduce udev rules that configure GCE-specific behaviour. (LP: #1662491) gce-compute-image-packages (20160930-0ubuntu3~16.04.1) xenial; urgency=medium * Reintroduce udev rules that configure GCE-specific behaviour. (LP: #1662491) -- Daniel Watkins Wed, 15 Feb 2017 13:07:36 + ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1662491 Title: gce-compute-image-packages dropped udev rules that were present in gce-utils Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: New Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] The impact is two-fold: (a) The udev rules were tuning the performance for GCE's specific environment, so users are seeing a substantial performance hit in some cases. (b) Google's users expect to be able to configure the Google daemons to log their output to the console, which is no longer possible. [Test Case] (a) /sys/block/sda/queue/scheduler should show noop as the selected scheduler. (b) Adding https://github.com/GoogleCloudPlatform/compute-image-packages/blob/master/google_config/rsyslog/90-google.conf to /etc/rsyslog.d and rebooting should cause logging from GCE's daemons to show up in the serial console. An example line: Feb 15 11:17:03 zesty-170215-1113 startup-script: INFO Starting startup scripts. [Regression Potential] There is limited regression potential, as the rules have been recommended for use by GCE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1662491/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1664949] Re: Daemons do not log output to serial console
This bug was fixed in the package gce-compute-image-packages - 20160930-0ubuntu5~16.04.0 --- gce-compute-image-packages (20160930-0ubuntu5~16.04.0) xenial; urgency=medium * Backport to xenial. gce-compute-image-packages (20160930-0ubuntu5) zesty; urgency=medium * Install upstream-provided rsyslog configuration so that daemons can log to the serial console. (LP: #1664949) gce-compute-image-packages (20160930-0ubuntu4) zesty; urgency=medium * Reintroduce udev rules that configure GCE-specific behaviour. (LP: #1662491) gce-compute-image-packages (20160930-0ubuntu3~16.04.1) xenial; urgency=medium * Reintroduce udev rules that configure GCE-specific behaviour. (LP: #1662491) -- Daniel Watkins Wed, 15 Feb 2017 13:07:36 + ** Changed in: gce-compute-image-packages (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1664949 Title: Daemons do not log output to serial console Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] When attempting to debug startup issues, the serial console in the GCE web console is a useful tool. With gce-utils, the GCE daemons logged to the serial console, but that change has been dropped for gce- compute-image-packages. [Test Case] Launch an instance and observe Google daemon logging in the serial console. For example: Feb 15 11:17:03 zesty-170215-1113 startup-script: INFO Starting startup scripts. [Regression Potential] Minimal; we are only adding a rsyslog rule to redirect the daemon output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1664949/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1662491] Re: gce-compute-image-packages dropped udev rules that were present in gce-utils
This bug was fixed in the package gce-compute-image-packages - 20160930-0ubuntu5~16.10.0 --- gce-compute-image-packages (20160930-0ubuntu5~16.10.0) yakkety; urgency=medium * Backport to yakkety. gce-compute-image-packages (20160930-0ubuntu5) zesty; urgency=medium * Install upstream-provided rsyslog configuration so that daemons can log to the serial console. (LP: #1664949) gce-compute-image-packages (20160930-0ubuntu4) zesty; urgency=medium * Reintroduce udev rules that configure GCE-specific behaviour. (LP: #1662491) -- Daniel Watkins Wed, 15 Feb 2017 12:59:02 + ** Changed in: gce-compute-image-packages (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1662491 Title: gce-compute-image-packages dropped udev rules that were present in gce-utils Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: New Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] The impact is two-fold: (a) The udev rules were tuning the performance for GCE's specific environment, so users are seeing a substantial performance hit in some cases. (b) Google's users expect to be able to configure the Google daemons to log their output to the console, which is no longer possible. [Test Case] (a) /sys/block/sda/queue/scheduler should show noop as the selected scheduler. (b) Adding https://github.com/GoogleCloudPlatform/compute-image-packages/blob/master/google_config/rsyslog/90-google.conf to /etc/rsyslog.d and rebooting should cause logging from GCE's daemons to show up in the serial console. An example line: Feb 15 11:17:03 zesty-170215-1113 startup-script: INFO Starting startup scripts. [Regression Potential] There is limited regression potential, as the rules have been recommended for use by GCE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1662491/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1664949] Re: Daemons do not log output to serial console
This bug was fixed in the package gce-compute-image-packages - 20160930-0ubuntu5~16.10.0 --- gce-compute-image-packages (20160930-0ubuntu5~16.10.0) yakkety; urgency=medium * Backport to yakkety. gce-compute-image-packages (20160930-0ubuntu5) zesty; urgency=medium * Install upstream-provided rsyslog configuration so that daemons can log to the serial console. (LP: #1664949) gce-compute-image-packages (20160930-0ubuntu4) zesty; urgency=medium * Reintroduce udev rules that configure GCE-specific behaviour. (LP: #1662491) -- Daniel Watkins Wed, 15 Feb 2017 12:59:02 + ** Changed in: gce-compute-image-packages (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1664949 Title: Daemons do not log output to serial console Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Yakkety: Fix Released Status in gce-compute-image-packages source package in Zesty: Fix Released Bug description: [Impact] When attempting to debug startup issues, the serial console in the GCE web console is a useful tool. With gce-utils, the GCE daemons logged to the serial console, but that change has been dropped for gce- compute-image-packages. [Test Case] Launch an instance and observe Google daemon logging in the serial console. For example: Feb 15 11:17:03 zesty-170215-1113 startup-script: INFO Starting startup scripts. [Regression Potential] Minimal; we are only adding a rsyslog rule to redirect the daemon output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1664949/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 823254] Re: Port to python3
Am I correct in assuming that this has been dropped and won't be ported? (.. bit confused given how it still appears kylin software center seems to be related to software center) ** Changed in: software-center (Ubuntu) Status: Confirmed => Incomplete ** Changed in: software-center (Ubuntu Xenial) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/823254 Title: Port to python3 Status in software-center package in Ubuntu: Incomplete Status in software-center source package in Quantal: Won't Fix Status in software-center source package in Xenial: Won't Fix Bug description: This is a meta bug that tracks what needs to be done to get a python3 version of software-center ready: The following package need to have python3 packages: pygobject: bug #802486 (done) aptdaemon: bug #823216 (done) python-xdg: bug #823150 (done) python-defer: bug #823220 (done) xapian: bug #823227 (upstream is working on this, needs help testing) piston-mini-client: bug #823229 (done) python-oauth: bug #823252 (done, Upstream is dead, please replace with python-oauthlib) Both python3-oauth and python3-oauthlib now exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/823254/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589580] Re: Security improvements to TEXT coder broke it
This bug was fixed in the package imagemagick - 8:6.7.7.10-6ubuntu3.4 --- imagemagick (8:6.7.7.10-6ubuntu3.4) trusty-security; urgency=medium * SECURITY REGRESSION: test label regression (LP: #1646485) - debian/patches/0161-Do-not-ignore-SetImageBias-bias-value.patch: updated to fix bad backport. - debian/patches/0162-Suspend-exception-processing-if-there-are-too-many-e.patch: updated to apply cleanly. * SECURITY REGRESSION: text coder issue (LP: #1589580) - debian/patches/fix_text_coder.patch: add extra check to coders/mvg.c, fix logic in coders/txt.c. -- Marc Deslauriers Wed, 22 Feb 2017 10:04:25 -0500 ** Changed in: imagemagick (Ubuntu Trusty) Status: Confirmed => Fix Released ** Changed in: imagemagick (Ubuntu Precise) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589580 Title: Security improvements to TEXT coder broke it Status in imagemagick package in Ubuntu: Fix Committed Status in imagemagick source package in Precise: Fix Released Status in imagemagick source package in Trusty: Fix Released Status in imagemagick source package in Xenial: Fix Released Status in imagemagick source package in Yakkety: Fix Released Bug description: In ubuntu 16.04 (xenial): $ convert test.txt test.pdf convert: improper image header `test.txt' @ error/txt.c/ReadTXTImage/433. convert: no images defined `test.pdf' @ error/convert.c/ConvertImageCommand/3210. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy imagemagick imagemagick: Installed: 8:6.8.9.9-7ubuntu5.1 Candidate: 8:6.8.9.9-7ubuntu5.1 Version table: *** 8:6.8.9.9-7ubuntu5.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 8:6.8.9.9-7ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1589580/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1589580] Re: Security improvements to TEXT coder broke it
This bug was fixed in the package imagemagick - 8:6.8.9.9-7ubuntu8.3 --- imagemagick (8:6.8.9.9-7ubuntu8.3) yakkety-security; urgency=medium * SECURITY REGRESSION: text coder issue (LP: #1589580) - debian/patches/fix_text_coder.patch: add extra check to coders/mvg.c, fix logic in coders/txt.c. -- Marc Deslauriers Wed, 22 Feb 2017 11:10:55 -0500 ** Changed in: imagemagick (Ubuntu Yakkety) Status: Confirmed => Fix Released ** Changed in: imagemagick (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1589580 Title: Security improvements to TEXT coder broke it Status in imagemagick package in Ubuntu: Confirmed Status in imagemagick source package in Precise: Fix Released Status in imagemagick source package in Trusty: Fix Released Status in imagemagick source package in Xenial: Fix Released Status in imagemagick source package in Yakkety: Fix Released Bug description: In ubuntu 16.04 (xenial): $ convert test.txt test.pdf convert: improper image header `test.txt' @ error/txt.c/ReadTXTImage/433. convert: no images defined `test.pdf' @ error/convert.c/ConvertImageCommand/3210. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy imagemagick imagemagick: Installed: 8:6.8.9.9-7ubuntu5.1 Candidate: 8:6.8.9.9-7ubuntu5.1 Version table: *** 8:6.8.9.9-7ubuntu5.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 8:6.8.9.9-7ubuntu5 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1589580/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1667007] Re: [Hyper-V] Mellanox VF driver does not support >16 vCPUs
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Tags added: kernel-da-key kernel-hyper-v xenial -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1667007 Title: [Hyper-V] Mellanox VF driver does not support >16 vCPUs Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: In the course of enabling SR-IOV on Azure, discovered that the Mellanox Driver with 16 or more vCPUs fails. Mellanox has submitted the following patch upstream to correct this problem. Prerequisite: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650058 I will post the upstream commit once it lands. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667007/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1667056] [NEW] linux-raspi2: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1667052 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-trusty block-proposed-vivid block-proposed-xenial kernel-release-tracking-bug kernel-sru-cycle-2017.02.22-1 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Tags added: block-proposed-vivid ** Tags added: block-proposed-xenial ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workfl
[Group.of.nepali.translators] [Bug 1667058] [NEW] linux-snapdragon: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1667052 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-snapdragon (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-trusty block-proposed-vivid block-proposed-xenial kernel-release-tracking-bug kernel-sru-cycle-2017.02.22-1 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Tags added: block-proposed-vivid ** Tags added: block-proposed-xenial ** Also affects: linux-snapdragon (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: k
[Group.of.nepali.translators] [Bug 1667061] [NEW] linux-aws: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1667052 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-aws (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-trusty block-proposed-vivid block-proposed-xenial kernel-release-tracking-bug kernel-sru-cycle-2017.02.22-1 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Tags added: block-proposed-vivid ** Tags added: block-proposed-xenial ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-t
[Group.of.nepali.translators] [Bug 1667052] [NEW] linux: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Status: Invalid ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-precise block-proposed-trusty block-proposed-vivid block-proposed-xenial kernel-release-tracking-bug kernel-sru-cycle-2017.02.22-1 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-precise ** Tags added: block-proposed-trusty ** Tags added: block-proposed-vivid ** Tags added: block-proposed-xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Impo
[Group.of.nepali.translators] [Bug 1667054] [NEW] linux-lts-xenial: -proposed tracker
Public bug reported: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1667052 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-lts-xenial (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: block-proposed-trusty block-proposed-vivid block-proposed-xenial kernel-release-tracking-bug kernel-sru-cycle-2017.02.22-1 xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed-trusty ** Tags added: block-proposed-vivid ** Tags added: block-proposed-xenial ** Also affects: linux-lts-xenial (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Changed in: linux-lts-xenial (Ubuntu Xenial) Status: New => Confirmed ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-security Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-security Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) ** Changed in: kernel-sru-workflow/promote-to-updates
[Group.of.nepali.translators] [Bug 1666986] Re: package does not include dpkg version
** Changed in: curtin (Ubuntu) Importance: Undecided => Medium ** Changed in: curtin (Ubuntu) Status: New => Confirmed ** Also affects: curtin (Ubuntu Zesty) Importance: Medium Status: Confirmed ** Also affects: curtin (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Xenial) Status: New => Confirmed ** Changed in: curtin (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: curtin (Ubuntu Zesty) Status: Confirmed => Fix Released ** Changed in: curtin (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: curtin (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1666986 Title: package does not include dpkg version Status in curtin package in Ubuntu: Fix Released Status in curtin source package in Xenial: Confirmed Status in curtin source package in Yakkety: Confirmed Status in curtin source package in Zesty: Fix Released Bug description: Begin SRU Template [Impact] A feature was added to curtin upstream to allow the package build process to add its version to the curtin version reported. That version is exposed via: $ curtin version 0.1.0~bzr460-0ubuntu1 And then also $ python3 -c 'from curtin import version; print(version.version_string())' 0.1.0~bzr460-0ubuntu1 The above are shown in zesty. However, the SRU'd versions did not get the packaging change to write that information, so they show only 0.1.0 The fix is to make the change made in zesty's debian/rules. [Test Case] $ apt-get install curtin $ curtin version Expect to see the packaged version reported, with bzr460 in it. [Regression Potential] Low chance of regression, as 'curtin version' and the python library function version_string was only recently added for this feature, so nothing would depend on the broken behavior. End SRU Template in trunk revno 448, we added patching of a file in curtin via debian/rules so that the packaged version would report its version correctly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: curtin 0.1.0~bzr460-0ubuntu1~16.10.1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Feb 22 16:20:42 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: curtin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1666986/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1601954] Re: ensure all items are included in changelog and standardise packaging
This bug was fixed in the package linux-meta-snapdragon - 4.4.0.1047.39 --- linux-meta-snapdragon (4.4.0.1047.39) xenial; urgency=medium * Bump ABI 4.4.0-1047 * ensure all items are included in changelog and standardise packaging (LP: #1601954) - simplify meta package packaging - add git-ubuntu-log for changelog formatting - add update-version to simplify updates -- Thadeu Lima de Souza Cascardo Wed, 01 Feb 2017 11:37:11 -0200 ** Changed in: linux-meta-snapdragon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1601954 Title: ensure all items are included in changelog and standardise packaging Status in linux-meta package in Ubuntu: Fix Released Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-lts-trusty package in Ubuntu: New Status in linux-meta-lts-xenial package in Ubuntu: New Status in linux-meta-raspi2 package in Ubuntu: New Status in linux-meta-snapdragon package in Ubuntu: Fix Released Status in linux-signed package in Ubuntu: Fix Released Status in linux-meta source package in Precise: Fix Released Status in linux-meta-aws source package in Precise: Invalid Status in linux-meta-lts-trusty source package in Precise: Fix Released Status in linux-meta-lts-xenial source package in Precise: Invalid Status in linux-meta-raspi2 source package in Precise: New Status in linux-meta-snapdragon source package in Precise: New Status in linux-signed source package in Precise: New Status in linux-meta source package in Trusty: Fix Released Status in linux-meta-aws source package in Trusty: Invalid Status in linux-meta-lts-trusty source package in Trusty: Invalid Status in linux-meta-lts-xenial source package in Trusty: Fix Released Status in linux-meta-raspi2 source package in Trusty: New Status in linux-meta-snapdragon source package in Trusty: New Status in linux-signed source package in Trusty: New Status in linux-meta source package in Xenial: Fix Released Status in linux-meta-aws source package in Xenial: Fix Released Status in linux-meta-lts-trusty source package in Xenial: Invalid Status in linux-meta-lts-xenial source package in Xenial: Invalid Status in linux-meta-raspi2 source package in Xenial: Fix Committed Status in linux-meta-snapdragon source package in Xenial: Fix Released Status in linux-signed source package in Xenial: New Bug description: simplify packaging and ensure all items are included in changelog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1601954/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1540461] Re: Recurring events not displayed
This bug was fixed in the package evolution-ews - 3.22.3-0ubuntu1 --- evolution-ews (3.22.3-0ubuntu1) yakkety-proposed; urgency=medium * New upstream release (LP: #1663863) - This fixes recurring events not display with Exchange 2016 (LP: #1540461) * Bump minimum evolution and evolution-data-server versions to 3.22.3 -- Bryan Quigley Thu, 09 Feb 2017 12:19:36 -0500 ** Changed in: evolution-ews (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1540461 Title: Recurring events not displayed Status in evolution-ews: Unknown Status in evolution-ews package in Ubuntu: Fix Released Status in evolution-ews source package in Xenial: Fix Released Status in evolution-ews source package in Yakkety: Fix Released Bug description: [Impact] * The EWS plugin doesn't display recurring/repeated events in the calender. Only single time events are displayed. Outlook Online displays all the events correctly. The EWS plugin doesn't seem to thrown any errors, so people using it may not notice some events are missing. This actually is a bug on the server side, that the evolution developers have worked around. [Test Case] * You need a EWS server, the best instructions are from https://social.technet.microsoft.com/Forums/office/en- US/9952d9ea-6040-46b8-93d7-f163c09acd70/bug-in-ews-invalid-ical- format-if-recurrent-event-modified?forum=exchangesvrdevelopment Basically: 1. Create a recurring event with no end date. E.g. every Monday at 10am on OWA/Outlook Online (I used as start date 29th of August 2016) 2. Query the calendar item through EWS and check the MimeContent field. It's OK, it contains a END:VCALENDAR 3. Change a single instance by moving it to Tuesday 10am (in OWA), I moved the one from 19th September to 20st September 2016 4. Now query the recurrent calendar item again and voilà: the "END:VCALENDAR" is now missing [Regression Potential] * EWS plugin breaks in other ways. [Other Info] * This is fixed in Zesty. * No testers have come forward about 14.04 and the code has diverged a bit since then. (I don't have a test environment for this, so any fix would rely on other testers) Versions: Ubuntu Gnome: 15.10 evolution-ews: 3.18.0-3~wily1 MS Exchange Server: 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1540461/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1540461] Re: Recurring events not displayed
This bug was fixed in the package evolution-ews - 3.18.5-1ubuntu1 --- evolution-ews (3.18.5-1ubuntu1) xenial-proposed; urgency=medium * Fix recurring events not displayed with Exchange 2016 (LP: #1540461) -- Bryan Quigley Thu, 02 Feb 2017 11:25:57 -0500 ** Changed in: evolution-ews (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1540461 Title: Recurring events not displayed Status in evolution-ews: Unknown Status in evolution-ews package in Ubuntu: Fix Released Status in evolution-ews source package in Xenial: Fix Released Status in evolution-ews source package in Yakkety: Fix Released Bug description: [Impact] * The EWS plugin doesn't display recurring/repeated events in the calender. Only single time events are displayed. Outlook Online displays all the events correctly. The EWS plugin doesn't seem to thrown any errors, so people using it may not notice some events are missing. This actually is a bug on the server side, that the evolution developers have worked around. [Test Case] * You need a EWS server, the best instructions are from https://social.technet.microsoft.com/Forums/office/en- US/9952d9ea-6040-46b8-93d7-f163c09acd70/bug-in-ews-invalid-ical- format-if-recurrent-event-modified?forum=exchangesvrdevelopment Basically: 1. Create a recurring event with no end date. E.g. every Monday at 10am on OWA/Outlook Online (I used as start date 29th of August 2016) 2. Query the calendar item through EWS and check the MimeContent field. It's OK, it contains a END:VCALENDAR 3. Change a single instance by moving it to Tuesday 10am (in OWA), I moved the one from 19th September to 20st September 2016 4. Now query the recurrent calendar item again and voilà: the "END:VCALENDAR" is now missing [Regression Potential] * EWS plugin breaks in other ways. [Other Info] * This is fixed in Zesty. * No testers have come forward about 14.04 and the code has diverged a bit since then. (I don't have a test environment for this, so any fix would rely on other testers) Versions: Ubuntu Gnome: 15.10 evolution-ews: 3.18.0-3~wily1 MS Exchange Server: 2016 To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1540461/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1639896] Re: Backport support for AMD Polaris
This bug was fixed in the package xserver-xorg-video-amdgpu - 1.1.2-0ubuntu0.16.04.1 --- xserver-xorg-video-amdgpu (1.1.2-0ubuntu0.16.04.1) xenial; urgency=medium * Backport to xenial. - bugfix release - further support for Polaris (LP: #1639896) xserver-xorg-video-amdgpu (1.1.2-1) unstable; urgency=medium * New upstream release. - fix-configdir.diff: Dropped, fixed upstream [ Julien Cristau ] * Use https URL in debian/watch. xserver-xorg-video-amdgpu (1.1.1-1) unstable; urgency=medium * New upstream release. * fix-configdir.diff: Fix installing the config snippet. -- Timo Aaltonen Mon, 07 Nov 2016 20:40:47 +0200 ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Released Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1658289] Re: Regression in pdo_pgsql after SRU to php 7.0.13 (fixed upstream)
This bug was fixed in the package php7.0 - 7.0.15-0ubuntu0.16.04.1 --- php7.0 (7.0.15-0ubuntu0.16.04.1) xenial; urgency=medium * New upstream release - LP: #1663405 - Refresh patches for new upstream release. * debian/patches/0050-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester . Closes LP: #1658289. -- Nishanth Aravamudan Tue, 14 Feb 2017 14:53:34 -0800 ** Changed in: php7.0 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1658289 Title: Regression in pdo_pgsql after SRU to php 7.0.13 (fixed upstream) Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Fix Released Status in php7.0 source package in Yakkety: Fix Released Bug description: [Impact] * Running PDO::lastInsertId() using a bad sequence name (not updated or nonexistent) no longer throws an exception. * This is a functional regression in upstream PHP between 7.0.8 and 7.0.13, which was previously SRU'd to xenial and yakkety. [Test Case] * https://github.com/php/php- src/blob/master/ext/pdo_pgsql/tests/bug73959.phpt which was added in the upstream commit that fixed the issue. * I have backported the test-case along with the SRU'd versions, and the test suite is run at build and autopkgtest time. [Regression Potential] * This is an upstream bugfix with a small and contained solution, I believe the regression potential is minimal; in fact, we regressed in the prior SRU, so this returns lost functionality. -- After upgrading php7.0 to 7.0.13-0ubuntu0.16.04.1 from xenial-updates, we had a couple of failed tests in our internal test suite. I reported php bug #73959, which was then fixed in commit 21ac79e94bd0335bf885b807e09c4d86d75d776a. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1658289/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1663405] Re: [SRU] microrelease exception for src:php7.0 (7.0.15)
This bug was fixed in the package php7.0 - 7.0.15-0ubuntu0.16.04.1 --- php7.0 (7.0.15-0ubuntu0.16.04.1) xenial; urgency=medium * New upstream release - LP: #1663405 - Refresh patches for new upstream release. * debian/patches/0050-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester . Closes LP: #1658289. -- Nishanth Aravamudan Tue, 14 Feb 2017 14:53:34 -0800 ** Changed in: php7.0 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1663405 Title: [SRU] microrelease exception for src:php7.0 (7.0.15) Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Fix Released Status in php7.0 source package in Yakkety: Fix Released Bug description: There have been a number of microreleases of PHP 7.0 upstream since the last update to Xenial (which corresponded to the merge in Yakkety). Ase we have re-merged again in Zesty, it feels appropriate to provide another MRE update to php7.0. A number of critical security and bug-fixes are present in each 7.0.x. Rather than backporting individual patches (e.g., Bug # 1569509), I believe it makes significantly more sense to follow the upstream 7.0.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.0.x: - 7.0.15: http://php.net/ChangeLog-7.php The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly. Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packing to run the source tests during the build itself. I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.1.0. Additionally for this SRU, there is (at least) one bug fixed upstream that was specifically introduce by the prior SRU (to 7.0.13) which will be fixed by updating to a newer upstream version: LP: #1658289. I have also discussed this on IRC with the security team for coordinating the next security update of php7.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1663405/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1658289] Re: Regression in pdo_pgsql after SRU to php 7.0.13 (fixed upstream)
This bug was fixed in the package php7.0 - 7.0.15-0ubuntu0.16.10.1 --- php7.0 (7.0.15-0ubuntu0.16.10.1) yakkety; urgency=medium * New upstream release - LP: #1663405 - Refresh patches for new upstream release. * debian/patches/0048-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester . Closes LP: #1658289. -- Nishanth Aravamudan Tue, 14 Feb 2017 14:44:43 -0800 ** Changed in: php7.0 (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1658289 Title: Regression in pdo_pgsql after SRU to php 7.0.13 (fixed upstream) Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Fix Committed Status in php7.0 source package in Yakkety: Fix Released Bug description: [Impact] * Running PDO::lastInsertId() using a bad sequence name (not updated or nonexistent) no longer throws an exception. * This is a functional regression in upstream PHP between 7.0.8 and 7.0.13, which was previously SRU'd to xenial and yakkety. [Test Case] * https://github.com/php/php- src/blob/master/ext/pdo_pgsql/tests/bug73959.phpt which was added in the upstream commit that fixed the issue. * I have backported the test-case along with the SRU'd versions, and the test suite is run at build and autopkgtest time. [Regression Potential] * This is an upstream bugfix with a small and contained solution, I believe the regression potential is minimal; in fact, we regressed in the prior SRU, so this returns lost functionality. -- After upgrading php7.0 to 7.0.13-0ubuntu0.16.04.1 from xenial-updates, we had a couple of failed tests in our internal test suite. I reported php bug #73959, which was then fixed in commit 21ac79e94bd0335bf885b807e09c4d86d75d776a. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1658289/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1663405] Re: [SRU] microrelease exception for src:php7.0 (7.0.15)
This bug was fixed in the package php7.0 - 7.0.15-0ubuntu0.16.10.1 --- php7.0 (7.0.15-0ubuntu0.16.10.1) yakkety; urgency=medium * New upstream release - LP: #1663405 - Refresh patches for new upstream release. * debian/patches/0048-Fix-pdo_pgsql.patch: Fixed #73959 - lastInsertId fails to throw an exception in pdsql. Thanks to andrewnester . Closes LP: #1658289. -- Nishanth Aravamudan Tue, 14 Feb 2017 14:44:43 -0800 ** Changed in: php7.0 (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1663405 Title: [SRU] microrelease exception for src:php7.0 (7.0.15) Status in php7.0 package in Ubuntu: Fix Released Status in php7.0 source package in Xenial: Fix Committed Status in php7.0 source package in Yakkety: Fix Released Bug description: There have been a number of microreleases of PHP 7.0 upstream since the last update to Xenial (which corresponded to the merge in Yakkety). Ase we have re-merged again in Zesty, it feels appropriate to provide another MRE update to php7.0. A number of critical security and bug-fixes are present in each 7.0.x. Rather than backporting individual patches (e.g., Bug # 1569509), I believe it makes significantly more sense to follow the upstream 7.0.x. Upstream PHP is demonstrating an improved approach of bugfixes only in 7.0.x: - 7.0.15: http://php.net/ChangeLog-7.php The upstream CI is at: https://travis-ci.org/php/php-src and is run regularly. Our php7.0 source package has autopkgtests for the 4 SAPIs, mod-php, cgi, fpm and cli. We have also updated the packing to run the source tests during the build itself. I do not believe there is a firm statement from upstream on API/ABI stability, but the general approach seems to be a BC-break would result in 7.1.0. Additionally for this SRU, there is (at least) one bug fixed upstream that was specifically introduce by the prior SRU (to 7.0.13) which will be fixed by updating to a newer upstream version: LP: #1658289. I have also discussed this on IRC with the security team for coordinating the next security update of php7.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1663405/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1666413] Re: linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge
Good catch. I'm marking this invalid, ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1666413 Title: linux-image-hwe-16.04 depends on linux-generic-hwe-16.04-edge Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: Installing the linux-generic-hwe-16.04 package pulls in linux-generic- hwe-16.04-edge, thus the system has linux-image-4.8.0-34-generic and linux-image-4.8.0-36-generic installed. The system then boots to 4.8.0-36. Installing linux-generic-hwe-16.04 shouldn't pull in linux-generic- hwe-16.04-edge and only one kernel should be installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666413/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1656399] Re: Returning to existing session is unreliable and can leave on blank screen
This bug was fixed in the package lightdm - 1.21.5-0ubuntu1 --- lightdm (1.21.5-0ubuntu1) zesty; urgency=medium * New upstream release: - Fix logic that checked if a session was being stopped. This fixes a race condition that could cause logging into an existing session from a greeter to not return to that session. (LP: #1656399) -- Robert Ancell Wed, 22 Feb 2017 12:38:50 +1300 ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1656399 Title: Returning to existing session is unreliable and can leave on blank screen Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in Light Display Manager 1.20 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: [Impact] Due to a logic bug LightDM returning to an existing session from a greeter can be unreliable. This case is common in systems which use the greeter as a lock screen. The bug was introduced in revision 1954 to fix bug 1296276. The race condition seems to have been made more likely to the change in revision 2437 to fix bug 1637758. [Test Case] 1. Log into a session 2. Switch to the greeter (e.g. dm-tool switch-to-greeter) 3. Log in again Expected result Returned to existing session Observed result Not always returned, can end up on blank screen. Since this is a race condition this may not occur on some systems. [Regression Potential] Low, the fix is to correct a logic bug that made LightDM think it hadn't stopped a session correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1656399/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1666827] Re: Backport fixes for Rename Network return 403 Error
** Also affects: horizon (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: horizon (Ubuntu Yakkety) Status: New => Fix Released ** Changed in: horizon (Ubuntu Trusty) Status: New => Triaged ** Changed in: horizon (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1666827 Title: Backport fixes for Rename Network return 403 Error Status in Ubuntu Cloud Archive: New Status in OpenStack Dashboard (Horizon): New Status in horizon package in Ubuntu: New Status in horizon source package in Trusty: Triaged Status in horizon source package in Xenial: Triaged Status in horizon source package in Yakkety: Fix Released Bug description: [Impact] Non-admin users are not allowed to change the name of a network using the OpenStack Dashboard GUI [Test Case] 1. Deploy trusty-mitaka or xenial-mitaka OpenStack Cloud 2. Create demo project 3. Create demo user 4. Log into OpenStack Dashboard using demo user 5. Go to Project -> Network and create a network 6. Go to Project -> Network and Edit the just created network 7. Change the name and click Save 8. Observe that your request is denied with an error message [Regression Potential] Minimal. We are adding a patch already merged into upstream stable/mitaka for the horizon call to policy_check before sending request to Neutron when updating networks. The addition of rule "update_network:shared" to horizon's copy of Neutron policy.json is our own due to upstream not willing to back- port this required change. This rule is not referenced anywhere else in the code base so it will not affect other policy_check calls. Upstream bug: https://bugs.launchpad.net/horizon/+bug/1609467 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1666827/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
