[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2019-04-02 Thread James Howe
> None of the packages which you are having an issue with are ones from
the official Ubuntu archive

What about these? Why is libcurl3 even in Bionic as a conflicting
package if nothing was supposed to use it?

$ apt-cache rdepends libcurl3
libcurl3
Reverse Depends:
  libcurl-openssl1.0-dev
  |flashplugin-installer
  libxmltooling7
  ruby-ethon

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754294

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829893] [NEW] Default redis-sentinel config has incorrect comments

2019-05-21 Thread James Howe
Public bug reported:

The file /etc/redis/sentinel.conf is a self-documenting default config file.
However, a number of doc comments don't match the items.

In particular:
"sentinel myid" is documented as "sentinel monitor"
"sentinel monitor" is documented as "sentinel down-after-milliseconds"
"sentinel config-epoch" is documented as "sentinel parallel-syncs"
"sentinel leader-epoch" is documented as "sentinel failover-timeout".

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: redis-sentinel 5:4.0.9-1ubuntu0.1
ProcVersionSignature: Microsoft 4.4.0-17134.706-Microsoft 4.4.35
Uname: Linux 4.4.0-17134-Microsoft x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Tue May 21 15:49:56 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: redis
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.redis.sentinel.conf: [inaccessible: [Errno 13] 
Permission denied: '/etc/redis/sentinel.conf']

** Affects: redis (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829893

Title:
  Default redis-sentinel config has incorrect comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1829893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829893] Re: Default redis-sentinel config has incorrect comments

2019-05-23 Thread James Howe
On further investigation, the shipped config file is immediately changed
when the service starts after installation, so it's an upstream bug in
redis.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829893

Title:
  Default redis-sentinel config has incorrect comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1829893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829893] Re: Default redis-sentinel config has incorrect comments

2019-05-23 Thread James Howe
https://github.com/antirez/redis/issues/5388

** Bug watch added: github.com/antirez/redis/issues #5388
   https://github.com/antirez/redis/issues/5388

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829893

Title:
  Default redis-sentinel config has incorrect comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1829893/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1831079] [NEW] Documentation bug for pam_userdb

2019-05-30 Thread James Howe
Public bug reported:

The man page for pam_userdb(8) has an incorrect example

> auth  sufficient pam_userdb.so icase db=/etc/dbtest.db

should be

> auth  sufficient pam_userdb.so icase db=/etc/dbtest

It should also be mentioned in the options that ".db" will be added to
the value of db.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1
ProcVersionSignature: Microsoft 4.4.0-17134.706-Microsoft 4.4.35
Uname: Linux 4.4.0-17134-Microsoft x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Thu May 30 13:33:25 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: pam
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pam (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831079

Title:
  Documentation bug for pam_userdb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1831079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1692850] [NEW] graphite.wgsi is not executable

2017-05-23 Thread James Howe
Public bug reported:

Default installation fails to run, returning a 500 Internal Server Error
when navigating to the graphite web frontend.

[Mon May 22 11:28:23.079148 2017] [:error] [pid 9344:tid
139738154194816] mod_wsgi (pid=9344): Target WSGI script '/usr/share
/graphite-web/graphite.wsgi' cannot be loaded as Python module.

