Package: gnome-pilot
Version: 2.0.12-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
Package: gmoo
Version: 0.5.6-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 themselve
Package: gnome-pilot-conduits
Version: 2.0.12-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 p
Package: gnome-pim
Version: 1.4.9-2.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 th
Package: gretl
Version: 1.4.1-3
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 themselv
Package: gtk-engines
Version: 0.12-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 the
Package: ircii-pana
Version: 1:1.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 the
Package: mozart-gtk
Version: 20040429-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
Package: gtkgo
Version: 0.0.10-12
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: pixelize
Version: 0.9.2-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 thems
Package: paul
Version: 0.1.1-3
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 themselve
Package: scigraphica
Version: 0.8.0-9.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
Package: qiv
Version: 2.0-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 themselves w
Package: smilutils
Version: 0.3.0-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 them
Package: transcalc
Version: 0.13-1.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 the
Package: unixodbc
Version: 2.2.11-9
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 them
Package: vertex
Version: 0.1.15-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 themse
Package: xzgv
Version: 0.8-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 themselves
Package: ygraph
Version: 0.15-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 themselv
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> Dude I was CC on that fun thread where you were yelling at everyone. No need
> for redundant BTS entries, really.
1) I wasn't yelling at anyone; perhaps you have me confused with
someone else.
2) ftpmaster requested that bugs be filed.
Thomas
Steve Langasek <[EMAIL PROTECTED]> writes:
> Please take it under advisement that I am currently trying to persuade
> Thomas that the gdk-imlib11-dev and gdk-imlib11 packages should be abandoned
> in favor of reintroduction of gdk-imlib1 and gdk-imlib1-dev as
> libpng12-based packages. I know a c
Dirk Eddelbuettel <[EMAIL PROTECTED]> writes:
> It's a 1-character change. In my book that doesn't call for Severity: serious
> given that I have a history of responding within 24 hrs. But whatever.
It (was) a FTBFS bug; all FTBFS bugs are severity serious.
Please don't regard bug reports as
Package: maxima
Version: 5.9.1-12
Severity: critical
Maxima FTBFS on powerpc. This is currently holding back some C++
shared library transition work (in particular for libgmp3).
See
http://buildd.debian.org/fetch.php?&pkg=maxima&ver=5.9.1-12&arch=powerpc&stamp=1128709716&file=log&as=raw.
Thoma
Ron <[EMAIL PROTECTED]> writes:
> In this case I just need to fix the build-dep from png10 -> png12,
> (for the bits I'm responsible for) but I guess I missed the memo
> that we were rolling on that this week. I'm not unhappy that it's
> happening, just surprised at how...
We actually rolled on
Can you fix bug 329564? It's delaying the C++ library transition and
should take only a moment to fix. I'm happy to do an NMU as well if
that's ok with you.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: mftrace
Severity: grave
Version: 1.1.16-1
Tags: patch, upstream
gf2pbm on powerpc fails entirely when compiled with -O2. It produces
errors like "Too many bits found when loading character 65", and the
resulting output is empty.
I have found the following patch solves the problem. I f
retitle 334163 mftrace: Please package version 1.1.17 of mftrace
thanks
Han-Wen Nienhuys is fast!
Thomas
--- Begin Message ---
Thomas Bushnell BSG wrote:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>
>>I'm attempting a fix now.
>
>
> Do
severity 334781 important
tag 334781 +moreinfo
thanks
I just uploaded lilypond 2.6.3-2. Can you retry once that becomes
available on your architecture and let me know the results?
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PR
severity 304932 important
retitle 304932 lilypond: FTBFS on amd64: Error making documentation.
thanks
Contrary to what Goswin von Brederlow said, this bug does not happen
on all archs; the bug that happens on all archs is #334877.
An examination of the failures shows that they are entirely disti
"Aaron M. Ucko" <[EMAIL PROTECTED]> writes:
> lilypond-data appears to have gained an architecture-dependent file,
> which is inappropriate both because the package is architecture-all
> and because the file is under /usr/share:
>
> $ dpkg -L lilypond-data | fgrep .so | xargs file
> /usr/share/lil
Ralf Stubner wrote:
> BTW, anybody encountering bug #335055/#335065 can, as a simple
> workaround, create an empty file /var/lib/texmf/web2c/foo.fmt before
> (re)configuring tetex-bin
Please don't think that this means it's ok to take a week to fix this
bug. It stalls autobuilding of any packag
Package: gcc-4.0
Version: 4.0.2-2
Severity: serious
Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
See:
http:://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=hppa&stamp=1130038470&file=log&as=raw
Severity serious because this creates an FTBFS situation for lilyp
Version: 2.6.3-7
Package: lilypond
Severity: serious
Lilypond fails to build on hppa due to a gcc bug. Reported to the
gcc-4.0 package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
retitle 335286 gcc: Internal error compiling lilypond on hppa,arm
thanks
http://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=arm&stamp=1130041300&file=log&as=raw
reports the same problem on arm.
It can be confirmed *not* to happen on powerpc and alpha.
Thomas
--
To UNSUBSCRIBE
reassign 335286 gcc-4.0
thanks
Steve Langasek <[EMAIL PROTECTED]> writes:
> reassign 335286 lilypond
> thanks
>
> On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
>
>> Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
>
>&g
The fix for this bug is now on its way into the archive, but because
it involves NEW processing, it won't necessarily be there right away.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 325421 +unreproducable
thanks
Martijn Pieters <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.8.10-13
> Severity: grave
>
> GnuCash consistently crashes when trying to create sub-accounts, making the
> package next to unusable.
I'm unable to reproduce this on my system.
What i
What is your locale when you use gnucash?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
"Aaron M. Ucko" <[EMAIL PROTECTED]> writes:
> The libofx source package includes a debian/shlibs file that
> inappropriately reads
>
> libofx 1 libofx1c2
>
> and evidently overrides dh_makeshlibs; as a result, packages such as
> gnucash that build against the library fail to pick up appropriat
tags 273900 + moreinfo
thanks
Do you still encounter this abort?
If so, can you please try with gnucash 1.8.10-15 or later, and let me
know if the problem occurs even then?
Thanks, Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
severity 325997 important
thanks
Adrian Bunk <[EMAIL PROTECTED]> writes:
> severity 325997 serious
> thanks
Please read bug 325710. The bug is in libofx1c2, which is now an
obsolete package.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMA
reopen 325421
severity 325421 important
thanks
Martijn Pieters <[EMAIL PROTECTED]> writes:
>> I think this bug is also fixed by the bugfix in 1.8.10-15 of gnucash.
>> Please install that and if the bug still occurs for you, reopen this
>> bug report and I will see what I can figure out.
>
> The
Benjamin Drieu <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG <[EMAIL PROTECTED]> writes:
>
>> Unfortunately, the bug is in libofx1c2 (or rather, one specific
>> version of it). I'm not sure the correct fix, but bug #325710
>> contains what I *think* i
I have observed this bug on powerpc too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--- Begin Message ---
Hi Tomas,
You contacted me a while back about the roleplaying package, which I
have set to ITA. Your last comment on bug 246486 was that fixing it
and bringing it up to date would be the be difficult, and perhaps the
package should just be removed.
I think that's a good a
severity 303687 normal
reassign 303687 gconf2
thanks
"Adam M." <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.8.10-11
> Severity: grave
>
> gnucash dumps core on startup after the latest update.
This is actually a bug in gconf. There is a simple workaround
described in /usr/share/
reassign 303687 gconf2
severity 303687 normal
thanks
> I disagree most strenuously. Up until this version, gnucash worked *fine*
> without gconf; now, I can't pull gnucash up on a remote display at all
> because of this bletcherous dependency. I think this is a grave bug in
> gtkhtml, and I don
Steve Langasek <[EMAIL PROTECTED]> writes:
> Well, I think it's equally valid to say that this is a libgconf11 bug, for
> trying to launch the gnome2 version of gconfd and *not* falling back to
> launching the gnome1.2 version. If people want to fix this via gconf2,
> that's fine; the important t
Steve Langasek <[EMAIL PROTECTED]> writes:
> An strace shows that libgconf11 is trying to start gconfd-2, not gconfd-1.
> It succeeds in starting it, then fails to find the control file in the
> desired gnome 1.2 location.
Ok, then perhaps it's true that fixing libgconf11 is best.
Regardless, tho
Adam M <[EMAIL PROTECTED]> writes:
> I know you can reassign bugs all you want, but the problem remains
> that gnucash DOES NOT work in Sid. I downgraded gnucash to the one in
> Sarge and it works perfectly, with latest gconf.
Yes, this is not in dispute. The problem is that either gconf2 (or
gc
Thank you both so much for being will to work with me on solving this
bug; I know I can be difficult at times and I appreciate your
patience.
The new libgconf11 package hasn't hit powerpc yet (where I do all my
unstable development). Once it does, I'll verify that it solves the
observed symptoms
The following patch allows python-gnome to build apparently correctly.
foo
Description: Binary data
> Gnucash does not start and gives the following error:
> ERROR: Could not find slib/require.scm in ("/usr/share/guile"
> "/usr/share/gnucash/guile-modules" "/usr/share/gnucash/scm" ""
> "/usr/share/guile/site" "/usr/share/guile/1.6" "/usr/share/guile" ".")
Can you please show me the output of
Package: lilypond
Severity: critical
This is a pseudo-bug to prevent the new lilypond from entering sarge.
In my opinion there is a likelihood of interoperation bugs which will
take a while to iron out, and I am not confident that we should ship
the new version in sarge.
Thomas
--
To UNSUBSCR
Paul Johnson <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 1.8.10-7
> Severity: grave
> Justification: renders package unusable
>
> When ever I open an account ledger in gnucash - the following crash
> message occurs -
> Application "/usr/bin/guile-1.6" (process ) has crashed
> d
[EMAIL PROTECTED] (Frank Pavageau) writes:
> I don't reproduce it either. I compared the versions of packages listed
> in the bug report with mine, and found this discrepancy in the
> reporter's list :
>
> ii libice6 4.3.0.dfsg.1-10 Inter-Client Exchange library
> ii libsm6
Package: grisbi
Severity: serious
As can be seen from
http://buildd.debian.org/fetch.php?&pkg=grisbi&ver=0.5.5-1&arch=mipsel&stamp=1107431070&file=log&as=raw,
grisbi builds are now failing on mipsel.
The fix should be trivial, as indicated in the build log itself:
checking build system type.
Lior Kaplan <[EMAIL PROTECTED]> writes:
> Hi,
>
> What can be done for bug #230677? It was a year since an NMU was done
> (march 2004). The problem is fixed.
>
> But since it was fixed by the NMU, it's still open as RC bug, and the
> package won't go to sarge.
>
> I think the bug should be closed.
Adrian Bunk <[EMAIL PROTECTED]> writes:
> severity 306015 grave
> thanks
>
> Hi Steve,
>
> first of all, if you downgrade a bug only a good hour after I upgraded
> it, it would be nice if you would:
> - Cc me
> - send a better explanation than "This is not a missing dependency, feh"
Looking at t
Adrian Bunk <[EMAIL PROTECTED]> writes:
> You seem to confuse this with bug closing. It's common practice to
> adjust the severity of a bug to a RC one if a RC issue was mistakenly
> reported as non-RC, and neither your Developers Reference nor your
> release team have ever disagreed with this
Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes:
> I think etch should really no longer ship this dummy package that's
> obsolete this long. Please upon next upload of lilypond, stop building
> this dummy package to get it removed.
I agree.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
So it sounds like you did:
Create file named "foo.xac"
Do lots of edits on foo.xac [set 1]
Then open file named "foo.2004xx.xac" (a backup of foo).
Do lots of edits on foo.2004xx.xac [set 2]
Then open foo.xac again.
Do lots of edits on foo.xac [set 3], which triggers the backup purger and
Daniel Burrows <[EMAIL PROTECTED]> writes:
> Yes, that's true, and as far as I'm concerned, making that the default would
> be enough to close the bug. The main thing that bothered me is that you can
> lose a lot of data with no warning just using the default behavior of the
> program the way it'
Theodore Tso <[EMAIL PROTECTED]> writes:
> I would appreciate any comments from the Debian Release Managers and
> Debian Masters about whether or not it is required to remove any files
> which are legal for us to redistribute (such as RFC's and I-D's), but
> which are not DFSG-compliant from sourc
Package: gnucash
Version: 2.0.2-1
Severity: grave
Tags: upstream
2.0.2 unfortunately contains a serious register-entry bug that prevents
many kinds of register transactions from being properly committed, causes
crashes, and so forth. In all likely this is a single-point bug.
--
To UNSUBSCRIB
severity 392488 important
retitle 392488 lilypond-data: don't ship .pyc files in accord with Python policy
thanks
"Sam Hocevar \(Debian packages\)" <[EMAIL PROTECTED]> writes:
> Package: lilypond-data
> Version: 2.6.5-2
> Severity: serious
> Justification: Policy 9.1.1
>
>/usr/share/lilypond
severity 392488 important
thanks
You can now stop playing BTS tag; thanks.
Andreas Barth <[EMAIL PROTECTED]> writes:
> severity 392488 serious
>
> * Thomas Bushnell BSG ([EMAIL PROTECTED]) [061012 10:39]:
>> However, .pyc files are machine-independent, so there is no v
Sam Morris <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 2.0.1-3
> Severity: serious
>
> After telling Gnucash where to save the report, it freezes.
Can you please:
1: Try this with 2.0.2-2, and
2: Give me a recipe for how to recreate the bug, preferably on an
empty file?
Thomas
Sam Morris <[EMAIL PROTECTED]> writes:
> Package: gnucash
> Version: 2.0.1-3
> Severity: serious
>
> After telling Gnucash where to save the report, it freezes.
I checked it out, and it is a real bug (though not serious).
I'll report it upstream and see what they say.
--
To UNSUBSCRIBE, emai
On Mon, 2008-02-11 at 03:55 +0300, Wartan Hachaturow wrote:
> What does gnucash bug #444950 has to do with qgit's number #440950?
Nothing, obviously, just a typo. Go ahead and close the bug of course.
> Thank you for removing my package from testing :(
I think nothing of the kind would have ha
Package: rhythmbox
Version: 0.10.1-1+b3
Severity: grave
--- Please enter the report below this line. ---
Upon today's update in unstable rhythmbox seems to be entirely unable to
playback. This occurs for tracks in the music library (I have tried
both MP3 and OGG tracks), and for internet radio s
Upon further experimentation, the crash only happens if the audio device
cannot be opened. This often happens for me if a java web app has
played sound first, because my java grabs audio.
It used to be that in such a circumstance rhythmbox would report an
error. Now it crashes badly. So this it
On Wed, 2007-07-04 at 19:53 +0200, Holger Levsen wrote:
> Hi debian-kernel ;)
>
> for those of you who dont read debian-devel... :-)
>
> On Wednesday 04 July 2007 18:14, Thomas Bushnell BSG wrote:
> > I'm trying to find out who has responsibility for Bug #430646.
>
On Sun, 2007-07-15 at 22:48 +0100, Neil Williams wrote:
> It's been a while since the patch was provided. I've tested at this end
> and the patch appears fine. It actually results in a much smaller .diff
> via interdiff (attached).
>
> Are you willing to do an NMU if Thomas does not respond?
>
>
Package: fglrx-driver
Version: 8.44.3-1
Severity: serious
--- Please enter the report below this line. ---
Upon "up"grade to 8.44.3, my X server no longer knows about the proper
resolutions of my screen.
/etc/X11/xorg.conf has the following for each depth:
Modes "1920x1440" "1
OK, you said in your report that you were "reporting from Debian
machine", which I take it to mean that the failed build is not on
Debian. The scm package builds just fine on Debian; it looks as if you
are trying to build it on ubuntu. I can't support what happens when you
build the Debian packag
Package: grub
Version: 0.97-27
Severity: serious
update-grub mutates the boot device incorrectly in producing menu.lst.
This bug, btw, caused a remote server to fail to reboot automatically
and cost me actual expense in remote debugging assistance.
Attached is menu.lst-before (which I hand-edited
This is the sort of thing that should be fixed in a stable patch
release.
The problem originates in the sarge->etch upgrade, which changed device
names from hd* to sd*; something has failed to notice that and the
results are sufficiently disastrous that a stable update seems called
for.
Thomas
On Thu, 2008-01-10 at 21:41 +0100, Sebastian Pipping wrote:
> > What is the system like on which you are building? What processor?
> > What OS? Can you give me a complete--that is, not pruned at all--build
> > log?
>
> Full build log is attached. It was created running
>
>$ dpkg-buildpacka
On Fri, 2008-01-11 at 15:30 +1100, Jason Thomas wrote:
> The lines between the automagic markers are auto generated and subject
> to change. You need to edit the default options between those markers
> to suit your needs. Then when you run update-grub the generated
> content
> will be correct.
On Sat, 2008-01-12 at 14:45 +0100, Joerg Jaspert wrote:
> Package: libofx
> Severity: serious
> (a bug to not forget this issue, together with the reject of the newer
> version from NEW).
>
> this package contains non-free files, the DTDs, at least those from the
> OFX standard, have a non-free
Hi: I'm the Debian maintainer for libofx and for gnucash. I'm writing
to you because you are responsible (in some fashion) for the maintenance
of packages which depend on libofx.
Unfortunately, it has come to light that libofx contains non-free
software. Importantly, the DTD files which describe
--- Begin Message ---
I confirm that it's not fixed too. Here's the clean debdiff patch which
fix this problem :
http://upload.leservicetechnique.com/bugs/gnucashdesktop.debdiff
--
Saïvann
--- End Message ---
Package: guile-1.8
Version: 1.8.3+1-1
Severity: serious
--- Please enter the report below this line. ---
Guile 1.8 does not build on sparc.
http://buildd.debian.org/fetch.cgi?&pkg=guile-1.8&ver=1.8.3%2B1-1&arch=sparc&stamp=1195798674&file=log
--- System information. ---
Architecture: i386
Ker
Upstream libofx does not have any immediate ideas about what next steps
should be.
I am in contact with the OFX Consortium about granting a license which
we can work with.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED
On Sat, 2008-01-12 at 14:45 +0100, Joerg Jaspert wrote:
> Package: libofx
> Severity: serious
>
> Hi
>
> (a bug to not forget this issue, together with the reject of the newer
> version from NEW).
>
> this package contains non-free files, the DTDs, at least those from the
> OFX standard, have a
Package: gnucash
Version: 2.2.3-1
Severity: serious
This version of the Debian gnucash package does not support libofx. But
there is hope that the libofx licensing problems which are the root
issue may be settled. Accordingly, this non-ofx version should not
migrate into testing until we have so
On Sat, 2007-09-08 at 09:52 +0100, Neil Williams wrote:
> Package: gnucash
> Version: 2.0.5-1.1
> Severity: serious
> Tags: patch
> Justification: no longer builds from source
>
> debian/rules needs to be tweaked to allow gnucash to use the current
> version of g-wrap in unstable. As a side-effect
On Sun, 2007-09-09 at 10:12 +0200, Michal Politowski wrote:
> Package: gnucash
> Version: 2.0.5-2
> Severity: grave
> Justification: renders package unusable
>
> After upgrade to 2.0.5-2 gnucash fails to start with the following message:
> ERROR: Could not find slib/require.scm in ("/usr/sh
On Sun, 2007-09-09 at 11:43 +0200, Michal Politowski wrote:
> Symlink only changed the error to
> ERROR: Unbound variable: slib:features
I know what this means and why it's happening; Rob Browning (the Debian
guile guy) also should. He and I can hopefully work together to get it
repaired soon.
On Thu, 2007-09-13 at 22:49 -0400, Ken Wolf wrote:
> I too am experiencing the same problem described in this thread.
> Is there a fix or workaround to this issue?
I'm talking to the guile maintainer, but he is taking the position at
the moment that he must wait until guile upstream decides to act
On Fri, 2007-09-14 at 15:20 +1000, Bryan Cebuliak wrote:
> Current stable gnucash 2.2.1 will build properly as long as guile
> 1.8 [and its dependants] is[are] not installed. Guile 1.8 can be
> installed later with no interference. See:
> http://wiki.gnucash.org/wiki/Building
Is this true e
On Fri, 2008-10-03 at 07:56 +0200, Luk Claes wrote:
> tags 500615 + patch
> thanks
>
> Dear maintainer,
>
> I've prepared an NMU for mmorph (versioned as 2.3.4.2-11.1) and uploaded it
> to DELAYED/3. Please feel free to tell me if I should delay it longer.
Yes, please remove it from the upload q
On Fri, 2008-10-03 at 22:48 +0200, Luk Claes wrote:
>
> I didn't wait at all, I informed maintainers at the beginning of the
> cycle, though if at the end of the cycle there are too much versions (5
> in this case) of a library we can either remove the whole lot that
> depends on them or make them
On Wed, 2008-08-27 at 17:46 +0200, Bas Wijnen wrote:
> Package: gnucash
> Version: 2.2.6-1
> Severity: grave
> Justification: causes data loss
>
> I was trying to use gnucash over sshfs, to allow several machines to
> handle the same file. It complained that it was unable to get a lock,
> and so
On Thu, 2008-08-28 at 20:34 +0200, Micha Lenk wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> Bas Wijnen wrote:
> > On Wed, Aug 27, 2008 at 01:02:56PM -0700, Thomas Bushnell BSG wrote:
> >>> I was trying to use gnucash over sshfs, to al
The logic expressed in the #gnucash discussion is bogus. Errors like
ENLNK or EMLNK would also prevent link but not prevent copying. There
is no harm in at least trying copying if EROFS comes in, and the code
shouldn't assume that every error on link will be an error on copying.
Thomas
--
On Thu, 2008-08-28 at 23:39 +0200, Micha Lenk wrote:
> > There are far better error codes to return.
>
> ... what error codes listed in the link(2) manpage do you think of?
> The best one that comes to my mind is EPERM: "The filesystem containing
> oldpath and newpath does not support the creation
See http://nopaste.debianforum.de/9635 for what might be a good patch
for this bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, 2009-04-21 at 14:06 +0200, Vincent Fourmond wrote:
> severity 524023 grave
> thanks
>
> Hello,
>
> As lilypond simply does not work in unstable, I'm raising the
> severity to grave. The patch mentionned in the bug report files works
> perfectly fine. I hereby announce my intention to
101 - 200 of 257 matches
Mail list logo
