Re: Black screen / X issue fixed

[Cyril Brulebois]

Philip Hands  (2017-08-15):
> Oh, and the "obviously" wasn't meant to be something like a complaint,
> just saying that it was the thing that was causing some of the installs
> to grind to a halt -- so nothing to say sorry for.
> 
> Sorry if what I said sounded like I was grumpy about it -- that was not
> even slightly the case. :-)

Oh, no worries, was just mentioning why I didn't connect the dots
properly when the topic was brought up.

Thanks for the instructions in the other mail, will look when I have a
chance, probably in a few days.


KiBi.


signature.asc
Description: Digital signature

Bug#871730: Improving the icons

[Stéphane Blondon]

I think it's prettier with colored icons (see the screenshot).
If you prefer this version, simply replace the icons from the previous
archive by the icons provided by the attached archive (the picture in
the png/ directory).

The directory svg/ in the attached archive provides the icons in svg
format, as provided by Adwaita but the modification to set up the
colors. The filenames in the svg/ directoy are unchanged from Adwaita theme.


colored_icons.tar.xz
Description: application/xz


signature.asc
Description: OpenPGP digital signature

Re: Black screen / X issue fixed

[Philip Hands]

Cyril Brulebois  writes:

> Hi,
>
> Philip Hands  (2017-08-14):
>> Yes that's the behaviour I was commenting on in IRC, and which was
>> obviously being spotted by the jenkins/cucumber setup.
>
> Sorry, based on earlier comments over the previous days/weeks, I went
> for a “X is broken” shortcut and might not have actually got your exact
> point.

Oh, and the "obviously" wasn't meant to be something like a complaint,
just saying that it was the thing that was causing some of the installs
to grind to a halt -- so nothing to say sorry for.

Sorry if what I said sounded like I was grumpy about it -- that was not
even slightly the case. :-)

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Re: Black screen / X issue fixed

[Philip Hands]

Cyril Brulebois  writes:

> Hi,
>
> Philip Hands  (2017-08-14):
>> Yes that's the behaviour I was commenting on in IRC, and which was
>> obviously being spotted by the jenkins/cucumber setup.
>
> Sorry, based on earlier comments over the previous days/weeks, I went
> for a “X is broken” shortcut and might not have actually got your exact
> point.
>
>> BTW It is possible to run get something like shell access to the
>> running d-i via its ttyS0 (by putting rather a lot of stuff on the
>> kernel boot command line), so if that would help I can run tests for
>> you and/or explain the proceedure.
>
> If you would have a little time to explain this, that would be immensely
> useful. Feel free to just sum it up quickly in an email, I might write
> some docs about it afterwards.

Well, it's a bit horrible, but as long as you don't need to type the
kernel command line by hand it's OK.

The code that does the trick is here:

  
https://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/tree/cucumber/features/step_definitions/common_steps.rb#n217

which you can see the result of at about 27 seconds into this:

  
https://jenkins.debian.net/view/lvc/job/lvc_debian-testing-daily/1341/artifact/results/00%3A01%3A57_Install_Debian,_and_boot_to_a_login_prompt,_Examples___1_.mpg

What that does is start a while loop that reads from /dev/ttyS0, and
runs the commands that you type, returning the STDOUT, STDERR, and
result code, separated by various control characters which you probably
don't care about.

If you do that, then you can use nc (or whatever) to connect to the TCP
port which is defined for the KVM's ttyS0, and type commands, and get
their output, followed by a result code.  It's almost like having a shell
prompt, other than the slightly odd ordering of STDERR and the result.

It would probably be better to have a udeb that contains a thing for
running the listener, like the debugging thing that is available in
tails -- theirs returns results in json, and lets one run as users other
than root, and can drop thing into the background, but we don't really
need all that in d-i.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#872181: debootstrap: error processing argument #4

[Douglas Guptill]

Package: debootstrap
Version: 1.0.67+deb8u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

 running rootstrap to create a devuan filesystem.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 ran rootstrap.  It failed; with an error message from these lines

if [ ! -e "$SCRIPT" ]; then
error 1 NOSCRIPT "No such script: %s" "$SCRIPT"
fi


   * What was the outcome of this action?

   rootstrap failed.

   * What outcome did you expect instead?

   rootstrap to succeed.

suggested patch from:
  diff downloads/debootstrap-1.0.91/debootstrap /usr/sbin/debootstrap :
416c395
<   SCRIPT="$DEBOOTSTRAP_DIR/scripts/$4"
---
>   SCRIPT="$4"

