May 2013 - openSUSE Packaging - openSUSE Mailing Lists

[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