Re: torified netinst.iso and live.iso

[Tempest]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Steve McIntyre:
> This sounds like a very good idea, thanks! As far as I can see,
> we'd need to:
> 
> 1. add the extra packages (tor, apt-transport-tor, anything else?)
> 
> very easy - I can add those to the package lists for d-i and/or 
> debian-cd very easily
> 
> 2. change the sources.list to use those and the onion addresses
> 
> slightly more involved - we'd need to tweak things, maybe give 
> users the choice during installation
> 
> 3. if the user chose to use tor at install time, change d-i itself
> to use tor for even the initial installation packages
> 
> much more complex - we'd need tor support built into d-i too, I 
> guess
> 
> If we'd want #3 too, that will need development work in d-i from 
> somebody who knows tor?
> 

this is it, in a nutshell. goal would be to do the initial
base/package installs over tor at install time. that way, if someone
downloaded the netinst.iso with torbrowser, all of the debian install
process would later be torified as well, effectively blocking various
levels of eyes from seeing that debian was ever used.

thank you for the reply.

- -- 
gpg key - 0x2A49578A7291BB34
fingerprint - 63C4 E106 AC6A 5F2F DDB2 3840 2A49 578A 7291 BB34
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX4hq3XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2M0M0RTEwNkFDNkE1RjJGRERCMjM4NDAy
QTQ5NTc4QTcyOTFCQjM0AAoJECpJV4pykbs04SAP/38Rf8pr9ebtotPUO5XwVbWE
D0osbYnDGtA9EooieArJ3NbISo+yJfDrWjpr4Pymb4tIerv+x+pUCLzwPIMSikVC
S2vo4wZtbKql/Z1cSuFlyuhVrmwpv9MOQfoTdj+PQfofujqxWqwc2VQeUBtU8QFN
SYanyCZ9eXjQaQz3IliCVdDL7PfcWqxO7OjCkkyFRsWnPyS/hK2v6iu/mOdZVu6X
ExqguZk2SXCQdOOkoXhMMT4EH7+beFGDcwIdCuITj8usfP54wMIVgNUvAjj3//QY
uneND0BB9/VxF+8y1yoXsPk5PlUjs8BDNfRXYeKKgK+cUK0oCmlPoOqo9XAr53pu
6MOgoLG/mMNw/2VWuTm4VDd/V/ijnqz9B5tgCBP34CeFdCKwQiHUoXTJJ7vPbSfn
d5/q850BRnzrxNsZtDUJ4HURlp2dTUPLowY8tR1VQ4uV+Z4LTeLo7zlU1W77h0F6
9TrfrxOy9IoDvhZhOueLJzpaK/fx2Lb24WHNVc8zF58O8qxs4boZk1qZE9nkDCxC
BKIOticlerw9VilZT+lMLlN3iK855WOv4dmetyTZ2lD4ZgQ9kTOGyzD7XKZDxeFe
cLF2x9LtH5oe8ywwCy1NhOxWyFFsgjhDTx3Etill3oyTtl/kwm+IdQou7apqSs4u
fLLjFapnPhHS8dAbbCso
=F6e7
-END PGP SIGNATURE-

Processed: tagging 837649

[Debian Bug Tracking System]

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

> tags 837649 + patch
Bug #837649 [debootstrap] debootstrap: Add support for Packages.xz
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#837649: debootstrap: Add support for Packages.xz

[Ansgar Burchardt]

Ansgar Burchardt writes:
> debootstrap should support archives that only provide Packages.xz.
>
> I'll try to take a look at implementing this soon.  From a quick glance
> it shouldn't be too difficult given several compression formats are
> already supported (bz2, gz, uncompressed).

I've prepared a patch for this[1].  It worked for me with both a
Packages.xz suite (stretch) and one only providing Package.bz2, but not
.xz (squeeze).

Ansgar

  [1] 
https://github.com/aburch/debootstrap/commit/1689d645aacb0bc3f9edb86526f67e776469942a

Bug#755848: Patch

[Eric Desrochers]

