Re: unifont-bin: Consider dropping unifont-viewer and therefore the dependency on unmaintained libwx-perl
Hi, On Fri, 20 Oct 2023 14:11:22 +0100 Simon McVittie wrote: > unifont-bin depends on libwx-perl, which as mentioned in #1054146 is > unmaintained upstream and only minimally maintained in Debian. > > debian-installer build-depends on unifont-bin, which brings libwx-perl > into the critical path for being able to build d-i. Okay. Isn't it enough to split unifont-viewer from unifont-bin, then? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: About terms of service
Hi from ex-FSI employee ;) Please use more appropriate mailing list for such questions, this is for debian-installer, bootloader, etc., not for user's questions. It would be better to use debian-japanese@ or use Debian-JP mailing list (see https://www.debian.or.jp) In Japanese, 元FSI社員より ;) このような質問についてはより適切なユーザー向けメーリングリストを利用ください。 日本語で質問したい場合は debian-japanese@ などが良いでしょうし、 Debian-JP のメーリングリストを使うのも良いでしょう。 On Thu, 29 Jun 2023 17:27:47 +0900 今川陽裕 wrote: > I look for a terms of service. > Can you tell me where I can find a terms of service. There is no such things for Debian, We are not company, just create and provide free software distribution. If you'd worry about its license, please look license in each packages. 我々は利用規約などを用意してはいません。Debianは有志ボランティアによる フリーソフトウェアの作成と提供を行っています。もしソフトウェアの利用に際して ライセンスが気になるようであれば、各ソフトウェアパッケージにライセンスを明記 してあるので、それを確認してください。 -- Hideki Yamane
More automated process in the future (Re: Debian 11 after upgrade from debian 10 issue
On Sat, 12 Mar 2022 11:38:02 + "Andrew M.A. Cater" wrote: > The release notes for Debian Bullseye make it clear that the stanza for > security changed with the Debian release. Can we make it automated process during upgrade in the future release? Our release notes are really useful (I know it since translated into Japanese :), but automated process is much better for users. -- Hideki Yamane
Re: Should /boot be ext2, instead of ext4?
On Sat, 4 Sep 2021 21:43:50 +0100 Steve McIntyre wrote: > Ummm. In my experience quite a number of older armel/armhf devices > booting using U-Boot may *not* be able to boot using ext4. I don't have any knowledge about U-Boot and arm devices, so here's a question. Is U-Boot different on each devices? It means, U-Boot on device A can read ext4 but on device B cannot. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Should /boot be ext2, instead of ext4?
On Sat, 4 Sep 2021 14:00:06 -0700 "J. William Campbell" wrote: > but if we are talking about a > /boot partition, there is no good reason to change it to ext4. Ext4 is reliable than ext2, I guess. And, /boot needs it. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Should /boot be ext2, instead of ext4?
On Tue, 10 Aug 2021 19:33:37 +0200 Ben Hutchings wrote: > This is bug #985463. If we can confirm no architecture has a limit to use ext2 now, then we can change it to ext4, right? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Q: different behavior about d-i between normal install image and live image
On Wed, 18 Aug 2021 02:05:16 +0100 Steve McIntyre wrote: > > Is it intended behavior? > > Yes, this has always been the case. If you install using the live > image, you get (approximately) a clone of the live image on ypur hard > drive. Thanks for the answer. Hmm, some people who chose "debian-installer" at first menu guess it acts as normal installation image, not live image specific one. > If you want flexibility to choose different packages, use a > normal installation image. Yeah, but it's hard to know... -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Q: different behavior about d-i between normal install image and live image
Hi, There is a different behavior between normal install image and live image, that is asking choose tasks with tasksel. At live image, start with debian-installer to install (not calamares on GUI), there is no step via tasksel. Is it intended behavior? -- Hideki Yamane
Re: debian:stable docker image points wrong path for security updates
Hi Tianon, On Mon, 16 Aug 2021 11:56:35 -0700 Tianon Gravi wrote: > Just to close the loop, > https://github.com/docker-library/official-images/pull/10730 (for > anyone who wants to follow along). :) Thanks! :) Now release-notes CI works. https://salsa.debian.org/ddp-team/release-notes/-/jobs/1820974 -- Hideki Yamane
debian:stable docker image points wrong path for security updates
Hi, I've commited release notes translation update to repo but CI failed. It is because debian:stable docker image's setting: it is still old style "stable/updates", instead of "stable-security" for security updates(*). >> Err:5 http://security.debian.org/debian-security stable/updates Release >> 404 Not Found [IP: 151.101.130.132 80] > $ docker run -it debian:stable /bin/bash > root@467cd5226ed1:/# sed -i -e 's/stable\/updates/stable-security/' > /etc/apt/sources.list > root@467cd5226ed1:/# apt update > Get:1 http://deb.debian.org/debian stable InRelease [113 kB] > Get:2 http://security.debian.org/debian-security stable-security InRelease > [44.1 kB] > Get:3 http://security.debian.org/debian-security stable-security/main amd64 > Packages [19.0 kB] > Get:4 http://deb.debian.org/debian stable-updates InRelease [40.1 kB] > Get:5 http://deb.debian.org/debian stable/main amd64 Packages [8178 kB] > Fetched 8393 kB in 4s (2044 kB/s) > Reading package lists... Done Do you know When it will update to bullseye? *) https://www.debian.org/releases/stable/amd64/release-notes/ch-information.html#security-archive -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: install guide: Some translated messeges (po/ja/using-d-i.po) not shown in html
Hi, On Mon, 09 Aug 2021 09:18:04 +0200 Holger Wansing wrote: > There is no problem here. > > The website (URL above) shows the version of installation-guide currently in > testing. > But there has been no upload since you translated that chapter (3 days ago!). > > You can find a preview of installation-guide at https://d-i.debian.org/manual/ Thank you, Holger. I've completely forgot about its site. Looks good now, and I'd keep it. -- Hideki Yamane
install guide: Some translated messeges (po/ja/using-d-i.po) not shown in html
Hi, I've translated ja.po for install guide but not shown in generated html. https://www.debian.org/releases/bullseye/amd64/ch06s04.ja.html#completing-installed-system I cannot find any errors for .po with msgfmt tool, can someone help me, please? -- Hideki Yamane
Should /boot be ext2, instead of ext4?
Hi, I've found that d-i creates /boot as ext2 for guided partioning with LVM. I think ext4 is better but is there any reason to do so? (e.g. some architecture or bootloader cannot recognize ext4 for it) If not, I'll prepare a MR for it. (Of course, it will be treated after bullseye release). -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#934713: os-prober: missing dependency on mount
control: tags -1 +patch On Thu, 15 Aug 2019 16:49:46 +0200 Johannes Schauer wrote: > > > https://lists.debian.org/20170726081846.ga22...@fatal.se > > > > Well, debian-devel@ isn't where one files bug reports against packages that > > suddenly need a dependency? > > I was not trying to justify or excuse the omission of the src:util-linux > maintainers. I can only imagine that os-prober somehow slipped through the > cracks when the src:util-linux maintainers filed bugs against all packages > that > need the mount utilities during the buster release cycle. > > I agree that the situation now is unfortunate but I only reported this problem > once I stumbled across it. I was not involved in the decision two years ago. Anyway, here's a tiny MR https://salsa.debian.org/installer-team/os-prober/-/merge_requests/9 If it would be a wrong way to deal with this bug, then close above MR and remove Tags: patch, please. If not - just merge it and push the package :D -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: fonts-lklug-sinhala: Stop creating udeb
On Sun, 25 Apr 2021 13:31:38 +0200 Cyril Brulebois wrote: > In hindsight, we have this bug report: #987449 where Sinhala is > mentioned as one language where the installer regresses. > > We have yet to figure out what's happening, but maybe you could delay > the deletion a little, just in case the old udeb is still needed on the > long run? > > Thanks for considering, and sorry for the false start. Ouch, already did it. It's in unstable without unblock, you can safely ignore it. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: fonts-lklug-sinhala: Stop creating udeb
On Fri, 23 Apr 2021 23:21:47 +0200 Cyril Brulebois wrote: > It seems both tasksel and debian-installer were updated to use the > replacement on the deb and udeb fronts respectively, so you should be > good to go I think? Thank you, let's go. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: fonts-lklug-sinhala: Stop creating udeb
On Fri, 16 Sep 2016 00:35:01 +1000 Harshula wrote: > Package: fonts-lklug-sinhala > Version: 0.6-3 > Severity: important > > Please stop creating udeb for fonts-lklug-sinhala. > > The LKLUG font is viewed as deprecated and we've been trying to > encourage other fonts that can succeed as the default Sinhala font on > GNU/Linux. > > At this stage the Noto Sinhala range, in fonts-noto-hinted, is a more > appropriate default font than LKLUG. > > See the discussion here: > http://sourceforge.net/p/sinhala/mailman/message/34481529/ > > $ apt-cache rdepends fonts-lklug-sinhala > fonts-lklug-sinhala > Reverse Depends: > task-sinhala-desktop > > $ dpkg -L fonts-noto-hinted | grep -i sinhala > /usr/share/fonts/truetype/noto/NotoSansSinhala-Bold.ttf > /usr/share/fonts/truetype/noto/NotoSansSinhala-Regular.ttf > > Thanks, > # It's easy to do, but can I do this or should stop to do so? More input is welcome. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#830794: --exclude does not apply to required packages, contrary to manpage
control: fixed -1 1.0.105 I'm not sure why, but it seems to work properly now ;) > $ sudo debootstrap --variant=minbase --cache-dir=/home/henrich/tmp/cache > --exclude=bash buster ~/tmp/buster > I: Target architecture can be executed > > > I: Retrieving InRelease > (snip) > $ sudo chroot ~/tmp/buster > chroot: failed to run command '/bin/bash': No such file or directory > $ sudo chroot ~/tmp/buster /bin/dash > # -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#879755: tries to install apt-transport-https even if doesn't exist
Hi, Just simply checking codename patch for debootstrap is here, comments are welcome. https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/41/diffs -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#926214: debootstrap: clean up /var/cache/apt/archives/*
control: severity -1 wishlist control: tags -1 +patch Hi, Here's a patch. diff --git a/debootstrap b/debootstrap index 8fbf954..397bc09 100755 --- a/debootstrap +++ b/debootstrap @@ -33,6 +33,7 @@ ARCH="" HOST_ARCH="" HOST_OS="" KEEP_DEBOOTSTRAP_DIR="" +KEEP_APT_CACHE="" USE_DEBIANINSTALLER_INTERACTION="" SECOND_STAGE_ONLY="" CHROOTDIR="" @@ -227,6 +228,10 @@ if [ $# != 0 ] ; then KEEP_DEBOOTSTRAP_DIR=true shift ;; + --keep-apt-cache) + KEEP_APT_CACHE=true + shift + ;; --arch|--arch=?*) if [ "$1" = "--arch" ] && [ -n "$2" ] ; then ARCH="$2" @@ -840,6 +845,10 @@ if am_doing_phase second_stage; then fi fi +if [ ! "$KEEP_APT_CACHE" = true ]; then + rm -rf "$TARGET/var/cache/apt/archives" "$TARGET/var/lib/apt/lists" +fi + if am_doing_phase kill_target; then if [ "$KEEP_DEBOOTSTRAP_DIR" != true ]; then info KILLTARGET "Deleting target directory"
Bug#921815: debootstrap umount "host" /proc when running in a Docker container
control: tags -1 +moreinfo Hi, On Sat, 09 Feb 2019 05:01:32 +0100 "Kristian Klausen" wrote: > Package: debootstrap > Version: 1.0.110~bpo9+1 > When running debootstrap inside a Docker container, debootstrap umount both > /proc and $TARGET/proc. How do I check it? - run docker - get debootstrap 1.0.110 and install it - debootstrap sid sid - /proc is there inside docker as below > root@b49ab8b7f3eb:~# ls /proc/ > 1 crypto iomemkpageflagspartitions sysrq-trigger > 19486 devices ioports loadavg pressure sysvipc > acpi diskstatsirq locks sched_debug thread-self > asound dma kallsyms meminfo schedstattimer_list > buddyinfo driver kcoremisc self tty > busexecdomains key-usersmodules slabinfo uptime > cgroupsfb keys mountssoftirqs version > cmdlinefilesystems kmsg mtrr stat vmallocinfo > consoles fs kpagecgroup net swapsvmstat > cpuinfointerrupts kpagecount pagetypeinfo sys zoneinfo -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#935334: debootstrap: man page says that --include will add package to download and extract list, but an experiment shows opposite
control: tags -1 +moreinfo Hi, > So, it follows from manual page that --include=alpha will add a package to > set of packages, > which are extracted at extract stage. But experiment shows that this is not > true. Please describe your expectation and the results since it's not clear for me. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#951367: debootstrap: Raspbian bootstrap: Failed getting release file
On Sun, 16 Feb 2020 15:31:56 +0100 Michael Büsch wrote: > $ sudo debootstrap --arch=armhf --foreign --verbose > --keyring=raspbian-archive-keyring-20120528.2/raspbian.public.key.gpg buster > /tmp/debootstrap-test/ > http://mirror1.hs-esslingen.de/pub/Mirrors/archive.raspbian.org/raspbian/ Please try without --verbose, I guess its option is something wrong with. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Asking for access to team
Hi, On Mon, 22 Jul 2019 14:27:41 -0300 "eamanu15 ." wrote: > I just saw the Hideki Yamane presentation in debconf, > and I am interest on help on debootstrap and in > other package's team Thanks! :) Note: my slide on that presentation https://docs.google.com/presentation/d/1_pGrOX8QpDeSnTqoPPn8NYZ_-zEs3egdQMc-R17lZRs/edit#slide=id.p > Could you give me access to the team, please? Before that, I suggest you just make a fork repository under your account and do "git clone" and look into it. Then check BTS and find some bugs you can tackle. Welcome to debootstrap world :) -- Hideki Yamane
Bug#710709: debootstrap: consider creating (dangling) /etc/mtab symlink
control: tags -1 +patch
revised patch
>From 55c21c166959a93b961c572d5f366d35d054ce24 Mon Sep 17 00:00:00 2001
From: Hideki Yamane
Date: Wed, 1 May 2019 04:24:43 +0900
Subject: [PATCH] create symlink from /proc/self/mounts to /etc/mtab
With old kernel version, there is /proc/mounts instead of
/proc/self/mounts, so check whether /proc/self exists
---
functions | 7 +++
1 file changed, 7 insertions(+)
diff --git a/functions b/functions
index 24f0357..46ebceb 100644
--- a/functions
+++ b/functions
@@ -1176,6 +1176,13 @@ setup_proc () {
in_target mount -t sysfs sysfs /sys || true
umount_on_exit /sys
fi
+ if [ ! -f "$TARGET/etc/mtab" ]; then
+ if [ -L "$TARGET/proc/self" ]; then
+ cd "$TARGET/etc" && ln -s ../proc/self/mounts
mtab
+ elif [ -f "$TARGET/proc/mounts" ]; then
+ cd "$TARGET/etc" && ln -s ../proc/mounts mtab
+ fi
+ fi
on_exit clear_mtab
;;
esac
--
2.20.1
Bug#926214: debootstrap: clean up /var/cache/apt/archives/*
On Tue, 2 Apr 2019 16:44:14 +0900 Hideki Yamane wrote: > $ sudo rm -r sid/var/cache/apt/archives/* and also /var/lib/apt/lists -- Hideki Yamane
Bug#926216: debootstrap: Add dpkgopt
package: debootstrap severity: wishlist mmdebstrap has aptopt and dpkgopt option to manage apt and dpkg via passing some options to it, put conf file to /etc/apt/apt.conf.d/99mmdebstrap and /etc/dpkg/dpkg.cfg.d/99mmdebstrap. I think it's worth to add such option to debootstrap, especially dpkgopt to reduce image size via "--dpkgopt='path-exclude=/usr/share/man/*' \ --dpkgopt='path-exclude=/usr/share/locale/*' \ --dpkgopt='path-exclude=/usr/share/doc/*' \" for minimize it. -- Hideki Yamane
Bug#926214: debootstrap: clean up /var/cache/apt/archives/*
package: debootstrap severity: minor debootstrap-ed image contains some .deb files that would not be used anymore, so removing them at finish is better since we can shrink it. $ sudo debootstrap --cache-dir=/home/henrich/tmp/cache sid sid (...) $ sudo du -sh sid 282Msid $ sudo rm -r sid/var/cache/apt/archives/* $ sudo du -sh sid 236Msid Any comments? -- Hideki Yamane
Bug#925048: debootstrap: --keyring= Release signed by unknown key (key id EF0F382A1A7B6500)
control: tags -1 +unreproducible +moreinfo
On Tue, 19 Mar 2019 21:08:42 +0530 "Veek.M" wrote:
>* What led up to the situation?
> dpkg-deb -R debian-archive-keyring_2017.5_all.deb /tmp/
> ls *.gpg|xargs -I{} debootstrap --download-only --force-check-gpg
> --keyring={} --variant minbase --arch amd64 --make-tarball=debian_amd64
> stable /root/dbs_debian_amd64 https://debian.ethz.ch/debian
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> E: Release signed by unknown key (key id EF0F382A1A7B6500)
> but
> debootstrap --download-only --force-check-gpg --variant minbase --arch amd64
> --make-tarball=debian_amd64 stable /root/dbs_debian_amd64
> https://debian.ethz.ch/debian
> works
>
> There's a problem with using --keyring=whatever.gpg
I cannot reproduce it
$ sudo debootstrap --version
debootstrap 1.0.89
$ sudo debootstrap --download-only --force-check-gpg --variant minbase --arch
amd64 --make-tarball=debian_amd64
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg stable stretch
I: Retrieving InRelease
I: Retrieving Release
I: Checking Release signature
I: Valid Release signature (key id 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500)
I: Retrieving Packages
^CE: Interrupt caught ... exiting
It seems that your procedure of specifying gpg key is bit strange.
> dpkg-deb -R debian-archive-keyring_2017.5_all.deb /tmp/
> ls *.gpg|xargs -I{} debootstrap --download-only --force-check-gpg
> --keyring={} --variant minbase --arch amd64 --make-tarball=debian_amd64
> stable /root/dbs_debian_amd64 https://debian.ethz.ch/debian
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#911036: Acknowledgement (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
On Sun, 3 Mar 2019 17:20:30 +0100 Cyril Brulebois wrote: > I'd rather avoid testing more things at this stage. ;-( Okay, when the window will be opened for it, then? I'm curious. -- Hideki Yamane
Bug#911036: Acknowledgement (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
On Sat, 16 Feb 2019 20:30:00 +0900 Hideki Yamane wrote: > Sorry for the delay, I've made and tested new patch for it as > https://salsa.debian.org/installer-team/partman-lvm/merge_requests/2 Can someone review it? > -boot -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Going ahead with non-free-firmware
Hi, On Sun, 24 Feb 2019 16:44:39 +0100 Ansgar wrote: > Sadly no; I think some later discussion made me doubt that there was > indeed consensus about having non-free-firmware (and only that and not > non-free-doc, non-free-drivers, non-free-*). Nor about how it would > work. > > I don't think we should add a new component without having that > (component meaning main, contrib, non-free, non-free-firmware here). > They are not nice to handle on the archive side. Thanks for your reply. Well, then is there any proposal to improve setting non-free firmware in installer now? -- Hideki Yamane
Re: Going ahead with non-free-firmware
Hi, Is there any progress about non-free-firmware section? > Hi, > > I think there was consensus to introduce the non-free-firmware section > and move the non-free firmware blobs there. I'm wondering what we need > to do next? > > Besides the ftp team setting the new section up, I expect the installer > would need changes to enable it instead of non-free when non-free > firmware is required; maybe it still needs to ask for non-free as well > for other reasons? Other teams might also need to add the new section, > e.g. the release team, packages.d.o, ... I expect the list to be > hard-coded in quite a few places. > > Then the release notes need to document that "non-free-firmware" might > have to be added to sources.list. > > Finally we need to identify the packages that should move there. I > guess all non-free packages named "firmware-*" would be a good match. > > Ansgar -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#911036: Acknowledgement (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
Hi Steve, On Wed, 13 Feb 2019 18:00:36 + Steve McIntyre wrote: > >I'm afraid your fix in choose_partition/lvm/do_option is broken. It's > >causing problems for other people trying to use LVM in d-i. See > >#922100, which I've just confirmed locally. > > I've reverted your change for now - we've already had 2 bug > reports. Please test and fix as/when you can. Sorry for the delay, I've made and tested new patch for it as https://salsa.debian.org/installer-team/partman-lvm/merge_requests/2 Could you check it, please? -- Hideki Yamane
Bug#918722: debootstrap: says InRelease file expired
On Wed, 9 Jan 2019 14:13:14 +0100 Julien Cristau wrote: > I reverted the 1.0.113 changes to unbreak this and uploaded 1.0.114. Thanks to take caring for this. > I'm happy to review an updated version when you get that working. Hope > that's ok. Now I've pushed MR with (hopefully) fixed version, please check it. -- Hideki Yamane
Bug#918659: Debootstrap started to fail with Busybox
control: tags -1 +patch Hi, On Tue, 8 Jan 2019 04:43:40 +0100 Piotr Jurkiewicz wrote: > Debootstrap started to fail with busybox since version 1.0.113. I've created a merge request for that. https://salsa.debian.org/installer-team/debootstrap/merge_requests/24 Hope someone in -boot would review it. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: debootstrap_1.0.113_source.changes ACCEPTED into unstable
Hi, On Sun, 06 Jan 2019 18:04:18 + Debian FTP Masters wrote: > debootstrap (1.0.113) unstable; urgency=low > . >* Fail if its repository is expired (in InRelease file) since creating > base image from such repository is insecure. If you want to use such > repo with notice, please use "--no-check-valid-until" option I've merged long-standing MR since this summer, and probably (and hopefully) last upload to unstable before buster. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp http://wiki.debian.org/HidekiYamane
Re: Slack segmentation fault
On Tue, 25 Dec 2018 10:45:58 +0300 Sky Darkness wrote: > When Slack is installed on a clean Debian buster, it generates a > Segmentation Fault error. It's because slack problem with glibc update. BTW, debian-boot is not appropriate mailing list for this issue, please use debian-u...@lists.debian.org, instead. # and slack is not provided by Debian, so it's better to check their forum, etc. -- Hideki Yamane
Re: debootstrap_1.0.112_source.changes ACCEPTED into unstable
On Sun, 23 Dec 2018 10:04:07 + Debian FTP Masters wrote: > debootstrap (1.0.112) unstable; urgency=low > . >[ Thomas Lange ] >* optimize code, make debootstrap faster (Closes: #871835) I've put Thomas's hack into unstable, with low urgency. It shows same result (except time) with previous version for stretch, buster and sid on my machine at least. Please test it and file bug report if you got any trouble. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?
Hi, On Sun, 23 Dec 2018 00:36:52 + Simon McVittie wrote: > To be completely clear about the decision that Ian asked the technical > committee to overrule: > > In all debootstrap versions since 1.0.102, merged /usr is the default (for > all variants except --variant=buildd). This means that new installations > of Debian buster using debian-installer will have merged /usr. > > Do the debian-installer and debootstrap maintainers think this should > continue to be true for the buster release? At this time, yes. +1 However, if it'll be a blocker for release during freeze, it should be reverted. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
partman-lvm update
Hi, Can someone update partman-lvm package to include below fix? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911036 -- Hideki Yamane
Re: Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default? /usr by default
Hi, On Wed, 5 Dec 2018 08:39:27 + Simon McVittie wrote: > It might also be considered appropriate to revert the change in > debootstrap 1.0.111 if data from reproducible-builds demonstrates that > bugs similar to #913226 have all been fixed or are very rare, but this > should be done cautiously, and certainly not before buster is released. Okay, my opinion is "Push usr-merge effort forward, fix those issues with it as bug that is tracked at reproducible builds(*), and turn it on again as default (probably after buster cycle)". *) https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default
Hi, Thanks Simon, it's perhaps clear for me now. On Sun, 2 Dec 2018 15:15:21 + Simon McVittie wrote: > > - What is the problem? (broken build for which packages? Just R?) > > The problem we're aware of is: > > Some packages auto-detect the absolute path to an executable (for example > bash or perl) and hard-code it into their output (for example the #! line > of the bash scripts in quilt). Can we check and track this behavior in our packages? Once disable merged-usr is good to prevent confusion but we detect such as a bug for manage non-merged-usr and merged-usr Debian system in the end, right? (or do you want to stay change in debootstrap 1.0.111 forever?) -- Hideki Yamane
Re: #914897: debootstrap, buster: Please disabled merged /usr by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, On Fri, 30 Nov 2018 19:40:45 +0100 "Didier 'OdyX' Raboud" wrote: > tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by > default now, or are you OK letting the TC decide on this subject? Hmm, I'm still considering what's the good way... > Hideki, if I read the debootstrap history correctly, you enabled "merged > /usr" > by default in debootstrap 1.0.102. Yes, that's right. #839046 was filed in Sep 2016, and uploaded in Jun 2018. > Given the recent discussion in debian- > devel@ (starting at [0]) and on #914897, could you (or anyone speaking as > with > a "debootstrap maintainer" hat on) state if, either of: > > * you would be willing to toggle the "merged /usr" default in debootstrap in a > subsequent upload; > * you maintain that the "merged /usr" default (to yes) is here to stay. Well, with a quick look to the thread (I cannot follow all of the email in it, tons of emails...), I cannot find the discussion about - What is the problem? (broken build for which packages? Just R?) - How many packages are affected? - Why it was caused? (just symlink to /bin or /sbin isn't enough to deal with it?) - Does it cause any failure on users' machine? So, I want to listen above things (not thought or idea), then reply to your question. Please quote if someone can do it. - -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp http://wiki.debian.org/HidekiYamane -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEQZYJUbYxgXxV33EdBBJ4KqpAHFMFAlwDzlUACgkQBBJ4KqpA HFOnfxAAv8s9EQwntX9SBHALIY+5X1Ma98aMhrzZ2SWDt1txznXRt18z/85oOWqs FGLrm2QY159qWEG2lpsWhAIr7wQJBPcFH5MRQcn6pDM6pXB1ioaTsW9uhd/AMl+s mCyvWW0xtJ1ww2EXV2hN5X0K4AAre2rajb0P4p6efeY5V9sbMQ/gZa+L2sJuL1P/ /6fK4Kxe893lVuZ3oxtOhKRkdgi1V1X63kUURofuTSZiVzeGYWAuPdnHBxADs9vK kk6mpUFkYSeOfg45h2KQzUqeTsX5GTogWIFqEOAJ0KJGDusOiFEPWL/pus+De1E7 cyEX2i6yq3wOOQBov5/eNH2gMs9pDaOqM8hR0tjvya4aAJOa7VyFY2GzMdsEHdQe Ay7EtzG3RLwuiQ0XrSmIyaDdlJpofCGernNgVu+dnBJb/1U4RHgneVbIELULGUYm DGFov6FpeUQB6wc/fsaoDWQBiwwNCS2qkJnZJg5nu4ne12NqnERqoq2lIR3ivSe2 1Oi9v/ClKqNSKGLAIoRVvllZhs9W1ppwkZIqtC0mZlN05nw7Wyrj4YoRbJ4r70Rd rdQzTntchOXbYOmdt2H6yUdpnJJoA46+OxlwykvjrUnDnzgheNMJ0wRh36LcOz50 pjQBQGGVVl/9+Tjw/vSCu+alwLwPY34YFOM8I4fh/V0OHbO4fNE= =yD0D -END PGP SIGNATURE-
Re: [debian-installer] Call to update translations for Buster
On Wed, 17 Oct 2018 08:55:35 +0900 Kenshi Muto wrote: > Could you add `kmuto' to committer group or merge > https://salsa.debian.org/installer-team/d-i/merge_requests/3 ? Add some review to that commit, please check it. -- Hideki Yamane
Bug#911036: Acknowledgement (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
control: tags -1 +patch On Tue, 16 Oct 2018 12:38:30 +0900 Hideki Yamane wrote: > Here's a step to reproduce this bug And here's a proposed patch, please review it. https://salsa.debian.org/installer-team/partman-lvm/merge_requests/1 -- Hideki Yamane
Bug#911036: Acknowledgement (partman-lvm: Volume group name "■" has invalid characters, and cannot removed)
Hi, Here's a step to reproduce this bug --- 1. boot from d-i media and start installer 2. create encrypted LVM volume 3. select "go back" and "Change language" to "Japanese" (or other multi-byte locale) 4. select "論理ボリュームマネージャーの設定 (Configure the Logical Volume Manager)" -> "論理ボリュームの削除 (Delete logical volue)" and any volume 5. Got error 6. select "戻る (go back) and "言語の選択/Change language" to "English" 7. select "Configure the Logical Volume Manager" -> "Delete logical volume" and any volume 8. you can delete it without error! -- Hideki Yamane
Bug#909658: debian-installer: blank screen on install (HP Elitebook 830 G5)
control: merge 899240 -1 control: severity -1 serious Hi, I've updated to newest BIOS 1.04 (Oct 11th version) and then change UEFI setting with enable legacy boot (CSM) and d-i works. (I guess old HP Elitebook 830 G5 BIOS doesn't work well). I'll rise its severity since it seems to be common issue on new hardware, and unfortunately some hardware doesn't support CSM. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#911036: partman-lvm: Volume group name "■" has invalid characters, and cannot removed
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
Bug#909658: debian-installer: blank screen on install (HP Elitebook 830 G5)
On Wed, 26 Sep 2018 23:20:29 +0900 Hideki Yamane wrote: > > Success > > - Ubuntu18.04.1 (Linux 4.15.0-29-generic) > > > > Fail > > - Debian9.4 > > - both Debian Installer Buster Alpha 3 release and daily image Boot resolution is different between Ubuntu and d-i. Ubuntu 18.04.1 https://photos.app.goo.gl/yWTJV6RQ7dXZDFQA8 Debian Installer Buster Alpha 3 https://photos.app.goo.gl/t7ASV2qZ4rZ4kPvk7 -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#909658: debian-installer: blank screen on install (HP Elitebook 830 G5)
Hi, Additional info, - CentOS7 and Fedora29 work - Debian9.5 (Debian Live) also works (able to login to GNOME desktop) but install goes to blank screen On Wed, 26 Sep 2018 21:16:24 +0900 Hideki Yamane wrote: > Package: debian-installer > Severity: important > > Hi, > > I've tried to install Debian on my new laptop HP EliteBook 830 G5 > but failed since it shows only blank screen after selecting installation > mode (both graphical and text). Screen doesn't work but system still > seems to alive because when I've selected "Install with speech synthesis" > it speaks. > > UEFI secure boot was disabled, and it looks similar to Bug#899240 > but it doesn't work even if legacy boot is enabled. > > > However, Ubuntu 18.04.1 boots successfully, so I can get hardware info and > attach it to this report. > > Any ideas? > > - > Success > - Ubuntu18.04.1 (Linux 4.15.0-29-generic) > > Fail > - Debian9.4 > - both Debian Installer Buster Alpha 3 release and daily image > > Machine > - name: HP EliteBook 830 G5/CT Notebook PC > - cpu: Core i5-7200U (skylake) > - graphic: Intel HD graphics 620 -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#909658: debian-installer: blank screen on install (HP Elitebook 830 G5)
Package: debian-installer Severity: important Hi, I've tried to install Debian on my new laptop HP EliteBook 830 G5 but failed since it shows only blank screen after selecting installation mode (both graphical and text). Screen doesn't work but system still seems to alive because when I've selected "Install with speech synthesis" it speaks. UEFI secure boot was disabled, and it looks similar to Bug#899240 but it doesn't work even if legacy boot is enabled. However, Ubuntu 18.04.1 boots successfully, so I can get hardware info and attach it to this report. Any ideas? - Success - Ubuntu18.04.1 (Linux 4.15.0-29-generic) Fail - Debian9.4 - both Debian Installer Buster Alpha 3 release and daily image Machine - name: HP EliteBook 830 G5/CT Notebook PC - cpu: Core i5-7200U (skylake) - graphic: Intel HD graphics 620 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 02) Subsystem: Hewlett-Packard Company Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 02) Subsystem: Hewlett-Packard Company Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) (prog-if 30 [XHCI]) Subsystem: Hewlett-Packard Company Sunrise Point-LP USB 3.0 xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP Thermal subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP Serial IO I2C Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP Serial IO I2C Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) Subsystem: Hewlett-Packard Company Sunrise Point-LP CSME HECI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:1c.0 PCI bridge: Intel Corporation Device 9d13 (rev f1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge: Intel Corporation Sunrise Poi
Are you still interested in debootstrap?
Hi Junichi, I asked you about this via twitter several times but I got no answer, you are nominated as debootstrap uploaders but never done it. Do you want to stay there or not? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#893713: debootstrap-udeb: containts too many scripts files (most of them are symlink but...)
On Sat, 25 Aug 2018 09:11:45 +0200 Raphael Hertzog wrote: > you should really add some automated test > to catch the regressions. Well, limited to this time, how did I catch its regression with test? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#893713: debootstrap-udeb: containts too many scripts files (most of them are symlink but...)
On Tue, 21 Aug 2018 12:37:00 +0200 Raphael Hertzog wrote: > While cleaning up the list of scripts to keep, you decided to drop the > scripts for all derivatives making it impossible to use the udeb built > for Debian on any derivative (Kali bug report here: > https://bugs.kali.org/view.php?id=4921) It was not correct assumptions that derivatives use it own udeb packages, my apologies. > So you saved a few kilobytes and made the life harder for others. > IMO it was the wrong decision. It was my mistake, of course, but I DON'T WANT TO MAKE SOMEONE'S LIFE ANY HARDER, IT IS NOT INTENDED. People who made wrong decision should be blamed as fool? If so, please revert debootstrap before I started to commit to it. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#891009: debootstrap: wrongly falls back to https://deb.debian.org when try to create Ubuntu chroot
On Wed, 21 Feb 2018 22:31:02 +0900 Hideki Yamane wrote: > And, https assures only secure *connection*, not integrity of *contents* > as GPG does, so this behavior is not good, IMO. As I said above, what https ensures and gpg does is different, and "if there's no reliable keyring then fallback to https connection" behavior is not good. I suggest to remove this feature from debootstrap, do you have any idea for it? If so, please let me know it and why. -- Hideki Yamane
Re: Q: What's the relationship between Secure Boot and debootstrap?
On Thu, 2 Aug 2018 15:31:38 +0800 Helen Koike wrote: > Yes, that was my fault, sorry about that, I meant we needed to check and > update the tools that generate images. No problem. BTW, is there any planned schedule to complete to enable SB in Debian? I heard about there's a much progress for it but not sure when it will come to Debian. -- Hideki Yamane
Bug#905165: debootstrap - fails in docker environment
On Wed, 1 Aug 2018 07:55:07 +0200 Bastian Blank wrote: > Package: debootstrap > Version: 1.0.106 > Severity: grave > > debootstrap fails in docker environment completely by: Could you try 1.0.107 in git repo, please? I was in trouble with uploading it, but it would be better one. And if it still happens, please describe reproduce step for it. -- Hideki Yamane
Re: Q: What's the relationship between Secure Boot and debootstrap?
On Wed, 1 Aug 2018 14:47:58 +0100 Steve McIntyre wrote: > Yup, just updated in git now... Thanks! :) -- Hideki Yamane
Re: Towards Debian Buster Alpha 4
Hi, On Tue, 31 Jul 2018 02:06:40 +0200 Cyril Brulebois wrote: > If you have changes pending in master branches that need uploading, or > specific packages that need to reach testing, please mention which, and > why. I failed to upload debootstrap 1.0.107 but will do it after DebConf. And will upload 1.0.108 with some fixes (not apply speedup patches). -- Hideki Yamane
Re: Q: What's the relationship between Secure Boot and debootstrap?
On Tue, 31 Jul 2018 17:11:14 +0100 Steve McIntyre wrote: > That kind of thing, yes. Should have been clearer. Debootstrap itself > doesn't install a kernel or bootloader, which were the packages I was > thinking about. Then, we don't need to modify debootstrap package for SB at all, right? If so, please update your slide before upload. -- Hideki Yamane
Q: What's the relationship between Secure Boot and debootstrap?
Hi, During "Report from the Debian EFI team about the support of Secure Boot on Debian" session, you said that maybe we should touch debootstrap, but I'm not sure what should we do for it. Could you explain your thought for it, please? -- Hideki Yamane
Bug#728344: debootstrap does not report errors
On Wed, 30 Oct 2013 23:30:56 +0100 Michal Suchanek wrote: > This is quite likely broken but debootstrap should report the error and not > just silently terminate. Here's a proposed Merge Request https://salsa.debian.org/installer-team/debootstrap/merge_requests/20 -- Hideki Yamane
Bug#904804: debootstrap: Unable to deboostrap a sid environment on stretch
control: reassign -1 util-linux Hi, On Sat, 28 Jul 2018 15:47:39 +0800 Nicolas Braud-Santoni wrote: > I just realised it's currently impossible to debootstrap a sid (build) > environment on Debian stretch, creating difficulties for attendees of the > DebConf packaging workshop, presumably because of util-linux being > uninstallable. I confirmed it with current debootstrap on sid, but it's not debootstrap's fault but it's in repo. >> login (1:4.5-1.1) breaks util-linux (<< 2.32-0.2~) and is installed. > shadow (1:4.5-1.1) unstable; urgency=medium > > * Non-maintainer upload (greetings from DebCamp/DebConf Taiwan). > * Stop shipping su and break old util-linux version. (See #833256) > - Breaks on old version to force lockstep upgrade, which should > really be a depends-new-version (and can be switched around > together with util-linux once the transition is finished). > Using Breaks/Depends the 'wrong' way around is to make apt > unpack things in the 'right' order (avoiding any gaps where > /bin/su is not available during the upgrade phase). > > -- Andreas Henriksson Fri, 27 Jul 2018 10:07:37 +0200 However, util-linux is (2.32-0.1). I'm not sure which side should care about it, but once reassign to util-linux. -- Hideki Yamane
Bug#871835: speed up for debootstrap
On Fri, 27 Jul 2018 11:25:40 +0200 Cyril Brulebois wrote: > For some reason it seems I didn't follow up to this bug report but I'm > pretty sure I did reply on debian-boot@ in some way: we need automated > tests before and after those patches. And we need to make sure they > yield the exact same results. Please don't merge the whole stack of > patches without such checks. I heard about Thomas has set his test system and works well. It'd be better to share its info, then. -- Hideki Yamane
Bug#871835: speed up for debootstrap
Hi, As prepared MR in https://salsa.debian.org/installer-team/debootstrap/merge_requests/19 I'll put it into 1.0.108, _after DebConf_ since I don't have GPG key on my laptop (I have the new one but it's not in keyring now). If some one want to push 1.0.107 into repository, it's nice. -- Hideki Yamane
Bug#893713: debootstrap-udeb: containts too many scripts files (most of them are symlink but...)
On Fri, 23 Mar 2018 21:40:08 +0900 Hideki Yamane wrote: > > What's the problem here? > > It's not a problem, but we can improve it, IMO (so severity is low). Proposed Merge Request https://salsa.debian.org/installer-team/debootstrap/merge_requests/15 -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#902350: systemd-container: /proc/1/environ doesn't contain
Hi, On Mon, 25 Jun 2018 16:55:40 +0200 Cyril Brulebois wrote: > Please anchor the grep pattern to avoid accidental matches against > variables whose name ends with container (e.g. foo_container), and > values which start with lxc-libvirt (e.g. lxc-libvirt-something-else); > adding ^ on the left and $ on the right would do that. Thanks, indeed. And Ben suggested just use $container and it's better. > It seems there are quite a number of other places with such issues. I'll look into it, later. -- Hideki Yamane
Bug#902350: systemd-container: /proc/1/environ doesn't contain
"container=systemd-nspawn" info Message-Id: <20180625231751.08904561b88a44c993b3f...@iijmio-mail.jp> In-Reply-To: <20180625214341.1adc6be263157d3184907...@iijmio-mail.jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 25 Jun 2018 21:43:41 +0900 Hideki Yamane wrote: > I've got a suggestion to use $container to detect systemd-nspawn, > it can be used before/after 239-1. debootstrap should be changed > to use it, so reassign to debootstrap. I've created MergeRequest as https://salsa.debian.org/installer-team/debootstrap/merge_requests/13 Please review it. -- Hideki Yamane
Bug#901717: debootstrap: Version 1.0.102 breaks use of file mirrors
Hi, On Sat, 23 Jun 2018 11:14:58 +0100 Christopher Obbard wrote: > $ cat test/debootstrap/debootstrap.log > ... > /debootstrap/debootstrap: 1428: /debootstrap/debootstrap: cannot open > //var/lib/apt/lists/http:__deb.debian.org_debian_dists_buster_main_binary-armhf_Packages: > No such file Oh, that is not expected, installation was failed... Here's a proposed patch. diff --git a/debootstrap b/debootstrap index 023a54f..c61636f 100755 --- a/debootstrap +++ b/debootstrap @@ -422,6 +422,7 @@ fi if [ "$SECOND_STAGE_ONLY" = "true" ]; then SUITE=$(cat "$DEBOOTSTRAP_DIR/suite") ARCH=$(cat "$DEBOOTSTRAP_DIR/arch") + USER_MIRROR=$(cat "$DEBOOTSTRAP_DIR/mirror") if [ -e "$DEBOOTSTRAP_DIR/variant" ]; then VARIANT=$(cat "$DEBOOTSTRAP_DIR/variant") SUPPORTED_VARIANTS="$VARIANT" @@ -725,6 +726,7 @@ if am_doing_phase first_stage; then cp "$DEBOOTSTRAP_DIR"/scripts/*-common "$TARGET/debootstrap/" echo "$ARCH">"$TARGET/debootstrap/arch" echo "$SUITE" >"$TARGET/debootstrap/suite" + echo "$USER_MIRROR" >"$TARGET/debootstrap/mirror" [ "" = "$VARIANT" ] || echo "$VARIANT" >"$TARGET/debootstrap/variant" echo "$required">"$TARGET/debootstrap/required" > >> we should write the file mirror URI to sources.list > > > > And that assumption needs to be discussed. > > > > If we would create chroot with debootstrap specified with file:/// > > mirror and bring it to another environment, sources.list should > > point local file mirror or not? > > You are right, thinking about it mirror URI should not added to sources.list. > I do like the original method debootstrap 1.0.101 uses of caching the > list of packages when using a file mirror under debootstrap.invalid. > All of the packages are cached in the first-stage anyway. > > After the install is complete, we should clear /etc/apt/sources.list > of debootstrap.invalid. > The user should update /etc/apt/sources.list himself anyway. I prefer to use http(s)://deb.debian.org/debian as default mirror setting for it, since it's okay for most users and works.
Bug#774331: debootstrap: fakechroot variant fails with fakechroot not found
control: tags -1 +unreprodocible Hi, Running "$ fakechroot fakeroot /usr/sbin/debootstrap --variant=fakechroot jessie jessie" on Jessie works fine, on Stretch and newer fakechroot causes segfault but it is not debootstrap's fault. Vagrant Cascadian wrote: > And in debootstrap.log: > > Setting up systemd (215-8) ... > Initializing machine ID from random generator. > chfn: PAM: System error > adduser: `/usr/bin/chfn -f systemd Time Synchronization > systemd-timesync' returned error code 1. Exiting. > dpkg: error processing package systemd (--configure): >subprocess installed post-installation script returned error exit >status 1 >Setting up dmsetup (2:1.02.90-2) ... >dpkg: systemd-sysv: dependency problems, but configuring anyway as you >requested: > systemd-sysv depends on systemd (= 215-8); however: > Package systemd is not configured yet. >systemd-sysv depends on systemd; however: > Package systemd is not configured yet. It seems that is fakechroot issue, too. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745082 -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: debootstrap/1.0.102 appears to break debuerreotype autopkgtest
On Tue, 19 Jun 2018 09:23:18 +0200 Ansgar Burchardt wrote: > I'm not sure why >= stretch should be more complicated? Something like > [1] (untested) should work? > > [1] > <https://salsa.debian.org/ansgar/debootstrap/commits/allow-merged-usr-for-stretch-again> Aha, it means just clicking merge button is easy for me ;) -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: debootstrap/1.0.102 appears to break debuerreotype autopkgtest
Hi, On Tue, 19 Jun 2018 08:09:17 +0200 Ansgar Burchardt wrote: > The `-k` option doesn't work for older releases (some packages do > replace files there). It should always be used for newer releases (>= > stretch) to have less differences between --merged-usr and > --no-merged-usr. >= stretch ? If it's >= buster (not include stretch), it's easy to apply changes. > (As it should always be applied it shouldn't be set in > `setup_merged_usr` as that is misleading.) Okay, thanks. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#731859: Happens to me on stretch
Hi, On Mon, 18 Jun 2018 20:22:28 +0900 Hideki Yamane wrote: > > Here are ways you can run it: > > > > ./bug-731859-demo-v2.sh stretch chroot With provided script, it runs debootstrap under chroot, however, debootstraped environment under chroot causes problem with symlink. $ sudo chroot stretch.chroot true $ sudo chroot stretch.chroot/home/x/stretch/ true chroot: failed to run command 'true': No such file or directory $ ls -al stretch.chroot/home/x/stretch/lib64/ total 8 drwxr-xr-x 2 henrich henrich 4096 6月 19 02:36 . drwxr-xr-x 19 henrich henrich 4096 6月 19 02:38 .. lrwxrwxrwx 1 henrich henrich 47 1月 14 10:39 ld-linux-x86-64.so.2 -> /home/x/stretch/lib/x86_64-linux-gnu/ld-2.24.so I don't know why, but ld-linux-x86-64.so.2 point not point to /lib/x86_64-linux-gnu/ld-2.24.so, this scripts always returns error. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#901826: fakechroot doesn't work on sid
Package: fakechroot Version: 2.19-3 Severity: important Dear Maintainer, fakechroot works on Stretch but not on Sid. >henrich@stretch1:~$ fakechroot --version >fakechroot version 2.19 >henrich@stretch1:~$ fakechroot chroot stretch true >henrich@stretch1:~$ echo $? >0 >henrich@sid1:~$ fakechroot --version >fakechroot version 2.19 >henrich@sid1:~$ fakechroot chroot sid /bin/true >/usr/sbin/chroot: failed to run command '/bin/true': No such file or directory Any suggestion? -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fakechroot depends on: ii libfakechroot 2.19-3 fakechroot recommends no packages. fakechroot suggests no packages. -- no debconf information
Bug#731859: Happens to me on stretch
Hi,
On Mon, 18 Jun 2018 12:15:51 +1000
Russell Stuart wrote:
> I didn't get that failure, but a postinst expecting /proc to be mounted
> doesn't sound unreasonable.
Hmm.
> > I'm not sure how to run nested chroot with success, it means
> > "chroot "/tmp/${suite}" /bin/sh" line would still fail, though.
>
> The nested chroot was just a way of getting a repeatable test
> environment in a few lines of shell script. It worked for me, but
> apparently not for you. So I've attached a new version which provides
> numerous environments. They all fail for me in exactly the same way
> the simple one did; hopefully you will find at least of them more
> illuminating than my previous effort. Sadly it's an order of magnitude
> larger.
>
> Here are ways you can run it:
>
> ./bug-731859-demo-v2.sh stretch chroot
> ./bug-731859-demo-v2.sh stretch nspawn
> ./bug-731859-demo-v2.sh stretch kvm
> ./bug-731859-demo-v2.sh buster chroot
> ./bug-731859-demo-v2.sh buster nspawn
> ./bug-731859-demo-v2.sh buster kvm
>
> The "chroot" environment is as before, but with dev, dev/pts, proc and
> sys mounted in the chroot when the demonstration runs. The "nspawn" is
> a systemd-nspawn running in a directory identical to the chroot. "kvm"
> is a qemu-system-x86_64 VM using an identical directory as it's root
> file system. It will drop you in a shell when it starts. Run the
> demonstration by running /bug.sh. Press Control-A followed by x to
> exit.
>
> When running these tests either unset the http_proxy environment
> variable or set it to something that will work inside all environments.
I've run it and got failure as below (my question is can we run nested
chroot without failure?)
> ./bug-731859-demo-v2.sh stretch chroot
+ chroot /tmp/stretch /bin/sh
chroot: failed to run command '/bin/sh': No such file or directory
> ./bug-731859-demo-v2.sh stretch nspawn
I: Base system installed successfully.
+ chroot /home/x/stretch /bin/sh
chroot: failed to run command '/bin/sh': No such file or directory
+ ls -l /home/x/stretch/sbin/ldconfig /home/x/stretch/sbin/ldconfig.REAL
-rwxr-xr-x 1 x x 67 Jun 18 16:47 /home/x/stretch/sbin/ldconfig
-rwxr-xr-x 1 x x 881912 Jan 14 19:39 /home/x/stretch/sbin/ldconfig.REAL
Container stretch.nspawn exited successfully.
> ./bug-731859-demo-v2.sh stretch kvm
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... [3.245515] Btrfs loaded,
crc32c=crc32c-generic
Scanning for Btrfs filesystems
[3.324262] print_req_error: I/O error, dev fd0, sector 0
[3.327074] floppy: error 10 while reading block 0
[3.411652] random: fast init done
done.
[3.445007] cryptd: max_cpu_qlen set to 1000
Warning: fsck not present, so skipping root file system
[3.492000] EXT4-fs (sda): mounting ext2 file system using the ext4 subsystem
[3.495787] EXT4-fs (sda): mounted filesystem without journal. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
/bin/sh: 0: can't access tty; job control turned off
> ./bug-731859-demo-v2.sh buster chroot
I: Base system installed successfully.
+ chroot /home/x/buster /bin/sh
chroot: failed to run command '/bin/sh': No such file or directory
+ ls -l /home/x/buster/sbin/ldconfig /home/x/buster/sbin/ldconfig.REAL
-rwxr-xr-x 1 x x 67 Jun 18 10:07 /home/x/buster/sbin/ldconfig
-rwxr-xr-x 1 x x 901088 Mar 29 19:47 /home/x/buster/sbin/ldconfig.REAL
+ exit
+ umount buster.chroot/sys
+ umount buster.chroot/proc
+ umount buster.chroot/dev/pts
+ umount buster.chroot/dev
> ./bug-731859-demo-v2.sh buster nspawn
I: Base system installed successfully.
+ chroot /home/x/buster /bin/sh
chroot: failed to run command '/bin/sh': No such file or directory
+ ls -l /home/x/buster/sbin/ldconfig /home/x/buster/sbin/ldconfig.REAL
-rwxr-xr-x 1 x x 67 Jun 18 17:03 /home/x/buster/sbin/ldconfig
-rwxr-xr-x 1 x x 901088 Mar 30 04:47 /home/x/buster/sbin/ldconfig.REAL
Container buster.nspawn exited successfully.
> ./bug-731859-demo-v2.sh buster kvm
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... [3.308450] Btrfs loaded,
crc32c=crc32c-generic
Scanning for Btrfs filesystems
[3.384200] print_req_error: I/O error, dev fd0, sector 0
[3.386911] floppy: error 10 while reading block 0
[3.471441] random: fast init done
done.
[3.504605] cryptd: max_cpu_qlen set to 1000
Warning: fsck not present, so skipping root file system
[3.548903] EXT4-fs (sda): mounting ext2 file system using the ext4 subsystem
[3.553363] EXT4-fs (sda): mounted filesystem without journal. Opts: (null)
don
Bug#899155: systemd-setup-machine-id leaving mount behind?
Hi, On Wed, 13 Jun 2018 15:16:00 +0200 Michael Biebl wrote: > Control: reassign -1 debootstrap > Control: found -1 1.0.98 > > I'm going to reassign this bug report to debootstrap given it was > introduced by the changes in 1.0.98, specifically [1] Now I've fixed it as https://salsa.debian.org/installer-team/debootstrap/merge_requests/11 Could someone review (& merge) it, please? -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: debootstrap/1.0.102 appears to break debuerreotype autopkgtest
Hi, On Fri, 15 Jun 2018 07:57:21 +0900 Hideki Yamane wrote: > > > Instead of stretch simply defaulting to non-merged-usr, it's now > > > _blacklisted_ from merged-usr, even if I explicitly specify > > > "--merged-usr", right? Is that the intended implementation here? > > Yes, since releases until stretch was already shipped without merged-usr, > so it should be. But loose restriction for test purpose is okay, IMO. Anyway, I've created a patch for it. Please review it https://salsa.debian.org/installer-team/debootstrap/merge_requests/12 -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#731859: Happens to me on stretch
Hi,
On Sun, 27 May 2018 21:19:20 +1000 Russell Stuart
wrote:
> The attached script ("bug-731859-demo.sh") does a nested debootstrap
> run. The outer run sets up a chroot for the Debian suite passed on
> the command line (eg, "stretch"), then runs a nested debootstrap --
> variant=fakechroot in that environment. For me both these fail:
>
> ./bug-731859-demo.sh stretch
> ./bug-731859-demo.sh buster
Thank you for providing script :)
I've tested it and got failure. However, I could fix it a bit by adding
"sudo mount -t proc none "${suite}.chroot/proc"" after debootstraping.
Because debootstrap failure is caused by "systemd-machine-id-setup" in
systemd.postinst, and can improve it with /proc mount.
Russell, could you test it, please?
> They fail in different ways, but the root cause appears to be the same:
> the ldconfig isn't working. Note that both leave ldd.REAL and
> ldconfig.REAL lying around in the nested run.
I'm not sure how to run nested chroot with success, it means
"chroot "/tmp/${suite}" /bin/sh" line would still fail, though.
--
Hideki Yamane
Re: debootstrap/1.0.102 appears to break debuerreotype autopkgtest
Hi, On Thu, 14 Jun 2018 10:15:51 -0700 Tianon Gravi wrote: > > Instead of stretch simply defaulting to non-merged-usr, it's now > > _blacklisted_ from merged-usr, even if I explicitly specify > > "--merged-usr", right? Is that the intended implementation here? Yes, since releases until stretch was already shipped without merged-usr, so it should be. But loose restriction for test purpose is okay, IMO. Question with 'EXTRACT_DEB_TAR_OPTIONS="$EXTRACT_DEB_TAR_OPTIONS -k"' It was introduced https://bugs.debian.org/838388 , so it should not be applied to all releases. However, I'm not sure which "older" release for it, especially whether it equals to merged-usr. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: Re: debootstrap/1.0.102 appears to break debuerreotype autopkgtest
Hi, > The patch for #839046 also disabled --merged-usr for stretch as stretch > was added to the blacklist in first_stage_install(). > > debootstrap should default to non-merged-usr for stretch, but it should > be possible to enable merged-usr via the command-line parameter to avoid > the regression in debuerreotype. Stretch is blacklisted (in scripts/debian-common) and I've tested on my box, it is non-merged-usr environment. Is it stretch? We can use "--no-merged-usr" and "--merged-usr" options explicitly. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#594052: debootstrap: create example /etc/hosts and /etc/fstab?
Hi, Thank you for your explanation. debootstrap is used to create just not simple chroot but for containers, like lxc, systemd-nspawn, etc., so adding sample /etc/fstab and hosts is better for them, IMO. On Tue, 5 Jun 2018 08:58:21 +0200 Samuel Thibault wrote: > We could also see at merging deboostrap and crosshurd, since they > are two tools which do almost the same thing, and see crosshurd's > README.Debian suggesting so. Okay, I'll check it. BTW, is there any known blocker to merge them? -- Hideki Yamane
Bug#594052: debootstrap: create example /etc/hosts and /etc/fstab?
Hi, On Mon, 23 Aug 2010 15:18:45 +0200 Samuel Thibault wrote: > Colin Watson, le Mon 23 Aug 2010 12:45:12 +0100, a écrit : > > Does anyone have any thoughts on this? > > Mmm, aren't you actually looking for crosshurd? (which should really be > called crossdebian nowadays). AIUI, using debootstrap is just meant for > chroots & such. You mean, adding /etc/fstab sample is harm for hurd (or kfreebsd)? If so, how about if we can apply it for only linux? -- Hideki Yamane
Re: Processed: Bug #551838 in debootstrap marked as pending
Hi, I've prepared MergeRequest as https://salsa.debian.org/installer-team/debootstrap/merge_requests/8 > Make --unpack-tarball works properly (it means, just extract tarball and > configure it without any downloads) > > > --unpack-tarball just exec "first_stage" and "second_stage" phase, ignore > "finddebs" and "dldebs" > Some options overwrites phases info each other, so make them exclusive > Save some package info to file to include to tarball made with --make-tarball Please review and merge it, thanks. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: debootstrap does not carry --components across --foreign/--second-stage
Hi, I've created patch for this bug report. Could you check it, please? See https://salsa.debian.org/installer-team/debootstrap/merge_requests/7 And please someone on debian-boot list apply this MergeRequest. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#877855: debootstrap does not carry --components across --foreign/--second-stage
Hi,
On Wed, 21 Mar 2018 18:58:27 +0900 Hideki Yamane wrote:
> Since in debootstrap, $TARGET/etc/apt/sources.list is deleted at
> starting for second stage.
And also it was removed in debootstrap script.
> . "$SCRIPT"
>
> if [ "$SECOND_STAGE_ONLY" = "true" ]; then
> MIRRORS=null:
> else
> MIRRORS="$DEF_MIRROR"
> if [ "$USER_MIRROR" != "" ]; then
> MIRRORS="$USER_MIRROR"
> MIRRORS="${MIRRORS%/}"
> fi
> fi
>
> export MIRRORS
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#668903: The installer marks everything manually installed.
control: reassign -1 debian-installer Hi, > This ultimately results in a lot of junk accumulated on the system from > the start... you have to pluck packages out manually and check all of > the 350 or so packages installed by the installer to see if they're > actually required or not. debootstrap pulls several packages but not for the packages from tasks, so I want to reassign back to debian-installer. -- Hideki Yamane
Bug#557322: manpage: mention that dependency resolution can readd excluded packages
control: tags -1 +pending Hi, Now --exlucde works properly and it is not added again (and maybe break dependency). -- Hideki Yamane
Bug#783589: debootstrap --exclude=dash doesn't
control: tags -1 +pending Now we can execute --exclude=dash (however, of course it fails ;) $ DEBOOTSTRAP_DIR=./ sudo ./debootstrap --cache-dir=/home/henrich/tmp/cache --exclude=dash stretch ~/tmp/stretch I: Target architecture can be executed (snip) W: Failure trying to run: chroot "/home/henrich/tmp/stretch" dpkg --force-depends --install /var/cache/apt/archives/base-passwd_3.5.43_amd64.deb W: See /home/henrich/tmp/stretch/debootstrap/debootstrap.log for details In debootstrap.log, > dpkg: warning: 'sh' not found in PATH or not executable > dpkg: error: 1 expected program not found in PATH or not executable > Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin -- Hideki Yamane
Bug#888709: debootstrap: Silently fails if the target directory exists and is not empty.
control: fixed -1 1.0.97 Hi, This behavior was fixed in 1.0.97 as > * Forbid the usage of non-empty directories with --print-debs and >--make-tarball Now we can see message as below. $ debootstrap --print-debs stretch ~/tmp/stretch E: Target directory '/home/henrich/tmp/stretch' is not empty and it would be wiped -- Hideki Yamane
Re: debootstrap: [idea] force review before commit to master
On Mon, 21 May 2018 00:29:55 +0100
Simon McVittie wrote:
> However, it seems plausible that Docker wouldn't allow the fake schroot
> or the fake pbuilder to run either - I don't think Docker containers are
> allowed to exercise CAP_SYS_ADMIN, which is needed when playing with
> mount points. It might be necessary to skip that part. Unfortunately
> systemd-detect-virt --container doesn't seem to detect Docker as anything
> more specific than "container-other", so the test script might have to
> resort to looking for mentions of docker in /proc/self/mountinfo,
> or pessimistically assume that "container-other" has all possible
> container limitations.
Then, how about checking /proc/1/mountinfo with " /docker" and "cgroup"
like this?
diff --git a/debian/tests/debian-testing b/debian/tests/debian-testing
index 9b39896..52d4584 100755
--- a/debian/tests/debian-testing
+++ b/debian/tests/debian-testing
@@ -32,6 +32,16 @@ sub capture {
return $output;
}
+my $check_non_docker_env;
+if (run([qw(grep "\ \/docker.*cgroup" /proc/1/mountinfo)], '&>', '/dev/null'))
{
+diag("it seems docker environment");
+$check_non_docker_env = 0;
+}
+else {
+diag("okay, it's not docker environment");
+$check_non_docker_env = 1;
+}
+
my @maybe_unshare_mount_ns;
if (verbose_run(['unshare', '-m', 'true'])) {
@@ -255,8 +265,10 @@ if (!verbose_run(['debootstrap',
BAIL_OUT("debootstrap failed: $?");
}
-check_chroot(chroot => 'chroot.d', can_mknod_ptmx => $can_mknod_ptmx,
-kernel => $kernel, container => $container);
+if ($check_non_docker_env) {
+check_chroot(chroot => 'chroot.d', can_mknod_ptmx => $can_mknod_ptmx,
+kernel => $kernel, container => $container);
+}
if ($^O ne 'linux') {
diag("Cannot use systemd-nspawn on non-Linux");
Bug#839046: [PATCH] Enable merged-/usr by default again now that dpkg-shlibdeps is fixed (Closes: #839046)
On Sun, 27 May 2018 21:08:42 +0200 Raphael Hertzog wrote: > If anything your argument would mean that we should have different default > for the --merged-usr flag for different release. This might indeed be > important if we want to make sure that recent debootstrap do not introduce > unexpected problems when building chroot for very old releases. Yes, I mean that. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#839046: [PATCH] Enable merged-/usr by default again now that dpkg-shlibdeps is fixed (Closes: #839046)
On Tue, 22 May 2018 16:21:01 +0200 Raphael Hertzog wrote: > I don't understand your question. The required fixes are in the version of > dpkg that is in stretch. I mean, if we try to create new stretch chroot with merged-usr, it becomes to be NOT equal to stretch environment since its /lib*, /bin and /sbin are merged to /usr. We should not apply it for pre-buster, IMHO. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#742672: allow debootstrap to take a bare codename as the script parameter
control: tags -1 +pending Hi, I've created Merge Request as https://salsa.debian.org/installer-team/debootstrap/merge_requests/2 Please someone review it. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#896071: debootstrap fails to retrive Release file over https
On Sun, 20 May 2018 10:14:13 +0200 Philipp Kern wrote: > So the way it works with your patch is that local variables are > inherited by called functions (but not the caller). So from and dest > from just_get() are visible in wgetprogress() and hence the construction > of $@ works. I'd rather have $dest and $from be explicit parameters to > wgetprogress. Given that you reset $@ anyway I don't see how that'd hurt. Hmm, but if I don't put $dest and $from to $@ and other parameters are empty, then it would be extracted as '' and wget will fail. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Re: debootstrap: [idea] force review before commit to master
On Fri, 18 May 2018 21:15:35 +0200
Philipp Kern wrote:
> I suppose the test harness is autopkgtest? Is there prior art on how to
> set that up on Salsa? (Picking the backend and making sure that it
> works, for instance.)
Usually I just put debian/.gitlab-ci.yml as below, build package and
kick autopkgtest automatically.
-
image: debian:sid
variables:
# adjust to your source package
PKG: screenfetch
stages:
- build
- autopkgtest
package_build:
stage: build
script:
- echo "deb-src http://deb.debian.org/debian sid main" >>
/etc/apt/sources.list && apt update -qq && apt build-dep ./ -y -qq
- apt install -y -qq dpkg-dev && dpkg-buildpackage -us -uc -b && mkdir
build; cd ../; ls -al && mv ./${PKG}_*.deb ./${PKG}_*.changes ${PKG}/build/
artifacts:
paths:
- build/*.deb
- build/*.changes
#piuparts:
# stage: piuparts
# script:
#- apt update -qq && apt install -y -qq piuparts
#- piuparts --mirror=http://deb.debian.org/debian --logfile=../piuparts.log
--fail-on-broken-symlinks build/*.changes
# dependencies:
#- package_build
autopkgtest:
stage: autopkgtest
script:
- apt update -qq && apt install -y -qq autopkgtest
- autopkgtest build/*.changes -- null
dependencies:
- package_build
Bug#896071: debootstrap fails to retrive Release file over https
On Sat, 19 May 2018 20:18:17 +0200 Philipp Kern wrote: > You local'ed from and dest and now don't pass it anymore to > wgetprogress. How does this work? It is passed to wget via $@ -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#839046: [PATCH] Enable merged-/usr by default again now that dpkg-shlibdeps is fixed (Closes: #839046)
On Thu, 17 May 2018 11:37:32 +0200 Laurent Bigonville wrote: > + * Enable merged-/usr by default again now that dpkg-shlibdeps is fixed Is it applied to from buster to sid? It maybe break the enviroment until stretch release. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Bug#896071: debootstrap fails to retrive Release file over https
On Mon, 14 May 2018 00:48:53 +0200
Philipp Kern wrote:
> any new about incorporating Raphael's suggestion? There's still a grave
> bug opened against debootstrap right now (on a version that is in testing).
Sorry for late reply, revert previous fix and modified functions as
Raphael suggested, and it works on my box. Please check it.
diff --git a/functions b/functions
index dc55faf..350f463 100644
--- a/functions
+++ b/functions
@@ -79,6 +79,18 @@ progress_next () {
wgetprogress () {
[ ! "$VERBOSE" ] && NVSWITCH="-nv"
local ret=0
+
+ set -- -O "$dest" "$from" "$@"
+ if [ -n "$PRIVATEKEY" ]; then
+ set -- "$PRIVATEKEY" "$@"
+ fi
+ if [ -n "$CERTIFICATE" ]; then
+ set -- "$CERTIFICATE" "$@"
+ fi
+ if [ -n "$CHECKCERTIF" ]; then
+ set -- "$CHECKCERTIF" "$@"
+ fi
+
if [ "$USE_DEBIANINSTALLER_INTERACTION" ] && [ "$PROGRESS_NEXT" ]; then
wget "$@" 2>&1 >/dev/null | "$PKGDETAILS" "WGET%"
"$PROGRESS_NOW" "$PROGRESS_NEXT" "$PROGRESS_END" >&3
ret=$?
@@ -401,20 +413,14 @@ just_get () {
# args: from dest
local from="$1"
local dest="$2"
+
mkdir -p "${dest%/*}"
+
if [ "${from#null:}" != "$from" ]; then
error 1 NOTPREDL "%s was not pre-downloaded" "${from#null:}"
- elif [ "${from#http://}"; != "$from" ] || [ "${from#ftp://}"; != "$from"
]; then
- # http/ftp mirror
- if wgetprogress -O "$dest" "$from"; then
- return 0
- else
- rm -f "$dest"
- return 1
- fi
- elif [ "${from#https://}"; != "$from" ] ; then
- # http/ftp mirror
- if wgetprogress "$CHECKCERTIF" "$CERTIFICATE" "$PRIVATEKEY" -O
"$dest" "$from"; then
+ elif [ "${from#http://}"; != "$from" ] || [ "${from#ftp://}"; != "$from"
] || [ "${from#https://}"; != "$from" ]; then
+ # HTTP(S) mirror (FTP mirror is deprecated but not removed)
+ if wgetprogress ; then
return 0
else
rm -f "$dest"
Re: debootstrap/1.0.98 breaks debomatic/0.23-1 autopkgtest in testing
On Wed, 16 May 2018 13:53:11 +0200 Paul Gevers wrote: > > This is due to #898738. > > Thanks for picking this up, but why then didn't it fail with debootstrap > 1.0.97¹ as the bug suggests that version had the same issue. Hmm, it seems that runs fine again with debootstrap 1.0.99 https://ci.debian.net/data/packages/unstable/amd64/d/debomatic/311372.log -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
