Orphaned Packages in rawhide (2015-04-13)
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Package(co)maintainers Status Change === ale orphan, cicku, silfreed 8 weeks ago bfgminerorphan, pwouters 11 weeks ago clc-intercalorphan, iarnell 22 weeks ago dbus-tools orphan, miminar 22 weeks ago dircproxy orphan, jwilson 13 weeks ago erlang-jsx orphan, erlang-sig, peter 5 weeks ago fldigi-doc orphan, dp67 21 weeks ago gnome-schedule orphan, sundaram 3 weeks ago gtk-smooth-engine orphan, raveit65, vicodan 6 weeks ago identicurse orphan, smilner 4 weeks ago ip6sic orphan, flo 13 weeks ago isicorphan13 weeks ago ivtv-firmware orphan, athimm, jwilson, kwizart 6 weeks ago ivtv-utils orphan, athimm6 weeks ago jackrabbit orphan5 weeks ago libgtkhotkeyorphan, sundaram 3 weeks ago mate-user-share orphan, raveit65, vicodan 10 weeks ago maven-anno-plugin orphan, goldmann 17 weeks ago mediawiki-openidorphan, athimm, kurtseifried 6 weeks ago mercury orphan5 weeks ago mojomojoorphan, iarnell, perl-sig 22 weeks ago naimorphan, lmacken 3 weeks ago netactview orphan1 weeks ago obexftp orphan, itamarjp 0 weeks ago porkorphan, lmacken 3 weeks ago pympdtouchgui orphan, slankes 13 weeks ago python-asyncmongo orphan, silas 17 weeks ago python-sockjs-tornado orphan, gholms3 weeks ago python-sqlalchemy0.5orphan1 weeks ago python-sqlamp orphan1 weeks ago python-tvrage orphan7 weeks ago python-xkit orphan, sundaram 3 weeks ago rubygem-spruz orphan, maxamillion 6 weeks ago spambayes orphan7 weeks ago umlgraphorphan, akurtakov, fabiand, raphgro 17 weeks ago visualvmorphan, davidcl, dbhole, jerboaa, 9 weeks ago jvanek xlhtml orphan, sundaram 3 weeks ago xnoise orphan, salimma 13 weeks ago xprobe2 orphan, lmacken 3 weeks ago zoneminder orphan, mebourne 0 weeks ago zukini orphan, odysseus 11 weeks ago zukiwi orphan, odysseus 11 weeks ago The following packages require above mentioned packages: Depending on: erlang-jsx (28), status change: 2015-03-04 (5 weeks ago) thrift (maintained by: willb) erlang-thrift-0.9.1-13.fc22.3.i686 requires erlang-jsx = 1.4.2-4.fc22 accumulo (maintained by: ctubbsii, mizdebsk) accumulo-1.6.1-2.fc22.src requires libthrift-java = 0.9.1-13.fc22.3 accumulo-core-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-gc-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-master-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-server-base-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1
Orphaned Packages in branched (2015-04-13)
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Package(co)maintainers Status Change === bfgminerorphan, pwouters 8 weeks ago clc-intercalorphan, iarnell 8 weeks ago dbus-tools orphan, miminar 8 weeks ago dircproxy orphan, jwilson 8 weeks ago erlang-jsx orphan, erlang-sig, peter 5 weeks ago fldigi-doc orphan, dp67 8 weeks ago gnome-schedule orphan, sundaram 3 weeks ago gtk-smooth-engine orphan, raveit65, vicodan 6 weeks ago identicurse orphan, smilner 4 weeks ago ip6sic orphan8 weeks ago isicorphan8 weeks ago ivtv-firmware orphan, athimm, jwilson, kwizart 6 weeks ago ivtv-utils orphan, athimm6 weeks ago jackrabbit orphan5 weeks ago libgtkhotkeyorphan, sundaram 3 weeks ago mate-user-share orphan, raveit65, vicodan 8 weeks ago maven-anno-plugin orphan, goldmann 8 weeks ago mediawiki-openidorphan, athimm, kurtseifried 6 weeks ago mercury orphan5 weeks ago mojomojoorphan, iarnell, perl-sig 8 weeks ago naimorphan, lmacken 3 weeks ago netactview orphan1 weeks ago ninja orphan, adrian8 weeks ago obexftp orphan, itamarjp 0 weeks ago porkorphan, lmacken 3 weeks ago pympdtouchgui orphan, slankes 8 weeks ago python-asyncmongo orphan, silas 8 weeks ago python-sockjs-tornado orphan, gholms3 weeks ago python-sqlalchemy0.5orphan1 weeks ago python-sqlamp orphan1 weeks ago python-tvrage orphan7 weeks ago python-xkit orphan, sundaram 3 weeks ago rubygem-spruz orphan, maxamillion 6 weeks ago spambayes orphan7 weeks ago umlgraphorphan, akurtakov, fabiand, raphgro 8 weeks ago visualvmorphan, davidcl, dbhole, jerboaa, 8 weeks ago jvanek xlhtml orphan, sundaram 3 weeks ago xnoise orphan, salimma 8 weeks ago xprobe2 orphan, lmacken 3 weeks ago zoneminder orphan, mebourne 0 weeks ago zukini orphan, odysseus 8 weeks ago zukiwi orphan, odysseus 8 weeks ago The following packages require above mentioned packages: Depending on: erlang-jsx (28), status change: 2015-03-04 (5 weeks ago) thrift (maintained by: willb) erlang-thrift-0.9.1-13.fc22.3.i686 requires erlang-jsx = 1.4.2-4.fc22 accumulo (maintained by: ctubbsii, mizdebsk) accumulo-1.6.1-2.fc22.src requires libthrift-java = 0.9.1-13.fc22.3 accumulo-core-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-gc-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-master-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1, mvn(org.apache.thrift:libthrift) = 0.9.1 accumulo-server-base-1.6.1-2.fc22.noarch requires mvn(org.apache.hadoop:hadoop-client) = 2.4.1
Re: dnf replacing yum and dnf-yum
On 10. 4. 2015 at 16:21:14, Michael Schroeder wrote: > On Fri, Apr 10, 2015 at 03:52:32PM +0200, Jan Zelený wrote: > > I've been using just `dnf update` to update my system for almost a year > > now > > and there is not a single package on my system that is not updated to the > > latest version in the repo. > > Hmm, but doesn't that mean that you wouldn't care if '--best' became > the default? I guess ... I'm trying point out that if you don't need to have every single update as soon as it's out, both ways will work for you equally well. > To decide what the default should be you need to look at use cases > where the option makes a difference and then find out, what's best > (or most convenient) for the user. Agreed. I guess I'm just reluctant to change the default at the first sign of inconvenience. Chances are that the change will be inconvenient to many more people who are quiet so far because everything works great for them. Thanks Jan -- 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: dnf replacing yum and dnf-yum
On 10. 4. 2015 at 17:50:08, Reindl Harald wrote: > Am 10.04.2015 um 17:48 schrieb Marcin Juszkiewicz: > > W dniu 10.04.2015 o 16:29, Reindl Harald pisze: > >> well, that so called "crap" was in the past helpful to find out *which* > >> package pulls a cross-dep-chain while in the past 2 years yum also more > >> and more crippeled it's output > >> > >> it was also helpful in case deps where broken to find out the origin > >> package responsible for and not only once i decided to remove a specific > >> package because of that informations > >> > >> in short: that "crap" was helpful to reach to a minimum stripped down > >> systems over the years > > > > I have no doubt that it was useful in some cases. But probably 90+% of > > yum users did not cared about it at all > > but did they got hurted? > unlikely > > i really hate that attitude calling remove visible informations > "usability" while systemd on the other hand spits the logs full of > irrelevant informations all day long by burry the relevant ones We are talking about information that is irrelevant in 90+% of yum runs (allegedly, I wouldn't dare estimating this number myself). Hiding such information by default while making it available to people who really care about it sounds like a nice usability feature to me. Now, I admit that the second half is limping a bit. The information is available but it's not as easily accessible as you want it to be. If you want to help us, I invite you to write a plugin that will show the information you seek in a way you see fit. Thanks Jan -- 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: dnf replacing yum and dnf-yum
Am 13.04.2015 um 10:00 schrieb Jan Zelený: We are talking about information that is irrelevant in 90+% of yum runs (allegedly, I wouldn't dare estimating this number myself). Hiding such information by default while making it available to people who really care about it sounds like a nice usability feature to me. it is irrelevant in 90% of yum runs? so what - but it don't hurt Now, I admit that the second half is limping a bit. The information is available but it's not as easily accessible as you want it to be. If you want to help us, I invite you to write a plugin that will show the information you seek in a way you see fit and i invite you to just take the existing code in YUM and re-implement it because DNF was originally a fork of YUM and somebody has taken things away to later ask users re-implement them - that's not how the world works signature.asc Description: OpenPGP digital signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
rawhide report: 20150413 changes
Compose started at Mon Apr 13 05:15:03 UTC 2015 Broken deps for i386 -- [Agda-stdlib] ghc-agda-lib-ffi-0.0.2-5.fc22.i686 requires libHSinteger-gmp-0.5.0.0-ghc7.6.3.so ghc-agda-lib-ffi-0.0.2-5.fc22.i686 requires libHSghc-prim-0.3.0.0-ghc7.6.3.so ghc-agda-lib-ffi-0.0.2-5.fc22.i686 requires libHSbase-4.6.0.1-ghc7.6.3.so ghc-agda-lib-ffi-0.0.2-5.fc22.i686 requires ghc(base-4.6.0.1-ced5f3d8c90960e9f372129163296e44) ghc-agda-lib-ffi-devel-0.0.2-5.fc22.i686 requires ghc-devel(base-4.6.0.1-ced5f3d8c90960e9f372129163296e44) ghc-agda-lib-ffi-devel-0.0.2-5.fc22.i686 requires ghc-compiler = 0:7.6.3 ghc-agda-lib-ffi-devel-0.0.2-5.fc22.i686 requires ghc-compiler = 0:7.6.3 [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.i686 requires libofstd.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires liboflog.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg8.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg16.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libijg12.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmnet.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmjpeg.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimgle.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmimage.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.i686 requires libdcmdata.so.3.6 [aunit] aunit-2013-7.fc22.i686 requires libgnat-4.9.so [aws] aws-3.1.0-12.fc22.i686 requires libgnat-4.9.so aws-3.1.0-12.fc22.i686 requires libgnarl-4.9.so aws-devel-3.1.0-12.fc22.i686 requires libgnat-4.9.so aws-devel-3.1.0-12.fc22.i686 requires libgnarl-4.9.so [bro] broccoli-2.3-1.fc22.i686 requires bro-2.3 python-broccoli-2.3-1.fc22.i686 requires bro-2.3 [bustle] bustle-0.4.8-1.fc23.i686 requires libHSdbus-0.10.8-ghc7.8.4.so bustle-0.4.8-1.fc23.i686 requires ghc(dbus-0.10.8-ca372b3d5372ab2e67a5ef78d0f32f75) [crystal] crystal-2.2.1-2.fc22.i686 requires libkdecorations.so.4 [din] din-5.2.1-3.fc22.i686 requires libircclient.so.0 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.i686 requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.i686 requires libsres.so.14 [dsqlite] dsqlite-1.1.1-5.fc22.i686 requires libphobos-ldc.so.64 [elk] elk-mpich-2.3.22-10.fc22.i686 requires libopa.so.1 elk-mpich-2.3.22-10.fc22.i686 requires libmpl.so.1 elk-mpich-2.3.22-10.fc22.i686 requires libmpichf90.so.12 elk-mpich-2.3.22-10.fc22.i686 requires libmpich.so.12 [fawkes] fawkes-plugin-player-0.5.0-19.fc22.i686 requires libboost_thread.so.1.55.0 fawkes-plugin-player-0.5.0-19.fc22.i686 requires libboost_system.so.1.55.0 fawkes-plugin-player-0.5.0-19.fc22.i686 requires libboost_signals.so.1.55.0 [florist] florist-2011-16.fc22.i686 requires libgnat-4.9.so florist-2011-16.fc22.i686 requires libgnarl-4.9.so [gambas3] gambas3-gb-jit-3.6.1-3.fc22.i686 requires libLLVM-3.5.so [gcc-python-plugin] gcc-python2-debug-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 gcc-python2-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 gcc-python3-debug-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 gcc-python3-plugin-0.13-2.fc22.i686 requires gcc = 0:4.9.2-1.fc22 [gl3n] gl3n-0.20140505-13.fc22.i686 requires libphobos-ldc.so.64 [gnatcoll] gnatcoll-2013-9.fc22.i686 requires libgnat-4.9.so gnatcoll-2013-9.fc22.i686 requires libgnarl-4.9.so [gnome-chemistry-utils] gnome-chemistry-utils-gnumeric-0.14.10-5.fc23.i686 requires libspreadsheet-1.12.20.so [gpaw] gpaw-mpich-0.10.0.11364-9.fc22.i686 requires libopa.so.1 gpaw-mpich-0.10.0.11364-9.fc22.i686 requires libmpl.so.1 gpaw-mpich-0.10.0.11364-9.fc22.i686 requires libmpich.so.12 [gromacs] gromacs-mpich-4.6.5-5.fc22.i686 requires libopa.so.1 gromacs-mpich-4.6.5-5.fc22.i686 requires libmpl.so.1 gromacs-mpich-4.6.5-5.fc22.i686 requires libmpich.so.12 gromacs-mpich-libs-4.6.5-5.fc22.i686 requires libopa.so.1 gromacs-mpich-libs-4.6.5-5.fc22.i686 requires libmpl.so.1 gromacs-mpich-libs-4.6.5-5.fc22.i686 requires libmpich.so.12 [hadoop] hadoop-common-2.4.1-6.fc22.noarch requires mvn(io.netty:netty:3.6.6.Final) hadoop-hdfs-2.4.1-6.fc22.noarch requires mvn(org.jboss.netty:netty:3.6.6.Final) hadoop-hdfs-2.4.1-6.fc22.noarch requires mvn(io.netty:netty:3.6.6.Final) hadoop-mapreduce-2.4.1-6.fc22.noarch requires mvn(io.netty:netty:3.6.6.Final) hadoop-tests-2.4.1-6.fc22.noarch requires mvn(io.netty:netty:3.6.6.Final) [hbase] hbase-0.98.3-2.fc22.noarch requires mvn(io.netty:netty:3.6.6.Final)
Re: dnf replacing yum and dnf-yum
On Mon, 13 Apr 2015 at 10:22 Reindl Harald > > > Now, I admit that the second half is limping a bit. The information is > > available but it's not as easily accessible as you want it to be. If you > want > > to help us, I invite you to write a plugin that will show the > information you > > seek in a way you see fit > > and i invite you to just take the existing code in YUM and re-implement > it because DNF was originally a fork of YUM and somebody has taken > things away to later ask users re-implement them - that's not how the > world works > > Yes, this is how the world works in open source development, you can request all the changes you want, but it up to the upstream project to select what they want to prioritize and implement. It is much better if you make some contribution yourself, instead of complaining, if you want something to change. DNF is not YUM, it implement mostly the same features, but it is a totally different codebase, it started as fork og yum many years ago, but they have moved i differnt directions since then. You has it owns depsolver written in python, dnf uses a 3 party sat solver. So it is not possible to take code from the yum delsolver and put it into dnf, it don't make any sense at all. I coded the --skip-broken feature in yum and it took many years to get it right and caused me many gray hairs, the depsolver used in dnf has support for removing packages from the transaction there is causing problems, but it is not easy to get information from the solver and present then to the user in a good way, so I understand that the dnf developers prioritize there limited time on other things, there matter for more people. The world is changing al the time, and so does thing in Fedora, mayor parts is ripped out and replaced all the time, with new stuff there is not working as the old part. So you have to move on and learn how the new beast is working for good and bad. Tim -- 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 or review swap for libkindrv
Hi everyone, I've created a package for libkindrv which needs reviewing: https://bugzilla.redhat.com/show_bug.cgi?id=1210004 The package is a small library/driver package, so the review will probably be rather simple. I'd appreciate a review and I'm also willing to do a review swap. Thanks, 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
Re: dnf debug-info-install
On Tuesday 07 of April 2015 07:25:32 Michael Catanzaro wrote: > On Tue, 2015-04-07 at 14:15 +0200, Vít Ondruch wrote: > > Dne 7.4.2015 v 14:09 Michael Catanzaro napsal(a): > > > Hi, > > > > > > I want 'dnf debug-info-install' to be available by default on > > > Workstation. > > > > Sorry for my ignorance, but why it should be installed by default? > > > > Vít > > Because gdb recommends you use it whenever it detects that debuginfo > is missing. I plan to add a new argument to 'abrt-cli' called 'gdb' [0] which will download all the necessary debug info packages and run gdb with a core dump detected by ABRT. You wouldn't need dnf debu-ginfo-install at all, because ABRT has own algorithm for downloading the debug packages, and ABRT is installed by default (double win :). Regards, Jakub [0] https://github.com/abrt/abrt/issues/934 -- 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: hibernation support - lack of distro-wide coordination between systemd, dracut, anaconda, pm-utils and maybe more?
- Original Message -
> On 01.04.2015 10:29, Jaroslav Skarvada wrote:
> >>> pm-hibernate is obsolete as others already mentioned.
> >>
> >> Do the pm-utils maintainers/upstream know this?
> >>
> >
> > Hi,
> >
> > I am pm-utils maintainer. I own some other "legacy" packages and
> > I am retiring them only if there are good reasons for it
> > (e.g. unfixed security bugs, breakage, etc.), because there may
> > be still users using such packages / depending on their functionality.
> >
> > Regarding pm-utils, most of the functionality is currently handled
> > by systemd. If there is anybody still using it, I think it shouldn't be
> > hard to migrate. Also I think this package may be quite confusing
> > for newcomers. Upstream said it's dead, so there are probably
> > good reasons to retire. But currently there are the following
> > packages in rawhide depending on pm-utils:
> >
> > cdm
> > kdebase3
>
>
> Same as with the 'cdm'.
>
> http://pkgs.fedoraproject.org/cgit/kdebase3.git/commit/?id=2221c4
> +
> kdebase3.spec
> Patch26: kdebase-3.5.5-suspend.patch
> %define _with_suspend 1
> %{?_with_suspend:%patch26 -p1 -b .suspend}
>
> ---
> kdebase-3.5.5-suspend.patch | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kdebase-3.5.5-suspend.patch b/kdebase-3.5.5-suspend.patch
> index 0462543..e1a5d0a 100644
> --- a/kdebase-3.5.5-suspend.patch
> +++ b/kdebase-3.5.5-suspend.patch
> @@ -62,8 +62,8 @@
> +void KSMShutdownDlg::slotSuspend()
> +{
> +switch ( suspendType ) {
> -+ case SUSPEND_TYPE_HIBERNATE: system("/usr/bin/pm-hibernate"); break;
> -+ case SUSPEND_TYPE_STANDBY: system("/usr/bin/pm-suspend"); break;
> ++ case SUSPEND_TYPE_HIBERNATE: system("/usr/bin/systemctl hibernate");
> break;
> ++ case SUSPEND_TYPE_STANDBY: system("/usr/bin/systemctl suspend");
> break;
> +}
> +reject();
> +}
>
> ...
>
> > I will drop pm-utils when resolved
> >
> > regards
> >
> > Jaroslav
> >
>
> And that's it.
> - cdm DONE
> - kdebase3 DONE
> - wicd DONE
> - pm-utils DONE
>
>
>
Thanks,
retired in master
regards
Jaroslav
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
grepmail license change
The grepmail stack (perl-FileHandle-Unget, perl-Mail-Mbox-MessageParser, grepmail) has changed from GPL+ to GPLv2 in Rawhide. Paul. -- 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: dnf replacing yum and dnf-yum
- Original Message - > From: "Pete Travis" > To: "Development discussions related to Fedora" > > Sent: Friday, April 10, 2015 5:31:08 PM > Subject: Re: dnf replacing yum and dnf-yum > On Apr 10, 2015 4:39 AM, "Radek Holy" < rh...@redhat.com > wrote: > > > > > > Hm, I think that it depends on the use case. AFAIK, distro-sync is mostly > > used to upgrade Fedora (an unsupported approach AFAIK) and to replace some > > testing/3rd-party versions of package with the "official" ones. (BTW, I'd > > appreciate if anyone will share their use case) While in the first case, I > > think that the upgrade's behaviour is preferred, in the other case, the > > install's behaviour is better IMO. (Which dangerously indicates that the > > --skip-broken switch is a good solution :( ) > > > > Anyway, file an RFE (if it isn't filed already) please. We can > > track/discuss it there. > > > > Thank you in advance > > -- > > Radek Holý > > > (lots of trimming, and skipping an RFE, as this just pertains to the > distro-sync use case question) > distro-sync is useful for getting to a sane state after temporarily enabling > some repo that interacts with the primary ones. This can happen with third > party repos, but we can consider an entirely in-house situation: > The user finds a bug in widget-2.5.7 and reports it. A fix for widget is > shipped and the user is asked to test via `dnf update widget --enablerepo > updates-testing`. The transaction pulls in many requires from > updates-testing (although at this point, I realize dnf may not be upgrading > the requires in this transaction if they are not versioned). The new widget > is tested, life goes on. > Later, the user wants to install or update some package whizbang that shares > requires with widget. That package has versioned requires on packages from > the updates repo, but some of the installed packages are from > updates-testing and don't provide what whizbang needs. > Something like `dnf --allowerasing install whizbang` might be the appropriate > and precise tool to get through that transaction. `dnf distro-sync` is the > less precise, big-hammer tool for the user that doesn't know or care to > track down the intricacies of widget and whizbang dependencies. They ran > some command from a bug report a while ago and moved on, and now they run > distro-sync to return their system to a known-good state and move on. > This sort of thing is most common during the prerelease cycle, when users > will have updates-testing on then off, and there are freezes, and branching, > and lots of activity that might leave early adopters in an unsane state. > And yeah, it is very useful for upgrades. Even when ran after a proper fedup > upgrade. > --Pete Yeah, that's basically what I meant by 'replace some testing versions of package with the "official" ones'. Anyway, thank you for elaborating on it. I'll definitely make a test case from it. I'd like to let those doing the actions described above know that there is also a not very well known command "dnf repository-packages remove-or-distro-sync" which is specifically designed for switching from packages installed from testing/3rd-party repositories -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- 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: Self Introduction: Toby Goodwin
Hello Toby, On Fri, 2015-04-10 at 21:52 +, Toby Goodwin wrote: > I've been using Free Software for a very long time, and contributing in > a small way for nearly 20 years. I even worked briefly for Cygnus in the > 1990s, shortly before the Red Hat acquisition. I've been an enthusiastic > user of Fedora since... well, since long before it was called Fedora: > about Red Hat Linux 4 IIRC! > > I've been meaning to join the Fedora Developers for ages. There are a > couple of packages I'm hoping to contribute. Time permitting I'd also > like to get involved in helping to support Haskell in Fedora, as I have > some experience in this area. > > I look forward to working with you all! Welcome! Glad to have you on board! > Toby. Lubo -- 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-22 Branched report: 20150413 changes
Compose started at Mon Apr 13 07:15:03 UTC 2015 Broken deps for armhfp -- [Sprog] Sprog-0.14-27.fc20.noarch requires perl(:MODULE_COMPAT_5.18.0) [aeskulap] aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libofstd.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires liboflog.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg8.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg16.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libijg12.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmnet.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmjpeg.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmimgle.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmimage.so.3.6 aeskulap-0.2.2-0.19beta1.fc22.armv7hl requires libdcmdata.so.3.6 [avro] avro-mapred-1.7.5-9.fc22.noarch requires hadoop-mapreduce avro-mapred-1.7.5-9.fc22.noarch requires hadoop-client [bro] broccoli-2.3-1.fc22.armv7hl requires bro-2.3 python-broccoli-2.3-1.fc22.armv7hl requires bro-2.3 [crystal] crystal-2.2.1-2.fc22.armv7hl requires libkdecorations.so.4 [dnssec-check] dnssec-check-1.14.0.1-4.fc20.armv7hl requires libval-threads.so.14 dnssec-check-1.14.0.1-4.fc20.armv7hl requires libsres.so.14 [gcc-python-plugin] gcc-python2-debug-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 gcc-python2-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 gcc-python3-debug-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 gcc-python3-plugin-0.13-2.fc22.armv7hl requires gcc = 0:4.9.2-1.fc22 [kde-style-skulpture] kde-style-skulpture-0.2.4-9.fc22.armv7hl requires libkdecorations.so.4 [kfilefactory] kfilefactory-0.1.1-8.fc21.noarch requires kdebase-workspace [leksah] ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(utf8-string-0.3.7-013ef9ad8ac70ebb11df31f487b74f26) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(unix-2.6.0.1-7550b9ae9dbc74e4d6570cc239a29030) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(transformers-0.3.0.0-23508e0b4a1c1bc1cf2c2de3bb13e90c) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(time-1.4.0.1-970760bdd865d8b6cafac382276795a2) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(text-0.11.3.1-17cae9ba49c3f3d533bf78a6e387f543) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(strict-0.3.2-04f0cc1e99eff2196c0a7cd16d748b37) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(regex-tdfa-1.1.8-0b03687c4e38c00ef92e9445170081e2) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(regex-base-0.93.2-6a541a53412d1d7d310fa69bca50c85f) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(pretty-1.1.1.0-2de27f83b2c1c65d629a564e9e01b27d) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(parsec-3.1.3-a8bebef411959de671abb0f1f7da556f) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(old-time-1.1.0.1-29c02e2b3bbdfd9a5756f0c46f4d6071) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(network-2.4.1.2-82f6bcf79fe0252b3ab387e8dcb82e71) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(mtl-2.1.2-2f2cd438035824ec2bed4811930bc232) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(ltk-0.12.1.0-2fbb10498719be9dbdbb3d9f8adedbec) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(leksah-server-0.12.1.2-7dbd70c9f5e4dd8b3b5efcb6597b3bfd) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(hslogger-1.2.1-43834164508859009a3cc8aef7fd1e84) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(gtksourceview2-0.12.5.0-588b179d0562576f9afa46559cebf79f) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(gtk-0.12.5.0-2342a114ec8897cecfdda15ac92aed08) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(glib-0.12.5.0-1b94df160e141377711a221615168695) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(gio-0.12.5.0-b012293268f349d8f05c73d053798c7b) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(ghc-7.6.3-18fc786f8ad3478b9bb568d865b0e48d) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(filepath-1.3.0.1-62570c67b40fb99e7078c0d179220531) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(enumerator-0.4.19-a164f71ed1088e349dd8bc4cdee8e449) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(directory-1.2.0.1-504c99535d64699e20e001d81b577d06) ghc-leksah-devel-0.12.1.3-16.fc22.armv7hl requires ghc-devel(deepseq-1.3.0.1-aa1be128186a233c7290faf88620ffe5) ghc-leksah-devel-0.12.1.3-16.fc22.
Re: Review or review swap for libkindrv
hi, take you can chose one of these: https://bugzilla.redhat.com/show_bug.cgi?id=832803 https://bugzilla.redhat.com/show_bug.cgi?id=987558 (apache activemq openejb/tomee dep) regards gil Il 13/04/2015 10:56, Till Hofmann ha scritto: Hi everyone, I've created a package for libkindrv which needs reviewing: https://bugzilla.redhat.com/show_bug.cgi?id=1210004 The package is a small library/driver package, so the review will probably be rather simple. I'd appreciate a review and I'm also willing to do a review swap. Thanks, 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
corsepiu pushed to perl-HTML-Lint (f21). "Upstream update. (..more)"
>From e310f358114c561d4c2b3c6f5308f2d803dc58c9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ralf=20Cors=C3=A9pius?=
Date: Tue, 7 Apr 2015 11:56:09 +0200
Subject: Upstream update.
- Modernize spec.
diff --git a/.gitignore b/.gitignore
index d42c393..18ef76d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1 @@
-/HTML-Lint-2.20.tar.gz
+/HTML-Lint-2.22.tar.gz
diff --git a/perl-HTML-Lint.spec b/perl-HTML-Lint.spec
index 148ce84..1734fec 100644
--- a/perl-HTML-Lint.spec
+++ b/perl-HTML-Lint.spec
@@ -1,6 +1,6 @@
Name: perl-HTML-Lint
-Version:2.20
-Release:9%{?dist}
+Version:2.22
+Release:1%{?dist}
Summary:HTML::Lint Perl module
License:Artistic 2.0
Group: Development/Libraries
@@ -48,13 +48,16 @@ find $RPM_BUILD_ROOT -depth -type d -exec rmdir {}
2>/dev/null \;
make test
%files
-%defattr(-,root,root,-)
%doc Changes README
%{_bindir}/weblint
%{perl_vendorlib}/*
%{_mandir}/man3/*
%changelog
+* Tue Apr 07 2015 Ralf Corsépius - 2.22-1
+- Upstream update.
+- Modernize spec.
+
* Thu Aug 28 2014 Jitka Plesnikova - 2.20-9
- Perl 5.20 rebuild
diff --git a/sources b/sources
index 6c1f349..7435cc5 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-c6063f33797d6a36dc3ae2e0c3d06ded HTML-Lint-2.20.tar.gz
+b04ea191d1ffbcfd798097239a0a70ee HTML-Lint-2.22.tar.gz
--
cgit v0.10.2
http://pkgs.fedoraproject.org/cgit/perl-HTML-Lint.git/commit/?h=f21&id=e310f358114c561d4c2b3c6f5308f2d803dc58c9
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/perl-devel
[POC-change] Fedora packages point of contact updates
Change in package status over the last 168 hours 4 packages were orphaned AcetoneISO2 [master] was orphaned by moceap CD/DVD Image Manipulator https://admin.fedoraproject.org/pkgdb/package/AcetoneISO2 obexftp [f22, f21, f20, master] was orphaned by cicku Tool to access devices via the OBEX protocol https://admin.fedoraproject.org/pkgdb/package/obexftp plexus-graph [f21] was orphaned by lkundrak Graph data structures manipulation library https://admin.fedoraproject.org/pkgdb/package/plexus-graph zoneminder [f22, f21, f20, master] was orphaned by tibbs A camera monitoring and analysis tool https://admin.fedoraproject.org/pkgdb/package/zoneminder 6 packages were retired perl-Catalyst-Engine-PSGI [f22, master] was retired by jplesnik PSGI engine for Catalyst https://admin.fedoraproject.org/pkgdb/package/perl-Catalyst-Engine-PSGI perl-qpid [f22, master, epel7] was retired by mcpierce Perl bindings for the Qpid messaging framework https://admin.fedoraproject.org/pkgdb/package/perl-qpid perl-qpid_proton [f22, el6, epel7, master] was retired by mcpierce Perl language bindings for Qpid Proton https://admin.fedoraproject.org/pkgdb/package/perl-qpid_proton plexus-graph [master] was retired by mizdebsk Graph data structures manipulation library https://admin.fedoraproject.org/pkgdb/package/plexus-graph python-qpid_messaging [f22, master, epel7] was retired by mcpierce Python bindings for the Qpid messaging framework https://admin.fedoraproject.org/pkgdb/package/python-qpid_messaging systemd-ui [f22, master] was retired by zbyszek Graphical front-end for systemd https://admin.fedoraproject.org/pkgdb/package/systemd-ui 14 packages unorphaned -- django-avatar [el6] was unorphaned by kevin A django module for handling user avatars https://admin.fedoraproject.org/pkgdb/package/django-avatar django-celery [el6] was unorphaned by puiterwijk Django Celery Integration https://admin.fedoraproject.org/pkgdb/package/django-celery django-countries [el6] was unorphaned by kevin Provides a country field for Django models https://admin.fedoraproject.org/pkgdb/package/django-countries django-keyedcache [el6] was unorphaned by kevin Utilities for simplified development of cache aware objects https://admin.fedoraproject.org/pkgdb/package/django-keyedcache django-kombu [el6] was unorphaned by puiterwijk Kombu transport using the Django database as a message store https://admin.fedoraproject.org/pkgdb/package/django-kombu django-picklefield [el6] was unorphaned by puiterwijk Implementation of a pickled object field https://admin.fedoraproject.org/pkgdb/package/django-picklefield django-registration [el6] was unorphaned by puiterwijk A user-registration application for Django https://admin.fedoraproject.org/pkgdb/package/django-registration django-threaded-multihost [el6] was unorphaned by puiterwijk Django app to enable multi-site awareness in Django apps https://admin.fedoraproject.org/pkgdb/package/django-threaded-multihost git-cola [epel7] was unorphaned by moceap A sleek and powerful git GUI https://admin.fedoraproject.org/pkgdb/package/git-cola netbeans [master] was unorphaned by limb Integrated Development Environment (IDE) https://admin.fedoraproject.org/pkgdb/package/netbeans netbeans-platform8 [master] was unorphaned by limb NetBeans Platform 8 https://admin.fedoraproject.org/pkgdb/package/netbeans-platform8 python-gflags [f22, f21, f20, master] was unorphaned by orion Commandline flags module for Python https://admin.fedoraproject.org/pkgdb/package/python-gflags skychart [el6] was unorphaned by mattia Planetarium software for the advanced amateur astronomer https://admin.fedoraproject.org/pkgdb/package/skychart wss4j [f22, master] was unorphaned by mbooth Apache WS-Security implementation https://admin.fedoraproject.org/pkgdb/package/wss4j 0 packages were unretired 8 packages were given gettext-commons [f22, f21, f20, master] was given by petersen to pravins Java internationalization (i18n) library https://admin.fedoraproject.org/pkgdb/package/gettext-commons ibus-typing-booster [f22, f21, f20, master] was given by petersen to mfabian A typing booster engine for the IBus platform https://admin.fedoraproject.org/pkgdb/package/ibus-typing-booster lftp [f22, f21, f20, master] was given by thozza to luhliarik A sophisticated file transfer program https://admin.fedoraproject.org/pkgdb/package/lftp nafees-pakistani-web-naskh-fonts [f22, f21, f20, master] was given by petersen to pravins Nafees pakistani web naskh font for writing Urdu https://admin.fedoraproject.org/pkgdb/package/nafees-
dnf interactive config file updates
I see that dnf has sprung apt-style configuration file messages: -- $ sudo dnf install mingw32-srvany Using metadata from Mon Apr 13 13:56:00 2015 (1:43:07 hours old) Package mingw32-srvany-1.0-15.20150115gitfd659e77.fc23.noarch is already installed, skipping. Dependencies resolved. Nothing to do. Configuration file '/etc/pam.d/fingerprint-auth' lrwxrwxrwx. 1 root root 19 Feb 21 2012 /etc/pam.d/fingerprint-auth -> fingerprint-auth-ac -rw-r--r--. 1 root root 701 May 9 2012 /etc/pam.d/fingerprint-auth.rpmnew ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions M : merge configuration files Z : background this process to examine the situation S : skip this file The default action is to keep your current version. *** aliases (Y/I/N/O/D/M/Z/S) [default=N] ? -- In fact I _didn't_ change that file, so the message is wrong. I suspect we'll end up with Debian interactive installs, which as a Debian user I find to be a regression. - 'dnf -y install' doesn't suppress the message. - In fact you cannot even kill it with ^C. You have to killall -9 dnf. This happens on dozens of file now, every time I use dnf. Make it go away! Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v -- 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: dnf interactive config file updates
Am 13.04.2015 um 16:45 schrieb Richard W.M. Jones: I see that dnf has sprung apt-style configuration file messages: -- $ sudo dnf install mingw32-srvany Using metadata from Mon Apr 13 13:56:00 2015 (1:43:07 hours old) Package mingw32-srvany-1.0-15.20150115gitfd659e77.fc23.noarch is already installed, skipping. Dependencies resolved. Nothing to do. Configuration file '/etc/pam.d/fingerprint-auth' lrwxrwxrwx. 1 root root 19 Feb 21 2012 /etc/pam.d/fingerprint-auth -> fingerprint-auth-ac -rw-r--r--. 1 root root 701 May 9 2012 /etc/pam.d/fingerprint-auth.rpmnew ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions M : merge configuration files Z : background this process to examine the situation S : skip this file The default action is to keep your current version. *** aliases (Y/I/N/O/D/M/Z/S) [default=N] ? -- In fact I _didn't_ change that file, so the message is wrong. I suspect we'll end up with Debian interactive installs, which as a Debian user I find to be a regression. - 'dnf -y install' doesn't suppress the message WHAT? dnf really should be deleayed to F23 or F24 -y is a unconditional thing the only correct result is .rpmnew signature.asc Description: OpenPGP digital signature -- 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: dnf interactive config file updates
On Mon, 13 Apr 2015 15:45:41 +0100 "Richard W.M. Jones" wrote: > > I see that dnf has sprung apt-style configuration file messages: > > -- > $ sudo dnf install mingw32-srvany > Using metadata from Mon Apr 13 13:56:00 2015 (1:43:07 hours old) > Package mingw32-srvany-1.0-15.20150115gitfd659e77.fc23.noarch is > already installed, skipping. Dependencies resolved. > Nothing to do. > Configuration file '/etc/pam.d/fingerprint-auth' > lrwxrwxrwx. 1 root root 19 Feb 21 > 2012 /etc/pam.d/fingerprint-auth -> fingerprint-auth-ac -rw-r--r--. 1 > root root 701 May 9 2012 /etc/pam.d/fingerprint-auth.rpmnew > >==> Package distributor has shipped an updated version. > What would you like to do about it ? Your options are: > Y or I : install the package maintainer's version > N or O : keep your currently-installed version > D : show the differences between the versions > M : merge configuration files > Z : background this process to examine the situation > S : skip this file >The default action is to keep your current version. > *** aliases (Y/I/N/O/D/M/Z/S) [default=N] ? > -- > > In fact I _didn't_ change that file, so the message is wrong. > > I suspect we'll end up with Debian interactive installs, which as a > Debian user I find to be a regression. > > - 'dnf -y install' doesn't suppress the message. > > - In fact you cannot even kill it with ^C. You have to killall -9 > dnf. > > This happens on dozens of file now, every time I use dnf. Make it go > away! I suspect this is caused by the 'rpmconf' plugin ? sudo dnf remove python3-dnf-plugins-extras-rpmconf I agree it's behavior isn't good there. Bug(s) filed? kevin pgpOZju5avqBb.pgp Description: OpenPGP digital signature -- 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: dnf interactive config file updates
- Original Message - > From: "Kevin Fenzi" > To: devel@lists.fedoraproject.org > Sent: Monday, April 13, 2015 5:01:45 PM > Subject: Re: dnf interactive config file updates > > On Mon, 13 Apr 2015 15:45:41 +0100 > "Richard W.M. Jones" wrote: > > > > > I see that dnf has sprung apt-style configuration file messages: > > > > -- > > $ sudo dnf install mingw32-srvany > > Using metadata from Mon Apr 13 13:56:00 2015 (1:43:07 hours old) > > Package mingw32-srvany-1.0-15.20150115gitfd659e77.fc23.noarch is > > already installed, skipping. Dependencies resolved. > > Nothing to do. > > Configuration file '/etc/pam.d/fingerprint-auth' > > lrwxrwxrwx. 1 root root 19 Feb 21 > > 2012 /etc/pam.d/fingerprint-auth -> fingerprint-auth-ac -rw-r--r--. 1 > > root root 701 May 9 2012 /etc/pam.d/fingerprint-auth.rpmnew > > > >==> Package distributor has shipped an updated version. > > What would you like to do about it ? Your options are: > > Y or I : install the package maintainer's version > > N or O : keep your currently-installed version > > D : show the differences between the versions > > M : merge configuration files > > Z : background this process to examine the situation > > S : skip this file > >The default action is to keep your current version. > > *** aliases (Y/I/N/O/D/M/Z/S) [default=N] ? > > -- > > > > In fact I _didn't_ change that file, so the message is wrong. > > > > I suspect we'll end up with Debian interactive installs, which as a > > Debian user I find to be a regression. > > > > - 'dnf -y install' doesn't suppress the message. > > > > - In fact you cannot even kill it with ^C. You have to killall -9 > > dnf. > > > > This happens on dozens of file now, every time I use dnf. Make it go > > away! > > I suspect this is caused by the 'rpmconf' plugin ? Yes, correct. > sudo dnf remove python3-dnf-plugins-extras-rpmconf > > I agree it's behavior isn't good there. Bug(s) filed? Yes, please. Against the DNF's community plugins (dnf-plugins-extras), please. And can you please also immediately file a Bugzilla (if it does not exist) next time you hit a bug? Thanks in advance -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- 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: dnf interactive config file updates
On Mon, Apr 13, 2015 at 11:26:43AM -0400, Radek Holy wrote: > > > - Original Message - > > From: "Kevin Fenzi" > > To: devel@lists.fedoraproject.org > > Sent: Monday, April 13, 2015 5:01:45 PM > > Subject: Re: dnf interactive config file updates > > > > On Mon, 13 Apr 2015 15:45:41 +0100 > > "Richard W.M. Jones" wrote: > > > > > > > > I see that dnf has sprung apt-style configuration file messages: > > > > > > -- > > > $ sudo dnf install mingw32-srvany > > > Using metadata from Mon Apr 13 13:56:00 2015 (1:43:07 hours old) > > > Package mingw32-srvany-1.0-15.20150115gitfd659e77.fc23.noarch is > > > already installed, skipping. Dependencies resolved. > > > Nothing to do. > > > Configuration file '/etc/pam.d/fingerprint-auth' > > > lrwxrwxrwx. 1 root root 19 Feb 21 > > > 2012 /etc/pam.d/fingerprint-auth -> fingerprint-auth-ac -rw-r--r--. 1 > > > root root 701 May 9 2012 /etc/pam.d/fingerprint-auth.rpmnew > > > > > >==> Package distributor has shipped an updated version. > > > What would you like to do about it ? Your options are: > > > Y or I : install the package maintainer's version > > > N or O : keep your currently-installed version > > > D : show the differences between the versions > > > M : merge configuration files > > > Z : background this process to examine the situation > > > S : skip this file > > >The default action is to keep your current version. > > > *** aliases (Y/I/N/O/D/M/Z/S) [default=N] ? > > > -- > > > > > > In fact I _didn't_ change that file, so the message is wrong. > > > > > > I suspect we'll end up with Debian interactive installs, which as a > > > Debian user I find to be a regression. > > > > > > - 'dnf -y install' doesn't suppress the message. > > > > > > - In fact you cannot even kill it with ^C. You have to killall -9 > > > dnf. > > > > > > This happens on dozens of file now, every time I use dnf. Make it go > > > away! > > > > I suspect this is caused by the 'rpmconf' plugin ? > > Yes, correct. > > > sudo dnf remove python3-dnf-plugins-extras-rpmconf > > > > I agree it's behavior isn't good there. Bug(s) filed? > > Yes, please. Against the DNF's community plugins (dnf-plugins-extras), please. > > And can you please also immediately file a Bugzilla (if it does not exist) > next time you hit a bug? I almost always do. But what's the bug here? The feature itself or the fact that -y doesn't make it go away? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ -- 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: dnf interactive config file updates
Anyway, here is the BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1211344 Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- 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: plowshare is not shipped with modules anymore
> "EM" == Elder Marco writes: EM> So, upstream recommends to deal with "plowshare" core only, which it EM> is quite stable. And I agree. Well, look at how clamav does it. The package provides a snapshot of the virus data so that we can ship _something_. This will be updated when freshclam runs. EM> So, the question is: Am I violating Fedora Packaging Guidelines if I EM> do not provide the modules into fedora repositories? Perhaps read over https://fedoraproject.org/wiki/Packaging:Guidelines#Packages_which_are_not_useful_without_external_bits Personally, I would still ship a module package, but for that to work, the software has to have a mechanism for local downloads to override system-provided modules. - J< -- 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: Fwd: Why Isn't NFS Working?
> "KM" == Kelly Miller writes: KM> I just tried to mount my home folders using NFS as I usually do, but KM> no matter what I get the error mount.nfs: requested NFS version or KM> transport protocol is not supported. Did something change in the KM> Alpha of Fedora 22 to suddenly break NFS mounting? I've tried a KM> bunch of mount options, but nothing seems to work. I know that a kernel update in Fedora 21 broke kerberized NFS4 export (on the server) when selinux is enabled, but I'm guessing that's not your issue. Perhaps you could provide more details. - J< -- 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: dnf interactive config file updates
On Mon, 13 Apr 2015 17:43:38 +0100 "Richard W.M. Jones" wrote: > > I almost always do. > > But what's the bug here? The feature itself or the fact that -y > doesn't make it go away? I'd say at least: -y doesn't stop interactive questions from the plugin. and There's no way to exit the plugin short of kill kevin pgphIN5MKFASB.pgp Description: OpenPGP digital signature -- 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: dnf replacing yum and dnf-yum
On Mon, 2015-04-13 at 08:47 +0200, Mathieu Bridon wrote: > Le dimanche 12 avril 2015 à 17:06 -0700, Adam Williamson a écrit : > > > > It's hard to see how you build a perfect dep check other than > > trying > > to solve the deps of *every single package in the distro* against > > every proposed update. > > Can't we run repoclosure on (at the same time) the fedora repo, the > updates repo, and a temporary repo made of the packages to be pushed? > > Repoclosure does check for the deps of every single package in the > set > of repos it is provided. Not sure offhand if we've looked into using repoclosure to check this, but one obvious issue I can think of is, what if repoclosure isn't clean *to start with*? Do you diff the outputs and try to decide whether things got better or worse? And what exactly do you do when decide things got worse? Parse the repoclosure and try to guess which of the updates to blame? That's already complex enough, I guess, that we can't expect it to be 100%. I hope this discussion is illustrating that my initial point was accurate: any proposal which relies on the existence of a 100% reliable depcheck is a problematic proposal. :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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: Moving Docker image under Cloud edition?
On 04/09/2015 02:37 PM, Dennis Gilmore wrote: > On Thursday, April 09, 2015 12:07:55 PM Joe Brockmeier wrote: >> On 04/08/2015 06:41 PM, Dennis Gilmore wrote: >>> the docker base image is part of the Base WG. so it seems wrong to put it >>> on the Cloud page, but we should do something to advertise it more. >> >> But there's no Base WG page or anything... I know it's sitting there >> now, but I don't think end users care about which working group does it. >> >> Conceptually, it seems to me to fit with Cloud. Other suggestions welcome. >> >> I'm also curious whether there should be some closer collaboration >> between base wg and cloud on the container image(s)? > > there probably should be closer collaboration, it started under the cloud WG > and was moved to the Base WG. I do not really mind where it sits, but it > should not go flip flopping. OK. And apologies for contributing to that, but we're all still figuring things out there. I suppose the best answer for now is to ride out the F22 release as-is and see about changing for F23 and forward? Best, jzb -- Joe Brockmeier | Principal Cloud & Storage Analyst j...@redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/ signature.asc Description: OpenPGP digital signature -- 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: dnf replacing yum and dnf-yum
On Mon, 2015-04-13 at 10:43 -0700, Adam Williamson wrote: > On Mon, 2015-04-13 at 08:47 +0200, Mathieu Bridon wrote: > > Le dimanche 12 avril 2015 à 17:06 -0700, Adam Williamson a écrit : > > > > > > It's hard to see how you build a perfect dep check other than > > > trying > > > to solve the deps of *every single package in the distro* against > > > every proposed update. > > > > Can't we run repoclosure on (at the same time) the fedora repo, the > > updates repo, and a temporary repo made of the packages to be pushed? > > > > Repoclosure does check for the deps of every single package in the > > set > > of repos it is provided. > > Not sure offhand if we've looked into using repoclosure to check this, > but one obvious issue I can think of is, what if repoclosure isn't > clean *to start with*? Block all updates push until repoclosure gets cleaned? Of course, Bodhi admins would need to still be able to force pushes, to not block security updates or updates which fix repoclosure. Think of the incentive this would provide to fix broken deps! :) -- Mathieu -- 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: Moving Docker image under Cloud edition?
Agreed - it's too late to change anything for F22. But moving forward, I think there's a discussion that needs to happen about the inter-relationships of the various projects associated with "Cloud": 1. OpenShift Origin 2. RHEL Atomic 3. Fedora Atomic 4. CentOS Atomic 5. fedora-dockerfiles and the underlying upstreams - Docker and Kubernetes. Some questions: 1. Will OpenShift Origin ever be distributed via Fedora? 2. Will CentOS Atomic always be independent of both Fedora Atomic and RHEL Atomic? 3. Will there always be three forums for interaction with the fedora-dockerfiles project (GitHub issues, Cloud Trac and RedHat Bugzilla?) I note that many of the pieces here are clearly marked as "for developers - not ready for production". So the over-arching question for me as a user/developer is, "When *will* they be ready for production?" On Mon, Apr 13, 2015 at 10:58 AM, Joe Brockmeier wrote: > On 04/09/2015 02:37 PM, Dennis Gilmore wrote: >> On Thursday, April 09, 2015 12:07:55 PM Joe Brockmeier wrote: >>> On 04/08/2015 06:41 PM, Dennis Gilmore wrote: the docker base image is part of the Base WG. so it seems wrong to put it on the Cloud page, but we should do something to advertise it more. >>> >>> But there's no Base WG page or anything... I know it's sitting there >>> now, but I don't think end users care about which working group does it. >>> >>> Conceptually, it seems to me to fit with Cloud. Other suggestions welcome. >>> >>> I'm also curious whether there should be some closer collaboration >>> between base wg and cloud on the container image(s)? >> >> there probably should be closer collaboration, it started under the cloud WG >> and was moved to the Base WG. I do not really mind where it sits, but it >> should not go flip flopping. > > OK. And apologies for contributing to that, but we're all still figuring > things out there. > > I suppose the best answer for now is to ride out the F22 release as-is > and see about changing for F23 and forward? > > Best, > > jzb > -- > Joe Brockmeier | Principal Cloud & Storage Analyst > j...@redhat.com | http://community.redhat.com/ > Twitter: @jzb | http://dissociatedpress.net/ > > > -- > devel mailing list > devel@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/devel > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- OSJourno: Robust Power Tools for Digital Journalists http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. -- 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: Moving Docker image under Cloud edition?
I left off two pieces 6. Fedora Docker Hub images, and 7. CentOS Docker Hub images, which are vastly more popular than the Fedora ones. On Mon, Apr 13, 2015 at 11:49 AM, M. Edward (Ed) Borasky wrote: > Agreed - it's too late to change anything for F22. But moving forward, > I think there's a discussion that needs to happen about the > inter-relationships of the various projects associated with "Cloud": > > 1. OpenShift Origin > 2. RHEL Atomic > 3. Fedora Atomic > 4. CentOS Atomic > 5. fedora-dockerfiles > > and the underlying upstreams - Docker and Kubernetes. Some questions: > > 1. Will OpenShift Origin ever be distributed via Fedora? > 2. Will CentOS Atomic always be independent of both Fedora Atomic and > RHEL Atomic? > 3. Will there always be three forums for interaction with the > fedora-dockerfiles project (GitHub issues, Cloud Trac and RedHat > Bugzilla?) > > I note that many of the pieces here are clearly marked as "for > developers - not ready for production". So the over-arching question > for me as a user/developer is, "When *will* they be ready for > production?" > > On Mon, Apr 13, 2015 at 10:58 AM, Joe Brockmeier wrote: >> On 04/09/2015 02:37 PM, Dennis Gilmore wrote: >>> On Thursday, April 09, 2015 12:07:55 PM Joe Brockmeier wrote: On 04/08/2015 06:41 PM, Dennis Gilmore wrote: > the docker base image is part of the Base WG. so it seems wrong to put it > on the Cloud page, but we should do something to advertise it more. But there's no Base WG page or anything... I know it's sitting there now, but I don't think end users care about which working group does it. Conceptually, it seems to me to fit with Cloud. Other suggestions welcome. I'm also curious whether there should be some closer collaboration between base wg and cloud on the container image(s)? >>> >>> there probably should be closer collaboration, it started under the cloud WG >>> and was moved to the Base WG. I do not really mind where it sits, but it >>> should not go flip flopping. >> >> OK. And apologies for contributing to that, but we're all still figuring >> things out there. >> >> I suppose the best answer for now is to ride out the F22 release as-is >> and see about changing for F23 and forward? >> >> Best, >> >> jzb >> -- >> Joe Brockmeier | Principal Cloud & Storage Analyst >> j...@redhat.com | http://community.redhat.com/ >> Twitter: @jzb | http://dissociatedpress.net/ >> >> >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel >> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > > > > -- > OSJourno: Robust Power Tools for Digital Journalists > http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists > > Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. -- OSJourno: Robust Power Tools for Digital Journalists http://www.znmeb.mobi/stories/osjourno-robust-power-tools-for-digital-journalists Remember, if you're traveling to Bactria, Hump Day is Tuesday and Thursday. -- 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: dnf interactive config file updates
On Mon, Apr 13, 2015 at 17:49:45 +0100, "Richard W.M. Jones" wrote: Anyway, here is the BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1211344 I filed https://bugzilla.redhat.com/show_bug.cgi?id=1208626 previously. You can disable it on the command line for scripting. -- 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: dnf interactive config file updates
On Mon, Apr 13, 2015 at 02:17:14PM -0500, Bruno Wolff III wrote: > On Mon, Apr 13, 2015 at 17:49:45 +0100, > "Richard W.M. Jones" wrote: > > > >Anyway, here is the BZ: > >https://bugzilla.redhat.com/show_bug.cgi?id=1211344 > > I filed https://bugzilla.redhat.com/show_bug.cgi?id=1208626 previously. > You can disable it on the command line for scripting. OK, but I think it's better if all dnf plugins understand 'dnf -y', otherwise we'll end up having to have a pile of --disableplugin hacks for every badly behaved plugin. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW -- 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: Fwd: Why Isn't NFS Working?
Let's see... The server is CentOS 6. There's nothing fancy about the setup; rather than running an account sync like NIS or LDAP, I just make sure that both computers have the same users with the same user id's on both computers (it's a home network setup with both computers sitting right next to each other with a switch between them, so I can guarantee that). I'm using the same fstab options I normally use: hard, intr, rsize=8192, wsize=8192, tcp, nfsvers=3 . But for whatever reason, I get this message whenever I try to mount the drive. On Mon, Apr 13, 2015 at 12:54 PM, Jason L Tibbitts III wrote: > > "KM" == Kelly Miller writes: > > KM> I just tried to mount my home folders using NFS as I usually do, but > KM> no matter what I get the error mount.nfs: requested NFS version or > KM> transport protocol is not supported. Did something change in the > KM> Alpha of Fedora 22 to suddenly break NFS mounting? I've tried a > KM> bunch of mount options, but nothing seems to work. > > I know that a kernel update in Fedora 21 broke kerberized NFS4 export > (on the server) when selinux is enabled, but I'm guessing that's not > your issue. Perhaps you could provide more details. > > - J< > -- 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: Fwd: Why Isn't NFS Working?
I managed to figure it out. nfs-lock doesn't seem to be starting through systemd, and I'm not sure why. I can start it using start manually, but when I try to enable it to start on system load, it claims "No file or directory". On Mon, Apr 13, 2015 at 6:15 PM, Kelly Miller wrote: > Let's see... > The server is CentOS 6. There's nothing fancy about the setup; rather > than running an account sync like NIS or LDAP, I just make sure that both > computers have the same users with the same user id's on both computers > (it's a home network setup with both computers sitting right next to each > other with a switch between them, so I can guarantee that). I'm using the > same fstab options I normally use: hard, intr, rsize=8192, wsize=8192, tcp, > nfsvers=3 . But for whatever reason, I get this message whenever I try to > mount the drive. > > On Mon, Apr 13, 2015 at 12:54 PM, Jason L Tibbitts III > wrote: > >> > "KM" == Kelly Miller writes: >> >> KM> I just tried to mount my home folders using NFS as I usually do, but >> KM> no matter what I get the error mount.nfs: requested NFS version or >> KM> transport protocol is not supported. Did something change in the >> KM> Alpha of Fedora 22 to suddenly break NFS mounting? I've tried a >> KM> bunch of mount options, but nothing seems to work. >> >> I know that a kernel update in Fedora 21 broke kerberized NFS4 export >> (on the server) when selinux is enabled, but I'm guessing that's not >> your issue. Perhaps you could provide more details. >> >> - J< >> > > -- 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: hibernation support - lack of distro-wide coordination between systemd, dracut, anaconda, pm-utils and maybe more?
OK not everyone is on the same page, apparently. This bug was just closed by Anaconda as WONTFIX. suggested swap for laptop seems low https://bugzilla.redhat.com/show_bug.cgi?id=1037472 I don't see how hibernation works reliably with such a low default swap size. Chris Murphy -- 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: dnf interactive config file updates
On Mon, Apr 13, 2015 at 21:20:49 +0100, "Richard W.M. Jones" wrote: On Mon, Apr 13, 2015 at 02:17:14PM -0500, Bruno Wolff III wrote: On Mon, Apr 13, 2015 at 17:49:45 +0100, "Richard W.M. Jones" wrote: > >Anyway, here is the BZ: >https://bugzilla.redhat.com/show_bug.cgi?id=1211344 I filed https://bugzilla.redhat.com/show_bug.cgi?id=1208626 previously. You can disable it on the command line for scripting. OK, but I think it's better if all dnf plugins understand 'dnf -y', otherwise we'll end up having to have a pile of --disableplugin hacks for every badly behaved plugin. I mentioned that because I thought it might be useful now. I'd like to see a config file for every plugin so that you can disable them without having to uninstall them. For the rpmconf plugin it would also be nice to be able to set some behavior for scripts other than ignore. I believe I noted that in my bug report. -- 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: hibernation support - lack of distro-wide coordination between systemd, dracut, anaconda, pm-utils and maybe more?
On Mon, Apr 13, 2015 at 04:39:38PM -0600, Chris Murphy wrote: > OK not everyone is on the same page, apparently. This bug was just > closed by Anaconda as WONTFIX. > > suggested swap for laptop seems low > https://bugzilla.redhat.com/show_bug.cgi?id=1037472 > > I don't see how hibernation works reliably with such a low default swap size. Yeah, hibernation is automatically invoked when battery runs low (and is generally useful in other cases), so we should provide enough swap for it to work. With moern disk sizes 4GB one way or the other is hardly noticable, so it doesn't make sense to economize. Zbyszek -- 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: plowshare is not shipped with modules anymore
Thanks! cicku, good idea! Ralf, plowshare is a command-line downloader/uploader for some of the most popular file-sharing websites. Each module (written in bash) corresponds to a different sharing site. The modules are downloaded via plowmod, from a oficial repository provided by upstream. But, the users can install a module provided by another user, if they want to. The modules are updated constantly and it is difficult to update the package at the same pace. So, providing a core package and let the users to update the modules is a better idea in my opinion. The modules are installed under ~/.config/plowshare/modules.d/ Jason, thanks! I could package the modules. But this is not a good ideia as explained above. The package will be quickly outdated. Perharps, before I mark it as stable. However, if necessary, I will submit a review request to a new package, that will contain the modules. On Mon, Apr 13, 2015 at 1:52 PM, Jason L Tibbitts III wrote: > > "EM" == Elder Marco writes: > > EM> So, upstream recommends to deal with "plowshare" core only, which it > EM> is quite stable. And I agree. > > Well, look at how clamav does it. The package provides a snapshot of > the virus data so that we can ship _something_. This will be updated > when freshclam runs. > > EM> So, the question is: Am I violating Fedora Packaging Guidelines if I > EM> do not provide the modules into fedora repositories? > > Perhaps read over > > https://fedoraproject.org/wiki/Packaging:Guidelines#Packages_which_are_not_useful_without_external_bits > > Personally, I would still ship a module package, but for that to work, > the software has to have a mechanism for local downloads to override > system-provided modules. > > - J< > -- Elder Marco GNU/Linux User: #471180 "O conhecimento é tristeza: aqueles que mais sabem são os que mais profundamente devem lamentar a mais fatal verdade, a árvore do conhecimento não é a da vida." (Da tragédia Manfred, de Byron e citado por Nietzsche em "Humano, Demasiado humano") -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
[Test-Announce] Fedora 22 Virt Test Day is Thu Apr 16!
Hey all, A reminder that the Fedora 22 Virt Test Day is this coming Thu Apr 16. Check out the test day landing page: https://fedoraproject.org/wiki/Test_Day:2015-04-16_Virtualization It's a great time to make sure your virt workflow is still working correctly with the latest packages in Fedora 22. No requirement to run through test cases on the wiki, just show up and let us know what works (or breaks). Thanks, Cole ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- 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: Texlive packaging (Was: A proposal for Fedora updates)
Jindrich Novy wrote: > What's wrong with it? It is autogenerated, you are not supposed to touch > the spec file directly but edit texlive.spec.template and regenerate the > spec file by tl2rpm. All subpackages are generated with correct > dependencies (at least according to upstream metadata) and packages with > wrong non-free licences are excluded from build automatically. The issue is that a security fix that really only required fixing one package's scriptlets ended up requiring users of Fedora 21 and even Fedora 20 to update thousands of binary packages that didn't actually change at all. Over a slow Internet connection or with a slow CPU, this can take hours. Kevin Kofler -- 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: dnf replacing yum and dnf-yum
Kevin Fenzi wrote: > * dnf-yum is installed by default. By that I mean it is in the 'core' > group in comps next to dnf. [snip] > * If you wish to still use yum, the yum package provides now > a /usr/bin/yum-deprecated command that is the old yum > command renamed. It also has the notice message as above > on it. IMHO, this is a really bad solution. yum should be yum, dnf should be dnf. Kevin Kofler -- 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: dnf interactive config file updates
Kevin Fenzi wrote: > I suspect this is caused by the 'rpmconf' plugin ? > > sudo dnf remove python3-dnf-plugins-extras-rpmconf IMHO, this kind of plugins (also the snapper one) really ought to ship off by default and require a config file entry to explicitly enable. The mere act of installing a package must not change the behavior of such a core tool in this way. In combination with the allowance for users installing signed packages in PackageKit, this can even be argued to be a security issue. Kevin Kofler -- 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: hibernation support - lack of distro-wide coordination between systemd, dracut, anaconda, pm-utils and maybe more?
On Tue, 2015-04-14 at 00:39 +, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Apr 13, 2015 at 04:39:38PM -0600, Chris Murphy wrote: > > OK not everyone is on the same page, apparently. This bug was just > > closed by Anaconda as WONTFIX. > > > > suggested swap for laptop seems low > > https://bugzilla.redhat.com/show_bug.cgi?id=1037472 > > > > I don't see how hibernation works reliably with such a low default > > swap size. > Yeah, hibernation is automatically invoked when battery runs low > (and is generally > useful in other cases), so we should provide enough swap for it to > work. With > moern disk sizes 4GB one way or the other is hardly noticable, 'Modern disk sizes' like the 128GB (that's GB, not GiB) that's standard on the basic XPS 13 developer edition model, fr'instance? http://www.dell.com/us/business/p/xps-13-linux/pd -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- 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: plowshare is not shipped with modules anymore
On 04/14/2015 03:01 AM, Elder Marco wrote: Ralf, plowshare is a command-line downloader/uploader for some of the most popular file-sharing websites. Each module (written in bash) corresponds to a different sharing site. The modules are downloaded via plowmod, from a oficial repository provided by upstream. Well, as I said before, I do not like packages, which are doing so. I consider them to be a security and data privacy risk, but I am not in a position to change upstreams nor users. My advise to users: Don't use such packages if you are concerned about your data and your installations' security. Ralf -- 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: hibernation support - lack of distro-wide coordination between systemd, dracut, anaconda, pm-utils and maybe more?
On Mon, Apr 13, 2015 at 07:20:46PM -0700, Adam Williamson wrote: > On Tue, 2015-04-14 at 00:39 +, Zbigniew Jędrzejewski-Szmek wrote: > > On Mon, Apr 13, 2015 at 04:39:38PM -0600, Chris Murphy wrote: > > > OK not everyone is on the same page, apparently. This bug was just > > > closed by Anaconda as WONTFIX. > > > > > > suggested swap for laptop seems low > > > https://bugzilla.redhat.com/show_bug.cgi?id=1037472 > > > > > > I don't see how hibernation works reliably with such a low default > > > swap size. > > Yeah, hibernation is automatically invoked when battery runs low > > (and is generally > > useful in other cases), so we should provide enough swap for it to > > work. With > > moern disk sizes 4GB one way or the other is hardly noticable, > > 'Modern disk sizes' like the 128GB (that's GB, not GiB) that's > standard on the basic XPS 13 developer edition model, fr'instance? > http://www.dell.com/us/business/p/xps-13-linux/pd That one's tough. Disk is less than 15 times memory size (30 or 60 for the higher end models). OK, so swap 2x memory seems excessive. Actually swap with the same as memory should work *most* of the time. There's no guarantee that any amount swap will be enough, since it could all be filled by the time hibernation is requested, but we should try to cover most normal usage. But considering that swap will be slow on HDD, so users will most likely avoid using more than a small amount, and SDD are small, so it's expensive to provide bigger swap, the default that anaconda uses seems OK. An exception is for computers with small amount of RAM (<= 2GB?). There swaps is more likely to be filled and the default size for swap should imho be higher than the amount of RAM. The details can be worked out. But I don't understand the justification for closing of the bug: (In reply to David Lehman from comment #1) > Anaconda does not automatically configure systems for hibernation at this > time. Hibernation is important for many use cases, including graphical environments, and anaconda should support them. Zbyszek -- 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: hibernation support - lack of distro-wide coordination between systemd, dracut, anaconda, pm-utils and maybe more?
On 04/13/2015 08:34 PM, Zbigniew Jędrzejewski-Szmek wrote: The details can be worked out. But I don't understand the justification for closing of the bug: (In reply to David Lehman from comment #1) Anaconda does not automatically configure systems for hibernation at this time. Hibernation is important for many use cases, including graphical environments, and anaconda should support them. Especially since Gnome by default hibernates on low battery. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
