Re: [Mageia-dev] Bug squash party update

[Remco Rijnders]

On Sun, Mar 25, 2012 at 03:42:33PM +0100, Colin wrote in 
<4f6f2ed9.4060...@colin.guthr.ie>:

'Twas brillig, and Remco Rijnders at 25/03/12 13:29 did gyre and gimble:

The experiences so far have been mixed. We now have 7 more release
blockers than at the start of the weekend, with none closed since friday
afternoon. The uptake has been less than we had hoped for, but the
upside is that people are performing tests, and also that open bugs are
being reassesed as to their severity.


This isn't strictly true. e.g. there are some tracker bugs that are
themselves release blockers and those tracker bugs then have bugs that
block them. I've been busy fixing and closing a few bug reports that
related to the systemd tracker for example:
https://bugs.mageia.org/show_bug.cgi?id=2120


That no release blockers have been fixed yet is a bit of a shame, but
that does not mean that no work has been done on them. On several of the
bugs we have open we've seen promising progress in the past few days.


As per above, saying "none closed since Friday" or "no release blockers
have been fixed yet" is actually not quite true. Sadly, of course, this
means that when you expand out the bugs you probably now have a lot more
real release blocking bugs than you previously thought! :D


Hi Colin,

Thanks for the clarification on what I wrote. Indeed, I did not go in to 
recursively check the tracker bugs. That said, I hope my original message 
was sufficiently clear that uptake of the bug squash party was less than I 
had hoped for while still recognising people did work on open bug reports 
on the weekend. Your efforts, as always, were noticed and much appreciated 
:-)


Thanks again!

Remmy


signature.asc
Description: Digital signature

Re: [Mageia-dev] freez push clamav-0.97.4

[Thomas Spuhler]

On Saturday, March 24, 2012 04:21:36 PM Colin Guthrie wrote:
> 'Twas brillig, and Thomas Spuhler at 24/03/12 22:49 did gyre and gimble:
> > On Saturday, March 24, 2012 12:36:06 PM Sander Lepik wrote:
> >> On Mar 24, 2012 9:13 PM, "Thomas Spuhler"  wrote:
> >>> please push clamav-0.97.4
> >>> --
> >>> Best regards
> >>> Thomas Spuhler
> >> 
> >> Why?
> >> 
> >> --
> >> Sander
> > 
> > it's an upgrade from 0.97.4
> > We need to provide the newest version of the antivirus package
> 
> This, by itself, is not a very good explanation.
> 
> If this is purely a definitions update then that's fine.
> If this is a bugfix update that's probably fine too (depending on the bug)
> If it's a new feature update then that likely won't make it.
> 
> People are all very busy. It only takes the person requesting the push a
> minute or two to describe things properly. Please give your busy
> colleagues the respect they deserve and provide good explanations to
> save them having to spend time discussing and asking further questions.
> 
> We still don't really have enough information to decide on this one!
> 
> So please state whether it's just definitions or bugfix (and if so what
> bugs) etc.
> 
> Col
Sorry, I was busy last night and today with non Linux related staff and wanted 
to give this as much time as possible to be tested
The upgrade isn't necessarily needed. The new package provides some bug fixes 
as provieded on their web site. See below.
But if we don't do it, users will soon after the release get the message they 
your clamav version is outdated. Do we want that?


ClamAV 0.97.4 has been released!

March 19th, 2012 Posted by - webmaster

ClamAV 0.97.4 includes minor bugfixes, detection improvements and
initial support for on-access scanning under Mac OS X (see
contrib/ClamAuth).

This update is recommended for all users.

*

-- 
Best regards
Thomas Spuhler

[Mageia-dev] KDE configuration file regressions

[Frank Griffin]

I'm not sure if this is worth a bug report, but the incremental KDE 
upgrades in cauldron have a bad habit of regressing changes to 
configurations and preferences.  With every major upgrade, the fact that 
I've disabled the screensaver gets forgotten.  Sound volume keeps 
resetting to 1%.  Changes I've made to konsole settings to patch the yet 
unfixed bug that sets vertical terminal dimensions to the screen maximum 
get undone.


This stuff isn't critical for cauldron upgrades, but it will be for 
release upgrades if peoples' existing KDE preferences get trampled on 
indiscriminately.  There probably ought to be a review of what the RPMs 
are tagging as conf files, and the scope should be increased.

Re: [Mageia-dev] freeze push mgaonline

[Kamil Rytarowski]

On 15.03.2012 15:25, n...@gmx.com wrote:

Hi!

Please push mgaonline.

- new tarball 2.77.32
* stop using Mandriva URLs and replace them by www.mageia.org (mga#1590)
* replace Mandriva strings by Mageia in gnome-mandrakeonline.desktop
* replace MIME Type application/x-mdv-exec by application/x-mga-exec
* extend $MGA_YEARS in mgaupdate to 2012
* delete MANDRIVA_VERSION variable as not used
- replace obsolete drakx-newt with drakxtools-curses
- stop using MANDRIVA_VERSION in %install
- rename mandriva-mgaonline.desktop with mageia-mgaonline.desktop
- clean Categories in the .desktop file (remove X-Mandriva-* entry)
- remove %update_desktop_database and %clean_desktop_database (not used anymore)
- remove %update_mime_database and %clean_mime_database (not used anymore)
- clean .spec

ping?

[Mageia-dev] How should packages with version in name be handled?

[David W. Hodgins]

I've started qa testing upgrading from Mageia 1 to
Cauldron, to ensure going from Mageia 1 to 2 will
go smoothly.

I'm running into a some cases like
https://bugs.mageia.org/show_bug.cgi?id=5103
where Mageia 1 has libchamplain-gtk0.8_1
  and Cauldron has libchamplain-gtk0.12_0

As the packages contain version numbers in the package name,
urpmi is not treating it as a package update, which results
in messages such as

The following packages have to be removed for others to be upgraded:
libchamplain-gtk0.8_1-0.8.3-1.mga1.i586
 (due to missing libclutter-gtk-0.10.so.0)
libchamplain0.8_1-0.8.3-1.mga1.i586
 (due to missing libclutter-glx-1.0.so.0)

Am I correct in thinking that adding an obsoletes of
libchamplain-gtk0.8_1 to libchamplain-gtk0.12_0 would
get urpmi to remove it without generating the above
message?

If so, should I be opening bug reports for each of these
cases, or should it be left as is, and simply tell the
users to go ahead and answer yes to the prompt?

Regards, Dave Hodgins

Re: [Mageia-dev] freeze push: perl_checker

[nicolas vigier]

On Mon, 26 Mar 2012, Thierry Vignaud wrote:

> Hi
> 
> Please let in perl_checker

Submitted.

[Mageia-dev] freeze push: perl_checker

[Thierry Vignaud]

Hi

Please let in perl_checker
It enables to have better reporting on iurt, installer & drakxtools
code in order to find issues.
Which we sadly find since there were commiters not using perl_checker
in the previous year :-(

Detailed log:

- fake packages:
  o add RPM4 (for eg: iurt)
  o update Net::FTP for installer
- perl_checker:
  o recognize \B in regexps
  o recognize -p (pipe test) & -S (socket test)
  o recognize getpgrp()
  o kill "undeclared variable $^S"

See you

Re: [Mageia-dev] Freeze Push: rsyslog

[nicolas vigier]

On Mon, 26 Mar 2012, Colin Guthrie wrote:

> Please push rsyslog.
> 
> It's a bugfix release from 5.8.8 which lost data.
> 
> "There was an important flaw in 5.8.8 that caused disk queue content to
> be lost after a shutdown and restart of rsyslogd. So if you run this
> version, an upgrade to 5.8.9 is highly suggested."
> 
> http://www.rsyslog.com/rsyslog-5-8-9-v5-stable-released/

Submitted.

Re: [Mageia-dev] Too late for this ? (cairo 1.12)

[Colin Guthrie]

'Twas brillig, and JA Magallón at 25/03/12 23:59 did gyre and gimble:
> And I found that there was a plf flag in the spec (to enable font aa),
> but we have no tainted build, I think. I have tainted repos enabled but
> urpmi just installs the standard version.

Is that needed these days? I thought things were OK for AA fonts these
days... or is it only partially the case?

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] Freeze Push: rsyslog

[Colin Guthrie]

Please push rsyslog.

It's a bugfix release from 5.8.8 which lost data.

"There was an important flaw in 5.8.8 that caused disk queue content to
be lost after a shutdown and restart of rsyslogd. So if you run this
version, an upgrade to 5.8.9 is highly suggested."

http://www.rsyslog.com/rsyslog-5-8-9-v5-stable-released/

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] Too late for this ? (cairo 1.12)

[JA Magallón]

On 03/26/2012 12:35 AM, Funda Wang wrote:

I'm afraid yes, cairo is a base library for all gtk2/3 apps. We cannot
do such a big version bump now.



Well, I understand.
Anyways, as src.rpm was pretty simple, I rebuilt it locally and works
pretty fine. I think things got a bit smoother, but anyways it can be
self suggestion.
Just for the record, it built without any problem. I just replaced
source tarballs and changed versions in spec, no lib major bump nor
anything, so it replaced old one.

And I found that there was a plf flag in the spec (to enable font aa),
but we have no tainted build, I think. I have tainted repos enabled but
urpmi just installs the standard version.


2012/3/26 JA Magallón:

http://cairographics.org/news/cairo-1.12.0/



--
J.A. Magallon \   Winter is coming...

Re: [Mageia-dev] Too late for this ? (cairo 1.12)

[Funda Wang]

I'm afraid yes, cairo is a base library for all gtk2/3 apps. We cannot
do such a big version bump now.

2012/3/26 JA Magallón :
> http://cairographics.org/news/cairo-1.12.0/
>
> --
> J.A. Magallon         \               Winter is
> coming...

[Mageia-dev] Too late for this ? (cairo 1.12)

[JA Magallón]

http://cairographics.org/news/cairo-1.12.0/

--
J.A. Magallon \   Winter is coming...

Re: [Mageia-dev] Freeze push: udisks2

[Anne Nicolas]

Le 25/03/2012 23:55, David Walser a écrit :
> Colin Guthrie wrote:
>> Primary reason for requesting this is a fix for MMC/SD cards.
>>
>> http://cgit.freedesktop.org/udisks/commit/?id=3b277903af128fb632897d8932fe300f216ead38
>>
>> Misc small fixes also included. This is really a part of the
>> infrastructure needed by GNOME3, so I presume it's covered by the same
>> version freeze escaping policy, but if not, please shout and I'll revert
>> and cherry-pick patches instead.
>>
>> Col
> 
> Ping?
> 

Submitted

-- 
Anne
http://mageia.org

Re: [Mageia-dev] Freeze push: udisks2

[David Walser]

Colin Guthrie wrote:
> Primary reason for requesting this is a fix for MMC/SD cards.
> 
> http://cgit.freedesktop.org/udisks/commit/?id=3b277903af128fb632897d8932fe300f216ead38
> 
> Misc small fixes also included. This is really a part of the
> infrastructure needed by GNOME3, so I presume it's covered by the same
> version freeze escaping policy, but if not, please shout and I'll revert
> and cherry-pick patches instead.
> 
> Col

Ping?

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[David Walser]

Kamil Rytarowski wrote:
> On 25.03.2012 17:20, Pascal Terjan wrote:
>>
>>
>> On Sun, Mar 25, 2012 at 15:51, Angelo Naselli > > wrote:
>>
>> In data domenica 25 marzo 2012 14:48:01, Julien ha scritto:
>> > Hello,
>> >
>> > Is there a mass rebuild planned before mageia 2 ? And if not, is
>> there a
>> > value in rebuilding a package without update since 1 year ?
>> Can you point us the list? Maybe we can consider if they can go,
>> or have to be
>> rebuild, or removed...
>>
>>
>> That's one third of the packages
>>
>> [schedbot@valstar ~]$ ls 
>> /distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga1.src.rpm | wc -l
>> 3420
>> [schedbot@valstar ~]$ ls 
>> /distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga2.src.rpm | wc -l
>> 6479
>>
> I have got a semi-automated script to do it.

It's too late to do a mass rebuilding, of course, but if you have a script that 
does it, it would be useful if you ran it locally and report 
which packages now fail to build.  Those ones should be fixed.

Re: [Mageia-dev] MariaDB: problem: final estimated release date

[David Walser]

Colin Guthrie wrote:
> 'Twas brillig, and Maarten Vanraes at 23/03/12 17:39 did gyre and gimble:
>> ( see https://mariadb.atlassian.net/secure/Dashboard.jspa , look at road map 
>> )
>> 
>> MariaDB RC 5.5.2229/Mar/12
>> MariaDB GA 5.5.2309/Apr/12
>> 
>> that means that the GA (final release) is 2 days after release freeze :-(
>> (not counting any possible extra delays)
>> 
>> however, i would like to have the final release and not the release 
>> candidate.
>> 
>> any thoughts on this?
> 
> Well, sh1t happens... We'll just have to go with the RC and we can
> always issue an update to the final release afterwards. I don't think
> this is a huge problem. If there happen to be delays for other reasons
> we can maybe push it in, but I wouldn't bank on it!
> 
> Col

As a matter of fact, I've noticed lately Mandriva issuing updates to newer 
versions of mysql for non-security reasons.  Apparently they make 
an exception to the no version updates policy for this package now (obviously 
they keep the updates within the same stable branch).  Perhaps 
we could too for mariadb.  Not saying we definitely should, I don't follow 
mysql/mariadb development.

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[D.Morgan]

On Sun, Mar 25, 2012 at 11:31 PM, Luis Daniel Lucio Quiroz
 wrote:
> Isnt it better that each maintainer rebuild his packages by his own? Using
> self criteria

this is too late now, we need to fix bugs, the release critical now
and not "rebuild" packages.

Re: [Mageia-dev] Freeze push: foomatic-filters

[David Walser]

David Walser wrote:
> Florian Hubold  writes:
>> Am 20.03.2012 10:36, schrieb David Walser:
>> > Minor foomatic-filters update (4.0.14) contains just one change, should be
> safe to go in:
>> >* foomaticrip.c: If the input data is PDF but the driver requires
>> >  PostScript, use the pdftops CUPS filter when CUPS is the spooler.
>> >  This way we always use the same method to convert PDF to PostScript
>> >  in the whole system, including any workarounds applied in the CUPS
>> >  filter.
>> >
>> > Confirmed that it builds and installs fine locally.
>> >
>> >
>> Well, does it also work just fine?
> 
> Yes.  Thanks for asking and sorry I didn't mention it earlier.
> 
> I tested this at work printing PDFs to a printer configured to use PostScript
> and it works fine.

Ping?

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Luis Daniel Lucio Quiroz]

