Processing of base-installer_1.182_source.changes

2018-08-10 Thread Debian FTP Masters
base-installer_1.182_source.changes uploaded successfully to localhost
along with the files:
  base-installer_1.182.dsc
  base-installer_1.182.tar.xz
  base-installer_1.182_amd64.buildinfo

Greetings,

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



Creating my own Preseeded ISO with partman replaced by a ZFS step

2018-08-10 Thread Bailey Parker
Hello,

I'm looking to preseed an installer for a cluster, but I'd like all machines to
boot from ZFS roots. [The best recommendation I've found][1] wants me to boot a
LiveCD, install ZFS, setup the zpool, and the `chroot` in and repeat the
installation manually. This seems really tedious and error-prone, and somewhat
defeats the purpose of the preseeded installer.

I'd like to somehow modify the installer ISO that I create when preseeding to
include ZFS (so that before the package manager is configured, a ZFS pool can
be created), replace the partman step with some custom scripting that [creates
a zpool and sets up the datasets][2], and finally install zfs-dkms (also
zfsutils-linux and zfs-initramfs).

Looking at [an example stretch preseed file][3] (and I must confess, a friend
who is capable of scrolling to the end of a file found this--why
partman/early_command is at the end and not with the other partman stuff is
beyond me!), it seems like if I was able to add the compiled ZFS kernel module
and utils to initrd (along with my preseed file), I could run my zpool stuff
from partman/early_command. However, I'd still need a way to skip the default
partman stuff so that it couldn't overwrite all my work and somehow inform the
rest of the install process to use my ZFS root.

I also came across [partman-zfs][4], but apparently this is only for a FreeBSD
port. Could that be useful in any way?

In digging through mail archives, I also came across [this script][5], but it's
unclear to me how exactly that would fit into my desired workflow. This sounds
like you'd need to manually drop to a shell to install/setup ZFS.

Is there a sane way to go about adding ZFS root support to my preseeded install
or should I abandon this and wait for better support?  If the latter, are there
steps I could take to add better support given my limited knowledge of d-i?

Thanks,
Bailey Parker

  [1]: https://github.com/zfsonlinux/zfs/wiki/Debian-Stretch-Root-on-ZFS
  [2]: 
https://github.com/zfsonlinux/zfs/wiki/Debian-Stretch-Root-on-ZFS#step-3-system-installation
  [3]: https://www.debian.org/releases/stable/example-preseed.txt
  [4]: https://packages.debian.org/sid/partman-zfs
  [5]: https://lists.debian.org/debian-boot/2018/01/msg00334.html



Re: Creating my own Preseeded ISO with partman replaced by a ZFS step

2018-08-10 Thread Cyril Brulebois
Hi,

Bailey Parker  (2018-08-10):
> Is there a sane way to go about adding ZFS root support to my preseeded
> install or should I abandon this and wait for better support?  If the
> latter, are there steps I could take to add better support given my
> limited knowledge of d-i?

I'm afraid we're not going to support ZFS as that would mean supporting
out-of-tree kernel modules, which we migrated away from years ago.


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


signature.asc
Description: PGP signature


Bug#905827: Buster on Dell XPS 15 9570

2018-08-10 Thread Ben Hutchings
On Fri, 2018-08-10 at 12:21 +0200, Geert Stappers wrote:
[...]
> Changed boot mode to
>   1) Legacy External Device Boot Mode, Secure Boot OFF
[...]

This sounds like BIOS emulation, which is not really recommended on
current UEFI systems.

Ben.

-- 
Ben Hutchings
Time is nature's way of making sure that
everything doesn't happen at once.



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


apt-setup_0.142_source.changes ACCEPTED into unstable

2018-08-10 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Aug 2018 20:45:59 +0200
Source: apt-setup
Binary: apt-setup-udeb apt-mirror-setup apt-cdrom-setup
Architecture: source
Version: 1:0.142
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Description:
 apt-cdrom-setup - set up a CD in sources.list (udeb)
 apt-mirror-setup - set up a mirror in sources.list (udeb)
 apt-setup-udeb - Configure apt (udeb)
Changes:
 apt-setup (1:0.142) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
 .
   [ Updated translations ]
   * Finnish (fi.po)
   * Hebrew (he.po) by Yaron Shahrabani
   * Telugu (te.po) by Praveen Illa
Checksums-Sha1:
 13769b5db7f0054612bfd7893f0724b9bd08a4b6 1828 apt-setup_0.142.dsc
 b56872b31680c2b4244d4628383b71d2edac3d79 252200 apt-setup_0.142.tar.xz
 5a033889a8f39cf39946ccdb1a2fa50c642646b6 5943 apt-setup_0.142_amd64.buildinfo
Checksums-Sha256:
 d12e199d4c3866023b1e73cc0adfda9817c53bc163663e9ad7cadfbc08606a61 1828 
apt-setup_0.142.dsc
 4a251483d544574097fbae3992422a33f17767167ef83d2a177fd7924ff60bce 252200 
apt-setup_0.142.tar.xz
 21557e3a3eab43ece1676f14230ec2a74260f1f27a4f23de23eafaff0c0c155c 5943 
apt-setup_0.142_amd64.buildinfo
Files:
 5f896aee1914d812e7d0bf8b764ef7ab 1828 debian-installer extra 
apt-setup_0.142.dsc
 d84dfbd4266f3620f9ffb36b365ada9b 252200 debian-installer extra 
apt-setup_0.142.tar.xz
 0afc7945d9bfc6a8f019df54ef70703c 5943 debian-installer extra 
apt-setup_0.142_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAltt4c0ACgkQWfGHyhVu
sHbtrhAAw9STWtV/rmIg6Gq9igu62fajv9CqSX64C/EZOkPjjZT90Ax78LFv/1/C
vKz71iYIBDiPRafExNMo4Lxud+vohohPYp8trlKWoUmTkiyRdbjgQtdi3KVV1vB2
22sRuT/5kDw/JmMLM0kjUJjP5jQhQvdudYRpdlbiszjTNHIIU6BheIbBhC6FUfr2
7h+FvdtY8i/EJpk3LTzk+SIkH5QEXMvYHdnk0XjqARf/rnMFaRD2RTAR9b4lxtTC
BCh7+74S5cf8/Ra2XcnsYCUFO5YVIP2FkdPw64xzXbNI9jlxLW+JPtOaMSKjSoq3
VIc2N7HjBh6bP4I/bh9fdPxCfKH17YT+JMZ0i+TU0N5muvtbsbAd54uH/eNZAdy6
Uxia1G7ouSPANySUIX9LvUXKCCjE2RsitdRLQYdPVilc0GT9Q6xFpzNj/oSQENjy
yCzutpaJqqs3O9taKVWjGpp9lUIdYC4tPQAzY6rOK9Wx8Ak+xPjvboRJLULxztRC
xl2Eb/wZO702QPw59xGHN9ECGL+ac6sFc5bkIK6o3XhU3V2QR/p5WUUcOsTC3Shy
OQpqnl97V9fKnBIHEANZZG3+FXnYobYoRCv6Z/5qPJnDx46KEHgdC7ZCQDQY8U1p
jIyGFB5hVm6GqTGN5qRualuJcFbtvw24CNdMvuHtpnQhpbycwNo=
=FYqp
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



