Re: [Mageia-dev] Versions freeze

[Michael Scherer]

Le vendredi 02 mars 2012 à 20:53 +0100, Maarten Vanraes a écrit :
> Op vrijdag 02 maart 2012 20:16:11 schreef Thomas Backlund:
> > 02.03.2012 21:08, Dimitri Jakov skrev:
> > > Besides... GNOME 3.4 is going to be released on March 28 - does that
> > 
> > Yes we know...
> > 
> > > mean that we won't be able to ship it with Mageia 2?
> > 
> > Nope, we have that as an exception to the freeze...
> > (that's why we already run 3.3.x)
> > 
> > we will have Gnome 3.4.x and KDE 4.8.x in Mageia 2
> 
> also, I hope mariadb-5.5.x final (right now we have 5.5.20 which is the alpha 
> version; beta will come quite soon, then the rc and finals follow pretty fast 
> and these only contain bugfixes)

Next time, maybe waiting for the beta would be better, cauldron is not
mean to be a playground for testing upstream softwares when we do not
have a strong assurance that the stable will end i the stable release.

If everybody start to do that, we spend more time on upgrading to
version that should have been stable than fixing others bugs.

And if upstream could also try to be a little bit less original and
follow some easy to grasp convetion about version number.

-- 
Michael Scherer

Re: [Mageia-dev] Versions freeze

[Thomas Backlund]

03.03.2012 11:24, Michael Scherer skrev:
> Le vendredi 02 mars 2012 à 20:53 +0100, Maarten Vanraes a écrit :
>> Op vrijdag 02 maart 2012 20:16:11 schreef Thomas Backlund:
>>> 02.03.2012 21:08, Dimitri Jakov skrev:
 Besides... GNOME 3.4 is going to be released on March 28 - does that
>>>
>>> Yes we know...
>>>
 mean that we won't be able to ship it with Mageia 2?
>>>
>>> Nope, we have that as an exception to the freeze...
>>> (that's why we already run 3.3.x)
>>>
>>> we will have Gnome 3.4.x and KDE 4.8.x in Mageia 2
>>
>> also, I hope mariadb-5.5.x final (right now we have 5.5.20 which is the 
>> alpha 
>> version; beta will come quite soon, then the rc and finals follow pretty 
>> fast 
>> and these only contain bugfixes)
> 
> Next time, maybe waiting for the beta would be better, cauldron is not
> mean to be a playground for testing upstream softwares when we do not
> have a strong assurance that the stable will end i the stable release.
> 

Actually in this case it is ok, since we've been tracking upstream 5.5.x
branch with the target for 5.5.x final, so "alpha" in this case
only means fully synced with mysql 5.5 and afaik all intended mariadb
patches merged...

They are only a bit late :/


> If everybody start to do that, we spend more time on upgrading to
> version that should have been stable than fixing others bugs.
> 
> And if upstream could also try to be a little bit less original and
> follow some easy to grasp convetion about version number.
> 

Re: [Mageia-dev] Versions freeze

[Michael Scherer]

Le vendredi 02 mars 2012 à 16:06 +0100, Johnny A. Solbu a écrit :
> On Friday 02 March 2012 15:31, Wolfgang Bornath wrote:
> > Back in my school days when we had to do a home work project of 1
> > month our teacher used to remind us the day before scheduled deadline
> > - for people like me it meant to start working on the project!
> > 
> > Some people may be like me...
> 
> Maybe we should have a policy on when to remind developers on version freezes.
> Say, one or two weeks before the freeze, so they get a chance to submit final 
> changes.

We reminded there is version freeze coming during meetings ( like
http://meetbot.mageia.org/mageia-dev/2012/mageia-dev.2012-02-15-20.13.log.html#l-75
 ), or what is the plan until the release ( 
http://meetbot.mageia.org/mageia-dev/2012/mageia-dev.2012-01-26-20.03.html ). 
We gave the list of date in advance
( https://wiki.mageia.org/en/Mageia_2_development ) and a link to the
planning in every mail of announce, as well in blog posts and forums
post.

We have a calendar ( http://www.mageia.org/en/calendar/ ), where the
freeze was given.  

And I expect people to either be experienced packager ( ie who have
already done 1 release and so know the rules ), or to be new packagers
with a experienced packager ( ie mentor ) who should have explained the
release cycle. 

So if people have missed the whole plan, there is a problem that we need
to fix, and the first step would be to collect reasons why they did
missed it, not nag more everybody on every possible channels.

For people who didn't miss and who read the mails etc, the reminder are
annoying and the more reminder we put, the more they will start to
ignore them. And I see no reason to annoy those that do the job and
follow thing to help those that don't. 

So if someone want to start collecting feedback, digesting it and
present it, just say that you are volunteer on the list, and start the
collect.

-- 
Michael Scherer

Re: [Mageia-dev] Versions freeze

[Sander Lepik]

03.03.2012 11:42, Michael Scherer kirjutas:

We have a calendar ( http://www.mageia.org/en/calendar/ ), where the
freeze was given.
Weird, if i add this calendar into my google calandar or into Thunderbird, i see no events 
from it. Some settings are wrong?


And now the reason why i started this thread: i was not sure if this date is confirmed. As 
you can see from https://wiki.mageia.org/en/Mageia_2_development there have been delays. How 
do i know that this will really happen?


Maybe we can use something like Mozilla is doing for their releases 
(https://wiki.mozilla.org/Features/Release_Tracking) - i mean some status/health field that 
would say if the date is confirmed or the date is at risk for some reason. Then no reminders 
are needed but i can be sure that this date will stick.


--
Sander

Re: [Mageia-dev] Updating the lm_sensors package with a new "sensors-detect" script without a new lm_sensors version

[Jani Välimaa]

2012/3/2 Jeff Robins :
> Hello,
>
> Bug 4095 ( https://bugs.mageia.org/show_bug.cgi?id=4095) asks that we
> update the version of the "sensors-detect" script in the lm_sensors
> package.
>
> I have checked with the lm_sensors people (Jean Delvare) and this
> should be safe.  They are working on a new version of the lm_sensors
> code, but were
> "delayed by a last minute bug (not in sensors-detect.)"
>
> I would normally prefer to wait for the new version, but Jean is busy
> with other issues at the moment and I know we're coming up on version
> freeze.
>
> Any thoughts?
>

Update script, bump release and submit..

Re: [Mageia-dev] executable libraries

[Guillaume Rousse]

Le 02/03/2012 22:01, Per Øyvind Karlsen a écrit :

Den 21:51 2. mars 2012 skrev Maarten Vanraes  følgende:

Op vrijdag 02 maart 2012 21:29:05 schreef Anssi Hannula:

02.03.2012 21:57, Maarten Vanraes kirjoitti:

Op vrijdag 02 maart 2012 15:22:23 schreef Anssi Hannula:

02.03.2012 00:17, Maarten Vanraes kirjoitti:

Op donderdag 01 maart 2012 23:05:35 schreef Anssi Hannula:
[...]


does this mean debug info fails for these?


I'm not immediately sure (I never remember how the debug/stripping
stuff works exactly), but I think either a) debug symbols extraction
and thus -debug packaging, b) stripping, or c) both will fail with
non-executable shared libs.


in that case i guess we would need a policy or bs check to make sure we
don't fail some libraries debug and strip


Possibly.

Interestingly, Debian policy disallows executable permission on shared
libs:
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-
ru ntime

"Shared libraries should not be installed executable, since the dynamic
linker does not require this and trying to execute a shared library
usually results in a core dump."


which is sort of strange, since libc is actually executable by design.

i see where they are coming from

but i guess the first part of this is, why is there a find with
executable restrictions for the code relating to stripped binaries and
debug?

is it because it's also used for real executables?


I guess it is there just to speed up the process, otherwise it would
have to run 'file' for every file in the package (and many packages have
lots of files).


still, it seems kind of weird, there are rpmlint checks for unstripped
libraries, but i do have 34 libraries not marked as executable, while the
stripping+ debug seems to target only executables?

i wonder if we should make another check library unset as executable or even
check what happened with these libraries not marked as executable?

I posted a link to a rpmlint patch implementing such a check to this thread two
hours ago.. :p
I don't much point to a check, when a rpm-helper scriptlet would be able 
to automatically enforce any given permission set.


--
Mines are equal opportunity weapons
-- Murphy's Military Laws n°55

[Mageia-dev] BS broken ?

[Luc Menut]

Hello,

The BS seems broken; I submitted this morning kdebase4-workspace, and 
the build is still in progress (4 hours after). Same thing with 
gnuradio-3.5.1-8.mga2 i586 (12 hours).
It seems that the BS indefinitely retries to build kdebase4-workspace 
(on http://pkgsubmit.mageia.org/, the build machine regularly changes).



regards,
Luc

--
Luc Menut

Re: [Mageia-dev] BS broken ?

[Thomas Backlund]

03.03.2012 15:04, Luc Menut skrev:
> Hello,
> 
> The BS seems broken; I submitted this morning kdebase4-workspace, and 
> the build is still in progress (4 hours after). Same thing with 
> gnuradio-3.5.1-8.mga2 i586 (12 hours).
> It seems that the BS indefinitely retries to build kdebase4-workspace 
> (on http://pkgsubmit.mageia.org/, the build machine regularly changes).
> 

I will kill all builds on both nodes as soon as new glibc is uploaded,
and force recreation of all cauldron chroots...

--
Thomas

Re: [Mageia-dev] BS broken ?

[Luc Menut]

Le 03/03/2012 14:04, Luc Menut a écrit :

Hello,

The BS seems broken; I submitted this morning kdebase4-workspace, and
the build is still in progress (4 hours after). Same thing with
gnuradio-3.5.1-8.mga2 i586 (12 hours).
It seems that the BS indefinitely retries to build kdebase4-workspace
(on http://pkgsubmit.mageia.org/, the build machine regularly changes).



I just tried to build locally  kdebase4-workspace in iurt: urpmi fails 
to install BuildRequires.


After 657/764 installed packages:
[...]
starting installing packages
created transaction for installing on / (remove=0, install=0, upgrade=8)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Basenames index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Group index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Requirename index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Triggername index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Dirnames index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Installtid index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Sigmd5 index using db4 - Cannot allocate memory (12)
error: rpmdb: Lock table is out of available locker entries
error: cannot open Sha1header index using db4 - Cannot allocate memory (12)

[...]

...retrieving done
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages index using db4 - Cannot allocate memory (12)
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm

[...]

error: rpmdb: Lock table is out of available locker entries
error: cannot open Packages database in /var/lib/rpm
unable to open rpmdb
I: [iurt_root_command] ERROR: chroot

I: [iurt2] [iurt2] --- end of command output ---

[...]


It seems a pb with rpm.


--
Luc Menut

Re: [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates

[Wolfgang Bornath]

2012/3/3 Wolfgang Bornath :
> 2012/3/3 Barry Jackson :
>> On 02/03/12 16:53, Wolfgang Bornath wrote:
>>>
>>> 2012/3/2 Wolfgang Bornath:

 whould be fixed with coming updates.
>>>
>>>
>>> should be fixed
>>> Sorry.
>>>
>> Seems this was not the problem for you, but my FX series card has had no
>> nvidia available since x11 was updated before Christmas.
>> I think I need a new graphic card :(
>
> Well, I don't know, but after last update tonight (mirror sync status
> 23:01 Paris time) the complete system which was working fine is now
> hosed anyway.
>
> 1. Nouveau driver still there (although I tried with XFdrake to get
> the nvidia re-installed), but that did not make my system unusable
> before
> 2. wifi connection totally lost (not possible to get a connection,
> whichever way I tried)
> 3. After system start the system now displays a message that it can
> not start Gnome 3 because my graphic system is possibly not able to
> run in normal Gnome 3, so it starts in a somehow "compatibility mode".
> /etc/X11/xorg.conf shows that the nouveau driver is working, which
> never had problems with Gnome 3.
> 4. I switched to tty2, and was presented with my keyboard now writing
> in black! Trying to write 'asdf' does not show any character but
> hitting enter returns 'asdf: command not found"
>
> Points 2, 3, 4 occurred at reboot after the update.
> I'll call it a day...

After todays updates the issues are resolved:

1. After reconfiguring X and reboot the proprietary driver was
accepted and Gnome 3 started without problems
2. After removing all net connections and recreating wlan0 (in MCC
without enabling networkmanager) wifi is working again
3. Input on ttys is back to white on black

-- 
wobo

Re: [Mageia-dev] BS broken ?

[Luc Menut]

Le 03/03/2012 14:06, Thomas Backlund a écrit :

03.03.2012 15:04, Luc Menut skrev:

Hello,

The BS seems broken; I submitted this morning kdebase4-workspace, and
the build is still in progress (4 hours after). Same thing with
gnuradio-3.5.1-8.mga2 i586 (12 hours).
It seems that the BS indefinitely retries to build kdebase4-workspace
(on http://pkgsubmit.mageia.org/, the build machine regularly changes).



I will kill all builds on both nodes as soon as new glibc is uploaded,
and force recreation of all cauldron chroots...



OK, you can kill kdebase4-workspace's builds immediately if you want to 
free build nodes; they won't build with the current chroot.



--
Luc Menut

Re: [Mageia-dev] BS broken ?

[Thomas Spuhler]

On Saturday, March 03, 2012 06:56:25 AM Luc Menut wrote:
> Le 03/03/2012 14:06, Thomas Backlund a écrit :
> > 03.03.2012 15:04, Luc Menut skrev:
> >> Hello,
> >> 
> >> The BS seems broken; I submitted this morning kdebase4-workspace, and
> >> the build is still in progress (4 hours after). Same thing with
> >> gnuradio-3.5.1-8.mga2 i586 (12 hours).
> >> It seems that the BS indefinitely retries to build kdebase4-workspace
> >> (on http://pkgsubmit.mageia.org/, the build machine regularly changes).
> > 
> > I will kill all builds on both nodes as soon as new glibc is uploaded,
> > and force recreation of all cauldron chroots...
> 
> OK, you can kill kdebase4-workspace's builds immediately if you want to
> free build nodes; they won't build with the current chroot.

I have been trying to build php-pear-horde pacakges for a week w/o success.
It seems theBS cannot find the horde-pear-channel. I kept waiting since it was 
in fact down for some time, but it builds locally as well as on the mdv bs.
Thas the BS lost dns service?
-- 
Best regards
Thomas Spuhler

Re: [Mageia-dev] BS broken ?

[Pascal Terjan]

On Sat, Mar 3, 2012 at 15:21, Thomas Spuhler  wrote:
> On Saturday, March 03, 2012 06:56:25 AM Luc Menut wrote:
>> Le 03/03/2012 14:06, Thomas Backlund a écrit :
>> > 03.03.2012 15:04, Luc Menut skrev:
>> >> Hello,
>> >>
>> >> The BS seems broken; I submitted this morning kdebase4-workspace, and
>> >> the build is still in progress (4 hours after). Same thing with
>> >> gnuradio-3.5.1-8.mga2 i586 (12 hours).
>> >> It seems that the BS indefinitely retries to build kdebase4-workspace
>> >> (on http://pkgsubmit.mageia.org/, the build machine regularly changes).
>> >
>> > I will kill all builds on both nodes as soon as new glibc is uploaded,
>> > and force recreation of all cauldron chroots...
>>
>> OK, you can kill kdebase4-workspace's builds immediately if you want to
>> free build nodes; they won't build with the current chroot.
>
> I have been trying to build php-pear-horde pacakges for a week w/o success.
> It seems theBS cannot find the horde-pear-channel. I kept waiting since it was
> in fact down for some time, but it builds locally as well as on the mdv bs.
> Thas the BS lost dns service?

What is failing exactly?
DNS seem to be working fine.

Re: [Mageia-dev] BS broken ?

[Thomas Spuhler]

On Saturday, March 03, 2012 08:26:40 AM Pascal Terjan wrote:
> On Sat, Mar 3, 2012 at 15:21, Thomas Spuhler  wrote:
> > On Saturday, March 03, 2012 06:56:25 AM Luc Menut wrote:
> >> Le 03/03/2012 14:06, Thomas Backlund a écrit :
> >> > 03.03.2012 15:04, Luc Menut skrev:
> >> >> Hello,
> >> >> 
> >> >> The BS seems broken; I submitted this morning kdebase4-workspace, and
> >> >> the build is still in progress (4 hours after). Same thing with
> >> >> gnuradio-3.5.1-8.mga2 i586 (12 hours).
> >> >> It seems that the BS indefinitely retries to build kdebase4-workspace
> >> >> (on http://pkgsubmit.mageia.org/, the build machine regularly
> >> >> changes).
> >> > 
> >> > I will kill all builds on both nodes as soon as new glibc is uploaded,
> >> > and force recreation of all cauldron chroots...
> >> 
> >> OK, you can kill kdebase4-workspace's builds immediately if you want to
> >> free build nodes; they won't build with the current chroot.
> > 
> > I have been trying to build php-pear-horde pacakges for a week w/o
> > success. It seems theBS cannot find the horde-pear-channel. I kept
> > waiting since it was in fact down for some time, but it builds locally
> > as well as on the mdv bs. Thas the BS lost dns service?
> 
> What is failing exactly?
> DNS seem to be working fine.

The logs say:
Unknown channel "pear.horde.org"

but locally I get 
[root@localhost ~]# pear list-upgrades
WARNING: channel "pear.horde.org" has updated its protocols, use "pear 
channel-update pear.horde.org" to update
pear.horde.org Available Upgrades (stable):
===
ChannelPackage   Local  Remote Size
pear.horde.org Horde_ActiveSync  1.2.3 (stable) 1.2.4 (stable) 87kB
pear.horde.org Horde_Crypt   1.1.0 (stable) 1.1.1 (stable) 135kB
pear.horde.org Horde_Data1.0.4 (stable) 1.0.5 (stable) 31kB
pear.horde.org Horde_Group   1.0.4 (stable) 1.0.5 (stable) 21kB
pear.horde.org Horde_Http1.1.0 (stable) 1.1.1 (stable) 11.8kB
pear.horde.org Horde_Imap_Client 1.4.3 (stable) 1.5.1 (stable) 134kB
pear.horde.org Horde_Itip1.0.6 (stable) 1.0.7 (stable) 33kB
pear.horde.org Horde_Mail1.0.3 (stable) 1.1.0 (stable) 21kB
pear.horde.org Horde_Memcache1.0.4 (stable) 1.0.5 (stable) 13.2kB
pear.horde.org Horde_Rdo 1.1.0 (stable) 1.1.1 (stable) 30kB
pear.horde.org Horde_Support 1.0.1 (stable) 1.0.2 (stable) 22kB

So it seems the channel is up and working

-- 
Best regards
Thomas Spuhler

Re: [Mageia-dev] BS broken ?

[Thomas Backlund]

03.03.2012 17:38, Thomas Spuhler skrev:
> On Saturday, March 03, 2012 08:26:40 AM Pascal Terjan wrote:
>> On Sat, Mar 3, 2012 at 15:21, Thomas Spuhler  wrote:
>>> On Saturday, March 03, 2012 06:56:25 AM Luc Menut wrote:
 Le 03/03/2012 14:06, Thomas Backlund a écrit :
> 03.03.2012 15:04, Luc Menut skrev:
>> Hello,
>>
>> The BS seems broken; I submitted this morning kdebase4-workspace, and
>> the build is still in progress (4 hours after). Same thing with
>> gnuradio-3.5.1-8.mga2 i586 (12 hours).
>> It seems that the BS indefinitely retries to build kdebase4-workspace
>> (on http://pkgsubmit.mageia.org/, the build machine regularly
>> changes).
>
> I will kill all builds on both nodes as soon as new glibc is uploaded,
> and force recreation of all cauldron chroots...

 OK, you can kill kdebase4-workspace's builds immediately if you want to
 free build nodes; they won't build with the current chroot.
>>>
>>> I have been trying to build php-pear-horde pacakges for a week w/o
>>> success. It seems theBS cannot find the horde-pear-channel. I kept
>>> waiting since it was in fact down for some time, but it builds locally
>>> as well as on the mdv bs. Thas the BS lost dns service?
>>
>> What is failing exactly?
>> DNS seem to be working fine.
> 
> The logs say:
> Unknown channel "pear.horde.org"
> 
> but locally I get 
> [root@localhost ~]# pear list-upgrades
> WARNING: channel "pear.horde.org" has updated its protocols, use "pear 
> channel-update pear.horde.org" to update
> pear.horde.org Available Upgrades (stable):
> ===
> ChannelPackage   Local  Remote Size
> pear.horde.org Horde_ActiveSync  1.2.3 (stable) 1.2.4 (stable) 87kB
> pear.horde.org Horde_Crypt   1.1.0 (stable) 1.1.1 (stable) 135kB
> pear.horde.org Horde_Data1.0.4 (stable) 1.0.5 (stable) 31kB
> pear.horde.org Horde_Group   1.0.4 (stable) 1.0.5 (stable) 21kB
> pear.horde.org Horde_Http1.1.0 (stable) 1.1.1 (stable) 11.8kB
> pear.horde.org Horde_Imap_Client 1.4.3 (stable) 1.5.1 (stable) 134kB
> pear.horde.org Horde_Itip1.0.6 (stable) 1.0.7 (stable) 33kB
> pear.horde.org Horde_Mail1.0.3 (stable) 1.1.0 (stable) 21kB
> pear.horde.org Horde_Memcache1.0.4 (stable) 1.0.5 (stable) 13.2kB
> pear.horde.org Horde_Rdo 1.1.0 (stable) 1.1.1 (stable) 30kB
> pear.horde.org Horde_Support 1.0.1 (stable) 1.0.2 (stable) 22kB
> 
> So it seems the channel is up and working
> 

Chroots build without dns support, as everything built must be provided
by the repos, not checked/downloaded during build time.


Just patch the code to stop trying to get online.

--
Thomas

Re: [Mageia-dev] Versions freeze

[Colin Guthrie]

'Twas brillig, and Sander Lepik at 03/03/12 10:03 did gyre and gimble:
> 03.03.2012 11:42, Michael Scherer kirjutas:
>> We have a calendar ( http://www.mageia.org/en/calendar/ ), where the
>> freeze was given.
> Weird, if i add this calendar into my google calandar or into
> Thunderbird, i see no events from it. Some settings are wrong?

Just FWIW, I see the events from this calendar in Thunderbird fine.

Col

-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] Versions freeze

[Johnny A. Solbu]

On Saturday 03 March 2012 10:42, Michael Scherer wrote:
> We reminded there is version freeze coming during meetings

Some of us can't attend these IRC-meetings at the current scheduled time.

> We gave the list of date in advance

That is not a freeze Reminder.

> and a link to the planning in every mail of announce, 

That is not a freeze reminder.
Besides, I don't remember seeing any version freeze announces untill after this 
thread came, saying it should be announced in advance.

> as well in blog posts and forums post.

Many of us don't read blogs and forums.
Besides, I was once told or read somewhere that developers and packagers should 
follow /this/ list in order to receive important notices and follow the 
development process. Not to read a blog and attend the forums.

> We have a calendar where the freeze was given.

That is a schedule, not a freeze reminder.

> And I expect people to either be experienced packager ( ie who have
> already done 1 release and so know the rules ), or to be new packagers
> with a experienced packager ( ie mentor ) who should have explained the
> release cycle. 

Knowing the cycle is not a freeze reminder.

> So if people have missed the whole plan, there is a problem that we need
> to fix, and the first step would be to collect reasons why they did
> missed it, not nag more everybody on every possible channels.

You miss my whole point.
I am talking about one -1- reminder to the list when the Version freeze is 
about to happen. Not that it is scheduled to occur in two months.

You need to remember that we are flawed human beeings. And this may come as a 
surprise for some, but human beeings happens to have a tendency to forget 
things. Even important things. That is why all kinds of reminders and reminder 
related services exists.

-- 
Johnny A. Solbu
PGP key ID: 0xFA687324


signature.asc
Description: This is a digitally signed message part.

Re: [Mageia-dev] Versions freeze

[Pascal Terjan]

On Sat, Mar 3, 2012 at 16:42, Johnny A. Solbu  wrote:
> On Saturday 03 March 2012 10:42, Michael Scherer wrote:
>> We reminded there is version freeze coming during meetings
>
> Some of us can't attend these IRC-meetings at the current scheduled time.
>
>> We gave the list of date in advance
>
> That is not a freeze Reminder.
>
>> and a link to the planning in every mail of announce,
>
> That is not a freeze reminder.
> Besides, I don't remember seeing any version freeze announces untill after 
> this thread came, saying it should be announced in advance.
>
>> as well in blog posts and forums post.
>
> Many of us don't read blogs and forums.
> Besides, I was once told or read somewhere that developers and packagers 
> should follow /this/ list in order to receive important notices and follow 
> the development process. Not to read a blog and attend the forums.

The freeze was reminded on this list in the email announcing that beta
1 iso were on their way, 2 weeks ago
https://www.mageia.org/pipermail/mageia-dev/2012-February/011914.html

Re: [Mageia-dev] qt3-devel

[Colin Guthrie]

'Twas brillig, and Kamil Rytarowski at 02/03/12 19:43 did gyre and gimble:
> On 02.03.2012 19:55, Thomas Backlund wrote:
>> 02.03.2012 20:49, Kamil Rytarowski skrev:
>>> Hello!
>>>
>>> Is possible to ship qt3-devel with Mageia? Half of the the Polish
>>> community is demanding it, and because of lack of qt3-devel people can't
>>> switch from other Well Known Distros to Mageia.
>>>
>> NO.
>>
>> As stated a million times before...
>>
>> qt3 is obsolete
>>
>> The only reason we have some qt3 runtime support is because of LSB
> Sad..
>>
>> Any stuff needed should be ported to qt4.
> Actually this is not true. One of our Mageia users (who introduced
> Mageia on a dozen of machines) can't switch the next dozen because of
> lacking Rivendell Radio Broadcasting software (
> http://www.rivendellaudio.org/index.shtml ), the other can't use his
> favourite qt3 apps, and a few others (including RH employee) are forced
> to use Fedora or KDE4.
> 
> If the "obsolete" part is the only reason, then it's not too strong..
> the package is maintained and there is *upstream*.
> 
> As of the 3.5.13 release the Trinity project has taken over maintenance
> of Qt3.
> 
> This means we are the new "upstream" location for up-to-date Qt3
> source code.
> Since there have been no updates or stable releases from
> Nokia/Trolltech in many years and there are literally hundreds patches
> floating around, there was a significant need for a central location.
> By maintaining Qt3 it will allow us to continue to improve Qt3
> outside the scope of Trinity. It will also provide a central location
> for Linux distributions to build packages from, and contributers to
> submit code to.
> For obvious reasons any Qt3 version released by this project is
> licensed under the GPL only; holders of Trolltech Qt licenses may not
> use these versions in their proprietary projects.
> 
> http://www.trinitydesktop.org/wiki/bin/view/Documentation/Releases_3_5_13#Qt3
> 
> 
> Trinity is currently packaged for Mandriva, OpenSUSE and available for
> the main distros.

I am thoroughly unimpressed with this trinity stuff. Open Source
software gives people freedoms and that's good, but it doesn't stop them
making bad decisions.

Times move on. Why take a legacy bit of software and keep on developing
it? If they *really* cared so much for the KDE3 interface they would
port it to qt4 or even qt5, not limp on with outdated base layers.


Col



-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

[Mageia-dev] Problem with latest network manager

[Colin Guthrie]

Seems the latest network manager is busted...

Won't start or stop properly nor allow networks to actually work...

Not sure exactly what is wrong, but I'll try and look into it if noone
else does.

Col
-- 

Colin Guthrie
colin(at)mageia.org
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/

Re: [Mageia-dev] Versions freeze

[Oliver Burger]

Am 03.03.2012 17:42, schrieb Johnny A. Solbu:

You miss my whole point.
I am talking about one -1- reminder to the list when the Version freeze is 
about to happen.

Not that it is scheduled to occur in two months.


You need to remember that we are flawed human beeings. And this may come as a 
surprise for some,
but human beeings happens to have a tendency to forget things. Even 
important things. That is why

all kinds of reminders and reminder related services exists.

In the last meeting invitation, Anne did talk about it (before this 
thread started). And even if people can't attend the meetings because of 
other duties or being on the wrong side of earth, there are the logs.
And in the last meeting logs for this channel, the reminder was said and 
discussed.


Oliver

Re: [Mageia-dev] BS broken ?

[Thomas Spuhler]

On Saturday, March 03, 2012 08:42:58 AM Thomas Backlund wrote:
> 03.03.2012 17:38, Thomas Spuhler skrev:
> > On Saturday, March 03, 2012 08:26:40 AM Pascal Terjan wrote:
> >> On Sat, Mar 3, 2012 at 15:21, Thomas Spuhler  
wrote:
> >>> On Saturday, March 03, 2012 06:56:25 AM Luc Menut wrote:
>  Le 03/03/2012 14:06, Thomas Backlund a écrit :
> > 03.03.2012 15:04, Luc Menut skrev:
> >> Hello,
> >> 
> >> The BS seems broken; I submitted this morning kdebase4-workspace,
> >> and the build is still in progress (4 hours after). Same thing with
> >> gnuradio-3.5.1-8.mga2 i586 (12 hours).
> >> It seems that the BS indefinitely retries to build
> >> kdebase4-workspace (on http://pkgsubmit.mageia.org/, the build
> >> machine regularly changes).
> > 
> > I will kill all builds on both nodes as soon as new glibc is
> > uploaded, and force recreation of all cauldron chroots...
>  
>  OK, you can kill kdebase4-workspace's builds immediately if you want
>  to free build nodes; they won't build with the current chroot.
> >>> 
> >>> I have been trying to build php-pear-horde pacakges for a week w/o
> >>> success. It seems theBS cannot find the horde-pear-channel. I kept
> >>> waiting since it was in fact down for some time, but it builds locally
> >>> as well as on the mdv bs. Thas the BS lost dns service?
> >> 
> >> What is failing exactly?
> >> DNS seem to be working fine.
> > 
> > The logs say:
> > Unknown channel "pear.horde.org"
> > 
> > but locally I get
> > [root@localhost ~]# pear list-upgrades
> > WARNING: channel "pear.horde.org" has updated its protocols, use "pear
> > channel-update pear.horde.org" to update
> > pear.horde.org Available Upgrades (stable):
> > ===
> > ChannelPackage   Local  Remote Size
> > pear.horde.org Horde_ActiveSync  1.2.3 (stable) 1.2.4 (stable) 87kB
> > pear.horde.org Horde_Crypt   1.1.0 (stable) 1.1.1 (stable) 135kB
> > pear.horde.org Horde_Data1.0.4 (stable) 1.0.5 (stable) 31kB
> > pear.horde.org Horde_Group   1.0.4 (stable) 1.0.5 (stable) 21kB
> > pear.horde.org Horde_Http1.1.0 (stable) 1.1.1 (stable) 11.8kB
> > pear.horde.org Horde_Imap_Client 1.4.3 (stable) 1.5.1 (stable) 134kB
> > pear.horde.org Horde_Itip1.0.6 (stable) 1.0.7 (stable) 33kB
> > pear.horde.org Horde_Mail1.0.3 (stable) 1.1.0 (stable) 21kB
> > pear.horde.org Horde_Memcache1.0.4 (stable) 1.0.5 (stable) 13.2kB
> > pear.horde.org Horde_Rdo 1.1.0 (stable) 1.1.1 (stable) 30kB
> > pear.horde.org Horde_Support 1.0.1 (stable) 1.0.2 (stable) 22kB
> > 
> > So it seems the channel is up and working
> 
> Chroots build without dns support, as everything built must be provided
> by the repos, not checked/downloaded during build time.
> 
> 
> Just patch the code to stop trying to get online.
> 
> --
> Thomas

I am afraid I would have to redo about 300+ pear package specs this close to 
the version freeze. I do not have the time for this.
What has changed in the last week on the BS? Was does this change fix?

-- 
Best regards
Thomas

Re: [Mageia-dev] BS broken ?

[Pascal Terjan]

> I am afraid I would have to redo about 300+ pear package specs this close to
> the version freeze. I do not have the time for this.

That's very annoying as it means we depend on external system to be
able to rebuild the package if we need for any reason (like security
updates).
I hope this does not include any compiled module as it may be licence
violation if some are GPL and we don't have the sources.

> What has changed in the last week on the BS? Was does this change fix?

I am not aware of any change

Re: [Mageia-dev] Versions freeze

[Sander Lepik]

On Mar 3, 2012 7:41 PM, "Oliver Burger"  wrote:
> And in the last meeting logs for this channel, the reminder was said and
discussed.
>
> Oliver

Can this link be sent to list after meeting? Or is this too much asked? Or
was it sent and i just missed it?

--
Sander

Re: [Mageia-dev] Versions freeze

[Oliver Burger]

Am 03.03.2012 21:10, schrieb Sander Lepik:

On Mar 3, 2012 7:41 PM, "Oliver Burger" mailto:oliver@googlemail.com>> wrote:
 > And in the last meeting logs for this channel, the reminder was said
and discussed.
 >
 > Oliver

Can this link be sent to list after meeting? Or is this too much asked?
Or was it sent and i just missed it?

Well, actually I'm sure it could. But why? All meeting logs are publicly 
available at https://meetbot.mageia.org/


I did send those links to the i18n list after meeting s there but most 
of the time, I just forgot.
And I think looking at the meetbot page from time to time isn't all that 
hard and can be done by anyone.


Cheers,

Oliver

Re: [Mageia-dev] Versions freeze

[Pascal Terjan]

On Sat, Mar 3, 2012 at 20:55, Oliver Burger  wrote:
> Am 03.03.2012 21:10, schrieb Sander Lepik:
>>
>> On Mar 3, 2012 7:41 PM, "Oliver Burger" > > wrote:
>>  > And in the last meeting logs for this channel, the reminder was said
>> and discussed.
>>  >
>>  > Oliver
>>
>> Can this link be sent to list after meeting? Or is this too much asked?
>> Or was it sent and i just missed it?
>>
> Well, actually I'm sure it could. But why? All meeting logs are publicly
> available at https://meetbot.mageia.org/
>
> I did send those links to the i18n list after meeting s there but most of
> the time, I just forgot.
> And I think looking at the meetbot page from time to time isn't all that
> hard and can be done by anyone.

Maybe the bot could send it automatically to the right list depending
on the channel where the meeting happens?

Re: [Mageia-dev] Versions freeze

[Sander Lepik]

> Well, actually I'm sure it could. But why? All meeting logs are publicly
available at https://meetbot.mageia.org/

Why? Because now i know this link for some time and then i forget it again
:) Sorry but Mageia isn't the only project where i'm contributing. I just
can't remember everything. But thanks for the link.

--
Sander

Re: [Mageia-dev] Problem with latest network manager

[Juan Luis Baptiste]

On Sat, Mar 3, 2012 at 12:27 PM, Colin Guthrie  wrote:
> Seems the latest network manager is busted...
>
> Won't start or stop properly nor allow networks to actually work...
>
> Not sure exactly what is wrong, but I'll try and look into it if noone
> else does.
>
> C

I'm working right now on updating it to 0.9 final released at the
beginning of this week, give me a couple hours to finish and test with
this one.

-- 
Juancho

Re: [Mageia-dev] BS broken ?

[Luc Menut]

Le 03/03/2012 14:04, Luc Menut a écrit :

Hello,

The BS seems broken; I submitted this morning kdebase4-workspace, and
the build is still in progress (4 hours after). Same thing with
gnuradio-3.5.1-8.mga2 i586 (12 hours).
It seems that the BS indefinitely retries to build kdebase4-workspace
(on http://pkgsubmit.mageia.org/, the build machine regularly changes).




kdebase4-workspace still doesn't build on the BS (it builds fine outside 
iurt).

compiz seems to have the same pb.

regards,
Luc


--
Luc Menut

Re: [Mageia-dev] Problem with latest network manager

[John Balcaen]

Le 3 mars 2012 18:07, "Juan Luis Baptiste"  a écrit :
[...]

>
> I'm working right now on updating it to 0.9 final released at the
> beginning of this week, give me a couple hours to finish and test with
> this one.
>

I guess Colin is talking about NetworkManager & not knetworkmanager :)

Re: [Mageia-dev] Problem with latest network manager

[Juan Luis Baptiste]

On Sat, Mar 3, 2012 at 5:25 PM, John Balcaen  wrote:
>
> I guess Colin is talking about NetworkManager & not knetworkmanager :)


Well anyway I'm already finishing :P

-- 
Juancho

Re: [Mageia-dev] Versions freeze

[Maarten Vanraes]

Op zaterdag 03 maart 2012 10:36:55 schreef Thomas Backlund:
> 03.03.2012 11:24, Michael Scherer skrev:
> > Le vendredi 02 mars 2012 à 20:53 +0100, Maarten Vanraes a écrit :
> >> Op vrijdag 02 maart 2012 20:16:11 schreef Thomas Backlund:
> >>> 02.03.2012 21:08, Dimitri Jakov skrev:
>  Besides... GNOME 3.4 is going to be released on March 28 - does that
> >>> 
> >>> Yes we know...
> >>> 
>  mean that we won't be able to ship it with Mageia 2?
> >>> 
> >>> Nope, we have that as an exception to the freeze...
> >>> (that's why we already run 3.3.x)
> >>> 
> >>> we will have Gnome 3.4.x and KDE 4.8.x in Mageia 2
> >> 
> >> also, I hope mariadb-5.5.x final (right now we have 5.5.20 which is the
> >> alpha version; beta will come quite soon, then the rc and finals follow
> >> pretty fast and these only contain bugfixes)
> > 
> > Next time, maybe waiting for the beta would be better, cauldron is not
> > mean to be a playground for testing upstream softwares when we do not
> > have a strong assurance that the stable will end i the stable release.
> 
> Actually in this case it is ok, since we've been tracking upstream 5.5.x
> branch with the target for 5.5.x final, so "alpha" in this case
> only means fully synced with mysql 5.5 and afaik all intended mariadb
> patches merged...

yes, and so far that haven't been any complaints yet, waiting for mikala, 
since he's the most likely person to have issues about it.

> They are only a bit late :/

yes :-(

allthough according to upstream, there seems to be a good chance it will be 
released as final quite quickly

> > If everybody start to do that, we spend more time on upgrading to
> > version that should have been stable than fixing others bugs.
> > 
> > And if upstream could also try to be a little bit less original and
> > follow some easy to grasp convetion about version number.

yes, it seems they will upgrade the version to +1 for beta and so forth.

but they consider the major versions 5.5 the real version. but still, took me 
a while to figure it out...

Re: [Mageia-dev] Versions freeze

[Maarten Vanraes]

Op zaterdag 03 maart 2012 22:34:41 schreef Sander Lepik:
> > Well, actually I'm sure it could. But why? All meeting logs are publicly
> 
> available at https://meetbot.mageia.org/
> 
> Why? Because now i know this link for some time and then i forget it again
> 
> :) Sorry but Mageia isn't the only project where i'm contributing. I just
> 
> can't remember everything. But thanks for the link.
> 
> --
> Sander

maybe we could have the meetbot send it to another mailing list and the people 
who don't frequently are able to follow the meetings can subscribe to that.

i don't think it's a bad idea to read what has happened in the meetings as a 
packager team member...

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release libvirt-0.9.10-2.mga2

[Thierry Vignaud]

On 4 March 2012 00:56, misc  wrote:
> misc  0.9.10-2.mga2:
> + Revision: 217731
> - add libyajl-devel as BuildRequires, should fix #4685

That is?
Please include a one liner description...

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release rpm-4.9.1.2-20.mga2

[Thierry Vignaud]

On 3 March 2012 14:56, tmb  wrote:
> tmb  1:4.9.1.2-20.mga2:
> + Revision: 217265
> - restore P4000 as it's not causing the the out of memory errors

That is?
Please include a one liner description of the fixed issue.
Especially on such a core package...

Re: [Mageia-dev] rpm read locks issue.

[Thierry Vignaud]

On 3 March 2012 01:52, D.Morgan  wrote:
>>> virhe: rpmdb: Lock table is out of available locker entries
>>> virhe: indeksin Group avaus db4:llä ei onnistu - Muistin varaaminen ei
>>> onnistu (12)
>>
>> I wonder, could it be because of:
>>
>> tv  1:4.9.1.2-17.mga2:
>> + Revision: 215717
>> - patch 5000: switch back to former, much smaller BDB memory pool size
>> (RhBug:752897)
>
> i tried to remove it for testing purpose but we still have the issue.
>
> Thierry do you see what may be the culprit for this ?

As previously said, I'm aware of only one cause: sg using librpm
having crashed previously

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release rpm-4.9.1.2-20.mga2

[Anssi Hannula]

04.03.2012 03:41, Thierry Vignaud kirjoitti:
> On 3 March 2012 14:56, tmb  wrote:
>> tmb  1:4.9.1.2-20.mga2:
>> + Revision: 217265
>> - restore P4000 as it's not causing the the out of memory errors
> 
> That is?
> Please include a one liner description of the fixed issue.
> Especially on such a core package...
> 

I guess he means this one,

here's Luc encountering it in BS:
http://www.mageia.org/pipermail/mageia-dev/2012-March/012553.html

and me on my cauldron box:
http://www.mageia.org/pipermail/mageia-dev/2012-March/012517.html

-- 
Anssi Hannula

[Mageia-dev] possibly important packages missing updates

[David Walser]

I noticed five packages that look important, seem to not have been updated in 
quite a while, and might be unmaintained.  They are:

- prelink
- cyrus-sasl
- syslinux
- elfutils
- keyutils

All have newer versions available in Mandriva.  Hopefully some experienced 
packagers can evaluate these and update before the freeze if needed.

Other than that, we seem to be in pretty good shape heading into the freeze.

[Mageia-dev] Errors/warning from drakxtools-13.89.1

[Charles A Edwards]

Error/warning is attached.

It occurred when using urpme to remove old kernel and nvidia-dkms
module.


Charles


-- 
Did I say 2?  I lied.
--
Mageia release 2 (Cauldron) for x86_64$
On SuperSizehttp://www.eslrahc.com
Registered Linux user #182463
3.2.6-server-3.mga2 x86_64
--


drakxtools warnings
Description: Binary data


signature.asc
Description: PGP signature

Re: [Mageia-dev] Errors/warning from drakxtools-13.89.1

[Manuel Hiebel]

Le samedi 03 mars 2012 à 22:15 -0500, Charles A Edwards a écrit :
> Error/warning is attached.
> 
> It occurred when using urpme to remove old kernel and nvidia-dkms
> module.
> 
https://bugs.mageia.org/show_bug.cgi?id=4783
> 
> Charles
> 
>