Sorry, but with so little information there's nothing we can do. atom is not a Mageia package, so if it is not working, you should report the issue upstream (at GitHub).

Please run `LC_ALL=C urpmi atom.x86_64.rpm` and post the output.

Sorry
i get this:

SECURITY: The following package is _NOT_ signed (OK ((none))): atom.x86_64.rpm
installing atom.x86_64.rpm
Preparing...                     #############################################
Installation failed:	file /usr/bin/apm from install of atom-1.17.0-0.1.x86_64 conflicts with file from package apmd-3.2.2-32.mga5.x86_64

But i can use another editor for example Emacs. I try to built a web page using html5... I can use Bluefish or libreoffice.
Thanks Regard's

(In reply to Jorge Humberto Moreno F from comment #2)
> Installation failed:	file /usr/bin/apm from install of
> atom-1.17.0-0.1.x86_64 conflicts with file from package
> apmd-3.2.2-32.mga5.x86_64

This means that the atom-1.17.0-0.1.x86_64 package contains a file, /usr/bin/apm, which has the same name as and thus conflicts with the /usr/bin/apm file of Mageia's apmd-3.2.2-32.mga5.x86_64 package.

You can uninstall the apmd package, and atom should install fine.

This conflict is track in this upstream Atom bug report: https://github.com/atom/atom/issues/3926
But there is little hope to see upstream fix it.

They do raise good points about apmd being pretty obsolete though, so we might want to drop it and thus facilitate the installation of thirdparty atom packages.

Another option could be to make our apmd package conflict the "atom" package name, which should hopefully improve the error message and maybe propose to uninstall apmd to install atom.

Assigning to the apmd maintainer to decide what should be done ("wontfix" would also be a valid approach, as we don't have to support thirdparty packages in the first place - but here maybe we can accommodate).

See Also: (none) => https://github.com/atom/atom/issues/3926
Assignee: bugsquad => shlomif

One more to remove APMD from the basic installation and rename it's bin file to apmd. Had the same problem reported here and after uninstall apmd, Atom.io installed fine. Searching for this problem I found that APMD is useless for Mageia  6. APM it's not in any kernel config file (inside /boot) and won't be necessary in  the future. It's for old hardware basicly and such hardware won't run mageia 6 anyway due to limited video capabilities. But thinking is some text only build to run and old hardware maybe the package maintainer could just rename the exec from apm to other thing as apmd or apmad just for those who would use in such cases. But the package has to be removed from the vanilla installations as it's just a waste of space at the moment, If the kernel is not configured to use it , it does not need to be installed by default. Thanks.

CC: (none) => fabio.muller

@ Jorge,

Thank you for having taken the needed time to report this issue!

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and say so.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Note that we are a community distribution, which means that we, the Mageia users, make Mageia together in our free time. If you'd like to help maintain packages, then please consider becoming a Mageia packager https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

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