Source of the Tarball for AUR Package Submissions?

When submiting a package to the AUR, are we supposed to submit the foo.pkg.tar.gz that makepkg creates in the directory, or do we tar up the entire /var/abs/local/foo/ directory ourselves and send that tarball?
The reason I ask is that when trying to sumbit the tarball created by makepkg directly, I kept receiveing the message "Error - No file uploaded".  I am probably just misunderstanding the documentation, and it looks as though I need to tar up the entire directory, but can anyone set me straight so I can be sure?

Sorry for such the stupid question.  I wrote that while I was at my windows machine at work and didn't have access to the abs directory to compare.  The more I thought about it, the more it made sense to just include the PKGBUILD and not all of the other stuff created by makepkg.  I had read that doc over a bunch of times, but never really picked up the obvious.  Thanks Snowman...patience is a virture :-)
EDIT:  Looking back through some of the documentation, I think where I got confused was from the wiki page ABS - the Arch Build System where it talks about "What is a package file?" in reference to the foo.pkg.tar.gz type file, and when submitting packages to the AUR, it prompts you to "Upload package file:" in reference to the plain old tarball with only the PKGBUILD, .install files, etc...

Similar Messages

  • What are the rules for AUR packages that rely on Alien bins [solved]

    Hi,
    I use ArchLinuxArm and want to create an AUR package that gets binaries from, lets say Fedora ARM, extracts them and modifies the config files in order to make it compatible with the Arch way of Linux. Of course, the PKGBUILD I am going to write will limit installation on the appropriate arcitecture, e.g. armv7h, then.
    Is this generally allowed or will my package be deleted after submission to AUR?
    Best,
    RaumZeit
    Last edited by RaumZeit (2013-10-27 01:38:31)

    AUR queries should be posted to the aur-general mailing list.
    As indicated in the thread linked by Karol above, it is permitted to append unsupported architectures to the arch array of a PKGBUILD that builds on officially supported architectures. That does not necessarily mean that we will allow packages that only build on unsupported architectures. This should be discussed on the mailing list. I have a vague memory of this coming up before and I think the consensus was that such packages would not be supported, but that consensus may have changed. Personally, I do not see a problem with such packages right now and I expect official supported to be extended in the future,  so I am in favor of allowing them.
    Packages that install pre-compiled binaries should be distinguished from normal packages with a "-bin" suffix. Such packages are permitted as long as they do not violate applicable licenses.

  • Searching for AUR packages with "%" queries

    According to https://wiki.archlinux.org/index.php/AUR#Searching it is possible to use mysql LIKE queries to search for a package.  But I can't find packages if I use queries with "%".
    For example, when I try to search for firefox%spell or firefox%spell%, I get nothing.
    I expected those queries would return the same results as firefox-spell.
    The question is: do LIKE queries work (or do I use them wrong)?
    Last edited by alezost (2014-02-13 08:14:08)

    It's not working from the web iterface, but cower does a good job:
    ~ > cower -s firefox spell
    aur/firefox-spell-en-us 7.0.1-2 (3)
    English (US) spellchecking dictionary for Firefox.
    aur/firefox-spell-es-es 1.7-1 (2)
    Spanish (Spain) spellchecking dictionary for Firefox.
    aur/firefox-spell-es-mx 1.1.3-3 (0)
    Spanish (Mexico) spellchecking dictionary for Firefox.
    aur/firefox-spell-pt-br 2.1.1-1 <!> (3)
    Brazilian Portuguese language dictionary (spellcheker) for Firefox
    aur/firefox-spell-ru-en 1.0.0.1-8 <!> (10)
    Russian/English spellchecker dictionary for Firefox
    aur/mozvoikko 2.0.1-9 (4)
    Finnish spell-checker extension for Firefox/thunderbird/seamonkey using Voikko

  • Official packages "required by" search for AUR packages

    I often want to see which aur packages depend on a given official package.
    e.g. recently to see that qt5-webengine is being used by something (qupzilla-git),
    but most often to see if I might later regret updating to a git version
    because there are interesting packages that depend on released versions.
    My current understanding is that to do this I would have to clone http://pkgbuild.com/git/aur-mirror.git/
    and then grep -r pkgname.
    Does anyone have a better way?

    AUR is pretty big.
    http://pkgbuild.com/git/aur-mirror.git/ … ter.tar.xz is 120 MB but it decompresses into 1.2 GB on disk. I'd recommend using an efficient searching method unless you want to wait ... and wait ... and wait. And then you run out of memory ;P
    AUR 4.0 is git-based, so maybe they'll include something like this. Ask on the ML, if you want.
    AUR packages that depend on qt5-webengine:
    j8-git
    qupzilla-git
    mist
    The snapshot has 70k package directories, 15k more than the current AUR, so you get some false positives when grepping (i.e. packages that aren't available anymore).

  • Source of the address for output type ZCOO(Certificate of origin)?

    Hi,
    I have to locate the source of the address field in the output type ZCOO-Certificate of Origin ,in transaction VF03. I got the sap script name from TNAPR table as Z_SD_EXPORT_FUCO and address field had the the values from V55ENAFT-ZZ_PL_STRAS but i cant find from which table this values is being retrieved in the corresponding print program RVADAUS1.Could anyone help track this?

    Hi,
      why cant you look for whre-used list for that custom field? or there should be user exit / Badi.
    Regards,
    ~Satya

  • Remove init.d debian script for AUR package

    I would like to make a new package for HQplayer network audio daemon.
    I have made this PKGBUILD (where init.d is removed from debian package and a new systemd service is added).
    Is this correct?
    pkgname=hqplayer-network-audio-daemon
    _debpkgver=2.0.5
    pkgver=$_debpkgver
    pkgrel=1
    pkgdesc="Signalyst Network Audio Daemon"
    arch=('x86_64')
    url="http://www.signalyst.com/"
    license=('Proprietary')
    depends=('alsa-lib')
    source=("http://www2.signalyst.com/bins/naa/debian_wheezy/networkaudiod_2.0.5-20_i386.deb" '[email protected]')
    sha256sums=('369bc3379b11fb05813567d47278f8f24711bb5240269ec725c8f17adecf1a21' '083a3080512283cf43930ad54749cee14a21bed5fc1596e63cce4482e1aeed96')
    package() {
    cd "$srcdir"
    bsdtar xf data.tar.gz -C "$pkgdir"
    install -Dm644 "[email protected]" \
    "$pkgdir/usr/lib/systemd/system/[email protected]"
    rm -r "$pkgdir/etc/init.d"

    Sorry but it is not an "opaque binary from an unknown source": network audio daemon is made by Jussi Laako, a very well known expert in audio digital conversion, known on the net by "miska" (see the posts at computeraudiophile.com for example).
    And yes, it is working very well. HQplayer play an audio file in one computer and  network audio daemon reproduce it in another.  There is a version of HQplayer for linux that will work for 30 minutes without buying the licence.
    I will make a package also of HQplayer as soon as possible, since the network daemon will not work without it
    For the licence I guess that I could change to 'unknown'
    Here is a copy of debian control file:
    Package: networkaudiod
    Version: 2.0.5-20
    Architecture: i386
    Maintainer: Jussi Laako <[email protected]>
    Installed-Size: 319
    Pre-Depends: debconf
    Depends: libasound2 (>= 1.0.16), libc6 (>= 2.4), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), debconf (>= 0.5) | debconf-2.0
    Priority: extra
    Homepage: http://www.signalyst.com/consumer.html
    Description: Signalyst Network Audio Daemon
    Signalyst Network Audio Daemon is a light weight server for asynchronous
    network audio stream playback. It is an implementation of Signalyst
    Network Audio Adapter protocol.
    Last edited by hifi25nl (2014-06-19 08:11:26)

  • What's the problem for this package????

    My Package is :
    CREATE OR REPLACE PACKAGE MY_PAQ IS
    TYPE RESULT IS REF CURSOR;
    FUNCTION MY_FUN
    RETURN RESULT;
    END MY_PAQ;
    CREATE OR REPLACE PACKAGE BODY MY_PAQ IS
    FUNCTION MY_FUN
    RETURN RESULT
    IS
    C RESULT;
    BEGIN
    OPEN C FOR SELECT * FROM MY_TAB;
    RETURN C;
    END MY_FUN;
    END MY_PAQ;
    SQL> SELECT MY_PAQ.MY_FUN FROM DUAL;
    SELECT MY_PAQ.MY_FUN FROM DUAL
    ERROR at line 1:
    ORA-00902: invalid datatype
    I like that my function returns a set of rows from a table(s)
    thanks in advance
    Mario

    Mario,
    Package seems okay. However since the function returns an open cursor, one suggested option is as follows:
    sqlplus > variable test_cursor refcursor;
    use this bind variable and call the function
    sqlplus > exec :test_cursor := MY_PAQ.MY_FUN;
    sqlplus > print test_cursor;
    <BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Mario Alberto Suarez ([email protected]):
    My Package is :
    CREATE OR REPLACE PACKAGE MY_PAQ IS
    TYPE RESULT IS REF CURSOR;
    FUNCTION MY_FUN
    RETURN RESULT;
    END MY_PAQ;
    CREATE OR REPLACE PACKAGE BODY MY_PAQ IS
    FUNCTION MY_FUN
    RETURN RESULT
    IS
    C RESULT;
    BEGIN
    OPEN C FOR SELECT * FROM MY_TAB;
    RETURN C;
    END MY_FUN;
    END MY_PAQ;
    SQL> SELECT MY_PAQ.MY_FUN FROM DUAL;
    SELECT MY_PAQ.MY_FUN FROM DUAL
    ERROR at line 1:
    ORA-00902: invalid datatype
    I like that my function returns a set of rows from a table(s)
    thanks in advance
    Mario<HR></BLOCKQUOTE>
    null

  • When the update for iPhone Packager will be available??

    Anybody has any idea, when the new update will be available of iPhone packager? Does new update will be able to interact with the iPhone OS to load the images from the Camera Roll, if internet connection is available, message notification, badges etc...

    I think the iPad 2 is great news for us.  The amount of apps make with Flash that are on the store have proved that it can work.  We just hit a bit of a performance wall currently.  Now that the iPad 2 is dual core however we should be bale to expect much better performance.  Of course true Objective C programming will always be more efficient but my point is that soon the quality difference between Objective C and the ios packager is going to be more transparent.
    My only hope is that this doesn't discourage people from continusing to optimize their code.  The one thing that has plagued Flash over the years has been sloppy code which I myself am partially guilty for I guess.  The ios packager has forced many of us to learn the proper way of doing things.
    Of course we have awhile before we can expect a perfect world.  There are a lot of iPad 1's out there yet and it will be a few years before we can target only the iPad 2.
    Finally I would love to see the ios packager expanded on.  I think what Adobe is doing has been a good start.  Of course we did hit that 6 month roadblock but now that we are back on track I hope to see the packager expanded to support more ios features.

  • Cannot retrieve aur packages installed with yaourt

    I accidently deleted /var/lib/pacman folder while attempting to solve my update issues (updating system after a long time) . I restored my local pacman database with the excellent guide in the wiki using /var/log/pacman.log  http://wiki.archlinux.org/index.php/Pac … l_database. I was able to update and restore my system. However, yaourt is not listing my installed aur packages. I re-installed yaourt and tried packer as well but it is not able to find the aur packages I installed using yaourt earlier to my update ( It is able to install and list new aur packages) . I can run the old aur packages  but I am not able to remove or list them. How can I list these lost aur packages or remove them completely? Is there a way to retrieve the database for aur packages installed with yaourt?
    Thanks.

    Hi karol,
    Thanks for your response.
    Executing pacman -Qm only lists aur packages which were installed after I accidently deleted /var/lib/pacman. I am not able to list those aur packages that I installed with yaourt prior to my /var/lib/pacman deletion. I am not sure how the accidental deletion and this issue is related, but I would like to delete these old aur packages. One example of such an aur package installed through yaourt (prior to blunder of /var/lib/pacman deletion ) was chromium-browser. I am able to run chromium-browser, but since this package is very old I would like to remove it. However, neither pacman nor yaourt is able to remove it.
    # pacman -R chromium-browser
    chromium-browser not found, searching for group...
    error: 'chromium-browser': not found in local db
    $ yaourt -R chromium-browser
    You are not allowed to launch /usr/bin/pacman with sudo
    Please enter root password
    Password:
    chromium-browser not found, searching for group...
    error: 'chromium-browser': not found in local db
    However chromium-browser is present on my system and runs very well.
    $ locate chromium-browser
    /etc/chromium-browser
    /etc/chromium-browser/default
    /opt/chromium-browser
    /opt/chromium-browser/chrome
    /opt/chromium-browser/chrome-wrapper
    /opt/chromium-browser/chrome.pak
    /opt/chromium-browser/chrome_sandbox
    /opt/chromium-browser/libffmpegsumo.so
    /opt/chromium-browser/locales
    /opt/chromium-browser/product_logo_48.png
    /opt/chromium-browser/resources
    /opt/chromium-browser/xdg-settings
    /opt/chromium-browser/locales/am.pak
    /opt/chromium-browser/locales/ar.pak
    /opt/chromium-browser/locales/bg.pak
    /opt/chromium-browser/locales/bn.pak
    /opt/chromium-browser/locales/ca.pak
    /opt/chromium-browser/locales/cs.pak
    /opt/chromium-browser/locales/da.pak
    /opt/chromium-browser/locales/de.pak
    /opt/chromium-browser/locales/el.pak
    /opt/chromium-browser/locales/en-GB.pak
    /opt/chromium-browser/locales/en-US.pak
    /opt/chromium-browser/locales/es-419.pak
    /opt/chromium-browser/locales/es.pak
    /opt/chromium-browser/locales/et.pak
    /opt/chromium-browser/locales/fi.pak
    /opt/chromium-browser/locales/fil.pak
    /opt/chromium-browser/locales/fr.pak
    /opt/chromium-browser/locales/gu.pak
    /opt/chromium-browser/locales/he.pak
    /opt/chromium-browser/locales/hi.pak
    /opt/chromium-browser/locales/hr.pak
    /opt/chromium-browser/locales/hu.pak
    /opt/chromium-browser/locales/id.pak
    /opt/chromium-browser/locales/it.pak
    /opt/chromium-browser/locales/ja.pak
    /opt/chromium-browser/locales/kn.pak
    /opt/chromium-browser/locales/ko.pak
    /opt/chromium-browser/locales/lt.pak
    /opt/chromium-browser/locales/lv.pak
    /opt/chromium-browser/locales/ml.pak
    /opt/chromium-browser/locales/mr.pak
    /opt/chromium-browser/locales/nb.pak
    /opt/chromium-browser/locales/nl.pak
    /opt/chromium-browser/locales/or.pak
    /opt/chromium-browser/locales/pl.pak
    /opt/chromium-browser/locales/pt-BR.pak
    /opt/chromium-browser/locales/pt-PT.pak
    /opt/chromium-browser/locales/ro.pak
    /opt/chromium-browser/locales/ru.pak
    /opt/chromium-browser/locales/sk.pak
    /opt/chromium-browser/locales/sl.pak
    /opt/chromium-browser/locales/sr.pak
    /opt/chromium-browser/locales/sv.pak
    /opt/chromium-browser/locales/sw.pak
    /opt/chromium-browser/locales/ta.pak
    /opt/chromium-browser/locales/te.pak
    /opt/chromium-browser/locales/th.pak
    /opt/chromium-browser/locales/tr.pak
    /opt/chromium-browser/locales/uk.pak
    /opt/chromium-browser/locales/vi.pak
    /opt/chromium-browser/locales/zh-CN.pak
    /opt/chromium-browser/locales/zh-TW.pak
    /opt/chromium-browser/resources/inspector
    /opt/chromium-browser/resources/inspector/Images
    /opt/chromium-browser/resources/inspector/devtools.css
    /opt/chromium-browser/resources/inspector/devtools.html
    /opt/chromium-browser/resources/inspector/devtools.js
    /opt/chromium-browser/resources/inspector/inspector.css
    /opt/chromium-browser/resources/inspector/inspector.html
    /opt/chromium-browser/resources/inspector/inspectorSyntaxHighlight.css
    /opt/chromium-browser/resources/inspector/Images/back.png
    /opt/chromium-browser/resources/inspector/Images/checker.png
    /opt/chromium-browser/resources/inspector/Images/clearConsoleButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/closeButtons.png
    /opt/chromium-browser/resources/inspector/Images/consoleButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/consoleIcon.png
    /opt/chromium-browser/resources/inspector/Images/cookie.png
    /opt/chromium-browser/resources/inspector/Images/database.png
    /opt/chromium-browser/resources/inspector/Images/databaseTable.png
    /opt/chromium-browser/resources/inspector/Images/debuggerContinue.png
    /opt/chromium-browser/resources/inspector/Images/debuggerPause.png
    /opt/chromium-browser/resources/inspector/Images/debuggerStepInto.png
    /opt/chromium-browser/resources/inspector/Images/debuggerStepOut.png
    /opt/chromium-browser/resources/inspector/Images/debuggerStepOver.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallDown.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallDownBlack.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallDownWhite.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRight.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightBlack.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightDown.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightDownBlack.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightDownWhite.png
    /opt/chromium-browser/resources/inspector/Images/disclosureTriangleSmallRightWhite.png
    /opt/chromium-browser/resources/inspector/Images/dockButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/elementsIcon.png
    /opt/chromium-browser/resources/inspector/Images/enableOutlineButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/enableSolidButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/errorIcon.png
    /opt/chromium-browser/resources/inspector/Images/errorMediumIcon.png
    /opt/chromium-browser/resources/inspector/Images/errorRedDot.png
    /opt/chromium-browser/resources/inspector/Images/excludeButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/focusButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/forward.png
    /opt/chromium-browser/resources/inspector/Images/glossyHeader.png
    /opt/chromium-browser/resources/inspector/Images/glossyHeaderPressed.png
    /opt/chromium-browser/resources/inspector/Images/glossyHeaderSelected.png
    /opt/chromium-browser/resources/inspector/Images/glossyHeaderSelectedPressed.png
    /opt/chromium-browser/resources/inspector/Images/goArrow.png
    /opt/chromium-browser/resources/inspector/Images/graphLabelCalloutLeft.png
    /opt/chromium-browser/resources/inspector/Images/graphLabelCalloutRight.png
    /opt/chromium-browser/resources/inspector/Images/grayConnectorPoint.png
    /opt/chromium-browser/resources/inspector/Images/largerResourcesButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/localStorage.png
    /opt/chromium-browser/resources/inspector/Images/nodeSearchButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/paneBottomGrow.png
    /opt/chromium-browser/resources/inspector/Images/paneBottomGrowActive.png
    /opt/chromium-browser/resources/inspector/Images/paneGrowHandleLine.png
    /opt/chromium-browser/resources/inspector/Images/paneSettingsButtons.png
    /opt/chromium-browser/resources/inspector/Images/pauseOnExceptionButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/percentButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/profileGroupIcon.png
    /opt/chromium-browser/resources/inspector/Images/profileIcon.png
    /opt/chromium-browser/resources/inspector/Images/profileSmallIcon.png
    /opt/chromium-browser/resources/inspector/Images/profilesIcon.png
    /opt/chromium-browser/resources/inspector/Images/profilesSilhouette.png
    /opt/chromium-browser/resources/inspector/Images/radioDot.png
    /opt/chromium-browser/resources/inspector/Images/recordButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/recordToggledButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/reloadButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/resourceCSSIcon.png
    /opt/chromium-browser/resources/inspector/Images/resourceDocumentIcon.png
    /opt/chromium-browser/resources/inspector/Images/resourceDocumentIconSmall.png
    /opt/chromium-browser/resources/inspector/Images/resourceJSIcon.png
    /opt/chromium-browser/resources/inspector/Images/resourcePlainIcon.png
    /opt/chromium-browser/resources/inspector/Images/resourcePlainIconSmall.png
    /opt/chromium-browser/resources/inspector/Images/resourcesIcon.png
    /opt/chromium-browser/resources/inspector/Images/resourcesSilhouette.png
    /opt/chromium-browser/resources/inspector/Images/resourcesSizeGraphIcon.png
    /opt/chromium-browser/resources/inspector/Images/resourcesTimeGraphIcon.png
    /opt/chromium-browser/resources/inspector/Images/scriptsIcon.png
    /opt/chromium-browser/resources/inspector/Images/scriptsSilhouette.png
    /opt/chromium-browser/resources/inspector/Images/searchSmallBlue.png
    /opt/chromium-browser/resources/inspector/Images/searchSmallBrightBlue.png
    /opt/chromium-browser/resources/inspector/Images/searchSmallGray.png
    /opt/chromium-browser/resources/inspector/Images/searchSmallWhite.png
    /opt/chromium-browser/resources/inspector/Images/segment.png
    /opt/chromium-browser/resources/inspector/Images/segmentChromium.png
    /opt/chromium-browser/resources/inspector/Images/segmentEnd.png
    /opt/chromium-browser/resources/inspector/Images/segmentHover.png
    /opt/chromium-browser/resources/inspector/Images/segmentHoverChromium.png
    /opt/chromium-browser/resources/inspector/Images/segmentHoverEnd.png
    /opt/chromium-browser/resources/inspector/Images/segmentHoverEndChromium.png
    /opt/chromium-browser/resources/inspector/Images/segmentSelected.png
    /opt/chromium-browser/resources/inspector/Images/segmentSelectedChromium.png
    /opt/chromium-browser/resources/inspector/Images/segmentSelectedEnd.png
    /opt/chromium-browser/resources/inspector/Images/segmentSelectedEndChromium.png
    /opt/chromium-browser/resources/inspector/Images/sessionStorage.png
    /opt/chromium-browser/resources/inspector/Images/splitviewDimple.png
    /opt/chromium-browser/resources/inspector/Images/splitviewDividerBackground.png
    /opt/chromium-browser/resources/inspector/Images/statusbarBackground.png
    /opt/chromium-browser/resources/inspector/Images/statusbarBackgroundChromium.png
    /opt/chromium-browser/resources/inspector/Images/statusbarBottomBackground.png
    /opt/chromium-browser/resources/inspector/Images/statusbarBottomBackgroundChromium.png
    /opt/chromium-browser/resources/inspector/Images/statusbarButtons.png
    /opt/chromium-browser/resources/inspector/Images/statusbarButtonsChromium.png
    /opt/chromium-browser/resources/inspector/Images/statusbarMenuButton.png
    /opt/chromium-browser/resources/inspector/Images/statusbarMenuButtonChromium.png
    /opt/chromium-browser/resources/inspector/Images/statusbarMenuButtonSelected.png
    /opt/chromium-browser/resources/inspector/Images/statusbarMenuButtonSelectedChromium.png
    /opt/chromium-browser/resources/inspector/Images/statusbarResizerHorizontal.png
    /opt/chromium-browser/resources/inspector/Images/statusbarResizerVertical.png
    /opt/chromium-browser/resources/inspector/Images/storageIcon.png
    /opt/chromium-browser/resources/inspector/Images/successGreenDot.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarBlue.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarGray.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarGreen.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarOrange.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarPurple.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarRed.png
    /opt/chromium-browser/resources/inspector/Images/timelineBarYellow.png
    /opt/chromium-browser/resources/inspector/Images/timelineCheckmarks.png
    /opt/chromium-browser/resources/inspector/Images/timelineDots.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillBlue.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillGray.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillGreen.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillOrange.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillPurple.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillRed.png
    /opt/chromium-browser/resources/inspector/Images/timelineHollowPillYellow.png
    /opt/chromium-browser/resources/inspector/Images/timelineIcon.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillBlue.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillGray.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillGreen.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillOrange.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillPurple.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillRed.png
    /opt/chromium-browser/resources/inspector/Images/timelinePillYellow.png
    /opt/chromium-browser/resources/inspector/Images/tipBalloon.png
    /opt/chromium-browser/resources/inspector/Images/tipBalloonBottom.png
    /opt/chromium-browser/resources/inspector/Images/tipIcon.png
    /opt/chromium-browser/resources/inspector/Images/tipIconPressed.png
    /opt/chromium-browser/resources/inspector/Images/toolbarItemSelected.png
    /opt/chromium-browser/resources/inspector/Images/treeDownTriangleBlack.png
    /opt/chromium-browser/resources/inspector/Images/treeDownTriangleWhite.png
    /opt/chromium-browser/resources/inspector/Images/treeRightTriangleBlack.png
    /opt/chromium-browser/resources/inspector/Images/treeRightTriangleWhite.png
    /opt/chromium-browser/resources/inspector/Images/treeUpTriangleBlack.png
    /opt/chromium-browser/resources/inspector/Images/treeUpTriangleWhite.png
    /opt/chromium-browser/resources/inspector/Images/undockButtonGlyph.png
    /opt/chromium-browser/resources/inspector/Images/userInputIcon.png
    /opt/chromium-browser/resources/inspector/Images/userInputPreviousIcon.png
    /opt/chromium-browser/resources/inspector/Images/userInputResultIcon.png
    /opt/chromium-browser/resources/inspector/Images/warningIcon.png
    /opt/chromium-browser/resources/inspector/Images/warningMediumIcon.png
    /opt/chromium-browser/resources/inspector/Images/warningOrangeDot.png
    /opt/chromium-browser/resources/inspector/Images/warningsErrors.png
    /opt/chromium-browser/resources/inspector/Images/whiteConnectorPoint.png
    /usr/bin/chromium-browser
    /usr/share/applications/chromium-browser.desktop
    /usr/share/licenses/chromium-browser-bin
    /usr/share/licenses/chromium-browser-bin/LICENSE.txt
    /usr/share/man/man1/chromium-browser.1.gz
    /usr/share/pixmaps/chromium-browser.png
    Chromium-browser is just one of the packages I remember having installed using yaourt prior to the /var/lib/pacman deletion. I would like to know if there is a way to find all such aur packages installed through yaourt prior to /var/lib/pacman deletion and if possible, delete them.
    Thanks.
    Last edited by billy123 (2010-04-05 16:35:35)

  • [yaourt] Keep sources/build files only for specific AUR packages

    Hi,
    By default, packages are build in BUILDDIR=/tmp/makepkg, which itself usually is a virtual dir in RAM. I generally like this behaviour, so I don't wanna change the BUILDDIR variable to point to a dir on the harddisk, but for a few packages I'd welcome the sources/build dir to be kept, e.g. for *-git packages to reduce build time on consecutive updates. Is there a neat Arch-way to tell the makepkg system to use a different dir (i.e., one on the harddisk) for specific packages? It'd be even greater to be able to use wildcards as well, so I could just enable this option for all *-git packages.
    And as I said, I generally like the idea of building in RAM so the trick to just let BUILDDIR point to a dir on my hdd and put a command in some shutdown-script to delete all but the directories ending in -git wouldn't be perfect
    Cheers
    Last edited by epinephrine (2013-01-27 16:25:17)

    Oh you're right in that BUILDDIR isn't set by default. I use yaourt for building AUR packages, so this is a yaourt related question, oops. I'll ask in the appropriate forum...
    Some packages are only available as git packages, and that for a good reason. Some git repository maintainers follow the good working principle to always have their master branch stable and deployable and do development and testing in respective branches to keep master clean. E.g. I maintain 2 git packages on the AUR, and there are no other "stable" options, also as git makes sense for these packages.
    And sometimes you just need a more up2date version

  • Are AUR packages signed? How do I check the signature if they are?

    Hi,
    Are AUR packages signed? How do I check the signature if they are?
    Thank you!

    andreicristianpetcu wrote:Thank you for your answers! Some Aur packages basically wget some tar.gz and uncompress it and I wanted to know if there is a way to test if this is the same archive that I wanted to install.
    Archives downloaded by PKGBUILDs are never the same as the archive you want to install. Are you referring to PKGBUILDs which just repackage .deb or .rpm archives? As mentioned, there's checksums (typically of zero benefit to security), and sometimes GPG signatures provided by upstream. But, this is only a part of the process. The attack surface is wider than just the source tarball and the PKGBUILD. Consider that you don't even need a PKGBUILD to create a package which pacman understands.
    andreicristianpetcu wrote:I told him that this cannot be done on most packages on most GNU/Linux distros.
    No, it absolutely can. All operating systems are prone to attack by social engineering and can fall victim to lax system administration. The "Linux doesn't get virii" mantra is a falsehood propagated by people relying on statistics rather than actual operating system features and security practices.
    andreicristianpetcu wrote:Since I am a Arch user I wanted to find out if there is a way (except for reading the pkgbuild) from which I can check the validity of the package.
    Given an arbitrary archive foo-1-1-x86_64.pkg.tar.xz, there is absolutely no way to determine what PKGBUILD was used to build it. This is a key reason why signing binary packages in the repositories is important!
    andreicristianpetcu wrote:From what I know the files from the other repos are signed (correct me if I'm wrong).
    Right, in order to assert provenance of a package. If the signature for a package is valid, you can assume that you have a copy of the package which a developer or TU built.

  • Package Manager for AUR

    With Chakra you can install the CCR ( the same as AUR) packages with Package Manager. We should be pleased if this is possible with Arch.

    Please, don't forget to mark the thread [SOLVED].
    P.S.: Make friends with Arch Wiki and forum search button: they are really a great source of information.
    Last edited by bohoomil (2012-04-02 16:58:00)

  • The "nvidia-beta-ck" aur package and the "linux-ck" package issue?

    I use the linux-ck unofficail repo to install the BFQ scheduler enabled kernel.  Today it upgraded to the 3.8.8 and it updated fine but the 319 nvidia beta drivers weren't installed after the update.  So I reinstalled the nvidia-beta aur package and everything was fine.  Is there a way for it to automatically hook the nvidia drivers into the kernel -- say with dkms or will I need to re-install the drivers everytime the kernel updates.

    I think there's an nvidia-all package in the AUR no?  You can probably modify that to work with the beta package.

  • How to inspect AUR package PKBUILD and .install files

    Hi,
    Linux and arch newbie here. I was reading the wiki article about the AUR and noticed this bit:
    Warning: Carefully check all files. cd to the newly created directory and carefully check the PKGBUILD and any .install file for malicious commands. PKGBUILDs are bash scripts containing functions to be executed by makepkg: these functions can contain any valid commands or Bash syntax, so it is totally possible for a PKGBUILD to contain dangerous commands through malice or ignorance on the part of the author. Since makepkg uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list.
    This is something that have not been doing at all in the past, but I am trying to improve my practices managing my system.
    The problem is, I do not know what exactly I am looking at or for in these files. If I give these files a look over before installing the package, can I honestly expect to spot something malicious? What would I need to learn to notice if something was fishy?
    Anyway, I am not to worried about this practically, because I only use a handful of AUR packages and I usually install ones based on recommendations, not just at random. But it still seemed interesting for the wiki to stress this so strongly. How important is this guidline anyway?
    Thanks!
    [EDIT: spelling]
    Last edited by supernerd (2014-06-25 10:41:13)

    I scan the whole PKGBUILD. I start by ensuring that the source link to the original source looks accurate. For example, take the source line for gmusicbrowser-git:
    source=("${pkgname}::git+http://github.com/squentin/gmusicbrowser.git")
    I know this is the correct link to the source, and so it passes my check. But suppose it had said:
    source=("${pkgname}::git+http://youvebeenhackedhub.com/1337haxorz/gmusicbrowser.git")
    I would become suspicious. Of course this is an exaggeration, but common sense goes a long ways here. At least check the first time..
    With the source verified, I ensure that the md5sum or sha256sum block has a sum. This way, if a download is compromised at the source, the sha256 or md5sum can catch it before you installed (this assumes that the PKGBUILD is not "bad" and has the sum number of a package that wasnt compromised). Note that with git this isnt necessary (the git process protects against such problems). Anytime a tarball is downloaded and extracted however, the sums should be present in the PKGBUILD. If I go to install an AUR package that has 'SKIP' for the md5sum/sha256sum block, I will double or triple check the source of the tarball (or of the patch files enclosed in the build directory, etc..)
    I also look for any "dangerous" commands in the build and install sections. For example, if I see "rm -rf" I had better see something like $pkgdir to start the directory path or be VERY sure the path is "safe". Since makepkg is not run as root this should theoretically not be a problem, but imagine if someone put "rm -rf /home/*" (warning: do not run that command on your system!) in there! This is mostly common sense; in time as you get more comfortable with bash and various linux commands it will make more and more sense and you will be able to spot mistakes.
    Also, consider the user posting the pkgbuild. "Trusted Users" are selected as trustworthy members of the community, so obviously you can feel much more comfortable with PKGBUILDS they have made (Xyne comes to mind..). For people you may not know, check what other PKGBUILDs they have available. After awhile, you develop a trust for certain people whos PKGBUILDs or software you have used. For example, I wouldnt hesitate to build/install using a PKGBUILD put up by BurntSushi since I use some of his software, have personally corresponded with him, and find him to be responsible. You might "develop" such rapport with other AUR users I dont even know about.
    Consider the vote count of a package as an approximate metric. Dont discount a package because it has 0 votes- it may just be that not many people have use for that particular software. Ive considered hosting a PKGBUILD for "xfce4-terminal-nowindowhints"; consider that tilers generally ignore them anyway, and that my package would only be useful for someone literally using xfce4-terminal with pytyle. How high do you think the vote count would be (even if the PKGBUILD had 0 errors)? On the other hand, you at least have a good chance the PKGBUILD is solid if the package has 354 people voting for it.. That said, the package could have been well-maintained before (when it received a ton of votes), and the quality has dropped since- just be mindful of these trends.
    Finally, adding all of these things together will leave the odds of a malicious PKGBUILD affecting your system pretty slim, though its certainly not impossible. I have never (to my knowledge to be fair) encountered a malicious PKGBUILD, though I have found a few that had errors or outdated sources, etc.
    Last edited by GSF1200S (2014-06-29 10:13:50)

  • Sticky bit in unsupported AUR packages

    Hello,
    In my ventures to provide a PKGBUILD for an app called gnump3d, I've come across something with the unsupported (only?) build script packages in AUR that can cause some problems.
    Here is an (one) example of such a package:
    $ wget --quiet aur.archlinux.org/packages/tomcat/tomcat.tar.gz
    $ tar tvzf tomcat.tar.gz
    drwxr-sr-x nobody/aur 0 2006-06-27 02:50:53 tomcat/
    -rw-r--r-- nobody/aur 938 2006-06-27 02:49:10 tomcat/PKGBUILD
    -rw-r--r-- nobody/aur 415 2005-06-16 20:11:45 tomcat/tomcat.conf.d
    -rwxr-xr-x nobody/aur 706 2005-06-16 20:11:12 tomcat/tomcat
    Notice the owner, group and the sticky bit on the directory. These permissions seem to be standard for the AUR build script packages.
    Now, if use aurbuild to build this package, I get this content in the package:
    drwxr-sr-x root/root 0 2006-08-08 01:48:05 etc/
    drwxr-sr-x root/root 0 2006-08-08 01:48:05 etc/rc.d/
    -rwxr-xr-x root/root 706 2006-08-08 01:48:05 etc/rc.d/tomcat
    drwxr-sr-x root/root 0 2006-08-08 01:48:05 etc/conf.d/
    -rw-r--r-- root/root 415 2006-08-08 01:48:05 etc/conf.d/tomcat
    <SNIP>
    I'm pretty sure that these sticky bits weren't intended. If I build the package with yaourt, which uses srcpac as a backend, things get more troublesome:
    drwxr-sr-x root/549 0 2006-08-08 02:03:00 etc/
    drwxr-sr-x root/549 0 2006-08-08 02:03:00 etc/rc.d/
    -rwxr-xr-x root/549 706 2006-08-08 02:03:00 etc/rc.d/tomcat
    drwxr-sr-x root/549 0 2006-08-08 02:03:00 etc/conf.d/
    -rw-r--r-- root/549 415 2006-08-08 02:03:00 etc/conf.d/tomcat
    <SNIP>
    549 ought to be the group id of aur in the AUR repository.
    Careless usage of makepkg can also make this happen. Not building as root, but in a fakeroot environment, seems to prevent it from happen.
    From what I can see, the erroneous permissions are created when the install command is used in the PKGBUILD script, within the newly unpacked build script package.
    This is certainly not meant to bash the authors of aurbuild or yaourt (or tomcat; many PKGBUILDs use install, mine included), I just wanted to raise the issue. Can something be done about this? Don't know where, though. Removing the sticky bit on the directory in the build script package would be one solution. Or maybe makepkg could warn about erroneous permissions. Or... Or something? Is it a bug or a feature?
    Cheers

    Ok fixed aurbuild. Now it extracts the tarball from AUR into /tmp then copies it into the build dir which inherets the modes and owenership of the parent directory there (being $HOME), I'm pretty sure this is how tar does it.
    As pointed out above this setgid issue only occurred during root user builds.
    More info:
    -v1.5.1 (August 8, 2006)
    *Fixed inhereted setgid bit in the built the package resulting from AUR's set mode of the parent directory in the tarball.
    The unwanted inhereted bit occured only under the following circumstances:
    - user was root.
    - a 'install -m' line was excuted in the PKGBUILD without explicitly setting the first pair of octets, ie 644 instead of 0644
    - Any other type of 'chmod' command without the first octet set.
    If you have built any packages meeting the criteria list above, rebuild and install offending packages now. Run the update command to get the list of all
    packages built from AUR. String them together in a space separated line to aurbuild and use the menu to see if any install/chmod lines were used. You can
    use (s) from the menu to skip the current package and move on to the next.

Maybe you are looking for