[Bug 207393] sysutils/debootstrap: update to 1.0.79

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Feb 21 14:49:57 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207393

            Bug ID: 207393
           Summary: sysutils/debootstrap: update to 1.0.79
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: lifanov at mail.lifanov.com

Created attachment 167258
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=167258&action=edit
sysutils/debootstrap: 1.0.78 -> 1.0.79

Please update sysutils/debootstrap to 1.0.79. Changes:

debootstrap (1.0.79) unstable; urgency=medium

  [ Samuel Thibault ]
  * hurd: move setting up dev and servers firmlink to setup_proc stage. Also
    firmlink proc there.  Thanks Gabriele Giacone for all the investigation!
    (Closes: #768102)
    (Closes: #768102)

 -- Christian Perrier <bubulle at debian.org>  Fri, 19 Feb 2016 07:23:59 +0100

debootstrap (1.0.78+nmu1) unstable; urgency=medium

  * Non-maintainer upload.
  * Split setup_devices in setup_devices (which now only deals with static
    device nodes) and setup_dynamic_devices, and move the calls to
    setup_devices from the beginning of the second stage to the end of the
    first stage.
    setup_dynamic_devices mounts the appropriate filesystems which provide
    dynamic device nodes for the architectures which need one in
    debootstrap (kfreebsd and hurd).
    This fixes a bug in --second-stage introduced in 1.0.34 and exposed
    by the devices-related changes of 1.0.76: the second stage debootstrap
    runs "dpkg --print-architecture >/dev/null" at the very beginning of
    the program when /dev is still empty, so it creates an empty regular
    file in place of /dev/null and this will cause mknod to fail later.
    (Closes: #813232)

 -- Marco d'Itri <md at linux.it>  Wed, 17 Feb 2016 01:23:23 +0100

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list