partman-md_89_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Dec 2018 14:24:27 +0100 Source: partman-md Binary: partman-md Architecture: source Version: 89 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Description: partman-md - Add to partman support for MD (udeb) Closes: 838503 Changes: partman-md (89) unstable; urgency=medium . * Team upload . [ Steve McIntyre ] * When we create a new RAID1/5/6/10 array , start it syncing at the minimum speed allowed by the system. If we let it run at full speed, that will just slow the installation down while we're installing packages etc. There's nothing to protect at this point anyway. Closes: #838503 . [ Holger Wansing ] * Remove trailing whitespaces from changelog file, to fix lintian tag. Checksums-Sha1: 51185483f5b8e7542d4bcbb57a919396ae302272 1708 partman-md_89.dsc 141574f698bd2c3d8976f3c3716b18f735ac675d 182088 partman-md_89.tar.xz f93181666366eaf2c39fba3d841a9f1961b7eea0 5267 partman-md_89_amd64.buildinfo Checksums-Sha256: e6c8a298356a094730224d2c327df131f8551241cfa19cda268162bfbfcb9f4a 1708 partman-md_89.dsc de5925c525b84f355c4826f19a03d79988457735289e95ab46dfcb02246ffb42 182088 partman-md_89.tar.xz bc8128c1d3c9305c525dddae7ba261bd6dcb1a5dbed00c0ca73a921c44dfcec6 5267 partman-md_89_amd64.buildinfo Files: d4ff1b4d7f0b88286a441cb554715981 1708 debian-installer standard partman-md_89.dsc bda0f6339b205e512a48c99f6c5ea3ef 182088 debian-installer standard partman-md_89.tar.xz 3a2cc47b4f5ebafa030ef32d4307fa95 5267 debian-installer standard partman-md_89_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlwg30sVHGh3YW5zaW5n QG1haWxib3gub3JnAAoJEFnxh8oVbrB2afMP/j+bECmGLsOEjArPn4isZq7DBzuH X1Gq1JqT6+4oNhMZEEw3Oa9aehN3J0zn32OTig5qXI8rot3cRVk6nvUDL3nFfwT3 rW80f744BOYhR1bK4L6WmBtWwPyp1igDB0Yc2kRVE2Rw73ladmrw3Iah1tMSeL+D JsT8SP99DH/QR8kwh15q1sSGOPqiZncwwmYoGHmX9vt1hau8sp9Bhsba8O+WLsVu HYVQ59oCViU0bM4BGqLnpRRgCqe6N08riamw8EMU55GJ4iavnp44/waA1GjwId8Q Ic+wDglSDFl1EcfsOBGynAZOguVe27E2Nu4mFkzoHhBxv8OWm43R7MshuyKqBnfd PKh8dB1M1rnLS9TYbYH41Quo3U9LdWauthqyMTP2RIWKmZOuU23hT22o6bsf0gNU vctla8SWVimU2aulaZ4yzilR5xire2/iMpW7gl6+YHJF3MNdb9EE2kktjYahMrGi T/lbJt8HSBZwJ4YAECunKBKxHaCWkMlbyVQu1xEOCjWRQH4mU+5euBzH9dNuugWT KWjYt9JR376ZRYCLfCvqikh3o7X2T0edxQBYJCD+QTblvgO2PrGPfzqc2EpObMFr 8Vb77FCkGOUYeTO64MqaMdKAzwxAulIGMTLFvZECQgs+g0roVMq5zrd1EIcAUn+b xRJoh1ZAUtUphFiV =yqnx -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of partman-md_89_source.changes
partman-md_89_source.changes uploaded successfully to localhost along with the files: partman-md_89.dsc partman-md_89.tar.xz partman-md_89_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#838503: marked as done (debian-installer: mdadm should not start syncing RAID1 arrays at full speed during installation)
Your message dated Mon, 24 Dec 2018 13:49:32 + with message-id and subject line Bug#838503: fixed in partman-md 89 has caused the Debian Bug report #838503, regarding debian-installer: mdadm should not start syncing RAID1 arrays at full speed during installation 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 ow...@bugs.debian.org immediately.) -- 838503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Version: 20160630 When creating a RAID1 array in the debian-installer and using it for the installation, mdadm immediately starts syncing the disks of the RAID array. This is a bad idea, because the subsequent install will be really slow on rotational disks (linear disk access by mdadm and random disk access by dpkg). On a fairly recent computer with 2 SATA disks, the installation took around 20 minutes before even arriving to the tasksel step. I can see two solutions: 1) lower the speed of the syncing operation, by setting the "dev.raid.speed_limit_max" sysctl setting to e.g. 1000; 2) disable syncing altogether, by passing "--assume-clean" to mdadm when creating the array. This second solution does not seem to be recommended by the mdadm developers, here is an excerpt of the mdadm man page: --assume-clean Tell mdadm that the array pre-existed and is known to be clean. It can be useful when trying to recover from a major failure as you can be sure that no data will be affected unless you actually write to the array. It can also be used when creating a RAID1 or RAID10 if you want to avoid the initial resync, however this practice — while normally safe — is not recommended. Use this only if you really know what you are doing. When the devices that will be part of a new array were filled with zeros before creation the operator knows the array is actually clean. If that is the case, such as after running badblocks, this argument can be used to tell mdadm the facts the operator knows. Regards, --- End Message --- --- Begin Message --- Source: partman-md Source-Version: 89 We believe that the bug you reported is fixed in the latest version of partman-md, 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 838...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Holger Wansing (supplier of updated partman-md 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Dec 2018 14:24:27 +0100 Source: partman-md Binary: partman-md Architecture: source Version: 89 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Description: partman-md - Add to partman support for MD (udeb) Closes: 838503 Changes: partman-md (89) unstable; urgency=medium . * Team upload . [ Steve McIntyre ] * When we create a new RAID1/5/6/10 array , start it syncing at the minimum speed allowed by the system. If we let it run at full speed, that will just slow the installation down while we're installing packages etc. There's nothing to protect at this point anyway. Closes: #838503 . [ Holger Wansing ] * Remove trailing whitespaces from changelog file, to fix lintian tag. Checksums-Sha1: 51185483f5b8e7542d4bcbb57a919396ae302272 1708 partman-md_89.dsc 141574f698bd2c3d8976f3c3716b18f735ac675d 182088 partman-md_89.tar.xz f93181666366eaf2c39fba3d841a9f1961b7eea0 5267 partman-md_89_amd64.buildinfo Checksums-Sha256: e6c8a298356a094730224d2c327df131f8551241cfa19cda268162bfbfcb9f4a 1708 partman-md_89.dsc de5925c525b84f355c4826f19a03d79988457735289e95ab46dfcb02246ffb42 182088 partman-md_89.tar.xz bc8128c1d3c9305c525dddae7ba261bd6dcb1a5dbed00c0ca73a921c44dfcec6 5267 partman-md_89_amd64.buildinfo Files: d4ff1b4d7f0b88286a441cb554715981 1708 debian-installer standard partman-md_89.dsc bda0f6339b205e512a48c99f6c5ea3ef 182088 debian-installer standard partman-md_89.tar.xz 3a2cc47b4f5ebafa030ef32d4307fa95 5267 debian-installer standard partman-md_89_amd64.buildinfo -BEGIN PGP SIGNATURE-
partman-lvm_125_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 24 Dec 2018 14:07:43 +0100 Source: partman-lvm Binary: partman-lvm Architecture: source Version: 125 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Holger Wansing Description: partman-lvm - Adds support for LVM to partman (udeb) Closes: 911036 Changes: partman-lvm (125) unstable; urgency=medium . * Team upload . [ Hideki Yamane ] * Fix invalid characters in volume group names (Closes: #911036). . [ Holger Wansing ] * Remove trailing whitespaces from changelog file, to fix lintian tag. . [ Updated translations ] * Arabic (ar.po) by ButterflyOfFire * Finnish (fi.po) by Juhani Numminen * Latvian (lv.po) by Tranzistors Checksums-Sha1: df1c42902b433da5b84e5d4ee9c512188a21283f 1721 partman-lvm_125.dsc 7d8c46354e64682e28d312950f6d73fbcc22919f 251640 partman-lvm_125.tar.xz 9509ff73ec0d0776bf5941a0ff7981b0c96ec245 5285 partman-lvm_125_amd64.buildinfo Checksums-Sha256: 1dd8dd21c44e5a0c9d3ec07ddd70c6830130a53e87debbabe0bc94d99be244e8 1721 partman-lvm_125.dsc 46e2285c81f37b510629199a8c26f128413795ac580d40349a20badc28f35fc2 251640 partman-lvm_125.tar.xz 0b8a2e80b77393c14b759bbff41a11084f8e6911c64ce1aacc2f75ace3055772 5285 partman-lvm_125_amd64.buildinfo Files: 0612460617909e47b901d3bb3f0ba4cf 1721 debian-installer optional partman-lvm_125.dsc db4f9acfe24e538622f016bde60c1c49 251640 debian-installer optional partman-lvm_125.tar.xz 77b48ca348e09af306f811db98903ce8 5285 debian-installer optional partman-lvm_125_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlwg3QcVHGh3YW5zaW5n QG1haWxib3gub3JnAAoJEFnxh8oVbrB2OksQALI7wd2TzYc7+f0LM7qhKMRWdaVd KCPOR3JBsCiWFZnbde2io0v8wzyxKwif4JJMcxwnV0gL5W4CO8TqMggAs2/s2jCM y3dRANECbhn5PWLGYMUmNMauCFfIP/NXkGc7JQHM2/AmSlyubF/XIDpZchMXQH6M jDTe2NCIPm2tVbGRS0BWnSA4dA6jF9GZ/sOU2PjsoGkJiAr0M/mQSPbSqZv6xUIU P8h7JNCbLAk7JACvmN6kPIGtrZZTb4BghGHYGu3jhTDYMqxllMyTTWfs4F5SNuLS osYSNCEw4TgdeLeFWP7rXfK2cJJd2Sh69EBpdTwIu8FtKkYl6jnvJBnHSw7XysHr 0N3wBRQakz4RPHZweLuhaR6CtD+qcrF6fd6wCR3KY8X/L1esTniBOrGSmYdh02sS rEmy+Y/5rHKMxLGTYtIwGW87XIjFyF5IWHdPbKlsZUiMWv6yFmHQPHnAOwQRPKsr IoLD0b+2EhFlltZDI9i95dHAp4jpuH37h9pJqKV+35MppQrK6DEqUEkXzOHsrw0f 9gWQkMZuo+rOYBmpIJr9rwM9X4HNcoHg2GeKGt/4YoTpktS9NW0BOEvPXcYv25/0 +Gw0xtAKzkN8L3KGl9vySLY3abHi0TjEPGADM5bnLmJlMkKRRjZtYv9AzVIuPFUh aREV0R+voDvkPiD/ =v6sv -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of partman-lvm_125_source.changes
partman-lvm_125_source.changes uploaded successfully to localhost along with the files: partman-lvm_125.dsc partman-lvm_125.tar.xz partman-lvm_125_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#911036: marked as done (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
Your message dated Mon, 24 Dec 2018 13:35:05 +
with message-id
and subject line Bug#911036: fixed in partman-lvm 125
has caused the Debian Bug report #911036,
regarding partman-lvm: Volume group name "■" has invalid characters, and
cannot removed
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 ow...@bugs.debian.org
immediately.)
--
911036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911036
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: partman-lvm
Version: 124
Severity: important
tags: d-i
Hi,
While installing with d-i buster alpha3, I've tried to remove Logical Volume
but couldn't. At VT4 shows below error
> partman-lvm:Volume group name "■" has invalid characters
> partman-lvm:Cannot process volume group ■
However, LV names are "home", "root" and "swap_1", not "■".
("■" may be mojibake?)
># lvscan
> ACTIVE'/dev/elitebook830-vg/root' [<27.94 GiB] inherit
> ACTIVE'/dev/elitebook830-vg/swap_1' [<31.84 GiB] inherit
> ACTIVE'/dev/elitebook830-vg/home' [<893.34 GiB] inherit
And "lvremove /dev/elitebook830-vg/{root,swap_1,home}" works well at VT2.
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
--- End Message ---
--- Begin Message ---
Source: partman-lvm
Source-Version: 125
We believe that the bug you reported is fixed in the latest version of
partman-lvm, 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 911...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Holger Wansing (supplier of updated partman-lvm 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 ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 24 Dec 2018 14:07:43 +0100
Source: partman-lvm
Binary: partman-lvm
Architecture: source
Version: 125
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Holger Wansing
Description:
partman-lvm - Adds support for LVM to partman (udeb)
Closes: 911036
Changes:
partman-lvm (125) unstable; urgency=medium
.
* Team upload
.
[ Hideki Yamane ]
* Fix invalid characters in volume group names (Closes: #911036).
.
[ Holger Wansing ]
* Remove trailing whitespaces from changelog file, to fix lintian tag.
.
[ Updated translations ]
* Arabic (ar.po) by ButterflyOfFire
* Finnish (fi.po) by Juhani Numminen
* Latvian (lv.po) by Tranzistors
Checksums-Sha1:
df1c42902b433da5b84e5d4ee9c512188a21283f 1721 partman-lvm_125.dsc
7d8c46354e64682e28d312950f6d73fbcc22919f 251640 partman-lvm_125.tar.xz
9509ff73ec0d0776bf5941a0ff7981b0c96ec245 5285 partman-lvm_125_amd64.buildinfo
Checksums-Sha256:
1dd8dd21c44e5a0c9d3ec07ddd70c6830130a53e87debbabe0bc94d99be244e8 1721
partman-lvm_125.dsc
46e2285c81f37b510629199a8c26f128413795ac580d40349a20badc28f35fc2 251640
partman-lvm_125.tar.xz
0b8a2e80b77393c14b759bbff41a11084f8e6911c64ce1aacc2f75ace3055772 5285
partman-lvm_125_amd64.buildinfo
Files:
0612460617909e47b901d3bb3f0ba4cf 1721 debian-installer optional
partman-lvm_125.dsc
db4f9acfe24e538622f016bde60c1c49 251640 debian-installer optional
partman-lvm_125.tar.xz
77b48ca348e09af306f811db98903ce8 5285 debian-installer optional
partman-lvm_125_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAlwg3QcVHGh3YW5zaW5n
QG1haWxib3gub3JnAAoJEFnxh8oVbrB2OksQALI7wd2TzYc7+f0LM7qhKMRWdaVd
KCPOR3JBsCiWFZnbde2io0v8wzyxKwif4JJMcxwnV0gL5W4CO8TqMggAs2/s2jCM
y3dRANECbhn5PWLGYMUmNMauCFfIP/NXkGc7JQHM2/AmSlyubF/XIDpZchMXQH6M
jDTe2NCIPm2tVbGRS0BWnSA4dA6jF9GZ/sOU2PjsoGkJiAr0M/mQSPbSqZv6xUIU
P8h7JNCbLAk7JACvmN6kPIGtrZZTb4BghGHYGu3jhTDYMqxllMyTTWfs4F5SNuLS
osYSNCEw4TgdeLeFWP7rXfK2cJJd2Sh69EBpdTwIu8FtKkYl6jnvJBnHSw7XysHr
0N3wBRQakz4RPHZweLuhaR6CtD+qcrF6fd6wCR3KY8X/L1esTniBOrGSmYdh02sS
rEmy+Y/5rHKMxLGTYtIwGW87XIjFyF5IWHdPbKlsZUiMWv6yFmHQPHnAOwQRPKsr
IoLD0b+2EhFlltZDI9i95dHAp4jpuH37h9pJqKV+35MppQrK6DEqUEkXzOHsrw0f
9gWQkMZuo+rOYBmpIJr9rwM9X4HNcoHg2GeKGt/4YoTpktS9NW0BOEvPXcYv25/0
+Gw0xtAKzkN8L3KGl9vySLY3abHi0TjEPGADM5bnLmJlMkKRRjZtYv9AzVIuPFUh
aREV0R+voDvkPiD/
=v6sv
-END PGP SIGNATURE End Message ---
Re: partman-lvm update
Hi, Hideki Yamane wrote: > Hi, > > Can someone update partman-lvm package to include below fix? > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911036 Just uploaded. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Re: Bug#906016: transition: gjs built with mozjs60
On Mon, 2018-12-24 at 12:01 +, Simon McVittie wrote: > On Sun, 23 Dec 2018 at 16:29:31 +0100, John Paul Adrian Glaubitz wrote: > > Can we postpone the decision until after the holidays? Then I have enough > > time for trying to whip up a patch. > > That seems fine, but please note that most of the changes necessary to > remove gjs from s390x happened some time ago (in late September and early > October); so if you are able to make mozjs60 work correctly on s390x, > we will likely already need to revert some changes to bring it back. > If the d-i maintainers remove gjs/GNOME Shell on s390x and then you > subsequently get mozjs60 working on s390x, the list of changes to revert > to bring back gjs/s390x just becomes slightly longer. > > I'm also not at all sure whether the GNOME Shell environment works > on s390x hardware, which as far as I know doesn't have either a > Mesa-supported GPU or the llvmpipe driver - if it never worked then we > aren't actually losing anything. Presumably s390 porters would have a > better idea of what works and what doesn't. IBM Z (why do they keep renaming it?) supports PCI Express now, so I think it's *possible* to install a Mesa-supported GPU, if unlikely. Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious. signature.asc Description: This is a digitally signed message part
Re: Bug#906016: transition: gjs built with mozjs60
On Sun, 23 Dec 2018 at 16:29:31 +0100, John Paul Adrian Glaubitz wrote: > Can we postpone the decision until after the holidays? Then I have enough > time for trying to whip up a patch. That seems fine, but please note that most of the changes necessary to remove gjs from s390x happened some time ago (in late September and early October); so if you are able to make mozjs60 work correctly on s390x, we will likely already need to revert some changes to bring it back. If the d-i maintainers remove gjs/GNOME Shell on s390x and then you subsequently get mozjs60 working on s390x, the list of changes to revert to bring back gjs/s390x just becomes slightly longer. I'm also not at all sure whether the GNOME Shell environment works on s390x hardware, which as far as I know doesn't have either a Mesa-supported GPU or the llvmpipe driver - if it never worked then we aren't actually losing anything. Presumably s390 porters would have a better idea of what works and what doesn't. smcv
