Dear devel friends,
Please, could one of you be so kind as to answer this post. it is a
problem for immense numbers of people who have new laptops and need to be
able to install debian with the 2.6 kernel, as we need our hardware
recognised, but must dual boot.
The 2.6 kernel uses physic
G E TY O U R U N I V E R S I T Y D I P L O M A
Do you want a prosperous future, increased earning power more money and the respect of
all?
Call this number: 1 775 490 9881 (24 hours)
There are no required tests, classes, books, or interviews!
Get a Bachelors, Masters, MBA, GED
Package: debian-installer
Version: 20040528
Severity: important
Tags: patch
Justification: fails to build from source
Hi,
debian-installer FTBFS because the kernel has been updated a few times
and input-modules are now compiled in. Patch attached.
MfG
Goswin
-- System Information:
Debia
Package: netcfg
Version: 0.63
Severity: normal
Tags: d-i
I have seen two systems where I don't always get a default route after
dhcp succeeds:
1. My (probably misconfigured) vmware virtual machine. I never seem to
get a default route set up on this machine via dhcp. If I add one by
hand, it
I did an install of tc1 using a businesscard iso image and a usb
keychain, and also saw this problem there. So this can't be the new
languagechooser, and it affects tc1 also.
This system has the following in /etc/console-tools/config:
SCREEN_FONT=lat0-sun16
SCREEN_FONT_MAP=iso15
--
see shy jo
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 252930 still PATH problems in shell menu item
Bug#252930: Installation-Reports: Beta 4 as a VMware Guest
Changed Bug title.
> reassign 252930 base-config
Bug#252930: still
yazdzik wrote:
> The 2.6 kernel uses physical geometry readings, which makes dual booting
> impossible after using the sarge installer, and this particular problem is
> an issue with all distros based upon 2.6, thus being reported everywhere.
>The "workaround" for fc2 is to use the install
Geert Stappers wrote:
> I had a closer look at /var/log/messages and found:
>
> Setting up console-data (2002.12.04dbs-40) ...
> Bareword "previous_module" not allowed while "strict subs" in use at
> /var/lib/dpkg/info/console-data.config line 1045.
> Execution of /var/lib/dpkg/info/console-data.
This is regarding a report that dpkg failed to run as /sbin and
/usr/sbin were not in PATH. I've received a log from the bug submitter
that shows that he was using base-config's shell menu item, and running
apt by hand. I had tried to fix this problem with root's PATH in
base-config, but by fix did
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 253536 normal
Bug#253536: debian-installer: Amd64 kernel updates
Severity set to `normal'.
>
End of message, stopping processing here.
Please contact me if you need assis
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 253536 pending
Bug#253536: debian-installer: Amd64 kernel updates
Tags were: patch
Tags added: pending
>
End of message, stopping processing here.
Please contact me if you ne
Goswin von Brederlow wrote:
> Package: debian-installer
> Version: 20040528
> Severity: important
> Tags: patch
> Justification: fails to build from source
Please stop using important as a severity for amd64 packages until amd64
is an official arch or there is a consensus that it's the right
sever
Hi,
I've finally figured out the cause for this problem. To put it shortly
the problem is that, unlike the lat{0,2}-sun16 fonts, there is indeed no
box-drawing chars in iso0{1,2}.f16 fonts used in the related lines of
termwrap. We could consider the resulting appearance as a feature (ie.
di
Recai Oktas wrote:
> The fix is simple, just do a 's/iso01.f16/lat0-sun16/' in above line of
> termwrap (and perhaps repeat this substitute on all iso01.f16 fonts). I
> think this might be the urgent fix for an upcoming 'tc1'. But for
> future releases, I would like to learn the comments on so
Dear J,
I am honoured that you replied.
My bug report, 250051, described the inability to reboot into windows, but I
presumed, as would most newbies, it was my hardware configuration that was
somehow unusual.
The basic links describing the problem I had, and, now clearly, anyone would
have, usin
lilo-installer_0.46_i386.changes uploaded successfully to localhost
along with the files:
lilo-installer_0.46.dsc
lilo-installer_0.46.tar.gz
lilo-installer_0.46_i386.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscr
Your message dated Thu, 10 Jun 2004 00:02:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#252256: fixed in lilo-installer 0.46
has caused the attached Bug report 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 no
Accepted:
lilo-installer_0.46.dsc
to pool/main/l/lilo-installer/lilo-installer_0.46.dsc
lilo-installer_0.46.tar.gz
to pool/main/l/lilo-installer/lilo-installer_0.46.tar.gz
lilo-installer_0.46_i386.udeb
to pool/main/l/lilo-installer/lilo-installer_0.46_i386.udeb
Announcing to [EMAIL PROTECTED
Processing commands for [EMAIL PROTECTED]:
> reopen 252256
Bug#252256: installation-reports
Bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To
Your message dated Wed, 9 Jun 2004 21:31:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Bug#252256: marked as done (installation-reports)]
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Package: installation-reports
Debian-installer-version: 2004/06/10
http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/ia64/tc1/sarge-ia64-businesscard.iso
uname -a: Linux berry 2.4.25-itanium-smp #1 SMP Thu Mar 18 18:55:54 MST 2004 ia64
unknown
Date: 2004/06/10 14:45
Method: Network instal
Hi,
I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
images, debs and udebs from alioth including a fixed sid console-data.
I managed to install and boot a debian system from the cdrom with one
problem:
The init.d script of discover1 tries to rm /media/cdrom0/* which of
course
Processing commands for [EMAIL PROTECTED]:
> reassign 253211 base-config
Bug#253211: Problems with the screen display in second stage
Bug reassigned from package `installation-reports' to `base-config'.
> retitle 253211 No line box drawing characters in 2.4 installs for Latin languages
Bug#253211
Quoting Dennis Stampfer ([EMAIL PROTECTED]):
> > What about discover1_debian_po.po which I sent with the discover1_po.po?
> > Can you commit it?
>
> Yes, I commited it a few seconds ago. Now the debconf-translation and
> the program translation (already commited by Christian Perrier) are in
> SV
reassign 253211 base-config
retitle 253211 No line box drawing characters in 2.4 installs for Latin languages
thanks
Quoting Recai Oktas ([EMAIL PROTECTED]):
> (1) For all languages, use the proper fonts with the box drawing chars
> in everywhere (both in termwrap and console-tools/config), prov
Quoting Goswin von Brederlow ([EMAIL PROTECTED]):
> Hi,
>
> I have updated the sid-amd64-cdrom.iso on alioth to the latest D-I
> images, debs and udebs from alioth including a fixed sid console-data.
I suppose that testing it on an already installed machine is not
"dangerous" ? No risk of breakin
101 - 126 of 126 matches
Mail list logo
