شما نمی توانید بیش از 25 موضوع انتخاب کنید موضوع می‌بایستی با حروف یا شماره ها شروع شود. و می‌تواند شامل دَش ('-') باشد و طول آن تا 35 کارکتر نیز امکانپذیر است.
 
 
 
 
 
 
Dr. Ralf S. Engelschall ff6908c4de blind update of (perhaps still broken) Mozilla 24 سال پیش
00DEV adjust paths 24 سال پیش
a2ps require flex and bison 24 سال پیش
amd requires also bison 24 سال پیش
analog Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
antiword Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
apache Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
apg fix building 24 سال پیش
autoconf Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
autogen Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
automake Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
axyftp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
bash Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
bc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
bind Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
binutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
bison Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
boxes fix dependencies 24 سال پیش
bzip2 Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
c2man Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
calc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
cftp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
cpio Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
curl Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
cvs Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
cvsweb Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
db Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
dcron Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
delegate Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
dhcpd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
diffutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
dmalloc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
docbook Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
emacs Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
epm Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
exim Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
fetchmail Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
figlet Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
file Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
fileutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
findutils Fix installation procedure (determined by src2make) 24 سال پیش
flawfinder Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
flex switch back to the release version 24 سال پیش
freetype Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gated Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gawk Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gcc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gettext Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ghostscript Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gimp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
glib Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
glimpse Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gnupg Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
graphviz Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
grep Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
grepmail fixed group 24 سال پیش
groff Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gtk Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
guile Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gup Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
gzip Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
heise Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
hexer Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
htdig Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
html2latex Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
imagemagick Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
imapd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
imlib Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
indent Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
infozip Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
inn Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
instant Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
iozone Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ircd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ircii Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
iselect Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ispell Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
its4 fixed group 24 سال پیش
jitterbug Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
jpeg Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
kermit Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
lame Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
less Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
lftp upgrade to lftp 2.4.7 24 سال پیش
libiconv Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
libpcap Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
libtool Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
libxml Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
libxslt Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
limo Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
links Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
lmtp2nntp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
logsurfer Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
lrzsz Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
lsof Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
lynx Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
m4 Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
magicpoint Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mailgrep Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
majordomo Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
make Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
minicom Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mirror Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mkgallery Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mkisofs Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mm Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mng Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mozilla blind update of (perhaps still broken) Mozilla 24 سال پیش
mpack Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mpg123 Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mtools Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mutt Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
myodbc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
mysql Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
nail Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
nano Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ncftp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ncurses Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
netcat Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
nmap Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
nntpcache Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ntp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
openjade Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
openldap Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
openpkg fix bootstrap version 24 سال پیش
openssh Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
openssl fix compilation 24 سال پیش
orbit Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
par Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
patch Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
pcre Fix requirements (found by our src2make) 24 سال پیش
pdksh Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
perl Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
perl-gd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
perl-ssl Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
petidomo Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
pgp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
php Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
pinfo Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
png Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
portsentry Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
postfix upgrade unstable version 24 سال پیش
prngd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
procmail Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
proftpd Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
psutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
pth Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
pureftpd upgrade to pure-ftpd 1.0.3 24 سال پیش
python Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
qpopper Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
qt Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
rc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
rcs Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
recode Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
rfc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
rrdtool Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
rsync Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ruby Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
samba Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sasl Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
scanssh Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
screen Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sed Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sendmail Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sfio Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sgml Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sgmlfmt Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sharutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
shellutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
shiela Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
shtool Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
siege Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sitecopy Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
skey Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
slang Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
smtpfeed Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
snmp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
squid Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ssmtp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
str Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
strace Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
stunnel Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
suck Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
sudo Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tar Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tcl Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tcpdump Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tcsh Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
termutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tetex Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
texinfo upgrade to 4.0d because 4.0 fails on installation 24 سال پیش
textutils Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tiff Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
tin Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
txt2man Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
txt2pdf Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
txt2regex Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
units Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
unixodbc Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
ups Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
uucp Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
uudeview Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
vim Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
w3m Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
wget Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
whatmask Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
whois Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
wml Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
xdelta Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
xmake Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
xmame Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
xterm Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
zebra Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
zlib Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
zope Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
zsh Hmmmm.... goodbye good thought out but in practice unusable %{l_branch} variable. We have to use a static value here (implies manual editing again), because else source and binary RPM filenames won't match if binary is built one or more days after the source was rolled. 24 سال پیش
00README Initial revision 24 سال پیش