Two questions on update_initramfs (in Debian 9 amd64 with systemd)

[Frantisek Rysanek]

Dear everyone,

I'm playing with NFSroot and overlayfs.
Which appears to work fine.
Based on other people's work, I've put together a script
(see it attached, including credits of my key "inspirations")
that goes into

   /etc/initramfs-tools/scripts/init-bottom/

Obviously this gets embedded in the initial ramdisk if I run

   update_initramfs -u -k my.kernel.version

and the point is that the script then runs at early stages of boot, 
where it can insert an overlayFS layer while the NFS mountpoint
stays "read only" all the time (if so desired).
There are a number of tangential notes that are off topic here, I may 
eventually leave a blog entry or something later on, when I'm happy 
with the result :-)

The NFS-booted system is a 64bit x86 Debian 9. The "source export" of 
the diskless NFS root lives in a subdirectory on a server (same 
distro). Say /var/NFSboot/stretch/. The NFS-booted Debian has been 
installed in the subdir using a pretty standard method based on 
debootstrap and some final touches in a chrooted shell.
No special sauce here.

I have two questions to ask:

Question #1:
It seems that my script, called overlay.sh, that I placed in
  /etc/initramfs-tools/scripts/init-bottom/
gets executed by update_initramfs "while building the initrd image" !
I.e., when I run update_initramfs in a chroot on my server, I end up 
with some erratic instances of overlayfs mounted on the server :-O
Does this have a rational explanation?
Apologies for being lazy to read the guts of update_initramfs.
If you've read the script, you already know my workaround for this.
(I test for the presence of an environment variable, that's only 
present "at build time" - in which case the interesting 
overlayfs-related stuff gets skipped.)

Question #2:
Anyone who's played with debootstrap or even just cloning an 
installed system to a different disk has probably reached a point
(based on numerous "Debian migration" howto's)
where you need to chroot into the target directory, but before it 
make sense to take that plunge, you first need to bind-mount a 
handful of system directories, served by the kernel via special 
filesystems. I have a tiny script to do the bind-mounts (and 
umounts!) for me, that goes like this:

   mount --bind --make-rslave /proc $DESTDIR/proc
   mount --bind --make-rslave /dev $DESTDIR/dev
   mount --bind --make-rslave /sys $DESTDIR/sys
   mount --bind --make-rslave /run $DESTDIR/run

   chroot $DESTDIR /bin/bash

   umount $DESTDIR/run
   umount $DESTDIR/sys
   umount $DESTDIR/dev
   umount $DESTDIR/proc

The older howtos use just --bind (or the equivalent "-o bind").
There's a Debian FAQ explaining that the "rslave" option is now 
needed, since the arrival of systemd.
  https://wiki.debian.org/systemd#Shared_bind_mounts
The "rslave" option serves to avoid unmounting both the "bind slave"
and the "bind source" mountpoints when just "the slave" mountpoint 
gets unmounted. And yes I have learned the hard way why the rslave 
option is needed, on my server when chrooting for update_initramfs in 
the NFSroot ;-)

So I now have the "rslave" option, and still, after I run 
update_initramfs, I get "side effects": the trailing part of my 
"chroot wrapper script" cannot unmount some of the mountpoints
on the grounds of some of them being busy. The error message from 
umount suggests fuser and one other command to reveal the culprits, 
but in my case those didn't help...

=> so the second question really is: any clues what gets launched by 
update_initramfs, that keeps some of the devices in the "chroot 
directory" open?

It's not a major problem, at least with --make-rslave my host server 
does not collapse anymore when umounting the bind-mounted
slave directories. And instead of the server-side chroot, 
alternatively I can maintain the diskless distro by mounting the 
NFSroot "rw" on a single diskless station... 
(direct RW mount of the NFS export, without an intermediate overlayfs 
layer).

Any clues to my questions would be welcome :-)

Frank Rysanek

The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.

    File information ---
 File:  overlay.sh
 Date:  2 Sep 2019, 23:21
 Size:  2019 bytes.
 Type:  Unknown


overlay.sh
Description: Binary data

Re: Bug#935589: cdimage.debian.org: xserver-xorg-input-synaptics package missing in xfce-CD-1 iso

[Steve McIntyre]

Let's try that again, without the typo in debian-desktop...

