Package Details: packettracer 7.3.1-3

Git Clone URL: (read-only, click to copy)
Package Base: packettracer
Description: Cisco PacketTracer 7.3.1 installation package
Upstream URL:
Licenses: custom
Submitter: Vamp898
Maintainer: runnytu
Last Packager: runnytu
Votes: 112
Popularity: 0.78
First Submitted: 2009-02-18 07:52
Last Updated: 2020-10-13 17:27

Pinned Comments

runnytu commented on 2020-01-04 16:58

To install all versions of packettracer except 7.2.2, follow this guidelines: 1. Download the snapshot from this AUR. 2. Tar -zxf the packettracer.tar.gz snapshot (it creates the dir packettracer/ with the PKGBUILD on it). 3. Download the latest packettracer tarball from your Netacad account and copy it into the packettracer/ dir. 4. Create the package with the command makepkg (it creates a packettracer.pkg.tar.xz). 5. Install the package with either makepkg -i or sudo pacman -U packettracer.pkg.tar.xz.

Packettracer 7.2.2 are auto installable via run file, download it from netacad webpage and run it, you don't need this package.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 ... Next › Last »

cfinnberg commented on 2020-07-29 19:55

If someone wants to use yay (package version 7.3.0):

yay -G packettracer
cd packettracer
curl -OL
sudo pacman -U packettracer-7.3.0-6-x86_64.pkg.tar.xz

xiretza commented on 2020-06-18 11:43

@bkb: stop it already. If you really want something to change, post a patch and we'll tell you why it violates AUR guidelines.

bkb commented on 2020-06-18 11:41

Second time, what are you talking about? yay is adapted to the AUR, it's this package who isn't adapted to AUR. For the second time, the "third party card" doesn't always work? And no, I don't have any problems with AUR PKGBUILD or makepkg, just with "local://PacketTracer_730_amd64.deb"

No they don't have to make it yay compliant, but AUR compliant, and here it's not

koatao commented on 2020-06-18 10:40

yay is not official, it is an AUR helper, therefor, yay should adapt to the AUR, not the other way around. If you have a problem with the way AUR, PKGBUILD, makepkg and so on are designed , then you make your case on the forum, mail, wiki (anywhere but here would be a better place). Obviously, maintainers does not have to make their AUR package yay compliant. READ the wiki (first line): They are NOT SUPPORTED. This package is compliant with the SUPPORTED way to do things. So yeah, i think your problem is with the way the supported way works, and not packettracer package in particular. So I invite you to start new forum post, so things discussed here are kept related to this package.

bkb commented on 2020-06-18 10:19

What are you talking about, it has nothing to do with yay, all packages works nicely with it. It's this package that it's not installable without manual intervention

Think a little before invoking dumbly the "third party" card

The problem will remain the same even if someday pacman develop something for AUR packages

koatao commented on 2020-06-18 09:59

@bkb Then your problem is with yay. And here is not the place to discuss about it. It has nothing to do with this package specifically.

bkb commented on 2020-06-18 09:19

@xiretza corrected

xiretza commented on 2020-06-17 17:45

pacman does not build packages. pacman will never build packages. there is nothing an AUR package can do to make pacman -Syu build it.

bkb commented on 2020-06-17 17:44

Like always

For me automatic = yay -Syu, everything else = non automatic

koatao commented on 2020-06-17 14:06

@bkb, no, you don't have to compile anything yourself to install version 7.3.0. You need 4 files before using makepkg: PKGBUILD of course, packettracer.install, and PacketTacer_730_amd64.deb.