Re: Bug#707851: Soften the the wording recommending menu files: let's do it in Jessie.

[Bill Allombert]

On Sun, Jan 05, 2014 at 02:33:20PM -0800, Steve Langasek wrote:
> Furthermore, I think the idea of an application "belonging" to one system or
> the other is misplaced.  The purpose of both the original menu system and
> the freedesktop standard is to give users consistent, menu-driven access to
> the software installed on the computer.  While a given desktop environment
> is going to give precedence to software that is integrated with that desktop
> environment, users should be able to expect that they can access all
> software installed on the system through the GUI, via the appropriate
> submenus.  Telling maintainers to integrate with one of two different menu
> systems does not achieve this.
> 
> So if the Debian menu system is insufficiently expressive to meet our needs,
> we should be giving clear advice for the use of the fdo menu system.

This is backward: the Debian menu system is more expressive than the fdo menu
system and easier to support by window manager by requiring much less software
support (in particular XDG menu requires XML processing).

Debian menu is supported by much more window managers than the XDG menu draft.

I do not believe Debian should favor desktop environment over lightweight 
window managers, especially since Debian users are more likely than other 
to favor use lightweight environments.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140225224014.GG20431@yellowpig

Bug#747855: libindi-data: circular dependency with libindidriver0c, libindi-plugins

[Bill Allombert]

Package: libindi-data
Version: 0.9.8.1-2
Severity: important

Hello Debian Krap Maintainers,

There is a circular dependency between libindi-data, libindi-plugins and
libindidriver0c:

libindi-data:Depends: libindi-plugins (>= 0.9.8.1-2)
libindi-plugins :Depends: libindidriver0c (>= 0.9.7)
libindidriver0c :Depends: libindi-data (>= 0.9.8.1-2)

Circular dependencies involving shared libraries are known to cause problems
during upgrade, so we should try to avoid them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140512095330.GA19767@yellowpig

Bug#729363: libkdepim4: circular dependency hell

[Bill Allombert]

On Sun, Jan 11, 2015 at 04:26:25PM +0100, Sandro Knauß wrote:
> Hey,
> 
> > In that case, why put them in separated binary packages where a single one
> > would do ?
> 
> Because you do not want to install to much stuff, if you only install one 
> application built from kdepim (kontact, kmail, akgregator, 
> akonadiconsole,...).

Precisely, the circular dependency prevent you from doing that, by forcing
the installation of the other.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2015054525.GC25129@yellowpig

Bug#888888: libkf5libkdepim-plugins has circular Depends on libkf5libkdepimakonadi5

[Bill Allombert]

Package: libkf5libkdepim-plugins
Version: 4:17.08.3-1
Severity: important

Hello Debian/Kubuntu KDE maintainers,

There is a circular dependency between libkf5libkdepim-plugins and 
libkf5libkdepimakonadi5:

libkf5libkdepim-plugins :Depends: libkf5libkdepimakonadi5
libkf5libkdepimakonadi5 :Depends: libkf5libkdepim-plugins

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to avoid them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#808607: libqt5gui5 has circular Depends on libqt5xcbqpa5

[Bill Allombert]

Package: libqt5gui5
Version: 5.5.1+dfsg-8
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between libqt5gui5 and libqt5xcbqpa5:

libqt5gui5  :Depends: libqt5xcbqpa5
libqt5xcbqpa5   :Depends: libqt5gui5 (>= 5.5.0)

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to avoid them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#292401: kdm_config override /etc/kde3/kdm/kdmrc which is a conffile

[Bill Allombert]

Package: kdm
Version: 4:3.3.1-4
Severity: serious
Justification: Policy 10.7.3


Hello KDE maintainers,

kcontrol overwrite the conffile /etc/kde3/kdm/kdmrc without
respecting comment and formating. For example if you start with the
file provided in the current kdm package, launch kcontrol,
choose Login manager->Administrator Mode,make a change, cancel it
and it apply, you get a complelty different file /etc/kde3/kdm/kdmrc,
see patch below.

This means dpkg conffiles handling is useless here since you cannot
merge the changes.

Cheers,
Bill


-- debconf information:
  kdm/stop_running_server_with_children: false
* kdm/default_servers_nolisten_tcp:
* kdm/default_servers_100dpi:
* kdm/default_nolisten_udp:
* shared/default-x-display-manager: kdm
  kdm/daemon_name: /usr/bin/kdm
  kdm/oldconfig:


--- kdmrc   2005-01-26 21:54:01.0 +0100
+++ /etc/kde3/kdm/kdmrc 2005-01-26 23:47:40.0 +0100
@@ -1,512 +1,70 @@
-# KDM master configuration file
-#
-# Definition: the greeter is the login dialog, i.e., the part of KDM
-# which the user sees.
-#
-# You can configure every X-display individually.
-# Every display has a display name, which consists of a host name
-# (which is empty for local displays specified in the Xservers file),
-# a colon and a display number. Additionally, a display belongs to a
-# display class (which can be ignored in most cases; the control center
-# does not support this feature at all).
-# Sections with display-specific settings have the formal syntax
-# "[X-" host [":" number [ "_" class ]] "-" sub-section "]"
-# You can use the "*" wildcard for host, number and class. You may omit
-# trailing components; they are assumed to be "*" then.
-# The host part may be a domain specification like ".inf.tu-dresden.de".
-# From which section a setting is actually taken is determined by these
-# rules:
-# - an exact match takes precedence over a partial match (for the host part),
-#   which in turn takes precedence over a wildcard
-# - precedence decreases from left to right for equally exact matches
-# Example: display name "myhost:0", class "dpy".
-# [X-myhost:0_dpy] precedes
-# [X-myhost:0_*] (same as [X-myhost:0]) precedes
-# [X-myhost:*_dpy] precedes
-# [X-myhost:*_*] (same as [X-myhost]) precedes
-# [X-*:0_dpy] precedes
-# [X-*:0_*] (same as [X-*:0]) precedes
-# [X-*:*_*] (same as [X-*])
-# These sections do NOT match this display:
-# [X-hishost], [X-myhost:0_dec], [X-*:1], [X-:*]
-# If a setting is not found in any matching section, the default is used.
-#
-# Every comment applies to the following section or key. Note that all
-# comments will be lost if you change this file with the kcontrol frontend.
-# The defaults refer to KDM's built-in values, not anything set in this file.
-
 [General]
-# This option exists solely for the purpose of a clean automatic upgrade.
-# Don't even think about changing it!
 ConfigVersion=2.2
-# If the value starts with a slash (/), it specifies the file, where X-servers
-# to be used by KDM are listed; the file is in the usual XDM-Xservers format.
-# Otherwise it's interpreted like one line of the Xservers file, i.e., it
-# specifies exactly one X-server.
-# Default is ":0 [EMAIL PROTECTED] /usr/X11R6/bin/X -nolisten tcp"
-Xservers=/etc/kde3/kdm/Xservers
-# VTs to allocate to X-servers. A negative number means that the VT will be
-# used only if it is free. If all VTs in this list are used up, the next free
-# one greater than the last one in this list will be allocated.
-# Default is ""
-ServerVTs=-7
-# Where KDM should store its PID (don't store if empty).
-# Default is ""
 PidFile=/var/run/kdm.pid
-# Whether KDM should lock the PID file to prevent having multiple KDM
-# instances running at once. Don't change unless you're brave.
-# Default is true
-#LockPidFile=false
-# Where to store authorization files.
-# Default is "/var/run/xauth"
-#AuthDir=/tmp
-# Whether KDM should automatically re-read configuration files, if it
-# finds them having changed.
-# Default is true
-#AutoRescan=false
-# Additional environment variables KDM should pass on to all programs it runs.
-# LD_LIBRARY_PATH and XCURSOR_THEME are good candidates;
-# otherwise it shouldn't be necessary very often.
-# Default is ""
-#ExportList=LD_LIBRARY_PATH,ANOTHER_IMPORTANT_VAR
-# A character device KDM should read entropy from.
-# Empty means use the system's preferred entropy device.
-# Default is ""
-#RandomDevice=/dev/altrandom
-# Where the command FiFos should be created. Make it empty to disable
-# the FiFos.
-# Default is "/var/run/xdmctl"
-#FifoDir=/tmp
-# To which group the global command FiFo should belong.
-# Can be either a name or a numerical ID.
-# Default is 0
-#FifoGroup=xdmctl
-# The directory kdm should store persistent working data in.
-# Default is "/var/lib/kdm"
-#DataDir=
-# The directory KDM should store users' .dmrc files in. This is only needed
-# if the home directories are not readable before actually logging in (like
-# with AFS).
-# Default is ""
-#Dmr

Bug#292401: kdm_config override /etc/kde3/kdm/kdmrc which is a conffile

[Bill Allombert]

severity 292401 serious
quit
Justification: Break sarge_rc_policy.txt/3. Configuration files

