Bug#343998: anjuta: Anjuta 1.2.4-1+b1 crash on launch: workaround via experimental

Package: anjuta Version: 1.2.4-1+b1 Followup-For: Bug #343998 Anjuta failed to start after upgrading libgtk2.0-0=2.8.9-2 but I found a workaround. It's a little strange though. (I already use some experimental packages but others would need to add experimental to the sources list.) I upgraded

Bug#345253: Second attempt works

FYI, a second attempt to remove it succeeds. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#344723: Please fast-track the readline5 bugfix

Could you fast-track this one? It's at the base of a number of progression-to-testing delays, including the KDE mess. -- Nathanael Nerode <[EMAIL PROTECTED]> This space intentionally left blank. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact

Bug#345288: mantis: Plethora of vulnerabilities

Package: mantis Severity: grave Tags: security Justification: user security hole Lots of vulnerabilites have yet again been found in Mantis: CVE-2005-4524: Notes on private bugs may be leaked. CVE-2005-4523: Private bugs may be leaked through RSS feeds. CVE-2005-4522: XSS in view_filters_pa

Bug#345282: xjig: Please stop shipping /usr/doc symlink

Package: xjig Version: 2.4-9 Severity: serious Justification: FHS We're post-sarge, so no /usr/doc symlink please. This can usually be solved by rebuilding with a new debhelper. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#345281: rolldice: Please remove /usr/doc symlink and stop making it

Package: rolldice Version: 1.10-1 Severity: serious Justification: FHS We're post-sarge, so no symlinks in /usr/doc please. You can usually fix this by updating debhelper and rebuilding. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE

Bug#328031: Fwd: Re: Erlang 10.b.9 compile bug on Debian GNU/Linux SPARC

Hi, I am forwarding the information from upstream to the bug so that it will not get lost (see below). I've checked the build procedure and, indeed, the architecture detection is done by looking at the output of 'uname -m'. On Solaris this returns "sun4u" on ultrasparc hardware, our kernel retu

Bug#345253: Removal fails

