| Summary: | app-arch/gzip-1.3.11 doesn't gunzip with paludis | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dirk Heinrichs <dirk.heinrichs.ext> |
| Component: | Current packages | Assignee: | Stephen Bennett (RETIRED) <spb> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | bique.alexandre, ciaran.mccreesh, dirk.heinrichs, gentoo-bugzilla, greg, pookey |
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Dirk Heinrichs
2007-02-06 12:47:16 UTC
I can confirm this - I suggest higher severity why, no one reads severity anyways Downgrading to 1.3.10 resolves the problem. build up the gzip with debugging enabled and see where it hangs builds/runs fine on my amd64/x86 installs it does this: root 20553 0.0 0.0 2944 1536 pts/7 S+ 13:01 0:00 /bin/bash /usr/libexec/paludis/utils/dounpack cowsay-3.03.tar.gz root 20556 0.0 0.0 1908 680 pts/7 S+ 13:01 0:00 tar zxf /usr/portage/distfiles/cowsay-3.03.tar.gz --no-same-owner root 20557 76.3 0.0 3076 1552 pts/7 R+ 13:01 0:02 /bin/sh /bin/gzip -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -cd -d with more and more -cd's added, seems to recursivly call itself somehow... don't know if that helps. I've downgraded now is everyone here using paludis ? Yep, I do. (In reply to comment #7) > Yep, I do. So don't paste emerge --info next time, you are just confusing people. (And works just fine here w/ portage). (In reply to comment #8) > (And works just fine here w/ portage). For that to be useful information, you'd also have to say whether it breaks for you with Paludis. Breaks here to with paludis. (In reply to comment #10) > Breaks here to with paludis. Which is all very well, but has anyone positively confirmed that it works with Portage but not Paludis on the same system with the same configuration? Installing gzip-1.3.11 breaks only with paludis on my system. With portage-2.1.2-r8 it works.
With paludis my /bin/gzip binary seems to consist of some lines of bash script with the real binary appended afterwards.
I don't have the broken binary anymore since I already replaced it with another one to recover my system.
paludis --info
paludis 0.16.2
Built by root@ummon on 2007-01-28T18:38:03+0100
CXX: i686-pc-linux-gnu-g++ 4.1.1 (Gentoo 4.1.1-r3)
CXXFLAGS: -march=pentium3 -Os -pipe
LDFLAGS:
DATADIR: /usr/share
LIBDIR: /usr/lib
LIBEXECDIR: /usr/libexec
SYSCONFDIR: /etc
stdlib: GNU libstdc++ 20060524
libebt: 1.3.0
libwrapiter: 1.0.0
sandbox: enabled
Repository virtuals:
Configuration information:
format: virtuals
Repository installed_virtuals:
Configuration information:
format: installed_virtuals
Repository gentoo:
Configuration information:
buildroot: /var/tmp/paludis
cache: /usr/portage/metadata/cache
distdir: /usr/portage/distfiles
eclassdirs: /usr/portage/eclass
format: ebuild
location: /usr/portage
names_cache: /usr/portage/.cache/names
newsdir: /usr/portage/metadata/news
pkgdir: /var/empty
profiles: /usr/portage/profiles/default-linux/x86/2006.1/desktop
root: /
securitydir: /usr/portage/metadata/glsa
setsdir: /usr/portage/sets
sync: rsync://rsync.gentoo.org/gentoo-portage
sync_options:
write_cache: /var/cache/paludis/metadata
Package information:
app-admin/eselect-compiler: (none)
dev-java/java-config: 1.3.7, 2.0.31-r3
dev-lang/python: 2.4.4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: (none)
dev-util/confcache: (none)
sys-apps/sandbox: 1.2.18.1
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.17
sys-devel/gcc-config: 1.3.14
sys-devel/libtool: 1.5.22
virtual/os-headers: 2.6.20
Variable information:
ACCEPT_KEYWORDS:
AUTOCLEAN:
CBUILD: i686-pc-linux-gnu
CFLAGS: -march=pentium3 -Os -pipe
CHOST: i686-pc-linux-gnu
CONFIG_PROTECT: /usr/share/X11/xkb /usr/kde/3.5/share/config /usr/kde/3.5/env /usr/kde/3.5/shutdown /usr/share/config
CONFIG_PROTECT_MASK: /etc/java-config/vms/ /etc/env.d/java/ /etc/gconf /etc/terminfo /etc/texmf/web2c /etc/revdep-rebuild /etc/splash
CTARGET:
CXXFLAGS: -march=pentium3 -Os -pipe
DISTDIR: /usr/portage/distfiles
FEATURES:
GENTOO_MIRRORS:
INSTALL_MASK:
LANG:
LC_ALL:
LDFLAGS:
LINGUAS:
MAKEOPTS: -j2
PKGDIR:
PORTAGE_RSYNC_EXTRA_OPTS:
PORTAGE_RSYNC_OPTS:
PORTAGE_TMPDIR: /var/tmp/paludis
PORTDIR: /usr/portage
PORTDIR_OVERLAY:
SYNC:
USE:
Repository installed:
Configuration information:
buildroot: /var/tmp/paludis
format: vdb
location: /var/db/pkg
names_cache: /var/db/pkg/.cache/names
provides_cache: /var/db/pkg/.cache/provides
root: /
world: /var/db/pkg/world
Repository local:
Configuration information:
buildroot: /var/tmp/paludis
cache: /var/empty
distdir: /usr/portage/distfiles
eclassdirs: /usr/portage/eclass
format: ebuild
location: /usr/local/portage
names_cache: /usr/local/portage/.cache/names
newsdir: /usr/local/portage/metadata/news
pkgdir: /var/empty
profiles: /usr/portage/profiles/default-linux/x86/2006.1/desktop
root: /
securitydir: /usr/local/portage/metadata/glsa
setsdir: /usr/local/portage/sets
sync: file:///usr/local/portage
sync_options:
write_cache: /var/cache/paludis/metadata
Repository paludis-extras:
Configuration information:
buildroot: /var/tmp/paludis
cache: /var/empty
distdir: /usr/portage/distfiles
eclassdirs: /usr/portage/eclass /usr/local/paludis-extras/eclass
format: ebuild
location: /usr/local/paludis-extras
names_cache: /usr/local/paludis-extras/.cache/names
newsdir: /usr/local/paludis-extras/metadata/news
pkgdir: /var/empty
profiles: /usr/portage/profiles/default-linux/x86/2006.1/desktop
root: /
securitydir: /usr/local/paludis-extras/metadata/glsa
setsdir: /usr/local/paludis-extras/sets
sync: rsync://drzile.dyndns.org/paludis-extras
sync_options:
write_cache: /var/cache/paludis/metadata
(In reply to comment #12) > With paludis my /bin/gzip binary seems to consist of some lines of bash script > with the real binary appended afterwards. Would be helpful to know what those lines are. I can at least confirm that the resulting binary from downgrading to 1.3.10 using paludis works just fine (as it did before, when it was installed using portage). Please don't tell us that using another package manager breaks gzip. If you set FEATURES=test and install it using Portage, it breaks in exactly the same way, right? The lines in the gzip binary are:
#!/bin/sh
PATH=${GZIP_BINDIR-'/usr/bin'}:$PATH
exec gzip -cd "$@"
Could not reproduce this with "FEATURES=test emerge -va app-arch/gzip"
But I too had problems to reproduce this using paludis. The first time simply rebuilding gzip with paludis everything worked fine only after downgrading gzip and upgrading again my gzip binary was broken again. So maybe it doesn't happen every time?
(In reply to comment #14) > I can at least confirm that the resulting binary from downgrading to 1.3.10 > using paludis works just fine (as it did before, when it was installed using > portage). Please don't tell us that using another package manager breaks > gzip. OK forget about this. I was also able to install 1.3.11 just fine using portage. After that, I can also re-install gzip with paludis just fine, with and without SKIP_FUNCTIONS=test. (In reply to comment #15) > If you set FEATURES=test and install it using Portage, it breaks in exactly the > same way, right? > No, it doesn't. It really seems to be a paludis issue. It happens when: 1) gzip 1.3.10 is installed 2) paludis is used for upgrading, no matter if SKIP_FUNCTIONS=test is set or not. It does not happen when 1) updating with emerge 2) re-installing 1.3.11 (with emerge or paludis). Just ran into this bug myself. Downgrading to 1.3.10 fixed it. Ok, I found it. Paludis has a weird bug involving overwriting stale symlinks with objects. 0.18.0, which will be out in a few hours, fixes this. 0.18.0 is in the tree; closing. *** Bug 165848 has been marked as a duplicate of this bug. *** |
