Package seems not to be updated

simonls · April 12, 2022, 12:21am

Since:

github.com/spdegabrielle/Qi-Quickscripts

package name consistent with name on package index

spdegabrielle:master ← SimonLSchlee:consistent-pkgname-case

opened 07:33PM - 10 Apr 22 UTC

SimonLSchlee

+6 -6

This is one way to fix #2 With this change the github project name is still in…consistent, which sadly means that when you just use the github clone copy&paste `git@github.com:spdegabrielle/qi-quickscripts.git` followed by `raco pkg install` in that directory you end up with a `qi-quickscripts` package name, while it is named `Qi-Quickscripts` if you install via package index via `raco pkg install Qi-Quickscripts`. I am not sure what would be better: 1. this pull request + rename this git repository to start with uppercase & a quick syncronized update of the package index pathes/meta-info. 2. Or the other way around change everything to lowercase, but that would mean dependencies have to change, which seems like a bigger problem than 1. Creating a draft pull request, because I want feedback on this, I think 1. could work well.

the package server seems to be stuck, not updating the package. The package name stayed the same, however it points to a git repository that was renamed to make the case consistent with the package name.

Can somebody look into what is happening?

joeld · April 13, 2022, 12:04am

I pushed some new commits to my splitflap package 4 days ago and apparently people still aren’t seeing any updates. @samth or @mflatt is there something up with the package server again?

samth · April 13, 2022, 12:17am

There was a problem, but it's been fixed. Splitflap seems updated: splitflap

simonls · April 13, 2022, 1:43am

It still isn't updating, maybe it is somehow similar to this issue (mentioned by @countvajhula):

github.com/racket/pkg-index

Renaming a package with only lower-/upper-case changes does not work

opened 11:34PM - 05 Jun 20 UTC

countvajhula

Re: [this email thread](https://groups.google.com/forum/#!topic/racket-users/VeL…kiGtmH9s), I wanted to change a package name from Titlecase to lowercase. This didn't work, but renaming it to a different name and then back to the lowercase version did work. E.g.: This works: `Mypackage -> Mypackage-temp -> mypackage ` But not `Mypackage -> mypackage ` As Tony pointed out in the email thread, it likely prevents the direct rename because the new name conflicts with "an existing" package (i.e. itself). Also, last time I checked (which could have been months ago), `raco pkg install <pkgname>` did not find the package unless the Titlecase name was used, and likewise in `info.rkt`, the Titlecase name was needed to indicate the dependency or it would not be found. Since names differing only in case are considered equivalent for the purposes of uniqueness, should this not perhaps also hold for `raco` and `info.rkt`? i.e. raco pkg install should tolerate case variation to install the unique package that such varying names could refer to (whatever the "preserved" case of that package name may be). For reference, this is the package that was renamed: https://pkgd.racket-lang.org/pkgn/package/relation

However the package name wasn't changed, instead the case of the git repository has changed.
Maybe there is some problem where there is a mixture of some kind of case-insensitive part and another that is case-sensitive?
Does the build environment start from a cleaned-up state or is there a lowercase "qi-quickscripts" folder hanging around somewhere that somehow prevents the uppercase version from being build, or something similar?

I don't really understand the details.

sorawee · April 13, 2022, 2:13am

Perhaps it's because of https://github.com/racket/racket/issues/4122? The checksum doesn't change, right? A fake empty commit is worth trying.

samth · April 13, 2022, 3:10pm

It looks updated to me. Both the repository and the pkg server agree that the checksum is 6eea8599e2fa9.

simonls · April 13, 2022, 9:44pm

Hmm the docs now look update to me, maybe that was actually a browser cache issue, maybe I have forgotten to force reload. The package says it last updated yesterday.

simonls · April 13, 2022, 9:52pm

Maybe, but I also pushed a commit, I don't really have good data about what happened when and now it just works. Maybe it just looked as if it hadn't been updated, if my browser showed me a cached version, I am not sure now.

dstorrs · April 28, 2022, 3:35pm

Necro bump.

majordomo2 is stuck at commit 1ae638f7c55afc08fb7afbd36836b0c4dc3ec00f although current is e09f7aad66c6bed898dc7b1c4b9a14f4cc2dc8e7. I did multiple 'rescan all my packages' yesterday and another today without success. Is there anything I can do beyond that?

samth · April 29, 2022, 6:48pm

I fixed this again. Messaging me on Slack or Discord is more likely to get my attention quickly if this happens.

dstorrs · April 29, 2022, 7:18pm

Thanks, Sam. I'll keep that in mind for next time -- I haven't been on either but I'll look for them.

Topic		Replies	Views
Help with Package Index Issue Site Feedback question	2	273	December 2, 2021
Package removed after trying to update them Questions & Answers question	4	142	January 5, 2024
Package Server new package workaround Questions & Answers	11	320	April 8, 2022
Package building seems stop working Questions & Answers	2	130	December 22, 2022
Suggestion: track if your modules have been installed from pkg server Questions & Answers suggestion	3	270	February 12, 2022

Package seems not to be updated

Related Topics