You are not logged in.
Hi all, so, I have two things to say:
1) There is a package on the AUR, "nemo-megasync", it first was just provided as a deb file by Andrew of webupd8.org, this package is the megasync extension for the nemo file manager, and the user elken made a PKGBUILD for it.
But Andrew doesn't maintain nemo-megasync anymore, so I decided to maintain it myself, and you can find it here: https://github.com/Pival81/nemo-megasync .
As you can read in the description of the project, I did nothing other than just changing the word "nautilus" with "nemo" in every file of the original tarball (which can be found here: mega.nz/linux ) and, surprisingly for me, it worked.
I wanted to maintain the package on the AUR, so i commented and even sent an email to elken, but he/she did not respond. It even seems that another user is interested in what i want to do.
Is there any "moderator" who can help me make me the maintainer of the package?
2) I tried to make a PKGBUILD for the latest version of doomsday, the doom engine, because the package on the AUR is the stable version, while i want to build the version 2.0.
I had to upload it on the OpenSuSE Build System, because my laptop wouldn't be able to build it (even obs made it in an hour).
When it finished i tried to install it but it gave me these errors:
✘ pival81@Extensa5235 ~ yaourt doomsday
1 home_Pival81_arch_Arch_Extra/doomsday 2.0.0-2013
An advanced Doom engine that supports DOOM, Heretic and Hexen.
2 aur/doomsday 1.15.8-1 (Out of Date) (10) (0.57)
An advanced Doom engine that supports DOOM, Heretic and Hexen.
==> Enter n° of packages to be installed (ex: 1 2 3 or 1-3)
==> -------------------------------------------------------
==> 1
resolving dependencies...
looking for conflicting packages...
Packages (1) doomsday-2.0.0-2013
Total Installed Size: 53.39 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [######################] 100%
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
error: failed to commit transaction (conflicting files)
doomsday: /usr/include/assimp/Compiler/poppack1.h exists in filesystem
doomsday: /usr/include/assimp/Compiler/pstdint.h exists in filesystem
doomsday: /usr/include/assimp/Compiler/pushpack1.h exists in filesystem
doomsday: /usr/include/assimp/DefaultLogger.hpp exists in filesystem
doomsday: /usr/include/assimp/Exporter.hpp exists in filesystem
doomsday: /usr/include/assimp/IOStream.hpp exists in filesystem
doomsday: /usr/include/assimp/IOSystem.hpp exists in filesystem
doomsday: /usr/include/assimp/Importer.hpp exists in filesystem
doomsday: /usr/include/assimp/LogStream.hpp exists in filesystem
doomsday: /usr/include/assimp/Logger.hpp exists in filesystem
doomsday: /usr/include/assimp/NullLogger.hpp exists in filesystem
doomsday: /usr/include/assimp/ProgressHandler.hpp exists in filesystem
doomsday: /usr/include/assimp/ai_assert.h exists in filesystem
doomsday: /usr/include/assimp/anim.h exists in filesystem
doomsday: /usr/include/assimp/camera.h exists in filesystem
doomsday: /usr/include/assimp/cexport.h exists in filesystem
doomsday: /usr/include/assimp/cfileio.h exists in filesystem
doomsday: /usr/include/assimp/cimport.h exists in filesystem
doomsday: /usr/include/assimp/color4.h exists in filesystem
doomsday: /usr/include/assimp/color4.inl exists in filesystem
doomsday: /usr/include/assimp/config.h exists in filesystem
doomsday: /usr/include/assimp/defs.h exists in filesystem
doomsday: /usr/include/assimp/importerdesc.h exists in filesystem
doomsday: /usr/include/assimp/light.h exists in filesystem
doomsday: /usr/include/assimp/material.h exists in filesystem
doomsday: /usr/include/assimp/material.inl exists in filesystem
doomsday: /usr/include/assimp/matrix3x3.h exists in filesystem
doomsday: /usr/include/assimp/matrix3x3.inl exists in filesystem
doomsday: /usr/include/assimp/matrix4x4.h exists in filesystem
doomsday: /usr/include/assimp/matrix4x4.inl exists in filesystem
doomsday: /usr/include/assimp/mesh.h exists in filesystem
doomsday: /usr/include/assimp/metadata.h exists in filesystem
doomsday: /usr/include/assimp/postprocess.h exists in filesystem
doomsday: /usr/include/assimp/quaternion.h exists in filesystem
doomsday: /usr/include/assimp/quaternion.inl exists in filesystem
doomsday: /usr/include/assimp/scene.h exists in filesystem
doomsday: /usr/include/assimp/texture.h exists in filesystem
doomsday: /usr/include/assimp/types.h exists in filesystem
doomsday: /usr/include/assimp/vector2.h exists in filesystem
doomsday: /usr/include/assimp/vector2.inl exists in filesystem
doomsday: /usr/include/assimp/vector3.h exists in filesystem
doomsday: /usr/include/assimp/vector3.inl exists in filesystem
doomsday: /usr/include/assimp/version.h exists in filesystem
doomsday: /usr/lib64 exists in filesystem
Errors occurred, no packages were upgraded.
I took the build instructions from the rules file in an archive used to build debs on launchpad.
The PKGBUILD can be found here: https://build.opensuse.org/package/view … D?expand=1
And the pre-compiled package here: http://download.opensuse.org/repositori … pkg.tar.xz
Before updating to the latest release (2016) I want to make the package installable and then upload it on the AUR with the name of doomsday-daily.
I hope someone can help me! Thanks in advance! (and sorry for my bad english)
Offline
Offline
Oh, ok, thanks.
I'll just have to wait then.
And what about doomsday?
Offline
And what about doomsday?
The error should be self-explanatory: the files you're trying to install already exist on your filesystem.
You can use 'pacman -Qo' to determine which package owns the files.
Offline