Your message dated Fri, 21 Nov 2014 21:08:05 +0100
with message-id <87r3wwe2qi....@deep-thought.43-1.org>
and subject line Re: Bug#769303: reverse override: aptitude:admin/standard 
aptitude-common:admin/standard
has caused the Debian Bug report #769303,
regarding reverse override: aptitude:admin/standard 
aptitude-common:admin/standard
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.)


-- 
769303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: ftp.debian.org
severity: serious
X-Debbugs-Cc: aptit...@packages.debian.org

hello.

it appears that downgrading the priority of aptitude and friends from
important to to standard, we have caused this bug to resurface:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681347

[i tried stating that this problem happened again in the bug that was
created to demote aptitude and aptitude-common from important to standard, 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758561 , but the bug
was archived with no resolution]

in testing and unstable, debian-installer installations can no longer
complete, because they hang at the "select and install" screen.  this
can be observed in /var/log/syslog:

Sep 19 15:43:13 main-menu[4024]: INFO: Menu item 'pkgsel' selected
Sep 19 15:43:15 pkgsel: checking for (security) updates to the base
system
Sep 19 15:43:16 in-target: Can't exec "aptitude": No such file or
directory at /usr/bin/debconf-apt-progress line 130, <STDIN> line 2.
Sep 19 15:43:16 in-target: Use of uninitialized value in vec
at /usr/bin/debconf-apt-progress line 274, <STDIN> line 2.
Sep 19 15:43:16 in-target: Use of uninitialized value in vec
at /usr/bin/debconf-apt-progress line 275, <STDIN> line 2.

because aptitude is no longer "important", it wasn't installed
into /target, and the screen's progress updates failed, hanging the
install.

debconf-apt-progress either needs to be switched to apt-get, to relieve
the aptitude dependency, or aptitude needs to be marked as important
again.

this problem has existed for at least two months.

david

--- End Message ---
--- Begin Message ---
Hi,

Default Identity <n...@photongenic.net> writes:
> to keep from running into kernel module issues and things of the like,
> the installers that i use [with a preseed that's dynamically generated
> per release, per machine] are sourced from
> dists/stable/main/installer-${arch}/current/images/netboot/debian-installer/${arch}/
> , which i use to stand up VMs in xen [also specifying
> mirror/suite=${suite} as desired on the kernel cmdline].
>
> with that change that was made in august [bug #758561], the stable
> debian-installer image still expects aptitude to be present in /target,
> but i'm guessing the dependency resolution doesn't bring it in [because
> it's no longer essential], so the install falls on its face in the
> stated way.
>
> the summary appears to be, due to the change made in august, stable
> install media can no longer be used to install testing or unstable.

I don't think using the stable installer to install anything but stable
is supported. It might work, but it might just break too (thus closing
this bug).

The recommended way to install a testing/unstable system is to install
stable and upgrade as far as I know.

Ansgar

--- End Message ---

Reply via email to