On Wed, 20 Jun 2001, Vincent Danen wrote:
How many more times should I report this bug? :-(
Exactly when did you report the bug? Is it possible the packages were
built prior to your reporting the bug? Did you check the cooker
packages?
rpm -qip the kdelibs packages and see if
On Thu Jun 21, 2001 at 02:52:16PM +0100, Michael Brown wrote:
How many more times should I report this bug? :-(
Exactly when did you report the bug? Is it possible the packages were
built prior to your reporting the bug? Did you check the cooker
packages?
rpm -qip the
On Thu, 21 Jun 2001, Vincent Danen wrote:
QA process is not a 24hr deal... =) It sometimes takes a little bit
longer, and kdelibs is a big package that needs thorough testing
(this isn't cooker we're talking about!). So the delay is not in
mirroring, but in QA. We could do it
On Thu Jun 21, 2001 at 08:12:41PM +0100, Michael Brown wrote:
QA process is not a 24hr deal... =) It sometimes takes a little bit
longer, and kdelibs is a big package that needs thorough testing
(this isn't cooker we're talking about!). So the delay is not in
mirroring, but in
On Thu, 21 Jun 2001, Vincent Danen wrote:
I just checked, and kdelibs in cooker is 2.2-0.alpha2... I don't know
how we can get kdelibs 2.1.2 into cooker without causing even more
problems... =) Remember, cooker moves fast and usually has the latest
and greatest... versions that we
On Fri Jun 22, 2001 at 02:09:08AM +0100, Michael Brown wrote:
I don't see how this will help. Security/bugfix updates are not
open packages or public packages until they are published. In
many cases, non-public bugs (security) are being fixed... making this
available to cooker will
Notice the build date? If his report was made *after* June the 3rd,
then it is obvious why it's not fixed in this package.
Still, you could refrain from public release of a build that is *known* to
be broken. -3mdk appeared on mirrors just yesterday and not June the 4th. It
is different
On Wednesday 20 June 2001 05:41, you wrote:
Thanks for the absolutely incorrect assumptions, gurun.
My writing was based on the observation, that the official treatment of a
bug-report was abandoned, i.e.
1) bug-report
2) is the bug reproduced, that is real
3) give it a bug number
One
On Wednesday 20 June 2001 10:41, you wrote:
On 19 Jun 2001, Daouda LO wrote:
Anyway, I'll take care of this. Expect 4mdk by the end of this
week.
Good. In case it got lost in the noise, remember to also fix the two
dependency problems (libarts2 need kdelibs and kdelibs needs
libglib2)
David,
Was wondering if there's an estamated date for KDE beta 1? Also,
will kpackage fixes have to wait until then?
Vinny.
On Wednesday 20 June 2001 13:40, you wrote:
So, no KDE packages will be uploaded before KDE 2.2.beta1 announce.
There are too many changes between
On Thursday 21 June 2001 01:41, you wrote:
David,
Was wondering if there's an estamated date for KDE beta 1?
http://developer.kde.org/development-versions/kde-2.2-release-plan.html
Sources: tarballs will be made on Monday
Binaries: RPMS for 7.2, 8.0 i586 and PPC will be available on
On Thu Jun 21, 2001 at 12:22:46AM +0100, Michael Brown wrote:
How many more times should I report this bug? :-(
Exactly when did you report the bug? Is it possible the packages were
built prior to your reporting the bug? Did you check the cooker
packages?
rpm -qip the kdelibs
On 19 Jun 2001, Daouda LO wrote:
Anyway, I'll take care of this. Expect 4mdk by the end of this week.
Good. In case it got lost in the noise, remember to also fix the two
dependency problems (libarts2 need kdelibs and kdelibs needs libglib2)
and the duplicate libqtmcop.so*, as in my patch
On Tue, 19 Jun 2001, Vincent Danen wrote:
Easy to resolve for those who know what they're doing. Now, picture the
newbie to Mandrake who got talked into it by one of us trying to figure out
why their sound just won't work after they did exactly what they were taught
and trusted
Arnd Bergmann [EMAIL PROTECTED] writes:
On 19 Jun 2001, Daouda LO wrote:
Anyway, I'll take care of this. Expect 4mdk by the end of this week.
Good. In case it got lost in the noise, remember to also fix the two
dependency problems (libarts2 need kdelibs and kdelibs needs libglib2)
On Mon, 18 Jun 2001, Timothy Wagner wrote:
Easy to resolve for those who know what they're doing. Now, picture the
newbie to Mandrake who got talked into it by one of us trying to figure out
why their sound just won't work after they did exactly what they were taught
and trusted only
On Mon, 18 Jun 2001, Timothy Wagner wrote:
Easy to resolve for those who know what they're doing. Now, picture the
newbie to Mandrake who got talked into it by one of us trying to figure out
why their sound just won't work after they did exactly what they were taught
and trusted only
On Tue Jun 19, 2001 at 07:12:05PM +0100, Michael Brown wrote:
Easy to resolve for those who know what they're doing. Now, picture the
newbie to Mandrake who got talked into it by one of us trying to figure out
why their sound just won't work after they did exactly what they were taught
On Tuesday 19 June 2001 20:16, you wrote:
How many more times should I report this bug? :-(
Exactly when did you report the bug? Is it possible the packages were
built prior to your reporting the bug? Did you check the cooker
packages?
Very interesting attitude - the Mandrake staff
On Tue Jun 19, 2001 at 10:01:18PM +0200, guran wrote:
How many more times should I report this bug? :-(
Exactly when did you report the bug? Is it possible the packages were
built prior to your reporting the bug? Did you check the cooker
packages?
Very interesting attitude - the
20 matches
Mail list logo
