January 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 240644] New: installation asks for CD1 but the cd is in drive
by bugzilla_noreply＠novell.com 12 Jul '08

12 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=240644 Summary: installation asks for CD1 but the cd is in drive Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: snwint(a)novell.com ReportedBy: mmrazik(a)novell.com QAContact: jsrain(a)novell.com During the installation I wanted to configure LDAP + kerberos autentification. Ldap packages were installed correctly, however I con not proceed with KDC configuration. Al I get is: "Insert '20070131-062828 CD1'" (in details: 'Mounting media failed'). However the CD1 is in the driver (actually the ldap packages were installed from it). y2logs are following -- 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.

1 5

[Bug 227460] New: yast should block auto mount when changing disc
by bugzilla_noreply＠novell.com 12 Jul '08

12 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=227460 Summary: yast should block auto mount when changing disc Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com KDE 3.5.5, opensuse 10.2 Let's say I have to install software from CD1 and CD2. When I am asked to insert CD2 instead of CD1, and I do it, Konqueror pops up with CD2 contents. Yast should block such auto-notification. -- 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.

1 6

[Bug 231444] New: a libzypp lock failure should always report at least the PID of the locking processz
by bugzilla_noreply＠novell.com 10 Jul '08

10 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=231444 Summary: a libzypp lock failure should always report at least the PID of the locking processz Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: libzypp AssignedTo: kkaempf(a)novell.com ReportedBy: meissner(a)novell.com QAContact: kkaempf(a)novell.com If another process is locking the zypp db, then the failed dialogbox should always say at least the PID of the locking process. Its the only way to really find out who locks it and the information is already available. -- 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.

1 4

[Bug 225435] New: dar-2.2.5-25: comparison with string literal
by bugzilla_noreply＠novell.com 09 Jul '08

09 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=225435 Summary: dar-2.2.5-25: comparison with string literal Product: openSUSE 10.2 Version: RC 5 Platform: All OS/Version: SuSE Linux 10.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de I just tried to build the package dar-2.2.5-25 I got the following warning message from the compiler. ./dar_suite/dar_suite.cpp:61: warning: comparison with string literal The source code is if(DAR_LOCALEDIR != "") Perhaps the programmer intended if( strcmp( DAR_LOCALEDIR, "") != 0) -- 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.

1 3

[Bug 233655] New: Enable "comparison with string literal" gcc warnings?
by bugzilla_noreply＠novell.com 09 Jul '08

09 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=233655 Summary: Enable "comparison with string literal" gcc warnings? Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: meissner(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: qa(a)suse.de CC: dcb314(a)hotmail.com I wonder whether we should we enable "comparison with string literal" gcc warnings (RPM_OPT_FLAGS) and even trigger a fatal build error? I think we could safe David's resources (rebuilding each package and filing bugreports) and Novell's resources (bugreport handling) as well. -- 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.

1 21

[Bug 235818] New: Kernel Bug in kernel-default-2.6.18.2-34 on x86-64 SMP machine
by bugzilla_noreply＠novell.com 09 Jul '08

09 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=235818 Summary: Kernel Bug in kernel-default-2.6.18.2-34 on x86-64 SMP machine Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: asvetter(a)cip.physik.uni-wuerzburg.de QAContact: qa(a)suse.de Kernel Bug in kernel-default-2.6.18.2-34 on x86-64 SMP machine: Jan 12 16:13:55 wpyc009 kernel: BUG: warning at fs/inotify.c:171/set_dentry_child_flags() Jan 12 16:13:55 wpyc009 kernel: Jan 12 16:13:55 wpyc009 kernel: Call Trace: Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d54dc>] set_dentry_child_flags+0x66/0x132 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d560f>] remove_watch_no_event+0x67/0x76 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d5a7d>] inotify_destroy+0x92/0xbf Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d5b9a>] inotify_release+0x1a/0x73 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80210559>] __fput+0xae/0x182 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80221b2a>] filp_close+0x5c/0x64 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80236bdd>] put_files_struct+0x6c/0xc3 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802131c3>] do_exit+0x2b0/0x8fc Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802450b9>] cpuset_exit+0x0/0x6c Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802295f6>] get_signal_to_deliver+0x46e/0x49d Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80227fdd>] do_signal+0x55/0x74a Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8025c8e8>] thread_return+0x0/0xef Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8029463d>] __remove_hrtimer+0x27/0x39 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80255f03>] hrtimer_cancel+0xc/0x16 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8025d736>] do_nanosleep+0x47/0x70 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80255df0>] hrtimer_nanosleep+0x58/0x118 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80226034>] do_wait+0x9c1/0xa44 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80294821>] hrtimer_wakeup+0x0/0x22 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80258097>] sysret_signal+0x1c/0x27 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8025831b>] ptregscall_common+0x67/0xac Jan 12 16:13:55 wpyc009 kernel: -- 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.

1 22

[Bug 238672] New: api doesn't accept arch other than i586/x86_64
by bugzilla_noreply＠novell.com 07 Jul '08