Isnt it better that each maintainer rebuild his packages by his own? Using self 
criteria

Enviado desde mi teléfono Verizon Wireless

-Mensaje original-
De: Angelo Naselli 
Para: Mageia development mailing-list 
Enviado: dom, mar 25, 2012 21:16:45 GMT+00:00
Asunto: Re: [Mageia-dev] mass rebuild for Mga 2 ?

> This is not doable now. Freeze time, it should have been done much
> before. Please focus on bug reports in Bugzilla

Well who thinks some mga1 packages here in the outcoming mga2 
and not been rebuilt, has problems could add a bug report for that to allow 
a "bug fixing rebuilding" :)

-- 
Angelo

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Angelo Naselli]

> This is not doable now. Freeze time, it should have been done much
> before. Please focus on bug reports in Bugzilla

Well who thinks some mga1 packages here in the outcoming mga2 
and not been rebuilt, has problems could add a bug report for that to allow 
a "bug fixing rebuilding" :)

-- 
Angelo


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

Re: [Mageia-dev] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Luc Menut]

Le 25/03/2012 22:02, Thierry Vignaud a écrit :

On 25 March 2012 18:35, Luc Menut  wrote:

Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.


That's a very rare usage.
Most users won't do that.
Those who do should be able to fix the mga1 entry IMHO.



using many distros on the same system is not so uncommon.
Is the installer chain load grub by default if another distro is already 
installed on the system? or does it add mga entries on the existing grub 
config?


--
Luc Menut

Re: [Mageia-dev] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Colin Guthrie]

'Twas brillig, and Colin Guthrie at 25/03/12 20:56 did gyre and gimble:
> 'Twas brillig, and Luc Menut at 25/03/12 20:55 did gyre and gimble:
>> Le 25/03/2012 19:08, Colin Guthrie a écrit :
>>> 'Twas brillig, and Luc Menut at 25/03/12 17:35 did gyre and gimble:
 Le 25/03/2012 17:45, r...@mageia.org a écrit :
> Revision
>  226393
> Author
>  colin

 [...]

>
> +%triggerpostun backend -- drakxtools-backend<   14.1-2
> +if [ -w /boot/grub/menu.lst ]; then
> +  if grep -q splash= /boot/grub/menu.lst; then
> +echo"Migrating kernel commandline bootsplash arguments in grub"
> +sed -i 's/ splash=silent / splash quiet /;s/ splash=silent$/
> splash quiet/;s/ splash=verbose / /;s/ splash=verbose$//;'
> /boot/grub/menu.lst
> +  fi
> +fi
> +

 IIUC this script, you update splash=silent&  splash=verbose in
 /boot/grub/menu.lst for all the lines.
 What happens if we have entries for mga1 or other distros in the same
 grub menu.lst ?
 Aren't you going to break all these entries with such update?

 Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.
>>>
>>> Yeah, good point.
>>>
>>> Any suggestions on how to do this more gracefully?
>>
>> Nope.
>>
>> Is this trigger needed for an upgrade mga1->mga2? or is it only for
>> cauldron update?
>> If it's only for cauldron, I think that it would be safer to drop the
>> trigger.
> 
> Yeah, it's needed for mga1 -> mga2 upgrade.

I guess the regexp could look for:

\(vmlinuz\( \|-3.3[^ ]*\) .*\) splash=silent

But that might not catch some variations.

I'd be tempted to say "sod it" as per Thierry's message. I guess chain
loading grubs is maybe more common on dual setups?

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] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Thierry Vignaud]

On 25 March 2012 18:35, Luc Menut  wrote:
> Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.

That's a very rare usage.
Most users won't do that.
Those who do should be able to fix the mga1 entry IMHO.

Re: [Mageia-dev] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Colin Guthrie]

'Twas brillig, and Luc Menut at 25/03/12 20:55 did gyre and gimble:
> Le 25/03/2012 19:08, Colin Guthrie a écrit :
>> 'Twas brillig, and Luc Menut at 25/03/12 17:35 did gyre and gimble:
>>> Le 25/03/2012 17:45, r...@mageia.org a écrit :
 Revision
  226393
 Author
  colin
>>>
>>> [...]
>>>

 +%triggerpostun backend -- drakxtools-backend<   14.1-2
 +if [ -w /boot/grub/menu.lst ]; then
 +  if grep -q splash= /boot/grub/menu.lst; then
 +echo"Migrating kernel commandline bootsplash arguments in grub"
 +sed -i 's/ splash=silent / splash quiet /;s/ splash=silent$/
 splash quiet/;s/ splash=verbose / /;s/ splash=verbose$//;'
 /boot/grub/menu.lst
 +  fi
 +fi
 +
>>>
>>> IIUC this script, you update splash=silent&  splash=verbose in
>>> /boot/grub/menu.lst for all the lines.
>>> What happens if we have entries for mga1 or other distros in the same
>>> grub menu.lst ?
>>> Aren't you going to break all these entries with such update?
>>>
>>> Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.
>>
>> Yeah, good point.
>>
>> Any suggestions on how to do this more gracefully?
> 
> Nope.
> 
> Is this trigger needed for an upgrade mga1->mga2? or is it only for
> cauldron update?
> If it's only for cauldron, I think that it would be safer to drop the
> trigger.

Yeah, it's needed for mga1 -> mga2 upgrade.

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] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Colin Guthrie]

'Twas brillig, and Luc Menut at 25/03/12 17:35 did gyre and gimble:
> Le 25/03/2012 17:45, r...@mageia.org a écrit :
>> Revision
>> 226393
>> Author
>> colin
> 
> [...]
> 
>>
>> +%triggerpostun backend -- drakxtools-backend<  14.1-2
>> +if [ -w /boot/grub/menu.lst ]; then
>> +  if grep -q splash= /boot/grub/menu.lst; then
>> +echo"Migrating kernel commandline bootsplash arguments in grub"
>> +sed -i 's/ splash=silent / splash quiet /;s/ splash=silent$/
>> splash quiet/;s/ splash=verbose / /;s/ splash=verbose$//;'
>> /boot/grub/menu.lst
>> +  fi
>> +fi
>> +
> 
> IIUC this script, you update splash=silent & splash=verbose in
> /boot/grub/menu.lst for all the lines.
> What happens if we have entries for mga1 or other distros in the same
> grub menu.lst ?
> Aren't you going to break all these entries with such update?
> 
> Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.

