View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006877 | GNUnet | build process | public | 2021-05-18 03:19 | 2023-01-09 10:13 |
| Reporter | Brendan | Assigned To | schanzen | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Product Version | Git master | ||||
| Summary | 0006877: Consider allowing shallow fetches from git repos. | ||||
| Description | When fetching a commit behind HEAD from gnunet/taler repos, git has to do a full fetch instead which takes a long time. It is convenient for packaging from a commit that it can do a shallow fetch to save time, but not essential. | ||||
| Additional Information | guile: warning: failed to install locale environment variable `PATH' set to `/gnu/store/378zjf2kgajcfd7mfr98jn5xyc5wa3qv-gzip-1.10/bin:/gnu/store/sf3rbvb6iqcphgm1afbplcs72hsywg25-tar-1.32/bin' hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name> Initialized empty Git repository in /gnu/store/18pi1dbri5p3w8fpm3qs65p5pm6nxhcz-gnunet-0.14.1-c2cd7ec/.git/ error: Server does not allow request for unadvertised object c2cd7ec031ff925294b5c4c0c992fe9014846430 Failed to do a shallow fetch; retrying a full fetch... | ||||
| Tags | No tags attached. | ||||
|
|
Can you elaborate why you need this? We usually tag our releases so you can pull the tags and dev branches as well as master(0000004:0000001) |
|
|
Sometimes we build from other commits when the release is broken and bugs are fixed later like is the case now. It's not a big deal, you can always reject this if its somehow troublesome to do. In guix we have roughly 1100 packages who's source refers to some arbitrary commit for various reasons rather than the release tarball or tag. |
|
|
I think our policy for packagers is that they can get their own account and work in a branch for packaging. There you may then create tags (e.g. 0.14.1guix{0,1,2...}) which include fixes to your build system as well in order to create your own release versions. At least, that is how it will be for debian. |
|
|
I did not find an option to do that for our infra. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-05-18 03:19 | Brendan | New Issue | |
| 2021-05-18 09:54 | schanzen | Note Added: 0017873 | |
| 2021-05-18 14:35 | Brendan | Note Added: 0017875 | |
| 2021-05-18 19:00 | schanzen | Note Added: 0017877 | |
| 2023-01-09 10:13 | schanzen | Assigned To | => schanzen |
| 2023-01-09 10:13 | schanzen | Status | new => resolved |
| 2023-01-09 10:13 | schanzen | Resolution | open => won't fix |
| 2023-01-09 10:13 | schanzen | Note Added: 0019618 |
