May 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] CrossToolchain question
by Matwey V. Kornilov 25 Oct '13

25 Oct '13

Hi, In CrossToolchain:avr, I see avr-gcc-* and cross-avr-gcc. What is the difference? What is correct naming? (I suppose the last one). What guidelines/rules should I follow to create CrossToolchain subproject for yet unsupported arch? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 22

[opensuse-packaging] Packaging Guideline enforcement
by Dominique Leuenberger a.k.a DimStar 10 Sep '13

10 Sep '13

Dear Factory contributors and packagers, As openSUSE 12.2 is frozen and Factory is 'open to go wild' again, I would like to announce that the packaging guidelines have some extensions (not really new) that will be stricter enforced than they used to be. Currently a common rule to be 'ignored' or packagers are not aware is around the topics of: - .Changes entries - Patches First, the .changes entry (rpm changelog) surves two purposes: - News for the user - History tracking of packaging changes (often referenced in bugs to verify if a user has the latest packaging bugfixeS). A simple "Update to version x.y.z" is, as before, not accepted. There should be some buzz around the update for the user; some major reasons to the upgrade should be listed Changes on the package itself should be mentioned in a way that any other contributor to the same package can follow traces of why something is the way it is. Commonly, Added (build)dependencies are interesting to be seen, special hacks to make something work in a particular way [..]: Always consider that package maintenance is a distributed task and various contributors need to be able to step up at will. Patches: The rules about patches are listed at http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines . Most prominent is likely the mentioning of the patches life cycle, which forces you to mention additions and removals of patches in the changelog. As history shows, this can be helpful if a patch got removed, and later a regression is reported; finding out when a patch was removed can be crucial in reconstructing feature sets (including contacting the contributor that dropped it.. which is easily extracted from the .changes if listed) The main appeal is to the devel project maintainers / reviewers, to keep out for those rules, to live according to them, as it is frustrating for everybody if a package needs to be declined by the Factory Review team: - The dev prj maintainer is the one getting the 'decline' (as it was usually a forwarded request), which often leaves the 'fixing' to the devel project maintainers, where the 'originator' of the fix would have been willing to actually do that... And the Factory Review team also prefers to see complying submissions to having to reject SRs... reject is not fun for anybody! Looking forward to many more SRs to accept! Dominique / DimStar -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

29 105

[opensuse-packaging] SONAME question
by Greg Freemyer 28 Aug '13

28 Aug '13

I just updated filesystems:ntfs-3g_ntfsprogs to have a new SONAME (83 -> 84) Do I need to add a Obsoletes: statement? Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 8

[opensuse-packaging] Package looking for volunteers: CodeAnalyst
by Cristian Morales Vega 08 Aug '13

08 Aug '13

As per https://bugzilla.novell.com/show_bug.cgi?id=793541 it seems CodeAnalyst needs a new maintainer. Any volunteer? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 13

[opensuse-packaging] can apache HTTP Server be updated to version 2.4.4 [from v-2.4.3]
by doiggl＠velocitynet.com.au 19 Jun '13

19 Jun '13

Hello, Can apache HTTP Server be updated to version 2.4.4 [from v-2.4.3] https://build.opensuse.org/package/show?package=apache2&project=openSUSE%3A… http://httpd.apache.org/download.cgi Stable Release - Latest Version: 2.4.4 (released 2013-02-25) http://httpd.apache.org/download.cgi#apache24 -- Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] package looking for maintainer: the AT daemon
by Cristian Rodríguez 18 Jun '13

18 Jun '13

Hi: I will no longer maintain fix or otherwise care about the "at" daemon, starting now because I would rather devout my time testing and improving systemd.timer(5) So it is now up for grabs. that's all ;) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

19 47

[opensuse-packaging] Discontinuing some old GNOME:* projects in OBS
by Vincent Untz 09 Jun '13

09 Jun '13

