[arch-general] [core/filesystem 2010.10-1 -> 2010.12-1] breaks makepkg and firefox
Dear devs, guys: I've been struggling for the past three days trying to find what was breaking makepkg [0] script and preventing Firefox to launch. Thanks I do weekly backups of my system I found after trial & error -updating one package at a time- the responsable is the core/filesystem package. Is anyone else suffering this? I already tried to look for info in www.archlinux.org/packages but it's not listed there. Should I open a new ticket at the bugtracker? Thanks for any advice. 0. Here are some logs: makepkg output after installing new filesystem 2010.12-1: http://aur.pastebin.com/VzRUu6yN /etc/makepkg.conf (untouched): http://aur.pastebin.com/RnqjbYaX last pacman's log with filesystem 2010.12-1 package installed: http://aur.pastebin.com/rZtXgifP
Le 18/12/2010 22:14, Martín Cigorraga a écrit :
Dear devs, guys:
I've been struggling for the past three days trying to find what was breaking makepkg [0] script and preventing Firefox to launch. Thanks I do weekly backups of my system I found after trial& error -updating one package at a time- the responsable is the core/filesystem package. Is anyone else suffering this? I already tried to look for info in www.archlinux.org/packages but it's not listed there. Should I open a new ticket at the bugtracker?
Thanks for any advice.
0. Here are some logs: makepkg output after installing new filesystem 2010.12-1: http://aur.pastebin.com/VzRUu6yN /etc/makepkg.conf (untouched): http://aur.pastebin.com/RnqjbYaX last pacman's log with filesystem 2010.12-1 package installed: http://aur.pastebin.com/rZtXgifP
Two things please: - repaste that stuff with 'LANG=C' prepended to the command(s) - is this the package you're trying to install? https://aur.archlinux.org/packages.php?ID=23363
On Sat, Dec 18, 2010 at 05:14:45PM -0300, Martín Cigorraga wrote:
Dear devs, guys:
I've been struggling for the past three days trying to find what was breaking makepkg [0] script and preventing Firefox to launch. Thanks I do weekly backups of my system I found after trial & error -updating one package at a time- the responsable is the core/filesystem package. Is anyone else suffering this? I already tried to look for info in www.archlinux.org/packages but it's not listed there. Should I open a new ticket at the bugtracker?
Thanks for any advice.
0. Here are some logs: makepkg output after installing new filesystem 2010.12-1: http://aur.pastebin.com/VzRUu6yN /etc/makepkg.conf (untouched): http://aur.pastebin.com/RnqjbYaX last pacman's log with filesystem 2010.12-1 package installed: http://aur.pastebin.com/rZtXgifP
Looks to me like the errors are related to yaourt. makepkg doesn't built in /tmp unless you explicitly tell it to. Make sure /tmp is set with permission 1777 d
2010/12/18 Dave Reisner
On Sat, Dec 18, 2010 at 05:14:45PM -0300, Martín Cigorraga wrote:
Dear devs, guys:
I've been struggling for the past three days trying to find what was breaking makepkg [0] script and preventing Firefox to launch. Thanks I do weekly backups of my system I found after trial & error -updating one package at a time- the responsable is the core/filesystem package. Is anyone else suffering this? I already tried to look for info in www.archlinux.org/packages but it's not listed there. Should I open a new ticket at the bugtracker?
Thanks for any advice.
0. Here are some logs: makepkg output after installing new filesystem 2010.12-1: http://aur.pastebin.com/VzRUu6yN /etc/makepkg.conf (untouched): http://aur.pastebin.com/RnqjbYaX last pacman's log with filesystem 2010.12-1 package installed: http://aur.pastebin.com/rZtXgifP
Looks to me like the errors are related to yaourt. makepkg doesn't built in /tmp unless you explicitly tell it to.
Make sure /tmp is set with permission 1777
d
Thanks for your quick answer. @cantabile, @Dave Since I didn't upgraded core/filesystem package I have no issues with makepkg and FF. In fact I already installed Dropbox by downloading the PKGBUILD and the rest of the files and running makepkg as usual and even up- dated aur/calibre-bzr and bleachbit-svn with yaourt without problems. The problem here is the core/filesystem package that somehow mess my system rendering FF and makepkg unusable - either way makepkg is invoked, via CLI or thru a pacman wrapper like yaourt). Regarding the 'missing' package I was talking about core/filesystem. When I said I didn't find the package in www.archlinux.org/packages I was talking about core/filesystem which I tried to find with the x86_64 filter - my bad, I apologize for that. The package of course is located here: http://www.archlinux.org/packages/core/any/filesystem/ My desire when mailing to the list was to know if anyone else were expe- rimenting the same issue as I. Just a crazy though: can this be a permissions issue? What have me so lost is why I'm experimenting this because so far I never had any problems in so much time updating the whole system everyday or at least every other day. As a plus, despite a bunch of AUR packages (yes, I know what that implies but I check everyone of them carefully before install'em) I try to keep my system as much as standard and vanilla as possible since I use my Arch for everyday job so please discard thinking of any obscure changes I could have done. Thanks again for your time =)
Hi,
I added core/filesystem to the Ignore= field in pacman.conf.
How will affect my system wait for the next package release while keep
updating the rest of packages as usual?
Thanks!
2010/12/18, Martín Cigorraga
2010/12/18 Dave Reisner
On Sat, Dec 18, 2010 at 05:14:45PM -0300, Martín Cigorraga wrote:
Dear devs, guys:
I've been struggling for the past three days trying to find what was breaking makepkg [0] script and preventing Firefox to launch. Thanks I do weekly backups of my system I found after trial & error -updating one package at a time- the responsable is the core/filesystem package. Is anyone else suffering this? I already tried to look for info in www.archlinux.org/packages but it's not listed there. Should I open a new ticket at the bugtracker?
Thanks for any advice.
0. Here are some logs: makepkg output after installing new filesystem 2010.12-1: http://aur.pastebin.com/VzRUu6yN /etc/makepkg.conf (untouched): http://aur.pastebin.com/RnqjbYaX last pacman's log with filesystem 2010.12-1 package installed: http://aur.pastebin.com/rZtXgifP
Looks to me like the errors are related to yaourt. makepkg doesn't built in /tmp unless you explicitly tell it to.
Make sure /tmp is set with permission 1777
d
Thanks for your quick answer.
@cantabile, @Dave Since I didn't upgraded core/filesystem package I have no issues with makepkg and FF.
In fact I already installed Dropbox by downloading the PKGBUILD and the rest of the files and running makepkg as usual and even up- dated aur/calibre-bzr and bleachbit-svn with yaourt without problems.
The problem here is the core/filesystem package that somehow mess my system rendering FF and makepkg unusable - either way makepkg is invoked, via CLI or thru a pacman wrapper like yaourt).
Regarding the 'missing' package I was talking about core/filesystem. When I said I didn't find the package in www.archlinux.org/packages I was talking about core/filesystem which I tried to find with the x86_64 filter - my bad, I apologize for that. The package of course is located here: http://www.archlinux.org/packages/core/any/filesystem/
My desire when mailing to the list was to know if anyone else were expe- rimenting the same issue as I. Just a crazy though: can this be a permissions issue?
What have me so lost is why I'm experimenting this because so far I never had any problems in so much time updating the whole system everyday or at least every other day. As a plus, despite a bunch of AUR packages (yes, I know what that implies but I check everyone of them carefully before install'em) I try to keep my system as much as standard and vanilla as possible since I use my Arch for everyday job so please discard thinking of any obscure changes I could have done.
Thanks again for your time =)
Martín Cigorraga escribió:
Thanks for your quick answer.
@cantabile, @Dave Since I didn't upgraded core/filesystem package I have no issues with makepkg and FF.
In fact I already installed Dropbox by downloading the PKGBUILD and the rest of the files and running makepkg as usual and even up- dated aur/calibre-bzr and bleachbit-svn with yaourt without problems.
The problem here is the core/filesystem package that somehow mess my system rendering FF and makepkg unusable - either way makepkg is invoked, via CLI or thru a pacman wrapper like yaourt).
Regarding the 'missing' package I was talking about core/filesystem. When I said I didn't find the package in www.archlinux.org/packages I was talking about core/filesystem which I tried to find with the x86_64 filter - my bad, I apologize for that. The package of course is located here: http://www.archlinux.org/packages/core/any/filesystem/
My desire when mailing to the list was to know if anyone else were expe- rimenting the same issue as I. Just a crazy though: can this be a permissions issue?
Works for me. What are your /tmp permissions after installing the filesystem package? That's where the <<< used in lines 268 and 272 will be creating a temporary file with random name. It's odd that it would be returning an errno=0 instead of EPERM, though. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Works for me. What are your /tmp permissions after installing the filesystem package? That's where the <<< used in lines 268 and 272 will be creating a temporary file with random name. It's odd that it would be returning an errno=0 instead of EPERM, though.
Hi Linas, First of all, sorry for the (very) late reply and thanks for your interest, there were some not so good changes in my life lately and I couldn't answer early :) Following your suggestion I did some research on this issue and this is what I found: /tmp folder permissions are the same after installing the new package, however (and this is the real thing) I found every normal user in the system are given root privileges, that's why makepkg fails, because it tries to compile the package as root; if I launch makepkg with --asroot argument it while run ok. I found too that adding a new user after upgrading core/filesystem it's created as expected without any issues. Anyways, if no problem arise I think I will wait until next package update and try to upgrade it but in the event it's totally necessary to upgrade this package seems I will need to do that 'trick' of creating a new user after upgrading and migrating my actual user to the new one. Thank you very much again! Last, wish you all people the best for the upcoming year: Happy New Year! =D
participants (4)
-
cantabile
-
Dave Reisner
-
Linas
-
Martín Cigorraga