On Mon, Sep 02, 2019 at 11:42:44PM +0100, Steve McIntyre wrote:
>control: reassign -1 task-xfce-desktop
>
>Hi Karthik,
>
>On Sat, Aug 24, 2019 at 04:10:53PM +0530, karthik wrote:
>>Package: cdimage.debian.org
>>Severity: normal
>>
>>Dear Maintainer,
>>
>>*** Reporter, please consider answering these questions, where appropriate ***
>>
>>   * What led up to the situation?
>>  After a fresh install of xfce CD testing weekly iso on lenovo x230 
>> laptop, I have noticed that the touchpad options were missing in mouse & 
>> touchpad settings
>>   * What exactly did you do (or not do) that was effective (or
>> ineffective)?
>>  installed xserver-xorg-input-synaptics package 
>>   * What was the outcome of this action?
>>  touchpad options were visible back again!
>>   * What outcome did you expect instead?
>>  same as above
>>
>>Please include this package in upcoming iso builds, It is an important one.
>
>If it's important that it's available, then a better place for the bug
>would be against the task-xfce-desktop package. That way it will be
>pulled in automatically via dependencies for the CD build.
>
>-- 
>Steve McIntyre, Cambridge, UK.st...@einval.com
>The two hard things in computing:
> * naming things
> * cache invalidation
> * off-by-one errors  -- Stig Sandbeck Mathisen
>
>
-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Arguing that you don't care about the right to privacy because you have
 nothing to hide is no different than saying you don't care about free
 speech because you have nothing to say."
   -- Edward Snowden

Processed: Re: Bug#935589: cdimage.debian.org: xserver-xorg-input-synaptics package missing in xfce-CD-1 iso

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 task-xfce-desktop
Bug #935589 [cdimage.debian.org] cdimage.debian.org: 
xserver-xorg-input-synaptics package missing in xfce-CD-1 iso
Bug reassigned from package 'cdimage.debian.org' to 'task-xfce-desktop'.
Ignoring request to alter found versions of bug #935589 to the same values 
previously set
Ignoring request to alter fixed versions of bug #935589 to the same values 
previously set

-- 
935589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935589
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bug#935589: cdimage.debian.org: xserver-xorg-input-synaptics package missing in xfce-CD-1 iso

[Steve McIntyre]

control: reassign -1 task-xfce-desktop

Hi Karthik,

On Sat, Aug 24, 2019 at 04:10:53PM +0530, karthik wrote:
>Package: cdimage.debian.org
>Severity: normal
>
>Dear Maintainer,
>
>*** Reporter, please consider answering these questions, where appropriate ***
>
>   * What led up to the situation?
>   After a fresh install of xfce CD testing weekly iso on lenovo x230 
> laptop, I have noticed that the touchpad options were missing in mouse & 
> touchpad settings
>   * What exactly did you do (or not do) that was effective (or
> ineffective)?
>   installed xserver-xorg-input-synaptics package 
>   * What was the outcome of this action?
>   touchpad options were visible back again!
>   * What outcome did you expect instead?
>   same as above
>
>Please include this package in upcoming iso builds, It is an important one.

If it's important that it's available, then a better place for the bug
would be against the task-xfce-desktop package. That way it will be
pulled in automatically via dependencies for the CD build.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
The two hard things in computing:
 * naming things
 * cache invalidation
 * off-by-one errors  -- Stig Sandbeck Mathisen

Bug#939071: 6.4 Load Missing Firmware should mention unpacking zip/tar

[Miguel Figueiredo]

Hi,

On 02/09/19 16:10, Baptiste Jammet wrote:

[...]


I don't think the installation guide must cover the "how to use a zip
archive" case, but it can maybe suggest to use an external soft and
that firmaware files are *.deb.


Debian includes unzip, why not include it ?



For example, in installation-guide/en/using-d-i/loading-firmware.xml:
[...] and unpack it to
-the file system on the medium.
+the file system on the medium. Use an appropriate software like
+7-Zip (https://www.7-zip.org/)
+or tar (https://www.gnu.org/software/tar/) to obtain a list of *.deb
+files to put in the /firmware directory mentioned.
[...]
It is also possible to copy individual firmware files to the medium. Loose
firmware could be obtained for example from an already installed system or
-from a hardware vendor.
+from a hardware vendor. These files are generally binary files and
+named *.bin.

Baptiste




--
Best regards / Melhores cumprimentos,

Miguel Figueiredo

Processed: severity of 927165 is important

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Was not RC after all
> severity 927165 important
Bug #927165 [debian-installer] debian-installer: improve support for LUKS
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
927165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914712: Add the touchpad drivers to be able to use any compatible touchpad during the installations

[21naown]

Hello,


I am very sorry to send you this reply with such a delay.

The hardware come from Elantech and Synaptics.


Best regards.

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Cyril Brulebois]

Pirate Praveen  (2019-09-02):
> On Mon, Sep 2, 2019 at 10:03 PM, Julien Cristau  wrote:
> > On Mon, Sep  2, 2019 at 21:27:46 +0500, Pirate Praveen wrote:
> > 
> > >  How do I get this file? There is no such log in /var/log. There is
> > > no
> > >  logfile option I can find in manpage.
> > > 
> > Look in /srv/chroot/debian-sid.
> > 
> 
> Thanks. debootstrap.log attached.

I don't really understand what's going on.

Can you please:
 - tell us what environment this is (assuming buster, with backports enabled?)
 - remove the target directory and start over, with the --verbose flag
 - share the new debootstrap.log
 - tell us whether some (transparent) proxy might be having fun with your 
traffic
 - try with forcing either cdn-fastly or cdn-aws
 - try with a different mirror (e.g. ftp.{ch,de,fr}.debian.org)


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Pirate Praveen]

