Bug#240188: Package dependencies violate policy
On Thu, Mar 25, 2004 at 09:29:28PM -0800, Stephen Zander wrote: > > "Chris" == Chris Cheney <[EMAIL PROTECTED]> writes: > Chris> Technically nothing really needs to depend on > Chris> xlibs-static-pic at runtime, but at the same time anything > Chris> that builds against anything it provides must Build-Depend > Chris> on it otherwise they won't work on hardly any of the archs > Chris> in Debian. Making libarts1-dev extra isn't really a good > Chris> idea but not depending on xlibs-static-pic means that all > Chris> KDE sources will have to add explicit build depends on > Chris> xlibs-static-pic. Perhaps just changing xlibs-static-pic to > Chris> optional would be the best solution? > > If you can get Branden to go along, then go ahead. However, I don't > understand the downside of changing the priority of libarts-dev. The > policy section I quoted explicitly permits Build-Depends against lower > priority packages. What concerns you about haing libarts-dev be > Priority: extra? I suppose you didn't look at the domino effect making libarts1-dev extra would have. Chris signature.asc Description: Digital signature
Bug#240188: Package dependencies violate policy
> "Chris" == Chris Cheney <[EMAIL PROTECTED]> writes: Chris> Technically nothing really needs to depend on Chris> xlibs-static-pic at runtime, but at the same time anything Chris> that builds against anything it provides must Build-Depend Chris> on it otherwise they won't work on hardly any of the archs Chris> in Debian. Making libarts1-dev extra isn't really a good Chris> idea but not depending on xlibs-static-pic means that all Chris> KDE sources will have to add explicit build depends on Chris> xlibs-static-pic. Perhaps just changing xlibs-static-pic to Chris> optional would be the best solution? If you can get Branden to go along, then go ahead. However, I don't understand the downside of changing the priority of libarts-dev. The policy section I quoted explicitly permits Build-Depends against lower priority packages. What concerns you about haing libarts-dev be Priority: extra? -- Stephen "It's like crazy gluing your nostrils shut to quit cocaine" -- Bill Mahl, on stomach stapling as a weight control method
Bug#240188: Package dependencies violate policy
On Thu, Mar 25, 2004 at 06:53:50PM -0800, Stephen Zander wrote: > Package: libarts1-dev > Version: 1.2.1-2 > Severity: serious > > Section 2.5 says: > > Packages must not depend on packages with lower priority values (excluding > build-time dependencies). > > libarts1-dev violates this by being Priority: optional and depending on > xlibs-stat-pic, which is Priority: extra Technically nothing really needs to depend on xlibs-static-pic at runtime, but at the same time anything that builds against anything it provides must Build-Depend on it otherwise they won't work on hardly any of the archs in Debian. Making libarts1-dev extra isn't really a good idea but not depending on xlibs-static-pic means that all KDE sources will have to add explicit build depends on xlibs-static-pic. Perhaps just changing xlibs-static-pic to optional would be the best solution? Chris signature.asc Description: Digital signature
Bug#240188: Package dependencies violate policy
Package: libarts1-dev Version: 1.2.1-2 Severity: serious Section 2.5 says: Packages must not depend on packages with lower priority values (excluding build-time dependencies). libarts1-dev violates this by being Priority: optional and depending on xlibs-stat-pic, which is Priority: extra -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.20-evms Locale: LANG=C, LC_CTYPE=C
Processed: kde-extras (main) Recommends ksetisaver (contrib)
Processing commands for [EMAIL PROTECTED]: > severity 227839 serious Bug#227839: kde-extras (main) Recommends ksetisaver (contrib) Severity set to `serious'. > tags 227839 + wontfix Bug#227839: kde-extras (main) Recommends ksetisaver (contrib) Tags were: patch Tags added: wontfix > tags 227839 - patch Bug#227839: kde-extras (main) Recommends ksetisaver (contrib) Tags were: wontfix patch Tags removed: patch > tags 227839 + sarge Bug#227839: kde-extras (main) Recommends ksetisaver (contrib) Tags were: wontfix Tags added: sarge > tags 227839 + sid Bug#227839: kde-extras (main) Recommends ksetisaver (contrib) Tags were: sarge wontfix Tags added: sid > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#240128: konqueror: When a tab is closed, new selected tab should be the previous tag, not the next one
Package: konqueror Version: 3.2.1-1 Severity: wishlist At least when the the "Open new tab after current tab" option is enabled, if a tab is closed then the previous tab should be displayed, not the next one. That is, if I am browsing a site with, say, related links or expanded images that each open in a new window, then when I click one it will appear in the next tab and will get the focus. I then want to close the new tab and return to the previous site to click a new link. However, when I close the tab, the previous site's tab does not get the focus if there is another tab after it. So, if I want to follow several different pop-up links, I have to close the tab and then change tabs every time. This behavior is very tiresome if you have to do it frequently. Example: My browser is open with two tabs. Tab 1 is memepool.com and Tab 2 is google.com. I click a link on memepool as "Open in a new tab". Read the site, close the tab, I'm looking at google. Change tabs, open another memepool link. Read the site, close the tab, I'm looking at google. Repeat ad nauseum.
Bug#240108: kghostview: Often does not open PDF with the "Zoom In" tool enabled
Package: kghostview Version: 4:3.2.1-1 Severity: minor As in the subject, often the application opens a local PDF file leaving some tools disabled -in particular the "zoom in" tool: see the attached piece of snapshot. Reloading the file enables the control. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages kghostview depends on: ii gs 7.07-1 The Ghostscript Postscript interpr ii gs-esp [gs] 7.07.1-4 The Ghostscript Postscript interpr 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 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 xlibs 4.3.0-7 X Window System client libraries m ii zlib1g 1:1.2.1-5compression library - runtime -- no debconf information snapshot1.png Description: PNG image
kdenonbeta/kdedebian/kapture
CVS commit by mornfall: fix the breakage from last commit, ie: compile! M +1 -1 libcapture/pkgcache-test.cpp 1.10 M +12 -30libcapture/pkgcache.cpp 1.10 M +3 -3 libcapture/pkgcache.h 1.11 M +2 -3 libkapture/pkgnodeview.cpp 1.7
Bug#240053: kpdf: KPDF renders some images upside down.
Package: kpdf Version: 4:3.2.1-1 Severity: normal Kpdf renders some images upside down, such as those in the backgrounds of pages 3- of the document at: http://www.deh.gov.au/atmosphere/airquality/lead/pubs/leadpaint.pdf GPDF, XPDF and Ghostscript do not have this problem (although ghostscript gets confused about page orientation). -- System Information: Debian Release: testing/unstable Architecture: i386 (i686) Kernel: Linux 2.6.3 Locale: LANG=en_AU, LC_CTYPE=en_AU Versions of packages kpdf 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 libfreetype62.1.7-2 FreeType 2 font engine, shared lib ii libgcc1 1:3.3.3-4GCC support library ii libice6 4.3.0-7 Inter-Client Exchange library ii libpaper1 1.1.14 Library for handling paper charact 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 xlibs 4.3.0-7 X Window System client libraries m ii zlib1g 1:1.2.1-5compression library - runtime -- no debconf information
Processed: Re: Bug#239607: can't open the search dialog
Processing commands for [EMAIL PROTECTED]: > severity 239607 wishlist Bug#239607: can't open the search dialog Severity set to `wishlist'. > forwarded 239607 http://bugs.kde.org/show_bug.cgi?id=72347 Bug#239607: can't open the search dialog Noted your statement that Bug has been forwarded to http://bugs.kde.org/show_bug.cgi?id=72347. > forwarded 194419 http://bugs.kde.org/show_bug.cgi?id=7506 Bug#194419: kghostview: pdf files in landscape format aren't correctly displayed Noted your statement that Bug has been forwarded to http://bugs.kde.org/show_bug.cgi?id=7506. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
kdenonbeta/kdedebian/kapture/libcapture
CVS commit by mornfall: - remove loads of obsolete code - make it a bit more readable (ie clean up a bit - add madison-lite to pkgcache-test as it should manifest the libdigest-md5-perl problem (which it does not, i guess it's because of the delay optimization; i'm however not sure whether this 100% solves the problem, so it needs some testing or even reasoning why it did (not) solve it) M +2 -0 pkgcache-test.cpp 1.9 M +0 -198pkgcache.cpp 1.9 M +39 -43pkgcache.h 1.10
Re: kwin does not provide window manager?
On Tuesday 23 March 2004 09:28 am, Dominique Devriese wrote: > I think this is a valid question. Is kwin usable without the rest of > kde ? If so, we should tell update-alternatives that it's an > alternative for x-window-manager. If I am just doing some stuff quickly and just need terminals and screen space I run 'xinit' then 'kwin&' kwin is very usable as just a Window manager. Including it in update alternatives would rock. :) -- Samir M. Nassar http://steamedpenguin.com/ You won't be able to email me using the address I use to post. Use the alias sp same domain to send mail.
Bug#240027: kdm: KDM does not start correctly on boot
Package: kdm Version: 4:3.2.1-1 Severity: normal Tags: sid The system comes up normally. The kdm init script says "Starting K Desktop Manager: kdm", but KDM does not come up. At this point, a remote login reveals that there are 2 kdm processes running. Output of "ps ax": 1133 ?S 0:00 /usr/bin/kdm 1134 ?S 0:00 /usr/bin/kdm_config A manual "/etc/init.d/kdm restart" results in Stopping K Desktop Manager: kdm not responding to TERM signal (pid 1133). Starting K Desktop Manager: kdm. After that, KDM is still "locked", except there is now another pair of kdm processes running. I have tried the whole procedure with XDMCP enabled, and was unable to get a remote login window. The kdm.log file does not offer any information. The strange part: If i log in as "root" (or sometimes as user) locally on the console, KDM starts up after some seconds! Now, everything works correctly. I have already tried out different graphics drivers, with no success. Also, other display managers (gdm) do not have this problem. There are some peculiarities about the affected computer: It is relatively new and equipped with ill-supported hardware like SATA controller. For that reason, i am running kernel 2.6.5-rc2. Also, since the SATA drive locks up frequently, i set up he system to boot from an nfs root via DHCP... I would be surprised if this nfs root method was the cause of the kdm problem,because i did not see any other problems. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.5-rc2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] Versions of packages kdm depends on: ii debconf 1.4.17 Debian configuration management sy ii kdebase-bin 4:3.2.1-1KDE Base (binaries) 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-5GCC support library ii libice6 4.3.0-7 Inter-Client Exchange library ii libpam-runtime 0.76-16 Runtime support for the PAM librar ii libpam0g0.76-16 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-5The 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 xbase-clients 4.3.0-7 miscellaneous X clients ii xlibs 4.3.0-7 X Window System client libraries m ii zlib1g 1:1.2.1-5compression library - runtime -- debconf information: kdm/stop_running_server_with_children: false * shared/default-x-display-manager: kdm kdm/daemon_name: /usr/bin/kdm
Bug#240015: Undeclared conflict with juk
On Thu, Mar 25, 2004 at 12:43:48PM +0100, Noèl Köthe wrote: > reassign 240015 juk This is a problem for both packages. > You have an outdated version of juk. juk 3.2.1 is uploaded but right now > is only available for i386: > You have to wait until juk is available for ppc in version 3.2.x. > Only kde-i18n should have languages/translations of packages released by > kde. In that case you ought to do something to ensure that the system won't try to install the new kde-i18n-engb on top of an old version of juk. I'd guess that given that the files were moved out of juk you'd want to conflict with old versions of it. -- "You grabbed my hand and we fell into it, like a daydream - or a fever."
Processed: Re: Bug#239918: kopete: no irc /ignore command
Processing commands for [EMAIL PROTECTED]: > package kopete Ignoring bugs not assigned to: kopete > tags 239918 +upstream Bug#239918: kopete: no irc /ignore command Tags were: upstream Tags added: upstream > forwarded 239918 http://bugs.kde.org/show_bug.cgi?id=64163 Bug#239918: kopete: no irc /ignore command Forwarded-to-address changed from http://bugs.kde.org/show_bug.cgi?id=64163 to http://bugs.kde.org/show_bug.cgi?id=64163. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#239918: kopete: no irc /ignore command
Paul Johnson writes: > Alejandro Exojo <[EMAIL PROTECTED]> writes: >> As a tip: fill your wishlist in bugs.kde.org. KDE developers are >> very quick in adding new features, but if you fill them in debian >> BTS, you will only make debian mantainer's work harder, because >> they need to do this work for you. ;-) > Understood. However, my understanding of the BTS is that it exists > because the Debian developers probably have better karma with the > upstream developers and know how to communicate effectively with > them. It's also my understanding that maintainers act as liasons > between the userbase and upstream. This may be true, but the Debian developers are also overloaded with upstream bugs, and as a result, upstream bugs often don't get forwarded at all. Furthermore the KDE people are very good at handling bugs themselves, so our help is not really necessary. cheers domi
