tags 369513 + unreproducable,moreinfo
thanks
Alberto Maurizi <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.9.6-3
> Severity: grave
> Justification: renders package unusable
>
>
> gnucash does not start anymore.
> after the splash disappears, the main window indicates that it is
> l
tags 369513 - unreproducible, moreinfo
severity 369513 minor
title 369513 gnucash: remembers even impossible window positions
thanks
Alberto Maurizi <[EMAIL PROTECTED]> writes:
> OK, following your suggestions I managed to "solve" de bug.
> I try to explain the problem because it can
Thomas Themel <[EMAIL PROTECTED]> writes:
> I just noticed that the new gnucash version seems to corrupt imported
> data sets. I use the package with [EMAIL PROTECTED] set, and the
> following procedure reproducably loses a lot of transactions from my
> accounts:
Hi, thanks for your bug report.
It's nice that guile-1.6 now builds on ia64, but a shame that it
doesn't work at all. The failures look just like the sort of things
that scm also does on ia64.
However, this is no big surprise to me. I said a while back, but it
may have gotten lost, that scm also does not work on ia64. Upstre
Bill Allombert <[EMAIL PROTECTED]> writes:
> On Tue, Jun 06, 2006 at 08:52:26AM -0700, Thomas Bushnell BSG wrote:
>> <[EMAIL PROTECTED]> writes:
>>
>> > Hello Rob and Thomas,
>> >
>> > This bug is assigned to libglade9 which has been removed
<[EMAIL PROTECTED]> writes:
> Hello Rob and Thomas,
>
> This bug is assigned to libglade9 which has been removed from
> unstable.
>
> As a consequence, this bug should either be closed or reassigned.
Bug 337346 (in your subject line) has nothing to do with glade, and is
closed as of guile-1.6/1.
Bill Allombert <[EMAIL PROTECTED]> writes:
> On Tue, Jun 06, 2006 at 09:25:06AM -0700, Thomas Bushnell BSG wrote:
>> Bill Allombert <[EMAIL PROTECTED]> writes:
>>
>> > On Tue, Jun 06, 2006 at 08:52:26AM -0700, Thomas Bushnell BSG wrote:
>> >> <
Steve Langasek <[EMAIL PROTECTED]> writes:
>> Perhaps the maintainer should file a request with the FTP masters to
>> have it removed, at which point the bug will be automatically closed.
>
> Bugs aren't automatically closed on package removal.
Curious; I get such messages all the time when packa
Bill Allombert <[EMAIL PROTECTED]> writes:
> Now, that we are back on track, do you know whether this bug should be
> reassigned or closed ?
The similar bug in guile-1.6 has been fixed. It's up to the
maintainer, but I think it can be closed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Mon, Jun 05, 2006 at 04:47:44PM -0700, Thomas Bushnell BSG wrote:
>> The correct response, I believe, is for Debian guile-1.6 to declare in
>> the architecture spec that ia64 is not supported.
>
>> This is also a rele
--- Begin Message ---
Hi,
Thomas Bushnell BSG ([EMAIL PROTECTED]) wrote on 2006-06-06:
> I don't use QIF, so I don't have any QIF files to work with.
I've made up a simple test data set that seems to reproduce the issue
just fine since I didn't like the idea of circulating
tags 370502 - moreinfo
tags 370502 + confirmed,upstream
thanks
Thomas Themel <[EMAIL PROTECTED]> writes:
> I've made up a simple test data set that seems to reproduce the issue
> just fine since I didn't like the idea of circulating my accounting data
> for the last two years too widely.
Of co
Package: python-serial
Version: 2.2-2
Severity: grave
Attempting to install python-serial fails with the following error,
making the package impossible to use:
Errors were encountered while processing:
python-serial
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to ins
Somehow the main text of my bug report got dropped. No clue how that
happened. Anyway, here's the gist:
Attempting to install python-serial fails with the following error,
making the package impossible to use:
Errors were encountered while processing:
python-serial
E: Sub-process /usr/bin/dpk
Matthias Klose <[EMAIL PROTECTED]> writes:
> find /usr/share/pycentral/python-parrallel -ls
# find /usr/share/pycentral/python-parrallel -ls
find: /usr/share/pycentral/python-parrallel: No such file or directory
# find /usr/share/pycentral/python-parallel -ls
find: /usr/share/pycentral/python-par
The related bug at
http://bugzilla.gnome.org/show_bug.cgi?id=344219, when solved, will
result in a reduction of the severity of this bug and a necessary
change to its title.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED
It looks like the bug is caused by having a QIF file being imported
which does not contain valid UTF8 data. Then when it's written out,
what gets written out is invalid, and so when it's written in, it
can't be parsed and the transactions vanish.
The correct solution is to ask the user what the
Matthias Klose <[EMAIL PROTECTED]> writes:
>> > NEW: --WARN-- [lin001w] File `/usr/X11R6/bin/dh_pycentral' does not belong
>> > to any package.
>> > NEW: --WARN-- [lin001w] File `/usr/X11R6/bin/py_compilefiles' does not
>> > belong to any package.
>> > NEW: --WARN-- [lin001w] File `/usr/X11R6/bi
Barry Hawkins <[EMAIL PROTECTED]> writes:
> Please send us the output of the following:
>
> $ dpkg -l python2.[1,2]
I get the same as you:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X
Matthew MacLeod <[EMAIL PROTECTED]> writes:
> I can confirm this new error with the i386 version of the package, with
> slib verions 3a2-3, 3a2-4, and 3a2-5.
Can you please file a new bug report then, since it is clearly a
distinct error than the old one?
Thomas
--
To UNSUBSCRIBE, email to [E
Justin Pryzby <[EMAIL PROTECTED]> writes:
> package wmtz
> tag 346975 patch
> thanks
>
> I intend to NMU a fix for this bug sponsored by some member of the QA
> group; patch attached. My pbuild result of this patch was clean, and
> produced a binary package with expected debdiff output from the m
Justin Pryzby <[EMAIL PROTECTED]> writes:
> I intend to NMU a fix for this bug sponsored by some member of the QA
> group; patch attached. My pbuild result of this patch was clean, and
> produced a binary package with expected debdiff output from the most
> recent version in sid. Build logs and
Adam Kessel <[EMAIL PROTECTED]> writes:
>> I leave to you the task now of locating the bug report that you didn't
>> bother looking for the first time.
>
> I got the same error, and quickly scanned bugs.debian.org/gnucash for
> hash-for-each. I found this bug, with no explanation or pointer to
Package: guile-1.6
Version: 1.6.7-2
Severity: serious
Guile fails to build on ia64 with a test suite failure.
See
http://buildd.debian.org/fetch.php?&pkg=guile-1.6&ver=1.6.7-2&arch=ia64&stamp=1138179040&file=log&as=raw.
This may or may not be related to #326905, but because ia64 is a
release ar
found 351693 1.6.7-3
thanks
Unfortunately, buildd logs show that this bug is still present in
1.6.7-3.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Can you please work on #351693? Perhaps simply following the
suggestion in the bug report would solve the problem; I don't know.
But regardless, it's silly that such a small thing should be causing
problems for three months now.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
severity 366556 important
reassign 366556 xfonts-encodings
merge 366556 365403
thanks
Alberto Maurizi <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.8.12-8
> Severity: grave
> Justification: renders package unusable
>
>
> below is the result of
>
> $ gnucash &> gnuchas.log
>
>
Rob Browning <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>> Can you please work on #351693? Perhaps simply following the
>> suggestion in the bug report would solve the problem; I don't know.
>> But regardless, it&
Rob Browning <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>> http://buildd.debian.org/build.php?arch=&pkg=guile-1.6
>>
>> The ia64 buildd admin clearly has just not processed the failing log.
>
> Ahh. This isn
Rob Browning <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>> I don't know what you're talking about.
>
> Actually, I just clicked on the wrong link.
Oh good, it seemed like we were surely looking at different files
e
Nathanael Nerode <[EMAIL PROTECTED]> writes:
> As discussed in this bug, mhash's maintainer appears to be MIA or
> out to lunch.
>
> Is it OK if we forcibly orphan the package now?
There is no procedure for forcible orphaning the package.
If you have a fix for the bug (the bug log seems to sugge
So my question from Monday is still there. Perhaps following the
suggestion in the bug log will solve the problem?
The bug has now been blocking gnucash from entering testing for three
months...
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
Rob Browning <[EMAIL PROTECTED]> writes:
> - I tried building the package in merulo's unstable chroot. That
> worked fine. Since the chroot doesn't have slib installed, and
> neither did the buildd (according to the log), slib's not likely
> to be the problem.
So the suggestion in
Rob Browning <[EMAIL PROTECTED]> writes:
>> I agree that this is extremely unlikely. The only guess is that the
>> bug log includes a purge of guile-1.6-libs; though even that shouldn't
>> matter since guile-1.6-libs doesn't contain anything that would be
>> left behind absent a purge.
>
> The mo
Marc 'HE' Brockschmidt <[EMAIL PROTECTED]> writes:
> gnucash 1.9.5-3 fails to build on a mips buildd:
Thank you for your bug report. The actual failure was not the
"config.status" check, which as can be seen from the log was ignored
correctly by the makefile; rather, the problem appears later on
Bastian Blank <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.9.6-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
Oh shoot. This was supposedly fixed in 1.9.5, but the fix didn't
actually get into the package. For the record, the bug is not about
Paul Martin <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.8.12-9
> Severity: grave
> Justification: renders package unusable
>
> $ gnucash
> ERROR: Unbound variable: gnc:debugging?
>
> This is because gnucash-common (1.9.6-1) is in unstable, but gnucash
> itself is still at 1.8.12-9
Matt Kraai <[EMAIL PROTECTED]> writes:
> On Thu, May 18, 2006 at 12:47:44PM +0200, Martin Michlmayr wrote:
>> Do you see this too? Putting -lcrypt sooner works for me, as in:
>> gcc -g -O2 -Wall -lcrypt -Wl,--as-needed -o .libs/efstool efstool.o
>> ./.libs/libefs.so -L/usr/lib /usr/lib/libgli
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> Package: bonobo
> Version: 1.0.22-8
> Severity: serious
>
> This package fails to build from source. Patch coming in a separate
> mail.
Very curious how this should appear, but no point in figuring that
out. Thanks for the report and the upload is
Rob Browning <[EMAIL PROTECTED]> writes:
> At this point, my best guess is that this may be a bug in 1.6.7 that
> has been fixed in 1.6.8. I believe a number of GC and syntax related
> bugs have been fixed since 1.6.7, and I wouldn't be surprised if one
> of those is the culprit.
>
> Unfortunatel
"Albert Cahalan" <[EMAIL PROTECTED]> writes:
> I lost all sorts of apps that Debian no longer packages.
> I even lost penguineyes. Want to package it for me?
>
> I guess it was wrong to rely on shared libraries. Debian
> should use static linking. About the only thing stable
> is the kernel system
"Albert Cahalan" <[EMAIL PROTECTED]> writes:
> old stuff needs libpng2
> new stuff depends on stuff that conflicts with libpng2
> user needs the new stuff, and wants to keep the old stuff
Can you give a specific example please?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Sat, May 20, 2006 at 10:57:20AM -0700, Rob Browning wrote:
>
>> At this point, my best guess is that this may be a bug in 1.6.7 that
>> has been fixed in 1.6.8. I believe a number of GC and syntax related
>> bugs have been fixed since 1.6.7, and I w
Package: libaqbanking
Version: 1.5.99+1.6.0beta-3
Severity: serious
Can you please build libaqbanking against libgnutls-dev instead of
libssl-dev? (This also requires changing -lssl to -lgnutls-openssl.)
libssl-dev is not GPL compatible and cannot be used in a GPLd
program. This means it canno
"Gabriel M. Beddingfield" <[EMAIL PROTECTED]> writes:
> Workaround:
> # apt-get install slib=3a1-4.2
> # apt-get install gnucash
>
> This looks like my fault -- I'm a newbie to Debian and I'm running a
> mixed system (testing/unstable). Apt installed slib=3a2-2 (unstable)
> before, which had th
I apologize; my previous explanation was incorrect.
There is no bug here at all; I believe you simply must wait for the
new ofx to be build for your architecture.
> This is particularly annoying because the failed install seems to have wiped
> out my previous working install.
What "failed in
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> Package: malaga
> Version: 6.13-5
> Severity: serious
>
> Your package fails to build:
>
> dpkg-gencontrol: warning: can't parse dependency libmalaga1-dev libmalaga2-dev
> dpkg-gencontrol: error: error occoured while parsing Conflicts
Wow, I wonder w
This is not helpful; please give a complete build log and not just
part of one. Especially I need to know such details as the
architecture, and version of packages that lilypond depends on.
Thomas
Daniel Schepler <[EMAIL PROTECTED]> writes:
> Package: lilypond
> Version: 2.6.3-10
> Severity:
Can you provide me with the complete output of "printenv" from within
a failing attempt?
Thomas
Jörg Sommer <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.9.3-1
> Severity: serious
> Justification: no longer builds from source
>
> Hi,
>
> % dpkg-buildpackage -rfakeroot -b
> ...
>
Peter Samuelson <[EMAIL PROTECTED]> writes:
> The miscfiles copyright file says GNU-manifesto.gz is distributed under
> the GPL. The file itself says "Modified versions may not be made."
>
> Please edit the file to remove the misleading statement, perhaps
> replacing it with a standard GPL notice
severity 354973 serious
thanks
Remi Vanicat <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.9.1-1
> Severity: grave
> Tags: experimental
> Justification: renders package unusable
>
> When trying to run a localy build experimental gnucash, it failed at
> startup with the error:
> Sub
severity 374660 normal
thanks
John M Flinchbaugh <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.9.7-1
> Severity: grave
> Justification: renders package unusable
>
> Unpacking replacement gnucash ...
> dpkg: error processing /var/cache/apt/archives/gnucash_1.9.8-1_i386.deb
> (--unpa
Jim Woodruff <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 2.0.0-1
> Severity: grave
> Justification: renders package unusable
>
> Everytime I try to open an account register, GnuCash crashes with
> the dialog box "GnuCash Unexpectedly Quit". This makes the
> Application unusable.
>
>
Loïc Minier <[EMAIL PROTECTED]> writes:
> On Fri, May 26, 2006, Thomas Bushnell BSG wrote:
>> This is blocked waiting for the python-defaults to be changed.
>
> It's not clear to me why you can't fix the gcc-4.1 build failure before
> python2.4 is uploaded.
merge 335981 336371
thanks
Bastian Blank <[EMAIL PROTECTED]> writes:
> Package: scm
> Version: 5e1-2
> Severity: serious
>
> There was an error while trying to autobuild your package:
It is not necessary to file duplicate bug reports. Please check the
BTS before filing reports.
Thomas
--
T
> I had problems when trying to use SLIB for the first time:
>
> guile> (use-modules (ice-9 slib))
> guile> (require 'priority-queue)
> ERROR: In procedure open-file:
> ERROR: Permission denied: "/usr/share/slibcat"
> ABORT: (system-error)
Which version of guile are you using?
What does the fil
Version: 3a2-2
Bert <[EMAIL PROTECTED]> writes:
> Package: slib
> Version: 3a1-5
> Severity: grave
> Justification: renders package unusable
>
> Upgrade from 3a1-5 to 3a2-1 fails with
>
> Errors were encountered while processing:
> slib
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
Neil Williams <[EMAIL PROTECTED]> writes:
> ?? Whatever I do with slib forces the removal of g-wrap ??
Please read the bug log to which you were appending.
(http://bugs.debian.org/337359).
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [
Rob Browning <[EMAIL PROTECTED]> writes:
> Well, it should contain all the "important parts", but should be
> modified to work appropriately for guile, whatever that means. It
> looks to me like in the past, guile may have been modifying guile.init
> to produce ice-9/slib.scm. However, without k
Package: libpcre3
Version: 6.4-1
Severity: critical
Justification: breaks the whole system
libpcre3 install its libraries in /usr/lib:
/usr/lib/libpcre.so.3.12.0
/usr/lib/libpcrecpp.so.0.0.0
/usr/lib/libpcreposix.so.3.12.0
However, crucial system binaries needed at boot time depend on it, progr
Matthias Klose <[EMAIL PROTECTED]> writes:
> This bug report is filed against the source package which builds
> a library depending on libstdc++6 and defining or referencing
> *mt_alloc* symbols. The package has to be rebuilt with either
> g++-4.0_4.0.2-4 or g++-3.4_3.4.4-10 (or newer). Please r
Steve Langasek <[EMAIL PROTECTED]> writes:
> Why not? AFAIK, there's no reason that you can't do an additional upload
> that would let both new binary package names through the NEW queue at the
> same time.
Because it won't get through any faster that way. It will simply get
added to the existi
Joerg Jaspert <[EMAIL PROTECTED]> writes:
> - Your package was held back since it was requested to ease a move of
> whatever packages to testing. I cant see right now a unblock request in
> my mail folders (but that may be because Im @work, so may be unable to
> find it, limited access to my mailb
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> Package: imlib11-dev
> Version: 1.9.14-26
> Severity: serious
>
> Hi,
>
> Your package has a dependency on xlibs-dev which has been removed
> as annouced on:
> http://lists.debian.org/debian-devel-announce/2005/11/msg00022.html
>
> This is now causing buil
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> This can be solved in 2 ways:
> - Add a build dependency on libxt-dev
> - Rebuild the configure script with debian's autoconf, since it
> fixes the problem that the macro's check for something in
> libxt-dev. Please also see
> /usr/share/doc/autotoo
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> On Fri, Jan 06, 2006 at 06:42:13PM +0100, Kurt Roeckx wrote:
>> /usr/bin/ld: cannot find -lXext
>> collect2: ld returned 1 exit status
>> make[3]: *** [gnome-moz-remote] Error 1
>
> There are some other errors too:
> readXPM.c:138:21: error: X11/xpm.h: No
reopen 343182
thanks
> I don't understand why this bug was closed. The explanation given makes
> no sense. Both installation and removal of this package require the file
> "/usr/bin/kpsewhich", which seems to come from either package
> "tetex-bin" or package "libkpathsea-perl". So either one of t
Steve Langasek <[EMAIL PROTECTED]> writes:
>> Running gnucash causes the splash screen to load, then it crashes with
>> the following error:
>
>> ERROR: Unbound variable: hash-for-each
>
> This error does not occur when using the versions of slib/guile-1.6-slib in
> testing; so this appears to b
tags 348018 +help
thanks
Daniel Burrows <[EMAIL PROTECTED]> writes:
> Whatever the problem is, it seems to involve the way that the Gnucash core
> calls the Scheme modules. The following code in an interactive Guile session
> does what you would expect:
>
> (use-modules (ice-9 slib))
> (requi
Bob <[EMAIL PROTECTED]> writes:
> This bug shows as being resolved but it appears as it is not.
Please read the bug log and the referenced bugs. People seem to enjoy
opening the same bugs over and over, and I'm getting tired of
repeating the same replies over and over.
Thomas
--
To UNSUBSCRI
Paul TBBle Hampson <[EMAIL PROTECTED]> writes:
> A GPL package (which only depends on libcurl3-gnutls) is installed:
> libcurl3-gnutls gets pulled in
>
> A package that can't work with gnuTLS version of libcurl (and
> therefore libcurl3-gnutls conflicts with it) is installed:
> libcurl
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On Sat, 10 Sep 2005, Thomas Bushnell BSG wrote:
>> It is *absolutely intolerable* to declare such conflicts for shared
>> libraries, where there are easy solutions: MAKE TWO LIBRARIES THAT
>> HAVE DIFFERENT NA
Have you been making any progress on bugs 324796/327288?
This bug is blocking progress on many packages.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
These grave bugs in gs-gpl are blocking work and causing trouble for
many people. Is there anything I can do to help get them fixed? I'm
happy to do NMUs if that would be helpful. Please advise.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Sun, Sep 18, 2005 at 03:48:20PM -0700, Thomas Bushnell BSG wrote:
>
>> These grave bugs in gs-gpl are blocking work and causing trouble for
>> many people. Is there anything I can do to help get them fixed? I'm
>>
Package: epiphany
Severity: grave
epiphany depends on libclanlib2, which no longer exists in unstable.
It should be recompiled, to pick up the new libclanlib2c2.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: grip
Severity: grave
grip depends on libid3-3.8.3, which packages no longer exists in
unstable. It needs to be recompiled, so that it gets the new
libid3-3.8.3c2.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This emacs21 bug is still around, blocking some other packages too.
Since version 21.4a-1 works just fine on powerpc, perhaps the
following change in 21.4a-2 might just be the problem? It does rather
stand out.
* Apply patch supporting the ppc64 architecture. This is a slightly
modified pa
Rob Browning <[EMAIL PROTECTED]> writes:
> That seems likely. I should get a chance to test today or tomorrow.
Sweet. :) Let me know if there's anything I can do to help.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> Your package is failing to build because it has a build
> dependency on libpng10-dev, which has been removed from sid. You
> will have to switch that to using libpng12-dev instead.
Thanks; the blocking bugfix at the moment for all this work is the
upload
Roger Leigh <[EMAIL PROTECTED]> writes:
> Unless you intend to upload a new version in the next few days, or
> have any objection to the following patch, I intend to NMU gtkhtml to
> fix this RC bug.
I will not be able to get to this for at least a week. Please feel
free to NMU the patch wheneve
Package: aptitude
Version: 0.2.15.9-5
Severity: grave
Justification: renders package unusable
aptitude no longer functions as of the latest upgrade of the package. The
error looks like it is getting the wrong version of some library, or is
otherwise missing a dependency. This error happens aft
Daniel Burrows <[EMAIL PROTECTED]> writes:
> Someone uploaded a version of apt that changed the ABI without changing the
> SONAME. This should be fixed in unstable with apt 0.6.40.1 and aptitude
> 0.2.15.9-6.
Have these already been uploaded?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
imlib+png2 is just the png2 version of imlib; since png2 (aka png10)
is now gone, imlib+png2 is on its way out too.
imlib now provides the necessary libraries (with appropriate new
sonames) and gnome-1 (the libraries of which I now maintain) are
transitioning. Once everything is transitioned, we
Ryan Murray <[EMAIL PROTECTED]> writes:
> On Sun, Oct 02, 2005 at 09:09:49PM -0700, Thomas Bushnell BSG wrote:
>> imlib+png2 is just the png2 version of imlib; since png2 (aka png10)
>> is now gone, imlib+png2 is on its way out too.
>
> I'll be uploading once
Package: mftrace
Severity: serious
Please upgrade mftrace to at least version 1.1.16. Upstream says this
is necessary to compile lilypond; and the fixes for several lilypond
bugs are waiting on the compilation errors being solved.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a s
It should now be possible to build gdk-pixbuf, with a Build-Depends on
libpng12-dev and libgnome-dev (>= 1.4.2-24), and upload. Please let
me know if there's anything I've missed that makes that not possible.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
Package: amaya
Version: 8.5-1
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themselves
Package: cronosii
Version: 0.2.2.23.1-2
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages
Package: eboard
Version: 0.9.5-5
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themsel
Package: entity
Version: 1.0.1-7
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themsel
Package: extace
Version: 1.9.3-1
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themsel
Package: fidelio
Version: 0.9.6-10
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages thems
Package: gco
Version: 0.3.3-8
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themselves
Package: gfpoken
Version: 0.27-1
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themsel
Package: fvwm
Version: 1:2.5.14-2
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themse
Package: gkrellweather
Version: 2.0.6-5
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages
Package: glimmer
Version: 1.2.1-4
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themse
Package: gkrellm
Version: 2.2.7-2
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages themse
Package: gmgaclock
Version: 0.4.8-2.1
Severity: serious
This package fails to build from source because it declares a build
dependency on imlib1-dev and/or gdk-imlib1-dev, which are no longer
installable due to the removal of libpng10-dev from Debian.
The imlib1-dev and gdk-imlib1-dev packages th
1 - 100 of 257 matches
Mail list logo