Hi, I was looking at https://build.opensuse.org/project/subprojects?project=GNOME and realized we have many many subprojects, with many of them being really old. I've started marking as DISCONTINUED (in the description) some of these projects: - GNOME:STABLE:2.x - GNOME:STABLE:{3.0,3.2,3.4} - GNOME:Backports:2.x - GNOME:Community (superseded with GNOME:Apps, really) At the same time, I'm removing all maintainers and only leaving the gnome-maintainers group (to avoid people changing packages in these projects, but still have a group who can jump in if really needed) and disabling build on Factory when it was still there. I'm planning to do the same for the following projects which have not been active in a long time, so please shout fast (within a week) if you don't want this: - GNOME:Apps:F-Spot - GNOME:Apps:F-Spot:Unstable - GNOME:Apps:Tasque - GNOME:Apps:Tomboy - GNOME:Apps:Tomboy:Unstable - GNOME:Ayatana:11.4 - GNOME:Ayatana:deprecated - GNOME:Evolution and GNOME:Evolution:* - GNOME:GNOME1 Note that I'm not removing any package, nor dropping any repository. So all of this should be revertable. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 1

[opensuse-packaging] Python and CFLAGS
by Cristian Morales Vega 31 May '13

31 May '13

I am trying to compile in openSUSE 12.3 a program which uses "waf" to build. It fails to detect Python.h because the test program is compiled with -O0 and -D_FORTIFY_SOURCE=2, and you can't use both at the same time. The FORTIFY_SOURCE part comes from waf using: "get_config_var('CFLAGS')". And from what I can see that gets the CFLAGS used to build python itself from %{_libdir}/python2.7/config/Makefile, from the python-base package. Now, I don't know the first thing about the "Python way". So, can somebody answer: - There is really some use for Python defining this CFLAGS "config_var"? - It's normal for the build systems to try to retrieve get_config_var('CFLAGS')? Why? - We really need a Makefile in python-base? - And %{_libdir}/python2.7/config/Makefile.pre and %{_libdir}/python2.7/config/Makefile.pre.in in python-devel? - Should the python package be patched to remove "%{optflags}" from %{_libdir}/python2.7/config/Makefile? Thanks. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] Recommended packages ignored when Installing from osb, works with manual download
by Sebastian Schubert 30 May '13

30 May '13

Hi, I want to install the package flac2all: https://build.opensuse.org/package/show?package=flac2all&project=home%3Aseb… which is only available in this very repository (my obs home repository). I thus added the home repository to my local list of repositories (see below for list of activated repositories). Installing from the repository does not take into account the recommended and suggested packages: # zypper in flac2all Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: flac flac2all 2 new packages to install. Overall download size: 554.1 KiB. After the operation, additional 1.6 MiB will be used. Continue? [y/n/?] (y): n If I download the very same rpm directly from build service and install it directly with zypper giving the direct path to the rpm (see above), then the recommended packages will be evaluated: # zypper in /home/schubert/Downloads/flac2all-3.28-2.1.noarch.rpm Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: flac flac2all The following package is recommended, but will not be installed because it's unwanted (was manually removed before): vorbis-tools The following packages are suggested, but will not be installed: lame nero-aac 2 new packages to install. Overall download size: 554.1 KiB. After the operation, additional 1.6 MiB will be used. Continue? [y/n/?] (y): n I would expect the very same behaviour. Is this a bug or a feature? Cheers, Sebastian In the following a list of my repositories. Basically, only the standard openSUSE and my home repository are enabled: # zypper lr --details # | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service ---+-----------------------------+------------------------------------+---------+---------+----------+--------+------------------------------------------------------------------------------------------+-------- 1 | Geo | Geo | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Application:/Geo/openSUSE_12.3/ | 2 | R | R | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/R:/patched/open… | 3 | R_supplement | R supplement | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/R:/supplement/o… | 4 | Science | Science | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/science/openSUSE_12.3/ | 5 | download.opensuse.org-Extra | openSUSE BuildService - KDE:Extra | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_12.3/ | 6 | download.opensuse.org-games | openSUSE BuildService - Games | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_12.3/ | 7 | ftp.gwdg.de-suse | Packman Repository | Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_12.3/ | 8 | google-earth | google-earth | No | Yes | 99 | rpm-md | http://dl.google.com/linux/earth/rpm/stable/x86_64 | 9 | ocefpaf | ocefpaf | No | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/ocefpaf/openSUSE_12.3/ | 10 | openSUSE-12.3-1.7 | openSUSE-12.3-1.7 | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.3/repo/oss/ | 11 | opensuse-guide.org-repo | libdvdcss repository | No | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/12.3/ | 12 | repo-debug | openSUSE-12.3-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/12.3/repo/oss/ | 13 | repo-debug-update | openSUSE-12.3-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/12.3/ | 14 | repo-debug-update-non-oss | openSUSE-12.3-Update-Debug-Non-Oss | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/12.3-non-oss/ | 15 | repo-non-oss | openSUSE-12.3-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/12.3/repo/non-oss/ | 16 | repo-source | openSUSE-12.3-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/12.3/repo/oss/ | 17 | repo-update | openSUSE-12.3-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/12.3/ | 18 | repo-update-non-oss | openSUSE-12.3-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/12.3-non-oss/ | 19 | sebschub | sebschub | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/home:/sebschub/openSUSE_12.3/

