Riccardo Mottola | 25 Jan 18:45 2015

CHECKPKG_OVERRIDES trivial question

Hi,

when I run "mgar package"and I get override suggestions, is this list 
always "full" or does it take in account those which remain?

In other works, if I have added certain overrides which I consider 
checked, should I still see them (like it is happening for me) or should 
I not?

Riccardo

Dagobert Michelsen | 21 Jan 17:42 2015

Checkpkg false positive

Hi folks,

looks like there are false positives on checkpkg when there are multiple
symlink redirects. The errors look like this:

CHECKPKG_OVERRIDES_CSWlibicu-dev += file-needed-but-no-package-satisfies-it|/opt/csw/lib/amd64/icu/current/Makefile.inc|CSWlibicu-dev|contains|symlink|/opt/csw/lib/amd64/icu/Makefile.inc|which|needs|the|target|file:|/opt/csw/lib/amd64/icu/current/Makefile.inc
CHECKPKG_OVERRIDES_CSWlibicu-dev += file-needed-but-no-package-satisfies-it|/opt/csw/lib/amd64/icu/current/pkgdata.inc|CSWlibicu-dev|contains|symlink|/opt/csw/lib/amd64/icu/pkgdata.inc|which|needs|the|target|file:|/opt/csw/lib/amd64/icu/current/pkgdata.inc
CHECKPKG_OVERRIDES_CSWlibicu-dev += file-needed-but-no-package-satisfies-it|/opt/csw/lib/icu/current/Makefile.inc|CSWlibicu-dev|contains|symlink|/opt/csw/lib/icu/Makefile.inc|which|needs|the|target|file:|/opt/csw/lib/icu/current/Makefile.inc
CHECKPKG_OVERRIDES_CSWlibicu-dev += file-needed-but-no-package-satisfies-it|/opt/csw/lib/icu/current/pkgdata.inc|CSWlibicu-dev|contains|symlink|/opt/csw/lib/icu/pkgdata.inc|which|needs|the|target|file:|/opt/csw/lib/icu/current/pkgdata.inc

This is the filetree at that position:

dam <at> unstable10x [global]:/home/dam/mgar/pkg/libicu54/trunk > find
work/solaris10-i386/pkgroot/opt/csw/lib/icu -ls
5318390    2 drwxr-xr-x   3 dam      csw             6 Jan 21 16:56 work/solaris10-i386/pkgroot/opt/csw/lib/icu
5318391    1 lrwxrwxrwx   1 dam      csw            20 Jan 21 16:56
work/solaris10-i386/pkgroot/opt/csw/lib/icu/Makefile.inc -> current/Makefile.inc
5318392    1 lrwxrwxrwx   1 dam      csw            19 Jan 21 16:56
work/solaris10-i386/pkgroot/opt/csw/lib/icu/pkgdata.inc -> current/pkgdata.inc
5318394    2 drwxr-xr-x   2 dam      csw             4 Jan 21 16:56 work/solaris10-i386/pkgroot/opt/csw/lib/icu/54.1
5318396    1 -rw-r--r--   1 dam      csw           548 Jan 21 16:55 work/solaris10-i386/pkgroot/opt/csw/lib/icu/54.1/pkgdata.inc
5318395    6 -rw-r--r--   1 dam      csw          9826 Jan 21 16:55 work/solaris10-i386/pkgroot/opt/csw/lib/icu/54.1/Makefile.inc
5318393    1 lrwxrwxrwx   1 dam      csw             4 Jan 21 16:56 work/solaris10-i386/pkgroot/opt/csw/lib/icu/current -> 54.1

Best regards

 — Dago

--

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
(Continue reading)

Dagobert Michelsen | 15 Jan 15:26 2015

Subversion

Hi Rupert,

in your subversion update several things are broken. I noticed you bumped the
version and silenced checkpkg:
  https://buildfarm.opencsw.org/source/diff/opencsw/csw/mgar/pkg/subversion/trunk/Makefile?r2=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%2Fsubversion%2Ftrunk%2FMakefile%4024518&r1=%2Fopencsw%2Fcsw%2Fmgar%2Fpkg%2Fsubversion%2Ftrunk%2FMakefile%4023460

This is unfortunate as the checkpkg errors would have lead you to the issue.
Properly updating subversion is difficult, after investigating for the last two
days these are the prerequisites I have identified:

- location of the subversion config changed back from /opt/csw/etc/subversion to
  /etc/subversion leading to the buildfarm config to be not pulled in.
- libtool needs to be updated to honour gcc 4.9.x tags
- this will probably help in allowing cc/gcc mixture of subversion and the
  foreign function apis
- python module needs to be modulated for 2.6/2.7/3.x

So, please, do not just override the checkpkg errors without investigation or
we will have broken packages.

Thanks

  — Dago

--

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

Attachment (smime.p7s): application/pkcs7-signature, 3266 bytes
(Continue reading)

Carsten Grzemba | 8 Jan 11:20 2015
Picon

Re: Doodle Wintercamp 2015

of course, I setup a wiki page

Am 08.01.15 schrieb Peter FELECAN <pfelecan <at> opencsw.org>:

Carsten Grzemba <grzemba <at> contac-dt.de> writes:

> I setup a doodle poll for OpenCSW Winter Camp 2015 which should take
> place in Ilmenau (50° 41′ N, 10° 55′ O)

Can you give us a little bit more information about Ilmenau, where do
you think that the camp will take place, &c.
--
Peter
Carsten Grzemba | 8 Jan 08:43 2015
Picon

Doodle Wintercamp 2015

I setup a doodle poll for OpenCSW Winter Camp 2015 which  should take place in Ilmenau (50° 41′ N, 10° 55′ O)