base-installer_1.182_source.changes ACCEPTED into unstable

2018-08-10 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 10 Aug 2018 22:28:14 +0200
Source: base-installer
Binary: base-installer bootstrap-base
Architecture: source
Version: 1.182
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Holger Wansing 
Description:
 base-installer - base system installation framework (udeb)
 bootstrap-base - Install the base system (udeb)
Changes:
 base-installer (1.182) unstable; urgency=medium
 .
   * Team upload
 .
   [ Cyril Brulebois ]
   * Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
 .
   [ Updated translations ]
   * Swedish (sv.po) by Anders Jonsson
   * Simplified Chinese (zh_CN.po) by Boyuan Yang
Checksums-Sha1:
 9e211dd2a641c63cda3ddf03fb4859134f4e16cc 1918 base-installer_1.182.dsc
 bc5f113efb56a2d865d59c5047f9fb2d14e1fbeb 254540 base-installer_1.182.tar.xz
 51351ee9a791ceee7adbf60e27c31873833ed32f 5840 
base-installer_1.182_amd64.buildinfo
Checksums-Sha256:
 e8215b344a3d5df8d0f96847460d075d9cd9fd64c5f8d48e8b95ac7fe466b549 1918 
base-installer_1.182.dsc
 d90371ee0ef5706fd2e15f6b350307136dbcab56cece31cf7230cf441d879ccc 254540 
base-installer_1.182.tar.xz
 14be7728263dbdb15585bf48ffc6caad71af4451683d50245410f051a9c77d55 5840 
base-installer_1.182_amd64.buildinfo
Files:
 d75fe9010990c2b073277e7e5d857321 1918 debian-installer required 
base-installer_1.182.dsc
 89479f547dc33f421dd89e4bbea4fd79 254540 debian-installer required 
base-installer_1.182.tar.xz
 8f55b87046061db91f49bf926d978194 5840 debian-installer required 
base-installer_1.182_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEESWrG6BRCSzSFCDUpWfGHyhVusHYFAltt9vcACgkQWfGHyhVu
sHYJUg/8DoI3Sorw2DUkPStyvoMF2Slg4ujlDcipq+ocZh07InX5D7FoYsiEx2kH
7tt0DhMF+Ez4LsMTnqerYhaRLyp/X0WO+DjOM6Mnn8NsfdJG+WNvgMKCdhY2BoQK
SZn2DMQ1ukvidYknIzp4vIojBDhOcHn27cuBvaH7SVgFmsuzsVgTgMLUkBqesXtl
SQCaycDSyOmggXUrzthS6DhPm1CwR8RwQEq+8g42vM+IcEzzf9Viki+hes6NeeO9
+GjejRJFDyDJelSO5c2B/hP7pRJ1FKFPTPZM+FaH8FpoWWSm82whYkLjxNGbO+11
jw+/ZG9s2mgzn0+oEnb9cGa5tWWmuzUm0W6OMrPuwk/YA+LUo2wDkWU4M/L+PMv0
kEaAo8IebvjGm7FrHYIAjY1mcoVv/V7gHh7ZEI+ADgdGPxIv0IuQ7nfOaC8i2PIW
KGzW8evHtiNOglLcYCYu6KDKv55xUeRFg5+o7GlEcqC5p3uSRGfDohcVFNZf4Qqk
RFgS9qT5ygHNT91CEaVMZWIJUqJsvHohlDt7wVpwaUL/lrIRQBoi3vDdZyw9VuEz
KUYTzuK/A2IP/N63yHcE6yQjjAaq+sx4BgwZQZ/bDKlpsOAkyVgOPofw52ZW4rqm
TqJ9NT7QfG7tlNNyv6TYLuBxE35rJ5qKbruX1f4CH7ni8IzT4V8=
=jSSX
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Re: anna_1.68_source.changes ACCEPTED into unstable

2018-08-10 Thread Holger Wansing
Hi,

Cyril Brulebois  wrote:
> Debian FTP Masters  (2018-08-09):
> >  anna (1.68) unstable; urgency=medium
> >  .
> >* Team upload
> >  .
> >[ Cyril Brulebois ]
> >* Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
> >  .
> >[ Updated translations ]
> >* Hebrew (he.po) by Yaron Shahrabani
> 
> Congratulations! :)
> 
> Now you need to remember tagging and pushing your tag. :)
> 
> (That's on me, I didn't explicitly mention that in our mail exchange.)

Yes, and I didn't read anything about that in the several packaging/uploading
docu.
So that's mostly best practice, but no strict packaging rule or the like?

Also, I don't know anything about tagging.
So, I need to know something more about this tagging:

When do we use it?
Just for every new uploaded version, as it seems...
More circumstances, where to set tags?

Which tags do we use? The lightweighted or the annotated ones?
Looking at the existing tags, it seems that's annotated ones, but without
GPG signatur. Right?



Holger



-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Processing of apt-setup_0.142_source.changes

2018-08-10 Thread Debian FTP Masters
apt-setup_0.142_source.changes uploaded successfully to localhost
along with the files:
  apt-setup_0.142.dsc
  apt-setup_0.142.tar.xz
  apt-setup_0.142_amd64.buildinfo

Greetings,

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



Re: anna_1.68_source.changes ACCEPTED into unstable

2018-08-10 Thread Cyril Brulebois
Debian FTP Masters  (2018-08-09):
>  anna (1.68) unstable; urgency=medium
>  .
>* Team upload
>  .
>[ Cyril Brulebois ]
>* Update Vcs-{Browser,Git} to point to salsa (alioth's replacement).
>  .
>[ Updated translations ]
>* Hebrew (he.po) by Yaron Shahrabani

Congratulations! :)

Now you need to remember tagging and pushing your tag. :)

(That's on me, I didn't explicitly mention that in our mail exchange.)


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


