Checksum error when updating tazpkg (878

SliTaz Forum » English Support » Live and installation

Checksum error when updating tazpkg (878 > 881)

(7 posts) (4 voices)

Started 8 years ago by Ceel
Latest reply from Aleksej
This topic is not a support question

Tags:

No tags yet.

Ceel

offline

Administrator

Hi all,

Seems there is a problem with the checksum of the last tazpkg package (881)

tazpkg-881.tazpkg    100% |*******************************|   129k  0:00:00 ETA
Checksum error for "tazpkg-881.tazpkg"

Recharging repository "Main"
================================================================================
Checking...                                                           [ Done ]
Database timestamp: 12/04/15 03:36
================================================================================
Repository "Main" is up to date.

tazpkg-881.tazpkg    100% |*******************************|   129k  0:00:00 ETA
Checksum error for "tazpkg-881.tazpkg"
Please wait until the mirror synchronization is complete and try again.

I tried 2 hours later and had the same error

Posted 8 years ago #

Aleksej

offline
Coder-hobbyist

Hi Ceel,

We need to rework our mirror updating system.
The problem comes from that facts:

1. New packages database created using current packages in the cook.slitaz.org (see pkgdb.log).
2. At this point any packages can be updated or just re-cooked, and their md5sum will changed.
3. Packages database (now outdated) and new packages transferred from cook.slitaz.org to mirror1.slitaz.org.

We need to disable cooker for a period of time just after the database is created up to all new packages are transferred to mirror1 to have exact database / packages snapshot.

I yet don't know how to do it. I hope Pascal will help with the files transfer.

Posted 8 years ago #
Ceel

offline
Administrator

Hi Aleksej,

OK, thanks. I thought it was a problem with this package because tazpkg didn't meet any problem with others (21) during the update.

Posted 8 years ago #
Aleksej

offline
Coder-hobbyist

Sorry, I can only guess and may be completely wrong.

I only can see that package database created on cook.slitaz.org near the midnight on server time.
Next, pkgs.slitaz.org is hosted on the same server as mirror1.slitaz.org, and you can see current mirror date / time at the bottom -- it is the time when package database was created. When I not sleep all the night until morning I can see that date / time is changed early morning, about 5-6 hours on my clocks. So I guessing this is the time when packages database both with packages are transferred from cook to mirror1.

I want to say I encounter problems yesterday night when I updated tazpkg from 881 to 882. Cook just not build it automatically, nor updated receipt. I don't know what it was, but hope over time all get better.

Posted 8 years ago #
llev

offline
Member

Hi,

Aleksej, I think you're completely right :) This morning tazpkg updated flawlessly.

Posted 8 years ago #
Bellard

offline
Key Master

@Aleksej: My fault, sorry.

1-

The bug: http://hg.slitaz.org/tazpkg/rev/a3c27a443a4d (879)
The fix: http://hg.slitaz.org/tazpkg/rev/f9b5a4545fff (883)

The idea: for example, you can find the following line in packages.equiv

dropbear=pam:dropbear-pam

It means: if you want to install dropbear *and* pam is already installed, then substitute dropbear-pam

2- In my crontab on tank I have:

30 4 * * * /home/bellard/bin/sync-tank

In sync-tank: if the most recent file in /home/slitaz/<each version>/chroot/home/slitaz/packages
is not a .tazpkg (i.e. is the cook pkgdb result) then do 'tazdev -p bellard <current-version>'

In each chroot crontab, something like:

0 2 * * * ls -t /home/slitaz/packages/ | sed q | grep -q tazpkg$ && cook pkgdb --flavors

Posted 8 years ago #
Aleksej

offline
Coder-hobbyist

Hi Pascal,

I have much more fails, no need to sorry.

I started to write tests for tazpkg: http://hg.slitaz.org/tazpkg/rev/70ac720dba11
Test #5 tries to install "pam", then "dropbear" as you wrote above. And TazPkg with your changes passed test.

In future plans for tests: make few packages (using tazpkg) with the same name but with different version. Emulate mirror using localhost /var/www/... Put there first package, install, put there second package, recharge, test update, redo, block package, test again...

Thank you for explanations. I will think that can be done.
First I want to speed-up 'cook pkgdb' as much as possible distributing a single large load onto each package cooking. But I'll have 2 days of work ahead without much free time.

Posted 8 years ago #

RSS feed for this topic

Reply

You must log in to post.