[opensuse-packaging] Factory status
The following packages have been failing to build on Factory for more than 7 days. This is a reminder for anybody that could be interested in any of them. Any package failing to build for more than 100 days is in danger of being dropped by Coolo without previous warning (other than these emails). Name Devel project User Status - libgcj43 openSUSE:Factory matz2 Fails for 285 days: undefined reference to `__cxa_call_unexpected' - elilo Base:System rwill Fails for 100 days: undefined reference to `__stack_chk_fail_local' (New upstream version 3.14 available) - selinux-policy security:SELinux alanrouse Fails for 82 days: error(s) encountered while parsing configuration (Different changes in devel project (since 6 months)) - libgcj41 openSUSE:Factory matz2 Fails for 55 days: java test cases... - compiz X11:Compiz bekun Fails for 52 days: kwin changes - kdegraphics3 KDE:KDE3 Ansus Fails for 50 days: gphoto update (Current sources were declined: request 138654) - xerces-j2-bootstrap openSUSE:Factory mvyskocil Fails for 41 days: temporary failure - hawk network:ha-clustering:Factory tserong Fails for 41 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) - python-tagpy devel:languages:python saschpe Fails for 41 days: taglib update - rubygem-webyast-time YaST:Web kwk Fails for 39 days: Missing partial shared/online_help (Different changes in devel project (since 3 days)) - grub Base:System duwe Fails for 34 days: error: 'stdscr' undeclared (first use in this function) (New upstream version 1.96 available) - trustedgrub security duwe Fails for 34 days: error: 'stdscr' undeclared (first use in this function) - libsyncml0 mobile:synchronization:FACTORY cstender Fails for 34 days: error: 'g_mutex_new' is deprecated - irc-otr server:irc AndreasStieger Fails for 31 days: error: too few arguments to function 'otrl_message_receiving' - psi network *vdziewiecki Fails for 31 days: error: 'OtrlMessageAppOps' has no member named 'notify' (Current sources were declined: request 138463) - tasks GNOME:Apps os-gnome-maintainers Fails for 31 days: "Only <libecal/libecal.h> should be included directly. - libopensync-plugin-evolution2 mobile:synchronization:FACTORY cstender Fails for 31 days: Only <libebook/libebook.h> should be included directly. - gnome-phone-manager GNOME:Apps os-gnome-maintainers Fails for 31 days: Only <libebook/libebook.h> should be included directly. - planner GNOME:Apps os-gnome-maintainers Fails for 31 days: error: libedataserver/e-source-list.h: No such file or directory - gnome-do-plugins GNOME:Apps os-gnome-maintainers Fails for 31 days: Type `FlickrNet.FoundUser' does not contain a definition for `Username' - qutim KDE:Distro:Factory magist3r Fails for 31 days: libotr update - f-spot GNOME:Apps os-gnome-maintainers Fails for 31 days: The type or namespace name `Licenses' could not be found - python3-numpy openSUSE:Factory matejcik Fails for 30 days: 'PyUnicodeObject' has no member named 'length - python3-progressbar openSUSE:Factory saschpe Fails for 30 days: 'format' in __slots__ conflicts with class variable - python3-SQLAlchemy openSUSE:Factory saschpe Fails for 30 days: __init__() takes 2 positional arguments but 3 were given - python3-Sphinx openSUSE:Factory saschpe Fails for 30 days: No module named 'rst' - openal-soft devel:openSUSE:Factory lnussel Fails for 27 days: shlib-policy-name-error (Badness: 10000) libopenal1 - nss_ldap network:ldap rhafer Fails for 24 days: vers_string: command not found (Current sources were declined: request 139094) - yast2-network YaST:Head mfilka Fails for 24 days: broken test suite (Current sources were declined: request 140030) - libgdiplus0 Mono:Factory ajorgensen Fails for 23 days: https://bugzilla.novell.com/show_bug.cgi?id=778506 (Different changes in devel project (since 2 months)) - qt3-extensions openSUSE:Factory Ansus Fails for 22 days: png15 switch - csound multimedia:apps tiwai Fails for 20 days: error: unknown type name 'PARSE_PARM' - qt3-devel-doc openSUSE:Factory Ansus Fails for 20 days: libpng15 switch - libQtWebKit4 KDE:Qt dirkmueller Fails for 20 days: too many arguments to function 'int WebCore::XPath::xpathyyparse()' - gstreamer-0_10-plugins-vaapi multimedia:libs tiwai Fails for 20 days: unknown type name 'PFNGLMULTITEXCOORD2FPROC' - uwsgi server:http jimfunk Fails for 20 days: broken erlang - libreoffice LibreOffice:Factory pmladek Fails for 18 days: UTF8.h: No such file or directory (Different changes in devel project (since 4 days)) - sgmltool Publishing keichwa Fails for 16 days: bison update - branding-basedonopensuse system:install:head coolo Fails for 15 days: gdmflexiserver conflicts - installation-images system:install:head snwint Fails for 12 days: package changes (Different changes in devel project (since 1 day)) - ibus-rime M17N *Ignotusp Fails for 11 days: undefined reference to `RimeSetupLogging' - argus security mseben Fails for 11 days: bison/flex update (Current sources were declined: request 139872) - libsmi network:utilities nadvornik Fails for 11 days: bison/flex update - dosemu Emulators snwint Fails for 11 days: bison/flex update - openttd-opengfx games ammler Fails for 11 days: broken test suite (Different sources in devel project (since 10 days)) - crawl games saschpe Fails for 9 days: pngs can't be opened I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people? I include the user not as a blame game, but hoping it means we get better information about who is actually maintaining a package. The two cases with a '*' on it are the ones were I took the last name from a long list of project maintainers. But where it's actually not obvious who maintains it. I ignored changelogs on purpose. The information should be available in the package metadata. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 4 November 2012 12:38, Cristian Morales Vega
- libgdiplus0 Mono:Factory ajorgensen Fails for 23 days: https://bugzilla.novell.com/show_bug.cgi?id=778506 (Different changes in devel project (since 2 months))
The email to ajorgensen@novell.com wasn't delivered. Are all @novell.com emails now invalid? If so, is such an email in the OBS a sign that that person is not working for Suse any more? Is ajorgensen still active or did he stop contributing to openSUSE when all the Xamarin thing happened? Notice that: $ osc my prj -U ajorgensen Banshee GNOME:Community home:ajorgensen home:ajorgensen:archer security:bandit $ osc my pkg -U ajorgensen Mono/IPCE Mono/boo-legacy Mono/gnome-desktop-sharp2 Mono/gtksourceview-sharp2 Mono/monotools-server Mono/ndesk-dbus Mono/ndesk-dbus-glib Mono/uiaatkbridge Mono/uiautomation Mono/uiautomationwinforms Mono:Community/Mono_ASP.NET_BlogStarterKit Mono:Community/Mono_ASP.NET_ClassifiedsStarterKit Mono:Community/Mono_ASP.NET_ClubWebSite Mono:Community/apache2-mono-complete Mono:Community/bareftp Mono:Community/flickrnet Mono:Community/gdata-sharp Mono:Community/gtwitter Mono:Community/last-exit Mono:Community/log4net Mono:Community/mojoportal Mono:Community/mono-addins Mono:Community/mono-fuse Mono:Community/mono-zeroconf Mono:Community/mysql-connector-net Mono:Community/ndesk-dbus Mono:Community/ndesk-dbus-glib Mono:Community/nhibernate Mono:Community/nini Mono:Community/nunit Mono:Community/opentf Mono:Community/taglib-sharp Mono:Community/taoframework Mono:Community/wf-apps Mono:Community:smuxi/nini Mono:Community:smuxi/smuxi Mono:Factory/IPCE Mono:Factory/apache2-mod_mono Mono:Factory/boo Mono:Factory/flickrnet Mono:Factory/gnome-desktop-sharp2 Mono:Factory/gnome-keyring-sharp Mono:Factory/gnome-sharp2 Mono:Factory/gtk-sharp2 Mono:Factory/gtksourceview-sharp2 Mono:Factory/ikvm Mono:Factory/libgdiplus0 Mono:Factory/libgluezilla0 Mono:Factory/mono-addins Mono:Factory/mono-basic Mono:Factory/mono-core Mono:Factory/mono-debugger Mono:Factory/mono-nat Mono:Factory/mono-tools Mono:Factory/mono-zeroconf Mono:Factory/monodevelop Mono:Factory/monodevelop-boo Mono:Factory/monodevelop-database Mono:Factory/monodevelop-debugger-gdb Mono:Factory/monodevelop-debugger-mdb Mono:Factory/monodevelop-java Mono:Factory/monodevelop-python Mono:Factory/monodevelop-vala Mono:Factory/monotorrent Mono:Factory/monsoon Mono:Factory/nant Mono:Factory/ndesk-dbus Mono:Factory/ndesk-dbus-glib Mono:Factory/webkit-sharp Mono:Factory/xsp ... Is the Mono stack in openSUSE unmaintained? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, 4 Nov 2012 12:47:27 +0000, Cristian Morales Vega
Is ajorgensen still active
Seems like he isn't with Novell anymore, as I can't find him in the internal Novell Address Book. So we should start searching for new maintainers.
or did he stop contributing to openSUSE when all the Xamarin thing happened
Seems so. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, Nov 04, 2012 at 12:47:27PM +0000, Cristian Morales Vega wrote:
On 4 November 2012 12:38, Cristian Morales Vega
wrote: - libgdiplus0 Mono:Factory ajorgensen Fails for 23 days: https://bugzilla.novell.com/show_bug.cgi?id=778506 (Different changes in devel project (since 2 months))
The email to ajorgensen@novell.com wasn't delivered. Are all @novell.com emails now invalid? If so, is such an email in the OBS a sign that that person is not working for Suse any more? Is
The colleagues that work for Novell still have Novell addresses. Usualy SUSE employees however have suse.com addresses these days.
ajorgensen still active or did he stop contributing to openSUSE when all the Xamarin thing happened? Notice that:
I think he was laid off with the rest of the Mono team, and also stopped being inactive on openSUSE.
Is the Mono stack in openSUSE unmaintained?
There are one or two people looking at mono packages still I think. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 5 November 2012 08:39, Marcus Meissner
I think he was laid off with the rest of the Mono team, and also stopped being inactive on openSUSE.
OK. So I did ask to all the maintainers of Mono, Mono:Community and Mono:Factory to clean him... and I found there were seven project maintainers in that list in the same situation: aaronbockover bgmerrell gabrielburt grendello mchristensen1 rustyhowell twiest These users are in the metadata of these packages: Mono:Community/cross-mono-build-dependencies Mono:Community/blogengine Mono:Community/gpx2crs Mono:Community/keepass Mono:Community/moma Mono:Community/pgsql-testdb Mono:Community/wf-testapps Banshee:Legacy/banshee Banshee:Legacy/ipod-sharp Banshee:Legacy/mono-zeroconf Banshee:Legacy/ndesk-dbus Banshee:Legacy/ndesk-dbus-glib Banshee:Legacy/podsleuth Banshee:Legacy/taglib-sharp Mono/mono-zeroconf Mono:Factory/mono-zeroconf multimedia:apps/moonshine multimedia:apps/opensuse-codecs-installer multimedia:libs/schroedinger And these projects: Banshee Banshee:Legacy Banshee:Unstable GNOME:Community GNOME:GNOME1 Meego Mono Mono:Community Mono:Factory multimedia:apps multimedia:libs telepathy windows:mingw:win32:EXPERIMENTAL windows:mingw:win64:EXPERIMENTAL X11:RemoteDesktop X11:RemoteDesktop:x2go Could Suse/Novell do the same with a more exhaustive list? Could people with the needed permissions clean this? Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* Cristian Morales Vega
I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
using "plain text", the font is irrelevant, but adding a empty line between item would greatly improve readability. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 4 November 2012 13:46, Patrick Shanahan
* Cristian Morales Vega
[11-04-12 07:40]: ... I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
using "plain text", the font is irrelevant, but adding a empty line between item would greatly improve readability.
It's relevant if you want columns to look like columns. But it seems Thunderbird (or GMail) made something weird with the spaces and the columns were lost. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* Cristian Morales Vega
On 4 November 2012 13:46, Patrick Shanahan
wrote: * Cristian Morales Vega
[11-04-12 07:40]: ... I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
using "plain text", the font is irrelevant, but adding a empty line between item would greatly improve readability.
It's relevant if you want columns to look like columns. But it seems Thunderbird (or GMail) made something weird with the spaces and the columns were lost.
Yes, tb displays by *your* selected (or default as installed) font rather than "plain text". But then *you* have chosen to display "plain text" in a graphical app with a font *you* choose to use. Open the email in a text console and it will *definitely* look different. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* Patrick Shanahan
* Cristian Morales Vega
[11-04-12 09:41]: On 4 November 2012 13:46, Patrick Shanahan
wrote: * Cristian Morales Vega
[11-04-12 07:40]: ... I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
using "plain text", the font is irrelevant, but adding a empty line between item would greatly improve readability.
It's relevant if you want columns to look like columns. But it seems Thunderbird (or GMail) made something weird with the spaces and the columns were lost.
Yes, tb displays by *your* selected (or default as installed) font rather than "plain text". But then *you* have chosen to display "plain text" in a graphical app with a font *you* choose to use. Open the email in a text console and it will *definitely* look different.
Your email client editor also wrapped the text destroying the columns. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 04/11/12 14:49, Patrick Shanahan wrote:
* Patrick Shanahan
[11-04-12 09:46]: * Cristian Morales Vega
[11-04-12 09:41]: On 4 November 2012 13:46, Patrick Shanahan
wrote: * Cristian Morales Vega
[11-04-12 07:40]: ... I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
using "plain text", the font is irrelevant, but adding a empty line between item would greatly improve readability.
It's relevant if you want columns to look like columns. But it seems Thunderbird (or GMail) made something weird with the spaces and the columns were lost.
Yes, tb displays by *your* selected (or default as installed) font rather than "plain text". But then *you* have chosen to display "plain text" in a graphical app with a font *you* choose to use. Open the email in a text console and it will *definitely* look different.
Your email client editor also wrapped the text destroying the columns.
There is too much cleverness in GMail/Thunderbird. I hope now it is better: Name Devel project User Status - libgcj43 openSUSE:Factory matz2 Fails for 285 days: undefined reference to `__cxa_call_unexpected' - elilo Base:System rwill Fails for 100 days: undefined reference to `__stack_chk_fail_local' (New upstream version 3.14 available) - selinux-policy security:SELinux alanrouse Fails for 82 days: error(s) encountered while parsing configuration (Different changes in devel project (since 6 months)) - libgcj41 openSUSE:Factory matz2 Fails for 55 days: java test cases... - compiz X11:Compiz bekun Fails for 52 days: kwin changes - kdegraphics3 KDE:KDE3 Ansus Fails for 50 days: gphoto update (Current sources were declined: request 138654) - xerces-j2-bootstrap openSUSE:Factory mvyskocil Fails for 41 days: temporary failure - hawk network:ha-clustering:Factory tserong Fails for 41 days: cannot load such file -- gettext/tools/rgettext (rails 2 vs rails 3?) - python-tagpy devel:languages:python saschpe Fails for 41 days: taglib update - rubygem-webyast-time YaST:Web kwk Fails for 39 days: Missing partial shared/online_help (Different changes in devel project (since 3 days)) - grub Base:System duwe Fails for 34 days: error: 'stdscr' undeclared (first use in this function) (New upstream version 1.96 available) - trustedgrub security duwe Fails for 34 days: error: 'stdscr' undeclared (first use in this function) - libsyncml0 mobile:synchronization:FACTORY cstender Fails for 34 days: error: 'g_mutex_new' is deprecated - irc-otr server:irc AndreasStieger Fails for 31 days: error: too few arguments to function 'otrl_message_receiving' - psi network *vdziewiecki Fails for 31 days: error: 'OtrlMessageAppOps' has no member named 'notify' (Current sources were declined: request 138463) - tasks GNOME:Apps os-gnome-maintainers Fails for 31 days: "Only <libecal/libecal.h> should be included directly. - libopensync-plugin-evolution2 mobile:synchronization:FACTORY cstender Fails for 31 days: Only <libebook/libebook.h> should be included directly. - gnome-phone-manager GNOME:Apps os-gnome-maintainers Fails for 31 days: Only <libebook/libebook.h> should be included directly. - planner GNOME:Apps os-gnome-maintainers Fails for 31 days: error: libedataserver/e-source-list.h: No such file or directory - gnome-do-plugins GNOME:Apps os-gnome-maintainers Fails for 31 days: Type `FlickrNet.FoundUser' does not contain a definition for `Username' - qutim KDE:Distro:Factory magist3r Fails for 31 days: libotr update - f-spot GNOME:Apps os-gnome-maintainers Fails for 31 days: The type or namespace name `Licenses' could not be found - python3-numpy openSUSE:Factory matejcik Fails for 30 days: 'PyUnicodeObject' has no member named 'length - python3-progressbar openSUSE:Factory saschpe Fails for 30 days: 'format' in __slots__ conflicts with class variable - python3-SQLAlchemy openSUSE:Factory saschpe Fails for 30 days: __init__() takes 2 positional arguments but 3 were given - python3-Sphinx openSUSE:Factory saschpe Fails for 30 days: No module named 'rst' - openal-soft devel:openSUSE:Factory lnussel Fails for 27 days: shlib-policy-name-error (Badness: 10000) libopenal1 - nss_ldap network:ldap rhafer Fails for 24 days: vers_string: command not found (Current sources were declined: request 139094) - yast2-network YaST:Head mfilka Fails for 24 days: broken test suite (Current sources were declined: request 140030) - libgdiplus0 Mono:Factory ajorgensen Fails for 23 days: https://bugzilla.novell.com/show_bug.cgi?id=778506 (Different changes in devel project (since 2 months)) - qt3-extensions openSUSE:Factory Ansus Fails for 22 days: png15 switch - csound multimedia:apps tiwai Fails for 20 days: error: unknown type name 'PARSE_PARM' - qt3-devel-doc openSUSE:Factory Ansus Fails for 20 days: libpng15 switch - libQtWebKit4 KDE:Qt dirkmueller Fails for 20 days: too many arguments to function 'int WebCore::XPath::xpathyyparse()' - gstreamer-0_10-plugins-vaapi multimedia:libs tiwai Fails for 20 days: unknown type name 'PFNGLMULTITEXCOORD2FPROC' - uwsgi server:http jimfunk Fails for 20 days: broken erlang - libreoffice LibreOffice:Factory pmladek Fails for 18 days: UTF8.h: No such file or directory (Different changes in devel project (since 4 days)) - sgmltool Publishing keichwa Fails for 16 days: bison update - branding-basedonopensuse system:install:head coolo Fails for 15 days: gdmflexiserver conflicts - installation-images system:install:head snwint Fails for 12 days: package changes (Different changes in devel project (since 1 day)) - ibus-rime M17N *Ignotusp Fails for 11 days: undefined reference to `RimeSetupLogging' - argus security mseben Fails for 11 days: bison/flex update (Current sources were declined: request 139872) - libsmi network:utilities nadvornik Fails for 11 days: bison/flex update - dosemu Emulators snwint Fails for 11 days: bison/flex update - openttd-opengfx games ammler Fails for 11 days: broken test suite (Different sources in devel project (since 10 days)) - crawl games saschpe Fails for 9 days: pngs can't be opened -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
* Cristian Morales Vega
On 04/11/12 14:49, Patrick Shanahan wrote: ...
Your email client editor also wrapped the text destroying the columns.
There is too much cleverness in GMail/Thunderbird. I hope now it is better:
Much, no wrap and good spacing. Good even when lines wrap. Also looked in gmail via browser and displays very well, especially "view original". -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 4 November 2012 15:30, Cristian Morales Vega
- openal-soft devel:openSUSE:Factory lnussel Fails for 27 days: shlib-policy-name-error (Badness: 10000) libopenal1
Someone can explain this one? It seems that libopenal1 was removed from the expection list, even if libopenal0 is still there. It actually could make sense, since there is no other implementation of openal with libopenal.so.1 while there are two with libopenal.so.0 (because we patch it, but OK). But who did it? Did he inform lnussel? Do we all agree to rename libopenal1-soft to libopenal1? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 4 November 2012 17:55, Cristian Morales Vega
On 4 November 2012 15:30, Cristian Morales Vega
wrote: - openal-soft devel:openSUSE:Factory lnussel Fails for 27 days: shlib-policy-name-error (Badness: 10000) libopenal1
Someone can explain this one? It seems that libopenal1 was removed from the expection list, even if libopenal0 is still there. It actually could make sense, since there is no other implementation of openal with libopenal.so.1 while there are two with libopenal.so.0 (because we patch it, but OK). But who did it? Did he inform lnussel? Do we all agree to rename libopenal1-soft to libopenal1?
Renamed it is: SR#140254 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Cristian Morales Vega wrote:
The following packages have been failing to build on Factory for more than 7 days. This is a reminder for anybody that could be interested in any of them. Any package failing to build for more than 100 days is in danger of being dropped by Coolo without previous warning (other than these emails).
Name Devel project User Status
- libgcj43 openSUSE:Factory matz2 Fails for 285 days: undefined reference to `__cxa_call_unexpected' - elilo Base:System rwill Fails for 100 days: undefined reference to `__stack_chk_fail_local' (New upstream version 3.14 available) - selinux-policy security:SELinux alanrouse Fails for 82 days: error(s) encountered while parsing configuration (Different changes in devel project (since 6 months)) - libgcj41 openSUSE:Factory matz2 Fails for 55 days: java test cases...
The above is roughly what it looks like in knode in monospace.
I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
In knode, they're folded. -- Per Jessen, Zürich (14.9°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, 04 Nov 2012 12:38:33 +0000
Cristian Morales Vega
I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
Wrapped lines and not easy to read. Maybe you should attach original text file, or resort to "modern" methods like LibreOffice table, where font doesn't really matter, and you can embed links. (People with low bandwidth Internet connection can't participate in packaging without solving problems how to handle bigger files that such table.) -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, Nov 4, 2012 at 1:38 PM, Cristian Morales Vega
I'm actually fighting with the plain text format. This time I'm trying with quite long lines that are nice presented _with a monospace font_. What's the result for you, people?
Columns are a tad misaligned (not using monospace), but aside from that, it looks quite alright. Have you tried aligning columns with tabs? Those should work better for non-monospace clients (quite every client out there) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sunday 04 November 2012, Cristian Morales Vega wrote:
The following packages have been failing to build on Factory for more than 7 days. This is a reminder for anybody that could be interested - libgcj43 openSUSE:Factory matz2 - libgcj41 openSUSE:Factory matz2 Fails for 55 days: java test cases...
Hi, would it be possible to get those compilers finally dropped? they don't build on ARM at all, and for months the submitrequests from the devel project are rejected due to licensing policy changes in Factory. I don't see any solution going forward and I don't know what it takes to get it finally removed. I'm pretty sure that nothing depends on it anymore as we have removed all dependencies on those compilers for the ARM port (at least as far as it mattered to us).
- libQtWebKit4 KDE:Qt dirkmueller Fails for 20 days: too many arguments to function 'int WebCore::XPath::xpathyyparse()' - gstreamer-0_10-plugins-vaapi
Fixed. It took me more time to find why I'm included in your email than to actually fix the compile issue. it would be nice to enhance the formatting to make it more obvious to find _my_ problems (perhaps sort by bugowner and not by failed time..) Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, Nov 05, 2012 at 10:34:24PM +0100, Dirk Mueller wrote:
On Sunday 04 November 2012, Cristian Morales Vega wrote:
The following packages have been failing to build on Factory for more than 7 days. This is a reminder for anybody that could be interested - libgcj43 openSUSE:Factory matz2 - libgcj41 openSUSE:Factory matz2 Fails for 55 days: java test cases...
Hi,
would it be possible to get those compilers finally dropped? they don't build on ARM at all, and for months the submitrequests from the devel project are rejected due to licensing policy changes in Factory. I don't see any solution going forward and I don't know what it takes to get it finally removed. I'm pretty sure that nothing depends on it anymore as we have removed all dependencies on those compilers for the ARM port (at least as far as it mattered to us).
For openjdk, we need only the latest gcj, so the former ones can be easilly dropped and everyone will be happy. I've issued following delete requests openSUSE:Factory libgcj41 140302 openSUSE:Factory libgcj43 140303 devel:gcc libgcj43 140304 devel:gcc libgcj41 140304 @michael: feel free to drop the libgcj4[1-6] from devel:gcc too Regards Michal Vyskocil
On Sun, Nov 4, 2012 at 9:38 AM, Cristian Morales Vega
- python-tagpy devel:languages:python saschpe Fails for 41 days: taglib update
Hi. I've got a fix for this, it's in multimedia:libs. Thing is, I just noticed python-tagpy's devel project is actually d:l:p[1], not m:l[2]. The fix needed another fix for taglib[4] (which I just forwarded to factory), so I would have fixed it first in m:l anyway if I had known. I can SR from m:l to d:l:p, and then forward to Factory, but I'm wondering why is there such duplication. I can't see anything depending on it[0]. [0] https://build.opensuse.org/package/binary?arch=x86_64&filename=python-tagpy-0.94.8-2.1.x86_64.rpm&package=python-tagpy&project=multimedia%3Alibs&repository=openSUSE_Factory [1] https://build.opensuse.org/package/files?package=python-tagpy&project=devel%3Alanguages%3Apython [2] https://build.opensuse.org/package/show?package=python-tagpy&project=multimedia%3Alibs [4] https://build.opensuse.org/package/show?package=taglib&project=multimedia%3Alibs -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 08.11.2012 19:30, schrieb Claudio Freire:
On Sun, Nov 4, 2012 at 9:38 AM, Cristian Morales Vega
wrote: - python-tagpy devel:languages:python saschpe Fails for 41 days: taglib update
Hi. I've got a fix for this, it's in multimedia:libs.
Thing is, I just noticed python-tagpy's devel project is actually d:l:p[1], not m:l[2]. The fix needed another fix for taglib[4] (which I just forwarded to factory), so I would have fixed it first in m:l anyway if I had known. I can SR from m:l to d:l:p, and then forward to Factory, but I'm wondering why is there such duplication. I can't see anything depending on it[0].
Generally, all Python modules are collected in d:l:r:e and usually, other projects linkpac from there. It's rather uncommon to be the other way around. Even though the module is closely related to taglib, it's an independent project and IMO belongs into d:l:r:e. So it would make sense if you would indeed submit to d:l:r:e, however will accept the request will also (automatically) forward this to Factory.
[0] https://build.opensuse.org/package/binary?arch=x86_64&filename=python-tagpy-0.94.8-2.1.x86_64.rpm&package=python-tagpy&project=multimedia%3Alibs&repository=openSUSE_Factory [1] https://build.opensuse.org/package/files?package=python-tagpy&project=devel%3Alanguages%3Apython [2] https://build.opensuse.org/package/show?package=python-tagpy&project=multimedia%3Alibs [4] https://build.opensuse.org/package/show?package=taglib&project=multimedia%3Alibs
BTW. I think you sent this mail to half the openSUSE project :-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, Nov 8, 2012 at 4:33 PM, Sascha Peilicke
On Sun, Nov 4, 2012 at 9:38 AM, Cristian Morales Vega
wrote: - python-tagpy devel:languages:python saschpe Fails for 41 days: taglib update
Hi. I've got a fix for this, it's in multimedia:libs.
Thing is, I just noticed python-tagpy's devel project is actually d:l:p[1], not m:l[2]. The fix needed another fix for taglib[4] (which I just forwarded to factory), so I would have fixed it first in m:l anyway if I had known. I can SR from m:l to d:l:p, and then forward to Factory, but I'm wondering why is there such duplication. I can't see anything depending on it[0].
Generally, all Python modules are collected in d:l:r:e and usually, other projects linkpac from there. It's rather uncommon to be the other way around. Even though the module is closely related to taglib, it's an independent project and IMO belongs into d:l:r:e.
So it would make sense if you would indeed submit to d:l:r:e, however will accept the request will also (automatically) forward this to Factory.
So, now I've got it in d:l:p, but it's failing because taglib hasn't made the snapshot repo yet. I guess I have to wait until it does to submit (otherwise autobuild would reject the SR for failing to build in Factory)... right? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 09.11.2012 16:30, schrieb Claudio Freire:
On Thu, Nov 8, 2012 at 4:33 PM, Sascha Peilicke
wrote: On Sun, Nov 4, 2012 at 9:38 AM, Cristian Morales Vega
wrote: - python-tagpy devel:languages:python saschpe Fails for 41 days: taglib update
Hi. I've got a fix for this, it's in multimedia:libs.
Thing is, I just noticed python-tagpy's devel project is actually d:l:p[1], not m:l[2]. The fix needed another fix for taglib[4] (which I just forwarded to factory), so I would have fixed it first in m:l anyway if I had known. I can SR from m:l to d:l:p, and then forward to Factory, but I'm wondering why is there such duplication. I can't see anything depending on it[0].
Generally, all Python modules are collected in d:l:r:e and usually, other projects linkpac from there. It's rather uncommon to be the other way around. Even though the module is closely related to taglib, it's an independent project and IMO belongs into d:l:r:e.
So it would make sense if you would indeed submit to d:l:r:e, however will accept the request will also (automatically) forward this to Factory. So, now I've got it in d:l:p, but it's failing because taglib hasn't made the snapshot repo yet.
I guess I have to wait until it does to submit (otherwise autobuild would reject the SR for failing to build in Factory)... right? If you put in the SR "does not build at the moment till snapshot was updated", I usually do not decline it :)
autobuild is no more btw - the build status is checked by factory-auto, which will not reject for that reason but leave the decision to me. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (11)
-
Claudio Freire
-
Cristian Morales Vega
-
Dirk Müller
-
Marcus Meissner
-
Michal Vyskocil
-
Patrick Shanahan
-
Per Jessen
-
Philipp Thomas
-
Rajko
-
Sascha Peilicke
-
Stephan Kulow