> On January 26, 2005 17:56, Bill Allombert wrote:
> > Package: kdm
> > Version: 4:3.3.1-4
> > Severity: serious
> > Justification: Policy 10.7.3
> 
> ...which states:
> 
> Configuration file handling must conform to the following behavior:
> 
> * local changes must be preserved during a package upgrade, and
> * configuration files must be preserved when the package is removed,
>and only deleted when the package is purged.
> 
> Nothing kcontrol does violates policy 10.7.3, which describes package 
> upgrades and removals. It does not forbid some GUI tool from completely 
> re-writing the file, since running that tool is up to the user and has 
> nothing to do with packaging policy.

If you prefer, read <http://release.debian.org/sarge_rc_policy.txt>:
(which is the official definition of RC)

3. Configuration files

Packages must not modify their own or other packages conffiles
programmatically. (The only correct way to modify a conffile is
the user running an editor specifically; if anything more automated
is required or useful, configuration files must _NOT_ be handled as
conffiles)

> That kcontrol does what it does is very annoying and a very nasty 
> shortcoming, but not a policy violation.

You miss the point, it is not only a config file, but a *conffile*:
 
 The easy way to achieve this behavior is to make the configuration
 file a `conffile'.  This is appropriate only if it is possible to
 distribute a default version that will work for most installations,
 although some system administrators may choose to modify it.  This
 implies that the default version will be part of the package
 distribution, and must not be modified by the maintainer scripts
 during installation (or at any other time).

> To fix this, we'd need either to ship a kdmrc that conforms to the 
> kcontrol configurator's basic pattern, and so wouldn't be modified by 
> kcontrol more than is really necessary (could we make it keep the 
> comments, at least?), or else re-write the kdm module of kcontrol to 
> behave less stupidly, which would be quite an undertaking.
> 
> Comments?

Alternatively, you could stop shipping /etc/kde3/kde/kdmrc at all,
provide a non-config file /usr/share/kde/kdmrc, change kdm to read
/usr/share/kde/kdmrc if /etc/kde3/kde/kdmrc does not exist.
That mean people having a /etc/kde3/kde/kdmrc won't get the change 
from /usr/share/kde/kdmrc, but currently they won't either if they
use kcontrol. I don't know if it is better.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310873: kdelibs4 <--> kdelibs-bin circular dependency

[Bill Allombert]

Package: kdelibs4
Version: 4:3.3.2-6.1
Severity: important

Hello Debian KDE team,

There is a circular dependency between kdelibs4 and kdelibs-bin which
cause aptitude dist-upgrade to try to remove the whole KDE set of
packages during some woody to sarge upgrade. See Bug #310490.

Cheers
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310873: kdelibs4 <--> kdelibs-bin circular dependency

[Bill Allombert]

On Fri, May 27, 2005 at 07:48:20PM -0400, Christopher Martin wrote:
> On May 26, 2005 12:57, Bill Allombert wrote:
> > There is a circular dependency between kdelibs4 and kdelibs-bin which
> > cause aptitude dist-upgrade to try to remove the whole KDE set of
  ^
> > packages during some woody to sarge upgrade. See Bug #310490.
^^^  ^^^
> Was the aptitude being used to perform the upgrade itself updated to the 
> Sarge level beforehand? This problem has cropped up before, and better 
> results were obtained if this was done. See #183702 and #183985.

Why not reading the bug you are replying to ?
BTW, #310490 is 100% reproducible.

Cheers,
Bill.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A Prisonner of the dependency hell

[Bill Allombert]

On Fri, May 27, 2005 at 04:49:14PM -0700, Steve Langasek wrote:
> On Sat, May 28, 2005 at 01:03:13AM +0200, Bill Allombert wrote:
> > I need to attract your attention on bug #310490.
> 
> > This show a pure woody system that cannot be upgraded to sarge
> > using the recommended way witout basically removing KDE.
> > This bug is 100% reproducible, but I have not yet completly
> > tracked the problem, though I have seen pretty awkward behaviour from
> > apt. In particular 'apt-get install fontconfig' fails with a message
> > claiming that defoma cannot installed while defoma is up-to-date.
> 
> > Upgrading with dselect work much better.
> 
> > I did not try yet to upgrade using aptitude in interactive mode.
> 
> I don't suppose there's a smaller test case involving fewer packages?

I have not yet found one, I will retry tomorrow (its 2AM here, and my
setup is quite slow).

> I know KDE upgrade tests had been done at one point.  Maybe someone on the
> KDE team can shed light on this problem?

Well, I have done the following experiment:
1) debootstrap woody
2) install desktop task + X task (so I got X+KDE+GNOME).
3) upgrade to sarge.

Everything worked smoothly, so that not too bad.

Cheers,
Bill.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#310873: kdelibs4 <--> kdelibs-bin circular dependency

[Bill Allombert]

On Fri, May 27, 2005 at 08:06:02PM -0400, Christopher Martin wrote:
> Yes, I had noticed that the report seems to indicate that the packaging 
> tools were not upgraded beforehand, but people often leave out certain 
> strange things, so I thought it best to ask, and it led to my other point 
> anyway. Your response only begs the question of whether or not upgrading 
> the packaging tools before attempting the full woody to sarge update 
> improves the situation. I'm not in a position to test matters myself at 
> this exact moment in time.

It does not.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A Prisonner of the dependency hell

[Bill Allombert]

On Fri, May 27, 2005 at 04:49:14PM -0700, Steve Langasek wrote:
> On Sat, May 28, 2005 at 01:03:13AM +0200, Bill Allombert wrote:
> > I need to attract your attention on bug #310490.
> 
> > This show a pure woody system that cannot be upgraded to sarge
> > using the recommended way witout basically removing KDE.
> > This bug is 100% reproducible, but I have not yet completly
> > tracked the problem, though I have seen pretty awkward behaviour from
> > apt. In particular 'apt-get install fontconfig' fails with a message
> > claiming that defoma cannot installed while defoma is up-to-date.
> 
> > Upgrading with dselect work much better.
> 
> > I did not try yet to upgrade using aptitude in interactive mode.
> 
> I don't suppose there's a smaller test case involving fewer packages?

OK, I have done that:
1) debootstrap woody
2) install konqueror,libqt3 and aptitude
3) move to sarge
aptitude -f dist-upgrade want to remove konqueror

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A Prisonner of the dependency hell

[Bill Allombert]

On Fri, May 27, 2005 at 04:49:14PM -0700, Steve Langasek wrote:
> Hi Bill,
> 
> I don't suppose there's a smaller test case involving fewer packages?

After spending a dozen of hour tracking it, I have the obvious headache,
but also the following:

1) debootstrap woody

2) Install the following packages:
konqueror aptitude libqt3 libhtml-tree-perl libapt-pkg-perl libft-perl

3) point apt at sarge.

At this point you are between a rock and a hard place:
You can do
2) aptitude install aptitude, but that remove konqueror and perl
3) aptitude dist-upgrade, but that remove konqueror

As for the culprit, my headache does not allow me to investigate more,
but here some clues: In _woody_,

1) libqt3 has a circular dependency with libqt3-mt.
2) libhtml-tree-perl has a circular dependency with libwww-perl.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#215946: /etc/kde3/magic/*.magic

[Bill Allombert]

On Tue, Dec 02, 2003 at 11:29:20AM +0100, Dominique Devriese wrote:
> If I understand the KMimeMagic code properly, then what you are trying
> to accomplish is possible by putting an extra *.magic file in the
> /etc/kde3/magic directory.  It should be used automagically by the KDE
> MIME system.  If you need an example, install the kolf package, it
> contains such a file iirc.

Thanks for your study.

> Please let us know if this fixes your problem, and if this bug can be
> closed. 

Until this is properly documented, the bug should not be closed.

Also that does not address why KDE need its own mime-magic system.
Why not using the /etc/mime-magic file ?

Does the kolf magic file required to be a config files ? If not, why
not drop it under a directory that is not in /etc ?

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Re: Bug#770430: openbox: Fails to launch qtconfig

[Bill Allombert]

reassign 770430
retitle 770430 qt4-qtconfig: menu entry use wildcard
quit
On Fri, Nov 21, 2014 at 12:17:25AM -0800, Dan DeVoto wrote:
> Package: menu
> Version: 2.1.47
> Severity: normal
> 
> Dear Maintainer,
> 
> Using Openbox 3.5.2-8, when I attempt to launch qt4-qtconfig from the
> Openbox menu (under Debian --> Applications --> System --> Administration-->
> QtConfig) I get the following popup error:
> 
> Failed to execute child process "/usr/lib/*/qt4/bin/qtconfig" (No such file
> or directory).
> 
> Launching qtconfig from the command line or from launchers like Kupfer works
> fine.

Hello Dan and Debian Qt/KDE Maintainers, the menu file for qt4-qtconfig reads:

?package(qt4-qtconfig):\
needs="x11"\
section="Applications/System/Administration"\
title="QtConfig"\
longtitle="Qt Configuration Utility"\
hints="Qt4 config tool"\
command="/usr/lib/*/qt4/bin/qtconfig"

However the use of a wildcard in the command field is problematic:
If both /usr/lib/x86_64-linux-gnu/qt4/bin/qtconfig and
/usr/lib/i386-linux-gnu/qt4/bin/qtconfig are installed, then
this will expand to something nonsensical.

Also use of wildcards in command is not well supported by all the window 
manager.

Why not simply call /usr/bin/qtconfig-qt4 (which is a symlink to
../lib/x86_64-linux-gnu/qt4/bin/qtconfig ?

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141121170837.GA22693@yellowpig

Bug#899111: libkf5globalaccel-bin has circular Depends on libkf5globalaccelprivate5

[Bill Allombert]

Package: libkf5globalaccel-bin
Version: 5.46.0-1
Severity: important

Hello Debian/Kubuntu maintainers,

There is a circular dependency between libkf5globalaccel-bin and
libkf5globalaccelprivate5:

libkf5globalaccel-bin :Depends: libkf5globalaccelprivate5 (>= 5.11.0+git)
libkf5globalaccelprivate5 :Depends: libkf5globalaccel-bin

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should strive to avoid them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#729363: libkdepim4: circular dependency hell

[Bill Allombert]

Package: libkdepim4
Version: 4:4.11.3-1
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency hell between libincidenceeditorsng4, libkdepim4,
libmailcommon4, libmailimporter4, libmessagecomposer4, libmessageviewer4,
libpimcommon4 and libtemplateparser4:

libincidenceeditorsng4  :Depends: libkdepim4 (= 4:4.11.3-1)
libkdepim4  :Depends: libmailcommon4 (= 4:4.11.3-1), libpimcommon4 (= 
4:4.11.3-1)
libmailcommon4  :Depends: libincidenceeditorsng4 (= 4:4.11.3-1), libkdepim4 (= 
4:4.11.3-1), libmailimporter4 (= 4:4.11.3-1), libmessagecomposer4 (= 
4:4.11.3-1), libmessageviewer4 (= 4:4.11.3-1), libpimcommon4 (= 4:4.11.3-1), 
libtemplateparser4 (= 4:4.11.3-1)
libmailimporter4:Depends: libkdepim4 (= 4:4.11.3-1)
libmessagecomposer4 :Depends: libkdepim4 (= 4:4.11.3-1), libmessageviewer4 
(= 4:4.11.3-1), libtemplateparser4 (= 4:4.11.3-1)
libmessageviewer4   :Depends: libkdepim4 (= 4:4.11.3-1), libpimcommon4 (= 
4:4.11.3-1)
libpimcommon4   :Depends: libkdepim4 (= 4:4.11.3-1)
libtemplateparser4  :Depends: libmessageviewer4 (= 4:4.11.3-1)

The full dependency graph is available at


Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131112105015.GA14364@yellowpig

Bug#729363: libkdepim4: circular dependency hell

[Bill Allombert]

On Tue, Nov 12, 2013 at 09:42:36AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> On Tuesday 12 November 2013 11:50:15 Bill Allombert wrote:
> > Package: libkdepim4
> > Version: 4:4.11.3-1
> > Severity: important
> > 
> > Hello Debian Qt/KDE Maintainers,
> > 
> > There is a circular dependency hell between libincidenceeditorsng4,
> > libkdepim4, libmailcommon4, libmailimporter4, libmessagecomposer4,
> > libmessageviewer4, libpimcommon4 and libtemplateparser4:
> 
> [snip]
> 
> > The full dependency graph is available at
> > <http://debian.semistable.com/dot/libtemplateparser4_unstable.png>
> 
> Just for the record, all of them come from the same source and we are not 
> shipping headers for them (so no external packages con build depend on them).

In that case, why put them in separated binary packages where a single one
would do ?

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131118104939.GD10513@yellowpig

Bug#834099: libkf5akonadicore-bin: circular dependency with libkf5akonadiwidgets5

[Bill Allombert]

Package: libkf5akonadicore-bin
Version: 4:16.04.3-1
Severity: important

Hello Debian/Kubuntu Qt/KDE Maintainers,

There is a circular dependency between libkf5akonadicore-bin and
libkf5akonadiwidgets5:

libkf5akonadicore-bin   :Depends: libkf5akonadiwidgets5 (= 4:16.04.3-1)
libkf5akonadiwidgets5   :Depends: libkf5akonadicore-bin (= 4:16.04.3-1)

Circular dependencies are known to cause problems during upgrade, so we
should try to avoid them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#963848: libqt5texttospeech5: circular dependency hell

[Bill Allombert]

Package: libqt5texttospeech5
Version: 5.14.2-2
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between libqt5texttospeech5,
qtspeech5-flite-plugin and qtspeech5-speechd-plugin:

libqt5texttospeech5 :Depends: qtspeech5-speechd-plugin, 
qtspeech5-flite-plugin
qtspeech5-flite-plugin  :Depends: libqt5texttospeech5 (>= 5.8.0~alpha)
qtspeech5-speechd-plugin:Depends: libqt5texttospeech5 (>= 5.8.0~alpha)

Complex circular dependencies are known to cause problems during upgrade, so we
should try to avoid them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#853899: [kde-cli-tools] kdesu binary is not linked in any PATH directory

[Bill Allombert]

On Tue, Mar 14, 2017 at 02:52:26PM +0100, Maximiliano Curia wrote:
> Control: tag -1 + wontfix
> 
> ¡Hola Éter!
> 
> El 2017-02-01 a las 21:41 +0100, Éter escribió:
> > Package: kde-cli-tools Version: 4:5.8.4-1 Severity: normal
> 
> > The binary "/usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu" included in
> > package kde-cli-tools is not linked to any of the PATH directories. This
> > way we can't execute the program directly from the terminal.
> 
> > It would be good to have the binary symlinked to /usr/bin
> 
> kdesu is not as secure as we would like it to be, mostly due to X (see
> https://blog.martin-graesslin.com/blog/2017/02/editing-files-as-root/ for
> example). It's currently sort of deprecated upstream and a replacement is in
> the works (probably based on policykit). As such I really don't want to
> attract more users to kdesu.

Hello Maximiliano,
kdesu was in /usr/bin for a long time, so it is not like people do not
know about it. Further being in /usr/lib/* does not prevent bad actors
to use it or to trick users to use it, so it is not a security improvement.

It is more than ten years since a policykit was proposed as a solution
but it has never materialised and is unlikely to provide a kdesu
alternative that does not have the same issues.

The only result is that su-to-root cannot use kdesu anymore and so
it defaults to something even less secure.

Cheers,
-- 
Bill.  (su-to-root maintainer)

Imagine a large red swirl here. 

Re: Bug#602118: menu: su-to-root script should include kdesudo method to gain root privileges

[Bill Allombert]

On Mon, Nov 01, 2010 at 06:52:16PM +0100, Niccolo Rigacci wrote:
> Package: menu
> Version: 2.1.44
> Severity: wishlist
> 
> For KDE users, if kdesudo package is installed, the best way to gain
> superuser privileges is through the kdesudo command.

Hello Niccolo,

This is assuming that sudo is configured that way, no ? Debian systems do not 
have to
use sudo for superuser privileges.

> The /usr/sbin/su-to-root script should test for the presence of kdesudo
> program and eventually use it.

The issue is that su-to-root need to know whether it must use kdesudo or kdesu,
and neither PAM nor sudo will tell that.

In GNOME, gksu handles both root-passwordful and root-passwordless systems 
through a
gconf setting, so this is less of an issue.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101103085214.gc21...@yellowpig

Bug#609807: konsole: missing Debian menu entry.

[Bill Allombert]

Package: konsole
Version: 4:4.4.5-1
Severity: normal

Hello Debian Qt/KDE Maintainers,

konsole is missing a Debian menu entry since Sat, 09 Jan 2010.
The file below (/usr/share/menu/konsole) should work:

?package(konsole):\
needs="X11"\
section="Applications/Terminal Emulators"\
title="Konsole"\
command="/usr/bin/konsole"

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110112161520.ga19...@yellowpig

Bug#633437: kdenetwork: Please Build-Depends on libjpeg-dev, not libjpeg62-dev

[Bill Allombert]

Package: kdenetwork
Version: 4:4.6.3-1
Severity: important

Hello Debian Qt/KDE Maintainers,

There is an upcoming libjpeg transition from libjpeg62 to libjpeg8.
As mentionned on debian-devel-announce[1], please update kdenetwork to
Build-Depends on libjpeg-dev instead of libjpeg62-dev.

The following Build-Depends was found:

kdenetwork  :Build-Depends: libjpeg62-dev 

[1] http://lists.debian.org/debian-devel-announce/2010/02/msg6.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110710095852.GA27983@yellowpig

Bug#634134: kdenetwork: Please Build-Depends on libjpeg-dev, not libjpeg62-dev

[Bill Allombert]

Source: kdenetwork
Version: 4:4.6.3-1
Severity: important

Hello Debian Qt/KDE Maintainers,

We are transitionning from libjpeg62 to libjpeg8.
As mentionned on debian-devel-announce[1], please update kdenetwork to
Build-Depends on libjpeg-dev instead of libjpeg62-dev.

The following Build-Depends was found:

kdenetwork  :Build-Depends: libjpeg62-dev 

[1] http://lists.debian.org/debian-devel-announce/2010/02/msg6.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110717082310.GA11874@yellowpig

Bug#634135: koffice: Please Build-Depends on libjpeg-dev, not libjpeg62-dev

[Bill Allombert]

Source: koffice
Version: 1:2.3.3-1
Severity: important

Hello Debian Qt/KDE Maintainers,

We are transitionning from libjpeg62 to libjpeg8.
As mentionned on debian-devel-announce[1], please update koffice to
Build-Depends on libjpeg-dev instead of libjpeg62-dev.

The following Build-Depends was found:

koffice :Build-Depends: libjpeg62-dev 

[1] http://lists.debian.org/debian-devel-announce/2010/02/msg6.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110717082329.GA11889@yellowpig

Bug#478694: libqt4-gui has circular Depends on libqt4-svg

[Bill Allombert]

Package: libqt4-gui
Version: 4.4.0~rc1-5
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between libqt4-gui and libqt4-svg:

libqt4-gui  :Depends: libqt4-svg (>= 4.4.0~rc1-5)
libqt4-svg  :Depends: libqt4-gui (= 4.4.0~rc1-5)

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Bug#273732 closed by Ana Guerrero (reply to 273...@bugs.debian.org) (Package kdebase removed from Debian)

[Bill Allombert]

reopen 273732
reassign 273732 kdebase-runtime
found 273732 4:4.2.2-1
quit

On Wed, Apr 22, 2009 at 04:18:42PM +, Debian Bug Tracking System wrote:
> Version: 4:3.5.10.dfsg.1-2+rm
> 
> Hi,
> 
> You filed the bug http://bugs.debian.org/273732 
> in the Debian BTS against the package kdebase.
> 
> Debian has switched to KDE 4 in unstable and kdebase 
> does not exist in KDE 4. Therefore, I am closing this bug as fixed 
> in *unstable*. The bug will remain open for stable since it is
> shipping KDE 3.5.

It is not fixed: kdebase-runtime still exist and include a lot of binaries
without manpages:

/usr/bin/kcmshell4
/usr/bin/kde-cp
/usr/bin/kde-mv
/usr/bin/kde-open
/usr/bin/kde4
/usr/bin/kde4-menu
/usr/bin/kfile4
/usr/bin/khotnewstuff4
/usr/bin/kiconfinder
/usr/bin/kioclient
/usr/bin/kmimetypefinder
/usr/bin/knotify4
/usr/bin/kquitapp
/usr/bin/ksvgtopng4
/usr/bin/ktraderclient
/usr/bin/ktrash4
/usr/bin/kuiserver
/usr/bin/kwalletd
/usr/bin/nepomukserver
/usr/bin/nepomukservicestub
/usr/bin/solid-hardware

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#273732: closed by Ana Guerrero (reply to 273...@bugs.debian.org) (Package kdebase removed from Debian)

[Bill Allombert]

On Sun, Apr 26, 2009 at 10:32:07PM +0200, Cyril Brulebois wrote:
> Bill,
> 
> you know, that's kinda useless unless you actually provide manpages. We
> already have such lists through lintian reports on lintian.debian.org.

Well I reported this bug nearly five years ago and nothing has been
done, and kde4 is used as a pretext to close it. The motivation for
the bug is still there.

Anyway, since the binary are probably documented somewhere, it should
be possible to generate manpages automatically that point to the 
documentation. At least that would be a start.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#530522: kdelibs-bin has circular Depends on kdelibs5

[Bill Allombert]

Package: kdelibs-bin
Version: 4:4.2.2-2
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between kdelibs-bin and kdelibs5:

kdelibs-bin :Depends: kdelibs5 (= 4:4.2.2-2)
kdelibs5:Depends: kdelibs-bin (>= 4:4.2.2-2)

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

This bug look like the KDE4 version of #310873 which was solved a long time
ago.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#655382: libqt4-dbus has circular Depends on qdbus

[Bill Allombert]

Package: libqt4-dbus
Version: 4:4.7.4-2
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between libqt4-dbus and qdbus:

libqt4-dbus :Depends: qdbus (= 4:4.7.4-2)
qdbus   :Depends: libqt4-dbus (= 4:4.7.4-2)

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120110195643.GA24326@yellowpig

Re: Bug#666545: menu: please migrate to kde-runtime

[Bill Allombert]

On Sat, Mar 31, 2012 at 06:44:47PM +0200, Pino Toscano wrote:
> Source: menu
> Version: 2.1.46
> Severity: wishlist
> Tags: patch
> 
> Hi,
> 
> since KDE SC 4.7, the kdebase-runtime source and binary have been
> renamed to kde-runtime, and kdebase-runtime is now a transitional
> metapackage.
> Could you please add kde-runtime as alternative in the suggestions
> of menu? Attached there is a patch for it.

Hello Pino,

Could not kde-runtime provides a virtual package kdesu so I could just
Suggests: kdesu ? 
It utsed to be kdebase-bin, kdebase-runtime and now kde-runtime.
This is moving to fast.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120402083522.GB2453@yellowpig

Bug#546199: libsoprano4: circular dependency with soprano-daemon

[Bill Allombert]

Package: libsoprano4
Version: 2.3.0+dfsg.1-2+b3
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between libsoprano4 and soprano-daemon:

libsoprano4 :Depends: soprano-daemon (= 2.3.0+dfsg.1-2+b3)
soprano-daemon  :Depends: libsoprano4 (>= 2.3.0)

Circular dependencies involving shared libraries are known to cause problems
during upgrade, so we should try to get rid of them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#569239: libqt3-mt-dev: please depend on libjpeg-dev, not libjpeg62-dev

[Bill Allombert]

Package: libqt3-mt-dev
Version: 3:3.3.8b-6
Severity: serious

Hello Debian Qt/KDE Maintainers,

There is a new version of libjpeg (libjpeg8) that replace libjpeg62.
libjpeg62-dev is only kept for LSB compatibility and should not be
used for building packages.

libqt3-mt-dev depends on libjpeg62-dev. Please change it to depends on
libjpeg-dev instead. Please also change the Build-Dependency to be on
libjpeg-dev and not libjpeg62-dev.

This dependency on libjpeg62-dev prevent packages Build-Depending on both 
libqt3-mt-dev and libjpeg-dev to install their dependencies, due to the conflict
between libjpeg62-dev and libjpeg-dev.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#342898: libkdepim1a has circular Depends on libkcal2b

[Bill Allombert]

Package: libkdepim1a
Version: 4:3.4.3-1
Severity: important

Hello Debian KDE team,

There is a circular dependency between libkdepim1a and libkcal2b:

libkdepim1a :Depends: libkcal2b (>= 4:3.4.3)
libkcal2b   :Depends: libkdepim1a (>= 4:3.4.3)

Circular dependencies between shared libaries are known to cause
problems during upgrade, so we should try to get rid of them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#342900: koffice-data has circular Depends on koffice-libs

[Bill Allombert]

Package: koffice-data
Version: 1:1.4.2-3
Severity: important

Hello Debian KDE maintainers,

There is a circular dependency between koffice-data and koffice-libs:

koffice-data:Depends: koffice-libs (= 1:1.4.2-3)
koffice-libs:Depends: koffice-data (= 1:1.4.2-3)


Circular dependencies are known to cause problems during upgrade,
so we should try to get rid of them.

Since koffice-data is a data package, it is quite likely it does not need
actually to depend on koffice-libs and removing this dependency would
remove the circular dependency, so I would suggest you do so.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#360919: kdm: please use xsessions .desktop files generated by menu-xdg

[Bill Allombert]

Package: kdm
Version: 4:3.5.2-1
Severity: wishlist

Hello Debian KDE maintainers,

menu-xdg package version 0.2.3 include a menu-method that generate
xsessions .desktop files in /var/lib/menu-xdg/xsessions/  from the list
of window-managers using the Debian menu system.

This wishlist is to use theses files to supplement the list of available
sessions in the kdm menu. This way, if menu and menu-xdg are installed,
kdm will always display the full list of available window-managers.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#372791: libarts1-akode: overwrite `/usr/lib/libarts_akode.la', which is also in akode

[Bill Allombert]

Package: libarts1-akode
Version: 4:3.5.3-1
Severity: serious

Hello Debian Qt/KDE Maintainers,

When doing a sarge to sid upgrade with piuparts

/usr/sbin/piuparts -a -d sarge -d sid gnupg gnome kde

the upgrade fails with

  Selecting previously deselected package libarts1-akode.
  Unpacking libarts1-akode (from .../libarts1-akode_4%3a3.5.3-1_i386.deb) ...
  dpkg: error processing 
/var/cache/apt/archives/libarts1-akode_4%3a3.5.3-1_i386.deb (--unpack):
  trying to overwrite `/usr/lib/libarts_akode.la', which is also in package 
akode
  dpkg-deb: subprocess paste killed by signal (Broken pipe)

So libarts1-akode should Replaces: akode

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#394629: libqt4-gui has circular Depends on libqt4-qt3support

[Bill Allombert]

Package: libqt4-gui
Version: 4.2.0-2
Severity: important

Hello Debian Qt/KDE Maintainers,

There is newly introduced circular dependency between libqt4-gui and
libqt4-qt3support:

libqt4-gui  :Depends: libqt4-qt3support (>= 4.2.0)
libqt4-qt3support   :Depends: libqt4-gui (>= 4.2.0)


Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

A similar circular dependencies between QT libraries caused a lot of
problem during wody to sarge upgrades.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large blue swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#444896: qt4-qtconfig: wrong menu section

[Bill Allombert]

Package: qt4-qtconfig
Version: 4.3.1-2
Severity: normal

Hello Debian Qt/KDE Maintainers,

The file /usr/share/menu/qt4-qtconfig reads
?package(qt4-qtconfig):\
needs="x11"\
section="Applications/System"\
title="QtConfig"\
longtitle="Qt Configuration Utility"\
hints="Qt4 config tool"\
command="/usr/bin/qtconfig-qt4"

Thanks for migrating to the new menu structure. However, menu entries
must be not be placed in Applications/System but in one of its
subsection, probably Applications/System/Administration.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#444899: kbugbuster: wrong menu section

[Bill Allombert]

Package: kbugbuster
Version: 4:3.5.7-3
Severity: normal

Hello Debian Qt/KDE Maintainers,

The file /usr/share/menu/kbugbuster reads
?package(kbugbuster):\
needs="x11"\
section="Applications/System/Security"\
hints="KDE"\
title="KBugBuster"\
longtitle="KBugBuster (KDE Bug Management)"\
icon="/usr/share/pixmaps/kbugbuster.xpm"\
command="/usr/bin/kbugbuster"

Thanks for migrating to the new menu structure. Hwoever I do not
think Applications/System/Security is appropriate for KBugBuster.
Applications/Project Management seems more appropriate.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#445038: kword: please update menu section

[Bill Allombert]

Package: kword
Version: 1:1.6.3-3
Severity: normal

Hello Debian Qt/KDE Maintainers,

The file /usr/share/menu/kword reads
?package(kword):\
needs="x11"\
section="Apps/Editors"\
hints="KDE,Word processors"\
title="KWord"\
longtitle="KWord (Word Processing)"\
icon="/usr/share/pixmaps/kword.xpm"\
command="/usr/bin/kword"

Please migrate to the new menu structure. section="Apps/Editors" should
be changed to section="Applications/Office".

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#445122: kompare: typo in menu entry

[Bill Allombert]

Package: kompare
Version: 4:3.5.7-3
Severity: normal

Hello Debian Qt/KDE Maintainers,

The file /usr/share/menu/kompare reads
?package(kompare):\
needs="x11"\T
section="Applications/Text"\
hints="KDE"\
title="Kompare"\
longtitle="Kompare (Diff/Patch Frontend)"\
icon="/usr/share/pixmaps/kompare.xpm"\
command="/usr/bin/kompare"

There is a spurious T after needs="x11"\

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#215946: /etc/kde3/magic/*.magic

[Bill Allombert]

On Sat, Dec 06, 2003 at 03:18:16PM -0600, Chris Cheney wrote:
> On Wed, Dec 03, 2003 at 05:59:01PM +0100, Bill Allombert wrote:
> > Until this is properly documented, the bug should not be closed.
> > 
> > Also that does not address why KDE need its own mime-magic system.
> > Why not using the /etc/mime-magic file ?
> 
> What /etc/mime-magic file, you mean the one that gnome provides?[1] Why
> doesn't gnome use the KDE one? :P All I see that is standard is a
> /etc/magic file which does not include anything that was directly built
> into the file(1) utility, which happens to mean /etc/magic is empty.

Then why not add mime-magic support to mime-types and share that between
all the program that need it instead of replicating the feature all
along ?

> The way KDE is designed all its upstream config related files go into
> $prefix/share/config, this had to be worked around by Debian to put it
> into /etc/kde3. As I understand it none of the files in
> $prefix/share/config were not meant to be directly edited by the admin

> but Debian requires any config related file be editable. However, KDE
> upstream does many very stupid things so I wouldn't be surprised if they
> intended $prefix/share/config to be editable as well, even though they

KDE 1.1 provided a way to modify the files in /usr/share/kde... by
asking first for the root password. So yes they were editable...

> put it in an obviously wrong location.

What you need is a 3-way overriding process like Debian menu does:

1: ~/.kde3/share/config   for user config.
2: /etc/kde3  for sysadmin config.
3: /use/share/kde3/config for package config.

Files in 1) override files in 2) and 3), files in 2) override files in 3).

You ship 2) basically empty (everything should go in 3).)

e.g. menu use
1: ~/.menu
2: /etc/menu
3: /usr/lib/menu

Cheers,
Bill.

Bug#215946: /etc/kde3/magic/*.magic

[Bill Allombert]

On Fri, Dec 05, 2003 at 12:39:43AM +0100, Dominique Devriese wrote:
> >> Please let us know if this fixes your problem, and if this bug can
> >> be closed.
> 
> > Until this is properly documented, the bug should not be closed.
> 
> How would you suggest this should be documented.

It is Debian specific ? if not it should go in the KDE documentation
in the 'How I add a new mime-type section'.

You can also add a file
/etc/kde3/magic/README
that explain the format, etc... and drop a note in README.Debian.

> > Also that does not address why KDE need its own mime-magic system.
> > Why not using the /etc/mime-magic file ?
> 
> Because the existing system was not sufficient.  KDE apps ( like
> e.g. kolf ) need to be able to install a file which contains some more
> data for the magic system.  It would not be a good idea ( imho, hope
> you agree with me on this ) to let them each edit the /etc/magic
> file.  The KDE system allows this by letting them put a *.magic file
> in $kde_prefix/config/magic/ or /etc/kde3/magic/ or
> ~/.kde/config/magic/.
> 
> I do disagree with your point about KDE not needing its own mime-magic
> system.  It would of course be better if it would use a general
> mime-magic system, but I'm currently not aware of any such things or
> whatever, that provide the functionality described above.

KDE need a mime-magic system. But it don't need to be private to KDE.
I mean, it make sense to configure KDE and GNOME to use different
programs for the same mime-type but not to see the same file with two
different mime-type.

It would make a lot of sense to add mime-magic support to mime-support.

> > Does the kolf magic file required to be a config files ? If not, why
> > not drop it under a directory that is not in /etc ?
> 
> I'm not sure about this issue ( I can see how it's not a user-editable
> config file, and thus it might not belong in /etc ( what are the
> criteria exactly ? As I see it, there are lots of things in /etc that
> don't really belong there ), but I'm not sure how technically possible
> it is to put it elsewhere ).

If you support both $kde_prefix/config/magic/ and /etc/kde3/magic/, I
don't see why kolf magic cannot go in $kde_prefix/config/magic.

In fact I am not sure why /etc/kde3/magic/ need to be a directory if
$kde_prefix/config/magic/ for application plug-in.

Cheers,
Bill.

Bug#215946: /etc/kde3/magic/*.magic

[Bill Allombert]

On Sat, Dec 13, 2003 at 02:05:50PM -0600, Colin Watson wrote:
> 
> Isn't this what's in the /usr/share/misc/file directory?

Is there a matching /etc file for local addition, like /etc/magic but
with MIME-types instead of string ?

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

kderemove menu tag

[Bill Allombert]

Hello KDE developers,

Christopher Martin was kind enough to write the documentation 
of the kderemove menu tag.

> Debian Menu System Documentation, Section 7.2.1
> 
> kderemove:
> All KDE applications should include this tag, using kderemove="y" to avoid
> a duplicate entry in the KDE menu, when KDE is used in conjunction with
> the Debian menu system. Without this tag, KDE's own menu will contain an
> entry for the application in its Debian menu system subfolders, in
> addition to the KDE menu system's own "native" entry. Such duplication is
> inelegant and can cause technical problems.

I plan to add it to the menu manual. So if you want to propose change,
please tell me.

For the record, there are 215 menu entries with kderemove,
152 with kderemove="y", 62 with kderemove="1& and one with 
kderemove="" (klogic).

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#237260: menu-methods use incorrectly replacewith

[Bill Allombert]

Package: kdelibs-bin
Version: 4:3.2.1-1
Severity: normal

Hello KDE maintainers,

I am testing the new KDE menu-methods and they are broken:

# update-menus
Unknown error, message=replacewith($string, $replace, $with): $replace and 
$with must have the same length.
install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-dirs: aborting
update-menus[4496]: Script 
/etc/menu-methods/freedesktop-desktop-entry-spec-dirs returned error status 1.
Unknown error, message=replacewith($string, $replace, $with): $replace and 
$with must have the same length.
install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-apps: aborting
update-menus[4496]: Script 
/etc/menu-methods/freedesktop-desktop-entry-spec-apps returned error status 1.

genmenu call replacewith($section,"/ ","-") which is incorrect, you need
to use replacewith($section,"/ ","--") if you want to replace both '/'
and ' ' by a dash. 

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=français, LC_CTYPE=français

Versions of packages kdelibs-bin depends on:
ii  kdelibs4  4:3.2.1-1  KDE core libraries
ii  libart-2.0-2  2.3.16-1   Library of functions for 2D graphi
ii  libbz2-1.01.0.2-1A high-quality block-sorting file 
ii  libc6 2.3.2.ds1-11   GNU C Library: Shared libraries an
ii  libcupsys21.1.20final-16 Common UNIX Printing System(tm) - 
ii  libfam0c102   2.7.0-5client library to control the FAM 
ii  libgcc1   1:3.3.3-2  GCC support library
ii  libgcrypt11.1.12-4   LGPL Crypto library - runtime libr
ii  libgnutls70.8.12-5   GNU TLS library - runtime library
ii  libice6   4.3.0-5Inter-Client Exchange library
ii  libpng12-01.2.5.0-5  PNG library - runtime
ii  libqt3c102-mt 3:3.2.3-2  Qt GUI Library (Threaded runtime v
ii  libsm64.3.0-5X Window System Session Management
ii  libstdc++51:3.3.3-2  The GNU Standard C++ Library v3
ii  libtasn1-00.1.2-1Manage ASN.1 structures (runtime)
ii  libx11-6  4.3.0-5X Window System protocol client li
ii  libxext6  4.3.0-5X Window System miscellaneous exte
ii  libxml2   2.6.6-1GNOME XML library
ii  libxrender1   0.8.3-5X Rendering Extension client libra
ii  libxslt1.11.1.2-3XSLT processing library - runtime 
ii  netpbm2:10.0-3   Graphics conversion tools
ii  python2.3.3-7An interactive high-level object-o
ii  xlibs 4.3.0-5X Window System client libraries m
ii  zlib1g1:1.2.1-4  compression library - runtime

-- no debconf information

Bug#237258: Please use KDE specific menu-method name

[Bill Allombert]

Package: kdelibs-bin
Version: 4:3.2.1-1
Severity: normal

Hello KDE maintainers,

I really appreciate your effort of implementing a freedesktop menu layer
on tope of Debian menu, especially since KDE is not the only menu-manager
to use freedesktop menu, so this work can be reused for e.g.
GNOME.

Do you have plan about that ?

Currently though, I feel that naming the KDE menu-methods names
freedesktop-desktop-entry-spec-dirs, freedesktop-desktop-entry-spec-apps

are inappropriate, since they are shipped in kdelibs-bin and will not
be available for other freedesktop menu system if KDE is not
installed, so I woulkd ask you to rename then to something keyed to KDE.
menu manual recommend to use  or - if an
extension is neccessary.

Of course, having those menu method in a package depended by all
freedesktop menu system is probably a better long term goal, but
that has yet to happen.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 
-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=français, LC_CTYPE=français

Versions of packages kdelibs-bin depends on:
ii  kdelibs4  4:3.2.1-1  KDE core libraries
ii  libart-2.0-2  2.3.16-1   Library of functions for 2D graphi
ii  libbz2-1.01.0.2-1A high-quality block-sorting file 
ii  libc6 2.3.2.ds1-11   GNU C Library: Shared libraries an
ii  libcupsys21.1.20final-16 Common UNIX Printing System(tm) - 
ii  libfam0c102   2.7.0-5client library to control the FAM 
ii  libgcc1   1:3.3.3-2  GCC support library
ii  libgcrypt11.1.12-4   LGPL Crypto library - runtime libr
ii  libgnutls70.8.12-5   GNU TLS library - runtime library
ii  libice6   4.3.0-5Inter-Client Exchange library
ii  libpng12-01.2.5.0-5  PNG library - runtime
ii  libqt3c102-mt 3:3.2.3-2  Qt GUI Library (Threaded runtime v
ii  libsm64.3.0-5X Window System Session Management
ii  libstdc++51:3.3.3-2  The GNU Standard C++ Library v3
ii  libtasn1-00.1.2-1Manage ASN.1 structures (runtime)
ii  libx11-6  4.3.0-5X Window System protocol client li
ii  libxext6  4.3.0-5X Window System miscellaneous exte
ii  libxml2   2.6.6-1GNOME XML library
ii  libxrender1   0.8.3-5X Rendering Extension client libra
ii  libxslt1.11.1.2-3XSLT processing library - runtime 
ii  netpbm2:10.0-3   Graphics conversion tools
ii  python2.3.3-7An interactive high-level object-o
ii  xlibs 4.3.0-5X Window System client libraries m
ii  zlib1g1:1.2.1-4  compression library - runtime

-- no debconf information

Bug#237260: menu-methods use incorrectly replacewith

[Bill Allombert]

On Wed, Mar 10, 2004 at 01:57:35PM -0600, Chris Cheney wrote:
> Then how come update-menus doesn't output the above messages for me? I'm
> not saying you are wrong just that update-menus in sid does not give the
> maintainer any notice that something is wrong like you imply in your bug
> report. Recall that I had mentioned that replacewith was confusing in
> the documentation, so the fact that update-menus really doesn't print
> any errors in the version in Debian compounds the likelyhood of scripts
> doing it wrong. A version of menu in Debian that can print messages like
> you showed above would be very useful for maintainers (imho).
> 
> calc:/etc/menu-methods# update-menus
> calc:/etc/menu-methods#
> 
> No error messages at all, -v (verbose) and -d (debug) doesn't show any
> errors either.
> 
> BTW - I have menu version 2.1.9-5.

Yes, I use the CVS version that does output this message. But either
way, using two parameters of different length is nonsensical.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#237258: Please use KDE specific menu-method name

[Bill Allombert]

On Wed, Mar 24, 2004 at 01:54:34AM -0600, Chris Cheney wrote:
> Probably the menu files should go into the menu package itself since
> they are so small (3K total) that they have no real need to be in a
> separate package by themselves. Then once Debian converts over to the
> freedesktop menu system after sarge releases it will be easy to remove
> it. :)

lol

> Currently Gnome does not follow the freedesktop menu spec or base
> directory spec (it partially implemented base dir for 2.6) but will
> most likely support both for Gnome 2.8 to be released ~ Sept 2004.

Well, this means Gnome in sarge will not be able to use the menu 
generated by those menu-methods and so they must only be run when KDE is
installed, so they belong to the KDE packages.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#239945: kdesu has no manpage

[Bill Allombert]

Package: kdebase-bin
Version: 4:3.2.1-1
Severity: normal

$ man kdesu
No manual entry for kdesu
See 'man 7 undocumented' for help when manual pages are not available.

$ man kdesud
No manual entry for kdesud
See 'man 7 undocumented' for help when manual pages are not available.

I expected setuid binaries to deserve more attention.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=fr_FR, LC_CTYPE=fr_FR

Versions of packages kdebase-bin depends on:
ii  kdelibs44:3.2.1-1KDE core libraries
ii  libart-2.0-22.3.16-3 Library of functions for 2D graphi
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libfam0c102 2.7.0-5  client library to control the FAM 
ii  libgcc1 1:3.3.3-4GCC support library
ii  libice6 4.3.0-7  Inter-Client Exchange library
ii  libpam-runtime  0.76-15  Runtime support for the PAM librar
ii  libpam0g0.76-15  Pluggable Authentication Modules l
ii  libpng12-0  1.2.5.0-5PNG library - runtime
ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime v
ii  libsm6  4.3.0-7  X Window System Session Management
ii  libstdc++5  1:3.3.3-4The GNU Standard C++ Library v3
ii  libx11-64.3.0-7  X Window System protocol client li
ii  libxext64.3.0-7  X Window System miscellaneous exte
ii  libxrender1 0.8.3-7  X Rendering Extension client libra
ii  libxtst64.3.0-7  X Window System event recording an
ii  xlibs   4.3.0-7  X Window System client libraries m
ii  zlib1g  1:1.2.1-5compression library - runtime

-- no debconf information

Re: Bug#241083: update-menus and kde 3.2

[Bill Allombert]

reassign 241083 kdelibs-bin
quit

On Fri, Apr 02, 2004 at 11:25:56PM +0200, giovanni wrote:
> update-menus doesn't work with kde 3.2 (from unstable)

This is a known problem with kdelibs-bin, redirected.

> These are the error messages:
> 
> sh: line 1: /usr/bin/kdm-update-menu: No such file or directory
> Unknown error, message=replacewith($string, $replace, $with): $replace
> and $with
> must have the same length.
> install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-dirs:
> aborting
> update-menus[1280]: Script
> /etc/menu-methods/freedesktop-desktop-entry-spec-dirs
> returned error status 1.
> Unknown error, message=replacewith($string, $replace, $with): $replace
> and $with
> must have the same length.
> install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-apps:
> aborting
> update-menus[1280]: Script
> /etc/menu-methods/freedesktop-desktop-entry-spec-apps
> returned error status 1.
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing')
> Architecture: i386 (i686)
> Kernel: Linux 2.4.25
> Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
> 
> Versions of packages menu depends on:
> ii  dpkg1.10.20  Package maintenance system for 
> Deb
> ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries 
> an
> ii  libgcc1 1:3.3.3-5GCC support library
> ii  libstdc++5  1:3.3.3-5The GNU Standard C++ Library v3
> 
> -- no debconf information

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Re: Bug#242975: /usr/bin/update-menus: Unknown error, message=replacewith($string, $replace, $with)

[Bill Allombert]

reassign 242975 kdm
quit
On Fri, Apr 09, 2004 at 06:43:32PM -0700, Yazz D. Atlas wrote:
> I seem to be having issues with update-menus... I was using gdm as my X 
> login
> manager and wanted to try kdm. Since switching I have lost choices of which
> desktop to run under gdm. Kdm lists afew while gdm now list just the few
> defaults and Gnome.

I don't think they still use update-menus to generate the list.

> ii  kdebase3.2.1-1KDE Base metapackage
> ii  twm4.3.0-7Tab window manager
> ii  gnome-session  2.4.2-4The GNOME 2 Session Manager
> ii  fluxbox0.9.4+cvs20030 Highly configurable and low resource 
> X11 Win
> ii  metacity   2.6.5-1A lightweight GTK2 based Window Manager
> 
> 
> Now when I run update-menus the following happens... 

This particular problem is supposed to be fixed in kdelibs-bin 3.2.2-1

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Re: Bug#237820: menu: update-menu 2.1.10 fails on some menu entries

[Bill Allombert]

reassign 237820 kdelibs-bin
tags 237820 fixed
quit

On Sat, Mar 13, 2004 at 08:49:22PM +0100, Jérôme Marant wrote:
> I'm sorry for the inconvenience. I'm reassigning the bug
> to kdelibs-bin.

It did not happen, so I am doing it now. As far as I know that bug can
be closed, since it i fixed in kdelibs-bin 3.2.2-1.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#237258: Please _really_ use KDE specific menu-method name

[Bill Allombert]

reopen 237258
thanks

Hello Chris,

This bug was probably closed by error:

$ dpkg -L kdelibs-bin | grep freedesktop
/etc/menu-methods/freedesktop-desktop-entry-spec-apps
/etc/menu-methods/freedesktop-desktop-entry-spec-dirs
$ dpkg -l kdelibs-bin | grep kdelibs-bin
ii  kdelibs-bin3.2.2-1KDE core binaries

Also I received complaints that Debian menu in kicker is broken
that I am investigating

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#243344: libarts1: most manpages are dummies

[Bill Allombert]

Package: libarts1
Version: 1.2.2-1
Severity: normal

Hello KDE maintainers,

Most manpages in this packages are dummy, at least
artsd  artsdsp  artsplay artsrec artsshell artswrapper
They look like

ARTSD(1)  ARTSD(1)

NAME
   artsd -- fixme

SYNOPSIS
   artsd  [-A]   [-a audioiomethod]  [-b bits]  [-D devicename]  [-d]  [-F
   fragments]  [-f]  [-h]  [-l level]  [-m appName]  [-N]  [-n]  [-p port]
   [-r samplingrate]  [-S size]  [-s seconds]  [-u]  [-v]  [-w n]

DESCRIPTION
   This manual page documents briefly the artsd command.

   artsd fixme.

OPTIONS
   This  program  follows  the  usual  GNU  command line syntax, with long
   options starting with two  dashes  (`-').   A  summary  of  options  is
   included below.

   -Afixme

