[Bug 1166611] New: Extend golang %files section with golang.org/x directory ownership
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1166611
Bug ID: 1166611
Summary: Extend golang %files section with golang.org/x
directory ownership
Product: Fedora
Version: rawhide
Component: golang
Assignee: vbatts(a)redhat.com
Reporter: jchaloup(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)fedoraproject.org,
renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
https://groups.google.com/forum/#!topic/golang-nuts/eD8dh3T9yyA
First post:
...
This list shows the current base import paths, and their new equivalents.
code.google.com/p/go.benchmarks -> golang.org/x/benchmarks
code.google.com/p/go.blog -> golang.org/x/blog
code.google.com/p/go.crypto -> golang.org/x/crypto
code.google.com/p/go.exp -> golang.org/x/exp
code.google.com/p/go.image -> golang.org/x/image
code.google.com/p/go.mobile -> golang.org/x/mobile
code.google.com/p/go.net -> golang.org/x/net
code.google.com/p/go.sys -> golang.org/x/sys
code.google.com/p/go.talks -> golang.org/x/talks
code.google.com/p/go.text -> golang.org/x/text
code.google.com/p/go.tools -> golang.org/x/tools
...
import paths are being extended for new equivalents starting with
"golang.org/x/..."
Version-Release number of selected component (if applicable):
golang-1.3.99-2.1.4rc1.fc22
How reproducible:
Always
Steps to Reproduce:
1. rpm -q --provides golang | grep golang.org
Actual results:
Empty result
Expected results:
/usr/share/gocode/src/golang.org
/usr/share/gocode/src/golang.org/x
Additional info:
Extend ownership for all branches (at least el6, f20,f21,master)
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 6 months
[Bug 1187077] New: Fedora:latest docker image yum won't update
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1187077
Bug ID: 1187077
Summary: Fedora:latest docker image yum won't update
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: cyborg101010(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
Description of problem:
I cannot install from or update yum inside Docker.
RUN yum install make automake gcc gcc-c++ kernel-devel tar wget
---> Running in 04cdfe47b7ac
One of the configured repositories failed (Fedora 21 - x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the
problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable fedora
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=fedora.skip_if_unavailable=true
Cannot retrieve metalink for repository: fedora/21/x86_64. Please verify its
path and try again
Version-Release number of selected component (if applicable):
Docker 1.4.1
Fedora:latest
How reproducible:
Seems rare, but I can find others with the issue (e.g.
https://registry.hub.docker.com/_/fedora/ see comment from crackcomm)
Steps to Reproduce:
1. Take any examples https://github.com/fedora-cloud/Fedora-Dockerfiles
2. docker build an example
3. Wait for yum update / install
Actual results:
Yum errors and exits.
Expected results:
Yum update / install
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1161618] New: influxdb: please update to 0.8.5
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1161618
Bug ID: 1161618
Summary: influxdb: please update to 0.8.5
Product: Fedora
Version: rawhide
Component: golang-github-influxdb-influxdb
Assignee: jchaloup(a)redhat.com
Reporter: ruben(a)rubenkerkhof.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)fedoraproject.org, vbatts(a)redhat.com
Thanks for packaging influxdb!
Would it be possible to upgrade the package to 0.8.5? It contains some fixes
regarding sharding I bumped in to, and also the new collectd plugin would be
nice to have.
Kind regards,
Ruben
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1119282] New: [Regression] Unable to run docker client as non-root user
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1119282
Bug ID: 1119282
Summary: [Regression] Unable to run docker client as non-root
user
Product: Fedora
Version: 19
Component: docker-io
Assignee: lsm5(a)switzerlandmail.ch
Reporter: psavage(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)switzerlandmail.ch,
mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io,
vbatts(a)redhat.com
Description of problem: Docker used to be able to run it's client as non-root
user, allowed things like `docker ps` and `docker run` but since latest update
I am unable to do that. Even though the user running the docker command is in
the docker group, which previously worked.
Version-Release number of selected component (if
applicable):docker-io-1.0.0-6.fc19.x86_64
How reproducible:
Steps to Reproduce:
1. Run docker ps
2.
3.
Actual results:
2014/07/14 13:25:33 Get http:///var/run/docker.sock/v1.12/containers/json: dial
unix /var/run/docker.sock: permission denied
Expected results:
Docker command should run
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1144636] New: Docker fails to start on systems with SELinux and btrfs
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1144636
Bug ID: 1144636
Summary: Docker fails to start on systems with SELinux and
btrfs
Product: Fedora
Version: 20
Component: docker-io
Severity: urgent
Assignee: lsm5(a)fedoraproject.org
Reporter: voxadam(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
External Bug ID: Red Hat Bugzilla 1128041
External Bug ID: Red Hat Bugzilla 1128041
Description of problem:
The Docker daemon fails to start on systems with SELinux and btrfs
Version-Release number of selected component (if applicable):
Kernel: 3.16.2-200.fc20.x86_64 #1 SMP
Docker: 1.2.0 (2.fc20)
libselinux: 2.2.1 (6.fc20)
How reproducible:
Incredibly so.
Steps to Reproduce:
1. Install F20 on btrfs
2. systemctl start docker
3. Bang head against desk
Actual results:
adam@dekatron ~/bin sudo systemctl start docker
[sudo] password for adam:
Job for docker.service failed. See 'systemctl status docker.service' and
'journalctl -xn' for details.
✘ adam@dekatron ~/bin journalctl -xn
-- Logs begin at Wed 2014-09-17 14:41:46 PDT, end at Fri 2014-09-19 18:18:26
PDT. --
Sep 19 18:18:18 dekatron.voxadam.com docker[7517]: 2014/09/19 18:18:18 SELinux
is not supported with the BTRFS graph driver!
Sep 19 18:18:18 dekatron.voxadam.com systemd[1]: docker.service: main process
exited, code=exited, status=1/FAILURE
Sep 19 18:18:18 dekatron.voxadam.com systemd[1]: Failed to start Docker
Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Expected results:
Docker should start.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1128041
https://github.com/docker/docker/issues/7952
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1176302] New: /var/log/docker incorrectly asserts that kernel 2.6.32* "might be unstable running docker"
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1176302
Bug ID: 1176302
Summary: /var/log/docker incorrectly asserts that kernel
2.6.32* "might be unstable running docker"
Product: Fedora EPEL
Version: el6
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: afoxson(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
Description of problem:
The following warning appears in /var/log/docker:
"WARNING: You are running linux kernel version 2.6.32-504.1.3.el6.x86_64, which
might be unstable running docker. Please upgrade your kernel to 3.8.0."
Version-Release number of selected component (if applicable):
docker-io-1.3.2-2.el6.x86_64.rpm
How reproducible:
Consistently.
Steps to Reproduce:
1. Run docker in daemon mode.
2. Review /var/log/docker.
Actual results:
The aforementioned warning appears in /var/log/docker.
Expected results:
The aforementioned warning not appearing in /var/log/docker.
Additional info:
This warning is incorrect as per:
https://github.com/docker/docker/issues/407#issuecomment-43206662
which states:
"Kernels older than 3.8 aren't supported. That means technical support isn't
provided and you might run into unexpected behavior, even if it seems like it's
working. The only exception is the kernel provided by RHEL6 (2.6.32xxxxxx)
which was patched and improved to work properly with Docker."
It seems that an environment variable is available for this situation, as per:
https://github.com/shykes/docker-dev/commit/2c2a655da14f6de9353454673f2a1...
which states:
"set DOCKER_NOWARN_KERNEL_VERSION=1 to disable the warning for RHEL 6.5"
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 9 months
[Bug 1184710] New: dnsmasq needs to be restarted after reboot for dns to work in a Docker container
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1184710
Bug ID: 1184710
Summary: dnsmasq needs to be restarted after reboot for dns to
work in a Docker container
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: jshepherd(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
jchaloup(a)redhat.com, jperrin(a)centos.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com
External Bug ID: Red Hat Bugzilla 1128208
External Bug ID: Red Hat Bugzilla 1128208
Description of problem:
Docker replies on dnsmasq to have 'listen-address' set to the docker bridge,
and have bind-interfaces option turned on. However in this configuration
dnsmasq has to start after docker in order for DNS to work in a docker
container.
Version-Release number of selected component (if applicable):
docker-io 1.4.0
dnsmasq 2.72
How reproducible:
Reboot the system with docker, and dnsmasq enabled.
Steps to Reproduce:
1. Ensure docker is using the default dns option of 172.17.42.1
2. Use the attached dnsmasq.conf
3. Reboot the system
4. Launch a docker container:
`docker run -i -t centos /usr/bin/ping www.redhat.com`
Actual results:
Cannot resolve hostname
Expected results:
Response from 'akamai' or similar
Additional info:
See related issue #1128208
I tried added a systemd 'After' for dnsmasq on docker.service, but it doesn't
seem to be honoured by systemd.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 9 months
[Bug 1108349] New: remove golang-github-syndtr-gocapability from epel7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1108349
Bug ID: 1108349
Summary: remove golang-github-syndtr-gocapability from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-github-syndtr-gocapability
Assignee: vbatts(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
remove this package from epel7 as it's now available in rhel7 proper.
Version-Release number of selected component (if applicable):
golang-github-syndtr-gocapability-0-0.5.git3454319.el7
Additional info:
retired from dist-git:
http://pkgs.fedoraproject.org/cgit/golang-github-syndtr-gocapability.git/...
For pkgdb, Vincent could you run this for the epel7 branch (I'm not an admin
for this one):
pkgdb-cli orphan --retire golang-github-syndtr-gocapability epel7
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 9 months