On Tuesday 06 December 2005 05:23, Jurij Smakov wrote:
It's not kernel's fault. I have just booted the 2.6.14 off today's
sid_d-i daily netinst, and it has the bug. The bug appears because the
af_unix_init function is invoked twice, and it normally should not
happen. This function is the init
Package: gtk+2.0-directfb
Version: 2.0.9.2-12
Severity: serious
Justification: FTBFS
The package fails to build on these two architectures with the same error:
gdkpango.c: In function 'gdk_draw_layout_line_with_colors':
gdkpango.c:307: warning: enumeration value 'PANGO_UNDERLINE_ERROR' not
Package: parted
Version: 1.6.25.1-1
Severity: serious
Justification: FTBFS
The package fails to build on these two architectures with the same error:
../../../libparted/fs_hfs/advfs.c: In function 'hfs_read_bad_blocks':
../../../libparted/fs_hfs/advfs.c:241: internal compiler error: Floating
Thiemo Seufer replied to #342028 (similar error for gtk+2.0-directfb):
From the symptom I expect this to be fixed in gcc-4.0 4.0.2-4.
Possibly this is valid for parted too.
I understand that rebuilds are already being scheduled.
[23:12:11] fjp ths: So, just ask buildd admins to schedule a
found 339711 2.0pl5-19.3
thanks
Sam, thanks for working on this.
I'm afraid the NMU has not fixed the problem on sparc though.
[EMAIL PROTECTED]:~$ dpkg -l dhcp-client
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/
On Saturday 03 December 2005 15:49, Frans Pop wrote:
Sam, thanks for working on this.
I'm afraid the NMU has not fixed the problem on sparc though.
I've found the cause. One patch had an extention .diff instead of
.patch and because of that was not applied.
I've uploaded (NMU) a new version
close 341878 1.22
thanks
Bug arrived after fix had already been uploaded, therefore closing this
way.
On Saturday 03 December 2005 21:03, Joey Hess wrote:
Daily build install is failing like this on alpha, and I think on sparc
as well:
No, it does not affect Sparc. Problem was that in some
Package: linux-2.6
Version: 2.6.14-4
Severity: serious
The following error happens on Debian Installer boot in vmware (386 kernel).
This problem was not present in -3.
The system does come up after the error, but it looks so basic (memory
management AFAICT) that I've set RC severity anyway.
Feel
the output of 'dmesg' and contents (using nano) of /var/log/syslog)?
Thanks.
Frans Pop
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
regarding this [2], but I'm not sure that also applies for Debian.
Cheers,
Frans Pop
[1] http://bugs.debian.org/340935
[2] https://wiki.ubuntu.com/NetworkMagic
pgp1MQ11QL9G9.pgp
Description: PGP signature
Package: netcfg
Version: 1.17
Severity: serious
Justification: Makes package unsuitable for release
Now that udev is enabled in d-i for kernel 2.6.14, regular interfaces get
recognized as being hotpluggable.
However, as udev no longer uses hotplug, the current configuration set up
by netcfg no
On Saturday 19 November 2005 05:05, Steve Langasek wrote:
What's holding up the switch to dhcp3-client-udeb? Andrew Pollock did
a lot of work earlier this year to get it ready for d-i use. Is there
still something missing, or is it just a question of trying it out?
The only issue AFAIK is
On Saturday 19 November 2005 10:41, Steve Langasek wrote:
Do we actually have reason to believe that this is a memory leak, i.e.,
leaving the daemon running will continue to eat more memory? If the
program simply needs 70-some MB to run, that's unfortunate, but not RC;
if, OTOH, its memory
On Saturday 19 November 2005 15:15, Steve Langasek wrote:
Granted, though it seems that at least two of the architectures you
quoted don't support floppy installs in etch? :)
Sparc does but they are not part of official release as building them
requires root.
pgpRx89JdeMb9.pgp
Description:
I'm seeing the same problem on my Sparc Ultra10. Switching to dhcp3-client
solved the issue.
Removal of the package might not be such a good idea as Debian-Installer
uses the dhcp-client-udeb. I've not yet checked if the udeb has the same
problems on sparc.
pgpj9M3nFzGdl.pgp
Description: PGP
tag 337382 pending
thanks
On Friday 04 November 2005 09:48, Daniel Schepler wrote:
Tracing this by adding a set -x to the command line, it appears this
is being caused by s390 expanding to an ARCH_FULL of S/390.
Correct. This is already fixed in the rules file by changing the
separators for
severity 337382 important
thanks
Downgrading this issue. As the installation-guide is arch all, it does not
need to be build on the buildd's and is therefore less critical. It
should at least not block the current version from moving to testing.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Package: libgtk+2.0-directfb-dev
Version: 2.0.9.2-10
Followup-For: Bug #337248
As this package supplies .pc files, it should depend on pkg-config
(libgtk2.0-dev does the same).
No real hurry to add this as this is currently taken care of for
cdebconf-gtk by its dependency on libgtk2.0-dev.
--
severity 335950 normal
reassign 335950 installation-reports
thanks
On Thursday 27 October 2005 00:32, Kenneth Gessner wrote:
Severity: critical
Justification: breaks the whole system
Again the severity is inflated. How can it break the system if there is no
system installed?
cannot install
On Monday 24 October 2005 17:46, Faidon Liambotis wrote:
Moreover, I highly doubt that memory leak bugs are justified as
severity critical.
For regular applications I would agree. For an application that runs as a
daemon and is likely to run permanently on a server, I think an RC
severity is
Package: tetex-bin
Version: 3.0-9
Followup-For: Bug #334613
I've seen the same problem, with the following extra note.
Setting up tetex-bin was retried automatically, and that time
succeeded. After that tetex-extra could be set up and it appears
that the total installation was successful.
Package: ctrlproxy
Version: 2.6.2-1
Severity: critical
Justification: breaks unrelated software
After running ctrlproxy for a fairly long time as daemon:
Mem: 30180 29248932 0 1336 5596
-/+ buffers/cache: 22316 7864
Swap:60440
On Tuesday 11 October 2005 13:17, Gaudenz Steinlin wrote:
Please try the attached patch and see if the generated binary works.
Compiles and runs fine on my Ultra 10.
Output of old and new versions attached.
Cheers,
FJP
Reading PCI hardware database...
Reading PCI hardware database...
Reading
On Monday 26 September 2005 17:11, Lennart Sorensen wrote:
My raid install of sarge used grub. Why ever would you want it to use
lilo?
No idea. Just noticed in installation reports that quite a few users
prefer lilo over grub.
Or does grub behave that differently on amd64 that it can't
On Sunday 25 September 2005 09:40, Petter Reinholdtsen wrote:
Why the serious severity? lilo is not the default boot loader, so
this only affect expert installs.
Because LILO is the default installer in some cases (/ on XFS IIRC) and is
also ofter prefered by users for RAID installs.
Also, it
Package: base-installer
Version: 1.24
Severity: serious
In commit r29833 the value of link_in_boot was changed from false to true
for i386 and amd64. This change make lilo-installer fail as lilo.conf is
configured to expect symlinks for the kernel and initrd in / (if boot is
not a separate
Package: partconf
Version: 1.10
Severity: grave
Tags: d-i
During installation for s/390, partconf no longer recognizes partitions on
a dasd. This is probably due to recompilation against libparted 1.6.24.
pgpmSfYq3oxbn.pgp
Description: PGP signature
On Wednesday 07 September 2005 23:21, you wrote:
It would be extremely helpful if you could find a way to reproduce
this that does not require root... any ideas?
Well, I think the problem can also be reproduced outside a
debian-installer environment (getting linux-image-2.6.12-1-386 (2.6.12-2)
(pruning CC list; AFAIK all will still get the message this way)
On Tuesday 30 August 2005 04:56, Steve Langasek wrote:
So we're going to have another release with a very elaborate upgrade
procedure in the release notes (which a lot of users, especially
desktop users, don't read anyway)?
On Monday 29 August 2005 11:06, Sven Luther wrote:
* reboot
* upgrade udev
This is definitively not a user-friendly procedure.
In effect this means that any user having udev installed will have to put
udev on hold. Because of versioned dependencies on udev, this will
probably make a lot
On Monday 29 August 2005 12:35, Marco d'Itri wrote:
On Aug 29, Frans Pop [EMAIL PROTECTED] wrote:
In effect this means that any user having udev installed will have to
put udev on hold.
No, if the kernel has not been upgraded yet then preinst will fail.
Hmm. Won't that fail the whole dist
On Sunday 21 August 2005 03:56, Horms wrote:
I've put the following in SVN, so this
should be resolved in the next release.
I noticed on IRC that you put a closes: #322723 in the changelog.
I'm wondering if that is correct as I would say there still is a bad bug
in gcc-4.0 causing the kernel
On Friday 19 August 2005 21:01, Bastian Blank wrote:
- the problem is not there in the 686 image.
On request from waldi, I've compiled a -386 kernel (using gcc-4.0) with
one change in ./debian/arch/i386/config.386:
- CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+ # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
The
On Tuesday 16 August 2005 19:35, Andres Salomon wrote:
Regarding this problem with iproute:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282492
Would it be possible to include a fix for this, or at least make
CONFIG_ATM_CLIP a module instead of a yes in the stock kernel?
I'm
reassign 322723 linux-2.6
retitle 322723 D-I: 'id route add' fails w/ Network is unreachable
thanks
We have just tested this issue using an installer with the busybox version
from Sarge and the error shows up then as well.
We feel this makes the kernel the most likely source of the problem.
reopen 225693
retitle boot-floppies should never migrate to testing
thanks
Oops. boot-floppies is the source package and that still _is_ in unstable.
There is also a bug in the BTS website which led me astray here...
pgp38HKiKvP0O.pgp
Description: PGP signature
Package: dhcp-client-udeb
Version: 2.0pl5-19.1
Severity: serious
Tags: d-i
Installations for 1386 using current daily builds (using 2.6.12) are
failing with a screen saying no default route could be set.
The cause for this is that in /etc/dhclient the 'ip route add' command is
failing. It
severity 320784 normal
thanks
Daily images can be broken sometimes (like the images dated 31-07-2005)...
On Monday 01 August 2005 14:29, Torok Edwin wrote:
Debian-installer-version:
http://cdimage.debian.org/pub/cdimage-testing/etch_d-i/i386/20050709/de
bian-testing-i386-netinst.iso uname
On Tuesday 26 July 2005 19:27, Stefan Esterer wrote:
After i choose the Sarge install in grub the kernel stops after some
time with :
modprobe: FATAL: Error inserting pciehp
(/lib/modules/2.6.8-2-686/kernel/drivers/pci/hotplug/shpchp.ko):
Operation not permitted
shpchp: can't be loaded
Hi Jurij,
Could you take a look at this bug (as you submitted the original patch and
this could be kernel headers related...).
Cheers,
FJP
On Wednesday 20 July 2005 09:26, Blars Blarson wrote:
discover1 failed to build on a sparc buildd, duplicated on my sparc
pbuilder:
[11:30:24] pere any
on an extremely course basis.
Cheers,
Frans Pop
Here are the headers for the original message:
Return-path: [EMAIL PROTECTED]
Received: from [195.240.184.66] (helo=localhost)
by smtp-out1.tiscali.nl with esmtp (Tiscali http://www.tiscali.nl)
id 1Dua9c-0002lD-DD
for [EMAIL
Package: xsupplicant
Version: 1.0.1-4
Severity: grave
Tags: security
Justification: user security hole
When xsupplicant is started on boot, my wireless card is not up.
In that situation, xsupplicant happily dumps configuration settings,
including username/password settings, to
I've tried to trace the last remaining error.
As far as I can tell, this problem is not in debootstrap, so it would have
to be in d-i's run-debootstrap.
I have done an install with extra debugging statements around the last
statements in debootstrap (see deboot.debug), but even with an explicit
Package: debootstrap-udeb
Version: 0.3.1
Severity: grave
Two errors in functions breaking new installations have been confirmed
testing debootstrap udeb in sid during an emulated S/390 installation.
The following 2 changes will fix them.
===
local totaldebs=0
- local leftoverdebs=$*
+
(Sending this from work, so sorry for breaking thread and I have now idea
how formatting will turn out...)
-if [ ! -e /dev/.devfsd ] [ ! -e /dev/md0 ] ; then
+if [ ! -e /dev/md0 ] ; then
I wonder if this change is correct for a udev fix.
IIRC -e /dev/.devfsd checks for _devfsd_, not udev.
Package: docbook-xsl
Version: 1.68.1-0.1
Severity: grave
Justification: renders package unusable
Although the issue in itself is probably not extremely important, I stll
think it is RC because it is an regression for which other packages
(probably xsltproc) need to be fixed, for which there is
On Sunday 24 April 2005 18:39, Frans Pop wrote:
I have built the package for s390, but can not upload myself (still
waiting for DAM approval).
Joey Hess has just done the upload, so it's now complete for all archs.
Cheers,
FJP
pgpTbZXTxLxQd.pgp
Description: PGP signature
Urgency: low
Maintainer: Frans Pop [EMAIL PROTECTED]
Changed-By: Gopal Narayanan [EMAIL PROTECTED]
Description:
pgplot5- large subroutine library for plotting scientific data
Closes: 146077 248551
Changes:
pgplot5 (5.2.2-6) unstable; urgency=low
.
* Removed PIC compilation for static library
Package: cgiemail
Version: 1.6-24
Severity: serious
Justification: Policy 10.7.3
cgiemail does not delete its configuration file /etc/cgiemail.conf when
the package is purged.
Should this file maybe be made into a conffile?
-- System Information:
Debian Release: 3.1
APT prefers testing
APT
it to you what to do with this bug report.
IMO both errors I reported are still there, but as it is after all
relatively easy to recover from the resulting inconsistency (once you
know how), you may want to downgrade to important.
Thanks again,
Frans Pop
--
To UNSUBSCRIBE, email to [EMAIL
Package: lvm2
Version: 2.0.0.24-1
Severity: critical
Justification: Can break whole system
During a reorganization of my LVs, I did a lvremove that in itself
produced no errors. However, the next lvremove failed with messages that
devices (?) had been 'left open' and metadata for the VG that
and as I can not access
my sys-root LV, I can not get to the backups.
Or is there some kind of trick to that?
I've also attached the output for 'lvdisplay lvdisplay.txt 21'.
Note the 'Device ??? has been left open' lines in that output.
Cheers,
Frans Pop
Volume group sys inconsistent
Device
severity 292366 normal
thanks
On Wednesday 26 January 2005 17:20, Sergio Rua wrote:
On the first reboot, it enters on the menu where you will set up the
root password and some other configs. But I was unable to do anything
here as the server entered on a loop with the error Incorrect charset
I've also been having crashes using kbabel in Sarge (see #289646). I've
had crashes with several po files now.
The behavior is somewhat eratic: when I first had the crash, I could
always reproduce it, now I find that sometimes the crash does not happen.
Very likely my crashes are related to
501 - 554 of 554 matches
Mail list logo
