I am not only in approval of Micha's NMU, but if he judges a version
upgrade of gnucash to be suitable and is interested in preparing that
NMU, I approve that too.
Thomas
On Tue, 2009-09-01 at 19:17 +0200, Joachim Breitner wrote:
> Hi,
>
> Am Dienstag, den 01.09.2009, 15:18 +0200 schrieb Micha
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
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 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 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
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 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
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
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]
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
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
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: 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, 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
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
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
--- 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 ---
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
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
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 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
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
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
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: 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
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 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 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 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 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-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?
>
>
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 Wed, 2007-04-18 at 11:21 -0700, Russ Allbery wrote:
> Can you try applying the following patch to the source package and
> rebuilding? I don't have a Debian PPC system running AFS to easily test
> with, but we think this may fix the problem.
Sorry I couldn't get to it earlier, but I can confir
On Wed, 2007-04-18 at 11:21 -0700, Russ Allbery wrote:
> Can you try applying the following patch to the source package and
> rebuilding? I don't have a Debian PPC system running AFS to easily test
> with, but we think this may fix the problem.
I'm in the middle of a crunch moment in the preparat
Package: openafs-client
Version: 1.4.4.dfsg1-1
Severity: grave
Justification: renders package unusable
When I run aklog, I get the following helpful error message:
~$ aklog -d
Authenticating to cell becket.net (server aquinas.becket.net).
We've deduced that we need to authenticate to realm BECKET
severity 402753 important
thanks
On Thu, 2007-02-08 at 02:29 +0200, Yitzchak Gale wrote:
> This package is supposed to provide documentation,
> but none at all is provided due to bugs. So this
> is a grave bug.
Your hypothesis is incorrect. But thanks for the attention to the bug,
and the work
> I noticed the above package upgrades are for the i386 architecture. Is
> the fix being
> ported to the alpha architecture as well?
No port is necessary as such. The autobuilders will pick the package up
and upload it, though the alpha one seems to be a bit behind right now
so I don't know how
On Sun, 2007-01-14 at 03:55 -0800, Steve Langasek wrote:
> On Sat, Jan 13, 2007 at 09:26:13PM -0800, Thomas Bushnell BSG wrote:
> > Hi Steve; you were very helpful with the last alpha bug reported by this
> > submitter; I'm wondering if you can give it a little attention. I
On Fri, 2007-01-12 at 21:38 +0100, Loïc Minier wrote:
> On Fri, Jan 12, 2007, Thomas Bushnell BSG wrote:
> > If the package does not build properly on a normal system, under the
> > circumstances you describe, that means there is a bug.
> >
> > It does not mean that the
On Fri, 2007-01-12 at 21:26 +0100, Loïc Minier wrote:
> On Fri, Jan 12, 2007, Thomas Bushnell BSG wrote:
> > No. You are making all kinds of assumptions, and just guessing, I
> > think. The debian/rules file explicitly uses guile-1.6 unconditionally.
> > If that isn'
On Fri, 2007-01-12 at 20:20 +0100, Loïc Minier wrote:
> On Fri, Jan 12, 2007, Thomas Bushnell BSG wrote:
> > I am saying that the build failure, in my opinion, has *nothing to do*
> > with missing packages. There is no indication in the error that the
> > problem is a
On Fri, 2007-01-12 at 10:25 +0100, Loïc Minier wrote:
> On Thu, Jan 11, 2007, Thomas Bushnell BSG wrote:
> > I don't see any reason to think there are missing build deps. It seems
> > rather like the build is pulling in parts of guile-1.8 for some bogus
> > reason. I ca
On Thu, 2007-01-11 at 21:49 +0100, Loïc Minier wrote:
> On Thu, Jan 11, 2007, Jim Woodruff wrote:
> > Here's a thought, since the error referred to guile 1.8
> > (ERROR: Could not find slib/require.scm in ("" "" "/usr/share/guile/site"
> > "/usr/share/guile/1.8" "/usr/share/guile"))
> > Shouldn't
On Thu, 2007-01-11 at 08:58 -0800, Jim Woodruff wrote:
> Loïc Minier formed by artistic effort the following on 01/11/07 07:31:
> > On Thu, Jan 11, 2007, Jim Woodruff wrote:
> >
> >> I have attached my debug info:
> >>
> >
> > That's already very interesting, thanks: it shows that the bug
On Thu, 2007-01-11 at 10:19 -0800, Jim Woodruff wrote:
> Here's a thought, since the error referred to guile 1.8
> (ERROR: Could not find slib/require.scm in ("" "" "/usr/share/guile/site"
> "/usr/share/guile/1.8" "/usr/share/guile"))
> Shouldn't I have the guile-1.8-dev? This package doesn't
> se
On Wed, 2007-01-10 at 14:43 -0800, Jim Woodruff wrote:
> I have the following installed:
>
> libgail-common1.8.11-4
> libgail-dev 1.8.11-4
> libgail17 1.8.11-4
Ah, helpful. I think I may know what the problem is. Can you send me
the contents of /usr/share/doc/libgail17/changel
tag 406378 +unreproducible, +moreinfo
thanks
On Wed, 2007-01-10 at 10:04 -0800, Jim Woodruff wrote:
> Package: gnucash
> Version: 2.0.2-2.1
> Severity: grave
> Justification: renders package unusable
>
> Everytime I try to open an account register, GnuCash crashes with the dialog
> box
> "GnuCas
On Sun, 2006-12-31 at 21:10 +0100, Loïc Minier wrote:
> Finally, since glib's upstream added support for key names with MIME
> types chars such as "/" and "+" for gnome-vfs2, I also added a patch to
> silently support key names with spaces in the middle of the name (not
> at the beginning or at
On Sat, 2006-12-30 at 17:15 +0100, Josselin Mouette wrote:
> Le vendredi 29 décembre 2006 à 10:48 -0800, Thomas Bushnell BSG a
> écrit :
> > Despite what Josselin has said, I can see no indication from a brief
> > perusal of the upstream branch sources in trac that upstream gnu
Despite what Josselin has said, I can see no indication from a brief
perusal of the upstream branch sources in trac that upstream gnucash
either no longer uses these key files or has changed away from the keys
with embedded spaces.
I have asked gnucash upstream for their thoughts on the long-term
On Fri, 2006-12-29 at 03:06 +0100, Josselin Mouette wrote:
> Le jeudi 28 décembre 2006 à 17:29 -0800, Thomas Bushnell BSG a écrit :
> > On Fri, 2006-12-29 at 01:56 +0100, Josselin Mouette wrote:
> > > Now, if you don't provide us with the necessary data, we won
On Fri, 2006-12-29 at 08:44 +0100, Martin Schulze wrote:
> For the sake of the upcoming release, I wonder how many files / users
> are affected by this change? Is it really release-critical? If not,
> would it not helpe if Thomas provides a script in the gnucash package
> that adjusts the keys th
On Fri, 2006-12-29 at 01:56 +0100, Josselin Mouette wrote:
> Now, if you don't provide us with the necessary data, we won't be able
> to fix the regression it introduces in gnucash.
Here is a sample file; I suspect the offending character is the space,
if I'm reading Marc Brockschmidt's regex righ
On Fri, 2006-12-29 at 01:56 +0100, Josselin Mouette wrote:
> Now, if you don't provide us with the necessary data, we won't be able
> to fix the regression it introduces in gnucash.
There are clearly two plausible solutions to the underlying problem:
1. Change gnucash to conform to the new behavi
On Fri, 2006-12-29 at 01:41 +0100, Josselin Mouette wrote:
> > 1) The release team has asked us not to upload changes which are not
> > destined for etch, and making gnucash work with the glib in unstable is
> > therefore a low priority;
>
> The glib in unstable is destined for etch, whether you l
On Fri, 2006-12-29 at 00:49 +0100, Josselin Mouette wrote:
> Le jeudi 28 décembre 2006 à 14:47 -0800, Thomas Bushnell BSG a écrit :
> > Package: glib2.0
> > Version: 2.12.5-3
> >
> > This version of glib (both 2.12.5-3 and 2.12.6-1) causes an important
> > reg
On Tue, 2006-12-26 at 17:27 +0100, Robert Schueler wrote:
> Package: gnucash
> Version: 2.0.2-2.1
> Severity: grave
> Justification: renders package unusable
>
> Gnucash fails to write the config file under .gnucash/books/ which store data
> about configured reports and windows-size.
> Following
Version: 2.0.3-2.1
Package: gnucash
Severity: serious
NMU upload of gnucash fails to build on arm.
make[5]: Entering directory
`/build/buildd/gnucash-2.0.2/src/network-utils/test'
if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../.. -I../../..
-I../../../src/test-core -I.. -pthread
From Paul's comments, it seems to me that there is no need for the
current Aleph it's been replaced, and it's three years old. I have no
opinion about whether it ought to be dropped from Debian.
Paul also explains that AFNIX replaced Aleph, and should not be thought
of as just a new version with
On Tue, 2006-12-12 at 21:20 +0100, Frank Küster wrote:
> We've got a problem here, since all three packages are in testing,
> provide /usr/bin/aleph, and conflict with each other (or rather, the
> *tex* packages conflict with aleph).
Eek.
>
> The right solution to this would be to package the "n
severity 402692 important
tags 402692 +unreproducable, +moreinfo
thanks
On Mon, 2006-12-11 at 23:26 -0500, James Aspnes wrote:
> Package: gnucash
> Version: 2.0.2-2
> Severity: grave
>
> Gnucash crashes when tabbing off of an autofilled description in
> register entry. This error message appear
The latest version of guile, guile-1.8, does not work on ia64. See
#401400 for more information.
Because lilypond depends on guile, this causes a problem for further
support for lilypond on ia64 in Debian. The latest version of lilypond,
2.8, does not build against guile-1.6.8, and thus requires
On Tue, 2006-12-05 at 00:44 +, Adam D. Barratt wrote:
> No, I'm not a developer. I have however being triaging ftp.d.o bugs for
> some time now.
Cool; I know that bug triage is a hugely important thing and I am very
appreciative of those who help me out with my packages doing that.
> The addr
Severity: serious
Package: ftp.debian.org
Can you please remove the out-of-date ia64 package for lilypond in
unstable? The crucial prerequisite guile-1.8 does not work on it, and
the guile maintainer does not have the necessary expertise to fix it
right away. For the moment, this means that guil
On Sun, 2006-11-12 at 14:45 -0800, Steve Langasek wrote:
> found 361354 1:1.1+dfsg1-1
> thanks
>
> Ok, this bug still manifests in mailutils 1.1, the current version in
> unstable.
>
> Observing the effects myself, and rereading your report carefully, I do have
> to question again the severity as
On Sun, 2006-11-12 at 06:29 -0800, Steve Langasek wrote:
> Hi Thomas,
>
> For my part, I do have to wonder if an mbox with an embedded NUL is even a
> valid mbox file. What is your MTA/MDA for this setup?
Perfectly ordinary Debian exim and mail spool file format.
If you believe that this is not
On Fri, 2006-11-10 at 15:04 -0800, Steve Langasek wrote:
>
> > Architecture: !s390
>
> No, this syntax is not supported.
What is needed to finally support it? It's been wanted for years now
and is clearly better than not having it.
Thomas
signature.asc
Description: This is a digitally sign
Package: seahorse
Version: 0.9.5-3
Severity: grave
seahorse reliably crashes when I ask it to delete a key. I have lots of
keys.
In the "Keys I've Collected" tab, I right-click on a key, and select
"delete"
(or I use the pull down menu). A dialog asks for confirmation, I say to
go ahead and del
Package: guile-1.8-dev
Severity: grave
Version: 1.8.1+1-1
Hi Rob...wonderful that guile 1.8 is now in Debian! Thanks for all
the hard work.
Unfortunately, some lilypond checks related to guile fail.
checking libguile.h usability... no
checking libguile.h presence... no
checking for libgu
Package: openoffice.org-core
Version: 2.0.4~rc3-1
Severity: grave
Justification: renders package unusable
When I start oowriter now, on no document (so I get the default "Untitled1"
name) (not sure if this is a relevant fact), the font size display says "1"
from the get-go instead of my expected
Package: openoffice.org-core
Version: 2.0.4~rc3-1
Severity: grave
Justification: renders package unusable
oowriter now crashes on startup with the following message:
/usr/lib/openoffice/program/soffice.bin: error while loading shared libraries:
libicuuc.so.26: cannot open shared object file: N
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
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
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
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
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
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
I'm not sure after all that the lilypond failures were the same bug.
They are a different bug: that fontconfig doesn't reliably work right
if $HOME doesn't exist.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The original submitter's bug report says that the debconf question
overwrite_existing_local_conf is false, which should answer the
comment made lower:
Please make sure you have allowed fontconfig to replace your
fonts.conf file.
If anything, this seems like an updating problem? How could t
The s390 build of lilypond 2.6.5-1 (but not others) also failed for
apparently this reason. See
http://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.5-1&arch=s390&stamp=1158538806&file=log&as=raw
At the end:
cd ./out ; fc-cache .
/build/buildd/lilypond-2.6.5/mf/out: failed to write cache
m
Builds of lilypond 2.6.5 worked tonight, with the wonderful assistance
of Keith Packard, the fontconfig maintainer who fixed an interface bug
in a speedy way. There are some minor packaging nits I'll need to fix
tomorrow, and then I will be able to upload 2.6.5. That should make
it into etch.
I
Bill Allombert <[EMAIL PROTECTED]> writes:
> I spent quite some time investigating #359855...
>
> Apparently you need to add ttf-bitstream-vera and ttf-freefont to the
> build-depends to fix the problem.
>
> At least that worked for me, though I don't know exactly why.
Splendid; I'm going to try
Rob Browning, the guile maintainer, has been doing a lot of hard work
trying to get guile-1.8 into Debian. Turns out there were some
critical timing bugs affecting the operation of fork in the guile
threading implementation, bugs which are too intractible to solve
immediately.
Rob has uploaded g
"Aaron M. Ucko" <[EMAIL PROTECTED]> writes:
> gnucash depends on having an identical version of gnucash-common,
> which is fine for regular uploads but breaks on binary-only NMUs, such
> as the one that just happened for the libdbus-1-3 and libofx3
> transitions. To correct this, please declare a
tags 359855 +help
thanks
<[EMAIL PROTECTED]> writes:
> On Wed, Aug 02, 2006 at 11:35:35AM -0700, Thomas Bushnell BSG wrote:
>>
>> These bug will be closed certainly by the time lilypond 2.8 hits the
>> archive; work is proceeding on that effort.
>>
>> T
reassign 378346 libgail-dev
retitle 378346 libgail-dev: gnucash crashes in libgail on alpha
thanks
Reassigned to libgail in accordance with upstream's recommendation;
see below.
Thomas
--- Begin Message ---
On Fri, Aug 11, 2006 at 12:32:27PM -0700, Thomas Bushnell BSG wrote:
&g
Jim Woodruff <[EMAIL PROTECTED]> writes:
> To make sure, I restarted gnucash, ran the check & repair all utility,
> and resaved
> my account file. bug #378346 is still there.
Thanks for checking; this is what I suspected would be the case.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
> Package: gnucash
> Version: 2.0.1-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
Thank you for your bug report; I have tracked this down to a bug in
g-wrap which has now been reported.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL
Package: libgwrap-runtime0-dev
Version: 1.9.6-3
Severity: serious
The 1.9.6-3 ia64 version of g-wrap contains a bogus pkgconfig file,
with the line:
module_directory=${datarootdir}/guile/site
Where the powerpc and other versions contain the line:
module_directory=${prefix}/share/guile/site
Margarita Manterola <[EMAIL PROTECTED]> writes:
> Hola Thomas Bushnell BSG!
>
>> > I've prepared a new package for gal, and I intend to upload it.
>> Are we in a zero-day NMU period?
>
> Indeed, I was fixing an RC bug (gal FTFBSed), that's why I upload
Margarita Manterola <[EMAIL PROTECTED]> writes:
> I've prepared a new package for gal, and I intend to upload it.
Are we in a zero-day NMU period?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
These bug will be closed certainly by the time lilypond 2.8 hits the
archive; work is proceeding on that effort.
The bugs are RC bugs, but do not seem to be the sort that pose any
actual inconvenience to anyone, so I don't intend to fix them in
lilypond 2.6. However, if this poses some inconveni
Hi Steve; you said a bit ago that you were going to try to rebuild
libgail.so so that a more useful backtrace from the gnucash crash on
alpha could be obtained.
Should I keep on waiting for this, or proceed on a different tack?
I think that upstream would be happy to take the lead on debugging i
Loïc Minier <[EMAIL PROTECTED]> writes:
> So IIUC, a new upstream release requires python 2.4 and fixes the
> gcc-4.1 build failure.
This is correct.
> Concerning the new upstream release, I suggest you follow the Python
> transition and package lilypond with python 2.4 as the PYTHON runtime
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.
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.
>
>
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
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
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
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
1 - 100 of 257 matches
Mail list logo