This patch include a script under finish-install.d/56netcfg-hostname that 
detect if netcfg/hostname is set in preseed file and override the hostname at 
the end of the installation. If not set then it keeps the hostname as is.
>From 53522b8129f9542a1d7c9a21344d8b8b2732c9ce Mon Sep 17 00:00:00 2001
From: Eric Desrochers 
Date: Tue, 20 Sep 2016 20:02:16 -0400
Subject: [PATCH] Fix netcfg/hostname that does not set hostname

---
 finish-install.d/56netcfg-hostname | 17 +
 1 file changed, 17 insertions(+)
 create mode 100755 finish-install.d/56netcfg-hostname

diff --git a/finish-install.d/56netcfg-hostname b/finish-install.d/56netcfg-hostname
new file mode 100755
index 000..2256c5b
--- /dev/null
+++ b/finish-install.d/56netcfg-hostname
@@ -0,0 +1,17 @@
+#! /bin/sh
+set -e
+
+PROGNAME=$(basename $0)
+CURRENT_HOSTNAME=`/bin/hostname`
+NETCFG_HOSTNAME=`/bin/debconf-get netcfg/hostname`
+
+# Override hostname, if "netcfg/hostname" is set in preseed file. #
+if [ -n "$NETCFG_HOSTNAME" ]; then
+/bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /target/etc/hostname
+/bin/sed -i "s/$CURRENT_HOSTNAME/$NETCFG_HOSTNAME/" /target/etc/hosts
+/usr/bin/logger "$PROGNAME: d-i netcfg/hostname $NETCFG_HOSTNAME took precedence"
+
+# Keep hostname as is, if "netcfg/hostname" is not set in preseed file. #
+else
+exit 0
+fi
-- 
2.5.0

Processed: merging 770658 718632

[Debian Bug Tracking System]

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

> merge 770658 718632
Bug #770658 [debootstrap] fails to debootstrap debian on fedora: Failure trying 
to run: chroot /debian mount -t proc proc /proc
Bug #718632 [debootstrap] chroot fails due to incorrect path on Arch Linux
Marked as found in versions debootstrap/1.0.64.
Bug #770658 [debootstrap] fails to debootstrap debian on fedora: Failure trying 
to run: chroot /debian mount -t proc proc /proc
Marked as found in versions debootstrap/1.0.48+deb7u1.
Merged 718632 770658
> thanks
Stopping processing here.

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

Bug#544120: marked as done (debootstrap: --make-tarball yields exit value 1 (one))

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 01:40:32 +0200
with message-id <8737kuxhqn@deep-thought.43-1.org>
and subject line Re: debootstrap: --make-tarball yields exit value 1 (one)
has caused the Debian Bug report #544120,
regarding debootstrap: --make-tarball yields exit value 1 (one)
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.)


-- 
544120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.10lenny1
Severity: important

The following perfectly valid and correct usage

   # debootstrap --include host --exclude laptop-detect \
 --arch i386 --make-tarball ./packs.tgz \
 etch /mnt/ http://host-of-choice/debian/

completes with return value 1, thus preventing its use
in a GNU Makefile, unless error checking is avoided on
the above statement. This must be judged as a major
impediment and undesirable behaviour.

The mandatory full file path demanded by "--unpack-tarball"
in version 1.0.10lenny1, contrasted to the relative path
accepted bu "--make-tarball", is likewise annoying, but is
easier to detect and circumvent in standard ways.

-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable'), (90, 'testing'), (80, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=sv_SE.ISO-8859-15, LC_CTYPE=sv_SE.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages debootstrap depends on:
ii  binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina
ii  wget1.11.4-2 retrieves files from the web

debootstrap recommends no packages.

debootstrap suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.0.83

I tried to reproduce this with the current version of debootstrap
running

  debootstrap --force-check-gpg \
--include host --exclude laptop-detect \
--arch i386 --make-tarball stretch.tgz \
stretch stretch [mirror]

As this finished without as error (that is with return code 0), I assume
this has since been fixed.

Ansgar--- End Message ---

