[arch-dev-public] [PATCH 2/2] Accept any *.pkg.tar.* package file name

Eric Bélanger snowmaniscool at gmail.com
Sun Feb 21 23:05:26 EST 2010

On Sun, Feb 21, 2010 at 4:26 PM, Pierre Schmitz <pierre at archlinux.de> wrote:
> Am Sonntag, 21. Februar 2010 08:47:27 schrieb Pierre Schmitz:
>> After a few tests with a local repo I guess I am ready to submit my
>> changes.  So, here is the plan:
>> 1) Add me to the dbscripts-git group and let me push my patch to the repo
>> 2) Checkout the scripts into /arch or /arch-new (to be discussed)
>> 3) Check which packages need to be kept in gz format for a while.(is it
>> just  pacman, libarchive and xz-utils) and add PKGEXT='.pkg.tar.gz' into
>> their PKGBUILDs
>> 4) Start packaging xz compressed packages
>> 5) Should we ask everyone to set PKGEXT to .pkg.tar.xz in makepkg.conf and
>>    probably ship it as default?
>> 6) Apply the same changes on sigurd (community server)
> Thomas has added the new scripts to /arch-new The devtools pacakge in testing
> is the first xz compressed package. Everybody say hurray!
> If you upload xz packages with the devtools make sure PKGEXT in your
> makpekg.conf is set to .pkg.tar.xz.
> PS: we figured out that the dbscripts on sigurd are quite outdated and thus
> wont remove old packages. So this will be fixed once we update those, too.
> --
> Pierre Schmitz, https://users.archlinux.de/~pierre

There seem to be problems (archrelease) with the new devtools package.

First when building a i686 package for doxygen, my connection quitted
during the process:

$ extrapkg
committing changes to trunk...done
uploading doxygen-1.6.3-1-i686.pkg.tar.xz
       1.33M 100%   88.11MB/s    0:00:00 (xfer#1, to-check=0/1)

sent 1.33M bytes  received 31 bytes  48.23K bytes/sec
total size is 1.33M  speedup is 1.00
releasing package...svn: Network connection closed unexpectedly
skipping x86_64

I reran extrapkg, thinking that it would work this time but it didn't:

$ extrapkg
committing changes to trunk...done
sent 68 bytes  received 12 bytes  53.33 bytes/sec
total size is 1.33M  speedup is 16577.30
releasing package.../usr/bin/archrelease: line 29: [[: -1M: value too
great for base (error token is "1M")
svn: In directory 'repos'
svn: Error processing command 'modify-entry' in 'repos'
svn: Error modifying entry for 'extra-i686'
svn: 'extra-i686' is not under version control
svn: Working copy '/home/eric/svnroot/doxygen/repos' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
svn: Can't add 'repos/extra-i686/trunk' to a parent directory
scheduled for deletion
svn: Working copy '/home/eric/svnroot/doxygen/repos' locked
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
skipping x86_64

I don't know what happened but I had a copy of trunk in
repos/extra-i686.  I thought that it was a fluke because of the
network glitch so I did a new checkout and did the copying/commit by

Now with another package (ecasound), it doesn't release at all:

$ extrapkg "Upstream update, Improved description"
committing changes to trunk...done
sent 69 bytes  received 12 bytes  54.00 bytes/sec
total size is 1.05M  speedup is 12930.17
releasing package...already done

I don't know why it says "already done" because that was the first
time that I ran extrapkg so it defenitely not done.  I'll probably
need to do it by hand.

Another thing: it was mentionned on the IRC channel that namcap
doesn't work with the new xz packages. It would be nice to have xz
support in namcap before we start pushing these changes out.

More information about the arch-dev-public mailing list