Your message dated Thu, 03 Oct 2024 18:19:08 +0100 with message-id <5a604f25df8d5b2a2624bf3265976b46f218f1e4.ca...@adam-barratt.org.uk> and subject line Re: Bug#977733: www.debian.org: inconsistent info in repo regarding file english/News/2019/20190216.wml has caused the Debian Bug report #977733, regarding www.debian.org: inconsistent info in repo regarding file english/News/2019/20190216.wml to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977733 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: www.debian.org Severity: normal Dear Maintainers, It seems that there is something odd in the webmaster-team/webwml.git repository at salsa regarding file english/News/2019/20190216.wml. We get inconsistent results when we issue the git log command using different arguments. Commit with hash 9bd5a55d72acee622d9e25eecb70e1beb93d0ea4 was made in December 2019, and it corresponds to a modification of file english/News/2019/20190216.wml according to the output of the "git log ... commit-hash" command: $ git log -n1 --format=fuller --name-only 9bd5a55d72acee622d9e25eecb70e1beb93d0ea4 commit 9bd5a55d72acee622d9e25eecb70e1beb93d0ea4 Author: Laura Arjona Reina <larj...@debian.org> AuthorDate: Fri Dec 13 20:13:29 2019 +0100 Commit: Laura Arjona Reina <larj...@debian.org> CommitDate: Fri Dec 13 20:13:29 2019 +0100 remove the tag for frontpage english/News/2019/20190216.wml On the other hand, if we ask for the commits that represent modifications of the very same file via the "git log -- path/filename" command, we get the following: $ git log --format=fuller --name-only -- english/News/2019/20190216.wml commit ea6a13e28f99e15f67ccfd6b74b4cc4bb185fdbd Author: Laura Arjona Reina <larj...@debian.org> AuthorDate: Tue Apr 2 08:28:56 2019 +0200 Commit: Laura Arjona Reina <larj...@debian.org> CommitDate: Tue Apr 2 08:35:59 2019 +0200 https://security.debian.org -> https://www.debian.org/security english/News/2019/20190216.wml commit fdc485a3cb59ae0b5ef29c7ff90f411b2444ed09 Author: Donald Norwood <don...@debian.org> AuthorDate: Sat Feb 16 10:38:53 2019 -0500 Commit: Donald Norwood <don...@debian.org> CommitDate: Sat Feb 16 10:38:53 2019 -0500 Debian 9.8 release announcement english/News/2019/20190216.wml As you can see, the output of the second command does not include the commit with hash 9bd5a55d72acee622d9e25eecb70e1beb93d0ea4, Dec. 2019. The first (most recent) commit shown was made in April 2019. Note: we have found a similar behaviour regarding file english/CD/faq/index.wml. If you think that it is better to submit a separate bug report for it, please, let me know. Regards, Rafa.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---On Sun, 2022-01-23 at 10:09 +0000, Rafa wrote: > When we add the option --full-history to our "git log -- > path/filename" > command we do get the commit we expected (the one with hash > 9bd5a55d72acee622d9e25eecb70e1beb93d0ea4): [...] > So, the reported behaviour seems to be just a consequence of git log > command's default history simplification. > > I think that this bug report can be closed now. Doing so now. Regards, Adam
--- End Message ---
