ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: Sergey Kuznetsov <yozhik@atom.ru>
To: community@altlinux.ru
Subject: Re: [Comm] X-modeline
Date: Wed, 18 Dec 2002 18:45:33 +0300
Message-ID: <20021218184533.2f2ceac4.yozhik@atom.ru> (raw)
In-Reply-To: <20021218180254.1944cfa3.yozhik@atom.ru>

On Wed, 18 Dec 2002 18:02:54 +0300
Sergey Kuznetsov <yozhik@atom.ru> wrote:

> On Wed, 18 Dec 2002 16:50:25 +0200
> Michael Shigorin <mike@osdn.org.ua> wrote:
> 
> > On Wed, Dec 18, 2002 at 05:24:03PM +0300, Sergey Kuznetsov
> > wrote:
> > > > Это Вы от жизни отстали :-)  Текущий 0.32-alt1 много чему
> > > > научился.
> > > Заинтриговали. Чему, например?
> > 
> > trickster:~> rpm -q --lastchange videogen-0.32-alt1 
> > * Mon Dec 02 2002 Michael Shigorin <mike@altlinux.ru>
> > 0.32-alt1
> > 
> > - 0.32 (NVidia support)
> > - patch1 not applicable
> > - spec cleanup
> > 
> > Тж. CHANGES от 0.16 до 0.32:
> > 
> > --- 
> > The videogen change log:
> > 
> > 0.32    released: 26 Nov 2002
> > 
> >         - fixed a small bug which can cause a segfault
> > 
> > 0.31    released: 21 Nov 2002
> > 
> >         - major changes to the calculation algorithm which
> >         fixes
> >           some of the problems with the new nvidia support
> > 
> >         - some other minor changes
> > 
> > 0.30    released: 30 Oct 2002
> > 
> >         - major rewrite of the whole code, primarily a
> >           very different (and hopefully better) user
> >           interface
> > 
> >         - added nvidia driver compatibility support
> >         
> >         - updated documentation
> > 
> > 0.21    released: 6 Mar 2001
> > 
> >         - made some minor internal changes to the code
> > 
> >         - renamed command line options to be less cryptic
> > 
> >         - cleaned up and revised documentation and all other
> >         files
> > 
> >         - dropped GPLv2 file from the package, it's a waste
> >         of
> >           diskspace
> > 
> > 0.20    released: 19 Feb 2000
> > 
> >         - almost the entire code has been rewritten
> > 
> >         - new calculation algorhythm implemented
> > 
> >         - added a default value for the horizontal sync pulse
> > 
> >         - the manpage has been revised to reflect changes
> > 
> > ---
> > 
> > Т.е. два rewrite -- и мы уже умеем ~/.videogen и все блага
> > цивилизации. :)
> > 
> > Только вот строчку 1400x1050 @97 все равно пришлось еще долго
> > ровнять в xvidtune.  Надо посмотреть, что вышеупомянутый
> > CGI-скриптик насчитает (без правок)...
> 
> Пойду поставлю (хотя бы из любопытства).

Мда... Индейское жилище, однако.

[root@localhost root]# apt-get install videogen
Reading Package Lists... Done
Collecting File Provides... Done
Building Dependency Tree... Done
The following packages will be upgraded
  videogen