signature.asc
Description: PGP signature


Re: Bug#905793: Why does the Installer formats given swap

2018-08-10 Thread Lennart Sorensen
On Fri, Aug 10, 2018 at 10:08:52AM +0200, Herbert Kaminski wrote:
> Am Thu, 9 Aug 2018 14:14:15 -0400
> schrieb lsore...@csclub.uwaterloo.ca (Lennart Sorensen):
> 
> > [...] 
> > Well 99.9% of installs don't have another linux on the system, 
>^
> Interesting. How did you get that figure?

Totally made it up. :)

I suspect I guessed low in fact.

-- 
Len Sorensen



Bug#905827: Buster on Dell XPS 15 9570, thunderbolt

2018-08-10 Thread Geert Stappers
On Fri, Aug 10, 2018 at 12:21:03PM +0200, Geert Stappers wrote:
> Package: installation-report
> 
> Summary: Customer did what hardware vendor should have done
> 
> The original plan was to order a XPS 15 pre-install with Linux.
> 
.. 
> 
> The Dell XPS 15 9570 now runs Debian Buster. What works:
> * the nice graphical screen
> * keyboard
> * touchpad
> * the NVMe  sdd
> * WIFI
> * and probably more  (untested yet)
> 

Thunderbolt docking station does work, initialy only in display port mode


To use wired ethernet interface and USB from the TB dock

Install the package `bolt`, plus this

root@trancilo:~# boltctl
 ● Dell Thunderbolt Cable
   ├─ type:  peripheral
   ├─ name:  Thunderbolt Cable
   ├─ vendor:Dell
   ├─ uuid:  00ed4274-2f5f-d400--
   ├─ status:connected
   │  ├─ authflags:  none
   │  └─ connected:  vr 10 aug 2018 16:43:13 UTC
   └─ stored:no

 ● Dell Thunderbolt Dock
   ├─ type:  peripheral
   ├─ name:  Thunderbolt Dock
   ├─ vendor:Dell
   ├─ uuid:  10b56968-2f5f-8680--
   ├─ status:connected
   │  ├─ authflags:  none
   │  └─ connected:  vr 10 aug 2018 16:43:14 UTC
   └─ stored:no

root@trancilo:~# boltctl enroll 00ed4274-2f5f-d400--
 ● Dell Thunderbolt Cable
   ├─ type:  peripheral
   ├─ name:  Thunderbolt Cable
   ├─ vendor:Dell
   ├─ uuid:  00ed4274-2f5f-d400--
   ├─ dbus path: 
/org/freedesktop/bolt/devices/00ed4274_2f5f_d400__
   ├─ status:authorized
   │  ├─ authflags:  none
   │  ├─ parent: c401-0080-7f18-2350-5310cc402021
   │  ├─ syspath:
/sys/devices/pci:00/:00:1b.0/:02:00.0/:03:00.0/:04:00.0/domain0/0-0/0-1
   │  ├─ authorized: vr 10 aug 2018 17:07:44 UTC
   │  └─ connected:  vr 10 aug 2018 16:43:13 UTC
   └─ stored:yes
  ├─ when:   vr 10 aug 2018 17:07:44 UTC
  ├─ policy: auto
  └─ key:no

root@trancilo:~# 
root@trancilo:~# boltctl enroll 10b56968-2f5f-8680--
 ● Dell Thunderbolt Dock
   ├─ type:  peripheral
   ├─ name:  Thunderbolt Dock
   ├─ vendor:Dell
   ├─ uuid:  10b56968-2f5f-8680--
   ├─ dbus path: 
/org/freedesktop/bolt/devices/10b56968_2f5f_8680__
   ├─ status:authorized
   │  ├─ authflags:  none
   │  ├─ parent: 00ed4274-2f5f-d400--
   │  ├─ syspath:
/sys/devices/pci:00/:00:1b.0/:02:00.0/:03:00.0/:04:00.0/domain0/0-0/0-1/0-301
   │  ├─ authorized: vr 10 aug 2018 17:09:51 UTC
   │  └─ connected:  vr 10 aug 2018 16:43:14 UTC
   └─ stored:yes
  ├─ when:   vr 10 aug 2018 17:09:51 UTC
  ├─ policy: auto
  └─ key:no

root@trancilo:~# 



Cheers
Geert Stappers
DevOps Engineer



Re: Bug#905793: Why does the Installer formats given swap

2018-08-10 Thread Herbert Kaminski
Am Fri, 10 Aug 2018 11:00:31 -0400
schrieb lsore...@csclub.uwaterloo.ca (Lennart Sorensen):

> On Fri, Aug 10, 2018 at 10:08:52AM +0200, Herbert Kaminski wrote:
> > Am Thu, 9 Aug 2018 14:14:15 -0400
> > schrieb lsore...@csclub.uwaterloo.ca (Lennart Sorensen):
> >   
> > > [...] 
> > > Well 99.9% of installs don't have another linux on the system,   
> >^
> > Interesting. How did you get that figure?  
> 
> Totally made it up. :)

OK, so I assume there is no feedback about who installed what and how
and when and where ;-)

Why I care at all: In the past, I used to test the Debian installer on
my main computer as it was the only one with up to date hardware, and I
had on it my working OS and a spare installation, and one or two DI
test installations. I found it quite annoying that after each test
the UUID of the swap changed, so I stopped testing DI. 

BTW the 5 people in the world having more than one installation on the
same machine presumably know well how to avoid the potential problems of
shared swap.

Regards
  Herbert

-- 



Re: Creating my own Preseeded ISO with partman replaced by a ZFS step

2018-08-10 Thread Raymond Burkholder

On 2018-08-10 04:51 PM, Bailey Parker wrote:

I'd like to somehow modify the installer ISO that I create when preseeding to
include ZFS (so that before the package manager is configured, a ZFS pool can
be created), replace the partman step with some custom scripting that [creates
a zpool and sets up the datasets][2], and finally install zfs-dkms (also
zfsutils-linux and zfs-initramfs).
I use the late_command to install kernel modules, packages, mirrors, 
kernels, etc.  I have used this to install the zfs modules for 
non-root-zfs boots where zfs partitions are used in other capacities


The late-command allows package install as well as 'in-target' style 
commands, which could call scripts loaded via the preseed process.

In digging through mail archives, I also came across [this script][5], but it's
unclear to me how exactly that would fit into my desired workflow. This sounds
like you'd need to manually drop to a shell to install/setup ZFS.

could probably be handled by the preseed late_command in-target abilities

