#archlinux32 | Logs for 2024-11-27
Back
[00:44:02] -!- mvchtz has quit [Ping timeout: 248 seconds]
[00:46:15] -!- mvchtz has joined #archlinux32
[02:02:28] -!- mvchtz has quit [Ping timeout: 245 seconds]
[02:04:57] -!- mvchtz has joined #archlinux32
[07:19:54] -!- srvntx has quit [Quit: poof!]
[08:19:31] -!- srvntx has joined #archlinux32
[10:02:19] -!- lithium_pt has quit [Ping timeout: 260 seconds]
[10:13:30] -!- lithiumpt has joined #archlinux32
[10:18:33] -!- lithiumpt has quit [Ping timeout: 252 seconds]
[10:33:32] -!- lithiumpt has joined #archlinux32
[11:02:20] -!- gehidore has quit [*.net *.split]
[11:02:20] -!- dmc has quit [*.net *.split]
[11:04:45] -!- gehidore has joined #archlinux32
[11:04:45] -!- dmc has joined #archlinux32
[11:37:09] -!- mavchatz has joined #archlinux32
[11:37:12] -!- mvchtz has quit [Ping timeout: 252 seconds]
[11:48:02] mavchatz is now known as mvchtz
[12:01:27] -!- mvchtz has quit [Quit: WeeChat 4.1.1]
[12:31:49] -!- drathir_tor has joined #archlinux32
[12:42:53] -!- oaken-source has quit [Ping timeout: 265 seconds]
[14:14:30] -!- oaken-source has joined #archlinux32
[14:33:31] -!- drathir_tor has quit [Ping timeout: 260 seconds]
[14:41:12] -!- abaumann has joined #archlinux32
[14:41:42] <abaumann> sorry, I have to copy mysql databases from the buildmaster to archlinux32.org and take everything down.
[14:41:54] <abaumann> replication got completely out of sync
[14:46:36] -!- drathir_tor has joined #archlinux32
[14:51:04] -!- oaken-source has quit [Ping timeout: 252 seconds]
[15:47:21] -!- mvchtz has joined #archlinux32
[16:05:47] <bill-auger> should i halt or revert package imports
[16:06:34] <bill-auger> abaumann: ^ you mean the repos are not sane?
[16:08:08] <abaumann> aeh. just the buildmaster mysql is down
[16:08:19] <abaumann> till I have manually synched master and slave
[16:08:41] <abaumann> the repos are sane
[16:32:48] -!- oaken-source has joined #archlinux32
[16:52:49] <buildmaster> Hi abaumann!
[16:52:49] <buildmaster> !rq abaumann
[16:52:50] <phrik> buildmaster: <abaumann> The next step will be to distribute code to neighbour servers or use the Amazon cluster in the build script to run tests..
[16:52:56] <abaumann> ah, it failed. started things again, though not synced.
[16:53:02] -!- abaumann has quit [Quit: leaving]
[18:06:36] -!- oaken-source has quit [Ping timeout: 252 seconds]
[18:56:14] -!- abaumann has joined #archlinux32
[18:56:26] <abaumann> take too..
[18:56:31] <abaumann> *two
[19:50:30] <buildmaster> Hi abaumann!
[19:50:30] <buildmaster> !rq abaumann
[19:50:30] <phrik> buildmaster: <abaumann> canary no. 2 is back on testing. :-)
[19:50:50] <abaumann> ok, synched again.
[19:50:52] -!- abaumann has quit [Quit: leaving]
[21:56:41] -!- morriset has joined #archlinux32
[21:58:18] <morriset> Hi! Recently (Couple of weeks ago) I've installed Arch32. Today I tried to update the system bun unfortunately I get the error "invalid or corrupted package (PGP signature)"
[21:58:52] <morriset> I've tried the following commands with no success:
[21:58:55] <morriset> pacman -S archlinux-keyring
[21:58:57] <morriset> pacman -S archlinux32-keyring
[21:59:43] <morriset> Also tried rm -fr /etc/pacman.d/gnupg && pacman-key --init && pacman-key --populate
[22:00:09] <morriset> But still getting the PGP signature error. Any other suggestion?
[22:26:51] <bill-auger> morriset: someone reported the same problem yesterday (on IRC) - that apparently was not user-error; so it should probably have a bug report, would you mind opening a bug report
[22:28:26] <bill-auger> blowing away yoyr keyring like that, i think that should have worked - but that is not the best way to fix signature errors
[23:17:19] <morriset> bill-auger: I know it is not the best way, is more like last resource. :)
[23:17:38] <morriset> this is happening only in arch32, not 64.
[23:35:50] <bill-auger> that was not a last resort though - well before the lst resort comes checking the bug tracker for existing issues, and reporting the problem if there is not bug report
[23:37:11] <bill-auger> i know how to fix your problem - we worked through it yesterday - but i do not want to walk two people through the exact same procedure two days in a row - if you open a bug report, i will post the solution to it
[23:38:37] <bill-auger> FWIW, there is an open bug report about the keyring now, but it is a different problem - i believe that one is resolved now