[SOLVED] yaourt -Syua wants to update a package which hasn't changed

pgoetz · 2014-04-24 20:40:44

I built a modest package, vi-vim-symlink, tested it extensively with pacman, and then uploaded it to AUR.

Recently some user reported that every time he runs yaourt, the package wants to be reinstalled. I installed yaourt and confirmed this behavior:

gecko:~~$ yaourt -Syua
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
 Foreign packages: | 4 / 4

==> Package upgrade only (new release):
aur/vi-vim-symlink 1-1 1 -> 1

==> Continue upgrade ? [Y/n]
==> [V]iew package detail   [M]anually select packages
==> --------------------------------------------------

Does anyone have any idea why this is happening? The package is super simple and only creates a couple of symlinks, uninstalling vi, if necessary.

Last edited by pgoetz (2014-04-25 21:33:06)

HalosGhost · 2014-04-24 20:56:49

Looks like the source tarball was repackaged without having been sync'd. So, the one you have installed is 1-1 which is the version that the PKGBUILD creates. But the version in the ALUR is not 1-1, it's just 1. Try doing the following:

$ makepkg -s
$ makepkg -S

And then uploading the resulting source package. By the way, take a look at the Packaging Standards, that package breaks a couple rules. It's also completely unnecessary, but whatever.

All the best,

-HG

pgoetz · 2014-04-24 21:05:22

Thanks for the quick and helpful response!

HalosGhost wrote:

By the way, take a look at the Packaging Standards, that package breaks a couple rules. It's also completely unnecessary, but whatever.

I read through all the packaging guidelines and ABS-related Wiki pages before posting, including the one you reference. Would you mind telling me which rules I'm breaking? I have no idea what they might be.

HalosGhost · 2014-04-24 21:10:23

For starters, that pkgdesc is huge for no reason at all. Also, does that package actually work? Those symlinks don't look valid at all.

All the best,

-HG

pgoetz · 2014-04-24 21:13:18

HalosGhost wrote:

It's also completely unnecessary, but whatever.

I missed this on first read. I also wouldn't mind knowing why it's unnecessary. I agonized over the best way to do this (link vi/view to vim) and settled on a package as the most robust.

pgoetz · 2014-04-24 21:26:31

HalosGhost wrote:

For starters, that pkgdesc is huge for no reason at all. Also, does that package actually work? Those symlinks don't look valid at all.

The package definitely works (I'm using it on several machines). The pkgdesc is lengthy because it's kind of an odd package, so I tried to explain the reason for it's existence. (This came after a lengthy forum discussion on the issue of most linux users expecting /usr/bin/vi and /usr/bin/view to actually be vim, and not Bill Joy vi.) If I were just packaging bottle.py or something like this my pkgdesc would be short.

Do you see anything which is an actual violation of the Arch Packaging Standards?

I'm still not entirely sure what this means or how this happened.

Looks like the source tarball was repackaged without having been sync'd

AUR wouldn't let me upload the package without a url; first I added a random url (one of my servers), then changed my mind and used the vim url -- this must have been when things got out of whack.

Lone_Wolf · 2014-04-25 11:37:18

maybe something like this would work for the description :

"Links vi and view to vim. This is the default on the majority of OSes/distros . edit/ex/vedit are not linked."

------------------------
I looked into the .AURINFO you provide, and it does not list the pkgver .
Maybe that's what causes this yaourt behaviour ?

-------------------
You have license as 'custom' , and this normally requires a separate license to be installed in /usr/share/licenses/$pkgname .
Not sure whether it'd be better to replicate vi/ vim licenses or provide a separate license file from yourself.
It's a minor issue, but you might want to ask for opinions about that on aur-general or arch-general ML.

Awebb · 2014-04-25 14:54:11

This is the first time I have seen an .AURINFO in the source file list. What's wrong with your PKGBUILD in the first place?

pgoetz · 2014-04-25 21:23:22

Lone_Wolf wrote:

I looked into the .AURINFO you provide, and it does not list the pkgver .
Maybe that's what causes this yaourt behaviour ?

Argh, this fixed the problem! I did include a pkgver, but it's wasn't in the right format:

pkgver = 1

instead of

pkgver = 1-1

Re: licensing. The documentation suggests using the license "unknown" if the license isn't known, but I agree this doesn't make sense, since it's my package so I should know what the license is. Originally I wanted to use MIT or BSD, but these require a custom license file as well. Based on your comment, I researched the /usr/share/license/common licenses and settled on CDDL as the best fit, since I don't really care what people do with these 2 symlinks. <:)

pgoetz · 2014-04-25 21:29:43

Awebb wrote:

This is the first time I have seen an .AURINFO in the source file list. What's wrong with your PKGBUILD in the first place?

There's nothing wrong with my PKGBUILD, however it seems that one is encouraged to include a .AURINFO file, which I created, but the command

makepkg --source

doesn't include the .AURINFO file in the source tarball. I posted to the forum about that here, and after some discussion it appeared that the most robust way of dealing with this was to add the .AURINFO file to the source file list. This is now documented in the Wiki.

I agree that this is not a satisfying solution to the problem (the source file list should only include source files), so if you have a better way of doing this please let me know. No one involved in the forum discussion referenced above had a better idea.

pgoetz · 2014-04-25 21:32:45

Lone_Wolf wrote:

"Links vi and view to vim. This is the default on the majority of OSes/distros . edit/ex/vedit are not linked."

I forgot to add: thanks for this simplified package description! I just kept my original description pending some explanation why I shouldn't use all 80 characters available to me for the pkgdesc field.

Awebb · 2014-04-26 12:09:22

Try uploading it without the AURINFO and see if your problem goes away. Then check, if the AUR reads the PKGBUILD correctly without the AURINFO.

pgoetz · 2014-04-28 11:23:30

Awebb wrote:

Try uploading it without the AURINFO and see if your problem goes away. Then check, if the AUR reads the PKGBUILD correctly without the AURINFO.

That pinpoints the problem -- the pkgver field in .AURINFO was incorrect -- see my response to Lone_Wolf above, and thanks for the helpful suggestion!

Arch Linux

#1 2014-04-24 20:40:44

[SOLVED] yaourt -Syua wants to update a package which hasn't changed

#2 2014-04-24 20:56:49

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#3 2014-04-24 21:05:22

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#4 2014-04-24 21:10:23

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#5 2014-04-24 21:13:18

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#6 2014-04-24 21:26:31

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#7 2014-04-25 11:37:18

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#8 2014-04-25 14:54:11

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#9 2014-04-25 21:23:22

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#10 2014-04-25 21:29:43

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#11 2014-04-25 21:32:45

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#12 2014-04-26 12:09:22

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

#13 2014-04-28 11:23:30

Re: [SOLVED] yaourt -Syua wants to update a package which hasn't changed

Board footer