http://doodle.com/zkgvgc53ydqeff26

Carsten
Carsten Grzemba | 5 Jan 15:46 2015
Picon

Wintercamp 2014 Ilmenau?

I would start the organization of the Wintercamp which should take place in Ilmenau.
Or there are any other plans?

Carsten

How to find [easy] stuff to do

Hello maintainers,

We're well past the winter solstice, nights are getting shorter, but
there are still many long evenings until the spring. If you're looking
for something easy to do, you have, among other things, backgammon,
and package building. Here's how to find easy (and not so easy) stuff
to do:

1. Find stale packages and update them. You can look for your
packages, and/or packages next to names in red: these are inactive
maintainers.

http://buildfarm.opencsw.org/obsolete-pkgs/stale-packages.html

2. Clean up after package renames. When we rename a package, the old
package becomes a stub. To remove stubs we need to make sure nothing
depends on them. We have a page which lists packages that need to be
rebuilt (to free up stubs for removal):

http://buildfarm.opencsw.org/obsolete-pkgs/PkgsToRebuildFrom_unstable_SunOS5.10_i386.html

3. Identify packages that don't work and can be removed. At the bottom
of the stale packages report, there is a list of packages which were
uploaded by someone who no longer uploads anything, and nothing
depends on them. Install the package and try to use it. Does it work?
If not, it should be removed. Broken packages hurt our project's
reputation: People would download one package and if it's broken, they
would assume all packages are like that (which we know is not true).

4. Find a small coding project

http://wiki.opencsw.org/projects-available

5. Review other people's commits

Subscribe to the devel <at>  mailing list and see what other people are
doing. If you're new, you might learn something new. If you've been
here a while, you might help someone else.

==================================================

FAQ

Q: Can I refresh package listed under somebody else's name?
A: Yes! The exception are the core packages like GCC or Apache. In
such case talk to people first. As we talked in October[1], we're
accepting that our package database doesn't reflect reality as to who
owns (cares about) which package. We only have information about who
was the last person to upload each package. The two things are
correlated, but not strongly.

Q: What if I want a package to be assigned to my name?
A: Rebuild it and re-upload.

Have a happy 2015!

Maciej

[1] http://lists.opencsw.org/pipermail/maintainers/2014-October/019510.html

Maciej (Matchek) Bliziński | 28 Dec 20:21 2014

Tweet from tomww ( <at> tomww)

tomww ( <at> tomww) tweetou às 7:06 da tarde on dom, Dez 28, 2014:
<at> phaus
<at> xattack
<at> cpj1
<at> opensolaris
<at> bahamat
<at> opencsw
Anyone of you attending #31C3?
Would enjoy talking w/ u about FOSS packages
(https://twitter.com/tomww/status/549280315370635264?s=03)

Riccardo Mottola | 24 Dec 16:41 2014

EXTRA_RUNPATH_DIRS, LD_OPTIONS an B direct

Hi,

during the building of GNUstep base package, the only mass of warnings I 
have is about two quite similar problems, but proably still different.

CHECKPKG_OVERRIDES_CSWgnustep-base += 
no-direct-binding|/opt/csw/GNUstep/System/Library/Libraries/libgnustep-base.so.1.24.7|is|not|directly|bound|to|soname|libffi.so.5

This is the library I am building against an existing library.

Now, Dagobert explains to me that the problem is related to LD_OPTIONS 
and the -B direct flag.
My problem is understanding better LD_OPTIONS and their interaction with 
configure.

GNUstep's configure is "LDFLAGs" aware and will push them down to the 
make. LD_OPTIONS is instead just ignored and not messed with (I asked 
some of the GNUstep guys).

I understand that gar tries already to set the correct LD_OPTIONS, but 
they do not get used.

First, what are LD_OPTIONS? They seem to be something quite specific to 
Soalris, similar to LDFLAGS but not equivalent.

How do you handle this with other packages using configure? Is it only 
me running into this problem?

as well as

CHECKPKG_OVERRIDES_CSWgnustep-base += soname-not-found|libgnustep-base.so.1.24|is|needed|by|opt/csw/GNUstep/System/Tools/gdnc

which is different since it is some of the tools against the library itself being built.
Here Dago suggests setting EXTRA_RUNPATH_DIRS.

I added in my Makefile
EXTRA_RUNPATH_DIRS = /opt/csw/GNUstep/System/Library/Libraries

but I still get the warning!

Riccardo

Dagobert Michelsen | 23 Dec 23:39 2014

Re: [gar:code] [r24511] - rthurner: trac, ignore checkpkg errors.

Hi Rupert,

> Am 23.12.2014 um 23:29 schrieb Repository GAR Solaris Package Build System code <noreply@...>:
> trac, ignore checkpkg errors. http://sourceforge.net/p/gar/code/24511/

Please do not override the dependency-on-stub error:
  http://wiki.opencsw.org/checkpkg-error-tags#toc17

The package name is now the normalized CSWpy-setuptools instead of CSWpysetuptools.

I can only again point to the above page when there is doubt about when to override
(and when not to) an checkpkg error.

Best regards

  — Dago

--

-- 
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

Attachment (smime.p7s): application/pkcs7-signature, 3266 bytes
Ben Walton | 23 Dec 11:25 2014

git for the stable catalog

Hi All,


I need to update git for the stable catalog to address CVE-2014-9390. I've rolled 2.2.1 for unstable and released it. The stable catalog currently has 1.8.4.

I can force 2.2.1 to stable, but it's a major version bump and has some incompatibilities with the 1.8 series. How are others building for stable, if at all?

Thanks
-Ben

Gmane