On Fri, 2015-05-15 at 04:58 +0200, Cyril Brulebois wrote:
> Control: tag -1 pending
>
> jnqnfe (2015-01-15):
> > Package: debootstrap
> > Severity: important
> > Tags: security patch
> >
> > In the event of a GPG keyring not being found, debootstrap may f
Control: reopen -1
Control: reassign -1 live-build
Control: retitle -1 live-build: non-live d-i not configured correctly
On Fri, 2015-02-27 at 22:26 +0100, Cyril Brulebois wrote:
> jnqnfe (2015-02-27):
> > Control: retitle -1 Sid d-i's are actually Jessie d-i's
>
> Th
Control: retitle -1 Sid d-i's are actually Jessie d-i's
On Fri, 2015-02-27 at 06:46 +0100, Cyril Brulebois wrote:
> jnqnfe (2015-02-26):
> > On Thu, 26 Feb 2015 22:07:00 +0100 Cyril Brulebois wrote:
> > > d-i installs a jessie system by default; if you want sid, you
On Thu, 26 Feb 2015 22:07:00 +0100 Cyril Brulebois wrote:
> Please use reportbug, so that debian-boot@ receives a mail that can be
> replied to (i.e. including the bug number) instead of mixing To: submit@
> && Cc: debian-boot@.
My apologies, it did not occur to me that the additional CC would ca
Package: debian-installer
I have a Debian live image based on Sid that I built a couple of weeks
ago. I opted to build a proper copy of the Debian installer into this
(not the default "live" installer). This installer is unmodified, just
copied from
/dists/sid/main/installer-amd64/current/images/c
Package: partman-lvm
Severity: important
Partitioning froze up during LVM creation in the following scenario.
Using a virtualbox VM I attempted an installation of Debian sid amd64.
For this I used the installer in a live CD I built with a dev copy of
live-build (I have been working on adding EFI
Just ftr, so people don't think I'm a total idiot, I'd read in several
places that there was no fsck for btrfs, so I was deliberately ignoring
the missing btrfs.fsck warning and assuming it had been installed.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "un
Control: close -1
Control: archive -1
As identified in bug #777578, btrfs-tools was not installed during the
installation, which was the real cause of the issues I was experiencing.
So on the assumption that a resolution to that issue would successfully
allow cryptsetup to be added to the initrd w
On 11/02/2015 18:42, Ben Hutchings wrote:
> So the root (no pun intended) of the problem is that btrfs-tools was
> not installed. Ben.
Ah ha, you're absolutely right, I assumed it was but it is indeed not
installed. Thanks for that.
Yep, now it boots successfully :D
--
To UNSUBSCRIBE, email
On 11/02/2015 05:05, Ben Hutchings wrote:
> On Wed, 2015-02-11 at 03:04 +0000, jnqnfe wrote:
>> I think that my issues might all stem from initramfs-tools, so
>> reassigning.
> I don't think so - other packages hook into initramfs-tools and are
> quite capable of br
control: reassign -1 initramfs-tools
control: retitle -1 initramfs-tools: fails to work with btrfs
control: severity -1 grave
I think that my issues might all stem from initramfs-tools, so reassigning.
Firstly, I cannot run update-initramfs within a chroot via a live CD against
this btrfs based
> So far, I have identified:
> 1) that the initrd of this install is lacking at least cryptsetup.
> 2) that an identical install, with the exception of using ext4 instead
> of btrfs, works perfectly fine (at least in terms of booting, I have not
> checked issue #3 from the mailing list discussion).
I have tried to do an identical install using (graphical) expert mode
this time, leaving initrd on 'generic'. This results in the same problem:
[0.00 ] tsc: Fast TSC calibration failed
Loading, please wait...
Gave up waiting for root device. Common problems:
ALERT! /dev/mapper/sda3_crypt
Package: debian-installer
Severity: important
As already described in the users mailing list [1], I have a Debian sid
amd64 install in a VM, using EFI, GPT, btrfs and luks, which after
installation is left broken.
So far, I have identified:
1) that the initrd of this install is lacking at least c
Updated patch, forgot to update the changelog.
commit 19b474c6ba60314bc8a0dcfb7dfdcb328ad14310
Author: jnqnfe
Date: Fri Jan 30 19:19:47 2015 +
Implement use of grub gfxpayload setting instead of 'vga=' param
diff --git a/build/config/amd64.cfg b/build/config/amd64.cfg
ind
24x768 being the default. Unless
you're happy with the blurry image, either the default needs switching
down to 800x600 in this patch, or the image needs replacing with a
higher res copy.
commit 364b428be604a25064f90bb9146c62e962b2c8c5
Author: jnqnfe
Date: Fri Jan 30 04:04:41 2015 +
I
Control: retitle -1 Use of depreciated graphics param with grub2
To reclarify the problem, now that I have investigated and solved it in
live-build: I noticed a message from grub2 about VGA=788 being a
depreciated graphics param, and being relatively new to linux I
mistakenly thought this was a ke
Package: debian-cd
When an official Debian disc image is loaded on a system with EFI, the
bootloader is displayed at at size of 800x600, larger than that used on
BIOS systems (640x480). The disc images include a bootloader splash
image (found in the syslinux directory) which has dimensions of 640x
iles being redownloaded after correcting the mistake (if the existing
copies aren't reused, I haven't yet read enough of the code carefully to
know at this point, nor have I run the code - been too busy to have time).
commit b066af054dad924641bd0cfa4dfd669a9db28bc5
Author: jnqnfe
Date:
file to be used, which only has an
effect if the user has not explicitly specified via a parameter a file
to use, and then only if the default does not exist. I still stand by my
patch being worth implementing though.
commit 8a6f178930c79b6b5beb505dfb811908b606c16c
Author: jnqnfe
Date: Fri Jan 16
Additional patch attached to update the manpages with regard to the new
param introduced in the previously supplied patch.
commit 30a65d578daecbc58fe8159572d7c0da9af2ecee
Author: jnqnfe
Date: Fri Jan 16 04:49:43 2015 +
Update manpage with new --sha-size parameter
diff --git a
those
already in place, applogies for that, I have a lot of work to do.
commit f2283fe99cac2f103d71cd4e5bab2757829d58f0
Author: jnqnfe
Date: Thu Jan 15 20:27:47 2015 +
Add new --no-https-fallback param
Allows the user to prevents falling back to a default https mirror in the
event
Ok, if that's the general feeling on grub legacy now (I'm relatively new
to the Linux world), and recognising your status in the Debian community
(thus respecting highly your opinion on this matter), I will ignore
supporting it further and push for removal from live-build. Thanks.
On 15/01/2015 12
'sha binary
unavailable warning' with an error.
- Removes the sha1 fallback, requiring users to explicitly specify
--sha-size=1 if they need sha1sum to be used.
commit cce61c7c3d89293506817df0dd6ee646b8d8092e
Author: jnqnfe
Date: Thu Jan 15 19:38:44 2015 +
Provide sha size par
Package: debootstrap
Tags: security patch
Patch attached to output warning if falling back to sha1.
commit 0911f1a8ba757a013e4c97e017634eb0ab746997
Author: jnqnfe
Date: Thu Jan 15 19:22:17 2015 +
Issue warning if having to fall back to sha1
diff --git a/debootstrap b/debootstrap
Updated 1.0.67 based patch attached.
I am not currently particularly familiar with the debootstrap codebase,
however this certainly seems like a condition that should result in an
error to me.
commit 8e084dc9b0c6d6ee02668e3581e55bbe3047a4d1
Author: jnqnfe
Date: Thu Jan 15 18:05:20 2015 +
I am having some graphics issues using grub-legacy, and I'm struggling
to find an answer.
I am currently working on fixing various bootloader issues with Debian
live images generated by the live-build tool (the full list of which can
be found in bug #775322 if you're interested). Today I have mana
Package: debian-installer
Grub2 (efi) and syslinux config bootloader menu entries are using
depreciated video graphics kernel parameters. At least this is the case
with a Debian 7.7 install image I have to hand, I am unaware if this has
been fixed in more recent versions of d-i, though I did brief
Package: win32-loader
Version: 0.7.7
Severity: important
Running win32-loader on an up-to-date Windows 8.1 install results in a
not supported dialog. Creating this bug report as a reminder that
support for newer editions of Windows is needed.
Exact dialog message:
"This program doesn't support Wi
as worth adding additional
sizes to cover hi-dpi on Windows. I'll consider your list though, and of
course once the svg icon has been created, any desired sizes can be
easily created from that.
On 17/12/2014 07:26, Didier 'OdyX' Raboud wrote:
> Le mercredi, 10 décembre 2014, 05.56:22
Sorry, I don't mean to create a load of unecessary noise on the list
over something as trivial as an icon, but I noticed that I messed up one
of them (darkgrey-white-grad). Fixed copy attached. Also added red variant.
logos.tar.bz2
Description: Binary data
In relation to bug #772691 (autorun.inf not displaying a custom Debian
icon from setup.exe aka win32-loader.exe when a Debian install disc/iso
is loaded in a Windows environment, unlike Ubuntu) which I just
reported, I created a small collection of possible replacement icons for
win32-loader.exe (s
32 matches
Mail list logo
