6:17 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Keywords:
--------------------+-------------------------------------------------------
Free hot issues, come and stop by!
Excerpt:
depcheck inputs:
{{{
Pending builds: ['PyKDE-3.16.6-7.fc14', 'PyQt-3.18.1-8.fc14',
'PyQt4-4.8.3-2.fc14', 'PyQwt-5.2.0-10.fc14',
'akonadi-1.5.1-1.fc14',
'attica-0.2.0-1.fc14', 'avogadro-1.0.1-11.fc14',
'backintime-1.0.6-1.fc14', 'calibre-0.7.38-3.fc14.2',
'calibre-0.7.38-4.fc14', 'digikam-1.9.0-1.fc14',
'jpilot-1.8.0-2.fc14',
'kde-i18n-3.5.10-14.fc14', 'kde-l10n-4.6.1-1.fc14.1',
'kde-plasma-smooth-
tasks-0.0.1-0.1.wip20101106.fc14.2', 'kde-plasma-yawp-0.3.6-1.fc14.2',
'kdeaccessibility-4.6.1-1.fc14', 'kdeadmin-4.6.1-1.fc14',
'kdeartwork-4.6.1-1.fc14', 'kdebase-4.6.1-3.fc14', 'kdebase-
runtime-4.6.1-1.fc14', 'kdebase-workspace-4.6.1-2.fc14',
'kdebindings-4.6.1-1.fc14', 'kdeedu-4.6.1-2.fc14',
'kdegames-4.6.1-1.fc14', 'kdegames3-3.5.10-9.fc14',
'kdegraphics-4.6.1-1.fc14', 'kdelibs-4.6.1-4.fc14',
'kdemultimedia-4.6.1-1.fc14', 'kdenetwork-4.6.1-2.fc14',
'kdepim-4.4.10-2.fc14', 'kdepim-runtime-4.4.10-2.fc14',
'kdepimlibs-4.6.1-1.fc14', 'kdeplasma-addons-4.6.1-1.fc14',
'kdesdk-4.6.1-1.fc14', 'kdetoys-4.6.1-1.fc14',
'kdeutils-4.6.1-1.fc14',
'kdevelop-4.2.0-2.fc14', 'kdevelop-php-1.2.0-2.fc14',
'kdevplatform-1.2.0-3.fc14', 'kicad-2011.01.28-1.rev2765.fc14',
'kipi-
plugins-1.9.0-1.fc14', 'koffice-2.3.3-1.fc14', 'konq-
plugins-4.6.1-1.fc14', 'kphotoalbum-4.1.1-7.fc14',
'ktorrent-4.1.0-1.fc14', 'libktorrent-1.1.0-1.fc14',
'nepomukcontroller-0.2-4.fc14', 'oxygen-icon-theme-4.6.1-1.fc14',
'perl-
Locale-US-1.2-2.fc14', 'perl-Math-Random-ISAAC-1.004-2.fc14',
'phonon-4.4.4-2.fc14', 'phonon-backend-gstreamer-4.4.4-2.fc14',
'phonon-
backend-xine-4.4.4-3.fc14', 'plowshare-0.9.4-0.5.svn1391.fc14',
'polkit-
kde-0.99.0-2.fc14', 'polkit-qt-0.99.0-2.fc14',
'qedje-0.4.0-8.fc14',
'qgis-1.6.0-3.fc14.1', 'qscintilla-2.4.6-2.fc14',
'qzion-0.4.0-10.fc14',
'sems-1.3.1-4.fc14.1', 'shared-desktop-ontologies-0.6.0-1.fc14',
'sip-4.12.1-4.fc14', 'soprano-2.6.0-2.fc14', 'thunarx-
python-0.2.3-3.fc14.1', 'veusz-1.9-2.fc14.1', 'wmtop-0.84-3.fc14']
}}}
depcheck outputs:
{{{
IGNORE: ktorrent-4.1.0-1.fc14.i686 plasma-scriptengine-
googlegadgets-4.6.1-2.fc14.x86_64 plasma-scriptengine-
python-4.6.1-2.fc14.x86_64 kdebase-workspace-ksplash-
themes-4.6.1-2.fc14.noarch kdebase-runtime-devel-4.6.1-1.fc14.x86_64
nepomukcontroller-0.2-4.fc14.x86_64 1:kde-i18n-3.5.10-14.fc14.noarch kde-
l10n-Maithili-4.6.1-1.fc14.1.noarch plasma-scriptengine-
ruby-4.6.1-2.fc14.x86_64 kdebase-runtime-devel-4.6.1-1.fc14.i686
REJECT:
ACCEPT: 7:kdenetwork-devel-4.6.1-2.fc14.x86_64 attica-
devel-0.2.0-1.fc14.x86_64 attica-devel-0.2.0-1.fc14.i686 qzion-
devel-0.4.0-10.fc14.i686 kde-l10n-Portuguese-4.6.1-1.fc14.1.noarch phonon-
devel-4.4.4-2.fc14.i686 3:koffice-kplato-libs-2.3.3-1.fc14.i686 polkit-qt-
doc-0.99.0-2.fc14.noarch 7:kdenetwork-devel-4.6.1-2.fc14.i686
sems-g722-1.3.1-4.fc14.1.x86_64 qscintilla-devel-2.4.6-2.fc14.i686 shared-
desktop-ontologies-0.6.0-1.fc14.noarch kdepimlibs-4.6.1-1.fc14.x86_64 1
:kde-i18n-Japanese-3.5.10-14.fc14.noarch kde-l10n-
Ukrainian-4.6.1-1.fc14.1.noarch php-qt-devel-4.6.1-1.fc14.x86_64 sems-
xmlrpc2di-1.3.1-4.fc14.1.x86_64 kde-l10n-Thai-4.6.1-1.fc14.1.noarch
kphotoalbum-4.1.1-7.fc14.x86_64 kdeedu-math-cantor-R-4.6.1-2.fc14.x86_64
kdeedu-marble-libs-4.6.1-2.fc14.i686 kdevplatform-1.2.0-3.fc14.i686 kde-
l10n-LowSaxon-4.6.1-1.fc14.1.noarch qgis-grass-1.6.0-3.fc14.1.i686 1:kde-
i18n-Danish-3.5.10-14.fc14.noarch kde-l10n-Brazil-4.6.1-1.fc14.1.noarch 1
:kde-i18n-Lithuanian-3.5.10-14.fc14.noarch kdevplatform-
devel-1.2.0-3.fc14.i686 soprano-2.6.0-2.fc14.x86_64 qzion-python-
devel-0.4.0-10.fc14.i686 kdeedu-math-libs-4.6.1-2.fc14.i686
libktorrent-1.1.0-1.fc14.i686 1:kdepim-runtime-libs-4.4.10-2.fc14.i686 7
:kdepim-devel-4.4.10-2.fc14.i686 kdm-4.6.1-2.fc14.x86_64 kipi-
plugins-1.9.0-1.fc14.x86_64 PyQwt-devel-5.2.0-10.fc14.x86_64 sems-
speex-1.3.1-4.fc14.1.x86_64 kdeplasma-addons-devel-4.6.1-1.fc14.x86_64
oxygen-icon-theme-4.6.1-1.fc14.noarch 6:kdebase-devel-4.6.1-3.fc14.x86_64
kde-l10n-Hindi-4.6.1-1.fc14.1.noarch 7:kdepim-libs-4.4.10-2.fc14.i686
PyKDE-3.16.6-7.fc14.x86_64 backintime-gnome-1.0.6-1.fc14.noarch
9:kdevelop-4.2.0-2.fc14.x86_64 qzion-0.4.0-10.fc14.x86_64 ktorrent-
libs-4.1.0-1.fc14.i686 1:kde-i18n-Arabic-3.5.10-14.fc14.noarch kde-l10n-
Danish-4.6.1-1.fc14.1.noarch qzion-python-0.4.0-10.fc14.x86_64 6
:kdemultimedia-libs-4.6.1-1.fc14.x86_64 6:kdebase-devel-4.6.1-3.fc14.i686
3:koffice-kplato-2.3.3-1.fc14.x86_64 3:koffice-kpresenter-
libs-2.3.3-1.fc14.x86_64 kde-l10n-Korean-4.6.1-1.fc14.1.noarch sems-
early_announce-1.3.1-4.fc14.1.x86_64 QtRuby-devel-4.6.1-1.fc14.x86_64 6
:kdelibs-apidocs-4.6.1-4.fc14.noarch kdeartwork-kxs-4.6.1-1.fc14.x86_64
kde-l10n-Latvian-4.6.1-1.fc14.1.noarch kdeedu-devel-4.6.1-2.fc14.x86_64
wmtop-0.84-3.fc14.x86_64 kde-style-phase-4.6.1-1.fc14.x86_64 3:koffice-
kexi-libs-2.3.3-1.fc14.x86_64 kdeartwork-4.6.1-1.fc14.x86_64 3:koffice-
okular-odpgenerator-2.3.3-1.fc14.x86_64 7:kdepim-
devel-4.4.10-2.fc14.x86_64 7:system-config-printer-kde-4.6.1-1.fc14.x86_64
libktorrent-1.1.0-1.fc14.x86_64 kde-l10n-Interlingua-4.6.1-1.fc14.1.noarch
1:kde-i18n-Romanian-3.5.10-14.fc14.noarch 1:kde-i18n-
British-3.5.10-14.fc14.noarch kde-l10n-Chinese-
Traditional-4.6.1-1.fc14.1.noarch 7:kio_msits-4.6.1-1.fc14.x86_64 kde-
l10n-Chinese-4.6.1-1.fc14.1.noarch kde-l10n-Romanian-4.6.1-1.fc14.1.noarch
akonadi-1.5.1-1.fc14.x86_64 3:koffice-kpresenter-libs-2.3.3-1.fc14.i686
qzion-devel-0.4.0-10.fc14.x86_64 plowshare-0.9.4-0.5.svn1391.fc14.noarch
qedje-python-devel-0.4.0-8.fc14.x86_64 7:kdegraphics-4.6.1-1.fc14.x86_64 6
:kdegames-libs-4.6.1-1.fc14.i686 PyQt-devel-3.18.1-8.fc14.i686
calibre-0.7.38-3.fc14.2.x86_64 kdeedu-kstars-libs-4.6.1-2.fc14.i686 3
:koffice-kword-2.3.3-1.fc14.x86_64 kde-l10n-Slovak-4.6.1-1.fc14.1.noarch
sems-conference-1.3.1-4.fc14.1.x86_64 qscintilla-
python-2.4.6-2.fc14.x86_64 kdesdk-devel-4.6.1-1.fc14.x86_64 6:kdebase-
libs-4.6.1-3.fc14.x86_64 6:kdebase-libs-4.6.1-3.fc14.i686 sip-
devel-4.12.1-4.fc14.x86_64 6:kdemultimedia-devel-4.6.1-1.fc14.x86_64 3
:koffice-karbon-2.3.3-1.fc14.x86_64 1:kde-i18n-
Ukrainian-3.5.10-14.fc14.noarch 3:koffice-kword-libs-2.3.3-1.fc14.i686
kde-l10n-Serbian-4.6.1-1.fc14.1.noarch 3:koffice-devel-2.3.3-1.fc14.i686 1
:kdepim-runtime-4.4.10-2.fc14.x86_64 avogadro-devel-1.0.1-11.fc14.i686
kdevelop-php-1.2.0-2.fc14.x86_64 1:kdeaccessibility-libs-4.6.1-1.fc14.i686
kdeplasma-addons-libs-4.6.1-1.fc14.i686 kde-l10n-Norwegian-
Nynorsk-4.6.1-1.fc14.1.noarch PyQt4-devel-4.8.3-2.fc14.x86_64 6:kdegames-
devel-4.6.1-1.fc14.x86_64 1:kde-i18n-Slovak-3.5.10-14.fc14.noarch
6:kdebase-4.6.1-3.fc14.x86_64 qyoto-devel-4.6.1-1.fc14.i686 3:koffice-
kexi-2.3.3-1.fc14.x86_64 kde-l10n-Estonian-4.6.1-1.fc14.1.noarch digikam-
libs-1.9.0-1.fc14.x86_64 1:kdepim-runtime-libs-4.4.10-2.fc14.x86_64 qgis-
python-1.6.0-3.fc14.1.i686 soprano-devel-2.6.0-2.fc14.x86_64 digikam-
devel-1.9.0-1.fc14.x86_64 6:kdegames-minimal-4.6.1-1.fc14.x86_64 1:kde-
i18n-Portuguese-3.5.10-14.fc14.noarch 6:kdemultimedia-4.6.1-1.fc14.x86_64
backintime-common-1.0.6-1.fc14.noarch 1:kde-i18n-
Chinese-3.5.10-14.fc14.noarch 3:koffice-kplato-libs-2.3.3-1.fc14.x86_64 3
:koffice-karbon-libs-2.3.3-1.fc14.i686 kde-l10n-
British-4.6.1-1.fc14.1.noarch kde-l10n-Bulgarian-4.6.1-1.fc14.1.noarch
qgis-python-1.6.0-3.fc14.1.x86_64 kdepimlibs-devel-4.6.1-1.fc14.i686 kde-
l10n-Spanish-4.6.1-1.fc14.1.noarch kde-l10n-Khmer-4.6.1-1.fc14.1.noarch
kde-l10n-Catalan-Valencian-4.6.1-1.fc14.1.noarch qzion-0.4.0-10.fc14.i686
kdeartwork-screensavers-4.6.1-1.fc14.x86_64 attica-0.2.0-1.fc14.x86_64 9
:kdevelop-libs-4.2.0-2.fc14.x86_64 1:kde-i18n-Brazil-3.5.10-14.fc14.noarch
python3-sip-devel-4.12.1-4.fc14.x86_64 6:kdegames-libs-4.6.1-1.fc14.x86_64
7:kdetoys-4.6.1-1.fc14.x86_64 sems-1.3.1-4.fc14.1.x86_64 3:koffice-
kpresenter-2.3.3-1.fc14.x86_64 python3-sip-4.12.1-4.fc14.i686 kdepimlibs-
akonadi-4.6.1-1.fc14.i686 qedje-devel-0.4.0-8.fc14.x86_64 PyQwt-
devel-5.2.0-10.fc14.i686 PyKDE4-akonadi-4.6.1-1.fc14.x86_64 kde-l10n-
Arabic-4.6.1-1.fc14.1.noarch qscintilla-python-devel-2.4.6-2.fc14.noarch
kdeedu-kstars-libs-4.6.1-2.fc14.x86_64 3:koffice-kdchart-
devel-2.3.3-1.fc14.i686 3:koffice-kexi-driver-pgsql-2.3.3-1.fc14.x86_64
konq-plugins-4.6.1-1.fc14.x86_64 jpilot-1.8.0-2.fc14.x86_64
kdeedu-4.6.1-2.fc14.x86_64 PyKDE4-devel-4.6.1-1.fc14.i686 7:kdegraphics-
devel-4.6.1-1.fc14.i686 kdeedu-libs-4.6.1-2.fc14.x86_64 1:kde-i18n-
Tamil-3.5.10-14.fc14.noarch sems-conf_auth-1.3.1-4.fc14.1.x86_64
sip-4.12.1-4.fc14.x86_64 PyQt-devel-3.18.1-8.fc14.x86_64
qyoto-4.6.1-1.fc14.x86_64 sems-ivr-1.3.1-4.fc14.1.x86_64
kdegames3-libs-3.5.10-9.fc14.x86_64 qgis-1.6.0-3.fc14.1.x86_64 6:kdeutils-
printer-applet-4.6.1-1.fc14.x86_64 kdeedu-math-libs-4.6.1-2.fc14.x86_64
kde-l10n-Gujarati-4.6.1-1.fc14.1.noarch kdebindings-4.6.1-1.fc14.i686
kdevplatform-libs-1.2.0-3.fc14.x86_64 phonon-4.4.4-2.fc14.x86_64
PyQt4-devel-4.8.3-2.fc14.i686 1:kde-i18n-French-3.5.10-14.fc14.noarch sip-
macros-4.12.1-4.fc14.x86_64 PyKDE-devel-3.16.6-7.fc14.i686 php-qt-
devel-4.6.1-1.fc14.i686 3:koffice-kword-libs-2.3.3-1.fc14.x86_64 3
:koffice-filters-2.3.3-1.fc14.x86_64 php-qt-4.6.1-1.fc14.x86_64 kde-
plasma-yawp-0.3.6-1.fc14.2.x86_64 avogadro-libs-1.0.1-11.fc14.i686
korundum-devel-4.6.1-1.fc14.i686 kdebase-workspace-devel-4.6.1-2.fc14.i686
korundum-devel-4.6.1-1.fc14.x86_64 qscintilla-2.4.6-2.fc14.i686 3:koffice-
karbon-libs-2.3.3-1.fc14.x86_64 python3-sip-devel-4.12.1-4.fc14.i686
python3-PyQt4-devel-4.8.3-2.fc14.i686 soprano-2.6.0-2.fc14.i686
kdevplatform-devel-1.2.0-3.fc14.x86_64 kdeplasma-
addons-4.6.1-1.fc14.x86_64 2:phonon-backend-gstreamer-4.4.4-2.fc14.x86_64
kde-l10n-Galician-4.6.1-1.fc14.1.noarch kdebindings-
devel-4.6.1-1.fc14.x86_64 6:kdegames-4.6.1-1.fc14.x86_64 3:koffice-kexi-
driver-mysql-2.3.3-1.fc14.x86_64 kdepimlibs-akonadi-4.6.1-1.fc14.x86_64
phonon-devel-4.4.4-2.fc14.x86_64 akonadi-devel-1.5.1-1.fc14.x86_64 kde-
l10n-Punjabi-4.6.1-1.fc14.1.noarch qzion-python-devel-0.4.0-10.fc14.x86_64
kde-l10n-Walloon-4.6.1-1.fc14.1.noarch 1:kde-i18n-
Greek-3.5.10-14.fc14.noarch 1:mono-icon-theme-4.6.1-1.fc14.noarch
kdegames3-3.5.10-9.fc14.x86_64 kross-ruby-4.6.1-1.fc14.x86_64 digikam-
libs-1.9.0-1.fc14.i686 qedje-python-devel-0.4.0-8.fc14.i686
qgis-1.6.0-3.fc14.1.i686 python3-PyQt4-devel-4.8.3-2.fc14.x86_64 kipi-
plugins-libs-1.9.0-1.fc14.i686 qscintilla-2.4.6-2.fc14.x86_64 3:koffice-
filters-2.3.3-1.fc14.i686 kdevplatform-libs-1.2.0-3.fc14.i686 kde-l10n-
German-4.6.1-1.fc14.1.noarch kde-l10n-Croatian-4.6.1-1.fc14.1.noarch
kdeartwork-sounds-4.6.1-1.fc14.noarch 7:kdepim-libs-4.4.10-2.fc14.x86_64 7
:kdenetwork-libs-4.6.1-2.fc14.x86_64 kdeedu-marble-
libs-4.6.1-2.fc14.x86_64 sip-devel-4.12.1-4.fc14.i686 1:kde-i18n-
Korean-3.5.10-14.fc14.noarch 1:kde-i18n-Hindi-3.5.10-14.fc14.noarch
kdeartwork-wallpapers-4.6.1-1.fc14.noarch qgis-grass-1.6.0-3.fc14.1.x86_64
1:kde-i18n-Catalan-3.5.10-14.fc14.noarch qedje-0.4.0-8.fc14.x86_64 kde-
l10n-Italian-4.6.1-1.fc14.1.noarch 1:kde-i18n-Czech-3.5.10-14.fc14.noarch
kdepimlibs-devel-4.6.1-1.fc14.x86_64 PyQt4-4.8.3-2.fc14.x86_64 1:kde-i18n-
Turkish-3.5.10-14.fc14.noarch sip-4.12.1-4.fc14.i686 1:kde-i18n-
Hungarian-3.5.10-14.fc14.noarch python3-PyQt4-4.8.3-2.fc14.x86_64 oxygen-
cursor-themes-4.6.1-2.fc14.noarch libktorrent-devel-1.1.0-1.fc14.i686
kdegames3-devel-3.5.10-9.fc14.x86_64 kde-l10n-
Kannada-4.6.1-1.fc14.1.noarch 1:kde-i18n-Norwegian-3.5.10-14.fc14.noarch
kdegames3-libs-3.5.10-9.fc14.i686 qgis-devel-1.6.0-3.fc14.1.i686
kimono-4.6.1-1.fc14.x86_64 ktorrent-4.1.0-1.fc14.x86_64 3:koffice-
kspread-2.3.3-1.fc14.x86_64 1:kde-i18n-Icelandic-3.5.10-14.fc14.noarch 6
:kdelibs-devel-4.6.1-4.fc14.x86_64 kdeedu-math-4.6.1-2.fc14.x86_64
PyKDE4-akonadi-4.6.1-1.fc14.i686 perl-Locale-US-1.2-2.fc14.noarch kde-
l10n-Swedish-4.6.1-1.fc14.1.noarch qedje-0.4.0-8.fc14.i686
kdepimlibs-4.6.1-1.fc14.i686 kdeplasma-addons-devel-4.6.1-1.fc14.i686 1
:kde-i18n-German-3.5.10-14.fc14.noarch kdeplasma-addons-
libs-4.6.1-1.fc14.x86_64 korundum-4.6.1-1.fc14.x86_64 kdebase-workspace-
devel-4.6.1-2.fc14.x86_64 attica-0.2.0-1.fc14.i686 libktorrent-
devel-1.1.0-1.fc14.x86_64 kde-l10n-Dutch-4.6.1-1.fc14.1.noarch kdeedu-
libs-4.6.1-2.fc14.i686 kde-l10n-Basque-4.6.1-1.fc14.1.noarch
PyQt4-4.8.3-2.fc14.i686 PyKDE4-4.6.1-1.fc14.x86_64 1:kde-i18n-
Polish-3.5.10-14.fc14.noarch sems-gsm-1.3.1-4.fc14.1.x86_64 ktorrent-
libs-4.1.0-1.fc14.x86_64 kde-l10n-Hebrew-4.6.1-1.fc14.1.noarch digikam-
devel-1.9.0-1.fc14.i686 1:kde-i18n-Swedish-3.5.10-14.fc14.noarch 3
:koffice-devel-2.3.3-1.fc14.x86_64 1:kde-i18n-
Serbian-3.5.10-14.fc14.noarch PyKDE4-devel-4.6.1-1.fc14.x86_64 soprano-
apidocs-2.6.0-2.fc14.noarch qyoto-devel-4.6.1-1.fc14.x86_64 PyQt-
examples-3.18.1-8.fc14.x86_64 sems-mailbox-1.3.1-4.fc14.1.x86_64 1:kde-
i18n-Slovenian-3.5.10-14.fc14.noarch polkit-qt-devel-0.99.0-2.fc14.i686 3
:koffice-krita-2.3.3-1.fc14.x86_64 sems-pin_collect-1.3.1-4.fc14.1.x86_64
kdepimlibs-apidocs-4.6.1-1.fc14.noarch plasma-wallpaper-
marble-4.6.1-1.fc14.x86_64 1:kde-i18n-Chinese-Big5-3.5.10-14.fc14.noarch
akonadi-1.5.1-1.fc14.i686 6:kdelibs-devel-4.6.1-4.fc14.i686 kipi-plugins-
libs-1.9.0-1.fc14.x86_64 kde-l10n-Indonesian-4.6.1-1.fc14.1.noarch 1
:kdepim-runtime-devel-4.4.10-2.fc14.x86_64 kde-plasma-smooth-
tasks-0.0.1-0.1.wip20101106.fc14.2.x86_64 1:kde-i18n-
Italian-3.5.10-14.fc14.noarch kde-l10n-French-4.6.1-1.fc14.1.noarch 1:kde-
i18n-Finnish-3.5.10-14.fc14.noarch 1:kdeaccessibility-4.6.1-1.fc14.x86_64
sems-gateway-1.3.1-4.fc14.1.x86_64 9:kdevelop-devel-4.2.0-2.fc14.i686
sems-diameter_client-1.3.1-4.fc14.1.x86_64 1:kdeaccessibility-
libs-4.6.1-1.fc14.x86_64 thunarx-python-0.2.3-3.fc14.1.x86_64 3:koffice-
kplato-2.3.3-1.fc14.i686 kde-l10n-Russian-4.6.1-1.fc14.1.noarch
kdebindings-devel-4.6.1-1.fc14.i686 1:kde-i18n-
Punjabi-3.5.10-14.fc14.noarch shared-desktop-ontologies-
devel-0.6.0-1.fc14.noarch 7:kdeadmin-4.6.1-1.fc14.x86_64 1:kde-i18n-
Spanish-3.5.10-14.fc14.noarch akonadi-devel-1.5.1-1.fc14.i686 1:kde-i18n-
Dutch-3.5.10-14.fc14.noarch phonon-backend-xine-4.4.4-3.fc14.x86_64 6
:kdemultimedia-devel-4.6.1-1.fc14.i686 1:kde-i18n-
Hebrew-3.5.10-14.fc14.noarch 1:kde-i18n-Estonian-3.5.10-14.fc14.noarch
kde-l10n-Lithuanian-4.6.1-1.fc14.1.noarch kdevplatform-1.2.0-3.fc14.x86_64
kdeedu-kstars-4.6.1-2.fc14.x86_64 sems-python-1.3.1-4.fc14.1.x86_64 kde-
l10n-Hungarian-4.6.1-1.fc14.1.noarch QtRuby-4.6.1-1.fc14.x86_64 kde-
plasma-ktorrent-4.1.0-1.fc14.x86_64 kde-l10n-Turkish-4.6.1-1.fc14.1.noarch
1:kdepim-runtime-devel-4.4.10-2.fc14.i686 kdeedu-devel-4.6.1-2.fc14.i686
qedje-python-0.4.0-8.fc14.x86_64 nuvola-icon-theme-4.6.1-1.fc14.noarch
kde-style-phase-4.6.1-1.fc14.i686 soprano-devel-2.6.0-2.fc14.i686 sems-
dsm-1.3.1-4.fc14.1.x86_64 kdebindings-4.6.1-1.fc14.x86_64
PyQt-3.18.1-8.fc14.x86_64 kde-l10n-Finnish-4.6.1-1.fc14.1.noarch
7:kdepim-4.4.10-2.fc14.x86_64 QtRuby-devel-4.6.1-1.fc14.i686
7:kdenetwork-4.6.1-2.fc14.x86_64 9:kdevelop-libs-4.2.0-2.fc14.i686
kdegames3-devel-3.5.10-9.fc14.i686 kde-l10n-Greek-4.6.1-1.fc14.1.noarch 1
:kde-i18n-Bengali-3.5.10-14.fc14.noarch kde-l10n-
Slovenian-4.6.1-1.fc14.1.noarch avogadro-devel-1.0.1-11.fc14.x86_64 kde-
l10n-Icelandic-4.6.1-1.fc14.1.noarch digikam-1.9.0-1.fc14.x86_64 kdesdk-
devel-4.6.1-1.fc14.i686 3:koffice-kexi-libs-2.3.3-1.fc14.i686 kde-l10n-
Catalan-4.6.1-1.fc14.1.noarch 7:kdegraphics-devel-4.6.1-1.fc14.x86_64 3
:koffice-suite-2.3.3-1.fc14.x86_64 2:phonon-backend-
gstreamer-4.4.4-2.fc14.i686 avogadro-1.0.1-11.fc14.x86_64
calibre-0.7.38-4.fc14.x86_64 python3-PyQt4-4.8.3-2.fc14.i686 6
:kdemultimedia-libs-4.6.1-1.fc14.i686 qgis-devel-1.6.0-3.fc14.1.x86_64
qedje-devel-0.4.0-8.fc14.i686 polkit-kde-0.99.0-2.fc14.x86_64 kross-
python-4.6.1-1.fc14.x86_64 kde-l10n-Irish-4.6.1-1.fc14.1.noarch polkit-qt-
devel-0.99.0-2.fc14.x86_64 PyKDE-devel-3.16.6-7.fc14.x86_64
qyoto-4.6.1-1.fc14.i686 kde-l10n-Japanese-4.6.1-1.fc14.1.noarch
QtRuby-4.6.1-1.fc14.i686 avogadro-libs-1.0.1-11.fc14.x86_64 9:kdevelop-
devel-4.2.0-2.fc14.x86_64 backintime-kde-1.0.6-1.fc14.noarch 1:kde-i18n-
Bulgarian-3.5.10-14.fc14.noarch python3-sip-4.12.1-4.fc14.x86_64 kdeedu-
marble-4.6.1-2.fc14.x86_64 PyQwt-5.2.0-10.fc14.x86_64 kde-l10n-
Kazakh-4.6.1-1.fc14.1.noarch 1:kde-i18n-Russian-3.5.10-14.fc14.noarch kde-
l10n-Polish-4.6.1-1.fc14.1.noarch qscintilla-devel-2.4.6-2.fc14.x86_64
veusz-1.9-2.fc14.1.x86_64 7:kdenetwork-libs-4.6.1-2.fc14.i686 kde-l10n-
Czech-4.6.1-1.fc14.1.noarch phonon-4.4.4-2.fc14.i686 kde-l10n-
Norwegian-4.6.1-1.fc14.1.noarch phonon-backend-xine-4.4.4-3.fc14.i686 3
:koffice-kdchart-devel-2.3.3-1.fc14.x86_64 perl-Math-Random-
ISAAC-1.004-2.fc14.noarch 6:kdegames-devel-4.6.1-1.fc14.i686 1:kde-i18n-
Norwegian-Nynorsk-3.5.10-14.fc14.noarch
}}}
error:
{{{
AssertionError: Build kicad-2011.01.28-1.rev2765.fc14 passed in as a
pending build, but depcheck produced no result for it.
}}}
Full log attached.
There are surely more builds like that, not just kicad.
The question is - who's got the balls to fight the yum objects and find
the problem? :-) Or Will, would you have a look at that?
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
6:22 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
I've hit attachment size limits, so the full log is here:
http://kparal.fedorapeople.org/autoqa/t284_depcheck.DEBUG
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:1>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
6:34 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
I have improved depcheck output and ran the test again today. The missing
build from depcheck output is really just the mentioned one (kicad).
The new full log is here:
http://kparal.fedorapeople.org/autoqa/t284_depcheck.DEBUG_2
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:2>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
10:26 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by tflink):
== Cause ==
This is due to the fact that yum is written such that the skipped package
information is only made available when dependency resolving issues can be
successfully resolved.
In the cases that we're seeing this, yum can't resolve the dependencies,
doesn't update its public data structures and we don't find any
information about the deps with problems.
yum-3_2_X head, line 1186
{{{
#!python
if rescode != 1:
self.verbose_logger.debug("SKIPBROKEN: took %i rounds ", count)
self.verbose_logger.info(_('\nPackages skipped because of
dependency problems:'))
skipped_list = [p for p in skipped_po]
skipped_list.sort()
for po in skipped_list:
msg = _(" %s from %s") % (str(po),po.repo.id)
self.verbose_logger.info(msg)
self.skipped_packages.extend(skipped_list) # make the skipped
packages public
else:
# If we cant solve the problems the show the original error messages.
self.verbose_logger.info("Skip-broken could not solve problems")
return 1, orig_restring
return rescode, restring
}}}
== Root Cause ==
As far as I can tell, the root cause of this is feeding bad data into yum.
I spent a lot of time with
[http://autoqa.fedoraproject.org/results/92666-autotest/ job 92666]
(depcheck, x86_64, F14).
This particular failure is interesting because the
[http://autoqa.fedoraproject.org/results/92524-autotest/ same update
passed on i386].
The problem is a conflict between how depcheck works and how the spec file
for wine is written.
{{{
Requires: wine-wow(x86-64) = %{version}-%{release}
Conflicts: wine-wow(x86-32) = %{version}-%{release}
}}}
Since we're trying to install both the 32 and 64 bit versions of wine on
x86_64, yum can't seem to resolve a solution, fails and doesn't report the
broken packages (apparently by design)
== Possible Fixes ==
This one is a little harder; I can't really think of a great fix ATM. The
ones that I can think of are:
* Request enhancement for yum to make skipped packages available on
failure
* I imagine that there is a reason this data isn't provided, though
* Don't feed bad data into yum
* The only way I can think of doing that in the case of 92666 is to
pre-determine the conflicts on each package and exclude one of them from
the 'install' set of pending and accepted packages.
* I'd have to think that one through a bit more, not sure it's a good
idea.
* Assume no output is NEEDS_INSPECTION
* Assuming FAILURE would cause a false negative in the case of job
92666 (and I assume others)
* Assuming NEEDS_INSPECTION would at least let other packages get
commented instead of crashing and stopping any bodhi updates
* Blacklist the packages that are causing problems
* flag them for manual testing?
Of these solutions, I think that setting the missing updates to
NEEDS_INSPECTION is the best short term fix. It keeps depcheck from
crashing as much and doesn't have problems with false positives or
negatives. It would probably be an annoyance for the affected maintainers,
though.
If we can figure out how to pre-parse the rpm data to form the install
set, that should also work but I also think that might be more of a long-
term fix.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:3>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
2:23 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
Replying to [comment:3 tflink]:
This particular failure is interesting because the
[http://autoqa.fedoraproject.org/results/92524-autotest/ same update
passed on i386].
The problem is a conflict between how depcheck works and how the spec
file for wine is written.
{{{
Requires: wine-wow(x86-64) = %{version}-%{release}
Conflicts: wine-wow(x86-32) = %{version}-%{release}
}}}
Since we're trying to install both the 32 and 64 bit versions of wine on
x86_64, yum can't seem to resolve a solution, fails and doesn't report
the
broken packages (apparently by design)
Why do we try to install both? Shouldn't mash ensure only relevant
packages are put into the repository?
When I try to "yum install wine" on my F14, it only wants to install wine-
wow.x86_64, not wine-wow.i686. However, it wants to install other wine-*
dependencies that are i686, that is true.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:4>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
9:06 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by tflink):
Replying to [comment:4 kparal]:
Why do we try to install both? Shouldn't mash ensure only
relevant
packages are put into the repository?
When I try to "yum install wine" on my F14, it only wants to install
wine-wow.x86_64, not wine-wow.i686. However, it wants to install other
wine-* dependencies that are i686, that is true.
I'm only speculating here, but I imagine that it was seen as a solution to
multilib installs. Since depcheck doesn't actually have access to repos,
we download everything that we need from the beginning.
I wonder if we could be a bit smarter about this without too much effort,
though. Download all 32 and 64 bit packages, mash them and only try to
install the packages for the current arch. Since the repo for accepted and
proposed packages DOES have files, I think that we would be able to pull
in what we need without causing dependency issues like this.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:5>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
6:58 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: closed
Priority: major | Milestone: Hot issues
Component: tests | Resolution: duplicate
Keywords: |
--------------------+-------------------------------------------------------
Changes (by kparal):
* status: new => closed
* resolution: => duplicate
Comment:
Marking as duplicate of ticket #325, we will track this issue there.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:6>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
4:20 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Changes (by tflink):
* status: closed => reopened
* resolution: duplicate =>
Comment:
I'm re-opening this ticket because this issue has been annoying me and I
want to propose a quick fix for this until we end up fixing it the right
way since we're losing the comments from entire tests if one build has
problems.
Builds missing information will be tagged as "NEEDS_INSPECTION" and the
test result as a whole will be tagged "NEEDS_INSPECTION" if there is
missing information (ie, yum had errors)
https://fedorahosted.org/reviewboard/r/147/
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:7>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
3:26 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
I reviewed that. My greatest concern is whether we can rely on depcheck
output when some builds were not evaluated correctly.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:8>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
10:54 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by jlaska):
Replying to [comment:8 kparal]:
I reviewed that. My greatest concern is whether we can rely on
depcheck
output when some builds were not evaluated correctly.
ff crashes for me when attempting to reply in reviewboard. I'll reply
here ...
The code itself seems fine. But it will have a side effect - updates
with builds
with no depcheck output will be reported to Bodhi as
NEEDS_INSPECTION.
Is that
desired? My first thought would be not to send reports, when we have
nothing to
report.
Hmm, I'd suggest we send them and treat them like FAILED results. But I
guess the question is, who is expected to act based on the
NEEDS_INSPECTION results? For PASSED results, no action is needed by the
maintainer. For FAILED results, action is needed by the maintainer. For
NEEDS_INSPECTION results, I'm assuming action is needed by the maintain
also? Not just in resolving any issue (which is the case for FAILED
results), but in identifying whether an issue exists.
Also, can we be sure that if depcheck does not produce output for
some
build, it
does mean that other builds were evaluated correctly?
To rephrase ... because we couldn't close the deps loop, the concern is
that we can't be sure we really did depsclosure?
I'd hesitate to say we can't trust them ... because my sense is we'd
bottleneck on depcheck results far too often. My initial thought was we'd
just treat these NEEDS_INSPECTION builds like others that FAILED depcheck.
Unlike with FAILED results, our testing was not able to determine whether
the builds are depsolvable, and they need manual inspection (note, this
will need some docs for maintainers).
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:9>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
3:04 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
Replying to [comment:9 jlaska]:
Hmm, I'd suggest we send them and treat them like FAILED results.
But I
guess the question is, who is expected to act based on the
NEEDS_INSPECTION results?
I believe that is not really finalized yet. Originally we designed
NEEDS_INSPECTION result with this semantics: "The maintainer must review
the results and then waive them if they seem OK. Until that time the
result counts as FAILED." However, we still don't have any waiving
mechanism supported and in the meantime we started using NEEDS_INSPECTION
results as a hint for *us*, saying that something has gone wrong with that
test and it needs to be looked at.
It means we still have to finalize those result keywords. But for both
NEEDS_INSPECTION meanings there is not much sense in sending them to the
package maintainers. They can't do a thing with it.
To rephrase ... because we couldn't close the deps loop, the
concern is
that we can't be sure we really did depsclosure?
Exactly. I'd rather send smaller amount of test results, but correct, then
send larger amount of test results, but possibly incorrect.
I'd hesitate to say we can't trust them ... because my sense
is we'd
bottleneck on depcheck results far too often. My initial thought was we'd
just treat these NEEDS_INSPECTION builds like others that FAILED depcheck.
Unlike with FAILED results, our testing was not able to determine whether
the builds are depsolvable, and they need manual inspection (note, this
will need some docs for maintainers).
I'm afraid that is something a person cannot decide (in case of depcheck
test). If he could, he would have done that already and we wouldn't have
needed depcheck test in the first case.
If I look at the problem through package maintainers eyes: "My package
received FAILED/NEEDS_INSPECTION result, noting that I should review the
test output, but due to a bug in the test, there is no output I can
review. So why did I even receive that warning? It's the problem of
AutoQA, not mine. I can't do anything about it, it just annoys me."
I don't think it's a good idea to send maintainers notifications about
failures in our test. It's better not to send at all, rather than send
something they can't do anything about.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:10>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
8:42 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by jlaska):
Replying to [comment:10 kparal]:
Exactly. I'd rather send smaller amount of test results, but
correct,
then send larger amount of test results, but possibly incorrect.
Certainly, someone closer to depcheck internals should speak to this, but
from a high-level ... I don't see any problems with reporting PASS for any
successful builds in that test run. As long as the untested builds aren't
also getting PASSED, we aren't introducing closure problems into the
repos.
I'm afraid that is something a person cannot decide (in case of
depcheck
test). If he could, he would have done that already and we wouldn't have
needed depcheck test in the first case.
Yeah, fair point.
If I look at the problem through package maintainers eyes: "My
package
received FAILED/NEEDS_INSPECTION result, noting that I should review the
test output, but due to a bug in the test, there is no output I can
review. So why did I even receive that warning? It's the problem of
AutoQA, not mine. I can't do anything about it, it just annoys me."
Yeah, if it's clearly a test bug ... and there is no way a maintainer
could determine the cause of the failure by inspecting the logs ... I
could see how this would be unactionable (word?) for the maintainer.
I don't think it's a good idea to send maintainers
notifications about
failures in our test. It's better not to send at all, rather than send
something they can't do anything about.
We're still planning to only send notification when all tests for a
package have finished, right? If so ... this wouldn't be an additional
notification.
You make great points Kamil. I don't want to send maintainers nonsense
results where they can't figured out I'm hoping there is a way we can not
introduce more notifications, but also note that the test did not PASS or
FAIL (e.g. NEEDS_INSPECTION). When I look at bodhi updates that are
missing results, it makes me wonder whether there are
scheduler/test/reporting bugs in AutoQA. Assuming publishing a
NEEDS_INSPECTION result doesn't increase email notification, I'd prefer
getting a NEEDS_INSPECTION result, instead of no result at all.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:11>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
9:50 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by tflink):
After the conversation here and in IRC, we agreed to do the following:
* Send results for non-missing builds
* Send NO results for missing builds
There are definitely problems with using NEEDS_INSPECTION, as noted above
- mostly an intended meaning other than "test issue".
We talked about adding a new state along the lines of "AUTOQA_ERROR" to
signify that there was no information on the package, but decided that it
would be OK to just not send results for now.
As noted above, this is just a short term hacky-fix and we need to root
cause the issue that's causing the missing build information.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:12>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
4:07 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by tflink):
diff in RB updated to set all missing results to "AUTOQA_ERROR" and not
report those results to bodhi. The test result as a whole is also changed
to "FAILED"
https://fedorahosted.org/reviewboard/r/147/
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:13>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
1:54 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
Reviewed.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:14>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
3:05 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by tflink):
I updated the diff in RB to ignore updates that contain builds with
missing information so that potentially wrong information isn't sent to
bodhi, stop using AUTOQA_ERROR and add information the proper places.
It took a while but I was finally able to artificially induce this issue
in my dev env for testing. Everything seems to be working as designed.
https://fedorahosted.org/reviewboard/r/147/
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:15>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
2:41 a.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: Hot issues
Component: tests | Resolution:
Keywords: |
--------------------+-------------------------------------------------------
Comment (by kparal):
Reviewed.
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:16>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
4:10 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: closed
Priority: major | Milestone: Hot issues
Component: tests | Resolution: fixed
Keywords: |
--------------------+-------------------------------------------------------
Changes (by tflink):
* status: reopened => closed
* resolution: => fixed
Comment:
Changed overall status to 'NEEDS_INSPECTION' and pushed to master.
commit 5ff4248a25f235d56afc1473487a8c745f0a97c0
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:17>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
1:29 p.m.
#284: depcheck does not produce output for some pending updates
--------------------+-------------------------------------------------------
Reporter: kparal | Owner:
Type: defect | Status: closed
Priority: major | Milestone: 0.5.0
Component: tests | Resolution: fixed
Keywords: |
--------------------+-------------------------------------------------------
Changes (by kparal):
* milestone: Hot issues => 0.5.0
--
Ticket URL: <https://fedorahosted.org/autoqa/ticket/284#comment:18>
AutoQA <http://autoqa.fedorahosted.org>
Automated QA project
4708
days inactive
4783
days old
autoqa-devel@lists.fedorahosted.org
18 comments
1 participants
participants (1)
-
fedora-badges