Thanks,
Douglas.

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debootstrap depends on:
ii  wget  1.16-1+deb8u2

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2017.5~deb8u1
ii  gnupg   1.4.18-7+deb8u3

debootstrap suggests no packages.

-- no debconf information

Re: Black screen / X issue fixed

[Cyril Brulebois]

Hi,

Philip Hands  (2017-08-14):
> Yes that's the behaviour I was commenting on in IRC, and which was
> obviously being spotted by the jenkins/cucumber setup.

Sorry, based on earlier comments over the previous days/weeks, I went
for a “X is broken” shortcut and might not have actually got your exact
point.

> BTW It is possible to run get something like shell access to the
> running d-i via its ttyS0 (by putting rather a lot of stuff on the
> kernel boot command line), so if that would help I can run tests for
> you and/or explain the proceedure.

If you would have a little time to explain this, that would be immensely
useful. Feel free to just sum it up quickly in an email, I might write
some docs about it afterwards.

Thanks!


KiBi.


signature.asc
Description: Digital signature

Re: Busybox in Debian

[Ben Hutchings]

On Mon, 2017-08-14 at 16:42 +0200, Denys Vlasenko wrote:
[...]
> > > minips
> 
> It's just mini-ps. Proliferation of reinvented tools
> with slightly different names.

It's not a POSIX-compliant ps implementation.  Anyway, initramfs-tools
doesn't need it.

> > > nuke
> 
> This is "rm -rf -- FILE". Should not be necessary.

klibc-utils doesn't implemnt rm, only nuke.  busybox could install nuke
in the initramfs as a wrapper for rm.

> > > resume
> 
> Writes "maj:min:offset" to /sys/power/resume.
> Looks like this is support for resume from disk?

Correct.

> > > run-init
> 
> This tool is doing this:
[...]
> There is the "switch_root" tool in util-linux which does the
> crucial part of this functionality - deleting / remounting / chrooting.
> It is in bbox too.

initramfs-tools used to use switch_root if possible, but it didn't
support the -d (drop capabilities) option.  Later on we needed
validation of the init filename to support symlinks (e.g. /sbin/init ->
/lib/systemd/systemd), so I added and used the -n (dry run) option to
run-init.  busybox would need to support both of these.

> If you want "resume" and "ipconfig" in bbox, I can do that.

Go for it.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
  - John Lennon



signature.asc
Description: This is a digitally signed message part

Re: Busybox in Debian

[Denys Vlasenko]

>> ipconfig

Looks like it is used to run DHCP / BOOTP / RARP
on several interfaces, including a possibility
to run it on _all_ existing interfaces
(excluding loopback and point-to-point).
I see how this can be useful during boot.


>> minips

It's just mini-ps. Proliferation of reinvented tools
with slightly different names.


>> nuke

This is "rm -rf -- FILE". Should not be necessary.


>> resume

Writes "maj:min:offset" to /sys/power/resume.
Looks like this is support for resume from disk?


>> run-init

This tool is doing this:

Usage: exec run-init [-d caps] [-c consoledev] /real-root /sbin/init [args]
/*
 * run_init(realroot, consoledev, drop_caps, init, initargs)
 *
 * This function should be called as the last thing in kinit,
 * from initramfs, it does the following:
 *
 * - Delete all files in the initramfs;
 * - Remounts /real-root onto the root filesystem;
 * - Chroots;
 * - Drops comma-separated list of capabilities;
 * - Opens /dev/console;
 * - Spawns the specified init program (with arguments.)
 *
 * On failure, returns a human-readable error message.
 */

There is the "switch_root" tool in util-linux which does the
crucial part of this functionality - deleting / remounting / chrooting.
It is in bbox too.



If you want "resume" and "ipconfig" in bbox, I can do that.

Re: Black screen / X issue fixed

[Philip Hands]

Cyril Brulebois  writes:

> Cyril Brulebois  (2017-08-08):
>> So I've been meaning to debug the black screen in graphical installer
>> for quite a while, but I've been busy with preparing for my talk, then
>> discussing busybox with new recruits.
>> 
>> I've finally managed to bisect that down to the following dinstalls:
>>   2017-06-20 22:37:45 (last OK)
>>   2017-06-21 03:38:47 (first KO)
>> 
>> and out of the 6 packages, I've isolated the culprit:
>>   libexpat1-udeb_2.2.1-1_amd64.udeb
>> 
>> Right afterwards I've discovered that an installer built against
>> unstable… just works again. I'm suspecting the new expat upstream
>> version might have been the fix we needed:
>>   https://tracker.debian.org/news/860347
>> 
>> But I doubt it makes much sense to also isolate what/when the exact
>> fix happened. I thought I would just share the “when did it break?”
>> part.
>
> This is fun: the bug is “fixed” in that the language selection screen
> pops up properly, but it's not actually possible to get any input (incl.
> VT switching) into the installer. I'll look into this once I'm back from
> DebConf.

Yes that's the behaviour I was commenting on in IRC, and which was
obviously being spotted by the jenkins/cucumber setup.

BTW It is possible to run get something like shell access to the running
d-i via its ttyS0 (by putting rather a lot of stuff on the kernel boot
command line), so if that would help I can run tests for you and/or
explain the proceedure.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#872094: lilo-installer: fdisk dependency needed

[andreas]

Source: lilo-installer
Version: 1.53
Severity: important
User: util-li...@packages.debian.org
Usertags: fdisk-dependency

Hello,

As recently announced on debian-devel-announce[1] packages who need
any of sfdisk, cfdisk or fdisk will need to add a dependency on the
new fdisk package.

Your package lilo-installer showed up on codesearch.debian.net and a
very quick analysis suggested you might want to add a dependency
(and/or build-dependency if you use it at build-time, eg. tests).

Please use the backwards-compatible way of specifying the dependency
as suggested in the debian-devel-announce mail:

fdisk | util-linux (<< 2.29.2-3~)

(and if only for tests you might want to add the build profile
)

Please reassign this bug report to the binary package shipping the
affected part of your source.

If your more detailed analysis shows this should be a recommends,
suggests or even no relationship at all to the fdisk package then
please just close this bug report stating the results of your
analysis (and if so sorry for bothering you).

Regards, Andreas Henriksson

[1]:
https://lists.debian.org/debian-devel-announce/2017/08/msg5.html 

Bug#872091: debian-installer: fdisk dependency needed

[andreas]

Source: debian-installer
Version: 20170615
Severity: important
User: util-li...@packages.debian.org
Usertags: fdisk-dependency

Hello,

As recently announced on debian-devel-announce[1] packages who need
any of sfdisk, cfdisk or fdisk will need to add a dependency on the
new fdisk package.

Your package debian-installer showed up on codesearch.debian.net and
a very quick analysis suggested you might want to add a dependency
(and/or build-dependency if you use it at build-time, eg. tests).

Please use the backwards-compatible way of specifying the dependency
as suggested in the debian-devel-announce mail:

fdisk | util-linux (<< 2.29.2-3~)

(and if only for tests you might want to add the build profile
)

Please reassign this bug report to the binary package shipping the
affected part of your source.

If your more detailed analysis shows this should be a recommends,
suggests or even no relationship at all to the fdisk package then
please just close this bug report stating the results of your
analysis (and if so sorry for bothering you).

Regards, Andreas Henriksson

[1]:
https://lists.debian.org/debian-devel-announce/2017/08/msg5.html 

Re: Busybox in Debian

[Denys Vlasenko]

On Mon, Aug 14, 2017 at 3:05 PM, Ben Hutchings  wrote:
> On Mon, 2017-08-14 at 14:55 +0200, Denys Vlasenko wrote:
>> On Sat, Aug 12, 2017 at 4:15 PM, Ben Hutchings 
>> wrote:
>> > On Fri, 2017-08-11 at 14:54 -0400, Chris Boot wrote:
>> > [...]
>> > > - The default initramfs assembly system, initramfs-tools, incorporates
>> > > busybox into the initramfs and it's used until the root filesystem (and
>> > > /usr if separate) is mounted and can be pivot_rooted into. We also use
>> > > parts of klibc in the initramfs, and I'm not yet entirely clear what
>> > > tools in the initramfs are klibc tools, busybox applets or executables
>> > > copied from the running system.
>> >
>> > [...]
>> >
>> > If initramfs-tools is configured to use busybox, busybox installs all
>> > its commands and then klibc-utils installs any commands that are not
>> > already there.  So for any command that they both implement, the
>> > busybox implementation is used.
>>
>> Do you have a list of tools klibc-utils installs?
>
> If busybox is used, then klibc-utils provides these:
>
> chroot
> losetup
> pivot_root

There are such applets in busybox too.
If they are buggy or incompatible (e.g. a missing option),
please let me know.

> halt
> poweroff
> reboot

These applets are in busybox too, but they may do
bbox-specific actions depending on configuration.

If FEATURE_CALL_TELINIT=y, they run "telinit N",
expecting it to know how to signal init.

Otherwise they assume the bbox init is on the system,
and they simply signal it:
SIGUSR1 = halt, SIGUSR2 = poweroff, SIGTERM = reboot.

/* talk to init */
if (!ENABLE_FEATURE_CALL_TELINIT) {
/* bbox init assumed */
rc = kill(1, signals[which]);
} else {
/* SysV style init assumed */
/* runlevels:
 * 0 == shutdown
 * 6 == reboot */
execlp(CONFIG_TELINIT_PATH,
CONFIG_TELINIT_PATH,
which == 2 ? "6" : "0",
(char *)NULL
);
bb_perror_msg_and_die("can't execute '%s'",
CONFIG_TELINIT_PATH);
}


> fstype

What does this do?


> nfsmount

And this one? If ordinary mount can't mount NFS for some reason,
it's interesting to look into that reason. Sometime ago,
kernel grew the ability to mount NFS without funky binary API
in mount syscall, so it's even easier now - mount tool only has to
resolve DNS name to an IP address.

If you are going to play with it, not that you probaly do _not_
need FEATURE_MOUNT_NFS=y: it is
"Support mounting NFS file systems on Linux < 2.6.23" option,
not "You need this, or else NFS mounts will not work".


> ipconfig
> minips
> nuke
> resume
> run-init

These look like klibc-utils inventions?

Re: Busybox in Debian

[Denys Vlasenko]

On Sat, Aug 12, 2017 at 4:15 PM, Ben Hutchings  wrote:
> On Fri, 2017-08-11 at 14:54 -0400, Chris Boot wrote:
> [...]
>> - The default initramfs assembly system, initramfs-tools, incorporates
>> busybox into the initramfs and it's used until the root filesystem (and
>> /usr if separate) is mounted and can be pivot_rooted into. We also use
>> parts of klibc in the initramfs, and I'm not yet entirely clear what
>> tools in the initramfs are klibc tools, busybox applets or executables
>> copied from the running system.
> [...]
>
> If initramfs-tools is configured to use busybox, busybox installs all
> its commands and then klibc-utils installs any commands that are not
> already there.  So for any command that they both implement, the
> busybox implementation is used.

Do you have a list of tools klibc-utils installs?

Re: Busybox in Debian

[Ben Hutchings]

On Mon, 2017-08-14 at 14:55 +0200, Denys Vlasenko wrote:
> On Sat, Aug 12, 2017 at 4:15 PM, Ben Hutchings 
> wrote:
> > On Fri, 2017-08-11 at 14:54 -0400, Chris Boot wrote:
> > [...]
> > > - The default initramfs assembly system, initramfs-tools, incorporates
> > > busybox into the initramfs and it's used until the root filesystem (and
> > > /usr if separate) is mounted and can be pivot_rooted into. We also use
> > > parts of klibc in the initramfs, and I'm not yet entirely clear what
> > > tools in the initramfs are klibc tools, busybox applets or executables
> > > copied from the running system.
> > 
> > [...]
> > 
> > If initramfs-tools is configured to use busybox, busybox installs all
> > its commands and then klibc-utils installs any commands that are not
> > already there.  So for any command that they both implement, the
> > busybox implementation is used.
> 
> Do you have a list of tools klibc-utils installs?

If busybox is used, then klibc-utils provides these:

chroot
fstype
halt
ipconfig
losetup
minips
nfsmount
nuke
pivot_root
poweroff
reboot
resume
run-init

(not all of which are actually used).

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
  - John Lennon



signature.asc
Description: This is a digitally signed message part

Debian Bug report logs - #864734

[Chrisotphe Blamart]

hello,

about this report :
debootstrap --variant=minbase don't install apt-get on chroot

The debootstrap process (on stretch) stop when finding /dev, /proc or 
/sys directory previously created on the chroot environment

This problem don't occur in jessie


mkdir /mnt/{dev, dev/pts, proc, sys}
debootstrap --variant=minbase stretch /mnt

  -> Process stop without error, all packages are not installed

Bug#864734: informations about debootstrap bug

[Chrisotphe Blamart]

hello,

about this report :
debootstrap --variant=minbase don't install apt-get on chroot

The debootstrap process (on stretch) stop when finding /dev, /proc or 
/sys directory previously created on the chroot environment

This problem don't occur in jessie

mkdir /mnt/{dev, dev/pts, proc, sys}
debootstrap --variant=minbase stretch /mnt

  -> Process stop without error, all packages are not installed