[Group.of.nepali.translators] [Bug 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)
After providing more background, the Trusty package needs to be uploaded
to the security pockets to ensure our Ubuntu Pro users are able to get
this update. This is essential to Pro users getting updates from the new
esm-infra pockets.
** Changed in: unattended-upgrades (Ubuntu Trusty)
Status: Won't Fix => 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/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
In Progress
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Bionic:
Fix Committed
Status in unattended-upgrades source package in Eoan:
Fix Committed
Bug description:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1611987] Re: [SRU] glance-simplestreams-sync charm doesn't support keystone v3
** Changed in: simplestreams (Ubuntu Artful)
Status: Confirmed => Won't Fix
** Changed in: simplestreams (Ubuntu Xenial)
Assignee: (unassigned) => Joshua Powers (powersj)
** Changed in: simplestreams (Ubuntu Xenial)
Assignee: Joshua Powers (powersj) => Rafael David Tinoco (rafaeldtinoco)
--
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/1611987
Title:
[SRU] glance-simplestreams-sync charm doesn't support keystone v3
Status in OpenStack glance-simplestreams-sync charm:
Fix Released
Status in Glance - Simplestreams Sync Charm:
Invalid
Status in simplestreams:
Fix Released
Status in simplestreams package in Ubuntu:
Fix Released
Status in simplestreams source package in Xenial:
Confirmed
Status in simplestreams source package in Artful:
Won't Fix
Status in simplestreams source package in Bionic:
Fix Released
Status in glance-simplestreams-sync package in Juju Charms Collection:
Invalid
Bug description:
[Impact]
simplestreams can't sync images when keystone is configured to use v3,
keystone v2 is deprecated since mitaka[0] (the version shipped with
xenial)
The OpenStack Keystone charm supports v3 only since Queens and
later[1]
[Test Case]
* deploy a openstack environment with keystone v3 enabled
- get a copy of the bundle available at
http://paste.ubuntu.com/p/hkhsHKqt4h/ , this bundle deploys a minimal version
of xenial-mitaka.
Expected result:
- "glance image-list" lists trusty and xenial images
- the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log
contains details of the images pulled from cloud-images.u.c (example:
https://pastebin.ubuntu.com/p/RWG8QrkVDz/ )
Actual result:
- "glance image-list" is empty
- the file glance-simplestreams-sync/0:/var/log/glance-simplestreams-sync.log
contains the following stacktrace
INFO * 04-09 22:04:06 [PID:14571] * root * Calling DryRun mirror to get item
list
ERROR * 04-09 22:04:06 [PID:14571] * root * Exception during syncing:
Traceback (most recent call last):
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py",
line 471, in main
do_sync(charm_conf, status_exchange)
File "/usr/share/glance-simplestreams-sync/glance-simplestreams-sync.py",
line 232, in do_sync
objectstore=store)
File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py",
line 374, in __init__
super(ItemInfoDryRunMirror, self).__init__(config, objectstore)
File "/usr/lib/python2.7/dist-packages/simplestreams/mirrors/glance.py",
line 126, in __init__
self.keystone_creds = openstack.load_keystone_creds()
File "/usr/lib/python2.7/dist-packages/simplestreams/openstack.py", line
61, in load_keystone_creds
raise ValueError("(tenant_id or tenant_name)")
ValueError: (tenant_id or tenant_name)
[Regression Potential]
* A possible regression will manifest itself figuring out if v2 or v3
should be used, after the connection is made there are no further
changes introduced by this SRU
[Other Info]
I was deploying a Mitaka Trusty 16.04 charm based Openstack cloud
(using the cloud archives), including glance-simplestreams-sync, using
keystone v3.
Once I had everything deployed, the glance-simplestreams-sync service
couldn't authenticate because it's using keystone v2, not v3, as you
can see from the following:
INFO * 08-10 23:16:01 [PID:33554] * root * glance-simplestreams-sync
started.
DEBUG * 08-10 23:16:01 [PID:33554] * keystoneclient.session * REQ: curl
-i -X POST http://x.y.z.240:5000/v2.0/tokens -H "Content-Type:
application/json" -H "User-Agent: python-keystoneclient" -d '{"auth":
{"passwordCredentials": {"username": "image-stream", "password":
"thisisnotapassword"}, "tenantId": "blahblahtenantidblahblah"}}'
INFO * 08-10 23:16:01 [PID:33554] * urllib3.connectionpool * Starting
new HTTP connection (1): x.y.z.240
DEBUG * 08-10 23:16:01 [PID:33554] * urllib3.connectionpool * Setting
read timeout to None
DEBUG * 08-10 23:16:01 [PID:33554] * urllib3.connectionpool * "POST
/v2.0/tokens HTTP/1.1" 401 114
DEBUG * 08-10 23:16:01 [PID:33554] * keystoneclient.session * RESP: [401]
CaseInsensitiveDict({'content-length': '114', 'vary': 'X-Auth-Token', 'server':
'Apache/2.4.7 (Ubuntu)', 'date': 'Wed, 10 Aug 2016 23:16:01 GMT',
'www-authenticate': 'Keystone uri="http://x.y.z.240:5000";',
'x-openstack-request-id': 'req-f8aaf12d-01ea-46
[Group.of.nepali.translators] [Bug 1815051] Re: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries
Marking all fixed-released and unsubscribing field-critical. ** Changed in: cloud-init (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: cloud-init Status: Fix Committed => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: Confirmed => Fix Released ** Changed in: cloud-init (Ubuntu Cosmic) 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/1815051 Title: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Status in cloud-init source package in Bionic: Fix Released Status in cloud-init source package in Cosmic: Fix Released Bug description: The netplan configuration redeclares the nameservers anchor for every single section (vlans, bonds), and use the same id for similar entries (id001). In this specific case the network configuration in maas have a bond0 with two vlans, bond0.3502 and bond0.3503, and an untagged bond1 without vlans. The rendered 50-cloud-init.yaml looks like this: network: version: 2 ethernets: ... bonds: ... bond1: ... nameservers: &id001 <- anchor declaration here addresses: - 255.255.255.1 - 255.255.255.2 - 255.255.255.3 - 255.255.255.5 search: - customer.domain - maas ... bondM: ... nameservers: *id001 vlans: bond0.3502: ... nameservers: &id001 <- anchor redeclaration here addresses: - 255.255.255.1 - 255.255.255.2 - 255.255.255.3 - 255.255.255.5 search: - customer.domain - maas bond0.3503: ... nameservers: *id001 As the cloudinit renders an invalid yaml file, the netplan apply produces the following error: (due to the anchor redeclaration in the vlans section): Invalid YAML at /etc/netplan/50-cloud-init.yaml line 118 column 25: second occurence This render bug prevents us using the untagged bond and the bond with the vlans in the same configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1815051/+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 1816627] Re: test
** Changed in: cloud-init Status: New => Invalid ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Invalid ** Changed in: cloud-init (Ubuntu Disco) Status: New => 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/1816627 Title: test Status in cloud-init: Invalid Status in cloud-init package in Ubuntu: Invalid Status in cloud-init source package in Xenial: Invalid Status in cloud-init source package in Disco: Invalid Bug description: test To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1816627/+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 1724951] Re: Ntp schema definition permits empty ntp cloud-config, but code disallows
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
--
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/1724951
Title:
Ntp schema definition permits empty ntp cloud-config, but code
disallows
Status in cloud-init:
In Progress
Status in cloud-init package in Ubuntu:
New
Status in cloud-init source package in Xenial:
New
Status in cloud-init source package in Zesty:
New
Status in cloud-init source package in Artful:
New
Bug description:
http://pad.lv/1724951
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1724951
=== Begin SRU Template ===
[Impact]
Customers who provide the following cloud-config will get a Runtime error
#cloud-config
ntp:
The expected behavior, per docs, is that an empty ntp configuration will
result in
"4 pools will be used in the format {0-3}.{distro}.pool.ntp.org.".
[Test Case]
if [ ! -f './lxc-proposed-snapshot' ]; then
wget
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
chmod 755 lxc-proposed-snapshot;
fi
# 1. Provide a empty ntp configuration to cloud-init
cat > install-ntp.conf
[Group.of.nepali.translators] [Bug 1718681] Re: Package copyright file omits Apache 2 license
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => High
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: Confirmed => Invalid
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Zesty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Artful)
Status: New => Confirmed
--
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/1718681
Title:
Package copyright file omits Apache 2 license
Status in cloud-init:
Invalid
Status in cloud-init package in Ubuntu:
Confirmed
Status in cloud-init source package in Xenial:
Confirmed
Status in cloud-init source package in Zesty:
Confirmed
Status in cloud-init source package in Artful:
Confirmed
Bug description:
In the Ubuntu package source, packages/debian/copyright says the
License is either GPL-3 or Apache 2.0 and includes summaries of both
licenses with links to the full license texts.
debian/copyright says that the license is either GPL-3 or Apache 2.0,
but only includes the GPL-3 summary and link (together with the MIT
licence terms for cloudinit/boto_utils.py)
I believe the terms of the Apache licence and the terms the LICENSE
file require the inclusion of the Apache 2 summary and link in the
debian/copyright file.
cloud-init.tar is not relevant to this issue.
Seen on Azure
$ dpkg-query -W -f='${Version}' cloud-init
0.7.9-233-ge586fe35-0ubuntu1~16.04.1
$ cat /usr/share/doc/cloud-init/copyright
Format-Specification:
http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=135
Name: cloud-init
Maintainer: Scott Moser
Source: https://launchpad.net/cloud-init
This package was debianized by Soren Hansen on
Thu, 04 Sep 2008 12:49:15 +0200 as ec2-init. It was later renamed to
cloud-utils by Scott Moser
Upstream Author: Scott Moser
Soren Hansen
Chuck Short
Copyright: 2010, Canonical Ltd.
License: GPL-3 or Apache-2.0
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License version 3, as
published by the Free Software Foundation.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see
[Group.of.nepali.translators] [Bug 1177432] Re: [SRU] cloud-init archive template should match Ubuntu Server
** Changed in: cloud-init 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/1177432 Title: [SRU] cloud-init archive template should match Ubuntu Server Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Precise: Fix Released Status in cloud-init source package in Trusty: Fix Released Status in cloud-init source package in Vivid: Fix Released Status in cloud-init source package in Wily: Fix Released Status in cloud-init source package in Xenial: Fix Released Bug description: [SRU Justification] Ubuntu Cloud Images are inconsistent with desktop and bare-metal server installations since backports, restricted and multiverse are not enabled. This is effected via cloud-init that uses a template to select an in-cloud archive. [FIX] Make the cloud-init template match that of Ubuntu-server. [REGRESION] The potential for regression is low. However, all users will experience slower fetch times on apt-get updates especially on slower or high latency networks. [TEST] 1. Build image from -proposed 2. Boot up image 3. Confirm that "sudo apt-get update" pulls in backports, restricted and multiverse. Backports are currently not enabled in the cloud-init template. This is needed in order to get the backport kernels on cloud images. Related bugs: * bug 997371: Create command to add "multiverse" and "-backports" to apt sources * bug 1513529: cloud image built-in /etc/apt/sources.list needs updating To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1177432/+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 1664179] Re: Wrong POM dependency in javax.servlet.jsp:jsp-api:2.2
Marking yakkety as won't fix due to EOL status. ** Changed in: tomcat7 (Ubuntu Yakkety) Status: Fix Committed => 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/1664179 Title: Wrong POM dependency in javax.servlet.jsp:jsp-api:2.2 Status in tomcat7 package in Ubuntu: Invalid Status in tomcat7 source package in Trusty: Fix Released Status in tomcat7 source package in Xenial: Fix Committed Status in tomcat7 source package in Yakkety: Won't Fix Bug description: == Begin SRU Template == [Impact] * The Tomcat7 package specifies an incorrect version of the javax.servlet api. If users attempt to use the version specified, 2.2, it will fail trying to find that version as it does not exist at all. * Currently the version is auto filled in by @MAVEN.DEPLOY.VERSION@, which is used to fill in other fields as well. However, the API versions are not all the same and should not be specified like this. * The official servlet version for Tomcat 7, 3.0, was specified here: https://jcp.org/en/jsr/detail?id=315 [Test Case] An example to test Tomcat7 on Trusty. The same instructions can apply to other releases. Overview: Install tomcat7 and attempt to build the pom. It will fail as the built in library specifies a non-existent version of 2.2. * lxc launch ubuntu-daily:trusty trusty * lxc exec trusty bash * apt install tomcat7 maven-debian-helper libmaven-dependency-plugin-java libservlet3.0-java * wget https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1664179/+attachment/4818104/+files/pom.xml * mvn-debian -q generate-sources -X [Regression Potential] * Users currently experiencing this issue would be expecting a SRU fix to come from us. Working around it would require changing the /usr/share/maven-repo/javax/servlet/jsp/jsp-api/2.2/jsp-api-2.2.pom to use the 3.0 version. This fix does the same thing. * There is the slight, albeit incredibly low chance, that someone actually has scripted something to modify the package itself and swap out @MAVEN.DEPLOY.VERSION@ to the correct value. * The tomcat8 package has gone away from using @MAVEN.DEPLOY.VERSION@ in favor of specifying the exact version as well to avoid this type of mismatch. [Other Info] Hi, Ubuntu 16.04.1 LTS, libservlet3.0-java=7.0.68-1ubuntu0.1 In /usr/share/maven-repo/javax/servlet/jsp/jsp-api/2.2/jsp-api-2.2.pom file that belongs to libservlet3.0-java there is the following dependency: javax.servlet servlet-api 2.2 compile But there is no corresponding javax.servlet:servlet-api:2.2 in /usr/share/maven-repo. So if I try to build some Java library that depends on javax.servlet.jsp:jsp-api:2.2 with mvn-debian, I cannot do it due to wrong transitive dependency. I've attached a test pom.xml to reproduce the bug: ubuntu@build:~$ ls -la pom.xml -rw-rw-r-- 1 ubuntu ubuntu 1185 Feb 13 10:12 pom.xml ubuntu@build:~$ ubuntu@build:~$ mvn-debian -q generate-sources find: ‘/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar’: No such file or directory find: ‘/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar’: No such file or directory find: ‘/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar’: No such file or directory [ERROR] Failed to execute goal on project yyy: Could not resolve dependencies for project xxx:yyy:pom:debian: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact javax.servlet:servlet-api:jar:2.2 has not been downloaded from it before. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException ubuntu@build:~$ I believe that javax.servlet.jsp:jsp-api:2.2 should list javax.servlet :servlet-api:3.0 as dependency, not 2.2 == End SRU Template == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1664179/+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 1666570] Re: Post install script has error in RegEx
Marking yakkety as won't fix due to EOL status.
** Changed in: tomcat7 (Ubuntu Yakkety)
Status: Triaged => Won't Fix
** Changed in: tomcat7 (Ubuntu Yakkety)
Assignee: Joshua Powers (powersj) => (unassigned)
--
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/1666570
Title:
Post install script has error in RegEx
Status in tomcat7 package in Ubuntu:
Invalid
Status in tomcat8 package in Ubuntu:
Fix Released
Status in tomcat7 source package in Trusty:
Fix Released
Status in tomcat7 source package in Xenial:
Triaged
Status in tomcat8 source package in Xenial:
Fix Released
Status in tomcat7 source package in Yakkety:
Won't Fix
Status in tomcat8 source package in Yakkety:
Fix Released
Status in tomcat8 source package in Zesty:
Fix Released
Status in tomcat7 package in Debian:
New
Status in tomcat8 package in Debian:
Fix Released
Bug description:
== Begin SRU Template ==
[Impact]
* On upgrade of tomcat7 package, if a user has updated their JAVA_OPTS
variable to include a '%' an upgrade will fail. The sed command in the postinst
uses the '%' character to act as a delimiter, previous versions used '/'
however it was updated to '%' in hopes it was far less common.
* This SRU updates it to a character that should not be found in the
JAVA_ARGS value, namely '\001'.
* This is the same solution Debian and tomcat maintainers are now using for
Tomcat8.
[Test Case]
An example to test Tomcat7 on Trusty. The same instructions can apply
to Tomcat8 on the other releases.
Overview: Install the version from the current release. Modify
JAVA_OPTS and then install the version from proposed to validate it
upgrades successfully.
* lxc launch ubuntu-daily:trusty trusty
* lxc exec trusty bash
* apt install tomcat7
* Edit /etc/default/tomcat7, set JAVA_OPTS="-Djava.awt.headless=true
-XX:ErrorFile=/var/log/tomcat7/java_error%p.log -XX:+DisableExplicitGC
-XX:+UseG1GC"
* # Enable proposed
* apt update
* apt install tomcat7
* When asked, 'Keep the local version currently installed'
* With the fix, install will complete
* Without the fix, the error as described under "Other Info" will appear
[Regression Potential]
* Users currently experiencing this issue would be expecting a SRU fix to
come from us. Working around it would require changing their JAVA_OPTS
temporarily, accepting the maintainers version of the defaults script, or
modifying the package's postinst script directly.
* In either case the proposed fix will over write any changes an end user may
have made to the postinst, and all for correctly working expected behavior.
* There is the slight, albeit incredibly low chance, that someone actually
has the '\001' character in their JAVA_OPTS. In which, case the upgrade would
fail as this bug describes.
[Other Info]
* Using a new delimiter that is far less likely to be in someone's path.
This is not the first time the delimiter has changed, as it originally as '/'
which is obviously going to show up as soon as someone adds a path.
* Upstream change to tomcat8:
https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/patch/?id=7664221d66701e2c31a31fe3b4f22e8bea4158dc
* Error message on failure:
Setting up tomcat7 (7.0.52-1ubuntu0.10) ...
sed: -e expression #1, char 97: unknown option to `s'
dpkg: error processing package tomcat7 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
tomcat7
E: Sub-process /usr/bin/dpkg returned an error code (1)
== End SRU Template ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1666570/+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 1710808] Re: dovecot lmtp crash with sieve
Given zesty and newer has 2.2.27, marking invalid for development release, adding target for Xenial. ** Also affects: dovecot (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: dovecot (Ubuntu) Status: New => 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/1710808 Title: dovecot lmtp crash with sieve Status in dovecot package in Ubuntu: Invalid Status in dovecot source package in Xenial: New Bug description: dovecot 1:2.2.22-1ubuntu2.4 on xenial contains a bug described in this thread: https://dovecot.org/list/dovecot/2016-March/103654.html It seems to be fixed on Dovecot 2.2.23: https://www.dovecot.org/doc/NEWS v2.2.23 2016-03-30 Timo Sirainen .. - Fixed assert-crash related to istream-concat, which could have been triggered at least by a Sieve script. Is is possible to upgrade the package on xenial? Petri To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1710808/+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 1551747] Re: ubuntu-fan causes issues during network configuration
** Changed in: cloud-init Status: New => 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/1551747 Title: ubuntu-fan causes issues during network configuration Status in cloud-init: Invalid Status in Snappy: Confirmed Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Released Status in ubuntu-fan source package in Yakkety: Fix Released Bug description: it seems that ubuntu-fan is causing issues with network configuration. On 16.04 daily image: root@localhost:~# snappy list NameDate Version Developer canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-02-22 16.04.0-10.armhf canonical I see this when I'm activating a wifi card on a raspberry pi 2. root@localhost:~# ifdown wlan0 ifdown: interface wlan0 not configured root@localhost:~# ifup wlan0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/c4:e9:84:17:31:9b Sending on LPF/wlan0/c4:e9:84:17:31:9b Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e) DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e) DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 (xid=0x5ec9c081) DHCPOFFER of 192.168.0.170 from 192.168.0.251 DHCPACK of 192.168.0.170 from 192.168.0.251 RTNETLINK answers: File exists bound to 192.168.0.170 -- renewal in 17145 seconds. run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 Failed to bring up wlan0. === [Impact] Installing ubuntu-fan can trigger error messages when initialising with no fan configuration. [Test Case] As above. [Regression Potential] Low, suppresses errorneous error messages. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1551747/+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 1584431] Re: mongosniff crashes on start
Marking yakkety invalid as it is now EOL. Working to get xenial merge
unstuck.
** Changed in: mongodb (Ubuntu Yakkety)
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/1584431
Title:
mongosniff crashes on start
Status in mongodb package in Ubuntu:
Fix Released
Status in mongodb source package in Xenial:
In Progress
Status in mongodb source package in Yakkety:
Invalid
Bug description:
== Begin SRU Template ==
[Impact]
* mongosniff crashes when it receives messages with no namespace. The result
is that a user cannot even press only the enter key without the mongosniff
application crashing.
* mongosniff in Xenial and Yakkety is essentially broken currently because of
a check in the code that gets the message namespace, but if there is no
namespace it crashes.
[Test Case]
* lxc launch ubuntu-daily:xenial xenial
* lxc exec xenial bash
* apt install mongodb
* mongosniff --source NET lo
* # Open a 2nd terminal and run the following
* lxc exec xenial bash
* mongo
* # press enter a few times or type 'help'
* # Observe mongosniff abort, with a core dump, in the first window
[Regression Potential]
* Users currently experiencing this issue would be expecting a SRU fix to
come from us as the application is broken in a major way.
* The only work around it would would require rebuilding mongodb from source
with the fix to resolve the issue.
* The change was limited to the mongosniff source code only.
[Other Info]
Ubuntu:
* Xenial x64
Packages:
#user@localhost:~$ for i in `dpkg --get-selections|grep -v deinstall|grep
mongo|cut -f1`; do echo $i `sudo apt-cache show $i|sed -n -e 's/^.*Version:
1://p'`; done
* mongodb 2.6.10-0ubuntu1
* mongodb-clients 2.6.10-0ubuntu1
* mongodb-server 2.6.10-0ubuntu1
Steps to reproduce:
1. start service
2. start sniffer
3. start shell
4. crash sniffer
---
user@localhost:~$ sudo service mongodb start
user@localhost:~$ mongo
MongoDB shell version: 2.6.10
connecting to: test
(...)
user@localhost:~$ sudo mongosniff --source NET lo
sniffing... 27017
127.0.0.1:37522 -->> 127.0.0.1:27017 admin.$cmd 60 bytes id:0 0
query: { whatsmyuri: 1 } ntoreturn: 1 ntoskip: 0
2016-05-22T01:26:35.545-0400 Assertion failure messageShouldHaveNs()
src/mongo/db/dbmessage.cpp 82
2016-05-22T01:26:35.553-0400 0xea35a9 0xe397cf 0xe14772 0x86aca8 0x615c13
0x7f614d369ef6 0x7f614d36e9d1 0x7f614d3731fd 0x616a5a 0x5e57a9 0x7f614c71a830
0x614389
mongosniff(_ZN5mongo15printStackTraceERSo+0x39) [0xea35a9]
mongosniff(_ZN5mongo10logContextEPKc+0x21f) [0xe397cf]
mongosniff(_ZN5mongo12verifyFailedEPKcS1_j+0x142) [0xe14772]
mongosniff() [0x86aca8]
mongosniff(_Z10got_packetPhPK11pcap_pkthdrPKh+0x573) [0x615c13]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(+0x5ef6) [0x7f614d369ef6]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(+0xa9d1) [0x7f614d36e9d1]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(pcap_loop+0x5d) [0x7f614d3731fd]
mongosniff(_Z8toolMainiPPcS0_+0x69a) [0x616a5a]
mongosniff(main+0x9) [0x5e57a9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f614c71a830]
mongosniff(_start+0x29) [0x614389]
terminate called after throwing an instance of 'mongo::AssertionException'
what(): assertion src/mongo/db/dbmessage.cpp:82
Aborted (core dumped)
user@localhost:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1584431/+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 1357880] Re: /etc/logcheck/ignore.d.server/dhclient needs updated regex
** Changed in: logcheck (Ubuntu Yakkety)
Status: Triaged => 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/1357880
Title:
/etc/logcheck/ignore.d.server/dhclient needs updated regex
Status in logcheck package in Ubuntu:
Fix Released
Status in logcheck source package in Trusty:
Triaged
Status in logcheck source package in Xenial:
Triaged
Status in logcheck source package in Yakkety:
Won't Fix
Status in logcheck source package in Zesty:
Fix Released
Bug description:
The regex on line 12 in /etc/logcheck/ignore.d.server/dhclient needs
updating since it does not match the current output from dhclient
The current line (12) as included in version 1.3.16 of logcheck-database
looks like this:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhclient(-2.2.x)?: DHCP(REQUEST|RELEASE)
(of [.0-9]{7,15} )?on [[:alnum:].-]+ to [.0-9]{7,15} port 67$
The line should look something like this is order to match the current outpt
format of dhclient:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhclient(-2.2.x)?(\[[[:digit:]]+\])?:
DHCP(REQUEST|RELEASE) (of [.0-9]{7,15} )?on [[:alnum:].]+ to [.0-9]{7,15} por
t 67( \(xid=0x[0-9a-f]+\))?$
This has been observed on a fresh install of ubuntu server 14.04.1 (no
upgrades from previous versions).
Procedure to reproduce:
- Install system that has at least one interface running dhcpclient
- Wait for dhclient to request or renew it's ip lease
- Wait for logwatch to run and send out its notification
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logcheck-database 1.3.16
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
Date: Sun Aug 17 10:09:15 2014
Dependencies:
InstallationDate: Installed on 2014-08-14 (2 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.3)
PackageArchitecture: all
SourcePackage: logcheck
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.logcheck.cracking.d.kernel: [deleted]
modified.conffile..etc.logcheck.cracking.d.rlogind: [deleted]
modified.conffile..etc.logcheck.cracking.d.rsh: [deleted]
modified.conffile..etc.logcheck.cracking.d.smartd: [deleted]
modified.conffile..etc.logcheck.cracking.d.tftpd: [deleted]
modified.conffile..etc.logcheck.cracking.d.uucico: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.bind: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.cron: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.incron: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.logcheck: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.postfix: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.ppp: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.pureftp: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.qpopper: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.squid: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.ssh: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.stunnel: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.sysklogd: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.telnetd: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.tripwire: [deleted]
modified.conffile..etc.logcheck.ignore.d.paranoid.usb: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.acpid: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.amandad: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.amavisd.new: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.anacron: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.anon.proxy: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.apache: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.apcupsd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.arpwatch: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.asterisk: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.automount: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.bind: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.bluez.utils: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.courier: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cpqarrayd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cpufreqd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cron: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cron.apt: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cups.lpd: [deleted]
modified.conffile..etc.logcheck.ignore.d.server.cvs.pserver: [deleted]
modified.conffile..etc.logcheck.ignore
[Group.of.nepali.translators] [Bug 1610500] Re: package pptpd 1.4.0-7ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I am nominating this for Xenial. As previously suggested this should be fixed there and has been reported in other bugs in Xenial to help ease upgrade. ** Also affects: pptpd (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1610500 Title: package pptpd 1.4.0-7ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pptpd package in Ubuntu: Fix Released Status in pptpd source package in Xenial: Confirmed Bug description: This is one of the crashed that happened during upgrade to 16.04 LTS. The install routine was exited with a script error. Try to figure stuff of since pptpd seems to be outdated ProblemType: Package DistroRelease: Ubuntu 16.04 Package: pptpd 1.4.0-7ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Fri Aug 5 21:40:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-02-25 (1988 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pptpd Title: package pptpd 1.4.0-7ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1610500/+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 1664179] Re: Wrong POM dependency in javax.servlet.jsp:jsp-api:2.2
@arges because the package is source only in zesty I am marking the primary task as invalid. ** Changed in: tomcat7 (Ubuntu) Status: Fix Committed => 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/1664179 Title: Wrong POM dependency in javax.servlet.jsp:jsp-api:2.2 Status in tomcat7 package in Ubuntu: Invalid Status in tomcat7 source package in Trusty: In Progress Status in tomcat7 source package in Xenial: In Progress Status in tomcat7 source package in Yakkety: In Progress Bug description: == Begin SRU Template == [Impact] * The Tomcat7 package specifies an incorrect version of the javax.servlet api. If users attempt to use the version specified, 2.2, it will fail trying to find that version as it does not exist at all. * Currently the version is auto filled in by @MAVEN.DEPLOY.VERSION@, which is used to fill in other fields as well. However, the API versions are not all the same and should not be specified like this. * The official servlet version for Tomcat 7, 3.0, was specified here: https://jcp.org/en/jsr/detail?id=315 [Test Case] An example to test Tomcat7 on Trusty. The same instructions can apply to other releases. Overview: Install tomcat7 and attempt to build the pom. It will fail as the built in library specifies a non-existent version of 2.2. * lxc launch ubuntu-daily:trusty trusty * lxc exec trusty bash * apt install tomcat7 maven-debian-helper libmaven-dependency-plugin-java libservlet3.0-java * wget https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1664179/+attachment/4818104/+files/pom.xml * mvn-deiban -q generate-sources -X [Regression Potential] * Users currently experiencing this issue would be expecting a SRU fix to come from us. Working around it would require changing the /usr/share/maven-repo/javax/servlet/jsp/jsp-api/2.2/jsp-api-2.2.pom to use the 3.0 version. This fix does the same thing. * There is the slight, albeit incredibly low chance, that someone actually has scripted something to modify the package itself and swap out @MAVEN.DEPLOY.VERSION@ to the correct value. * The tomcat8 package has gone away from using @MAVEN.DEPLOY.VERSION@ in favor of specifying the exact version as well to avoid this type of mismatch. [Other Info] Hi, Ubuntu 16.04.1 LTS, libservlet3.0-java=7.0.68-1ubuntu0.1 In /usr/share/maven-repo/javax/servlet/jsp/jsp-api/2.2/jsp-api-2.2.pom file that belongs to libservlet3.0-java there is the following dependency: javax.servlet servlet-api 2.2 compile But there is no corresponding javax.servlet:servlet-api:2.2 in /usr/share/maven-repo. So if I try to build some Java library that depends on javax.servlet.jsp:jsp-api:2.2 with mvn-debian, I cannot do it due to wrong transitive dependency. I've attached a test pom.xml to reproduce the bug: ubuntu@build:~$ ls -la pom.xml -rw-rw-r-- 1 ubuntu ubuntu 1185 Feb 13 10:12 pom.xml ubuntu@build:~$ ubuntu@build:~$ mvn-debian -q generate-sources find: ‘/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar’: No such file or directory find: ‘/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar’: No such file or directory find: ‘/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar’: No such file or directory [ERROR] Failed to execute goal on project yyy: Could not resolve dependencies for project xxx:yyy:pom:debian: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact javax.servlet:servlet-api:jar:2.2 has not been downloaded from it before. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException ubuntu@build:~$ I believe that javax.servlet.jsp:jsp-api:2.2 should list javax.servlet :servlet-api:3.0 as dependency, not 2.2 == End SRU Template == To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1664179/+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 1584431] Re: mongosniff crashes on start
** Changed in: mongodb (Ubuntu Trusty)
Status: New => Invalid
** Changed in: mongodb (Ubuntu Xenial)
Status: New => In Progress
** Changed in: mongodb (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: mongodb (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: mongodb (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: mongodb (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: mongodb (Ubuntu Trusty)
Assignee: (unassigned) => Joshua Powers (powersj)
** Changed in: mongodb (Ubuntu Yakkety)
Assignee: (unassigned) => Joshua Powers (powersj)
** Changed in: mongodb (Ubuntu Xenial)
Assignee: (unassigned) => Joshua Powers (powersj)
--
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/1584431
Title:
mongosniff crashes on start
Status in mongodb package in Ubuntu:
Fix Released
Status in mongodb source package in Trusty:
Invalid
Status in mongodb source package in Xenial:
In Progress
Status in mongodb source package in Yakkety:
In Progress
Bug description:
Ubuntu:
* Xenial x64
Packages:
#user@localhost:~$ for i in `dpkg --get-selections|grep -v deinstall|grep
mongo|cut -f1`; do echo $i `sudo apt-cache show $i|sed -n -e 's/^.*Version:
1://p'`; done
* mongodb 2.6.10-0ubuntu1
* mongodb-clients 2.6.10-0ubuntu1
* mongodb-server 2.6.10-0ubuntu1
Steps to reproduce:
1. start service
2. start sniffer
3. start shell
4. crash sniffer
---
user@localhost:~$ sudo service mongodb start
user@localhost:~$ mongo
MongoDB shell version: 2.6.10
connecting to: test
(...)
user@localhost:~$ sudo mongosniff --source NET lo
sniffing... 27017
127.0.0.1:37522 -->> 127.0.0.1:27017 admin.$cmd 60 bytes id:0 0
query: { whatsmyuri: 1 } ntoreturn: 1 ntoskip: 0
2016-05-22T01:26:35.545-0400 Assertion failure messageShouldHaveNs()
src/mongo/db/dbmessage.cpp 82
2016-05-22T01:26:35.553-0400 0xea35a9 0xe397cf 0xe14772 0x86aca8 0x615c13
0x7f614d369ef6 0x7f614d36e9d1 0x7f614d3731fd 0x616a5a 0x5e57a9 0x7f614c71a830
0x614389
mongosniff(_ZN5mongo15printStackTraceERSo+0x39) [0xea35a9]
mongosniff(_ZN5mongo10logContextEPKc+0x21f) [0xe397cf]
mongosniff(_ZN5mongo12verifyFailedEPKcS1_j+0x142) [0xe14772]
mongosniff() [0x86aca8]
mongosniff(_Z10got_packetPhPK11pcap_pkthdrPKh+0x573) [0x615c13]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(+0x5ef6) [0x7f614d369ef6]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(+0xa9d1) [0x7f614d36e9d1]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(pcap_loop+0x5d) [0x7f614d3731fd]
mongosniff(_Z8toolMainiPPcS0_+0x69a) [0x616a5a]
mongosniff(main+0x9) [0x5e57a9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f614c71a830]
mongosniff(_start+0x29) [0x614389]
terminate called after throwing an instance of 'mongo::AssertionException'
what(): assertion src/mongo/db/dbmessage.cpp:82
Aborted (core dumped)
user@localhost:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1584431/+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 1666570] Re: Post install script has error in RegEx
Only source package, binary is not present in zesty
** Also affects: tomcat8 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: tomcat8 (Ubuntu Trusty)
** Patch removed: "debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1666570/+attachment/4834136/+files/tomcat7_7.0.52-1ubuntu11.debdiff
** Changed in: tomcat7 (Ubuntu Zesty)
Status: In Progress => Invalid
** Changed in: tomcat7 (Ubuntu Zesty)
Assignee: Joshua Powers (powersj) => (unassigned)
--
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/1666570
Title:
Post install script has error in RegEx
Status in tomcat7 package in Ubuntu:
Invalid
Status in tomcat8 package in Ubuntu:
New
Status in tomcat7 source package in Trusty:
New
Status in tomcat7 source package in Xenial:
New
Status in tomcat8 source package in Xenial:
New
Status in tomcat7 source package in Yakkety:
New
Status in tomcat8 source package in Yakkety:
New
Status in tomcat7 source package in Zesty:
Invalid
Status in tomcat8 source package in Zesty:
New
Status in tomcat7 package in Debian:
New
Bug description:
== Begin SRU Template ==
[Impact]
* On upgrade of tomcat7 package, if a user has updated their JAVA_OPTS
variable to include a '%' an upgrade will fail. The sed command in the postinst
uses the '%' character to act as a delimiter, previous versions used '/'
however it was updated to '%' in hopes it was far less common.
* This SRU updates it to a character that should not be found in the
JAVA_ARGS value, namely '\001'.
* This is the same solution Debian and tomcat maintainers are now using for
Tomcat8.
[Test Case]
Install the version from the trusty pocket. Modify JAVA_OPTS and then
install the version from security/updates to reproduce the issue.
* lxc launch ubuntu-daily:trusty terusty
* lxc exec trusty bash
* apt install tomcat7=7.0.52-1
* Edit /etc/defaults/tomcat7, set JAVA_OPTS="-Djava.awt.headless=true
-XX:ErrorFile=/var/log/tomcat7/java_error%p.log -XX:+DisableExplicitGC
-XX:+UseG1GC"
* Enable proposed or use version from ppa (ppa:powersj/tomcat7-1666570)
* apt update
* apt install tomcat7
* Keep the local version currently installed
* With the fix, install will complete
* Without the fix, post-installation script will return a sed -e expression
#1 error.
[Regression Potential]
* Using a new delimiter that is far less likely to be in someone's path.
This is not the first time the delimiter has changed, as it originally as '/'
which is obviously going to show up as soon as someone adds a path.
* Upstream change to tomcat8:
https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/patch/?id=7664221d66701e2c31a31fe3b4f22e8bea4158dc
[Other Info]
* Error message on failure:
Setting up tomcat7 (7.0.52-1ubuntu0.10) ...
sed: -e expression #1, char 97: unknown option to `s'
dpkg: error processing package tomcat7 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
tomcat7
E: Sub-process /usr/bin/dpkg returned an error code (1)
== End SRU Template ==
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1666570/+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 1585121] Re: awstats produces regex warnings in version 7.4 with Perl 5.22 on Ubuntu 16.04 LTS
** Changed in: awstats (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: awstats (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: awstats (Ubuntu Xenial)
Importance: Undecided => High
--
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/1585121
Title:
awstats produces regex warnings in version 7.4 with Perl 5.22 on
Ubuntu 16.04 LTS
Status in awstats package in Ubuntu:
Fix Released
Status in awstats source package in Xenial:
Confirmed
Status in awstats package in Debian:
Unknown
Bug description:
[Impact]
The main awstats script triggers the Perl deprecation warnings about
unescaped braces in regexes, every time the script is run (which, by
default is every 10 minutes, via cron, sending out an email with
these).
[Test Case]
1. apt install awstats
2. run '/usr/share/awstats/tools/update.sh'
You should get an error because of a missing config parameter, but if
this bug is present, you also get six "Unescaped left brace in regex
is deprecated, ..." messages before that.
[Regression Potential]
I don't see any way this could go wrong. The patch is trivial, and is
already included upstream and in yakkety.
[Original Description]
> Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/\"%{ <-- HERE Referer}i\"/ at
/usr/lib/cgi-bin/awstats.pl line 9043.
> Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/\"%{ <-- HERE User-Agent}i\"/ at
/usr/lib/cgi-bin/awstats.pl line 9044.
> Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/%{ <-- HERE mod_gzip_input_size}n/ at
/usr/lib/cgi-bin/awstats.pl line 9045.
> Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/%{ <-- HERE mod_gzip_output_size}n/ at
/usr/lib/cgi-bin/awstats.pl line 9046.
> Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/%{ <-- HERE mod_gzip_compression_ratio}n/ at
/usr/lib/cgi-bin/awstats.pl line 9047.
> Unescaped left brace in regex is deprecated, passed through in regex;
marked by <-- HERE in m/\(%{ <-- HERE ratio}n\)/ at /usr/lib/cgi-bin/awstats.pl
line 9048.
Those warnings occur whenever we execute awstats and they can easily
be fixed by escaping the "{" and "}" at the mentioned lines. In fact
awstats 7.5 fixed those lines already itself:
> AWStats Changelog
> -
>
> * 7.5 *
>
> - Compatibility with Perl 5.22
Please consider backporting those fixes, because awstats is most
likely executed by cron or such and this produces unnecessary mails
with those warnings. Disabling mails on warnings/errors is of course
no solution, because one would miss real configuration errors or such
this way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1585121/+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
