On 8 August 2011 06:42, andre999 and...@laposte.net wrote:
Everything seemed to install ok, but when I try to run a gui application
(such as rpmdrake) under chroot, I get the message :
No protocol specified
Cannot be run in console mode.
Which is expected
If anyone has an idea what I might
Hi
I think we should do a security update of chromium-browser-stable
that would be a backport of cauldron's chromium-browser-stable.
WDYT?
See you
Le mardi 9 août 2011 07:21:43, Thierry Vignaud a écrit :
Hi
I think we should do a security update of chromium-browser-stable
that would be a backport of cauldron's chromium-browser-stable.
WDYT?
it should be push as an update and not a backport.
eventually the beta unstable could be pushed
09.08.2011 13:21, Thierry Vignaud kirjutas:
Hi
I think we should do a security update of chromium-browser-stable
that would be a backport of cauldron's chromium-browser-stable.
WDYT?
See you
Finally someone is thinking about it :) Yes, of course! We have version
11 when there is version 13
Hi,
As someone may have seen, the BS is broken. We have identified the cause of
breakage and will fix it (if we manage to reach someone in sysadmin team).
Please be patient.. :)
--
Jani Välimaa
BS is borked.
Every build failed on initializing the chroot.
eg:
http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20110809113922.tv.valstar.8603/log/chroot/
Can someone fixes it and reupload failed uploads?
Thx
Upgrade in cauldron is broken, check the output:
~]# LC_ALL=C urpmi --noclean --auto-select
In order to satisfy the 'libpeas-gtk-1.0.so.0()(64bit)' dependency,
one of the following packages is needed:
1- lib64peas-gtk1.0_0-1.1.1-1.mga2.x86_64: Library plugin handling UI
part (to install)
2-
2011/8/9 Zé mmode...@gmail.com:
Upgrade in cauldron is broken, check the output:
~]# LC_ALL=C urpmi --noclean --auto-select
In order to satisfy the 'libpeas-gtk-1.0.so.0()(64bit)' dependency,
one of the following packages is needed:
1- lib64peas-gtk1.0_0-1.1.1-1.mga2.x86_64: Library plugin
Thanks for fixing the spec file and submit the package.
I have a comment and a few questions. First the comment.
an experienced packager telling someone like me (and others not so experienced
packagers) why the package build failed that built just a few month ago would
have helped learning how
Thomas Spuhler a écrit :
Thanks for fixing the spec file and submit the package.
I have a comment and a few questions. First the comment.
an experienced packager telling someone like me (and others not so experienced
packagers) why the package build failed that built just a few month ago would
10 matches
Mail list logo
