Bug#972580: dpkg-query throw error when asking for field "source:Upstream-Version"

Package: dpkg Version: 1.19.7 Command example throwing the error: dpkg-query --show --showformat '${Package} ${source:Upstream-Version}\n' s* Error message: dpkg-query: error: version '' has bad syntax: version string is empty >From the manual per 1.19.7 / 2019-06-03 "source:Upstream-Version

Bug#952508: Cannot call external script in rule CMD option

Yes, exec bit is set and script also tested directly in console. How does your cmd option lines look like in the config-file? Now I start to suspect that not even the default cmd line "logger..." is running. I don't see the message in syslog it should create. Enabled debug in config-file and rest

Bug#952512: vsftpd stalls when host has been blocked by PAM

Package: vsftpd Version: 3.0.3-12 Description: When an authentication is blocked by PAM (module: pam_abl.so) because of the remote-host is blocked the vsftpd service is stalled and doesn't accept connection until service is restarted (reload is not enough). I guess vsftpd have a bug when it gets t

Bug#952508: Cannot call external script in rule CMD option

Package: libpam-abl Version: 0.6.0-5 Description: I cannot run a simple shell script: I have the following options in my "/etc/security/pam_abl.conf": user_rule=*:3/1h host_rule=*:5/5h host_purge=1d user_purge=1d limits=100-300 user_db=/var/lib/abl/users.db host_db=/var/lib/abl/hosts

Bug#952421: Cannot use PAM modules which call subprocess e.g. pam_exec

Package: vsftpd Version: version 3.0.3 Description: It seems vsftpd blocks/hang if you use a PAM module which call a subprocess like pam_exec. See this thread on StackExchange, which also claim the CentOS package have fixed the bug. https://askubuntu.com/questions/406486/vsftpd-hanging-when-using-

Bug#951480: Misleading status message when lock password with "--lock"

Package: passwd Version: 1:4.5-1.1 When using the option "--lock", passwd will print the following status message: "passwd: password expiry information changed." I assume the "--lock" option only lock the password (sing !) and neither change the expiration date of the account or any of the other

Bug#950577: And "allow_writeable_chroot=YES|NO"

Can't dind "allow_writeable_chroot" in the manual either.

Bug#950584: whitespace break "/etc/vsftpd.conf"

Package: vsftpd Version: 3.0.3-12 If a whitespace surfix a option in the "/etc/vsftpd.conf" file, the service fail to start. E.g "guest_enable=YES " I guess it depends of the eyes if this is a bug or a feature-request. But I just wasted more than an hour because of this, so at the moment I fee

Bug#950577: Missing option in man (utf8_filesystem)

Package: vsftpd Version: 3.0.3-12 The option "utf8_filesystem" in "/etc/vsftpd.conf" is not listed in the manual. I might be it's rather self-description, but the default value is not, neither if the option is supported at all. One might think the remarked option in the configfil is simple a le

Bug#948692: "postconf -d maillog_file" doesn't show actual value

Package: postfix Version: 3.4.7 Value in my main.cf: maillog_file = /var/log/postfix.log Result of "postconf -d | grep log_file": maillog_file = maillog_file_compressor = gzip maillog_file_prefixes = /var, /dev/stdout maillog_file_rotate_suffix = %Y%M%d-%H%M%S Content in master.cf postlo

Bug#948308: closed by Andreas Metzler (Re: Bug#948308: Macro AUTH_SERVER_ALLOW_NOTLS_PASSWORDS ignore true/false)

But I would expect "AUTH_SERVER_ALLOW_NOTLS_PASSWORDS = False" would disable it. What I'm trying to say is that whatever value you insert after the "=" is ignored. -Original Message- From: Debian Bug Tracking System [mailto:ow...@bugs.debian.org] Sent: 7. ja

Bug#948308: Macro AUTH_SERVER_ALLOW_NOTLS_PASSWORDS ignore true/false

Package: exim4-daemon-heavy Version: 4.92-8+deb10u3 I've put the following in macro in "/etc/exim4/conf.d/main/000_localmacros": It seem the activation on this macro is rather inconsistent: "AUTH_SERVER_ALLOW_NOTLS_PASSWORDS" > error "AUTH_SERVER_ALLOW_NOTLS_PASSWORDS=" > OK "AUTH_SERVER_ALL

Bug#936098: Buster test, error with fuse installing qemu-kvm

Package: qemu-kvm Version: 1:3.1+dfsg-8 Error: Setting up qemu-system-gui (1:3.1+dfsg-8) ... Processing triggers for systemd (242-4) ... Processing triggers for man-db (2.8.6.1-1) ... Processing triggers for libc-bin (2.28-10) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.1+d

Bug#934070: Info received (Bug#934070 closed by Michael Tokarev (Re: Bug#934070: No support for HyperV synIC in machine type > pc-i440fx-3.0))

I withdraw my last mail...I've become wiser since! :-P I was convinced I was using the correct values in my Virt XML, but I wasn't. The one listed on the linked bugzilla thread is of course the correct ones. Sorry for the noise. On Thu, Aug 8, 2019 at 5:42 PM Debian Bug Tracking System < ow...@bu

Bug#934070: closed by Michael Tokarev (Re: Bug#934070: No support for HyperV synIC in machine type > pc-i440fx-3.0)

