Created attachment 560 [details]
kshutdown spec file

I attached spec file adaptation from Mandriva spec file. I tested it on my laptop KDE 64-bits and it looks like ok.

Package is imported on svn & should be soon available on cauldron.

CC: (none) => balcaen.john

Is it possible to backport it to Mageia 1? Thanks.

CC: (none) => olivier.delaune

lol, Sophie gives a French summary:

[15:15] <Sophie> KShutDown est un outils avancé de gestion de l'extinction // core-release (Mga, cauldron, i586)

The package doesn't need to be backported, because it is in Mdv

assigning to maintainer

Keywords: Backport => (none)
CC: (none) => marja11
Assignee: bugsquad => juan.baptiste
Source RPM: (none) => kshutdown
Whiteboard: (none) => Mdv, cauldron

I don't understand very well which is the problem here ? the spec file has the Summary tag both in english and french:


Summary:        Advanced shut down utility for KDE
Summary(fr):    KShutDown est un outils avancé de gestion de l'extinction

Maybe you see the french text because of your locale?

This was the first time Sophie showed me a summary in French on IRC.
But I don't mind, j'aime la France et les Français(es) :D

BTW, it was assigned to you because of the request to package it for Mga 1 ;)

Indeed, but I have no idea why sophie shows the french version instead of the default english version. Also this is the first time I see a spec file with a localized Summary ?

(In reply to comment #8)
> Indeed, but I have no idea why sophie shows the french version instead of the
> default english version. Also this is the first time I see a spec file with a
> localized Summary ?

Ok I talked about this with mikala on IRC and he tells me this is an RPM bug that is already fixed on cauldron.

(In reply to comment #8)
> Indeed, but I have no idea why sophie shows the french version instead of the
> default english version. Also this is the first time I see a spec file with a
> localized Summary ?

I am a beginner in packaging so I do not know the usage about locale. I saw
that in other spec file. If there is any problem, I guess you can remove it.

So, it isn't clear to me what I have to do. If it doesn't needs to be backported because it was already on Mandriva, should I push it as an update ?

@ Juan Luis

Just do the same as was done for bug 1502 and 2641, those packages were in Mdv, too and got packaged for cauldron first.

Please push to 1/updates_testing and assign to QA testing :) After they validate the package, it'll be pushed from testing to 1/updates :)

The current kshutdown 2.0 doesn't compile on cauldron :(

I'll have to dig deeper into this and see if I can come up with a patch. Also I'll try with latest 2.1 beta version. That version could be sent to updates_testing ? or just the patched 2.0 version ?

2.1beta fails too, but anyway, this is on cauldron with KDE 4.7.3 so I still should push the update for mga 1 as this problem won't happen there ;)

And I'll try to figure out how to fix this problem for cauldron later.

hmmm but if the package isn't in mga 1, how can I push the update ? the updates policy says to check out the mga 1 version, update/fix, set subrel it and push to updates_testing.

How should be the procedure in this case ?

(In reply to comment #15)
> hmmm but if the package isn't in mga 1, how can I push the update ? the updates
> policy says to check out the mga 1 version, update/fix, set subrel it and push
> to updates_testing.
> 
> How should be the procedure in this case ?

hmm, all I know is that packages that were in Mdv 2010.x, can be packaged for 1, no need to backport them, and that I've seen them go in 1/updates

@ Florian

Can you help Juan Luis with the correct procedure?

CC: (none) => doktor5000

Meanwhile, I found:

https://wiki.mageia.org/en/Updates_policy#Version_Policy

item 3:
We will make exceptions for packages that did not make it into mga1 and are additions to the distribution, provided they do not impact any other packages and can pass full QA.

https://wiki.mageia.org/en/Mgarepo#The_package_doesn.27t_exist_yet_in_Mageia_1

Version/Release of a package in stable must be behind cauldron.

So:
1. bump release for cauldron
2. use subrel for stable/updates

CC: (none) => n54

(In reply to comment #18)
> https://wiki.mageia.org/en/Mgarepo#The_package_doesn.27t_exist_yet_in_Mageia_1
> 
> Version/Release of a package in stable must be behind cauldron.
> 
> So:
> 1. bump release for cauldron
> 2. use subrel for stable/updates

So I do a checkout directly from cauldron, do 1 and 2 and submit to updates_testing ? I thought that there was a restriction on that and mgarepo won't let me do that submit... I'm not at my machine right now so I can't test it.

1) Copy the package from cauldron's tree into updates/1's tree:
svn cp svn+ssh://svn.mageia.org/svn/packages/cauldron/kshutdown svn+ssh://svn.mageia.org/svn/packages/updates/1/kshutdown

2)Edit cauldron's package and bump release (+1)

3)If there is need to edit something in updates/1's version then don't touch Release number! Just add: "%define subrel 1" at the beginning of the .spec.