Yeah, good point.

Any suggestions on how to do this more gracefully?

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] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Luc Menut]

Le 25/03/2012 19:08, Colin Guthrie a écrit :

'Twas brillig, and Luc Menut at 25/03/12 17:35 did gyre and gimble:

Le 25/03/2012 17:45, r...@mageia.org a écrit :

Revision
 226393
Author
 colin


[...]



+%triggerpostun backend -- drakxtools-backend<   14.1-2
+if [ -w /boot/grub/menu.lst ]; then
+  if grep -q splash= /boot/grub/menu.lst; then
+echo"Migrating kernel commandline bootsplash arguments in grub"
+sed -i 's/ splash=silent / splash quiet /;s/ splash=silent$/
splash quiet/;s/ splash=verbose / /;s/ splash=verbose$//;'
/boot/grub/menu.lst
+  fi
+fi
+


IIUC this script, you update splash=silent&  splash=verbose in
/boot/grub/menu.lst for all the lines.
What happens if we have entries for mga1 or other distros in the same
grub menu.lst ?
Aren't you going to break all these entries with such update?

Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.


Yeah, good point.

Any suggestions on how to do this more gracefully?


Nope.

Is this trigger needed for an upgrade mga1->mga2? or is it only for 
cauldron update?
If it's only for cauldron, I think that it would be safer to drop the 
trigger.


Luc


--
Luc Menut

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Anne nicolas]

2012/3/25 Pascal Terjan :
>
>
> On Sun, Mar 25, 2012 at 18:26, Funda Wang  wrote:
>>
>> Maybe we could filter out those noarch packages, esp those perl modules.
>
>
> [schedbot@valstar ~]$ urpmf --use-distrib
> /distrib/mirror/distrib/cauldron/i586/ --qf %arch:%sourcerpm i586:.*mga1 |
> sort -u | wc -l
> 912
>

This is not doable now. Freeze time, it should have been done much
before. Please focus on bug reports in Bugzilla

-- 
Anne
http://www.mageia.org

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Pascal Terjan]

On Sun, Mar 25, 2012 at 18:26, Funda Wang  wrote:

> Maybe we could filter out those noarch packages, esp those perl modules.
>

[schedbot@valstar ~]$ urpmf --use-distrib
/distrib/mirror/distrib/cauldron/i586/ --qf %arch:%sourcerpm i586:.*mga1 |
sort -u | wc -l
912

Re: [Mageia-dev] Freeze push request QuaZip 0.4.4

[Anssi Hannula]

25.03.2012 20:53, Angelo Naselli kirjoitti:
>> Build failure.
> argh, i forgot cmake dep, sorry.
> Should be ok now.

Submitted.

-- 
Anssi Hannula

Re: [Mageia-dev] freeze push request: scite

[Angelo Naselli]

> This package is owned by anaselli cause it was built while he was
> mentoring me.
I could give it to you if there's a problem since you're maintaining it :)

-- 
Angelo


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

Re: [Mageia-dev] Freeze push request QuaZip 0.4.4

[Angelo Naselli]

> Build failure.
argh, i forgot cmake dep, sorry.
Should be ok now.
-- 
Angelo


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

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Funda Wang]

Maybe we could filter out those noarch packages, esp those perl modules.

2012/3/26 Pascal Terjan :
>
>
> On Sun, Mar 25, 2012 at 18:11, Thierry Vignaud 
> wrote:
>>
>> On 25 March 2012 18:15, Pascal Terjan  wrote:
>> >> Now, in order to provide a very good Mageia 2, every package should
>> >> be rebuilt with the new toolchain/glibc in order to make sure they
>> >> still build _and_ work correctly (and flush out any bugs in the
>> >> toolchain)
>> >>
>> >> Now this rebuild should be done preferably in BR order when possible,
>> >> to rule out bad interaction between packages and be preferably be
>> >> fully done by alpha3 or beta1 at the latest so we have time to fix
>> >> it properly for Mageia 2.
>>
>> (...)
>>
>> > Rebuilding half of the distribution now seems the best way to add bugs
>> > before the release...
>>
>> On the other hand, we my got bugs introduced when pushing a security
>> update due to the new toolchain not having been tested with those
>> packages...
>> Or having packages not rebuilding when patching them for security
>> fixes.
>
>
> Yes but I think it's something that should have been done after toolchain
> was updated in december, or at latest around beta1/version freeze, not 2
> weeks before the release candidate

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Pascal Terjan]

On Sun, Mar 25, 2012 at 18:11, Thierry Vignaud wrote:

> On 25 March 2012 18:15, Pascal Terjan  wrote:
> >> Now, in order to provide a very good Mageia 2, every package should
> >> be rebuilt with the new toolchain/glibc in order to make sure they
> >> still build _and_ work correctly (and flush out any bugs in the
> >> toolchain)
> >>
> >> Now this rebuild should be done preferably in BR order when possible,
> >> to rule out bad interaction between packages and be preferably be
> >> fully done by alpha3 or beta1 at the latest so we have time to fix
> >> it properly for Mageia 2.
>
> (...)
>
> > Rebuilding half of the distribution now seems the best way to add bugs
> > before the release...
>
> On the other hand, we my got bugs introduced when pushing a security
> update due to the new toolchain not having been tested with those
> packages...
> Or having packages not rebuilding when patching them for security
> fixes.
>

Yes but I think it's something that should have been done after toolchain
was updated in december, or at latest around beta1/version freeze, not 2
weeks before the release candidate

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Thierry Vignaud]

On 25 March 2012 18:15, Pascal Terjan  wrote:
>> Now, in order to provide a very good Mageia 2, every package should
>> be rebuilt with the new toolchain/glibc in order to make sure they
>> still build _and_ work correctly (and flush out any bugs in the
>> toolchain)
>>
>> Now this rebuild should be done preferably in BR order when possible,
>> to rule out bad interaction between packages and be preferably be
>> fully done by alpha3 or beta1 at the latest so we have time to fix
>> it properly for Mageia 2.

(...)

> Rebuilding half of the distribution now seems the best way to add bugs
> before the release...

On the other hand, we my got bugs introduced when pushing a security
update due to the new toolchain not having been tested with those
packages...
Or having packages not rebuilding when patching them for security
fixes.

[Mageia-dev] libgphoto version: freeze buster?

[Colin Guthrie]

Hi,

When looking at https://bugs.mageia.org/show_bug.cgi?id=4177 I noticed
that libgphoto would need updated to support that camera model:

http://gphoto.org/news/


The version above what we have is supports these new cameras:

Kodak C1530
Sony DSC-HX100V, DSC-A1000, SLT-A55
Nikon CoolPix P7000, P7100, P500, L120, L23, S5100, S3100,
Nikon D2Hs, D5100
Canon EOS 10D, 1D Mark IV, 1100D, 600D
Canon PowerShot A2000IS, A3100IS,
Fuji FinePix F80EXR, X10
Apple iPad, iPhone 4
Panasonic DMC-TZ18, TZ20


This is a relatively edge package. Should we consider upgrading it and
pushing it through freeze?

I've built the package locally and it builds without any issues or
complications.