1 0

[opensuse-packaging] reminder for systemd services: do not use syslog.target anymore
by Frederic Crozat 29 May '13

29 May '13

Hi all, just a reminder because I had to fix one package (sendmail) which had a hard dependency on syslog.target (Requires), in addition to After=syslog.target. With recent (>202) systemd release, syslog.target is no longer provided: services are ensured they are started after logging socket is setup, so journal will capture all syslog messages and will store them and forward them to syslog implementation (if running). With openSUSE 12.3, having syslog.target was already not doing anything (but the target was still there) but it was removed in Factory. I think very few packages have systemd service file with "Requires=syslog.target", which does break in Factory (sendmail was an example). For packages with only "After=syslog.target", there won't be any issue (since it is just an ordering information). In any case, if you are still seeing services with syslog.target as Requires or After, please clean them. Thanks ! -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 3

[opensuse-packaging] Re: content of change log (Re: [obs submit-request 176782] devel:languages:python/python-ldap: declined by saschpe)
by Sascha Peilicke 28 May '13

28 May '13

Hi Michael, CC'ing opensuse-packaging@ On 05/28/2013 10:00 AM, Michael Ströder wrote: > HI! > > I think in the case of a simple update due to a new upstream release, > especially with a module used by developers, it's the most appropriate change > note to just reference exact release number of the new upstream version. > > The following two approaches are IMO completely wrong: > > 1. Copy&paste the whole possibly lengthy change log of upstream. Sure, but the more important details should be added. > 2. Summarize the change log of upstream release likely leading to incomplete > and therefore useless information. It's anything but useless, especially if there's a potential behavior change. > > The changelog of a package IMO should only mention > > 1. local patches, backports etc. (most important) > > 2. changes to spec files, package build options etc. > > 3. One-line notes about relationship to upstream release. > > 4. Known side effects on other packages. Agreed on all of those :-) > 5. In rare cases changes of upstream code in case upstream code does not > provide a detailed change log. So you really want people to first download the RPM, unrpm it and then search for a ChangeLog or CHANGES or NEWS file? I think it is better to allow users to use the same process they already know, namely "rpm -q --changelog $foo.rpm" and get something meaningful. > Where is this dicussed in detail? I think this was discussed in many ways on opensuse-package@ and probably opensuse-factory@. Please check the archives, we may want to enhance the wiki either way. > > Ciao, Michael. > > SPeilicke(a)suse.com wrote: >> >> State of submit-request #176782 was changed by saschpe: >> >> new -> declined >> >> Comment: >> sorry but you have to provide a more detailed changes entry when updating versions. otherwise this won't enter factory >> >> https://build.opensuse.org/request/diff/176782 >> >> Source >> project: home:stroeder:branches:devel:languages:python >> package: python-ldap >> revision: 5 >> >> Target: >> project: devel:languages:python >> package: python-ldap > -- 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(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

4 7

[opensuse-packaging] E: shlib-policy-name-error
by Shawn W Dunn 22 May '13

22 May '13

So I'm building consort-panel in devel:cloverleaf:Consort/consort-panel and rpmlint is kicking up what is apparently this very serious error: libpanel-consort-applet-4-0.x86_64: E: shlib-policy-name-error (Badness: 10000) libpanel-applet-1-0 [ 152s] Your package contains a single shared library but is not named after its [ 152s] SONAME. Which is fine, I'm working with the upstream developer, and we'll change the name, but what would be the most appropriate name for this library, so we stay consistent with openSUSE policy?

6 12

[opensuse-packaging] high quality HDMI CALBLE
by Sally 22 May '13

