[pacman-dev] pacman3 logging issues
Just thought I'd send this email before I forgot about it. Here is a log from my pacman3 -Syu yesterday: http://pastebin.archlinux.org/548 The aspell upgrade alone was logged 9 times...so I'm thinking there is a bit of an issue here with the way log entries are being written to the file. I haven't looked at the logging code enough yet to know what is going on, but I thought I'd at least present a concrete example to the list. Happy holidays to everyone! -Dan
Hmh, i've read some trough the code right away. As it seems, the log function is just called once per package upgraded, so my intention is rather to look at the list and deplist building and execution of the update. I'm not very happy reading trough the code, i don't really get warm with it as fast as i want, maybe caused by the fact i havn't been developing in c for the past 2 years, as well as i developed in c++, not pure c. Though, i'm trying to understand the architecture behind dep building. Seems not "my way" as often in os applications, but it seems to work. What i'm wondering is why sync is that often needed (see the log), especially in a linear operation without threads. Last but not least, i've taken a look into package signing, missing some documentation on this tough (gnupg made easy). Merry christmas, // STi On Sunday 24 December 2006 23:32, Dan McGee wrote:
Just thought I'd send this email before I forgot about it. Here is a log from my pacman3 -Syu yesterday:
http://pastebin.archlinux.org/548
The aspell upgrade alone was logged 9 times...so I'm thinking there is a bit of an issue here with the way log entries are being written to the file. I haven't looked at the logging code enough yet to know what is going on, but I thought I'd at least present a concrete example to the list.
Happy holidays to everyone!
-Dan
_______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://www.archlinux.org/mailman/listinfo/pacman-dev
On Sunday 24 December 2006 23:32, Dan McGee wrote:
The aspell upgrade alone was logged 9 times...so I'm thinking there is
Even worse... look at the times. it's the same 10-20 lines logged over and over. On 12/25/06, Georg Grabler <ggrabler@gmail.com> wrote:
What i'm wondering is why sync is that often needed (see the log), especially in a linear operation without threads.
That is not a threaded "sync" - that's part of pacman's operation. It's -Sy, actually.
On 12/28/06, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Sunday 24 December 2006 23:32, Dan McGee wrote:
The aspell upgrade alone was logged 9 times...so I'm thinking there is
Even worse... look at the times. it's the same 10-20 lines logged over and over.
Have you been able to duplicate this? I don't know if you can always make it happen, but I was thinking of doing some more experimentation later today. I also noticed another funny issue. Run a 'pacman -Ss pacman > anyfile', and notice how each word of the description ends up on its own line. pacman 2 didn't do this, kind of an interesting behavior. I can try and look into this too. -Dan
On 12/28/06, Dan McGee <dpmcgee@gmail.com> wrote:
I also noticed another funny issue. Run a 'pacman -Ss pacman > anyfile', and notice how each word of the description ends up on its own line. pacman 2 didn't do this, kind of an interesting behavior. I can try and look into this too.
Oh damn, didn't think about that one. That has to do with the way it determines the width for the description by getting the terminal width. (Which is 0 or null when not outputting to a terminal). So, I need to check if we're a tty in getcols (simple fix).
Bringing back up an old topic, but it happened again. Doesn't seem to happen when installing individual packages, but when doing a system upgrade you definitely get the multiple log repeats. We should try to figure this one out. http://pastebin.archlinux.org/824 -Dan
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Georg Grabler