The issue is resolved if the file /usr/share/graphite-web/graphite.wsgi
is made executable.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: graphite-web 0.9.12+debian-3
ProcVersionSignature: Ubuntu 4.4.0-78.99~14.04.2-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.24
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 23 10:31:32 2017
InstallationDate: Installed on 2015-12-03 (536 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: graphite-web
UpgradeStatus: Upgraded to trusty on 2016-08-09 (286 days ago)

** Affects: graphite-web (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Description changed:

- Ubuntu 14.04.5 LTS
- graphite-web 0.9.12+debian-3
- 
  Default installation fails to run, returning a 500 Internal Server Error
  when navigating to the graphite web frontend.
  
  [Mon May 22 11:28:23.079148 2017] [:error] [pid 9344:tid
  139738154194816] mod_wsgi (pid=9344): Target WSGI script '/usr/share
  /graphite-web/graphite.wsgi' cannot be loaded as Python module.
  
  The issue is resolved if the file /usr/share/graphite-web/graphite.wsgi
  is made executable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: graphite-web 0.9.12+debian-3
  ProcVersionSignature: Ubuntu 4.4.0-78.99~14.04.2-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 23 10:31:32 2017
  InstallationDate: Installed on 2015-12-03 (536 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: graphite-web
  UpgradeStatus: Upgraded to trusty on 2016-08-09 (286 days ago)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692850

Title:
  graphite.wgsi is not executable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphite-web/+bug/1692850/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 998086] Re: package smokeping 2.6.7-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

2012-05-11 Thread James Howe
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998086

Title:
  package smokeping 2.6.7-1 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smokeping/+bug/998086/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 998086] [NEW] package smokeping 2.6.7-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

2012-05-11 Thread James Howe
Public bug reported:

james@BMCServer1:~$ lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04


james@BMCServer1:~$ apt-cache policy smokeping
smokeping:
  Installed: 2.6.7-1
  Candidate: 2.6.7-1
  Version table:
 *** 2.6.7-1 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
100 /var/lib/dpkg/status

Expected: disto upgrade from 11.10 to 12.4

During "do-release-upgrade" I was prompted to conform if I wanted to
overwrite my smokeping config files with default ones from the package
maintainer ("/etc/smokeping/config.d/", Targets, Probes, Presentation,
General, "/etc/smokeping/basepage.html") . I selected No for each. After
confirming for basepage.html, I received this output:

"
*** basepage.html (Y/I/N/O/D/Z) [default=N] ? n
Installing new version of config file /etc/init.d/smokeping ...
chown: invalid group: `smokeping:smokeping'
dpkg: error processing smokeping (--configure):
 subprocess installed post-installation script returned error exit status 1
No apport report written because MaxReports is reached already
  Setting up 
dmsetup (2:1.02.48-4ubuntu7.1) ...
"

The result of an "id" shows that smokeping isn't in the group smokeping
(and actually the smokeping group doesn't exist), this is not a change
I've made to the server config:

james@BMCServer1:~$ id smokeping
uid=111(smokeping) gid=121(snmp) groups=121(snmp),33(www-data)

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: smokeping 2.6.7-1
ProcVersionSignature: Ubuntu 3.0.0-16.28-server 3.0.17
Uname: Linux 3.0.0-16-server x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri May 11 15:29:25 2012
ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
PackageArchitecture: all
SourcePackage: smokeping
Title: package smokeping 2.6.7-1 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-05-11 (0 days ago)

** Affects: smokeping (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998086

Title:
  package smokeping 2.6.7-1 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/smokeping/+bug/998086/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 2064112] Re: mk-sbuild fails to add user to group on first run

2024-04-29 Thread James Howe
Sorry, I was running in a Docker container, and $USER was undefined.

** Changed in: ubuntu-dev-tools (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064112

Title:
  mk-sbuild fails to add user to group on first run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2064112/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064112] [NEW] mk-sbuild fails to add user to group on first run

2024-04-29 Thread James Howe
Public bug reported:

/usr/bin/mk-sbuild line 301:

sudo adduser "$USER" sbuild

should be:

sudo usermod -a -G sbuild "$USER"

otherwise it fails with the message:

fatal: Only one or two names allowed.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-dev-tools 0.201ubuntu2
Uname: Linux 5.15.146.1-microsoft-standard-WSL2 x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CloudBuildName: ubuntu-oci:minimized
CloudSerial: 20240423
Date: Mon Apr 29 11:54:10 2024
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 TERM=xterm
SourcePackage: ubuntu-dev-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-dev-tools (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug cloud-image noble

** Description changed:

  /usr/bin/mk-sbuild line 301:
  
- sudo adduser "$USER" sbuild
+ sudo adduser "$USER" sbuild
  
  should be:
  
- sudo adduser "$USER" -G sbuild
+ sudo usermod -a -G sbuild "$USER"
  
  otherwise it fails with the message:
  
- fatal: Only one or two names allowed.
+ fatal: Only one or two names allowed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-dev-tools 0.201ubuntu2
  Uname: Linux 5.15.146.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudBuildName: ubuntu-oci:minimized
  CloudSerial: 20240423
  Date: Mon Apr 29 11:54:10 2024
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  TERM=xterm
+  PATH=(custom, no user)
+  TERM=xterm
  SourcePackage: ubuntu-dev-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064112

Title:
  mk-sbuild fails to add user to group on first run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2064112/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1829893] Re: Default redis-sentinel config has incorrect comments

2024-10-01 Thread James Howe
Just noticed that no maintainer ever looked at this.

The upstream bug was fixed in 6.2, so affects Ubuntu releases before
23.10 (mantic).

** Changed in: redis (Ubuntu)
   Status: New => Invalid

** Tags added: focal jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829893

Title:
  Default redis-sentinel config has incorrect comments

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/redis/+bug/1829893/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2083366] [NEW] SyntaxWarnings in checkrestart

2024-10-01 Thread James Howe
Public bug reported:

After upgrading from 22.04 to 24.04, checkrestart now logs the following
on every invocation:

/usr/sbin/checkrestart:222: SyntaxWarning: invalid escape sequence '\S'
  m = re.match('^diversion by (\S+) (from|to): (.*)$', line)
/usr/sbin/checkrestart:398: SyntaxWarning: invalid escape sequence '\('
  if re.compile("DEL").search(last) or re.compile("\(deleted\)").search(data) 
or re.compile("\(path inode=[0-9]+\)$").search(data):
/usr/sbin/checkrestart:398: SyntaxWarning: invalid escape sequence '\('
  if re.compile("DEL").search(last) or re.compile("\(deleted\)").search(data) 
or re.compile("\(path inode=[0-9]+\)$").search(data):
/usr/sbin/checkrestart:430: SyntaxWarning: invalid escape sequence '\s'
  if re.compile("\s\(deleted\)$").search(fname):
/usr/sbin/checkrestart:437: SyntaxWarning: invalid escape sequence '\s'
  data = re.split('\s+', output.strip('\n'), 3)
/usr/sbin/checkrestart:440: SyntaxWarning: invalid escape sequence '\s'
  if re.compile("\s\(deleted\)$").search(f):
/usr/sbin/checkrestart:464: SyntaxWarning: invalid escape sequence '\.'
  if ( f.startswith('/lib/') or f.startswith('/usr/lib/') ) and 
re.compile("\.so[\d.]+$"):
/usr/sbin/checkrestart:468: SyntaxWarning: invalid escape sequence '\+'
  f = re.compile("\+").sub("\+", f)
/usr/sbin/checkrestart:468: SyntaxWarning: invalid escape sequence '\+'
  f = re.compile("\+").sub("\+", f)
/usr/sbin/checkrestart:469: SyntaxWarning: invalid escape sequence '\d'
  f = re.compile(".so[\d.]+$").sub(".so.*", f)
/usr/sbin/checkrestart:470: SyntaxWarning: invalid escape sequence '\.'
  f = re.compile("\.").sub("\.", f)
/usr/sbin/checkrestart:470: SyntaxWarning: invalid escape sequence '\.'
  f = re.compile("\.").sub("\.", f)
/usr/sbin/checkrestart:594: SyntaxWarning: invalid escape sequence '\('
  if re.compile("\(path inode=[0-9]+\)$").search(f):
/usr/sbin/checkrestart:651: SyntaxWarning: invalid escape sequence '\d'
  re_uids = re.compile('Uid:\t(\d+)\t(\d+)\t(\d+)\t(\d+)$')
/usr/sbin/checkrestart:764: SyntaxWarning: invalid escape sequence '\('
  return re.sub('( \(deleted\)|.dpkg-new).*$','',f)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: debian-goodies 0.88.1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Oct  1 14:37:36 2024
PackageArchitecture: all
SourcePackage: debian-goodies
UpgradeStatus: Upgraded to noble on 2024-09-30 (1 days ago)

** Affects: debian-goodies (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083366

Title:
  SyntaxWarnings in checkrestart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-goodies/+bug/2083366/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080636] Re: upgrade script from 22.04 to 24.04 fails due to package 'postgresql-13-postgis-3'

2024-11-07 Thread James Howe
> remove postgres, upgrade and then install the latest packaged version.

That is not how it has worked on any previous upgrade, nor how it still
works if you don't have postgis installed.

The upgrade should add the new postgres version while leaving the old
packages installed and the service running.

That's why Debian has gone to all the trouble of supporting multiple
different postgres versions installed and running simultaneously on the
same system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080636

Title:
  upgrade script from 22.04 to 24.04  fails due to package
  'postgresql-13-postgis-3'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2080636/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2071916] Re: do-release-upgrade fails, appears to be due to postgis

2024-11-07 Thread James Howe
Same problem upgrading from 22.02 with postgresql-14-postgis-3.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071916

Title:
  do-release-upgrade fails, appears to be due to postgis

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2071916/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs