Your message dated Sat, 29 Mar 2025 09:03:22 -0300
with message-id <[email protected]>
and subject line closing this bug
has caused the Debian Bug report #1021308,
regarding gitolite3: repository "disappears" after upgrade from 3.6.6-1 to 
3.6.12-1
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 [email protected]
immediately.)


-- 
1021308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021308
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gitolite3
Version: 3.6.12-1
Severity: important

please note this bugreport is for a completely different system from the
one on which it is reported: please *IGNORE* the system information below

an upgrade on libre-soc.org to 3.6.12-1 resulted in just one of the
repositories disappearing after a cosmetic change to the gitolite.conf
file.  there are over 60 repositories on that server, and there is
cross-integration with ikiwiki

the only one that disappeared was the one to which ikiwiki has to have
write-permission

the group-perms for the wiki.git are www-data and group-set (rwxrwsrxx)

however...

changing those permissions to gitolite3 (which would have destroyed
ikiwiki's ability to commit to the repo back-end as www-data)
did not "fix" the problem and gitolite3 ultimately had to be
reverted to 3.6.6-1


-- System Information:
Debian Release: 8.1
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
Unfortunately there is still not enough information here to make any
progress. Feel free to re-open the bug if you have a recipe to reproduce
the problem.

--- End Message ---

Reply via email to