Is there a sane way to go about adding ZFS root support to my preseeded install
or should I abandon this and wait for better support?  If the latter, are there
steps I could take to add better support given my limited knowledge of d-i?



I've used SaltStack to build my various preseed scripts depending upon 
how physical or virtual machines are built.




Processing of debootstrap_1.0.107_amd64.changes

2018-08-10 Thread Debian FTP Masters
debootstrap_1.0.107.dsc has incorrect md5 checksum; deleting it
debootstrap_1.0.107_amd64.buildinfo has incorrect md5 checksum; deleting it

Greetings,

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



Processing of debootstrap_1.0.107_amd64.changes

2018-08-10 Thread Debian FTP Masters
debootstrap_1.0.107_amd64.changes uploaded successfully to localhost
along with the files:
  debootstrap_1.0.107.dsc
  debootstrap_1.0.107.tar.gz
  debootstrap-udeb_1.0.107_all.udeb
  debootstrap_1.0.107_all.deb
  debootstrap_1.0.107_amd64.buildinfo

Greetings,

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



Re: Creating my own Preseeded ISO with partman replaced by a ZFS step

2018-08-10 Thread Nicholas D Steeves
On Sat, Aug 11, 2018 at 01:32:40AM +0200, Cyril Brulebois wrote:
> Hi,
> 
> Bailey Parker  (2018-08-10):
> > Is there a sane way to go about adding ZFS root support to my preseeded
> > install or should I abandon this and wait for better support?  If the
> > latter, are there steps I could take to add better support given my
> > limited knowledge of d-i?
> 
> I'm afraid we're not going to support ZFS as that would mean supporting
> out-of-tree kernel modules, which we migrated away from years ago.

Automated Debian on ZFS installation seems like a problem that FAI
should be able to solve.  https://wiki.debian.org/FAI

They don't yet have ZFS support, it's on the roadmap, and they might
be looking for someone to implement it.
  https://fai-project.org/roadmap

Cheers,
Nicholas


signature.asc
Description: PGP signature


debootstrap_1.0.107_amd64.changes ACCEPTED into unstable