07 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=238672 Summary: api doesn't accept arch other than i586/x86_64 Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: poeml(a)novell.com QAContact: adrian(a)novell.com trying to create this project: <project name="openSUSE:10.2"> <repository status='disabled' name='standard'> <arch>ppc</arch> </repository> <title>the openSUSE 10.2 distribution</title> <description></description> </project> the api errors out as following. Using 'i586' instead works. Strange error message. [D|# 7942] add validation mapping: "source", :packagelist => :directory [D|# 7942] add validation mapping: "source", :filelist => :directory [D|# 7942] add validation mapping: "source", :index => :directory [D|# 7942] add validation mapping: "source", :project_meta => :project [D|# 7942] add validation mapping: "source", :package_meta => :package [I|# 7942] Processing SourceController#project_meta (for ::ffff:127.0.42.2 at 2007-01-25 12:50:10) [GET] [I|# 7942] Session ID: d120f05ff441348972d93d2a0261e013 [I|# 7942] Parameters: {"project"=>"test", "action"=>"project_meta", "controller"=>"source"} [D|# 7942] AUTH: [D|# 7942] no authentication string was sent [I|# 7942] Rendering status [I|# 7942] errorcode 'unknown' - Authentication required [I|# 7942] Rendering status (401) [I|# 7942] Filter chain halted as [extract_user] returned false [I|# 7942] Completed in 0.01779 (56 reqs/sec) | Rendering: 0.00598 (33%) | DB: 0.00000 (0%) | 401 [http://127.0.42.2/source/test/_meta] [D|# 7941] add validation mapping: "source", :packagelist => :directory [D|# 7941] add validation mapping: "source", :filelist => :directory [D|# 7941] add validation mapping: "source", :index => :directory [D|# 7941] add validation mapping: "source", :project_meta => :project [D|# 7941] add validation mapping: "source", :package_meta => :package [I|# 7941] Processing SourceController#project_meta (for ::ffff:127.0.42.2 at 2007-01-25 12:50:12) [GET] [I|# 7941] Session ID: 57234097f064f999094d7b12fbc24f4f [I|# 7941] Parameters: {"project"=>"test", "action"=>"project_meta", "controller"=>"source"} [D|# 7941] AUTH: BasicQWRtaW46b3BlbnN1c2U= [D|# 7941] User Load (0.002740) SELECT * FROM users WHERE (login = 'Admin') LIMIT 1 [D|# 7941] User Columns (0.008541) SHOW FIELDS FROM users [D|# 7941] USER found: Admin [D|# 7941] User Admin initialised [D|# 7941] User's source backend <:>, rpm backend: <:> [D|# 7941] ### project_name: "test" [D|# 7941] Project.find( "test" ) [D|# 7941] prepared find args: ["test", {:name=>"test"}] [D|# 7941] [BSSQL] find( Project, ["test", {:name=>"test"}] ) [D|# 7941] retrieving target_uri for model ':project' [D|# 7941] retrieving option hash for model ':project' [D|# 7941] [BSSQL] query_from_options: {:name=>"test"} [D|# 7941] [BSSQL] query_from_options: query is: '@name='test'' [D|# 7941] DbProject Columns (0.005302) SHOW FIELDS FROM db_projects [D|# 7941] [BSSQL] find conditions: ["db_projects.name LIKE BINARY ?", "test"] [D|# 7941] DbProject Load (0.002024) SELECT db_projects.* FROM db_projects WHERE (db_projects.name LIKE BINARY 'test') [F|# 7941] ActiveXML::Transport::NotFoundError (not found): /srv/www/obs/common/lib/activexml/transport.rb:213:in `find' /srv/www/obs/common/lib/activexml/base.rb:69:in `find' /app/controllers/source_controller.rb:211:in `project_meta' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:941:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:941:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:368:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/rescue.rb:82:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in `process' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in `dispatch' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:150:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:54:in `process!' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:53:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:23:in `process!' /srv/www/obs/frontend/public/dispatch.fcgi:24 [I|# 7941] Rendering status [I|# 7941] errorcode 'unknown' - not found [I|# 7941] Rendering status (404) [D|# 7942] add validation mapping: "source", :packagelist => :directory [D|# 7942] add validation mapping: "source", :filelist => :directory [D|# 7942] add validation mapping: "source", :index => :directory [D|# 7942] add validation mapping: "source", :project_meta => :project [D|# 7942] add validation mapping: "source", :package_meta => :package [I|# 7942] Processing SourceController#project_meta (for ::ffff:127.0.42.2 at 2007-01-25 12:50:23) [PUT] [I|# 7942] Session ID: 45bea062c51504de67a96bd4a348d33e [I|# 7942] Parameters: {"project"=>"test", "action"=>"project_meta", "controller"=>"source"} [D|# 7942] checking schema map for controller 'source', action 'project_meta' [D|# 7942] schema_file: project [D|# 7942] schema_path: /srv/www/docs/api/frontend/project.xsd [D|# 7942] trying to validate against schema '/srv/www/docs/api/frontend/project.xsd' [D|# 7942] validation tmpfile: /srv/www/obs/frontend/tmp/opensuse_frontend_validator.7942.0 [D|# 7942] xmllint return value: 3 [D|# 7942] XML: <project name="openSUSE:10.2"> <repository status='disabled' name='standard'> <arch>ppc</arch> </repository> <title>the openSUSE 10.2 distribution</title> <description></description> </project> Suse::ValidationError (validation failed, output: /srv/www/obs/frontend/tmp/opensuse_frontend_validator.7942.0:2: element repository: Schemas validity error : Element 'repository': This element is not expected. Expected is ( title ). /srv/www/obs/frontend/tmp/opensuse_frontend_validator.7942.0 fails to validate ): /lib/opensuse/validator.rb:155:in `validate' /lib/opensuse/validator.rb:52:in `validate_incoming_xml' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:399:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:399:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:394:in `each' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:394:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:383:in `before_action' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:365:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/rescue.rb:82:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in `process' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in `dispatch' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:150:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:54:in `process!' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:53:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:23:in `process!' /srv/www/obs/frontend/public/dispatch.fcgi:24 [I|# 7942] Rendering status [I|# 7942] errorcode 'uncaught_exception' - validation failed, output: /srv/www/obs/frontend/tmp/opensuse_frontend_validator.7942.0:2: element repository: Schemas validity error : Element 'repository': This element is not expected. Expected is ( title ). /srv/www/obs/frontend/tmp/opensuse_frontend_validator.7942.0 fails to validate [I|# 7942] Rendering status (500) -- 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.

1 8

[Bug 226041] New: A new install of 10.2 RC1 seems to be more prone to errors than 10.2
by bugzilla_noreply＠novell.com 07 Jul '08

07 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=226041 Summary: A new install of 10.2 RC1 seems to be more prone to errors than 10.2 Product: openSUSE 10.2 Version: RC 1 Platform: 32bit OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kern(a)sibbald.com QAContact: jsrain(a)novell.com Because of certain minor problems, I had to do the installation on my laptop three times before it completed correctly. The first time, I selected everything I wanted to be installed. When it got to the third CD, it complained that it could not find the package tetex on the CD. I clicked on Skip, hoping to continue without that package, and the install immediately failed and bounced into the red system error screen. If I am not mistaken on previous systems (i.e. 10.1) you would have already done a reboot and hence I would have been able to "manually" install all the missing packages. However, an attempt to reboot failed after printing GRUB in the upper left corner. I started installation again (after reburning CD 3), and this time decided to select a minimal installation. This time it completed, and I used Yast to select a large bunch of packages to install (Gnome, development tools, ...). After completing the selection, it found unresolvable conflicts. Since the information printed on the conflict page is somewhat confusing (it is hard to read what the original package is as the name seems to be mixed with other data). I mistakenly told it to remove kde-base (I think). I believed this would simply not install the update package. Well after clicking to continue, it proceeded to delete some 290 packages. Clicking on Abort had no effect. As you can imagine, this left the system in an unusable state -- the worst part was that it had removed all the yast repositories in a way that produced errors when I reran yast. The third installation went well. Recommendation: 1. Try to get the system in a stable bootable condition as fast as possible, even if it takes putting back in the reboot that 10.1 did. That reboot was not annoying to me -- rather it saved me when my CD drive died during loading the 3rd CD of version 10.1 (I finished the install via Internet using yast). 2. Please look at how the information is displayed in the conflict resolution dialog. For me the original package is not clearly displayed, and I have certainly missunderstood what deleting that particular package meant (confusion between deleting it and not upgrading). 3. Abort clearly doesn't work as it should. The process of deleting packages just ignored all my requests to abort. Please note that I mention this for your information, but the installation went no worse than the previous distros I've installed (RedHat, Fedora, debian, Ubuntu, ...). Despite the problems I had, I think you have the best installer of any distro. -- 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.

1 6

[Bug 233619] New: iFolder client never finishes syncronization - looks like simias/mono issue
by bugzilla_noreply＠novell.com 07 Jul '08

07 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=233619 Summary: iFolder client never finishes syncronization - looks like simias/mono issue Product: openSUSE 10.2 Version: RC 5 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: dvosburg(a)novell.com QAContact: qa(a)suse.de Tried with numerous iFolders, and syncronization fails after a different number of files and different disk space each time. Log simply returns 'Syncronization Complete' with hundreds of files that are not syncronized. Occurs with shipping code, and after upgrading mono to 1.2.2, recompiling simias and iFolder client daily releases. Works as it should on SLE_10 and 10.1 with the same mono, simias, and ifolder-client -- 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.

1 7

[Bug 237690] New: *.pc missing in devel-32bit RPMs
by bugzilla_noreply＠novell.com 06 Jul '08

06 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=237690 Summary: *.pc missing in devel-32bit RPMs Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de trying to build 32bit software on 64bit SUSE is a pain, because there are no *.pc pkgconfig files for those 32bit libs included: atuin> pin /usr/lib64/pkgconfig/ | wc 302 2898 43432 atuin> pin /usr/lib/pkgconfig/ | wc 303 2908 41859 atuin> pin /usr/lib/pkgconfig/ | grep -c 32bit 0 please include *.pc files in devel-32bit RPMs too, so that I can set PKG_CONFIG_PATH to find/use 32bit libs... -- 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.

1 11