Bug#629583: marked as done (debootstrap: can't install on nfs shares)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 01:29:50 +0200
with message-id <877fa6xi8h@deep-thought.43-1.org>
and subject line Re: Bug#629583: debootstrap: can't install on nfs shares
has caused the Debian Bug report #629583,
regarding debootstrap: can't install on nfs shares
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.)


-- 
629583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.30
Severity: important

i've tried debootstrap and cdebootstrap on the debian live cd (and on some 
other systems as well)
debootstraping to a local drive works fine, but it just hangs when installing 
to a nfs mounted folder
both, amd64 and i386, are affected
found this bug in 1.0.26 and 1.0.30
strace debootstrap output ended with chroot, right after extracting packages

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  wget  1.12-3.1   retrieves files from the web

Versions of packages debootstrap recommends:
ii  debian-archive-keyring2010.08.28 GnuPG archive keys of the Debian a
ii  gnupg 1.4.11-3   GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
There has been no follow-up on Joey's question[1] by the submitter.

Ansgar

  [1] https://bugs.debian.org/629583#15--- End Message ---

Bug#799341: marked as done (x32 and failure to install chroot environment due to mount failure)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 01:24:09 +0200
with message-id <87fuouxihy@deep-thought.43-1.org>
and subject line Re: Bug#799341: x32 and failure to install chroot environment 
due to mount failure
has caused the Debian Bug report #799341,
regarding x32 and failure to install chroot environment due to mount failure
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.)


-- 
799341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.72
Severity: important

*

I work with a free/open source project (http://www.cryptopp.com/). A
Debian maintainer reported a failure for X32. I'm trying to get a test
rig setup to duplicate the issue. I'm following Debian's X32Port wiki
page (https://wiki.debian.org/X32Port).

# apt-get install debian-ports-archive-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
debian-ports-archive-keyring is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# debootstrap --arch=x32
--keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg
unstable debian-x32 http://ftp.debian-ports.org/debian
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 1AD7967B6A55FDD7C0746577A53AB45AC448326E)
I: Retrieving Packages
...

I: Extracting util-linux...
I: Extracting zlib1g...
W: Failure trying to run: chroot /root/debian-x32 mount -t proc proc /proc
W: See /root/debian-x32/debootstrap/debootstrap.log for details
# cat /root/debian-x32/debootstrap/debootstrap.log
gpgv: Signature made Thu Sep 17 21:20:09 2015 EDT using RSA key ID C448326E
gpgv: Good signature from "Debian Ports Archive Automatic Signing Key
(2015) "
gpgv: Signature made Thu Sep 17 21:20:09 2015 EDT using RSA key ID C448326E
gpgv: Good signature from "Debian Ports Archive Automatic Signing Key
(2015) "
chroot: failed to run command 'mount': Exec format error

*

These issues may (or may not) be related. Michael Tokarev, who helped
with some qemu-system and qemu-user issues I was having, is familiar
with them.

799120, "execv and format error due to binfmt types [sic]",
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799120)
784605, "binfmt masks: allow ELF_OSABI=0|3 on some architectures"
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784605)

799120 has a different title; it was summarized for convenience with
the cause for this report.

*

Based on the debootstrap command, I'm filing against debootstrap. But
I have a feeling it may not be correct. In fact, my last couple of
bugs in this area have been filed against the wrong package, so please
accept my apologies in advance.

I also tried qemu-debootstrap process with the following result, so I
don't believe its qemu or qemu-user issue:

# qemu-debootstrap --arch=x32 --keyring
/usr/share/keyrings/debian-archive-keyring.gpg --variant=buildd
--exclude=debfoster unstable debian-x32 http://ftp.debian.org/debian
E: Sorry, I don't know how to support arch

*

# Debian 8, x86_64, fully patched. I run 'update' and 'dist-upgrade'
religiously.

$ uname -a
Linux debian-8-x64 4.1.0-2-amd64 #1 SMP Debian 4.1.6-1 (2015-08-23)
x86_64 GNU/Linux

$ lsb_release
No LSB modules are available.

*