On Mon, Sep 2, 2019 at 10:03 PM, Julien Cristau  
wrote:

On Mon, Sep  2, 2019 at 21:27:46 +0500, Pirate Praveen wrote:

 How do I get this file? There is no such log in /var/log. There is 
no

 logfile option I can find in manpage.


Look in /srv/chroot/debian-sid.



Thanks. debootstrap.log attached.


Cheers,
Julien


amd64: ok
amd64: ok
2019-09-02 20:44:10 URL:http://deb.debian.org/debian/dists/sid/Release.gpg [1601/1601] -> "/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg" [1]
gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
2019-09-02 20:45:06 URL:http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg [1601/1601] -> "/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg" [1]
gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
--2019-09-02 20:45:13--  http://deb.debian.org/debian/dists/sid/Release.gpg
Resolving deb.debian.org (deb.debian.org)... 130.89.148.14, 149.20.4.15, 5.153.231.4, ...
Connecting to deb.debian.org (deb.debian.org)|130.89.148.14|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg [following]
--2019-09-02 20:45:13--  http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg
Resolving cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)... 151.101.156.204, 2a04:4e42:25::204
Connecting to cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)|151.101.156.204|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1601 (1.6K)
Saving to: '/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg'

 0K . 100% 36.2M=0s

2019-09-02 20:45:14 (36.2 MB/s) - '/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg' saved [1601/1601]

gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
2019-09-02 21:05:30 URL:http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg [1601/1601] -> "/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg" [1]
gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
2019-09-02 21:14:43 URL:http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg [1601/1601] -> "/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg" [1]
gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
sed: can't read /srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release: No such file or directory
amd64: ok
sed: can't read /srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release: No such file or directory
amd64: ok
2019-09-02 21:20:49 URL:http://deb.debian.org/debian/dists/sid/Release.gpg [1601/1601] -> "/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg" [1]
gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
--2019-09-02 21:38:56--  http://deb.debian.org/debian/dists/sid/Release.gpg
Resolving deb.debian.org (deb.debian.org)... 130.89.148.14, 128.31.0.62, 5.153.231.4, ...
Connecting to deb.debian.org (deb.debian.org)|130.89.148.14|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg [following]
--2019-09-02 21:38:57--  http://cdn-fastly.deb.debian.org/debian/dists/sid/Release.gpg
Resolving cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)... 151.101.156.204, 2a04:4e42:25::204
Connecting to cdn-fastly.deb.debian.org (cdn-fastly.deb.debian.org)|151.101.156.204|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1601 (1.6K)
Saving to: '/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg'

 0K . 100% 57.7M=0s

2019-09-02 21:38:58 (57.7 MB/s) - '/srv/chroot/debian-sid/var/lib/apt/lists/partial/deb.debian.org_debian_dists_sid_Release.gpg' saved [1601/1601]

gpgv: can't open signed data '/srv/chroot/debian-sid/var/lib/apt/lists/deb.debian.org_debian_dists_sid_Release'
gpgv: can't hash datafile: No such file or directory
amd64: ok
--2019-09-02 21:51:08--  

Processed: Re: Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #939266 {Done: Cyril Brulebois } [debootstrap] debootstrap 
fails to create a sid chroot with Error executing gpgv to check Release 
signature
Bug reopened
Ignoring request to alter fixed versions of bug #939266 to the same values 
previously set

-- 
939266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Julien Cristau]

On Mon, Sep  2, 2019 at 21:27:46 +0500, Pirate Praveen wrote:

> How do I get this file? There is no such log in /var/log. There is no
> logfile option I can find in manpage.
> 
Look in /srv/chroot/debian-sid.

Cheers,
Julien

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Cyril Brulebois]

Control: reopen -1

Pirate Praveen  (2019-09-02):
> On Mon, Sep 2, 2019 at 9:37 PM, Cyril Brulebois  wrote:
> > I think you should install the Recommends before reporting a bug.
> 
> I have all the recommends installed. Why do you assume I don't have it?

I seem to have hit the reply button too fast, apologies for that.

What if you instrument debootstrap's functions file to output what it
sees from gpg? Or wrap the debootstrap call with strace?

Like Julien, I cannot replicate your issue locally.



Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Pirate Praveen]

On Mon, Sep 2, 2019 at 9:47 PM, Julien Cristau  
wrote:

On Mon, Sep  2, 2019 at 21:13:13 +0500, Pirate Praveen wrote:




 On Mon, Sep 2, 2019 at 9:36 PM, Julien Cristau > wrote:

 > Control: tags -1 unreproducible moreinfo
 >
 > On Mon, Sep  2, 2019 at 20:53:13 +0500, Pirate Praveen wrote:
 >
 > >  Package: debootstrap
 > >  Version: 1.0.114, 1.0.115~bpo10+1
 > >  Severity: important
 > >
 > >  I think debootstrap should be able to create a sid chroot but 
fails

 > > with
 > >  this error,
 > >
 > >  $ sudo debootstrap sid /srv/chroot/debian-sid
 > >  I: Target architecture can be executed
 > >  I: Retrieving Release.gpg
 > >  I: Checking Release signature
 > >  E: Error executing gpgv to check Release signature
 > >
 > Works for me.  Care to give more verbose info?
 >

 Even with --verbose there is no extra information, is there another 
way to

 get more information.


Providing debootstrap.log maybe?



How do I get this file? There is no such log in /var/log. There is no 
logfile option I can find in manpage.



Cheers,
Julien

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Julien Cristau]

On Mon, Sep  2, 2019 at 21:13:13 +0500, Pirate Praveen wrote:

> 
> 
> On Mon, Sep 2, 2019 at 9:36 PM, Julien Cristau  wrote:
> > Control: tags -1 unreproducible moreinfo
> > 
> > On Mon, Sep  2, 2019 at 20:53:13 +0500, Pirate Praveen wrote:
> > 
> > >  Package: debootstrap
> > >  Version: 1.0.114, 1.0.115~bpo10+1
> > >  Severity: important
> > > 
> > >  I think debootstrap should be able to create a sid chroot but fails
> > > with
> > >  this error,
> > > 
> > >  $ sudo debootstrap sid /srv/chroot/debian-sid
> > >  I: Target architecture can be executed
> > >  I: Retrieving Release.gpg
> > >  I: Checking Release signature
> > >  E: Error executing gpgv to check Release signature
> > > 
> > Works for me.  Care to give more verbose info?
> > 
> 
> Even with --verbose there is no extra information, is there another way to
> get more information.
> 
Providing debootstrap.log maybe?

Cheers,
Julien

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Pirate Praveen]

On Mon, Sep 2, 2019 at 9:37 PM, Cyril Brulebois  wrote:

I think you should install the Recommends before reporting a bug.


I have all the recommends installed. Why do you assume I don't have it?

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Pirate Praveen]

On Mon, Sep 2, 2019 at 9:36 PM, Julien Cristau  
wrote:

Control: tags -1 unreproducible moreinfo

On Mon, Sep  2, 2019 at 20:53:13 +0500, Pirate Praveen wrote:


 Package: debootstrap
 Version: 1.0.114, 1.0.115~bpo10+1
 Severity: important

 I think debootstrap should be able to create a sid chroot but fails 
with

 this error,

 $ sudo debootstrap sid /srv/chroot/debian-sid
 I: Target architecture can be executed
 I: Retrieving Release.gpg
 I: Checking Release signature
 E: Error executing gpgv to check Release signature


Works for me.  Care to give more verbose info?



Even with --verbose there is no extra information, is there another way 
to get more information.


sudo debootstrap --verbose sid /srv/chroot/debian-sid
I: Target architecture can be executed
I: Retrieving Release.gpg
I: Checking Release signature
E: Error executing gpgv to check Release signature

Btw bullseye also works and I already have the recommends installed.

$ apt policy debian-archive-keyring
debian-archive-keyring:
 Installed: 2019.1
 Candidate: 2019.1
 Version table:
*** 2019.1 500
   500 http://deb.debian.org/debian buster/main amd64 Packages
   100 /var/lib/dpkg/status
$ apt policy arch-test
arch-test:
 Installed: 0.15-2
 Candidate: 0.15-2
 Version table:
*** 0.15-2 500
   500 http://deb.debian.org/debian buster/main amd64 Packages
   100 /var/lib/dpkg/status



Cheers,

Julien

Processed: Re: Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Debian Bug Tracking System]

Processing control commands:

> tags -1 unreproducible moreinfo
Bug #939266 [debootstrap] debootstrap fails to create a sid chroot with Error 
executing gpgv to check Release signature
Added tag(s) unreproducible and moreinfo.

-- 
939266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#939266: marked as done (debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature)

[Debian Bug Tracking System]