22 May '13

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <STYLE type=text/css> </STYLE> <META http-equiv=Content-Type content=text/html;charset=utf-8><BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css></STYLE> <META content="MSHTML 6.00.2900.6380" name=GENERATOR></HEAD> <BODY style="FONT-SIZE: 10.5pt; MARGIN: 10px" bgColor=#ffffff> <DIV><FONT face="Times New Roman" size=3>Dear </FONT></DIV> <DIV><FONT face="Times New Roman" size=3></FONT> </DIV> <DIV><FONT face="Times New Roman" size=3>How are you?</FONT></DIV> <DIV><FONT face="Times New Roman" size=3></FONT> </DIV> <DIV><FONT face="Times New Roman" size=3>I'm Sally from VCOM. I had sent the email about the VCOM to you, i believe you have know something about it, right? The attachment is the specification of the HDMI cable, you can choose which one you like and tell me , i will reply you as soon as possible.</FONT></DIV> <DIV><FONT face="Times New Roman" size=3></FONT> </DIV> <DIV><FONT face="Times New Roman" size=3>Waiting for your reply.</FONT></DIV> <DIV><FONT face="Times New Roman" size=3></FONT> </DIV> <DIV><FONT face="Times New Roman" size=3>Thanks & best regard.</FONT></DIV><SPAN id=fttx_sign_begin></SPAN> <DIV> <DIV><FONT size=3><STRONG></STRONG></FONT> </DIV> <DIV><FONT size=3><STRONG>Sally</STRONG> <BR>Vcom International Ltd<BR> <BR>E-mail:vcom18@vcom.hk<BR>MSN:vcom18@hotmail.com<BR>Tel: +86-20-22832571<BR>Fax:+86-20-22832562</FONT></DIV> <DIV><FONT size=3>Mob:+86-15999942105</FONT></DIV> <DIV><FONT size=3>Skype:vcom18<BR>Address:Youke Business Center. Bulding D 2F/1,Kexin Rd,Tangxia,Tianhe District, Guangzhou City,Guangdong Province,China </FONT></DIV> <DIV> </DIV></DIV><SPAN id=fttx_sign_end></SPAN></BODY></HTML>

1 0

[opensuse-packaging] E: athena 64-bit-portability issue
by Shawn W Dunn 18 May '13

18 May '13

I'm building devel:cloverleaf:Consort/athena, and I get to this stage of the build locally (osc build): 61s] ... running 01-check-debuginfo [ 61s] ... testing for empty debuginfo packages [ 61s] ... running 02-check-gcc-output [ 61s] ... testing for serious compiler warnings [ 61s] (using /usr/lib/build/checks-data/check_gcc_output) [ 61s] (using /var/tmp/build-root/.build.log) [ 61s] E: athena 64bit-portability-issue athena-toolbar.c:457 The offending code from src/athena-toolbar.c is: GtkWidget * athena_toolbar_get_show_location_entry (AthenaToolbar *self) { return self->priv->show_location_entry; } I'm not sure how this would affect portability. Is this a glitch in osc/OBS, or do I have something wrong in my source?

5 6

[opensuse-packaging] W: non-standard-uid nobody
by Dmitriy Perlow 16 May '13

16 May '13

Hello. I am going to submit to Factory https://build.opensuse.org/package/show?package=pdnsd&project=network I got a warning: > pdnsd.i586: W: non-standard-uid /var/cache/pdnsd/pdnsd.cache nobody > A file in this package is owned by an unregistered user id. To register > the > user, please branch the devel:openSUSE:Factory:rpmlint rpmlint package, > add > the user to the "config" file and send a submitrequest. Should I really do it or are there any tricks for such situations? Thanks! -- Dmitriy DA(P).DarkneSS Perlow / Linux x64 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Need help with racket package
by toganm＠opensuse.org 14 May '13

14 May '13

Hi, With the new libpng16 in the factory, I have a problem with the racket package. Currently I have a branch at home:toganm:branches:devel:languages:misc racket where I solved the problem by adding libpng12 to BuildRequires for factory builds. However, I am not happy with the current solution, as it is the last result IMO. It looks as if libpng16 is not backwards compatible. All other releases build fine with other libpng versions available in their respective releases. The problem is at collects/racket/draw/unsafe/png.rkt where using ffi calls racket defines how to use the png. Unfortunately just adding libpng16 to the available options in this file does not help the package to get build in factory. (see the unapplied png16.patch) Since the only other package available in Factory is libpng12 I have added this as BuildRequires and Requires to the package, with the hope something will surface by the time factory goes to m2 or m3. The current approach in upstream is use libpng12 (and by reading the comments in the above mentioned png.rkt they do say png12 and png14 is what they support). So my question is two folds: What do you think about this approach, and if it is OK should I revert the other releases to libpng12 as well or Among thee is there someone who could fix the ffi calls in png.rkt (as I have no knowledge of libpng internals and my lisp/scheme is not at that level) Thanks in advance Togan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] 1k failed at d:l:py?
by Claudio Freire 13 May '13

