Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream issues #20

Open
25 of 41 tasks
AladW opened this issue Mar 4, 2016 · 9 comments
Open
25 of 41 tasks

Upstream issues #20

AladW opened this issue Mar 4, 2016 · 9 comments
Labels

Comments

@AladW
Copy link
Member

AladW commented Mar 4, 2016

Closed

Reported

Not reported

  • expac misses support for --sysroot
  • libmakepkg message.sh misses PURPLE and CYAN
  • mkarchroot Failed to copy /etc/resolv.conf to /root/etc/resolv.conf
  • makechrootpkg rm: cannot remove '/logdest/logpipe.zJztfPcl': No such file or directory
    pacman-dev
  • makechrootpkg default makepkg options cannot be overridden (in particular --noconfirm)
  • makepkg hangs on INT (Ctrl+C, interactive) when run from a script
  • repo-add relies on hardcoded list of extensions: mimetype should suffice
@AladW AladW added the upstream label Mar 4, 2016
@AladW AladW changed the title aurweb RPC interface Upstream issues Mar 13, 2016
@AladW AladW added the pacman label Mar 13, 2016
@rmarquis
Copy link

You can add to your list that the RPC currently includes all architecture dependent (make)depends in the same arrays. See here for details.

@AladW
Copy link
Member Author

AladW commented Mar 16, 2016

Added, thanks for the reminder.

AladW pushed a commit that referenced this issue Apr 8, 2016
Fix surf2 build, see #20
@AladW AladW removed the pacman label Apr 13, 2016
AladW pushed a commit that referenced this issue Apr 30, 2016
+ Use pacman --print instead of expac+pacsift (see #20)
AladW pushed a commit that referenced this issue May 5, 2016
UTF-8 issues with expac/pacsift (#20)
AladW pushed a commit that referenced this issue Mar 22, 2017
@AladW
Copy link
Member Author

AladW commented Apr 28, 2017

Upstream issues for repose:

Removed from the first post as support will be removed from aurbuild, see #238.

@eli-schwartz
Copy link

https://bugs.archlinux.org/task/49946 fixed in git

Error codes for all in https://lists.archlinux.org/pipermail/pacman-dev/2017-September/022156.html
Currently in the patchqueue at https://git.archlinux.org/users/allan/pacman.git/commit/?h=patchqueue&id=ab2be5794de8a57426ec3fc0f631cc766a0b8227

@eli-schwartz
Copy link

eli-schwartz commented Dec 17, 2017

pacman vercmp alpha '' results in -1 (alpha < "") FS#49093

Submitted fix at https://lists.archlinux.org/pipermail/pacman-dev/2017-December/022211.html
At least, empty strings are still considered valid version strings, but passing only one argument is now an error.

@AladW AladW removed this from the Backlog milestone Mar 20, 2018
@eli-schwartz
Copy link

pacman vercmp alpha '' results in -1 (alpha < "") FS#49093

What's the dead end here? vercmp alpha is now a fatal error in the latest stable release. I don't think it's strictly necessary to call vercmp with quoted arguments, as any actual version in the wild, with a space in it, is invalid and can be checked as such -- vercmp doesn't do any checks at all to determine whether a pkgver is invalid or not.

From the bug report:

Well, vercmp is useful in other cases, such as comparing sync/local versions (with pacman --print or expac) against the AUR RPC (with curl/json). If either string is empty, you'd have to be aware of the limitation, and workaround by e.g. setting -1 yourself if the variable is empty.

Anyway in this case I'd expect detecting a nonexistent package to be implemented via checking the returned contents of curl/expac, rather than making assumptions about the version comparison.

@AladW
Copy link
Member Author

AladW commented Sep 26, 2018

I guess it can be handled in a satisfactory way from the caller, unlike any of the other "dead end" issues. I moved it to "closed".

@eli-schwartz
Copy link

Great, we're now even closer to "all dead ends lead to aurweb". :D

@AladW AladW pinned this issue Jan 17, 2019
@AladW AladW unpinned this issue Nov 18, 2020
@micwoj92
Copy link

pacsift: no output if --sysroot is specified andrewgregory/pacutils#26

Should be marked as done I think, upstream issue was solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants