Re: KDE 3.5 Release Candidate 1 packages available on alioth - Debian

This is a discussion on Re: KDE 3.5 Release Candidate 1 packages available on alioth - Debian ; Christopher Martin wrote: > [Please follow-up to debian-kde@lists.debian.org only. Thanks.] > > 3.5 RC1 PACKAGES > ================ > > The Debian Qt/KDE team has been hard at work, and would like to announce the > availability of packages for KDE ...

+ Reply to Thread
Results 1 to 15 of 15

Thread: Re: KDE 3.5 Release Candidate 1 packages available on alioth

  1. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Christopher Martin wrote:
    > [Please follow-up to debian-kde@lists.debian.org only. Thanks.]
    >
    > 3.5 RC1 PACKAGES
    > ================
    >
    > The Debian Qt/KDE team has been hard at work, and would like to announce the
    > availability of packages for KDE 3.5 Release Candidate 1. These packages
    > have not been uploaded to the archive, not even experimental, but are
    > available from the pkg-kde alioth repository. They are still rough and
    > experimental, so don't use them unless you're willing to risk a broken
    > desktop. You can access the packages by adding the following lines to your
    > sources.list:
    >
    > deb http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    > deb-src http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    >


    First of all, thanks for your work.
    Looking at the packages I noticed that they are still compiled against
    the old hal/dbus packages from unstable. Wouldn't it have been worthwile
    to choose the uptodate hal/dbus versions from experimental? There have
    been major advances in this versions and IIRC the GNOME 2.12 packages in
    experimental also use new hal/dbus version already.

    Cheers,
    Michael

    P.S.: Please CC me, I'm not subscribed.
    --
    Why is it that all of the instruments seeking intelligent life in the
    universe are pointed away from Earth?

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

    iD8DBQFDe/9Qh7PER70FhVQRAvrBAKC2TRJeReAojSoQPCKzSa5ox6mhzACg xqNX
    wLgso14rzdeEl6UMybUn5sY=
    =LSBm
    -----END PGP SIGNATURE-----


  2. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Now only if some caritative soul uploaded the amd64 debs... :P

    Rafael Rodríguez


    > Christopher Martin wrote:
    > > [Please follow-up to debian-kde@lists.debian.org only. Thanks.]
    > >
    > > 3.5 RC1 PACKAGES
    > > ================
    > >
    > > The Debian Qt/KDE team has been hard at work, and would like to announce
    > > the availability of packages for KDE 3.5 Release Candidate 1. These
    > > packages have not been uploaded to the archive, not even experimental,
    > > but are available from the pkg-kde alioth repository. They are still
    > > rough and experimental, so don't use them unless you're willing to riska
    > > broken desktop. You can access the packages by adding the following lines
    > > to your sources.list:
    > >
    > > deb http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    > > deb-src http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./


  3. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Rafael Rodríguez a écrit :
    > Now only if some caritative soul uploaded the amd64 debs... :P
    >
    > Rafael Rodríguez
    >
    >
    >
    >>Christopher Martin wrote:
    >>
    >>>[Please follow-up to debian-kde@lists.debian.org only. Thanks.]
    >>>
    >>>3.5 RC1 PACKAGES
    >>>================
    >>>
    >>>The Debian Qt/KDE team has been hard at work, and would like to announce
    >>>the availability of packages for KDE 3.5 Release Candidate 1. These
    >>>packages have not been uploaded to the archive, not even experimental,
    >>>but are available from the pkg-kde alioth repository. They are still
    >>>rough and experimental, so don't use them unless you're willing to risk a
    >>>broken desktop. You can access the packages by adding the following lines
    >>>to your sources.list:
    >>>
    >>>deb http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    >>>deb-src http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./

    >
    >


    arts, kdelibs and kdebase built fine yet.
    but kdenetwork FTBS on amd64 :

    g++ -DHAVE_CONFIG_H -I.
    -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc
    -I../../../..
    -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc
    -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete
    -I../../../../kopete/libkopete
    -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete/avdevice
    -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete/ui
    -I../../../../kopete/libkopete/ui -I/usr/include/kde
    -I/usr/share/qt3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
    -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500
    -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
    -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 -Wformat-security
    -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions
    -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST
    -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT kircmessage.lo -MD
    -MP -MF .deps/kircmessage.Tpo -c
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp
    -fPIC -DPIC -o .libs/kircmessage.o
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:
    In static member function 'static KIRC::Message
    KIRC::Message:arse(KIRC::Engine*, const QTextCodec*, bool*)':
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:171:
    error: ISO C++ says that these are ambiguous, even though the worst
    conversion for the first is better than the worst conversion for the second:
    /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    QMemArray:perator[](int) const [with type = char]
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:171:
    note: candidate 2: operator[](const char*, long int)
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:172:
    error: ISO C++ says that these are ambiguous, even though the worst
    conversion for the first is better than the worst conversion for the second:
    /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    QMemArray:perator[](int) const [with type = char]
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:172:
    note: candidate 2: operator[](const char*, long int)
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:174:
    error: ISO C++ says that these are ambiguous, even though the worst
    conversion for the first is better than the worst conversion for the second:
    /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    QMemArray:perator[](int) const [with type = char]
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:174:
    note: candidate 2: operator[](const char*, long int)
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:175:
    error: ISO C++ says that these are ambiguous, even though the worst
    conversion for the first is better than the worst conversion for the second:
    /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    QMemArray:perator[](int) const [with type = char]
    /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:175:
    note: candidate 2: operator[](const char*, long int)
    make[6]: *** [kircmessage.lo] Error 1
    make[6]: Leaving directory
    `/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/obj-x86_64-linux-gnu/kopete/protocols/irc/libkirc'


    patch to fix it:

    --- kircmessage.cpp.orig 2005-11-17 08:24:06.000000000 +0100
    +++ kircmessage.cpp 2005-11-17 08:29:12.000000000 +0100
    @@ -168,11 +168,11 @@
    //
    // Some servers send '\n' instead of '\r\n' that
    the RFCs say they should be sending.

    - if (length > 1 && raw[length-2] == '\n') {
    - raw[length-2] = '\0';
    + if (length > 1 && raw.at(length-2) == '\n') {
    + raw.at(length-2) = '\0';
    }
    - if (length > 2 && raw[length-3] == '\r') {
    - raw[length-3] = '\0';
    + if (length > 2 && raw.at(length-3) == '\r') {
    + raw.at(length-3) = '\0';
    }

    kdDebug(14121) << "<< " << raw << endl;

    Cheers,
    Mik


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

  4. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    DD

    Keep up the good work! (and drop a note when they're ready) )

    Rafael Rodríguez

    2005/11/17, Mickael Marchand :
    > Rafael Rodríguez a écrit :
    > > Now only if some caritative soul uploaded the amd64 debs... :P
    > >
    > > Rafael Rodríguez
    > >
    > >
    > >
    > >>Christopher Martin wrote:
    > >>
    > >>>[Please follow-up to debian-kde@lists.debian.org only. Thanks.]
    > >>>
    > >>>3.5 RC1 PACKAGES
    > >>>================
    > >>>
    > >>>The Debian Qt/KDE team has been hard at work, and would like to announce
    > >>>the availability of packages for KDE 3.5 Release Candidate 1. These
    > >>>packages have not been uploaded to the archive, not even experimental,
    > >>>but are available from the pkg-kde alioth repository. They are still
    > >>>rough and experimental, so don't use them unless you're willing to risk a
    > >>>broken desktop. You can access the packages by adding the following lines
    > >>>to your sources.list:
    > >>>
    > >>>deb http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    > >>>deb-src http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./

    > >
    > >

    >
    > arts, kdelibs and kdebase built fine yet.
    > but kdenetwork FTBS on amd64 :
    >
    > g++ -DHAVE_CONFIG_H -I.
    > -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc
    > -I../../../..
    > -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc
    > -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete
    > -I../../../../kopete/libkopete
    > -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete/avdevice
    > -I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete/ui
    > -I../../../../kopete/libkopete/ui -I/usr/include/kde
    > -I/usr/share/qt3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
    > -D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500
    > -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
    > -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 -Wformat-security
    > -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions
    > -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST
    > -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT kircmessage.lo -MD
    > -MP -MF .deps/kircmessage.Tpo -c
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp
    > -fPIC -DPIC -o .libs/kircmessage.o
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:
    > In static member function 'static KIRC::Message
    > KIRC::Message:arse(KIRC::Engine*, const QTextCodec*, bool*)':
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:171:
    > error: ISO C++ says that these are ambiguous, even though the worst
    > conversion for the first is better than the worst conversion for the second:
    > /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    > QMemArray:perator[](int) const [with type = char]
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:171:
    > note: candidate 2: operator[](const char*, long int)
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:172:
    > error: ISO C++ says that these are ambiguous, even though the worst
    > conversion for the first is better than the worst conversion for the second:
    > /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    > QMemArray:perator[](int) const [with type = char]
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:172:
    > note: candidate 2: operator[](const char*, long int)
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:174:
    > error: ISO C++ says that these are ambiguous, even though the worst
    > conversion for the first is better than the worst conversion for the second:
    > /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    > QMemArray:perator[](int) const [with type = char]
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:174:
    > note: candidate 2: operator[](const char*, long int)
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:175:
    > error: ISO C++ says that these are ambiguous, even though the worst
    > conversion for the first is better than the worst conversion for the second:
    > /usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    > QMemArray:perator[](int) const [with type = char]
    > /home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:175:
    > note: candidate 2: operator[](const char*, long int)
    > make[6]: *** [kircmessage.lo] Error 1
    > make[6]: Leaving directory
    > `/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/obj-x86_64-linux-gnu/kopete/protocols/irc/libkirc'
    >
    >
    > patch to fix it:
    >
    > --- kircmessage.cpp.orig 2005-11-17 08:24:06.000000000 +0100
    > +++ kircmessage.cpp 2005-11-17 08:29:12.000000000 +0100
    > @@ -168,11 +168,11 @@
    > //
    > // Some servers send '\n' instead of '\r\n' that
    > the RFCs say they should be sending.
    >
    > - if (length > 1 && raw[length-2] == '\n') {
    > - raw[length-2] = '\0';
    > + if (length > 1 && raw.at(length-2) == '\n') {
    > + raw.at(length-2) = '\0';
    > }
    > - if (length > 2 && raw[length-3] == '\r') {
    > - raw[length-3] = '\0';
    > + if (length > 2 && raw.at(length-3) == '\r') {
    > + raw.at(length-3) = '\0';
    > }
    >
    > kdDebug(14121) << "<< " << raw << endl;
    >
    > Cheers,
    > Mik
    >


  5. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    On November 17, 2005 02:32, Mickael Marchand wrote:
    > arts, kdelibs and kdebase built fine yet.
    > but kdenetwork FTBS on amd64 :


    I've updated the package; it now includes the fix for this.

    Cheers,
    Christopher Martin

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Signed by Christopher Martin

    iD8DBQBDfJ99U+gWW+vtsysRAqTmAJ0ZGVWojd/1GvXVVjuF6eF453Vo4gCfU4Ip
    UqGxgWJa7mUbkDbEAEvpwsg=
    =ViFg
    -----END PGP SIGNATURE-----


  6. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    On November 16, 2005 22:55, Michael Biebl wrote:
    > Looking at the packages I noticed that they are still compiled against
    > the old hal/dbus packages from unstable. Wouldn't it have been worthwile
    > to choose the uptodate hal/dbus versions from experimental? There have
    > been major advances in this versions and IIRC the GNOME 2.12 packages in
    > experimental also use new hal/dbus version already.


    Well, the idea behind the packages is to test them and ready them for
    inclusion in the archive. If the archive will contain the old dbus/hal,
    then we should build and test against them. Besides, building against the
    new dbus/hal is not a small matter - the package names have changed, and so
    updating to experimental dbus/hal means that users will not be able to drop
    back down to unstable kdebase packages without major package
    removal/reinstallation. Besides rebuilding kdebase, we'd have to rebuild
    k3b, since it also uses the old dbus/hal in unstable.

    That said, feel free to rebuild kdebase yourself, and let us know if there
    are major issues (since we'll have to deal with them eventually anyway).

    Cheers,
    Christopher Martin

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Signed by Christopher Martin

    iD8DBQBDfKEtU+gWW+vtsysRAukxAKChUe6eUOxmT2QNgKGlPl/CR/lSIwCbBS82
    bay3n/F04oLFgkV2aaVFkyc=
    =uQrG
    -----END PGP SIGNATURE-----


  7. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    AMD64 packages :
    deb ftp://ftp-fourier.ujf-grenoble.fr/debian/kde35rc1/ ./

    these packages are not provided by the KDE packagers team, there are
    just provided as is by me (with no warranty ... .. ..

    Cheers,
    Mik


    Rafael Rodríguez a écrit :
    > DD
    >
    > Keep up the good work! (and drop a note when they're ready) )
    >
    > Rafael Rodríguez
    >
    > 2005/11/17, Mickael Marchand :
    >
    >>Rafael Rodríguez a écrit :
    >>
    >>>Now only if some caritative soul uploaded the amd64 debs... :P
    >>>
    >>>Rafael Rodríguez
    >>>
    >>>
    >>>
    >>>
    >>>>Christopher Martin wrote:
    >>>>
    >>>>
    >>>>>[Please follow-up to debian-kde@lists.debian.org only. Thanks.]
    >>>>>
    >>>>>3.5 RC1 PACKAGES
    >>>>>================
    >>>>>
    >>>>>The Debian Qt/KDE team has been hard at work, and would like to announce
    >>>>>the availability of packages for KDE 3.5 Release Candidate 1. These
    >>>>>packages have not been uploaded to the archive, not even experimental,
    >>>>>but are available from the pkg-kde alioth repository. They are still
    >>>>>rough and experimental, so don't use them unless you're willing to risk a
    >>>>>broken desktop. You can access the packages by adding the following lines
    >>>>>to your sources.list:
    >>>>>
    >>>>>deb http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    >>>>>deb-src http://pkg-kde.alioth.debian.org/kde-3.5-rc1 ./
    >>>
    >>>

    >>arts, kdelibs and kdebase built fine yet.
    >>but kdenetwork FTBS on amd64 :
    >>
    >> g++ -DHAVE_CONFIG_H -I.
    >>-I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc
    >>-I../../../..
    >>-I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc
    >>-I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete
    >>-I../../../../kopete/libkopete
    >>-I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete/avdevice
    >>-I/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/libkopete/ui
    >>-I../../../../kopete/libkopete/ui -I/usr/include/kde
    >>-I/usr/share/qt3/include -I/usr/X11R6/include -DQT_THREAD_SUPPORT
    >>-D_REENTRANT -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500
    >>-D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W
    >>-Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -Wall -O2 -Wformat-security
    >>-Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions
    >>-fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST
    >>-DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -MT kircmessage.lo -MD
    >>-MP -MF .deps/kircmessage.Tpo -c
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp
    >> -fPIC -DPIC -o .libs/kircmessage.o
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:
    >>In static member function 'static KIRC::Message
    >>KIRC::Message:arse(KIRC::Engine*, const QTextCodec*, bool*)':
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:171:
    >>error: ISO C++ says that these are ambiguous, even though the worst
    >>conversion for the first is better than the worst conversion for the second:
    >>/usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    >>QMemArray:perator[](int) const [with type = char]
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:171:
    >>note: candidate 2: operator[](const char*, long int)
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:172:
    >>error: ISO C++ says that these are ambiguous, even though the worst
    >>conversion for the first is better than the worst conversion for the second:
    >>/usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    >>QMemArray:perator[](int) const [with type = char]
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:172:
    >>note: candidate 2: operator[](const char*, long int)
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:174:
    >>error: ISO C++ says that these are ambiguous, even though the worst
    >>conversion for the first is better than the worst conversion for the second:
    >>/usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    >>QMemArray:perator[](int) const [with type = char]
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:174:
    >>note: candidate 2: operator[](const char*, long int)
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:175:
    >>error: ISO C++ says that these are ambiguous, even though the worst
    >>conversion for the first is better than the worst conversion for the second:
    >>/usr/share/qt3/include/qmemarray.h:99: note: candidate 1: type&
    >>QMemArray:perator[](int) const [with type = char]
    >>/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/./kopete/protocols/irc/libkirc/kircmessage.cpp:175:
    >>note: candidate 2: operator[](const char*, long int)
    >>make[6]: *** [kircmessage.lo] Error 1
    >>make[6]: Leaving directory
    >>`/home/mikmak/src/kde-debian/kdenetwork-3.5-rc1/obj-x86_64-linux-gnu/kopete/protocols/irc/libkirc'
    >>
    >>
    >>patch to fix it:
    >>
    >>--- kircmessage.cpp.orig 2005-11-17 08:24:06.000000000 +0100
    >>+++ kircmessage.cpp 2005-11-17 08:29:12.000000000 +0100
    >>@@ -168,11 +168,11 @@
    >> //
    >> // Some servers send '\n' instead of '\r\n' that
    >>the RFCs say they should be sending.
    >>
    >>- if (length > 1 && raw[length-2] == '\n') {
    >>- raw[length-2] = '\0';
    >>+ if (length > 1 && raw.at(length-2) == '\n') {
    >>+ raw.at(length-2) = '\0';
    >> }
    >>- if (length > 2 && raw[length-3] == '\r') {
    >>- raw[length-3] = '\0';
    >>+ if (length > 2 && raw.at(length-3) == '\r') {
    >>+ raw.at(length-3) = '\0';
    >> }
    >>
    >> kdDebug(14121) << "<< " << raw << endl;
    >>
    >>Cheers,
    >>Mik
    >>



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

  8. Re: Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Hi Christopher,
    > Well, the idea behind the packages is to test them and ready them for
    > inclusion in the archive. If the archive will contain the old dbus/hal,


    I disagree for some reasons:
    - People testing stuff from experimental will probably also want to test
    DBUS and GNOME from experimental. After all, they are brave experimental
    testers! Currently this means uninstalling KDE (which I just did.)
    - New DBus will enter unstable some time, too, you know. You should also
    test KDE with the new DBus, why don't you do it at the same time?
    - Gnome 2.12 has been sitting in experimental for a month now - they
    will probably upload to unstable soon, too? Especially since they aren't
    affected much by the C++ allocator changes I think.
    - Gnome 2.12 was shipped with Ubuntu Breezy, so it has received a
    *serious* amount of testing already on a Debian-based system
    - Downgrading dbus from experimental to unstable shouldn't be hard, *because* the package
    names have changed and they conflict... so once you upload KDE packages
    to unstable, even with an old dbus, a simple "apt-get install kde
    dbus-1" should install the new KDE and the old dbus again. They'll only
    get conflicts if they have other dbus-related stuff (read: gnome from
    experimental) installed. In that case they can just stick with the
    experimental version...

    > removal/reinstallation. Besides rebuilding kdebase, we'd have to rebuild
    > k3b, since it also uses the old dbus/hal in unstable.


    K3B is actually the only reason (apart rare konqueror webpage tests) why
    I have parts of KDE installed... So I'd prefer to have it built with
    experimental DBUS, too... ;-)

    best regards,
    Erich Schubert
    --
    erich@(vitavonni.de|debian.org) -- GPG Key ID: 4B3A135C (o_
    There is no branch of mathematics, however abstract, which may not //\
    some day be applied to phenomena of the real world. --- Lobatchevsky V_/_
    Für jedes Problem gibt es eine Lösung,
    die einfach, klar und falsch ist.

  9. Re: Re: KDE 3.5 Release Candidate 1 packages available on alioth

    * Erich Schubert [Sat, 26 Nov 2005 01:21:54 +0100]:

    > I disagree for some reasons:


    [snip]

    That reasons may be better understood after reading the following IRC
    snippet:

    01:01 grmpf. why did they rebuild kde and upload it to
    experimental, but not using dbus from experimental?
    01:02 erich: http://lists.debian.org/debian-kde/2.../msg00072.html
    01:04 dato: yeah, but I'm now just going to uninstall kde,
    since I want to test the new gnome, which uses the new
    dbus...
    01:05 they're just making the whole transition of the new dbus
    harder by not testing with it yet.
    01:07 haha, no.
    01:07 the gnome team has it easy 'cause they know that, whenever
    they want to push the version of gnome in experimental to
    unstable, the new dbus will have been uploaded to sid in
    advance.
    01:07 (cause they work together/are the same people/etc.)
    01:08 otoh, if the kde team wants to have liberty on when to
    upload to unstable, they (we) can't depend on the new dbus
    on experimental: what if when we want the new KDE in sid
    dbus is not ready? users would be forced to go back to the
    old one.
    01:09 erich: you may have a bit of a point; for that, get in
    touch with Christopher, e.g. by replying to that message.

    --
    Adeodato Simó dato at net.com.org.es
    Debian Developer adeodato at debian.org

    Listening to: Elton John - Turn the lights out when you leave


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

  10. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Adeodato Simó wrote:
    > * Erich Schubert [Sat, 26 Nov 2005 01:21:54 +0100]:
    >
    >
    >>I disagree for some reasons:

    >
    >
    > [snip]
    >
    > That reasons may be better understood after reading the following IRC
    > snippet:
    >
    > 01:01 grmpf. why did they rebuild kde and upload it to
    > experimental, but not using dbus from experimental?
    > 01:02 erich: http://lists.debian.org/debian-kde/2.../msg00072.html
    > 01:04 dato: yeah, but I'm now just going to uninstall kde,
    > since I want to test the new gnome, which uses the new
    > dbus...
    > 01:05 they're just making the whole transition of the new dbus
    > harder by not testing with it yet.
    > 01:07 haha, no.
    > 01:07 the gnome team has it easy 'cause they know that, whenever
    > they want to push the version of gnome in experimental to
    > unstable, the new dbus will have been uploaded to sidin
    > advance.
    > 01:07 (cause they work together/are the same people/etc.)
    > 01:08 otoh, if the kde team wants to have liberty on when to
    > upload to unstable, they (we) can't depend on the newdbus
    > on experimental: what if when we want the new KDE in sid
    > dbus is not ready? users would be forced to go back to the
    > old one.
    > 01:09 erich: you may have a bit of a point; for that, get in
    > touch with Christopher, e.g. by replying to that message.
    >


    I completely agree with Eric. In addition I tested the 3.5-rc1 packages
    from alioth, rebuilt kdebase inside a unstable chroot with hal/dbus from
    experimental and all I had to do was a 1 line fix in debian/control. KDE
    3.5 directly supports newer hal/dbus and doesn't need this huge patch
    that is currently needed for Ubuntu Breezy. The package built without a
    problem and so far KDE 3.5 runs just fine here. (The only issue I could
    find is, that konqueror doesn't display local partitions in media:/ if
    you don't run hal with retain-privileges).
    For K3B and other packages I currently use (bluez-utils, tomboy, ..) the
    recompilation was easy as with kdebase.

    Although I can understand Adeato's concerns I think they would only
    apply if KDE 3.5 wanted to enter unstable before Gnome 2.12 which is
    unlikely given the time of testing that Gnome 2.12 already got and KDE
    3.5 not even released yet.
    IMHO now would be the right time to switch the hal/dbus packages to the
    ones in experimental. I mean what would be your alternatives: ship KDE
    3.5 for unstable compiled with the old hal/dbus packages conflicting
    with Gnome 2.12 which would require an additional transtion? Maybe you
    could outline your plans on how you want to tackle this issue.


    Cheers,
    Michael

    --
    Why is it that all of the instruments seeking intelligent life in the
    universe are pointed away from Earth?


    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

    iD8DBQFDiDTYh7PER70FhVQRAvI9AJ9Kt8YVWGgW5Lc1dRQYrc gnsP5g0QCfRayd
    T8LzbqWagBch+BpYRYc7u8Y=
    =vwRd
    -----END PGP SIGNATURE-----


  11. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Hi,

    i'm having a problem with the amd64 packages provided by mikmak. Kontact
    simply explodes whenever i try to send a mail from the kmail part. It doesn't
    even show up the backtrace window... From kmail it seems to run fine.

    anyone else has had problems with this?

    Rafael Rodríguez

  12. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Le Saturday 26 November 2005 11:41, Rafael Rodríguez(Rafael Rodríguez
    ) disait:
    > Hi,


    Hi,

    > anyone else has had problems with this?


    I have the same issu...
    Is there a fix?
    --
    Glennie
    "La vie offre toujours deux pentes. On grimpe ou on se laisse
    glisser."

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)

    iQEVAwUAQ4hmyNHiioqkksXaAQLKNggAls2hzuTIcozI06u6Fz bpLMnGJwzzz/3v
    3xkhIB0zseaeQgmHm3Gn/YLh/S4J8CQ13GgC4QF5+Xub60oxs6qZkjqWuc7w6cva
    rWLyptEgSlNuh2MeGklnmhUpuvIChmfdBZLKarNOgTmFMoYBa5 f1wCrmYN9nxhaZ
    10xFG0vsOxcFgN+FqkkQCy0zAl2j3ZI8OHoaBB06pqHRb1xNxK IzArCOuwq2UflE
    s3scp4r/sK7fl2l38LqJtdwWJLtU0wbSemIr0Nv+8y9iNOVIQhIfwEP98E NE/msc
    OTKGLAj/lv5xXh69p1lcxskDjBwwP1ZJXVPPaUwKiIoqpvd7tieYRQ==
    =ibbC
    -----END PGP SIGNATURE-----


  13. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Your reasons for wanting kdebase to be rebuilt with experimental dbus/hal
    seem mainly to boil down to a desire to run both GNOME and KDE from
    experimental. While there is nothing wrong with wanting this, I still don't
    find that sufficient to overrule the other reasons I have stated for
    preferring to test kdebase against the old dbus/hal.

    Moreover, the general principle you seem to be hinting at of "stuff in
    experimental should be built against other experimental stuff" is very
    rarely practiced - experimental uploads are usually there to be
    cherry-picked for use with Sid. Experimental is not a real distribution
    that most people run in its entirety. Otherwise we'd be building against
    any random updated library that happened to be there as well as dbus/hal.

    FWIW, Ubuntu (and many other distributions) will be building their KDE
    against the new dbus/hal, so if there are critical problems, we will find
    out through them.

    However, if it does appear that the new dbus/hal will enter unstable before
    3.5.0, then the case for building 3.5 against the new dbus/hal becomes much
    stronger. We'll see.

    Also, if for the next round of 3.5 uploads to alioth (when 3.5 arrives at
    3.5.0 final), someone (a DD or a well-known Debian contributor) wants to
    provide alternate kdebase/k3b debs built against the new dbus/hal, I can't
    see the harm in them being made available somewhere. Someone could do that
    right now, in fact.

    Cheers,
    Christopher Martin

    On November 25, 2005 19:21, Erich Schubert wrote:
    > I disagree for some reasons:
    > - People testing stuff from experimental will probably also want to test
    > DBUS and GNOME from experimental. After all, they are brave experimental
    > testers! Currently this means uninstalling KDE (which I just did.)
    > - New DBus will enter unstable some time, too, you know. You should also
    > test KDE with the new DBus, why don't you do it at the same time?
    > - Gnome 2.12 has been sitting in experimental for a month now - they
    > will probably upload to unstable soon, too? Especially since they aren't
    > affected much by the C++ allocator changes I think.
    > - Gnome 2.12 was shipped with Ubuntu Breezy, so it has received a
    > *serious* amount of testing already on a Debian-based system
    > - Downgrading dbus from experimental to unstable shouldn't be hard,
    > *because* the package names have changed and they conflict... so once you
    > upload KDE packages to unstable, even with an old dbus, a simple "apt-get
    > install kde dbus-1" should install the new KDE and the old dbus again.
    > They'll only get conflicts if they have other dbus-related stuff (read:
    > gnome from experimental) installed. In that case they can just stick with
    > the experimental version...
    >
    > > removal/reinstallation. Besides rebuilding kdebase, we'd have to
    > > rebuild k3b, since it also uses the old dbus/hal in unstable.

    >
    > K3B is actually the only reason (apart rare konqueror webpage tests) why
    > I have parts of KDE installed... So I'd prefer to have it built with
    > experimental DBUS, too... ;-)


    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.2 (GNU/Linux)
    Comment: Signed by Christopher Martin

    iD8DBQBDib2lU+gWW+vtsysRApu9AJsH9bo133eFPZcawh0hMc sXEJrCGgCgneXg
    PPbSIACwqXeNbu6fW5dJDQc=
    =oqPp
    -----END PGP SIGNATURE-----


  14. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Glennie Vignarajah a écrit :
    > Le Saturday 26 November 2005 11:41, Rafael Rodríguez(Rafael Rodríguez
    > ) disait:
    >
    >>Hi,

    >
    >
    > Hi,
    >
    >
    >>anyone else has had problems with this?

    >
    >
    > I have the same issu...
    > Is there a fix?


    try installing *-dbg to get a backtrace maybe

    Cheers,
    Mik


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

  15. Re: KDE 3.5 Release Candidate 1 packages available on alioth

    Rafael Rodríguez wrote:
    > what's the usual place?
    >
    > i can't find anything in ftp://ftp-fourier.ujf-grenoble.fr/debian/
    >
    > I'm too asleep maybe?
    >
    > Rafael Rodríguez
    >


    as I said it was still compiling,
    now finished

    Cheers,
    Mik


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

+ Reply to Thread