message then please contact Michael Tokarev < > m...@tls.msk.ru> by > replying to this email. > > > -- > 934070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934070 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > ---

Bug#934070: No support for HyperV synIC in machine type > pc-i440fx-3.0

Package: qemu-kvm Version: 1:3.1+dfsg-7 (QEMU 3.1.0 / Kernel 4.19) Running Windows 10 guest build >= 1803 will give high host CPU usage (even though it's close to null in client) if you don't enable HyperV synIC which can i.a. be done in Virt XML: * * But it seem only older

Bug#929508: ...and no model info the the actual LV where it would make sense

But It would make a lot of sense to assign a model value for LV device itself, but this is omitted! E.g. "LVM LV"

Bug#929508: lsblk doesn't show correct model when disk is converted to LVM Physical Volume

the model property. It's just wrong! Best regards Brian Wengel Denmark

Bug#925182: Feature request: Support for QEMU Virtio driver for CD-ROM

Package: debian-installer Version: debian-testing-amd64-DVD-1.iso, from 2019-03-16 When installing Debian as a guest in KVM/QEMU assigning the ISO to a CD-ROM using Virtio or Virtio-SCSI as the bus type the debian-installer cannot see the CD-ROM drive and ask for drivers. I assume the Virtio dri

Bug#925105: closed by Steve McIntyre (Re: Bug#925105: CD-ROM is default repository, not mirror)

gs.debian.org with problems > > > > -- Forwarded message -- > From: Steve McIntyre > To: Brian Wengel , 925105-d...@bugs.debian.org > Cc: > Bcc: > Date: Wed, 20 Mar 2019 16:38:52 + > Subject: Re: Bug#925105: CD-ROM is default repository, not

Bug#925105: CD-ROM is default repository, not mirror

Package: debian-installer Version: debian-testing-amd64-DVD-1.iso, from 2019-03-16 After a clean installation this in the content of the sources.list: # deb cdrom:[Debian GNU/Linux testing _Buster_ - Official Snapshot amd64 DVD Binary-1 20190311-05:00]/ buster contrib main deb cdrom:[Debian GN

Bug#924760: logfiles...

37 PM Samuel Thibault wrote: > Brian Wengel, le dim. 17 mars 2019 22:19:57 +0100, a ecrit: > > The problem seem to be related to XFS filesystem (of the root partition). > > I hereby attach syslog and partman from the installation. > > Mmm, nothing was attached? > > Sa

Bug#924760: logfiles...

The problem seem to be related to XFS filesystem (of the root partition). I hereby attach syslog and partman from the installation.

Bug#924760: Grub is extremely picky in regards to partition

, Mar 17, 2019 at 11:50 AM Samuel Thibault wrote: > Control: tags -1 + moreinfo > > Hello, > > It is hard to understand what issue exactly you had, so we can only try > to guess... > > Brian Wengel, le dim. 17 mars 2019 01:52:17 +0100, a ecrit: > > I hope the in

Bug#924760: Grub is extremely picky in regards to partition

Package: debian-installer Version: Buster, debian-testing-amd64-DVD-1.iso, downloaded 2019-03-16 I hope the installer could be a little more flexible in regards to EFI partition, or is it because it require a SWAP partition, haven't been able to point down the problem. Can only make a successful

Bug#924730: "No kernel modules were found" using the direct online installer (virsh)

Package: debian-installer Version: From testing, http://httpredir.debian.org/debian/dists/buster/main/installer-amd64/ Installing Debian 10 as KVM/QEMU guest, host Debian 9. Virsh-install command: SCIO virt-install \ --virt-type kvm \ --name "Debian10" \ --vcpus 2 \ --memory 2048 \ --boot uefi \

Bug#924699: su root, doesn't have /usr/sbin/ in path

Well, it seems using "su root" doesn't give you a root session with /usr/sbin/ included in the path. Just tested this in Debian 9, it works in 9.

Bug#924699: CANCEL / REMOVE THIS BUG-REPORT

Sorry, my mistake! It's actually the same design in Debian 9 (how do you remove a bug? Couldn't find anything about it on https://wiki.debian.org/HowtoUseBTS and https://www.debian.org/Bugs/Reporting) smime.p7s Description: S/MIME cryptographic signature

Bug#924699: Additinal info

I only get this problem when logon by the ”normal” user I’ve created in the installer doing install. If I do a “su root” the /usr/sbin is not included in the path either. It works fine if I logon specific with root I found this in /etc/profile if [ "`id -u`" -eq 0 ]; then PATH="/usr/lo

Bug#924699: installer doesn't include "/usr/sbin/" in the PATH environment

Package: debian buster installer (debian-testing-amd64-DVD-1.iso, 2019-03-16) I assume it's not on purpose not to include "/usr/sbin/" in the PATH. (I assume it's the installer that setup the path?) On my new installed Debian Buster directly from DVD iso: /# echo $PATH */usr/local/bin:/usr/bin:/

Bug#917051: Debian test (10) installer, storage issues

Package: installer (debian-testing-amd64-DVD-1.iso 2018-12-17) Version: test I experience two issues in regards to the Detect disk and Modify partitions parts of the installer. I have an Samsung NVMe PM