Hi, I am trying to install Leap 15.4. But during the installation of packages, I get messages like these: YaST2 Installation of package ca-certificates failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(ca-certificates-2+git20210309.21162a6-2.1.noarch) scriptlet failed, exit status 127 error: ca-certificates-2+git20210309.21162a6-2.1.noarch: install failed YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(python3-six-1.14.0-12.1.noarch) scriptlet failed, exit status 127 error: python3-six-1.14.0-12.1.noarch: install failed I click 'Ignore' every time, and then this message appears: YaST2 Warning Ignoring a package failure may result in a broken system. The system should be later verified by running the Software Management module. And the list of uninstallable packages goes on and on: python3-pip wireless-tools systemd-presets-common-SUSE sg3_utils netcfg login_defs klogd issue-generator cyrus-sasl systemd-presets-branding-openSUSE iputils ebtables device-mapper shadow kbd alsa-utils lockdev etc. I had the same problem when trying to install 15.3. I did manage to install TW, however. Does anybody have any idea what could be the problem here?
On 08.06.2022 17:19, Siard wrote:
Hi,
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package ca-certificates failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(ca-certificates-2+git20210309.21162a6-2.1.noarch) scriptlet failed, exit status 127 error: ca-certificates-2+git20210309.21162a6-2.1.noarch: install failed
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(python3-six-1.14.0-12.1.noarch) scriptlet failed, exit status 127 error: python3-six-1.14.0-12.1.noarch: install failed
I click 'Ignore' every time, and then this message appears:
YaST2 Warning Ignoring a package failure may result in a broken system. The system should be later verified by running the Software Management module.
And the list of uninstallable packages goes on and on:
python3-pip wireless-tools systemd-presets-common-SUSE sg3_utils netcfg login_defs klogd issue-generator cyrus-sasl systemd-presets-branding-openSUSE iputils ebtables device-mapper shadow kbd alsa-utils lockdev etc.
I had the same problem when trying to install 15.3. I did manage to install TW, however.
Does anybody have any idea what could be the problem here?
Start with describing how you perform installation.
Andrei Borzenkov wrote:
On 08.06.2022 17:19, Siard wrote:
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(python3-six-1.14.0-12.1.noarch) scriptlet failed, exit status 127 error: python3-six-1.14.0-12.1.noarch: install failed .... ....
And the list of uninstallable packages goes on and on:
python3-pip wireless-tools systemd-presets-common-SUSE sg3_utils .... ....
I had the same problem when trying to install 15.3. I did manage to install TW, however.
Does anybody have any idea what could be the problem here?
Start with describing how you perform installation.
I have had Debian as my main distro for a long time, but wanted to try openSUSE, maybe I'll switch to it. I made a bootable USB stick with the Network Image, booted and followed the instructions. I put openSUSE on /dev/sdb7, which is on a logical volume. Chose ext4 as file system, because Grub does not recognize a btrfs file system when it is on a logical volume. Judging from the error messages, it could be a permission problem??
On 2022-06-08 20:54, Siard wrote:
Andrei Borzenkov wrote:
On 08.06.2022 17:19, Siard wrote:
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(python3-six-1.14.0-12.1.noarch) scriptlet failed, exit status 127 error: python3-six-1.14.0-12.1.noarch: install failed .... ....
And the list of uninstallable packages goes on and on:
python3-pip wireless-tools systemd-presets-common-SUSE sg3_utils .... ....
I had the same problem when trying to install 15.3. I did manage to install TW, however.
Does anybody have any idea what could be the problem here?
Start with describing how you perform installation.
I have had Debian as my main distro for a long time, but wanted to try openSUSE, maybe I'll switch to it. I made a bootable USB stick with the Network Image, booted and followed the instructions. I put openSUSE on /dev/sdb7, which is on a logical volume. Chose ext4 as file system, because Grub does not recognize a btrfs file system when it is on a logical volume. Judging from the error messages, it could be a permission problem??
I assume you are formatting /dev/sdb7? -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
Carlos E. R.:
Siard:
Andrei Borzenkov:
Siard:
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied error: %prein(python3-six-1.14.0-12.1.noarch) scriptlet failed, exit status 127 error: python3-six-1.14.0-12.1.noarch: install failed .... ....
And the list of uninstallable packages goes on and on:
python3-pip wireless-tools systemd-presets-common-SUSE sg3_utils .... ....
I had the same problem when trying to install 15.3. I did manage to install TW, however.
Does anybody have any idea what could be the problem here?
Start with describing how you perform installation.
I have had Debian as my main distro for a long time, but wanted to try openSUSE, maybe I'll switch to it. I made a bootable USB stick with the Network Image, booted and followed the instructions. I put openSUSE on /dev/sdb7, which is on a logical volume. Chose ext4 as file system, because Grub does not recognize a btrfs file system when it is on a logical volume. Judging from the error messages, it could be a permission problem??
I assume you are formatting /dev/sdb7?
Yes, the installer offers to format it. This is a picture I took from the window named 'Edit /dev/sdb7': https://postimg.cc/xcBhw6JW
On 6/8/22 16:32, Siard wrote:
I assume you are formatting /dev/sdb7? Yes, the installer offers to format it. This is a picture I took from the window named 'Edit /dev/sdb7': https://postimg.cc/xcBhw6JW
What is the rest of your partition layout for the openSUSE install? Where is /boot and where is /home? While you can use a single / for root and home, when I installed to ext4 it also wanted to create a separate boot partition. I didn't research why, just took Carlos' advise and left it. (it was only 8M) -- David C. Rankin, J.D.,P.E.
On 6/8/22 22:44, David C. Rankin wrote:
On 6/8/22 16:32, Siard wrote:
I assume you are formatting /dev/sdb7? Yes, the installer offers to format it. This is a picture I took from the window named 'Edit /dev/sdb7': https://postimg.cc/xcBhw6JW
What is the rest of your partition layout for the openSUSE install?
Where is /boot and where is /home?
While you can use a single / for root and home, when I installed to ext4 it also wanted to create a separate boot partition. I didn't research why, just took Carlos' advise and left it. (it was only 8M)
Also note if you are using your Debian home partition with openSUSE, there will be a UID/GID mapping difference between the distros. You will need to see what is attempting to access what and make sure it isn't a UID/GID issue. -- David C. Rankin, J.D.,P.E.
David C. Rankin:
David C. Rankin:
Siard:
Carlos E.R.:
I assume you are formatting /dev/sdb7?
Yes, the installer offers to format it. This is a picture I took from the window named 'Edit /dev/sdb7': https://postimg.cc/xcBhw6JW
What is the rest of your partition layout for the openSUSE install?
Where is /boot and where is /home?
While you can use a single / for root and home, when I installed to ext4 it also wanted to create a separate boot partition. I didn't research why, just took Carlos' advise and left it. (it was only 8M)
I have not created any separate partitions. I'm not aware of the advantages of a separate boot partition either, I never had one, but never noticed any problems.
Also note if you are using your Debian home partition with openSUSE, there will be a UID/GID mapping difference between the distros. You will need to see what is attempting to access what and make sure it isn't a UID/GID issue.
No, I have a separate partition with all the data I want to share among different distros, mounted on /data in each of them. But as you can read in another post, it looks like I've finally found the cause of the installation hiccups. I have Leap 15.4 installed now. :-) :-)
David C. Rankin wrote:
On 6/8/22 16:32, Siard wrote:
I assume you are formatting /dev/sdb7? Yes, the installer offers to format it. This is a picture I took from the window named 'Edit /dev/sdb7': https://postimg.cc/xcBhw6JW
What is the rest of your partition layout for the openSUSE install? Where is /boot and where is /home?
It probably isn't pertinent for the issue at hand.
While you can use a single / for root and home, when I installed to ext4 it also wanted to create a separate boot partition. I didn't research why, just took Carlos' advise and left it. (it was only 8M)
On servers, we virtually always have everything (/, /home, /boot) on one partition, excluding larger data partitions. -- Per Jessen, Zürich (18.1°C)
On 2022-06-09 05:44, David C. Rankin wrote:
On 6/8/22 16:32, Siard wrote:
I assume you are formatting /dev/sdb7? Yes, the installer offers to format it. This is a picture I took from the window named 'Edit /dev/sdb7': https://postimg.cc/xcBhw6JW
What is the rest of your partition layout for the openSUSE install?
Where is /boot and where is /home?
While you can use a single / for root and home, when I installed to ext4 it also wanted to create a separate boot partition. I didn't research why, just took Carlos' advise and left it. (it was only 8M)
The 8MB partition is not /boot, it is a BIOS raw partition. It has to do with booting in BIOS mode. Even when not needed, it doesn't hurt, while creating it if missing and actually needed is a pain. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
On 08.06.2022 21:54, Siard wrote:
Andrei Borzenkov wrote:
On 08.06.2022 17:19, Siard wrote:
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied
This sounds like root is mounted with noexec option.
error: %prein(python3-six-1.14.0-12.1.noarch) scriptlet failed, exit status 127 error: python3-six-1.14.0-12.1.noarch: install failed .... ....
And the list of uninstallable packages goes on and on:
python3-pip wireless-tools systemd-presets-common-SUSE sg3_utils .... ....
I had the same problem when trying to install 15.3. I did manage to install TW, however.
Does anybody have any idea what could be the problem here?
Start with describing how you perform installation.
I have had Debian as my main distro for a long time, but wanted to try openSUSE, maybe I'll switch to it. I made a bootable USB stick with the Network Image, booted and followed the instructions. I put openSUSE on /dev/sdb7, which is on a logical volume.
I do not understand what it means. What is "logical volume"?
Chose ext4 as file system, because Grub does not recognize a btrfs file system when it is on a logical volume.
Nor do I understand that. What is "logical volume"?
Judging from the error messages, it could be a permission problem??
On 09.06.22 07:08, Andrei Borzenkov wrote:
On 08.06.2022 21:54, Siard wrote:
I put openSUSE on /dev/sdb7, which is on a logical volume.
I do not understand what it means. What is "logical volume"?
s/volume/partition/ Josef -- SUSE Software Solutions Germany GmbH Frankenstraße 146 90461 Nürnberg Germany Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman (HRB 36809, AG Nürnberg) www.suse.com
Andrei Borzenkov:
Siard:
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied
This sounds like root is mounted with noexec option.
Well, I investigated this further, and it looks like I've finally found it. During installation, in the 'Fstab Options' dialog, I had checked 'Mountable by User' and 'Do Not Mount at System Start-up'. See this picture: https://postimg.cc/QFmgLbRZ It's probably the last option that caused the problems. I have finally installed Leap 15.4 now. (Hurray!)
I made a bootable USB stick with the Network Image, booted and followed the instructions. I put openSUSE on /dev/sdb7, which is on a logical volume.
I do not understand what it means. What is "logical volume"?
Chose ext4 as file system, because Grub does not recognize a btrfs file system when it is on a logical volume.
Nor do I understand that. What is "logical volume"?
As Josef Moellers already noticed, I'd better call it 'logical partition'. A disk drive can contain a maximum of four primary partitions or three primary partitions and a single extended partition. That extended partition, then, can be subdivided into several so-called logical partitions. As you see, these are MBR partitions, not UEFI yet. Maybe worth telling. I had SuSE from December 1999, when version 6.3 came out, till March 2007, when its new owner Novell went to cooperate with a certain company that is NOT known for its noble intentions. I could not live with that, tried a few other distros and went on with Debian. My last SuSE version was 10.0. Now that the storm seems to be over, I had a second look. I recognize quite a few names in this list from posters that were already around by then. IMO, Debian, while very reliable, is not easy if you're not an IT professional. For me, it would have been more difficult without the knowledge I had gathered from my SuSE years. As a typical example, I learned the basics of vi from two pages in the SuSE manual. Without it, the road to sort everything out would be way longer. With Ubuntu, on the other hand, you feel treated like a toddler, as if someone is holding your hand. Version names like Focal Fossa, Groovy Gorilla, Hirsute Hippo, Impish Indri and Jammy Jellyfish, I find them annoying and irritating. To me, openSUSE looks like the golden mean. The difference between Leap and Tumbleweed looks very much the same as the difference between Debian Stable and Testing. I always had both. You could have TW as your main distro and have Leap as fallback.
On 2022-06-09 16:03, Siard wrote:
Andrei Borzenkov:
Siard:
I am trying to install Leap 15.4. But during the installation of packages, I get messages like these:
YaST2 Installation of package python3-six failed. Details: Subprocess failed. Error: RPM failed: Command exited with status 1. History: - error: failed to exec scriptlet interpreter /bin/sh: Permission denied
This sounds like root is mounted with noexec option.
Well, I investigated this further, and it looks like I've finally found it. During installation, in the 'Fstab Options' dialog, I had checked 'Mountable by User' and 'Do Not Mount at System Start-up'. See this picture: https://postimg.cc/QFmgLbRZ It's probably the last option that caused the problems. I have finally installed Leap 15.4 now. (Hurray!)
Yes, that could be the problem. I'm curious, why did you do that? -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
On Thu, 9 Jun 2022 18:24 +0200, Carlos E. R. wrote:
On 2022-06-09 16:03, Siard wrote:
During installation, in the 'Fstab Options' dialog, I had checked 'Mountable by User' and 'Do Not Mount at System Start-up'. See this picture: https://postimg.cc/QFmgLbRZ It's probably the last option that caused the problems. I have finally installed Leap 15.4 now. (Hurray!)
Yes, that could be the problem.
I'm curious, why did you do that?
Well, in /etc/fstab I always have every partition (except swap and the running system) set to 'rw,user,noauto'. I guess I did not realize soon enough that in this case that was not very clever....
On 2022-06-10 13:01, Siard wrote:
On Thu, 9 Jun 2022 18:24 +0200, Carlos E. R. wrote:
On 2022-06-09 16:03, Siard wrote:
During installation, in the 'Fstab Options' dialog, I had checked 'Mountable by User' and 'Do Not Mount at System Start-up'. See this picture: https://postimg.cc/QFmgLbRZ It's probably the last option that caused the problems. I have finally installed Leap 15.4 now. (Hurray!)
Yes, that could be the problem.
I'm curious, why did you do that?
Well, in /etc/fstab I always have every partition (except swap and the running system) set to 'rw,user,noauto'. I guess I did not realize soon enough that in this case that was not very clever....
Oh, ok, s just a slip. I thought it might be some idea of achieving something or other :-) -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
Siard wrote:
As Josef Moellers already noticed, I'd better call it 'logical partition'. A disk drive can contain a maximum of four primary partitions or three primary partitions and a single extended partition.
That was a looooooooong time ago, with the DOS partition table. These days with GPT, just call it a partition :-) -- Per Jessen, Zürich (18.0°C)
Siard composed on 2022-06-09 16:03 (UTC+0200):
A disk drive can contain a maximum of four primary partitions or three primary partitions and a single extended partition.
Every one of the four entries in the portion of "the partition table" contained in the MBR represent a definition of one primary partition. Therefore, all entries in the MBR are primaries, including the extended. The extended simply serves a different purpose - extending the partition table to include sector(s) elsewhere on disk that define either additional table sector(s) that extend "the table", and/or additional partition(s). -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Felix Miata asserted on 2022-06-09 23:25 (UTC+0200):
Siard composed on 2022-06-09 16:03 (UTC+0200):
A disk drive can contain a maximum of four primary partitions or three primary partitions and a single extended partition.
Every one of the four entries in the portion of "the partition table" contained in the MBR represent a definition of one primary partition. Therefore, all entries in the MBR are primaries, including the extended.
Several sites state otherwise. "On a MBR disk, there can only be maximum 4 primary partitions or less than 4 primary partitions plus one extended partition." https://www.diskpart.com/resource/disk-partition-basic-understanding.html "Primary and extended partitions are the main disk divisions; one hard disk may contain up to four primary partitions, or three primary partitions and one extended partition." https://www.werockyourweb.com/office/equipment/hard-drives/partitions/ "A standard master boot record (MBR)-based hard disk can contain up to four primary partitions or three primary partitions and one extended partition." https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend... "A disk drive can contain a maximum of four primary partitions or three primary partitions and a single extended partition." https://www.differencebetween.com/difference-between-primary-partition-and-v... Etc. etc.
On 2022-06-10 12:05, Siard wrote:
Felix Miata asserted on 2022-06-09 23:25 (UTC+0200):
Siard composed on 2022-06-09 16:03 (UTC+0200):
A disk drive can contain a maximum of four primary partitions or three primary partitions and a single extended partition.
Every one of the four entries in the portion of "the partition table" contained in the MBR represent a definition of one primary partition. Therefore, all entries in the MBR are primaries, including the extended.
Several sites state otherwise.
"On a MBR disk, there can only be maximum 4 primary partitions or less than 4 primary partitions plus one extended partition." https://www.diskpart.com/resource/disk-partition-basic-understanding.html
It is the same thing :-) Many people, me included, consider the extended partition as just a type of primary partition. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin -
David C. Rankin -
Felix Miata -
Josef Moellers -
Per Jessen -
Siard