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