Bug 50862 - error: %preun(strongswan-5.9.14-alt1.x86_64) scriptlet failed, exit status 1
Summary: error: %preun(strongswan-5.9.14-alt1.x86_64) scriptlet failed, exit status 1
Status: CLOSED DUPLICATE of bug 50673
Alias: None
Product: Branch p11
Classification: Unclassified
Component: strongswan (show other bugs)
Version: unspecified
Hardware: x86_64 Linux
: P5 normal
Assignee: qa-team@altlinux.org
QA Contact: qa-p11@altlinux.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-08 13:46 MSK by mrsclick
Modified: 2024-07-08 15:49 MSK (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mrsclick 2024-07-08 13:46:50 MSK
After update to ALT Workstation K 11.0ALPHA start getting the warning: 

W: There are multiple versions of "strongswan" in your system. 
This package won't be cleanly updated, unless you leave only one version. To leave multiple versions installed, you may remove that warning by setting the following option in your configuration file: RPM::Allow-Duplicated { "^strongswan$"; }; To disable these warnings completely set: RPM::Allow-Duplicated-Warning "false"; W: You may want to run apt-get update to correct these problems 

I just checked and ensure that system has two different versions of strongswan package: 

# rpm -qa | grep strongswan 
strongswan-5.9.14-alt2.x86_64 
strongswan-5.9.14-alt1.x86_64 

So, I tried to remove outdated version (alt1) and got some errors: 

#rpm -e strongswan-5.9.14-alt1.x86_64 
preun_service: usage: preun_service <service> error: 
%preun(strongswan-5.9.14-alt1.x86_64) scriptlet failed, exit status 1 
error: strongswan-5.9.14-alt1.x86_64: erase failed 

It is seems like while update process the replace an old version of strongswan package was failed and then system has two version of it. So, guess problem is in package remove scriptlet.
Comment 1 Alexander Makeenkov 2024-07-08 14:52:58 MSK
(Ответ для mrsclick на комментарий #0)
> W: There are multiple versions of "strongswan" in your system. 

# apt-get dedup


(Ответ для mrsclick на комментарий #0)
> So, guess problem is in package remove scriptlet.

https://bugzilla.altlinux.org/50673

*** This bug has been marked as a duplicate of bug 50673 ***
Comment 2 mrsclick 2024-07-08 15:19:01 MSK
I did it last friday and yes, it solves the problem temporary (as I thought then), but today, when again try to update (run apt-get update) the system, this problem is turn back cause in true the package was not been removed.

Cause apt-get dedup also finished with an same error.

The following packages will be REMOVED:
  strongswan#5.9.14-alt1:sisyphus+351092.100.1.1@1718639554
0 upgraded, 0 newly installed, 1 removed and 0 not upgraded.
Need to get 0B of archives.
After unpacking 4952kB disk space will be freed.
Do you want to continue? [Y/n] Y
Committing changes...
Preparing...                                                                                                                    #################################################################################################### [100%]
preun_service: usage: preun_service <service>
error: %preun(strongswan-5.9.14-alt1.x86_64) scriptlet failed, exit status 1
error: strongswan-5.9.14-alt1.x86_64: erase failed
E: Some errors occurred while running transaction

And at the end second version (duplicate) still installed.

# rpm -qa | grep strongswan
strongswan-5.9.14-alt2.x86_64
strongswan-5.9.14-alt1.x86_64
Comment 3 mrsclick 2024-07-08 15:39:10 MSK
Пока что удалил через --noscripts, как описано здесь https://bugzilla.altlinux.org/50673, если снова появится проблема сообщу.
Comment 4 mrsclick 2024-07-08 15:42:07 MSK
Однако это явно баг потому что от пользователя требуется неявные действия, он должен быть осведомлён о том как ему стоит поступать в этом случае. Т.е. воспроизводимость проблемы очевидна, проблема критичная так как затрагивает сетевой стек и влияет на работу apt-get, но бага почему то (имеется в виду 50673) была закрыта на основании того что коллективно вместе с ОП\ТС таки смогли выйти из ситуации. Но проблема как была так и осталась, поэтому появился Bug 50862 репорт.
Comment 5 Alexander Makeenkov 2024-07-08 15:49:41 MSK
(Ответ для mrsclick на комментарий #4)
> бага почему то (имеется в виду 50673) была закрыта

Можете переоткрыть её и написать туда.