Thoughts?


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] mass rebuild for Mga 2 ?

[Julien]

Le Sun, 25 Mar 2012 16:51:57 +0200,
Angelo Naselli  a écrit :

> In data domenica 25 marzo 2012 14:48:01, Julien ha scritto:
> > Hello,
> > 
> > Is there a mass rebuild planned before mageia 2 ? And if not, is there a
> > value in rebuilding a package without update since 1 year ?
> Can you point us the list? Maybe we can consider if they can go, or have
> to be rebuild, or removed...
> 

I don't have a specific list, I just have a package (lsdvd) which hasn't be
modified since 11 months (no bug reported, no upstream release, etc.) and I
asked myself if it has value to rebuild it.

regards
Julien

Re: [Mageia-dev] [packages-commits] [226393] Migrate grub bootsplash params to new style: 'splash quiet' rather than 'splash=silent' (mga#3430)

[Luc Menut]

Le 25/03/2012 17:45, r...@mageia.org a écrit :

Revision
226393
Author
colin


[...]



+%triggerpostun backend -- drakxtools-backend<  14.1-2
+if [ -w /boot/grub/menu.lst ]; then
+  if grep -q splash= /boot/grub/menu.lst; then
+echo"Migrating kernel commandline bootsplash arguments in grub"
+sed -i 's/ splash=silent / splash quiet /;s/ splash=silent$/ splash 
quiet/;s/ splash=verbose / /;s/ splash=verbose$//;' /boot/grub/menu.lst
+  fi
+fi
+


IIUC this script, you update splash=silent & splash=verbose in 
/boot/grub/menu.lst for all the lines.
What happens if we have entries for mga1 or other distros in the same 
grub menu.lst ?

Aren't you going to break all these entries with such update?

Personaly, I use the same /boot/grub/menu.lst for mga 1 and cauldron.

regards,
Luc


--
Luc Menut

Re: [Mageia-dev] Freeze push request QuaZip 0.4.4

[Anssi Hannula]

25.03.2012 19:16, Anssi Hannula kirjoitti:
> 25.03.2012 17:50, Angelo Naselli kirjoitti:
>> According to quazip changelog (here below) it's a bug fixing release.
>>
>> mikala and me decided it should go on mga2, i tested applications
>> that require it and seem not to have problems.
>>  
>> QuaZIP changes
>>
>> * 2012-01-14 0.4.4
>> * Fixed isSequential() test that was causing open() failures on
>>   Unix.
>> * Fixed sub-directory compressing in JlCompress.
>> * Added MS VS 2008 solution, compatible with the binary Qt
>>   distribution (tested on MS VS 2008 Express, had to run MOC
>>   manually due to the lack of plugin in Express).
>> * Fixed extracting directories in JlCompress.
>> * Fixed JlCompress.h includes in the test suite, which used
>>   lowercase names thus breaking on case-sensitive systems.
>> * Implemented missing QuaZipFile::getZip() that was only
>>   declared.
>> * Fixed reopening closed files.
>> * Fixed possible memory leak in case of open error.
>>
>> Thanks in advance,
> 
> Submitted.
> 

Build failure.

-- 
Anssi Hannula

Re: [Mageia-dev] Freeze push request QuaZip 0.4.4

[Anssi Hannula]

25.03.2012 17:50, Angelo Naselli kirjoitti:
> According to quazip changelog (here below) it's a bug fixing release.
> 
> mikala and me decided it should go on mga2, i tested applications
> that require it and seem not to have problems.
>  
> QuaZIP changes
> 
> * 2012-01-14 0.4.4
> * Fixed isSequential() test that was causing open() failures on
>   Unix.
> * Fixed sub-directory compressing in JlCompress.
> * Added MS VS 2008 solution, compatible with the binary Qt
>   distribution (tested on MS VS 2008 Express, had to run MOC
>   manually due to the lack of plugin in Express).
> * Fixed extracting directories in JlCompress.
> * Fixed JlCompress.h includes in the test suite, which used
>   lowercase names thus breaking on case-sensitive systems.
> * Implemented missing QuaZipFile::getZip() that was only
>   declared.
> * Fixed reopening closed files.
> * Fixed possible memory leak in case of open error.
> 
> Thanks in advance,

Submitted.

-- 
Anssi Hannula

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Pascal Terjan]

On Sun, Mar 25, 2012 at 17:07, Kamil Rytarowski  wrote:

> **
> On 25.03.2012 17:20, Pascal Terjan wrote:
>
>
>
> On Sun, Mar 25, 2012 at 15:51, Angelo Naselli  wrote:
>
>> In data domenica 25 marzo 2012 14:48:01, Julien ha scritto:
>> > Hello,
>> >
>> > Is there a mass rebuild planned before mageia 2 ? And if not, is there a
>> > value in rebuilding a package without update since 1 year ?
>>  Can you point us the list? Maybe we can consider if they can go, or have
>> to be
>> rebuild, or removed...
>>
>
>  That's one third of the packages
>
>  [schedbot@valstar ~]$ ls
> /distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga1.src.rpm | wc -l
>  3420
> [schedbot@valstar ~]$ ls
> /distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga2.src.rpm | wc -l
> 6479
>
>  I have got a semi-automated script to do it.
>
> On 05.12.2011 15:26, Thomas Backlund wrote:
>
> Hi,
>
> so... the long wait is over
>
> I've submitted gcc-4.6.2-1.mga2 to core/release now.
>
> As soon as it's available on the primary mirror I'll invalidate the
> cauldron chroots on the BS to make sure the new gcc is used.
>
> Ater that I'll submit a new glibc and kernel so they are built with
> the new toolchain.
>
> So, we now have glibc & the toolchain upgraded:
> - glibc is at 2.14.1 (available in cauldron since 2011-10-24)
> - binutils 2.22 (available in cauldron since 2011-11-28)
> - gcc-4.6.2 (available later today (2011-12-05)
>
> Now, in order to provide a very good Mageia 2, every package should
> be rebuilt with the new toolchain/glibc in order to make sure they
> still build _and_ work correctly (and flush out any bugs in the
> toolchain)
>
> Now this rebuild should be done preferably in BR order when possible,
> to rule out bad interaction between packages and be preferably be
> fully done by alpha3 or beta1 at the latest so we have time to fix
> it properly for Mageia 2.
>
> --
> Thomas
>
>
> So we should focus not on the mga1 packages but not [re]bulded since
> pushing the 4.6.2.
>
> On 06.12.2011 00:13, Thomas Backlund wrote:
>
> 05.12.2011 16:26, Thomas Backlund skrev:
>
> Hi,
>
> so... the long wait is over
>
> I've submitted gcc-4.6.2-1.mga2 to core/release now.
>
> As soon as it's available on the primary mirror I'll invalidate the
> cauldron chroots on the BS to make sure the new gcc is used.
>
> Ater that I'll submit a new glibc and kernel so they are built with
> the new toolchain.
>
>
>
> New gcc-4.6.2-1.mga2, glibc-2.14.1-3.mga2, kernel-3.1.4-2.mga2 are now on
> the mirrors.
>
> --
> Thomas
>
> So 6th December is the day when new toolchain landed on the mirrors and
> all older packages should be rebuilt.
>
> I will prepare a tracker to monitor it according to the package
> maintainership. :)
>