13 May '13

What's going on with devel:languages:python? A thousand or so failed packages in bleeding edge, and it's been going on for a while now. I've been waiting for it to get fixed... should I do more than wait? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] erlang rpmlint highlight
by Matwey V. Kornilov 13 May '13

13 May '13

Hi, I. Introduction. This is to highlight rpmlint efforts to support erlang based application and libraries. In home:matwey:erlang project, there are packages rebuilt with customized version of rpmlint. Four basic tests has been implemented, some of them are just for demonstration, other may be quite helpful for package maintainers. 1. beam-consists-compile-time Every beam file has six-tuple in CInf chunk, For instance, (2013, 5, 8, 12, 9, 19). Actually, we are not able to remove this information now (but we do want, I suppose). So, this test is mostly for fun. 2. beam-compiled-without-debug_info We can check whether the file has been compiled with turned on debug_info. This is considered as quite desirable by both Fedora and openSUSE packagers. 3. beam-was-not-recompiled Every beam file also tracks filename of the source file from which it has been compiled. Let us take a look at example from real life: [ 1297s] erlang.i586: W: beam-was-not-recompiled /usr/lib/erlang/lib/erts-5.10.1/ebin/zlib.beam /ldisk/egil/git/otp/erts/preloaded/src/zlib.erl [ 1297s] erlang.i586: W: beam-was-not-recompiled /usr/lib/erlang/lib/erts-5.10.1/ebin/prim_zip.beam /ldisk/egil/git/otp/erts/preloaded/src/prim_zip.erl [ 1297s] erlang.i586: W: beam-was-not-recompiled /usr/lib/erlang/lib/erts-5.10.1/ebin/otp_ring0.beam /ldisk/egil/git/otp/erts/preloaded/src/otp_ring0.erl These three files have been compiled from files located at /ldisk/... and obviously it was not inside the OBS. This is quite serious issue, because we can not guarantee that compiled code corresponds to the sources. This leads to paranoid security issues. 4. beam-import-not-found The most sophisticated test. It was inspired by experiments with auto requires/provides for erlang. Erlang has dynamic linking at runtime, so at compile time you can compile a module which requires a function which may even not exist in the whole universe. This makes the packages potentially broken. Even the function really exists in some module, the packager may forget to add proper Requires. Let us again take a look at example from real life: [ 53s] erlang-rfc4627.i586: W: beam-import-not-found /usr/lib/erlang/lib/rfc4627_jsonrpc-0.01/ebin/rfc4627_jsonrpc_cowboy.beam cowboy_http_req:method/1 [ 53s] erlang-rfc4627.i586: W: beam-import-not-found /usr/lib/erlang/lib/rfc4627_jsonrpc-0.01/ebin/rfc4627_jsonrpc_cowboy.beam cowboy_http_req:raw_path/1 [ 53s] erlang-rfc4627.i586: W: beam-import-not-found /usr/lib/erlang/lib/rfc4627_jsonrpc-0.01/ebin/rfc4627_jsonrpc_cowboy.beam cowboy_http_req:headers/1 This package has (optional) interface for cowboy http server. But we don't have rpm package with cowboy http server at all. This case is not so critical, because there are other interfaces. But maybe this package should be split to erlang-rfc4627, erlang-rfc4627-cowboy, erlang-rfc4627-http. This test is quite limited by rpmlint functionality. Cross-dependencies between packages generated from a single .spec are impossible to properly detect and this leads to false-positives. Maybe this should be redesigned to incorporate rules how to specify Requires/Provides for erlang. II. Under the hood. There is python module pybeam https://github.com/matwey/pybeam that is able to efficiently parse whole beam file and represent it as python object. This module is based on quite powerful python-construct module, that is able to parse and build binary structured data. The CheckErlang.py (module for rpmlint) is located at https://github.com/matwey/rpmlint-checks III. So what? Ok, this surely requires further testing, bug-hunting and discussion. But now, I would like to get some feedback from opensuse rpmlint maintainers and everyone to whom this all may concern. And surely, I think sooner or later this should be included into our factory rpmlint. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1

