Fedora 27-20170817.n.3 compose check report
Missing expected images: Atomic qcow2 x86_64 Workstation live i386 Server boot i386 Atomic raw-xz x86_64 Kde live i386 Failed openQA tests: 36/126 (x86_64), 3/18 (i386), 1/2 (arm) ID: 131551 Test: x86_64 Server-dvd-iso base_services_start URL: https://openqa.fedoraproject.org/tests/131551 ID: 131555 Test: x86_64 Server-dvd-iso support_server URL: https://openqa.fedoraproject.org/tests/131555 ID: 131558 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller URL: https://openqa.fedoraproject.org/tests/131558 ID: 131560 Test: x86_64 Server-dvd-iso server_cockpit_default URL: https://openqa.fedoraproject.org/tests/131560 ID: 131564 Test: x86_64 Server-dvd-iso server_role_deploy_database_server URL: https://openqa.fedoraproject.org/tests/131564 ID: 131573 Test: x86_64 Workstation-live-iso install_no_user URL: https://openqa.fedoraproject.org/tests/131573 ID: 131575 Test: x86_64 Workstation-live-iso base_services_start URL: https://openqa.fedoraproject.org/tests/131575 ID: 131579 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/131579 ID: 131584 Test: x86_64 Workstation-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/131584 ID: 131587 Test: x86_64 Workstation-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/131587 ID: 131592 Test: x86_64 KDE-live-iso base_services_start URL: https://openqa.fedoraproject.org/tests/131592 ID: 131596 Test: x86_64 KDE-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/131596 ID: 131599 Test: x86_64 KDE-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/131599 ID: 131600 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/131600 ID: 131601 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/131601 ID: 131605 Test: x86_64 universal upgrade_desktop_64bit URL: https://openqa.fedoraproject.org/tests/131605 ID: 131606 Test: x86_64 universal upgrade_server_64bit URL: https://openqa.fedoraproject.org/tests/131606 ID: 131607 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/131607 ID: 131609 Test: x86_64 universal upgrade_kde_64bit URL: https://openqa.fedoraproject.org/tests/131609 ID: 131610 Test: x86_64 universal upgrade_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/131610 ID: 131611 Test: x86_64 universal upgrade_2_minimal_64bit URL: https://openqa.fedoraproject.org/tests/131611 ID: 131612 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/131612 ID: 131613 Test: x86_64 universal upgrade_2_server_64bit URL: https://openqa.fedoraproject.org/tests/131613 ID: 131614 Test: x86_64 universal upgrade_2_kde_64bit URL: https://openqa.fedoraproject.org/tests/131614 ID: 131615 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/131615 ID: 131617 Test: x86_64 universal install_shrink_ext4 URL: https://openqa.fedoraproject.org/tests/131617 ID: 131618 Test: x86_64 universal install_shrink_ntfs URL: https://openqa.fedoraproject.org/tests/131618 ID: 131622 Test: x86_64 universal install_kickstart_firewall_disabled URL: https://openqa.fedoraproject.org/tests/131622 ID: 131623 Test: x86_64 universal support_server URL: https://openqa.fedoraproject.org/tests/131623 ID: 131626 Test: x86_64 universal install_mirrorlist_graphical URL: https://openqa.fedoraproject.org/tests/131626 ID: 131631 Test: x86_64 universal install_kickstart_user_creation URL: https://openqa.fedoraproject.org/tests/131631 ID: 131633 Test: x86_64 universal install_kickstart_firewall_configured URL: https://openqa.fedoraproject.org/tests/131633 ID: 131660 Test: x86_64 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/131660 ID: 131671 Test: x86_64 universal install_kickstart_hdd URL: https://openqa.fedoraproject.org/tests/131671 ID: 131672 Test: x86_64 universal upgrade_minimal_64bit URL: https://openqa.fedoraproject.org/tests/131672 ID: 131673 Test: x86_64 universal install_rescue_encrypted URL: https://openqa.fedoraproject.org/tests/131673 ID: 131674 Test: x86_64 universal install_rescue_encrypted@uefi URL: https://openqa.fedoraproject.org/tests/131674 ID: 131677 Test: i386 universal upgrade_desktop_32bit URL: https://openqa.fedoraproject.org/tests/131677 ID: 131678 Test: i386 universal upgrade_2_desktop_32bit URL: https://openqa.fedoraproject.org/tests/131678 ID: 131679 Test: i386 universal install_package_set_kde URL: https://openqa.fedoraproject.org/tests/131679 Soft failed openQA tests: 50/126 (x86_64), 14/18 (i386) (Tests completed, but using a workaround for a known bug)
Re: Fedora Elections to FESCo & FAmSCo - Voting period is in progress
On 08/18/2017 08:23 AM, Jan Kurik wrote: On Thu, Aug 17, 2017 at 3:17 PM, Benson Muite wrote: Is it possible for the people who are running and have not answered interview questions for the blog or have an informative profile to do so? Voting is not limited to relevant group, so some information on election options is helpful. One can of course do a web search, email list posting and commit history summary, but this may not always give exactly relevant information. This is up to the candidates. Candidates can use i.e. social networks to present them self. Typically every candidate has a User page which is linked from the voting machine. And again, it is up to the candidate what information he would like to publish there. We are not forcing candidates to publish any information, it is their free will. IMHO, this needs to change to make the elections meaningful, again. Ralf ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Could not execute retire
On Fri, Aug 18, 2017 at 11:42 AM, Honggang LI wrote: > Hi, > > https://bugzilla.redhat.com/show_bug.cgi?id=1404043#c41 > > As new rdma-core package had been imported to fedora-27, I'm working > on retire the old user space rdma stack packages. I only run the retire > command on branch 'f27' and 'master'. Branches older than f27 will be > kept. > > For example: > = > [honli@localhost libmlx4 (f27)]$ fedpkg retire 'Obsoleted by rdma-core' > /usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: > DeprecationWarning: fedora.client.bodhi has been deprecated. Please use > bodhi.client.bindings instead. > DeprecationWarning) > rm '.gitignore' > rm '0001-Add-ibv_query_port-caching-support.patch' > rm '0002-Add-RoCE-IP-based-addressing-support-for-UD-QPs.patch' > rm '0002-libmlx4-add-s390x-platform-support.patch' > rm 'libmlx4-1.0.6-compiler-warnings.patch' > rm 'libmlx4-checksum.mbox' > rm 'libmlx4-dracut-module-setup.sh' > rm 'libmlx4.spec' > rm 'sources' > [f27 c10fec4] Obsoleted by rdma-core > 10 files changed, 1 insertion(+), 890 deletions(-) > delete mode 100644 .gitignore > delete mode 100644 0001-Add-ibv_query_port-caching-support.patch > delete mode 100644 0002-Add-RoCE-IP-based-addressing-support-for-UD-QPs.patch > delete mode 100644 0002-libmlx4-add-s390x-platform-support.patch > create mode 100644 dead.package > delete mode 100644 libmlx4-1.0.6-compiler-warnings.patch > delete mode 100644 libmlx4-checksum.mbox > delete mode 100644 libmlx4-dracut-module-setup.sh > delete mode 100644 libmlx4.spec > delete mode 100644 sources > Counting objects: 3, done. > Delta compression using up to 8 threads. > Compressing objects: 100% (1/1), done. > Writing objects: 100% (3/3), 281 bytes | 0 bytes/s, done. > Total 3 (delta 0), reused 0 (delta 0) > remote: Emitting a message to the fedmsg bus. > remote: * Publishing information for 1 commits > remote: * Notifying alternative-arch people > To ssh://ho...@pkgs.fedoraproject.org/rpms/libmlx4 >9d18640..c10fec4 f27 -> f27 > FAS password for user honli: > Could not execute retire: Un-expected openid provider asked: > https://admin.fedoraproject.org/pkgdb/ > [honli@localhost libmlx4 (f27)]$ ls > dead.package > [honli@localhost libmlx4 (f27)]$ > = > > Can I ignore this error message? > "Could not execute retire: Un-expected openid provider asked: > https://admin.fedoraproject.org/pkgdb/"; > > > > And as "PkgDB is in read-only mode", I had been re-direct to > [1] https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb . > Section "3.5 How do I retire a package?" is very simple compare to link > [2] https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life . > > I'm confused. Which link I should follow [1] or [2]? > Hi Honggang, Looks like you need the new version of fedpkg-1.29, which is in Bodhi[1]. [1] https://bodhi.fedoraproject.org/updates/?packages=rpkg&request=testing&status=pending > thanks > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org -- Regards, Chenxiong Qi ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Fedora Elections to FESCo & FAmSCo - Voting period is in progress
On Thu, Aug 17, 2017 at 3:17 PM, Benson Muite wrote: > Is it possible for the people who are running and have not answered > interview questions for the blog or have an informative profile to do so? > Voting is not limited to relevant group, so some information on election > options is helpful. One can of course do a web search, email list posting > and commit history summary, but this may not always give exactly relevant > information. This is up to the candidates. Candidates can use i.e. social networks to present them self. Typically every candidate has a User page which is linked from the voting machine. And again, it is up to the candidate what information he would like to publish there. We are not forcing candidates to publish any information, it is their free will. Regards, Jan > > On 08/17/2017 03:39 PM, Jan Kurik wrote: >> >> Hi, >> >> let me remind you we have Voting period of the currently running >> Fedora Elections into FESCo and FAmSCo in progress. >> Please vote for your candidates to FAmSCo [1] and FESCo [2]. >> The Voting period ends on August 21th, 2017 at 23:59:59 UTC. >> >> You might also check an article, summarizing interviews with nominees [3]. >> >> [1] >> https://admin.fedoraproject.org/voting/vote/famsco-august-2017-2nd.round >> [2] >> https://admin.fedoraproject.org/voting/vote/fesco-august-2017-2nd.round >> [3] https://fedoramagazine.org/august-2017-elections/ >> >> Thanks for your support. >> Regards, >> Jan >> > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Is it possible atlas is linked wrongly by new binutils?
It should work now [1]. Jakub [1]: https://koji.fedoraproject.org/koji/taskinfo?taskID=21296324 On 9.8.2017 11:37, Richard W.M. Jones wrote: > > ocaml-gsl (OCaml bindings for GNU Scientific Library) currently > fails to link to atlas: > > + /usr/bin/ocamlfind ocamlopt -g -I lib -linkpkg -package bigarray -I lib -I > examples lib/gsl.cmxa examples/blas_ex.cmx -o examples/blas_ex.native > /usr/lib64/atlas/libsatlas.so: undefined reference to `dlarfy_' > /usr/lib64/atlas/libsatlas.so: undefined reference to `slarfy_' > /usr/lib64/atlas/libsatlas.so: undefined reference to `clarfy_' > /usr/lib64/atlas/libsatlas.so: undefined reference to `zlarfy_' > collect2: error: ld returned 1 exit status > > However this only happens with the very latest atlas that was built by > binutils 2.29 (atlas-3.10.2-18.fc27.x86_64). It doesn't occur with > the previous version of atlas (atlas-3.10.2-16.fc26) even though there > seems to have been no change in atlas. > > $ nm -D /usr/lib64/atlas/libtatlas.so | grep larfy > U clarfy_ > U dlarfy_ > U slarfy_ > U zlarfy_ > > I looked in /usr/lib64 on my development machine which has atlas > installed but there is no .so* file that I can find which defines > these symbols. I also couldn't work out where in the atlas code > (which is a bit strange) these references are used. > > Hence the question: Is this breakage in atlas? binutils? > > Rich. > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Could not execute retire
Hi, https://bugzilla.redhat.com/show_bug.cgi?id=1404043#c41 As new rdma-core package had been imported to fedora-27, I'm working on retire the old user space rdma stack packages. I only run the retire command on branch 'f27' and 'master'. Branches older than f27 will be kept. For example: = [honli@localhost libmlx4 (f27)]$ fedpkg retire 'Obsoleted by rdma-core' /usr/lib/python2.7/site-packages/fedora/client/bodhi.py:48: DeprecationWarning: fedora.client.bodhi has been deprecated. Please use bodhi.client.bindings instead. DeprecationWarning) rm '.gitignore' rm '0001-Add-ibv_query_port-caching-support.patch' rm '0002-Add-RoCE-IP-based-addressing-support-for-UD-QPs.patch' rm '0002-libmlx4-add-s390x-platform-support.patch' rm 'libmlx4-1.0.6-compiler-warnings.patch' rm 'libmlx4-checksum.mbox' rm 'libmlx4-dracut-module-setup.sh' rm 'libmlx4.spec' rm 'sources' [f27 c10fec4] Obsoleted by rdma-core 10 files changed, 1 insertion(+), 890 deletions(-) delete mode 100644 .gitignore delete mode 100644 0001-Add-ibv_query_port-caching-support.patch delete mode 100644 0002-Add-RoCE-IP-based-addressing-support-for-UD-QPs.patch delete mode 100644 0002-libmlx4-add-s390x-platform-support.patch create mode 100644 dead.package delete mode 100644 libmlx4-1.0.6-compiler-warnings.patch delete mode 100644 libmlx4-checksum.mbox delete mode 100644 libmlx4-dracut-module-setup.sh delete mode 100644 libmlx4.spec delete mode 100644 sources Counting objects: 3, done. Delta compression using up to 8 threads. Compressing objects: 100% (1/1), done. Writing objects: 100% (3/3), 281 bytes | 0 bytes/s, done. Total 3 (delta 0), reused 0 (delta 0) remote: Emitting a message to the fedmsg bus. remote: * Publishing information for 1 commits remote: * Notifying alternative-arch people To ssh://ho...@pkgs.fedoraproject.org/rpms/libmlx4 9d18640..c10fec4 f27 -> f27 FAS password for user honli: Could not execute retire: Un-expected openid provider asked: https://admin.fedoraproject.org/pkgdb/ [honli@localhost libmlx4 (f27)]$ ls dead.package [honli@localhost libmlx4 (f27)]$ = Can I ignore this error message? "Could not execute retire: Un-expected openid provider asked: https://admin.fedoraproject.org/pkgdb/"; And as "PkgDB is in read-only mode", I had been re-direct to [1] https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb . Section "3.5 How do I retire a package?" is very simple compare to link [2] https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life . I'm confused. Which link I should follow [1] or [2]? thanks ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: review swap
On Fri, Aug 18, 2017 at 6:32 AM, Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > I'm looking for a reviewer for > > Bug 1478231 – Review Request: conda - Cross-platform, Python-agnostic > binary package manager > https://bugzilla.redhat.com/1478231 Taken. You helped a lot to deepin packaging. -robin > > > I can review stuff in return. > > Zbyszek > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Need assistance to build knotter for Fedora
Following the request from Design team, I struggle to package Knotter
for review due to failure related to Qt5.
https://koji.fedoraproject.org/koji/taskinfo?taskID=21287726
As I am not familiar with Qt5. Can someone help to fix the error please.
I attached the spec file for view. Knotter website is on
http://knotter.mattbas.org/
--
Luya Tshimbalanga
Graphic & Web Designer
E: l...@fedoraproject.org
W: http://www.coolest-storm.net
#%%global commit0 507c147c8a8d55bfc42163fab4b5d31b4b8a90ea
#%%global shortcommit0 %%(c=%%{commit0}; echo ${c:0:7})
#%%global date 20150218
Name: knotter
Version: 0.9.6
#Release: 0.1%%{?date:.%%{date}git}%%{?dist}
Release: 1%{dist}
Summary: Knots editor
License: GPLv3+
URL: https://knotter.mattbas.org
#%%{?shortcommit0:
#Source0: https://github.com/mbasaglia/Knotter/archive/%{commit0}.tar.gz#/%%{name}-%%{shortcommit0}.tar.gz}
#%%{!?shortcommit0:
Source0: https://github.com/mbasaglia/Knotter/archive/%{version}.tar.gz#/%{name}-%{version}.tar.gz
BuildRequires: qt-devel
BuildRequires: qt5-qtbase-devel
BuildRequires: qt5-qtdeclarative-devel
BuildRequires: qt5-qttools-devel
Requires: qt5-qtbase-gui
Patch0: Qt5.7-metatype.patch
%description
Knotter is a free and open source customizable interlace patterns
whose design is historically used as a decorations in many places
by different cultures.
%prep
%autosetup -p0
%build
#export CXXFLAGS=-std=c++11
./configure.sh --prefix=%{_prefix}
%make_build
%install
%make_install
%files
%license COPYING
%doc AUTHORS README
%{_datadir}/applications/%{name}.desktop
%changelog
* Fri Jun 16 2017 Luya Tshimbalanga - 0.9.6-1
- Initial build
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
review swap
I'm looking for a reviewer for Bug 1478231 – Review Request: conda - Cross-platform, Python-agnostic binary package manager https://bugzilla.redhat.com/1478231 I can review stuff in return. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: [Modularity]: Service levels and EOL expectations?
On Thu, Aug 17, 2017 at 11:19:53AM -0500, Adam Miller wrote: > >> Service Level: 6 months (effective SL: 3 months/EOL: 2017-11-08 due > >> to dependency on openSSL) > > > > Ouch. Yes, but I think that that should be a warning sent to the module > > maintainers (and collectively to devel list) rather than show to end > > users. > I think this data needs to be displayed to users. As a sysadmin, I > would absolutely want that information available to me similar to how > I am able to check/view security update information with 'dnf > updateinfo'. I mean that the message for end users should be: Service Level: 3 months and maintainers should get a warning mail. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: g2clib static lib file name change
Am 2017-08-17 um 09:45 schrieb Jos de Kloe: Hi, thanks for your remark. I am aware of one single other package that uses this lib, for which I am the maintainer myself. The updates policy for rawhide says: A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them. Actually I don't know how to find out if there are others. I could not find an easy tool/method in the collection of fedora packaging tools/websites to do a query for other packages that have a BR on this library. repoquery --enablerepo=fedora-source --enablerepo=updates-source --archlist=src --whatrequires g2clib-static Greetings, Volker On 08/15/2017 10:23 PM, Michael Schwendt wrote: On Tue, 15 Aug 2017 22:13:00 +0200, Jos de Kloe wrote: Hi, I just build a new version of g2clib (upgraded from 1.4.0 to 1.6.0), and with this change this static library for grib file handling changes name: old: libgrib2c.a new: libg2c_v1.6.0.a I dont know of a packaging guideline that tells me to announce this, but to prevent surprises for dependent packages I thought I'd mention it. Well, are you aware of any src.rpm that needs this library as build requirement? If so, better inform the packager directly, because the next (re)build of that package will fail. If not other packages in the distribution use this lib, there may be private users of the Fedora package, but it's uncertain whether they can be reached via devel@ list. Packaging guidelines don't cover changes like that, but Update guidelines may: https://fedoraproject.org/wiki/Category:Package_Maintainers ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
About retiring OmegaT from Fedora
Hi all: My first important package in Fedora was OmegaT[1]. AFAIK is the best FLOSS computer aid translator tool available. With the time OmegaT has been enjoying a very active development with a significant (to me) handicap: new releases adds new features with new dependencies on java libraries not available in Fedora. As you perfectly know, updating the package requires to add each one of those libraries as new packages. But I can't find the time for such that effort. That's the reason the last Fedora version is 2.6.3 and the lasts at upstream are 3.6.0 / 4.1.2. So, I give up. I want to retire the package from Fedora because I'm sure I will not be able to update it anymore. I'll wait some days waiting someone expressing their interest on taking ownership. Otherwise I'll start the retirement process. Yours. [1] https://apps.fedoraproject.org/packages/OmegaT PS: OTOH I plan to publish OmegaT as a flatpak package via Flathub. Seems to me it would be a lot easier to maintain that way. I'm aware Flathub is out of the scope of Fedora :-/ -- Ismael Olea http://olea.org/diario/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
I need your reviews
Hello, After reviewing near 50 packages recently, I'd really like if anyone could also review a few of my packages which are sitting around. Of course, I'm open to review swaps, so if you have an old package that have been waiting for a review too, please contact me. Currently, I have waiting: - intel-hybrid-driver: This enables VP9 decoding ability on Skylake/Kabylake https://bugzilla.redhat.com/show_bug.cgi?id=1475962 - qdirstat: a clone of k4dirstat written with Qt5 https://bugzilla.redhat.com/show_bug.cgi?id=1476201 - A whole bunch of Golang library needed for packaging rclone. They are all generated by the gofed utility so they should be straightforward to review: - golang-github-jlaffaye-ftp - A FTP client package for Go https://bugzilla.redhat.com/show_bug.cgi?id=1475817 - golang-github-golang-sync - Go concurrency primitives https://bugzilla.redhat.com/show_bug.cgi?id=1475872 - golang-github-billziss-gh-cgofuse - Cross-platform FUSE library for Go https://bugzilla.redhat.com/show_bug.cgi?id=1475741 - golang-bazil-fuse - Go library for writing FUSE userspace filesystems https://bugzilla.redhat.com/show_bug.cgi?id=1475750 - golang-github-Unknwon-goconfig - Configuration file parser for the Go Programming Language https://bugzilla.redhat.com/show_bug.cgi?id=1475763 - golang-github-ncw-go-acd - Go library for accessing the Amazon Cloud Drive https://bugzilla.redhat.com/show_bug.cgi?id=1475841 - golang-github-ncw-dropbox-sdk-go-unofficial - An unofficial Go SDK for integrating with the Dropbox API v2 https://bugzilla.redhat.com/show_bug.cgi?id=1475832 - golang-github-nsf-termbox-go - A minimalistic API which allows programmers to write text-based user interfaces https://bugzilla.redhat.com/show_bug.cgi?id=1475846 - golang-github-rfjakob-eme - Encrypt-Mix-Encrypt for Go https://bugzilla.redhat.com/show_bug.cgi?id=1475850 - golang-github-xanzy-ssh-agent - Create a ssh-agent on any type of OS from any Go application https://bugzilla.redhat.com/show_bug.cgi?id=1475863 - golang-github-VividCortex-ewma - Exponentially Weighted Moving Average algorithms for Go https://bugzilla.redhat.com/show_bug.cgi?id=1475791 Thanks. Robert-André Mauchin ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: [Modularity]: Service levels and EOL expectations?
On Tue, Aug 8, 2017 at 10:21 AM, Matthew Miller wrote: > On Tue, Aug 08, 2017 at 10:38:15AM -0400, Przemek Klosowski wrote: >> >Yeah, that would get crazy fast. The 6 month granularity proposal >> >should help*some*, and we should probably go into this carefully. >> >> Technically, the SL for the module could have the narrow meaning >> referring to the module only, and the tools could follow the chain >> of dependencies and display it as: >> >> Service Level: 6 months (effective SL: 3 months/EOL: 2017-11-08 due >> to dependency on openSSL) > > Ouch. Yes, but I think that that should be a warning sent to the module > maintainers (and collectively to devel list) rather than show to end > users. > I think this data needs to be displayed to users. As a sysadmin, I would absolutely want that information available to me similar to how I am able to check/view security update information with 'dnf updateinfo'. -AdamM > > -- > Matthew Miller > > Fedora Project Leader > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: git push fails for new packages
On Thu, Aug 17, 2017 at 12:10:04PM -0300, Athos Ribeiro wrote: > On Thu, Aug 17, 2017 at 03:18:54PM +0800, Chenxiong Qi wrote: > > I just forked fedpkg minutes ago when writing this mail. I also can't > > push to my forked repo. > > > > I got these fetch and push urls. > > > > mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git > > (fetch) > > mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git > > (push) > > > > and got similar error reported originally in this thread, > > > > FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru > > (or you mis-spelled the reponame) > > fatal: Could not read from remote repository. > > > > Please make sure you have the correct access rights > > and the repository exists. > > I am getting the same error while trying to push to a repository created > this morning. > > $ git push origin master > FATAL: W any rpms/golang-github-shogo82148-go-shuffle athoscr DENIED by > fallthru > (or you mis-spelled the reponame) > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. Fix running, it looks like the tool processing the requests is still missing one API call :) Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: git push fails for new packages
On Thu, Aug 17, 2017 at 03:18:54PM +0800, Chenxiong Qi wrote: > I just forked fedpkg minutes ago when writing this mail. I also can't > push to my forked repo. > > I got these fetch and push urls. > > mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git > (fetch) > mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git > (push) > > and got similar error reported originally in this thread, > > FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru > (or you mis-spelled the reponame) > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. I am getting the same error while trying to push to a repository created this morning. $ git push origin master FATAL: W any rpms/golang-github-shogo82148-go-shuffle athoscr DENIED by fallthru (or you mis-spelled the reponame) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. -- Athos Ribeiro http://www.ime.usp.br/~athoscr ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Fedora Elections to FESCo & FAmSCo - Voting period is in progress
Is it possible for the people who are running and have not answered interview questions for the blog or have an informative profile to do so? Voting is not limited to relevant group, so some information on election options is helpful. One can of course do a web search, email list posting and commit history summary, but this may not always give exactly relevant information. On 08/17/2017 03:39 PM, Jan Kurik wrote: Hi, let me remind you we have Voting period of the currently running Fedora Elections into FESCo and FAmSCo in progress. Please vote for your candidates to FAmSCo [1] and FESCo [2]. The Voting period ends on August 21th, 2017 at 23:59:59 UTC. You might also check an article, summarizing interviews with nominees [3]. [1] https://admin.fedoraproject.org/voting/vote/famsco-august-2017-2nd.round [2] https://admin.fedoraproject.org/voting/vote/fesco-august-2017-2nd.round [3] https://fedoramagazine.org/august-2017-elections/ Thanks for your support. Regards, Jan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Elections to FESCo & FAmSCo - Voting period is in progress
Hi, let me remind you we have Voting period of the currently running Fedora Elections into FESCo and FAmSCo in progress. Please vote for your candidates to FAmSCo [1] and FESCo [2]. The Voting period ends on August 21th, 2017 at 23:59:59 UTC. You might also check an article, summarizing interviews with nominees [3]. [1] https://admin.fedoraproject.org/voting/vote/famsco-august-2017-2nd.round [2] https://admin.fedoraproject.org/voting/vote/fesco-august-2017-2nd.round [3] https://fedoramagazine.org/august-2017-elections/ Thanks for your support. Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: How to request new branch?
Am 17.08.2017 um 11:58 schrieb Pierre-Yves Chibon: On Thu, Aug 17, 2017 at 11:18:33AM +0200, Björn 'besser82' Esser wrote: Am 17.08.2017 um 10:09 schrieb Pierre-Yves Chibon: On Thu, Aug 17, 2017 at 09:26:17AM +0200, Björn 'besser82' Esser wrote: Still a problem here with libyui-qt-graph for epel7, f25 and f26 branches: Fix running, give it a few minutes and you should be good to go :) Thank you! Pushing works now, but builds on Koji are failing because of the package isn't properly tagged… :( Does it work for you now? Yay! Builds are fine now! Thank you! =) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
0Day policy update
Hi, as discussed in thread [1] I would like to propose update of the blocker process SOP page [2] regarding Accepted0Day and AcceptedPreviousRelease. Currently we have in the policy the following statement: "Accepted0Day is used for cases where the fix does not need to appear in the final frozen release, but must be available as an update on release day. AcceptedPreviousRelease is used for cases where the fix must appear as an update for one or more stable releases." This statement does not fully define timing of Accepted0Day and AcceptedPreviousRelease with regard to release date. During F26 release cycle we were on Go/No-Go meetings discussing whether we need to block release on a bug or whether we can release it as 0day. The main concern was timing of 0day bugs where we did not have guaranteed that a fix for the 0day bug will be available on time for the release day. Having this experience I would like to propose update of the blocker process SOP page [2], defining also more specific timing of 0day bugs. My proposal looks as follow: "Accepted0Day is used for cases where the fix does not need to appear in the final frozen release, but must be available as an update on release day. AcceptedPreviousRelease is used for cases where the fix must appear as an update for one or more stable releases. If an Accepted0Day or an AcceptedPreviousRelease might possibly block a release it must be also verified at the time of Go/No-Go meeting for the related release day, otherwise it is considered as a blocker." Does anyone has any objection or concern to update the SOP as proposed ? [1] https://lists.fedoraproject.org/archives/list/t...@lists.fedoraproject.org/thread/Q46M75GUKRHMI5IMNGBNL6XHLD5GLLTS/#ATXNQML4XMFTK3XGSAHD5AURL3BREDL2 [2] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process Regards, Jan -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: How to request new branch?
On Thu, Aug 17, 2017 at 11:18:33AM +0200, Björn 'besser82' Esser wrote: > Am 17.08.2017 um 10:09 schrieb Pierre-Yves Chibon: > > On Thu, Aug 17, 2017 at 09:26:17AM +0200, Björn 'besser82' Esser wrote: > > > Still a problem here with libyui-qt-graph for epel7, f25 and f26 branches: > > Fix running, give it a few minutes and you should be good to go :) > > Thank you! Pushing works now, but builds on Koji are failing because of the > package isn't properly tagged… :( Does it work for you now? Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Arduino in Fedora
On Wed, Aug 16, 2017 at 3:16 PM, Tom Callaway wrote: > > > On 08/16/2017 09:09 AM, Peter Robinson wrote: >> For reference there's a bunch of history on this bug about getting it >> up to date https://bugzilla.redhat.com/show_bug.cgi?id=1316315 > > Thanks. I give lots of credit to Gianluca's work on the 1.6 branch, most > of that was still applicable in the 1.8 code. > I actually struggled a bit on the upgrades because of the changes/additional deps they added at almost every update. For instance, the liblistserial addition dates back to the 1.6.8 update (which I was, slowly, working on); I guess jumping directly on he 1.8.x train would have been a better choice. Thanks for having a look at that, I will integrate your changes in the repo package as soon as I can. Regards G. -- Gianluca Sforna http://plus.google.com/+gianlucasforna - http://twitter.com/giallu Tinker Garage - http://tinkergarage.it ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: tcp_wrappers deprecation
On Wed, 2017-08-16 at 12:10 -0400, Stephen John Smoogen wrote: > On 16 August 2017 at 05:44, Tomas Mraz wrote: > > > On 08/16/2017 11:37 AM, Michal Sekletar wrote: > > > On Tue, Aug 15, 2017 at 1:58 PM, Jakub Jelen > > > wrote: > > > > > > > > > > > So can we discuss it now once more without the affiliation to > > > > systemd? > > > > The fact is that we still do not have any other replacement > > > > except > > > > firewalls. But do we need one? > > > > > > > > > > IIRC, in the past discussion there was quite a lot of people > > > arguing > > > that we actually need one. I personally don't think we as a > > > distribution need a drop-in replacement. However, what we > > > possibly > > > need, is a migration path for already deployed systems using > > > tcp_wrappers. Just dropping tcp_wrappers and potentially leaving > > > deployed services completely open would very irresponsible. > > > > > > Also we should consider an impact this change will have on our > > > downstreams focusing on enterprise use-cases (CentOS, RHEL). I > > > recon > > > that "splash damage" potentially caused by this change will be > > > bigger > > > there than in Fedora itself. > > > > On the other hand shipping downstream openssh patch adding this > > support > > when there is already similar functionality present in upstream via > > the > > Match directive in sshd_config is something I would definitely not > > vote > > for. > > > > The main purpose of tcp_wrappers is to allow a 'live' control > mechanism to > an op level person/program who may not be able to change > configuration > files without going through change control systems or restart > services (for > similar reasons). > > In various places, changing a startup/shutdown program requires going > through all kinds of extra hassles. So having a layer where the > 'local' > admin can quickly 'stop' some resource usage is required. The > tcp_wrappers > was the mechanism to do this. This meant that openssh/postfix/etc did > not > need to be restarted to get the new ips to allow or disallow. A > program > could go through logs and add/remove hosts to a file without altering > other > files and thus could be apparmor/selinux policy limited for further > protections. > > If there is a way to have systemd read from a 'central' file to > allow/deny > ips without requiring a systemctl reload/restart of all the services > that > would be useful to know and would be the way to call it a > 'replacement' of > the original functionality. Then any .service file could just say it > is > looking at that file for appropriate matches and those that don't > need it > don't. AFAIK, that was the feature that was removed from systemd in 2014. It can not work for services (they handle the connections on their own), but it can simply work with systemd sockets (and instanced services). And the same way it worked for sockets, it will work in future using tcpd by replacing ExecStart=-/usr/sbin/sshd -i $OPTIONS with ExecStart=@-/usr/sbin/tcpd /usr/sbin/sshd -i $OPTIONS in /etc/systemd/system/sshd@.service (for SSHD example). Source [1]. It needs some tweaks to SELinux policy (I am having a look into that), but there is a way for these who need it. Also using sockets will allow you that every service instance is reading a fresh configuration (in SSHD case). [1] https://lists.freedesktop.org/archives/systemd-devel/2014-April/018 793.html Regards, -- Jakub Jelen Software Engineer Security Technologies Red Hat, Inc. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: How to request new branch?
Am 17.08.2017 um 10:09 schrieb Pierre-Yves Chibon: On Thu, Aug 17, 2017 at 09:26:17AM +0200, Björn 'besser82' Esser wrote: Still a problem here with libyui-qt-graph for epel7, f25 and f26 branches: Fix running, give it a few minutes and you should be good to go :) Thank you! Pushing works now, but builds on Koji are failing because of the package isn't properly tagged… :( ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: How to request new branch?
On Thu, Aug 17, 2017 at 09:26:17AM +0200, Björn 'besser82' Esser wrote: > Still a problem here with libyui-qt-graph for epel7, f25 and f26 branches: Fix running, give it a few minutes and you should be good to go :) Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: g2clib static lib file name change
Hi, thanks for your remark. I am aware of one single other package that uses this lib, for which I am the maintainer myself. The updates policy for rawhide says: > A week in advance, notify maintainers who depend on their package to > rebuild when there are abi/api changes that require rebuilds in other > packages or offer to do these rebuilds for them. Actually I don't know how to find out if there are others. I could not find an easy tool/method in the collection of fedora packaging tools/websites to do a query for other packages that have a BR on this library. On 08/15/2017 10:23 PM, Michael Schwendt wrote: > On Tue, 15 Aug 2017 22:13:00 +0200, Jos de Kloe wrote: > >> Hi, >> >> I just build a new version of g2clib (upgraded from 1.4.0 to 1.6.0), and >> with this change this static library for grib file handling changes name: >> old: libgrib2c.a >> new: libg2c_v1.6.0.a >> >> I dont know of a packaging guideline that tells me to announce this, but >> to prevent surprises for dependent packages I thought I'd mention it. > > Well, are you aware of any src.rpm that needs this library as build > requirement? If so, better inform the packager directly, because the next > (re)build of that package will fail. If not other packages in the distribution > use this lib, there may be private users of the Fedora package, but it's > uncertain whether they can be reached via devel@ list. > > Packaging guidelines don't cover changes like that, but Update guidelines > may: https://fedoraproject.org/wiki/Category:Package_Maintainers > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Is it possible atlas is linked wrongly by new binutils?
On 08/17/2017 12:05 AM, Dan Horák wrote: On Wed, 16 Aug 2017 22:57:28 +0200 Kevin Kofler wrote: Dave Love wrote: Kevin Kofler writes: If you are talking about the missing RPM AutoProvides: Provides: libblas.so.3()(64bit) does wonders. I mean you need to get the soname right and ensure that you have everything implemented in the replacement library. Only the soname of the Provides matters. The actual library file can be a symlink to the monolithic libopenblas.so.0, the dynamic linker (ld.so) will load it just fine. The soname is only read at link time, and there, it is fine (and in fact desired) that newly linked applications get libopenblas.so.0 recorded as the soname, not libblas.so.3. Various things have been changed to use openblas on x86 after some of us agitated. The problem is, "various things" is not enough, we need a plan to ensure ALL things use it. It's not available for them all as far as I know -- there's an rpm macro which says which ones. I'm happy if that's wrong now. "things" = "packages" here. Surely OpenBLAS should work for all the BLAS- using packages on x86, especially if we symlink libblas.so to it. If not, it is a bug either in OpenBLAS or in the package. OpenBLAS is not available for some exotic architectures, but the solution there is to build ATLAS (or some other implementation) for those architectures (and those architectures only) and set up the symlinks there too. in F-27+ we should have OpenBLAS available for all active Fedora architectures Dan ___ OpenBLAS (https://github.com/xianyi/OpenBLAS) and BLIS (https://github.com/flame/blis) are nice, but for performance, may need to rethink packaging entirely. Ability to use GPUs may require better coordination with upstream developers - clBLAS looks promising for this, but seemed not to have gained much traction. This would be particularly useful for single precision applications such as image and audio processing. RocBLAS (https://github.com/ROCmSoftwarePlatform/rocBLAS) is an open alternative, but mostly for AMD. For commonly used libraries, might it be worth getting performance information in Koji or Copr? It may also be good to allow intelligent performance based choice of BLAS library based on architecture, what may be the best library on a 2 core mobile platform, 32 core workstation, ARM cloud server, Power cloud server etc. may be quite different. Having a correct and slow reference BLAS is also useful. Though expectation of average user to choose correct BLAS implementation may be too much - packager may have a better idea of a reasonable default. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: git push fails for new packages
On Thu, 2017-08-17 at 15:18 +0800, Chenxiong Qi wrote: > On Wed, 2017-08-16 at 11:31 -0700, Kevin Fenzi wrote: > > On 08/16/2017 11:18 AM, Martin Gansser wrote: > > > i still get the message koji not in list errors, some works... > > > some > > > doesn't ... > > > > > > BuildError: package nuvola-app-mixcloud not in list for tag f25- > > > updates-candidate > > > BuildError: package nuvola-app-google-play-music not in list for > > > tag f26-updates-candidate > > > BuildError: package nuvola-app-google-play-music not in list for > > > tag f25-updates-candidate > > > > The script that syncs this got stuck this morning. :( > > > > It's running again now... it takes about 30min or so to run, so > > things > > should be all updated after that. > > > > Additionally, we are replacing this script with one that listens to > > fedmsgs and on new branches just adds those, so hopefully after > > today > > they should get added right after the branch. > > > > The slow script will still run once a day to make sure no requests > > were > > dropped. > > > > kevin > > > > I just forked fedpkg minutes ago when writing this mail. I also can't > push to my forked repo. > > I got these fetch and push urls. > > mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git > (fetch) > mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git > (push) > > and got similar error reported originally in this thread, > > FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru > (or you mis-spelled the reponame) > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > It works now. Thanks. > > > > > ___ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: How to request new branch?
Am 17.08.2017 um 02:02 schrieb Kevin Fenzi: On 08/16/2017 04:19 PM, Jaroslav Skarvada wrote: - Original Message - On Mon, Aug 14, 2017 at 06:16:20PM -0400, Jaroslav Skarvada wrote: According to the fedrepo doc linked from [1] I did: $ fedrepo-req-branch preeny f26 And the ticket [2] was closed with a message: "The branch in PDC was created. You may now create the branch in Pagure using git." I did: $ git checkout -b f26 Switched to a new branch 'f26' $ git push -u origin f26 Total 0 (delta 0), reused 0 (delta 0) remote: FATAL: C refs/heads/f26 rpms/preeny jskarvad DENIED by refs/heads/f[0-9][0-9] remote: error: hook declined to update refs/heads/f26 To ssh://pkgs.fedoraproject.org/rpms/preeny ! [remote rejected] f26 -> f26 (hook declined) error: failed to push some refs to 'ssh://jskar...@pkgs.fedoraproject.org/rpms/preeny' FTR, this has been fixed, we're working on a fix to stop doing this manually :) Pierre ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Thanks for info, I successfully created the branch, but it still doesn't build [1]: BuildError: package preeny not in list for tag f26-updates-candidate Fixed now. Sorry this one fell through the cracks. Hopefully we are now back on track and all packages will be setup as soon as the request is processed moving forward. kevin Still a problem here with libyui-qt-graph for epel7, f25 and f26 branches: ``` $ for i in epel7 f25 f26 ; do git checkout $i && git push -u origin $i ; done ; Zu Branch 'epel7' gewechselt Total 0 (delta 0), reused 0 (delta 0) remote: FATAL: C refs/heads/epel7 rpms/libyui-qt-graph besser82 DENIED by refs/heads/epel[0-9] remote: error: hook declined to update refs/heads/epel7 To ssh://pkgs.fedoraproject.org/rpms/libyui-qt-graph ! [remote rejected] epel7 -> epel7 (hook declined) error: Fehler beim Versenden einiger Referenzen nach 'ssh://besse...@pkgs.fedoraproject.org/rpms/libyui-qt-graph' Zu Branch 'f25' gewechselt Total 0 (delta 0), reused 0 (delta 0) remote: FATAL: C refs/heads/f25 rpms/libyui-qt-graph besser82 DENIED by refs/heads/f[0-9][0-9] remote: error: hook declined to update refs/heads/f25 To ssh://pkgs.fedoraproject.org/rpms/libyui-qt-graph ! [remote rejected] f25 -> f25 (hook declined) error: Fehler beim Versenden einiger Referenzen nach 'ssh://besse...@pkgs.fedoraproject.org/rpms/libyui-qt-graph' Zu Branch 'f26' gewechselt Total 0 (delta 0), reused 0 (delta 0) remote: FATAL: C refs/heads/f26 rpms/libyui-qt-graph besser82 DENIED by refs/heads/f[0-9][0-9] remote: error: hook declined to update refs/heads/f26 To ssh://pkgs.fedoraproject.org/rpms/libyui-qt-graph ! [remote rejected] f26 -> f26 (hook declined) error: Fehler beim Versenden einiger Referenzen nach 'ssh://besse...@pkgs.fedoraproject.org/rpms/libyui-qt-graph' ``` Cheers, Björn ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: git push fails for new packages
On Wed, 2017-08-16 at 11:31 -0700, Kevin Fenzi wrote: > On 08/16/2017 11:18 AM, Martin Gansser wrote: > > i still get the message koji not in list errors, some works... some > > doesn't ... > > > > BuildError: package nuvola-app-mixcloud not in list for tag f25- > > updates-candidate > > BuildError: package nuvola-app-google-play-music not in list for > > tag f26-updates-candidate > > BuildError: package nuvola-app-google-play-music not in list for > > tag f25-updates-candidate > > The script that syncs this got stuck this morning. :( > > It's running again now... it takes about 30min or so to run, so > things > should be all updated after that. > > Additionally, we are replacing this script with one that listens to > fedmsgs and on new branches just adds those, so hopefully after today > they should get added right after the branch. > > The slow script will still run once a day to make sure no requests > were > dropped. > > kevin > I just forked fedpkg minutes ago when writing this mail. I also can't push to my forked repo. I got these fetch and push urls. mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git (fetch) mydev ssh://pkgs.fedoraproject.org/forks/cqi/rpms/fedpkg.git (push) and got similar error reported originally in this thread, FATAL: W any forks/cqi/rpms/fedpkg cqi DENIED by fallthru (or you mis-spelled the reponame) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