1 packages upgraded, 0 newly installed, 0 removed and 792 not
upgraded. Need to get 21,0kB of archives. After unpacking 10,4kB
will be used. Get:1 ftp://ftp.altlinux.ru i586/classic videogen
2:0.32-alt1 [21,0kB] Fetched 21,0kB in 5s (3914B/s)
rpmdb: Page 5184 encountered a second time on free list
error: db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database
verification failed Executing RPM (/bin/rpm -Uvh --fancypercent
--oldpackage)... Preparing...                
#################################################################
#[100%]
1: videogen                 
#################################################################
#[100%]
rpmdb: PANIC: Invalid argument
error: db4 error(-30981) from dbcursor->c_put: DB_RUNRECOVERY:
Fatal error, run database recovery error: db4 error(-30981) from
db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from dbcursor->c_close: DB_RUNRECOVERY:
Fatal error, run database recovery error: db4 error(-30981) from
db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal
error, run database recovery error: error(-30981) storing record
videogen into Name error: db4 error(-30981) from db->sync:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run
database recovery error: error(-30981) storing record videogen
into Basenames error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run
database recovery error: error(-30981) storing record
videogen.1x.gz into Basenames error: db4 error(-30981) from
db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal
error, run database recovery error: error(-30981) storing record
videogen-0.32 into Basenames error: db4 error(-30981) from
db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal
error, run database recovery error: error(-30981) storing record
BUGS into Basenames error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run
database recovery error: error(-30981) storing record CHANGES
into Basenames error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run
database recovery error: error(-30981) storing record README into
Basenames error: db4 error(-30981) from db->get: DB_RUNRECOVERY:
Fatal error, run database recovery error: db4 error(-30981) from
db->put: DB_RUNRECOVERY: Fatal error, run database recovery
error: error(-30981) storing record THANKS into Basenames error:
db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->put:
DB_RUNRECOVERY: Fatal error, run database recovery error:
error(-30981) storing record videogen.sample into Basenames
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal
error, run database recovery error: cannot open Group index using
db3 -  (-30981) error: db4 error(-30981) from db3c_open:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->put:
DB_RUNRECOVERY: Fatal error, run database recovery error:
error(-30981) storing record libc.so.6 into Requirename error:
db4 error(-30981) from db->get: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->put:
DB_RUNRECOVERY: Fatal error, run database recovery error:
error(-30981) storing record libc.so.6(GLIBC_2.0) into
Requirename error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->put: DB_RUNRECOVERY: Fatal error, run
database recovery error: error(-30981) storing record
libc.so.6(GLIBC_2.1) into Requirename error: db4 error(-30981)
from db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal
error, run database recovery error: error(-30981) storing record
libm.so.6 into Requirename error: db4 error(-30981) from
db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->put: DB_RUNRECOVERY: Fatal
error, run database recovery error: error(-30981) storing record
videogen into Providename error: db4 error(-30981) from db->sync:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->close:
DB_RUNRECOVERY: Fatal error, run database recovery error: cannot
open Dirnames index using db3 -  (-30981) error: db4
error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->close:
DB_RUNRECOVERY: Fatal error, run database recovery error: cannot
open Requireversion index using db3 -  (-30981) error: db4
error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->close:
DB_RUNRECOVERY: Fatal error, run database recovery error: cannot
open Provideversion index using db3 -  (-30981) error: db4
error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->close:
DB_RUNRECOVERY: Fatal error, run database recovery error: cannot
open Installtid index using db3 -  (-30981) error: db4
error(-30981) from db->open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->close:
DB_RUNRECOVERY: Fatal error, run database recovery error: cannot
open Sigmd5 index using db3 -  (-30981) error: db4 error(-30981)
from db->open: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal
error, run database recovery error: cannot open Sha1header index
using db3 -  (-30981) error: db4 error(-30981) from db->open:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->close: DB_RUNRECOVERY: Fatal error, run
database recovery error: cannot open Filemd5s index using db3 - 
(-30981) error: db4 error(-30981) from db3c_open: DB_RUNRECOVERY:
Fatal error, run database recovery error: db4 error(-30981) from
db->get: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->open: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Triggername index using db3 -  (-30981) error:
db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->sync:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->sync:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db->sync: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->sync:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery error: db4
error(-30981) from db3c_open: DB_RUNRECOVERY: Fatal error, run
database recovery error: db4 error(-30981) from db->get:
DB_RUNRECOVERY: Fatal error, run database recovery***
PSM_RDB_LOAD: header #572 not found error: db4 error(-30981) from
db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->sync: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db->close: DB_RUNRECOVERY: Fatal
error, run database recovery error: db4 error(-30981) from
dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: db4 error(-30981) from db_env_create: DB_RUNRECOVERY:
Fatal error, run database recovery error: db4 error(-30981) from
dbenv->remove: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: Page 5184 encountered a second time on free list error:
db4 error(-30979) from db->verify: DB_VERIFY_BAD: Database
verification failed E: Sub-process /bin/rpm returned an error
code (1)

С уважением,
Сергей


  reply	other threads:[~2002-12-18 15:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-18  9:31 Maxim Yarushin
2002-12-18  9:38 ` [Comm] X-modeline Michael Shigorin
2002-12-18 10:22   ` Alexey I. Froloff
2002-12-18 10:41     ` Michael Shigorin
2002-12-18 11:27       ` Maxim Yarushin
2002-12-18 11:32         ` Michael Shigorin
2002-12-18 10:35   ` Vitaly Ostanin
2002-12-18 10:35   ` Maxim Yarushin
2002-12-18 13:31   ` [Comm] X-modeline Sergey Kuznetsov
2002-12-18 14:09     ` [Comm] X-modeline Michael Shigorin
2002-12-18 14:24       ` Sergey Kuznetsov
2002-12-18 14:50         ` Michael Shigorin
2002-12-18 15:02           ` [Comm] X-modeline Sergey Kuznetsov
2002-12-18 15:45             ` Sergey Kuznetsov [this message]
2002-12-18 17:28               ` [Comm] X-modeline Michael Shigorin
2002-12-18 18:20                 ` Максим Ярушин
2002-12-18 20:28               ` [Comm] X-modeline Vitaly Lipatov
2002-12-19 14:12                 ` Sergey Kuznetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021218184533.2f2ceac4.yozhik@atom.ru \
    --to=yozhik@atom.ru \
    --cc=community@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Community general discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
		mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
	public-inbox-index community

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.community


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git