Please force migration of wireless-tools to testing.
We need to do another upload of debian-installer to fix an issue with
syslinux menus on x86, but it FTBFS on amd64 because:
The following packages have unmet dependencies:
netcfg: Depends: libiw30-udeb (>= 30~pre1) but it is not installab
On Thursday 24 December 2009, Frans Pop wrote:
> I've already committed a proper fix in D-I for this a bit earlier [2]
> and therefore reverted this nonsense. After testing if my fix is correct
> I'll also upload D-I again as otherwise 'alpha1' images would also be
> broken.
The last CD build fail
On Thursday 24 December 2009, Stephen Powell wrote:
> Do you want me to use the production (Lenny) installer? Or do you want
> me to use the "daily build" from Squeeze to do the installs?
The Squeeze installer would be best as that has up-to-date kernel and
libparted. Unfortunately the "official
Just for grins, I thought I'd give you the full mapping of the CMS volume label.
This is in s390 assembler language format:
ADTIDENT DSCL4LABEL IDENTIFIER ("CMS1")
ADTIDDSCL6VOLUME IDENTIFIER (VOLSER)
ADTVER DSCL2VERSION LEVEL
ADTDBSIZ DSF
On Thursday 24 December 2009, Frans Pop wrote:
> > I would
> > really *really* like to see d-i properly integrated into the archive
> > and uploaded periodically so it can migrate to testing, as we've
> > discussed in the past many times. The current situation is a train
> > wreck.
And you simply
On Thu, Dec 24, 2009 at 09:33:03PM +0100, Frans Pop wrote:
>From farbror (CD build server):
>
>--- tools/boot/squeeze/boot-x86 (revision 1964)
>+++ tools/boot/squeeze/boot-x86 (working copy)
>@@ -230,7 +230,8 @@
>boot$N/isolinux/win32-loader.ini boot$N/
>fi
>
>-
On 2009-12-24 at 14:34:26 -0500, Frans Pop wrote:
> I would really like to know *exactly* what devices exist in Debian
> Installer when you get to the partman stage. The /var/log/partman log file
> as it is at the point after partman has initialized itself would also be
> useful.
>
> I guess yo
On Thursday 24 December 2009, you wrote:
> I saw that the graphical images weren't available any more so I
> disabled them.
Problem is that you did not disable them. You only silently ignored a
failure, with the result that you were creating broken images. If I had
not accidentally caught that n
From farbror (CD build server):
--- tools/boot/squeeze/boot-x86 (revision 1964)
+++ tools/boot/squeeze/boot-x86 (working copy)
@@ -230,7 +230,8 @@
boot$N/isolinux/win32-loader.ini boot$N/
fi
- if [ -e boot$N/isolinux/f3.txt.withgtk ]; then
+
+ if [ 0 =
On Thursday 24 December 2009, Stephen Powell wrote:
> On 2009-12-24 at 10:56:59 -0500, Frans Pop wrote:
> > To start with:
> > - What device name does such a partition have?
> > - How could it be distinguished from a partitionable dasd?
>
> The definitive documentation for this is in
> "Device Driv
On 2009-12-24 at 10:56:59 -0500, Frans Pop wrote:
> Please send the replies for these questions to the BR instead of the list!
Replying to the bug report, per your request.
On 2009-12-24 at 10:56:59 -0500, Frans Pop wrote:
> If you can provide me with *exact* info I need and if you can reply
> q
On 2009-12-24 at 12:32:18 -0500, Frans Pop wrote:
> The output of the following command would be useful as well:
> # parted /dev/ print
bash: parted: command not found
Of course, I wasn't running D-I at the time, I was running the
installed system. Do I have to run D-I? Or is there a package
th
DDDmeds.net
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RRmeds.net
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
As all packages needed to build D-I were now available, I have uploaded for
both stable and oldstable. An accept is not needed; apparently D-I gets an
automatic accept due to by-hand processing of the image tarballs.
For oldstable (20070308etch6) all arches have been built successfully.
For sta
On Thursday 24 December 2009, Frans Pop wrote:
> So the error is probably the result of anna trying to install the same
> package twice.
The exit code of anna was 8, which matches an error during unpack or
configure.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subj
Package: anna
Severity: serious
Yesterday I uploaded some packages, including base-installer and hw-detect.
Today during a test install from a local build this resulted in:
Failed to load installer component
loading base-installer failed for unknown reasons. Aborting.
I tried to reproduce it again, no chance; got experience and do not do
without thinking now.
Regards your questions
> Did you actually get the error "failed to determine the codename for this
release"
Yes, I got this error.
> Did you perhaps use expert mode and select "choose-mirror" as an
opti
Source: cdebconf-entropy
Version: 0.12
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091213 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> gcc -Wall -g -O2 -I. -fPIC -o text-plu
19 matches
Mail list logo