which is not incredible useful.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=fr_FR, LC_CTYPE=fr_FR

Versions of packages libarts1 depends on:
ii  libartsc0   1.2.2-1  aRts Sound system C support librar
ii  libasound2  1.0.3b-1 Advanced Linux Sound Architecture 
ii  libaudio2   1.6c-3   The Network Audio System (NAS). (s
ii  libaudiofile0   0.2.6-3  Open-source version of SGI's audio
ii  libc6   2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libesd0 0.2.29-1 Enlightened Sound Daemon - Shared 
ii  libgcc1 1:3.3.3-6GCC support library
ii  libglib2.0-02.2.3-1  The GLib library of C routines
ii  libice6 4.3.0-7  Inter-Client Exchange library
ii  libmad0 0.15.0b-3MPEG audio decoder library
ii  libogg0 1.1.0-1  Ogg Bitstream Library
ii  libpng12-0  1.2.5.0-5PNG library - runtime
ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime v
ii  libsm6  4.3.0-7  X Window System Session Management
ii  libstdc++5  1:3.3.3-6The GNU Standard C++ Library v3
ii  libvorbis0a 1.0.1-1  The Vorbis General Audio Compressi
ii  libvorbisfile3  1.0.1-1  The Vorbis General Audio Compressi
ii  libx11-64.3.0-7  X Window System protocol client li
ii  libxext64.3.0-7  X Window System miscellaneous exte
ii  libxt6  4.3.0-7  X Toolkit Intrinsics
ii  xlibs   4.3.0-7  X Window System client libraries m
ii  zlib1g  1:1.2.1-5compression library - runtime

-- no debconf information

Bug#246561: kicker: No Debian menu displayed

[Bill Allombert]

Package: kicker
Version: 4:3.2.2-1
Severity: important

Hello,

Kicker do not display any Debian menus one way or the others.
I have installed menu-xdg fwiw.
I have tried to use a new user without any .dot file to no avail.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=fr_FR, LC_CTYPE=fr_FR

Versions of packages kicker depends on:
ii  kdebase-data4:3.2.2-1KDE Base (shared data)
ii  kdelibs44:3.2.2-2KDE core libraries
ii  libart-2.0-22.3.16-5 Library of functions for 2D graphi
ii  libc6   2.3.2.ds1-12 GNU C Library: Shared libraries an
ii  libfam0c102 2.7.0-5  client library to control the FAM 
ii  libgcc1 1:3.3.3-6GCC support library
ii  libice6 4.3.0-7  Inter-Client Exchange library
ii  libkonq44:3.2.2-1Core libraries for KDE's file mana
ii  libpng12-0  1.2.5.0-5PNG library - runtime
ii  libqt3c102-mt   3:3.2.3-2Qt GUI Library (Threaded runtime v
ii  libsm6  4.3.0-7  X Window System Session Management
ii  libstdc++5  1:3.3.3-6The GNU Standard C++ Library v3
ii  libx11-64.3.0-7  X Window System protocol client li
ii  libxext64.3.0-7  X Window System miscellaneous exte
ii  libxrender1 0.8.3-7  X Rendering Extension client libra
ii  libxtst64.3.0-7  X Window System event recording an
ii  xlibs   4.3.0-7  X Window System client libraries m
ii  zlib1g  1:1.2.1-5compression library - runtime

-- no debconf information

Bug#248610: kdelibs-bin should depends on menu-xdg

[Bill Allombert]

Package: kdelibs-bin
Version: 4:3.2.2-2
Severity: normal

Hello KDE developers,

I receive lots of bugs report of KDE user that do not have a menu
anymore.

I think kdelibs-bin should depends on menu-xdg for sarge:

1) menu-xdg is a very small package so there is no real gain to not have
it installed.

2) you can disable menu-xdg functionality by removing the conffiles it
provide, so you do not need to remove it.

3) This will make transition to the new menu-xdg system smoother

4) I look at recommends when installing a new package, not when
upgrading and I expect most users do the same, so I am not surprised
they did not see the new Recommends.

Cheers,
Bill.
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26
Locale: LANG=fr_FR, LC_CTYPE=fr_FR

Versions of packages kdelibs-bin depends on:
ii  kdelibs4   4:3.2.2-2 KDE core libraries
ii  libart-2.0-2   2.3.16-5  Library of functions for 2D graphi
ii  libbz2-1.0 1.0.2-1   A high-quality block-sorting file 
ii  libc6  2.3.2.ds1-12  GNU C Library: Shared libraries an
ii  libcupsys2 1.1.20final+cvs20040330-3 Common UNIX Printing System(tm) - 
ii  libfam0c1022.7.0-5   client library to control the FAM 
ii  libgcc11:3.3.3-7 GCC support library
ii  libgcrypt1 1.1.12-4  LGPL Crypto library - runtime libr
ii  libgnutls7 0.8.12-5  GNU TLS library - runtime library
ii  libice64.3.0.dfsg.1-1Inter-Client Exchange library
ii  libpng12-0 1.2.5.0-6 PNG library - runtime
ii  libqt3c102-mt  3:3.2.3-2 Qt GUI Library (Threaded runtime v
ii  libsm6 4.3.0.dfsg.1-1X Window System Session Management
ii  libstdc++5 1:3.3.3-7 The GNU Standard C++ Library v3
ii  libtasn1-0 0.1.2-2   Manage ASN.1 structures (runtime)
ii  libx11-6   4.3.0.dfsg.1-1X Window System protocol client li
ii  libxext6   4.3.0.dfsg.1-1X Window System miscellaneous exte
ii  libxml22.6.9-2   GNOME XML library
ii  libxrender10.8.3-7   X Rendering Extension client libra
ii  libxslt1.1 1.1.6-1   XSLT processing library - runtime 
ii  netpbm 2:10.0-3  Graphics conversion tools
ii  python 2.3.3-7   An interactive high-level object-o
ii  xlibs  4.3.0.dfsg.1-1X Window System client libraries m
ii  zlib1g 1:1.2.1-5 compression library - runtime

-- no debconf information

Bug#248610: kdelibs-bin should depends on menu-xdg

[Bill Allombert]

On Wed, May 12, 2004 at 08:50:33AM -0400, Christopher Martin wrote:
> On May 12, 2004 07:09, Bill Allombert wrote:
> > I receive lots of bugs report of KDE user that do not have a menu
> > anymore.
> 
> Yes, we got a bunch as well.
> 
> > I think kdelibs-bin should depends on menu-xdg for sarge:
> >
> > 1) menu-xdg is a very small package so there is no real gain to not
> > have it installed.
> 
> menu-xdg depends on menu, and many people don't necessarily want menu 

I don't think this particular dependency (menu-xdg depending on menu)
is warranted. Indeed, the menu manual explicitly recommends against
depending on menu. Previous KDE packages did not depend on menu.
menu is part of the desktop task, though.

> installed. Some window managers (i.e. blackbox) change completely their 
> menus based on whether or not the menu package is installed.

You can also disable the blackbox menu-method instead of removing menu.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Re: Bug #248860: xterm missing from KDE menus

[Bill Allombert]

reassign 248860 kdelibs-bin
thanks
On Fri, May 14, 2004 at 08:33:27AM +0800, John wrote:
> Bill Allombert wrote:
> >What I  am asking is whether you have a Debian submenu in kicker:
> >it should be between 'All applications' and 'Editors'.
> >If you think a picture worths thousand words, look here
> ><http://people.debian.org/~ballombe/menu-snapshot/menu_en.png>
> >to see where XTerm should be.
> >
> >If you have no Debian submenu in KDE at all, then the problem
> >is certainly related to KDE.
> > 
> >
> 
> I don't.

OK, so it is a KDE problem and npot an xterm one. I redirect the problem
to kdelibs-bin.

Cheers,
Bill.

Bug#243375: kdelibs-bin: menu-method freedesktop should set the Generic Name Field to longtitle instead of title

[Bill Allombert]

On Mon, Apr 12, 2004 at 03:24:29PM -0500, Chris Cheney wrote:
> That is 79 chars wide! That probably won't even fit on the screen width
> of many systems. I am not sure what happens in that case, whether it
> just wraps the text of displays part of it off the side of the screen.
> 
> There are two real bugs here that you have touched on though.
> 1. Debian menu has no real concept of GenericName

Debian menu do not need to. You can use a generictitle field in menu
file and set up menu-methods to use it.

> 2. KDE menu doesn't display comments as tooltips (Gnome does this nicely)
> 
> If both of those bugs were fixed it would work much better. We could
> have GenericName = generictitle() and Comment = longtitle() or something

You need a $generictitle, but we already have it. longtitle() do not
exist, and generictitle() is not needed, AFAICS.

Add to xdg-desktop-entry-spec-apps
"GenericName=" $generictitle

And start to add generictitle="A Generic title" in menu files.

> similiar to that. I look forward to the time when Debian will convert to
> the freedesktop menu standards so that the integration will be much
> smoother. :)

LOL

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#243375: kdelibs-bin: menu-method freedesktop should set the Generic Name Field to longtitle instead of title

[Bill Allombert]

On Sat, Jul 03, 2004 at 02:01:25AM +0200, Dominique Devriese wrote:
> Bill Allombert writes:
> 
> > On Mon, Apr 12, 2004 at 03:24:29PM -0500, Chris Cheney wrote:
> >> There are two real bugs here that you have touched on though.
> >> 1. Debian menu has no real concept of GenericName
> 
> > Debian menu do not need to. You can use a generictitle field in menu
> > file and set up menu-methods to use it.
> 
> I was going to ask whether it might not be possible to mandate the
> field in the menu policy, but after looking into the docs a bit, I
> guess I need to first ask whether it wouldn't be a good idea to
> mandate some (minimal) things the menu files need to contain ?

