August 2013 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] condition test for a local build?
by Greg Freemyer 01 Aug '13

01 Aug '13

All, I need to have a pre-compile test that only runs if it is a local build. How do I do that? == details I maintain one package (python-plaso) that comes with a optional pre-compile test module to verify that for 6 specific libraries the latest available libraries are installed prior to building. It's a python script that looks on the Internet for the latest available tarballs for the 6 libraries. LIBYAL_URLS = { 'libevt': 'https://googledrive.com/host/0B3fBvzttpiiSYm01VnUtLXNUZ2M/', 'libevtx': 'https://googledrive.com/host/0B3fBvzttpiiSRnQ0SExzX3JjdFE/', 'liblnk': 'https://googledrive.com/host/0B3fBvzttpiiSQmluVC1YeDVvZWM/', 'libmsiecf': 'https://googledrive.com/host/0B3fBvzttpiiSVm1MNkw5cU1mUG8/', 'libregf': 'https://googledrive.com/host/0B3fBvzttpiiSSC1yUDZpb3l0UHM/', 'libvshadow': 'https://googledrive.com/host/0B3fBvzttpiiSZDZXRFVMdnZCeHc/', } I maintain all 6 of those too, so when I build python-plaso locally, I'd like it to bark if those are out of date. Alternatively, there are about 25 similarly structured libraries (libyal - yet another library). What would need to be done for the auto-version checker for factory to notice there is a new tarball and put in my routine factory status email? (That may already work, the download tarballs being hosted on a googledrive is something that just started a few months ago and I am just now updating the DL_URL fields in my spec files. Greg -- Greg Freemyer -- 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] Milestone4 next week
by Stephan Kulow 01 Aug '13

01 Aug '13

Hi, Remember that next week is the last milestone, which also marks feature freeze[¹]. "All changes need to be justified, e.g. by referencing explanations in bug tracking systems". We have the yast2->Ruby change in, kernel 3.11(RC) is currently in staging, just is systemd 205 - both may end up on M4 too. The weeks after that should see some polishing and a lot of testing, so we can have a solid Beta1 (once everyone is back from vacation we can pick the best wallpaper ;-) Greetings, Stephan P.S. [1] Additionally it marks the end of my son's Kindergarten, but that's only important to me ;-) -- 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] Version numbers with '+' and '~' in them?
by Greg Freemyer 01 Aug '13

01 Aug '13

Why does rpmlint consider 0~20130416 older than 0.0.0+20130128 ? Does RPM/zypper have the same logic? Is there some way to do a rename (Obsoletes / Provides) to move from 0.0.0 versioning to 0 versioning? == details I've got a package that has been in 12.2 and 12.3 named as: ewftools v0.0.0+20120813. It is currently in factory as v0.0.0+20130113 It's part of a library toolset known as libyal. (about 20 libyal packages in factory now). When the rest of the libyal packages were created post 12.3 they were versioned like libyal-tools v0~20130416, so I'm trying to update the libewf package to create a libewf-tools package that will supersede the old ewftools package Thus I added: Obsoletes: ewftools <= 0.0.0+20130128 Provides: ewftools = %{version} But rpmlint is complaining: libewf-tools.i586: W: self-obsoletion ewftools <= 0.0.0+20130128 obsoletes ewftools = 0~20130416 Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

2 2

[opensuse-packaging] factory submits okay if factory-snapshot doesn't have dependencies
by Greg Freemyer 01 Aug '13

01 Aug '13

All, I'm working on a collection of libraries (libyal). They are not all in the same devel project, so I can build all the packages in my home project, but once I submit them to devel projects, some of the packages quit building for the factory snapshot. Since I know the dependencies are in factory (as of a few hours ago), can I submit the packages now? Or do I need to wait until the BuildRequires libraries have made it into a factory snapshot? An example is filesystems:libsmdev Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 2