gmane.linux.openwall.user

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-05-09T02:24:43

This is now fixed by excluding a couple of scripts (that required those
modules) from syslinux-perl.  We're not installing the syslinux-perl
package normally, which is why this went unnoticed until your report.

Thanks,

Alexander

new Owl-current snapshot

Solar Designer — 2012-05-09T00:37:03

Hi,

A new snapshot of Owl-current is available, including ISO images, OpenVZ
container templates, binary packages for i686 and x86_64, and indeed
full sources.  The new ISOs are linked right from the Owl homepage:

http://www.openwall.com/Owl/

Significant changes since the previous set of ISOs and templates
(October 26, 2011) include update of the Linux/OpenVZ kernel to one
based on RHEL 5.8's, GCC update to 4.6.3, "gcc -Wl,-z,relro -Wl,-z,now"
by default as a security hardening measure, John the Ripper 1.7.9+ with
enabled OpenMP parallelization, AVX, and XOP support, move to ISOLINUX
for the bootloader for the ISOs (lets us provide larger kernel images),
building of glibc's UTF-8 locales by default (despite of the size
increase), new versions of OpenSSL, lftp, strace, hdparm.  Of these, the
kernel and OpenSSL updates are security fixes (as it is usual for these
components).  The changes are documented in more detail here:

http://www.openwall.com/Owl/CHANGES-current.shtml

Alexander

Re: screen termcap warning

а х — 2012-04-09T10:50:09

Thank you!
Your patches resolved this issue.


2012/4/9 Mesut Can Gürle <mesutcang< at >gmail.com>

Re: screen termcap warning

Mesut Can Gürle — 2012-04-09T10:17:21

Hello,

I inspected the problem. The problem is about libtermcap's buffer is
limited to 1024. I updated the buffer to 2048 as already updated in screen.

Patches I prepare and binary packages can be accessible from
http://mesutcang.net23.net/owl/libtermcap/.

Re: screen termcap warning

Solar Designer — 2012-04-08T15:17:32

Hi,

On Thu, Apr 05, 2012 at 12:58:39PM +0400, а х wrote:

Thank you for the problem report.

I think figuring this out and fixing it is a good task for a new
contributor to our project.  Any takers?

I'll over-quote the original report below since I'm CC'ing some
prospective contributors who are on owl-dev, but somehow not on
owl-users.


Alexander

screen termcap warning

а х — 2012-04-05T08:58:39

Hi,

I have warning message, when running screen:
tgetent: warning: termcap entry too long

I have packages installed:
termcap-11.0.1-owl1
libtermcap-2.0.8-owl7
libtermcap-devel-2.0.8-owl7
screen-4.0.3-owl1

