Bug#465369: ITP: golearn -- Debian educational browser
Quoting Jonas Smedegaard ([EMAIL PROTECTED]): > Package: wnpp > Severity: wishlist > Owner: Jonas Smedegaard <[EMAIL PROTECTED]> > > * Package name: golearn > Version : 0.2 > Upstream Author : Enrico Zini <[EMAIL PROTECTED]> & Miriam Ruiz <[EMAIL > PROTECTED]> > * URL : http://packages.debian.org/goplay > * License : GPL-2+ > Programming Lang: C++ > Description : Debian educational browser I'm not sure whether this is really descriptive of what the program does. "educational packages search tool using debtags" would maybe better fit as the software browses across the archive to search for packages (right?). Of course it browses an archive (mroe precisely what's listed in sources.list) of Debian packages but indeed not necessarily *the* Debian archive. That will probably bring the debate about "branding" here (explicitely mention Debian) but I would at least support moving the mention of Debian to the long description. signature.asc Description: Digital signature
Bug#465233: dictionaries-common: debconf prompt without input value
I hit this bug, too, but only at the "Preconfiguring packages ..." stage, with "dpkg-reconfigure dictionaries-common" it works fine. [UPGRADE] dictionaries-common 0.90.1 -> 0.95.1 [UPGRADE] wfrench 1.2.3-1 -> 1.2.3-2 -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#340601: libldap issues
* libldap has no supported thread-safe API. Threaded programs that link against libldap are required to handle locking themselves. Wow, ok, I'm very not happy with this answer. Russ left out a pertinent comment. I said: Until somebody decides to invest some energy into writing a new C API spec, (simply dusting off the expired C API draft won't cut it) there is not and will never be any official support for threading/re-entrancy in the LDAP API. I think that *all* libraries should have thread-safe APIs; We all agree on that. Thus this page http://scratchpad.wikia.com/wiki/LDAP_C_API but it's not going to happen until more people get involved. > and aside from this minor blemish, libldap_r appears to already be a perfectly good thread-safe, reentrant library, supported by upstream or not. Ideally libldap would be re-entrant and free-threaded. But there are so many other problems with the API already, we're not interested in putting any more bandaids on it. We need a ground-up effort at defining a new API. We may not have to throw out 100% of what we have today, but there's no point in continuing to patch it. It's junk, and needs to be rewritten. We have the following callers using libldap in Debian which also have need of thread-safety and currently take no additional steps to ensure libldap is thread-safe: - libnss-ldap Not true, nss_ldap already locks itself to prevent re-entrance. As such, it *must* only be linked with libldap, not libldap_r. (Remember, nss_ldap was written to work with other vendors' libraries too, and none of them are re-entrant, so it has to do the locking itself.) -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sunhttp://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465400: FTBFS: missing build-dependency on desktop-file-utils
Package: geda-gattrib Version: 1.4.0-1 Severity: serious Justification: no longer builds from source geda-gattrib's configure script wants to find update-desktop-database, which is in desktop-file-utils. That is not build-depended upon, so the build fails. -- William Grant signature.asc Description: OpenPGP digital signature
Bug#464840: svn-buildpackage: svn-do for ./debian-only dirs is very useful; please move into $PATH
tag 464840 pending thanks sean finney wrote: hey eddy, I was thinking for quite some time to move svn-do in /usr/bin, but i had my reserves since it is a contrib-ed script and it definitely needs some love. yeah, i could understand that. BTW, svn-buildpackage has it source in the collab-maint[1] area of svn.d.o, and always we (myself and Eduard) are always open to and waiting for new contributors. Now that you asked, I will probably do this, but I expect people to contribute patches when complaining that svn-do is not smart enough or should be extended. i think that's fair enough :) I just committed the change. This will be available once 0.6.24 will be released. [1] svn+ssh://svn.debian.org/svn/collab-maint/deb-maint/svn-buildpackage/trunk -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465182: osmo: Segm faults right after start up
On Mon, Feb 11, 2008 at 09:54:59PM +0100, Eike Nicklas wrote:
> Hi Uwe,
>
> On Sat, 09 Feb 2008 09:08:01 +0100 Uwe Steinmann wrote:
>
> >
> > I can't even see a window. It dies before.
> >
>
> Thanks for reporting this. The package seems to work fine on i386, so
> this might be ppc-specific. I don't have access to a ppc machine nor
> experience in debugging such potentially platform specific problems,
> but will contact upstream and do my best to find the source of the
> problem.
If I comment out the line 1637 in calendar.c
gtk_tooltips_set_tip (appGUI->osmo_tooltips,
appGUI->cal->n_timeline_button, _("Insert timeline"), NULL);
the application starts.
Uwe
--
MMK GmbH, Fleyer Str. 196, 58097 Hagen
[EMAIL PROTECTED]
Tel: 02331 840446Fax: 02331 843920
signature.asc
Description: Digital signature
Bug#465399: osmo: Full-year calendar is somewhat messed up
Package: osmo Version: 0.1.6-1 Severity: normal The Full-year calendar seems to have a small cosmetic bug. A month not starting on a monday has the number '255' instead of a empty field in the columns before the month actually starts. January 2008 looks like the following Mo Di Mi Do Fr ... 255 1 2 3 4 The same happens at the end of the month. Each month is filled up with 255. BTW, the full-year calendar starts up showing the calendar for 2008 but the little text field for changing the year says '2007'. Uwe -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'sid'), (500, 'oldstable'), (500, 'testing'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.22-3-powerpc Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Shell: /bin/sh linked to /bin/bash Versions of packages osmo depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii libcairo2 1.4.14-1 The Cairo 2D vector graphics libra ii libglib2.0-0 2.14.6-1 The GLib library of C routines ii libgtk2.0-02.12.7-1 The GTK+ graphical user interface ii libical0 0.30-1iCalendar library implementation i ii libpango1.0-0 1.18.4-1 Layout and rendering of internatio ii libxml22.6.31.dfsg-1 GNOME XML library osmo recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388361: This might be awhile.
Hello Brandon, > I have a sponsor for a couple other packages. Unfortunately, he is not > responding to my emails. I sent a Request for Sponsorship to > debian-mentors a few days ago, but there is no response to that. It > might be some time before I can adopt pydance. > > I fixed bug #434457, which is a bug that causes pydance to crash. I'll > upload the patch there, in case I can't adopt pydance anytime soon. why don't you join Debian Python Apps Team [1], inject the package in our svn repository, and ask sponsorship under DPAT hat? Regards, Sandro [1] http://wiki.debian.org/Teams/PythonAppsPackagingTeam -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465367: [Pkg-mailman-hackers] Bug#465367: unclean purge
On Tuesday 12 February 2008 03:55, [EMAIL PROTECTED] wrote: > Package: mailman > Severity: minor Which version? Please use the "reportbug" tool to include all relevant info into a bug report. thanks, Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465387: no way to install a game
Joey Hess wrote: Package: goplay Version: 0.2-1+b1 Severity: wishlist It should be possible to click to install a game. If that feature is added, goplay would be close to ready to be included in the desktop task. I'm not sure what would be the best way to handle the installation. "synaptic install " would be great, except synaptic doesn't support that yet. ;-) Synaptic must have *some* support for that, since update-manager uses it for something that should be "synaptic update/synaptic upgrade ". -- Regards, EddyP = "Imagination is more important than knowledge" A.Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461615: shogun: fixup a bit building by a user of version with lightsvm
tags 461615 + wontfix thanks On Sat, 2008-01-19 at 17:06 -0500, Yaroslav Halchenko wrote: > Package: shogun > Version: 0.4.4 > Severity: wishlist > > > Elaborate a bit handling of building debian package for the people > desired to include lightsvm -- it failed for me whenever I got full > upstream tarball -- I had to remove R/sg/src (which might be a very > cruel solution) to make it build nicely (otherwise it starts to > configure/build those and fails) I've added this paragraph to /usr/share/doc/shogun-doc/README.Debian: The nonfree SVMlight files have been removed from the upstream archive and the package is configured with --disable-svmlight. Users seeking for SVMLight may resort to using the included GPDT-SVM as a drop in replacement. It uses a very similar algorithm but in many practical applications was shown to be a lot faster. -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962 signature.asc Description: This is a digitally signed message part
Bug#449536: eclipse: Editor displays stack trace of error instead of file contents.
On Tue, Nov 06, 2007 at 02:02:08PM +0100, JN Dybowski wrote: > Package: eclipse > Version: 3.2.2-4 > Severity: important > > Upon starting eclipse the attached stack trace is being displayed instead of > file contents. Right clicking in the resource browser does not work. > Error occurs with testing and unstable versions for both sun-java6-jre and > gij. I can't reproduce this failure. I tested this also an amd64. Does it work with current java-gcj-compat from unstable for you? Cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#463659: evolution-data-server: Confirmed fixed with e-d-s 1.12.3-1
Package: evolution-data-server Followup-For: Bug #463659 Just to mention it's fixed for me by installing e-d-s 1.12.3-1 from unstable, at least for message referenced in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463659#20 Btw, I reassigned the bug on e-d-s too. Regards, -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-vserver-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages evolution-data-server depends on: ii evolution-data-server 1.12.3-1 architecture independent files for ii libbonobo2-0 2.21.90-1 Bonobo CORBA interfaces library ii libc6 2.7-6 GNU C Library: Shared libraries ii libcamel1.2-101.12.3-1 The Evolution MIME message handlin ii libcomerr21.40.5-2 common error description library ii libdb4.4 4.4.20-11 Berkeley v4.4 Database Libraries [ ii libebook1.2-9 1.12.3-1 Client library for evolution addre ii libecal1.2-7 1.12.3-1 Client library for evolution calen ii libedata-book1.2-21.12.3-1 Backend library for evolution addr ii libedata-cal1.2-6 1.12.3-1 Backend library for evolution cale ii libedataserver1.2-9 1.12.3-1 Utility library for evolution data ii libegroupwise1.2-13 1.12.3-1 Client library for accessing group ii libgconf2-4 2.20.1-2+b1GNOME configuration database syste ii libglib2.0-0 2.14.5-2 The GLib library of C routines ii libgnome2-0 2.20.1.1-1 The GNOME 2 library - runtime file ii libgnomevfs2-01:2.20.1-1 GNOME Virtual File System (runtime ii libgnutls13 2.0.4-1the GNU TLS library - runtime libr ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.7-4OpenLDAP libraries ii libnspr4-0d 4.7.0~1.9b1-2 NetScape Portable Runtime Library ii libnss3-1d3.12.0~1.9b1-2 Network Security Service libraries ii liborbit2 1:2.14.10-0.1 libraries for ORBit2 - a CORBA ORB ii libpopt0 1.10-3 lib for parsing cmdline parameters ii libsoup2.2-8 2.2.104-1 an HTTP library implementation in ii libxml2 2.6.31.dfsg-1 GNOME XML library ii zlib1g1:1.2.3.3.dfsg-11 compression library - runtime evolution-data-server recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465398: grub-pc: doesn't support 1280x800 on a widescreen laptop
Package: grub-pc
Version: 1.96+20080210-1
Severity: minor
My laptop's LCD supports 1280x800 in Xorg, but grub-pc's vbeinfo command
doesn't detect it and setting gfxmode to it does not work. This means I
need to prepare a special horizontally compressed image for the
background splash image to not look stretched out with 1024x768 mode.
-- Package-specific info:
*** BEGIN /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/sda1 / reiserfs rw,relatime 0 0
/dev/sda1 /dev/.static/dev reiserfs rw 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid 0 0
usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec 0 0
fusectl /sys/fs/fuse/connections fusectl rw 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/sda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/update-grub using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,1)
if font (hd0,1)/usr/share/grub/unicode.pff ; then
set gfxmode=1024x768
insmod gfxterm
insmod vbe
terminal gfxterm
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod png
if background_image (hd0,1)/boot/grub/splash.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_hurd ###
### END /etc/grub.d/10_hurd ###
### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, linux 2.6.24-1-686" {
linux (hd0,1)/boot/vmlinuz-2.6.24-1-686 root=/dev/sda1 ro vga=792
initrd (hd0,1)/boot/initrd.img-2.6.24-1-686
}
menuentry "Debian GNU/Linux, linux 2.6.24-1-686 (single-user mode)" {
linux (hd0,1)/boot/vmlinuz-2.6.24-1-686 root=/dev/sda1 ro single
vga=792
initrd (hd0,1)/boot/initrd.img-2.6.24-1-686
}
menuentry "Debian GNU/Linux, linux 2.6.23-1-686" {
linux (hd0,1)/boot/vmlinuz-2.6.23-1-686 root=/dev/sda1 ro vga=792
initrd (hd0,1)/boot/initrd.img-2.6.23-1-686
}
menuentry "Debian GNU/Linux, linux 2.6.23-1-686 (single-user mode)" {
linux (hd0,1)/boot/vmlinuz-2.6.23-1-686 root=/dev/sda1 ro single
vga=792
initrd (hd0,1)/boot/initrd.img-2.6.23-1-686
}
menuentry "Debian GNU/Linux, linux 2.6.22-3-686" {
linux (hd0,1)/boot/vmlinuz-2.6.22-3-686 root=/dev/sda1 ro vga=792
initrd (hd0,1)/boot/initrd.img-2.6.22-3-686
}
menuentry "Debian GNU/Linux, linux 2.6.22-3-686 (single-user mode)" {
linux (hd0,1)/boot/vmlinuz-2.6.22-3-686 root=/dev/sda1 ro single
vga=792
initrd (hd0,1)/boot/initrd.img-2.6.22-3-686
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86 ###
menuentry "Memory test (memtest86)" {
linux (hd0,1)/boot/memtest86.bin
}
### END /etc/grub.d/20_memtest86 ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
linux (hd0,1)/boot/memtest86+.bin
}
### END /etc/grub.d/20_memtest86+ ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-pc depends on:
ii base-files4.0.2 Debian base system miscellaneous f
ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy
ii libc6 2.7-6 GNU C Library: Shared libraries
ii liblzo2-2 2.02-3 data compression library
ii libncurses5 5.6+20080203-1 Shared libraries for terminal hand
-- debconf information:
* grub-pc/chainload_from_menu.lst: true
--
bye,
pabs
http://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#465397: debian-maintainers: jetring changeset for DM Applicant Y Giridhar Appaji Nag
Package: debian-maintainers Version: 1.19 Severity: normal Tags: patch -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I would like to be added to the DM keyring. I am attaching the jetring changeset for my DM application [1]. Moritz Muehlenhoff advocated [2] my application. [1] http://lists.debian.org/debian-newmaint/2008/02/msg00049.html [2] http://lists.debian.org/debian-newmaint/2008/02/msg00050.html Giridhar - -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash debian-maintainers depends on no packages. Versions of packages debian-maintainers recommends: ii gnupg 1.4.6-2+b1 GNU privacy guard - a free PGP rep - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHsUbw4eu+pR04mIcRAtU1AJ0WPJ9FkgsnhEdfADSACIs9vqP7cACfZQNj 86RWgpC8qh0gGAI9L9ZUBB0= =vasE -END PGP SIGNATURE- Changed-By: # keyring maintainer will fill this in Date: Tue, 12 Feb 2008 12:25:15 +0530 Comment: adding debian-maintainer Y Giridhar Appaji Nag NM-Page: https://nm.debian.org/[EMAIL PROTECTED] Agreement: http://lists.debian.org/debian-newmaint/2008/02/msg00049.html Advocates: http://lists.debian.org/debian-newmaint/2008/02/msg00050.html Action: import Data: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.6 (GNU/Linux) mQGiBEQ3g24RBACDmUprgUSsodGbrEr+cM//iy2mRYzujHJ/dDbCO8U2L2ltYDv0 yj++6JCFCdDhsKTTH4/fuMNnMUhXvi2wLADk7bzIndIG8QXXElXNE9VcTxpXS307 oEfrZ3VCOjfSd8yp79xVvpN7F18nmNAHTBvuRKjm4jtCFq4o+MLRb1pvKwCg+dy0 FC95HPPhHGFw+xl9+daUse8D/R80bv1neLY4gvmQ/VdawE10Np5rhlQ+Py0oZml3 1p6YMGWAZA+ppC/qCqkC6p4jX8OlJzZVEOuc97Yd8ySKiH2JjXbh4o+ICjTyXZde CeGziIWPGgYk0pRHuTPbPIztWzujwCWfdV3SLNHv8DGGdKf+YNGoFZTwkfzsE+BB yOtVA/0VyDi+YTt4rQ7DwvsxabLpiHtTt1wnO8JRRhGSgzQz12QqFT2TqVBzWddm lEQRLLxkD86PPtBM0FdD0arjumJGgtorh0TJjJMLSJQpjDsQy5GzUsKNZmp3t8sM 1oNUf4dwwaWpEZYeWle5mMxyM3tfJQLgnv91aedEmN9vSz2uLrQrWSBHaXJpZGhh ciBBcHBhamkgTmFnIDxnaXJpZGhhckBhcHBhamkubmV0PohjBBMRAgAjAhsDBgsJ CAcDAgQVAggDBBYCAwECHgECF4AFAkQ3icMCGQEACgkQ4eu+pR04mIeDUgCgwUID v2qSBcz+fJfmQLt9K3rOdL8AnAgu9xmapFJC/AHKe7jXinV3KbNniEYEEBECAAYF AkTX+UMACgkQFyn1hmqfPDhXKACfWTB/ngJMAq8sMUCdMU/yxVl+Jh0AnApQTPQF X73CpemQ6N04uTfIDKyOiEYEEBECAAYFAkTqr94ACgkQ4Rhi6gTxMLwzlgCaA5Sd 5Ks23owtB/4Q5lAV8qKfGmEAnjh+skHjrVp8ejtlACMoUzuyAaA1iEYEEBECAAYF Aka0VOQACgkQD+cvZLmwyfKh0QCeMgCgebliSV5jD88PA78h/YRM3okAoLSMdAhR 1CGMsSKin5HSCWhx8XSMiEYEEBECAAYFAka0znsACgkQGqhu7qUmpKXihACggaeV 33EOyaC2rjQfi5tY2ogrz4kAnjslkc6t/5VJOEa7QpsUvWfgHIMSiEYEEBECAAYF Aka27V8ACgkQKS6CjcT4LG2QWwCdF5jrRy33VsZ6cSSGjayFIZ7Bq94An0Fja/KW Uhhqd0N27k0x91TQFxsCiEYEEBECAAYFAka6IGcACgkQwAfeuzCCU0VCpACgu97d gYuBf6KSdAakm7ZYr6oU1y4Anj/cXmYxO0eSbW2z1ok2ohX97JvgiEYEEBECAAYF AkdYD2YACgkQ1OXtrMAUPS3aCwCbBaiKDuGhDKRFjJbzPi/agagVDpIAn2uCBtaK TsFyui6AQZQdmsU3/iNWiEYEEBECAAYFAkdYQvoACgkQtNIorZ24/wZO2QCeOTYR GzZNpi3B5lzFEvFEQ7QDENoAnio/mGfz+dUdeNaRJHi+1zLGRtoRiEYEEBECAAYF AkdZCb8ACgkQfPP1rylJn2ERbwCeIC32ipDU4Y9+ez243IrQGs2APrIAnjCnqD/B S1Lc3/2wDdbFu7D+719jiEYEEBECAAYFAkdZCkAACgkQJgw1SIj4j48KZgCeIErv rKqX8ayosZHoCZ/o5AKGpVIAnjiEqHiHw52URDlmtBB3E0qg07PXtCpZIEdpcmlk aGFyIEFwcGFqaSBOYWcgPGFwcGFqaUBpYmlibGlvLm9yZz6IYAQTEQIAIAUCRDeJ rAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEOHrvqUdOJiHvu8An3ackjc9 grHtc3TzxUrHq1gnO9cjAKDtPPSGi9R99OcQcLBTmk5gEIGxf4hGBBARAgAGBQJE 1/lIAAoJEBcp9YZqnzw4N1sAmwSIJiRnSyAaGqzT1j8FfBpj5tFlAJ93gxGxyurK a/QQR6vEvpvi/PGed4hGBBARAgAGBQJE6q/lAAoJEOEYYuoE8TC8fEcAoIRD+444 JzpL98dCj22yhwK503BCAJoCvDWpVmIr0zCjrPKfgTuViN7XOIhGBBARAgAGBQJG tFToAAoJEA/nL2S5sMnypq0An39AUNyheEs7SjkFyrjQ6QwqtOwwAJ9WGgzBW3h0 Saiv4eYQBYfeMtWxI4hGBBARAgAGBQJGtM5/AAoJEBqobu6lJqSl2GoAn1/UEMxj WsEKWtuB3ZdFDJMd2rvoAJ9xqh5EatLzqm3FmQF8IWYPd9GAVohGBBARAgAGBQJG tu1rAAoJECkugo3E+CxtcFgAn1hRzy1h7YYHSW/0UnSU7NRwQsbvAJ97glnIqehY 8uvKpahHuwFU2h+rj4hGBBARAgAGBQJGuiBnAAoJEMAH3rswglNFI/UAoKBjO2iC sEhGOEBnsHorZSetGNi9AJ9Nl4Zt8npCYHfZiIYg6Z0Af1n4QYhGBBARAgAGBQJH WA9mAAoJENTl7azAFD0tx9sAnRkggj17VE4kJrX7Vfkg1SORy/r3AJsGCzVvJ4Gw dhZLsi5BO6jovzTRyohGBBARAgAGBQJHWEOJAAoJELTSKK2duP8GybkAoN1FatY+ lJh9H0T1o2jIZ1Ls9kjPAKDMxUgofdqZFpJ+/UII2BSOHhg1/IhGBBARAgAGBQJH WQm/AAoJEHzz9a8pSZ9hS2sAniqYu5r3fYOUzHlrdUS5uf+W4m0ZAJ0cSdm3uKcr 5SlFXQ4dJN8KR20OGohGBBARAgAGBQJHWQpAAAoJECYMNUiI+I+PUaAAn3ZSSIHw /OyXV+Nxzu/DWBGOkZMnAJ91MxWe51v4NocMGOeAqBKAH4qpYtHYZNhiARAAAQEA AAD/2P/gABBKRklGAAEBAQJYAlgAAP/+AQ1wdWIgICAxMDI0RC8x RDM4OTg4NyAyMDA2LTA0LTA4CiAgICAgIEtleSBmaW5nZXJwcmludCA9IDVCNkIg RjIyMyBCNzY5IDYzRTkgRTJDQiAgMEEzRiBFMUVCIEJFQTUgMUQzOCA5ODg3CnVp ZCAgICAgICAgICAgICAgICAgIFkgR2lyaWRoYXIgQXBwYWppIE5hZyA8Z2lyaWRo YXJAYXBwYWppLm5ldD4KdWlkICAgICAgICAgICAgICAgICAgWSBHaXJpZGhhciBB cHBhamkgTmFnIDxhcHBhamlAaWJpYmxpby5vcmc+CnN1YiAgIDIwNDhnLzczRUFG MEI1IDIwMDYtM
Bug#465396: Warsow 4.1 New upstream release
Package: warsow Version: 4.1 Please update game in repository. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465379: wordnet: bashism in /bin/sh script
Hi, thanks for your QA effort. On Mon, 11 Feb 2008, Raphael Geissert wrote: check I've found your package containing a /bin/sh script making use of a bashism. checkbashisms' output: possible bashism in ./usr/bin/wnb line 112 (should be '.', not 'source'): source $configfile Are your sure that this is no false positive. IMHO the line you pointed to is pure TCL/TK code. I personally have no knowledge in TCL/TK and its syntax. It might be that the line you are mentioning is a system command that should be interpreted by /bin/sh but the fact that the first line of /usr/bin/wnb says it is a shell script just is a wrapper around wish. Not using bash as /bin/sh would lead to errors or unexpected behaviours. Have you actually observed such unexpected behaviour with wnb or are you just guessing. I can not commit this. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#434457: Fixed it.
tags 434457 +patch thanks I fixed this bug. The problem was an uncaught exception when reading in sm files that contained letters. I don't know what the letters are supposed to mean, but pydance should convert unrecognized input to a sane default, ignore, or give an error, rather than crashing. The patch that I attached will cause pydance to convert unkown characters into "0"'s, which is the behavior described in the pydance docs. -Brandon diff -ur pydance-1.0.3/fileparsers.py pydance-1.0.3-5/fileparsers.py --- pydance-1.0.3/fileparsers.py 2005-04-04 13:49:22.0 -0700 +++ pydance-1.0.3-5/fileparsers.py 2008-01-29 14:49:07.0 -0800 @@ -603,13 +603,13 @@ if gametype in games.COUPLE: step1 = [note] step2 = [note] - step1.extend([SMFile.step[int(s)] for s in sd[0:count/2]]) - step2.extend([SMFile.step[int(s)] for s in sd[count/2:]]) + step1.extend([SMFile.step[util.my_int(s)] for s in sd[0:count/2]]) + step2.extend([SMFile.step[util.my_int(s)] for s in sd[count/2:]]) stepdata[0].append(step1) stepdata[1].append(step2) else: step = [note] - step.extend([SMFile.step[int(s)] for s in sd]) + step.extend([SMFile.step[util.my_int(s)] for s in sd]) stepdata.append(step) beat += note / 4.0 diff -ur pydance-1.0.3/util.py pydance-1.0.3-5/util.py --- pydance-1.0.3/util.py 2004-05-23 09:00:42.0 -0700 +++ pydance-1.0.3-5/util.py 2008-01-29 14:45:33.0 -0800 @@ -90,3 +90,11 @@ parts[i] = parts[i][0].capitalize() + oldparts[1:] return " ".join(parts) + +# This function takes a string, and returns an int. Unlike the builtin int() +# function, this function returns 0 if the string does not represent a number +def my_int(x): + try: +return int(x) + except: +return 0
Bug#461546: tipcutils: General update after the debconf review process
IMPORTANT: please *really* use the patch attached to this mail and *not only* the PO files sent in bug reports. The same stands for rewritten debconf templates: please use the ones attcahed in this mail (in the .tar.gz file) and NOT those originally sent in #461546. I discovered a small glitch in them (extra space) and I unfuzzied all incoming PO files. Dear Debian maintainer, On Saturday, January 05, 2008, I sent you a notification about the beginning of a review action on debconf templates for tipcutils. Then, I sent you a bug report with rewritten templates and announcing the beginning of the second phase of this action: call for translation updates. Translators have been working hard and here is now the result of their efforts. Please consider using it EVEN if you committed files to your development tree as long as they were reported. The attached tarball contains: - debian/changelog with the list of changes - debian/control with rewrites of packages' descriptions - debian/ with all the rewritten templates file(s) - debian/po/*.po with all PO files (existing ones and new ones) As said, please use *at least* the PO files as provided here, preferrably over those sent by translators in their bug reports. All of them have been checked and reformatted. In some cases, formatting errors have been corrected. The patch.rfr file contains a patch for the templates and control file(s) alone. Please note that this patch applies to the templates and control file(s) of your package as of Saturday, January 05, 2008. If your package was updated in the meantime, I may have updated my reference copybut I also may have missed that. This is indeed why I suggested you do not modified such files while the review process was running, remember..:-) It is now safe to upload a new package version with these changes. Please notify me of your intents with regards to this. There is of course no hurry to update your package but feel free to contact me in case you would need sponsoring or any other action to fix this. -- patch.tar.gz Description: Binary data --- tipcutils.old/debian/templates 2008-01-01 12:48:57.719332464 +0100 +++ tipcutils/debian/templates 2008-01-19 14:08:41.712400356 +0100 @@ -1,52 +1,61 @@ +# These templates have been reviewed by the debian-l10n-english +# team +# +# If modifications/additions/rewording are needed, please ask +# [EMAIL PROTECTED] for advice. +# +# Even minor modifications require translation updates and such +# changes should be coordinated with translators and reviewers. + Template: tipcutils/configure Type: boolean Default: true -_Description: Configure this TIPC node now? - In case you don't know what TIPC is you most probably installed - the package "tipcutils" by accident. As it is a very special network protocol - you most probably don't need you might want to consider uninstalling it. - . - If you don't want to configure TIPC now, you can edit the configuration file - /etc/default/tipc later. +_Description: Should this TIPC node be configured automatically now? + If you do not choose this option, you can edit '/etc/default/tipc' or use + the command line tool 'tipc-config'. Template: tipcutils/address Type: string Default: 1.1.1 -_Description: The TIPC address of this node: - The TIPC address is written in Z.C.N (Zone.Cluster.Node) notation. +_Description: TIPC address of this node: + Please enter the TIPC address of this node, in Z.C.N (Zone.Cluster.Node) + notation. . - Make sure all nodes in your network have different addresses! + Each node in a network should have a unique address. Template: tipcutils/netid Type: string Default: 4711 -_Description: The Network ID of the TIPC Network this node shall join: - In case there is just one TIPC Network, keep the default! +_Description: Network ID of the TIPC network to join: + The default setting should be appropriate when there is only + one local TIPC network. Template: tipcutils/remote_management -Type: string -Default: disable -_Description: Enable/disable TIPC remote management for this node: - In case you don't know what this is keep it disabled! +Type: boolean +Default: false +_Description: Enable TIPC remote management? + Please choose this option if you are sure that network + management should be enabled for this node. Template: tipcutils/default_ndd Type: string Default: 0.0.0 -_Description: The default Neighbour Detection Domain for this TIPC node: - If there is no setting for a specific bearer this will be used as the Neighbour - Detection Domain. Setting a NDD for a specific bearer is not yet possible in - this package version. +_Description: Default neighbor detection domain for this TIPC node: + This setting will define the neighbor detection domain (NDD) if there is + no setting for a specific bearer. . - In case you don't know what this is keep the default! + Setting the NDD for a specific bearer is not yet possible in + this package version. Template: tipcuti
Bug#465395: libstlport5.1-dev: another warning about unused parameter
Package: libstlport5.1-dev
Version: 5.1.5-1
Severity: minor
Thanks for applying my patch. i just recompiled and found another one.
Not sure why that did not show up before, might have been introduced in
the last version. This time patch is a bit more complicated because the
parameter is used with debug output, so I had to add another
preprocessor macro. Anyway, it's straight-forward and it would be cool
if you could apply it in one of the next versions.
Best,
Norbert
diff -ru /usr/include/stlport-orig/stl/_algobase.c
/usr/include/stlport/stl/_algobase.c
--- /usr/include/stlport-orig/stl/_algobase.c 2007-09-09 02:12:28.0
-0700
+++ /usr/include/stlport/stl/_algobase.c2008-02-11 22:45:48.0
-0800
@@ -371,7 +371,7 @@
template
_ForwardIter __lower_bound(_ForwardIter __first, _ForwardIter __last, const
_Tp& __val,
- _Compare1 __comp1, _Compare2 __comp2, _Distance*) {
+ _Compare1 __comp1, _Compare2
_STLP_VERBOSE_PARAM(__comp2), _Distance*) {
_Distance __len = distance(__first, __last);
_Distance __half;
_ForwardIter __middle;
diff -ru /usr/include/stlport-orig/stl/config/features.h
/usr/include/stlport/stl/config/features.h
--- /usr/include/stlport-orig/stl/config/features.h 2007-08-18
13:45:42.0 -0700
+++ /usr/include/stlport/stl/config/features.h 2008-02-11 22:46:38.0
-0800
@@ -415,8 +415,11 @@
#if !defined (_STLP_DEBUG)
# define _STLP_VERBOSE_ASSERT(expr,diagnostic)
+# define _STLP_VERBOSE_PARAM(param)
# define _STLP_DEBUG_CHECK(expr)
# define _STLP_DEBUG_DO(expr)
+#else
+# define _STLP_VERBOSE_PARAM(param) param
#endif
#if !defined (_STLP_WEAK)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libstlport5.1-dev depends on:
ii g++ [c++-compiler]4:4.2.2-2 The GNU C++ compiler
ii g++-4.2 [c++-compiler]4.2.3-1The GNU C++ compiler
ii libstlport5.1ldbl 5.1.5-1STLport C++ class library
libstlport5.1-dev recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388361: This might be awhile.
I have a sponsor for a couple other packages. Unfortunately, he is not responding to my emails. I sent a Request for Sponsorship to debian-mentors a few days ago, but there is no response to that. It might be some time before I can adopt pydance. I fixed bug #434457, which is a bug that causes pydance to crash. I'll upload the patch there, in case I can't adopt pydance anytime soon. -Brandon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465393: `apache2.conf' is not mentioned in the manual
Package: apache2-doc Version: 2.2.8-1 Severity: wishlist The name of the main configuration file is `apache2.conf' in Debian. However, `apache2.conf' isn't mentioned in the documentation text at all. The main configuration file is referred to as `httpd.conf' on the pages of the manual: $ grep -rlF httpd.conf /usr/share/doc/apache2-doc/manual/* | wc -l 274 $ It's clear that one should not fix such number of files. It's desirable to add + The name of the main configuration file is `apache2.conf' in Debian. to `configuring.html'. `httpd.conf' will be preserved the meaning of Alias: --cut: configuring.html-- The main configuration file is usually called httpd.conf. --cut: configuring.html-- The list of the `configuring.html' files: /usr/share/doc/apache2-doc/manual/de/configuring.html /usr/share/doc/apache2-doc/manual/en/configuring.html /usr/share/doc/apache2-doc/manual/es/configuring.html /usr/share/doc/apache2-doc/manual/fr/configuring.html /usr/share/doc/apache2-doc/manual/ja/configuring.html /usr/share/doc/apache2-doc/manual/ko/configuring.html /usr/share/doc/apache2-doc/manual/pt-br/configuring.html Thanks, Tatiana Kronberg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375277: double console messages about card reader
(OK, now using initramfs-tools) ma> can we have an update on that issue for uname > 2.6.22 Linux jidanni2 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686 GNU/Linux Repeating still present. Here seen upon plugging in a MP3 player and doing $ dmesg scsi scan: INQUIRY result too short (5), using 36 scsi 1:0:0:0: Direct-Access USB 2.0 (HS) Flash Disk 1.00 PQ: 0 ANSI: 0 CCS sd 1:0:0:0: [sde] 4008881 512-byte hardware sectors (2053 MB) sd 1:0:0:0: [sde] Write Protect is off sd 1:0:0:0: [sde] Mode Sense: 00 c0 00 00 sd 1:0:0:0: [sde] Assuming drive cache: write through sd 1:0:0:0: [sde] 4008881 512-byte hardware sectors (2053 MB) sd 1:0:0:0: [sde] Write Protect is off sd 1:0:0:0: [sde] Mode Sense: 00 c0 00 00 sd 1:0:0:0: [sde] Assuming drive cache: write through sde: unknown partition table sd 1:0:0:0: [sde] Attached SCSI removable disk Also please fix: Driver 'sd' needs updating - please use bus_type methods -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464910: linux-image-2.6.24-1-686: probably due to force-enabling HPET
Package: linux-image-2.6.24-1-686 Version: 2.6.24-3 Followup-For: Bug #464910 Hi, This problem also occurs on my machine, hardware as indicated below. It's probably due to the HPET being force-enabled; see also http://bugs.debian.org/463716 and http://bugs.debian.org/386226 (the latter on a platform where the HPET is enabled by default), and perhaps others... The solution as indicated is to enable CONFIG_HPET_IRC_IRQ. Regards, Stephen -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-3) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Wed Feb 6 15:20:27 UTC 2008 ** Command line: root=/dev/md0 ro ** Tainted: PF (3) ** Kernel log: hda: hda1 hda2 DVB: registering new adapter (cx88[0]) DVB: registering frontend 0 (Conexant CX22702 DVB-T)... scsi 2:0:6:0: CD-ROMHP CD-Writer+ 9200 1.0e PQ: 0 ANSI: 4 target2:0:6: Beginning Domain Validation target2:0:6: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15) target2:0:6: Domain Validation skipping write tests target2:0:6: Ending Domain Validation Driver 'sr' needs updating - please use bus_type methods sr0: scsi3-mmc drive: 0x/0x cd/rw xa/form2 cdda tray sr 2:0:2:0: Attached scsi CD-ROM sr0 st: Version 20070203, fixed bufsize 32768, s/g segs 256 Driver 'st' needs updating - please use bus_type methods st 2:0:3:0: Attached scsi tape st0 st 2:0:3:0: st0: try direct i/o: yes (alignment 512 B) sr1: scsi3-mmc drive: 32x/32x writer cd/rw xa/form2 cdda tray sr 2:0:6:0: Attached scsi CD-ROM sr1 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 1:0:0:0: Attached scsi generic sg1 type 0 sr 2:0:2:0: Attached scsi generic sg2 type 5 st 2:0:3:0: Attached scsi generic sg3 type 1 sr 2:0:6:0: Attached scsi generic sg4 type 5 osst :I: Tape driver with OnStream support version 0.99.4 osst :I: $Id: osst.c,v 1.73 2005/01/01 21:13:34 wriede Exp $ Driver 'osst' needs updating - please use bus_type methods target2:0:3: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 32) w83627hf: Found W83627THF chip at 0x290 loop: module loaded nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt :01:00.0[A] -> GSI 16 (level, low) -> IRQ 17 NVRM: loading NVIDIA UNIX x86 Kernel Module 169.07 Thu Dec 13 18:42:56 PST 2007 padlock: VIA PadLock not detected. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-4, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-6, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. Adding 4194296k swap on /dev/mapper/cswap. Priority:-1 extents:1 across:4194296k NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): lan0: link is not ready fbx0: setting full-duplex. ip_tables: (C) 2000-2006 Netfilter Core Team Netfilter messages via NETLINK v0.30. nf_conntrack version 0.5.0 (16384 buckets, 65536 max) ip6_tables: (C) 2000-2006 Netfilter Core Team ctnetlink v0.93: registering with nfnetlink. ClusterIP Version 0.8 loaded successfully ADDRCONF(NETDEV_CHANGE): lan0: link becomes ready fbx0: no IPv6 routers present IA-32 Microcode Update Driver: v1.14a <[EMAIL PROTECTED]> lan0: no IPv6 routers present NET: Registered protocol family 4 tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky <[EMAIL PROTECTED]> Bluetooth: Core ver 2.11 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.9 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: Putting AGP V3 device at :00:00.0 into 8x mode agpgart: Putting AGP V3 device at :01:00.0 into 8x mode agpgart: Found an AGP 3.0 compliant device at :00:00.0. agpgart: Putting AGP V3 device at :00:00.0 into 8x mode agpgart: Putting AGP V3 device at :01:00.0 into 8x mode NVRM: API mismatch: the client has the version 169.09, but NVRM: this kernel module has the version 169.07. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. NVRM: API mismatch: the client has the version 169.09, but NVRM: this kernel module has the version 169.07. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: comp
Bug#465391: installed initramfs-tools ... now all OK
I see, first I install initramfs-tools and then I can install the image and remove yaird. OK, works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465392: scalapack -- please use gfortran based packages as build dependencies
Package: scalapack
Version: 1.8.0-1
Severity: important
Tags: patch
User: [EMAIL PROTECTED]
Usertags: gfortran
Hi!
I would request you to please shift Build-Depends to use the new
gfortran based Lapack, lam, mpich and Blas packages in order to phase
out packages dependent on the old g2c (g77). In this regard, I would
request you to refer to:
http://wiki.debian.org/GfortranTransition
You may wish to rename the package in order to provide for parallel
installability of the g77 and gfortran based scalapack packages, if
you choose to upload to unstable.
Attached is a patch which does the needful, which you may use to base
your change.
Also, please check whether using Add_ is correct. I presume something
like that is needed due to gfortran's new calling conventions.
Thank you.
Kumar
--
Kumar Appaiah,
458, Jamuna Hostel,
Indian Institute of Technology Madras,
Chennai - 600 036
diff -u scalapack-1.8.0/debian/control scalapack-1.8.0/debian/control
--- scalapack-1.8.0/debian/control
+++ scalapack-1.8.0/debian/control
@@ -3,7 +3,7 @@
Priority: extra
Maintainer: Muammar El Khatib <[EMAIL PROTECTED]>
Standards-Version: 3.7.2
-Build-Depends: libmpich1.0-dev (>= 1.2.7-1), lam4-dev (>= 7.1.1-3.2), pvm-dev, blacs-mpich-dev (>= 1.1-25), blacs-lam-dev, blacs-pvm-dev, g77, lapack3-dev | liblapack-3.so, refblas3-dev | libblas-3.so, debhelper (>= 5)
+Build-Depends: libmpich1.0-dev (>= 1.2.7-1), lam4-dev (>= 7.1.1-3.2), pvm-dev, blacs-mpich-dev (>= 1.1-25), blacs-lam-dev, blacs-pvm-dev, gfortran, liblapack-dev | liblapack.so.3gf , libblas-dev | libblas.so.3gf, debhelper (>= 5)
Package: scalapack1-mpich
Architecture: any
diff -u scalapack-1.8.0/debian/rules scalapack-1.8.0/debian/rules
--- scalapack-1.8.0/debian/rules
+++ scalapack-1.8.0/debian/rules
@@ -41,7 +41,7 @@
ar x ../$${i}_lam.a ;\
cd .. ;\
gcc -shared -Wl,-soname=lib$$i-lam.so.$(version_major) -o \
- lib$$i-lam.so.$(version) tmp/*.o -lblas-3 -llapack-3 -lblacsCinit-lam -lblacs-lam -llam -lg2c;\
+ lib$$i-lam.so.$(version) tmp/*.o -lblas-3 -llapack-3 -lblacsCinit-lam -lblacs-lam -llam -lgfortran;\
ln -snf lib$$i-lam.so.$(version) lib$$i-lam.so.$(version_major) ;\
ln -snf lib$$i-lam.so.$(version_major) lib$$i-lam.so ;\
rm tmp/* ;\
@@ -90,7 +90,7 @@
ar x ../$${i}_mpich.a ;\
cd .. ;\
gcc -shared -Wl,-soname=lib$$i-mpich.so.$(version_major) -o \
- lib$$i-mpich.so.$(version) tmp/*.o -lblas-3 -llapack-3 -lblacsCinit-mpich -lblacs-mpich -L /usr/lib/mpich/lib/shared -lmpich -lg2c;\
+ lib$$i-mpich.so.$(version) tmp/*.o -lblas-3 -llapack-3 -lblacsCinit-mpich -lblacs-mpich -L /usr/lib/mpich/lib/shared -lmpich -lgfortran;\
ln -snf lib$$i-mpich.so.$(version) lib$$i-mpich.so.$(version_major) ;\
ln -snf lib$$i-mpich.so.$(version_major) lib$$i-mpich.so ;\
rm tmp/* ;\
@@ -133,7 +133,7 @@
ar x ../$${i}_pvm.a ;\
cd .. ;\
gcc -shared -Wl,-soname=lib$$i-pvm.so.$(version_major) -o \
- lib$$i-pvm.so.$(version) tmp/*.o -lblas-3 -llapack-3 -lblacs-pvm -lpvm3 -lg2c;\
+ lib$$i-pvm.so.$(version) tmp/*.o -lblas-3 -llapack-3 -lblacs-pvm -lpvm3 -lgfortran;\
ln -snf lib$$i-pvm.so.$(version) lib$$i-pvm.so.$(version_major) ;\
ln -snf lib$$i-pvm.so.$(version_major) lib$$i-pvm.so ;\
rm tmp/* ;\
only in patch2:
unchanged:
--- scalapack-1.8.0.orig/SLmake.inc
+++ scalapack-1.8.0/SLmake.inc
@@ -96,10 +96,10 @@
#
# The fortran and C compilers, loaders, and their flags
#
-F77 = g77
+F77 = gfortran
#F77 = /usr/local/pgi/linux86/bin/pgf77
CC= gcc
-NOOPT = -w -fno-globals -fno-f90 -fugly-complex $(FPIC)
+NOOPT = -w $(FPIC)
F77FLAGS = -Wall -O6 -funroll-all-loops -ffast-math $(NOOPT)
CCFLAGS = -Wall $(FPIC) -O6 -funroll-all-loops -ffast-math
SRCFLAG =
@@ -117,7 +117,7 @@
# C preprocessor defs for compilation
# (-DNoChange, -DAdd_, -DUpCase, or -Df77IsF2C)
#
-CDEFS = -Df77IsF2C -DNO_IEEE $(USEMPI)
+CDEFS = -DAdd_ -DNO_IEEE $(USEMPI)
#
# The archiver and the flag(s) to use when building archive (library)
# Also the ranlib routine. If your system has no ranlib, set RANLIB = echo
signature.asc
Description: Digital signature
Bug#465391: never able to install a kernel again?
Package: yaird Apparently I will never be able to install or upgrade a kernel again without poisoning that kernel, as its /boot files are left in a halfway state after this adventure. Please advise. Setting up linux-image-2.6.24-1-686 (2.6.24-4) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: unrecognised device: /sys/devices/LNXSYSTM:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/LNXVIDEO:00 yaird error: there were errors in this run, aborting now without output (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.24-1-686 (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.24-1-686 E: Sub-process /usr/bin/dpkg returned an error code (1) # dpkg -i /var/cache/apt/archives/yaird_0.0.12-24_i386.deb dpkg - warning: downgrading yaird from 0.0.12-25 to 0.0.12-24. (Reading database ... 105176 files and directories currently installed.) Preparing to replace yaird 0.0.12-25 (using .../yaird_0.0.12-24_i386.deb) ... Unpacking replacement yaird ... Setting up yaird (0.0.12-24) ... Installing new version of config file /etc/yaird/Default.cfg ... # set linux-image-2.6.24-1-686 # http_proxy= apt-get install $@ Reading package lists... Done Building dependency tree Reading state information... Done linux-image-2.6.24-1-686 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up linux-image-2.6.24-1-686 (2.6.24-4) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: bad device link in /sys/class/input/event2/device (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.24-1-686 (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.24-1-686 E: Sub-process /usr/bin/dpkg returned an error code (1) Can I opt out and go back to the old way? # apt-get --purge remove yaird The following packages will be REMOVED: linux-image-2.6-686* linux-image-2.6.22-3-686* linux-image-2.6.24-1-686* linux-image-686* yaird* Apparently not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#11800: Want your love back?? Check it out
Do not pass! Valid only the for few days Each client will get incredible Christmas Discount! Let us advise you one of the best Canadian drugstores online. http://www.straightsent.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#456971: Bug#455623: FTBFS with GCC 4.3: missing #includes
On Sun, Feb 10, 2008 at 06:33:46PM +0100, Martin Michlmayr <[EMAIL PROTECTED]>
was heard to say:
> * Gaudenz Steinlin <[EMAIL PROTECTED]> [2008-02-09 21:01]:
> > I tried to fix this today, but quickly discovered that #456971 on
> > libsigc++-2.0-dev is blocking this further down the path. As I currently
> > don't have the time to fix libsigc++-2.0-dev as well I just subscribed
> > to #456971 and added a block. I will look into this again as soon as
> > #456971 is fixed.
> >
> > What are the current NMU rules for this issue? Would an NMU for #456971
> > be acceptable atm?
>
> I'm not sure there's a solution for #456971 yet, although I heard
> rumours the problem is fixed in a newer upstream release.
>
> Daniel, did you have any chance to look into this issue? This is
> getting really important because many packages fail to compile with
> gcc 4.3 because of this.
I did talk to upstream, and it looks like there is a completely new
branch of libsigc++ in which this is fixed. Unfortunately, it appears
that this change hasn't yet made it into the 2.0 branch. If this is
becoming important, then the steps I see are to:
(a) do my best to ensure that there are no nasty side-effects if I
apply the workaround I found earlier, and
(b) apply it if it looks safe.
I might be able to make some time next weekend to at least get some
work started on (a), although that's probably something other people
could verify as well. The patch that fixes the build is attached.
According to comments in the code, the typedef that's at fault is purely
a backwards-compatibility feature, and since it's just a typedef I would
*presume* that type erasure means it won't affect the ABI of the
library. I'll feel better if I can verify that lots of code still
builds and runs against the new version (and that the new version is
runtime-compatible with the old version).
Daniel
--- sigc++/signal.h.orig 2008-02-11 21:11:19.0 -0800
+++ sigc++/signal.h 2008-02-11 21:15:19.0 -0800
@@ -18,7 +18,11 @@
//Compilers, such as older versions of SUN Forte C++, that do not allow this also often
//do not allow a typedef to have the same name as a class in the typedef's definition.
//For Sun Forte CC 5.7 (SUN Workshop 10), comment this out to fix the build.
- #define SIGC_TYPEDEF_REDEFINE_ALLOWED 1
+ //
+ // Debian-specific patch: gcc-4.3 does not allow this either, and the
+ // comments below say this is a backwards-compatibility typedef, so
+ // just don't enable this feature at all.
+ //#define SIGC_TYPEDEF_REDEFINE_ALLOWED 1
#endif
namespace sigc {
Bug#465280: pbuilder fails to install libdirectfb-1.0-0: "Depends: libts0 (>= 1.0-1) which is a virtual package."
forcemerge 464222 465280 thanks On Mon, 2008-02-11 at 17:23:55 +0100, Alexander Schmehl wrote: > Package: libdirectfb-1.0-0 > Version: 1.0.1-6 > Severity: important > During building a package using pbuilder (with an uptodate build.tar.gz), I > noticed, that your package could not be installed (and therefore my package > failed to build). > > The relevent part of the pbuilder log is: > > = > The following packages have unmet dependencies: > libdirectfb-1.0-0: Depends: libts0 (>= 1.0-1) which is a virtual package. > = > > Don't know, if it's the fault of libdirectfb-1.0-0 or tslib, but I would > like to see this bug fixed soon; since most of my packages build depend on > libsdl1.2-dev and fail to build for that reason :) Yes, tslib. Should be uploading today or so... regards, guillem -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465389: gjdoc: please support src.com.sun.tools.javadoc.Main class
Package: gjdoc
Version: 0.7.8-8
Severity: wishlist
Tags: patch, upstream, fixed-upstream
This class is needed by TestNG. It should suffice to apply Michael's
patch that already went upstream:
Index: Makefile.am
===
RCS file: /sources/classpath/gjdoc/Makefile.am,v
retrieving revision 1.42
diff -u -3 -p -u -r1.42 Makefile.am
--- Makefile.am 21 Apr 2007 22:24:47 - 1.42
+++ Makefile.am 12 May 2007 10:37:08 -
@@ -60,6 +60,7 @@ gjdoc_DEPENDENCIES = lib-com-sun-javadoc
antlr.so
lib_com_sun_javadoc_la_SOURCES = \
+ src/com/sun/tools/javadoc/Main.java \
src/com/sun/javadoc/ClassDoc.java \
src/com/sun/javadoc/ConstructorDoc.java \
src/com/sun/javadoc/Doc.java \
@@ -369,10 +370,11 @@ $(lib_gnu_classpath_tools_gjdoc_la_GENSO
$(ANTLR) -o gnu/classpath/tools/gjdoc/expr $<
com-sun-javadoc-$(VERSION).jar: classes $(com_sun_javadoc_jar_CLASSES)
- $(JAR) cf $@ -C classes com/sun/javadoc
+ $(JAR) cf $@ -C classes com/sun/javadoc
+ $(JAR) uf $@ -C classes com/sun/tools/javadoc
com-sun-tools-doclets-Taglet-$(VERSION).jar: classes
$(com_sun_tools_doclets_Taglet_jar_CLASSES)
- $(JAR) cf $@ -C classes com/sun/tools
+ $(JAR) cf $@ -C classes com/sun/tools/doclets
gjdoc_resources = $(gnu_classpath_tools_gjdoc_jar_CSS)
$(gnu_classpath_tools_gjdoc_jar_DTDS) \
$(gnu_classpath_tools_gjdoc_jar_ENTS)
$(gnu_classpath_tools_gjdoc_jar_HTML) \
Index: NEWS
===
RCS file: /sources/classpath/gjdoc/NEWS,v
retrieving revision 1.12
diff -u -3 -p -u -r1.12 NEWS
--- NEWS21 Apr 2007 10:28:35 - 1.12
+++ NEWS12 May 2007 10:37:08 -
@@ -1,3 +1,7 @@
+Post 0.7.8
+
+* Add com.sun.tools.javadoc.Main to emulate javadoc.
+
New in release 0.7.8
* Naughty 1.5 release
Index: src/com/sun/tools/javadoc/Main.java
===
RCS file: src/com/sun/tools/javadoc/Main.java
diff -N src/com/sun/tools/javadoc/Main.java
--- /dev/null 1 Jan 1970 00:00:00 -
+++ src/com/sun/tools/javadoc/Main.java 12 May 2007 10:37:08 -
@@ -0,0 +1,9 @@
+package com.sun.tools.javadoc;
+
+public class Main
+{
+public static void main(String[] args)
+{
+ gnu.classpath.tools.gjdoc.Main.main(args);
+}
+}
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-melech (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gjdoc depends on:
ii antlr 2.7.6-10 language tool for constructing rec
ii debhelper 5.0.61helper programs for debian/rules
ii gij4:4.3-1 The GNU Java bytecode interpreter
ii gij-4.3 [java2-runtime 4.3-20080202-1The GNU Java bytecode interpreter
ii java-gcj-compat-headle 1.0.77-4 Java runtime environment using GIJ
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libgcc11:4.3-20080116-1 GCC support library
ii libgcj-bc 4.3-20070902-0Link time only library for use wit
ii libgcj9-0 4.3-20080202-1Java runtime library for use with
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
gjdoc recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465390: nethack-common: possible to blow horn while being strangled
Package: nethack-common Version: 3.4.3-10.3 Severity: normal While wearing an amulet of strangulation, it is impossible to eat or drink anything; nor is it possible to use breath weapons while polymorphed into D, or other similar actions. This would appear to indicate that the character's entire breathing action is stopped by the amulet. However, it is still possible to play horns while being strangled. This seems inconsistent, as playing horns generally requires blowing into them. Expected behavior: it should be impossible to play a horn while strangled. ---> Drake Wilson -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.2 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nethack-common depends on: ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy ii debianutils 2.28.2 Miscellaneous utilities specific t ii libc6 2.7-6 GNU C Library: Shared libraries Versions of packages nethack-common recommends: ii nethack-console 3.4.3-10.3 Text-based overhead view D&D-style -- debconf information: nethack-common/recover-setgid: false nethack-common/backup-incompatible: backup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461621: 10th Anniversary Donation!!!
You have been donated £1,000,000.00GBP,By the PRINCESS DIANA MEMORIAL FOUNDATION.You are to contact Mr Richie Dolce on [EMAIL PROTECTED] immediately. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465253: Confirmation
Hi, Just wanted to confirm that the problem exists on my machine too. I am using Sid with all updates as of Feb. 11th, 2008. Thanks, situert Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465387: no way to install a game
Package: goplay Version: 0.2-1+b1 Severity: wishlist It should be possible to click to install a game. If that feature is added, goplay would be close to ready to be included in the desktop task. I'm not sure what would be the best way to handle the installation. "synaptic install " would be great, except synaptic doesn't support that yet. ;-) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages goplay depends on: ii apt [libapt-pkg-libc6. 0.7.10Advanced front-end for dpkg ii debtags1.7.3+b3 Enables support for package tags ii ept-cache 0.5.14Commandline tool to search the pac ii games-thumbnails 20070824 thumbnails of games in Debian ii libc6 2.7-6 GNU C Library: Shared libraries ii libept00.5.14High-level library for managing De ii libfltk1.1 1.1.7-7 Fast Light Toolkit - shared librar ii libgcc11:4.3-20080202-1 GCC support library ii libstdc++6 4.3-20080202-1The GNU Standard C++ Library v3 ii libxapian151.0.5-1 Search engine library ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime goplay recommends no packages. -- no debconf information -- see shy jo signature.asc Description: Digital signature
Bug#465388: wmacpi doesn't work with sysfs
Package: wmacpi Version: wmacpi-2.2~rc1 wmacpi fails to give any battery data on my system (2.6.24.2 from kernel.org, also tested on 2.6.24.1). This seems to be due to the fact that wmacpi attempts to access BAT1/energy_*, while these values are not available on my laptop. $ ls /sys/class/power_supply/BAT1 alarm current_now power technology voltage_now charge_full devicepresenttype charge_full_design manufacturer status uevent charge_now model_namesubsystem voltage_min_design -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#31396: Best day yet
Tried, tested and prooven http://whineset.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465386: checkbashisms: please detect some $VARS which are bashisms + Here Strings + etc
Package: devscripts Version: 2.10.17 Severity: wishlist User: [EMAIL PROTECTED] Usertags: checkbashisms Please add the following bashisms based on the next test: $ cat bashisms #!/bin/sh echo $SECONDS echo $OSTYPE echo $HOSTTYPE echo $MACHTYPE echo $HOSTNAME echo $DIRSTACK echo $EUID echo $LINENO #posh _DOES_ display this one echo 'die!' > /dev/tcp/domain.tld/80 #Debian's bash doesn't support it, but... echo 'die!' > /dev/udp/domain.tld/21 #Debian's bash doesn't support it neither cat <<< 'echo moo!' bash <<< 'echo foo' $ bash bashisms 0 linux-gnu i486 i486-pc-linux-gnu nova /tmp 1000 9 bashisms: line 10: /dev/tcp/domain.tld/80: No such file or directory bashisms: line 11: /dev/udp/domain.tld/21: No such file or directory echo moo! foo $ zsh bashisms 0 linux-gnu i686 1000 9 bashisms:10: no such file or directory: /dev/tcp/domain.tld/80 bashisms:11: no such file or directory: /dev/udp/domain.tld/21 echo moo! foo $ ksh bashisms 0.001 9 echo moo! foo $ posh bashisms 9 bashisms:10: cannot create /dev/tcp/domain.tld/80: No such file or directory bashisms:11: cannot create /dev/udp/domain.tld/21: No such file or directory bashisms:12: syntax error: `< ' unexpected $ dash bashisms bashisms: 10: cannot create /dev/tcp/domain.tld/80: Directory nonexistent bashisms: 11: cannot create /dev/udp/domain.tld/21: Directory nonexistent bashisms: 12: Syntax error: redirection unexpected Kind regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375277: double console messages about card reader
> "ma" == maximilian attems <[EMAIL PROTECTED]> writes: ma> hotplug is gone inbetween. ma> can we have an update on that issue for uname > 2.6.22 ma> thanks OK but Preparing to replace linux-image-2.6.24-1-686 2.6.24-2 (using .../linux-image-2.6.24-1-686_2.6.24-4_i386.deb) ... The directory /lib/modules/2.6.24-1-686 still exists. Continuing as directed. Done. Unpacking replacement linux-image-2.6.24-1-686 ... Setting up linux-image-2.6.24-1-686 (2.6.24-4) ... Running depmod. Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: unrecognised device: /sys/devices/LNXSYSTM:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00 yaird error: unrecognised device: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/LNXVIDEO:00 yaird error: there were errors in this run, aborting now without output (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.24-1-686 (--configure): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.24-1-686 E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#460921: goplay in tasksel would be blocked by this
I'm considering including goplay in the desktop task in tasksel, with the idea that some desktop users like to play games and might want to use it to find some to play. This bug is one of the blockers for me doing that, since a goplay that doesn't work out of the box won't be very useful to those users. Would it be possible to have a suid helper program that can ept-cache reindex? Then goplay could call it on startup (with a nice progress bar, since it can be slow..). -- see shy jo signature.asc Description: Digital signature
Bug#465177: FTBFS: configure: error: unable to configure inotify support
On Monday 11 February 2008 7:59:40 pm Sergey Jin' Bostandzhyan wrote: > Hi, > > On Mon, Feb 11, 2008 at 06:54:10PM -0500, Andres Mejia wrote: > > > Well, if you are sure that the target machines *do have inotify > > > support* the only thing that could help is the config.log output of the > > > failed configure process. > > > > The best thing toward logs are located at > > http://buildd.debian.org/pkg.cgi?pkg=mediatomb . > > That's the stdout of configure, what I am looking for is the config.log > file that is created by configure during the process, but this is not there > because everything is purged after the build. Any idea if we can get it? > > > > Then it should work; we do check the headers and then we run some small > > > test code which is calling inotify_init(). If the inotify_init() > > > function returns -1 (error) we will compile without inotify support; > > > however - if the --enable-inotify parameter was specified configure > > > will abort because it can not do what the user wanted. > > > > > > So the question: is inotify really working on those systems? > > > > I'm finding this behavior strange. Ubuntu accepted mediatomb into their > > archive, yet now the powerpc architecture goes past the inotify check > > just fine, but the i386 and amd64 architectures do not. Take a look at > > https://launchpad.net/ubuntu/+source/mediatomb/0.10.0.dfsg1-1/ > > This is indeed very strange, it must be somehow related to the setup of > the particular machine. What I see is that the default inotify header is > not working, then we are retrying with our own and then it is failing. > > However, without seeing the config.log file I can not say anything... > > > I know for the case of the i386, I've been able to successfully build > > packages using pbuilder. > > Yes, I know, Leo has also been using pbuilder to create our custom .deb > packages and we did not have any problems with inotify. > > Is the exact environment that those machines are using available somewhere? > Can we reproduce the problem somehow? > > > Also, it looks like the Ubuntu buildd machines are giving a different > > error, for architectures that run the inotify check sucessfully. > > Indeed, it seems that the build runs through but there is something wrong > with the package, can't say much there either - I have no experience with > .deb packages. > > Kind regards, > Jin I've investigated this some more and found that the inotify-tools package fails the test to see if sys/inotify.h actually works for the powerpc and ia64 architectures as well, yet the build continues for that package, unlike in mediatomb. Here's the difference between the two packages' configure.ac *mediatomb's configure.ac* dnl The check below was inspired by configure.ac from the inotify tools dnl package, see the "Acknowledgements" section in our README file for more dnl information. CXXFLAGS="$CXXFLAGS $INOTIFY_CXXFLAGS" AC_MSG_CHECKING([whether sys/inotify.h works]) AC_RUN_IFELSE( AC_LANG_PROGRAM([[#include ]], [[return (-1 == inotify_init());]] ), [ AC_MSG_RESULT([yes]); AC_DEFINE([SYS_INOTIFY_H_OK],[1],[sys/inotify.h exists and works correctly])], [ AC_MSG_RESULT([no, using own inotify headers]) AC_MSG_CHECKING([whether inotify-nosys.h works]) AC_RUN_IFELSE( AC_LANG_PROGRAM([[#include "src/inotify-nosys.h"]], [[return (-1 == inotify_init());]] ), [ AC_MSG_RESULT([yes]); INOTIFY_OK=yes ], [ AC_MSG_RESULT([no, disabling inotify support]) INOTIFY_OK=missing ]) ]) fi *inotify-tools configure.ac* # Checks for header files. AC_CHECK_HEADERS([sys/inotify.h mcheck.h]) AC_LANG(C) AC_MSG_CHECKING([whether sys/inotify.h actually works]) AC_RUN_IFELSE( AC_LANG_PROGRAM([[#include ]], [[return (-1 == inotify_init());]] ), [AC_MSG_RESULT([yup]); AC_DEFINE([SYS_INOTIFY_H_EXISTS_AND_WORKS],[1], [sys/inotify.h exists and works correctly])], [AC_MSG_RESULT([nope, using own inotify headers])] ) Perhaps I'm wrong about what kernel each buildd machine is using. This would explain why this check fails on these architectures, but I can't find a straight answer. Sven, do you know the answer to this? The buildd machines use sbuild, which uses debootstrap for creating the chroot environment, so I'm sure at least the latest version of linux-libc-dev is installed. In case some buildd machines don't support inotify, the check to see if inotify works should be left out. -- Regards, Andres -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a sub
Bug#465385: Missing debian/control file in package loop-aes-source
Package: loop-aes-source Version: 3.2b-4 Severity: grave Justification: Makes the package unusable Hi, I am using Sid with the latest updates as of Feb 11th, 2008. I tried to build loop-aes kernel modules. I installed loop-aes-source and tried two methods: 1) using module assistant, and 2) using make-kpkg. Both of them fail to build the kernel module because the file debian/control is missing from the package. The mentioned file exists in Etch version of the package. Please rectify this problem. Thank you for your attention. Regards, situert Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445422: swaml: Wrong dependency on python2.4-rdflib
Hi,
Here is an NMU that should fix this bug. (Well if fixes the depends but
it should also allow swaml to run under 2.5).
I'm not absolutely positive but I do not believe a multi-build package
is necessary here.
Thanks,
Barry deFreese
diff -u swaml-0.0.5/debian/changelog swaml-0.0.5/debian/changelog
--- swaml-0.0.5/debian/changelog
+++ swaml-0.0.5/debian/changelog
@@ -1,3 +1,12 @@
+swaml (0.0.5-2.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Depend python-rdflib instead of python2.4-rdflib. (Closes: #445422).
+ * pyversions 2.4 -> 2.4-.
+ * Update .py scripts to use python, not python2.4.
+
+ -- Barry deFreese <[EMAIL PROTECTED]> Mon, 11 Feb 2008 22:51:06 -0500
+
swaml (0.0.5-2) unstable; urgency=low
* Added debian/watch file.
diff -u swaml-0.0.5/debian/control swaml-0.0.5/debian/control
--- swaml-0.0.5/debian/control
+++ swaml-0.0.5/debian/control
@@ -7,7 +7,7 @@
Package: swaml
Architecture: all
-Depends: ${python:Depends}, python2.4-rdflib
+Depends: ${python:Depends}, python-rdflib
Recommends: buxon
Description: Semantic Web Archive of Mailing Lists
SWAML reads a collection of email messages stored in a mailbox
diff -u swaml-0.0.5/debian/pyversions swaml-0.0.5/debian/pyversions
--- swaml-0.0.5/debian/pyversions
+++ swaml-0.0.5/debian/pyversions
@@ -1 +1 @@
-2.4
+2.4-
only in patch2:
unchanged:
--- swaml-0.0.5.orig/swaml.py
+++ swaml-0.0.5/swaml.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python2.4
+#!/usr/bin/env python
# -*- coding: utf8 -*-
#
# SWAML
Bug#465384: devscripts: [uscan] Inconsistencies with a remote website, not sure where the problem is.
Package: devscripts Version: 2.10.13 Severity: normal Dear uscan maintainers, in the Debian-Med packaging team, we have a problem with a watch file that only works the second time it is used. It is possible that the problem is the upstream website, but just in case, can you have look to the symptoms? You can find them in the following mails: http://lists.debian.org/msgid-search/[EMAIL PROTECTED] http://lists.debian.org/msgid-search/[EMAIL PROTECTED] If the problem comes from the remote website and you know that is faulty, we will forward this information upstream. Many thanks in advance, -- Charles Plessy, Debian-Med packaging team, Wakō, Saitama, Japan -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages devscripts depends on: ii debianutils 2.28.2 Miscellaneous utilities specific t ii dpkg-dev 1.14.16.6 package building tools for Debian ii libc6 2.7-4 GNU C Library: Shared libraries ii perl 5.8.8-12 Larry Wall's Practical Extraction ii sed 4.1.5-5The GNU sed stream editor Versions of packages devscripts recommends: ii fakeroot 1.8.10 Gives a fake root environment -- no debconf information
Bug#465275: [Pkg-electronics-devel] Bug#465275: Bug#465275: Gerbv 2.0.1 installs its OWN icon and .desktop file, fixes for packaging attached
On Tue, Feb 12, 2008 at 09:08:04AM +0530, Ramakrishnan Muthukrishnan wrote: > Peter Clifton <[EMAIL PROTECTED]> writes: > > > Hi, I've attached a debdiff with some improvements to the packaging for > > 2.0.1. This version now installs its own icons and .desktop file, so we > > don't need to install them manually from debian/rules any more. > > > > (It uses /usr/share/icons/hicolor/ to install various icons sizes, > > so we also need a call do dh_icons to update the icon cache after > > install / removal.) > > > > A final improvement, is that since extra-xdg-menus was approved for > > Debian, we can "Depends" on that to get an "Electronics" menu. This > > makes the unnecessary the inclusion of a bogus "Education" category, so > > I've included a patch to remove that. > > Thanks. I have applied your patch. WIll be uploaded in afew minutes. Hi, I think Depends is too strong for extra-xdg-menus, since it is not really a dependency. Recommends is appropriate, and aptitude and apt-get will install Recommends by default now. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#457503: gnumail.app: segfault on selecting preferences
On Sat, 22 Dec 2007 23:03:27 +0100 Xavier Brochard <[EMAIL PROTECTED]> wrote: > Wanted to configure a freshly installed GNUMail, I clicked on > preference and it crash. Hi Xavier, I made a change to GNUMail, which may or may not fix this crash. Can you try out the GNUMail package from experimental, and see if it still crashes when you click on preferences? http://packages.debian.org/experimental/amd64/gnumail.app/download Thanks -- Hubert Chathi <[EMAIL PROTECTED]> -- Jabber: [EMAIL PROTECTED] PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/ Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465372: ITP: cuteflow -- web-based open source document workflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: wnpp Severity: wishlist Package: cuteflow URL: http://www.cuteflow.org/ Version: 2.10.0 License: BSD Copyright: Timo Haberkern <[EMAIL PROTECTED]> Cuteflow is a web-based open source document circulation and workflow system. Users are able to define "documents" which are send step by step to every station/user in a list. It's an electronical way for doing document circulations. All operations like starting a workflow, tracking, workflow-definition or status observation can be done within a comfortable and easy to use webinterface. I'll be working on this package, Ailé -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHsRqdrL0qvlgvP4gRAkFKAJ9TXxpIYTw+L5KN7/Qv82C2l0os4wCfWHkA fZlsZqMSTK1B46DrMTsCAXI= =OFID -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465369: ITP: golearn -- Debian educational browser
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard <[EMAIL PROTECTED]> * Package name: golearn Version : 0.2 Upstream Author : Enrico Zini <[EMAIL PROTECTED]> & Miriam Ruiz <[EMAIL PROTECTED]> * URL : http://packages.debian.org/goplay * License : GPL-2+ Programming Lang: C++ Description : Debian educational browser GoLearn! is a Graphical User Interface (GUI) that uses DebTags for easily finding educational programs in Debian. The program uses FLTK for handling the widgets, and libept as the backend for retrieving the data. . It is a simple rip-off of the excellent GoPlay!, hacked to limit to the debtag "use::learn" and optionally filter on "field::" (instead of doing both with "game::"). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465367: unclean purge
Package: mailman Severity: minor Upon purge saw dpkg - warning: while removing mailman, directory ... not empty so not removed. for /usr/lib/mailman/pythonlib/email /usr/lib/mailman/pythonlib /usr/lib/mailman/bin /usr/lib/mailman/Mailman/Gui /usr/lib/mailman/Mailman/Queue /usr/lib/mailman/Mailman/Handlers /usr/lib/mailman/Mailman/Archiver /usr/lib/mailman/Mailman/Logging /usr/lib/mailman/Mailman /usr/lib/mailman /var/lib/mailman/qfiles /var/lib/mailman/lists /var/lib/mailman/archives/private /var/lib/mailman/archives /var/lib/mailman Some of these seem justified to protect one's data, but not all. Perhaps print a message upon purge about what is intentional or not. Not sure what piuparts would say. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461621: 10th Anniversary Donation/Grant
You have been donated £1,000,000.00GBP,By the PRINCESS DIANA MEMORIAL FOUNDATION.You are to contact Mr Richie Dolce on [EMAIL PROTECTED] immediately. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#449350: No reason to keep debmirror out of testing
Luk Claes wrote: Alexander E. Patrakov wrote: you have blocked debmirror out of testing due to bug #449350. However, with a fully up-to-date Lenny install, I can't reproduce the bug (even the original testcase), and therefore it definitely doesn't make the package unusable for me. The original submitter did find a workaround, so the package isn't unusable for him, too. Thus, the bug is either not RC at all, or belongs to a different package (and the proper title is "package ZZZ version YYY breaks debmirror"). Please reconsider your decision to block the package from testing. Why is this information only added to the bug log after it has been removed from testing? Because I don't watch BTS for packages that work fine. In other words, I didn't know that a release-critical bug is (wrongly) reported until debmirror ended up in "local & obsolete packages" section in aptitude due to it. -- Alexander E. Patrakov -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465366: blacs-mpi -- Please rebuild with gfortran and new lam, mpich
Package: blacs-mpi Version: 1.1-27 Severity: important Tags: patch User: [EMAIL PROTECTED] Usertags: gfortran Hi! I would request you to please shift Build-Depends to use the new gfortran based lam and mpich packages in order to phase out packages dependent on the old g2c (g77). In this regard, I would request you to refer to: http://wiki.debian.org/GfortranTransition You may wish to rename the package in order to provide for parallel installability of the g77 and gfortran based blacs-mpi packages, if you choose to upload to unstable. Attached is a tested patch which does the needful, which you may use to base your change. Thank you. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 diff -u blacs-mpi-1.1/Bmake.inc blacs-mpi-1.1/Bmake.inc --- blacs-mpi-1.1/Bmake.inc +++ blacs-mpi-1.1/Bmake.inc @@ -109,7 +109,7 @@ # setting for your platform, compile and run BLACS/INSTALL/xintface. # Choices are: Add_, NoChange, UpCase, or f77IsF2C. # --- - INTFACE = -Df77IsF2C + INTFACE = -DAdd_ # INTFACE = -DAdd_ # @@ -217,8 +217,8 @@ # optimization. This is the F77NO_OPTFLAG. The usage of the remaining # macros should be obvious from the names. #= - F77= g77 - F77NO_OPTFLAGS = $(FPIC) -fno-globals -fno-f90 -fugly-complex -w + F77= gfortran + F77NO_OPTFLAGS = $(FPIC) -w F77FLAGS = $(F77NO_OPTFLAGS) -O4 F77LOADER = $(F77) F77LOADFLAGS = diff -u blacs-mpi-1.1/debian/changelog blacs-mpi-1.1/debian/changelog --- blacs-mpi-1.1/debian/changelog +++ blacs-mpi-1.1/debian/changelog @@ -1,3 +1,10 @@ +blacs-mpi (1.1-27.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * gfortran. + + -- Kumar Appaiah <[EMAIL PROTECTED]> Mon, 11 Feb 2008 21:44:41 +0530 + blacs-mpi (1.1-27) unstable; urgency=low * New maintainer. Closes: #335008 diff -u blacs-mpi-1.1/debian/control blacs-mpi-1.1/debian/control --- blacs-mpi-1.1/debian/control +++ blacs-mpi-1.1/debian/control @@ -3,7 +3,7 @@ Priority: extra Maintainer: Muammar El Khatib <[EMAIL PROTECTED]> Standards-Version: 3.7.2 -Build-Depends: debhelper (>= 4), lam4-dev (>= 7.1.1-3.2), libmpich1.0-dev (>= 1.2.7-1), g77 +Build-Depends: debhelper (>= 4), lam4-dev (>= 7.1.1-3.2), libmpich1.0-dev (>= 1.2.7-1), gfortran Package: blacs1-mpich Section: libs only in patch2: unchanged: --- blacs-mpi-1.1.orig/TESTING/s.sh +++ blacs-mpi-1.1/TESTING/s.sh @@ -0,0 +1 @@ +gfortran -o /tmp/blacs-mpi/blacs-mpi-1.1/TESTING/EXE/xFbtest_MPI-LINUX-0-static-lam blacstest.o btprim_MPI.o tools.o /tmp/blacs-mpi/blacs-mpi-1.1/LIB/blacsF77init_MPI-LINUX-0.a /tmp/blacs-mpi/blacs-mpi-1.1/LIB/blacs_MPI-LINUX-0.a /tmp/blacs-mpi/blacs-mpi-1.1/LIB/blacsF77init_MPI-LINUX-0.a /tmp/blacs-mpi/blacs-mpi-1.1/LIB/*.a -L/usr/lib/lam/lib -llam signature.asc Description: Digital signature
Bug#173677: A Rose To Say...
Sweetest Things Aren't Things! http://24.151.255.140/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465275: [Pkg-electronics-devel] Bug#465275: Gerbv 2.0.1 installs its OWN icon and .desktop file, fixes for packaging attached
Peter Clifton <[EMAIL PROTECTED]> writes: > Hi, I've attached a debdiff with some improvements to the packaging for > 2.0.1. This version now installs its own icons and .desktop file, so we > don't need to install them manually from debian/rules any more. > > (It uses /usr/share/icons/hicolor/ to install various icons sizes, > so we also need a call do dh_icons to update the icon cache after > install / removal.) > > A final improvement, is that since extra-xdg-menus was approved for > Debian, we can "Depends" on that to get an "Electronics" menu. This > makes the unnecessary the inclusion of a bogus "Education" category, so > I've included a patch to remove that. Thanks. I have applied your patch. WIll be uploaded in afew minutes. -- Ramakrishnan VU3RDD <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465365: grub-ieee1275: grub-mkdevicemap writes a device.map with "No aliases found"
Package: grub-ieee1275 Version: 1.96+20080210-1 Severity: important grub-mkdevicemap ends without a failure notice but the file writes a device.map with "No aliases found" -- Package-specific info: *** BEGIN /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec 0 0 none /proc proc rw,nosuid,nodev,noexec 0 0 udev /dev tmpfs rw 0 0 /dev/mapper/pink-root / ext3 rw,noatime,errors=remount-ro,data=ordered 0 0 /dev/mapper/pink-root /dev/.static/dev ext3 rw,errors=remount-ro,data=ordered 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid 0 0 usbfs /proc/bus/usb usbfs rw,nosuid,nodev,noexec 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,nosuid,noexec 0 0 fusectl /sys/fs/fuse/connections fusectl rw 0 0 /dev/hda1 /boot ext2 rw,noatime 0 0 /dev/mapper/pink-tmp /tmp ext3 rw,noatime,data=ordered 0 0 /dev/mapper/pink-usr /usr ext3 rw,nodev,noatime,data=ordered 0 0 /dev/mapper/pink-var /var ext3 rw,nodev,noatime,data=ordered 0 0 /dev/mapper/pink-home /home ext3 rw,nosuid,nodev,noatime,user_xattr,acl,data=ordered 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec 0 0 /dev/sda5 /media/data ext3 rw,nosuid,nodev,data=ordered 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (No aliases found.) /dev/hda (No aliases found.) /dev/sda *** END /boot/grub/device.map -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (50, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.24-1-powerpc Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub-ieee1275 depends on: ii base-files4.0.2 Debian base system miscellaneous f ii bc1.06.94-3 The GNU bc arbitrary precision cal ii libc6 2.7-6 GNU C Library: Shared libraries ii libncurses5 5.6+20080203-1 Shared libraries for terminal hand ii powerpc-ibm-utils 1.1.0-1utilities for maintenance of IBM P ii powerpc-utils 1.1.3-22 Various utilities for Linux/PowerP grub-ieee1275 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464414: 1.3: does not install
Same here. AMD64 box, 386 chroot, the install just hangs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464726: More info
/etc/mahara/servername.conf contains the following: 8< # DO NOT EDIT THIS FILE! It is managed by debconf! # It will be overwritten the next time this package is configured. # Use 'dpkg-reconfigure mahara-apache2' instead. ServerName localhost 8< Note that if I do `dpkg-reconfigure -plow mahara-apache2`, I'm only asked one question about a redirection, and even if I let the answer empty, the ServerName remains "localhost". I'm no expert at apache configuration semantics, but it seemed to me that having a section should change apache's configuration globally (thus srewing the local admin's configuration). That's why most other files in /etc/apache2/conf.d just define an Alias (sometimes even commented) and change configuration with Directory sections. Doubtfully, Pierre -- [EMAIL PROTECTED] OpenPGP 0xD9D50D8A signature.asc Description: Digital signature
Bug#31396: reply:
Tried, tested and prooven http://whineset.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465364: checkbashisms: false positive '((' should be '$(('
Package: devscripts
Version: 2.10.16
User: [EMAIL PROTECTED]
Usertags: checkbashisms
Running checkbashisms on the next piece of code (from
sysv-rc_2.86.ds1-53_all.deb's /etc/init.d/rc)
produces a false positive "'((' should be '$(('" message.
---
#!/bin/sh
progress_size=$(((100 - $PROGRESS_STATE) / 3))
---
Test:
$ dash -c 'PROGRESS_STATE=20; progress_size=$(((100 - $PROGRESS_STATE) / 3));
echo $progress_size'
26
$ posh -c 'PROGRESS_STATE=20; progress_size=$(((100 - $PROGRESS_STATE) / 3));
echo $progress_size'
26
$ zsh -c 'PROGRESS_STATE=20; progress_size=$(((100 - $PROGRESS_STATE) / 3));
echo $progress_size'
26
$ bash -c 'PROGRESS_STATE=20; progress_size=$(((100 - $PROGRESS_STATE) / 3));
echo $progress_size'
26
TIA.
Cheers,
--
Atomo64 - Raphael
Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#432932: #432932: adding security tag
tag 432932 security thanks Anyone feel free to correct me if I'm wrong but this looks like a security bug. Regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465259: Oops---previous title change misleading
Dear Debian: I was a bit quick on the `send' button there---ktorrent is a red herring in this context. What I'm after is a title which, when displayed in the Found/Fixed list, allows me to decide whether I'm willing to put up with the bug. Looking through libqt3-mt's full bug list, it looks as if something like Causes ``undefined symbol: lstat64'' error in other apps. would be in order. Best wishes, Max Hyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465363: gnash: Cross Browser action
Package: gnash Version: 0.8.1~rc.070818-2.1+b1 Severity: critical Justification: breaks unrelated software Please open http://www.discus-fish24.de/ in firefox, then open the same site in konqueror if you klick in konqueror on one of the upper right buttons, the linked sites will be loaded in firefox by adding tabs here and load the link in firefox. this seem some kind of cross-browser bug. i dont no how to name this correctly. but i think in some circumstances critical. thanks, J. Dietrich Boock -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (995, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-mppe (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnash depends on: ii gnash-common 0.8.1~rc.070818-2.1+b1 free Flash movie player - common f ii libc6 2.7-6 GNU C Library: Shared libraries ii libgcc1 1:4.3-20080202-1 GCC support library ii libglib2.0-0 2.14.5-2 The GLib library of C routines ii libgtk2.0-0 2.12.7-1 The GTK+ graphical user interface ii libstdc++64.3-20080202-1 The GNU Standard C++ Library v3 gnash recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465177: Fwd: Re: Bug#465177: FTBFS: configure: error: unable to configure inotify support
Hello Sven, I don't know if you were tracking this, but there's this bug where certain architectures are failing to build mediatomb. Now as I understand it, the buildd machines builds packages in a chroot environment, with all packages found under unstable (the kernel, gcc, etc.). Isn't this correct? Here I'm forwarding a mail to you from one of the developers of Mediatomb. Can you help with this? -- Forwarded Message -- Subject: Re: Bug#465177: FTBFS: configure: error: unable to configure inotify support Date: Monday 11 February 2008 From: Sergey Jin' Bostandzhyan <[EMAIL PROTECTED]> To: Andres Mejia <[EMAIL PROTECTED]> Hi, On Mon, Feb 11, 2008 at 06:54:10PM -0500, Andres Mejia wrote: > > Well, if you are sure that the target machines *do have inotify support* > > the only thing that could help is the config.log output of the failed > > configure process. > > The best thing toward logs are located at > http://buildd.debian.org/pkg.cgi?pkg=mediatomb . That's the stdout of configure, what I am looking for is the config.log file that is created by configure during the process, but this is not there because everything is purged after the build. Any idea if we can get it? > > Then it should work; we do check the headers and then we run some small > > test code which is calling inotify_init(). If the inotify_init() function > > returns -1 (error) we will compile without inotify support; however - if > > the --enable-inotify parameter was specified configure will abort because > > it can not do what the user wanted. > > > > So the question: is inotify really working on those systems? > > I'm finding this behavior strange. Ubuntu accepted mediatomb into their > archive, yet now the powerpc architecture goes past the inotify check just > fine, but the i386 and amd64 architectures do not. Take a look at > https://launchpad.net/ubuntu/+source/mediatomb/0.10.0.dfsg1-1/ This is indeed very strange, it must be somehow related to the setup of the particular machine. What I see is that the default inotify header is not working, then we are retrying with our own and then it is failing. However, without seeing the config.log file I can not say anything... > I know for the case of the i386, I've been able to successfully build packages > using pbuilder. Yes, I know, Leo has also been using pbuilder to create our custom .deb packages and we did not have any problems with inotify. Is the exact environment that those machines are using available somewhere? Can we reproduce the problem somehow? > Also, it looks like the Ubuntu buildd machines are giving a different error, > for architectures that run the inotify check sucessfully. Indeed, it seems that the build runs through but there is something wrong with the package, can't say much there either - I have no experience with .deb packages. Kind regards, Jin --- -- Regards, Andres -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464910: another report of this bug
http://lists.debian.org/debian-user/2008/02/msg01213.html -- see shy jo signature.asc Description: Digital signature
Bug#463071: laptops and fceu
Part of this bug is a mistake. I can indeed use fceu with my laptop, but for some silly reason the numlock key on my thinkpad (I'll look into this separately) never lights up when in use. That said, the default key configuration still makes it difficult to use on a laptop because of having to use the numlock to access the configured buttons required. I'd have to switch in/out of numlock mode as I changed applications. Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465352: rm lilypond for sparc in unstable
Package: ftp.debian.org Severity: normal --- Please enter the report below this line. --- Please remove the lilypond package for sparc in unstable. I believe it's 2.10.29-1. Guile is no longer able to support sparc (#460617), and the build failure is preventing lilypond from entering testing. --- System information. --- Architecture: i386 Kernel: Linux 2.6.24-1-686 Debian Release: lenny/sid 500 unstablemirrors.kernel.org 4606 500 stable security.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#445016: sources
Hi, On Sun, Feb 10, 2008 at 10:38:05PM +0100, Andrzej Zięba wrote: > Package: athcool > Version: 0.3.11-1.1 > > I have built the package from sources and I got executable that does not > need the libpci2. The problem is that the package does not build from > the sources without a problem. I had to add -lz to the LIBS variable in > the makefile to make it link properly. Thanks, but I don't think this is the correct way to solve this problem. Athcool does not by itself use (any symbol from) libz; only libpci does. As long as libpci was available as a shared library, it was no problem, since shared libraries support dependencies. But for some reason, the pciutils maintainer has decided not to distribute this shared library anymore. The side effect is that the programs that want to use libpci now are supposed to "guess" what libraries libpci requires. I don't think this is correct. Fortunately, pciutils' upstream provide a libpci.pc pkgconfig file that can be used to find the correct dependencies for libpci. But for some reason the maintainer for pciutils does not distribute this file. Hence, I think the maintainer for pciutils should distribute this file in the pciutils-dev package (see bug #403181), and then I can use pkgconfig to generate the correct dependencies for athcool. Cheers, Nicolas
Bug#465169: linux-image-2.6.22-3-686: NFS causing a Null Pointer Oops that locks the machine up
On Sun, 10 Feb 2008, Paul Logasa Bogen II wrote: > Package: linux-image-2.6.22-3-686 > Version: 2.6.22-6 > Severity: normal > The machine will completely freeze up and the kern.log shows the following: > > Feb 9 22:23:29 twang kernel: BUG: unable to handle kernel NULL pointer > dereference at virtual address 006e > Feb 9 22:23:29 twang kernel: printing eip: > Feb 9 22:23:29 twang kernel: c017c070 > Feb 9 22:23:29 twang kernel: *pde = > Feb 9 22:23:29 twang kernel: Oops: [#1] > Feb 9 22:23:29 twang kernel: SMP > Feb 9 22:23:29 twang kernel: Modules linked in: nfs lockd nfs_acl sunrpc > autofs4 thermal fan button processor ac battery ipv6 dm_snapshot dm_mirror > dm_mod loop ide_cd cdrom generic tsdev intel_rng megaraid_mbox megaraid_mm > e1000 piix ide_core uhci_hcd usbcore ata_generic parport_pc parport serio_raw > floppy libata iTCO_wdt psmouse rtc sg e7xxx_edac edac_mc pcspkr ext3 jbd > mbcache sd_mod mptspi mptscsih mptbase scsi_transport_spi scsi_mod shpchp > pci_hotplug evdev > Feb 9 22:23:29 twang kernel: CPU:1 > Feb 9 22:23:29 twang kernel: EIP:0060:[]Not tainted VLI > Feb 9 22:23:29 twang kernel: EFLAGS: 00010206 (2.6.22-3-686 #1) > Feb 9 22:23:29 twang kernel: EIP is at graft_tree+0x22/0xc9 > Feb 9 22:23:29 twang kernel: eax: f19be9d8 ebx: d437bf2c ecx: > edx: d437bf2c > Feb 9 22:23:29 twang kernel: esi: ffec edi: ef14c3c0 ebp: > esp: d437bdf8 > Feb 9 22:23:29 twang kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: > 0068 > Feb 9 22:23:29 twang kernel: Process mount.nfs (pid: 31709, ti=d437a000 > task=c070 task.ti=d437a000) > Feb 9 22:23:29 twang kernel: Stack: ef14c3c0 d437bf2c cf618003 c017c3af > c03297c0 cf618003 > Feb 9 22:23:29 twang kernel: c017d399 c7458000 > ef14c3c0 cf618000 cf376000 0038b025 > Feb 9 22:23:29 twang kernel: d437be70 d437be78 > 017f f150b800 c027d5cf > Feb 9 22:23:29 twang kernel: Call Trace: > Feb 9 22:23:29 twang kernel: [] do_add_mount+0x86/0xfb > Feb 9 22:23:29 twang kernel: [] do_mount+0x647/0x69a > Feb 9 22:23:29 twang kernel: [] ip4_datagram_connect+0x2bf/0x314 > Feb 9 22:23:29 twang kernel: [] move_addr_to_user+0x39/0x50 > Feb 9 22:23:29 twang kernel: [] do_page_fault+0x2d0/0x57e > Feb 9 22:23:29 twang kernel: [] error_code+0x72/0x78 > Feb 9 22:23:29 twang kernel: [] atm_dev_register+0x26/0x1d4 > Feb 9 22:23:29 twang kernel: [] copy_mount_options+0x90/0x109 > Feb 9 22:23:29 twang kernel: [] sys_mount+0x77/0xb3 > Feb 9 22:23:29 twang kernel: [] sysenter_past_esp+0x6b/0xa1 > Feb 9 22:23:29 twang kernel: === > Feb 9 22:23:29 twang kernel: Code: c4 10 89 d0 5b 5e 5f 5d c3 57 89 c7 56 be > ea ff ff ff 53 8b 40 14 89 d3 83 78 30 00 0f 88 aa 00 00 00 8b 02 66 be ec ff > 8b 48 0c <0f> b7 41 6e 25 00 f0 00 00 3d 00 40 00 00 8b 47 10 0f 94 c2 8b > Feb 9 22:23:29 twang kernel: EIP: [] graft_tree+0x22/0xc9 SS:ESP > 0068:d437bdf8 > > > Paul Logasa Bogen II > System Administrator > Center for the Study of Digital Libraries > Texas A&M University please try 2.6.24-4 from unstable beside an important security fix it should have some nfs fixes, thanks for feedback. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465259: Change title to ``libktorrent-2.2.5.so: undefined symbol: lstat64''?
Dear Debian: On my current ``apt-get dist-upgrade'', the bug check tells me Retrieving bug reports... Done Parsing Found/Fixed information... Done serious bugs of libqt3-mt (3:3.3.7-9 -> 3:3.3.8b-1) #465259 - Same problem with ktorrent Not having seen the ktorrent bug list, this is moderately unhelpful... :-) Best wishes, Max Hyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465177: FTBFS: configure: error: unable to configure inotify support
Hi, On Mon, Feb 11, 2008 at 06:54:10PM -0500, Andres Mejia wrote: > > Well, if you are sure that the target machines *do have inotify support* > > the only thing that could help is the config.log output of the failed > > configure process. > > The best thing toward logs are located at > http://buildd.debian.org/pkg.cgi?pkg=mediatomb . That's the stdout of configure, what I am looking for is the config.log file that is created by configure during the process, but this is not there because everything is purged after the build. Any idea if we can get it? > > Then it should work; we do check the headers and then we run some small > > test code which is calling inotify_init(). If the inotify_init() function > > returns -1 (error) we will compile without inotify support; however - if > > the --enable-inotify parameter was specified configure will abort because > > it can not do what the user wanted. > > > > So the question: is inotify really working on those systems? > > I'm finding this behavior strange. Ubuntu accepted mediatomb into their > archive, yet now the powerpc architecture goes past the inotify check just > fine, but the i386 and amd64 architectures do not. Take a look at > https://launchpad.net/ubuntu/+source/mediatomb/0.10.0.dfsg1-1/ This is indeed very strange, it must be somehow related to the setup of the particular machine. What I see is that the default inotify header is not working, then we are retrying with our own and then it is failing. However, without seeing the config.log file I can not say anything... > I know for the case of the i386, I've been able to successfully build > packages > using pbuilder. Yes, I know, Leo has also been using pbuilder to create our custom .deb packages and we did not have any problems with inotify. Is the exact environment that those machines are using available somewhere? Can we reproduce the problem somehow? > Also, it looks like the Ubuntu buildd machines are giving a different error, > for architectures that run the inotify check sucessfully. Indeed, it seems that the build runs through but there is something wrong with the package, can't say much there either - I have no experience with .deb packages. Kind regards, Jin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#462178: please remove this package
Dear Holger, On 11/02/2008, Holger Levsen <[EMAIL PROTECTED]> wrote: > Dear Raphael, > > > This package is being tracked by me > > I saw your mail to this bug, but I consider QA work team work :-) Sure it is :) > > > and its removal will be requested after > > giving a grace period of time (more than one week) so there are more > > chances for people to adopt it. > > I orphaned the package just a few days ago, so please wait a little bit > > more. > > Why? Did you look at http://bugs.debian.org/230358 ? The package does not work > at all with a 2.6 kernel. A 2.4 kernel was last shipped with sarge, so there > is absolutly no point in keeping it any day longer in sid. But if you re-read the bug report you will see that the necessary changes to fix it aren't many (but I should probably reconsider that because of /proc not existing in newer kernels, starting with .24?) > > > Normally package removals should not be requested before two months since > > the package has been orphaned. In the case of this package I'll request its > > removal within two weeks. > > As you wrote: "normally"... > > This package should not have been part of the etch release, so it's pointless > to wait any day longer. Heck, you could even request its removal from > stable :-) I've already requested its removal from stable :) I don't see any real problem on keeping this report a few more days on wnpp to give people the opportunity to see it is up for adoption. IMO some people prefer to fix an existing package than to 'Debianise' from scratch, hence my desire to keep it a few more days. But if you believe it really makes no sense at all to keep the report open on wnpp feel free to reassign it to ftp.debian.org with a correct removal request subject and CC me so I update packages-actions.txt > > > regards, > Holger > > Kind regards, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html Say NO to Microsoft Office broken standard. See http://www.noooxml.org/petition -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465307: sonata: Sonata fails to start with a mp3 url on the net
Hi On Mon, 11 Feb 2008 20:07:39 +0100 Eric Gianquinto <[EMAIL PROTECTED]> wrote: > Sonata fails to start with a mp3 url on the net in the playlist with the > following error message: > > [EMAIL PROTECTED]:~$ sonata > Traceback (most recent call last): > File "/usr/bin/sonata", line 47, in ? > app = sonata.Base() > File "/usr/lib/python2.4/site-packages/sonata.py", line 1149, in __init__ > self.updatedb(None) > File "/usr/lib/python2.4/site-packages/sonata.py", line 4595, in updatedb > self.iterate_now() > File "/usr/lib/python2.4/site-packages/sonata.py", line 1784, in iterate_now > self.iterate() > File "/usr/lib/python2.4/site-packages/sonata.py", line 1741, in iterate > self.handle_change_status() > File "/usr/lib/python2.4/site-packages/sonata.py", line 3368, in > handle_change_status > if self.scrob_playing_duration > 4 * 60 or self.scrob_playing_duration > > int(self.prevsonginfo.time)/2: > File "/usr/lib/python2.4/site-packages/mpdclient3.py", line 311, in > __getattr__ > raise AttributeError > AttributeError I can not reproduce this with 1.4.2 which is currently in unstable. Can you reproduce it there? -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Bug#464919: Fails to boot (reboots after BIOS data check)
On Sat, 09 Feb 2008, Jacek Politowski wrote: > Package: linux-image-2.6.24-1-686 > Version: 2.6.24-3 > Severity: important > > Machine reboots right after booting - after "the dots" and "BIOS data > check successful.", before "Uncompressing kernel". > > It didn't occur in 2.6.24-2 and it doesn't occur in 2.6.22-3. > > I'm running it on Intel Core2Duo E6600 on ASRock 775Dual-VSTA (VIA > chipset mainboard). I haven't changed CMOS settings or added any > hardware recently. > try to manualy rerun lilo, does that help? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464933: linux-image-2.6.24-1-amd64: r8169 doesn't work with 2.6.24 (regression from 2.6.23)
On Sat, 09 Feb 2008, Jeroen Dekkers wrote: > Package: linux-image-2.6.24-1-amd64 > Version: 2.6.24-3 > Severity: important > > > With 2.6.24 r8169 stopped working on my asus A6Tc laptop. If I run > tcpdump on both sides, I see that it's able to send DHCP requests, but > the tcpdump on my laptop never shows the DHCP replies, so I guess > there is some bug in the receiving code. If I boot the same system > with 2.6.23 everything works fine. > please provide further info: dmesg lsmod ip a ip r -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465278: linux-image-2.6.24-1-powerpc: appletouch failure upon resume after suspend2ram
On Mon, 11 Feb 2008, Cyril Brulebois wrote: > Package: linux-image-2.6.24-1-powerpc > Version: 2.6.24-2 > Severity: normal > > I've been experiencing troubles with the appletouch driver on my iBook > G4 (last series) after resuming from a suspend2ram. With previous kernel > versions (all of them being Debian kernels), it was at least possible to > modprobe -r and modprobe it back, getting back to a functional driver > (even if restarting X was sometimes needed to get back synaptics > features, like tapping). Now, it's no longer possible to reload the > driver: can you please test 2.6.24-4 it had some usb stable fixes, along important security. thanks for feedback. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465348: alpine: pine kills any application it opens when pine closes
Package: alpine Version: 1.0+dfsg-3+b1 Severity: normal When opening any application using the appropriate mimetype handler on an attachment in a message, quitting pine kills the application as well. This is both unnecessary, and rather un-unixy (some would say rude)! Alas, there does not appear to be a config item for this. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24 (SMP w/2 CPU cores) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages alpine depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii libldap-2.4-2 2.4.7-5OpenLDAP libraries ii libncurses5 5.6+20080203-1 Shared libraries for terminal hand ii libpam0g 0.99.7.1-5 Pluggable Authentication Modules l ii libssl0.9.8 0.9.8g-4 SSL shared libraries alpine recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465347: Too many messages are marked fuzzy in apt-0.7.10
Package: apt
Version: 0.7.10
Severity: normal
In apt-0.7.* series many .po messages are marked as fuzzy. Such messages
are not loaded by gettext libraries, and instead only English versions of
messages are used. This results in visual package tools (like synaptic
and update-manager) displaying inconsistent messages - partially translated
and partially in English.
Example:
#: apt-pkg/depcache.cc:172 apt-pkg/depcache.cc:191 apt-pkg/depcache.cc:195
#, fuzzy
msgid "Reading state information"
This status text is visible after many routine package-related activities
(installing, upgrading, etc.)
In fact, running the following command in the /po directory of the apt
source tree gives me this:
for f in apt-0.7.10/po/*.po; do echo -n "${f} "; grep fuzzy ${f} | wc -l; done
apt-0.7.10/po/ar.po 22
apt-0.7.10/po/bg.po 31
apt-0.7.10/po/bs.po 29
apt-0.7.10/po/ca.po 31
apt-0.7.10/po/cs.po 31
apt-0.7.10/po/cy.po 139
apt-0.7.10/po/da.po 17
apt-0.7.10/po/de.po 31
apt-0.7.10/po/dz.po 31
apt-0.7.10/po/el.po 40
apt-0.7.10/po/en_GB.po 30
apt-0.7.10/po/es.po 17
apt-0.7.10/po/eu.po 14
apt-0.7.10/po/fi.po 30
apt-0.7.10/po/fr.po 2
apt-0.7.10/po/gl.po 13
apt-0.7.10/po/he.po 19
apt-0.7.10/po/hu.po 27
apt-0.7.10/po/it.po 30
apt-0.7.10/po/ja.po 2
apt-0.7.10/po/km.po 31
apt-0.7.10/po/ko.po 13
apt-0.7.10/po/ku.po 51
apt-0.7.10/po/mr.po 50
apt-0.7.10/po/nb.po 8
apt-0.7.10/po/ne.po 33
apt-0.7.10/po/nl.po 31
apt-0.7.10/po/nn.po 58
apt-0.7.10/po/pl.po 36
apt-0.7.10/po/pt_BR.po 30
apt-0.7.10/po/pt.po 28
apt-0.7.10/po/ro.po 31
apt-0.7.10/po/ru.po 30
apt-0.7.10/po/sk.po 30
apt-0.7.10/po/sl.po 58
apt-0.7.10/po/sv.po 13
apt-0.7.10/po/th.po 14
apt-0.7.10/po/tl.po 30
apt-0.7.10/po/uk.po 59
apt-0.7.10/po/vi.po 2
apt-0.7.10/po/zh_CN.po 2
apt-0.7.10/po/zh_TW.po 30
In previous versions (apt-0.6.*) there was no such a big problem. However,
in apt-0.7.* many new strings were introduced, and their contents were
created automatically as fuzzy. I believe the translation teams should
be given a remainder and opportunity to translate the new .po files.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465346: glibc-doc: Missing man page(s) for 'pthread_attr_get/setstacksize'
Package: glibc-doc Version: 2.7-6 Severity: normal No man page describing how to manage the thread stack with 'pthread_attr_getstacksize' and 'pthread_attr_setstacksize'. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.23 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394412: libxine1: I am also having this problem
* Reinhard Tartler <[EMAIL PROTECTED]> [080208 10:49]: > Micah Anderson <[EMAIL PROTECTED]> writes: > > > I am also having this problem, but I have all the packages mentioned > > installed: > > No, you are suffering a different problem. You seem to try to play a > specific mp3 stream on the net: > > Since this bug is closed and your issue is looks pretty unrelated, I'd > suggest that you file a new bug. Since this is an upstream issue, please > do so here: I spoke with upstream and it seems a patch was made and has already propagated in the most recent upload. It solves my problem, so I don't need to file another bug. Micah signature.asc Description: Digital signature
Bug#465144: menu.lst: wrong default entry 0saved
Robert Millan wrote: > On Mon, Feb 11, 2008 at 01:08:48AM +0100, Michael Biebl wrote: >> Robert Millan wrote: >>> On Sun, Feb 10, 2008 at 11:25:45PM +0100, Michael Biebl wrote: Package: grub-pc Version: 1.96+20080209-1 Severity: normal After installing grub-pc, I got the option to chainload grub2 from /boot/grub/menu.lst, which I chose. I use default saved in /boot/grub/menu.lst After the installation this entry was changed to default 0saved which is obviously wrong. >>> How does GRUB Legacy react to this oddity? >>> >> The saved default boot entry will not be selected. It falls back to boot >> the first boot entry. > > That is the intended behaviour. When you uninstall grub-pc, is menu.lst > restored to a sane state? (either "default 0" or "default saved") > I had re-run dpkg-reconfigure grub-pc and disabled the chain-loading. Now rerunning dpkg-reconfigure grub-pc and enabling chain-loading again doesn't update /boot/grub/menu.lst. So I can't tell if menu.lst is restored to a sane state after removing grub-pc. What I can tell though is that uninstalling grub-pc leaves *a lot* of cruft in /boot/grub/. I'm not sure, if the chain-loading idea is so great. I'd rather have /boot/grub cleaned up from any grub legacy cruft, everything imported into grub2 and simply make grub2 bullet proof, so the chain-loading workaround is no longer necessary. Would seem to be a cleaner solution to me. Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#465345: egrep: /etc/inetd.conf: No such file or directory
Package: fam
Version: 2.7.0-13.1
Severity: normal
Hi,
# ./fam
egrep: /etc/inetd.conf: No such file or directory
Usage: ./fam {start|stop|restart|force-reload}
Greetings,
Olaf
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fam depends on:
ii libc6 2.7-6GNU C Library: Shared libraries
ii libgcc1 1:4.3-20080202-1 GCC support library
ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3
ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip
ii portmap 6.0-5RPC port mapper
ii update-inetd4.29 inetd.conf updater
fam recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464953: Amd64 hotfix
> I modified the hotfix so it will also patch compat_sys_vmsplice, which > would be important on amd64 boxen with x86 compatibility enabled. Once again: The "hotfix" and also your modification are stupid, stupid, stupid and dangerous. The "hotfix" first attempts to try the exploit and this corrupts kernel memory. It is very likely that your system will crash shortly after and numerous people have reported that the "hotfix" just has that result either instantaneous or after a short while. Also while overwriting the vmsplice syscall with a "ret" will prevent the hole from being abused, this will also confuse software which wants to use the vmsplice call. At least one should return with a error. I'm not sure if there is any software in normal use which uses vmsplice but keep this in mind. And finally: If you really really want to use this kind of fix, why don't you just get rid of all the dangerous exploit code and only keep the code from inside the "de_exploit()" function and then call this code as root? This would do the job without causing memory corruption. But the best fix still is to just install a updated kernel and reboot. As said, you will anyway (but at a random time), at least when using this stupid "hotfix" which destroys your kernel memory. There might be systems which cannot be rebooted right now, but i most cases i feel that people who wan't to apply such a hotfix instead of deploying a clean solution are just lazy. Regards Michael -- It's an insane world, but i'm proud to be a part of it. -- Bill Hicks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405965: Feedback request.
Hello: Could anyone reproduce this on the latest etch version or any other? If so could you answer to Filipus questions? Does dmesg output any suspicious messages on konqueror load? Thanks, -- Raúl Sánchez Siles ->Proud Debian user<- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Bug#465174: module-assistant doesn't compile nvidia for kernel 2.6.24
#include * [EMAIL PROTECTED] [Mon, Feb 11 2008, 02:02:39AM]: > Package: module-assistant > Version: 0.10.8 > Severity: important Unless m-a did something wrong (like unpacking the wrong package) this is a job for nvidia-kernel-source' maintainer, not me. > /usr/src/modules/nvidia-kernel/nv/nv.c: At top level: > /usr/src/modules/nvidia-kernel/nv/nv.c:102: error: expected ‘=’, ‘,’, > ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token > /usr/src/modules/nvidia-kernel/nv/nv.c: In function ‘nvos_create_alloc’: > /usr/src/modules/nvidia-kernel/nv/nv.c:418: error: ‘nv_pte_t_cache’ > undeclared (first use in this function) nv_pte_t_cache does not exist in that line in the current version of nvidia-kernel-source (169.09-2). It first appears somewhere below, so I guess we deal with an old version of the package. Please check that and reassign the bug report to the appropriate package (or at least report the results). Regards, Eduard. -- "apt meldete, es werden ca. 70 Pakete deinstalliert werden müssen und mir kam es seltsam vor, aber dachte mir das Teil wird schon wissen was es tut." azeem: apt-get ist ein Tool, ein Werkzeug. Man nimmt doch auch von einem Hammer nicht an daß er schon weiß was er tut, wenn er mit 60 km/h auf deinen Daumen zurast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397939: Lintian: outdated-autotools-helper-file
On Mon, Feb 11, 2008 at 03:19:36PM -0800, Russ Allbery wrote: > Bas Wijnen <[EMAIL PROTECTED]> writes: > > On Mon, Feb 11, 2008 at 09:21:29AM -0800, Russ Allbery wrote: > > >> Always re-running autoconf and automake would increase the number of > >> FTBFS's that we'd need to fix. > > > Not really. > > No, really, I promise it will. :) Each time we upgrade autoconf, it will > break a bunch of packages that were doing things that weren't supported. Ah, that is a point. But that should not be the case if the packages build-depend on the right version, or is it still a problem? I know automake in particular changes a lot between versions, but that's why I always build-depend on a version (such as "automake1.10"). That's recommended as well AFAIK. So the problem of removing old versions of automake (such as automake1.8 at the moment) gets bigger, but it shouldn't make it FTBFS bugs most of the time. > > Yes, IMO it's one of those situations where Debian should do what's > > Right, not what's Easy (similar to what I wrote about the /bin/sh > > bash->dash move on -policy today). > > I am generally in favor of that, but I also don't have the free time to > volunteer for the release team, who ends up bearing the brunt of us doing > the right thing in this area, so, y'know, easy for me to say. :) I'm happy to report bugs and provide patches for many packages if that helps doing this properly. > > That's in principle a problem for the maintainer to solve, and > > secundarily for lintian. > > Well, yeah, but it would still be nice to provide some help. Sure. :-) Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://pcbcn10.phys.rug.nl/e-mail.html signature.asc Description: Digital signature
Bug#428889: KDE system routes
Yes, this problem still continues for k3b and Ark, it seems has beem fixed for videos opened with kaffeine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465344: gpsdrive: Building with mapnik 0.5
Package: gpsdrive
Version: 2.10~pre4-1
Severity: normal
Hello,
A new version of Mapnik, on which gpsdrive depends, has recently been
uploaded to experimental and will soon make its way into unstable.
Unfortunately, there is some ickiness involved, since mapnik upstream
does not (yet[0]) support multiple installed versions (with incompatible
plugins) concurrently yet. The fact that mapnik plugins would not be
compatible between corresponding .so versions was overlooked in the mapnik
0.4 packages, but has been corrected in the impending mapnik 0.5
packages.
In addition, a source change is needed to gpsdrive to support a changed
ABI in mapnik. Details of both changes follow:
1) Automatically determine location of mapnik input plugins using
mapnik-plugin-base and alter src/mapnik.cpp during build accordingly.
I tested this with a rather dirty hack (I'm not that familiar with the
dpatch build system, so I'm sure this could be done much better:
In debian/rules, after patching:
sed -i.bak -e "s#/usr/lib/mapnik/#$(shell mapnik-plugin-base)/#" src/mapnik.cpp
In debian/rules, before unpatching:
[ ! -f src/mapnik.cpp.bak ] || mv src/mapnik.cpp.bak src/mapnik.cpp
Your build-dependencies for libmapnik-dev will need to be updated to
libmapnik-dev (>= 0.5~svn638-1)
to make use of the 'mapnik-plugin-base' utility.
2) Patch src/mapnik.cpp for new mapnik API:
--- gpsdrive-2.10~pre4/src/mapnik.cpp.bak 2007-09-14 22:47:13.0
+0100
+++ gpsdrive-2.10~pre4/src/mapnik.cpp 2008-02-11 23:57:37.0 +
@@ -118,7 +118,7 @@
// Both datasorce_cache and font_engine are 'singletons'.
datasource_cache::instance()->register_datasources("/usr/lib/mapnik/input/");
-
freetype_engine::instance()->register_font("/usr/lib/mapnik/fonts/DejaVuSans.ttf");
+freetype_engine::register_font("/usr/lib/mapnik/fonts/DejaVuSans.ttf");
MapnikMap.WidthInt = 1280;
MapnikMap.HeightInt = 1024;
(the font path in that patch obviously changes based on a subsequent
dpatch) in the current Debian package.
This should probably be to work whichever version of mapnik is
installed, and pushed back to gpsdrive upstream.
I will raise the severity of this bug to 'important' once the new mapnik
packages hit unstable, and then to 'serious' shortly afterwards (since
this will become a FTBFS).
Note that I haven't fully tested gpsdrive with mapnik 0.5 - only that it
builds okay. Any other issues would probably be the subject of a separate
bug report.
Let me know if you need any further information on these issues.
Regards,
Dominic.
Maintainer for the Mapnik packages.
[0] https://trac.mapnik.org/ticket/72
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465177: FTBFS: configure: error: unable to configure inotify support
On Monday 11 February 2008 3:13:56 pm Sergey Jin' Bostandzhyan wrote: > On Mon, Feb 11, 2008 at 01:41:03PM -0500, Andres Mejia wrote: > > > do not pass the --enable-inotify parameter to the configure script; > > > presence of inotify will be detected automatically, if not available it > > > will be disabled on the fly. However, when the --enable-inotify > > > parameter is passed by the user, configure will abort with the error > > > that you are seeing if inotify checks fail. > > > > This is done on purpose so that no package on a different > > architecture/kernel builds packages sucessfully with a different set of > > options enabled, else I'm sure there would be a different set of bugs > > sooner or later. The inotify option is not enabled for any non-linux > > kernel using machine. > > > > The parameters passed to the configure script can be manually overridden > > by a user, but they won't be for the buildd machines. > > Well, if you are sure that the target machines *do have inotify support* > the only thing that could help is the config.log output of the failed > configure process. The best thing toward logs are located at http://buildd.debian.org/pkg.cgi?pkg=mediatomb . > > > What I still need to do is, to adapt the inotify check for cross > > > compiling, right now it will always fail when cross compiled. > > > > Actually, no cross compiling is done. The powerpc buildd machine is a > > powerpc machine. The same goes for the other buildd machines. > > Then it should work; we do check the headers and then we run some small > test code which is calling inotify_init(). If the inotify_init() function > returns -1 (error) we will compile without inotify support; however - if > the --enable-inotify parameter was specified configure will abort because > it can not do what the user wanted. > > So the question: is inotify really working on those systems? > > Kind regards, > Jin I'm finding this behavior strange. Ubuntu accepted mediatomb into their archive, yet now the powerpc architecture goes past the inotify check just fine, but the i386 and amd64 architectures do not. Take a look at https://launchpad.net/ubuntu/+source/mediatomb/0.10.0.dfsg1-1/ I know for the case of the i386, I've been able to successfully build packages using pbuilder. Also, it looks like the Ubuntu buildd machines are giving a different error, for architectures that run the inotify check sucessfully. -- Regards, Andres -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464733: linux-image-2.6.24-1-686: ipw2200 not working after upgrading from 2.6.24-2 to 2.6.24-3.
Hi Maximilian, > is that reproducible with 2.6.24-4 ? No, 2.6.24-4 works well. > also please don't use reportbug-ng it omits vital info, > please stick to reportbug. I've used reportbug: [2:54 /]$ dpkg -l reportbug-ng No packages found matching reportbug-ng. [2:54 /]$ dpkg -l reportbug | tail -n 1 ii reportbug 3.39 reports bugs in the Debian distribution Regards, Nikolay. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413200: Lowing severity
severity 413200 minor thanks. Hello: I'm afraid this problem cannot be given an important severity. I'll propose it as minor, please read their definitions below: important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. minor a problem which doesn't affect the package's usefulness, and is presumably trivial to fix. Thanks -- Raúl Sánchez Siles ->Proud Debian user<- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Bug#465143: libical0: 0.30-1 does not install /usr/share/libical/zoneinfo
> Just for the sake of completeness: Do I understand it correctly that the > set_zone_directory() function is not necessary anymore on *nix systems > when using libical >= 0.30? yes, set_zone_directory() function is not necessary anymore but on Debian :) We use tzdata from tzdata package. If you build libical yourself or on *nix systems, you can pass a configure option to use builtin tzdata (like 0.27). This isn't anymore the default behavior with libical >= 0.30. We recommand to use tzdata provided by the underlying system. cheers, Fathi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#464238: ucfq: fails to tell whether the configuration file was modified
tag 464238 + patch
thanks
Hi,
I think I've managed to solve this problem with the attached patch.
Please note that my perl is very limited, so I might be doing something
stupid here.
Cheers,
Nicolas
--- ucfq.orig 2008-02-12 00:49:40.0 +0100
+++ ucfq 2008-02-12 00:48:16.0 +0100
@@ -293,8 +293,9 @@
# Step 6: For each existing file, see if it has been changed
for my $file ($this->{file_list}->list) {
-$this->{file_list}->element($file)->{Hash} =
- $this->{hashfile_proxy}->hash($file);
+$this->{file_list}->element($file)->hash(
+ $this->{file_list}->element($file)->{Name},
+ $this->{hashfile_proxy}->hash($file));
if (! defined $this->{file_list}->element($file)->{Package}) {
$this->{file_list}->element($file)->{Package} =
$this->{registry_proxy}->find_pkg($file);
signature.asc
Description: Digital signature
Bug#465262: libopenobex: long term mass bug filing for cross build support.
Am Dienstag 12 Februar 2008 schrieb Neil Williams: > On Tue, 2008-02-12 at 00:09 +0100, Hendrik Sattler wrote: > > Am Montag 11 Februar 2008 schrieb Neil Williams: > > > +CROSS=CC=$(DEB_HOST_GNU_TYPE)-gcc > > > > Thanks for answering the first part. What is the CROSS variable about? Is > > it not needed as configure finds right gcc by default. > > Hmm, indeed it does. Sorry about that. You can drop the CROSS variable - > it is normally for situations where $(MAKE) insists on using gcc despite > --host. > > Would you like a revised patch? No, I already have one. HS signature.asc Description: This is a digitally signed message part.
Bug#465340: dpkg: Broken call to open in Dpkg/Control.pm
On Tue, Feb 12, 2008 at 12:25:13AM +0100, Frank Lichtenheld wrote:
> On Mon, Feb 11, 2008 at 11:47:13PM +0100, Soren Hansen wrote:
> > diff -Nru /tmp/63ah7FRjAl/dpkg-1.14.16.6ubuntu1/scripts/Dpkg/Control.pm
> > /tmp/fQCCS9NM6H/dpkg-1.14.16.6ubuntu2/scripts/Dpkg/Control.pm
> > --- dpkg-1.14.16.6ubuntu1/scripts/Dpkg/Control.pm 2008-01-18
> > 11:12:53.0 +0100
> > +++ dpkg-1.14.16.6ubuntu2/scripts/Dpkg/Control.pm 2008-02-11
> > 23:20:11.0 +0100
> > @@ -78,7 +78,7 @@
> > my ($self, $file) = @_;
> > $self->reset();
> > # Parse
> > -open(CDATA, "<", $file) || syserr(_g("cannot read %s"), $file);
> > +open(CDATA, "< $file") || syserr(_g("cannot read %s"), $file);
>
> Hmm, whatever problem you saw, this most certainly is not the right fix!
> Both lines are semantically identical... (barring any serious Perl
> bugs).
Granted my perl-fu is not that strong, and looking at the documentation,
I might have exaggerated the extent of this bug somewhat.
> Could you please go into more detail what you tried to fix?
The particular bug I was fixing was when called with "-c-", i.e. read
the control file from stdin. From perldoc:
In the 2-arguments (and 1-argument) form opening '-' opens STDIN
and opening '>-' opens STDOUT.
Without my patch, it's the 3-argument version of open, so opening "-"
fails (as there is no such file).
> Error messages?
From pkg-create-dbgsym:
dpkg-gencontrol: failure: cannot read -: No such file or directory
> Launchpad bug number?
Didn't bother doing the paper work :)
--
Soren Hansen
Virtualisation specialist
Ubuntu Server Team
http://www.ubuntu.com/
signature.asc
Description: Digital signature
Bug#442819: file: Thanks; added this magic upstream
Package: file Version: 4.23-1 Followup-For: Bug #442819 Note that the CVS camcorder magic was added commented out because it's not unambiguous enough. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (700, 'testing'), (601, 'unstable'), (600, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages file depends on: ii libc6 2.7-6 GNU C Library: Shared libraries ii libmagic1 4.23-1 File type determination library us file recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451261: Possibly upstream bug link
found 451261 4:3.5.8.dfsg.1-7 thanks Maybe this bug is the one at upstream http://bugs.kde.org/show_bug.cgi?id=73101 I'll go on investigating. -- Raúl Sánchez Siles ->Proud Debian user<- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
Bug#464082: dhcp3-client: Segmentation fault
- Original Message - From:<[EMAIL PROTECTED]> on behalf of *Andrew Pollock* Sent:Sun, 10 Feb, 2008 at 16:47 +1000 Subject: Re: Bug#464082: dhcp3-client: Segmentation fault > tags 464082 + moreinfo > thanks > > On Tue, Feb 05, 2008 at 04:27:52AM +0300, Alexander Davydenko wrote: > > Package: dhcp3-client > > Version: 3.1.0-2 > > Severity: important > > > > > > Here is output from dhclient -d -n > > > > -- > > Internet Systems Consortium DHCP Client V3.1.0 > > Copyright 2004-2007 Internet Systems Consortium. > > All rights reserved. > > For info, please visit http://www.isc.org/sw/dhcp/ > > > > Listening on LPF/eth1/00:90:27:5a:8c:8e > > Sending on LPF/eth1/00:90:27:5a:8c:8e > > Sending on Socket/fallback > > option_space_encapsulate: option space agent does not exist, but is > > configured. > > DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 > > DHCPOFFER from 1.2.3.1 > > option_space_encapsulate: option space agent does not exist, but is > > configured. > > DHCPREQUEST on eth1 to 255.255.255.255 port 67 > > DHCPACK from 1.2.3.1 > > Segmentation fault > > > > -- > > which is produced if a new request option `domain-search' is enabled > > together with the `domain-name' option. In that case the `resolv.conf' > > file populated with both `domain' and `search' directives. > > At the same time the interface is configured, but `dhclient.leases' file > > was still empty. Disabling `domain-name' from list doesn't helps. > > However in the case of default (commented) conf settings it works, but > > it allow only `domain' resolv's option. > > Please advise what version of dhcp3-server you're using. > > If it's >= 3.1.0, please send me your dhcp3.conf (out of band if you wish) > > Please send me your dhclient.conf > > I'd like to try and reproduce this in my test environment. > > regards > > Andrew - End original message - The DHCP server is from Windows Domain Controller (which version of Windows, I don't know). The content of dhclient.conf follows. # Configuration file for /sbin/dhclient, which is included in Debian's # dhcp3-client package. [comments skipped] send host-name "myhost.domain.com"; send dhcp-client-identifier 00:90:27:A5:12:7B; send dhcp-lease-time 604800; prepend domain-name "sub1.domain.org domain.org"; prepend domain-name-servers 172.3.1.2, 172.3.1.7; request subnet-mask, broadcast-address, routers, domain-name, domain-name-servers, domain-search, host-name, netbios-name-servers, netbios-scope, interface-mtu; require subnet-mask, domain-name-servers; prepend netbios-name-servers 172.3.1.2; reject 172.1.1.1,172.2.68.2; [comments skipped] BTW, the <[EMAIL PROTECTED]> is not accepted by master.debian.org from our smtp host. Cheers, -- Alexander Davydenko signature.asc Description: Digital signature
Bug#465343: stgit-contrib: please include stgit.el
Package: stgit-contrib Version: 0.14.1-3 Severity: wishlist StGIT includes an Emacs mode in its contrib directory. It would be really nice if the stgit-contrib package included that file (even if it just went in /usr/share/stgit-contrib or something). Thanks, Toby. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages stgit-contrib depends on: ii stgit 0.14.1-3 manage stacks of patches in a git stgit-contrib recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#465285: libmpich1.0gf -- package empty.
On Mon, 2008-02-11 at 22:38 +0530, Kumar Appaiah wrote: > Package: libmpich1.0gf > Version: 1.2.7-6 > Severity: serious > Tags: patch > > Hi! > > I noticed that the libmpich1.0gf package is empty! Please find > attached a simple patch to set the right install directories in > debian/rules. > > If I got something wrong, please excuse me. D'oh! Thanks for catching that. I should have noticed the empty package... Will rebuild right away. -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Engineering consulting with open source tools http://www.opennovation.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428889: Is this still happenning?
Hello Rafael: Are you still having the same problem on a recent Debian lenny/unstable version? Thanks. -- Raúl Sánchez Siles ->Proud Debian user<- Linux registered user #416098 signature.asc Description: This is a digitally signed message part.
