Bug#375513: mgm has no .desktop
Package: mgm Version: 1.1.cvs.20020221-2 Severity: wishlist Hello. mgm currently lacks a .desktop file. A bug was filed against the package in the Ubuntu bugtracker [1] and you can find a .desktop file attached there. It would be nice if this was included in Debian as well. [1] https://launchpad.net/bugs/50179 Thanks for your time, Vassilis Pandis ___ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375547: php4-tclink_3.4.0-4(armeb/unstable): issue with php4 depends generation
Package: php4-tclink Version: 3.4.0-4 Severity: important There was an error while trying to autobuild your package: > Automatic build of php4-tclink_3.4.0-4 on bob by sbuild/armeb 42 > Build started at 20060626-1506 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5), php4-dev (>= 4:4.3.10-10), libssl-dev [...] > dh_installchangelogs > dh_installdocs > dh_installexamples > dh_installdebconf > dh_link > dh_strip > dh_compress > dh_fixperms > dh_installdeb > dh_shlibdeps > dh_gencontrol -- -V"php:Depends=phpapi-`php-config4 --phpapi`" > dpkg-gencontrol: warning: can't parse dependency phpapi-Usage: > /usr/bin/php-config4 > [--prefix|--includes|--ldflags|--libs|--extension-dir|--version] > dpkg-gencontrol: error: error occurred while parsing Depends > dh_gencontrol: command returned error code 2304 > make: *** [binary-arch] Error 1 A full build log can be found at: http://experimental.ftbfs.de/build.php?arch=armeb&pkg=php4-tclink&ver=3.4.0-4 I'm not sure whether this is an armeb specific bug or whether this is something else. In any case, I'm seeing the same behaviour on other packages, too, though I didn't file a bug on those, yet. This bug is mostly meant as a way to solicit help ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375560: libxml-ruby1.8: new upstream release (0.3.8)
Package: libxml-ruby1.8 Severity: wishlist Upstream release has version 0.3.8. Debian libxml-ruby1.8 package is in version 0.3.4. I was going to make new package by my own but it yields on load: LoadError: /usr/lib/ruby/1.8/i486-linux/xml/libxml.so: undefined symbol: Init_libxml Any help? -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-urok-1 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to pl_PL.UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
xbox-raincoat 0.10-3 MIGRATED to testing
FYI: The status of the xbox-raincoat source package in Debian's testing distribution has changed. Previous version: 0.10-1 Current version: 0.10-3 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372780: OpenBSD can't boot via yaboot on powerpc (no dualboot possible)
On Sun, Jun 11, 2006 at 07:01:50PM +0200, Peter Voigt wrote: > Change the use of the path-parameter "bsd=" in yaboot.conf. > > Let this parameter point to the openbsd-kernel relativ > to the openbsd-partition. > > In my example let the user use "bsd-kernel=/bsd" > and not "bsd=/dev/hda..." > > And please change the hardcoded name of the openbsd-kernel. > > ofboot allways set the name to "bsd". But that is not good. > > If you compile a new openbsd-kernel, you usually > rename the old working kernel to "bsd.generic" or > "bsd.old". > > If the new kernel doesn't work, you need a fallback, but > cannot use yaboot. Yaboot is only able to boot "bsd" and > not any otherwise named openbsd-kernel. I am currently preparing an upload for our team to adopt the package (#354974). The last solution you point out, i.e. yaboot booting a BSD kernel directly, seems to be the most simple to implement without breaking anything for other users. Could you provide a patch against the current source code to do so? I do not have time currently to support *BSD on PowerPC, so if I do not have a patch, then I will close this bug at the new upload. Nevertheless, feel free to reopen it and to attach a patch to your bug report. Cheers, -- ((__,-"""-,__)) Aurélien GÉRÔME .---. `--)~ ~(--` Free Software Developer / \ .-'( )`-. Unix Sys & Net Admin [EMAIL PROTECTED]@./ `~~`@) (@`~~` /`\_/`\ | |.''`. // _ \\ | | : :' : | \ )|_ (8___8) `. `'` /`\_`> <_/ \ `---` `- \__/'---'\__/ BOFH excuse #298: Not enough interrupts signature.asc Description: Digital signature
Processed: Re: Bug#149946: yaboot: halt command doesn't work correctly
Processing commands for [EMAIL PROTECTED]: > tags 149946 upstream Bug#149946: yaboot: halt command doesn't work correctly Tags were: wontfix Tags added: upstream > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372780: OpenBSD can't boot via yaboot on powerpc (no dualboot possible)
On Tue, Jun 27, 2006 at 02:45:49AM +0200, Aurélien GÉRÔME wrote: > I do not have time currently to support *BSD on PowerPC, so > if I do not have a patch, then I will close this bug at the new > upload. Nevertheless, feel free to reopen it and to attach a patch > to your bug report. Well, maybe I have been a bit quick to reply. I will tag the bug as whishlist, I will not close it. :) Cheers, -- ((__,-"""-,__)) Aurélien GÉRÔME .---. `--)~ ~(--` Free Software Developer / \ .-'( )`-. Unix Sys & Net Admin [EMAIL PROTECTED]@./ `~~`@) (@`~~` /`\_/`\ | |.''`. // _ \\ | | : :' : | \ )|_ (8___8) `. `'` /`\_`> <_/ \ `---` `- \__/'---'\__/ BOFH excuse #121: halon system went off and killed the operators. signature.asc Description: Digital signature
Processed: Re: Bug#149946: yaboot: halt command doesn't work correctly
Processing commands for [EMAIL PROTECTED]: > tags 149946 wontfix Bug#149946: yaboot: halt command doesn't work correctly There were no tags set. Tags added: wontfix > severity 149946 minor Bug#149946: yaboot: halt command doesn't work correctly Severity set to `minor' from `normal' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: OpenBSD can't boot via yaboot on powerpc (no dualboot possible)
Processing commands for [EMAIL PROTECTED]: > tags 372780 +wishlist Unknown tag/s: wishlist. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n etch etch-ignore. Bug#372780: OpenBSD can't boot via yaboot on powerpc (no dualboot possible) There were no tags set. Tags added: > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#318168: marked as done (sawfish-xmms broken with new version of sawfish)
Your message dated Tue, 27 Jun 2006 00:23:24 -0500 with message-id <[EMAIL PROTECTED]> and subject line Fixed by upload of 0.4-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: sawfish Version: 1:1.3+cvs20050709-1 Severity: important after upgrading to the said version of sawfish, the xmms bindings for sawfish no longer work. also when adding a new key binding to sawfish using sawfish-ui, the xmms bindings dont show up under the list of commands. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12.2.20050712.0 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages sawfish depends on: ii gnome-terminal [x-termina 2.10.0-2 The GNOME 2 terminal emulator appl ii libatk1.0-0 1.10.1-2 The ATK accessibility toolkit ii libaudiofile0 0.2.6-6Open-source version of SGI's audio ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libesd0 0.2.36-1 Enlightened Sound Daemon - Shared ii libfontconfig12.3.2-1generic font configuration library ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libglib2.0-0 2.6.5-1The GLib library of C routines ii libgmp3 4.1.4-6Multiprecision arithmetic library ii libgtk2.0-0 2.6.8-1The GTK+ graphical user interface ii libice6 6.8.2.dfsg.1-1 Inter-Client Exchange library ii libpango1.0-0 1.8.1-1Layout and rendering of internatio ii librep9 0.17-9 an embeddable Emacs-Lisp-like runt ii libsm66.8.2.dfsg.1-1 X Window System Session Management ii libx11-6 6.8.2.dfsg.1-1 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-1 X Window System miscellaneous exte ii libxft2 2.1.7-1FreeType-based font drawing librar ii libxrender1 1:0.9.0-2 X Rendering Extension client libra ii rep-gtk 0.18-9 GTK binding for librep ii xlibs 6.8.2.dfsg.1-1 X Window System client libraries m ii zlib1g1:1.2.2-8 compression library - runtime sawfish recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Given that > Nothing related to sawfish. The rep-xmms package need to be repackaged > because now with GCC 4.0 the install path has changed > /usr/lib/rep/i386-pc-linux-gnu/xmms/ vs > /usr/lib/rep/i486-pc-linux-gnu/xmms/ And that the upload of 0.4-5 fixed #317633: rep-xmms: newest rep on x86 doesn't use /usr/lib/rep/i386-pc-linux-gnu/ but /usr/lib/rep/i486-pc-linux-gnu/ This bug is fixed by that upload, too. -- Rodrigo Gallardo --- End Message ---
