[pacman-dev] RC 2007.02.16
Latest and greatest. Not all that many changes here.. -Si works with the repo/package syntax, spacing on the "saving as .pacsave" output is fixed, etc Mostly minor. Test it out: http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.16-1-i686.pkg.tar.gz There is only one pending bug here, it's listed in the bugcatcher here: http://bugs.archlinux.org/task/6316 If anyone can reproduce that, let me know. I'm still trying to track that one down. Thanks guys!
2007/2/16, Aaron Griffin <aaronmgriffin@gmail.com>:
Latest and greatest. Not all that many changes here.. -Si works with the repo/package syntax, spacing on the "saving as .pacsave" output is fixed, etc
Mostly minor.
Test it out: http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.16-1-i686.pkg.tar.gz
There is only one pending bug here, it's listed in the bugcatcher here: http://bugs.archlinux.org/task/6316 hi If anyone can reproduce that, let me know. I'm still trying to track that one down.
Thanks guys!
I built a package containing a provides tag, but it seems that pacman don't write this information in the db, can anyone confirm that ? -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User
2007/2/16, Alessio 'mOLOk' Bolognino <themolok.ml@gmail.com>:
2007/2/16, Aaron Griffin <aaronmgriffin@gmail.com>:
Latest and greatest. Not all that many changes here.. -Si works with the repo/package syntax, spacing on the "saving as .pacsave" output is fixed, etc
Mostly minor.
Test it out: http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.16-1-i686.pkg.tar.gz
There is only one pending bug here, it's listed in the bugcatcher here: http://bugs.archlinux.org/task/6316 hi If anyone can reproduce that, let me know. I'm still trying to track that one down.
Thanks guys!
I built a package containing a provides tag, but it seems that pacman don't write this information in the db, can anyone confirm that ?
You mean that makepkg3 doesn't write provides info into .PKGINFO or gensync3 doesn't renerate correct database? -- Roman Kyrylych (Роман Кирилич)
On 2/16/07, Alessio 'mOLOk' Bolognino <themolok.ml@gmail.com> wrote:
I built a package containing a provides tag, but it seems that pacman don't write this information in the db, can anyone confirm that ?
Can you provide the PKGBUILD and the package (and the repo db) for me to inspect?
2007/2/16, Aaron Griffin <aaronmgriffin@gmail.com>:
On 2/16/07, Alessio 'mOLOk' Bolognino <themolok.ml@gmail.com> wrote:
I built a package containing a provides tag, but it seems that pacman don't write this information in the db, can anyone confirm that ?
Can you provide the PKGBUILD and the package (and the repo db) for me to inspect?
Ok, this is strange, I can't reproduce it anymore, I suspect I was installing (I tried more than once) the wrong package. I don't think you can fix my foolishness :) -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User
On 2/16/07, Alessio 'mOLOk' Bolognino <themolok.ml@gmail.com> wrote:
Ok, this is strange, I can't reproduce it anymore, I suspect I was installing (I tried more than once) the wrong package. I don't think you can fix my foolishness :)
Heh, no worries. I've had a few of these "omg THIS is broken... no wait, it's me being dumb" recently. On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I'm at work on a Windy machine. Can other people verify this is not an isolated issue? I suspect it's part if the fill_progress transition... /me shrugs
On 2/16/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I seem to have come across bigger issues...my ILoveCandy progress bar seems to have gone away, due to pacman3.conf being overwritten, even though it is specified as a backup file in my PKGBUILD. I don't know if anyone else has noticed, but I haven't seen any "saving this file as .pacnew" notices come up in quite a while. -Dan
2007/2/16, Dan McGee <dpmcgee@gmail.com>:
On 2/16/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I seem to have come across bigger issues...my ILoveCandy progress bar seems to have gone away, due to pacman3.conf being overwritten, even though it is specified as a backup file in my PKGBUILD. I don't know if anyone else has noticed, but I haven't seen any "saving this file as .pacnew" notices come up in quite a while.
I haven't seen them too. My pacman3.conf was not overwritten when doing pacman-rc upgrade today. I think this means that PKGBUILD used for building the latest RC contained backup=() and default pacman3.conf was not modified since last RC, so pacman3 didn't create .pacnew nor overwrite it (BTW, I have all NoUpgrade lines commented). -- Roman Kyrylych (Роман Кирилич)
On Fri, 16 Feb 2007 13:55:02 -0500 "Dan McGee" <dpmcgee@gmail.com> wrote:
On 2/16/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I seem to have come across bigger issues...my ILoveCandy progress bar seems to have gone away, due to pacman3.conf being overwritten, even though it is specified as a backup file in my PKGBUILD. I don't know if anyone else has noticed, but I haven't seen any "saving this file as .pacnew" notices come up in quite a while.
-Dan
I'm with you. I believe my pacman3.conf was overwritten as well. I'm not sure if it was this update or a different one though... I couldn't recreate it by installing 2007.02.16 again or by downgrading to 2007.02.13 and then up again to 2007.02.16. Sorry. Jason
2007/2/16, Jason Chu <jason@archlinux.org>:
On Fri, 16 Feb 2007 13:55:02 -0500 "Dan McGee" <dpmcgee@gmail.com> wrote:
On 2/16/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I seem to have come across bigger issues...my ILoveCandy progress bar seems to have gone away, due to pacman3.conf being overwritten, even though it is specified as a backup file in my PKGBUILD. I don't know if anyone else has noticed, but I haven't seen any "saving this file as .pacnew" notices come up in quite a while.
-Dan
I'm with you. I believe my pacman3.conf was overwritten as well. I'm not sure if it was this update or a different one though...
I've just installed one of my updated packages with pacman3 -U and it has created .pacnew and displayed a message. Everything as it should be. Dunno why your pacman3.conf was overwritten. :-/ -- Roman Kyrylych (Роман Кирилич)
On 2/16/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
2007/2/16, Jason Chu <jason@archlinux.org>:
On Fri, 16 Feb 2007 13:55:02 -0500 "Dan McGee" <dpmcgee@gmail.com> wrote:
On 2/16/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I seem to have come across bigger issues...my ILoveCandy progress bar seems to have gone away, due to pacman3.conf being overwritten, even though it is specified as a backup file in my PKGBUILD. I don't know if anyone else has noticed, but I haven't seen any "saving this file as .pacnew" notices come up in quite a while.
-Dan
I'm with you. I believe my pacman3.conf was overwritten as well. I'm not sure if it was this update or a different one though...
I've just installed one of my updated packages with pacman3 -U and it has created .pacnew and displayed a message. Everything as it should be. Dunno why your pacman3.conf was overwritten. :-/
I think lines 632-696 could use a careful look over in lib/libalpm/add.c. Aaron, your change in revision 1.98 to line 656 ( } else if(md5_orig || sha1_pkg) { ) seems a bit contradictory- shouldn't they either both be orig, or both be pkg? I'll try to take a look at all of this sometime and sort it out. -Dan
On 2/16/07, Dan McGee <dpmcgee@gmail.com> wrote:
I think lines 632-696 could use a careful look over in lib/libalpm/add.c. Aaron, your change in revision 1.98 to line 656 ( } else if(md5_orig || sha1_pkg) { ) seems a bit contradictory- shouldn't they either both be orig, or both be pkg?
You're probably right, it may have been a "lets see if this works, can't test sha1 right now, so I'll only change md5"... I'll peek at it.
On 2/16/07, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On 2/16/07, Dan McGee <dpmcgee@gmail.com> wrote:
I think lines 632-696 could use a careful look over in lib/libalpm/add.c. Aaron, your change in revision 1.98 to line 656 ( } else if(md5_orig || sha1_pkg) { ) seems a bit contradictory- shouldn't they either both be orig, or both be pkg?
You're probably right, it may have been a "lets see if this works, can't test sha1 right now, so I'll only change md5"... I'll peek at it.
I'll throw some of my test results out here for this whole possible bug. I manually edited one of the backup md5sums in the pacman DB and updated a package, and was able to get a pacnew notice. You only get this notice if the file has changed between package versions, so I simulated this manually by modifying the md5sum. This doesn't get me any closer to determining why my pacman3.conf was overwritten, however. I have a suspicion it might have to do with uninstalling a package completely and then reinstalling, but I'm not sure. -Dan
2007/2/16, Aaron Griffin <aaronmgriffin@gmail.com>:
On 2/16/07, Alessio 'mOLOk' Bolognino <themolok.ml@gmail.com> wrote:
Ok, this is strange, I can't reproduce it anymore, I suspect I was installing (I tried more than once) the wrong package. I don't think you can fix my foolishness :)
Heh, no worries. I've had a few of these "omg THIS is broken... no wait, it's me being dumb" recently.
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
.... yes, this is the only issue I've found so far. :P
I'm at work on a Windy machine. Can other people verify this is not an isolated issue? I suspect it's part if the fill_progress transition... /me shrugs
I could verify but I don't understand what Travis means with "ILoveCandy progress bar doesn't "chomp" anymore" :-/ -- Roman Kyrylych (Роман Кирилич)
On 2/16/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I could verify but I don't understand what Travis means with "ILoveCandy progress bar doesn't "chomp" anymore" :-/
If you set ILoveCandy in the pacman options (no arguments, just ILoveCandy by itself), pacman uses a fancy little "pacman" progress bar. It is supposed to alternate from 'C' to 'c' to "chomp" like pacman does.
2007/2/16, Aaron Griffin <aaronmgriffin@gmail.com>:
On 2/16/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I could verify but I don't understand what Travis means with "ILoveCandy progress bar doesn't "chomp" anymore" :-/
If you set ILoveCandy in the pacman options (no arguments, just ILoveCandy by itself), pacman uses a fancy little "pacman" progress bar. It is supposed to alternate from 'C' to 'c' to "chomp" like pacman does.
Thanks, I remember talks about ILoveCandy but didn't know about that option. Yep, I can confirm it doesn't "chomp". BTW, it is yellow! So pacman has coloured output already. ;-) -- Roman Kyrylych (Роман Кирилич)
2007/2/16, Roman Kyrylych <roman.kyrylych@gmail.com>:
2007/2/16, Aaron Griffin <aaronmgriffin@gmail.com>:
On 2/16/07, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
I could verify but I don't understand what Travis means with "ILoveCandy progress bar doesn't "chomp" anymore" :-/
If you set ILoveCandy in the pacman options (no arguments, just ILoveCandy by itself), pacman uses a fancy little "pacman" progress bar. It is supposed to alternate from 'C' to 'c' to "chomp" like pacman does.
Thanks, I remember talks about ILoveCandy but didn't know about that option. Yep, I can confirm it doesn't "chomp".
Hm, it starts with "c" but after first "o" it becomes "C" and stays so until the end. -- Roman Kyrylych (Роман Кирилич)
On Fri, 16 Feb 2007 02:47:51 -0600 "Aaron Griffin" <aaronmgriffin@gmail.com> wrote:
Latest and greatest. Not all that many changes here.. -Si works with the repo/package syntax, spacing on the "saving as .pacsave" output is fixed, etc
Mostly minor.
Test it out: http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.16-1-i686.pkg.tar.gz
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time. .... yes, this is the only issue I've found so far. :P -- Travis
2007/2/16, Travis Willard <travisw@wmpub.ca>:
On Fri, 16 Feb 2007 02:47:51 -0600 "Aaron Griffin" <aaronmgriffin@gmail.com> wrote:
Latest and greatest. Not all that many changes here.. -Si works with the repo/package syntax, spacing on the "saving as .pacsave" output is fixed, etc
Mostly minor.
Test it out: http://archlinux.org/~aaron/pacman/pacman-rc-2007.02.16-1-i686.pkg.tar.gz
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
What do you mean? Screenshot? ;-) -- Roman Kyrylych (Роман Кирилич)
On 2/16/07, Travis Willard <travisw@wmpub.ca> wrote:
Kind of a cosmetic issue, but the ILoveCandy progress bar doesn't "chomp" anymore - it just stays with a capital 'C' the whole time.
Just clearing out some issues here. This should be fixed in CVS now. I'm getting more and more behind with little things and trying to perfect the 3.0 release... so next build should fix this.
participants (6)
-
Aaron Griffin
-
Alessio 'mOLOk' Bolognino
-
Dan McGee
-
Jason Chu
-
Roman Kyrylych
-
Travis Willard