[mirror-admin] Hardlinking broken on the master?

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Fri, 4 Nov 2011 14:15:24 -0500
Chris Adams <cmadams at hiwaay.net> escribió:
> Once upon a time, Chris Adams <cmadams at hiwaay.net> said:
> > I see that Fedora 16 final has been staged.  It appears that
> > hardlinking is still not being done between trees:
> 
> Looking at it more: some things are linked, some things are not.  Now
> that my sync has finished for example, I see:
> 
> $ find * -name mscore-1.1-1.fc16.src.rpm | xargs ls -l
> -rw-r--r-- 2 mirror mirror 82314084 Jul 31 09:31
> development/16/source/SRPMS/mscore-1.1-1.fc16.src.rpm -rw-r--r-- 2
> mirror mirror 82314084 Jul 31 09:31
> releases/16/Everything/source/SRPMS/mscore-1.1-1.fc16.src.rpm
> -rw-rw-r-- 1 mirror mirror 82314084 Jul 31 09:31
> releases/16/Fedora/source/SRPMS/mscore-1.1-1.fc16.src.rpm -rw-rw-r--
> 1 mirror mirror 82314084 Jul 31 09:31
> releases/test/16-Beta/Fedora/source/SRPMS/mscore-1.1-1.fc16.src.rpm
> 
> 
> The only difference is in the permissions.  Why are some files group
> writable and some not (especially within a single release tree)?

its not intentionally broken, i even specifically ran hardlink after
rsyncing with --link-dest we have different processes that do the
different pieces of the compose and release process. anything i
manually run i always set the umask to 002 so that one of the other
release engineers will have perms to the bits to do things afterwards.
ive done it the same since taking over release engineering.so i guess
its been broken for awhile,  thanks for bringing it up ill look to get
it fixed and try to work out a way to make sure we dont do it again.

Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk60WX4ACgkQkSxm47BaWffE+wCfd3QmzVZhRejZodY3Di7xSpR4
EfkAmwS5TEdxeBcVnJUJxmo9L9PPptt/
=Pt2k
-----END PGP SIGNATURE-----

--