https://bugzilla.novell.com/show_bug.cgi?id=207161
Summary: build.opensuse.org web page: adding a build target twice
results in sql error
Product: openSUSE 10.2
Version: Alpha 4 plus
Platform: Other
OS/Version: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: aj(a)dungeon.inka.de
QAContact: qa(a)suse.de
explicit error handling might be nicer (or checking before adding
a target).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=205535
Summary: Chenging icon set in KDE Control Center has NO effect.
Cannot change icon set in KDE.
Product: openSUSE 10.2
Version: Alpha 4
Platform: i686
OS/Version: SuSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: dotsa(a)hotmail.com
QAContact: qa(a)suse.de
OpenSuse 10.1 updated to latest contents of
http://ftp.gwdg.de/pub/linux/misc/suser-guru/rpm/10.1ftp://mirrors.kernel.org/suse/i386/supplementary/KDE/update_for_10.1/http://software.opensuse.org/download/KDE:/Backports/SUSE_Linux_10.1ftp://mirrors.kernel.org/suse/update/10.1/http://packman.inode.at/suse/10.1http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/ (the source of
my KDE packages)
http://download.opensuse.org/distribution/SL-10.1/non-oss-inst-source
ABOUT THE PROBLEM:
After recent update of KDE and other (ImageMagic among them) packages the
following occurs:
1. Trying to set another icon set in KDE Control Center has no effect. Changes
are "accepted" and "updating settings" (or something line that) pupup/progress
window shows up and goes away. But, the icon set remains unchanged.
2. (Probably related) Choosing an icon in DigiKam for a tag crashes DigiKam.
(See http://bugs.kde.org/show_bug.cgi?id=133944) Judging by other issues, this
is probably not DigiKam bug.
3. (Probably not related, but who knows...) I have auto-login for one of the
users. Ever since the latest upgrade, on cold-boots, instead of the kde
session, I get an X-term-like window with message complaining that something
like "KDEInit.... failed to start". Clicking ok, getting back to KDM and
logging the same user in, gets me to the normal KDE desktop. Apparently a case
of "speeding up KDE start up" gone bad.
I would gladly provide some logs or other info, if I knew where to look.
The list of my kde packages / version bellow:
NetworkManager-kde-0.1r534534-4
kdemultimedia3-3.5.4-15.1
kdebase3-samba-3.5.4-58.1
kdelibs3-3.5.4-62.1
kdegraphics3-extra-3.5.4-14.1
kdepim3-devel-3.5.4-19.1
kdesdk3-3.5.4-14.7
kdepim3-kpilot-3.5.4-19.1
kdemultimedia3-mixer-3.5.4-15.1
kdemultimedia3-sound-3.5.4-15.1
kdenetwork3-InstantMessenger-3.5.4-21.4
kdegraphics3-pdf-3.5.4-14.1
kdeartwork3-3.5.4-13.1
kdenetwork3-3.5.4-21.4
kdepim3-networkstatus-3.5.4-19.1
kdewebdev3-3.5.4-10.2
kdeartwork3-xscreensaver-3.5.4-13.1
kdebase3-session-3.5.4-58.1
kdemultimedia3-arts-3.5.4-15.1
kdegraphics3-3.5.4-14.1
kdemultimedia3-extra-3.5.4-15.1
kdegraphics3-scan-3.5.4-14.1
kdelibs3-devel-3.5.4-62.1
kdepim3-sync-3.5.4-19.1
kdeaddons3-kontact-3.5.4-21.2
kdeaddons3-kate-3.5.4-21.2
kdeutils3-laptop-3.5.4-13.1
kdebase3-nsplugin-3.5.4-58.1
kdeadmin3-3.5.4-12.1
kdepim3-3.5.4-19.1
multisync-kdepim-0.82+cvs-25
kdebluetooth-1.0_beta1-1
kdelibs3-arts-3.5.4-62.1
kdegraphics3-postscript-3.5.4-14.1
kdenetwork3-lisa-3.5.4-21.4
kdenetwork3-news-3.5.4-21.4
kdebase3-extra-3.5.4-58.1
kdeartwork3-sound-3.5.4-13.1
kdenetwork3-vnc-3.5.4-21.4
kdeutils3-3.5.4-13.1
kdebase3-devel-3.5.4-58.1
kdemultimedia3-CD-3.5.4-15.1
kdebindings3-3.5.4-39.7
kdeaddons3-sound-3.5.4-21.2
kdeaddons3-kicker-3.5.4-21.2
kdepim3-mobile-3.5.4-19.1
kdebase3-ksysguardd-3.5.4-58.1
kdemultimedia3-video-3.5.4-15.1
kdeaddons3-konqueror-3.5.4-21.2
kdesdk3-translate-3.5.4-14.7
OpenOffice_org-kde-2.0.2-27.12
kdebase3-kdm-3.5.4-58.1
kdelibs3-doc-3.5.4-62.1
kdebase3-3.5.4-58.1
kdegraphics3-imaging-3.5.4-14.1
kdeaccessibility3-3.5.4-10.1
kdebindings3-java-3.5.4-8.20
kdebindings3-python-3.5.4-2.20
kdenetwork3-InstantMessenger-0.12-beta2-1
kdebase3-SuSE-10.1-58.7
kdeutils3-extra-3.5.4-13.1
kdegraphics3-fax-3.5.4-14.1
kdeartwork3-kscreensaver-3.5.4-13.1
kdenetwork3-lan-3.5.4-21.4
kde3-i18n-ru-3.5.4-70.1
kdegraphics3-kamera-3.5.4-14.1
kdebindings3-javascript-3.5.4-2.20
kdepim3-time-management-3.5.4-19.1
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208679
Summary: alt non-functioning in gedit
Product: openSUSE 10.2
Version: Alpha 4
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: mmeeks(a)novell.com
QAContact: qa(a)suse.de
My alt-key works in other apps, but running 'gedit' type some text, press
Alt->F for the menu - no Alt behavior - most odd.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208870
Summary: Bad grub location selected
Product: openSUSE 10.2
Version: Alpha 4
Platform: 64bit
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: hugo.costelha(a)gmail.com
QAContact: jsrain(a)novell.com
I had SUSE Linux 10.1 installed, and I was trying openSUSE 10.2, to help
improving it by bug reporting.
I had just one SATA drive installed with SUSE 10.1, so I installed an IDE
hard-drive and started openSUSE 10.2 installation from the CDs.
Initially openSUSE 10.2 sugested to use the SATA drive, so I changed it to use
the IDE drive, and proceeded with the install.
When it made the first reboot, the old (SUSE 10.1) GRUB appeared (with no
reference to openSUSE 10.2) and booted the 10.1. So, the grub install location
was badly selected.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=206972
Summary: A way to control whether built packages reach build
and/or dist area
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: BuildService
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: rguenther(a)novell.com
QAContact: adrian(a)novell.com
To avoid using packages for building or to avoid cluttering the dist area with
intermediate packages.
Like in CrossToolchain:sh4 I do not want to distribute cross-sh4-bootstrap-gcc,
but only need it as intermediate stage for building the other packages.
Like in home:rguenther I end up with choices for libgcc, which is provided by
libgcc (from Factory or 10.1) and libgcc41 (from gcc41 package) and libgcc42
(from gcc42 package). There is no need to use home:rguenther/gcc41 or
home:rguenther/gcc42 for resolving any dependencies on build-time of
home:rguenther.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207629
Summary: Triggering rebuilds does not do authentication
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: BuildService
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: rguenther(a)novell.com
QAContact: adrian(a)novell.com
Everyone (authenticated to the bs in general) can trigger rebuilds of packages
they do not maintain.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=207630
Summary: Debian repositories not useful for apt
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: BuildService
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: rguenther(a)novell.com
QAContact: adrian(a)novell.com
The repository structure for Debian_Etch does not conform to the standards
required by apt, so installing packages from it is painful.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208691
Summary: ifolder3 and simias source tarballs needlessly big
Product: openSUSE 10.2
Version: Alpha 4 plus
Platform: Other
OS/Version: Other
Status: NEW
Severity: Blocker
Priority: P5 - None
Component: GNOME
AssignedTo: jhargadon(a)novell.com
ReportedBy: rguenther(a)novell.com
QAContact: qa(a)suse.de
The source tarballs of ifolder3 and simias contain SVN meta-data:
drwxr-xr-x build/users 0 2006-08-16 22:43:59 simias-1.4.6228.1/
drwxr-xr-x build/users 0 2006-08-16 22:43:59 simias-1.4.6228.1/.svn/
drwxr-xr-x build/users 0 2006-08-16 22:43:59
simias-1.4.6228.1/.svn/text-b
ase/
-r--r--r-- build/users 86 2006-08-16 22:43:43
simias-1.4.6228.1/.svn/text-b
ase/AUTHORS.svn-base
-r--r--r-- build/users 15152 2006-08-16 22:43:43
simias-1.4.6228.1/.svn/text-b
ase/configure.in.svn-base
..
Use 'svn export' or other means to produce clean tarballs.
Both ifolder3 and simias build-depend on compat-libstdc++, this is wrong and
not necessary. Please fix this, too.
Thanks.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208447
Summary: rpm Obsoletes does not handle virtual dependencies
Product: openSUSE 10.2
Version: Alpha 4 plus
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: mls(a)novell.com
ReportedBy: rguenther(a)novell.com
QAContact: qa(a)suse.de
CC: aj(a)novell.com
rpm currently does not allow updating with -Uhv that would require removal of
another package providing the same virtual provides.
Consider:
libgcc41
Provides: libgcc = 4.1.0
Obsoletes: libgcc < 4.1.0
libgcc42
Provides: libgcc = 4.2.0
Obsoletes: libgcc < 4.2.0
if now libgcc41 is installed and we want to install libgcc42, rpm does not know
it needs to deinstall libgcc41, even though libgcc42 obsoletes libgcc.
If we know beforehand that libgcc41 exists at the time of packaging libgcc42
this can be worked around by obsoleting libgcc41 as well in libgcc42.
But now let's introduce a libgcc33 package which libgcc42 does not know about
and things break again.
libgcc33:
Provides: libgcc = 3.3.3
Obsoletes: libgcc < 3.3.3
Somehow teaching rpm to do the right thing here (deinstall all providers
of libgcc < $VERSION if libgcc < $VERSION is obsoleted by a to-be-installed
package) is essential.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=208694
Summary: YaST does not allow package downgrading if patches were
applied
Product: SUSE Linux 10.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: YaST2
AssignedTo: kkaempf(a)novell.com
ReportedBy: rguenther(a)novell.com
QAContact: jsrain(a)novell.com
CC: sh(a)novell.com
If you start with a 10.1 install and apply current online-updates you get a
xorg patch. If you then install xorg7 from an external source (openSUSE) you
can
not downgrade to xorg 6.9 again without re-installing.
This is because the applied patch imposes requirements on library versions, but
those are not available for downgrading. So downgrading to the available 10.1
packages fails and there is no way ignoring the patch dependencies or
uninstalling the patch.
I believe this (interaction of patches with dependencies) is a design issue and
is not easy to fix (other than by providing a "ignore this dependency" from the
Yast sw management module and allowing to re-apply a patch).
Still this is a quite severe issue, as requiring a re-install of the complete
system in this case is not acceptable.
[but unsupported external install, yadayada, so Critial priority only]
Note this problem is in openSUSE 10.2, too, I believe.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.