Re: How quickly should we retire orphaned packages?
On Fri, Aug 22, 2014 at 09:07:34AM +0100, Richard W.M. Jones wrote: > I don't understand the reference to "up to six months later" here. > > Can you explain how retirement is proposed to work precisely, with > timescales. > And here, "unretired without much effort" means what exactly? This is the process for Fedora (EPEL is slightly different in case someone wonders): - PoCs can orphan their packages every time for every release (Maybe this applies to everyone with commit ACLs or should at least allow for everyone with commit ACLs) - Anyone can retire orphaned packages in Branched till the final change deadline or in Rawhide. Then a reason is stored in a dead.package file in dist-git. - Once a week there is a report sent to devel@fpo about which packages were retired/orphaned in the previous week - Prior to branching, all orphaned and long time FTBFS packages are retired by rel-eng (with two releases a year, every orphaned package would be retired up to six months later). Also packages depending on packages to be retired will be retired, unless someone takes care of them. The announcements usually start some weeks prior to branching. - Up to two weeks after a package is retired, no re-review is required, so unretirement requires a ticket for rel-eng to unblock the package from koji to allow builds being distributed, an update to pkgdb to change the state from Retired to Approved (which currently needs to be made by rel-eng as well), and reverting the last commit in dist-git - Afterwards unretiring a package requires are re-review. Regards Till -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
F-21 Branched report: 20140823 changes
Compose started at Sat Aug 23 07:15:02 UTC 2014 Broken deps for armhfp -- [APLpy] APLpy-0.9.8-5.fc21.noarch requires pywcs [PyKDE] PyKDE-3.16.6-14.fc20.armv7hl requires sip-api(10) >= 0:10.0 [PyQuante] PyQuante-libint-1.6.4-11.fc21.1.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [audtty] audtty-0.1.12-9.fc20.armv7hl requires libaudclient.so.2 [authhub] authhub-0.1.2-3.fc19.armv7hl requires libjson.so.0 [cp2k] cp2k-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 cp2k-mpich-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 cp2k-openmpi-2.5.1-8.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [csound] csound-java-5.19.01-1.fc20.armv7hl requires libgcj_bc.so.1 csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat csound-java-5.19.01-1.fc20.armv7hl requires java-gcj-compat csound-java-5.19.01-1.fc20.armv7hl requires java-1.5.0-gcj csound-tk-5.19.01-1.fc20.armv7hl requires libtk8.5.so csound-tk-5.19.01-1.fc20.armv7hl requires libtcl8.5.so [deltacloud-core] deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudservers) deltacloud-core-rackspace-1.1.3-1.fc20.noarch requires rubygem(cloudfiles) [docker-registry] docker-registry-0.7.3-1.fc21.noarch requires docker-io [dragonegg] dragonegg-3.4-0.3.rc0.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [edelib] edelib-2.1-5.fc21.armv7hl requires libedelib.so edelib-devel-2.1-5.fc21.armv7hl requires libedelib.so [eucalyptus] eucalyptus-common-java-3.3.0-0.5.20130408git32052445.fc20.armv7hl requires hibernate3-jbosscache >= 0:3.6.10-7 [fatrat] 1:fatrat-1.2.0-0.21.beta2.fc21.armv7hl requires libtorrent-rasterbar.so.7 [flashrom] flashrom-0.9.6.1-5.svn1705.fc20.armv7hl requires libftdi.so.1 [flush] flush-0.9.12-10.fc21.armv7hl requires libtorrent-rasterbar.so.7 [freesteam] freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires libascend.so.1 [gcc-python-plugin] gcc-python2-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python2-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires libpython3.3dm.so.1.0 gcc-python3-debug-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 gcc-python3-plugin-0.12-18.fc21.armv7hl requires libpython3.3m.so.1.0 gcc-python3-plugin-0.12-18.fc21.armv7hl requires gcc = 0:4.8.2-14.fc21 [gedit-valencia] gedit-valencia-0.4.0-1.20131223git94442bf.fc21.armv7hl requires libvala-0.24.so.0 [ghc-hint] ghc-hint-devel-0.4.2.0-2.fc21.armv7hl requires ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc) [gnome-python2-desktop] gnome-python2-metacity-2.32.0-18.fc21.armv7hl requires libmetacity-private.so.0 [gnome-shell-extension-pomodoro] gnome-shell-extension-pomodoro-0.10.0-4.fc21.armv7hl requires libupower-glib.so.2 [gofer] ruby-gofer-0.77.1-2.fc21.noarch requires rubygem(qpid) >= 0:0.16.0 [hibernate-search] hibernate-search-4.5.1-4.fc21.noarch requires mvn(org.apache.avro:avro) [ice] ice-php-3.5.1-4.fc21.armv7hl requires php(zend-abi) = 0:20121212-32 ice-php-3.5.1-4.fc21.armv7hl requires php(api) = 0:20121113-32 [leiningen] leiningen-1.7.1-7.fc20.noarch requires maven-ant-tasks leiningen-1.7.1-7.fc20.noarch requires classworlds [leksah] ghc-leksah-devel-0.12.1.3-15.fc21.armv7hl requires ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc) [leksah-server] ghc-leksah-server-devel-0.12.1.2-15.fc21.armv7hl requires ghc-devel(ghc-7.6.3-9662c0f342b2d5c9e1cd2b6330e697bc) [libghemical] libghemical-2.99.1-24.fc20.armv7hl requires libf77blas.so.3 libghemical-2.99.1-24.fc20.armv7hl requires libatlas.so.3 [libopensync-plugin-irmc] 1:libopensync-plugin-irmc-0.22-7.fc20.armv7hl requires libopenobex.so.1 [libvirt] libvirt-lock-sanlock-1.2.7-2.fc21.armv7hl requires sanlock >= 0:2.4 libvirt-lock-sanlock-1.2.7-2.fc21.armv7hl requires libsanlock_client.so.1 [lirc] lirc-0.9.1a-2.fc21.armv7hl requires libiguanaIR.so.0(IGUANAIR_0) lirc-0.9.1a-2.fc21.armv7hl requires libiguanaIR.so.0 [ltsp] ltsp-client-5.4.5-8.fc21.armv7hl requires fuse-unionfs ltsp-server-5.4.5-8.fc21.armv7hl requires cdialog [meshmagick] meshmagick-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 meshmagick-libs-0.6.0-20.svn2898.fc21.armv7hl requires libOgreMain.so.1.8.1 [monodevelop-vala] monodevelop-vala-2.8.8.1-6.fc21.armv7hl requires vala < 0:0.25.0 [mpqc] mpqc-2.3.1-26.fc21.armv7hl requires libint(armv7hl-32) = 0:1.1.6-2.fc21 [netdisco] netdisco-1.1-7.fc21.noarch requires perl(SNMP::Info::Layer2::Bay) [openstack-nova]
Re: ModemManager update to 1.4.0 release
ModemManager http://freedesktop.org/wiki/Software/ModemManager - update to 1.4.0 release https://bugzilla.redhat.com/show_bug.cgi?id=1125426 ModemManager 1.4.0 --- This is a new stable release of ModemManager. * This version requires libmbim >= 1.10.0. This version comes with the following updates in the interfaces: * Updated the logic around the IP configuration properties in the Bearer: ** Setting DHCP as IP method in the IPv6 settings means that SLAAC should be used to retrieve correct addressing and routing details. ** DHCP IP method may now be combined with an explicit static IP address, as IPv6 SLAAC may require the link-local address to be present. ** MTU is now also included in the IP configuration properties, if specified by the modem, and applicable to both DHCP and STATIC methods. * New 'OFF' power state, which fully switches off the modem device. After setting the modem in this state, no further use of it can be done. Currently available in Wavecom and Cinterion. * Location interface: new 'unmanaged GPS' support, which allows to start/stop the GPS module in the modem, while leaving the location information retrieval to other processes. Currently available in modems with independent GPS TTYs, like Option/HSO, Cinterion and Huawei. * New Test DBus interface: not to be installed, just for internal system tests. Other notable changes include: * MBIM: support for ZTE and Sequans Communications modems. * Ericsson MBM: Support for AT-capable /dev/cdc-wdm ports. * Huawei: improved support for Network time retrieval. * Huawei: implemented GPS support. * Huawei: support for /dev/cdc-wdm AT ports via the new huawei-cdc-ncm driver. * Cinterion: implemented GPS support. * Cinterion: implemented unlock retries loading. * Cinterion: gather port types for multi-tty devices. * Cinterion: custom wait for SIM readiness after SIM-PIN unlock. * Wavecom: custom wait for SIM readiness after SIM-PIN unlock. * Probing: new flag to identify hotplugged devices which don't need full reset. * Tests: internal refactor of the ports handling code, allowing test-driven virtual ports and system tests run during 'make check'. This new feature also comes with a new internal 'Test' DBus interface, as well as new --test-[*] options in the ModemManager program. * and many more fixes... Delegating to you Matthew, so you don't get bored[1]. :) poma [1] http://events.linuxfoundation.org/sites/events/files/slides/Fedora-LinuxConNA-2014.pdf -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Review swap
Hi, due to a new dependence in the IQmol package, I need to get OpenMesh reviewed. https://bugzilla.redhat.com/show_bug.cgi?id=1132691 It's a very straightforward package, and I'm willing to review something of similar complexity. -- Susi Lehtola Fedora Project Contributor jussileht...@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: rawhide report: 20140823 changes
On 08/23/2014 09:03 AM, Fedora Rawhide Report wrote: Broken deps for i386 -- [gdal] gdal-1.11.0-7.fc22.i686 requires libgeotiff.so.1.2 gdal-java-1.11.0-7.fc22.i686 requires libgeotiff.so.1.2 gdal-libs-1.11.0-7.fc22.i686 requires libgeotiff.so.1.2 gdal-perl-1.11.0-7.fc22.i686 requires libgeotiff.so.1.2 I ran into this breakage today while trying to update some of my packages, it looks like it has to do with the mass rebuild that was just done. libgeotiff was rebuilt with a bumped soname on 2014-07-12 [1]. gdal's changelog shows that it was rebuilt on 2014-07-14 to pick up libgeotiff's soname change. Unfortunately, when gdal was rebuilt in the mass rebuild, koji pulled in an older version of libgeotiff: 1.25.15 which was built on 2014-06-07[2]. It now conflicts with libgeotiff-1.4.0 that is available in rawhide. There's several other packages in the list that are complaining about a missing libgeotiff.so.1.2, and some other packages that had a soname bump after the rebuild cutoff may also be affected. I haven't dug in any further than libgeotiff, just wanted to give everyone a head's up. Could a provenpackager handle rebuilding the packages that depend on libgeotiff? Thanks, Rich [1] http://koji.fedoraproject.org/koji/buildinfo?buildID=543467 [2] https://kojipkgs.fedoraproject.org//packages/gdal/1.11.0/7.fc22/data/logs/x86_64/root.log -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Unresponsive maintainer: skytux
Hello, I would like to ask if somebody knows how to contact Germán Racca, fas skytux. My last communication with him was in May, we talked about updating APLpy to use astropy instead of pywcs. Since then, he hasn't answered me. This is the request to update APLpy https://bugzilla.redhat.com/show_bug.cgi?id=1116895 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[HEADS UP] mesa 10.3-rc1 coming to f21
Hi, yesterday I've updated mesa to 10.4 (latest upstream commit) for rawhide[0]. Today I've updated mesa to 10.3-rc1 for f21[1]. Just merged master branch and prepared sources for 10.3-rc1. Hope it will not break anything, but FYI. I'm starting build it right now. [0] http://pkgs.fedoraproject.org/cgit/mesa.git/commit/?id=21f1a7fe9c861f76c1d4fd27c488629dcf4d24d2 [1] http://pkgs.fedoraproject.org/cgit/mesa.git/commit/?h=f21&id=25554877f69aa5eb6c3ce69fe716b221388ec26f -- -Igor Gnatenko signature.asc Description: This is a digitally signed message part -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
