[Dev] Packages seems not uploaded to our repository (anything wrong with libretools?)

Luke T. Shumaker lukeshu at sbcglobal.net
Mon Dec 2 05:49:01 GMT 2013


At Sun, 01 Dec 2013 21:11:21 -0500,
Luke T. Shumaker wrote:
> 
> At Sat, 30 Nov 2013 15:54:39 -0600,
> Jorge Araya Navarro wrote:
> > Maybe there is something wrong in libretools, I did something wrong or
> > missed something... anyway, help please :)
> 
> You're probably hitting a mirror that hasn't updated yet.  When you
> release, it only updates repo.parabolagnulinux.org, if you have other
> mirrors enabled in /etc/pacman.d/mirrorlist, those can take a while
> (24 hours?) to sync with repo.parabolagnulinux.org.

Hey, I just realized that you said which packages the issue is with,
and that I can check whether they are released.

It does appear that something went wrong, the packages are still
sitting in ~repo/staging-jorge.  Whatever error there was should have
shown up in the librerelease output.

So, I tried running db-update manually:

    $ STAGING=~repo/staging-jorge/staging db-update
    ==> ERROR PAckage pcr/ocsync-0.90.4-1-x86_64.pkg.tar.xz already exists in another repository
    ==> Removing left over lock from [pcr] (i686)
    ==> Removing left over lock from [pcr] (x86_64)
    ==> Removing left over lock from [pcr] (mips64el)

So, it appears that you tried to upload a duplicate version of ocsync
(you probably meant to bump pkgrel).  I moved the ocsync files to a
staging.bak directory, and tried again:

    $ mkdir -p staging-jorge/staging.bak/pcr
    $ mv staging-jorge/staging/pcr/ocsync-0.90.4-1-* staging-jorge/staging.bak/pcr/
    $ STAGING=~repo/staging-jorge/staging db-update
    ==> Updating [pcr]...
      -> owncloud-client-1.4.2-1-i686.pkg.tar.xz (i686)
      -> unittestpp-1.4-3-i686.pkg.tar.xz (i686)
      -> owncloud-client-1.4.2-1-x86_64.pkg.tar.xz (x86_64)
      -> unittestpp-1.4-3-x86_64.pkg.tar.xz (x86_64)

There you go!

I've left the ocsync files there, in case they matter to you.

Happy hacking,
~ Luke Shumaker



More information about the Dev mailing list