[opensuse-packaging] Deadline Extended - CFP: SCIECONF 2013
by info＠scieconf.com 09 May '13

09 May '13

Dear Authors, We apologise if you receive multiple copies of this message. Due to several requests on further extensions on submissions, we have considered extending submission on SCIECONF as follows: ======================================================================= C A L L F O R P A P E R S The 1st International VIRTUAL Conference (SCIECONF 2013) www.scieconf.com June, 10. - 14., 2013 =============== Important Dates =============== Submission Deadline: 31. May 2013 (EXTENSION) Authors Notification: 7. June 2013 (EXTENSION) Final Manuscript: 10. June 2013 Conference Dates: 10. - 14. June 2013 ===== Scope ===== The SCIECONF 2013 (www.scieconf.com) is event for researchers and scientific community, with ambitions to be well known, respected and high quality conference instantly growing in each year. The SCIECONF 2013 International VIRTUAL Conference connects scientists around the world. The main objective of the SCIECONF 2013 is to bring together researchers from many scientific areas with the aim of encouraging the exchange of ideas and experience. The conference is looking for original, unpublished research, projects reports, comparative studies, etc. All submitted papers will be peer-reviewed by reviewers. The SCIECONF 2013 seeks original contributions in all relevant areas, including but not limited to the following topics: ================== Topics of Interests ================== - Business Management - Marketing - Economy and Business Economics - Public service, Law - Financing and Accounting - Psychology, Sociology and Pedagogy, Social Science - Medicine - Veterinary medicine - Art, Religion, History, Culturology, Philosophy - Linguistics - Ecology - Agriculture - Natural science - mathematics - Natural science - chemistry - Natural science - biology - Natural science - physics - Electronics, Electrical Systems, Electrical Engineering - Energy - Industrial and Civil Engineering - Informatics - Information Technology - Wireless Technology - Hardware Technology - Transport and Logistics ============================ Paper Submission Guidelines ============================ Submit a full paper not more than six pages length (Proceedings Manuscript: two columns, single-spaced), including figures and references. You can find instructions how to format the Proceedings Manuscript at the following web page: http://scieconf.com/uploads/artfiles/1367354298-SCIECONF-TEMPLATE.docx Authors of all accepted papers will be informed about preparing and submitting the final manuscript(s) together with the notification of acceptance. ======================================== Special issues of international journals ======================================== The best selected papers at SCIECONF 2013 conference will be considered for publication in several Issues in International Journals (extended versions). ======================================== For Further Information Contact: info(a)scieconf.com www.scieconf.com ======================================== ----------------------------------------------------------------------- If you do not want to receive any more informational emails, visit http://www.my-conf.com/unsubscribe.php?c=FX2DWn+Hiz6B03TR9RuW+wrsGoNQveKlvn… -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] whitespace in directory name in specfile?
by Marguerite Su 08 May '13

08 May '13

Hi, here's the background: I wrote a shell script to make a package like steam in games. It'll use update-messages and update-scripts mechanisms to download commercial data on the user's own system to avoid unclear copyright. Then I have to %ghost all the files to keep track of them. But there're filenames and directory names with whitespaces in them. And it's hardcoded in the data config so I can't change. So how to write such names with whitespaces in RPM specfile? Anyone can share some experience? Greetings Margueirte -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 4

[opensuse-packaging] HDMI cable
by Sally 08 May '13