Your message dated Mon, 2 Sep 2019 18:07:40 +0200
with message-id <20190902160740.sifo674tpne2k...@mraw.org>
and subject line Re: Bug#939266: debootstrap fails to create a sid chroot with 
Error executing gpgv to check Release signature
has caused the Debian Bug report #939266,
regarding debootstrap fails to create a sid chroot with Error executing gpgv to 
check Release signature
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.)


-- 
939266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: debootstrap
Version: 1.0.114, 1.0.115~bpo10+1
Severity: important

I think debootstrap should be able to create a sid chroot but fails 
with this error,


$ sudo debootstrap sid /srv/chroot/debian-sid
I: Target architecture can be executed
I: Retrieving Release.gpg
I: Checking Release signature
E: Error executing gpgv to check Release signature

It works with creating buster chroot.

$ sudo debootstrap buster /srv/chroot/debian-buster
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 
6D33866EDD8FFA41C0143AEDDCC9EFBF77E11517)

I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on ...
I: Retrieving libacl1 2.2.53-4


--- End Message ---
--- Begin Message ---
Pirate Praveen  (2019-09-02):
> Package: debootstrap
> Version: 1.0.114, 1.0.115~bpo10+1
> Severity: important
> 
> I think debootstrap should be able to create a sid chroot but fails with
> this error,
> 
> $ sudo debootstrap sid /srv/chroot/debian-sid
> I: Target architecture can be executed
> I: Retrieving Release.gpg
> I: Checking Release signature
> E: Error executing gpgv to check Release signature
> 
> It works with creating buster chroot.
> 
> $ sudo debootstrap buster /srv/chroot/debian-buster
> I: Target architecture can be executed
> I: Retrieving InRelease
> I: Checking Release signature
> I: Valid Release signature (key id 6D33866EDD8FFA41C0143AEDDCC9EFBF77E11517)
> I: Retrieving Packages
> I: Validating Packages
> I: Resolving dependencies of required packages...
> I: Resolving dependencies of base packages...
> I: Checking component main on ...
> I: Retrieving libacl1 2.2.53-4

I think you should install the Recommends before reporting a bug.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Julien Cristau]

Control: tags -1 unreproducible moreinfo

On Mon, Sep  2, 2019 at 20:53:13 +0500, Pirate Praveen wrote:

> Package: debootstrap
> Version: 1.0.114, 1.0.115~bpo10+1
> Severity: important
> 
> I think debootstrap should be able to create a sid chroot but fails with
> this error,
> 
> $ sudo debootstrap sid /srv/chroot/debian-sid
> I: Target architecture can be executed
> I: Retrieving Release.gpg
> I: Checking Release signature
> E: Error executing gpgv to check Release signature
> 
Works for me.  Care to give more verbose info?

Cheers,
Julien

Re: Status of the daily builds

[Cyril Brulebois]

Steve McIntyre  (2019-09-02):
> Arg, sorry - noticed that barriere had moved myself yesterday on
> another package and it didn't hit me that it would also affect d-i. :-/

No worries.

Just confirmed that an amd64 build just hit dillon properly. And just
launched an i386 one for completeness (same IP addresses but different
SSH keypair).

> >Regarding other archs:
> > - arm64 is failing early so the log isn't propagated at the moment:
> >  grub-efi-arm64-signed : Depends: grub-common (= 2.04-2) but 2.04-3 is 
> > to be installed
> 
> ACK - that's just caused by a delay in the -signed upload to
> unstable. Should already be fixed.

Thanks for confirming, that looked plausible (and hidden on the two
other archs because of the barriere move) but was concentrating on the
needed changes.

In case someone wonders what they look like, see:

dillon:~d-i/daily-build-setup.git

> > - hurd-i386 is FTBFSing:
> >  genext2fs: genext2fs:S63freetype-workaround: Invalid argument
> > - mips is gone.
> 
> Nod. I'll disable the debian-cd stuff for mips too now.

Thanks.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#939266: debootstrap fails to create a sid chroot with Error executing gpgv to check Release signature

[Pirate Praveen]

Package: debootstrap
Version: 1.0.114, 1.0.115~bpo10+1
Severity: important

I think debootstrap should be able to create a sid chroot but fails 
with this error,


$ sudo debootstrap sid /srv/chroot/debian-sid
I: Target architecture can be executed
I: Retrieving Release.gpg
I: Checking Release signature
E: Error executing gpgv to check Release signature

It works with creating buster chroot.

$ sudo debootstrap buster /srv/chroot/debian-buster
I: Target architecture can be executed
I: Retrieving InRelease
I: Checking Release signature
I: Valid Release signature (key id 
6D33866EDD8FFA41C0143AEDDCC9EFBF77E11517)

I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on ...
I: Retrieving libacl1 2.2.53-4

Re: Status of the daily builds

[Steve McIntyre]

