installed, or maybe that it's not wired up properly somehow.
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
to socket /run/user/107/at-spi/bus_0:
Permission denied
thunar-volman: Unsupported USB device type "usb-storage".
(thunar-volman:3458): dbind-WARNING **: 09:54:06.862: Couldn't connect to
accessibility bus: Failed to connect to socket /run/user/107/at-spi/bus_0:
Permission deni
The fault results in periodic wifi breakage and strange symtoms
with an older Debian release. With the bullseye installer, it causes
the installer environment to reliably hang (crashed with no response
even to capslock led).
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. I
Thanks for the patch. Unfortunately (due mostly to me flailing) my
tests of this are so far inconclusive. I will get back to this in
January.
Regards,
Ian.
Ian Jackson writes ("debian-installer multi-console race with preseeding"):
> A workaround is to specify *exactly one* appropriate console=
> on the kernel command line. This causes the kernel to report only
> that console in /proc/consoles and the bug is avoided.
This
I just experienced this bug. Thanks for some very useful hints and
pointers from Colin Watson.
This is particularly awkward to debug because one of the parallel
invocations of d-i is usually invisible. And the precise results are
the results of races and can be different from one run to another.
Ian Jackson writes ("Bug#792547: grub-installer: add option to _not_ install to
UEFI boot order"):
> I see that Ian C updated this patch (in July 2015) and reported
> testing it successfully. Is it now OK ?
every Debian release I update our workaround to apply to the current
rel
(sending this because I got the release team address wrong)
Ian Jackson writes ("That merged-usr is mandatory is RC"):
> Control: severity -1 serious
>
> In #923091, Guillem (with dpkg maintainer hat on) asks for a
> base-installer option to allow installing bus
ocial
cohesion.
CCing the TC FYI (they have already been involved in merged-usr
debates via #914897) and the release team, in case they have an
opinion. FAOD I am not a maintainer of base-files but AFAICT the
base-files maintainer has not expressed an opinion about severity.
Ian.
--
Ian Jackson
Init Diversity team
debian-init-divers...@chiark.greenend.org.uk
should be consulted so that the appropriate fixes can be developed.
Finally, this change is rather late wrt the freeze.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.o
nvolves doing serious violence to the upstream
build system, or perhaps horrific rules file bodges.
Thanks,
Ian.
[1] Implicitly, without using a chroot.
[2] IIRC some people suggested this explicitly in the thread in
d-devel.
--
Ian JacksonThese opinions are my own.
If I emailed y
tc or freenode, or email me here.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Julien Cristau writes ("Re: Bug#914897: debootstrap, buster: Please disabled
merged /usr by default"):
> On 11/28/18 2:49 PM, Ian Jackson wrote:
> > This is a special case of a general problem: buster systems with
> > merged-/usr sometimes build packages which are broken
g new lossage we can have a proper
conversation about what the plan ought to be for buster and bullseye.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
e
redirect me if I am wrong.)
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
it will be most
convenient to file a separate bug for that.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
ar bug. So I have CC'd it.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
on of various kinds, much of it
quite heated.
Thanks for your attention,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Package: debootstrap
Version: 1.0.67
I run an automated test system. Recently we had a test fail, because
an invocation of "xt-install-image" from the xen-tools package failed.
xt-install-image printed this:
Installation method: debootstrap
Running command 'xt-install-image --hostname=debian.g
Philip Hands writes ("Re: Bug#820818: partman is not able to resize nvme0n1p3
in d-i"):
> BTW I just pushed Ben's alternative suggetion to the
> pu/resize-nvme-820818-benh branch:
>
>
> https://anonscm.debian.org/cgit/d-i/partman-partitioning.git/commit/?h=pu/resize-nvme-820818-benh&id=62c6964
an
(take a backup of my laptop and) provide a test partition for it to
try to resize.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Ian Jackson writes ("partman is not able to resize nvme0n1p3 in d-i"):
> It failed, saying "Because of an unknown reason it is impossible to
> resize" etc. The log on VC4 says:
>
> Apr 12 18:00:03 partman: Error running 'tune2fs -l /dev/nvme0n1'
>
Package: partman-partitioning
(I'm afraid I don't know the right package name nor the version
number. I searched with a general web search for `reporting bugs
debian-installer' and `reporting bugs partman', and looked on
https://wiki.debian.org/DebianInstaller, and didn't find any
guidance.)
I a
Jordi Mallach writes ("Reverting to GNOME for jessie's default desktop"):
> It's been around 9 months since tasksel changed (for real) the default
> desktop for new installs. At the time of the change, it was mentioned
> the issue would be revisited before the freeze, around debconf time.
Fascinat
Gunnar Wolf writes ("Re: Reverting to GNOME for jessie's default desktop"):
> And yes, many such computers are currently in use. And it would be a
> disservice not to provide CDs anymore. But that criteria should not be
> what guides our default for installation; a CD might not be able to
> have th
Cyril Brulebois writes ("Re: Bug#602506: HP DL165 boot crash with lenny i386
686 but OK with -bigmem or amd64"):
> Either way, kernel selection was adjusted over the last release cycles,
> especially after kernel flavours were reduced to a bare minimum. I doubt
> this bug is still current, so clos
reopen 601363 =
thanks
Holger writes:
> thank you for submitting installation reports, much appreciated.
Thanks for your attention. But I'm afraid I think you may have made a
mistake with this particular bug. It wasn't an installation report.
It was a request for a specific change in the softw
Daniel Pocock writes ("SI units (was Re: failure to communicate)"):
> It may actually be useful for the technical committee to review what is
> on the wiki and make some general statement about Debian's position (if
> they haven't done so in the past), and that can guide the way similar
> bugs are
Josselin Mouette writes ("Re: CD1 without a network mirror isn't sufficient to
install a full desktop environment"):
> Le lundi 10 septembre 2012 à 20:08 +0200, Karsten Merker a écrit :
> > I am not going to repeat all the discussions about GNOME 3, but
> > at least from the impressions I have go
Ian Jackson writes ("Re: The current kernel doesn't support the Logical Volume
Manager. You may need to load the lvm-mod module."):
> This is all rather unfortunate. Perhaps we could update the package
> name of the module udebs when the kernel is updated, and arrange for
&g
Philipp Kern writes:
> Currently we only ship udebs on CD images, which in turn cannot sanely be PXE
> booted, AFAIK.
>
> I guess we can then conclude that keeping the old installer binaries doesn't
> actually help anybody. Not even keeping those of r0. We should keep the old
> sources around in
Philipp Kern writes ("Re: The current kernel doesn't support the Logical Volume
Manager. You may need to load the lvm-mod module."):
> On Tue, Jan 31, 2012 at 11:50:48PM +0300, George Shuklin wrote:
> > 2) We didn't download newer initrd/vmlinuz and using saved images to your
> > servers (some day
I have a setup at work which, amongst other things, regularly
autoinstalls Debian. Because I don't want it to break unexpectedly, I
prefer to keep using old installation kernels - for example, new
kernels may have different requirements for non-free firmware etc., so
I think it's not trivial to ju
Package: cdebconf-text-udeb
Version: 0.154
When running the squeeze installer via a serial console there should
be something in the prompt to tell you that you can go back; you
shouldn't have to read the help to know this.
The help is very long and "go back" is an important option.
Also I'm not
Package: cdebconf
Severity: wishlist
It would be nice if at a cdebconf text prompt, you could say ! to get
a subshell. This is particularly important in debian-installer; there
are situations where things have gone wrong and you get into loops in
the installer.
If you're on a serial (or Xen PV)
Olaf van der Spek writes ("Re: Bug#605009: serious performance regression with
ext4"):
> Probably not an issue for dpkg, but in general:
> Don't you reset meta-data that way?
Yes. If you want to keep the metadata you must copy it.
> Require a second file (name), permission to write to it and as
Olaf van der Spek writes ("Re: Bug#605009: serious performance regression with
ext4"):
> On Fri, Nov 26, 2010 at 10:52 PM, Ted Ts'o wrote:
> > I am guessing you are doing (a) today --- am I right? =C2=A0(c) or (d)
> > would be best.
>
> Are there any plans to provide an API for atomic (non-durab
Package: partman-base
Running the lenny i386 installer on an HP DL165, I get this warning:
Unable to determine geometry of file/device /dev/cciss/c0d0. You should not
use Parted unless you REALLY know what you're doing!
Warning!
1. Ignore [*]
2. Cancel
Prompt: '?' for help, default
Package: base-installer
On an HP DL165 (AMD-based) system, lenny i386 does not install,
although lenny amd64 works fine. The installer kernel boots properly
and runs normally; the installation runs to completion (although I
have to interactively ignore a couple of warnings about the cciss RAID
co
Package: debian-installer
I'm using the current lenny installer. I have a system with two
disks, one of which I want erased as part of installer partitioning
(and the other of which I will install later).
However, I see this:
!! ERROR: Unable to automatically remove LVM data
Because the vo
I wrote:
> * This happens every time I give it a disk which has the layout I
>described in my first report.
So I think the steps to reproduce are:
* Unpack the image to a hard disk (or file which is going to be your
test VM's virtual device).
* Set up a local web server containing a pr
Package: rescue-mode
Version: 1.24
Severity: wishlist
It would be nice to provide people with cfdisk in the rescue
environment. There's already a cfdisk-udeb.
14:40 ([cfdisk-udeb] isn't used by d-i, but you could make use of it
manually if you were desperate)
14:41 col: That would
I have discovered that:
* This happens every time I give it a disk which has the layout I
described in my first report.
* The presence of cciss block devices is a red herring; I have
reproduced the problem on a machine without them. Indeed
the hardware doesn't appear to matter.
* Wh
Package: debian-installer
Version: lenny
I've been trying to get a reliable fully automatic netboot install.
The default value of netcfg/dhcp_timeout is rather too short for this
kind of application so I decided to increase it to 150.
Experimentation shows that values of greater than around 60 ar
Package: rootskel
Version: 1.50
The default /root/.bashrc contains this line:
export PS1='\h:\w\$ '
That line isn't necessary because /etc/bash.bashrc does a similar but
better thing:
PS1='${debian_chroot:+($debian_chroot)[EMAIL PROTECTED]:\w\$ '
Indeed, the /root/.bashrc PS1 setting defeats a
45 matches
Mail list logo
