Your message dated Thu, 31 Oct 2013 16:48:20 +0000 with message-id <[email protected]> and subject line Bug#727682: fixed in bilibop 0.4.19 has caused the Debian Bug report #727682, regarding bilibop-rules: Fails to configure: lsbilibop calls udevadm in an unsupported way to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 727682: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727682 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bilibop-rules Version: 0.4.17 Severity: serious Dear Maintainer, I've just dist-upgraded my Debian armhf running Toshiba AC100 (an ARM-based netbook originally running Android) from Wheezy to Jessie. As it currently runs of an SD card, installing bilibop sounds like a good idea. But bilibop-rules fails to install during configure phase. I've added a "set -x" to the package's postinst script to see where it exactly fails: + [ false = false ] + CUSTOM_RULES=false + HELPER=bilibop_rules_generator + [ -f /etc/udev/rules.d/66-bilibop.rules ] + db_get bilibop-rules/bilibop_rules_generator/customize + _db_cmd GET bilibop-rules/bilibop_rules_generator/customize + _db_internal_IFS= + IFS= + printf %s\n GET bilibop-rules/bilibop_rules_generator/customize + IFS= + IFS= read -r _db_internal_line + RET=false + return 0 + [ false = true ] + [ false = true ] + lsbilibop -l Usage: udevadm info OPTIONS --query=<type> query device information: name name of device node symlink pointing to node path sys device path property the device properties all all values --path=<syspath> sys device path used for query or attribute walk --name=<name> node or symlink name used for query or attribute walk --root prepend dev directory to path names --attribute-walk print all key matches while walking along the chain of parent devices --device-id-of-file=<file> print major:minor of device containing this file --export export key/value pairs --export-prefix export the key name with a prefix --export-db export the content of the udev database --cleanup-db cleanup the udev database --help + BILIBOP_LIST= dpkg: error processing bilibop-rules (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of bilibop: bilibop depends on bilibop-rules (= 0.4.17); however: Package bilibop-rules is not configured yet. /bin/lsbilibop seems to call udevadm in line 44 as follows: udev_root="$(udevadm info --root)" But calling "udevadm info --root" manually on the commandline throws exactly the above error message. According to the man-page, the --root option is only thought as additional option for two query types: --root Print absolute paths in name or symlink query. So I guess, some more parameters are necessary to get it working again. I'm just not sure which. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: armhf (armv7l) Kernel: Linux 2.6.38-ac2-ac100 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bilibop-rules depends on: ii bilibop-common 0.4.17 ii debconf [debconf-2.0] 1.5.51 ii initramfs-tools 0.114 ii initscripts 2.88dsf-43 Versions of packages bilibop-rules recommends: pn grub-common <none> pn lvm2 <none> pn udisks <none> Versions of packages bilibop-rules suggests: ii bilibop-lockfs 0.4.17 pn cryptsetup <none> pn grub-coreboot | grub-efi-amd64 | grub-efi-ia32 | grub-ieee1275 | <none> ii pmount 0.9.23-2 pn policykit-1 <none> -- debconf information: bilibop-rules/belongs_to_floppy_group/custom_rules_error: bilibop-rules/make_unpersistent_rules: keep bilibop-rules/belongs_to_floppy_group/internal_error: bilibop-rules/grub_device_map_manager: keep bilibop-rules/bilibop_rules_generator/bad_options: bilibop-rules/physical_volumes_filter/obtain_device_list_from_udev: bilibop-rules/bilibop_rules_generator/options: * bilibop-rules/on-live-system: false bilibop-rules/physical_volumes_filter/system-only: false bilibop-rules/physical_volumes_filter/warning: bilibop-rules/bilibop_rules_generator/customize: false bilibop-rules/physical_volumes_filter/filter: bilibop-rules/bilibop_rules_generator/overwrite: keep
--- End Message ---
--- Begin Message ---Source: bilibop Source-Version: 0.4.19 We believe that the bug you reported is fixed in the latest version of bilibop, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yann Amar <[email protected]> (supplier of updated bilibop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 25 Oct 2013 13:46:29 +0000 Source: bilibop Binary: bilibop bilibop-common bilibop-lockfs bilibop-rules bilibop-udev Architecture: source amd64 Version: 0.4.19 Distribution: unstable Urgency: high Maintainer: Yann Amar <[email protected]> Changed-By: Yann Amar <[email protected]> Description: bilibop - run Debian GNU/Linux from external media - metapackage bilibop-common - shell functions for bilibop scripts bilibop-lockfs - lock filesystems and write changes into RAM bilibop-rules - device management rules for OS running from external media bilibop-udev - minimal udev rule for Debian GNU/Linux running from external medi Closes: 727682 Changes: bilibop (0.4.19) unstable; urgency=high . * bilibop-lockfs: - Modify parse_and_modify_fstab() in lockfs.sh: skip 'rbind' mounts as well as 'bind' mounts. - Modify lockfs_mount_helper script: set -e. - Simplify lockfs_mount_helper; especially, rewrite the mount_fallback() function to parse the arguments provided by the parent process (mount) 'as is', and do not 'exec mount', but just 'mount' instead, to be able to exit with a code != 0 when mount_fallback() is called. - Modify lockfs_mount_helper and the local-bottom initramfs script to parse options (BILIBOP_LOCKFS_SIZE and boot commandline) and set the size of the tmpfs in a better and more reliable way (use regex instead of glob patterns). - Add new function 'is_write_protected()' in lockfs.sh (takes into account sd, mmcblk and mspblk devices) and call it from the local-bottom initramfs script. - Modify init-top initramfs script: in the case any drive is physically locked, override BILIBOP_LOCKFS and BILIBOP_LOCKFS_POLICY. . * bilibop-rules: Fix a bug in lsbilibop: since udev is now a part of systemd, 'udevadm info --root' no more works to query the udev_root value; so query it directly from udev.conf instead. (Closes: #727682) Checksums-Sha1: 2c645cf0201e3ea0d415919ada42b71db0727f20 1683 bilibop_0.4.19.dsc 7315acb78ce84c31617f5f096c7b4808441ffe3e 128604 bilibop_0.4.19.tar.gz 31a7b6426340e042a11813947941800bb934ee34 11076 bilibop_0.4.19_amd64.deb a6191e2f7f96acb02d15037e0fe15ae872857331 63038 bilibop-common_0.4.19_amd64.deb 2b484f7703896f72e661fe930c73204ed716c21d 39872 bilibop-lockfs_0.4.19_amd64.deb 57f2461ef79ec6bb0492b9c69a8476337dbc03f7 51926 bilibop-rules_0.4.19_amd64.deb be2d96fa326eba2fea45a8264123a8dbef8f1307 13140 bilibop-udev_0.4.19_amd64.deb Checksums-Sha256: 4e11e993a45ace307e98132b4d6720dd5f427952061dadaa70b9b34ba5eebf91 1683 bilibop_0.4.19.dsc babfde3646984e034fbeb0c71c3b9960b6e5e6f7b0869602de1dac135b30fe3a 128604 bilibop_0.4.19.tar.gz 9c4d8370016d50517d3bd3ed01ac9cd27141abc7c9d2e183e1c1d71231bbedc8 11076 bilibop_0.4.19_amd64.deb 2aa522eb9b0734aefb54b5d2a2d93c623480a6972a264c39619072bde85237a5 63038 bilibop-common_0.4.19_amd64.deb 55337ced1bd8b3727fddd9d9ab53d969290a756cc69d1a4df30522bbc0a6f3c9 39872 bilibop-lockfs_0.4.19_amd64.deb 2d1514456708a9b25e52d598936b931dabd459f74267387cec1a6ea4a8599a78 51926 bilibop-rules_0.4.19_amd64.deb 2160ee03b074e9f00de00b193ee7466e8f29d656a0da28f4a019a653c84c7f2f 13140 bilibop-udev_0.4.19_amd64.deb Files: 0aca7f0acfd4ce9f9229eaa2cf5ccb9b 1683 admin optional bilibop_0.4.19.dsc e1d0baf9dffe87d6554cbcd2f69210c1 128604 admin optional bilibop_0.4.19.tar.gz 419a1bef0a79ec2d422c9499c9bdc578 11076 metapackages extra bilibop_0.4.19_amd64.deb 15a2453e4d7ca0d10ff5bdcf36ed9a21 63038 admin optional bilibop-common_0.4.19_amd64.deb ddb554999bb092753f810189fbc6e831 39872 admin optional bilibop-lockfs_0.4.19_amd64.deb f0fe5b57ea65c991a43911ab6fa20b84 51926 admin optional bilibop-rules_0.4.19_amd64.deb c74e820df7a5182316875835484b12ce 13140 admin optional bilibop-udev_0.4.19_amd64.deb -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJScoaZAAoJELrOFdKldJj/gUoP/AkKSqbZRgVyPVcHfrHRbASh +r4pFIKpYorpvyxJ8rKTIDHOxNuPZUJUFAAlPhN6ayh+mzoO43aLn4BSOu3s/Bsa ykJItYMURXAJVH4kBvZKUH4uPArR2sfft0yLU4ZZ4uKcBLxP5eO+vIp2Hj9hMcGh H+jfBdq9qPgcukHHj1f9UHWqNb84LVRPh3qw9NtJSnf7a2if4fpvE7pBlJ+GQE8H pwDqUr361awzXdDGISF8v0lGKqdMUpNtYuLuxY0mtpRCJEtMNHh25xvzoHHSLED2 dJPYkrPCP5NlGrCQT6svLfmOWU5avDsBb/EpLpJnMdx3u+eBKnD0TBRU6HEnvjDV AqKc5/0WKW3II4m+4kujRpVJJnTXNBCCoo+5rd5AKNgFgwz/tgNxVDz8TzSJSnT2 odcHze5vHcHa9gkQzVzYyOsWs2eNFm2JddvCNE/7Pvv1s4Y8/A9WpCyiX4ZJ1J6L cTFyFwkQeHKlIbPVnOv1gzxt33T+dGkE/atu+LtHQ9xyOhprW7MrJ23Ob183F6Hx KgRQ3FuQIj0DHXhYayRAaPJ650vTPxgtoCetfVuQGarCibzHrokELJoiDlLh5mSI uyK96VUqpn0o5njAnFRQIeFl1xIntya/Vyc5u4Hxic4v+/Btm3LVewQjN6prdROM q3+4egCwnEdHD2xQmMEx =DeA2 -----END PGP SIGNATURE-----
--- End Message ---
