golang June 2014

golang@lists.fedoraproject.org

1 participants
94 discussions

[Bug 1100909] New: golang arm cross compile fails complaining about 5g
by Red Hat Bugzilla 13 Aug '14

13 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1100909 Bug ID: 1100909 Summary: golang arm cross compile fails complaining about 5g Product: Fedora Version: 20 Component: golang Severity: medium Assignee: vbatts(a)redhat.com Reporter: phil(a)sorber.net QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: After new 1.2.2-2 rpms for golang were updated, I attempted to cross compile a hello world for arm and it failed complaining about lack of 5g. Following packages installed: golang-1.2.2-2.fc20.x86_64 golang-pkg-bin-linux-amd64-1.2.2-2.fc20.x86_64 golang-pkg-linux-arm-1.2.2-2.fc20.noarch golang-src-1.2.2-2.fc20.noarch golang-pkg-linux-amd64-1.2.2-2.fc20.noarch $ GOOS=linux GOARCH=arm go build hello.go go tool: no such tool "5g" Version-Release number of selected component (if applicable): 1.2.2-2 How reproducible: Easy. Steps to Reproduce: 1. Install golang including the golang-pkg-linux-arm-1.2.2-2.fc20.noarch package 2. Attempt to build a hello world program with GOARCH=arm 3. Actual results: Error message: go tool: no such tool "5g" Expected results: A shiny new arm binary. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1101508] New: exec: "gcc": executable file not found in $PATH
by Red Hat Bugzilla 08 Aug '14

