[opensuse-factory] Bulk renaming of "README.SuSE"
Hi all, Dominique is cleaning up packages and renaming "README.SuSE" files to "README.SUSE". While this is of course warrented in principle, there is one case to consider. If the README.SuSE is hugely outdated, then the wrong spelling at least suggest that it is not new ;-) My example is the ifplugd package. I actually would not have expected anyone to still use this, but there was a bugreport, so I recently added a trivial patch to increase a netlink buffer size. Looking at README.SuSE (which comes from the upstream tarball), I am not even able to judge if this might actually work at all with todays networking mess that's called wicked. So I'm not sure if it is a good idea to suggest this file is relatively current by using the "new" spelling, when it definitely is not. Thanks for considering, and have a lot of fun... :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
Hi all,
Dominique is cleaning up packages and renaming "README.SuSE" files to "README.SUSE".
While this is of course warrented in principle, there is one case to consider. If the README.SuSE is hugely outdated, then the wrong spelling at least suggest that it is not new ;-)
My example is the ifplugd package. I actually would not have expected anyone to still use this, but there was a bugreport, so I recently added a trivial patch to increase a netlink buffer size.
Looking at README.SuSE (which comes from the upstream tarball), I am not even able to judge if this might actually work at all with todays networking mess that's called wicked. So I'm not sure if it is a good idea to suggest this file is relatively current by using the "new" spelling, when it definitely is not.
Thanks for considering, and have a lot of fun... :-)
I would suggest to not do automatic renaming, but manual renaming after checking that the contents are (at least apparently) correct. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloKHusACgkQtTMYHG2NR9VplACaA2z1XpmGE7M3Q1F2DSeH+nPi GxMAni8n8eBAdC29qGNQkc16ecRra8hV =Bs2/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
Hi all,
Dominique is cleaning up packages and renaming "README.SuSE" file
Thanks for considering, and have a lot of fun... :-)
I would suggest to not do automatic renaming, but manual renaming after checking that the contents are (at least apparently) correct.
Hi 1) Why do you assume its done automatically 2) Checking content of said files is of course not trivial amount of work - how about instead of suggesting that someone else does more work you do it? Cheers M
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
Hi all,
Dominique is cleaning up packages and renaming "README.SuSE" file
Thanks for considering, and have a lot of fun... :-)
I would suggest to not do automatic renaming, but manual renaming after checking that the contents are (at least apparently) correct.
Hi
1) Why do you assume its done automatically
Because the thread tittle has the word "Bulk".
2) Checking content of said files is of course not trivial amount of work - how about instead of suggesting that someone else does more work you do it?
Because I don't have access, sorry. OBS is a totally obscure art to me. I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
Hi all,
Dominique is cleaning up packages and renaming "README.SuSE" file
Thanks for considering, and have a lot of fun... :-)
I would suggest to not do automatic renaming, but manual renaming after checking that the contents are (at least apparently) correct.
Hi
1) Why do you assume its done automatically
Because the thread tittle has the word "Bulk".
2) Checking content of said files is of course not trivial amount of work - how about instead of suggesting that someone else does more work you do it?
Because I don't have access, sorry. OBS is a totally obscure art to me.
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current. That might be actually helpfull
M
On mardi, 14 novembre 2017 13.21:43 h CET martin@pluskal.org wrote:
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
Hi all,
Dominique is cleaning up packages and renaming "README.SuSE" file
Thanks for considering, and have a lot of fun... :-)
I would suggest to not do automatic renaming, but manual renaming after checking that the contents are (at least apparently) correct.
Hi
1) Why do you assume its done automatically
Because the thread tittle has the word "Bulk".
2) Checking content of said files is of course not trivial amount of work - how about instead of suggesting that someone else does more work you do it?
Because I don't have access, sorry. OBS is a totally obscure art to me.
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current.
That might be actually helpfull
M
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML). Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-11-14 13:27, Bruno Friedmann wrote:
On mardi, 14 novembre 2017 13.21:43 h CET martin@pluskal.org wrote:
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current.
That might be actually helpfull
M
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML).
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution.
Ok, I can do that. One bugzilla per file - is there a list of readmes? Or I may just work on those I have installed on my main system, as those are the ones of packages that I use. Ok, I have these - notice the dates, most are recent: Aug 7 11:21 /usr/share/doc/packages/WindowMaker-applets/README.SuSE Oct 19 2016 /usr/share/doc/packages/WindowMaker/README.SuSE Apr 26 2006 /usr/share/doc/packages/docbook-dsssl-stylesheets/README.SuSE Oct 7 2016 /usr/share/doc/packages/docbook_3/README.SuSE May 11 2016 /usr/share/doc/packages/html-dtd/README.SuSE May 24 2004 /usr/share/doc/packages/i4l-base/README.SuSE Jun 28 2016 /usr/share/doc/packages/ifplugd/README.SuSE Sep 30 2016 /usr/share/doc/packages/isapnp/README.SuSE Jun 11 2016 /usr/share/doc/packages/ispell-spanish/README.SuSE Jun 27 2016 /usr/share/doc/packages/leafnode/README.SuSE Oct 7 2016 /usr/share/doc/packages/openjade/README.SuSE May 12 2016 /usr/share/doc/packages/sleuth/README.SuSE Apr 28 2015 /usr/share/doc/packages/spamassassin/README.SuSE May 10 2016 /usr/share/doc/packages/tkdiff/README.SuSE Oct 7 2016 /usr/share/doc/packages/xmlto/README.SuSE There are more files, for instance: /usr/share/YaST2/theme/SuSELinux /opt/kde3/share/apps/rekall/examples/mushroomDAT_en/SuSE-Novell-Logo.jpg /usr/java/jdk1.8.0_151/jre/lib/fontconfig.SuSE.10.bfc /usr/share/doc/packages/postfix/resto/SPAMASSASSIN+POSTFIX.SuSE /usr/share/X11/fvwm2/pixmaps/openSuSE.xpm And then there is SuSEfirewall2, but I doubt you want to touch that one :-) -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On Tue, 2017-11-14 at 13:49 +0100, Carlos E. R. wrote:
On 2017-11-14 13:27, Bruno Friedmann wrote:
On mardi, 14 novembre 2017 13.21:43 h CET martin@pluskal.org wrote:
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current.
That might be actually helpfull
M
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML).
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution.
Ok, I can do that. One bugzilla per file - is there a list of readmes? Or I may just work on those I have installed on my main system, as those are the ones of packages that I use.
All README.SuSE in the distro can be found by: wget http://download.opensuse.org/tumbleweed/repo/oss/ARCHIVES.gz zgrep -P "README.SuSE" ARCHIVES.gz | \ awk '{print $1": "$10}' | grep -v i586 | sort Cheers Dominique
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2017-11-14 at 13:57 +0100, Dominique Leuenberger / DimStar wrote:
On Tue, 2017-11-14 at 13:49 +0100, Carlos E. R. wrote:
On 2017-11-14 13:27, Bruno Friedmann wrote:
On mardi, 14 novembre 2017 13.21:43 h CET martin@pluskal.org wrote:
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote: > On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried > wrote:
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current.
That might be actually helpfull
M
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML).
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution.
Ok, I can do that. One bugzilla per file - is there a list of readmes? Or I may just work on those I have installed on my main system, as those are the ones of packages that I use.
All README.SuSE in the distro can be found by:
wget http://download.opensuse.org/tumbleweed/repo/oss/ARCHIVES.gz zgrep -P "README.SuSE" ARCHIVES.gz | \ awk '{print $1": "$10}' | grep -v i586 | sort
Thanks. I'll limit myself, for the moment at least, to those packages I have installed and thus I have more knowledge. Quick question. How do I find the maintainer to add in the Bugzilla? I think there was an OBS command for it, but I can't locate what the procedure was. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloMwbkACgkQtTMYHG2NR9WtxgCfZ9zYCS+sVTOX1oU3ZRAwyKKJ 5fEAnR3gWr7z/M1EBj48lWAlMvo0YQ6p =l2NN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 16/11/17 09:07, Carlos E. R. wrote:
On Tuesday, 2017-11-14 at 13:57 +0100, Dominique Leuenberger / DimStar wrote:
On Tue, 2017-11-14 at 13:49 +0100, Carlos E. R. wrote:
On 2017-11-14 13:27, Bruno Friedmann wrote:
On mardi, 14 novembre 2017 13.21:43 h CET martin@pluskal.org wrote:
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote: > On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote: >> On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried >> wrote:
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current.
That might be actually helpfull
M
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML).
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution.
Ok, I can do that. One bugzilla per file - is there a list of readmes? Or I may just work on those I have installed on my main system, as those are the ones of packages that I use.
All README.SuSE in the distro can be found by:
wget http://download.opensuse.org/tumbleweed/repo/oss/ARCHIVES.gz zgrep -P "README.SuSE" ARCHIVES.gz | \ awk '{print $1": "$10}' | grep -v i586 | sort
Thanks. I'll limit myself, for the moment at least, to those packages I have installed and thus I have more knowledge.
Quick question.
How do I find the maintainer to add in the Bugzilla? I think there was an OBS command for it, but I can't locate what the procedure was.
with osc bugowner or if you use the create bugreport button in obs it will prefill some additional info as well simon@tek-top ~ ➤ osc bugowner efl Defined in project: X11:Enlightenment:Factory bugowner of efl : simotek Then if you need the email address osc whois which will give you the email address registered in bugzilla which is possibly different to the one they use on mailing lists etc. simon@tek-top ~ ➤ oosc whois simotek simotek: "Simon Lees" <simonf.lees@suse.com> -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
16.11.2017 03:26, Simon Lees пишет:
Quick question.
How do I find the maintainer to add in the Bugzilla? I think there was an OBS command for it, but I can't locate what the procedure was.
with osc bugowner or if you use the create bugreport button in obs it will prefill some additional info as well
simon@tek-top ~ ➤ osc bugowner efl Defined in project: X11:Enlightenment:Factory bugowner of efl : simotek
Then if you need the email address osc whois which will give you the email address registered in bugzilla which is possibly different to the one they use on mailing lists etc.
simon@tek-top ~ ➤ oosc whois simotek simotek: "Simon Lees" <simonf.lees@suse.com>
bor@bor-Latitude-E5450:~$ osc bugowner -e efl Defined in project: X11:Enlightenment:Factory bugowner of efl : simonf.lees@suse.com bor@bor-Latitude-E5450:~$ Or do you imply that "bugowner -e" can give different result from "whois"?
On 16/11/17 13:52, Andrei Borzenkov wrote:
16.11.2017 03:26, Simon Lees пишет:
Quick question.
How do I find the maintainer to add in the Bugzilla? I think there was an OBS command for it, but I can't locate what the procedure was.
with osc bugowner or if you use the create bugreport button in obs it will prefill some additional info as well
simon@tek-top ~ ➤ osc bugowner efl Defined in project: X11:Enlightenment:Factory bugowner of efl : simotek
Then if you need the email address osc whois which will give you the email address registered in bugzilla which is possibly different to the one they use on mailing lists etc.
simon@tek-top ~ ➤ oosc whois simotek simotek: "Simon Lees" <simonf.lees@suse.com>
bor@bor-Latitude-E5450:~$ osc bugowner -e efl Defined in project: X11:Enlightenment:Factory bugowner of efl : simonf.lees@suse.com
bor@bor-Latitude-E5450:~$
Or do you imply that "bugowner -e" can give different result from "whois"?
Nope I just didn't know it existed :-) -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-11-16 at 10:56 +1030, Simon Lees wrote:
On 16/11/17 09:07, Carlos E. R. wrote:
On Tuesday, 2017-11-14 at 13:57 +0100, Dominique Leuenberger / DimStar wrote:
...
Quick question.
How do I find the maintainer to add in the Bugzilla? I think there was an OBS command for it, but I can't locate what the procedure was.
with osc bugowner or if you use the create bugreport button in obs it will prefill some additional info as well
simon@tek-top ~ ➤ osc bugowner efl Defined in project: X11:Enlightenment:Factory bugowner of efl : simotek
Then if you need the email address osc whois which will give you the email address registered in bugzilla which is possibly different to the one they use on mailing lists etc.
simon@tek-top ~ ➤ oosc whois simotek simotek: "Simon Lees" <simonf.lees@suse.com>
Thanks, it works. I'll try also find the bugreport button, but some times it doesn't exist. For instance, here: <https://build.opensuse.org/package/show/openSUSE%3AFactory/spamassassin> I don't see a "report" or "bugzilla" button. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloNloEACgkQtTMYHG2NR9W7YgCgmMMpaow+Hzh+QWt1yXeaf2rY 7RgAmQGsQCe32brLfCgX7UCY+8K1u6pr =aRsI -----END PGP SIGNATURE-----
On jeudi, 16 novembre 2017 14.45:37 h CET Carlos E. R. wrote:
On Thursday, 2017-11-16 at 10:56 +1030, Simon Lees wrote:
On 16/11/17 09:07, Carlos E. R. wrote:
On Tuesday, 2017-11-14 at 13:57 +0100, Dominique Leuenberger / DimStar
wrote: ...
Quick question.
How do I find the maintainer to add in the Bugzilla? I think there was an OBS command for it, but I can't locate what the procedure was.
with osc bugowner or if you use the create bugreport button in obs it will prefill some additional info as well
simon@tek-top ~ ➤ osc bugowner efl Defined in project: X11:Enlightenment:Factory
bugowner of efl : simotek
Then if you need the email address osc whois which will give you the email address registered in bugzilla which is possibly different to the one they use on mailing lists etc.
simon@tek-top ~ ➤ oosc whois simotek simotek: "Simon Lees" <simonf.lees@suse.com>
Thanks, it works. I'll try also find the bugreport button, but some times it doesn't exist.
For instance, here:
<https://build.opensuse.org/package/show/openSUSE%3AFactory/spamassassin>
I don't see a "report" or "bugzilla" button.
Click developped at which drive you to https://build.opensuse.org/package/show/devel:languages:perl/spamassassin Et voilà the submit bug report button is there. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Nov 16, 2017 at 10:59 AM, Bruno Friedmann <bruno@ioda-net.ch> wrote:
On jeudi, 16 novembre 2017 14.45:37 h CET Carlos E. R. wrote:
Thanks, it works. I'll try also find the bugreport button, but some times it doesn't exist.
For instance, here:
<https://build.opensuse.org/package/show/openSUSE%3AFactory/spamassassin>
I don't see a "report" or "bugzilla" button.
Click developped at which drive you to https://build.opensuse.org/package/show/devel:languages:perl/spamassassin
Et voilà the submit bug report button is there.
Carlos, You can get from your link to Bruno's link by clicking "developed at" in the upper right corner. I believe you always get the "report bug" button on the "development" project, but not on the "factory" project. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2017-11-16 at 13:13 -0500, Greg Freemyer wrote:
On Thu, Nov 16, 2017 at 10:59 AM, Bruno Friedmann <bruno@ioda-net.ch> wrote:
On jeudi, 16 novembre 2017 14.45:37 h CET Carlos E. R. wrote:
Thanks, it works. I'll try also find the bugreport button, but some times it doesn't exist.
For instance, here:
<https://build.opensuse.org/package/show/openSUSE%3AFactory/spamassassin>
I don't see a "report" or "bugzilla" button.
Click developped at which drive you to https://build.opensuse.org/package/show/devel:languages:perl/spamassassin
Et voilà the submit bug report button is there.
Carlos, You can get from your link to Bruno's link by clicking "developed at" in the upper right corner.
I believe you always get the "report bug" button on the "development" project, but not on the "factory" project.
Ah! Interesting. The component gets set to "3rd party", described as "For Software in any repositories of the OBS, except the official openSUSE distributions". I don't know if I want that, because I'm reporting for TW. The assignee can be seen by clicking on "Show Advanced Fields", I just discovered this. - -- Cheers, Carlos E. R. (from openSUSE 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloN2k8ACgkQtTMYHG2NR9WOXQCgkrjFc/fITG/1yU2zY5Jr0sJF BJsAoJPNa/E5sD/KCj0hhOgHMCO0GYn1 =NXlT -----END PGP SIGNATURE-----
On 14/11/17 23:19, Carlos E. R. wrote:
On 2017-11-14 13:27, Bruno Friedmann wrote:
On mardi, 14 novembre 2017 13.21:43 h CET martin@pluskal.org wrote:
On Tue, 2017-11-14 at 12:59 +0100, Carlos E. R. wrote:
On 2017-11-14 11:19, martin@pluskal.org wrote:
On Mon, 2017-11-13 at 23:38 +0100, Carlos E. R. wrote:
On Monday, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
I can help, however, by reading such readmes on the packages I know enough about and then telling someone if I consider it obsolete or current.
That might be actually helpfull
M
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML).
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution.
Ok, I can do that. One bugzilla per file - is there a list of readmes? Or I may just work on those I have installed on my main system, as those are the ones of packages that I use.
Yep one bug per file, they will all have different maintainers. Start with the ones you know, short of installing every package I don't think there is a easy way to know unless we add a rpmlint warning / error for them.
Ok, I have these - notice the dates, most are recent:
Aug 7 11:21 /usr/share/doc/packages/WindowMaker-applets/README.SuSE Oct 19 2016 /usr/share/doc/packages/WindowMaker/README.SuSE Apr 26 2006 /usr/share/doc/packages/docbook-dsssl-stylesheets/README.SuSE Oct 7 2016 /usr/share/doc/packages/docbook_3/README.SuSE May 11 2016 /usr/share/doc/packages/html-dtd/README.SuSE May 24 2004 /usr/share/doc/packages/i4l-base/README.SuSE Jun 28 2016 /usr/share/doc/packages/ifplugd/README.SuSE Sep 30 2016 /usr/share/doc/packages/isapnp/README.SuSE Jun 11 2016 /usr/share/doc/packages/ispell-spanish/README.SuSE Jun 27 2016 /usr/share/doc/packages/leafnode/README.SuSE Oct 7 2016 /usr/share/doc/packages/openjade/README.SuSE May 12 2016 /usr/share/doc/packages/sleuth/README.SuSE Apr 28 2015 /usr/share/doc/packages/spamassassin/README.SuSE May 10 2016 /usr/share/doc/packages/tkdiff/README.SuSE Oct 7 2016 /usr/share/doc/packages/xmlto/README.SuSE
There are more files, for instance:
/usr/share/YaST2/theme/SuSELinux /opt/kde3/share/apps/rekall/examples/mushroomDAT_en/SuSE-Novell-Logo.jpg /usr/java/jdk1.8.0_151/jre/lib/fontconfig.SuSE.10.bfc /usr/share/doc/packages/postfix/resto/SPAMASSASSIN+POSTFIX.SuSE /usr/share/X11/fvwm2/pixmaps/openSuSE.xpm
And then there is SuSEfirewall2, but I doubt you want to touch that one :-)
Its going away oneday anyway :-) -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Tuesday, 14 November 2017 23:14 Simon Lees wrote:
On 14/11/17 23:19, Carlos E. R. wrote:
And then there is SuSEfirewall2, but I doubt you want to touch that one :-)
Its going away oneday anyway :-)
I thought it is planned to be replaced by firewalld as soon as in 15.0. Or is it only SLE15? Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Michal Kubecek [15.11.2017 07:28]:
On Tuesday, 14 November 2017 23:14 Simon Lees wrote:
On 14/11/17 23:19, Carlos E. R. wrote:
And then there is SuSEfirewall2, but I doubt you want to touch that one :-)
Its going away oneday anyway :-)
I thought it is planned to be replaced by firewalld as soon as in 15.0. Or is it only SLE15?
Michal Kubeček
Since Leap 15 will be based on SLE 15, it should be changed in both. However, I guess that for compatibility reasons SuSEfirewall2 will still be delivered, but not installed by default on new installations. Unless someone found a foolproof way to convert the configs, there should not be a replacement "by force" when upgrading ;) Just my 2¢ Werner --
On 14.11.2017 13:27, Bruno Friedmann wrote:
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML).
Well, I'll then just drop ifplugd when the bug-rate goes higher than "one bug per decade" ;-) Which of course will also solve the issue of wrongly named and outdated documentation.
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution.
Actually in this case, there wold need to be someone who actually uses ifplugd. Ok, there must be *one* user at least (because of the "invalid buffer size" report), but AFAICT from the bug report, he is not using it in the way README.S[uU]SE describes anyway. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 14.11.2017 um 15:07 schrieb Stefan Seyfried:
On 14.11.2017 13:27, Bruno Friedmann wrote:
For each package containing a such obsolete content, just open a bug so maintainer get warned directly (I guess some of them are no more on this ML). Well, I'll then just drop ifplugd when the bug-rate goes higher than "one bug per decade" ;-)
Which of course will also solve the issue of wrongly named and outdated documentation.
Adding valuable and refreshed content will increase the chance to get a fix. Help in doing and fixing shit is always appreciate in terms of contribution. Actually in this case, there wold need to be someone who actually uses ifplugd. Ok, there must be *one* user at least (because of the "invalid buffer size" report), but AFAICT from the bug report, he is not using it in the way README.S[uU]SE describes anyway.
ifplugd is used by wicked if you set "Activate Device" to "On cable connect" in YaST. Currently ifplugd is installed by the enhanced_base pattern. Maybe the wicked package should have "Requires: ifplugd", or at least a "Recommends: ifplugd". Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 15.11.2017 10:39, Herbert Graeber wrote:
ifplugd is used by wicked if you set "Activate Device" to "On cable connect" in YaST. Currently ifplugd is installed by the enhanced_base
This is totally crazy. Like almost everything in wicked. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2017-11-15 12:43, Stefan Seyfried wrote:
On 15.11.2017 10:39, Herbert Graeber wrote:
ifplugd is used by wicked if you set "Activate Device" to "On cable connect" in YaST. Currently ifplugd is installed by the enhanced_base
This is totally crazy. Like almost everything in wicked.
It's in the name, isn't it? ;-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 15 November 2017 12:43 Stefan Seyfried wrote:
On 15.11.2017 10:39, Herbert Graeber wrote:
ifplugd is used by wicked if you set "Activate Device" to "On cable connect" in YaST. Currently ifplugd is installed by the enhanced_base
This is totally crazy. Like almost everything in wicked.
AFAIK this is not really an invention of wicked. See ifcfg.template on any pre-wicked openSUSE/SLE, we had STARTMODE="ifplugd" option long before wicked was introduced. So wicked rather preserves the feature. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 15.11.2017 13:17, Michal Kubecek wrote:
On Wednesday, 15 November 2017 12:43 Stefan Seyfried wrote:
On 15.11.2017 10:39, Herbert Graeber wrote:
ifplugd is used by wicked if you set "Activate Device" to "On cable connect" in YaST. Currently ifplugd is installed by the enhanced_base
This is totally crazy. Like almost everything in wicked.
AFAIK this is not really an invention of wicked. See ifcfg.template on any pre-wicked openSUSE/SLE, we had STARTMODE="ifplugd" option long before wicked was introduced. So wicked rather preserves the feature.
Yes. But in the "good old days" sysconfig ifcfg-scripts were exactly this: bash scripts. They basically needed ifplugd to do stuff like "cable hotplug detection". Wicked, OTOH is compiled (C or C++?) code which could implement the ifplugd functionality easily in the wicked daemons which are running anyway. Just like NetworkManager is doing since its beginning. Resorting to starting an extra daemon, its code being more than 10 years unmaintained, to handle cable hotplug is an -- how do I write it politely -- ... "strange" design decision. But then the whole wicked invention was a strange design decision anyway and -- as Jan has already mentioned -- it's at least aptly named. BTW: in the last 10 years, the kernel and the network card drivers have moved on quite a bit, so even kiwi which apparently uses "ifplugstatus" from the ifplugd package could just check /sys/class/net/$interface/carrier. I'll file a drop request for Factory/ifplugd now. I am not going to maintain it (and help perpetuate this insanity) any longer. Users who really need this functionality in a separate daemon (I use it myself on systemd-less embedded systems) can just use busybox' ifplugd implementation, which works well. So if nobody takes maintainership of Base:System/ifplugd, it'll be history soon. Have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday, 15 November 2017 14:45 Stefan Seyfried wrote:
But in the "good old days" sysconfig ifcfg-scripts were exactly this: bash scripts. They basically needed ifplugd to do stuff like "cable hotplug detection". Wicked, OTOH is compiled (C or C++?) code which could implement the ifplugd functionality easily in the wicked daemons which are running anyway. Just like NetworkManager is doing since its beginning. Resorting to starting an extra daemon, its code being more than 10 years unmaintained, to handle cable hotplug is an -- how do I write it politely -- ... "strange" design decision.
I fully agree that it would make more sense if wicked did implement the functionality itself. After all, it doesn't run ip or ethtool either and talks to the kernel instead. In my experience, wicked maintainers/developers are reasonable people who can be talked to. (Which is part of why, while I'm still not convinced having wicked as replacement of ifup/ifdown rather than alternative was the right decision, I still trust wicked more than systemd-networkd.) So I believe if you tell them that you are going to get rid of ifplugd and suggest to implement the functionality in wicked, there is a good chance they will agree. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Nov 15, 2017 at 4:55 PM, Michal Kubecek <mkubecek@suse.cz> wrote:
On Wednesday, 15 November 2017 14:45 Stefan Seyfried wrote:
But in the "good old days" sysconfig ifcfg-scripts were exactly this: bash scripts. They basically needed ifplugd to do stuff like "cable hotplug detection". Wicked, OTOH is compiled (C or C++?) code which could implement the ifplugd functionality easily in the wicked daemons which are running anyway. Just like NetworkManager is doing since its beginning. Resorting to starting an extra daemon, its code being more than 10 years unmaintained, to handle cable hotplug is an -- how do I write it politely -- ... "strange" design decision.
I fully agree that it would make more sense if wicked did implement the functionality itself. After all, it doesn't run ip or ethtool either and talks to the kernel instead.
E-h-h ... could someone show where wicked is using ifplugd? To my best knowledge nanny is responsible for monitoring interfaces for carrier and configuring interfaces. And it does not rely on ifplugd. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 15.11.2017 um 15:11 schrieb Andrei Borzenkov:
On Wed, Nov 15, 2017 at 4:55 PM, Michal Kubecek <mkubecek@suse.cz> wrote:
On Wednesday, 15 November 2017 14:45 Stefan Seyfried wrote:
But in the "good old days" sysconfig ifcfg-scripts were exactly this: bash scripts. They basically needed ifplugd to do stuff like "cable hotplug detection". Wicked, OTOH is compiled (C or C++?) code which could implement the ifplugd functionality easily in the wicked daemons which are running anyway. Just like NetworkManager is doing since its beginning. Resorting to starting an extra daemon, its code being more than 10 years unmaintained, to handle cable hotplug is an -- how do I write it politely -- ... "strange" design decision. I fully agree that it would make more sense if wicked did implement the functionality itself. After all, it doesn't run ip or ethtool either and talks to the kernel instead.
E-h-h ... could someone show where wicked is using ifplugd? To my best knowledge nanny is responsible for monitoring interfaces for carrier and configuring interfaces. And it does not rely on ifplugd. I have take a look in the sources and I erred. Wicked does not use ifplugd. So it can be dropped without losing functionality.
Sorry for being up a blind alley... Herbert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2017-11-14 12:59, Carlos E. R. wrote:
Thanks for considering, and have a lot of fun... :-)
I would suggest to not do automatic renaming, but manual renaming after checking that the contents are (at least apparently) correct.
1) Why do you assume its done automatically
Because the thread tittle has the word "Bulk".
Bulk means mass, not automation. (Though automation is often used for mass updates.) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2017-11-13 at 22:36 +0100, Stefan Seyfried wrote:
Hi all,
Dominique is cleaning up packages and renaming "README.SuSE" files to "README.SUSE".
While this is of course warrented in principle, there is one case to consider. If the README.SuSE is hugely outdated, then the wrong spelling at least suggest that it is not new ;-)
Neither is the correct spelling of SUSE being SUSE (and not SuSE) anything new.. This dates back to 2004; giving maintainers 13 years to clean up the naming of the README.SuSE -> README.SUSE should be really enough. If my renaming of the file does not serve anything more than maintainers finally waiking up and validating the content of that file, that's still a good win. As it means it's something maintainers neglected for the last 13 years :) Cheers Dominique
On Mon, Nov 13, Stefan Seyfried wrote:
Looking at README.SuSE (which comes from the upstream tarball), I am not even able to judge if this might actually work at all with todays networking mess that's called wicked. So I'm not sure if it is a good idea to suggest this file is relatively current by using the "new" spelling, when it definitely is not.
So, as good package maintainer, you should either remove that file from the package list or add a hint to the README, that it could be outdated. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & CaaSP SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (13)
-
Andrei Borzenkov -
Bruno Friedmann -
Carlos E. R. -
Dominique Leuenberger / DimStar -
Greg Freemyer -
Herbert Graeber -
Jan Engelhardt -
martin＠pluskal.org -
Michal Kubecek -
Simon Lees -
Stefan Seyfried -
Thorsten Kukuk -
Werner Flamme