$ apt-cache show debootstrap
Package: debootstrap
Version: 1.0.72
Installed-Size: 236
Maintainer: Debian Install System Team 
Architecture: all
Depends: wget
Recommends: gnupg, debian-archive-keyring
Description-en: Bootstrap a basic Debian system
 debootstrap is used to create a Debian base system from scratch,
 without requiring the availability of dpkg or apt. It does this by
 downloading .deb files from a mirror site, and carefully unpacking them
 into a directory which can eventually be chrooted into.
Description-md5: 883a8efb3ed16248b0d2091d9c0b60c9
Tag: admin::virtualization, devel::debian, implemented-in::shell,
 interface::commandline, protocol::http, role::program, scope::utility,
 suite::debian, works-with-format::tar, works-with::software:package
Section: admin
Priority: extra
Filename: pool/main/d/debootstrap/debootstrap_1.0.72_all.deb
Size: 65002
MD5sum: bb770d60961ce50a906fe570a36f907d
SHA1: 52c6a120f24534e18dac02ee995d8066a5946fe7
SHA256: 501fb1b22c5b18a831c1fd983c108a1de9330baca6c08a55edef25c2e4f99e12

Package: debootstrap
Version: 1.0.67
Installed-Size: 229
Maintainer: Debian Install System Team 

Bug#365669: marked as done (debootstrap doesn't create /dev/hd* entries)

[Debian Bug Tracking System]

Your message dated Wed, 21 Sep 2016 01:19:36 +0200
with message-id <87k2e6xipj@deep-thought.43-1.org>
and subject line Re: Bug#365669: debootstrap and devices
has caused the Debian Bug report #365669,
regarding debootstrap doesn't create /dev/hd* entries
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.)


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

Package: debootstrap
Version: 0.3.3

Subject says it all: no /dev/hd* entries are created by debootstrap.

Configuration
-

VmWare on Windows, with an hda and a hdc drive.
Booting from hdc, which carries what I'll call the "base system", a 
netboot image that I ripped off from my rootserver provider and adapted 
to boot from hdc.

Incidentally, the base system is a Debian, with a 2.6.26 kernel.

I'm bootstrapping things onto the hda drive. hda partitions were mounted 
on the following mountpoints (which hence had to be created before 
running debootstrap):

  /inst  /dev/hda5
  /inst/boot /dev/hda1
  /inst/usr  /dev/hda6
  /inst/var  /dev/hda7

Behaviour
-

debootstrap runs through without any problems, and populates /inst/dev 
in three steps:

1) Create the /dev directory (very early, even before downloading packages).
2) Create a lot of standard devices (core, full, kmem, loop*, mem, null, 
port, ptmx, ram*, random, tty, urandom, zero; after download).
3) Create the MAKEDEV script and devices that seem at least partly 
386-specific (agpgart, audio*, console, dsp*, initctl, midi*, mixer*, 
mpu*, pts, rmidi*, sequencer, shm, smpte*, sndstat, tty0; almost near 
the end of the process).


It does not create /dev/hd* (or /dev/sd*) nodes, though I'm pretty sure 
they *should* be created (all the instructions on the WWW say 
"debootstrap, then chroot", and don't mention having to manually create 
the /dev/hd* nodes; I'm actually following their leads, so I'm not sure 
where exactly I'm doing things differently.)


What next?
--

* Did I make any dumb mistakes,
* should I turn to a mailing list for advice (I didn't find a clueful 
one yet, pointers very much appreciated!), or

* is this a bug in debootstrap?

I'm willing to provide any logs or other information, or run additional 
tests as requests.
FWIW, a full transcript of the installation steps I took can be found at 
http://durchholz.org/jo/debian-install/Main/DebianRootServer . The steps 
relevant for my current problems can be found starting at 
http://durchholz.org/jo/debian-install/Main/AllocatePartitions#ConcretePartitionLayout


Regards,
Jo

--- End Message ---
--- Begin Message ---
With udev and debootstrap only creating a minimal /dev (#571136), I
don't think this bug is relevant any longer and should be closed.

Ansgar--- End Message ---

Processed: Re: Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

[Debian Bug Tracking System]

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

> tag 838388 + patch
Bug #838388 [debootstrap] debootstrap: Fails to strap squeeze since 1.0.83
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

[Ansgar Burchardt]

tag 838388 + patch
thanks

Ansgar Burchardt writes:
> Ah, I'm to blame for that.  [1] added `-k` to the options passed to tar
> in order to avoid replacing the new symlinks from / to /usr with real
> directories.  However it looks like tar returns an error when there are
> actual file conflicts (as opposed to just symlink vs. directory).
>
> Only adding -k for newer distributions (i.e. the ones that merged-/usr
> supports) should work around the problem.

I pushed a patch implementing this to my debootstrap repository[2].  It
worked for Squeeze (w/o merged-/usr) and Stretch (w/ merged-/usr).

Ansgar

  [2] 
https://github.com/aburch/debootstrap/commit/5bb1da69596828821fe43b3ee63f733e4b8672e7

Processed: tagging 838388

[Debian Bug Tracking System]

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

> tags 838388 + confirmed
Bug #838388 [debootstrap] debootstrap: Fails to strap squeeze since 1.0.83
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

[Ansgar Burchardt]

Stephan Sürken writes:
> On Di, 2016-09-20 at 21:09 +0200, Julien Cristau wrote:
>> > It always exits here with exit code 2, without any further error
>> > message (not even when using --verbose).
>> >
>> There should be a log inside the target directory.
>
> ah, sure ;).
>
> debootstrap/debootstrap.log says:
>
> ---
> gpgv: Signature made Sat Apr 25 13:01:30 2015 CEST
> gpgv:using RSA key AED4B06F473041FA
> gpgv: Good signature from "Debian Archive Automatic Signing Key (6.0/squeeze) 
> "
> gpgv: Signature made Sat Apr 25 13:05:42 2015 CEST
> gpgv:using RSA key 64481591B98321F9
> gpgv: Good signature from "Squeeze Stable Release Key 
> "
> tar: ./usr/share/man/man1/sh.1.gz: Cannot create symlink to 'dash.1.gz': File 
> exists
> tar: ./bin/sh: Cannot create symlink to 'dash': File exists
> tar: Exiting with failure status due to previous errors

Ah, I'm to blame for that.  [1] added `-k` to the options passed to tar
in order to avoid replacing the new symlinks from / to /usr with real
directories.  However it looks like tar returns an error when there are
actual file conflicts (as opposed to just symlink vs. directory).

Only adding -k for newer distributions (i.e. the ones that merged-/usr
supports) should work around the problem.

Just --keep-directory-symlink would of course be ideal, but I doubt it
is supported everywhere (being a long option to start with).

Ansgar

  [1] 
https://anonscm.debian.org/cgit/d-i/debootstrap.git/commit/?id=6b79352a205a96cee441ae0c6247c4616097a517

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

[Stephan Sürken]

Hi Julien,

On Di, 2016-09-20 at 21:09 +0200, Julien Cristau wrote:

(...)

> > It always exits here with exit code 2, without any further error
> > message (not even when using --verbose).
> > 
> There should be a log inside the target directory.

ah, sure ;).

debootstrap/debootstrap.log says:

---
gpgv: Signature made Sat Apr 25 13:01:30 2015 CEST
gpgv:using RSA key AED4B06F473041FA
gpgv: Good signature from "Debian Archive Automatic Signing Key (6.0/squeeze) 
"
gpgv: Signature made Sat Apr 25 13:05:42 2015 CEST
gpgv:using RSA key 64481591B98321F9
gpgv: Good signature from "Squeeze Stable Release Key 
"
tar: ./usr/share/man/man1/sh.1.gz: Cannot create symlink to 'dash.1.gz': File 
exists
tar: ./bin/sh: Cannot create symlink to 'dash': File exists
tar: Exiting with failure status due to previous errors
gpgv: Signature made Sat Apr 25 13:01:30 2015 CEST
gpgv:using RSA key AED4B06F473041FA
gpgv: Good signature from "Debian Archive Automatic Signing Key (6.0/squeeze) 
"
gpgv: Signature made Sat Apr 25 13:05:42 2015 CEST
gpgv:using RSA key 64481591B98321F9
gpgv: Good signature from "Squeeze Stable Release Key 
"
tar: ./lib/libacl.so.1.1.0: Cannot open: File exists
tar: ./usr/share/doc/libacl1/copyright: Cannot open: File exists
tar: ./usr/share/doc/libacl1/changelog.Debian.gz: Cannot open: File exists
tar: ./usr/share/doc/libacl1/changelog.gz: Cannot open: File exists
tar: ./lib/libacl.so.1: Cannot create symlink to 'libacl.so.1.1.0': File exists
tar: Exiting with failure status due to previous errors
---