Rebuilding half of the distribution now seems the best way to add bugs
before the release...

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Kamil Rytarowski]

On 25.03.2012 17:20, Pascal Terjan wrote:



On Sun, Mar 25, 2012 at 15:51, Angelo Naselli > wrote:


In data domenica 25 marzo 2012 14:48:01, Julien ha scritto:
> Hello,
>
> Is there a mass rebuild planned before mageia 2 ? And if not, is
there a
> value in rebuilding a package without update since 1 year ?
Can you point us the list? Maybe we can consider if they can go,
or have to be
rebuild, or removed...


That's one third of the packages

[schedbot@valstar ~]$ ls 
/distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga1.src.rpm | wc -l

3420
[schedbot@valstar ~]$ ls 
/distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga2.src.rpm | wc -l

6479


I have got a semi-automated script to do it.

On 05.12.2011 15:26, Thomas Backlund wrote:

Hi,

so... the long wait is over

I've submitted gcc-4.6.2-1.mga2 to core/release now.

As soon as it's available on the primary mirror I'll invalidate the 
cauldron chroots on the BS to make sure the new gcc is used.


Ater that I'll submit a new glibc and kernel so they are built with
the new toolchain.

So, we now have glibc & the toolchain upgraded:
- glibc is at 2.14.1 (available in cauldron since 2011-10-24)
- binutils 2.22 (available in cauldron since 2011-11-28)
- gcc-4.6.2 (available later today (2011-12-05)

Now, in order to provide a very good Mageia 2, every package should
be rebuilt with the new toolchain/glibc in order to make sure they
still build _and_ work correctly (and flush out any bugs in the
toolchain)

Now this rebuild should be done preferably in BR order when possible,
to rule out bad interaction between packages and be preferably be
fully done by alpha3 or beta1 at the latest so we have time to fix
it properly for Mageia 2.

--
Thomas


So we should focus not on the mga1 packages but not [re]bulded since 
pushing the 4.6.2.


On 06.12.2011 00:13, Thomas Backlund wrote:

05.12.2011 16:26, Thomas Backlund skrev:

Hi,

so... the long wait is over

I've submitted gcc-4.6.2-1.mga2 to core/release now.

As soon as it's available on the primary mirror I'll invalidate the
cauldron chroots on the BS to make sure the new gcc is used.

Ater that I'll submit a new glibc and kernel so they are built with
the new toolchain.



New gcc-4.6.2-1.mga2, glibc-2.14.1-3.mga2, kernel-3.1.4-2.mga2 are now 
on the mirrors.


--
Thomas
So 6th December is the day when new toolchain landed on the mirrors and 
all older packages should be rebuilt.


I will prepare a tracker to monitor it according to the package 
maintainership. :)

[Mageia-dev] Freeze push - drakx-installer-help

[Kamil Rytarowski]

Hello!
Please push new drakx-installer-help

Change log:
- new tarball 2.3
* update doc files (from 2012-03-23)
* delete from README information that the doc files are available also 
after installation


And then please rebuild drakx-installer-stage2 against the new 
drakx-installer-help package.


Regards!

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Pascal Terjan]

On Sun, Mar 25, 2012 at 15:51, Angelo Naselli  wrote:

> In data domenica 25 marzo 2012 14:48:01, Julien ha scritto:
> > Hello,
> >
> > Is there a mass rebuild planned before mageia 2 ? And if not, is there a
> > value in rebuilding a package without update since 1 year ?
> Can you point us the list? Maybe we can consider if they can go, or have
> to be
> rebuild, or removed...
>

That's one third of the packages

