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
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
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
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
Good day,
I've recently attempted to repackage Pantheon, Elementary's Desktop
Environment, for openSUSE 12.3. I was able to get almost everything to
work by simply using Alien and installing the correct dependencies in
the correct order. However, Gala, the window manager, wasn't working
well at all.
Gala was showing an erroneous rendering of animations. As such I've
decided to port the libclutter that Elementary uses. Gala worked
admirably well with that version of libclutter, but it was at the
expense of the GNOME Desktop, GDM, and Lightdm. They couldn't use
Elementary's Libclutter and I had to reinstall openSUSE completely to
get rid of it (unisntalling and reinstalling didn't work).
Zypper counts Elementary's Libclutter as a downgrade of the one provided
by openSUSE 12.3.
They use libclutter-1.0.so.0 and libclutter-gtk-1.0.so.0. My coding
skills are too poor to port Gala to a higher level of Libclutter and I
can't figure out how to make Gala use an exclusive version of Libclutter
while the rest of the GNOME Desktop would use the default one.
The majority of Pantheon apps work very well under openSUSE and thanks
to the GNOME:Ayatana repo, we have most of the dependencies. Plank has
already been ported and packaged by an openSUSE user. I was able to get
Noise, Pantheon-files, Slingshot-launcher, and Wingpanel working. If
someone is interested in repackaging Gala for openSUSE, we can have
another desktop environment available.
Sincerely,
Antoine Saroufim
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello.
Recently I've decided to play xmahjongg and surprised that I had failed to
find out it in repos. So I made and submited it to games. When I opened a
request to Factory, coolo answered that we already had xmahjong (not
xmahjongg). I suggest to delete xmahjong and submit xmahjongg, that would
provide and obsolete xmahjong :)
Do I hear any objections?
--
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
Since a few day I've osc broken
osc --help
Traceback (most recent call last):
File "/usr/bin/osc", line 24, in <module>
osccli = commandline.Osc()
File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 82, in
__init__
self._load_plugins()
File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 7926, in
_load_plugins
mod = imp.load_source(modname, os.path.join(plugin_dir, extfile))
File "/var/lib/osc-plugins/osc-collab.py", line 53, in <module>
exclude_stuff.append(helper)
NameError: name 'exclude_stuff' is not defined
osc-0.140.0-103.1.noarch
osc-plugin-install-0.22-1.1.noarch
osc-plugin-overview-0.3.0-1.1.i586
osc-plugin-collab-0.96-12.1.noarch
all coming from openSUSE:/Tools/openSUSE_12.3/ repository
normal ?
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
openSUSE Member
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
I'm trying to create a tarball from a git tag and I'm not getting
logged in for some reason. What is the right syntax for:
git archive --format=tar
--remote=ssh://git@github/com/dkovar/analyzeMFT.git v2.0.4 >
analyzeMFT-v2.0.4.tar
The upstream git repo is at: https://github.com/dkovar/analyzeMFT
Thanks
Greg
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I'm working on update libortp[1]. For now, we have package named libortp8 and
version 0.20.0. Updating to current release 0.22.0 bumps so from 8 to 9. And
now I have a dilemma, should I create a new package named libortp9 and let it
reside along with libortp8 or create libortp (and avoid re-adding new package
in the future when so gets higher number) and remove libortp8?
[1]
https://build.opensuse.org/package/show?package=libortp8&project=devel%3Ali…
--
Pozdrawiam / Best regards,
Mariusz Fik
openSUSE Community Member
GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D
Hello,
this is a request to all package maintainers who have
any kind of BuildRequires for Ghostscript in the spec files.
I ask you to try out if it works for your particular packages
when you use for building packages since openSUSE 12.2 only
either BuildRequires: ghostscript-mini
or BuildRequires: ghostscript-mini-devel
in spec files that have any kind of BuildRequires for Ghostscript.
Background information and reasoning:
Since openSUSE 12.2 we have Ghostscript in the new source packages
"ghostscript" and "ghostscript-mini"
("ghostscript-mini" is only a link to "ghostscript")
and the Ghostscript fonts in the new separated source package
ghostscript-fonts, see
https://bugzilla.novell.com/show_bug.cgi?id=735824
In particular regarding "ghostscript-mini" see
https://build.opensuse.org/package/show?package=ghostscript-mini&project=Pr…
Excerpt:
-----------------------------------------------------------------
Minimal Ghostscript provides only the file
format drivers in particular to output
JPEG PNG PostScript and PDF files but no
printer drivers (in particular neither
'cups' nor 'ijs') and no X11 drivers.
The ghostscript-mini package is only meant
to be used by the openSUSE build service
to avoid possible loops in the build
dependencies because ghostscript-mini
has minimal build dependencies (in particular
neither CUPS nor X11 build dependencies).
For most packages which need to only run
Ghostscript during build, a single line
"BuildRequires: ghostscript-mini"
should be sufficient in the RPM spec file.
For most packages which need Ghostscript
development files to build, a single line
"BuildRequires: ghostscript-mini-devel"
should be sufficient in the RPM spec file.
-----------------------------------------------------------------
You should not need BuildRequires for ghostscript-fonts-* packages
because ghostscript-mini has RPM requires for ghostscript-fonts-std and
ghostscript-fonts-other to make sure that Ghostscript has its fonts, see
https://build.opensuse.org/package/view_file?expand=1&file=ghostscript-mini…
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org