Bug 10316 - guake terminal won't run because of missing python-pyxdg dependency
Summary: guake terminal won't run because of missing python-pyxdg dependency
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA3-64-OK MGA3-32-OK advisory
Keywords: validated_update
Depends on:
Blocks:
 
Reported: 2013-05-27 15:07 CEST by Atilla ÖNTAŞ
Modified: 2014-02-17 01:35 CET (History)
6 users (show)

See Also:
Source RPM: guake-0.4.4-2mga3.src.rpm
CVE:
Status comment:


Attachments

Description Atilla ÖNTAŞ 2013-05-27 15:07:40 CEST
Description of problem:
Guake package in Mageia3 misses python-pyxdg package dependency. Without this package it won't run. Specfile needs to be modified as Requires: python-pyxdg
This issue is fixed in Cauldron but should be updated/pushed to Mageia3

Version-Release number of selected component (if applicable):
guake-0.4.4-2mga3

How reproducible:
Install guake package and run guake from commandline. You can see it complains about python-xdg module is missing and refuses to run.

Steps to Reproduce:
1- $guake
2- see the missing python-xdg module error.

Reproducible: 

Steps to Reproduce:
Comment 1 Jani Välimaa 2013-05-27 17:22:15 CEST
Release is wrongly bumped in SVN for mga3. Only subrel should've added. Please revert %mkrel to 2.

CC: (none) => jani.valimaa

Comment 2 Jani Välimaa 2013-05-27 17:26:19 CEST
(In reply to Jani Välimaa from comment #1)
> Release is wrongly bumped in SVN for mga3. Only subrel should've added.
> Please revert %mkrel to 2.

Also, please don't mix tab and spaces. Use which ever is used in the rest of the .spec.
Comment 3 Atilla ÖNTAŞ 2013-05-27 23:34:26 CEST
(In reply to Jani Välimaa from comment #2)
Fixed in svn. Thank you pointing out.
Comment 4 Jani Välimaa 2013-05-28 09:40:47 CEST
Thanks.

One more thing, use SILENT in commit msgs you don't want to end to %changelog. There's a page about using SILENT somewhere in our wiki. IMHO commits fixing previous commits or changes which doesn't affect to pkg itself should not end to %changelog. You can edit commit msgs afterwards with 'svn propedit' [1].

However, I'll submit guake tonight to core/updates_testing.

[1] https://wiki.mageia.org/en/Packagers_svn#In_case_of_misspell.2C_how_can_I_edit_svn:log.3F
Comment 5 Jani Välimaa 2013-05-28 18:40:44 CEST
(In reply to Jani Välimaa from comment #4)
> 
> However, I'll submit guake tonight to core/updates_testing.
> 

Seems like it's already done. New release [1] is ready for validation.

[1] guake-0.4.4-2.1.mga3
Comment 6 Atilla ÖNTAŞ 2013-10-28 22:17:04 CET
Fixed in Mageia 3 and Cauldron. Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 7 Samuel Verschelde 2014-01-28 09:45:31 CET
Atilla, where do you see if fixed in Mageia 3? An update in Core Updates Testing is not "Fixed", it's pending. 

This bug report should be assigned to QA team for validation so that it reaches Core Updates for all users.

Status: RESOLVED => REOPENED
CC: (none) => stormi
Resolution: FIXED => (none)

Comment 8 Atilla ÖNTAŞ 2014-01-28 10:06:04 CET
(In reply to Samuel VERSCHELDE from comment #7)
You' re right. My mistake, but i learned a lot about bugs triage since October.
Comment 9 Samuel Verschelde 2014-01-28 10:11:30 CET
According to comment #5, the packager wants the update to be validated, but it hasn't been assigned to QA and there's no advisory text
Comment 10 Jani Välimaa 2014-02-10 06:26:55 CET
Don't get all this wrong, but all I did was some commenting about pkg'ing issues and stated that someone else pushed pkg to BS and thus it's available. Never did any commits etc. I'd say one/ones who started all this should also finish it.
Comment 11 Atilla ÖNTAŞ 2014-02-10 08:21:32 CET
(In reply to Jani Välimaa from comment #10)
> Don't get all this wrong, but all I did was some commenting about pkg'ing
> issues and stated that someone else pushed pkg to BS and thus it's
> available. Never did any commits etc. I'd say one/ones who started all this
> should also finish it.

Thank you Jani. Sorry for bothering you. I was long forgotten who pushed that. I have send mail to the packager who pushed this and asked to write an advisory or permit me to do so.
Comment 12 Jani Välimaa 2014-02-10 08:55:33 CET
No problem.

Atilla, you can write an advisory. Someone in QA team then pushes it to where it belongs.
Comment 13 Jani Välimaa 2014-02-10 08:56:30 CET
(In reply to Atilla ÃNTAÅ from comment #11)
> (In reply to Jani Välimaa from comment #10)
> > Don't get all this wrong, but all I did was some commenting about pkg'ing
> > issues and stated that someone else pushed pkg to BS and thus it's
> > available. Never did any commits etc. I'd say one/ones who started all this
> > should also finish it.
> 
> Thank you Jani. Sorry for bothering you. I was long forgotten who pushed
> that. I have send mail to the packager who pushed this and asked to write an
> advisory or permit me to do so.

Perhaps it was your mentor who pushed guake to BS.
Comment 14 Atilla ÖNTAŞ 2014-02-10 10:35:38 CET
Guake package has been updated for Mageia 3

You can test this by installing guake-0.4.4-2.1.mga3

Suggested advisory:
========================

Updated guake-0.4.4-2.1.mga3 package fix this issue:

Guake package in Mageia3 misses python-pyxdg package dependency. Without this package it won't run. This update brings python-pyxdg package as a required dependency for the guake package.
========================

Updated packages in core/updates_testing:
========================
guake-0.4.4-2.1.mga3

Source RPMs: 
========================
guake-0.4.4-2.1.mga3.src.rpm

Assignee: bugsquad => qa-bugs

Comment 15 Rémi Verschelde 2014-02-13 15:46:50 CET
Testing complete Mageia 3 x86_64.

CC: (none) => remi
Whiteboard: (none) => MGA3-64-OK

Comment 16 Malo Deniélou 2014-02-16 14:21:26 CET
Testing i586, MGA3.

CC: (none) => pierre-malo.denielou

Comment 17 Malo Deniélou 2014-02-16 14:32:50 CET
Testing complete Mageia 3 i586. It now starts and runs nicely.

However, during install, I get this warning (from the post script):
(gconftool-2:4262): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

But it's not a regression (it happens with the mga3 package as well).

Whiteboard: MGA3-64-OK => MGA3-64-OK MGA3-32-OK

Comment 18 Rémi Verschelde 2014-02-16 14:56:51 CET
Validating update, advisory has been uploaded. Please push to 3 core/updates.

Keywords: (none) => validated_update
Whiteboard: MGA3-64-OK MGA3-32-OK => MGA3-64-OK MGA3-32-OK advisory
CC: (none) => sysadmin-bugs

Comment 19 Thomas Backlund 2014-02-17 01:35:40 CET
Update pushed:
http://advisories.mageia.org/MGAA-2014-0051.html

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


Note You need to log in before you can comment on or make changes to this bug.