Hth!

S

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

[Julien Cristau]

On Tue, Sep 20, 2016 at 19:00:20 +, Stephan Suerken wrote:

> Package: debootstrap
> Version: 1.0.83
> Severity: normal
> 
> Dear Maintainers,
> 
> since 1.0.83 (1.0.82 tested successfully), deboostrap fails to
> strap (at least) squeeze. For example:
> 
> ---
> sudo /usr/sbin/debootstrap --variant buildd --arch amd64 squeeze 
> ./squeeze-amd64-83 http://archive.debian.org/debian
> (...)
> I: Extracting bash...
> I: Extracting libbz2-1.0...
> I: Extracting coreutils...
> I: Extracting dash...
> ---
> 
> It always exits here with exit code 2, without any further error
> message (not even when using --verbose).
> 
There should be a log inside the target directory.

Cheers,
Julien

Bug#838388: debootstrap: Fails to strap squeeze since 1.0.83

[Stephan Suerken]

Package: debootstrap
Version: 1.0.83
Severity: normal

Dear Maintainers,

since 1.0.83 (1.0.82 tested successfully), deboostrap fails to
strap (at least) squeeze. For example:

---
sudo /usr/sbin/debootstrap --variant buildd --arch amd64 squeeze 
./squeeze-amd64-83 http://archive.debian.org/debian
(...)
I: Extracting bash...
I: Extracting libbz2-1.0...
I: Extracting coreutils...
I: Extracting dash...
---

It always exits here with exit code 2, without any further error
message (not even when using --verbose).

Hth!

S

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 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)

Versions of packages debootstrap depends on:
ii  wget  1.18-2+b1

Versions of packages debootstrap recommends:
ii  debian-archive-keyring  2014.3
ii  gnupg   2.1.15-3

debootstrap suggests no packages.

-- no debconf information

Save up to 50% on your email marketing

[Jeremy Small]

Are you getting a return from your email marketing platform

 Hi

My name is Jeremy Small and I am with FireDrum Email
Marketing, an email marketing company located in Scottsdale,
AZ. I visited your site today and it appears your company is
using WordPress as a website platform.

I wanted to reach out to see if you have any interest in a
brief conversation to see how our email marketing solution
can integrate with WordPress to help stay in front of your
customers and prospects. In fact,
we have a free WordPress plugin -
https://www.firedrummarketing.com/c.jsp?l=84lb5fs4s=43z4zf9neq
 that I would encourage you to use.

I would like to know if you are interested in discussing how
I can personally help increase your email marketing results.
As an email deliverability expert, I aim to not only reduce
your email marketing costs, but to also increase your
audience engagement, and ROI.

 Please see our
price comparison -
https://www.firedrummarketing.com/c.jsp?l=1jaxg0dus=43z4zf9neq
 and our complete feature set.

In addition to the savings, I believe that we can give you a
more personally managed service while offering an interface
with increased functionality. Please let me know what time
is best to talk and I will be happy to discuss some options
that may interest you.

If you are not the person who handles these matters, please
let me know who does, so I can introduce myself to them.

Thank you for your time and I look forward to speaking with
you soon.

 Jeremy

Jeremy Small

FireDrum Internet Marketing

Tel: 480.699.1524 | Fax: 480.699.1657

9903 E. Bell Rd. Suite 120

Scottsdale, AZ 85260


www.FireDrum.com -
https://www.firedrummarketing.com/c.jsp?l=5c6cl71ks=43z4zf9neq


https://www.firedrummarketing.com/c.jsp?l=2walllj2s=43z4zf9neq


https://www.firedrummarketing.com/c.jsp?l=351t0ohds=43z4zf9neq


https://www.firedrummarketing.com/c.jsp?l=e41wi3zks=43z4zf9neq


https://www.firedrummarketing.com/c.jsp?l=5vhdl359s=43z4zf9neq


If you would like to be removed from my contact list, please
reply back 'Stop' in the subject line


Unsubscribe -
https://www.firedrummarketing.com/c.jsp?l=5glnfa1is=43z4zf9neq

Bug#838345: installation-reports: Successful Reiser4 Jessie 4.7.0-1+reiser4.0.1-amd64_4.7.4-1 kernel on VirtualBox 5.1.6

[Jose R Rodriguez]

Package: installation-reports
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

Boot method: netboot image
Image version: https://sourceforge.net/projects/debian-reiser4/
Date: September 19, 20:35:31 PDT

Machine: VirtualBox 5.1.6
Partitions:
Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs 10240   0 10240   0% /dev
tmpfs  tmpfs   4105045916404588   2% /run
/dev/sda5  reiser49822436 3798668   6023768  39% /
tmpfs  tmpfs  10262601108   1025152   1% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs  1026260   0   1026260   0% /sys/fs/cgroup
/dev/sda1  ext2140805   55482 78053  42% /boot
tmpfs  tmpfs   205252   8205244   1% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

Smooth Reiser4-enabled Jessie Debian-Installer in non-expert mode.
elvis-tiny has been integrated into this d-i -- since I found nano awful;
I wish I had elvis-tiny available as I was intially working on Reiser4 hack.

SSL-enabled Busybox in d-i automatically downloaded Reiser4-patched Linux 
kernel 4.7.0-1
-- modified for Jessie's GCC 4.9 -- as well as reiser4progs 1.1.0-1.x built for 
Debian Jessie AMD64. 

d-i also fetches linux-base from backports to satisfy recent kernel 
requirements.
Overall flawless installation for a non expert.

Node: payinalcitlalli
http://www.enlightenment.org/ss/e-57e0df154a3995.47690147.jpg

(as usual Xonecuiltzin is d-i BusyBox environment.)
-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20160919-14:55"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux payinalcitlalli 4.7.0-1+reiser4.0.1-amd64 #1 SMP Debian 
4.7.4-1+reiser4.0.1 (2016-09-19) x86_64 Xonecuiltzin
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 
IDE [8086:7111] (rev 01)
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung 
GmbH VirtualBox Graphics Adapter [80ee:beef]
lspci -knn: 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM 
Gigabit Ethernet Controller [8086:100e] (rev 02)
lspci -knn: Subsystem: Intel Corporation Device [8086:001e]
lspci -knn: Kernel driver in use: e1000
lspci -knn: 00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH 
VirtualBox Guest Service [80ee:cafe]
lspci -knn: 00:05.0 Multimedia audio controller [0401]: Intel Corporation 
82801AA AC'97 Audio Controller [8086:2415] (rev 01)
lspci -knn: Subsystem: Dell Device [1028:0177]
lspci -knn: 00:06.0 USB controller [0c03]: Apple Inc. KeyLargo/Intrepid USB 
[106b:003f]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 00:07.0 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 08)
lspci -knn: 00:0d.0 SATA controller [0106]: Intel Corporation 82801HM/HEM 
(ICH8M/ICH8M-E) SATA Controller [AHCI mode] [8086:2829] (rev 02)
lspci -knn: Kernel driver in use: ahci
usb-list: 
usb-list: Bus 01 Device 01: OHCI PCI host controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.7.0-1+reiser4.0.1-amd64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 01 Device 02: USB Tablet [80ee:0021]
usb-list:Level 01 Parent 01 Port 00  Class