Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]
Steve McIntyre writes: > Hi all! > > программист некто (in CC) reported this bug a few weeks back in > Debian. Since I applied the bundle of filesystem bounds-checking fixes > a few months back, he can't run grub-install. He's done the work to > determine that the patch that breaks things for him is > > 2d014248d540c7e087934a94b6e7a2aa7fc2c704 fs/f2fs: Do not read past the end of > nat journal entries > > The full thread of our discussion is at https://bugs.debian.org/1021846 > > I don't have any knowledge of f2fs to go any further here. Help please! :-) I don't know much about f2fs either, but has the value of `n` been captured versus NAT_JOURNAL_ENTRIES in the failing case? Might be useful to know how much it's going over by. Be well, --Robbie signature.asc Description: PGP signature
Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed
Package: libpam-systemd Version: 238-5 Severity: grave Justification: renders package unusable Dear Maintainer, (This bug has been reported also against systemd-shim: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 ) libpam-systemd requires systemd-shim version >=10-4~. No such version exists. This would make systemd-shim unusable. root@hpsiddie:/home/manul# apt-get dist-upgrade -d sysvinit-core+ libpam-systemd+ Reading package lists... Done Building dependency tree Reading state information... Done sysvinit-core is already the newest version (2.88dsf-59.10). Calculating upgrade... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpam-systemd : Depends: systemd-shim (>= 10-4~) but it is not going to be installed or systemd-sysv but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=es_US.UTF-8, LC_CTYPE=es_US.UTF-8 (charmap=UTF-8), LANGUAGE=es_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libpam-systemd depends on: ii dbus1.12.10-1 ii libc6 2.27-5 ii libpam-runtime 1.1.8-3.8 ii libpam0g1.1.8-3.8 ii systemd 238-5 ii systemd-shim10-3 libpam-systemd recommends no packages. libpam-systemd suggests no packages. -- no debconf information
Bug#871601: ansible-2.3.1.0+dfsg-1 is uninstallable
Package: ansible Version: 2.3.1.0+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, ansible-2.3.1.0+dfsg-1 depends on python-jinja2 < 2.9. However, this is not available in testing/unstable/experimental. As a result, ansible-2.3.1.0+dfsg-1 is uninstallable, and its migration from unstable has been blocked. Thanks, --Robbie -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT) 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: sysvinit (via /sbin/init) Versions of packages ansible depends on: ii python2.7.13-2 ii python-crypto 2.6.1-7+b1 ii python-httplib2 0.9.2+dfsg-1 ii python-jinja2 2.9.6-1 ii python-netaddr0.7.18-2 ii python-paramiko 2.0.0-1 ii python-pkg-resources 36.0.1-1 ii python-yaml 3.12-1+b1 Versions of packages ansible recommends: ii python-kerberos 1.1.5-2+b3 ii python-selinux2.6-3+b2 pn python-winrm ii python-xmltodict 0.11.0-1 Versions of packages ansible suggests: pn cowsay pn sshpass -- no debconf information
Bug#864377: docker.io: Failure to install (cannot start daemon)
Package: docker.io Version: 1.13.1~ds1-2 Followup-For: Bug #864377 Well, perhaps. The problem is that I can reproduce this on a fresh system installation by just triggering a reinstall: rharwood@seton:~$ sudo aptitude reinstall docker.io The following packages will be REINSTALLED: docker.io 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 0 B/11.0 MB of archives. After unpacking 0 B will be used. (Reading database ... 309020 files and directories currently installed.) Preparing to unpack .../docker.io_1.13.1~ds1-2_amd64.deb ... Unpacking docker.io (1.13.1~ds1-2) over (1.13.1~ds1-2) ... Setting up docker.io (1.13.1~ds1-2) ... [] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" failed. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (233-9) ... Processing triggers for man-db (2.7.6.1-2) ... Errors were encountered while processing: docker.io E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up docker.io (1.13.1~ds1-2) ... [] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" failed. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io Note that I haven't done any configuration or anything here, just installed the package and then asked for a reinstall. Thanks, --Robbie -- System Information: Debian Release: buster/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT) 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: sysvinit (via /sbin/init) Versions of packages docker.io depends on: ii adduser 3.115 ii containerd 0.2.3+git20170126.85.aa8187d~ds1-1 ii golang-libnetwork0.8.0-dev.2+git20170202.599.45b4086-1 ii init-system-helpers 1.48 ii iptables 1.6.1-2 ii libapparmor1 2.11.0-6 ii libc62.24-12 ii libdevmapper1.02.1 2:1.02.137-2+b1 ii libsqlite3-0 3.16.2-5 ii libsystemd0 233-9 ii lsb-base 9.20161125 ii runc 1.0.0~rc2+git20170201.133.9df8b30-2 Versions of packages docker.io recommends: ii ca-certificates 20161130+nmu1 ii cgroupfs-mount 1.4 ii git 1:2.13.2-3 ii xz-utils 5.2.2-1.2+b1 Versions of packages docker.io suggests: pn aufs-tools pn btrfs-progs pn debootstrap pn docker-doc pn rinse pn zfs-fuse | zfsutils -- no debconf information
Bug#864377: docker.io: Failure to install (cannot start daemon)
Package: docker.io Version: 1.13.1~ds1-2 Severity: grave Justification: renders package unusable Dear Maintainer, During a system upgrade, I got the following: Setting up docker.io (1.13.1~ds1-2) ... [] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" failed. dpkg: error processing package docker.io (--configure): Followed by, at the end: Errors were encountered while processing: docker.io E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up docker.io (1.13.1~ds1-2) ... [] Starting Docker: dockerinvoke-rc.d: initscript docker, action "start" failed. dpkg: error processing package docker.io (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: docker.io I grepped logs for error, but don't see anything related, and they're so incredibly verbose as to be useless. Thanks, --Robbie -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (600, 'unstable-debug'), (600, 'testing-debug'), (600, 'unstable'), (600, 'testing'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-rt-amd64 (SMP w/8 CPU cores; PREEMPT) 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: sysvinit (via /sbin/init) Versions of packages docker.io depends on: ii adduser 3.115 ii containerd 0.2.3+git20170126.85.aa8187d~ds1-1 ii golang-libnetwork0.8.0-dev.2+git20170202.599.45b4086-1 ii init-system-helpers 1.48 ii iptables 1.6.0+snapshot20161117-6 ii libapparmor1 2.11.0-3 ii libc62.24-11 ii libdevmapper1.02.1 2:1.02.137-2 ii libsqlite3-0 3.16.2-4 ii libsystemd0 232-25 ii lsb-base 9.20161125 ii runc 1.0.0~rc2+git20170201.133.9df8b30-1 Versions of packages docker.io recommends: ii ca-certificates 20161130+nmu1 ii cgroupfs-mount 1.4 ii git 1:2.13.1+next.20170605-1 ii xz-utils 5.2.2-1.2+b1 Versions of packages docker.io suggests: pn aufs-tools ii btrfs-progs 4.9.1-1 ii debootstrap 1.0.90 pn docker-doc pn rinse pn zfs-fuse | zfsutils -- no debconf information
Bug#860342: python3-taglib: Newer upstream releases available since Jan 21, 2014
Package: python3-taglib Severity: grave Justification: renders package unusable Dear Maintainer, Please update to a newer version of the package. This looks unmaintained and I would have filed an RM request save that there are packages that depend on this in the archive. Thanks. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (600, 'unstable-debug'), (600, 'testing-debug'), (600, 'unstable'), (600, 'testing'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT) 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)
Bug#857065: gmrun: Segfault after recent upgrades
Package: gmrun Version: 0.9.2-2.1+b2 Severity: grave Followup-For: Bug #857065 Raising severity to "grave" since it is usable becuse it segfaults every time we try to launch it. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (600, 'unstable-debug'), (600, 'testing-debug'), (600, 'unstable'), (600, 'testing'), (200, 'experimental-debug'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-rt-amd64 (SMP w/8 CPU cores; PREEMPT) 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 gmrun depends on: ii libatk1.0-0 2.22.0-1 ii libc62.24-9 ii libcairo21.14.8-1 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3+b2 ii libgcc1 1:6.3.0-8 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-0 2.50.3-1 ii libgtk2.0-0 2.24.31-2 ii libpango-1.0-0 1.40.4-1 ii libpangocairo-1.0-0 1.40.4-1 ii libpangoft2-1.0-01.40.4-1 ii libpopt0 1.16-10 ii libstdc++6 6.3.0-8 gmrun recommends no packages. gmrun suggests no packages. -- no debconf information
Bug#846535: openssl: 1.1.0c cannot decrypt files created by older versions of openssl
Package: openssl Version: 1.1.0c-2 Severity: critical Justification: causes serious data loss Dear Maintainer, After upgrading to a newer version of OpenSSL, I cannot decrypt a file that was encrypted using the OpenSSL in Stable (and had been decryptable until very recently). To reproduce: root@stable:~# echo "test" > file root@stable:~# echo "secretes" | openssl enc -aes-256-cbc -in file -out file.enc -pass stdin Then copy the file to a (testing) system and: rharwood@thriss:/tmp$ echo "secretes" | openssl enc -d -aes-256-cbc -in file.enc -out file -pass stdin bad decrypt 140704872014976:error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt:crypto/evp/evp_enc.c:529: Thanks! -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental'), (1, 'experimental-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-rt-amd64 (SMP w/8 CPU cores; PREEMPT) 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 openssl depends on: ii libc6 2.24-7 ii libssl1.1 1.1.0c-2 openssl recommends no packages. Versions of packages openssl suggests: ii ca-certificates 20161102 -- no debconf information
Bug#839844: freeipa-client: Uninstallable due to unsatisfiable Depends:
Package: freeipa-client Version: 4.3.2-2 Severity: grave Justification: renders package unusable Dear Maintainer, freeipa-client currently cannot be installed due to the following nonexistent dependencies: Depends: freeipa-common (= 4.3.2-2) which is a virtual package and is not provided by any available package Depends: python-ipaclient (= 4.3.2-2) which is a virtual package and is not provided by any available package Thanks. -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (600, 'testing-debug'), (600, 'testing'), (400, 'unstable-debug'), (400, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/8 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)
Bug#764564: [PKG-OpenRC-Debian] Bug#764564: openrc: fail to boot when encryption + lvm are present
Thomas Goirand z...@debian.org writes: Hi, If I'm not mistaking, this is the same bug as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754987 Don't think so. While there is a udev hang, it gets past this, as you can see from the messages at the end of the log. Furthermore, sysvinit completes boot even with the udev hang. and some information may be found here too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758480 Don't think it's this, either. I did not interrupt any part of boot in order to get this failure; this failure happens *every time*. It's possible that the filesystem is read-only during boot here which would cause failure, but I don't have a good way to check that. If you agree that this is the same bug, then I may close this one. Unless you see something that I don't, I think this is a different bug. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