08 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1101508 Bug ID: 1101508 Summary: exec: "gcc": executable file not found in $PATH Product: Fedora Version: 20 Component: golang Assignee: vbatts(a)redhat.com Reporter: mfojtik(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Running 'yum install gcc golang' fails with: Installing : golang-pkg-linux-amd64-1.2.2-7.fc20.noarch 50/252 # runtime/cgo exec: "gcc": executable file not found in $PATH warning: %post(golang-pkg-linux-amd64-1.2.2-7.fc20.noarch) scriptlet failed, exit status 2 Non-fatal POSTIN scriptlet failure in rpm package golang-pkg-linux-amd64-1.2.2-7.fc20.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1105901] New: golang-pkg-linux-amd64 is missing dependency on gcc
by Red Hat Bugzilla 08 Aug '14

08 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1105901 Bug ID: 1105901 Summary: golang-pkg-linux-amd64 is missing dependency on gcc Product: Fedora Version: 20 Component: golang Assignee: vbatts(a)redhat.com Reporter: jumanjiman(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: On a fresh installation of Fedora 20 with golang-1.2.2-7.fc20.x86_64 or Fedora Rawhide with golang-1.3rc1-1.fc21.x86_64, go get errors out with: go install runtime/cgo: open /usr/lib/golang/pkg/linux_amd64/runtime/cgo.a: permission denied Version-Release number of selected component (if applicable): see above How reproducible: always. see https://github.com/jumanjiman/bz1099206 for a reproducer test harness based on docker with f20 and rawhide images. Steps to Reproduce: 1. build minimal f20 or rawhide system 2. install golang 3. observe error: Running transaction Installing : golang-src-1.2.2-7.fc20.noarch 1/52 Installing : golang-pkg-bin-linux-amd64-1.2.2-7.fc20.x86_64 2/52 Installing : golang-1.2.2-7.fc20.x86_64 3/52 Installing : golang-pkg-linux-amd64-1.2.2-7.fc20.noarch 4/52 # runtime/cgo exec: "gcc": executable file not found in $PATH warning: %post(golang-pkg-linux-amd64-1.2.2-7.fc20.noarch) scriptlet failed, exit status 2 Non-fatal POSTIN scriptlet failure in rpm package golang-pkg-linux-amd64-1.2.2-7.fc20.noarch Installing : mpfr-3.1.2-4.fc20.x86_64 5/52 Actual results: see above for rpm install error and `go get' error. Expected results: on fresh install, i should be able to run `go get' without error. Additional info: if you install gcc _before_ golang in separate yum commands, the above errors do not appear. See https://app.wercker.com/#applications/5394ce3e85147b684f0c91a4 for output of reproducer test harness. Note the "build images" and "run the test suite" sections. Potential related BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1099206 https://bugzilla.redhat.com/show_bug.cgi?id=1099732 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1109039] New: finalize namespace errors with docker run
by Red Hat Bugzilla 25 Jul '14

25 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1109039 Bug ID: 1109039 Summary: finalize namespace errors with docker run Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: docker run will fail at times with namespace errors Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20 How reproducible: pretty much random from what I've noticed Steps to Reproduce: 1. docker run -it fedora bash 2. if you can't see the error in 1, run it again 3. repeat 2 until you see the error Actual results: Here's a sample from my machine: ------------------------------ lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:14 finalize namespace drop bounding set read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:18 finalize namespace drop capabilities read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash bash-4.3# exit exit lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:25 finalize namespace drop bounding set read /proc/1/status: bad file descriptor ------------------------------- Expected results: container shell should be accessible everytime -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1109533] New: finalize namespace errors with docker run
by Red Hat Bugzilla 25 Jul '14

25 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1109533 Bug ID: 1109533 Summary: finalize namespace errors with docker run Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, agrimm(a)redhat.com, fullung(a)gmail.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Depends On: 1109039 +++ This bug was initially created as a clone of Bug #1109039 +++ Description of problem: docker run will fail at times with namespace errors Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20 How reproducible: pretty much random from what I've noticed Steps to Reproduce: 1. docker run -it fedora bash 2. if you can't see the error in 1, run it again 3. repeat 2 until you see the error Actual results: Here's a sample from my machine: ------------------------------ lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:14 finalize namespace drop bounding set read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:18 finalize namespace drop capabilities read /proc/1/status: bad file descriptor lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash bash-4.3# exit exit lsm5 @ naruto : /home/lsm5 $ docker run -it fedora:rawhide bash 2014/06/13 06:42:25 finalize namespace drop bounding set read /proc/1/status: bad file descriptor ------------------------------- Expected results: container shell should be accessible everytime --- Additional comment from Lokesh Mandvekar on 2014-06-13 03:24:28 EDT --- Hmm, I can't seem to be able to replicate this on my rawhide machine, no matter how many times I try this, regardless of the image (centos,fedora,debian,ubuntu) --- Additional comment from Vincent Batts on 2014-06-13 14:43:54 EDT --- using a newer version of gocapability (3c85049eae) fixes this for me, on RHEL6 https://github.com/dotcloud/docker/commit/4bf03a0fac48a06298afa149d43392457… --- Additional comment from Andy Grimm on 2014-06-13 15:18:38 EDT --- I confirmed that switching from f20 docker-io to rawhide docker-io fixed it for me. --- Additional comment from Fedora Update System on 2014-06-13 16:19:20 EDT --- golang-github-syndtr-gocapability-0-0.7.git3c85049.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-github-syndtr-gocapability-0… --- Additional comment from Fedora Update System on 2014-06-13 16:45:54 EDT --- golang-github-syndtr-gocapability-0-0.7.git3c85049.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-github-syndtr-gocapability-0… --- Additional comment from Fedora Update System on 2014-06-13 16:53:05 EDT --- golang-github-syndtr-gocapability-0-0.7.git3c85049.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-github-syndtr-gocapability-0… --- Additional comment from Fedora Update System on 2014-06-14 16:00:27 EDT --- Package golang-github-syndtr-gocapability-0-0.7.git3c85049.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing golang-github-syndtr-gocapability-0-0.7.git3c85049.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1647/golang-github… then log in and leave karma (feedback). Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1109039 [Bug 1109039] finalize namespace errors with docker run -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1112700] New: docker container not started, bad file descriptor
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1112700 Bug ID: 1112700 Summary: docker container not started, bad file descriptor Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ldoktor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Created attachment 911745 --> https://bugzilla.redhat.com/attachment.cgi?id=911745&action=edit /var/log/messages output Description of problem: Sometimes when I try to start container I get this message: 2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor and the container is not started. Version-Release number of selected component (if applicable): docker-io-1.0.0-1.fc20.x86_64 How reproducible: rarely Steps to Reproduce: 1. use `docker run ...` (in this example: `/usr/bin/docker -D run --interactive --tty --name test_eHmi localhost:5000/ldoktor/fedora:latest bash -c bash` Actual results: Container is not started, message: 2014/06/24 13:39:34 finalize namespace drop bounding set read /proc/1/status: bad file descriptor is in the container output. Expected results: Container should start. Additional info: There were around 14 containers running and 2 not running when this bug occurred. This bug happened to me 3 or 4 times during one week (testing docker, so the failure percentage is really low). -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1112748] New: Selinux prevents docker-io from updating /etc/passwd within a container
by Red Hat Bugzilla 22 Jul '14

22 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1112748 Bug ID: 1112748 Summary: Selinux prevents docker-io from updating /etc/passwd within a container Product: Fedora Version: 20 Component: docker-io Severity: high Assignee: lsm5(a)redhat.com Reporter: artaxerxes2(a)iname.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Running a certain docker command fails to run the container as expected since selinux intercept a call to update /etc/passwd within the container. Version-Release number of selected component (if applicable): Docker version 1.0.0, build 63fe64c/1.0.0 selinux policy version is 29 How reproducible: always Steps to Reproduce: 1. # yum upgrade 2. # yum install docker-io 3. add username to the docker group and restart the daemon 4. verify 'getenforce' returns 'Enforcing' 5. docker run -t -i -p 80:80 -p 20022:22 oskarhane/docker-wordpress-nginx-ssh Actual results: 140624 15:34:46 mysqld_safe Logging to syslog. 140624 15:34:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql mysql root password: Yohraequ2eiB wordpress password: ieHie5toi0zo ssh password: se2Gai9eengu usermod: failure while writing changes to /etc/passwd % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 58606 100 58606 0 0 60339 0 --:--:-- --:--:-- --:--:-- 62148 Archive: nginx-helper.1.8.1.zip nginx-helper.1.8.1 packaged creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/readme.txt creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/admin.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/install.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-sidebar.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-general.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-support.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/ creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/config.json creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.eot inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.svg inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.ttf inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.woff creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/nginx-fontello.css inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx.js inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/rtp-social-icons-32-32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/logo.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/style.css extracting: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-icon-32x32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/nginx-helper.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/compatibility.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.mo inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.po inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/purger.php % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 38126 100 38126 0 0 151k 0 --:--:-- --:--:-- --:--:-- 154k Archive: wp-ffpc.1.5.0.zip wp-ffpc.1.5.0 packaged creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-acache.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-class.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-nginx-sample.conf inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/readme.txt inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-backend.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/uninstall.php creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-admin.css inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-abstract.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-utilities.php sed: warning: failed to set default file creation context to system_u:object_r:svirt_sandbox_file_t:s0:c8,c525: Permission deniedStarting memcached: memcached. 140624 15:34:59 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended /usr/local/lib/python2.7/dist-packages/supervisor-3.0-py2.7.egg/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2014-06-24 15:35:00,547 CRIT Supervisor running as root (no user in config file) 2014-06-24 15:35:00,646 INFO RPC interface 'supervisor' initialized 2014-06-24 15:35:00,646 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2014-06-24 15:35:00,646 INFO supervisord started with pid 380 2014-06-24 15:35:01,648 INFO spawned: 'nginx' with pid 391 2014-06-24 15:35:01,650 INFO spawned: 'mysqld' with pid 392 2014-06-24 15:35:01,651 INFO spawned: 'php5-fpm' with pid 393 2014-06-24 15:35:01,652 INFO spawned: 'ssh' with pid 394 2014-06-24 15:35:02,756 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:35:02,757 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:35:02,757 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:35:02,757 INFO success: ssh entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Expected results: 140624 15:36:48 mysqld_safe Logging to syslog. 140624 15:36:48 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql mysql root password: Eehujoh3ooyo wordpress password: nana8aiTh6ju ssh password: Eengoo2liMie % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 58606 100 58606 0 0 38969 0 0:00:01 0:00:01 --:--:-- 39412 Archive: nginx-helper.1.8.1.zip nginx-helper.1.8.1 packaged creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/ creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/install.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-general.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-sidebar.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/lib/nginx-support.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/logo.png extracting: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-icon-32x32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/rtp-social-icons-32-32.png inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx.js inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/style.css creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/ creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.ttf inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.woff inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.svg inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/font/nginx-fontello.eot creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/css/nginx-fontello.css inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/assets/nginx-helper-icons/config.json inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/admin/admin.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/nginx-helper.php inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/readme.txt inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/compatibility.php creating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/ inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.mo inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/languages/nginx-helper.po inflating: /usr/share/nginx/www/wp-content/plugins/nginx-helper/purger.php % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 38126 100 38126 0 0 49638 0 --:--:-- --:--:-- --:--:-- 49903 Archive: wp-ffpc.1.5.0.zip wp-ffpc.1.5.0 packaged creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-nginx-sample.conf inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-class.php creating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/ inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-admin.css inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-abstract.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-common/wp-plugin-utilities.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/uninstall.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/readme.txt inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-acache.php inflating: /usr/share/nginx/www/wp-content/plugins/wp-ffpc/wp-ffpc-backend.php Starting memcached: memcached. /usr/local/lib/python2.7/dist-packages/supervisor-3.0-py2.7.egg/supervisor/options.py:295: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2014-06-24 15:37:02,595 CRIT Supervisor running as root (no user in config file) 2014-06-24 15:37:02,603 INFO RPC interface 'supervisor' initialized 2014-06-24 15:37:02,603 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2014-06-24 15:37:02,603 INFO supervisord started with pid 385 140624 15:37:03 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 2014-06-24 15:37:03,606 INFO spawned: 'nginx' with pid 396 2014-06-24 15:37:03,607 INFO spawned: 'mysqld' with pid 397 2014-06-24 15:37:03,608 INFO spawned: 'php5-fpm' with pid 398 2014-06-24 15:37:03,609 INFO spawned: 'ssh' with pid 399 2014-06-24 15:37:04,716 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:37:04,716 INFO success: mysqld entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:37:04,716 INFO success: php5-fpm entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2014-06-24 15:37:04,716 INFO success: ssh entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Additional info: If selinux is set to non-enforcing (setenforce 0), then the problem disappears. Looking at the audit.log file there is nothing related to failed update around the time of the usermod command is launched. I tried the exact same steps on CentOS 6.5 and had no issue at all, even in Enforcing mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1101654] New: Permission denied when running Fedora images on Ubuntu
by Red Hat Bugzilla 14 Jul '14

14 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1101654 Bug ID: 1101654 Summary: Permission denied when running Fedora images on Ubuntu Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: sthorger(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io, vbatts(a)redhat.com Created attachment 899597 --> https://bugzilla.redhat.com/attachment.cgi?id=899597&action=edit Example Dockerfile Description of problem: Trying to run a basic Docker image from Fedora on Ubuntu 14.04, gives the following error message: 2014/05/27 17:00:26 exec: "/usr/bin/echo": stat /usr/bin/echo: permission denied Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Build attach Dockerfile 2. Run Actual results: 2014/05/27 17:00:26 exec: "/usr/bin/echo": stat /usr/bin/echo: permission denied Expected results: Hello world! Additional info: Removing "User hello" or "RUN yum -y update" makes it work as expected -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1110497] New: go test fails for multiple golang-* libraries
by Red Hat Bugzilla 08 Jul '14

08 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1110497 Bug ID: 1110497 Summary: go test fails for multiple golang-* libraries Product: Fedora Version: rawhide Component: golang Assignee: vbatts(a)redhat.com Reporter: lsm5(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: apparently, ever since the upgrade to go1.3rc2, go test in %check fails. Here's a sample from golang-github-gorilla-mux: go test github.com/gorilla/mux /var/tmp/rpm-tmp.iEoDQJ: line 31: 10812 Segmentation fault GOPATH=/usr/share/gocode:/home/lsm5/repositories/pkgs/fedora/golang-github-gorilla-mux/BUILDROOT/golang-github-gorilla-mux-0-0.14.git136d54f.fc21.x86_64//usr/share/gocode go test github.com/gorilla/mux error: Bad exit status from /var/tmp/rpm-tmp.iEoDQJ (%check) Version-Release number of selected component (if applicable): 1.3rc2-1.fc21 How reproducible: always Steps to Reproduce: 1. install latest golang on rawhide 2. try rebuilding any previously built golang lib (golang-github-gorilla-context or golang-github-gorilla-mux for instance) 3. see error -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1105046] New: argument prototype mismatch spew on update
by Red Hat Bugzilla 08 Jul '14

08 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=1105046 Bug ID: 1105046 Summary: argument prototype mismatch spew on update Product: Fedora Version: rawhide Component: golang Assignee: vbatts(a)redhat.com Reporter: yaneti(a)declera.com QA Contact: extras-qa(a)fedoraproject.org CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lemenkov(a)gmail.com, lsm5(a)redhat.com, renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 2

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang June 2014