Package: uim-common Version: 1:0.4.9.1-1 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Removing uim-common ... ERROR: could not open uim-module-manager.scm (errobj No such file or directory) *backtrace* >>(require "uim-module-manager.scm") >>(*catch (quote errobj) (require "uim

Bug#344995: [Pkg-octave-devel] Bug#344995: Solution

On Thu, 29 Dec 2005, Rafael Laboissiere wrote: > * folajimi <[EMAIL PROTECTED]> [2005-12-29 11:55]: > > > Is there anything that Colin and I can do yet? Colin is out of town, > > but I was just wondering if we will be able to resume work on the task > > assigned to us. > > IIRC, the task assigned

Bug#344995: [Pkg-octave-devel] Bug#344995: Solution

* folajimi <[EMAIL PROTECTED]> [2005-12-29 11:55]: > Is there anything that Colin and I can do yet? Colin is out of town, > but I was just wondering if we will be able to resume work on the task > assigned to us. IIRC, the task assigned to Colin and you was to split the octave-forge binary packag

Bug#345244: kball: not installable in sid

Package: kball Version: 0.0.20041216-2 Severity: grave Justification: renders package unusable Hi, here is the problem: # apt-get install kball Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossibl

Bug#345248: rafkill: not installable in sid

Package: rafkill Version: 1.2.0-2 Severity: grave Justification: renders package unusable Hi, here is the problem: # apt-get install rafkill Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible s

Bug#345249: kraptor: not installable in sid

Package: kraptor Version: 0.0.20040403-2 Severity: grave Justification: renders package unusable Hi, here is the problem: # apt-get install kraptor Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impos

Bug#345246: kq: not installable in sid

Package: kq Version: 0.98+cvs.20031006-6 Severity: grave Justification: renders package unusable Hi, here is the problem: # apt-get install kq Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible

Bug#345241: octave2.1: octave panics on start

Package: octave2.1 Version: 2.1.72-6 Severity: grave Justification: renders package unusable After upgrading octave today, it no longer starts at all. Reverting back to octave2.1_2.1.72-5_i386.deb makes it work again. This happens on at least two different machines. I have not done any further b

Bug#307299: twiki: TWiki.cfg

Package: twiki Version: 20040902-3 Followup-For: Bug #307299 Hi, I've got the same problem, attached my TWiki.cfg. norbi -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=hu_HU (charmap=ISO-8859-2) Versions of packages twiki dep

Bug#332631: pppstatus crashes with segfault

> Can I help in some way to help you to find the problem? You already have. It's either the toolchain of a library, most likely the latter. I suspect that a new upload will make the problem go away (but that doesn't mean the bug is gone!). -- John Hasler [EMAIL PROTECTED] Elmwood, WI USA --

Bug#344995: [Pkg-octave-devel] Bug#344995: Solution

On Thu, 29 Dec 2005, Rafael Laboissiere wrote: > * Joaquim Ortega <[EMAIL PROTECTED]> [2005-12-29 10:02]: > > > I believe that I have identified the bug. [...] With this three-line > > fix the package built fine. > > Thanks *_a lot_* for that! The package indeed builds fine in sid with > your sug

Bug#344995: [Pkg-octave-devel] Bug#344995: Solution

* Joaquim Ortega <[EMAIL PROTECTED]> [2005-12-29 10:02]: > I believe that I have identified the bug. [...] With this three-line > fix the package built fine. Thanks *_a lot_* for that! The package indeed builds fine in sid with your suggested changes. I prepared a new version of octave-forge wh

Bug#345223: xmltex: destroys local configuration

Package: xmltex Version: 1.9-10 Severity: serious See also #337436 on passivetex which has similar code. The postinst snippet below has the effect that if the local admin deletes the configuration file /etc/texmf/texmf.d/96passivetex.cnf, it is resurrected from the template file, which is a viola

Bug#343998: anjuta: I have the same problem

Package: anjuta Version: 1.2.4-1+b1 Followup-For: Bug #343998 I got the same problem here is my list of environment and dependencies, just in case please fix this problem: anjuta is completely useless for me a. -- System Information: Debian Release: testing/unstable APT prefers testing APT

Bug#345186: bbdb broken after apt-get upgrade

Package: bbdb Version: 2.35.cvs20040528-1 Severity: grave Justification: renders package unusable Hi, this is a followup to bug #344032 bbdb stopped functioning after an upgrade of emacs. Maybe this bug should be filed there. (...). Even with Roland Mas's work-around (in #344032) I get error

Bug#323318: Patch fix gcc4 issues

Hi, I needed to compile a module for linux-kernel-2.4, and find out this couple of patches wich fix thoses errors http://user.it.uu.se/~mikpe/linux/patches/2.4/patch-gcc4-fixes-v12-2.4.32

Bug#345170: fiaif: FIAIF NAT's any computer in any zone file if any other zone is set to nat 0.0.0.0/0 to 0.0.0.0/0

Package: fiaif Version: 1.20.0-2 Severity: critical Tags: security Justification: root security hole Facts: FIAIF with 3 zones zone.tun zone.int zone.ext zone.tun is used for a tun device zone.int is for the internal lan zone.ext is for the internet zone.int settings: SNAT[0]="EXT ALL 192.168

Bug#345168: Sarge version of nscd is completely broken (Fails to cache any entry)

Package: nscd Version: 2.3.2.ds1-22 Severity: critical Justification: breaks unrelated software I'm using nscd (sarge version) with LDAP, and it is not working. Attaching to it with strace -p $PID shows no activity while doing a simple ls -al /home with a few directories in /home, making co

Processed: Reassigning

Processing commands for [EMAIL PROTECTED]: > severity 343709 serious Bug#343709: semantic: Byte-compilation fails with emacs-snapshot Severity set to `serious'. > reassign 344999 semantic Bug#344999: emacs-snapshot-gtk: error building semantic Bug reassigned from package `emacs-snapshot-gtk' to `

Processed: Re: debiandoc-sgml-doc: FTBFS: debiandoc-sgml.en.pdf could not be generated properly

Processing commands for [EMAIL PROTECTED]: > reassign 338376 debiandoc-sgml Bug#338376: debiandoc-sgml-doc: FTBFS: debiandoc-sgml.en.pdf could not be generated properly Bug reassigned from package `debiandoc-sgml-doc' to `debiandoc-sgml'. > tags 338376 patch Bug#338376: debiandoc-sgml-doc: FTBFS

Bug#338376: debiandoc-sgml-doc: FTBFS: debiandoc-sgml.en.pdf could not be generated properly

reassign 338376 debiandoc-sgml tags 338376 patch thanks Me again, Frank Küster <[EMAIL PROTECTED]> wrote: > - The first is to load the textcomp package with the "force" option: > > \usepackage[force]{textcomp} > > But this might have other side effects; you'd have to carefully check > the re

Bug#345154: silgraphite2.0 - is no native package

Package: silgraphite2.0 Version: 102svn-1 Severity: serious > Need to get 807kB of source archives. > Get:1 http://incoming.debian.org unstable/main silgraphite2.0 102svn-1 (dsc) > [633B] > Get:2 http://incoming.debian.org unstable/main silgraphite2.0 102svn-1 (tar) > [807kB] > Fetched 807kB in

Bug#345153: isdnutils: ftbfs [sparc] @SHELL@: Command not found

Package: isdnutils Version: 1:3.7.2005-07-09-2.1 Severity: serious Justification: fails to build from source isduntils failed to build on a sparc buildd, duplicated on my sparc pbuilder. It also failed in the same way on powerpc and most other buildds. I suspect an incompatibility with the new

Bug#344989: libparagui1.0c2a: missing dependency on libfreetype6

Hello Steve. On Wed, Dec 28, 2005 at 01:56:32AM -0800, Steve Langasek wrote: > The libparagui1.0c2a package is missing a dependency on libfreetype6, > because libparagui-1.0.so.0 is not properly linked: > > $ ldd -d -r /usr/lib/libparagui-1.0.so.0 > /dev/null > undefined symbol: FT_Init_FreeType

Bug#343487: Re: Bug#343487: nessusd: cannot connect to 2.2.5-3 server

On Thu, Dec 29, 2005 at 11:17:41AM +0100, Marc Haber wrote: > The resulting packages naturally only depend on libssl0.9.7, and seem > to work fine. This might be a workaround. Great, yes, this is a workaround. Unfortunately it's a *local* workaround. Even if I can generate i386 packages compiled f

Bug#341236: your bug -- doxygen: fails to generate html documentation (segmentation fault)

Hi Justin, Maximiliano is correct. I compiled doxygen 1.4.5 myself and it worked. doxygen 1.4.2 could not handle one header file (include/litesql/datetime.hpp) with following lines: -- string asString(string format="%d.%m.%y") const; -- string asString(string format="%h:%M:%s") const; -

Bug#320521: marked as done (FTBFS: Does not forward declare classes)

Your message dated Thu, 29 Dec 2005 12:00:26 +0100 with message-id <[EMAIL PROTECTED]> and subject line closing 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 t

Bug#343487: Re: Bug#343487: nessusd: cannot connect to 2.2.5-3 server

On Wed, Dec 28, 2005 at 10:57:42AM +0100, Javier Fernández-Sanguino Peña wrote: > severity 343487 grave > tags 343487 pending confirmed sid etch > reassign 343487 nessus > thanks > > I downgraded the nessus client version to 2.2.5-2 (which is *not* compiled > against both 0.9.7 and 0.9.8 SSL libra

Bug#343998: Seems to be solved in anjuta-1.2.4a, avaliable in www.anjuta.org

Package: anjuta Version: 1.2.4-1+b1 Followup-For: Bug #343998 Patched in version 1.2.4a. Please, make .deb package with it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#226139: marked as done (amanda-server: chg-manual makes insecure use of /tmp)

Your message dated Thu, 29 Dec 2005 01:32:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#226139: fixed in amanda 1:2.4.5p1-1 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

Processed: downgrade

Processing commands for [EMAIL PROTECTED]: > unmerge #337497 Bug#337497: initramfs-tools: [powerpc] doesn't work on pegasos - ALERT! /dev/hda1 does Bug#332824: linux-image-2.6.13-1-686: Cannot find LVM root fs Bug#342925: initramfs-tools: [sparc64] generated initrd fails to boot Disconnected #337

Bug#338376: debiandoc-sgml-doc: FTBFS: debiandoc-sgml.en.pdf could not be generated properly

Hi, I have further analysed this bug and can give some input that might help. Frank Küster <[EMAIL PROTECTED]> wrote: > , > | ! Package textcomp Error: Symbol \textcurrency not provided by > | (textcomp)font family ppl in TS1 encoding. > | (textcomp)Default

Processed: your mail

Processing commands for [EMAIL PROTECTED]: > package octave-forge Ignoring bugs not assigned to: octave-forge > tags 344995 patch Bug#344995: octave-forge: FTBFS (ia64,mips,.../unstable): fixed.h: No such file or directory There were no tags set. Tags added: patch > End of message, stopping pro

Bug#344995: Solution

I believe that I have identified the bug. It is related to the new behaviour of make documented as * All pattern-specific variables that match a given target are now used (previously only the first match was used). What happens now is that in the file main/Makeconf.in and main/Makeconf.base

Bug#345010: marked as done (tkdiff: Tkdiff broken in 4.0.2-1sarge0 (security update))

Your message dated Wed, 28 Dec 2005 23:47:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#345010: fixed in tkdiff 1:4.0.2-1sarge1 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