Your message dated Wed, 22 Jul 2015 10:35:25 +0000 with message-id <[email protected]> and subject line Bug#773229: fixed in partman-base 187 has caused the Debian Bug report #773229, regarding partman-base: partitioning should not offer emmc boot0, boot1 or rpmb partitions as possible installation targets 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.) -- 773229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773229 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: partman-base Version: 180 Severity: normal I have an ARM board (Nvidia Jetson TK-1) which includes an on board eMMC. When installing the list of devices to select for installation partitioning included mmcblk1{boot0,boot1,rpmb}. (RPMB == Replay Protected Memory Block). These are not normal partitions and should not be included. They are small (4M) and have special hardware properties which makes them unsuitable for use. [0] has a reasonable description of what they are, suffice it to say that they are magic and shouldn't be messed with without care. They may not even be writable via normal means. [1] has some more background. lsblk says the following. sda is a SATA drive, mmcblk0 is a normal removable SD card (where my install actually lives) and mmcblk1 is the one with the magic partitions, which is soldered onto the board. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 243M 0 part ├─sda2 8:2 0 462.7G 0 part ├─sda3 8:3 0 1K 0 part └─sda5 8:5 0 2.9G 0 part mmcblk1rpmb 179:1024 0 4M 0 disk mmcblk1boot0 179:512 0 4M 1 disk mmcblk1boot1 179:768 0 4M 1 disk mmcblk0 179:0 0 14.5G 0 disk ├─mmcblk0p1 179:1 0 243M 0 part /boot ├─mmcblk0p2 179:2 0 13.6G 0 part / ├─mmcblk0p3 179:3 0 1K 0 part └─mmcblk0p5 179:5 0 674M 0 part [SWAP] mmcblk1 179:256 0 14.7G 0 disk ├─mmcblk1p1 179:257 0 4G 0 part ├─mmcblk1p2 179:258 0 4M 0 part ├─mmcblk1p3 179:259 0 64M 0 part ├─mmcblk1p4 179:260 0 4M 0 part ├─mmcblk1p5 179:261 0 4M 0 part ├─mmcblk1p6 179:262 0 4M 0 part ├─mmcblk1p7 179:263 0 4M 0 part └─mmcblk1p8 179:264 0 10.6G 0 part I'm a bit confused why boot0/1 show up since parted already filters read only devices (in parted_devices.c:process_device). I'm not sure how to identify these magic devices other than by name. Ian. [0] http://www.ebv.com/fileadmin/design_solutions/php/download.php?path=fileadmin%2Fproducts%2FEBVuniversity%2F120912_Micron_e.MMC%2F120912_mic_emmc_Partitioning.pdf [1] https://dev-nell.com/rpmb-emmc-errors-under-linux.html -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---Source: partman-base Source-Version: 187 We believe that the bug you reported is fixed in the latest version of partman-base, 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. Christian Perrier <[email protected]> (supplier of updated partman-base 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: SHA256 Format: 1.8 Date: Wed, 22 Jul 2015 11:05:28 +0200 Source: partman-base Binary: partman-base partman-utils Architecture: source i386 Version: 187 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team <[email protected]> Changed-By: Christian Perrier <[email protected]> Description: partman-base - Partition the storage devices (partman) (udeb) partman-utils - Utilities related to partitioning (udeb) Closes: 773229 Changes: partman-base (187) unstable; urgency=medium . [ Philip Hands ] * Do not list /dev/mmcblk.(rpmb|boot.) devices, as they cannot be usefully partitioned (Closes: #773229) Prompted by a patch from Tsung-Han Lin <[email protected]> . [ Updated translations ] * Turkish (tr.po) by Mert Dirik Checksums-Sha1: ca4735effb05629bc929f5975edac62f403229c8 1843 partman-base_187.dsc a46cfacc1ee047df43fa18b05e9de81e865f3cc3 173584 partman-base_187.tar.xz 44aa1f4b045dcfd20c9020607ab36828bbeea068 156096 partman-base_187_i386.udeb 92a97749df9c0a0ebeeb70454813acfc9f85f8a0 3296 partman-utils_187_i386.udeb Checksums-Sha256: 9ddc86761c29a157d518e332f5894460f7937c91ec7be33372fa1ca9258bb604 1843 partman-base_187.dsc ccff3eec8f3056a0c8b928aa6c85efe14f7decd2e0753dc2166d89cd344fb4f7 173584 partman-base_187.tar.xz 17c89ef7d9888eb865bae58be65a938b3624f129c1f9a5e70b7e037d5a587c9f 156096 partman-base_187_i386.udeb 53bd9fc0d77c51a23cd249877e3320923c7cf5759731e232036487924275563b 3296 partman-utils_187_i386.udeb Files: 1489b0a82eaa05ab3ad9524a108256d4 1843 debian-installer standard partman-base_187.dsc f4a4ffa3b7242251b1a75acfb976aca8 173584 debian-installer standard partman-base_187.tar.xz f7efc7000c7301d1d50c7292e62e6b77 156096 debian-installer standard partman-base_187_i386.udeb b81271d5d7a528b1d1168975026c73e1 3296 debian-installer extra partman-utils_187_i386.udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJVr25AAAoJEIcvcCxNbiWoQlMQAMaY96XFJmk8sbG+pWcZR5xX Q21KehEcCMrMWPkMrqW3Ta88bIY1ZrLV2dmaeixB6EW3ST05meHHLG1limy5VTKc QZDpHz1FlWhXV8/5SUk1gdskTZipiXW5jUtPZz3VxJfaf9a4ntbobC2O3BGS2nEB Z1YQjuwNDxEI8c9PCtCERz4IwGUGY6fKB7pTu3OgBDm3S9VPToqWXswUehFjb5pl UMYGNZAWFfbEMjtF2FZLr8zjm0zsViAJ3I5DTd5l8q6vL6hxmSmm7aE3iSBFFs4i gfF39ml3pEBGPUyvqr/7l5ag95NByE5w3XM67LAHLGR4LvwS/mWpHM8Na82VpEVd GTOrxEBLIVeAoX0148+bghAxo9iMAwp4wzy9VZMQXqwKluQh56tu1V1orRLvpKTT ZDeVROw7WfJIffWzzfxa2cq6t5oRCdIbbzmJlsA0lr7zuzKutzOMejJkI9iF7mus XfnKmVlvV1USfFG3iYiBjzcc60MhhQGxA5BwYrU4bDv0sadYzwkO0qExEno1S9eF sZnWY+pKlSBOi1F1ocBIcjbztqG12KUnSjXNA9nlJJnrgDm9vpJwLMERQKsI7e+6 lOpQhLqIfdd060scRxFuHW5WYpHvClo1Wi94XK2ZkZ8NNrN8Om4gvkZdIGoifoGv 2MmxeKzaExpVP/L7Bqqa =mh5U -----END PGP SIGNATURE-----
--- End Message ---
