[arch-dev-public] backport of symlink fix for pacman?
Every day we get new bugreports of perl not working because a symlink got overwritten. This is a bug in pacman that has been fixed according to git, but there's still no new release with this fix. Any drawbacks of applying http://projects.archlinux.org/git/?p=pacman.git;a=commit;h=7a42e24400499873c 3b9e1e2315edc808d753734 to the current version of pacman?
On 8/17/07, Jan de Groot <jan@jgc.homeip.net> wrote:
Every day we get new bugreports of perl not working because a symlink got overwritten. This is a bug in pacman that has been fixed according to git, but there's still no new release with this fix. Any drawbacks of applying http://projects.archlinux.org/git/?p=pacman.git;a=commit;h=7a42e24400499873c 3b9e1e2315edc808d753734 to the current version of pacman?
I'd need some other input here, but we actually rewrote the whole part dealing with this so I don't know if this patch as it stands will fix all the problems without introducing new ones. It may work in the short term, however. Thoughts on a 3.0.6 release with the locale issue and this issue fixed, and then focusing on 3.1? It has been a bit tough for me to juggle real life with pacman, so I don't tend to worry about bugfix releases anymore unless it is something really serious. -Dan
Dan McGee wrote:
On 8/17/07, Jan de Groot <jan@jgc.homeip.net> wrote:
Every day we get new bugreports of perl not working because a symlink got overwritten. This is a bug in pacman that has been fixed according to git, but there's still no new release with this fix. Any drawbacks of applying http://projects.archlinux.org/git/?p=pacman.git;a=commit;h=7a42e24400499873c 3b9e1e2315edc808d753734 to the current version of pacman?
I'd need some other input here, but we actually rewrote the whole part dealing with this so I don't know if this patch as it stands will fix all the problems without introducing new ones. It may work in the short term, however.
Thoughts on a 3.0.6 release with the locale issue and this issue fixed, and then focusing on 3.1? It has been a bit tough for me to juggle real life with pacman, so I don't tend to worry about bugfix releases anymore unless it is something really serious.
I like this idea of a 3.0.6 that doesn't involve a lot more work but just releases these fixes. I'd be happy to help test a 3.0.6 package. - P
On 8/17/07, Paul Mattal <paul@mattal.com> wrote:
Dan McGee wrote:
On 8/17/07, Jan de Groot <jan@jgc.homeip.net> wrote:
Every day we get new bugreports of perl not working because a symlink got overwritten. This is a bug in pacman that has been fixed according to git, but there's still no new release with this fix. Any drawbacks of applying http://projects.archlinux.org/git/?p=pacman.git;a=commit;h=7a42e24400499873c 3b9e1e2315edc808d753734 to the current version of pacman?
I'd need some other input here, but we actually rewrote the whole part dealing with this so I don't know if this patch as it stands will fix all the problems without introducing new ones. It may work in the short term, however.
Thoughts on a 3.0.6 release with the locale issue and this issue fixed, and then focusing on 3.1? It has been a bit tough for me to juggle real life with pacman, so I don't tend to worry about bugfix releases anymore unless it is something really serious.
I like this idea of a 3.0.6 that doesn't involve a lot more work but just releases these fixes. I'd be happy to help test a 3.0.6 package.
OK, I just released a pacman 3.0.5-3 that should fix three issues that were present in 3.0.5 vanilla: * erronous use of chmod (was already fixed with a patch) * Pacman config file parsing issue with tr_TR locale * Symlink to directory overwriting issues All these fixes are done in pacman-cumulative.patch, which is checked into CVS. -Dan
participants (3)
-
Dan McGee
-
Jan de Groot
-
Paul Mattal