Bug 3796 - 2_a2: /usr/share/doc/mariadb/README.urpmi reference to non-existent /etc/rc.d/init.d/mysqld
Summary: 2_a2: /usr/share/doc/mariadb/README.urpmi reference to non-existent /etc/rc.d...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: AL13N
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2011-12-17 16:18 CET by Bit Twister
Modified: 2011-12-17 21:26 CET (History)
0 users

See Also:
Source RPM: mariadb-5.5.18-0.bzr3169.20111216.mga2.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2011-12-17 16:18:59 CET 
Description of problem:

/usr/share/doc/mariadb/README.urpmi has reference to a non-existent /etc/rc.d/init.d/mysqld

Version-Release number of selected component (if applicable):


How reproducible: always


Steps to Reproduce:
1. urpmi mariadb
2. or if already installed, cat /usr/share/doc/mariadb/README.urpmi
3.
Comment 1 Manuel Hiebel 2011-12-17 16:42:04 CET 
Hi, thanks for reporting this bug.

yep: 529 	/etc/rc.d/init.d/mysqld stop

Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => alien

Comment 2 AL13N 2011-12-17 20:20:52 CET 
[ ]# urpmf init.d/mysqld
mariadb:/etc/rc.d/init.d/mysqld

i don't see the problem...?
Comment 3 Bit Twister 2011-12-17 21:22:42 CET 
(In reply to comment #2)
> [ ]# urpmf init.d/mysqld
> mariadb:/etc/rc.d/init.d/mysqld
> 
> i don't see the problem...?

Neither do I, Now. :(

Apparently the update I did two hours about put it back. :)

# ll /etc/rc.d/init.d/mysqld
-rwxr-xr-x 1 root root 14007 Dec 17 06:51 /etc/rc.d/init.d/mysqld

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

Comment 4 AL13N 2011-12-17 21:26:00 CET 
i did no such update to mariadb that would have such an effect, but i'm glad your issue is resolved...
Note You need to log in before you can comment on or make changes to this bug.