-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/24/2015 11:50 AM, denisart benjamin2 wrote:

Le 24/01/2015 17:48, Stefan Seyfried a écrit :

...

Hi,

...

I try to clean up a little our distribution, because some packages are unmaintained for a while or they just use depreciated protocols, whatever. But Like DimStar told me, I should ask others maintainers opinions about it. So I made a list in two parts, a first with obsolete packages and their possible replacements, and a second with packages which could be simply removed. bridge-utils > systemd-networkd

Am 24.01.2015 um 17:17 schrieb denisart benjamin2: this is a joke, right?

...

buffer What is wrong with buffer? Are there unhandled open bugreports? If not, there are two possible reasons: a) nobody uses it b) it has no problem

For buffer, it's b) (I use it). And that no maintainer needed to touch the package for over 3 years just shows that the code is apparenty well written.

...

I think the charge of work is very heavy and it would be fine to concentrate our efforts. For bridge-utils, some kind of joke. I noticed it and forget to look at possile alternatives. I wrote systemd-networkd to look at networkd functions later.

Although the bridge-utils topic appears to have put to rest, FYI, I quick Google search produced: The service is available with systemd >= 210. You will want to enable and start the systemd-networkd.service on the host and container. For debugging purposes, it is strongly advised to install the bridge-utils, net-tools and iproute2 packages. This is from the Arch Linux wiki. I think this clarifies that the idea of removing bridge-utils is not in the best of our interest. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJUw+8pAAoJEE4FgL32d2UkwVoH/2X99t4zVVAj42Fc9pU7pbz2 gWsikUKY6TxaPG3B/jamFKqjbtkq5ORAXYRFLfllmK+YvQMHQbJfTGIN+ooJByLP hPiYCQkiXuAR66TlfN1jGtOftNgyoKyIBur8HCmoRjGit/2M1q+kKWAv413HkKqE 6aRskW9EU5v6/CjCnHivGX/5qtf91OUU2CFbYfuOQXEarORCtETYsj8WFPeSfaw3 RwgZOWcqKMaAaJqacmONAOJ8EDLH1uWrGdyrL+E1pBWzfc2fe4s1TArllGOSzJCq v7HiUl8RBT91MvoTLsl4gMk61kmjkpSU4VM8YeCZMUf+3rJUEZSduuEW9XOI4CY= =Zbvj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Saturday 2015-01-24 17:48, Stefan Seyfried wrote:

Am 24.01.2015 um 17:17 schrieb denisart benjamin2:

...

I try to clean up a little our distribution, because some packages are unmaintained for a while or they just use depreciated protocols, whatever. But Like DimStar told me, I should ask others maintainers opinions about it. So I made a list in two parts, a first with obsolete packages and their possible replacements, and a second with packages which could be simply removed.

...

bridge-utils > systemd-networkd

this is a joke, right?

Yes, that was a joke. The correct line is: bridge-utils -> iproute (`man 8 bridge` for details)

What is wrong with buffer? For buffer, [...] (I use it).

May I inquire what you use it for? Tape drives are quite rare these days. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Sunday 2015-01-25 14:15, Stefan Seyfried wrote:

Am 24.01.2015 um 21:33 schrieb Jan Engelhardt:

...

Yes, that was a joke. The correct line is:

bridge-utils -> iproute

(`man 8 bridge` for details)

Hey, even Linus said that iproute sucks bigtime (userinterface wise) and I have to agree with him.

It remains wishful thinking. As long as no one is willing to build the extra parser for old command line recognition - and up to now, there has been verifiably no one -, nothing will happen. Efforts - like the nft-backed iptables - are few and far between.

...

May I inquire what you use it for? Tape drives are quite rare these days.

progress information during blockdevice-copies with dd for example :)

dd if=/dev/mapper/foo bs=256k | buffer -z 256k | netcat desthost 1234

But I agree, mbuffer could be used for this, too, but with different options etc.

I think you might be more interested in pv(1). Because that's meant to be used primarily for progress information, and not tickling out some status information out of a tape program where the user has to mess with buffer sizes (because they don't[1]). Speaking of which: socat. [1] Like those broken SO_SNDBUF=8192 recommendations for smb.conf - they just drove up the overhead. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Le 24/01/2015 18:18, Marcus Meissner a écrit :

On Sat, Jan 24, 2015 at 05:17:55PM +0100, denisart benjamin2 wrote:

...

Hello everyone.

I try to clean up a little our distribution, because some packages are unmaintained for a while or they just use depreciated protocols, whatever. But Like DimStar told me, I should ask others maintainers opinions about it. So I made a list in two parts, a first with obsolete packages and their possible replacements, and a second with packages which could be simply removed.

camsource > cheese As we discussed in your drop request, cheese is a UI tool.

camsource is a quite complex commandline / webcam webserver tool, it has an entirely different usage pattern.

...

freetype > freetype2 We can drop freetype if the last user is gone or converted, (currently: gltt, libLASi, mupdf, openttd, font-specimen, tuxpaint, texlive, VFlib3)

...

##### compat-openssl097g For this package I just filed a drop request. Had no idea this unsecure thing was still there.

...

a2ps This might probably still be used by people, even if enscript offers similar functionality.