[schedbot@valstar ~]$ ls
/distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga1.src.rpm | wc -l
3420
[schedbot@valstar ~]$ ls
/distrib/mirror/distrib/cauldron/SRPMS/core/release/*.mga2.src.rpm | wc -l
6479

Re: [Mageia-dev] freez push clamav-0.97.4

[Maarten Vanraes]

Op zondag 25 maart 2012 00:21:36 schreef Colin Guthrie:
> 'Twas brillig, and Thomas Spuhler at 24/03/12 22:49 did gyre and gimble:
> > On Saturday, March 24, 2012 12:36:06 PM Sander Lepik wrote:
> >> On Mar 24, 2012 9:13 PM, "Thomas Spuhler"  wrote:
> >>> please push clamav-0.97.4
> >>> --
> >>> Best regards
> >>> Thomas Spuhler
> >> 
> >> Why?
> >> 
> >> --
> >> Sander
> > 
> > it's an upgrade from 0.97.4
> > We need to provide the newest version of the antivirus package
> 
> This, by itself, is not a very good explanation.
> 
> If this is purely a definitions update then that's fine.
> If this is a bugfix update that's probably fine too (depending on the bug)
> If it's a new feature update then that likely won't make it.
> 
> People are all very busy. It only takes the person requesting the push a
> minute or two to describe things properly. Please give your busy
> colleagues the respect they deserve and provide good explanations to
> save them having to spend time discussing and asking further questions.
> 
> We still don't really have enough information to decide on this one!
> 
> So please state whether it's just definitions or bugfix (and if so what
> bugs) etc.
> 
> Col

IIUC older clamav engines aren't supported, and stop working. but the reason 
given was indeed not enough.

keep in mind that new features for this often means a security fix :-D

i think this'll likely go through, but the original poster should check to see 
how things are, and report them accurately.

Re: [Mageia-dev] mass rebuild for Mga 2 ?

[Angelo Naselli]

In data domenica 25 marzo 2012 14:48:01, Julien ha scritto:
> Hello,
> 
> Is there a mass rebuild planned before mageia 2 ? And if not, is there a
> value in rebuilding a package without update since 1 year ?
Can you point us the list? Maybe we can consider if they can go, or have to be 
rebuild, or removed...

-- 
Angelo


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

[Mageia-dev] Freeze push request QuaZip 0.4.4

[Angelo Naselli]

According to quazip changelog (here below) it's a bug fixing release.

mikala and me decided it should go on mga2, i tested applications
that require it and seem not to have problems.
 
QuaZIP changes

* 2012-01-14 0.4.4
* Fixed isSequential() test that was causing open() failures on
  Unix.
* Fixed sub-directory compressing in JlCompress.
* Added MS VS 2008 solution, compatible with the binary Qt
  distribution (tested on MS VS 2008 Express, had to run MOC
  manually due to the lack of plugin in Express).
* Fixed extracting directories in JlCompress.
* Fixed JlCompress.h includes in the test suite, which used
  lowercase names thus breaking on case-sensitive systems.
* Implemented missing QuaZipFile::getZip() that was only
  declared.
* Fixed reopening closed files.
* Fixed possible memory leak in case of open error.

Thanks in advance,
-- 
Angelo


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

Re: [Mageia-dev] Push request : oxygen -gtk

[Colin Guthrie]

'Twas brillig, and Hugo Pereira Da Costa at 24/03/12 19:03 did gyre and
gimble:
> On 03/24/2012 10:20 AM, Anne nicolas wrote:
>> 2012/3/24 D.Morgan:
>>> Hi,
>>>
>>>
>>> Please push oxygen-gtk it bring back version 1.2.2 but with the
>>> regression fixed.
>>>
>>>
>>> I tested and i can't reproduce the crashes ( like in mcc )
>> Done
> Hello,
> 
> just to double-check,
> 
> the new oxygen-gtk2 release should be oxygen-gtk2-1.2.2-1.tar.gz
> (available at
> http://download.kde.org/download.php?url=stable/oxygen-gtk2/1.2.2-1/src/oxygen-gtk2-1.2.2-1.tar.bz2)
> 
> 
> Also I'd recommand to update oxygen-gtk3 (should be
> oxygen-gtk3-1.0.2-1.tar.gz,
> available at
> http://download.kde.org/download.php?url=stable/oxygen-gtk3/1.0.2-1/src/oxygen-gtk3-1.0.2-1.tar.bz2)
> 
> since many of the issues with gtk3.3 have been fixed in this release.

Just wanted to say a quick thank you Hugo for keeping us up-to-speed here :)

Much appreciated!

KUTGW!

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] Bug squash party update

[Colin Guthrie]

'Twas brillig, and Remco Rijnders at 25/03/12 13:29 did gyre and gimble:
> The experiences so far have been mixed. We now have 7 more release
> blockers than at the start of the weekend, with none closed since friday
> afternoon. The uptake has been less than we had hoped for, but the
> upside is that people are performing tests, and also that open bugs are
> being reassesed as to their severity.

This isn't strictly true. e.g. there are some tracker bugs that are
themselves release blockers and those tracker bugs then have bugs that
block them. I've been busy fixing and closing a few bug reports that
related to the systemd tracker for example:
https://bugs.mageia.org/show_bug.cgi?id=2120

> That no release blockers have been fixed yet is a bit of a shame, but
> that does not mean that no work has been done on them. On several of the
> bugs we have open we've seen promising progress in the past few days.

As per above, saying "none closed since Friday" or "no release blockers
have been fixed yet" is actually not quite true. Sadly, of course, this
means that when you expand out the bugs you probably now have a lot more
real release blocking bugs than you previously thought! :D

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] Bug squash party update

[Rémi Verschelde]

2012/3/25 Remco Rijnders :
>
> If you are still willing to help out, I'd like to invite you to have a look
> at our release blocking bugs [1], today, tomorrow, or even after this party
> is over. For those of you testing the latest ISO's (beta 2), please have a
> look at the known errata [2].
>

Remmy forgot to add the links, so they should probably be:
[1] 
https://bugs.mageia.org/buglist.cgi?priority=release_blocker&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED
[2] https://wiki.mageia.org/en/Mageia_2_Errata

Regards,
Rémi / Akien

[Mageia-dev] mass rebuild for Mga 2 ?

[Julien]

Hello,

Is there a mass rebuild planned before mageia 2 ? And if not, is there a
value in rebuilding a package without update since 1 year ?

regards
Julien

Re: [Mageia-dev] Push request : oxygen -gtk

[D.Morgan]

On Sat, Mar 24, 2012 at 8:03 PM, Hugo Pereira Da Costa
 wrote:
> On 03/24/2012 10:20 AM, Anne nicolas wrote:
>>
>> 2012/3/24 D.Morgan:
>>>
>>> Hi,
>>>
>>>
>>> Please push oxygen-gtk it bring back version 1.2.2 but with the
>>> regression fixed.
>>>
>>>
>>> I tested and i can't reproduce the crashes ( like in mcc )
>>
>> Done
>
> Hello,
>
> just to double-check,
>
> the new oxygen-gtk2 release should be oxygen-gtk2-1.2.2-1.tar.gz
> (available at
> http://download.kde.org/download.php?url=stable/oxygen-gtk2/1.2.2-1/src/oxygen-gtk2-1.2.2-1.tar.bz2)

yes this is the one i used


>
> Also I'd recommand to update oxygen-gtk3 (should be
> oxygen-gtk3-1.0.2-1.tar.gz,
> available at
> http://download.kde.org/download.php?url=stable/oxygen-gtk3/1.0.2-1/src/oxygen-gtk3-1.0.2-1.tar.bz2)
> since many of the issues with gtk3.3 have been fixed in this release.


funda updated using this tarball too.

[Mageia-dev] Bug squash party update

[Remco Rijnders]

Dear all,

A brief update on our bug squashing efforts so far since the original blog 
post went out. I realise in there we wrote that there would be daily 
updates, but as there has been little news to report, I hope you can 
forgive me for this. Now, with about 2/3rd of the weekend behind us, this 
seems like a good time for an update.


The experiences so far have been mixed. We now have 7 more release 
blockers than at the start of the weekend, with none closed since friday 
afternoon. The uptake has been less than we had hoped for, but the upside 
is that people are performing tests, and also that open bugs are being 
reassesed as to their severity.


People have mostly been quietly working on 'their' bug reports, as they've 
been doing all along. To all of them I want to express gratitude for their 
ongoing work on making Mageia better. Also, over the course of the weekend 
we have seen some new faces helping out in testing and adding their 
comments to open bug reports. This is most welcome indeed!


That no release blockers have been fixed yet is a bit of a shame, but that 
does not mean that no work has been done on them. On several of the bugs 
we have open we've seen promising progress in the past few days.


If you are still willing to help out, I'd like to invite you to have a 
look at our release blocking bugs [1], today, tomorrow, or even after this 
party is over. For those of you testing the latest ISO's (beta 2), please 
have a look at the known errata [2].


Thank you all for your time and attention :-)

Sincerely,

Remmy


pgpFkbBn4F1hd.pgp
Description: PGP signature

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release drakx-installer-stage2-14.1-2.mga2

[Thierry Vignaud]

On 25 March 2012 13:34, Thomas Backlund  en eus skrivet:
 We need to actually include the fsck for btrfs...
>>>
>>> Oh has it actually got a proper fsck now?
>>
>> This is what I understood after reading brtfs-progs changelog
>
> Yep.
>
> We are now using the "dangerdonteveruse" branch :)
>
> wich is supposed to be the final rewrite of the btrfs-progs and was
> scheduled for release around Feb 15th... (2012 if you wonder...)
>
> I'm monitoring the btrfs@ ml and the upstream git tree to see if
> problems/bugfixes show up, but seems pretty quiet regarding current code
for btrfs.

Also you need to patch diskdrake so that it nows what fsck program to use.

Re: [Mageia-dev] [Freeze Push] liferea 1.8.3

[Julien]

Le Sat, 24 Mar 2012 14:11:06 +0100,
Julien  a écrit :

> Hi,
> 
> please push liferea 1.8.3 which fix the UI freeze when updating or Mark as
> Read feeds with ext4. It's an old bug which plague liferea since ages.
> 
> regards
> Julien

ping ?

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release drakx-installer-stage2-14.1-2.mga2

[Thomas Backlund]

Thierry Vignaud skrev 25.3.2012 14:18:

On 25 March 2012 13:04, Colin Guthrie  wrote:

tmb  14.1-2.mga2:
+ Revision: 226231
- rebuild for new xfsprogs and btrfs-progs


We need to actually include the fsck for btrfs...


Oh has it actually got a proper fsck now?


This is what I understood after reading brtfs-progs changelog


Yep.

We are now using the "dangerdonteveruse" branch :)

wich is supposed to be the final rewrite of the btrfs-progs and was 
scheduled for release around Feb 15th... (2012 if you wonder...)


I'm monitoring the btrfs@ ml and the upstream git tree to see if 
problems/bugfixes show up, but seems pretty quiet regarding current code.


--
Thomas

Re: [Mageia-dev] Freeze push - drakx-installer-help 2.2 and rebuild drakx-installer-stage2

[nicolas vigier]

On Sun, 25 Mar 2012, Thierry Vignaud wrote:

> On 25 March 2012 12:57, nicolas vigier  wrote:
>  Please push new drakx-installer-help 2.2
>  - new version 2.2
>  * add new images: note.png tip.png and warning.png
>  * fix typo in README (thanks Simon Parsons)
> 
>  And rebuild against new drakx-installer-help drakx-installer-stage2
> >>> Please do NOT push it at the moment, the added icons are wrong and shall
> >>> be fixed soon.
> >> OK, please push the package now! The icons are fixed.
> >
> > Submitted.
> 
> You still need to rebuild d-i-stage2 now

drakx-installer-stage2 now submitted.

Re: [Mageia-dev] Freeze push - drakx-installer-help 2.2 and rebuild drakx-installer-stage2

[Thierry Vignaud]

On 25 March 2012 12:57, nicolas vigier  wrote:
 Please push new drakx-installer-help 2.2
 - new version 2.2
 * add new images: note.png tip.png and warning.png
 * fix typo in README (thanks Simon Parsons)

 And rebuild against new drakx-installer-help drakx-installer-stage2
>>> Please do NOT push it at the moment, the added icons are wrong and shall
>>> be fixed soon.
>> OK, please push the package now! The icons are fixed.
>
> Submitted.

You still need to rebuild d-i-stage2 now

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release drakx-installer-stage2-14.1-2.mga2

[Thierry Vignaud]

On 25 March 2012 13:04, Colin Guthrie  wrote:
>>> tmb  14.1-2.mga2:
>>> + Revision: 226231
>>> - rebuild for new xfsprogs and btrfs-progs
>>
>> We need to actually include the fsck for btrfs...
>
> Oh has it actually got a proper fsck now?

This is what I understood after reading brtfs-progs changelog

[Mageia-dev] freeze push request: scite

[Matteo]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,
can somebody push scite 3.0.4?
It fixes a lot of bugs (since our last version was 2.29,
http://www.scintilla.org/ScintillaHistory.html).
Now it works fine even with gtk3 (version 3.0.3 fixed a gtk3 related bug
about printing).
This package is owned by anaselli cause it was built while he was
mentoring me.
Regards
- -- 
Matteo
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPbv7SAAoJED3LowjDDWbNknsH/341vZMxTSkpyYqrP20J6rca
QGc3LFKAfQpFupDq7LjGrA1ZlzqGWSImm+rd73kQ/op3cvjtch+aly1db8y9tcCE
QDfbBdRc+PSfA39XPhrz6/EPuY76Kmja1XWA3YPmm0J1jy//nLN2Icu3SG3T5HoP
J8G8FBECisO06AQSup8bAmCqZN2rjRZKmIFk1Olu5ZOp7HC2ENCZfKeDPuXXm/GS
DuvneXc1mOrRW666x2m6+WEkEGiUJ3JSQAWYlEorxA887EuR2x8nXNtww3dF7uCK
XYF30Ei4DOn2DqzxKReCOnhKbybln6Y9xmuyZXLn5GFzAQYjbHeCU8/b3orN+SI=
=pxA4
-END PGP SIGNATURE-

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release drakx-installer-stage2-14.1-2.mga2

[Colin Guthrie]

'Twas brillig, and Thierry Vignaud at 25/03/12 11:48 did gyre and gimble:
> On 25 March 2012 03:54, tmb  wrote:
>> tmb  14.1-2.mga2:
>> + Revision: 226231
>> - rebuild for new xfsprogs and btrfs-progs
> 
> We need to actually include the fsck for btrfs...

Oh has it actually got a proper fsck now?

-- 

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] Freeze push - drakx-installer-help 2.2 and rebuild drakx-installer-stage2

[nicolas vigier]

On Sat, 24 Mar 2012, Kamil Rytarowski wrote:

> On 22.03.2012 16:20, Kamil Rytarowski wrote:
>> On 22.03.2012 14:20, Kamil Rytarowski wrote:
>>> Hello!
>>>
>>> Please push new drakx-installer-help 2.2
>>> - new version 2.2
>>> * add new images: note.png tip.png and warning.png
>>> * fix typo in README (thanks Simon Parsons)
>>>
>>> And rebuild against new drakx-installer-help drakx-installer-stage2
>> Please do NOT push it at the moment, the added icons are wrong and shall 
>> be fixed soon.
> OK, please push the package now! The icons are fixed.

Submitted.

Re: [Mageia-dev] reeze push: drakconf

[nicolas vigier]

On Sun, 25 Mar 2012, Thierry Vignaud wrote:

> On 24 March 2012 08:02, Thierry Vignaud  wrote:
> > Hi
> >
> > Please let in drakconf: latest translations
> >
> > See you
> 
> Ping?

Submitted.

Re: [Mageia-dev] reeze push: drakconf

[Thierry Vignaud]

On 24 March 2012 08:02, Thierry Vignaud  wrote:
> Hi
>
> Please let in drakconf: latest translations
>
> See you

Ping?

Re: [Mageia-dev] [changelog] [RPM] cauldron core/release drakx-installer-stage2-14.1-2.mga2

[Thierry Vignaud]

On 25 March 2012 03:54, tmb  wrote:
> tmb  14.1-2.mga2:
> + Revision: 226231
> - rebuild for new xfsprogs and btrfs-progs

We need to actually include the fsck for btrfs...

Re: [Mageia-dev] [Freeze Push] compiz 0.9.7.2

[Julien]

Le Sat, 24 Mar 2012 13:54:08 +0100,
Julien  a écrit :

> Le Fri, 23 Mar 2012 10:33:09 +0100,
> Julien  a écrit :
> 
> > Hi,
> > 
> > Please push compiz 0.9.7.2, it's a bugfix release with fix for crash and
> > bugs in input handling.
> > 
> > When it's built, please push libcompizconfig (bzr429) which fix a
> > crasher in shortcut handling. (not sure I can push it myself ?)
> > 
> > If noone beats me, I'll rebuild compiz-plugins-(main|extra) and
> > compizconfig-python after that.
> > 
> > regards
> > Julien
> 
> Ping ?

I saw ennael pushed it and funda rebuilt plugins and config. Thanks to both
of you.

regards
Julien