[pacman-dev] .pacnew created when not needed, was: [signoff] openssh 5.0p1
2008/4/10, Xavier <shiningxc@gmail.com>:
On Thu, Apr 10, 2008 at 9:23 AM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
Hmm.. pacman created /etc/ssh/sshd_config.pacnew, but I didn't modify sshd_config, so I wonder why pacman didn't just overwrite it. :-/
Could you keep your /etc/ssh/sshd_config file, downgrade openssh to the older version, then check the output of pacman -Qii openssh ? And check the md5sum manually if needed.
If it tells you sshd_config is indeed not modified, try upgrading again, using --debug this time, and check the debug output of pacman.
I've deleted that file already. But I had an older snapshot so I've tried to reproduce the issue again. And I got it clearly reproduceable: 0) I have clean install from 0.4 archboot iso (IIRC) in vmware with pacman 3.1.3 and no openssh, only some packages were upgraded, so package database is not broken 1) pacman -S openssh --noconfirm --debug > install.log 2) pacman -Syu only upgrading pacman from 3.1.3 to 3.1.4 3) pacman -S openssh --noconfirm --debug > upgrade.log (upgrading from 4.7 to 5.0 where default sshd_config was chaged) 4) ls /etc/ssh/ moduli ssh_config sshd_config sshd_config.pacnew 5) pacman -Qii openssh | grep -A3 Backup > Qii.txt Logs are attached. As can be seen from upgrade.log pacman makes a wrong decission when comparing existing, new and original md5sums (original is empty). I'm keeping that old snapshot so I can reproduce the issue again if more debugging is needed. -- Roman Kyrylych (Роман Кирилич)
On Fri, Apr 11, 2008 at 9:56 AM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
0) I have clean install from 0.4 archboot iso (IIRC) in vmware with pacman 3.1.3 and no openssh, only some packages were upgraded, so package database is not broken
Hmm, you had 3.1.3, but which libarchive version? As Dan previously stated, the main reason for 3.1.4 release was this commit : http://projects.archlinux.org/git/?p=pacman.git;a=commitdiff;h=3fe43ffa04efd...
Logs are attached. As can be seen from upgrade.log pacman makes a wrong decission when comparing existing, new and original md5sums (original is empty).
pacman didn't make a wrong decision, the problem is indeed that the original md5sum is empty. This could for example be caused by the bug fixed by the above commit.
2008/4/11, Xavier <shiningxc@gmail.com>:
On Fri, Apr 11, 2008 at 9:56 AM, Roman Kyrylych
<roman.kyrylych@gmail.com> wrote:
0) I have clean install from 0.4 archboot iso (IIRC) in vmware with pacman 3.1.3 and no openssh, only some packages were upgraded, so package database is not broken
Hmm, you had 3.1.3, but which libarchive version? As Dan previously stated, the main reason for 3.1.4 release was this commit : http://projects.archlinux.org/git/?p=pacman.git;a=commitdiff;h=3fe43ffa04efd...
Logs are attached. As can be seen from upgrade.log pacman makes a wrong decission when comparing existing, new and original md5sums (original is empty).
pacman didn't make a wrong decision, the problem is indeed that the original md5sum is empty. This could for example be caused by the bug fixed by the above commit.
Aha! That explains things. It was definetely the old libarchive version that accompanied 3.1.3 pacman on that snapshot. -- Roman Kyrylych (Роман Кирилич)
On Fri, Apr 11, 2008 at 12:03 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
Aha! That explains things. It was definetely the old libarchive version that accompanied 3.1.3 pacman on that snapshot.
If it was the old version ( <= 2.4.12 ), then nothing is explained and it remains a mystery. If it was a newer version ( >= 2.4.14 ), it explains it. But you didn't say which version, so I don't know :)
2008/4/11, Xavier <shiningxc@gmail.com>:
On Fri, Apr 11, 2008 at 12:03 PM, Roman Kyrylych
<roman.kyrylych@gmail.com> wrote:
Aha! That explains things. It was definetely the old libarchive version that accompanied 3.1.3 pacman on that snapshot.
If it was the old version ( <= 2.4.12 ), then nothing is explained and it remains a mystery. If it was a newer version ( >= 2.4.14 ), it explains it. But you didn't say which version, so I don't know :)
Oops, sorry. :-) It was 2.4.14-1 -- Roman Kyrylych (Роман Кирилич)
On Fri, Apr 11, 2008 at 6:06 AM, Xavier <shiningxc@gmail.com> wrote:
On Fri, Apr 11, 2008 at 12:03 PM, Roman Kyrylych
<roman.kyrylych@gmail.com> wrote:
Aha! That explains things. It was definetely the old libarchive version that accompanied 3.1.3 pacman on that snapshot.
If it was the old version ( <= 2.4.12 ), then nothing is explained and it remains a mystery. If it was a newer version ( >= 2.4.14 ), it explains it. But you didn't say which version, so I don't know :)
Test case that should test Xavier's theory: 1. Start from clean image 2. pacman -Syu (I believe this should prompt you to upgrade both pacman and libarchive to 2.4.17) 3. Now try all ssh-related steps -Dan
participants (3)
-
Dan McGee
-
Roman Kyrylych
-
Xavier