And yes, submit into updates_testing and then assign the bug to QA asking to test it.

(next time don't ask the bugsquad instead of your mentor / another packagers...)

(In reply to comment #22)
> (next time don't ask the bugsquad instead of your mentor / another
> packagers...)

Sorry :(

There's a last issue here: currently kshutdown doesn't compile on cauldron with the latest KDE, not even the latest 2.1 beta (which I haven't updated to yet on cauldron), so I can't submit to the BS the bumped cauldron version. I suppose this isn't an issue while mga 2 isn't out, right ?

Ok, update pushed to updates_testing. As this package didn't exist in mga 1, it still needs some kind of advisory ?

Yes, it needs advisory.
Please note that for mentioning bugs in change log we have to write "- resolved bug description (mga #NUMBER)"

Testing complete on i586 for the srpm
kshutdown-2.0-1.mga1.src.rpm

Confirmed it showed up in the menu under Tools/System Tools.
Confirmed it could do a timed logout.

It correctly notified me I had disabled the show shutdown
options, disabling the option to try to have it shutdown.

CC: (none) => davidwhodgins

Advisory:

The KShutDown program was available on Mandriva 2010.x but it wasn't on Mageia 1. This update makes it available on Mageia 1.

We still need x86-64 testing for kshutdown.

I would like to test 64-bit version but I see nothing in Testing repo on Mga1.

(In reply to comment #29)
> I would like to test 64-bit version but I see nothing in Testing repo on Mga1.

Hello Olivier,

Yet the package is indeed in the Media Core_Updates_Testing :

v kshutdown:
2.0-1.mga1 // core-updates_testing (Mga, 1, x86_64)
2.0-1.mga1 // core-updates_testing (Mga, 1, i586)


You'd have to refresh the media with the command (as root):

# urpmi.update Release Updates Backports

CC: (none) => geiger.david68210

Indeed :/
everything works fine. I tested, screen lock, rebbot and shutdown.

Testing complete on Mageia release 1 (Official) for x86_64 ,it work fine.

-Installation, Ok
-Restart Computer, Ok
-Turn Off Computer, Ok
-lock Screen, Ok
-Logout, Ok
-Hibernate Computer, Ok
-With a selected time, it is also OK.

Sorry, but I found a minor problem.
If I select "lock screen", when I log me to unlock, style has changed (set at IaOra-kde instead of oxygen before locking sreen), and color too (set at Ia Ora Night instead of Oxygen).

Are you sure that you didn't install anything else when you installed kshutdown from update_testing repo ? can you reproduce that problem ?

Change back to oxygen theme, select "lock screen" and unlock to see if it happens again.

I rebooted my laptop and now I have not this problem anymore. So ok for me.

Validating the update.

Could someone from the sysadmin team push the srpm
kshutdown-2.0-1.mga1.src.rpm
from Core Updates Testing to Core Updates

Advisory:  This update adds the kshutdown package, an advanced shut down
utility for KDE, which was available in Mandriva 2010.2, but missing from
Mageia 1.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

$ kshutdown 
GDM: <FOUND>
GNOME: <FOUND>
Xfce: not detected
KDE Full Session: not detected
KDE 4: not detected
KDM: not detected
WARNING: GNOME/Xfce desktop and/or GDM (login manager) are not supported yet.
         Some functions may be unavailable.
         Try GShutdown which is more compatible with GNOME/GDM and Xfce.
         http://gshutdown.tuxfamily.org/

No luck here.

(In reply to comment #37)
> $ kshutdown 
> GDM: <FOUND>
> GNOME: <FOUND>
> WARNING: GNOME/Xfce desktop and/or GDM (login manager) are not supported yet.
>          Some functions may be unavailable.
>          Try GShutdown which is more compatible with GNOME/GDM and Xfce.
>          http://gshutdown.tuxfamily.org/
> 
> No luck here.

Maybe because kshutdown is done for KDE and you are in GNOME, I think you should use gshutdown as the warning is telling you...

Yes I know, my intention was to help with tests.. but I won't install KDE just for this.

And it seems there is no Gshutdown in Mageia.

Update pushed.

Status: ASSIGNED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED