Bug#986346: roundcube-plugins-extra: Please add twofactor_gauthenticator
Package: roundcube-plugins-extra Version: 1.4.10+1-3 Severity: wishlist Dear Maintainer, Please consider adding the "twofactor_gauthenticator" plugin to this package. Upstream URL: https://github.com/alexandregz/twofactor_gauthenticator Thanks! -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-3-amd64 (SMP w/3 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages roundcube-plugins-extra depends on: ii roundcube-core 1.4.11+dfsg.1-3 roundcube-plugins-extra recommends no packages. Versions of packages roundcube-plugins-extra suggests: ii fail2ban 0.11.2-1 -- no debconf information
Bug#980352: linux-image-5.10.0-1-amd64: fscache/CacheFiles crashing with assertion failure
Package: src:linux Version: 5.10.4-1 Severity: important X-Debbugs-Cc: li...@d.sb Dear Maintainer, I'm seeing an assertion failure when attempting to use fscache with NFS. This is causing programs that read from the NFS share to crash. Trace: = Jan 10 10:36:05 chi03 kernel: [819715.729949] CacheFiles: Jan 10 10:36:05 chi03 kernel: [819715.732895] CacheFiles: Assertion failed Jan 10 10:36:05 chi03 kernel: [819715.733268] [ cut here ] Jan 10 10:36:05 chi03 kernel: [819715.733671] kernel BUG at fs/cachefiles/rdwr.c:716! Jan 10 10:36:05 chi03 kernel: [819715.734055] invalid opcode: [#20] SMP PTI Jan 10 10:36:05 chi03 kernel: [819715.734418] CPU: 1 PID: 342823 Comm: node Tainted: G D 5.9.0-5-cloud-amd64 #1 Debian 5.9.15-1 Jan 10 10:36:05 chi03 kernel: [819715.735104] Hardware name: Red Hat KVM, BIOS 1.11.0-2.el7 04/01/2014 Jan 10 10:36:05 chi03 kernel: [819715.73] RIP: 0010:cachefiles_read_or_alloc_pages.cold+0x20/0x56 [cachefiles] Jan 10 10:36:05 chi03 kernel: [819715.736151] Code: be 97 ff ff ff e9 08 db ff ff 4d 87 e5 e9 83 ea ff ff 48 c7 c7 70 1b a3 c0 e8 15 68 bb fb 48 c7 c7 48 28 a3 c0 e8 09 68 bb fb <0f> 0b 48 c7 c7 70 1b a3 c0 e8 fb 67 bb fb 48 c7 c7 48 28 a3 c0 e8 Jan 10 10:36:05 chi03 kernel: [819715.737228] RSP: 0018:a8de01deba38 EFLAGS: 00010246 Jan 10 10:36:05 chi03 kernel: [819715.737629] RAX: 001c RBX: a8de01debd30 RCX: 98be2fc98488 Jan 10 10:36:05 chi03 kernel: [819715.738189] RDX: RSI: 0027 RDI: 98be2fc98480 Jan 10 10:36:05 chi03 kernel: [819715.738739] RBP: 98bd1a594900 R08: 0a5c R09: 0019 Jan 10 10:36:05 chi03 kernel: [819715.739291] R10: 0764 R11: a8de01deb8ce R12: 98bc86364120 Jan 10 10:36:05 chi03 kernel: [819715.739842] R13: a8de01debd30 R14: a8de01debbc4 R15: 98bc7ccbf9e8 Jan 10 10:36:05 chi03 kernel: [819715.740400] FS: 7f4ee30a8b20() GS:98be2fc8() knlGS: Jan 10 10:36:05 chi03 kernel: [819715.740980] CS: 0010 DS: ES: CR0: 80050033 Jan 10 10:36:05 chi03 kernel: [819715.741396] CR2: 559668694000 CR3: 0002ecdf0004 CR4: 001706a0 Jan 10 10:36:05 chi03 kernel: [819715.741947] Call Trace: Jan 10 10:36:05 chi03 kernel: [819715.742312] ? load_balance+0x174/0xd50 Jan 10 10:36:05 chi03 kernel: [819715.742674] ? _cond_resched+0x16/0x40 Jan 10 10:36:05 chi03 kernel: [819715.743048] ? fscache_alloc_retrieval+0x2f/0xe0 [fscache] Jan 10 10:36:05 chi03 kernel: [819715.743450] ? kmem_cache_alloc_trace+0xf5/0x210 Jan 10 10:36:05 chi03 kernel: [819715.743825] ? fscache_run_op+0x56/0xb0 [fscache] Jan 10 10:36:05 chi03 kernel: [819715.759972] __fscache_read_or_alloc_pages+0x235/0x2e0 [fscache] Jan 10 10:36:05 chi03 kernel: [819715.760412] __nfs_readpages_from_fscache+0x60/0x160 [nfs] Jan 10 10:36:05 chi03 kernel: [819715.760828] nfs_readpages+0xb5/0x1e0 [nfs] Jan 10 10:36:05 chi03 kernel: [819715.761192] ? bpf_prog_664d279cfb0774e6_netdata_sys_rea+0x51d/0x674 Jan 10 10:36:05 chi03 kernel: [819715.761641] read_pages+0x185/0x270 Jan 10 10:36:05 chi03 kernel: [819715.762046] page_cache_readahead_unbounded+0x1b2/0x230 Jan 10 10:36:05 chi03 kernel: [819715.762468] generic_file_buffered_read+0x59b/0xa50 Jan 10 10:36:05 chi03 kernel: [819715.762866] ? nfs4_get_valid_delegation+0x30/0x30 [nfsv4] Jan 10 10:36:05 chi03 kernel: [819715.763284] nfs_file_read+0x6d/0xa0 [nfs] Jan 10 10:36:05 chi03 kernel: [819715.763691] new_sync_read+0x112/0x1a0 Jan 10 10:36:05 chi03 kernel: [819715.764028] vfs_read+0xf8/0x180 Jan 10 10:36:05 chi03 kernel: [819715.764344] ksys_read+0x5f/0xe0 Jan 10 10:36:05 chi03 kernel: [819715.764673] do_syscall_64+0x33/0x40 Jan 10 10:36:05 chi03 kernel: [819715.765004] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 10 10:36:05 chi03 kernel: [819715.765395] RIP: 0033:0x7f4ee8761879 Jan 10 10:36:05 chi03 kernel: [819715.765730] Code: c3 8b 07 85 c0 75 24 49 89 fb 48 89 f0 48 89 d7 48 89 ce 4c 89 c2 4d 89 ca 4c 8b 44 24 08 4c 8b 4c 24 10 4c 89 5c 24 08 0f 05 e9 4d d3 ff ff 41 54 b8 02 00 00 00 49 89 f4 be 00 08 08 00 55 Jan 10 10:36:05 chi03 kernel: [819715.766806] RSP: 002b:7f4ee30a8538 EFLAGS: 0246 ORIG_RAX: Jan 10 10:36:05 chi03 kernel: [819715.767428] RAX: ffda RBX: 7f4ee30a8b20 RCX: 7f4ee8761879 Jan 10 10:36:05 chi03 kernel: [819715.767996] RDX: 9117 RSI: 5596684e5f20 RDI: 0012 Jan 10 10:36:05 chi03 kernel: [819715.768539] RBP: 7f4ee30a86b0 R08: R09: Jan 10 10:36:05 chi03 kernel: [819715.769083] R10: R11: 0246 R12: Jan 10 10:36:05 chi03 kernel: [819715.769630] R13: 0012 R14: 5596684e5f20 R15: 5596658be240 Jan 10 10:36:05 chi03 kernel: [819715.770171] Modules linked in:
Bug#971637: prometheus-alertmanager: generate-ui.sh throws "ERROR: invalid option"
Package: prometheus-alertmanager Version: 0.21.0+ds-2 Severity: normal X-Debbugs-Cc: li...@d.sb Dear Maintainer, When I run /usr/share/prometheus/alertmanager/generate-ui.sh to install the web UI, the following error occurs: Optimising source code... ERROR: invalid option --output=/tmp/tmp.zMO98JwUjl/script.js Changing line 26 from: --mangle --output=$TMPDIR/script.js to: --mangle --output $TMPDIR/script.js seems to fix the issue (that is, removing the `=` after `--output`). -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-2-cloud-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages prometheus-alertmanager depends on: ii init-system-helpers 1.58 ii libc62.31-3 ii systemd-sysv 246.4-1 prometheus-alertmanager recommends no packages. prometheus-alertmanager suggests no packages. -- Configuration Files: /etc/prometheus/alertmanager.yml changed [not included] -- no debconf information
Bug#956869: wireguard-dkms missing dependency on bc
Package: wireguard-dkms Version: 1.0.20200413-2 Severity: important Dear Maintainer, Attempting to install wireguard-dkms threw the following error: === DKMS make.log for wireguard-1.0.20200413 for kernel 4.19.0-8-amd64 (x86_64) Wed 15 Apr 2020 11:56:19 PM PDT make: Entering directory '/usr/src/linux-headers-4.19.0-8-amd64' /bin/sh: 1: bc: not found /var/lib/dkms/wireguard/1.0.20200413/build/compat/Kbuild.include:58: *** bc(1) is required for building. Stop. make[2]: *** [/usr/src/linux-headers-4.19.0-8-common/Makefile:1537: _module_/var/lib/dkms/wireguard/1.0.20200413/build] Error 2 make[1]: *** [Makefile:146: sub-make] Error 2 make: *** [Makefile:8: all] Error 2 make: Leaving directory '/usr/src/linux-headers-4.19.0-8-amd64' === Manually installing the "bc" package allowed the installation of wireguard-dkms to complete successfully The wireguard-dkms package should have a dependency on "bc" -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wireguard-dkms depends on: ii dkms 2.6.1-4 ii perl 5.28.1-6 Versions of packages wireguard-dkms recommends: ii wireguard1.0.20200319-1 ii wireguard-tools 1.0.20200319-1 wireguard-dkms suggests no packages. -- no debconf information
Bug#934768: speedtest-cli should depend on ca-certificates
Package: speedtest-cli Version: 2.1.1-2 Severity: normal Dear Maintainer, If you try to run speedtest-cli without installing ca-certificates, the following error is thrown: Retrieving speedtest.net configuration... Cannot retrieve speedtest configuration ERROR: As speedtest-cli is unusable without the CA certificates, it should have a dependency on the ca-certificates package. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.19.0-5-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages speedtest-cli depends on: ii python-pkg-resources 41.0.1-1 ii python33.7.3-1 ii python3-pkg-resources 41.0.1-1 speedtest-cli recommends no packages. speedtest-cli suggests no packages. -- no debconf information
Bug#923438:
I'm also hitting this issue on Debian Buster/Testing, after installing the Tinc package from experimental. I'd like to use Tinc 1.1, but had to downgrade to the Tinc 1.0 package in Buster for it to work properly.
Bug#914512: php-apcu: Rename to php7.2-apcu?
How are the versions determined? The issue I have at the moment is that the version of *php-apcu* in buster (5.1.12+4.0.11-2) is not compatible with the version of *php7.2-fpm* in buster. It looks like the current version of php-apcu only supports the RC of PHP 7.3, not the current released version of PHP (7.2). I had to compile php-apcu manually from source to get it working properly, as installing php-apcu was trying to install PHP 7.3 too. -- Regards, Daniel Lo Nigro https://d.sb/ | Twitter <http://twitter.com/Daniel15> | Facebook <http://www.facebook.com/daaniel> On Sat, Nov 24, 2018 at 3:30 AM OndÅ™ej Surý wrote: > php-apcu is a PECL extension that gets compiled for all available version > from the Debian (driven by php-all-dev package from src:php-defaults). > > This allows smooth transitions from one PHP version to another. > > So, what I am saying this works as intended, the phpX.Y-ext is reserved > solely for extensions shipped inside PHP (e.g. native extensions). > > Ondřej > -- > Ondřej Surý > > > On 24 Nov 2018, at 08:58, Daniel Lo Nigro wrote: > > > > Package: php-apcu > > Version: 5.1.12+4.0.11-2 > > Severity: normal > > > > Dear Maintainer, > > > > Most of the other PHP packages are prefixed with the version number, for > example "php7.2-gd", "php7.2-curl", etc. This allows multiple PHP versions > to be installed side-by-side. > > > > However, the APCU package is just called "php-apcu". Is there a reason > for this difference? It means I'm unable to have PHP 7.1 and 7.2 installed > side-by-side each with a packaged version of apcu, and instead need to > build from source. > > > > > > -- System Information: > > Debian Release: buster/sid > > APT prefers testing > > APT policy: (500, 'testing') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 4.18.0-2-amd64 (SMP w/1 CPU core) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Init: systemd (via /run/systemd/system) > > LSM: AppArmor: enabled > > > > Versions of packages php-apcu depends on: > > ii libc62.27-8 > > ii php-common 1:62 > > ii php7.3-cli [phpapi-20180731] 7.3.0~rc4-1 > > ii php7.3-phpdbg [phpapi-20180731] 7.3.0~rc4-1 > > > > Versions of packages php-apcu recommends: > > ii php-apcu-bc 1.0.4-3 > > > > Versions of packages php-apcu suggests: > > ii php7.1-gd [php-gd] 7.1.16-1 > > ii php7.2-gd [php-gd] 7.2.4-1 > > > > -- no debconf information > > > >
Bug#914512: php-apcu: Rename to php7.2-apcu?
Package: php-apcu Version: 5.1.12+4.0.11-2 Severity: normal Dear Maintainer, Most of the other PHP packages are prefixed with the version number, for example "php7.2-gd", "php7.2-curl", etc. This allows multiple PHP versions to be installed side-by-side. However, the APCU package is just called "php-apcu". Is there a reason for this difference? It means I'm unable to have PHP 7.1 and 7.2 installed side-by-side each with a packaged version of apcu, and instead need to build from source. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages php-apcu depends on: ii libc62.27-8 ii php-common 1:62 ii php7.3-cli [phpapi-20180731] 7.3.0~rc4-1 ii php7.3-phpdbg [phpapi-20180731] 7.3.0~rc4-1 Versions of packages php-apcu recommends: ii php-apcu-bc 1.0.4-3 Versions of packages php-apcu suggests: ii php7.1-gd [php-gd] 7.1.16-1 ii php7.2-gd [php-gd] 7.2.4-1 -- no debconf information
Bug#896452: whois: Update whois server for .ls
Package: whois Version: 5.3.0 Severity: normal Dear Maintainer, When a whois query is performed for a .ls domain, whois outputs the following text: This TLD has no whois server, but you can access the whois database at http://www.nic.ls/ However, this TLD does actually have a whois server at whois.nic.ls: $ whois -h whois.nic.ls google.co.ls % Domain Information over Whois protocol % % Whoisd Server Version: 3.10.2 % Timestamp: Sat Apr 21 09:48:38 2018 domain: google.co.ls registrant: ADMIN-LEO admin-c: ADMIN-LEO nsset:NS-GOOGLE registrar:REG-LEO registered: 03.07.2017 12:54:23 expire: 03.07.2018 ... -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages whois depends on: ii libc6 2.27-3 ii libidn2-0 2.0.4-1.1 whois recommends no packages. whois suggests no packages. -- no debconf information
Bug#319832: Also needed to add route
I just encountered this same issue. In addition to the 'ugly workaround', I also needed to explicitly add the default route otherwise my system did not have any outbound IPv6 connectivity: auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_fd 0 bridge_maxwait 0 # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319832 up ip -6 addr add 2605:6400:20:92e::1337:c0de/64 dev br0 up ip -6 route add 2605:6400:20::1/128 dev br0 up ip -6 route add default via 2605:6400:20::1 down ip -6 addr del 2605:6400:20:92e::1337:c0de/64 dev br0 down ip -6 route del default via 2605:6400:20::1 down ip -6 route del 2605:6400:20::1/128 dev br0 (in my this, 2605:6400:20:92e::1337:c0de is the server's IP while 2605:6400:20::1 is the gateway IP)
Bug#841981: nodejs should recommend ca-certificates
> > Apart from that, is there a good reason to use Recommend instead of Depend > ? I'm not sure. wget and libcurl3-gnutls both "Recommend" rather than "Depend" on ca-certificates. I think it's because wget still mostly works without it, it's just TLS/SSL connections that fail. Node.js behaves the same way, all of Node.js works without ca-certificates except for TLS connections.
Bug#841981: nodejs should recommend ca-certificates
Package: nodejs Version: 4.6.0~dfsg-2 Severity: normal Dear Maintainer, When CA certificates are not available, Node.js scripts that try to connect to remote servers using TLS/SSL fail with "Error: unable to get local issuer certificate". Other packages that rely on TLS (such as wget and libcurl3-gnutls) recommend the ca-certificates package, so nodejs should probably also do this. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-openvz-042stab108.8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages nodejs depends on: ii libc62.23-4 ii libgcc1 1:6.1.1-10 ii libicu57 57.1-2 ii libssl1.0.2 1.0.2h-1 ii libstdc++6 6.1.1-10 ii libuv1 1.9.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 nodejs recommends no packages. nodejs suggests no packages. -- no debconf information
Bug#841980: nodejs should recommend ca-certificates
Package: nodejs Version: 4.6.0~dfsg-2 Severity: normal Dear Maintainer, When CA certificates are not available, Node.js scripts that try to connect to remote servers using TLS/SSL fail with "Error: unable to get local issuer certificate". Other packages that rely on TLS (such as wget and libcurl3-gnutls) recommend the ca-certificates package, so nodejs should probably also do this. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-openvz-042stab108.8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages nodejs depends on: ii libc62.23-4 ii libgcc1 1:6.1.1-10 ii libicu57 57.1-2 ii libssl1.0.2 1.0.2h-1 ii libstdc++6 6.1.1-10 ii libuv1 1.9.1-1 ii zlib1g 1:1.2.8.dfsg-2+b1 nodejs recommends no packages. nodejs suggests no packages. -- no debconf information
Bug#811452: phpmyadmin: Missing Depends on dbconfig-mysql packages
Package: phpmyadmin Version: 4:4.5.3.1-1 Severity: normal I received this output while upgrading phpMyAdmin from 4.5.2-1 to 4.5.3.1-1: Preparing to unpack .../phpmyadmin_4%3a4.5.3.1-1_all.deb ... MySQL database support detected, but apparently missing Depends on dbconfig-mysql packages. Please report this issue to the package maintainer.. MySQL database support detected, but apparently missing Depends on dbconfig-mysql packages. Please report this issue to the package maintainer.. Unpacking phpmyadmin (4:4.5.3.1-1) over (4:4.5.2-1) ... MySQL database support detected, but apparently missing Depends on dbconfig-mysql packages. Please report this issue to the package maintainer.. MySQL database support detected, but apparently missing Depends on dbconfig-mysql packages. Please report this issue to the package maintainer.. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (750, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-openvz-042stab108.8-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages phpmyadmin depends on: ii dbconfig-common 2.0.0 ii debconf [debconf-2.0] 1.5.58 ii libjs-sphinxdoc 1.3.3-1 ii perl5.22.1-4 ii php-gettext 1.0.11-2 ii php-seclib 1.0.0-3 ii php5-cgi5.6.17-1~dotdeb+7.1 ii php5-common [php5-json] 5.6.17-1~dotdeb+7.1 ii php5-fpm5.6.17-1~dotdeb+7.1 ii php5-mysqlnd [php5-mysqli] 5.6.17-1~dotdeb+7.1 ii ucf 3.0031 Versions of packages phpmyadmin recommends: ii mariadb-client 10.0.23-1 ii mariadb-client-10.0 [virtual-mysql-client] 10.0.23-1 ii nginx-full [httpd] 1.9.6-2+b1 ii php-tcpdf 6.0.093+dfsg-1 ii php5-gd 5.6.17-1~dotdeb+7.1 Versions of packages phpmyadmin suggests: ii lynx-cur [www-browser] 2.8.9dev8-1 ii mariadb-server-10.0 [virtual-mysql-server] 10.0.23-1 -- debconf information: phpmyadmin/remove-error: abort * phpmyadmin/dbconfig-install: true phpmyadmin/dbconfig-remove: phpmyadmin/internal/skip-preseed: false phpmyadmin/missing-db-package-error: abort phpmyadmin/internal/reconfiguring: false * phpmyadmin/mysql/admin-user: root phpmyadmin/remote/newhost: phpmyadmin/setup-username: admin phpmyadmin/remote/host: * phpmyadmin/dbconfig-upgrade: true phpmyadmin/remote/port: * phpmyadmin/mysql/method: Unix socket * phpmyadmin/db/app-user: phpmyadmin2 * phpmyadmin/db/dbname: phpmyadmin2 phpmyadmin/dbconfig-reinstall: true * phpmyadmin/upgrade-error: ignore phpmyadmin/install-error: ignore phpmyadmin/upgrade-backup: true phpmyadmin/passwords-do-not-match: phpmyadmin/database-type: mysql phpmyadmin/purge: false * phpmyadmin/reconfigure-webserver:
Bug#803722: gdb segfaults when trying to debug HHVM
Package: gdb Version: 7.7.1+dfsg-5 Severity: important gdb segfaults when I try to debug HHVM: daniel@debian:/var/www/hhvm-bugs$ gdb --quiet hhvm Reading symbols from hhvm...Segmentation fault HHVM was installed from its hhvm-dbg Debian package, using the instructions at https://github.com/facebook/hhvm/wiki/Prebuilt-Packages-on-Debian-8. This is the backtrace from gdb, if it helps: #0 _int_malloc (av=av@entry=0x7622c620 , bytes=bytes@entry=640) at malloc.c:3700 #1 0x75f05a2c in __libc_calloc (n=, elem_size=) at malloc.c:3219 #2 0x00681911 in xcalloc (number=160, size=size@entry=4) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/common/common-utils.c:91 #3 0x004f93ef in elf_symfile_segments (abfd=0xd60850) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/elfread.c:120 #4 0x0056e53f in symfile_find_segment_sections (objfile=0xd88490) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:3796 #5 init_objfile_sect_indices (objfile=0xd88490) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:345 #6 default_symfile_offsets (objfile=0xd88490, addrs=) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:765 #7 0x0056c2d4 in syms_from_objfile_1 (add_flags=6, addrs=0xd4e040, objfile=0xd88490) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:1011 #8 syms_from_objfile (add_flags=6, addrs=0xd4e040, objfile=0xd88490) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:1029 #9 symbol_file_add_with_addrs (abfd=abfd@entry=0xd60850, name=name@entry=0x7fffe8ef "hhvm", add_flags=add_flags@entry=6, addrs=addrs@entry=0x0, flags=flags@entry=0, parent=parent@entry=0x0) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:1126 #10 0x0056c824 in symbol_file_add_from_bfd (parent=0x0, flags=0, addrs=0x0, add_flags=6, name=0x7fffe8ef "hhvm", abfd=0xd60850) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:1215 #11 symbol_file_add (name=name@entry=0x7fffe8ef "hhvm", add_flags=6, addrs=addrs@entry=0x0, flags=flags@entry=0) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:1230 #12 0x0056c888 in symbol_file_add_main_1 (args=0x7fffe8ef "hhvm", from_tty=1, flags=0) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/symfile.c:1255 #13 0x00592f2e in catch_command_errors_const (command=0x56c8b0 , arg=arg@entry=0x7fffe8ef "hhvm", from_tty=1, mask=mask@entry=RETURN_MASK_ALL) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/exceptions.c:567 #14 0x00595a45 in captured_main (data=data@entry=0x7fffe5d0) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/main.c:969 #15 0x00592d8a in catch_errors (func=func@entry=0x595080 , func_args=func_args@entry=0x7fffe5d0, errstring=errstring@entry=0x740755 "", mask=mask@entry=RETURN_MASK_ALL) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/exceptions.c:524 #16 0x00596084 in gdb_main (args=args@entry=0x7fffe5d0) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/main.c:1076 #17 0x0045484e in main (argc=, argv=) at /build/gdb-2hEJVN/gdb-7.7.1+dfsg/gdb/gdb.c:34 -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdb depends on: ii libc6 2.19-18+deb8u1 ii libexpat1 2.1.0-6+deb8u1 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libncurses5 5.9+20140913-1+b1 ii libpython2.7 2.7.9-2 ii libreadline6 6.3-8+b3 ii libtinfo5 5.9+20140913-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages gdb recommends: ii gdbserver 7.7.1+dfsg-5 ii libc6-dbg [libc-dbg] 2.19-18+deb8u1 Versions of packages gdb suggests: pn gdb-doc -- no debconf information
Bug#430484:
Sorry about that, I was not clear enough ;). In that sentence, you need to replace: "no matter what it is told in it's configuration." with: "no matter what it is told in its configuration." - Daniel On Sat, 2007-07-14 at 18:28 +0200, Ola Lundqvist wrote: > Hi again. > > As I can see this patch should not be applied at all. Is there any > fault with the spelling at all? If so please point out where. :) > > Regards, > > // Ola > > On Sat, Jul 14, 2007 at 01:46:52PM +1000, Daniel Lo Nigro wrote: > > Your patch is backwards :P > > You need to replace "it's" with "its", not the other way around. > > > > > > > > -- > - Ola Lundqvist --- > / [EMAIL PROTECTED] Annebergsslingan 37 \ > | [EMAIL PROTECTED] 654 65 KARLSTAD | > | http://opalsys.net/ +46 (0)70-332 1551 | > \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / > --- > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#430484:
Your patch is backwards :P You need to replace "it's" with "its", not the other way around. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]