[SOLVED] powershell visual issue

Fabienne · 2023-05-29 17:48:10

loqs wrote:

I uploaded the diff to a pastebin for you.
$ curl -o PKGBUILD.diff http://ix.io/4x0L
$ git apply -v PKGBUILD.diff

$ git apply -v PKGBUILD.diff
Checking patch PKGBUILD...
error: PKGBUILD: No such file or directory

loqs · 2023-05-29 18:07:57

The error should be self explanatory. The commands need to executed in the same directory as the PKGBUILD.

Fabienne · 2023-05-29 18:14:31

loqs wrote:

The error should be self explanatory. The commands need to executed in the same directory as the PKGBUILD.

Well, I got the same output when running in powerline-shell-git branch unless you mean somewhere else.

loqs · 2023-05-29 18:20:56

Fabienne wrote:

loqs wrote:
The error should be self explanatory. The commands need to executed in the same directory as the PKGBUILD.
Well, I got the same output when running in powerline-shell-git branch unless you mean somewhere else.

Arch_User_Repository#Acquire_build_files.

Fabienne · 2023-05-29 18:31:22

loqs wrote:

Fabienne wrote:
loqs wrote:
The error should be self explanatory. The commands need to executed in the same directory as the PKGBUILD.
Well, I got the same output when running in powerline-shell-git branch unless you mean somewhere else.
Arch_User_Repository#Acquire_build_files.

$ git apply -v PKGBUILD.diff
error: No valid patches in input (allow with "--allow-empty")

loqs · 2023-05-29 18:35:42

$ file PKGBUILD.diff 
PKGBUILD.diff: unified diff output, ASCII text
$ md5sum PKGBUILD.diff 
194274204513ed4cd7c09c9968881f55  PKGBUILD.diff
$ rm PKGBUILD.diff 
$ curl -o PKGBUILD.diff http://ix.io/4x0L
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   601  100   601    0     0   1130      0 --:--:-- --:--:-- --:--:--  1129
$ file PKGBUILD.diff 
PKGBUILD.diff: unified diff output, ASCII text
$ md5sum PKGBUILD.diff 
194274204513ed4cd7c09c9968881f55  PKGBUILD.diff
$ git apply -v PKGBUILD.diff
Checking patch PKGBUILD...
Applied patch PKGBUILD cleanly.
$ git apply -v PKGBUILD
error: No valid patches in input (allow with "--allow-empty")

Fabienne · 2023-05-29 18:48:24

loqs wrote:

$ file PKGBUILD.diff 
PKGBUILD.diff: unified diff output, ASCII text
$ md5sum PKGBUILD.diff 
194274204513ed4cd7c09c9968881f55  PKGBUILD.diff
$ rm PKGBUILD.diff 
$ curl -o PKGBUILD.diff http://ix.io/4x0L
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   601  100   601    0     0   1130      0 --:--:-- --:--:-- --:--:--  1129
$ file PKGBUILD.diff 
PKGBUILD.diff: unified diff output, ASCII text
$ md5sum PKGBUILD.diff 
194274204513ed4cd7c09c9968881f55  PKGBUILD.diff
$ git apply -v PKGBUILD.diff
Checking patch PKGBUILD...
Applied patch PKGBUILD cleanly.
$ git apply -v PKGBUILD
error: No valid patches in input (allow with "--allow-empty")

You seem to have the same issue as I can see.

loqs · 2023-05-29 18:52:48

You posted

$ git apply -v PKGBUILD.diff
error: No valid patches in input (allow with "--allow-empty")

My output for the same command is

$ git apply -v PKGBUILD.diff
Checking patch PKGBUILD...
Applied patch PKGBUILD cleanly.

I produced the same output you posted with a different command

$ git apply -v PKGBUILD
error: No valid patches in input (allow with "--allow-empty")

PKGBUILD and PKGBUILD.diff are not the same.
Are you transcribing the commands and their outputs by hand and introducing transcription errors?

Last edited by loqs (2023-05-29 18:53:21)

Fabienne · 2023-05-29 19:03:52

loqs wrote:

You posted
$ git apply -v PKGBUILD.diff
error: No valid patches in input (allow with "--allow-empty")
My output for the same command is
$ git apply -v PKGBUILD.diff
Checking patch PKGBUILD...
Applied patch PKGBUILD cleanly.
I produced the same output you posted with a different command
$ git apply -v PKGBUILD
error: No valid patches in input (allow with "--allow-empty")
PKGBUILD and PKGBUILD.diff are not the same.
Are you transcribing the commands and their outputs by hand and introducing transcription errors?

$ git apply -v PKGBUILD.diff
Checking patch PKGBUILD...
Applied patch PKGBUILD cleanly.

This is what I got now. I had to drag the PKGBUILD file do the right directory. What's next? pacman -Syu?

loqs · 2023-05-29 19:07:45

Fabienne wrote:

This is what I got now. I had to drag the PKGBUILD file do the right directory.

Then you are working in the wrong directory. See the link in post #30.

Fabienne wrote:

What's next? pacman -Syu?

Covered by later sections of the same link.

Fabienne · 2023-05-29 19:41:15

loqs wrote:

Fabienne wrote:
This is what I got now. I had to drag the PKGBUILD file do the right directory.
Then you are working in the wrong directory. See the link in post #30.

I tried in powerline-shell directory without success.

seth · 2023-05-29 19:44:36

First of all, stop "dragging" stuff somewhere.

Start with a fresh clone of the AUR package.

cd ~
rm -rf powerline-shell-git
git clone https://aur.archlinux.org/powerline-shell-git.git
cd powerline-shell-git
curl -o PKGBUILD.diff http://ix.io/4x0L
git apply -v PKGBUILD.diff
makepkg -i

loqs · 2023-05-29 19:47:20

Fabienne wrote:

I tried in powerline-shell directory without success.

Because that is a clone of the upstream project.

Fabienne · 2023-05-29 19:59:00

seth wrote:

First of all, stop "dragging" stuff somewhere.
Start with a fresh clone of the AUR package.
cd ~
rm -rf powerline-shell-git
git clone https://aur.archlinux.org/powerline-shell-git.git
cd powerline-shell-git
curl -o PKGBUILD.diff http://ix.io/4x0L
git apply -v PKGBUILD.diff
makepkg -i

This worked with adding -o in last line of command.
Now I can update the system and reboot?

seth · 2023-05-29 20:05:55

"-o" means you didn't actually build the package and you neither have to "update the system" nor "reboot" here.
Build the package, install it your next invocation of powerline-shell will hopefully be fine.

Fabienne · 2023-05-29 20:14:17

seth wrote:

"-o" means you didn't actually build the package and you neither have to "update the system" nor "reboot" here.
Build the package, install it your next invocation of powerline-shell will hopefully be fine.

well i did this before