On Mon, Sep 02, 2019 at 05:37:22PM +0200, Cyril Brulebois wrote:
>Hi,
>
>A few days ago, the missing ppc64el builds were finally spotted and that
>was fixed by updating the configuration (new IP for the porterbox) on
>dillon's side.
>
>Now, barriere seems to have been reset [I'm currently reading details
>over IRC but the exact details aren't too important for this mail], and
>I've just reinjected the needed configuration (ssh keypairs and
>configuration on the porterbox, and updated dillon accordingly), and I'm
>running builds manually to check whether some other steps are needed.
>This porterbox is used for both amd64 and i386.

Arg, sorry - noticed that barriere had moved myself yesterday on
another package and it didn't hit me that it would also affect d-i. :-/

>Regarding other archs:
> - arm64 is failing early so the log isn't propagated at the moment:
>  grub-efi-arm64-signed : Depends: grub-common (= 2.04-2) but 2.04-3 is to 
> be installed

ACK - that's just caused by a delay in the -signed upload to
unstable. Should already be fixed.

> - hurd-i386 is FTBFSing:
>  genext2fs: genext2fs:S63freetype-workaround: Invalid argument
> - mips is gone.

Nod. I'll disable the debian-cd stuff for mips too now.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Every time you use Tcl, God kills a kitten." -- Malcolm Ray

Status of the daily builds

[Cyril Brulebois]

Hi,

A few days ago, the missing ppc64el builds were finally spotted and that
was fixed by updating the configuration (new IP for the porterbox) on
dillon's side.

Now, barriere seems to have been reset [I'm currently reading details
over IRC but the exact details aren't too important for this mail], and
I've just reinjected the needed configuration (ssh keypairs and
configuration on the porterbox, and updated dillon accordingly), and I'm
running builds manually to check whether some other steps are needed.
This porterbox is used for both amd64 and i386.

Regarding other archs:
 - arm64 is failing early so the log isn't propagated at the moment:
  grub-efi-arm64-signed : Depends: grub-common (= 2.04-2) but 2.04-3 is to 
be installed
 - hurd-i386 is FTBFSing:
  genext2fs: genext2fs:S63freetype-workaround: Invalid argument
 - mips is gone.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#939071: 6.4 Load Missing Firmware should mention unpacking zip/tar

[Baptiste Jammet]

Hi Joey, 

Dixit Joey Hess, le 31/08/2019 :

