libqt2 libpng2 resolution
I think that the best solution to the problem would be for me to upload a new version of libqt2 2.3.1 compiled against libpng2. Due to the potential problems with upgrading from stable (potato) to the future new stable (woody). I will do this tomorrow morning. After I upload the new version of libqt2 packages will probably need to depend on that version and libpng2-dev and be rebuilt, at least for the current ones that are built against libpng3. I hope that eventually this sort of problem will not be an issue due to symbols being overridden. Is there some way to fix this from being an issue in the future? This is very big and annoying problem that probably affects other packages, even more than just libqt/imlib. If anyone has any further comments please feel free to let me know. Please direct all flames to Overfiend ;) Chris Cheney pgpufILn4qlSg.pgp Description: PGP signature
Re: libqt2 libpng2 resolution
On Mon, Jan 07, 2002 at 06:56:48AM +, John Gay wrote: > So, if I understand you correctly, you are going to revert qt back to the > old libpng2 rather than keep it at the new one, which Daniel is planning to > re-compile the rest of kde to? Yes, I am sponsoring Daniel so I will be compiling kde after I finish with libqt2. > This is just a temperary measure to fix the current majorly broken state of > KDE for the moment, right? Temporary as in libqt3 will be using libpng3, yes. I see little point in using libpng3 with libqt2 especially since it might break upgrades from potato. > Are you and Daniel planning to re-compile everything against the new > libpng and upload it in one go afterwards to reduce the headaches for those > of us tracking unstable and testing together? No. It will be reverted to libpng2. > At the moment, I've only got problems with kmail missing icons. konq has > its icon, unless I start it from the command line and I'm missing the KDE > splash screen when I log in. I have not checked the likes of kdevelop, > quata's+ or most of the rest of kde, because I haven't had much time and > ignorance is bliss : ). > I haven't done an update in a while, but I'm running testing with kde from > unstable, as that was more stable than testing. I'm just waiting until this > blows over and I can upgrade to a properly working kde. I've heard mixed > reports of some fixes but other breakages so I'm sitting on my hands to > keep from upgrading. Once I hear that the unstable kde is in good working > order again, I'll upgrade. Hopefully unstable kde will be working good within 10 days (time for buildds to catch up). > Thanks for picking up the pieces after Ivan had to drop kde. Several of us > were afraid we would have to wait through another version of Debian before > seeing kde in a stable branch. I am going to do my best to make sure KDE stays in Woody, I use it myself every day. > > Cheers, > > John Gay pgpMZ16Yngm7J.pgp Description: PGP signature
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
On Mon, Jan 07, 2002 at 05:06:27AM -0800, Philippe Troin wrote: -snip- > > Sounds good to fix all the current problems... however how are we > going to handle the libpng2 -> libpng3 conversion ? Your solution just > seems to postpone the problem. libqt 3.x already uses libpng3 so that looks like a good conversion spot. Chris
Re: libqt2 libpng2 resolution
After talking to one of the buildd guys I think the estimate will probably be bumped out to about 14 days, due to the time to build some of the key packages. Chris On Mon, Jan 07, 2002 at 10:07:48AM +, John Gay wrote: > On Monday 07 January 2002 07:22, Chris Cheney wrote: > > Hopefully unstable kde will be working good within 10 days (time for > > buildds to catch up). > > Thanks for the estimate! I'll be sure to hold you to that : ) > > And thanks for the detailed explanation of where you and Daniel are going > from here! At least we have something to look forward to and a time-frame to > watch as it flies by ; ) > > Cheers, > > John Gay > > "I love deadlines! I especially like the 'ZOOMing' sound they make as > thay fly by!" > > Douglas N. Adams > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > pgpn1KTnLVvWO.pgp Description: PGP signature
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
On Mon, Jan 07, 2002 at 10:07:23AM -0800, Philippe Troin wrote: -snip- > > Sounds good to me. > > How do you plan to prevent programs that link with libqt2 to also link > with libpng3 ? Manual check ? yes manual check pgp3Az1eSA42r.pgp Description: PGP signature
Re: libqt just broke again
On Mon, Jan 07, 2002 at 08:37:01PM -0500, James D. Freels wrote: > This evening, I upgraded my Debian/Sid system via apt-get, and > several packages were installed. Among them were several kde/qt > packages as listed below to -19.deb version and the icons were > not visible on the desktop (broken as before). Yep, that is a known side effect of going back to libpng2. Chris
Re: Lord, Love-A-Duck! My Icons are back!
On Mon, Jan 07, 2002 at 10:23:23PM -0500, John S. J. Anderson wrote: > So, is there any way to speed one's way back to a functional KDE? > Doesn't seem like 'apt-get -b source kde' is likely to work; can > anyone provide a list of packages that need to be rebuilt? This is probably more complicated than it needs to be, but I don't know how to use all the tools really well: apt-cache showpkg libpng3 | grep libpng3 - | cut -f 1 -d "," | xargs apt-cache show | grep Source: | sort | uniq That lists all sources that depend on libpng3 not all of which will need to rebuilt. Chris
Re: libqt just broke again
On Tue, Jan 08, 2002 at 10:49:53AM -0500, James D. Freels wrote: -snip- > What is the proper thing to do until these issues get fixed? What I did > before was create my own set of debs by building qt-x11 (that is where the > -18.deb files came from). I am currently building my own set of debs again > for the -19 version. I understand we have a mixture of kde packages that > depend on both png2 and png3. Are we eventually going to have only png2 > dependency for kde2 and png3 for kde3? Is that the plan? In the meantime, > shouldn't we have only libpng2 dependency in the Sid tree for kde2 ? Yes, libpng2 will be used for qt-x11 (libqt2) and libpng3 will be used for qt-x11-free (libqt3). qt-x11 (libqt2) was installed into sid yesterday, kdelibs will be installed today, and kdebase will be installed tomorrow. After that I will be building all remaining packages. Each of those first three packages are known to take ~ 40+ hours on m68k to compile. The packages should be ready to be installed into woody within 12 days, if all other RC bugs are resolved. Chris
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Wed, Jan 09, 2002 at 07:50:48AM +1100, Daniel Stone wrote: > On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: > > > It will be quite important as an interface option in KDE3, but I think > > > > Great! Now that we are on it, btw, do you know: > > > > + How smoothly does the CVS version of KDE 3 beta coexist on the same > >computer with current 2.2 debian packages? I would very much like > >to test it already but haven't dared to install yet in the fear > >of making the currently fine working 2.2 unusable.. > > I'm not sure that it does, at all. Chris? I am still working with you on KDE 2.2 (remember) ;) > > + Have they announced any estimated schedule for KDE3 release on > >KDE mailing lists? Ie. about when can we expect official Debian > >packages to appear in 'unstable?' > > "When it's ready". Bear in mind, however, that KDE has the fastest > release team/whatever known to man. Yea, I will have to start looking at the packaging of KDE3 ASAP. > > > these three words sum up its state in KDE2.2: "buggy as shit". I don't > > > intend to support something that is indeed buggy as shit. Live with the > > > odd jagged pixel. > > > > :) If you say so.. > > Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) Sound like a plan to me. ;) Chris Cheney
Re: [kde] and, for my next trick ...
On Thu, Jan 10, 2002 at 09:08:56PM +, John Gay wrote:
> On Thursday 10 January 2002 06:17, Daniel Stone wrote:
> > The libpng[23] screwup in unstable is now more or less resolved with
> > kde{base,graphics,network} in incoming. Now, the only packages that need
> > rebuilding are kdeaddons, kinkatta, kmerlin, koffice, and maybe kdetoys
> > (not sure on that one - Ben?). kdelibs was installed last night.
> >
> That was a quick 10-14 days ; )
It was 10-14 days for Woody, if no RC bugs block it.
> As with everyone else, I'll be waiting for everything to hit the unstable
> mirrors so I can upgrade in peace!
>
> Thanks for the quick work! You and Chris are a credit to Debian! Keep up the
> great work!
Thanks :)
> Cheers,
>
> John Gay
Re: kde.debian.net website
On Thu, Jan 10, 2002 at 05:20:12PM -0800, G. L. `Griz' Inabnit wrote: -snip- > The first thing that comes to mind is a list of sites where the .deb archives > are kept at. Currently in "the archive" soon there will be kde3 debs at http://people.debian.org/~ccheney/ > And this is NOT just for .deb(ian) We also need to support apt-rpm if > we can. > I'd like to see some archives for the (don't scream at me!!) apt-rpm sites > too. I don't 'like' RedHate, but with the new apt that is in it, it sure > would be sweet if we could support it. (convert those fadora wearin' > strangers!) How would supporting RedHat help convert them to Debian? :) Isn't KDE already in RedHat anyway? If RedHat wants to use apt-rpm then they are free to setup their own mirrors to use with it. Chris
Re: KDE dependency problem on a Debian Sid 3.0
On Fri, Jan 11, 2002 at 09:58:26AM +0100, [EMAIL PROTECTED] wrote: > Hello !! > > I have a little dependency problem on Debian GNU/Linux Sid 3.0 (yes, I know, > that's unstable...) : -snip- > Sorry, but the following packages have unmet dependencies: > kde: Depends: kpackage but it is not going to be installed > E: Sorry, broken packages I will get Daniels to give me an updated diff.gz and try to rebuild it asap. My system decided to eat its hard drive last night though so it might be a few days. :< Chris Cheney
Re: kde not starting as normal user
On Wed, Jan 16, 2002 at 12:13:06AM +0100, Jens Benecke wrote: -snip- > Why install a kernel module? install apmd, set your BIOS to DELAY-4-SEC and > set up a "suspend" event that calls shutdown in /etc/apm/events.d. :) or use acpid :)
Re: Interpreting FHS
On Thu, Jan 17, 2002 at 02:48:06AM +0200, Jarno Elonen wrote: -snip- > If there were a way to remove symlinks when the original file is removed, > I think the following structure would be the easiest to understand and > administrate: > > + usr > + bin > + qtcups -> ../qtcups/bin/qtcups > + nano -> ../nano/bin/nano > + sbin > + traceroute -> ../traceroute/bin/traceroute > + qtcups > + etc (conf) > + share (data) > + bin (binaries) > + doc (man, info) > + nano > + etc > + bin > + doc > + traceroute > + etc > + bin > + doc If it was structured like this then besides the other issues mentioned wrt libs, you could have up to ~ 8500 subdirs in /usr, not particularly good. 8) Chris Cheney
Re: Summary of KDE filesystem discussion
On Wed, Jan 16, 2002 at 11:51:44PM +, Julian Gilbey wrote: -snip- > > * Some proposed using /opt/kde3. Arguments: > > Not as a Debian package. /opt is for third-party software. > >Julian perhaps you should have read the rest of the email from him... :)
Re: KDE filesystem structure
On Wed, Jan 16, 2002 at 04:55:17PM +0100, Hendrik Naumann wrote: -snip- > - From an sysadmin point of view it is realy nice to have MOST of the > programms and the mayority of diskspace under /usr. I think many > networks are planed that way. Shure one could just link /opt to > /usr/opt and everything work, but then lets just start with > /usr/opt. I don't know if this is the case on all commerical *nix but /opt is typically bigger than /usr on them, and on the machines I admin is much larger. So I guess the many networks planned that way (large /usr) are all Linux networks? /usr/opt isn't defined in FHS so would probably not be a good idea. Chris
Re: Interpreting FHS
On Wed, Jan 16, 2002 at 07:40:26PM -0600, Ron Johnson wrote: > Call me crazy, but I've always thought that soft symlinks could be great here: > - Put each package in it's own subdir under, say, /pkg. > - Next, put symlinks into /usr/bin, /usr/lib, /etc, ad nauseum, in order to > follow the Debian Policy. > > This way, you could have /pkg/qt2, /pkg/qt3, /pkg/kde2, etc... Maybe it's > the DOS mentality of 1 subdir per program, but I think this makes things very > organized. > > What's this about only 8500 sub-dirs in /usr? The way he wrote the email/diagram he was putting each package under /usr/packagename. Chris
Re: KDE Packagers - What's the plan/roadmap/future & timescale?
On Mon, Jan 28, 2002 at 03:52:47PM -0800, tluxt wrote: > Hi, > > Sorry if this request implies you must recapitulate anything, > but after considering the alternatives, this seemed the better option. > > I know there was a scramble to take on packages & quickly find a solution > to the image/icon problem when Ivan released the packages he was maintaining. > > Now that that issue seems to be largely past, I would > appreciate it if you both would take a moment and answer a few questions, > involving things such as: > > 1) Who you are, what you do in real life, how you got involved in Debian, > and involved in KDE, what (if anything) you packaged in Debian before this, > what (if anything) you did in KDE before this, why & how you came to the > decision to take on maintainership of the KDE packages. I have been a Debian user since around Aug 1998, and have been a maintainer since July 2000 (I was stuck in the closed NM queue for a while). I currently have 19 source packages, 18 of which are not KDE related. Once I upload the all of the KDE packages I think I will have around 42. I decided to maintain the KDE packages because I use it every day and didn't want to see the packages deteriorate. > 2) What do you see as the time frame for upcomming Debian/KDE milestones? > Such as: > > A) What is the plan/roadmap/future for KDE related things in Debian? > the metapackage (or, what is it called now? Task?) of kde vs of kdebase. My plan is to examine all of KDE 2.2.2, which I am currently doing. Then I will upload a final set of packages so that they can make it into Woody. Then I will start preparing KDE 3 debs and will host them on p.d.o/~ccheney/ until KDE 3 is released or Woody is frozen whichever happens first. > B) What's up w/ KOffice for Debian? Re: Woody or Sid? I don't know anything about KOffice. > C) What's your recommendation regarding: would you advise people who want > to be making productive use of KDE now to run Woody or Sid? Well I thought that fixed KDE 2.2.2 would be in woody by now but it appears that m68k is holding up kdebase for a build deps (seems odd). I will try to get it in as soon as possible though. Sid should be fine if you want to run that. > D) What's up w/ KDE 3? - When, and for whom, should persons trying to make > actual daily use of KDE begin to use KDE3? Can KDE2 & KDE3 be put onto > the same system, and switched between? Is it necessary to do a complete > separate Debian install, (one for KDE2 & one for KDE3) on the harddisk > if one wants to be able to try switch between 2 & 3? KDE 3 is still a bit buggy from what I hear, I haven't actually built debs for it yet since I am still working on the 2.2.2. I would imagine that I will have good working debs by the time it is officially released (hopefully sooner). KDE2 and KDE3 can not be installed at the same time without some work, and I will not be supporting both of them being installed at the same time. I am not going to have both in the archive at the same time since it would take an enormous amount of space, if I remember correctly someone said KDE currently takes approximately 2.5GB of archive space now (between all the archs and woody/sid). > I ask these questions since I'd like to make some judgements about what to > put in the KDE HowTo I'm developing. For instance, I'd like to have good > data to base a decision on regarding: should I suggest, (and write it from > the perspective of) persons run Woody, and if necessary pull packages from > Sid? Or, is & will Sid be basically enough free of substantial problems > that it would be better for most people trying to do productive work with > KDE that they run Sid, in order to have the latest features? currently you probably still need to run Sid, but hopefully this situation will change soon. > (For instance, two areas I'm currently possibly affected by are: > 1) Kghostview - does the Sid version fix a major problem? I hope to address this issue in my next upload. > 2) kde vs kdebase - does Sid have a kde package that provides > many more features (& thus involves much less sw installation time/effort) > than Woody?) sid has the KDE meta packages which I don't think are in woody yet? The meta packages make it much easier to install KDE. > It would be much appreciated if you would each free up some of your > valueable time to each answer the above questions for all here who are > interested in the future of KDE on Debian! > > Thanks. :)
Re: KDE Packagers - What's the plan/roadmap/future & timescale?
On Mon, Jan 28, 2002 at 09:51:42PM -0600, Chris Cheney wrote: -snip- > > 1) Who you are, what you do in real life, how you got involved in Debian, > > and involved in KDE, what (if anything) you packaged in Debian before this, > > what (if anything) you did in KDE before this, why & how you came to the > > decision to take on maintainership of the KDE packages. I forgot to mention what I do outside of Debian. I am a Junior in Computer Science at Sam Houston State University in Huntsville, Texas. I also work as a Network Specialist at TXU Communications which is a telecommunications company (ILEC/CLEC/ISP). Thanks, Chris
Re: kdm error
On Tue, Jan 29, 2002 at 04:14:03PM -0800, Jason Majors wrote: -snip- > Sid as of 07:00 GMT Jan 29. The Xserver is 4.2.0 from > the prebuilt linux > i686 binaries at XFree86.org. The Xserver 4.2.0 libraries may be the reason it dies. -snip- > Jan 29 01:50:04 apocalypse kdm_config[1417]: Can't > write to core It looks like it segfaulted and couldn't write out the core file, for whatever reason. If you can get it to write the core file you can use gdb to determine why it segfaulted. Chris
Re: dpkg Weirdness
kde (meta) -> koffice (meta) -> kivio -> python2.1 maybe kivio in woody depends on python 1.5 ? Removing python2.1 on a sid system would require that kde, koffice, and kivio at minimum to be removed. Chris
Re: dpkg Weirdness
On Thu, Jan 31, 2002 at 03:42:55AM +, Nick wrote: > On Wed, 30 Jan 2002 19:58:30 -0600, Chris Cheney <[EMAIL PROTECTED]> > wrote: > > >kde (meta) -> koffice (meta) -> kivio -> python2.1 > > > >maybe kivio in woody depends on python 1.5 ? > > OK, thanks. I wasn't expecting KDE to depend on scripting language > packages. I forgot to mention that kde and koffice at least in sid are meta packages which means they don't really need to be installed, they just help you install of all the applications. Chris
Re: Would anyone here like an up to date KDE status page? (like perhaps kde.debian.net)
On Wed, Jan 30, 2002 at 08:32:43PM -0800, tluxt wrote: > Listing things such as the status of KDE for Woody & Sid, > the recommended packages to install for W&S (for instance, "kde" is > more comprehensive, but doesn't exist yet in W, therefore in W install > "kdebase"), the status for KDE3, etc? > > Please reply to this debian-kde@lists.debian.org list. I have something like this, but nearly as detailed at p.d.o/~ccheney/ basically it just tells what I am currently doing. It is heavily modeled after Branden's XSF page (see the source ;). A faq type page would probably be good to have also, if you want I can put it in my dir, or it can be setup elsewhere. Thanks, Chris
Re: Erroneous out of space msg & fs corruption on W>S then KDE install
On Thu, Jan 31, 2002 at 03:37:06AM -0800, tluxt wrote: > I then started KDE & web browsed, that worked fine. > I checked my df & had about 280MB free -snip- > > I then did > apt-get install kde > It said > 0 packages upgraded, 53 newly installed, 0 to remove and 19 not upgraded. > Need to get 17.0MB of archives. After unpacking 52.8MB will be used. > Do you want to continue? [Y/n] y > > I think this process had some problem I can't recall. > > I think I then continued again, > and here is where I got the error msg about being out of space, which > should not have occurred since the estimated size was well below the > available size. The 52.8MB used isn't the total actually required to complete the operation but I am not completely familiar with how dpkg installs packages. At a minimum you need the space for all the packages (the 53 debs) it downloads plus the space listed to install (52.8MB). I am not sure if you need double the space that the packages take unpacked or if dpkg just overwrites on install. I think that 280MB should have been enough free space though. 8) Chris
Re: libmysqlclient support in kdebase
On Thu, Jan 31, 2002 at 05:46:52PM +0100, Alex wrote: > As of samba 2.2.2-11 libmysqlclient is available in Debian, will it be > supported in kdebase in the next upload? (for de kio-smb ioslave) > > Alex Yes I will try to have it linked into kdebase. Chris
Re: Where is KwinTV? Again.
On Fri, Feb 01, 2002 at 11:04:36PM +, John Gay wrote: > I thought this was now an official part of kde multimedia? Who is building > the multimedia packages or are you looking for a volunteer? After my initial, As far as I can tell it is still part of kdenonbeta, I will take a look at it after getting the rest of kde cleaned up and if it works ok I will package it. Chris
Re: KDE-Debian HowTo for KDE2 & Debian3=Woody X86. Ver 0.18
On Sun, Feb 03, 2002 at 02:13:43AM -0800, tluxt wrote: > apt-get install aee ;Optional: Easy/simple editor for text mode display. > edit /etc/groups ;At end of the lpdamin line add the names of all > ;users you want to be able to modify printer configs. > ;Perhaps use "aee" editor. > /etc/init.d/cupsys restart;Restart the printer server w/ this command I believe you meant to edit /etc/group and the best way to do that is not by using a text editor. You should use adduser (user) (group). eg # adduser ccheney lpadmin Chris Cheney
Re: What is keeping 'kde' metapackage out of Woody?
On Sun, Feb 03, 2002 at 03:32:24PM -0800, tluxt wrote: > 1) What is package kde? I've heard of kde-base, and the 'kde' > metapackage, but not a 'regular' package called 'kde'. > 2) Is a bug of level 'important' able to keep a package out of W? 1) kde is a meta package that depends on other packages but does nothing itself. 2) no, see below. > So now we've found the kde metapackage info, and the most important bug is > 'important'. Is _that_ what is keeping the kde metapackage out of Woody? No, see below. > It takes a bug more severe than 'important' to keep a package out of > Woody, right? > [Can you give me a URL for where the description of what is > required for a package to get from S > W?] > Wrong? Does that mean an ugly font and problems with accented fonts is > keeping this very useful metapackage out of Woody? It takes a bug of severity serious or above to keep a package out of Woody unless the package's depends are not yet met. (There are few other small rules but they do not apply here.) See this url for more details: http://ftp-master.debian.org/testing/update_excuses.html > If so, that seems an awfully small problem holding up a package with major > benefits to installation efficiency, at least. That is _very_ bad, if > true. > > So, what, exaxtly, needs to be done to get the kde metapackage into Woody? > ? I am going to be putting meta packages into each source package for kde, so there will be for example a kdelibs package that depends on specific version of kdelibs3, kdelibs-bin, libarts, libarts-kde. That can then be depended on by the kde meta-package. This will keep kde for needing to change, and any time a new package is uploaded (like kdelibs) its meta package will automatically be updated as well. Does this sound good? Chris
Re: What is keeping 'kde' metapackage out of Woody?
On Mon, Feb 04, 2002 at 01:23:13AM -0800, tluxt wrote: -snip- > Um, ok, but why are there these two different pages? > These make it seem like there is both a package "kde", and > a package "meta-kde" that are different packages. > Do these two different URL, referring to both "package kde" > & "source meta-kde" refer to the same, or different things/packages?: The source is called meta-kde the packages that are built from it include a package called kde. > I guess the relevant item here is "meta-kde", right? Yes, all packages that are built from a source have to go into testing (woody) at the same time. > So, it's not the "important" level bug holding meta-kde up, > it's all those depends, right? > > Yow! That looks like a _lot_ of work needing to be done on meta-kde! > All those things have to go away before meta-kde can get into W, right? It isn't as bad as it looks, currently the reason it is being held out I believe is due to a bad NMU that was numbered as a source NMU instead of binary only NMU. With the next upload of the various packages that I do it should fix that problem. > Who does the work of getting all those packages built for all those > different processors? You? Someone who supports those other processors? > If you, when do you think you'll have all that work done? > > alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc > > Seriously: Is it _worth_ doing all that effort? We have buildd maintainers that partially automate the process of building the packages for all the various archs. The only requirement of the package maintainer is to insure that bugs keeping it from being built on the other archs are fixed. > If that is what Debian is, or has to have done for it, > perhaps it is time to fork Debian, and perhaps build for only > the 1,2 or at most 3 processors with the largest user base for > Debian users. > (Maybe i386 & whatever apple uses for their laptops (powerpc?) > and whatever the handhelds use (arm?).) > (How much effort is necessary, and how many potential users are gained, > by having to do builds for alpha, hppa, ia64, m68k, mips, mipsel, s390, > sparc?) > Or, at least only build KDE for those 1-3 processors. If someone else > wants to build a Debian Linux base for servers for all those processors, > that's fine. And, if they also want KDE for any of those platforms, > great, they should be free to use their time building them. Forking Debian would be much more work than just fixing a few packages, and most of the time the problem isn't because of the other archs. In this particular case I think the entire problem was due to a bad NMU. However not building KDE for m68k might be of some help. I am not going to do that though without asking the debian m68k group first. The issue with m68k isn't that they are slow to build, which sometimes is the case, but that it uses up a lot of buildd resources for arguably little benefit. I have turned on enable-final in my test packages, which I hope to upload soon, that will probably help reduce the time to build on all the archs. Chris
Re: What is keeping 'kde' metapackage out of Woody?
On Mon, Feb 04, 2002 at 11:02:27PM -0800, tluxt wrote: > Thanks for your info below. (See a few questions there.) > You missed this question at the very beginning of the message, :) > which refers to the subject of this message: > > Subject: What is keeping 'kde' metapackage out of Woody? > Q: And, where exactly in the Debian package system database web info pages > can this info be found? > [Perhaps you want to answer this question at a reasonable spot below.] See this and look at kdelibs: http://ftp-master.debian.org/testing/update_excuses.html summary: kdeadmin -> rpm -> doesn't build on m68k currently (will be fixed RSN) kdegraphics -> bad NMU kdelibs -> depends on glib1.3 (will be removed when I upload package) kdenetwork -> build failed on hppa (patch avail and will be applied) kdepim -> has RC bugs kdeutils -> bad NMU > --- Chris Cheney <[EMAIL PROTECTED]> wrote: > > On Mon, Feb 04, 2002 at 01:23:13AM -0800, tluxt wrote: > > > I guess the relevant item here is "meta-kde", right? > > > > Yes, all packages that are built from a source have to go into testing > > (woody) at the same time. > > > > Yow! That looks like a _lot_ of work needing to be done on meta-kde! > > > All those things have to go away before meta-kde can get into W, right? > > > > It isn't as bad as it looks, currently the reason it is being held out I > > believe is due to a bad NMU that was numbered as a source NMU instead of > > binary only NMU. With the next upload of the various packages that I do > > it should fix that problem. > > When do you think you will have that next upload done? Hopefully within this next week. There are some other changes I want to make along with fixing that issue. > What, very briefly, is the chain of reasoning from the above data > that leads you to your conclusion that "the reason it is being held out I > believe is due to a bad NMU"? > [I ask this so I can be informed how to trace such erros, so that > perhaps I could do that on my own eventually, so I could perhaps contribute > to helping fix such problems.] If a NMU is numbered like X.X it is considered a source NMU, but if it is numbered X.0.X it is considered a binary NMU. The person did a binary NMU with X.X numbering which caused the problem on those two packages. > > > Who does the work of getting all those packages built for all those > > > different processors? You? Someone who supports those other processors? > > > If you, when do you think you'll have all that work done? > > > > > > alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc > > > > > > Seriously: Is it _worth_ doing all that effort? > > > > We have buildd maintainers that partially automate the process of > > building the packages for all the various archs. The only requirement > > of the package maintainer is to insure that bugs keeping it from being > > built on the other archs are fixed. > > > > In this particular case I think the entire problem was due to a bad NMU. > > I have turned on enable-final in my test packages, which I hope > > to upload soon, that will probably help reduce the time to build on all > > the archs. > > == > In order to inform persons who want to know the process to use to keep up > with what needs to be done for kde in Debian, would you state briefly the > chain of evidence that one follows to know where holdup-causing problems lie > in getting package kde into a state satisfactory for it to be moved to woody? Steps to get package into Woody: 1. Build package 2. Upload package to ftp-master 3. At approximately 1:52pm (CST) dinstall installs package into sid 4. Build daemons download package and attempt to build. 5. After building build daemons upload package to ftp-master 6. Installed into Woody if all of the following occur. a. Correct number of days have passed (according to priority) b. No RC (serious or above) bugs exist for package. c. If all daemons have built and uploaded package (for archs that were available for previous version). > = > As an example of that I mean, something like: > > >From http://ftp-master.debian.org/testing/update_excuses.html > we see meta-kde shows: > kde/alpha unsatisfiable Depends: kghostview ['kdegraphics'] > > In the same file we see: > nothing about kghostview The ['kdegraphics'] part lists the name of the source, which is what is listed in the webpage. > > Also, in the same file we see: > kdegraphics (4:2.1.1-6 to 4:2.2.2-6) > Maintainer:
Re: Alien/RPM keeps trying to kill KDE. Help?
On Wed, Feb 06, 2002 at 02:03:09PM -0500, Phil Edwards wrote: > Okay, there's a software package out there which is being tracked by > Debian, but only very slowly. Some random guy built RPMs for it, so I > thought I'd grab them, and then use either 'rpm' or 'alien' to put the > package onto my testing/unstable machine. > > Grief... > > - alien wants rpm (and so do I, so it's not really alien's fault) > > - rpm depends on librpm4 > > BUT > > - librpm4 conflicts with librpm0, and > > - something called "kpackage" depends on librpm0 This will hopefully be fixed very soon, since rpm had failed to build on m68k but recently compiled correctly. > I don't use kpackage, but I can't remove it, because > > - kde depends on kpackage > > So anytime I try to do anything with 'rpm' dselect/apt-get attempts to > remove the entire KDE suite. Are you sure? The package kde itself is only a metapackage, removing it would not cause any other kde applications to be removed. > Maybe a bug should be filed against KDE? Why does it depend on kpackage? kde is only a meta package which pulls in all/most of the kde packages to make it easier to install. The bug exists on rpm already and I believe was fixed today, I haven't looked in the archive yet. Chris
Re: portable mirror?
I use debmirror, a complete sid i386/source us/non-us mirror takes roughly 8.75GB that might be a bit much for your laptop though. Chris On Thu, Feb 07, 2002 at 11:45:34AM -0800, JC Portlock wrote: > Hey folks. > > With Woody changing as rapidly as it is, the update/upgrades are killing me. > I'm looking for the best program to allow me to take a laptop to where I can > get some bandwidth, download what I need for my home system onto the laptop, > and then update/upgrade from the laptop to the desktop. (My home system is > dialup only). > > TIA
new kdelibs (2.2.2) upload
I made a new kdelibs 2.2.2-12 upload tonight. It changes quite a bit. I will be uploading new packages for kdebase and others asap. I have been quite busy with my CS classes recently, but I hope that will calm down soon. Chris
Re: What's best quick fix for broken kde metapackage?
On Mon, Feb 18, 2002 at 10:28:40AM -0500, Jaldhar H. Vyas wrote: > I'm willing to do an NMU if there really is a dpendency problem (and Chris > doesn't object) but is there really a problem? > > I have libglib1.3-12 installed and I was also able to install the kde > package without any dependency problems. Are you sure it is not just > because your apt mirror is not up to date or something? This should be fixed in the dinstall today. There will be some other issues that will be fixed once I upload the rest of the kde packages. I hope that I will not be doing quite as much repackaging on the others (except for kdebase). Chris
Re: What's best quick fix for broken kde metapackage?
On Wed, Feb 20, 2002 at 09:58:34PM -0800, [EMAIL PROTECTED] wrote: > So: did you do the dinstall? > Is the fix now in the Sid package pool (and hence should have been available > to > my system when I did apt-get update)? Not yet, it was uploaded but have to be manually added. > If so - any idea why my Sid is still having this problem? see above > If not - when (in # of days) do you think Sid systems will be able to install > metapackage "kde"? metapackage will be the last thing I fix since it depends on every other package. I will hopefully upload a new kdebase tomorrow (about 12hrs from now). They have new packages in them so have to be manually overridden before they can go in. As I found out today it will cause some ugly breakage so put kdelibs/kdebase on hold when they appear until I finish uploading the rest of kde. I wish versioned provides worked. :< Chris
Re: Will KDE make it into Woody?
On Sat, Feb 23, 2002 at 10:07:05PM -0800, [EMAIL PROTECTED] wrote: -snip- > [Something like: (readers note: I have _no_ idea what the dates & milestones > would really be.) > "Here's what I conclude needs to be done (& by when): > 2/25-create the metapackaging scheme > 2/28-package the individual metapackages > 3/1 -create the kde metapackage > 3/2 -alpla test > 3/3 -release the packages > 3/8 -beta test > 3/10-fix bugs > 3/11-re-release the fixed packages > ..." > ] As everyone else on this list knows dates like are meaningless since it is impossible to predict what will come up and I do have lots of outside pressures that will take away some time. However, if you want a pretty date list here it is. 2/24 - finish kdebase 2/25 - finish kdeadmin 2/26 - finish kdegraphics 2/27 - finish kdemultimedia 2/28 - finish kdenetwork 3/ 1 - finish kdepim 3/ 2 - finish kdeutils 3/ 3 - finish kde-meta 3/ 4 - finish kde-i18n 3/ 5 - finish kdebindings 3/ 6 - finish kdoc kdebase appears to be the biggest obstacle currently, and the others are probably easier to fix. I have been working on kdebase for about 5 days so far and I think it is almost finished. Chris
Re: Will KDE make it into Woody?
On Sun, Feb 24, 2002 at 03:08:49PM +0200, Jarno Elonen wrote: > Just one question, though: Daniel wrote a while ago that Chris redoing (some > of?) the package from scratch. Doesn't this mean that patches for most of the > current bugs in the DB are likely to be obsolete after that? > > Which packages are safe to work with at the moment? I am redoing the debian packaging of the programs, but not changing upstream code for the most part. So any patches needed would be welcome, I don't need patches for the bugs related to can't install *foo* package though. Thanks, Chris
Re: the non-existence of libglib1.3-12
On Sun, Feb 24, 2002 at 12:48:50PM +, Simon Hepburn wrote: > The sensible thing to do would be to build against the stable branch of > libglib (1.2). I suspect this is what Chris is doing ... hence the delay. > > Simon. libarts apparently needs 1.3 so I removed support for it entirely in the new upload I did last week. When it finally goes into the archive arts will no longer depend on glib at all. Chris
Re: Little Konqueror Irritations
On Sat, Feb 23, 2002 at 03:21:32PM +0100, Jens Benecke wrote: > On Sat, Feb 23, 2002 at 01:33:44PM +0200, Hugo van der Merwe wrote: > > > Whenever I go to Settings->Configure Konqueror it always pops up the > > dialog in the bottom right most corner, *behind* the panel. In fact, > > it is so far into the corner, that the window decorations are off the > > screen. How can I get this [EMAIL PROTECTED] thing to pop up in a sensible > > location? I don't want to move it each time... > > File a bug report (and include "trivial"/"obvious" in the subject, so > that somebody will look at it quickly) I am not sure what the problem is. I am using 1600x1200 and on my screen it looks centered. Maybe the source is hardcoded for a fixed location? Chris
Re: packages tasksel expects to find in woody, that arn't there
On Tue, Feb 26, 2002 at 11:07:49AM -0500, Joey Hess wrote: > Daniel Stone wrote: > > KDE is maintained, and works fine. kdelibs is sitting in incoming and > > AIUI needs an override to go in (even though it's not NEW). Most of its > > dependency problems are there; a kdebase package has also been prepared > > for upload to fix the other dependancy problem. > > > > Hopefully, with these uploads, meta-kde should hit woody. > > > > -d, crossing his fingers and knocking on wood(y?) > > aj reminded me that there was a reason we were trying to avoid using > meta/task packages -- at least big ones that have the potential to go > boom easily, and the above is why. On the other hand I don't want to > have to track what is in the kde package by hand. So I have implemented > something in tasksel that will automatically explode the task package > into its dependancies and list all of those. Tasksel need only be > rebuilt when the deps change. I am adding the meta packages to each kde source so they are rebuilt each time a new upload is done to fix any problems. example) kdelibs (meta) which depends on: libkdecore libkdecore-bin (...) then the kde (meta) package just depends on each of the others so it won't go boom (in theory). Chris
Re: x-session-manager?
On Thu, Feb 28, 2002 at 01:24:12AM +0100, Hendrik Sattler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > Every window-manager is registered as alternative in the category > x-window-manager (arg, I had to do that manually for xfce but it seems to be > orphaned :..( ) > However, kde registers as x-session-manager. I know that it is rather a > session than a window-manager but this cannot be changed anyway (or does it). > So why it is done this way? > > HS Afaik, kde isn't a x-session-manager, KDM is, and you can use KDM with other window managers. Chris
Re: x-session-manager?
On Thu, Feb 28, 2002 at 08:00:43PM +1100, Daniel Stone wrote: > On Thu, Feb 28, 2002 at 08:26:53AM +0100, [EMAIL PROTECTED] wrote: > > > Afaik, kde isn't a x-session-manager, > > > > > well, kde is not, but startkde invokes ksmserver, which is one -> kde is > > registered as a session manager. > > KDE is a desktop environment, technically. Pedant. :P > > > > KDM is, > > > > > WRONG! the player loses 1000 bucks ... :) > > Yea, calc loses $1000. So what do I win? Yep, that will teach me to try to answer questions after midnight. Heh. Chris
Re: Is autobuilding kde packages broken in Unstable?
On Fri, Mar 01, 2002 at 04:06:27PM +0100, Petter Reinholdtsen wrote: > > The autobuilders seem to fail for all KDE packages. The problem seem > to be related to kdebase and kdelibs. Checking > http://buildd.debian.org/fetch.php?&pkg=koffice&ver=1%3A1.1.1-6&arch=arm&stamp=1014541962&file=log&as=raw>, > I see this: > > The following information may help to resolve the situation: Sorry, > but the following packages have unmet dependencies: > kdebase-dev: Depends: kdebase-audiolibs (= 4:2.2.2-13) but it is > not going to be installed > kdelibs-dev: Depends: libkmid-dev (= 4:2.2.2-11) but it is not > going to be installed > E: Sorry, broken packages > > Anyone know what the problem is? kgeo, kdegames, koffice, kdetoys, > kdeutils, kdenetwork, kdemultimedia and kdeadmin seem to have problems > (not sure if everyone have this problem). Yes I know what the problem is and I am attempting to get kdelibs uploaded before dinstall today. The problem is that kdelibs is not installable currently. Chris
Debian KDE 2.2.2 update
kdelibs is in sid now and nearly built for all archs kdebase is in sid and still needs to be built for all archs kdeadmin has a bad build-dep and needs to be fixed kdegraphics has some issues daniels is looking at kdemultimedia is in sid and still needs to be built for all archs kdenetwork is in sid and still needs to be built for all archs kdepim is in sid and still needs to be built for all archs kdeutils is in sid and still needs to be built for all archs meta-kde still needs to be examined after the rest is finished If there is anything I missed let me know. Thanks, Chris
Re: Debian KDE 2.2.2 update
On Sun, Mar 03, 2002 at 06:23:48PM -0800, Tim Grogan wrote: > Thanks Chris, here's a newbie type question. To get all of the kde stuff > should I upgrade to sid? > > Tim If you want all of KDE right now you can upgrade to sid (if you are on x86) otherwise you can wait for about a week and hopefully it will be in woody. Chris pgpVilGyPBAbi.pgp Description: PGP signature
Re: Debian KDE 2.2.2 update
On Tue, Mar 05, 2002 at 11:09:39AM -0600, Colin Watson wrote: > Is anybody planning to adopt kde-i18n? It currently has its maintainer > field set to the QA group, but I'm not sure it's something we should > really be touching - it recently acquired a grave bug, too. > > There only seems to be an RFA: bug about it, not an O: bug, which may be > why it's been missed. > > -- > Colin Watson [EMAIL PROTECTED] I intend to adopt it with KDE 3, but I can do it earlier if needed. Chris
Re: Debian KDE 2.2.2 update
On Tue, Mar 05, 2002 at 06:33:53PM +, Colin Watson wrote: > On Tue, Mar 05, 2002 at 12:20:01PM -0600, Chris Cheney wrote: > > On Tue, Mar 05, 2002 at 11:09:39AM -0600, Colin Watson wrote: > > > Is anybody planning to adopt kde-i18n? It currently has its maintainer > > > field set to the QA group, but I'm not sure it's something we should > > > really be touching - it recently acquired a grave bug, too. > > > > I intend to adopt it with KDE 3, but I can do it earlier if needed. > > Depends how serious #136896 actually is, I suppose. I know Ivan's builds > for potato have contained kdelibs3 - was kdelibs2g used much by that > time? > > If it would help take load off you and you don't mind, I can QA-upload > kde-i18n with extra 'Replaces: kdelibs2g' fields where appropriate. > > -- > Colin Watson [EMAIL PROTECTED] Ivan's main KDE repo had KDE 2.0.1 which was kdelibs3, kdelibs2g is from KDE 1.1.2 which is ~ 16 months old. Why the user would still be using KDE 1.1.2 I am uncertain. I closed the bug since it only occurs from upgrading from a really old not in Debian release of KDE. Chris http://kde.tdyc.com/debian/dists/potato/kde2/binary-i386/libs/ http://kde.tdyc.com/debian/dists/potato/qt1apps/binary-i386/libs/
Re: KDE 2.2.2 unable to view JPG, PNG
On Tue, Mar 05, 2002 at 09:22:56PM -0500, Chris Goodwin wrote: > Hello all, > > I'm running KDE 2.2.2 built from source on a potato system. When I > compiled the packages, during the ./configure part I'd see the following: > > checking for libpng... no > checking for libjpeg6b... no > checking for libjpeg... -ljpeg > > I am unable to view .JPG or .PNG files, not as wallpaper, nor in preview > windows, etc. Applications that view .JPG or .PNG files (gimp, libpng2-dev and libjpeg62-dev should be enough for those. Chris
KDE status update
kdelibs - should go into woody once m68k builds kdebase - should go into woody once m68k, arm, mips builds kdeadmin - should go into woody once arm, m68k, s390, sparc builds kdegraphics - needs new upload to remove kamera kdemultimedia - needs build on all arch kdenetwork- should go into woody once alpha, hppa, ia64, m68k, sparc builds kdepim- only god can save this package[*] kdeutils - needs new upload to remove ark So it may still be possible for KDE to make it into woody, but it looks like kamera, ark, and kdepim will be casualties. Chris * If anyone knows how to fix the gcc 3.0 issues with kdepim please do so asap.
Re: KDE status update
On Wed, Mar 06, 2002 at 10:11:14PM +, Richard Ibbotson wrote: > Chris > > > So it may still be possible for KDE to make it into woody, but it > > looks like kamera, ark, and kdepim will be casualties. > > What about i386 and Kamera ? I'm a photographer. Been looking > forward to using Kamera for six months now. Be a shame if I can't > get hold of it. I'm using Gphoto to sort out the pictures that I've > been taking. Daniel Stone has more information about this but apparently kamera does not work with the new gphoto2 that is in sid. Chris
Re: KDE status update
On Wed, Mar 06, 2002 at 10:20:02PM +, Chris Howells wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wednesday 06 March 2002 21:51, Chris Cheney wrote: > > * If anyone knows how to fix the gcc 3.0 issues with kdepim please do so > > asap. > > Hrm, presumably this is KDE 2.2.2? I know several people build HEAD using gcc > 3 (and fix any problems in CVS), although I'm not sure that anybody bothers > with 2.2.2 and gcc 3. Yes, on HPPA arch gcc 3 is default aiui. The bug report is here: http://bugs.debian.org/133697 Chris
Re: KDE status update
On Wed, Mar 06, 2002 at 03:34:06PM -0700, David Bishop wrote: > What gcc 3.0 issues? I'm on pretty good terms with the kpilot developer, and > would be willing to do some leg work to get this into woody. And not having > korganizer, kpilot, knotes, etc, would suck :-) > > - -- > D.A.Bishop Please take a look at this bug: http://bugs.debian.org/133697 http://buildd.debian.org/fetch.php?&pkg=kdepim&ver=4%3A2.2.2-4&arch=hppa&stamp=1008870358&file=log&as=raw It does not compile at all on HPPA which is an arch that intends to ship with woody, which makes it an RC bug. :< Thanks, Chris this looks like it might be the culprit: c++ -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/include/kde -I/usr/include/qt -I. -I/usr/include/libpisock -I/usr/include/libpisock-DNDEBUG -O2 -fno-exceptions -fno-check-new -c kpilot.cc kpilot.cc: In destructor `virtual KPilotInstaller::~KPilotInstaller()': kpilot.cc:230: no matching function for call to `std::basic_ofstream >::basic_ofstream(int)' /usr/include/g++-v3/bits/std_iosfwd.h:84: candidates are: std::basic_ofstream >::basic_ofstream(const std::basic_ofstream >&)
Re: kghostview dependency problem and vi cursors still broken in woody
On Thu, Mar 07, 2002 at 01:17:16PM +0800, Crispin Wellington wrote: > Did a fresh install of woody. Installation ran without a hitch. > > Firstly, Im having dependency problems with kghostview and koffice-libs > > koffice-libs recommends kghostview >= 2.2-0 which is not available. > > Even sid doesn't seem to have such an advanced version of kghostview. Im > assuming the dependency info in koffice-libs is incorrect. Anyone else > experiencing this? Any work arounds? Has a bug report been submitted? sid does have kghostview 2.2.2-6.1, I am not sure about woody. > Secondly, the arrow keys in vi are still broken (was discussed without > adequate resolution in Febrary on debian-testing) :( Has a bug report > been submitted to the vi maintainer? You need new libncurses5 Chris
Debian KDE Status Update - 20020309
wanna-build status for different archs kdebase - m68k dep-wait - mips building (stuck?) kdeadmin - m68k building (stuck?) kdemultimedia - m68k building (stuck?) kdenetwork- hppa building (stuck?) - m68k failed - sparc needs-build kdepim- hppa building (stuck?) - m68k dep-wait - sparc needs-build kdeutils - hppa building (stuck?) - m68k dep-wait - sparc needs-build --- kdelibs - should go into woody once the m68k buildd maintainer uploads the m68k deb to ftp-master kdemultimedia - will not be available on mips/mipsel due to internal compiler errors. kdepim- will not be available on hppa due to gcc3 errors but will still go into woody. kdegraphics - needs new upload with DNC kamera (or fix for kamera) kdeutils - needs new upload with DNC ark (or fix for ark) --- kde-meta will be examined once all of the rest are finished. I might have missed something, if I did let me know. Thanks, Chris
Re: Konq Not Accepting Cookies
I have Konq set to ask and when I accept the cookies Yahoo sends it works fine. I haven't tried the other settings though. Chris On Sun, Mar 10, 2002 at 09:24:22AM -0500, Robert Tilley wrote: > Reading messages at Yahoo Groups requires your browser to accept cookies. > > I have set Konq to accept only cookies from groups.yahoo.com -- Failure. > > I have set Konq to accept ALL cookies -- failure. > > Yes, I have restarted Konq. and even KDE several times. I can re-set Konq. > to accept all cookies, Apply the settings, and still Yahoo Groups tells me > that cookies are being refused. > > Has anyone on this list encountered this problem with using Yahoo Groups at > groups.yahoo.com? > -- > Comments and information are appreciated. > > Robert Tilley, [EMAIL PROTECTED]
Re: packaging kde-apps
Typically you have: configure --prefix=/usr and make install DESTDIR=$(CURDIR)/debian/tmp You may need more than just the --prefix option on configure. You can look in KDE cvs HEAD to see what I have done with arts and kdelibs for examples. It is really nice if you use builddir != srcdir, see arts/kdelibs for an example of that also. I imagine a lot of people don't know about that feature of autotools. Chris BTW - dh_make --custom is not a valid argument afaict, you should probably use dh_make -t.
Debian KDE Status Update - 20020314
kdelibs- done kdenetwork - done kdepim - done --- wanna-build status kdebase - m68k building kdeadmin - m68k build failed (requeue requested) kdegraphics - needs build on all archs kdemultimedia - m68k build failed (requeue requested) --- kdeutils - need new upload with ark fix (have patch) It may be possible for KDE 2.2.2 to be in woody by sunday (except for kdegraphics/kdeutils) I am working on KDE 3 packaging now, do not bug me about them. :) Thanks, Chris
Re: libusb
The short answer is sane is out of date and needs to be recompiled since libusb0 no longer exists. Chris Here is what I emailed someone else wrt issue: Normally a library is named something like libusb and major sover of 0 so you have libusb0. However as I just recently noticed in libusb's case the library name appears to be libusb-0.1 with sover major of 4. I didn't see any other libraries that were like that at the time so I used libusb-0.1-4 as the name. ex) /usr/lib/libasound.so.2.0.0 - package name libasound2 /usr/lib/libusb-0.1.so.4.1.0 - so I picked name of libusb-0.1-4 I suppose I could have named it libusb-0.1.4 but if I change it now it will be considered new again and dinstall won't put it into sid until someone manually adds it, which in libusb-0.1-4's case took over a week. Then everything will have to be compiled against it again. If I had simply called it libusb4 like some other packages seem to libsigc++0 for example, when libusb upstream decides to call the library libusb-0.2 with major sover 4 I would have a problem, since the old package and the new package would be called the same thing.
Re: KDE 3.0rc3 Debs???
KDE 3.0 final has been tagged and I am working on finishing up the debs for it currently. It will probably take a few more days. Chris On Fri, Mar 29, 2002 at 09:16:06PM -0500, Robert Tilley wrote: > I have read reviews from people who already have KDE 3rc3 on their machines. > My question is: Do .debs exist for those debian-users who want to try it out > for themselves? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Out of Office AutoReply: KDE 3.0rc3 Debs???
When you are away from the office DO NOT SET YOUR MAILER TO RESPOND TO LIST TRAFFIC!!! Chris On Sat, Mar 30, 2002 at 04:02:00AM +0100, Mayer, Christian (Dregis) wrote: > Bin erst am 8.4.02 wieder im Hause. Bitte wenden Sie sich in dringenden > F?llen an "team-adsm" pgpV8ZZsfbQl8.pgp Description: PGP signature
Re: KDE 3.0rc3 Debs???
On Sat, Mar 30, 2002 at 01:13:59PM +0100, Petter Reinholdtsen wrote: > > [Chris Cheney] > > KDE 3.0 final has been tagged and I am working on finishing up the debs > > for it currently. It will probably take a few more days. > > Do you plan to include KDE 3.0 in Woody instead of KDE 2.2.2? No. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Disabled users, Help for
Griz, I am not really familiar with accesibility options under linux so hopefully others will speak up. But I do know that KDE has sticky keys support, it is under KControl -> Personalization -> Accesibility -> Keyboard. KDE also has an accessibility website http://accessibility.kde.org/ Chris Cheney On Thu, Apr 04, 2002 at 07:27:52PM -0800, G. L. `Griz' Inabnit wrote: > -BEGIN PGP SIGNED MESSAGE- > > Hey All ! > > I have a client/friend who's unfortunate enough to be stuffed into a > wheelchair (albeit a cool one) and has limit use of his arms. (Quad) > He's been in the MacroKludge Windon't arena far too long, and had me put > together a nice box for him to get into the Open Source market. > ATT it's an up-to-date WOODY box with KDE (and other wm's to play around > in). What I need is a 'sticky keys' like program. What do we have the the > mbilitity impared in KDE/linux ??? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE 3.0 debs
I want to make everyone aware of my KDE 3.0 plans. KDE 3.0 will not go into sid until woody is released, currently slated for May 1. I will probably also wait until after XFree 4.2 is released so that recompilation won't be needed. However, I will make preliminary debs available once I have finished packaging kdebase (the last package, which I am currently working on). If anyone has questions please keep it on the list if possible. Thanks, Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: When will it be ready?
On Tue, Apr 16, 2002 at 06:13:05PM -0400, Quenten Griffith wrote: > So is it just me or was not everyone aware that Debian takes long with > packages > and you are not going to get them righ away. If you want that then you > should > try Redhat. I installed KDE3 on a RedHat box and its not all that > diffrent or > great, its a little bit fast and has a few new nice tools and it looks > even more > like Windows then it did before. I personally prefered 2.2.1 to 3.0 > from what I > saw at it at first glance. So I don't understand the huge hurry of > every one > wanting to get it. There are those who like to be running the latestst > greatest > and there are those who would like it stable first. Rule of thumb never > install > something that is brand new right away because there are going to still > be bugs > in it, I have hosed my box a few times doing this. Yep, KDE 3.0.0 had quite a few bugs and they even still existed in 3.0.1 but puetzk is squashing them as quickly as I can find them. Hopefully 3.0.1 will be mostly bug free. I will most likely have debs finished by the time 3.0.1 is made available to packagers (May 8). I already have test debs available now but they still have a few debian specific bugs in them. Thanks, Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [KDE3] KPager/workspace weirdness
On Wed, May 01, 2002 at 02:53:38PM +0100, Dave Swegen wrote: > I've just started using KDE properly, but encountered something weird. > For some odd reason kpager lists the desktops in the wrong order. > Currently they are like this: > > 1 2 > 3 4 > > Which is fine in itself. However, using the option to drag a window to a > different workspace (not using kpager) has some interesting results: > > Dragging a window from workspace 1 off the right hand edge makes it end > up in workspace 3, and dragging it from 1 off the bottom edge makes it > appear on workspace 2. This is the inverse of what I would expect. How do you do this? I tried the obvious way of just dragging the box with the mouse off to one side or other and it didn't show up on any other workspace. > Likewise, mapping the desktop switching shortcuts has the same behaviour. > > Is there any way to make kpager stop acting in such a daft manner? Probably need to contact upstream to fix the bugs with the dragging and shortcuts, I think they like the new ordering though. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Out of Office AutoReply: [KDE3] KPager/workspace weirdness
On Thu, May 02, 2002 at 02:26:15AM +0200, Mayer, Christian (Dregis) wrote: > Bin erst am 6.5.02 wieder im Hause. Bitte wenden Sie sich in dringenden > F?llen an "team-adsm" Fix your damn autoreply program not to reply to list traffic. Thanks, Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where are the debian KDE3 sources?
On Fri, May 03, 2002 at 09:47:37PM +0200, Karolina Lindqvist wrote: > fredagen den 3 maj 2002 19.30 skrev Ross Boylan: > > > My understanding from earlier discussion on this list is that although > > the upstream has a debian directory, it is not necessarily current. > > The maintainer for some of the packages said he was using upstream, > > but his packages do not include the core KDE ones. > > True, true. I have tried it. Most packages compile with a little tweaking. > Just don't count on getting it through a compile without knowing how to tweak > debian files to build or knowing what to do when a KDE build fails. My packages should compile out of KDE 3.0 BRANCH as is unless something has changed in the past week. Afaik all my changes are checked into cvs as well, although I have not ported them to HEAD (3.1) yet. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 Update -- Please
On Thu, May 09, 2002 at 11:31:34PM +0200, Jean-Michel Leclant wrote: > Hi, > > You can try this uri, but I think you'd better to wait the official package. > > deb http://kde3.geniussystems.net/debian ./ > > Jean-Michel Yep that is the uri for my test debs there are still known bugs though. For more information you can go to #debian-kde on OPN. KDE 3.0.1 was just tagged yesterday and I am building a new set of debs against the official sources. Once I get the debs debugged I may upload to sid even before woody is released, as I understand it nothing from sid is going into woody any longer so it should be safe to upload now. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 Update -- Please
On Thu, May 09, 2002 at 09:30:36PM -0600, Doug Holland wrote: > On Thursday 09 May 2002 10:43 am, Robert Tilley wrote: > > I know that we're supposed to wait until XFree86 4.2 first appears for > > Debian before asking about KDE 3. Too bad. > > > > May 2, May 3, May 4, and May 5 (You get the idea) have passed and still no > > information on either of those packages is available -- at least to me. Is Woody released yet NO! Although I have heard word that Woody has been closed to files migrating into it so it may now be safe to upload KDE. > > No, I don't have the expertise to package software for Debian nor the time. > > I am only looking for a hint about when The Day of Release might occur. > > No offense, but is it really a good idea to hold off on official KDE 3 until > XFree86 4.2? From what I hear, the Debian priesthood hasn't even begun to > debianize X 4.2, and that it will require oodles of hacking & debugging > before it is considered ready for the Debian masses. KDE 3 does not require > X 4.2, why wait for it? I thought it would have been ready around the same time as KDE 3.0.1 but it appears it won't be. I may upload KDE before 4.2 is released after all. I am currently working on a third round of test debs with the official KDE 3.0.1 tar files. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fwd: How do I install KDE 3.0.1 Debs?
On Sat, May 11, 2002 at 01:44:37AM +0200, Hendrik Naumann wrote: > If you grep alpha-debs you should be able to deal with dpkg. There > are plenty of force switches you may need to use. > dpkg --force-help > will shows you all of them. The only thing force will help you do is fubar your system... Perhaps you don't recall someone's test debs which removed /usr/sbin previously. If install fails it will tell you why which then you can remove the offending packages without needing force. Also there is a text file that explains how to install kde3 and what the current known bugs are but I guess people are only propagating the url for the debs themselves. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How can I FTP KDE 3.01?
On Fri, May 10, 2002 at 09:23:59PM -0500, Robert Tilley wrote: > I would like to use an FTP program such as KBear to transfer the KDE 3.0.1 ^^^ > debs from http://kde3.geniussystems.net/debian/. Instead I must drag-n-drop > each file using Konqueror which is rather slow. > > When I try to connect to the address above I don't see the KDE files but > rather an 'a'-'z' listing of directories. I'm clueless as to why I'm not > taken to the kde listings. > > Any ideas? Yep think about what I underscored. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Experimental KDE3 debs -- first impressions
I only have test packages for packages I maintain... On Sun, May 12, 2002 at 12:12:11AM +0200, Volker Schlecht wrote: > Hi, > > > But they seem to miss kdesdk, > > I just did the updgrade and lost kbabel which I need. > > While we're at it: konq-plugins are sorely missing, too. Or > specifically: I'm sorely missing the ability to dis-/enable Javascript > with two clicks. > > ciao, > Volker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Experimental KDE3 debs -- first impressions
On Sun, May 12, 2002 at 09:49:59PM +1000, Mark Purcell wrote: > The instructions located at http://calc.cx/kde.txt expressly state that you > should NEVER use --force stating that if you do 'you are likely to > permanentaly break your system requiring a full reinstall'. > > There is a good reason for this, if dpkg is telling you there is a conflict > between packages you had better believe it!! If dpkg is reporting a > conflict the 'safe' option is to purge the installed conflicting package and > then reattempt installation. As pointed out elsewhere this maywell mean that > you will also be forced to uninstall other related packages such as xmms or > other KDE packages, but such is life on the bleeding edge. > > Remember these packages have not yet been integrated to provide a smooth > upgrade path from the Debian KDE2 packages to Debian KDE3 packages. The > smooth upgrade should (will) be provided by the Debian KDE3 packages when > they are offically included in the Debian distribution. Until then these > packages which you are installing are not guarenteed to upgrade from KDE2 > smoothly. Hence the instructions to purge all kdelibs3 and libarts packages > before you even attempt installation. Exactly, I guarantee that you can not upgrade from KDE2 to the current debs since they have no (or very few) conflicts in the control file. I am adding as many as I know about in my 3rd set of debs that I am working on currently. I will not upload debs into sid until I am reasonably sure that I have taken care of all the upgrade issues. Thanks, Chris Cheney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 on unstable
On Fri, May 17, 2002 at 06:56:07PM -0400, Cloverm wrote: > Any ideas when we might see KDE3 on unstable? I am very close to being done with packaging KDE 3.0.1. However from what I have read from complaints on debian-devel it may be up to a month before it gets installed due to the fact the packages will be marked NEW. I will see if I can convince a ftp admin to install them sooner though. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc 3.1 and KDE3
On Sat, May 18, 2002 at 02:29:01PM +0200, Carlos Acedo wrote: > kernel 2.4.18 will compile but not run :_( I am not surprised by this since the kernel is written for bugs in gcc aiui. > > Another problems I have with KDE3 (with gcc 2.95 too): > > - I can see jpegs images in preview nor desktop wallpaper but int > konqueror works well > > - Home and end keys in konsole doesn't work (I have tried all layouts) Use a decent shell, bash is broken... see bts. If I remember correctly zsh is supposed to work. A work around for bash is ctrl-a ctrl-e instead of using the special keys. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More KDE3 modules available
On Sun, May 19, 2002 at 04:47:47PM +0100, Richard Shaw wrote: > I try to install kdeaddons, but konq-plugins requires libarts1 >= 1.0.1 > I can only find packages for libarts1 1.0.0 from. Is there anywhere I > can get the required packages from? Yes, incoming new directory in debian ;) Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More KDE3 modules available
On Sun, May 19, 2002 at 09:12:49PM -0400, Cloverm wrote: > Where exactly is the incoming directory? Can you give us link? You can only get to it if you are a debian developer in which case you know where new is. I will try to put up final debs for everything once I finish the rest. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: More KDE3 modules available
On Mon, May 20, 2002 at 01:20:28PM +1000, Ben Burton wrote: > FWIW, I don't think even debian developers can get at the packages - they > seem to have no world read permissions. Well also KDE_3_0_BRANCH for arts, kdelibs have my final uploaded debian dirs :) Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE 3.0.1 debs
I have uploaded KDE 3.0.1 debs to kde3.geniussystems.net you can join OPN #debian-kde to discuss any issues you have. These debs should upgrade from KDE 2.2.2 but you will probably have to use a package management program like dselect or aptitude. I will not be uploading debs to incoming until after the gcc 3.0.1 transition which supposedly will happen within a month. Thanks, Chris Cheney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.0.1 debs
On Sat, May 25, 2002 at 04:12:47PM +0800, dano wrote: > "These debs should upgrade from KDE 2.2.2" -- yes, These are what i am > waiting for. Thank you, Chris. > > And the final newbie's question -- can I upgrade KDE 3.0.1 even when the > verison of XFree86 packages are still 4.1? > I decide to wait for XFree86 4.2 in sid. Yes they work fine with XFree86 4.1, and actually kdm does not work with an unmodified XFree86 4.2 since XFree86 doesn't setup xdmcp properly by default. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3.x and SID
On Thu, Jun 06, 2002 at 08:48:02PM +0200, Wolfgang Ratzka wrote: > Am Donnerstag, 6. Juni 2002 19:42 schrieb G. L. `Griz' Inabnit: > > I haven't seen an announcement when the KDE 3.x debs will be integrated > > into SID. Did I somehow miss this posting?? > > Would > http://lists.debian.org/debian-kde/2002/debian-kde-200205/msg00186.html > fit the bill? That is the right post, however that should have said gcc 3.1.x not 3.0.1. I will have to check with the Debian GCC people to see if the transition is still expected to occur soon. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
KDE 3 packaging - bug thread
I found out that gcc 3.1 is not actually going to be coming soon as some had hoped so I will be uploading KDE into sid soon (really this time). I need to know all current outstanding bugs that I still have not taken care of however, so people won't be screaming when it goes into sid so can everyone please post outstanding bugs against current kde 3 packaging as a reply to this message (so it will thread properly). My debs will be against 3.0.2 or shortly afterwards (3.0.2 tars should be out june 17) so if it is something upstream and fixed in cvs it will be fixed in my uploaded debs, otherwise if it isn't fixed upstream yet be sure to post about it here and file a bug with kde upstream. Thanks, Chris Cheney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 packaging - bug thread
On Tue, Jun 11, 2002 at 12:28:37AM +0200, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Tuesday 11 June 2002 00:05, Chris Cheney wrote: > > time). I need to know all current outstanding bugs that I still have > > not taken care of however, so people won't be screaming when it goes > > into sid so can everyone please post outstanding bugs against current > > kde 3 packaging as a reply to this message (so it will thread properly). > > Hmm, not really a bug, but a wish (and a very annoying thing to me): Is it > possible to have libarts and libarts1 coexist? The same for kdelibs3 and > kdelibs4. Currently, updating to kde 3 will deselect the old ones, and with > it important things like all additional apps for kde2 (of course), but also > wine!!! So users have to decide whether they want wine or kde 3 :-( > And the other thing with these dependencies is that whenever you incidentally > select a kde 2 app (e.g. kwintv, koffice etc.) in dselect, all kde3 packages > are deselected in the dependencies conflict page, and I have to select them > manually again to prevent them from being removed. I will look into libarts/libarts1 issue, but I know for certain the kdelibs issue is not resolvable, I have looked at it along with Kurt Granoth. If I remember correctly, it is almost possible to do but leaves the programs that do work limping along, certainly not in state most users would want. Once KDE 3 goes in though a lot of the KDE 2 apps will be updated. So it won't be nearly as big a problem as it is with KDE 3 outside the archive. Chris Cheney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 packaging - bug thread
On Tue, Jun 11, 2002 at 08:29:54AM +0400, Nikita V. Youshchenko wrote: > > I will look into libarts/libarts1 issue, but I know for certain the > > kdelibs issue is not resolvable, I have looked at it along with Kurt > > Granoth. If I remember correctly, it is almost possible to do but > > leaves the programs that do work limping along, certainly not in state > > most users would want. > > Could you please post the technical description of the issue here ? Which the libarts of kdelibs? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kdms default path 'wrong' (WAS: KDE 3 packaging - bug thread)
On Tue, Jun 11, 2002 at 06:55:34PM +0200, Achim Bohnet wrote: > On Tuesday 11 June 2002 11:49, Oswald Buddenhagen wrote: > > On Tue, Jun 11, 2002 at 10:00:47AM +0200, Achim Bohnet wrote: > > > As long as there's no general debian wide solution to 'login scripts > > > not sourced'. > > > > > i created /etc/X11/Xsession.d/98ossi_envsetup containing > > > > . /etc/profile > > test $HOME/.profile && . $HOME/.profile > > > > the problem is, that this can be used to undermine the options from > > Xsession.options. i'm not sure if a simple solution exists at all. > > There's also the 'trick' that if argv[0] starts with '-' the shell starts > as a login shell, e.g, > > ds10(0) ~ > sh > ds10(0) ~ > echo $dideldum > > ds10(0) ~ > grep didel ~/.bash_profile > export dideldum=yeah > ds10(0) ~ > cat bin/ttt > #!/bin/sh > echo "$dideldum" > ds10(0) ~ > exec -a -/bin/bash /bin/bash ttt > yeah > ds10(0) ~ > > > > Therefore IMHO where the script kde3 gnome are exec'ed the '-' trick > should be used (maybe inside a test so startx does not source the login > environment again. > > But independent of that ' would be good to see kdmrc use the debian default > paths for UserPath and SystemPath. would a /usr/bin/startkde consisting of exec /usr/bin/kde3 do what we need? Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3 packaging - bug thread
On Tue, Jun 11, 2002 at 07:19:31PM +0200, Gerrit Einhoff wrote: > The 3.0.1-debs I installed didn't provide "/etc/pam.d/kde" but > "/etc/pam.d/kdelibs4-data". Therefore kdm wasn't using that PAM-file and > wasn't e.g. reading /etc/environment. After I symlinked /etc/pam.d/kde" to > "kdelibs4-data" it worked fine... UGH! I bet this is the cause of most of the KDM related problems, thanks for finding this. > > Another thing: While all of KDE3 is very fast and stable, KNode seems to be > crashing all the time. Well, at least it's unstable enough to be really > annoying. Anyone else noticed that? Probably not a packaging bug, though... I haven't used KNode very much but I do know various programs are still buggy (like Noatun which is an upstream problem) :< Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: needing an assist
I am not sure but it sounds like your box is dying to me. Since your gcc is failing, artsd causes scsi errors (which is unrelated to artsd), and finally it can't recognize the object file it just created in the second compile. Chris On Thu, Jun 13, 2002 at 03:28:29PM -0700, G. L. `Griz' Inabnit wrote: > -BEGIN PGP SIGNED MESSAGE- > > - -BEGIN PGP SIGNED MESSAGE- > > Hey Chris, > > I'll send this to the debian-kde list too, but I wanted it addressed to > you > first. > > I've run into a very annoying situation with my dual p3 750 & artsd > after a > reinstall of SID. Any time I start artsd I have a never-ending output > (standard out) to the console complaining of scsi errors. I'm still in the > process of debugging the fault, and thought it could (yeah, right!) have > something to do with the smp. So, I fingered I'd just roll my own! :--) > > cd /usr/src/ > apt-get build-dep libarts && apt-get -b source libarts > which errors out with the following error; > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../dcop -I../libltdl -I../kdecore > - - -I../kdeui > - - -I../kssl -I/usr/include/qt -I/usr/X11R6/include -D_REENTRANT -DNDEBUG -O2 > - - -fno- > exceptions -fno-check-new -ftemplate-depth-99 -DQT_NO_TRANSLATION > - - -DQT_CLEAN_NAM > ESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -Wp,-MD,.deps/kapp.pp -c kapp.cpp > - - -fPI > C -DPIC -o .libs/kapp.o > kapp.cpp: In method `void KCheckAccelerators::checkAccelerators()': > kapp.cpp:138: Internal compiler error. > kapp.cpp:138: Please submit a full bug report. > kapp.cpp:138: Internal compiler error: > kapp.cpp:138: See http://www.gnu.org/software/gcc/bugs.html> for > instructio > ns. > make[4]: *** [kapp.lo] Error 1 > make[4]: Leaving directory `/usr/src/kdelibs-2.2.2/kdecore' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/usr/src/kdelibs-2.2.2/kdecore' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/usr/src/kdelibs-2.2.2' > make[1]: *** [all-recursive-am] Error 2 > make[1]: Leaving directory `/usr/src/kdelibs-2.2.2' > make: *** [build-stamp] Error 2 > Build command 'cd kdelibs-2.2.2 && dpkg-buildpackage -b -uc' failed. > E: Child process failed > > So, being a good geek, I finger what the hell and > > cd kdelibs-2.2.2 && dpkg-buildpackage -b -uc > (sigh)which errors out too with THIS error: > > /kdcopactionproxy.o .libs/kcolorcombo.o .libs/kpushbutton.o > .libs/kpanelextensio > n.o .libs/kcompletionbox.o .libs/kalphapainter.o .libs/ksqueezedtextlabel.o > .lib > s/kcommand.o .libs/kwindowlistmenu.o .libs/kfontcombo.o .libs/ktip.o > .libs/kdate > widget.o .libs/karrowbutton.o .libs/libkdeui_la_meta_unload.o > ../kdecore/.libs/ > libkdecore.so -L/usr/X11R6/lib -ldl > /usr/src/kdelibs-2.2.2/dcop/.libs/libDCOP.so > -L/usr/lib -lqt -lpng -lz /usr/lib/libjpeg.so -lXext -lX11 -lSM -lICE > - - -L/usr/li > b/gcc-lib/i386-linux/2.95.4 -lresolv -lXinerama -lstdc++ -lm -lc -lgcc > /usr/bin/ld: .libs/kaction.o: bad symbol index: 2097614 > .libs/kaction.o: could not read symbols: File format not recognized > collect2: ld returned 1 exit status > make[4]: *** [libkdeui.la.closure] Error 1 > make[4]: Leaving directory `/usr/src/kdelibs-2.2.2/kdeui' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/usr/src/kdelibs-2.2.2/kdeui' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory `/usr/src/kdelibs-2.2.2' > make[1]: *** [all-recursive-am] Error 2 > make[1]: Leaving directory `/usr/src/kdelibs-2.2.2' > make: *** [build-stamp] Error 2 > - - ->ROOT<- |dualie| /usr/src/kdelibs-2.2.2 tty1$ > > > Am I stupid, unlucky, or just missing the obvious? :--) > > - - -- > __ >OutCast Computer Consultants of Central Oregon > http://outcast-consultants.redmond.or.us > [EMAIL PROTECTED] > (541) 504-1388 /\IRC: 205.227.115.251:6667:#OutCasts /\ICQ: UIN 138930 > > > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.0.2 is out!!!
On Tue, Jun 25, 2002 at 07:23:41PM -0600, Doug Holland wrote: > Problems I still have so far > > *Many things in the kscreensaver are still broken. None of the > OpenGL > screensavers work, and the Matrix screensaver is still slow (the > xscreensaver > equivalent of this screensaver works just fine.) > > *Where is Koffice and Kdevelop? They're important applications > and need > to be distributed with the rest of KDE. The only packages updated to 3.0.2 so far are the ones I maintain as far as I know, when the others are updated those problems may go away. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Tips for Debianizing KDE3 apps?
You can take a look at one of the kde packages I maintain. If your particular package has a admin dir in it and it is up to date it should be fairly easy to take one of my packages debian dirs and use it for that new package. Chris On Tue, Jun 25, 2002 at 12:07:07AM +0300, Jarno Elonen wrote: > Hi, > > Could someone (Chris?) spare a moment and share with us some secrets of > Debianizing KDE3 packages? > > What to look out for (e.g. objdir!=srcdir problems and how to solve them), > have you made your own dh_make templates or other tools for KDE 3 etc? > > (The inspiration for this request comes from having been trying to get Kwave > and Pixie plus working on Debian with KDE 3. Neither works fine if I just > "make install" but complain about missing plugins - and besides, trying to > Debianize them is a great exercise.) > > - Jarno > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde3 debs do not work with libpng from sid
On Wed, Jun 26, 2002 at 03:54:00PM +0200, Michael Thaler wrote: > Hello, > > I tried to find out more about the problems I have with todays kde3 > debs from kde3.geniussystem.net and libpng. I have installed both > libpng2-dev and libpng3-dev. Everything in KDE3 should be linked to libpng3. Are you sure you actually have KDE3 installed? Perhaps it only halfway installed on your box or was held back. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kde3 debs do not work with libpng from sid (solved)
On Wed, Jun 26, 2002 at 05:22:12PM +0200, Michael Thaler wrote: > What I do not understand is, why kde is using the libqt from > /usr/local/qt... I do not have it in LD_LIBRARY_PATH Is it perhaps listed in /etc/ld.so.conf ? Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kdegraphics and KPovModeler?
I think that KPovModeler was added to kdegraphics in 3.1.0 which is not going to be released until late October. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem installing kdevelop-generated index.docbook
Or you can just copy the debiandirs file out of kdelibs4-dev and add this to your rules (if packaging): -include debian/debiandirs Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1
On Fri, Jul 12, 2002 at 02:10:47PM -0700, Jon Ellis wrote: > Does anyone know when KDE 3.1 will be released under Debian? > > Jon Probably not too long after it is actually released period. :P -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE 3.1
On Fri, Jul 12, 2002 at 04:54:29PM -0600, David Bishop wrote: -snip- > Well (and maybe this is what Jon meant) is anyone planning on packaging up > the > beta releases? I don't think anyone should bother with the alphas (too much > of a moving target), but at least with Ivan, there was a tradition of putting > the last few betas and release canidates through sid, or up on > people.debian.org. Obviously, as I'm not volunteering to do the packaging > and maintainence myself, this is a simple query, not a demand :-) > > Have a great weekend! Yes, I and a few other people have already started working on them, they are a moving target however and break regularly. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: audio io slave, ogg, and incorrect bitrates.
Woody has been frozen since last april (roughly 76 days). This bug is fixed in KDE 3 though. Chris On Tue, Jul 16, 2002 at 11:17:38AM +0800, Alwyn Schoeman wrote: > Apparently there is a patch for kde 2.2.2 here: > > http://homepage.usask.ca/~aco907/audiocd-vorbisrc3.patch > > I cannot see how this is still broken in the current 2.2.2 that is in > testing, but it is. Does it mean that the kde developers have not fixed > the problem yet themselves or is it the Debian packager's responsibility > to patch in the distribution? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 in sid update
On Sat, Jul 20, 2002 at 12:56:15AM +0100, Nicolai P Guba wrote: -snip- > I don't understand. What has gcc 3.0.1 to do with it. It's not even in > unstable and I have been running it for years now. In fact, this one right > here is 3.0.2 compiled with The original post was a typo, it was supposed to read 3.1.0, however 3.1.0 was buggy and it appears 3.2 will probably be the one debian switches to. GCC 3.2 should be released today, but I do not know how long it will take to switch to it. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 and KDE2 side by side
On Thu, Jul 25, 2002 at 09:33:02AM -0300, Ashley George wrote: > > Hi, > > I am running Debian unstable. Is it possible to install the KDE 3 > packages mentioned in recent postings side by side with Debian's 2.2 > packages? Multiple versions of KDE can not be installed into the same hierarchy and this is not a limitation of Debian, it is a limitation of how KDE works. You can of course have one version in /usr and one somewhere else like /opt or /usr/local. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 in sid update
On Sat, Jul 27, 2002 at 06:33:09PM +0100, John Gay wrote: > So what are the known working versions of GCC for compiling KDE3 with? > > I am looking to try my hand at building a Pentium-optimised box from scratch. > lfs uses GCC2.95.5 but Debian provides both GCC2.95.5 and GCC3? > > I've also looked into PGCC, but the latest patches they have are for > GCC2.95.3 and the site seems to be un-maintained. It is known to work on 2.95.4 and 3.0.x since those are the versions in Debian already. It will probably work with 3.1/3.2 but I am not certain. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: LIST-DAEMON COMMAND {{ DIGEST MODE FLAG TRUE TOGGLE }} STOP END
Why are you sending these strange messages to the list?
Chris
On Tue, Jul 30, 2002 at 02:32:10PM -0400, Craig Morehouse wrote:
> LIST-DAEMON COMMAND {{ DIGEST MODE FLAG TRUE TOGGLE }} STOP END
> --
> Our capacity for understanding is inversely proportional
> to how much we think we know.
>
>Set the controls for the heart of the sun.
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
