Bug#1032517:
On Wed, 8 Mar 2023 19:05:39 +0100 Jan Mojzis wrote:
Hello,
can You please send me the steps how i can reproduce it
- packages list/versions before the upgrade
- exact apt/apt-get command
- packages list/versions after the upgrade
Jan
I used aptitude to perform upgrade.
Before upgrade:
ii libnginx-mod-http-echo 1.22.0-3 amd64
ii libnginx-mod-http-perl 1.22.0-3 amd64
ri nginx-common 1.22.0-3 all
ii nginx-light1.22.0-3 amd64
ii python3-certbot-nginx 1.29.0-1 all
After:
ii libnginx-mod-http-echo 1:0.63-4 amd64
ii libnginx-mod-http-perl 1.22.1-7 amd64
ii nginx 1.22.1-7 amd64
ii nginx-common 1.22.1-7 all
ii nginx-light1.22.1-7 all
ii python3-certbot-nginx 2.1.0-2 all
Then I used aptitude to purge leftover configuration files:
# aptitude purge ?config-files
The following packages will be REMOVED:
emacsen-common{p} libpython3.10-minimal{p} nginx-common{p}
php8.1-cli{p} php8.1-common{p} php8.1-fpm{p} php8.1-opcache{p}
php8.1-readline{p} python3.10-minimal{p}
0 packages upgraded, 0 newly installed, 9 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?] y
Bug#1032517: nginx settings deleted on upgrade
I can confirm this bug. Happened to me twice yesterday. The problem occurs also when pruning is being done after system upgrade, in a separate step.
Bug#939076: (no subject)
The bug also affects me. Results in no network access after boot. Sep 10 12:46:52 sonata systemd[1]: Reached target Network. Sep 10 12:46:52 sonata systemd[1]: Reached target Network is Online. Sep 10 12:46:52 sonata kernel: bnx2x :01:00.2: firmware: failed to load bnx2x/bnx2x-e2-7.13.11.0.fw (-2) Sep 10 12:46:52 sonata kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware Sep 10 12:46:52 sonata kernel: bnx2x :01:00.2: Direct firmware load for bnx2x/bnx2x-e2-7.13.11.0.fw failed with error -2 Sep 10 12:46:52 sonata kernel: bnx2x: [bnx2x_func_hw_init:6002(eno3)]Error loading firmware Sep 10 12:46:52 sonata kernel: bnx2x: [bnx2x_nic_load:2730(eno3)]HW init failed, aborting
Bug#918659: Debootstrap started to fail with Busybox
Package: debootstrap Version: 1.0.113 Debootstrap started to fail with busybox since version 1.0.113. Previously it worked flawlessly with busybox. It fails silently, but debootstrap.log contains the following error: date: invalid date 'Tue, 15 Jan 2019 02:23:06 UTC' The reason is commit: 75cd76ca821bfe92434b26503b1716ca6b99fd0c, which parses Valid-Until using `date -d` command. Busybox's date command does not parse RFC 2822 dates. Please do not use `date -d` command for parsing Valid-Until field. Or, at least, shortcut with NO_CHECK_VALID_UNTIL **before** `date -d` command is called (so one will use --no-check-valid-until on Busybox to prevent debootstrap from silent fail).
Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted
After downgrading udev and libudev1 to 239-15, swap volume is mounted properly on boot. "lvm2-activation-generator: lvmconfig failed" is still produced on boot, but only once and seems not to break anything. Thanks.
Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted
Package: lvm2 Version: 2.03.01-2 Severity: grave On two machines running sid I observed errors during the upgrade to 2.03.01-2. One of these machines became practically unusable immediately after the update (disk IO operations became so slow that even closing aptitude took 2 minutes instead usual 3 seconds, I had to reboot it). On second machine I observed the same errors in log, but without the slowdown (maybe because it was RAID-based). After the update, both machines generate errors on boot: Dec 23 15:41:16 sonata lvm2-activation-generator: lvmconfig failed Dec 23 15:41:16 sonata lvm2-activation-generator: Activation generator failed. Dec 23 15:41:16 sonata systemd[547]: /lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1. Additionally, one of the machines is using lvm-based swap partition, which fails since the update: Dec 23 15:42:45 sonata systemd[1]: dev-mapper-sonata\x2dswap.device: Job dev-mapper-sonata\x2dswap.device/start timed out. Dec 23 15:42:45 sonata systemd[1]: Timed out waiting for device /dev/mapper/sonata-swap. Dec 23 15:42:45 sonata systemd[1]: Dependency failed for /dev/mapper/sonata-swap. Dec 23 15:42:45 sonata systemd[1]: Dependency failed for Swap. Dec 23 15:42:45 sonata systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'. Dec 23 15:42:45 sonata systemd[1]: dev-mapper-sonata\x2dswap.swap: Job dev-mapper-sonata\x2dswap.swap/start failed with result 'dependency'. Dec 23 15:42:45 sonata systemd[1]: dev-mapper-sonata\x2dswap.device: Job dev-mapper-sonata\x2dswap.device/start failed with result 'timeout'. Because this error: 1. Repeats on all machines I use. 2. All of which have completely default lvm config. 3. Results in swap being not activated. I set the severity to grave. Log recorded during the update: Dec 23 15:28:02 sonata systemd[1]: Reloading. Dec 23 15:28:02 sonata lvm2-activation-generator: lvmconfig failed Dec 23 15:28:02 sonata lvm2-activation-generator: Activation generator failed. Dec 23 15:28:02 sonata systemd[44153]: /lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1. Dec 23 15:28:02 sonata systemd[1]: Reloading. Dec 23 15:28:02 sonata lvm2-activation-generator: lvmconfig failed Dec 23 15:28:02 sonata lvm2-activation-generator: Activation generator failed. Dec 23 15:28:02 sonata systemd[44169]: /lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1. Dec 23 15:28:03 sonata systemd[1]: Reloading. Dec 23 15:28:03 sonata lvm2-activation-generator: lvmconfig failed Dec 23 15:28:03 sonata lvm2-activation-generator: Activation generator failed. Dec 23 15:28:03 sonata systemd[44190]: /lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1. Dec 23 15:28:03 sonata systemd[1]: Reloading. Dec 23 15:28:03 sonata lvm2-activation-generator: lvmconfig failed Dec 23 15:28:03 sonata lvm2-activation-generator: Activation generator failed. Dec 23 15:28:03 sonata systemd[44209]: /lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1. Dec 23 15:28:03 sonata systemd[1]: Reexecuting. Dec 23 15:28:04 sonata systemd[1]: systemd 240 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTIL Dec 23 15:28:04 sonata systemd[1]: Detected architecture x86-64. Dec 23 15:28:04 sonata lvm2-activation-generator: lvmconfig failed Dec 23 15:28:04 sonata lvm2-activation-generator: Activation generator failed. Dec 23 15:28:04 sonata systemd[44271]: /lib/systemd/system-generators/lvm2-activation-generator failed with exit status 1. Dec 23 15:28:04 sonata systemd[1]: lvm2-lvmetad.service: Current command vanished from the unit file, execution of the command list won't be resumed. Dec 23 15:28:04 sonata systemd[1]: lvm2-lvmetad.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until Dec 23 15:28:04 sonata systemd[1]: Stopping LVM event activation on device 8:3... Dec 23 15:28:04 sonata systemd[1]: Stopping Network Time Synchronization... Dec 23 15:28:04 sonata systemd[1]: systemd-timesyncd.service: Succeeded. Dec 23 15:28:04 sonata systemd[1]: Stopped Network Time Synchronization. Dec 23 15:28:04 sonata systemd[1]: Starting Network Time Synchronization... Dec 23 15:28:04 sonata systemd[1]: lvm2-pvscan@8:3.service: Succeeded. Dec 23 15:28:04 sonata systemd[1]: Stopped LVM event activation on device 8:3. Dec 23 15:28:04 sonata systemd[1]: Started Network Time Synchronization. Dec 23 15:28:04 sonata systemd[1]: systemd-journal-flush.service: Succeeded. Dec 23 15:28:04 sonata systemd[1]: Stopped Flush Journal to Persistent Storage. Dec 23 15:28:04 sonata systemd[1]: Stopping Flush Journal to Persistent Storage... Dec 23 15:28:04 sonata systemd-journald[15332]: Journal stopped Dec 23 15:28:04 sona
Bug#910400: mysqli stopped connecting to MySQL servers using caching_sha2_password
Well, the purpose of php-mysql package is to interact with MySQL server. And in order to do that, it has to connect to the server. caching_sha2_password is the default authentication method in MySQL 8.0. MySQL 8.0 is the current GA version. So this package is COMPLETELY unusable, unless someone downgrade MySQL server or change its default security settings. I think this perfectly fits the definition of a grave bug. And a regression. grave makes the package in question unusable or mostly so Are packages not working out-of-the-box after installation the experience Debian wants to provide? On 2018-10-06 06:34, OndÅej Surý wrote: Control: severity -1 important That’s not a grave bug. Please do not abuse severities. Ondřej -- Ondřej Surý On 6 Oct 2018, at 01:23, Piotr Jurkiewicz wrote: Package: php7.3-mysql Version: 7.3.0~rc2-2 Severity: grave After update to 7.3.0~rc2-2 (sid), mysqli extension stopped working. It can't connect to MySQL server, giving the following error message: PHP message: PHP Warning: mysqli::__construct(): The server requested authentication method unknown to the client [caching_sha2_password] It worked before the update (version 7.3.0~alpha3-1, I think). caching_sha2_password is the default authentication method in MySQL 8.0.
Bug#910400: mysqli stopped connecting to MySQL servers using caching_sha2_password
Package: php7.3-mysql Version: 7.3.0~rc2-2 Severity: grave After update to 7.3.0~rc2-2 (sid), mysqli extension stopped working. It can't connect to MySQL server, giving the following error message: PHP message: PHP Warning: mysqli::__construct(): The server requested authentication method unknown to the client [caching_sha2_password] It worked before the update (version 7.3.0~alpha3-1, I think). caching_sha2_password is the default authentication method in MySQL 8.0.
Bug#904720: Lot of cruft installed automatically as dependencies (e.g. Thai fonts, X11 libs)
Package: nfdump Version: 1.6.17-1 Trying to install nfdump on server, I get lot of unwanted packages automatically installed. I believe that X11 rendering libraries or Thai fonts are not needed for running nfdump, are they? These packages are mostly pulled by librrd. --\ Packages to be installed (1) pi nfdump +1,603 kB 1.6.17-1 --\ Packages being automatically installed to satisfy dependencies (18) piA fontconfig +555 kB2.13.0-5 piA fontconfig-config+452 kB2.13.0-5 piA fonts-dejavu-core+3,025 kB 2.37-1 piA libcairo2+1,408 kB 1.15.10-3 piA libdatrie1 +75.8 kB 0.2.12-1 piA libdbi1 +95.2 kB 0.9.0-5 piA libfontconfig1 +528 kB2.13.0-5 piA libfribidi0 +178 kB1.0.5-1 piA libpango-1.0-0 +389 kB1.42.1-2 piA libpangocairo-1.0-0 +101 kB1.42.1-2 piA libpangoft2-1.0-0+136 kB1.42.1-2 piA librrd8 +506 kB1.7.0-1+b2 piA libthai-data +620 kB0.1.27-2 piA libthai0 +96.3 kB 0.1.27-2 piA libxcb-render0 +174 kB1.13-2 piA libxcb-shm0 +119 kB1.13-2 piA libxext6 +127 kB2:1.3.3-1+b2 piA libxrender1 +71.7 kB 1:0.9.10-1
Bug#897943: mkfs.ext4 gets stuck on getrandom() syscall
After upgrading util-linux to version 2.32, mkfs.ext4 blocks just for 2 seconds when CRNG is not fully initialized, what I think is acceptable. Therefore, this bug can be closed. The reason was described by Theodore Y. Ts'o and following comments here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897572#184 This 2-second block can be entirely avoided by providing virtio-rng device to VM, as Theodore Y. Ts'o already wrote: -object rng-random,filename=/dev/urandom,id=rng0 \ -device virtio-rng-pci,rng=rng0 In Debian CONFIG_HW_RANDOM_VIRTIO=m, so 'virtio_rng' needs to be added to initramfs modules (/etc/initramfs-tools/modules) in order to use the virtio-rng device during boot.
Bug#897943: mkfs.ext4 gets stuck on getrandom() syscall
Package: e2fsprogs
Version: 1.44.1-2
Trying to mkfs.ext4 from initramfs (so with klibc) inside QEMU, it gets
stuck on getrandom syscall. Running it with strace:
uname({sysname="Linux", nodename="(none)", ...}) = 0
access("/sys/fs/ext4/features/lazy_itable_init", R_OK) = -1 ENOENT (No
such file or directory)
openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_EXCL) = 3
getuid()= 0
geteuid() = 0
getgid()= 0
getegid() = 0
prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER)
fstat(3, {st_mode=S_IFBLK|0600, st_rdev=makedev(8, 0), ...}) = 0
ioctl(3, BLKDISCARDZEROES, [0]) = 0
pread64(3, "\0\0\10\0\0\0
\0\231\231\1\0q\33\37\0\365\377\7\0\0\0\0\0\2\0\0\0\2\0\0\0"..., 1024,
1024) = 1024
close(3)= 0
access("/var/lib/e2fsprogs", W_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/dev/sda", O_RDWR|O_EXCL) = 3
getuid()= 0
geteuid() = 0
getgid()= 0
getegid() = 0
prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER)
fstat(3, {st_mode=S_IFBLK|0600, st_rdev=makedev(8, 0), ...}) = 0
ioctl(3, BLKDISCARDZEROES, [0]) = 0
ioctl(3, BLKROGET, [0]) = 0
uname({sysname="Linux", nodename="(none)", ...}) = 0
ioctl(3, BLKDISCARD, [0, 16777216]) = 0
write(1, "Discarding device blocks: ", 26Discarding device blocks: ) = 26
write(1, " 4096/2097152", 15 4096/2097152) = 15
write(1, "\10\10\10\10\10\10\10\10\10\10\10\1) = 150\10", 15
ioctl(3, BLKDISCARD, [16777216, 2147483648]) = 0
ioctl(3, BLKDISCARD, [2164260864, 2147483648]) = 0
ioctl(3, BLKDISCARD, [4311744512, 2147483648]) = 0
ioctl(3, BLKDISCARD, [6459228160, 2130706432]) = 0
write(1, " ", 15 ) = 15
write(1, "\10\10\10\10\10\10\10\10\10\10\10\1) = 150\10", 15
write(1, "done"..., 33done
) = 33
pwrite64(3,
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
3072, 1024) = 3072
access("/dev/random", R_OK) = 0
getrandom(
I wasn't experiencing such a behavior one month before, but I don't know
what caused it: kernel update from 4.15 to 4.16 or e2fsprogs update.
Workaround is to run mke2fs with explicitly specified uuid and hash seed:
mkfs.ext4 -U 08365ab2-bf18-43eb-9035-ce947f4a7565 -E hash_seed=08365a
b2-bf18-43eb-9035-ce947f4a7565 /dev/sda
I don't think mke2fs should do blocking random calls. /dev/urandom is
present and works fine (I checked it).
Bug#882201: closed by Gianfranco Costamagna (Re: Source files are included in the package file)
Control: reopen -1 File lists presented by packages.debian.org web interface are outdated. For example they do no contain shell completion files, which are part of the package since 1.1.2-1. Here is the real list of files installed by 1.1.2-3: # dpkg-query -L borgbackup /. /etc /etc/bash_completion.d /etc/bash_completion.d/borg /usr /usr/bin /usr/bin/borg /usr/bin/borgfs /usr/lib /usr/lib/python3 /usr/lib/python3/dist-packages /usr/lib/python3/dist-packages/borg /usr/lib/python3/dist-packages/borg/__init__.py /usr/lib/python3/dist-packages/borg/__main__.py /usr/lib/python3/dist-packages/borg/_chunker.c /usr/lib/python3/dist-packages/borg/_endian.h /usr/lib/python3/dist-packages/borg/_hashindex.c /usr/lib/python3/dist-packages/borg/_version.py /usr/lib/python3/dist-packages/borg/algorithms /usr/lib/python3/dist-packages/borg/algorithms/__init__.py /usr/lib/python3/dist-packages/borg/algorithms/blake2 /usr/lib/python3/dist-packages/borg/algorithms/blake2/COPYING /usr/lib/python3/dist-packages/borg/algorithms/blake2/README.md /usr/lib/python3/dist-packages/borg/algorithms/blake2/blake2-impl.h /usr/lib/python3/dist-packages/borg/algorithms/blake2/blake2.h /usr/lib/python3/dist-packages/borg/algorithms/blake2/blake2b-ref.c /usr/lib/python3/dist-packages/borg/algorithms/blake2-libselect.h /usr/lib/python3/dist-packages/borg/algorithms/checksums.c /usr/lib/python3/dist-packages/borg/algorithms/checksums.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/algorithms/checksums.pyx /usr/lib/python3/dist-packages/borg/algorithms/crc32_clmul.c /usr/lib/python3/dist-packages/borg/algorithms/crc32_dispatch.c /usr/lib/python3/dist-packages/borg/algorithms/crc32_slice_by_8.c /usr/lib/python3/dist-packages/borg/algorithms/xxh64 /usr/lib/python3/dist-packages/borg/algorithms/xxh64/xxhash.c /usr/lib/python3/dist-packages/borg/algorithms/xxh64/xxhash.h /usr/lib/python3/dist-packages/borg/archive.py /usr/lib/python3/dist-packages/borg/archiver.build /usr/lib/python3/dist-packages/borg/archiver.build/.sconsign.dblite /usr/lib/python3/dist-packages/borg/archiver.py /usr/lib/python3/dist-packages/borg/cache.py /usr/lib/python3/dist-packages/borg/cache_sync /usr/lib/python3/dist-packages/borg/cache_sync/cache_sync.c /usr/lib/python3/dist-packages/borg/cache_sync/sysdep.h /usr/lib/python3/dist-packages/borg/cache_sync/unpack.h /usr/lib/python3/dist-packages/borg/cache_sync/unpack_define.h /usr/lib/python3/dist-packages/borg/cache_sync/unpack_template.h /usr/lib/python3/dist-packages/borg/chunker.c /usr/lib/python3/dist-packages/borg/chunker.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/chunker.pyx /usr/lib/python3/dist-packages/borg/compress.c /usr/lib/python3/dist-packages/borg/compress.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/compress.pyx /usr/lib/python3/dist-packages/borg/constants.py /usr/lib/python3/dist-packages/borg/crc32.c /usr/lib/python3/dist-packages/borg/crypto /usr/lib/python3/dist-packages/borg/crypto/__init__.py /usr/lib/python3/dist-packages/borg/crypto/file_integrity.py /usr/lib/python3/dist-packages/borg/crypto/key.py /usr/lib/python3/dist-packages/borg/crypto/keymanager.py /usr/lib/python3/dist-packages/borg/crypto/low_level.c /usr/lib/python3/dist-packages/borg/crypto/low_level.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/crypto/low_level.pyx /usr/lib/python3/dist-packages/borg/crypto/nonces.py /usr/lib/python3/dist-packages/borg/crypto.c /usr/lib/python3/dist-packages/borg/fuse.py /usr/lib/python3/dist-packages/borg/hashindex.c /usr/lib/python3/dist-packages/borg/hashindex.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/hashindex.pyx /usr/lib/python3/dist-packages/borg/helpers.py /usr/lib/python3/dist-packages/borg/item.c /usr/lib/python3/dist-packages/borg/item.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/item.pyx /usr/lib/python3/dist-packages/borg/locking.py /usr/lib/python3/dist-packages/borg/logger.py /usr/lib/python3/dist-packages/borg/lrucache.py /usr/lib/python3/dist-packages/borg/nanorst.py /usr/lib/python3/dist-packages/borg/paperkey.html /usr/lib/python3/dist-packages/borg/patterns.py /usr/lib/python3/dist-packages/borg/platform /usr/lib/python3/dist-packages/borg/platform/__init__.py /usr/lib/python3/dist-packages/borg/platform/base.py /usr/lib/python3/dist-packages/borg/platform/darwin.pyx /usr/lib/python3/dist-packages/borg/platform/freebsd.pyx /usr/lib/python3/dist-packages/borg/platform/linux.c /usr/lib/python3/dist-packages/borg/platform/linux.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/platform/linux.pyx /usr/lib/python3/dist-packages/borg/platform/posix.c /usr/lib/python3/dist-packages/borg/platform/posix.cpython-36m-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/borg/platform/posix.pyx /usr/lib/python3/dist-packages/borg/remote.py /usr/lib/python3/dist-packages/borg/repository.py /usr/lib/python3/dist-packages/borg/selftest.py
Bug#882208: Please enable CONFIG_FW_CFG_SYSFS
Package: linux-image-amd64 Version: 4.13+86 Please consider enabling CONFIG_FW_CFG_SYSFS=m This would build QEMU out-of-band configuration forwarding module. It allows guest OS to read parameters and config files passed from host via QEMU command line. http://www.contrib.andrew.cmu.edu/~somlo/QEMU_fw_cfg/ https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg
Bug#882205: Please make openvswitch-switch recommended instead hard dependency
Package: mininet Open vSwitch is not necessary to run Mininet. There are many use cases for Mininet without Open vSwitch. For example we are using it to orchestrate nodes running Click Modular Router or in-kernel IP forwarding (like in examples/linuxrouter.py). Changing openvswitch-switch to Recommends instead Depends would allow us to build smaller VM images and avoid manual disabling of ovs daemons after installation. It would still be installed by default for most users who do not use additional --no-install-recommends flag.
Bug#882201: Source files are included in the package file
Package: borgbackup
Version: 1.1.2-3
Source files *.{c,h,pyx} and directories are included in the .deb
package file, what inflates Installed Size approximately 6 times.
Bug#831858: found 831858 in 0.8.4-1
I also encountered this bug on Stretch with aptitude 0.8.4-1. In my case it can be reproduced even simpler: 1. Install some package which has a dependency with apt-get, for example: $ apt-get install apt-src Entry in /var/apt/history.log: Start-Date: 2017-01-31 19:51:29 Commandline: apt-get install apt-src Install: libapt-pkg-perl:amd64 (0.1.30, automatic), apt-src:amd64 (0.25.2) End-Date: 2017-01-31 19:51:30 Note that package libapt-pkg-perl was installed automatically as a dependency. This package is also listed in /var/lib/apt/extended_states (last changed 2017-01-31 19:51:29): ... Package: libsdl1.2debian Architecture: amd64 Auto-Installed: 1 Package: libapt-pkg-perl Architecture: amd64 Auto-Installed: 1 --EOF-- 2. Start aptitude. You don't even need to do anything. Aptitude on its start overwrites /var/lib/apt/extended_states file, removing the entry for libapt-pkg-perl package: File /var/lib/apt/extended_states (last changed 2017-01-31 19:59:35): ... Package: libsdl1.2debian Architecture: amd64 Auto-Installed: 1 --EOF-- If there are more than one auto packages installed recently with apt-get, aptitude removes entries for all of them. So it is not the case that aptitude removes only the last entry, but all entries which were installed with apt-get since last aptitude run.
Bug#846145: Wrong path to php7.0-fpm.sock in sites-available/default
Package: nginx-common Version: 1.10.2-2 PHP snippet in sites-available/default points to: fastcgi_pass unix:/var/run/php7.0-fpm.sock; However, php7.0-fpm package (Debian Stretch) places this socket in: /var/run/php/php7.0-fpm.sock (notice additional 'php' directory)
Bug#767448: No way to override settings from /usr/share/initramfs-tools/conf-hooks.d/*
The UMASK variable is *documented* as affecting only the permissions for the initramfs image (which it doesn't seem to do reliably!) but it also affects the permissions for the files inside the initramfs. > When dropbear is used in the initramfs, the host private key must be kept secret and so the initramfs image must not be world-readable. But most of the files installed in the initramfs can be world-readable. Is that what you want to change? No. I wasn't even aware that UMASK also affects the permission of files inside initramfs (as this is undocumented, as you said). My setup is the following: Machine A with Debian boots from the network. Its /boot directory resides on machine B, which is simply a PXE server for machine A. /boot directory is mounted on machine A using sshfs. That way, on each update of machine A, kernel image and initramfs file are automatically transferred to machine B. The problem is that tftpd on machine B has compiled-in limitation which allows only publicly readable files (o+r) to be served via TFTP. Because dropbear package sets UMASK variable to 0077, (re)created initramfs file has no o+r permission. That means that it cannot be served by tftpd. So basically machine A won't boot on next reboot after update. That's why I must override UMASK for (re)created initramfs. Another solution for my problem would be to retain permission of existing initramfs file during initramfs regeneration and use UMASK only when initramfs file does not exist.
Bug#806260: Unnecessary period on the end of systemd service description in pppd-dns.service
Package: ppp Version: 2.4.6-3.1 Severity: minor By convention systemd service descriptions should not end with a period, because systemd adds period on its own. Now, log messages for this service ends with doubled periods, what is inconsistent with the rest of system and suggests that this service is waiting for something: systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.. Suggested fix: In file pppd-dns.service change: [Unit] Description=Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. to: [Unit] Description=Restore /etc/resolv.conf if the system crashed before the ppp link was shut down
Bug#767448: No way to override settings from /usr/share/initramfs-tools/conf-hooks.d/*
Package: initramfs-tools There is no way for user to override settings from /usr/share/initramfs-tools/conf-hooks.d. For example, dropbear package in file /usr/.../conf-hooks.d/dropbear sets UMASK variable to 0077. User cannot override this with his own setting in /etc. The only way to do that is to edit /usr/.../conf-hooks.d/dropbear file directly and change UMASK. However, such change will be of course overwritten on a next update of dropbear package. In my opinion, user-provided settings from /etc/* should have priority over package-provided settings form /usr/*. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742209: gnome: Gnome does not show icons on desktop
Source: gnome Severity: important I am testing the last Jessie installer. I have found that gnome-shell session as well as gnome-flashback session do not show icons on desktop (xfce session shows icons). I have not found any option to turn it on/off in control panel, so I assume that it is some kind of bug. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742212: synaptic: Quick search field is missing
Package: synaptic Version: 0.80.4 Severity: important As in topic, on the present Jessie preview quick search field in toolbar is missing. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-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 Versions of packages synaptic depends on: ii hicolor-icon-theme 0.13-1 ii libapt-inst1.5 0.9.15.5+b1 ii libapt-pkg4.12 0.9.15.5+b1 ii libatk1.0-0 2.10.0-2 ii libc62.18-4 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libept1.4.12 1.0.12 ii libgcc1 1:4.8.2-16 ii libgdk-pixbuf2.0-0 2.30.6-1 ii libglib2.0-0 2.38.2-5 ii libgtk-3-0 3.10.7-1 ii libpango-1.0-0 1.36.2-2 ii libpangocairo-1.0-0 1.36.2-2 ii libstdc++6 4.8.2-16 ii libvte-2.90-91:0.34.9-1 ii libx11-6 2:1.6.2-1 ii libxapian22 1.2.17-1 ii libxext6 2:1.3.2-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages synaptic recommends: ii libgtk2-perl 2:1.249-1 ii policykit-10.105-4 ii rarian-compat 0.8.1-5 Versions of packages synaptic suggests: ii apt-xapian-index 0.46 pn deborphan pn dwww pn menu pn software-properties-gtk ii tasksel 3.20 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742205: gnome-session-flashback: Overdependency: gnome-session-flashback installation should not lead to the installation of gnome-shell
Package: gnome-session-flashback Version: 3.8.0-2 Severity: important When user installs gnome-session-flashback in a clean system it leads to the installation of gnome-shell and a lot of its dependencies. When user explicitly install flashback session it means the he does not want to use gnome-shell and does not want to install gnome-shell session but only gnome-flashback session. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-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 Versions of packages gnome-session-flashback depends on: ii gnome-panel3.8.0-2 ii gnome-session-bin 3.8.4-3 ii gnome-session-common 3.8.4-3 ii gnome-settings-daemon 3.8.5-2 ii metacity 1:2.34.13-1 ii nautilus 3.8.2-2 ii notification-daemon0.7.6-1 ii policykit-1-gnome 0.105-2 Versions of packages gnome-session-flashback recommends: pn gnome-power-manager pn gnome-screensaver Versions of packages gnome-session-flashback suggests: pn desktop-base pn gnome-keyring pn gnome-user-guide -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
