Arch Linux

aabmass

Member

Registered: 2011-12-14

Posts: 34

Can't create new AUR package with same name as an old, deleted, one

A package I submitted/maintain, hyperterm, has been renamed upstream from hyperterm to hyper. So, I was planning to create a new AUR package called hyper and then submitting a merge-into request on the original. I first went to check if a package named hyper already exists with a AUR search; it doesn't.

So then I tried

git clone git+ssh://aur@aur.archlinux.org/package_name.git

and strangely didn't get the "warning: You appear to have cloned an empty repository." as described on the wiki. So I went in to look at what I just cloned and there is a PKGBUILD with:

pkgname=hyper
pkgver=0.1.1
pkgrel=1
pkgdesc="A Lightweight Web Browser"
arch=(any)
url="https://github.com/AxelMarchand/Hyper"
license=('MIT')
depends=('webkitgtk')
makedepends=('make' 'gcc' 'pkg-config')
source=('https://github.com/AxelMarchand/Hyper/releases/download/v0.1.1/hyper-0.1.1.tar.gz')
md5sums=('057970f90e9650f36faccc17e5f2061c')

build() {
    cd $srcdir/$pkgname-$pkgver

    make || return 1
    make clean
}

package() {
    cd $srcdir/$pkgname-$pkgver
    make install || return 1
}

I think what happened is there used to be a package called "hyper" in the AUR that got deleted. Regardless, I tried adding the repo for hyper as a remote in my package's repo and pushing, but it gets rejected by the git hook. Is this an AUR bug or am I missing something?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,553

Re: Can't create new AUR package with same name as an old, deleted, one

You need to start with the old repo then add your modifications.

aabmass

Member

Registered: 2011-12-14

Posts: 34

Re: Can't create new AUR package with same name as an old, deleted, one

You need to start with the old repo then add your modifications.

The thing is I don't want the other repo's history. I wanted to add the new repo as a remote so I could just follow the wiki:

If you have already created a git repository, you can simply create a remote for the AUR git repository and then fetch it:

$ git remote add remote_name git+ssh://aur@aur.archlinux.org/package_name.git
$ git fetch remote_name

where remote_name is the name of the remote to create (e.g., "origin"). See Git#Using remotes for more information.

When I try that via

git remote add hyper_new git+ssh://aur@aur.archlinux.org/hyper.git
git fetch hyper_new
# make changes and commit
git push hyper_new master

I get rejected by git:

To git+ssh://aur.archlinux.org/hyper.git
 ! [rejected]        master -> master (non-fast-forward)
error: failed to push some refs to 'git+ssh://aur@aur.archlinux.org/hyper.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

In other words, it wants me to merge in the old changes from the repo that should be bare. Should I just do this and then revert whatever commits the old package had?

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,553

Re: Can't create new AUR package with same name as an old, deleted, one

You need to start with the old repo then add your modifications.

The thing is I don't want the other repo's history.

There's nothing you can do about that. It's already there and you can't rewrite it.

Edit: after thinking about it, the only other option I can think of is to keep the current pkgbase and change the pkgname. Repos are based on pkgbase.

Last edited by Scimmia (2016-10-08 05:24:37)

quomoow

Member

Registered: 2016-10-11

Posts: 13

Re: Can't create new AUR package with same name as an old, deleted, one

https://www.archlinux.org/pacman/PKGBUILD.5.html -> speccially this 2 options

pkgrel -> This is the release number specific to the Arch Linux release. This allows package maintainers to make updates to the package’s configure flags, for example. This is typically set to 1 for each new upstream software release and incremented for intermediate PKGBUILD updates. The variable is not allowed to contain hyphens.

epoch ->  Used to force the package to be seen as newer than any previous versions with a lower epoch, even if the version number would normally not trigger such an upgrade. This value is required to be a positive integer; the default value if left unspecified is 0. This is useful when the version numbering scheme of a package changes (or is alphanumeric), breaking normal version comparison logic. See pacman(8) for more information on version comparisons.

Just ... pkgrel=!1 but pkgrel=2

or if it don't work use epoch=1

just... try, maybe it will work

Last edited by quomoow (2016-10-18 18:32:22)