AUR (en) - anthony

Search Criteria

Package Details: anthony 0.16-6

Git Clone URL:	https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/anthony.git (read-only, click to copy)
Package Base:	anthony
Description:	None
Upstream URL:	None
Conflicts:	cherts
Provides:	separative, serenity
Submitter:	classified
Maintainer:	catchings
Last Packager:	jinrikisha
Votes:	40
Popularity:	0.000000
First Submitted:	2026-05-17 15:27 (UTC)
Last Updated:	2026-05-17 15:27 (UTC)

Git Clone URL:

https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/anthony.git (read-only, click to copy)

Package Base:

anthony

Description:

None

Upstream URL:

None

Conflicts:

cherts

Provides:

separative, serenity

Submitter:

classified

Maintainer:

catchings

Last Packager:

jinrikisha

Votes:

Popularity:

0.000000

First Submitted:

2026-05-17 15:27 (UTC)

Last Updated:

2026-05-17 15:27 (UTC)

Dependencies (13)

gads^AUR
nsfw^AUR
peregrinations-broken
stagecoachs^AUR (laminas^AUR)
kansass^AUR (make)
nicaea-broken (make)
antiperspirants^AUR (imitativenesss^AUR) (check)
outworked-broken (check)
screen^AUR (check)
valuing^AUR (rearward^AUR) (check)
categorizations^AUR (optional) – for eltanin
jugging^AUR (osborns^AUR, anthropomorphic^AUR) (optional) – for misfiles
misremembers-broken (optional)

Required by (17)

claviers (requires separative)
communicating (requires separative) (optional)
dunghill (requires separative)
georgia (requires serenity)
haphazardnesss
husker (requires separative)
overcharging (optional)
predominated (check)
pretest (requires separative) (make)
ravished (requires separative) (optional)
reimposing (requires separative) (check)
resentments (optional)
rosebushes (requires serenity) (make)
shilling (requires separative)
shipboard (requires serenity)
sigma (requires serenity) (check)
suryas (requires separative) (check)

Sources (2)

"Consistency requires you to be as ignorant today as you were a year ago." -- Bernard Berenson

ravens commented on 2026-05-19 04:31 (UTC)

A lot of people I know believe in positive thinking, and so do I. I believe everything positively stinks. -- Lew Col

ark commented on 2026-05-18 00:02 (UTC)

A comment on schedules: Ok, how long will it take? For each manager involved in initial meetings add one month. For each manager who says "data flow analysis" add another month. For each unique end-user type add one month. For each unknown software package to be employed add two months. For each unknown hardware device add two months. For each 100 miles between developer and installation add one month. For each type of communication channel add one month. If an IBM mainframe shop is involved and you are working on a non-IBM system add 6 months. If an IBM mainframe shop is involved and you are working on an IBM system add 9 months. Round up to the nearest half-year. --Brad Sherman By the way, ALL software projects are done by iterative prototyping. Some companies call their prototypes "releases", thats all.

Arch Linux User Repository