Re: [opensuse-factory] xchat -> hexchat
On 2016-03-31T11:39:26, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
- Replace xchat by hexchat everywhere
Uh. So with this zypper dup round, xchat suddenly was silently dropped; hexchat was not automatically pulled in as a replacement/upgrade; hexchat ignores the existing xchat configuration files. Well done! Regards, Lars -- Architect Storage/HA SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Lars Marowsky-Bree píše v Út 05. 04. 2016 v 13:58 +0200:
On 2016-03-31T11:39:26, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
- Replace xchat by hexchat everywhere
Uh. So with this zypper dup round, xchat suddenly was silently dropped; hexchat was not automatically pulled in as a replacement/upgrade; hexchat ignores the existing xchat configuration files.
Xchat is unfortunately not developed anymore so we replaced it the same way like on sle12. Maybe we could add provides/obsoletes? But it should've been pulled in by the patterns. Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html Tom
On 2016-04-05T14:40:36, Tomas Chvatal <tchvatal@suse.cz> wrote:
hexchat was not automatically pulled in as a replacement/upgrade; hexchat ignores the existing xchat configuration files. Xchat is unfortunately not developed anymore so we replaced it the same way like on sle12.
The FATE for SLE 12 claims that it can "easily" re-use the existing configuration and logfiles, none of which happened here ... And I was very unhappy about a feature just being uninstalled silently on a zypper dup. I'd rather have kept the "not developed" version around until I made a conscious choice, or received some pop-up that I should update. But that's just me.
Maybe we could add provides/obsoletes? But it should've been pulled in by the patterns.
I had installed xchat not via the desktop patterns (which are way too large). So yes, the way to upgrade/replace packages definitely is via RPM requires.
Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html
That'd have been neat. And now too late. :-/ Regards, Lars -- Architect Storage/HA SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2016-04-05 at 14:40 +0200, Tomas Chvatal wrote:
Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html
You can't reliably touch configuration files in ~; there us no guarantee this is even on the same machine as the rpm is being installed. Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dominique Leuenberger / DimStar píše v Út 05. 04. 2016 v 14:47 +0200:
On Tue, 2016-04-05 at 14:40 +0200, Tomas Chvatal wrote:
Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html
You can't reliably touch configuration files in ~; there us no guarantee this is even on the same machine as the rpm is being installed.
Readme.MIGRATE to add? But we all know how many people read those? Tom
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 5.4.2016 14:51, Tomas Chvatal wrote:
Readme.MIGRATE to add? But we all know how many people read those?
At least when you use Yast for migration, it should now show messages coming with packages. Read more at https://lizards.opensuse.org/2016/02/25/highlights-of-development-sprint-15/ (Package notifications) HTH Lukas - -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux https://en.wikipedia.org/wiki/Scout_Promise#Czech_Republic http://www.scouting.org/Visitor/WhyScouting/ServingOthers.aspx -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlcDvUUACgkQVSqMdRCqTixVkwCffSdI8QChS9NSozYeYLnrZujf RTUAnjaMBKHFIfD3LisKrp7Klwwi/la4 =oz0i -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dominique Leuenberger / DimStar wrote:
On Tue, 2016-04-05 at 14:40 +0200, Tomas Chvatal wrote:
Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html
You can't reliably touch configuration files in ~; there us no guarantee this is even on the same machine as the rpm is being installed.
Exactly. The operations listed in the FAQ look like something hexchat could be trivially implement when started for the first time though. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dominique Leuenberger / DimStar <dimstar@opensuse.org> writes:
On Tue, 2016-04-05 at 14:40 +0200, Tomas Chvatal wrote:
Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html
You can't reliably touch configuration files in ~; there us no guarantee this is even on the same machine as the rpm is being installed.
It needs to be implemented in hexchat, to be done during the first run. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 05 avril 2016 à 14:40 +0200, Tomas Chvatal a écrit :
Lars Marowsky-Bree píše v Út 05. 04. 2016 v 13:58 +0200:
On 2016-03-31T11:39:26, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
- Replace xchat by hexchat everywhere
Uh. So with this zypper dup round, xchat suddenly was silently dropped; hexchat was not automatically pulled in as a replacement/upgrade; hexchat ignores the existing xchat configuration files.
Xchat is unfortunately not developed anymore so we replaced it the same way like on sle12.
Maybe we could add provides/obsoletes? But it should've been pulled in by the patterns.
Wrt configs what to do they should be almost 1:1 so we could handle it in %post? Something like following this page: http://hexchat.readthedocs.org/en/latest/faq.html
We'll have patches to handle that as part of SP2 (and next Leap). I guess the switch was a bit too soon. And no, the migration can't be done at package level, it needs to be done when hexchat is started for the first time (because it needs access to user data). -- Frederic Crozat Enterprise Desktop Release Manager SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Andreas Schwab -
Dominique Leuenberger / DimStar -
Frederic Crozat -
Lars Marowsky-Bree -
Ludwig Nussel -
Lukas Ocilka -
Tomas Chvatal