Bug 110406 – net-fs/netatalk-2.0.3 stable request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Diego Elio Pettenò (RETIRED) 2005-10-24 22:48:27 UTC]

I'm maintaining the 2.x series of netatalk (as netatalk 1.6 has problems on 
amd64 so I can't even test it in chroot), but the current stable version of 
netatalk is (where present) 1.6.4-r1. 
 
I'd like to see 2.0.3 stable as that is the one currently maintained by 
upstream, and the one I'm maintaining here (1.6 series can be considered 
unmaintained). 
 
ppc64 is actually they only "urgent" stable, as the 1.x series is not 64-bit 
safe, while 2.0.3 should be (works fine on amd64). 
 
Thanks, 
Diego

[Comment 1 Brent Baude (RETIRED) 2005-10-25 12:58:45 UTC]

Marked stable. There was a -r1 ebuild but I didnt mark that one as the bug title
specifically called out 2.0.3.

Thanks

[Comment 2 Luis Medinas (RETIRED) 2005-10-30 14:34:05 UTC]

-2.0.3 stable on amd64

[Comment 3 Joe Jezak (RETIRED) 2005-11-19 16:08:44 UTC]

Marked 2.0.3 ppc stable.

[Comment 4 MATSUU Takuto (RETIRED) 2005-11-21 05:57:36 UTC]

stable 2.0.3 on sh.

[Comment 5 Joshua Jackson (RETIRED) 2005-12-08 19:00:22 UTC]

I just did some testing on x86 for this bug, it appears that there's a collision
with glibc.

* checking 160 files for package collisions
existing file /usr/include/netatalk/at.h is not owned by this package

doing a equerly belongs for the file in question states that it belongs to
sys-libs/glibc-2.3.5-r2 (/usr/include/netatalk/at.h). 

[Comment 6 Diego Elio Pettenò (RETIRED) 2005-12-12 16:21:41 UTC]

Joshua is right, I have overseen that before because I merged netatalk having 
collision-protect disabled the first time I installed it. 
 
Arches: please marked -r2 stable as soon as you can that fixes this (quite 
severe) bug (glibc header overwritten). netatalk 1.6 shown the same behavior. 
 

[Comment 7 Joshua Jackson (RETIRED) 2005-12-14 19:34:01 UTC]

2.0.3-r2 marked stable on x86

[Comment 8 Gustavo Zacarias (RETIRED) 2005-12-20 07:36:45 UTC]

2.0.3-r2 sparc stable.

[Comment 9 Simon Stelling (RETIRED) 2005-12-23 16:11:02 UTC]

diego, please feel free to mark it stable on amd64 yourself

[Comment 10 Simon Stelling (RETIRED) 2005-12-23 16:25:35 UTC]

sorry, missed the fact about the (nonexisting) stable chroot.. readding amd64

[Comment 11 Joe Jezak (RETIRED) 2005-12-25 22:43:46 UTC]

Hansmi has already marked this ppc stable.

[Comment 12 Simon Stelling (RETIRED) 2005-12-31 11:44:20 UTC]

did you see:

QA Notice: the following files are setXid, dyn linked, and using lazy bindings
 This combination is generally discouraged.  Try re-emerging the package:
 LDFLAGS='-Wl,-z,now' emerge netatalk
LAZY usr/bin/afppasswd

at the bottom of the merge process?

marked stable on amd64 nevertheless

[Comment 13 Diego Elio Pettenò (RETIRED) 2005-12-31 13:51:36 UTC]

sh was already stabled, closing bug.

Simon, the problem is just a side, but I fixed it anyway (was a misnamed call).