2018-08-10 Thread Debian FTP Masters



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 26 Jul 2018 19:12:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.107
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 618839 829725 893713 903481 903657
Changes:
 debootstrap (1.0.107) unstable; urgency=medium
 .
   [ Patrick McDermott ]
   * Fix wgetprogress() with --debian-installer (Closes: #829725)
 .
   [ Dan Nicholson ]
   * Strip URL scheme from apt lists (Closes: #903481)
 .
   [ Hideki Yamane ]
   * Fix docker detection breaks QEMU's binfmt_misc bootstraping
 (Closes: #903657)
 - Avoid removing host's /proc on some environment
 - Add workaround for second-stage inside docker
   * Align scripts/gutsy to scripts/debian-common
   * Remove unnecessary script files from udeb package
 (Closes: #618839, #893713)
Checksums-Sha1:
 b20628c5c928a244be45c1936f5d2318b548b78f 1988 debootstrap_1.0.107.dsc
 1e46c94af6c421a97348679630a8ab6e08ecc316 74202 debootstrap_1.0.107.tar.gz
 42a33f6b6ac83ab3dab301d5bd746fb30079f2d7 20428 
debootstrap-udeb_1.0.107_all.udeb
 3e840e184ebb487eb7dc2fb055bcb448ba567cfa 71914 debootstrap_1.0.107_all.deb
 89ef75eded2a761ae21a17957fcf1148948ce9fd 5970 
debootstrap_1.0.107_amd64.buildinfo
Checksums-Sha256:
 aa64a2b1e5da8f8b1a0f59009e3e9f80cfa99400ba24f2fafaef8ec4998ce737 1988 
debootstrap_1.0.107.dsc
 e191aeb5855ec164902e012bccc504296fefecf3400b9a0c233843a01cc905bf 74202 
debootstrap_1.0.107.tar.gz
 923a606610b29f4ea277eaada7f2172292c87fe8632960e0fa7dac6b0e6c4f13 20428 
debootstrap-udeb_1.0.107_all.udeb
 d26114b8df0e8c99b3bae964b053672fafd9bf34f0577621dd3e2dc1a051dbc9 71914 
debootstrap_1.0.107_all.deb
 47421b738bb88cd146df4089fe7c64e949054c9dfcc549c6aed889814efb761e 5970 
debootstrap_1.0.107_amd64.buildinfo
Files:
 3965e136d83a9e86268f4a99ae8cc5a4 1988 admin optional debootstrap_1.0.107.dsc
 428e654319bc537c4e722f1b0c7ae142 74202 admin optional 
debootstrap_1.0.107.tar.gz
 58ae1e956e92453ed0a1f54a50e0ae29 20428 debian-installer optional 
debootstrap-udeb_1.0.107_all.udeb
 cfffc1f4eb637767a0be687e85b291d7 71914 admin optional 
debootstrap_1.0.107_all.deb
 7abe6b3d6bfc9b83e3ffaf1c1cf0eb69 5970 admin optional 
debootstrap_1.0.107_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEWOEiL5aWyIWjzRBMXTKNCCqqsUAFAltuWJoACgkQXTKNCCqq
sUAahA//fbVy4LJUEiFt+7oVQbRVOd/sBnU3/3B1/eDzLq+t4oQl67nn5pBGHVrA
3r6ulJZSRUyKKv1r9i40y7lJKgM/bQE9NIgT+ZufYqiDuNJPLXsGb/N8ZFnHblcy
c0r4w4XGxmPff9xSPyoSjAsgjmIeteoUPrd5ULs3HZc//SGjOCm3o6cm0eZWc0U6
sIlHhdDoTkn0gptTutc39aCXQDXYy5LjtQs1/qcqlND/JArd78XhH3wIDHWX1rK6
xrUWUKoTuLTGHlvR0JD46GEdWJhwhGZqKEgjQF8PS8v+Lp1gS3eh3TLgHrBHaFQk
Wd8caveSIQ1S+vVSK0dSGl7miMkVYY9WHKBT3umSIEaVuf8u04ZY/jYekjX0rney
TO5wwUZ1mlEoKtHicTnZNBgRYYLRJls5bbFWVanuoil5aBtokRuJx87r9uU1ODX4
7uZE60dElNg1qvG4RILIPe1ooGtyFjdyhwsHQGs6/SRbqFK5IqHvWsxrOEM9XvuN
+kov+wZEyUKuGtkxdTi2H5RvtaAVj+aaa+cFkBzT4t+DxiHJClt0vmjCKXgCKjj+
wPLlNuJP4kEChtzTY8OWDh0TN+HTC5yXeZA4V3Y7bXolMX3OkwOZToJlDCqizyj4
oThisLrRswnGzr9H8AAoghEGN/jnsjYLDJyyaBQr7XEoXwGxkk0=
=kSRA
-END PGP SIGNATURE-


Thank you for your contribution to Debian.



Re: Bug#905793: Why does the Installer formats given swap

2018-08-10 Thread John Paul Adrian Glaubitz
On 08/11/2018 01:56 AM, Herbert Kaminski wrote:
> Why I care at all: In the past, I used to test the Debian installer on
> my main computer as it was the only one with up to date hardware, and I
> had on it my working OS and a spare installation, and one or two DI
> test installations. I found it quite annoying that after each test
> the UUID of the swap changed, so I stopped testing DI. 

What's wrong with using a virtual machine for that? Why test d-i
on real hardware? On a VM, you'd just throw away the image afterwards.

> BTW the 5 people in the world having more than one installation on the
> same machine presumably know well how to avoid the potential problems of
> shared swap.

That's fine. But software has to adjust for the needs of 99.99% of its
users and not to 5 people who have an exotic usecase.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#905873: debootstrap: trusty and xenial not included in merged-usr blacklist

2018-08-10 Thread Randy Goldenberg
Package: debootstrap
Version: 1.0.106
Severity: normal
Tags: patch

Dear Maintainer,

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-131-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

debootstrap 1.0.106 installs a merged-usr file system by default.  Distros that 
do not use a merged-usr file system are blacklisted in 
/usr/share/debootstrap/scripts/.  /usr/share/debootstrap/scripts/trusty and 
/usr/share/debootstrap/scripts/xenial are symlinked to 
/usr/share/debootstrap/scripts/gutsy.  The script for gutsy does not include 
trusty and xenial as distros blacklisted for merged-usr file system deployment. 
 Consequently, merged-usr file systems are set up, resulting in failure when 
installation of non-merged-usr packages is attempted.  Below please find patch 
to blacklist trusty and xenial from merged-usr file system deployment.

--- gutsy.a 2018-08-10 14:37:30.569331851 -0700
+++ gutsy.b 2018-08-10 14:32:24.633067670 -0700
@@ -68,7 +68,7 @@ work_out_debs () {
 first_stage_install () {
case "$CODENAME" in
# "merged-usr" blacklist for past releases
-   
gutsy|hardy|intrepid|jaunty|karmic|lucid|maverick|natty|oneiric|precise|quantal|raring|saucy|utopic|vivid|wily|yakkety|zesty|artful|bionic|cosmic)
+   
gutsy|hardy|intrepid|jaunty|karmic|lucid|maverick|natty|oneiric|precise|quantal|raring|saucy|trusty|utopic|vivid|wily|xenial|yakkety|zesty|artful|bionic|cosmic)
[ -z "$MERGED_USR" ] && MERGED_USR="no"
;;
*)



Processing of debootstrap_1.0.107_amd64.changes

2018-08-10 Thread Debian FTP Masters
debootstrap_1.0.107.dsc has incorrect md5 checksum; deleting it
debootstrap_1.0.107_amd64.buildinfo has incorrect md5 checksum; deleting it

Greetings,

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



Bug#893713: marked as done (debootstrap-udeb: containts too many scripts files (most of them are symlink but...))

2018-08-10 Thread Debian Bug Tracking System
Your message dated Sat, 11 Aug 2018 04:48:53 +
with message-id 
and subject line Bug#893713: fixed in debootstrap 1.0.107
has caused the Debian Bug report #893713,
regarding debootstrap-udeb: containts too many scripts files (most of them are 
symlink but...)
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.)


-- 
893713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap-udeb
Severity: minor

Hi,

 It contains meaningless scripts as below.


drwxr-xr-x root/root 0 2018-03-17 23:46 ./usr/share/debootstrap/scripts/
-rw-r--r-- root/root  6016 2018-03-17 23:46 
./usr/share/debootstrap/scripts/aequorea
-rw-r--r-- root/root  6296 2018-03-17 23:46 
./usr/share/debootstrap/scripts/etch
-rw-r--r-- root/root  7461 2018-03-17 23:46 
./usr/share/debootstrap/scripts/gutsy
-rw-r--r-- root/root  6233 2018-03-17 23:46 
./usr/share/debootstrap/scripts/sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/artful -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/bartholomea -> aequorea
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/bionic -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/bullseye -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/buster -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/chromodoris -> aequorea
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/dasyatis -> aequorea
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/etch-m68k -> etch
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/hardy -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/intrepid -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/jaunty -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/jessie -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/jessie-kfreebsd -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/karmic -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/lenny -> etch
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/lucid -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/maverick -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/natty -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/oldoldstable -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/oldstable -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/oneiric -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/precise -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/quantal -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/raring -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/saucy -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/squeeze -> etch
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/stretch -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/trusty -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/utopic -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/vivid -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/wheezy -> sid
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/wily -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/xenial -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/yakkety -> gutsy
lrwxrwxrwx root/root 0 2018-03-17 23:46 
./usr/share/debootstrap/scripts/zesty -> gutsy

 Not harm but messy.
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.107

We believe that the bug you reported is fixed in the latest version of
debootstrap, which is 

Bug#903481: marked as done (debootstrap: Save apt compatible lists)

2018-08-10 Thread Debian Bug Tracking System
Your message dated Sat, 11 Aug 2018 04:48:53 +
with message-id 
and subject line Bug#903481: fixed in debootstrap 1.0.107
has caused the Debian Bug report #903481,
regarding debootstrap: Save apt compatible lists
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.)


-- 
903481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.106
Severity: normal
Tags: patch

Since commit 
https://salsa.debian.org/installer-team/debootstrap/commit/48d77abf3a4209f7cff72aec20f618e086169aa7
debootstrap no longer saves repo list files in an apt compatible
format. A side effect of the old debootstrap.invalid setup was that
the mv_invalid_to function renamed the downloaded repo lists to files
that apt uses. Before you'd get the following:

var/lib/apt/lists/deb.debian.org_debian_dists_sid_InRelease

Now you get

var/lib/apt/lists/http:__deb.debian.org_debian_dists_sid_InRelease

That means that you're required to run apt update after debootstrap
finishes since apt will ignore the downloaded lists.

--
Dan Nicholson  |  +1.206.437.0833  |  Endless
From ef2c7d1d7810b50f58554da0351e6daf572be11d Mon Sep 17 00:00:00 2001
From: Dan Nicholson 
Date: Tue, 10 Jul 2018 06:05:42 -0500
Subject: [PATCH] Strip URL scheme from apt lists

Apt saves the repo lists without the URL scheme, so when debootstrap
keeps the URL scheme in the name they're not usable by apt. That means
you need to run apt update in the completed target even though the lists
have already been fetched. Without this change the default InRelease was
saved as http:__deb.debian.org_debian_dists_sid_InRelease.

This is a regression from commit 48d77ab since the old
debootstrap.invalid setup would rename the lists to the proper name in
most cases since it stripped the leading http://.
---
 functions | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/functions b/functions
index 38c710b..7b893d7 100644
--- a/functions
+++ b/functions
@@ -490,12 +490,12 @@ apt_dest () {
 	pkg)
 		local m="$5"
 		printf "%s" "$APTSTATE/lists/"
-		echo "${m}_$6" | sed 's/\//_/g'
+		echo "${m}_$6" | sed -e 's,^[^:]\+://,,' -e 's/\//_/g'
 		;;
 	rel)
 		local m="$3"
 		printf "%s" "$APTSTATE/lists/"
