Package: network-manager
Version: 0.7.2-2
Severity: important
When running in managed mode with a wireless interface with WPA, after
logging in to KDE there will be two instances of wpa_supplicant, both
trying to bring the interface up simultaneously. This results in the
connection being brought
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
what is the use case for Sesame in Virtuoso? IIUC Virtuoso was going to
work as a separate backend for Nepomuk (?), independent of Sesame.
In other words, does it make sense to put effort into packaging Sesame
as a Nepomuk backend?
Cheers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
what is the use case for Sesame in Virtuoso? IIUC Virtuoso was going to
work as a separate backend for Nepomuk (?), independent of Sesame.
In other words, does it make sense to put effort into packaging Sesame
as a Nepomuk backend?
Cheers,
Package: network-manager
Version: 0.7.2-2
Severity: important
When running in managed mode with a wireless interface with WPA, after
logging in to KDE there will be two instances of wpa_supplicant, both
trying to bring the interface up simultaneously. This results in the
connection being brought
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Koch wrote:
The ivy thing will of course be patched out and replaced by the correct
classpath entries to /usr/share/java/...
No need. Ivy is already in Debian, and many packages provide Maven metadata.
The Ivy config just needs to be
https://bugs.kde.org/show_bug.cgi?id=204235
--- Comment #1 from Marcus Better marcus better se 2009-12-22 14:43:19 ---
Same crash with KDE 4.3.4 and Qt 4.6.0 (Debian).
Application: Knotes (knotes), signal: Segmentation fault
The current source language is auto; currently c.
[KCrash Handler
Package: kipi-plugins
Version: 0.9.0-1+b1
Severity: normal
The Vcs-Svn header points to
svn://svn.debian.org/pkg-kde/kde-extras/kipi-plugins/branches/kde4
which does not exist. It should probably be
svn://svn.debian.org/pkg-kde/kde-extras/kipi-plugins/trunk
-- System Information:
Debian
Package: kipi-plugins
Version: 0.9.0-1+b1
Severity: normal
When choosing to send an image by e-mail with Digikam, and selecting
default in the MUA list, with KDE's default MUA being set to
icedove, brings up a blank Icedove composer window. There is no image
attachment.
-- System Information:
tag 561844 patch
thanks
Here is a patch.
Cheers,
Marcus
diff -rux debian kipi-plugins-0.9.0.orig/sendimages/emailpage.cpp kipi-plugins-0.9.0/sendimages/emailpage.cpp
--- kipi-plugins-0.9.0.orig/sendimages/emailpage.cpp 2009-12-01 16:35:33.0 +0100
+++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tag 561724 pending
thanks
Xavier,
thanks for applying the patch. (You probably want to close this bug in
the changelog entry.)
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tag 561724 pending
thanks
Xavier,
thanks for applying the patch. (You probably want to close this bug in
the changelog entry.)
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
Package: kipi-plugins
Version: 0.9.0-1+b1
Severity: minor
Tags: upstream
In the sendimages plugin, there is an entry for Mozilla in the
list of MUAs. This should probably be removed because I doubt anyone
has a MUA actually called Mozilla anymore - witness the fact that
the option is guaranteed
** Bug watch added: Debian Bug tracker #555133
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555133
** Also affects: bluez (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555133
Importance: Unknown
Status: Unknown
--
/usr/lib/bluetooth/plugins/netlink.so:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tag 561724 pending
thanks
Xavier,
thanks for applying the patch. (You probably want to close this bug in
the changelog entry.)
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
Package: kdebase-workspace-bin
Version: 4:4.3.4-1
Severity: serious
Tags: patch upstream fixed-upstream
plasma-desktop crashes immediatey on startup in some configurations,
both on login and subsequent manual launches. This is triggered by hal
0.5.14-1, and keeping hal at 0.5.13-6 fixes the
Package: kdebase-workspace-bin
Version: 4:4.3.4-1
Severity: serious
Tags: patch upstream fixed-upstream
plasma-desktop crashes immediatey on startup in some configurations,
both on login and subsequent manual launches. This is triggered by hal
0.5.14-1, and keeping hal at 0.5.13-6 fixes the
Package: kdebase-workspace-bin
Version: 4:4.3.4-1
Severity: serious
Tags: patch upstream fixed-upstream
plasma-desktop crashes immediatey on startup in some configurations,
both on login and subsequent manual launches. This is triggered by hal
0.5.14-1, and keeping hal at 0.5.13-6 fixes the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brice Goglin wrote:
Don't use 1.7.0. And don't use experimental on amd64 until everything is
build.
No problem... I only tried it to see if it helped with the display
corruption I get with mainline kernel 2.6.32. (It didn't.) I get a
completely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brice Goglin wrote:
Don't use 1.7.0. And don't use experimental on amd64 until everything is
build.
No problem... I only tried it to see if it helped with the display
corruption I get with mainline kernel 2.6.32. (It didn't.) I get a
completely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Onkar Shinde wrote:
Would it be useful to have PACKAGE-dev packages for java containing the
source code, so that I can refer to it when developing on top of a
library?
Ideally you shouldn't refer to source code of libraries for writing
your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
found 552706 2.6.26-13lenny2
thanks
I get something similar on our HP Proliant 360DL G5 server. It's a
quad-core Xeon running linux-image-2.6.26-1-openvz-amd64
(2.6.26-13lenny2). This has happened several times during the last few
weeks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
found 552706 2.6.26-13lenny2
thanks
I get something similar on our HP Proliant 360DL G5 server. It's a
quad-core Xeon running linux-image-2.6.26-1-openvz-amd64
(2.6.26-13lenny2). This has happened several times during the last few
weeks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Alan Greenberger wrote:
So it is a java futex problem always showing up on printing and
triggered by iceweasel but not konqueror. It wasn't happening on
Lenny-slow in March. Does anyone have an idea what I could have done to
this system to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Koch wrote:
I'm not experienced enought with eclipse to know, whether such a setup
would make sens for eclipse too. However what surely makes sense, would be
the ability to install plugins not only as debian packages, but also via
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco d'Itri wrote:
On Oct 24, Marco d'Itri m...@linux.it wrote:
I am proposing to set net.ipv6.bindv6only=1 by default for new
installations
Done, let's see what breaks. :-)
All of Java, it seems [1]. I'm very surprised this breakage was known
Package: bugzilla3
Version: 3.2.5.1-2
Severity: normal
The cron job that runs sanitycheck.pl passes the value of the
maintainer configuration parameter with the --login option to this
script. If this address is not also a valid user account, the script
fails:
/etc/cron.daily/bugzilla3:
The name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 560142 openjdk-6
forcemerge 560056 560142
thanks
So somehow Java started to use IPv6 yesterday. Is this connected with the
change in the netbase package?
Yes, looks like it. Not sure which JRE you use, but it affects both
OpenJDK and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 560142 openjdk-6
forcemerge 560056 560142
thanks
So somehow Java started to use IPv6 yesterday. Is this connected with the
change in the netbase package?
Yes, looks like it. Not sure which JRE you use, but it affects both
OpenJDK and
Package: qemu-kvm
Version: 0.11.0+dfsg-1
Severity: important
After upgrading from kvm 88+dfsg-1, my Windows XP VM stopped drawing
the screen correctly. It started fine in a small window (640x480 I
guess) with the Windows startup screen, and then tried to switch to my
configured resolution
https://bugs.kde.org/show_bug.cgi?id=216073
--- Comment #3 from Marcus Better marcus better se 2009-12-07 12:57:09 ---
This went away after I upgraded to Qt 4.6.0 release. Peter, which Qt version
are you on?
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You
https://bugs.kde.org/show_bug.cgi?id=216073
Marcus Better mar...@better.se changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Koch wrote:
- Should all java stuff be repackaged? For example the xmlenc upstream
tarball contains only one jar and some docs. I could as well have removed
these files during package building.
You must remove any jars that are not built
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Koch wrote:
Now I saw, that in the eclipse GIT repository[3] there's one tag
upstream/3.5.1 and another one upstream/3.5.1+repack. I don't know,
whether the eclipse package is doing so, but we could standardize on:
- import the upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Meskes wrote:
You mean that it reboots although watchdog is up and running?
Ok, some more details. It reboots shortly after starting wd_keepalive,
early in the boot sequence. Maybe it is failing to keep up because of
all the disk activity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Fournier wrote:
On the other hand, both tomcat6-6.0.20/{build,extras}.xml (and incidently
tomcat6-6.0.20/debian/rules) seem to download quite a few files.
debian/rules binary should not download anything, please file a bug
with severity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Fournier wrote:
On the other hand, both tomcat6-6.0.20/{build,extras}.xml (and incidently
tomcat6-6.0.20/debian/rules) seem to download quite a few files.
debian/rules binary should not download anything, please file a bug
with severity
Package: rhino
Version: 1.7R2-2
Severity: minor
The man page for rhino says the following about the -opt option:
Optimizes at level optLevel, which must be an integer between 0 and
9.
However there is also a level -1, (interpreted mode, see
https://developer.mozilla.org/en/Rhino_Optimization).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Fournier wrote:
The package is currently missing the extra components (currently a
complete commons-logging implementation
That sounds like code duplication. It is supposedly a package-renamed
version of Commons Logging?
and support for JSR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marc Fournier wrote:
The package is currently missing the extra components (currently a
complete commons-logging implementation
That sounds like code duplication. It is supposedly a package-renamed
version of Commons Logging?
and support for JSR
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why is this needed when there is java.util.UUID? If some other package
depends on it, maybe that should be fixed instead...
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
https://bugs.kde.org/show_bug.cgi?id=216073
Summary: high CPU usage, long delays on most actions
Product: knode
Version: 4.3.2
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority:
https://bugs.kde.org/show_bug.cgi?id=216073
--- Comment #1 from Marcus Better marcus better se 2009-11-25 11:15:05 ---
Created an attachment (id=38566)
-- (http://bugs.kde.org/attachment.cgi?id=38566)
OProfile report with call graph information
--
Configure bugmail: https://bugs.kde.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why is this needed when there is java.util.UUID? If some other package
depends on it, maybe that should be fixed instead...
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
for the past few days I'm experiencing weird CPU thrashing problems in two
KDE apps: Amarok and Knode. Thought I would check if someone else is seeing
this.
When playing MP3 files in Amarok, the X.org process hogs the CPU. It goes
back to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
Knode just started being very slow, taking several seconds to react to
commands, while its CPU usage goes up.
Filed a bug upstream, with oprofile output:
https://bugs.kde.org/show_bug.cgi?id=216073
Cheers,
Marcus
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jedd wrote:
I don't run knode, but I do have amarok running most of the time.
I'm seeing xorg take up an entire core, even when amarok is
not playing anything.
Can you determine if it is related to Amarok at all?
Are you seeing lots of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kevin Krammer wrote:
Could you check whether this might be related to the widget style or icon
theme in use?
I use the default theme, so not sure how to test that.
Switching desktop effects on or off does not make any difference.
Cheers,
Marcus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Baron wrote:
There were certain plasmoids causing the Xorg problem.
I have a number of plasmoids that I didn't change for a long time, but the
X.org problem really occurs exactly when Amarok is playing music.
If Amarok is doing it, kill
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jedd wrote:
Without disk activity it becomes a more curious problem. What
video drivers are you using?
Intel (xserver-xorg-video-intel 2:2.9.0-1, upgraded to that long ago).
Out of curiosity - and the lack of disk activity suggests this isn't
Package: xserver-xorg-core
Version: 2:1.6.5-1
Severity: normal
When I play MP3 music with Amarok, the X.org CPU usage jumps up to
over 70%. As soon as I stop or pause Amarok, it goes back to the
normal level (under 10%).
Not sure if any of these could be related:
Package: qemu-kvm
Version: 0.11.0+dfsg-1
Severity: important
With insserv installed, qemu-kvm does not install correctly over kvm,
since the init script /etc/init.d/kvm is still in place and both init
scripts provide the kvm service.
Building dependency tree
Reading state information... Done
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Meskes wrote:
You mean that it reboots although watchdog is up and running?
It would seem so.
I didn't see any watchdog-related error messages in the syslog, but then
I didn't have verbose mode enabled.
Could you please try with
Package: xserver-xorg-core
Version: 2:1.6.5-1
Severity: normal
When I play MP3 music with Amarok, the X.org CPU usage jumps up to
over 70%. As soon as I stop or pause Amarok, it goes back to the
normal level (under 10%).
Not sure if any of these could be related:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mike Hommey wrote:
forwarded 542768 https://bugzilla.mozilla.org/show_bug.cgi?id=513556
You are not authorized to access bug #513556.
Yeah, I know. See this discussion:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My HP Proliant server rebooted tonight for no apparent reason, after
weeks or months of uptime. After that it started rebooting during the
boot sequence at around the same point (shortly after going multiuser, I
think). I tracked it to the watchdog
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John J Barton wrote:
https://bugzilla.mozilla.org/show_bug.cgi?id=513556
I get You are not authorized to access bug #513556. Is it security-
related?
No but it is classified as such I guess because so many crashes can be
used for exploits.
Do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Did you try setting the ipcp-max-failure option to 30? That seems to do
it in a lot of cases.
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcus Better wrote:
So, a tweet by user X, directed to a list L,
Sorry, that didn't make sense. Let's try again:
A tweet by user X directed to list L (of which X is a member), shows up
in the timeline of L, but not in the friends_timeline of any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
have you considered adding a mechanism for sending a sort of direct
message to a list?
This would allow users to send targeted tweets to a list (provided the
user is a member of the list). It could be incredibly useful. For
example tweets on a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Kaiser wrote:
have you considered adding a mechanism for sending a sort of direct
message to a list?
This would allow users to send targeted tweets to a list (provided the
user is a member of the list).
Not wild about this, because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marcel Molina wrote:
That is indeed an interesting idea that we've been thinking about.
Very nice to hear! :-)
rules around who can send and receive DMs would continue to be
enforced as normal, so for talking purposes, if you DMed a list, only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Kaiser wrote:
The thing I'm not getting is that I don't decide what lists I'm a member of;
Agreed.
I get added to them by the owner of that list. If @spammymcspammer adds me
to @spammymcspammer/spammy_spam, then anyone on that list can
I get the same problem with a FUTEX_WAIT hang when *starting* Eclipse
3.5 on my Debian amd64 squeeze/sid system (kernel 2.6.31.4, libc6
2.10.1-5, openjdk-6-jre 6b16-1.6.1-2). No fakeroot involved.
--
Strange openjdk hang in FUTEX_WAIT
https://bugs.launchpad.net/bugs/309407
You received this bug
I get the same problem with a FUTEX_WAIT hang when *starting* Eclipse
3.5 on my Debian amd64 squeeze/sid system (kernel 2.6.31.4, libc6
2.10.1-5, openjdk-6-jre 6b16-1.6.1-2). No fakeroot involved.
--
Strange openjdk hang in FUTEX_WAIT
https://bugs.launchpad.net/bugs/309407
You received this bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John J Barton wrote:
https://bugzilla.mozilla.org/show_bug.cgi?id=513556
I get You are not authorized to access bug #513556. Is it security-
related?
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
httpete wrote:
I need firefox 64 bit. Can you tell me the bug so I can track it or
give more information?
See also
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542768
https://bugs.launchpad.net/debian/+source/iceweasel/+bug/449744
Cheers,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John J Barton wrote:
That crash has been reported. It is in code without an owner and on a
platform not widely used.
Widely used is a relative term, but it appears to affect all 64-bit Linux
systems (confirmed for Fedora, Debian and Ubuntu). For
Package: bugzilla3
Version: 3.2.5.0-1
Severity: important
After the move of the CGI scripts, the rewrite rules in README.Debian
are not needed, and actually break the installation if followed.
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (990, 'stable'),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Jonathan Nieder wrote:
Marcus Better wrote:
The checkout-index command is frequently useful but is missing from
shell completion.
Hmm, checkout-index is intended more as a building block in scripts.
Yes, I had somehow missed the existence
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
retitle 542768 segfault with Firebug 1.5
found 542768 3.5.4-1
affects 542768 firebug xulrunner-1.9.1
thanks
Confirmed on Iceweasel 3.5.4-1 with xulrunner-1.9.1 1.9.1.4-1 and
Firebug 1.5b1.
It seems likely that this will give problems for Debian's
** Bug watch added: Debian Bug tracker #542768
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542768
** Also affects: iceweasel (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542768
Importance: Unknown
Status: Unknown
--
Firefox crashes when attempting to load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Murdoch wrote:
Could you add a JIRA issue for this problem?
Done, GRADLE-723.
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkrp8KwACgkQXjXn6TzcAQn93gCfcw1fXpjY7MXPAsGG6m4a4FcW
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesse Vincent wrote:
* Can rt-mailgate be configured not to drop the mail on the floor if the
reception fails? I would like the mail delivery to be retried by the mail
system.
..it should already be doing this. rt-mailgate only tells your MTA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't see a problem with this. Why should this be changed?
Consistency with many, or most, other commands? It's a widely used
convention, and diverging from it can break user expectation and make
the tool harder to use.
I know I have dropped the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
notfixed 536415 2:1.1.0~rc2-1
found 536415 2:1.1.0~rc2-1
thanks
Sorry, there is no difference whatsoever in this version.
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Meurer wrote:
On 23/10/2009 Marcus Better wrote:
Sorry, there is no difference whatsoever in this version.
yes, there is. there's a small speed increase in processing
key/passphrase, and a huge speed increase for higher keyslots.
Well
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
today we almost lost an incoming e-mail that was processed by rt-mailgate
but never appeared in RT as a ticket. The only thing I can see in the web
server logs around the time of the event is the following line:
[Fri Oct 23 08:41:31 2009]
of tinyca.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the tinyca package.
-# Daniel Nylander p...@danielnylander.se, 2006.
#
+# Daniel Nylander p...@danielnylander.se, 2006.
+# Marcus Better mar...@better.se, 2009.
msgid
msgstr
Project
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian's Tomcat is FHS-compliant, by necessity. That is the reason for
the differing directory structure.
Have you tried creating a Tomcat instance for Eclipse with tomcat6-user?
That gives you a separate Tomcat directory with its own conf directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Debian's Tomcat is FHS-compliant, by necessity. That is the reason for
the differing directory structure.
Have you tried creating a Tomcat instance for Eclipse with tomcat6-user?
That gives you a separate Tomcat directory with its own conf directory
Package: mediawiki
Version: 1:1.15.1-1
Severity: important
After running the web-based initial configuration of mediawiki
(/var/lib/mediawiki/config/index.php), it created a LocalSettings.php
and instructed me to place it in /etc/mediawiki:
~$ ls -l /etc/mediawiki/LocalSettings.php
-rw-rw-rw- 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reopen 366797
found 366797 0.46-9
thanks
I can reproduce this. When importing an EPS file, I get an error dialog
an no image:
Inkscape has received additional data from the script executed. The
script did not return an error, but this may
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerfried Fuchs wrote:
EDITOR=emacsclient --alternate-editor emacs
The question rather would be: How would you specify a pathname/filename
that has spaces in it?
By escaping like the shell perhaps?
following that approach might raise security
Package: nslcd
Version: 0.7.0
Severity: wishlist
The README mentions that password management is not supported by the
PAM module. This would obviously be very useful.
In the meantime I suppose passwords must be changed directly in LDAP?
-- System Information:
Debian Release: squeeze/sid
APT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually the simple symlink will not do it. Bugzilla's templates need to
be changed to reflect Debian's directory structure where the yui
directory has subdirectories for the different components.
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually the simple symlink will not do it. Bugzilla's templates need to
be changed to reflect Debian's directory structure where the yui
directory has subdirectories for the different components.
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Package: request-tracker3.8
Version: 3.8.5-1
Severity: wishlist
Instead of having a special command, update-rt-siteconfig, to
concatenate all the configuration files in
/etc/request-tracker3.8/RT_SiteConfig.d, it would be more
straightforward to have the RT_SiteConfig script source all the
Package: request-tracker3.8
Version: 3.8.5-1
Severity: normal
I ran
rt-setup-database-3.8 --dba rt --prompt-for-dba-password --action upgrade
without realising that I had accidentally forgotton to specify a
$DatabaseName in SiteConfig. This causes the script to go into an
endless loop,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is non-free. Please keep it out of Debian.
Surely you are aware of the huge controversy around Ext JS licensing.
There is no need to repeat that story here, let me just point to this page:
http://www.extjs.com/company/dual.php
Here they make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Goirand skrev:
Surely you are aware of the huge controversy around Ext JS licensing.
Hell, I missed it.
Oh well :-)
This doesn't appear at all on the license.txt. Do you
think I could still package it for the non-free archive?
I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Goirand skrev:
Please do not start a 100 post thread in this ITP if this has been
discussed in the past (let's not loose time twice on a bad license). I
just would like to have a link here to the archive of the old discussion
about if one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reopen 495107
found 495107 3.2.4.0-3
thanks
The proposed solution is not enough if you try to install Bugzilla in
another URL than /bugzilla3, which is probably very common. For example
I have created an alias for /bugzilla instead, but the links to
Package: bugzilla3
Version: 3.2.4.0-3
Severity: normal
The editparams.cgi page fails to save configuration changes. The
www-data user appears to lack write permission to
/etc/bugzilla3/params (I think, maybe I've changed this locally), but it also
tries to create a temporary file in
Package: bugzilla3
Version: 3.2.4.0-3
Severity: normal
I ran checksetup.pl and got the following suggestions for installing
additional Perl modules:
Chart: apt-get install libchart-perl
Template-GD: dh-make-perl --install --cpan Template::Plugin::GD::Image
PatchReader:
Package: bugzilla3
Version: 3.2.4.0-3
Severity: wishlist
Please include the sanitycheck.pl script that should be available in
the distribution, according to the Bugzilla Guide [1]. Maybe it should
be added to the cron job by default.
[1] http://www.bugzilla.org/docs/3.4/en/html/sanitycheck.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is non-free. Please keep it out of Debian.
Surely you are aware of the huge controversy around Ext JS licensing.
There is no need to repeat that story here, let me just point to this page:
http://www.extjs.com/company/dual.php
Here they make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The dependency should now be to libjs-yui, and the symlink
/usr/share/bugzilla3/web/js/yui
should now point to
../../../yui/html/yahoo-dom-event
Cheers,
Marcus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Goirand skrev:
Surely you are aware of the huge controversy around Ext JS licensing.
Hell, I missed it.
Oh well :-)
This doesn't appear at all on the license.txt. Do you
think I could still package it for the non-free archive?
I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Goirand skrev:
Please do not start a 100 post thread in this ITP if this has been
discussed in the past (let's not loose time twice on a bad license). I
just would like to have a link here to the archive of the old discussion
about if one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is non-free. Please keep it out of Debian.
Surely you are aware of the huge controversy around Ext JS licensing.
There is no need to repeat that story here, let me just point to this page:
http://www.extjs.com/company/dual.php
Here they make
201 - 300 of 2637 matches
Mail list logo