$ makepkg -i -o
==> Making package: powerline-shell-git r588.4b19aa4-1 (Mon 29 May 2023 09:56:47 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating powerline-shell git repo...
==> Validating source files with md5sums...
    powerline-shell ... Skipped
==> Extracting sources...
  -> Creating working copy of powerline-shell git repo...
Switched to a new branch 'makepkg'
==> Starting pkgver()...
==> Sources are ready.

and the powerline-shell still doesn't look fixed the way it was before.

loqs · 2023-05-29 20:20:56

Fabienne wrote:

well i did this before

$ makepkg -i -o
==> Making package: powerline-shell-git r588.4b19aa4-1 (Mon 29 May 2023 09:56:47 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating powerline-shell git repo...
==> Validating source files with md5sums...
    powerline-shell ... Skipped
==> Extracting sources...
  -> Creating working copy of powerline-shell git repo...
Switched to a new branch 'makepkg'
==> Starting pkgver()...
==> Sources are ready.

and the powerline-shell still doesn't look fixed the way it was before.

seth wrote:

"-o" means you didn't actually build the package

Why would you expect anything to change when you did not build or install a package?

Fabienne · 2023-05-29 20:23:38

loqs wrote:

Fabienne wrote:
well i did this before
$ makepkg -i -o
==> Making package: powerline-shell-git r588.4b19aa4-1 (Mon 29 May 2023 09:56:47 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating powerline-shell git repo...
==> Validating source files with md5sums...
    powerline-shell ... Skipped
==> Extracting sources...
  -> Creating working copy of powerline-shell git repo...
Switched to a new branch 'makepkg'
==> Starting pkgver()...
==> Sources are ready.
and the powerline-shell still doesn't look fixed the way it was before.
seth wrote:
"-o" means you didn't actually build the package
Why would you expect anything to change when you did not build or install a package?

Because I get this then

$ makepkg -i
==> Making package: powerline-shell-git r588.4b19aa4-1 (Mon 29 May 2023 10:21:47 PM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating powerline-shell git repo...
==> Validating source files with md5sums...
    powerline-shell ... Skipped
==> Extracting sources...
  -> Creating working copy of powerline-shell git repo...
Reset branch 'makepkg'
==> Starting pkgver()...
==> WARNING: A package has already been built, installing existing package...
==> Installing package powerline-shell-git with pacman -U...
[sudo] password for user: 
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) powerline-shell-git-r588.4b19aa4-1

Total Installed Size:  0.27 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                                                                                                                                                                                                   [--------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100%
(1/1) checking package integrity                                                                                                                                                                                                                                 [--------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100%
(1/1) loading package files                                                                                                                                                                                                                                      [--------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100%
(1/1) checking for file conflicts                                                                                                                                                                                                                                [--------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
powerline-shell-git: /usr/bin/powerline-shell exists in filesystem
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).

Fuxino · 2023-05-29 20:29:38

Fabienne wrote:

Because I get this then

error: failed to commit transaction (conflicting files)
powerline-shell-git: /usr/bin/powerline-shell exists in filesystem
Errors occurred, no packages were upgraded.
==> WARNING: Failed to install built package(s).

https://wiki.archlinux.org/title/Pacman … )%22_error

seth · 2023-05-29 20:32:36

Also https://bbs.archlinux.org/viewtopic.php … 4#p2102254
I'm starting to think that this is some sort of prank…

Fabienne · 2023-05-29 20:50:50

seth wrote:

Also https://bbs.archlinux.org/viewtopic.php … 4#p2102254
I'm starting to think that this is some sort of prank…

Sadly not a prank.
Ran

$ find /var/cache/pacman/pkg/ -iname "*.part" -delete

Now I have to remove powerline-shell-git-r588.4b19aa4-1 since it's the conflicting package? If so then I do that with

$ pacman -Rns powerline-shell-git-r588.4b19aa4-1

and then run

$ makepkg -i

?

seth · 2023-05-29 20:54:47

find /var/cache/pacman/pkg/ -iname "*.part" -delete

You managed to look at the wrong wiki paragraph.

Now I have to remove powerline-shell-git-r588.4b19aa4-1 since it's the conflicting package?

Do you have this package?

I told you what to do in the post I just linked in #45

loqs · 2023-05-29 21:02:18

seth wrote:

I'm starting to think that this is some sort of prank…

Possibly a serious case of help vampirism?

seth · 2023-05-29 21:12:36

Help vampires usually don't come up with new and creative ways to circumvent the solution at every step

I guess if there's really no understanding for anything one's doing…

@Fabienne, did somebody else install archlinux for you and then left you alone in front of the system?

Fabienne · 2023-05-29 21:12:49

seth wrote:

Now I have to remove powerline-shell-git-r588.4b19aa4-1 since it's the conflicting package?
Do you have this package?

Well yes unless it wouldn't say conflicting package.

seth wrote:

I told you what to do in the post I just linked in #45

It tried and it doesn't work.

Arch Linux

#26 2023-05-29 17:48:10

Re: [SOLVED] powershell visual issue

#27 2023-05-29 18:07:57

Re: [SOLVED] powershell visual issue

#28 2023-05-29 18:14:31

Re: [SOLVED] powershell visual issue

#29 2023-05-29 18:20:56

Re: [SOLVED] powershell visual issue

#30 2023-05-29 18:31:22

Re: [SOLVED] powershell visual issue

#31 2023-05-29 18:35:42

Re: [SOLVED] powershell visual issue

#32 2023-05-29 18:48:24

Re: [SOLVED] powershell visual issue

#33 2023-05-29 18:52:48

Re: [SOLVED] powershell visual issue

#34 2023-05-29 19:03:52

Re: [SOLVED] powershell visual issue

#35 2023-05-29 19:07:45

Re: [SOLVED] powershell visual issue

#36 2023-05-29 19:41:15

Re: [SOLVED] powershell visual issue

#37 2023-05-29 19:44:36

Re: [SOLVED] powershell visual issue

#38 2023-05-29 19:47:20

Re: [SOLVED] powershell visual issue

#39 2023-05-29 19:59:00

Re: [SOLVED] powershell visual issue

#40 2023-05-29 20:05:55

Re: [SOLVED] powershell visual issue

#41 2023-05-29 20:14:17

Re: [SOLVED] powershell visual issue

#42 2023-05-29 20:20:56

Re: [SOLVED] powershell visual issue

#43 2023-05-29 20:23:38

Re: [SOLVED] powershell visual issue

#44 2023-05-29 20:29:38

Re: [SOLVED] powershell visual issue

#45 2023-05-29 20:32:36

Re: [SOLVED] powershell visual issue

#46 2023-05-29 20:50:50

Re: [SOLVED] powershell visual issue

#47 2023-05-29 20:54:47

Re: [SOLVED] powershell visual issue

#48 2023-05-29 21:02:18

Re: [SOLVED] powershell visual issue

#49 2023-05-29 21:12:36

Re: [SOLVED] powershell visual issue

#50 2023-05-29 21:12:49

Re: [SOLVED] powershell visual issue

Board footer