Thanks for the report.
> /«PKGBUILDDIR»/engine/snappea/kernel/tables.c:229:67: error: narrowing
> conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]
I believe this is fixed by declaring the elements of index_by_permutation[] as
signed char, not just char. Caveat: I haven’t tried
Thanks for the report; I can reproduce the error here also.
I haven’t started digging yet for a resolution, but others may be ahead of me -
see bug #797234 for the source-highlight package (on which regina-normal
depends, and where the linking looks to be failing).
- Ben.
I’ve just tried to reproduce this, and I can’t - regina-normal seems to be
building fine under current sid/amd64 with gcc-5 and g++-5 installed and the
relevant CC / CXX environment variables set. The build log confirms that gcc-5
and g++-5 are indeed being called during the build.
I’d be
A note for these bug reports: much of the development on regina-normal has been
queued up behind the fact that the current version (circa 2009) includes a
KDE3-based GUI, and much of the new development has been queued behind the
(fairly hefty) port of the GUI (KDE3 - KDE4) and the underlying
Hi,
No reply in months, uploading an NMU which fixes this FTBFS. Please
find the patch attached.
Thanks for this (and apologies for the silence).
Ben.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
severity 476029 important
tags 476029 +pending
thanks
Hi,
During a rebuild of all packages in sid, your package failed to build on i386.
AFAICT the problem is because your build environment already has pre-set
CFLAGS and CXXFLAGS (both set to -g); it should not happen in a clean
build
Hi Sune,
kdeedu build doesn't fail by itself if it isn't found as it is only optional,
but we test afterwards if it is actually build.
As an aside, what I've done with regina-normal (which also uses
boost.python) is make debian/rules check the config.log immediately
after configure finishes,
No, its enough to rebuild the package with the new gcc package pointing
to gcc-4.1 installed.
Sure, but relying on (build-essential + libgcj-dev) assumes that the gcc
and gcj versions will always be the same. Past experience has suggested
this is not the case, which is why I've leaned towards
IMO its now the best time to get rid of this package totally.
FWIW, I'd forgotten that java-gcj-compat-dev even existed until your
mailout to d-d-announce last month (GCJ 4.1 transition). In this
mailout you ask maintainers of JNI packages to use
-I/usr/lib/jvm/java-gcj/include, which relies
Hi,
Probably a solution would be including libgcj7-dev.
It does. It build-depends on libgcj-dev (= 4:4.1.0), which brings in
libgcj7-dev.
From the amd64 build log (which failed in this way):
Unpacking libgcj7-dev (from .../libgcj7-dev_4.1.1-2_amd64.deb) ...
I suspect my problem is
Package: drgeo-doc
Version: 1.5-2.1
Severity: serious
Hi.
It seems that drgeo-doc (optional) depends on the web browser dillo (extra).
This means that a higher-priority package depends on a lower-priority
package, which is not allowed by policy (section 2.5).
However, I don't see why dillo is
forwarded 353814 http://bugs.kde.org/show_bug.cgi?id=122465
thanks mate
Hi,
I've filed this one upstream as well (#122465). FYI.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: kdelibs-bin
Version: 4:3.5.1-2
Severity: serious
Hi,
I have a KDE application whose documentation is licensed under the GPL.
In particular, its index.docbook contains the line:
legalnoticeunderGPL;/legalnotice
When I build the application and meinproc is run over the docbook
Hi again,
Just to confirm:
As for the cause: I'm not too familiar with meinproc internals, but I
suspect the culprit is
/usr/share/apps/ksgmltools2/customization/kde-chunk.xsl.
Around lines 90--100 it does look rather like the fdl-notice is being
dropped into the documentation regardless
Package: jikes-gij
Version: 1:1.22-3
Severity: serious
Hi,
Currently jikes-gij is uninstallable in sid, since none of the
libgcj*-common dependencies can be satisfied.
It seems the jar is now provided by libgcj6-jar, not libgcj6-common.
I therefore suspect that you'll be fine if you add a
Hi Luk,
There's a couple of other patches queued that I might take another look
at -- the larger python-pgsql update has been stalled to date because of
a bug in python2.4.
At any rate, since this is a serious issue I'll do an upload this week.
If you haven't heard from me by the weekend,
A no source-changes upload should be enough to fix this bug, thanks in
advance. I can also provide a NMU if needed.
Please do -- I'm out of action here until Dec 15.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
python2.1-egenix-mxdatetime is not available in sid. Maybe
python2.1-pgsql should be dropped in favor of python2.4-pgsql?
There are problems with bringing in python2.4-pgsql, see #334022.
However, I'll do an upload this weekend that removes 2.1 and 2.2 (this
has been waiting in the wings for
Ah, yes, I forgot to mention this when I mailed the security team
earlier.
Note that according to the Ubuntu advisory, this bug might also be
present in the koffice-libs package.
The issue for debian lies specifically within the kword binary package.
Unless I'm mistaken, debian's koffice-libs
Hi,
Attached the patch for the version I intend to upload.
Regarding koffice: I'd be happy if you could give me another 48 hours
or so to finish the koffice 1.4.2 packaging (which I agree has been
terribly delayed thus far). If you don't see anything uploaded by then
however, please do go
Hi,
Attached the patch for the version I intend to upload. Please respond if
you don't want this NMU to happen, if you are working yourself on a
patch or if you think that the attached patch won't work.
Looks fine to me, please do go ahead with the NMU.
Ben.
--
To UNSUBSCRIBE, email to
Package: kde-i18n
Severity: serious
Hi,
Several kde-i18n packages contain files that used to be shipped with the
old kturtle ( 4:3.4.2). There is no versioned replaces however, which
means the upgrade can break (as happened with me today).
The old kturtle package provided the following files,
Package: libqscintilla6
Version: 1.6-1
Severity: serious
Hi,
Both libqscintilla5 and libqscintilla6 ship the file:
/usr/lib/qt3/plugins/designer/libqscintillaplugin.so
However, libqscintilla6 contains no conflict with libqscintilla5. As a
result, the system will happily try to install them
Package: kde-i18n-de
Version: 4:3.4.2-3
Followup-For: Bug #326610
Hi,
Bug #326610 was filed because kde-i18n-de needs to replace
khangman ( 4:3.4.2). In fact this affects several languages, not just
kde-i18n-de.
The old khangman provided all of the following files:
Hi,
KBear is in the process of being adopted by someone else, but I haven't
yet heard if they plan on taking it through the g++-4 transition. If
I don't hear back in the next day or so, I'll transition it myeslf (at
which point it will become installable again).
b.
--
To UNSUBSCRIBE, email
Hi,
Just a note: Although most of kdeaddons' build-deps are ready now,
we're still waiting on libdb4.2++ to be transitioned.
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
The package depends on slang1 which is not available in unstable.
This renders the package unusable/uninstallable in unstable.
Can't do anything about this until the KDE/gcc4 transition goes through,
I'm afraid.
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
severity 322012 wishlist
thanks mate
This source package includes koffice-i18n-zhcngb2312 and
koffice-i18n-zhtwbig5. These otwo packages are dummy packages that
were present in sarge, etch and sid but were not present in woody.
Why is this RC?
Ben.
--
To UNSUBSCRIBE, email to [EMAIL
reassign 319154 kdelibs4-dev
thanks mate
(Reassigning to kdelibs which provides the offending headers.)
Hi Blars,
Things will almost certainly be broken at the moment for KDE packages
while the gcc4 transition is taking place. All gcc4-related errors will
be dealt with by the maintainers
Hi,
As I understand it, nothing can be done about this until the gcc4
transition, since C++ uploads are currently restricted according
to the transition policy.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
As I understand it, nothing can be done about this until the gcc4
transition, since C++ uploads are currently restricted according
to the transition policy.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
As I understand it, nothing can be done about this until the gcc4
transition, since C++ uploads are currently restricted according
to the transition policy.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
The gcc4 transition has already started.
Yes, that was what I meant by my messages -- I was noting in the BTS
why I can't fix any of these RC bugs at the moment.
but now you
know that there are two good reasons to upload kdeartwork ASAP. :)
Yes, I am aware that there are two
Hi,
Just a note for the BTS: the libpq4 rebuild does not fix this problem
for me. Moreover, #313507 and #313602 suggest that I am not alone.
It appears that the postgresql maintainer will be fixing this problem in
libpq4 shortly, so watch this space.
b.
--
To UNSUBSCRIBE, email to [EMAIL
tags 312847 + pending
tags 311328 + pending
thanks mate
Hi. Just a note that fixes for these bugs are ready to go, and will be
uploaded once libpq4 has fixed its unix socket locations (#313602).
b.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi,
Thanks for the report, and thanks Roger for verifying that the libpq4
rebuild fixes it.
I haven't uploaded these, but I can NMU if needed.
Please don't -- the postgresql 8.0 / libpq4 transition has only just
happened and the bug report is but a day old, and there are other things
I'd like
can you give me a hint, when this bug could be fixed?
You'll have to ask the kdevelop3 maintainer. At this stage I've done
all I can do until he uploads a new kdevelop3 without the conflicting
files.
Not beeing able to install kdevelop is very
frustrating, when you need it to work ;)
One
Hi,
Currently there is a conflict with the subversion kioslave appearing in
both kdevelop3-plugins in sid and kdesdk-misc 3.4.x.
My understanding is that kdevelop has actually copied the svn kioslave
from KDE 3.4 into its own source tree so that the svn kioslave is
available from kdevelop + kde
CVS commit by cloose:
Changed license from QPL to GPL v2 or later.
Once again, my many thanks to all those involved.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
tags 301785 + experimental
thanks mate
Hi.. just a note that this bug relates to the experimental and
unofficial KDE 3.4 packages on alioth, and not to any of the packages in
woody, sid or sarge.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi,
Can you please run kturtle from a console and let me know what error
messages (if any) are written to the console?
Also, does kturtle offer a window with a backtrace when it crashes? If
so, could you please send a copy of that backtrace?
(I can't reproduce this crash on my machine.)
Ben.
What about backporting for KDE 3.4, the current KDE version?
If it's possible to do this for KDE_3_3_BRANCH also then I'd be most
appreciative, since KDE 3.3 is currently the most likely candidate for
the coming debian release.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Hi,
Can you please try moving your ~/.kde/share/config/kturtlerc out of the
way, and let me know if it still crashes?
If it fixes the crash:
- Can you check whether the file had user write permissions?
- Can you send me a copy?
Thanks - Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Hi again,
At this stage it seems that everyone is happy to go with a dual QPL/GPL
license for cervisia. My question now is how to go forward with the change.
Thiago has written with the following instructions:
If you people are ok with a dual license, then please place notices in
all your
I prefer a single GPL license and AFAIK Christian too. I think this
shouldn't be a problem, right?
I don't see why not; from Bernd's reply (courtsey of Andras), he seems
happy with this also.
Ben.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
severity 289646 important
thanks mate
Hi. I've uploaded a new kdesdk with the s/check/checkWord/ patch, so
I'm lowering the severity of this bug. I'm leaving it open however,
since kbabel was in fact using the kdelibs API as documented -- in
theory kbabel was doing nothing wrong, so the problem
Hi,
Many thanks for looking after this.
Now to the real topic: if the licensing of the Cervisia part is a
problem for applications embedding or using it, it is fine for me
to change the license to GPL.
FWIW, the other authors have said they are happy with a dual license
(choice of QPL or
Hi,
It's me writing about Cervisia licensing again. We still haven't heard
back from Bernd Gehrmann at this stage, which means there's not really
much that we can do. AFAICT he hasn't been around for a few years now;
does anyone know of a way that we might be able to contact him? I've
already
Hi,
Thanks very much for looking at this bug.
I've just tested latest umbrello version (which will be released with
kde 3.4) and this works perfectly.
You mentioned in an earlier mail that you couldn't reproduce the data
loss with the current umbrello in sid. What then are you referring to
Well, as I said I couldn't reproduce the mentioned bug, but I got constant
annoying crashes while trying to do it, and the fact that I don't managed to
reproduce it doesn't mean it doesn't exist.
Everything works ok in 1.4.0-beta2, I've run diff through both versions (the
one in kde
Hi,
Thanks to everyone for their helpful responses.
BTW, about which KDE version do we talk? Is it enough if we change the
license in CVS HEAD aka KDE 4 (maybe 3.5)?
If a license change is likely, I would be most appreciative if the
change could be made in KDE_3_3_BRANCH also (since it
Hi.
Currently cervisia is licensed under the QPL. As the maintainer of
kdesdk in debian, I am unfortunately faced with having to remove
cervisia from the debian distribution since the QPL does not meet with
debian's free software guidelies. Of course this is debian's decision,
but nevertheless
Package: pmk
Severity: serious
Version: 0.9.0-1
Hi. On a fresh install of pmk (no previous version was installed), the
postinst fails at configure time (see below).
What appears to be happening is that the postinst is called as
postinst configure (no version argument), causing the command
dpkg
53 matches
Mail list logo