The documentation is clear about that:

 The fields  > You need a $generictitle, but we already have it. longtitle() do not
> > exist and generictitle() is not needed, AFAICS.
> 
> This seems very unclear to me.  AIUI, you mean that we "already have
> $generictitle" because the menu program and system don't need any
> changes outside of the menu files and menu methods to support the
> extra field ?  AFAICS, quite some packages do have $longtitle, so I
> think that saying that it doesn't exist is a bit strange.  And I don't

OK this is a bit technical...

What you need is a menu _variable_ ($foo). menu variable are created
dynamically from the menu entries, so $generictitle will exist as
soon as one menu entry provide a field generictitle="".

A menu _function_ foo() is something unrelated. We have a user-defined
title() function that let user choose between short titles and long
titles in window managers, but we do not have a longtitle() function
and I dont see what a generictitle() function would do either.
title() is defined by in menu.h by either

function title()=$title
or
function title()=ifelse($longtitle,$longtitle,$title)
depending of user choice.

> > Add to xdg-desktop-entry-spec-apps "GenericName=" $generictitle
> 
> > And start to add generictitle="A Generic title" in menu files.
> 
> Yeah, this is the easy part of the job.  The hard part is of course
> getting apps to provide the field.

Well, yes.

> >> similiar to that. I look forward to the time when Debian will
> >> convert to the freedesktop menu standards so that the integration
> >> will be much smoother. :)
> 
> > LOL
> 
> Hm, I'm wondering about how serious people are taking this.  I would
> personally like to see Debian move ( in the long term, like most
> Debian things ) to freedesktop menu standards, because those have a
> much higher chance of being available in third party software.  This
> is of course not at all urgent, and I'm not entirely sure it would be
> worth the extra effort.  What do you think about this ?

I don't think it will happen, or even that it is a good idea. Most
upstream .desktop (outside KDE or GNOME core) are made to advertise the
software rather than trying to build a consistent menu structure. 

I wonder if it would not be more worthwhile to keep the Debian menu
as an 'omnibus' menu, and reserve the xdg menu for the desktop
environnement. This way, the menu would provide a more consistent desktop
experience.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#243375: kdelibs-bin: menu-method freedesktop should set the Generic Name Field to longtitle instead of title

[Bill Allombert]

On Sat, Jul 03, 2004 at 02:08:24PM +0200, Dominique Devriese wrote:
> > The documentation is clear about that:
> 
> >  The fields  > are mandatory. Other fields are optional. Custom fields are
> > supported, so you can add new fields for you own purpose.
> 
> Right, I must have missed that.  How about adding longtitle and
> genericname to the mandated list ?

Because they are not mandatory for proper menu operation.

> > I don't think it will happen, or even that it is a good idea. Most
> > upstream .desktop (outside KDE or GNOME core) are made to advertise
> > the software rather than trying to build a consistent menu
> > structure.
> 
> Do you have examples of that ?  Wouldn't it be the job of the people

Consider asciijump as an example. 

> packaging the apps to fixup their .desktop files ?

Then there are no real benefit to use .desktop over menu files if you
have to edit them anyway. Experimentaly, people are more careful
when writing a new file that when editing upstream files.

> > I wonder if it would not be more worthwhile to keep the Debian menu
> > as an 'omnibus' menu, and reserve the xdg menu for the desktop
> > environnement. This way, the menu would provide a more consistent
> > desktop experience.
> 
> I don't really agree with the difference between what you call "the
> desktop environment", and other applications with menu methods.  In
> what way do these categories have different needs ?

I have no opinion myself, since I don't use desktop environments.
However reading comments about menus, I have seen several kind of users:

1) Users that want a menu with all available programs.

2) Users that want a menu with only 'Desktop' apps, say KDE programs and
openoffice.org. They claim that a menu entry for emacs e.g. is useless and 
confusing for newbie.

3) Users that prefer the Debian menu layout.

Having a separated (omnibus) Debian menu would let users 1 and 3 use it,
and do not get in the way of users 2). Of course, this is a compromise 
solution.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#273732: kdesktop and kdeeject have no manpages.

[Bill Allombert]

Package: kdesktop
Version: 4:3.3.0a-1
Severity: normal

Hello KDE Debian maintainers,

kdesktop include the following programs:
/usr/bin/kdeeject
/usr/bin/kdesktop
/usr/bin/kdesktop_lock
/usr/bin/kwebdesktop

but no matching manpages.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 

Bug#580044: kopete has circular Depends on libkopete4

[Bill Allombert]

Package: kopete
Version: 4:4.4.3-1
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between kopete and libkopete4:

kopete  :Depends: libkopete4 (>= 4:4.4.1)
libkopete4  :Depends: kopete

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100503103055.ga12...@yellowpig

Bug#588952: kchart has circular Depends on koffice-libs

[Bill Allombert]

Package: kchart
Version: 1:2.2.1-2
Severity: important

Hello Debian Qt/KDE Maintainers,

There is a circular dependency between kchart and koffice-libs:

kchart  :Depends: koffice-libs (>= 1:2.2.1-2)
koffice-libs:Depends: kchart

Circular dependencies involving shared libraries are known to cause problems
during upgrade between stable releases, so we should try to get rid of them.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100713183123.ga9...@yellowpig