Under screen:
bash-3.1# echo $TERMCAP
SC|screen|VT 100/ANSI X3.64 virtual terminal:\
:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:bs:bt=\E[Z:\
:cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:ct=\E[3g:\
:do=^J:nd=\E[C:pt:rc=\E8:rs=\Ec:sc=\E7:st=\EH:up=\EM:\
:le=^H:bl=^G:cr=^M:it#8:ho=\E[H:nw=\EE:ta=^I:is=\E)0:\
:li#52:co#197:am:xn:xv:LP:sr=\EM:al=\E[L:AL=\E[%dL:\
:cs=\E[%i%d;%dr:dl=\E[M:DL=\E[%dM:dc=\E[P:DC=\E[%dP:\
:im=\E[4h:ei=\E[4l:mi:IC=\E[%d< at >:ks=\E[?1h\E=:\
:ke=\E[?1l\E>:vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l:\
:ti=\E[?1049h:te=\E[?1049l:us=\E[4m:ue=\E[24m:so=\E[3m:\
:se=\E[23m:mb=\E[5m:md=\E[1m:mr=\E[7m:me=\E[m:ms:\
:Co#8:pa#64:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:AX:\
:vb=\Eg:G0:as=\E(0:ae=\E(B:\
:ac=\140\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:\
:po=\E[5i:pf=\E[4i:k0=\E[10~:k1=\EOP:

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-04-04T22:30:26

No.  The problem turned out to be that the secondary mirror feed from
which the kernel.org mirror is updated was not up to date.  I've just
corrected that.  Thus, the kernel.org mirror should have the new stuff
in a few more hours from now.  Meanwhile, you may download the newer
revision e.g. from ftp://ftp.fr.openwall.com/pub/Owl/current/ which was
already up to date (it updates from our primary feed).

Sorry about that, and thank you for helping identify this!

Alexander

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Zenny — 2012-04-04T17:51:28

v 1.140, but it was just pulled two days back. Has it changed in the
last 48 hours?



On 4/4/12, gremlin< at >gremlin.ru <gremlin< at >gremlin.ru> wrote:
Thanks, gremlin.

rpm --Fvh --aid ~build/RPMS/*.rpm and then make installworld
afterwards got smooth upgrade.

Thanks again to all (Gremlin, Solar, Chris Bopp, Ingmar and the
wonderful Owl community. ;-)

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-04-04T17:19:22

...

This is a known bug, which has already been fixed.  What revision of
installorder.conf are you using?  It should be 1.141 now.

Alexander

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Zenny — 2012-04-04T17:12:59

Thanks, I forced installed mpfr, libgomp and libmpc and then upgrade
again, to get the following:
....
no /usr/sbin/xinetd found; none killed.
   1:xinetd                 ########################################### [100%]
17:04:06: Installing openssl openssl-devel openssl-perl mtree openssh
openssh-clients openssh-server d:openssh-blacklist elinks nmap ncat
nping mutt openntpd readline readline-devel bc gnupg gdb lftp
(openssl-1.0.0d-owl2.x86_64.rpm openssl-devel-1.0.0d-owl2.x86_64.rpm
openssl-perl-1.0.0d-owl2.x86_64.rpm mtree-3.7.20050808-owl2.x86_64.rpm
openssh-3.6.1p2-owl27.x86_64.rpm
openssh-clients-3.6.1p2-owl27.x86_64.rpm
openssh-server-3.6.1p2-owl27.x86_64.rpm
openssh-blacklist-3.6.1p2-owl27.x86_64.rpm
elinks-0.11.7-owl1.x86_64.rpm nmap-5.51-owl1.x86_64.rpm
ncat-5.51-owl1.x86_64.rpm nping-5.51-owl1.x86_64.rpm
mutt-1.4.2.3-owl1.x86_64.rpm openntpd-3.7p1-owl5.x86_64.rpm
readline-5.1-owl1.x86_64.rpm readline-devel-5.1-owl1.x86_64.rpm
bc-1.06-owl8.x86_64.rpm gnupg-1.4.11-owl2.x86_64.rpm
gdb-6.3-owl4.x86_

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-04-04T14:25:08

Chris,

On Wed, Apr 04, 2012 at 02:35:57AM -1000, cpb< at >vps.log2.net wrote:

Sure.  I initially suspected the same thing as well.


That's no problem.  Your postings have been very helpful, such as to
encourage further knowledge exchange between the users of Owl in here.

Thank you!

Alexander

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

2012-04-04T12:35:57

Sorry, my mistake, I meant to say, "to another in-place with buildworld".
I concluded that Zenny had used buildworld to get into his situation, though
I don't think that anymore (a separate mistake).

Thanks for asking why I made my assertion instead of just saying it was wrong.
That's what I like about this list. The reason I assert that buildworld
(followed by installworld, of course) will not always take you from -stable to
-current is that I recently tried it (building mpfr, mpc, and friends first)
but ended up in a very strange place with rpm dependency errors similar to
Zenny's. That's why I have been so chatty on the list lately - "false authority
syndrome." :)

Chris Bopp
Honolulu, Hawaii

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-04-04T10:42:12

Why, as long as you're not trying to jump over an Owl release, this is
supposed to work.  For example, upgrades of Owl 3.0 to Owl-current, as
well as from Owl 3.0-stable to Owl-current, are supposed to work (with
"make installworld").  Moreover, even upgrades from older releases of
Owl should work as long as you upgrade to each intermediate release
first (e.g., 2.0 to 3.0 then to -current, not 2.0 to -current right away).

Of course, there may be issues with customized systems (including
systems that merely have additional RPMs installed, where an upgrade
might break those third-party RPMs' dependencies), but for clean
installs this should just work.

Alexander

Re: Upgrading to current gives dependency problem

2012-04-04T10:38:22

 > > # rpm -Fvh ~build/RPMS/*.rpm
 > > error: Failed dependencies

 > -Fvh only works in installed packages. Not on new dependancies.
 > RPM doesn't handle this case, that's where normally yum and
 > friends come to help.

--aidAdd suggested packages to the transaction set when needed.

Guess what I've quoted :-)

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-04-04T10:35:51

Thank you for confirming this.  I just took a closer look and it appears
that the problem with syslinux-perl is a bug in Owl-current.  We did not
run into it because the syslinux-perl subpackage is not included in our
installorder.conf.  So please just don't install this subpackage for
now.  If you use "make installworld" instead of the manual "rpm -Uvh
~build/RPMS/*.rpm", that should just work (not trying to install this
problematic subpackage).

Please let us know if you run into any other issues.

Thanks again,

Alexander

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

2012-04-04T09:26:52

You can't generally upgrade from one branch of Owl to another in-place with
installworld. You still have not said what you are upgrading *from*, which
makes a huge diffference. If it's Owl-stable, everything makes sense and
you have chosen a painful path. If it's some earlier Owl-current, then in-place
installworld *should* work, but it's not too surprising if it doesn't (see
Solar's suggestion about looking in the owl-dev mailing list around the time
of major changes.)

I have not tried to go from the -current ISOs up to Owl-current lately. The
ISOs are pretty old, by which I just mean a lot has happened on the -current
branch since then--and I think a lot more is about to happen! Look out for
glibc.next!

Chris Bopp
Honolulu, Hawaii

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

2012-04-04T09:14:09

Hello again Zenny,

Thanks for trying the suggestions; while it is true that rpm cannot figure
how to accomplish what you (or the installworld script) are asking for, there
is reason to be optimistic (I'm saying RPM-hell is never as bad as DLL-hell).

Let me suggest you take a step back and use rpm to analyze the problem. When
you get an error like this:


It is either because:
 1. You asked to upgrade (or remove) some perl modules WITHOUT also upgrading
    (removing) something which depends upon those modules ("syslinux").

    In this case RPM doesn't want to remove the perl modules because syslinux
    is "sitting" on them. You might be able to force it with --force, or you
    might be missing a syslinux....rpm file in your RPMS directory (so *.rpm
    did not include it).

OR

 2. You asked to upgrade (or install) some syslinux package WITHOUT also
    upgrading (installing) some perl modules which the new one needs.

    In this case RPM can't find a dependency, and so it doesn't want to install

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Igmar Palsenberg — 2012-04-04T09:06:46



-Fvh only works in installed packages. Not on new dependancies. RPM doesn't handle this case, that's where normally
yum and friends come to help.

Do an install of mpfr, libgomp. and mpc (rpm -ivh --force), and try the upgrade again.



Igmar

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Zenny — 2012-04-04T09:03:42

I got it from: http://mirrors.kernel.org/openwall/Owl/current/ using
the standard upgrade without any customization right now. I just
thought of upgrading first and then make customization.


As I stated earlier, the make installworld is done with Owl pre-built
RPMs, yet I was getting the problems as I reported.


I just followed http://openwall.info/wiki/Owl/upgrade without any
modifications so far.

Thanks!

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Solar Designer — 2012-04-03T21:56:53

You never mentioned where you got those RPMs.  Did you build them
yourself or did you download them?  Did you previously install
locally-built (by you) Owl RPMs on this system?


If you simply used "make installworld" using our pre-built RPMs, the
upgrade should have been smooth.

If you build your own RPMs and try to cross a major change in this way
(such as our update of OpenSSL or GCC), then, yes, you may get into
dependency hell that you'd need to resolve on your own.  Ways to resolve
it _might_ be found in owl-dev list postings from the right time period;
they generally involve multiple install/build/install steps.  If you're
not into developing Owl, then I suggest that you only upgrade using our
pre-built RPMs.


Alexander

Re: Upgrading to current gives dependency problem after kernel upgrade and boot

Zenny — 2012-04-03T21:41:01

Thanks Chris for an elaborative reply. Appreciate it. Same to Solar,

However, whenever I tried with

1. rpm -Uvh option, I get:
# rpm -Uvh ~build/RPMS/*.rpm
error: Failed dependencies:
perl(Crypt::PasswdMD5) is needed by syslinux-perl-4.04-owl2
perl(Digest::SHA1) is needed by syslinux-perl-4.04-owl2

2. And when I try to upgrade userland by the book (as stated in the
wiki, make installworld), I get:

Preparing...                ########################################### [100%]
   1:groff-doc              ########################################### [100%]
21:32:08: Skipping owl-cdrom
21:32:08: Removing temporary files
21:32:08: Failed to install: lftp
traceroute
make: *** [installworld] Error 1

3. When I try to manually upgrade lftp, I get:

# rpm -Uvh ~build/RPMS/lftp-4.1.1-owl1.x86_64.rpm
error: Failed dependencies:
libcrypto.so.10()(64bit) is needed by lftp-4.1.1-owl1
libssl.so.10()(64bit) is needed by lftp-4.1.1-owl1

It seems like a dependency hell. :-( Could not figure out how can I
upgrade smoot