>The instructions assume that the user will unpack the zip or tarball
>they download, but they don't say to do so. 
The section you mention says
(https://www.debian.org/releases/buster/amd64/ch06s04.en.html) :
>Just download the tarball or zip file for the correct release and
>unpack it to the file system on the medium.
…unpack is here !

>There's an implicit
>assumption that the user won't consider firmware.zip to be a
>firmware file. Also that the user knows how to extract zip files or
>tarballs or what any of these file types are.
I don't think the installation guide must cover the "how to use a zip
archive" case, but it can maybe suggest to use an external soft and
that firmaware files are *.deb.

For example, in installation-guide/en/using-d-i/loading-firmware.xml:
[...] and unpack it to
-the file system on the medium.
+the file system on the medium. Use an appropriate software like
+7-Zip (https://www.7-zip.org/)
+or tar (https://www.gnu.org/software/tar/) to obtain a list of *.deb
+files to put in the /firmware directory mentioned.
[...]
It is also possible to copy individual firmware files to the medium. Loose
firmware could be obtained for example from an already installed system or
-from a hardware vendor.
+from a hardware vendor. These files are generally binary files and
+named *.bin.

Baptiste


diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml
index ff75bd668..141a44e14 100644
--- a/en/using-d-i/loading-firmware.xml
+++ b/en/using-d-i/loading-firmware.xml
@@ -77,7 +77,10 @@ available from:
 
 
 Just download the tarball or zip file for the correct release and unpack it to
-the file system on the medium.
+the file system on the medium. Use an appropriate software like
+7-Zip (https://www.7-zip.org/)
+or tar (https://www.gnu.org/software/tar/) to obtain a list of *.deb
+files to put in the /firmware directory mentioned.
 
 
 
@@ -97,7 +100,8 @@ non-firmware packages:
 
 It is also possible to copy individual firmware files to the medium. Loose
 firmware could be obtained for example from an already installed system or
-from a hardware vendor.
+from a hardware vendor. These files are generally binary files and
+named *.bin.
 
 
   


pgpQwBHB6mUOc.pgp
Description: Signature digitale OpenPGP

Bug#939261: flash-kernel: please add missing models of Cubox-i

[Josua Mayer]

Package: flash-kernel
Version: 3.99
Severity: wishlist

Dear Maintainer,

While most models of the i.MX6 Cubox-i and HummingBoard are in the flash-kernel 
database,
the dual-lite variants of Cubox-i are missing:
- SolidRun Cubox-i Solo/DualLite
- SolidRun Cubox-i Solo/DualLite (1.5som)
- SolidRun Cubox-i Solo/DualLite (1.5som+emmc)

I have prepared the entries below based on the model fields in linux (master):

Machine: SolidRun Cubox-i Solo/DualLite
Kernel-Flavors: armmp
DTB-Id: imx6dl-cubox-i.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.imx-base bootscr.uboot-generic
Required-Packages: u-boot-tools

Machine: SolidRun Cubox-i Solo/DualLite (1.5som)
Kernel-Flavors: armmp
DTB-Id: imx6dl-cubox-i-som-v15.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.imx-base bootscr.uboot-generic
Required-Packages: u-boot-tools

Machine: SolidRun Cubox-i Solo/DualLite (1.5som+emmc)
Kernel-Flavors: armmp
DTB-Id: imx6dl-cubox-i-emmc-som-v15.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.imx-base bootscr.uboot-generic
Required-Packages: u-boot-tools

Please add these to the flash-kernel db.

sincerely
Josua Mayer

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable'), (90, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.19.0-5-armmp (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  devio  1.2-1.2+b1
ii  initramfs-tools0.133
ii  linux-base 4.6
ii  mtd-utils  1:2.0.1-1
ii  ucf3.0038+nmu1

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2019.01+dfsg-7

flash-kernel suggests no packages.

-- debconf information excluded

win32-loader_0.10.0_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 02 Sep 2019 08:50:12 +0200
Source: win32-loader
Architecture: source
Version: 0.10.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Didier Raboud 
Closes: 918863
Changes:
 win32-loader (0.10.0) unstable; urgency=medium
 .
   [ Thomas Gaugler ]
   * Introduce UEFI boot manager and Secure Boot support (Closes: #918863)
 - Patch netboot debian-installer grub efi file (temporary workaround)
   * Use Modern User Interface
   * Replace 'vga=' option with gfxpayload in grub.cfg
   * Major code refactor and cleanup:
 - Enable downloading via https for Windows 7 or newer
 - Allow GPG validity check in a folder with spaces
 - Add progress text and tidy up localization files
 - Replace use of external cpio.exe
 - Remove obsolete plugins
 - Use SOURCE_DATE_EPOCH and DEB_VERSION
 .
   [ Didier Raboud ]
   * Trim trailing whitespace.
   * Disable Farsi translation as its NSIS translation doesn't convert
 correctly to its designated codepage, see #939151
   * Bump debhelper from old 11 to 12, and S-V to 4.4.0 without changes needed
   * Add standard Salsa Gitlab-CI configuration
Checksums-Sha1:
 36445452ea530cf110ccad9d2e79c8cdbd018e48 1786 win32-loader_0.10.0.dsc
 98c4a143aa2ae55294bf41e13ff0b2903f783abd 256656 win32-loader_0.10.0.tar.xz
Checksums-Sha256:
 1f117a1ed428be874b87e1ac86d0d63d0abda0ff755c5dc51489eac2663f2af5 1786 
win32-loader_0.10.0.dsc
 2a9c7579b8a7472be87001646d4c0fb3148b93134c010067a810b4769bbbe2b3 256656 
win32-loader_0.10.0.tar.xz
Files:
 c9c8761513d1392c81dd0b9a02386d48 1786 utils optional win32-loader_0.10.0.dsc
 32096cb14a867a56d971ed055c97cad5 256656 utils optional 
win32-loader_0.10.0.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEe+WPIRpjNw1/GSB7i8+nHsoWNFUFAl1svG4ACgkQi8+nHsoW
NFWp3Qv+Mt7V2+SEsAReGITzREJYefrwVo6uGuuUp8HnxW0FSoKGKxkt3+OkDkLv
qNUKJv8p4j5LEEvfYHT3LSZoJ3gt1Q2hQT01mqSO0aNimpk/vDiHx9TGao2B77f+
U2gmgR7i1SowgNNHnzD4Oos5X/i9QwjBKnRJLjDte8uFWUQT/tfL4ebZ7dcB/8R4
rJiqVxYgX7b1ctXO16PhwN72L3IQ8vmeDDIrDXlgU4WhM84FxQp/oACCBoyGf7Jy
4yIQd6A7Eb6HVU38uL2ohbHQxQIvFHzOow4I7EhCUJmdzU7MPolt6mZjaqxXezhT
UMTTMvWxABIussI5QMCHrhAivMcKj1L8GZ9+NC9b8IRIQI+oNhEHhhTrjinnjybU
3A94KISBwthSlpPtrjFmgq3wbbGckBl667r/Vj+Uyet+r5H1cnFe9PrwzBipjVif
W1EQYtieNnEHX6dlbHPf0FnxVo1L33Fh9eqvpJ2jiNhyT3bg3VS1b+OXKQQV3NkC
wu8kD6ri
=dedo
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#918863: marked as done (reboot returns to Windows 10 on Lenovo X1)

[Debian Bug Tracking System]

Your message dated Mon, 02 Sep 2019 07:19:35 +
with message-id 
and subject line Bug#918863: fixed in win32-loader 0.10.0
has caused the Debian Bug report #918863,
regarding reboot returns to Windows 10 on Lenovo X1
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.)


-- 
918863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: win32-loader
Version: 0.8.3+deb9u1 +net

I have a new Lenovo X1 6th Gen running stock Windows 10. It has one
internal disk and 16GB Ram. The first thing I did with it was download and
run win32-loader. I didn't notice any errors, read the notice about
rebooting, waited eagerly for the installer to appear and instead rebooting
went right back to windows. I tried again selecting the text installation.
I tried rebooting using the windows start menu instead of letting win32-loader
do it. No luck. Here are the details copied from Debian-Installer loader:
Completed:

Created uninstaller: C:\win32-loader\Uninstall.exe
GET: http://deb.debian.org/debian/dists/stable//Release
GET: http://deb.debian.org/debian/dists/stable//Release.gpg
Extract: C:\Users\TB\AppData\Local\Temp\nsyA83C.tmp\gpgv.exe
Extract:
C:\Users\TB\AppData\Local\Temp\nsyA83C.tmp\debian-archive-keyring.gpg
Checking GPG signature on Release.
GET:
http://deb.debian.org/debian/dists/stable/main/installer-amd64/current/images//SHA256SUMS
Computing checksum for SHA256SUMS
11d5570a2b93fce413ec5a7bdc1e732210fc8f92e4171ee635f1a0830e862352 =
11d5570a2b93fce413ec5a7bdc1e732210fc8f92e4171ee635f1a0830e862352
GET:
http://deb.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/debian-installer/amd64/linux
Computing checksum for linux
97cdc7a6c984f353d742bd6e992433f3a0c5caabff97e097c4688f409927cadb =
97cdc7a6c984f353d742bd6e992433f3a0c5caabff97e097c4688f409927cadb
GET:
http://deb.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/debian-installer/amd64/initrd.gz
Computing checksum for initrd.gz
02ea00956ecdde0e4baa704fdad630d2e1e6284a9e643390c560f699409fc29a =
02ea00956ecdde0e4baa704fdad630d2e1e6284a9e643390c560f699409fc29a
Generating C:\win32-loader\grub.cfg
Extract: C:\win32-loader\cpio.exe
Extract: C:\win32-loader\gzip.exe
Appending preseeding information to C:\win32-loader\initrd.gz
Extract: C:\g2ldr
Extract: C:\g2ldr.mbr
Registering in BootMgr
Disabling NTFS compression in bootstrap files
Completed
--- End Message ---
--- Begin Message ---
Source: win32-loader
Source-Version: 0.10.0

We believe that the bug you reported is fixed in the latest version of
win32-loader, 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 918...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated win32-loader 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: SHA512

Format: 1.8
Date: Mon, 02 Sep 2019 08:50:12 +0200
Source: win32-loader
Architecture: source
Version: 0.10.0
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Didier Raboud 
Closes: 918863
Changes:
 win32-loader (0.10.0) unstable; urgency=medium
 .
   [ Thomas Gaugler ]
   * Introduce UEFI boot manager and Secure Boot support (Closes: #918863)
 - Patch netboot debian-installer grub efi file (temporary workaround)
   * Use Modern User Interface
   * Replace 'vga=' option with gfxpayload in grub.cfg
   * Major code refactor and cleanup:
 - Enable downloading via https for Windows 7 or newer
 - Allow GPG validity check in a folder with spaces
 - Add progress text and tidy up localization files
 - Replace use of external cpio.exe
 - Remove obsolete plugins
 - Use SOURCE_DATE_EPOCH and DEB_VERSION
 .
   [ Didier Raboud ]
   * Trim trailing whitespace.
   * Disable Farsi translation as its NSIS translation doesn't convert
 correctly to its designated codepage, see #939151
   * Bump debhelper from old 11 to 12, and S-V to 4.4.0 without changes needed
   * Add standard Salsa Gitlab-CI configuration
Checksums-Sha1:
 36445452ea530cf110ccad9d2e79c8cdbd018e48 1786 win32-loader_0.10.0.dsc
 

Processing of win32-loader_0.10.0_source.changes

[Debian FTP Masters]

win32-loader_0.10.0_source.changes uploaded successfully to localhost
along with the files:
  win32-loader_0.10.0.dsc
  win32-loader_0.10.0.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)