-		echo "${m}_$4" | sed 's/\//_/g'
+		echo "${m}_$4" | sed -e 's,^[^:]\+://,,' -e 's/\//_/g'
 		;;
 	esac
 }
-- 
2.11.0

--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.107

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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: Thu, 26 Jul 2018 19:12:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.107
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 618839 829725 893713 903481 903657
Changes:
 debootstrap (1.0.107) unstable; urgency=medium
 .
   [ Patrick McDermott ]
   * Fix wgetprogress() with --debian-installer (Closes: #829725)
 .
   [ Dan Nicholson ]
   * Strip URL scheme from apt lists (Closes: #903481)
 .
   [ Hideki Yamane ]
   * Fix docker detection breaks QEMU's binfmt_misc bootstraping
 (Closes: #903657)
 - Avoid removing host's /proc on some environment
 - Add workaround for second-stage inside docker
   * Align scripts/gutsy to scripts/debian-common
   * Remove unnecessary script files from udeb package
 (Closes: #618839, #893713)
Checksums-Sha1:
 b20628c5c928a244be45c1936f5d2318b548b78f 1988 debootstrap_1.0.107.dsc
 1e46c94af6c421a97348679630a8ab6e08ecc316 74202 debootstrap_1.0.107.tar.gz
 42a33f6b6ac83ab3dab301d5bd746fb30079f2d7 20428 
debootstrap-udeb_1.0.107_all.udeb
 3e840e184ebb487eb7dc2fb055bcb448ba567cfa 71914 debootstrap_1.0.107_all.deb
 

Bug#829725: marked as done (debootstrap: cannot bootstrap from repositories without InRelease files when --debian-installer set)

2018-08-10 Thread Debian Bug Tracking System
Your message dated Sat, 11 Aug 2018 04:48:52 +
with message-id 
and subject line Bug#829725: fixed in debootstrap 1.0.107
has caused the Debian Bug report #829725,
regarding debootstrap: cannot bootstrap from repositories without InRelease 
files when --debian-installer set
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.)


-- 
829725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.81
Severity: normal

I am using debootstrap in my own minimal system bootstrapper, and am making use
of the progress information reported to FH 3 as enabled by the
--debian-installer command-line flag.

Unfortunately, using this flag causes the behaviour of debootstrap to change,
specifically in its handling of InRelease / Release files.

During normal operation, debootstrap will first attempt to fetch an InRelease
file from the repository; if this is unavailable, i.e. the fetch fails with
404, then debootstrap will normally fall back to fetching a Release file
instead.  Indeed, this is the behaviour of debootstrap if --debian-installer is
not passed on the command-line.

debootstrap uses the wgetprogress() function to fetch these URLs.  It reads:

wgetprogress () {
[ ! "$VERBOSE" ] && QSWITCH="-q"
local ret=0
if [ "$USE_DEBIANINSTALLER_INTERACTION" ] && [ "$PROGRESS_NEXT" ]; then
wget "$@" 2>&1 >/dev/null | $PKGDETAILS "WGET%" $PROGRESS_NOW
$PROGRESS_NEXT $PROGRESS_END >&3
ret=$?
else
wget $QSWITCH "$@"
ret=$?
fi
return $ret
}

When the --debian-installer command-line flag is set, the first path of the if
branch will be taken - running the output of wget through a pipe, so that the
$PKGDETAILS command can be used to parse progress information provided by wget
and report it to FH 3 in a format usable by debian-installer.

However, if the URL passed to wget returns 404, then while the wget command
will fail, the $PKGDETAILS command, and thus the pipeline as a whole, does not,
and the wgetprocess () function thus erroneously returns success.

As a consequence, debootstrap does not fall back to fetching and using a
Release file as it should in this case, and the bootstrapping attempt as a
whole fails.

Because this is a POSIX shell-script, I don't believe there is a
straightforward mechanism to fetch the exit status of the wget command when it
is part of a pipeline.  (See: http://cfajohnson.com/shell/cus-faq-2.html#Q11).
It might be possible to enhance the code invoked by $PKGDETAILS to return a
fatal exit status if it does not definitely see a successful file retrieval?

A more direct work-around is to modify this function to unconditionally use the
second code path that does not attempt to invoke wget as part of a pipeline.
However, this does mean that you lose out on intra-file download progress
reporting.



-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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.18-1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   1.4.20-6

debootstrap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.107

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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: Thu, 26 Jul 2018 19:12:20 +0900
Source: debootstrap
Binary: debootstrap 

Bug#618839: marked as done (debootstrap-udeb: restore stable/testing/unstable scripts)

2018-08-10 Thread Debian Bug Tracking System
Your message dated Sat, 11 Aug 2018 04:48:52 +
with message-id 
and subject line Bug#618839: fixed in debootstrap 1.0.107
has caused the Debian Bug report #618839,
regarding debootstrap-udeb: restore stable/testing/unstable scripts
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.)


-- 
618839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: debootstrap-udeb
version: 1.0.28
severity: normal
tags: patch

It can actually be useful to have the various statically named scripts
available in the installer.  In particular, for working on snapshots,
its more useful for me to be able to use the term testing everywhere,
rather than hardcoding wheezy specifically just for debootstrap.

Attached is a patch for this.

Thanks,
Mike
diff -Nru debootstrap-1.0.28/debian/changelog debootstrap-1.0.28gilbert1/debian/changelog
--- debootstrap-1.0.28/debian/changelog	2011-02-21 19:51:19.0 -0500
+++ debootstrap-1.0.28gilbert1/debian/changelog	2011-03-18 16:25:11.0 -0400
@@ -1,3 +1,9 @@
+debootstrap (1.0.28gilbert1) unstable; urgency=low
+
+  * Don't remove convienience links in debootstrab-udeb.
+
+ -- Michael Gilbert   Fri, 18 Mar 2011 16:24:43 -0400
+
 debootstrap (1.0.28) unstable; urgency=low
 
   [ Miguel Figueiredo ]
diff -Nru debootstrap-1.0.28/debian/rules debootstrap-1.0.28gilbert1/debian/rules
--- debootstrap-1.0.28/debian/rules	2011-01-18 12:16:05.0 -0500
+++ debootstrap-1.0.28gilbert1/debian/rules	2011-03-18 16:24:36.0 -0400
@@ -23,7 +23,4 @@
 		debian/debootstrap-udeb/usr/share/debootstrap/scripts/edgy \
 		debian/debootstrap-udeb/usr/share/debootstrap/scripts/feisty \
 		debian/debootstrap-udeb/usr/share/debootstrap/scripts/*.buildd \
-		debian/debootstrap-udeb/usr/share/debootstrap/scripts/*.fakechroot \
-		debian/debootstrap-udeb/usr/share/debootstrap/scripts/stable \
-		debian/debootstrap-udeb/usr/share/debootstrap/scripts/testing \
-		debian/debootstrap-udeb/usr/share/debootstrap/scripts/unstable
+		debian/debootstrap-udeb/usr/share/debootstrap/scripts/*.fakechroot
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.107

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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: Thu, 26 Jul 2018 19:12:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.107
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 618839 829725 893713 903481 903657
Changes:
 debootstrap (1.0.107) unstable; urgency=medium
 .
   [ Patrick McDermott ]
   * Fix wgetprogress() with --debian-installer (Closes: #829725)
 .
   [ Dan Nicholson ]
   * Strip URL scheme from apt lists (Closes: #903481)
 .
   [ Hideki Yamane ]
   * Fix docker detection breaks QEMU's binfmt_misc bootstraping
 (Closes: #903657)
 - Avoid removing host's /proc on some environment
 - Add workaround for second-stage inside docker
   * Align scripts/gutsy to scripts/debian-common
   * Remove unnecessary script files from udeb package
 (Closes: #618839, #893713)
Checksums-Sha1:
 b20628c5c928a244be45c1936f5d2318b548b78f 1988 debootstrap_1.0.107.dsc
 1e46c94af6c421a97348679630a8ab6e08ecc316 74202 debootstrap_1.0.107.tar.gz
 42a33f6b6ac83ab3dab301d5bd746fb30079f2d7 20428 
debootstrap-udeb_1.0.107_all.udeb
 3e840e184ebb487eb7dc2fb055bcb448ba567cfa 71914 debootstrap_1.0.107_all.deb
 89ef75eded2a761ae21a17957fcf1148948ce9fd 5970 
debootstrap_1.0.107_amd64.buildinfo
Checksums-Sha256:
 aa64a2b1e5da8f8b1a0f59009e3e9f80cfa99400ba24f2fafaef8ec4998ce737 1988 
debootstrap_1.0.107.dsc
 e191aeb5855ec164902e012bccc504296fefecf3400b9a0c233843a01cc905bf 74202 
debootstrap_1.0.107.tar.gz
 

Bug#903657: marked as done (docker detection breaks QEMU's binfmt_misc bootstraping)

2018-08-10 Thread Debian Bug Tracking System
Your message dated Sat, 11 Aug 2018 04:48:53 +
with message-id 
and subject line Bug#903657: fixed in debootstrap 1.0.107
has caused the Debian Bug report #903657,
regarding docker detection breaks QEMU's binfmt_misc bootstraping
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.)


-- 
903657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.95ubuntu0.1
Severity: important

Dear Maintainer,

QEMU's build system has support for debootstrap using binfmt_misc and
QEMU's linux-user emulation. Since commit 9a6ebf628 this is broken as
it checks for the presence of wget which isn't available in the
second-stage environment.

If the user is doing a --second-stage it shouldn't matter that wget is
missing as all the packages have already been downloaded on the host
system.

For reference the wrapper script is:

  
https://git.qemu.org/?p=qemu.git;a=blob;f=tests/docker/dockerfiles/debian-bootstrap.pre;h=56e1aa7a21418437b5b0fbaf473a8686338d9014;hb=cee35138b59c6d6b0808c5fa644e3f063832860f

And you should be able to debootstrap on QEMU's master with a line
like:

  make docker-binfmt-image-debian-ubuntu-xenial-arm64 DEB_ARCH=arm64 \
DEB_TYPE=xenial DEB_URL=http://ports.ubuntu.com 
EXECUTABLE=./aarch64-linux-user/qemu-aarch64~

There is also a bug in QEMU's own script which means it always falls
back to the SCM version of debootstrap, but that is mine to fix ;-)

-- System Information:
Debian Release: buster/sid
  APT prefers bionic-updates
  APT policy: (500, 'bionic-updates'), (500, 'bionic-security'), (500, 'bionic')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf

Kernel: Linux 4.15.0-24-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debootstrap depends on:
ii  wget  1.19.4-1ubuntu2.1

Versions of packages debootstrap recommends:
ii  gnupg   2.2.4-1ubuntu1.1
ii  ubuntu-keyring  2018.02.28

Versions of packages debootstrap suggests:
pn  ubuntu-archive-keyring  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.107

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

Debian distribution maintenance software
pp.
Hideki Yamane  (supplier of updated debootstrap 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: Thu, 26 Jul 2018 19:12:20 +0900
Source: debootstrap
Binary: debootstrap debootstrap-udeb
Architecture: source all
Version: 1.0.107
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Hideki Yamane 
Description:
 debootstrap - Bootstrap a basic Debian system
 debootstrap-udeb - Bootstrap the Debian system (udeb)
Closes: 618839 829725 893713 903481 903657
Changes:
 debootstrap (1.0.107) unstable; urgency=medium
 .
   [ Patrick McDermott ]
   * Fix wgetprogress() with --debian-installer (Closes: #829725)
 .
   [ Dan Nicholson ]
   * Strip URL scheme from apt lists (Closes: #903481)
 .
   [ Hideki Yamane ]
   * Fix docker detection breaks QEMU's binfmt_misc bootstraping
 (Closes: #903657)
 - Avoid removing host's /proc on some environment
 - Add workaround for second-stage inside docker
   * Align scripts/gutsy to scripts/debian-common
   * Remove unnecessary script files from udeb package
 (Closes: #618839, #893713)
Checksums-Sha1:
 b20628c5c928a244be45c1936f5d2318b548b78f 1988 debootstrap_1.0.107.dsc
 1e46c94af6c421a97348679630a8ab6e08ecc316 74202 debootstrap_1.0.107.tar.gz
 42a33f6b6ac83ab3dab301d5bd746fb30079f2d7 20428 
debootstrap-udeb_1.0.107_all.udeb
 3e840e184ebb487eb7dc2fb055bcb448ba567cfa 71914 debootstrap_1.0.107_all.deb
 89ef75eded2a761ae21a17957fcf1148948ce9fd 5970 
debootstrap_1.0.107_amd64.buildinfo

Bug#905864: Ubuntu trusty and xenial are installed with merged-/usr by default

2018-08-10 Thread Derek Poon
Package: debootstrap
Version: 1.0.106
Tags: patch

Since debootstrap 1.0.102, merged-/usr installs are the default, except when 
installing blacklisted suites.  The blacklist was established in 
https://salsa.debian.org/installer-team/debootstrap/commit/4a1b3ca, whose 
commit message says:

Set non merged-usr release

We do not apply merged-usr until Debian stretch and Ubuntu cosmic.

However, the actual blacklist is (from scripts/gutsy):

case "$CODENAME" in

…|quantal|raring|saucy|utopic|vivid|wily|yakkety|zesty|artful|bionic|cosmic)

Note that trusty and xenial are missing.  This causes their installation to 
fail due to file conflicts in certain packages.

My speculation is that the omission was due to a copy-paste error from line 4 
of scripts/gutsy.






From: Derek Poon 
Date: Fri, 10 Aug 2018 14:47:05 -0700
Subject: [PATCH] Added trusty and xenial to merged-/usr blacklist

The blacklist should include all Ubuntu releases up to cosmic.
---
 scripts/gutsy | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/gutsy b/scripts/gutsy
index b460e90..82c59c5 100644
--- a/scripts/gutsy
+++ b/scripts/gutsy
@@ -68,7 +68,7 @@ work_out_debs () {
 first_stage_install () {
case "$CODENAME" in
# "merged-usr" blacklist for past releases
-   
gutsy|hardy|intrepid|jaunty|karmic|lucid|maverick|natty|oneiric|precise|quantal|raring|saucy|utopic|vivid|wily|yakkety|zesty|artful|bionic|cosmic)
+   
gutsy|hardy|intrepid|jaunty|karmic|lucid|maverick|natty|oneiric|precise|quantal|raring|saucy|trusty|utopic|vivid|wily|xenial|yakkety|zesty|artful|bionic|cosmic)
[ -z "$MERGED_USR" ] && MERGED_USR="no"
;;
*)
-- 
2.17.1


Re: Bug#905793: Why does the Installer formats given swap

2018-08-10 Thread Herbert Kaminski
Am Thu, 9 Aug 2018 14:14:15 -0400
schrieb lsore...@csclub.uwaterloo.ca (Lennart Sorensen):

> [...] 
> Well 99.9% of installs don't have another linux on the system, 
   ^
Interesting. How did you get that figure?

Regards,
  Herbert



Re: Bug#905793: Why does the Installer formats given swap

2018-08-10 Thread John Paul Adrian Glaubitz
On 08/10/2018 10:08 AM, Herbert Kaminski wrote:
> Am Thu, 9 Aug 2018 14:14:15 -0400
> schrieb lsore...@csclub.uwaterloo.ca (Lennart Sorensen):
> 
>> [...] 
>> Well 99.9% of installs don't have another linux on the system, 
>^
> Interesting. How did you get that figure?

It's most certainly a hyperbole, but I think it's not too far fetched
to assume that the number of users who are installing multiple Linux
distributions in parallel on the same machine is rather negligible.

So, I'm not sure whether that's a usecase worth supporting given
the fact that there are also potential issues you can run into
when sharing a swap partition among multiple Linux distributions
on the same disk.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Bug#905827: Buster on Dell XPS 15 9570

2018-08-10 Thread Geert Stappers
Package: installation-report

Summary: Customer did what hardware vendor should have done

Hi,

The original plan was to order a XPS 15 pre-install with Linux.

Website of Dell has / had it too well hidden,
so we ordered a XPS 15 9570 with MS Windows 10 and installed Linux.


Installed with version 2018-08-06
from 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/
the non-free firmware is for the wireless network interface card.

The .iso was dd-ed to a usb memory stick.

Upon power-on pressed repeatly F12 to get One-Time Boot Menu

Changed boot mode to
  1) Legacy External Device Boot Mode, Secure Boot OFF

Two warning screens/menus followed. Using lot of yellow text
and even red text.
Confirmed both with "Yes, my hardware, my choice of software"

Booted from the usb memory stick ( not from the partition
within the usb memory stick )

Was greeted by the graphical toplevel menu. Did choose 'install'.
Not 'graphical install' to avoid possible issues. The 'graphic
install' might work, it wasn't tested by me.

There was a warning about missing firmware, it could be ignored due
the use of the nonfree included CD image. ( With using the regular
image (also from weekly build 2018-08-06) there was the same warning
with more missing drivers missed, but ignoring that warning did get me
a working WIFI connection. )

The install went fine. Packages being downloaded. The nvme disk being
detected, partitioned, written.

The first reboots weren't succesfull, additional tweaking was needed.

Oh, by the way the firmware has a time sucking (customer insulting) way
of reporting "no boot device was found". It enters selftest mode and
after the plus five minutes test it eventually tells "no boot device".
Aborting the selftest results into a shutdown.
  @Dell: Please report "no boot device" without going through selftest


There was no boot device defined. Defined it manually in "BIOS".
Bootsequence, EFI, ... serveral menus ...  grubx64.efi

Then it did boot into a black screen. Used usb memory stick again
for booting into rescue mode. `dmesg` reported
[0.799..] ahci :00:17.0: Found 1 remapped NVMe devices.
[0.799..] ahci :00:17.0: Switch your BIOS from RAID to AHCI mode to use 
them.
Done under F12 -> OTHER OPTIONS -> BIOS SETUP -> System Configuration -> SATA 
Operation


The Dell XPS 15 9570 now runs Debian Buster. What works:
* the nice graphical screen
* keyboard
* touchpad
* the NVMe  sdd
* WIFI
* and probably more  (untested yet)


Cheers
Geert Stappers
DevOps engineer