Quoting Philip Mu?kovac (yo...@gmx.net):
> Package: debian-installer
> Version: 20140316
> Severity: serious
> Tags: d-i patch
> Justification: fails to build from source (but built successfully in the past)
>
> The makefile currently uses -perm +0111 to find files which have to be be
> processed
Package: debian-installer
Version: 20140316
Severity: serious
Tags: d-i patch
Justification: fails to build from source (but built successfully in the past)
The makefile currently uses -perm +0111 to find files which have to be be
processed
by mklibs which is deprecated.
findutils 4.5 from experi
Package: cdebconf
Version: 0.191
Severity: wishlist
Hi,
Since 1.17.0, dpkg is trying to run the maintainer scripts in a
different context based on the file context and fallback on
"dpkg_script_t".
OTHO, a maintainer script run by dpkg-reconfigure is never transitioned
out of the "dpkg_t" context
On Wed, Jun 18, 2014 at 11:18:57AM +0100, Ian Campbell wrote:
> Do you therefore disagree with my analysis that there is no such thing
> as a >2TB MMC card and therefore no reason to use GPT on such a thing?
There probably isn't yet, but I suspect at some point there will be.
I am mainly complain
same stick but loaded not from iso
menuentry "Debian Testing (Squeeze, 8~x, 20140618) netinstall amd64" {
linux /boot/iso/debian-testing-amd64/linux vga=normal --
initrd /boot/iso/debian-testing-amd64/initrd.gz
}
worked fine. If you are keen on trying to recreate similar 'bo
On Tue 17 Jun 2014 at 08:17:21 -0700, Jack Bates wrote:
> In the Debian Installer Rescue mode, how do I mount an NTFS filesystem?
Boot with "priority=low" on the command line. When loading the installer
components select ntfs-modules. Skip ahead to "Detect disks".
mount -tntfs /dev/sdb1 /mnt
Package: installation-reports
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
See my thread here:http://forums.debian.net/viewtopic.php?f=17&t=115191
* What exactly did you do (or not do) that was eff
On Wed, 2014-06-18 at 11:49 +0200, gianluca wrote:
> On 06/18/2014 09:43 AM, Ian Campbell wrote:
> > One *really* ugly thing we could do is create a fake partition in
> > whichever entry happens to overlap the SPL entry point whose GUID etc
> > happen to look like a valid SPL + branch instruction t
On 06/18/2014 09:43 AM, Ian Campbell wrote:
One *really* ugly thing we could do is create a fake partition in
whichever entry happens to overlap the SPL entry point whose GUID etc
happen to look like a valid SPL + branch instruction to the full SPL at
a safer location. Really ugly, yukk...
Ugl
On Wed, 2014-06-18 at 08:43 +0100, Ian Campbell wrote:
> I suppose it is possible that something somewhere is wanting to zero the
> GPT even in msdos mode (as you say below, perhaps to wipe any remains of
> a GPT).
I think it is parted doing this in ped_disk_clobber which is called from
various bi
(seems like I didn't actually CC linux-sunxi when I said I would, oh
well, I may post a summary to that list later)
On Tue, 2014-06-17 at 19:44 +0200, Karsten Merker wrote:
> Unfortunately the problematic part in this case is the SPL which
> is the only part of u-boot that cannot be relocated bec
On 06/17/2014 04:43 PM, Lennart Sorensen wrote:
On Tue, Jun 17, 2014 at 10:20:38AM +0100, Ian Campbell wrote:
CCing the linux-sunxi group.
It sure would be nice if CPU makers would stop putting their boot code
where the GPT goes. Do none of them EVER think their device will want
to use a disk
12 matches
Mail list logo