08 May '13

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns:o = "urn:schemas-microsoft-com:office:office"><HEAD> <STYLE type=text/css> </STYLE> <META http-equiv=Content-Type content=text/html;charset=utf-8><BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css> </STYLE> <BASE target=_blank> <STYLE type=text/css></STYLE> <META content="MSHTML 6.00.2900.6357" name=GENERATOR></HEAD> <BODY style="FONT-SIZE: 10.5pt; MARGIN: 10px" bgColor=#ffffff> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt">Dear friend,</SPAN></FONT></DIV> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt"></SPAN></FONT> </DIV> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt">How are you ?</SPAN></FONT></DIV> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt"></SPAN></FONT> </DIV> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt">I'm Sally from VCOM. Could you pls spend 1 min to read my email? Thanks a lot.</SPAN></FONT></DIV> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt"></SPAN></FONT> </DIV> <DIV><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt">We specialize in the computer cables & accessories and computer electronic for more than 18 years. The products' line as following:</SPAN><SPAN lang=EN-US style="FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-size: 10.5pt; mso-bidi-font-family: 宋体"><o:p></o:p></SPAN></FONT></DIV> <DIV> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt"> HDMI cable, VGA cable, USB cable, DVI cable, network cable , splitter, headphone& earphone, mouse&keyboard and android player and so on. HDMI cables are the hot selling in our company .</SPAN></FONT></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><o:p> </o:p></SPAN></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt">VCOM is committed to providing high quality computer cables and electronics to global consumers with competitive price. Up till now, VCOM has more than 84 distributors in global different countries.</SPAN><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><o:p></o:p></SPAN></FONT></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><o:p> </o:p></SPAN></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt"><FONT face="Times New Roman">The following is the website of our company. pls check it.  </FONT></SPAN><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><A href="http://www.vcom.hk/">http://www.vcom.hk/</A></SPAN></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"></SPAN> </P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><FONT face="Times New Roman">The attachment is productlist and the specification of the HDMI cable. Pls check it.</FONT></SPAN></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"> <o:p></o:p></SPAN></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><FONT face="Times New Roman"><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt">Looking forward to further talking with you.</P> <HR> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><IMG alt="" hspace=0 src="cid:777@41402.3551415972.154" align=baseline border=0></SPAN><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><o:p></o:p></SPAN></FONT></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><o:p> </o:p></SPAN></P> <P class=MsoNormal style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: left; mso-pagination: widow-orphan" align=left><SPAN lang=EN-US style="FONT-SIZE: 12pt; mso-font-kerning: 0pt"><FONT face="Times New Roman">Kind regards</FONT></SPAN><SPAN lang=EN-US style="FONT-SIZE: 12pt; FONT-FAMILY: 宋体; mso-font-kerning: 0pt; mso-bidi-font-family: 宋体"><o:p></o:p></SPAN></P></DIV><SPAN id=fttx_sign_begin></SPAN> <DIV> <DIV><FONT size=3><STRONG></STRONG></FONT> </DIV> <DIV><FONT size=3><STRONG>Sally</STRONG> <BR>Vcom International Ltd<BR> <BR>E-mail:vcom18@vcom.hk<BR>MSN:vcom18@hotmail.com<BR>Tel: +86-20-22832571<BR>Fax:+86-20-22832562</FONT></DIV> <DIV><FONT size=3>Mob:+86-15999942105</FONT></DIV> <DIV><FONT size=3>Skype:vcom18<BR>Address:Youke Business Center. Bulding D 2F/1,Kexin Rd,Tangxia,Tianhe District, Guangzhou City,Guangdong Province,China </FONT></DIV> <DIV> </DIV></DIV><SPAN id=fttx_sign_end></SPAN></BODY></HTML>

1 0

[opensuse-packaging] uncertainties about patch packaging
by Adam Spiers 07 May '13

07 May '13

Hi all, there are some minor issues with: https://en.opensuse.org/openSUSE:Packaging_Patches_guidelines Firstly, it does not document the exact format I should use in the .changes entry. The "Patch life cycle" section says: Any of those stages needs to be mentioned in the .changes file, including the file name of the patch. For example: * Add package-awesomeness.patch: Makes package awesome ... but an example is not sufficient to document a format. It's not clear whether documenting movement through the patch cycle in the .changes file is supposed to be machine-parseable, or just readable by humans. Either way, the requirements for conformity need to be more explicit. It's also unclear how I should add a line # PATCH-FIX-OPENSUSE fix-for-opensuse-specific-things.patch bnc#123456 when there is no bnc entry. If it's OK to omit the bnc# field, the page should say that. Or if it's not, the page should explicitly say that a bugzilla entry should be filed if one doesn't already exist. Finally, the page is entitled 'guidelines', but if non-conformance is grounds for rejecting a submitreq, I think 'guidelines' is too weak and it really should be labelled as a 'policy'. Thanks! Adam -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

6 16

[opensuse-packaging] [help]how to local build XX-32bit rpm on a x86_64 machine?
by Jun Hu 06 May '13

06 May '13