CIao, Marcus For a2ps, I found an interesting alternative. Unfortunately, I can't remember what. For camsource, I just didn't delete it from the list, don't worry :). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

...

a2ps

This might probably still be used by people, even if enscript offers similar functionality.

Is there actually any problem with a2ps? I wouldn't love to rewrite some toolchains just because somebody thinks it's dated. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/24/2015 01:55 PM, Shawn W Dunn wrote:

On Saturday, January 24, 2015 06:43:17 PM Ralf Lang wrote:

...

...

...

a2ps

This might probably still be used by people, even if enscript offers similar functionality. Is there actually any problem with a2ps? I wouldn't love to rewrite some toolchains just because somebody thinks it's dated.

I don't think anybody is suggesting that these packages are dropped outright. Just that they aren't included in openSUSE:Factory, they will still be there, in their respective development repos. Honestly, I think this is an effort that needs more focus, to reduce the overall workload on shipping a good Factory/Tumbleweed Product. You can't just keep *everything* in Factory in perpetuity, because ONE user might need it.

Why not? If a package in question has no security issues does not cause continuous headaches why not keep it? What is wrong with code that works well and has been used for a long time? Don't get me wrong, I like clean up efforts. But throwing stuff out just because it is old is from my perspective throwing out the baby with the bath water. Later, Robert - -- Robert Schweikert MAY THE SOURCE BE WITH YOU Public Cloud Architect LINUX rjschwei@suse.com IRC: robjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJUw/DwAAoJEE4FgL32d2UkfD4H/jW5YGHnC2H+lIvxUbDSbidO QCfUL2Tw5owdegj2c5kXMfI94MuasvCqyS4VADy79DBbft0Gd27xeoA/aWsVXTUy WFdyOA6f/wPn/kvAzuLE8S7i6dozd6fGnJIIndBMnVdbDcvMGwYtX5wCSu6T8+o+ 8/oIccjQR3LZnykC+QXoFOyhj3dxrKo4itfXax3NqhViciuOwxb7wLLAErcm30HD sESLrwtMqQX9/5eqEt6JcwlWB0oIQU5kaSDmn8LIu1fTMcK+UfeqPbj8jMUNWWDv GX2jisERtRCU09TLdr19pNp6hnAXOSpunS0kbLq0cVoT9bBqKnUvfhKcPpguwOo= =Mnrh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 25.01.2015 01:50, Archie Cobbs wrote:

On Sat, Jan 24, 2015 at 1:22 PM, Robert Schweikert wrote:

...

Why not? If a package in question has no security issues does not cause continuous headaches why not keep it? What is wrong with code that works well and has been used for a long time?

Don't get me wrong, I like clean up efforts. But throwing stuff out just because it is old is from my perspective throwing out the baby with the bath water.

I agree completely. I use a2ps frequently to print stuff.

Unless there is a problem, it seems like this would just be punishing a2ps for being reliable, bug-free code that lasts a long time. Isn't that what we want in software?

I'm not even sure where the impression came from it's no longer updated - it saw an update in august 2014. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 24.01.2015 19:55, Shawn W Dunn wrote:

On Saturday, January 24, 2015 06:43:17 PM Ralf Lang wrote:

...

...

...

a2ps

This might probably still be used by people, even if enscript offers similar functionality. Is there actually any problem with a2ps? I wouldn't love to rewrite some toolchains just because somebody thinks it's dated.

I don't think anybody is suggesting that these packages are dropped outright. Just that they aren't included in openSUSE:Factory, they will still be there, in their respective development repos. Honestly, I think this is an effort that needs more focus, to reduce the overall workload on shipping a good Factory/Tumbleweed Product. You can't just keep *everything* in Factory in perpetuity, because ONE user might need it.

(No Ralf, I'm not picking on you, I'm speaking in general)

No offense taken, but what benefit is it to drop a package which is actually used, has no issues and just works? Development repos are just not the same. They don't end up in the final product. They don't receive the same automated and human QA from "The address in the license file is no longer valid" to "please use this compiler setting from now on, because it makes the whole distribution more secure". All this leads to is a series of new submit requests and a lot of work. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

El 26/01/15 a las 06:11, Olaf Hering escribió:

On Sat, Jan 24, denisart benjamin2 wrote:

...

compat compat-openssl097g compat-readline4

Do these packages cause any issues? Instead of dropping them, add more libs to them so that old binaries continue to work.

Olaf

keeping old versions of openssl around is a terrible idea, in fact keeping anything less than $stable openssl around is. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 26.01.2015 14:46, Yamaban wrote:

On Mon, 26 Jan 2015 14:13, Cristian Rodríguez wrote:

...

El 26/01/15 a las 06:11, Olaf Hering escribió:

...

On Sat, Jan 24, denisart benjamin2 wrote:

...

compat compat-openssl097g compat-readline4

Do these packages cause any issues? Instead of dropping them, add more libs to them so that old binaries continue to work.

Olaf

keeping old versions of openssl around is a terrible idea, in fact keeping anything less than $stable openssl around is.

This is NOT the old version of openSSL, but a lib that takes the calls to openSSL in the old (0.97) format and "translates" them into calls to the actual $stable openSSL version. Please look at the code.

Can you please point to that calls mapping code? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org