Overview
Artifact ID: | c72342dbbb5da48d98fefa430751007d08b43880 |
---|---|
Ticket: | 1ab2001903732b9f238925eb47e68691b96f4669
Can't push changes to chiselapp.com |
User & Date: | anonymous 2021-07-19 23:39:28 |
Changes
- icomment:
I've had a chiselapp username for many years - it's the second component (of four) of my email address above. The name of the prime repo is the same as my username. Recently, I haven't been able to push changes to it - the most recent change showing on chiselapp is from June 20. My local repo has several changes since then, I have autosync switched on, so changes should have been pushed; anyway, I've done an explicit **fossil sync** and they haven't appeared. I've created a new repository, named **myStuff** and executed ``` % fossil remote https://chiselapp.com/user/<username>/repository/myStuff % fossil push ``` After the push command, fossil confirmed it was pushing to https://chiselapp.com/user/*username*/repository/myStuff, but was silent otherwise. My new repository is still empty. Before I executed the **fossil remote** command above, my local repo was pointing to https://chiselapp.com/use/*username*/repository/*username*; the command **fossil sync** behaved in a similar fashion - i.e. the only output was a message confirming the URL it was syncing with. I've raised the original **sync** problem in [the fossil forums](https://fossil-scm.org/forum/forumpost/46d8d3152162a4d4?t=h) and the folks there feel the problem lies with chiselapp not fossil. For reference, my local machine is running Linux Mint 20.2 Cinnamon, and my fossil client is 2.15 [2c6012c4aa].
- login: "anonymous"
- mimetype: "text/x-markdown"
- private_contact changed to: "66fa165f4d6461fc4cd65db7288486f7bd6fbf83"
- severity changed to: "Severe"
- status changed to: "Open"
- title changed to: "Can't push changes to chiselapp.com"
- type changed to: "Code_Defect"