Hi Guys: I want to build a zlib-devel-32bit rpm (for example: zlib-devel-32bit-1.2.7-7.1.x86_64.rpm ) , I have known I can build it successfully via OBS website , choosing the repositiory i586 , the build log is as follows: [ 36s] build: extracting built packages... [ 36s] libz1-1.2.7-7.1.i586.rpm [ 36s] zlib-devel-1.2.7-7.1.i586.rpm [ 36s] zlib-devel-static-1.2.7-7.1.i586.rpm [ 36s] libz1-32bit-1.2.7-7.1.x86_64.rpm [ 36s] zlib-devel-32bit-1.2.7-7.1.x86_64.rpm [ 36s] zlib-devel-static-32bit-1.2.7-7.1.x86_64.rpm [ 36s] zlib-1.2.7-7.1.src.rpm [ 36s] _statistics but if using local build , I found it can't generate the rpm by command "osc build i586" or "osc build " osc build i586's log: [ 90s] [ 90s] junwork.opensuse.com finished "build zlib.spec" at Sun May 5 02:45:47 UTC 2013. [ 90s] /var/tmp/build-root/usr/src/packages/SRPMS/zlib-1.2.7-7.1.1.src.rpm /var/tmp/build-root/usr/src/packages/RPMS/i586/zlib-devel-static-1.2.7-7.1.1.i586.rpm /var/tmp/build-root/usr/src/packages/RPMS/i586/zlib-devel-1.2.7-7.1.1.i586.rpm /var/tmp/build-root/usr/src/packages/RPMS/i586/libz1-1.2.7-7.1.1.i586.rpm osc build 's log: [ 71s] [ 71s] junwork.opensuse.com finished "build zlib.spec" at Sun May 5 02:52:52 UTC 2013. [ 71s] /var/tmp/build-root/usr/src/packages/SRPMS/zlib-1.2.7-7.1.1.src.rpm /var/tmp/build-root/usr/src/packages/RPMS/x86_64/libz1-1.2.7-7.1.1.x86_64.rpm /var/tmp/build-root/usr/src/packages/RPMS/x86_64/zlib-devel-1.2.7-7.1.1.x86_64.rpm /var/tmp/build-root/usr/src/packages/RPMS/x86_64/zlib-devel-static-1.2.7-7.1.1.x86_64.rpm now, how to local build XX-32bit rpm on a x86_64 machine? -- --------------------------------------------------------- Jun Hu DSE In Suse China. ---------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

5 11

[opensuse-packaging] Are factory live images broken - https://build.opensuse.org/stage/project/monitor?project=openSUSE%3AFactory%3ALive
by doiggl＠velocitynet.com.au 06 May '13

06 May '13

Hello, Are factory live images broken ? --Glenn From https://build.opensuse.org/stage/project/monitor?project=openSUSE%3AFactory… Examples: kiwi-image-livecd-gnome.i586 unresolvable kiwi-image-livecd-gnome.x86_64 unresolvable kiwi-image-livecd-kde.i586 unresolvable kiwi-image-livecd-kde.x86_64 unresolvable kiwi-image-livecd-x11 unresolvable unresolvable openSUSE-images unresolvable unresolvable nothing provides libzypp.so.1200 needed by PackageKit-backend-zypp, nothing provides libzypp.so.1200(ZYPP_plain) needed by PackageKit-backend-zypp, nothing provides libzypp.so.1200 needed by libyui-ncurses-pkg4, nothing provides libzypp.so.1200(ZYPP_plain) needed by libyui-ncurses-pkg4, nothing provides libzypp.so.1200 needed by libyui-gtk-pkg4, nothing provides libzypp.so.1200(ZYPP_plain) needed by libyui-gtk-pkg4 nothing provides libzypp.so.1200()(64bit) needed by PackageKit-backend-zypp, nothing provides libzypp.so.1200(ZYPP_plain)(64bit) needed by PackageKit-backend-zypp, nothing provides libzypp.so.1200()(64bit) needed by libyui-ncurses-pkg4, nothing provides libzypp.so.1200(ZYPP_plain)(64bit) needed by libyui-ncurses-pkg4, nothing provides libzypp.so.1200()(64bit) needed by libyui-gtk-pkg4, nothing provides libzypp.so.1200(ZYPP_plain)(64bit) needed by libyui-gtk-pkg4 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] Can reiser4progs package be updated from v1.0.7 to v1.0.8 - source update released
by doiggl＠velocitynet.com.au 04 May '13

04 May '13

Hello, Can reiser4progs package be updated from v1.0.7 to v1.0.8 source update released -> http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/re… https://build.opensuse.org/package/show?package=reiser4progs&project=filesy… openSUSE Build Service > Projects > filesystems > reiser4progs Thanks Glenn -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 1