Opened 4 years ago

Closed 3 years ago

#12400 closed bug (no change required)

pkgman update fails update to newer nightlies

Reported by: HAL Owned by: nobody
Priority: normal Milestone:
Component: - General Version:
Keywords: pkgman update fails Cc: HAL
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

For quite a while now I have been unable to get gcc2 hybrid updates with pkgman.

  1. Open terminal and type: pkgman update.
  2. Press enter.

Result Is:

~> pkgman update
Downloading repochecksum-1...done.
Validating checksum for Haiku...done.                                           
Downloading repocache-2...done.
Validating checksum for Haiku...done.                                           
Downloading repochecksum-1...done.
Validating checksum for HaikuPorts...done.                                      
Nothing to do.

I was trying to update from hrev49660 x86_gcc2 to hrev49662 x86_gcc2 I am able to update x86_64 nighlies with pkgman. If I want to update x86_gcc2 nightlies I have to download and install over the previous versions

Attachments (1)

syslog_copy (470.6 KB ) - added by HAL 4 years ago.

Download all attachments as: .zip

Change History (7)

by HAL, 4 years ago

Attachment: syslog_copy added

comment:1 by HAL, 4 years ago

I'm not certain if the syslog has relevant information.

comment:2 by diver, 4 years ago

Try pkgman full-sync.

comment:3 by HAL, 4 years ago

I over-wrote the repositories with:

pkgman add http://packages.haiku-os.org/haiku/master/$(getarch)/current
pkgman add http://packages.haiku-os.org/haikuports/master/repo/$(getarch)/current

then I just did the standard:

pkgman update

It woked this time. Maybe the repository file was corrupted or out of date on my system. I did try:

pkgman full-sync

before re adding the repositories. This did not work. I don't know if it was because of network/internet problems. After a reboot the network/internet was functioning properly when I overwrote the repositories.

comment:4 by vidrep, 3 years ago

Is this still an issue?

in reply to:  4 comment:5 by HAL, 3 years ago

Replying to vidrep:

Is this still an issue?

Sometimes it is. It has not happened the last few updates.

comment:6 by diver, 3 years ago

Resolution: no change required
Status: newclosed
Note: See TracTickets for help on using tickets.