aum can not copy /etc/resolv.conf

Bug #1186007 reported by Atilla Öntaş on 2013-05-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Yuri Myasoedov

Bug Description

Tonight i gave a try to aum. on my Mageia Cauldron 64 bit system. Using google translate for wiki page i think i setup everything correct. Give sudo perms on aum and begin with:

[atilla@localhost ~]$ aum -v --distrib= --distrib=/home/atilla/Mageia-RPMS/urpmi-proxy/repository/distrib/3/i586 --arch=i586 --chroot=chroot_mageia3_i586.tar.gz --upload-dir=/home/atilla/Mageia-RPMS/urpmi-proxy/repository/distrib/3/i586/media/tarakbumba/release/ rpm/SRPMS/pluma-plugins-1.2.0-2.mga3.src.rpm

This command gave me this pretty little error:
[DEBUG]: Copying /etc/resolv.conf file to chroot dir
Error: Catched error: Can't copy /etc/resolv.conf to chroot: Erişim engellendi (Not permitted)

So, what should i do?

Yuri Myasoedov (ymyasoedov) wrote :

Currently, aum has annoying bug with permissions. Try to retry this command with sudo:

aum -v --distrib= --distrib=/home/atilla/Mageia-RPMS/urpmi-proxy/repository/distrib/3/i586 --arch=i586 --chroot=chroot_mageia3_i586.tar.gz --upload-dir=/home/atilla/Mageia-RPMS/urpmi-proxy/repository/distrib/3/i586/media/tarakbumba/release/ rpm/SRPMS/pluma-plugins-1.2.0-2.mga3.src.rpm

But. First specified distrib ( --distrib= is not valid and doesn't point to distrib. I think you meant

I know about this bug and I'm fixing it. New version will be very soon. As I said, just use sudo.

Changed in aum:
assignee: nobody → Yuri Myasoedov (ymyasoedov)
importance: Undecided → High
status: New → In Progress
milestone: none → 0.2.2
Yuri Myasoedov (ymyasoedov) wrote :

Oops. I mean:

sudo aum -v --distrib= --distrib=/home/atilla/Mageia-RPMS/urpmi-proxy/repository/distrib/3/i586 --arch=i586 --chroot=chroot_mageia3_i586.tar.gz --upload-dir=/home/atilla/Mageia-RPMS/urpmi-proxy/repository/distrib/3/i586/media/tarakbumba/release/ rpm/SRPMS/pluma-plugins-1.2.0-2.mga3.src.rpm

Also, note if you don't specify --upload-dir, all built packages will be uploaded to the curent directory. E. g. this is optional.

Atilla Öntaş (tarakbumba) wrote :

Thank you! But using sudo for all is really annoying. I' ll try new version.

Yuri Myasoedov (ymyasoedov) wrote :

Actually, aum calls some privileged commands like "mount" or "chroot". Apparently, you should enter password at least one time after running aum, because aum will call these commands like "sudo mount", "sudo chroot" and so on.
Is this problematic for you to specify password for sudo?

There are two ways:
1. Run aum with sudo, and all internal command call will be calling without sudo.
2. Run aum with common permissions, and call only privileged commands with sudo internally from code.

I think, second way is more safe.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers