I am sorry that the KDE maintainers are incapable of forwarding bugs
upstream. One would assume that they, unlike me, have accounts on KDE's
Bugzilla.
GNOME has its problems, but its maintainers are actually
making some effort to maintain it, so I guess I'll switch to it.
Bye-bye now.
--
(OK, bug unarchived, now the message should get through...)
Just installed KDE 4.2.4. NO, dolphin does NOT have an option to open every
folder
in a new window automatically when you double-click. (Macintosh c. 1984
style.)
The equivalent of Konqueror's "Open folders in separate windows" optio
Package: konqueror
Version: 4:4.2.4-1
Severity: important
Under "Settings"/"Configure Konqueror...", under "File Management", there is an
option
called "Open folders in separate windows". I have had this option on since day
one.
It is absolutely essential -- I cannot comfortably browse files wi
Package: dolphin
Version: 4:4.2.2-1
Severity: wishlist
This is a wishlist. I found dolphin completely unusable because of only one
missing option.
I prefer to do my file browsing "old MacOS"-style, one window per folder, where
opening a folder opens a new window.
Konqueror has an configura
Package: kscd
Version: 4:3.5.1-1
Severity: important
This is a recurring and infuriating problem -- or actually, family of problems.
I'm not sure if they're related, so I'm filing bugs for each one.
Here's a reproduction recipe.
(1) Insert an audio CD. Open it in kscd. Stop it.
(2) Attempt to
Package: arts
Version: 1.4.2-5
Severity: important
Justification: fails to build from source
>From the log at
http://buildd.debian.org/fetch.php?&pkg=arts&ver=1.4.3-3&arch=hppa&stamp=1133415424&file=log&as=raw
we see:
checking for Qt... configure: error: Qt (>= Qt 3.3 and < 4.0) (library qt-mt)
r or not it Suggests: rar. I
think unrar will be a better choice for most people.
--
Nathanael Nerode <[EMAIL PROTECTED]>
"(Instead, we front-load the flamewars and grudges in
the interest of efficiency.)" --Steve Lanagasek,
http://lists.debian.org/debian-devel/2005/09/msg01
r not.
--
Nathanael Nerode <[EMAIL PROTECTED]>
Make sure your vote will count.
http://www.verifiedvoting.org/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: kicker
Version: 4:3.4.2-3.0.1
Severity: serious
On ia64, kicker has a binNMU, with an unsatisfiable exact
same-version dependency on the architecture: all package kdebase-data.
This prevents various packages like amarok from being built, since the
buildds can't install stuff.
The versi
I'm pleased to discover that as of today's kdelibs upload, all of
kdebindings's dependencies are transitioned on all arches so it's safe to
upload a transitioned kdebindings.
--
Nathanael Nerode <[EMAIL PROTECTED]>
This space intentionally left blank.
--
To UN
ake[4]: *** [pixmapfunction.h] Bus error
Anyone know what's going on there? Replies to lists please.
--
Nathanael Nerode
Doom! Doom!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Looks like gcc-3.4 *and* gcc-4.0 ICE on m68k.
Time to restrict the architecture list? :-P
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Chris Cheney wrote:
> 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).
>>
The lm-sensors mess has been solved by Aurelien Jarno. (Hooray!) The
new version has been arranged to work with both 2.4 and 2.6 kernels, with
no crashes or anything.
You can now reenable lm-sensors support if you do it carefully.
The source package must build-depend on libsensors-dev (>= 2.8.4
Colin Watson wrote:
>There's going to be one problem with these two, namely that they both
>need newer alsa-lib which needs newer jack-audio-connection-kit than
>what's in testing, and some things still need to be rebuilt for that.
Having anticipated that, I worked out an extensive list of the iss
d/kdebase-3.1.5/obj-s390-linux/ksysguard/ksysguardd'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/build/buildd/kdebase-3.1.5/obj-s390-linux/ksysguard'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/kdebase-3.1.5/obj-s390-linux'
ma
Chris Cheney wrote:
>And at the current rate that the buildds are retrying
>KDE 3.1.5 it will be months before it goes into sarge as well.
The undeniable fact that other parts of the project are making it harder for
sarge to be release-ready is no reason for you to make it harder for sarge to
be
Josh Metzler wrote:
>I propose that the initial upload of KDE 3.2 be made to experimental rather
>than unstable. Anyonw who is tracking sid ought to be able to figure out how
>to get 3.2 from experimental.
I strongly second this idea. This way, KDE 3.1.5 can get into sarge *while*
KDE 3.2 is
Chris Cheney wrote:
>There are currently two known bugs that will block KDE 3.1.5 from going
>into sarge #226727 and #226738. It seems the GCC people don't think
>their bug is important enough to fix...
More, that it wasn't diagnosed enough to fix in a reasonable amount of
time. :-( But kdelibs
Package: kde-extras
Version: 4:3.1.2
Severity: serious
Tags: patch
Justification: Policy 2.2.1
Change the "Recommends" to a "Suggests" in order to comply with policy.
Chris Cheney wrote:
kdelibs
---
m68k- failed - needs retry (waiting on qt-x11-free)
mips- failed - ICE #226727
Please try to find a workaround for this ICE (or help find & fix it).
The GCC developers haven't tracked it down yet, which means it may well
not be fixed by sarge release
kdegraphics
---
mips- failed - this one is odd
I believe that this is a bug with XFree86 vs. FreeType2 which was fixed
very recently. So it just needs to be retried. :-/
>kdeutils
>
>mips- failed - needs the SYS_sysinfo fix [1]
...
>[1] - Was broken after supposed toolchain freeze by f*cking wonderful
>toolchain changes.
Yeah, that one sucks a lot; I've noted some other packages it bites in the
appropriate bug trail. That one showed up in a supposed
>http://bugs.debian.org/release-critical/
>http://buildd.debian.org/stats/
>
>553 RC bugs are still open combined with the fact that the s390 buildd
>still isn't online and how far behind the other buildds are, leads me to
>believe sarge won't be releasing anytime soon. It certainly looks like
>it
omeone actually working on it already?
Replies to the list please.
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
This appears to be the last core KDE package *not* to be at version
3.1.4 in unstable.
(While it won't go into testing until the jack-audio-connection-kit
dependency chain is unclogged, that will probably be unclogged in the
next couple of weeks.)
Is someone interested in making the upload?
>kdebase_3.1.4-1_i386.changes uploaded successfully to localhost
>along with the files:
Hooray! Good work, Chris! :-)
(I criticize often enough, so I try to give praise where praise is due as
well.)
...taps fingers
"ASAP" as of two days ago. Any chance this will happen this year?!?
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
So we should get kdebase
today or tomorrow, then, right? If not, what the hell is going on and how
can we help?
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
se two bugs,
announce them so that people can help diagnose them.
If Chris doesn't upload a package in a few days, I hope that someone else
will upload a package fixing at least #210276 and #211475 (remember to
set the maintainer to the joint maintenance team while you're at it).
Apologies
Colin Watson wrote:
If an initial upload of kdebase 3.1.4 could be made before all of the
work necessary for a final release has been done, that would be very
much appreciated. You'll be able to start finding out whether there are
unexpected build problems that way, and you'll give the release te
Several estimates have come and gone, but could we have a new estimate
anyway? ;-)
on the kde end, though the glibc
people have their work cut out for them, of course.)
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
-only.
Once those two are in, it's just a matter of getting all the buildds to
do their jobs, and everything except kdemultimedia (glibc bug),
kdebindings (unpackaged), and meta-kde (who cares?) should go into 'testing'
pretty quickly. Frankly, I wouldn't worry about those at
The current[1] status of KDE in sid is below. Hopefully the buildds
will catch up soon then I can upload a new kdelibs.
Is there really any reason to wait for them to catch up?
health?
Do you need help? If so, on what?
The other transitions for sarge are clearing up pretty fast, so I'm starting
to worry about the state of KDE
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
#203303 [Chris Cheney]
5. kdeaddons 3.1.4 needs to be built & uploaded after kdegames and
kdemultimedia are. [Chris Cheney]
6. meta-kde 3.1.4 needs to be uploaded.
So, did I miss anything?
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
Anyone have a clue what's going on there? It looks like a timeout, but I
heard rumors it was a toolchain problem. How soon can this get fixed?
--
Nathanael Nerode
http://home.twcny.rr.com/nerode/neroden/fdl.html
38 matches
Mail list logo
