Bug#981679: Close Bug: KDevelop 5.6.2 now recognizes Debian specific clang --version output
This bug can be closed. No longer an issue with KDevelop 5.6.2. Fixed in KDevelop git commit fa83c76b133a52c8ce0e7af0aa8c060fadaa8536 Background: Debian and Ubuntu (and others?) have unique clang --version output. KDevelop tries a few different ways to determine the clang include directory. The most successful method seems to be matching on the output of the 'clang --version' output (which the developers recognize as unsafe ).
Bug#981679: Regex not matching Debian's clang output
I dug into the source. I can see where another guess at the path could be made
or one of the existing 3 could be loosened up to match the output of Debian's
clang-11 --version output.
Details:
In KDevelop source: plugins/clang/duchain/clanghelpers.cpp
QString ClangHelpers::clangVersion(){
...
QRegularExpression re(QStringLiteral("^clang version (\\d+\\.\\d+\\.\\d+)"));
...
}
The regular expression won't match as the Debian version of clang-11 has the
line starting with 'Debian clang' instead of just 'clang'
>clang-11 --version
Debian clang version 11.0.1-2
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Bug#981679: Ignore my last post
Oops... ignore the llvm-config solution I posted earlier.
Bug#981679: KDevelop Clang plugin issue
I discovered that creating: sudo ln /usr/bin/llvm-config-11 /usr/bin/llvm-config Allows KDevelop to work properly. So maybe an update-alternatives could be involved or just link(s) set up during the install of llvm. Justin Jones -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Bug#707078: minor typos in package descriptions
Erik Esterer wrote:
There are a few minor typos in the package desription part of the control
file.
A patch (against the control file in experimental) to fix these typos is
included.
There are a couple more than you noticed.
--- a/debian/control 2013-05-07 11:45:47.806452323 +0200
+++ b/debian/control 2013-05-07 11:47:37.549271029 +0200
@@ -101,7 +101,7 @@
Description: monochromatic icons theme
A monochromatic icon theme, designed for accessibility purposes.
This would be more natural without the word purposes. And is it an
icons theme or an icon theme? Either might be plausible, but I'll
go for icons theme.
.
- This package is part of the KDE accessibility module
+ This package is part of the KDE accessibility module.
(There's a missing stops in the next one, too.)
Package: kdeartwork-theme-window
Architecture: any
@@ -109,7 +109,7 @@
Replaces: kde-window-manager ( 4:4.5.80)
Breaks: kde-window-manager ( 4:4.5.80)
Description: window decoration for the K Window manager (KWin)
- This package contains additional window decorations for K Window Manager
+ This package contains additional window decorations for the K Window
Manager.
.
This package is part of the KDE artwork module.
Is the K Window manager capitalised like that or as the K Window
Manager? And is it a window decoration or (some) window
decorations? Presumably the latter in each case.
@@ -118,7 +118,7 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: widget styles for applications using Qt or KDE Development
Platform
- Currently it provides the following themes:
+ Currently it provides the following theme:
* phase
.
This package is part of the KDE artwork module.
Here you skipped Package: kscreensaver, which says:
Description: Additional screensavers for KScreenSaver
This package contains screensavers for KScreenSaver.
(What, so the package named kscreensaver doesn't itself contain the
executable called kscreensaver? Oh, and in fact there is no such
executable, it's just a library? That's confusing already.)
.
KScreenSaver can use XScreenSaver collection of screensavers with the
'kscreensaver-xsavers' package.
I wasn't even sure what that meant until I had read the description
for kscreensaver-xsavers. Make it:
Installing kscreensaver-xsavers lets KScreenSaver also use the
XScreenSaver collection of screensavers.
@@ -171,7 +171,8 @@
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: desktop themes for KDE Plasma Workspaces
- This package include several desktops theme to change Plasma look and feel
+ This package includes several desktops theme to change Plasma look and
+ feel.
.
This package is part of the KDE artwork module.
And several desktops theme should be several desktop themes, and
it should probably be to change Plasma's look and feel.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru kdeartwork-4.8.4.pristine/debian/control kdeartwork-4.8.4/debian/control
--- kdeartwork-4.8.4.pristine/debian/control 2013-01-26 15:48:00.0 +
+++ kdeartwork-4.8.4/debian/control 2013-05-07 13:38:12.268269341 +0100
@@ -100,17 +100,18 @@
Replaces: kmouth ( 4:4.6)
Breaks: kmouth ( 4:4.6)
Description: monochromatic icons theme
- A monochromatic icon theme, designed for accessibility purposes.
+ A monochromatic icons theme, designed for accessibility.
.
- This package is part of the KDE accessibility module
+ This package is part of the KDE accessibility module.
Package: kdeartwork-theme-window
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: kde-window-manager ( 4:4.5.80)
Breaks: kde-window-manager ( 4:4.5.80)
-Description: window decoration for the K Window manager (KWin)
- This package contains additional window decorations for K Window Manager
+Description: window decorations for the K Window manager (KWin)
+ This package contains additional window decorations for the K Window
+ Manager.
.
This package is part of the KDE artwork module.
@@ -119,7 +120,7 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: widget styles for applications using Qt or KDE Development Platform
- Currently it provides the following themes:
+ Currently it provides the following theme:
* phase
.
This package is part of the KDE artwork module.
@@ -129,11 +130,11 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, kde-workspace-bin
Recommends: kde-window-manager, kscreensaver-xsavers (= ${binary:Version})
-Description: Additional screensavers for KScreenSaver
+Description: additional screensavers for KScreenSaver
This package contains screensavers for KScreenSaver.
.
- KScreenSaver can use XScreenSaver collection of screensavers with the
- 'kscreensaver-xsavers' package.
+ Installing
Bug#707078: minor typos in package descriptions
Justin B Rye wrote:
There are a couple more than you noticed.
Oops, and I sent mine too soon, too.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru kdeartwork-4.8.4.pristine/debian/control kdeartwork-4.8.4/debian/control
--- kdeartwork-4.8.4.pristine/debian/control 2013-01-26 15:48:00.0 +
+++ kdeartwork-4.8.4/debian/control 2013-05-07 13:44:00.694167176 +0100
@@ -100,17 +100,18 @@
Replaces: kmouth ( 4:4.6)
Breaks: kmouth ( 4:4.6)
Description: monochromatic icons theme
- A monochromatic icon theme, designed for accessibility purposes.
+ A monochromatic icons theme, designed for accessibility.
.
- This package is part of the KDE accessibility module
+ This package is part of the KDE accessibility module.
Package: kdeartwork-theme-window
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Replaces: kde-window-manager ( 4:4.5.80)
Breaks: kde-window-manager ( 4:4.5.80)
-Description: window decoration for the K Window manager (KWin)
- This package contains additional window decorations for K Window Manager
+Description: window decorations for the K Window Manager (KWin)
+ This package contains additional window decorations for the K Window
+ Manager.
.
This package is part of the KDE artwork module.
@@ -119,7 +120,7 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: widget styles for applications using Qt or KDE Development Platform
- Currently it provides the following themes:
+ Currently it provides the following theme:
* phase
.
This package is part of the KDE artwork module.
@@ -129,11 +130,11 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, kde-workspace-bin
Recommends: kde-window-manager, kscreensaver-xsavers (= ${binary:Version})
-Description: Additional screensavers for KScreenSaver
+Description: additional screensavers for KScreenSaver
This package contains screensavers for KScreenSaver.
.
- KScreenSaver can use XScreenSaver collection of screensavers with the
- 'kscreensaver-xsavers' package.
+ Installing kscreensaver-xsavers lets KScreenSaver also use the
+ XScreenSaver collection of screensavers.
.
This package is part of the KDE artwork module.
@@ -143,7 +144,7 @@
Depends: ${shlibs:Depends}, ${misc:Depends}, kde-workspace-bin, xscreensaver-data, xscreensaver-data-extra, xscreensaver-screensaver-bsod
Recommends: kde-window-manager, kscreensaver (= ${binary:Version}), xscreensaver-gl, xscreensaver-gl-extra
Suggests: kscreensaver-xsavers-webcollage (= ${source:Version})
-Description: xscreensaver support for KScreenSaver
+Description: XScreenSaver support for KScreenSaver
This package allows KScreenSaver to use the XScreenSaver collection of
screensavers.
.
@@ -155,9 +156,9 @@
Depends: ${misc:Depends}, kscreensaver-xsavers (= ${source:Version}), xscreensaver-screensaver-webcollage, miscfiles, netpbm
Description: webcollage screensaver support for KScreenSaver
This package allows KScreenSaver to use the WebCollage screensaver, which
- downloads random pictures from the internet to create a collage.
+ downloads random pictures from the Internet to create a collage.
.
- IMPORTANT NOTICE: The internet contains all kinds of pictures, some of which
+ IMPORTANT NOTICE: the Internet contains all kinds of pictures, some of which
might be found inappropriate or offensive.
It is recommended that this screensaver not be used a public environment,
workplace, or where it may be seen by children.
@@ -172,7 +173,8 @@
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: desktop themes for KDE Plasma Workspaces
- This package include several desktops theme to change Plasma look and feel
+ This package includes several desktop themes to change Plasma's look
+ and feel.
.
This package is part of the KDE artwork module.
Bug#679230: karbon: package description review
Package: karbon Version: 2.4.2 Severity: wishlist Tags: patch I'm glad to see the package descriptions for the KOffice^WCalligra suite are being maintained; but there are still a few typos and other language problems, especially in the description for karbon. Package: calligra [...] Description: extensive productivity and creative suite Calligra Suite is a set of applications written to help you to accomplish your work. It includes office applications such as a word processor, a spreadsheet, a presentation program, a database application, etc, and raster and vectorial graphics tools. There's no such thing as vectorial graphics. (Yes, the adjective vectorial exists, as in phrases like vectorial relativity; but no, for artwork we just use the attributive noun: vector graphics.) While I'm editing this I might as well insist on s/etc/etc./ too. (Likewise when this is repeated in the calligra-reports-* packages.) . This metapackage provides all the components of the Calligra Suite. Package: karbon [...] Description: vector graphics application for the Calligra Suite Karbon is a vector drawing application with an user interface that is easy to s/an user/a user/ use, highly customizable and extensible. [...] Is this meant to be saying that Karbon's UI is: 1) easy to use, 2) highly customizable-and-extensible (in which case there's a missing conjunction after easy to use); or is it saying that it's: 1) easy to use, 2) highly customizable, and 3) extensible (which is just mildly awkward, in that it has the most complex phrase in the middle rather than at the end)? I'll assume the latter, and suggest removing the ambiguity by reordering them: Karbon is a vector drawing application with a user interface that is easy to use, extensible and highly customizable. (If I was standardising the text towards debian-l10n-english's house style I would also insert an extra (Harvard) comma there, but at present these descriptions are consistently not using that style.) [...] That makes Karbon a great application s/That/This/. for users starting to explore the world of vector graphics as well as for artists wanting to create breathtaking vector art. Features include: . * Loading support for ODG, SVG, WPG, WMF, EPS/PS * Writing support for ODG, SVG, PNG, PDF, WMF These don't seem to be in any particular order - I would recommend lining them up so that it's obvious where the overlap is: * Loading support for ODG, SVG, WMF, WPG, EPS/PS * Writing support for ODG, SVG, WMF, PDF, PNG (For d-l-e house style I would start each bulletpoint with lowercase and end it with a semicolon, but that's also not in my patch.) * Customizable user interface with freely placable toolbars and dockers ^ Unspellcheckable typo: s/placable/placeable/ (placable is the opposite of implacable). * Layer docker for easy handling of complex documents including preview thumbnails, support for grouping shapes via drag and drop, controlling visibility of shapes or locking * Advanced path editing tool with great on-canvas editing capabilies ^^ Typo: s/capabilies/capabilities/ * Various drawing tools for creating path shapes including a draw path tool, a pencil tool as well as a calligraphy drawing tool You can't just substitute in as well as in place of and; it's either * Various drawing tools for creating path shapes including a draw path tool, a pencil tool(,) and a calligraphy drawing tool or for variety: * Various drawing tools for creating path shapes including a draw path tool and a pencil tool, as well as a calligraphy drawing tool * Gradient and pattern tools for easy on-canvas editing of gradient and pattern styles * Top notch snapping facilities for guided drawing and editing (e.g. snapping to grid, guide lines, path nodes, bounding boxes, orthogonal positions, intersections of path shapes or extensions of lines and paths) * Includes many predefined shapes including basic shapes like stars, circle/ellipse, rectangle, image This is the only item on the list expressed as a verb phrase, and it's a bit repetitive (as well as using like in a manner unpopular with English teachers). Besides, how is image a predefined basic shape that belongs on this list? So I'd suggest rephrasing it as: * Many predefined basic shapes included, such as circle/ellipse, star or rectangle * Artistic text shape with support for following path outlines (i.e. text on path) * Complex path operations and effects like boolean set operations, The dictionaries say Boolean is capitalised (at least when it's not a reserved word in some programming language). path flattening, rounding and refining as well as whirl/pinch effects * Extensible by writing plugins for new tools, shapes
Re: [RFR] templates://phonon/{phonon-backend-null.templates}
Sune Vuorela wrote: Christian PERRIER wrote: Quoting David Prévot (dav...@altern.org): Please avoid “Qt 4” in short description of user-oriented packages, as advised in the Developer's Reference, and prefer something like “multimedia framework for KDE”. I agree that not having KDE written anywhere is kind of strange. Nothing specific to KDE's software in phonon. You can easily use phonon in Qt- environments without any trace of the KDE Platform. Yes, this was indeed why I was avoiding KDE in the synopsis - it would make it sound as if installing phonon was likely to pull in lots of desktop-environment-specific dependencies. On the other hand, given that Qt 4 is there in the long description, you don't really need it in the synopsis. I replaced QT 4 multimedia framework by multimedia framework for KDE in packages' synopsis. Please don't. KDE is people producing software. Oh, great, corporate rebranding kicks us in the teeth again. KDE™ has been redefined to officially not mean the K Desktop Environment, so apparently we're supposed to be going through all Debian's docs replacing KDE with Plasma Workspaces or something... multimedia framework by KDE would be correct, but look a bit weird. And I strongly suspect it would fail to communicate the idea to normal users anyway. How about from KDE? It's getting longer, but it simultaneously avoids the implication that it'll bring all its friends with it and pays lipservice to the new KDE is people idea... -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package -- 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/20110331113725.ga24...@xibalba.demon.co.uk
Re: [RFR] templates://phonon/{phonon-backend-null.templates}
Modestas Vainius wrote:
+ [...] The following Phonon
+ backend packages seem to be available for this system at the moment:
As long as we can trust the detection (what does this depend on?)
phonon-backends provide 'phonon-backend' virtual package.
Yes, and I don't see any non-free or i386-only or experimental
candidates - you're guaranteed a reliable list, with only the
recommended package ever likely to vary. That's why I went on to
take out the phrasing about needing to detect the ones that seem to
be available for this system at the moment.
To restore full Phonon multimedia capabilities, install one of the
Phonon back-end packages which are currently available for this system:
phonon-backend-null is a backend as well. I would like to see the word real
in this sentence.
My patch had no real Phonon back-end earlier, but okay, it wouldn't
hurt to add it here too. Or maybe one of the two mentions should make
it more explicit that it's unreal in the sense of being a dummy.
Oh, and I notice I missed a s/backend/back-end/, and I said Qt
multimedia framework for KDE when everywhere else it's Qt 4 and
desktop-neutral (does the version number matter? Are we ever
expecting to see a Qt 5?):
_Description: Missing back-end for Phonon
Applications using Phonon (the Qt 4 multimedia framework) will produce
no audio or video output, because only a dummy Phonon back-end is
installed on this system. This is typically an unintended configuration.
.
To restore full Phonon multimedia capabilities, install one of the real
Phonon back-end packages which are currently available for this system:
.
${recommended_backend} (recommended)${other_backends}
s/behaviour/behavior/
Are we using American English in Debian?
You're under no obligation to fake the accent, we've just chosen
standardization rather than standardisation for these reviews...
[PS:]
E: phonon: description-starts-with-package-name
I'm not sure why it's worse to *start* with the packagename than just
to redundantly *include* it within the description (personally I'm
more annoyed by all those package synopses that just describe package
foo as The GNU version of foo). But yes, maybe we should consider
changing all of them to something more purely descriptive like Qt 4
multimedia framework. I'll put that in my new patch too.
Note that this version changes libphononexperimental-dev's description
from
development files for the Phonon-Experimental library
to
Qt 4 multimedia framework - experimental development files
This may be distorting things too far - is there a better way of
accommodating the Phonon-Experimental library within this format?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Template: phonon-backend-null/isnt_functional_title
Type: title
_Description: Warning: Phonon is not functional
Template: phonon-backend-null/isnt_functional
Type: note
#flag:comment:4
# Translators: do not translate variable names
# only translate (recommended) (the one in parenthesis)
_Description: Missing back-end for Phonon
Applications using Phonon (the Qt 4 multimedia framework) will produce
no audio or video output, because only a dummy Phonon back-end is
installed on this system. This is typically an unintended configuration.
.
To restore full Phonon multimedia capabilities, install one of the real
Phonon back-end packages which are currently available for this system:
.
${recommended_backend} (recommended)${other_backends}
Source: phonon
Section: sound
Priority: optional
Maintainer: Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org
Uploaders: Modestas Vainius mo...@debian.org, Fathi Boudra f...@debian.org
Build-Depends: cdbs (= 0.4.51), debhelper (= 7.4.13), cmake (= 2.6.2),
pkg-kde-tools (= 0.11), dpkg-dev (= 1.15.5), automoc, libglib2.0-dev,
libpulse-dev (= 0.9.21), libqt4-dev (= 4.5)
Standards-Version: 3.9.1
Homepage: http://phonon.kde.org/
Vcs-Browser: http://git.debian.org/?p=pkg-kde/kde-req/phonon.git
Vcs-Git: git://git.debian.org/pkg-kde/kde-req/phonon.git
Package: phonon
Architecture: all
Depends: ${misc:Depends}, libphonon4 (= ${source:Version}),
${phonon:Recommended-Backend} | phonon-backend
Suggests: ${phonon:Recommended-Backend}, phonon-backend-gstreamer,
phonon-backend-xine, phonon-backend-mplayer
Description: Qt 4 multimedia framework - metapackage
Phonon is the Qt 4 multimedia API, which provides a task-oriented abstraction
layer for capturing, mixing, processing, and playing audio and video content.
.
This metapackage ensures that the system has a working Phonon configuration
installed (the core library and at least one back-end).
Package: libphonon-dev
Architecture: any
Section: libdevel
Depends: ${misc:Depends}, libphonon4 (= ${binary:Version}),
${sameVersionDep:libqt4-dev:libphonon4}, phonon-backend-null | phonon
Description: Qt 4 multimedia framework - development files
Phonon
Re: [RFR] templates://phonon/{phonon-backend-null.templates}
(My patch goes along with the request to revert to Type: note.) Christian PERRIER wrote: +_Description: Missing backend for Phonon The spelling backend is developerese - the standard English spelling is back end (and it's not that dictionaries are lagging behind normal usage; see e.g. http://en.wikipedia.org/wiki/Back_end;). But since I've already seen how hard it is to get developers to accept this I'll suggest the compromise form back-end within English text. + Phonon-based (i.e. most KDE and some Qt) applications will produce no audio or + video output because there is no real Phonon backend installed on this system. Typically, this is an undesirable configuration which you might have gotten to unintentionally. This use of -based is a potentially confusing shorthand - things like KTorrent aren't derivatives of Phonon, they just depend on it. Maybe we could simplify the syntax a bit and say: Applications using Phonon (the Qt multimedia framework for KDE) will produce no audio or video output because there is no real Phonon back-end installed on this system. This is typically an unintended configuration. . + If you wish to restore full Phonon multimedia capabilities, you + should install a real Phonon backend. The following Phonon + backend packages seem to be available for this system at the moment: As long as we can trust the detection (what does this depend on?) we could rely on the colon to imply most of this: To restore full Phonon multimedia capabilities, install one of the Phonon back-end packages which are currently available for this system: (This turns install back into an imperative, but with the preceding purpose clause it's advisory rather than a command.) The package descriptions have really good boilerplate already, so my corrections are mostly very fiddly: Package: phonon [...] + This metapackage ensures that a user has a working Phonon configuration installed on the system (the core library and at least one backend). Package installations work per-computer, not per-user. This metapackage ensures that the system has a working Phonon configuration installed (the core library and at least one back-end). Package: libphonon-dev [...] This package contains the development files needed to build Qt 4 applications using Phonon cross-platform multimedia framework. ^the Package: libphononexperimental-dev [...] +Description: Phonon-Experimental multimedia framework - development files Or should these packages be Description: Phonon multimedia framework - experimental library development files ...and so on? But that's not in my patch. This package contains the development files needed to build Phonon backends or + internal applications which need the Phonon-Experimental library. Third-party applications should not depend on this library. Please read README.Debian if you consider to Build-Depend on this package. That should be if you are considering Build-Depending on..., or just if you are considering a build-dependency on Package: libphononexperimental4 [...] This package contains the Phonon-Experimental library which might be needed by ^, Phonon backends or other internal applications. Third-party applications should not depend on this library. Please read README.Debian before using this library. Package: phonon-backend-null [...] This package does not provide any real Phonon backend. It can be used to disable Phonon audio/video capabilities. Please note that Phonon behaviour with this package installed has not been well tested. s/behaviour/behavior/ Package: phonon-dbg [...] This package contains debugging symbols of the Phonon library and main backends You should install this package when you are about to report a crash or want to debug a problem with Phonon or its backends. This package contains debugging symbols for the Phonon library and its main back-ends. Install it if you want to report a crash or debug a problem with Phonon or its back-ends. * * * Obligatory Why-The-Name Appendix: http://phonon.kde.org/cms/1020 -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package Template: phonon-backend-null/isnt_functional_title Type: title _Description: Warning: Phonon is not functional Template: phonon-backend-null/isnt_functional Type: note #flag:comment:4 # Translators: do not translate variable names # only translate (recommended) (the one in parenthesis) _Description: Missing backend for Phonon Applications using Phonon (the Qt multimedia framework for KDE) will produce no audio or video output because there is no real Phonon back-end installed on this system. This is typically an unintended configuration. . To restore full Phonon multimedia capabilities, install one of the Phonon
Bug#614947: konqueror-nsplugins: cobwebby package description
Package: konqueror-nsplugins
Version: 4:4.4.5-2
Severity: wishlist
Tags: patch
I've been running through the package lists looking for outdated
descriptions that no longer fulfill the requirement (in Debian Policy
3.4) that package descriptions should convey to readers why they might
want to have the software in question installed.
Description: Netscape plugin support for Konqueror
This package enables Konqueror to use Netscape plugins, such as Flash.
.
This package is part of the KDE base applications module.
Yes, well. I'd suggest:
Description: plugin support for Konqueror
Konqueror is the KDE web browser and advanced file manager. This is
a compatibility library enabling it to use plugins designed for
Netscape/Mozilla/etc (such as Flash).
.
This package is part of the KDE base applications module.
Given that konqueror-plugin-gnash provides Flash without this package
(and exists outside non-free/i386) should we perhaps be referencing
mozilla-openoffice instead? Though that's also a legacy name that'll
presumably need to change soon...
--
JBR
Ankh kak! (Ancient Egyptian blessing)
diff -ru kdebase-4.4.5.pristine/debian/control kdebase-4.4.5/debian/control
--- kdebase-4.4.5.pristine/debian/control 2011-01-13 19:35:37.0 +
+++ kdebase-4.4.5/debian/control 2011-02-24 12:24:03.485259012 +
@@ -145,8 +145,10 @@
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Breaks: gtk-qt-engine ( 1:1.0)
-Description: Netscape plugin support for Konqueror
- This package enables Konqueror to use Netscape plugins, such as Flash.
+Description: plugin support for Konqueror
+ Konqueror is the KDE web browser and advanced file manager. This is
+ a compatibility library enabling it to use plugins designed for
+ Netscape/Mozilla/etc (such as Flash).
.
This package is part of the KDE base applications module.
Re: [RFR] templates://kde4libs/{kdelibs5.templates}
Christian Perrier wrote:
Your review should be sent as an answer to this mail.
Luckily enough I didn't see anything worth complaining about in the
control file, once I'd got my head round the fact that kdelibs5
provides libraries for KDE 4.
_Description: Stop possible unsafe upgrade of KDE4 with running sessions?
[...]
+ Some KDE 4 applications are currently running (${apps}). It is recommended
+ to abort the upgrade of kdelibs5, terminate all KDE applications and KDE
sessions and try
upgrading again.
[...]
This phrasing all looks okay, but can you safely put ${apps} in the
middle like that, or is it liable to burst the paragraph? How about
shuffling things like this:
You are about to upgrade to the new version of the kdelibs5 package, which
introduces a major configuration change - details are given in
/usr/share/doc/kdelibs5/README.Debian (in short: user settings are moved
from ~/.kde to ~/.kde4). However, some KDE 4 applications are currently
running: ${apps}
.
It is recommended to abort the upgrade of kdelibs5, terminate all KDE
applications and KDE sessions, and try upgrading again.
.
+ If you choose to coontinue the upgrade, [...]
^typo
Oh, in fact there's stuff I'd change here:
Template: kdelibs5/upgrade_kdehome_info
Type: note
_Description: New user settings directory (KDEHOME) for KDE 4 applications
Once this package is upgraded, KDE 4 applications will use ~/.kde directory
to
store user settings and data (also known as KDEHOME) by default. Currently,
KDE 4 applications use ~/.kde4. KDE 3 applications has always used (and will
continue to use) ~/.kde.
Make that:
Once this package is upgraded, KDE 4 applications will use ~/.kde as the
default
directory to store user settings and data in (also known as KDEHOME).
Currently
KDE 4 applications use ~/.kde4. KDE 3 applications have always used (and
will
continue to use) ~/.kde.
+ When the upgrade is complete, it is safe to login to KDE as usual or, if
you are
only using individual KDE 4 applications, you may use Kaboom (available in
the
+ package of the same name) wizard to migrate user data before starting a
KDE 4 application.
To log in. The Kaboom (...) wizard part is slightly awkward but
patching it up spoils the same name part. (I hope nobody gets
confused by the package description for madbomber...)
When the upgrade is complete, it is safe to log in to KDE as usual; or, if
you
are only using individual KDE 4 applications, you can use the Kaboom wizard
(in
the package kaboom) to migrate user data before starting a KDE 4
application.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- kde4libs-4.3.2.pristine/debian/kdelibs5.templates 2009-10-08
07:33:28.0 +0100
+++ kde4libs-4.3.2/debian/kdelibs5.templates2009-10-17 11:17:22.0
+0100
@@ -6,27 +6,18 @@
Type: boolean
Default: true
_Description: Stop possible unsafe upgrade of KDE4 with running sessions?
- You are about to upgrade to the new version of the kdelibs5 package which
- introduces a major configuration change. Newly started KDE 4 applications
- will use ~/.kde directory to store user settings and data (also known as
- KDEHOME) by default while currently running KDE 4 applications use ~/.kde4.
- KDE 3 applications have always used (and will continue to use) ~/.kde. It
- seems that there are a few KDE 4 applications running on your system at the
- moment. To avoid potential setting/data loss, you should:
+ You are about to upgrade to the new version of the kdelibs5 package, which
+ introduces a major configuration change - details are given in
+ /usr/share/doc/kdelibs5/README.Debian (in short: user settings are moved
+ from ~/.kde to ~/.kde4). However, some KDE 4 applications are currently
+ running: ${apps}
.
- 1) Answer Yes, terminate all KDE applications and KDE sessions and try
- upgrading again.
+ It is recommended to abort the upgrade of kdelibs5, terminate all KDE
+ applications and KDE sessions, and try upgrading again.
.
- or 2) Answer No to continue upgrading. You should make sure that no new
- KDE 4 applications are started before you migrate your KDE 4 settings and
- data. Beware, that clean termination of the old KDE 4 session might not be
- safe..
- .
- Once upgrade is complete, login to KDE as usual or you may use Kaboom wizard
- (package name: kaboom) to migrate your user settings and data before starting
- any KDE 4 application.
- .
- Currently running KDE 4 applications: ${apps}
+ If you choose to continue the upgrade, you should make sure that no new
+ KDE 4 applications are started before KDE 4 settings and data are migrated.
+ A clean termination of the old KDE 4 session might not be safe.
Template: kdelibs5/upgrade_kdehome_info_title
Type: title
@@ -35,12 +26,11 @@
Template: kdelibs5/upgrade_kdehome_info
Type: note
Re: [RFR] templates://kde4libs/{kdelibs5.templates}
Sune Vuorela wrote:
Full NACK. You are changing the message. We are not moving from .kde to
.kde4.
Oops, I missed that. Revised patch with from ~/.kde4 to ~/.kde
attached.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
--- kde4libs-4.3.2.pristine/debian/kdelibs5.templates 2009-10-08
07:33:28.0 +0100
+++ kde4libs-4.3.2/debian/kdelibs5.templates2009-10-17 11:17:22.0
+0100
@@ -6,27 +6,18 @@
Type: boolean
Default: true
_Description: Stop possible unsafe upgrade of KDE4 with running sessions?
- You are about to upgrade to the new version of the kdelibs5 package which
- introduces a major configuration change. Newly started KDE 4 applications
- will use ~/.kde directory to store user settings and data (also known as
- KDEHOME) by default while currently running KDE 4 applications use ~/.kde4.
- KDE 3 applications have always used (and will continue to use) ~/.kde. It
- seems that there are a few KDE 4 applications running on your system at the
- moment. To avoid potential setting/data loss, you should:
+ You are about to upgrade to the new version of the kdelibs5 package, which
+ introduces a major configuration change - details are given in
+ /usr/share/doc/kdelibs5/README.Debian (in short: user settings are moved
+ from ~/.kde4 to ~/.kde). However, some KDE 4 applications are currently
+ running: ${apps}
.
- 1) Answer Yes, terminate all KDE applications and KDE sessions and try
- upgrading again.
+ It is recommended to abort the upgrade of kdelibs5, terminate all KDE
+ applications and KDE sessions, and try upgrading again.
.
- or 2) Answer No to continue upgrading. You should make sure that no new
- KDE 4 applications are started before you migrate your KDE 4 settings and
- data. Beware, that clean termination of the old KDE 4 session might not be
- safe..
- .
- Once upgrade is complete, login to KDE as usual or you may use Kaboom wizard
- (package name: kaboom) to migrate your user settings and data before starting
- any KDE 4 application.
- .
- Currently running KDE 4 applications: ${apps}
+ If you choose to continue the upgrade, you should make sure that no new
+ KDE 4 applications are started before KDE 4 settings and data are migrated.
+ A clean termination of the old KDE 4 session might not be safe.
Template: kdelibs5/upgrade_kdehome_info_title
Type: title
@@ -35,12 +26,11 @@
Template: kdelibs5/upgrade_kdehome_info
Type: note
_Description: New user settings directory (KDEHOME) for KDE 4 applications
- Once this package is upgraded, KDE 4 applications will use ~/.kde directory to
- store user settings and data (also known as KDEHOME) by default. Currently,
- KDE 4 applications use ~/.kde4. KDE 3 applications has always used (and will
+ Once this package is upgraded, KDE 4 applications will use ~/.kde as the
default
+ directory to store user settings and data in (also known as KDEHOME).
Currently,
+ KDE 4 applications use ~/.kde4. KDE 3 applications have always used (and will
continue to use) ~/.kde.
.
- When upgrade is complete, it is safe to login to KDE as usual or, if you are
- only using individual KDE 4 applications, you may use Kaboom (available in the
- package of the same name) wizard to migrate your user data before starting a
- KDE 4 application.
+ When the upgrade is complete, it is safe to log in to KDE as usual; or, if you
+ are only using individual KDE 4 applications, you may use the Kaboom wizard
(in
+ the package kaboom) to migrate user data before starting a KDE 4 application.
Template: kdelibs5/upgrade_kdehome_running_title
Type: title
_Description: Upgrading kdelibs5 while KDE 4 is running
Template: kdelibs5/upgrade_kdehome_running
Type: boolean
Default: true
_Description: Stop possible unsafe upgrade of KDE4 with running sessions?
You are about to upgrade to the new version of the kdelibs5 package, which
introduces a major configuration change - details are given in
/usr/share/doc/kdelibs5/README.Debian (in short: user settings are moved
from ~/.kde4 to ~/.kde). However, some KDE 4 applications are currently
running: ${apps}
.
It is recommended to abort the upgrade of kdelibs5, terminate all KDE
applications and KDE sessions, and try upgrading again.
.
If you choose to continue the upgrade, you should make sure that no new
KDE 4 applications are started before KDE 4 settings and data are migrated.
A clean termination of the old KDE 4 session might not be safe.
Template: kdelibs5/upgrade_kdehome_info_title
Type: title
_Description: Upgrading kdelibs5
Template: kdelibs5/upgrade_kdehome_info
Type: note
_Description: New user settings directory (KDEHOME) for KDE 4 applications
Once this package is upgraded, KDE 4 applications will use ~/.kde as the
default
directory to store user settings and data in (also known as KDEHOME).
Currently,
KDE 4 applications use ~/.kde4. KDE 3 applications have always used (and will
continue
Bug#547527: plasma desktop crashes and coredumps
Package: kdebase-workspace-bin Version: 4.3.1-1 It seems to crash quite often- but this time it crashed when I was switching between virtual desktops by using alt-f1, alt-f2, etc. backtrace: Core was generated by `plasma-desktop --nocrashhandler'. Program terminated with signal 11, Segmentation fault. #0 0xa8afb446 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so (gdb) bt #0 0xa8afb446 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #1 0xa8af7611 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #2 0xa8af7ffd in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #3 0xa8af80bb in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #4 0xa8af8a74 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #5 0xa8af8b2c in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #6 0xa8b04b76 in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #7 0xa8b0608c in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #8 0xb6885b33 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #9 0xb6886782 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #10 0xa8abfbe3 in TaskManager::TaskGroup::itemRemoved(TaskManager::AbstractGroupableItem*) () from /usr/lib/libtaskmanager.so.4 #11 0xa8ac05fb in TaskManager::TaskGroup::remove(TaskManager::AbstractGroupableItem*) () from /usr/lib/libtaskmanager.so.4 #12 0xa8aa779d in ?? () from /usr/lib/libtaskmanager.so.4 #13 0xa8aa7c87 in ?? () from /usr/lib/libtaskmanager.so.4 #14 0xa8aa903e in TaskManager::GroupManager::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libtaskmanager.so.4 #15 0xb6885b33 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #16 0xb6886782 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #17 0xb68c1177 in QTimer::timeout() () from /usr/lib/libQtCore.so.4 #18 0xb688be9e in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4 #19 0xb6880bcf in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #20 0xb6b1b814 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #21 0xb6b2397e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #22 0xb77a04ad in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #23 0xb68709cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #24 0xb689f361 in ?? () from /usr/lib/libQtCore.so.4 #25 0xb689b900 in ?? () from /usr/lib/libQtCore.so.4 #26 0xb4f454b8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #27 0xb4f48a13 in ?? () from /usr/lib/libglib-2.0.so.0 #28 0xb4f48b98 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #29 0xb689b858 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #30 0xb6bbafd5 in ?? () from /usr/lib/libQtGui.so.4 #31 0xb686f01a in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #32 0xb686f462 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #33 0xb68718b9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #34 0xb6b1b697 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #35 0xb7f1af40 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #36 0x080485b2 in _start () (gdb) Justin. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540778: kde theme: sticky thumb/tack is black (lost icon?)
Package: kdebase Version: 4.2.4-1 Distribution: 32-bit/testing After an apt-get dist-upgrade a few days ago (testing) and cleaning up several hundred old packages, the thumb/tack on the top left corner of the theme I am using is now black, is there a specific package that handles this icon within the theme, or? Probably an issue I caused(?) which package missing would cause this? See attached or check the image here: (3.5KiB) http://home.comcast.net/~jpiszcz/20090810/xterm.png Justin.attachment: xterm.png
Bug#540799: kde theme: sticky thumb/tack is black (lost icon?)
Package: kdebase Version: 4.2.4-1 I have a second system that is showing the same problem. Distribution: 32-bit/testing After an apt-get dist-upgrade a few days ago (testing) and cleaning up several hundred old packages, the thumb/tack on the top left corner of the theme I am using is now black, is there a specific package that handles this icon within the theme, or? Probably an issue I caused(?) which package missing would cause this? See attached or check the image here: (3.5KiB) http://home.comcast.net/~jpiszcz/20090810/xterm.png Justin. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525539: kwin in testing is still broken (for 1-2 months now)
Package: kwin Version: 3.5.10.dfsg.1-2 It is not compiled with XINERAMA support so all of the windows do not appear properly when using multiple monitors. A version that works is: kwin_3.5.9.dfsg.1-6_i386.deb When will this be fixed in mainline -testing so I no longer have to pin this package to this version? Justin. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525539: kwin in testing is still broken (for 1-2 months now)
On Sat, 25 Apr 2009, Lisandro Damián Nicanor Pérez Meyer wrote: On Sáb 25 Abr 2009 07:41:06 Justin Piszcz escribió: Package: kwin Version: 3.5.10.dfsg.1-2 It is not compiled with XINERAMA support so all of the windows do not appear properly when using multiple monitors. A version that works is: kwin_3.5.9.dfsg.1-6_i386.deb When will this be fixed in mainline -testing so I no longer have to pin this package to this version? It will not be fixed, as it will be replaced by KDE 4's counterpart as soon as it gets to testing. As KDE 4 is already in unstable, we can not upload a new version of kwin fro KDE 3. Maybe this bug should be tagged wontifx... -- Bebe a bordo (pero con moderación) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ Indeed, Ok-- now I know, thanks for the update, will keep installing the old version for now until KDE4 arrives in -testing. Justin.
Bug#522624: xinerama bug with latest kwin 3.5.10-1/3.5.10.dfsg.1-2
Package: kwin Version: 3.5.10-1 Just to confirm, I have the same bug after running apt-get dist-upgrade today, windows maximize incorrectly, xterms go to the wrong monitors, etc. http://lists.debian.org/debian-qt-kde/2009/03/msg00139.html http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg629706.html Fix/work-around, download this (for i386): http://debian.oregonstate.edu/debian/pool/main/k/kdebase/kwin_3.5.9.dfsg.1-6_i386.deb # dpkg -i kwin_3.5.9.dfsg.1-6_i386.deb dpkg - warning: downgrading kwin from 4:3.5.10.dfsg.1-2 to 4:3.5.9.dfsg.1-6. (Reading database ... 159424 files and directories currently installed.) Preparing to replace kwin 4:3.5.10.dfsg.1-2 (using kwin_3.5.9.dfsg.1-6_i386.deb) ... Unpacking replacement kwin ... Setting up kwin (4:3.5.9.dfsg.1-6) ... Add this to your /etc/apt/preferences: Package: kwin Pin: version 3.5.9* Pin-Priority: 1000 This fixes the problem for now until a new version of kwin is release w/xinerama support. Justin. -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#457323: kdm: PreselectUser=None fails to inhibit reading a pre-existing user cache
Package: kdm Version: 4:3.5.8.dfsg.1-2 Severity: normal After setting PreselectUser=None, a user was still preselected. It was necessary to [re]move /var/lib/kdm/kdmsts to avoid username preselection. So it seems that PreselectUser=None fails to work as advertized: # None - do not preselect any user However what it actually seems to do is: avoid updating the previous-username cache. I think the effect of PreselectUser=None should be to avoid *reading* the file. Inhibiting its update is a possible 2ndary effect. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#444251: dpkg-reconfigure bash doesn't work
reassign 444251 kompare severity 440945 important forcemerge 440945 444251 thanks On Thu, Sep 27, 2007 at 10:16:01AM +0200, [EMAIL PROTECTED] wrote: Package: bash Version: 3.1dfsg-8 Severity: important As bash completion doesn't work anymore on my box, I was trying to reconfigure bash, but when running dpkg-reconfigure bash I get this error (in french) Dans le fichier « /usr/share/menu/kompare » à (ou dans la définition qui se termine à) la ligne 2 : ?package(kompare): needs=x11\T ^ Attendu : « = » Traitement du fichier abandonné en raison d'erreurs... Seem actually to be a problem with kompare during update menus. FYI you can should send future error messages in english by first doing: export LC_ALL=C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kscreensaver: conffile prompt during testing update
Package: kdebase-bin Version: 3.5.2-2+b1 Severity: important File: /etc/pam.d/kscreensaver I didn't make this change, so I should not be prompted about it. I couldn't reproduce it, though, so I'm not filing it as bug.. Preparing to replace kdebase-bin 4:3.5.2-1 (using .../kdebase-bin_4%3a3.5.2-2+b1_i386.deb) ... Unpacking replacement kdebase-bin ... [...] Setting up kdebase-bin (3.5.2-2+b1) ... Installing new version of config file /etc/pam.d/kcheckpass ... Configuration file `/etc/pam.d/kscreensaver' == File on system created by you or by a script. == File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : background this process to examine the situation The default action is to keep your current version. *** kscreensaver (Y/I/N/O/D/Z) [default=N] ? D --- /etc/pam.d/kscreensaver 2004-04-11 14:46:01.0 -0400 +++ /etc/pam.d/kscreensaver.dpkg-new2006-05-06 21:18:35.0 -0400 @@ -1,10 +1,6 @@ # # /etc/pam.d/kscreensaver - specify the PAM behaviour of kscreensaver # - -# The standard Unix authentication modules, used with -# NIS (man nsswitch) as well as normal /etc/passwd and -# /etc/shadow entries. @include common-auth @include common-account @include common-password --- /etc/pam.d/kscreensaver 2004-04-11 14:46:01.0 -0400 +++ /etc/pam.d/kscreensaver.dpkg-new2006-05-06 21:18:35.0 -0400 @@ -1,10 +1,6 @@ # # /etc/pam.d/kscreensaver - specify the PAM behaviour of kscreensaver # - -# The standard Unix authentication modules, used with -# NIS (man nsswitch) as well as normal /etc/passwd and -# /etc/shadow entries. @include common-auth @include common-account @include common-password
Re: kscreensaver: conffile prompt during testing update
On Fri, May 19, 2006 at 04:26:04PM +0200, Pierre Habouzit wrote: Le Ven 19 Mai 2006 15:33, Justin Pryzby a ??crit : Package: kdebase-bin Version: 3.5.2-2+b1 Severity: important File: /etc/pam.d/kscreensaver I didn't make this change, so I should not be prompted about it. I couldn't reproduce it, though, so I'm not filing it as bug.. Preparing to replace kdebase-bin 4:3.5.2-1 (using .../kdebase-bin_4%3a3.5.2-2+b1_i386.deb) ... Unpacking replacement kdebase-bin ... [...] Setting up kdebase-bin (3.5.2-2+b1) ... Installing new version of config file /etc/pam.d/kcheckpass ... Configuration file `/etc/pam.d/kscreensaver' == File on system created by you or by a script. == File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : background this process to examine the situation The default action is to keep your current version. *** kscreensaver (Y/I/N/O/D/Z) [default=N] ? D we use classical conffiles here, so the bug is in dpkg, not kdebase-bin. also notice that you didn't Cc-ed [EMAIL PROTECTED], so your bug won't be submit to the BTS. As noted, I don't intend to submit a bug, since I cannot reproduce it. but please bug dpkg/apt here, we are not responsible of that problem. Is it reproducible for someone else? (If so, it is a dpkg problem). Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kscreensaver: conffile prompt during testing update
On Fri, May 19, 2006 at 11:14:27AM -0400, Christopher Martin wrote: There is nothing we can do to control whether the user is prompted or not. In this case, the reason you were prompted (despite not having manually altered the file) is probably because the file in question was accidentally dropped from the packages some time ago, and only re-added with the last upload. Thus the conffile updating mechanisms had no record of an original file to compare against the new one, and therefore no way to determine whether or not you'd updated the file manually, so it erred on the side of caution and prompted you before replacing it. In short, it was not a bug, but a sign of a bug being fixed. It shouldn't happen again. Ah, thanks for the explanation. The source of the problem, then, is that: . the conffile got dropped at some point; and, . when the conffile got restored, it had different content; actually, this happens even if the version at which the conffile content changed isn't exactly the version at which it was restored; if the buggy package not own the conffile was installed (and the conffile was [deliberately] not removed by dpkg or the admin), and then the new package (including a new conffile) is installed You can actually avoid the conffile prompt, though it may not be worth it since I think that think doesn't affect stable upgrades (dpkg, by definition handles conffile content changes gracefully, and automatically, as long as the package owning the conffile doesn't change [during the same upgrade as the content of the conffile changes]). Just make the preinstall script remove the file if: 1 it is an upgrade (and not a fresh install), from an affected version 2 the file exists 3 the md5sum of the file matches that stored in the dpkg status database, 4 the md5sum of the file matches (one of) the expected md5sum(s) from the affected version(s) 2 is unnecessary if you use rm -f, and 4 is not strictly necessary, but the world is a better place when there are more conditionals around a noninteractive rm. Justin On Friday 19 May 2006 09:33, Justin Pryzby wrote: Package: kdebase-bin Version: 3.5.2-2+b1 Severity: important File: /etc/pam.d/kscreensaver I didn't make this change, so I should not be prompted about it. I couldn't reproduce it, though, so I'm not filing it as bug.. Preparing to replace kdebase-bin 4:3.5.2-1 (using .../kdebase-bin_4%3a3.5.2-2+b1_i386.deb) ... Unpacking replacement kdebase-bin ... [...] Setting up kdebase-bin (3.5.2-2+b1) ... Installing new version of config file /etc/pam.d/kcheckpass ... Configuration file `/etc/pam.d/kscreensaver' == File on system created by you or by a script. == File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : background this process to examine the situation The default action is to keep your current version. *** kscreensaver (Y/I/N/O/D/Z) [default=N] ? D --- /etc/pam.d/kscreensaver 2004-04-11 14:46:01.0 -0400 +++ /etc/pam.d/kscreensaver.dpkg-new2006-05-06 21:18:35.0 -0400 @@ -1,10 +1,6 @@ # # /etc/pam.d/kscreensaver - specify the PAM behaviour of kscreensaver # - -# The standard Unix authentication modules, used with -# NIS (man nsswitch) as well as normal /etc/passwd and -# /etc/shadow entries. @include common-auth @include common-account @include common-password -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kscreensaver: conffile prompt during testing update
On Fri, May 19, 2006 at 06:27:53PM +0200, Pierre Habouzit wrote: Le Ven 19 Mai 2006 18:06, Justin Pryzby a ??crit : You can actually avoid the conffile prompt, though it may not be worth it since I think that think doesn't affect stable upgrades (dpkg, by definition handles conffile content changes gracefully, and automatically, as long as the package owning the conffile doesn't change [during the same upgrade as the content of the conffile changes]). Just make the preinstall script remove the file if: 1 it is an upgrade (and not a fresh install), from an affected version 2 the file exists 3 the md5sum of the file matches that stored in the dpkg status database, 4 the md5sum of the file matches (one of) the expected md5sum(s) from the affected version(s) 2 is unnecessary if you use rm -f, and 4 is not strictly necessary, but the world is a better place when there are more conditionals around a noninteractive rm. the real fix would be that dpkg includes ucf and uses automatically to deal with conffiles. because here, the old config file would have been present in the md5sum database, and upgrade would just have worked. if you want to militate for the integration of ucf into dpkg, just know that I'll second you. honnestly, here, dealing with the upgrade is more painful that the problem it solves, and I wouldn't even bother fixing it. I was actually wrong; item 3 on my list is not possible, since dpkg will not know anything about the file. So one must do 4, and not 3. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348437: kdm auto-login causes keyboard failure
Package: kdm Version: 3.4.3-3 This is already reported by a few hundred people on google. Problem: Box is set to autologin with KDM, after I am logged in, the keyboard either does not work or does weird things like auto-repeats etc. Using GDM fixes the problem as GDM does not appear to have the same bug. This occurs on two separate machines reported by users on google/mailing lists/etc-- many people have the issue, it appears it has not been fixed in Debian Etch yet :( Using: Debian Etch I am using Linux box 2.6.15.1 #2 SMP PREEMPT Mon Jan 16 17:43:05 EST 2006 i686 GNU/Linux and libc-2.3.5 Thanks! Justin. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319808: kmail: misuses man section sh
Package: kmail Severity: minor These four man pages: /usr/share/man/sh/man1/kmail_antivir.1.gz /usr/share/man/sh/man1/kmail_clamav.1.gz /usr/share/man/sh/man1/kmail_fprot.1.gz /usr/share/man/sh/man1/kmail_sav.1.gz ...are apparently filed under /sh/ because they're documenting shell scripts. But as far as the FHS is concerned, /usr/share/man/sh is an obsolete code for man pages in Serbocroat; and for non-localised documentation, Debian Policy mandates You should only use sections 1 to 9. -- System Information: Debian Release: 3.1 Architecture: i386 (i586) Kernel: Linux 2.6.11.hurakan Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- JBR Ankh kak! (Ancient Egyptian blessing) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
election results - Rolex or Cartier or Breitling
Get the Finest Rolex Watch Replica ! We only sell premium watches. There's no battery in these replicas just like the real ones since they charge themselves as you move. The second hand moves JUST like the real ones, too. These original watches sell in stores for thousands of dollars. We sell them for much less. - Replicated to the Smallest Detail - 98% Perfectly Accurate Markings - Signature Green Sticker w/ Serial Number on Watch Back - Magnified Quickset Date - Includes all Proper Markings http://www.chooseyourwatch4u.net/ you charismatic me camelopard me [2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#301127: kaboodle dies with sigsev or so when trying to play an mpeg
On Wed, Mar 23, 2005 at 10:39:16PM +0100, Dirk Salva wrote: Package: kaboodle Version: 4:3.3.1-2 Severity: grave Justification: renders package unusable When I start trying to view an mpeg or something else (like from leech.dk), kaboodle only starts, but does not play. When I push play-button, it breaks with a sigsev (KDE-crash-notifier) or so. Under 32bit sarge the same video-file works fine. Asus A8V Deluxe, NVidia 6600GT, 1GB RAM. Can you run it under GDB and see if the backtrace is usable? $ gdb kaboodle run bt Can someone test this on a 64 bit architecture other than amd64? This is sarge-ignore if the other 64 bit archs work. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#290547: libarts1: Troubled system-sound with KDE 3.3.1 on testing
On Fri, Jan 14, 2005 at 07:15:25PM +0100, Dirk Salva wrote: Package: libarts1 Version: 1.3.2-1 Severity: grave Justification: renders package unusable [...] And, another one: with the new KDE system hangs completely about 3 times! It hangs so awesome that there was no remote-login via ssh possible. Steps to reproduce? What were you doing at the time? Can you confirm that ssh worked immediately before KDE hung the system? Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#286373: Missing manpages: keditbookmarks, kfmclient, konqueror
Package: konqueror Version: 4:3.2.2-1 Severity: minor Missing manpages: keditbookmarks, kfmclient, konqueror -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (101, 'testing'), (99, 'unstable'), (9, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.9-rc1 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) snip
Bug#231529: X-Window-System can't be started with kernel 2.6.0
(**) Generic Mouse: Protocol: ImPS/2 (**) Option SendCoreEvents true (**) Generic Mouse: always reports core events (**) Option Device /dev/input/mice (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device Generic Mouse (II) UnloadModule: mouse (WW) No core pointer registered No core pointer Fatal server error: failed to initialize core devices When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] //*** schnapp * Greetings, Georg Colle. Heya, This problem appears to be that the mousedev module is not loaded automatically. This will then create this /dev/input/mice for you. After that XFree should load up without problems. So the problem really isn't with XFree itself, but the modules that get loaded with the new kernel. Hope this helps, Justin T
