Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pkgdev manifest . is complaining about manifests of other packages #85

Closed
TheChymera opened this issue Aug 24, 2022 · 14 comments
Closed

pkgdev manifest . is complaining about manifests of other packages #85

TheChymera opened this issue Aug 24, 2022 · 14 comments
Assignees
@arthurzam

Comments

@TheChymera
Copy link 

chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ pkgdev manifest .
--2022-08-24 15:16:38--  http://resources.chymera.eu/distfiles/nvcz_data-0.1.tar.xz
Resolving resources.chymera.eu... 173.236.180.143
Connecting to resources.chymera.eu|173.236.180.143|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://resources.chymera.eu/distfiles/nvcz_data-0.1.tar.xz [following]
--2022-08-24 15:16:38--  https://resources.chymera.eu/distfiles/nvcz_data-0.1.tar.xz
Connecting to resources.chymera.eu|173.236.180.143|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-08-24 15:16:39 ERROR 404: Not Found.

--2022-08-24 15:16:39--  http://resources.chymera.eu/distfiles/nvcz_data-0.2.tar.xz
Resolving resources.chymera.eu... 173.236.180.143
Connecting to resources.chymera.eu|173.236.180.143|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://resources.chymera.eu/distfiles/nvcz_data-0.2.tar.xz [following]
--2022-08-24 15:16:39--  https://resources.chymera.eu/distfiles/nvcz_data-0.2.tar.xz
Connecting to resources.chymera.eu|173.236.180.143|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-08-24 15:16:39 ERROR 404: Not Found.

 * generating manifest: sci-biology/bidsschematools::chymeric
 * failed fetching files: sci-biology/nvcz_data-0.2::chymeric
pkgdev manifest: error: failed build operation: failed fetching required distfiles

This being my overlay https://github.com/TheChymera/overlay

the actual packages aren't pushed, because pkgdev won't let me commit... It further for some reason deletes my manifests and then complains they aren't there...

chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ ebuild bidsschematools-0.4.0_rc1.ebuild manifest
>>> Creating Manifest for /home/chymera/src/overlay/sci-biology/bidsschematools
chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ cat Manifest 
DIST bids-error-examples-4dee93e8dc75ea7b63c94e1657bbc94e3e77dfd0.tar.gz 666982 BLAKE2B 08f3ec9734d323dae3bcabb5a22f0bfdb3cfff114523f73aa162fb0d62145dcb1c82315b729ced59a20edc4d896247bdbfd8dbd2aa1ec293160d2c6c1b469c16 SHA512 0cd1e3d1a5e5ecb29d5fb00293910f417b5fb0e787eed42d5242c94fcdf7871b8702ef5e1125474df32c077bc7ec810c1eeec236dbca6c9f7bb6998cf2b37a9c
DIST bids-examples-252449184b532ba08c26e53e422f1e05366ac102.tar.gz 35118815 BLAKE2B d0a8f50f362158bfa200f3db56d52e88d206d667660b65533e637078b1ca8061df751d50fcf4933336e4afd32a19b76e99d6034270b0121410d0ac4046d17a26 SHA512 c4ec6b77cae211572ade803520b07ea9d49a6d2ab8ad8f2cd3f9028ea70bd1bf8e92bbdb294aaf058f1095182bfa1ff1e0e6c138508a1dd0a9879c3ab325dc36
DIST bidsschematools-0.3.1.tar.gz 109064 BLAKE2B 9432ad8723975b20d8e64e50c44657a6fb97a01a640de8f56e32b29f6c806b3f5317c4761e9b5b567e38cdb69ae461c3e745c4de4f6f2cf648299d9376365369 SHA512 334200722d2d936abf44ea202253a46dfd6120d6dc2ce7a638abd721fdc6810e2f2172ab474883c1dcbba0de1d0e8edf8ab572af0955087375147a6d3ed76f48
DIST bidsschematools-0.3.1_p2.tar.gz 5725503 BLAKE2B bd3722a1d89d7788317a13931756200915c868c48dce9cd7ef45fa80bbe70861b38c93f9fedb95b73fb0467654c344b1d668865032528dbf5a8ef081a80bd0f8 SHA512 b1771124c0f4b81a8c36a72fba927531b202cabd043c187115cd46826e583486727e313709c41b3b3a5e3ff8a86f18066f24d48e41505019cd1e499e7afece38
DIST bidsschematools-0.4.0_rc1.tar.gz 1155987 BLAKE2B 05363a0919142c212a5ce24c840852a7407f54692ba0b260fdef374b3ceba4f8a326a805f1329be069c91ed447045d53d5070bcb7cdb0684d951e66aca091b23 SHA512 87184a7d9fc35263b78e7408892d585221e05acfc38b0322452eac977ca5361c1b5bc12c46961066496f4554ec33df095b79e276450779faed1898ef40d251d3
chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ pkgdev commit .
 * generating manifest: sci-biology/bidsschematools::chymeric
sci-biology/bidsschematools
  RedundantVersion: version 0.3.1: slot(0) keywords are overshadowed by versions: 0.3.1_p2, 0.4.0_rc1
  MissingManifest: version 0.3.1_p2: distfiles missing from Manifest: [ bids-error-examples-4dee93e8dc75ea7b63c94e1657bbc94e3e77dfd0.tar.gz, bids-examples-252449184b532ba08c26e53e422f1e05366ac102.tar.gz, bidsschematools-0.3.1_p2.tar.gz ]
  PythonGHDistfileSuffix: version 0.3.1_p2: GitHub archive 'bidsschematools-0.3.1_p2.tar.gz' ('https://github.com/bids-standard/bids-specification/archive/a87f8955b48d663eab08d7706c7302215c0e36d3.tar.gz') is not using '.gh.tar.gz' suffix
  RedundantVersion: version 0.3.1_p2: slot(0) keywords are overshadowed by version: 0.4.0_rc1
  MissingManifest: version 0.4.0_rc1: distfile missing from Manifest: [ bidsschematools-0.4.0_rc1.tar.gz ]

FAILURES
sci-biology/bidsschematools
  MissingManifest: version 0.3.1_p2: distfiles missing from Manifest: [ bids-error-examples-4dee93e8dc75ea7b63c94e1657bbc94e3e77dfd0.tar.gz, bids-examples-252449184b532ba08c26e53e422f1e05366ac102.tar.gz, bidsschematools-0.3.1_p2.tar.gz ]
  MissingManifest: version 0.4.0_rc1: distfile missing from Manifest: [ bidsschematools-0.4.0_rc1.tar.gz ]
chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ cat Manifest 
DIST bidsschematools-0.3.1.tar.gz 109064 BLAKE2B 9432ad8723975b20d8e64e50c44657a6fb97a01a640de8f56e32b29f6c806b3f5317c4761e9b5b567e38cdb69ae461c3e745c4de4f6f2cf648299d9376365369 SHA512 334200722d2d936abf44ea202253a46dfd6120d6dc2ce7a638abd721fdc6810e2f2172ab474883c1dcbba0de1d0e8edf8ab572af0955087375147a6d3ed76f48
@arthurzam arthurzam added the bug Something isn't working label Aug 24, 2022
@arthurzam arthurzam self-assigned this Aug 24, 2022
@arthurzam
Copy link
Member

  1. Please run pkgdev manifest --help and notice what does the extra arg at the end represent - [target ...] - so I guess it misinterpreted the . as all targets?
    I'm inclined to make it a special case (when it get value of . to always go just the cwd), but need to check if there is another behavior here.
    Note you should not add the . and just call pkgdev manifest
  2. The manifest and sizes of bidsschematools-0.3.0_rc1.tar.gz looks wrong? I deleted the manifest and rerun pkgdev manifest and got this diff (note that even the size changed):
diff --git a/sci-biology/bidsschematools/Manifest b/sci-biology/bidsschematools/Manifest
index 9acafeb..e3bf2d6 100644
--- a/sci-biology/bidsschematools/Manifest
+++ b/sci-biology/bidsschematools/Manifest
@@ -1,2 +1,2 @@
 DIST bidsschematools-0.3.0_pre20220801.tar.gz 5716585 SHA256 b91e5707786704c6a0ee13489d78fdc0d274b334ea435bb375498c07d40933eb SHA512 524206d54a04587180dd3b150bb4e88282d62cf1273717d3caedb6b227e74102b9b5d4e68cb2b1725ad6e19641e0fbcb5ee1b2b5931fa7025f918d72e8a591a9 WHIRLPOOL 8a732807ee307fe96093c1fa9b4943d8bf5bbe07a24258460c23d2f35adb91c8cce08516dcd8c8e61d0fe2be2a34ca0d8063612697031520fa5fba083cf4be7c
-DIST bidsschematools-0.3.0_rc1.tar.gz 5717759 SHA256 3789692e42d975eda76c680b53a8057c4d15b05983e879c09ab43291effa99fa SHA512 f250fd9fd88524d6d35ecd446e1b9abd7c80aa845ed08ee281f996a52e36f6e9d9eee855b752e1c7b35ae5c456eae94ca29b81e4585637286c1f535a5ec93105 WHIRLPOOL 4c6e42969a43c391af691784f4272603b0f26f173704add71891c6d9a255ae0e91444e538089c81368fdb5cc003e534425c9b95dd8f1888af3341f68cf48d613
+DIST bidsschematools-0.3.0_rc1.tar.gz 5718395 SHA256 c67cb4e4ae5ab8cefec19c171543e75b63246ea14e11efb5676e7ec8fb369b5c SHA512 032892e29e506b2b7865d81ce57966431bb8d480f8594f6f5da7ce5e83e8ba527987ad894a377f65dde3b7bc2638c914814c558c164f547b8da3ff36e338b1f4 WHIRLPOOL 35748fb6c96013507363d21a48ab797cbeafeb68bbaed6ea4339ab2a7be2524c987e8b56883bbb9d90f3acbdbe81347181294c1d67f6c68670e6bf1b554b589e

@TheChymera
Copy link
Author

@arthurzam ok, removing the file and re-running the command without the period seems to have solved it. So technically the issue from the title is solved, but what I mentioned in the text still happens, pkgdev commit still deletes the manifest and complains about not finding what it's looking for:

chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ cat Manifest 
DIST bids-error-examples-4dee93e8dc75ea7b63c94e1657bbc94e3e77dfd0.tar.gz 666982 BLAKE2B 08f3ec9734d323dae3bcabb5a22f0bfdb3cfff114523f73aa162fb0d62145dcb1c82315b729ced59a20edc4d896247bdbfd8dbd2aa1ec293160d2c6c1b469c16 SHA512 0cd1e3d1a5e5ecb29d5fb00293910f417b5fb0e787eed42d5242c94fcdf7871b8702ef5e1125474df32c077bc7ec810c1eeec236dbca6c9f7bb6998cf2b37a9c
DIST bids-examples-252449184b532ba08c26e53e422f1e05366ac102.tar.gz 35118815 BLAKE2B d0a8f50f362158bfa200f3db56d52e88d206d667660b65533e637078b1ca8061df751d50fcf4933336e4afd32a19b76e99d6034270b0121410d0ac4046d17a26 SHA512 c4ec6b77cae211572ade803520b07ea9d49a6d2ab8ad8f2cd3f9028ea70bd1bf8e92bbdb294aaf058f1095182bfa1ff1e0e6c138508a1dd0a9879c3ab325dc36
DIST bidsschematools-0.3.1.tar.gz 109064 BLAKE2B 9432ad8723975b20d8e64e50c44657a6fb97a01a640de8f56e32b29f6c806b3f5317c4761e9b5b567e38cdb69ae461c3e745c4de4f6f2cf648299d9376365369 SHA512 334200722d2d936abf44ea202253a46dfd6120d6dc2ce7a638abd721fdc6810e2f2172ab474883c1dcbba0de1d0e8edf8ab572af0955087375147a6d3ed76f48
DIST bidsschematools-0.3.1_p2.tar.gz 5725503 BLAKE2B bd3722a1d89d7788317a13931756200915c868c48dce9cd7ef45fa80bbe70861b38c93f9fedb95b73fb0467654c344b1d668865032528dbf5a8ef081a80bd0f8 SHA512 b1771124c0f4b81a8c36a72fba927531b202cabd043c187115cd46826e583486727e313709c41b3b3a5e3ff8a86f18066f24d48e41505019cd1e499e7afece38
DIST bidsschematools-0.4.0_rc1.tar.gz 1155987 BLAKE2B 05363a0919142c212a5ce24c840852a7407f54692ba0b260fdef374b3ceba4f8a326a805f1329be069c91ed447045d53d5070bcb7cdb0684d951e66aca091b23 SHA512 87184a7d9fc35263b78e7408892d585221e05acfc38b0322452eac977ca5361c1b5bc12c46961066496f4554ec33df095b79e276450779faed1898ef40d251d3
chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ pkgdev commit
 * generating manifest: sci-biology/bidsschematools::chymeric
sci-biology/bidsschematools
  RedundantVersion: version 0.3.1: slot(0) keywords are overshadowed by versions: 0.3.1_p2, 0.4.0_rc1
  MissingManifest: version 0.3.1_p2: distfiles missing from Manifest: [ bids-error-examples-4dee93e8dc75ea7b63c94e1657bbc94e3e77dfd0.tar.gz, bids-examples-252449184b532ba08c26e53e422f1e05366ac102.tar.gz, bidsschematools-0.3.1_p2.tar.gz ]
  PythonGHDistfileSuffix: version 0.3.1_p2: GitHub archive 'bidsschematools-0.3.1_p2.tar.gz' ('https://github.com/bids-standard/bids-specification/archive/a87f8955b48d663eab08d7706c7302215c0e36d3.tar.gz') is not using '.gh.tar.gz' suffix
  RedundantVersion: version 0.3.1_p2: slot(0) keywords are overshadowed by version: 0.4.0_rc1
  MissingManifest: version 0.4.0_rc1: distfile missing from Manifest: [ bidsschematools-0.4.0_rc1.tar.gz ]

FAILURES
sci-biology/bidsschematools
  MissingManifest: version 0.3.1_p2: distfiles missing from Manifest: [ bids-error-examples-4dee93e8dc75ea7b63c94e1657bbc94e3e77dfd0.tar.gz, bids-examples-252449184b532ba08c26e53e422f1e05366ac102.tar.gz, bidsschematools-0.3.1_p2.tar.gz ]
  MissingManifest: version 0.4.0_rc1: distfile missing from Manifest: [ bidsschematools-0.4.0_rc1.tar.gz ]
chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $ cat Manifest 
DIST bidsschematools-0.3.1.tar.gz 109064 BLAKE2B 9432ad8723975b20d8e64e50c44657a6fb97a01a640de8f56e32b29f6c806b3f5317c4761e9b5b567e38cdb69ae461c3e745c4de4f6f2cf648299d9376365369 SHA512 334200722d2d936abf44ea202253a46dfd6120d6dc2ce7a638abd721fdc6810e2f2172ab474883c1dcbba0de1d0e8edf8ab572af0955087375147a6d3ed76f48
chymera@darkhost ~/src/overlay/sci-biology/bidsschematools $

@TheChymera
Copy link
Author

@arthurzam ok, so this issue disappeared after I ran git add . in the ebuild directory. So I guess it was just me (1) misinterpreting what . does in pkgdev manifest . and/or (2) forgetting to add my ebuilds. Nevertheless it would be helpful to actually get a warning about that... so unless it's something else, I'll leave this open for now.

@TheChymera
Copy link
Author

Ok, so I don't think this was me forgetting to run git add .
Apparently pkgdev won't do anything unless I run git add . (or */*/Manifest depending on what I'm working on) before I run pkgdev commit --- even if these are files which were already tracked by git.

If I run git add */*/Manifest && cd app-misc/gebuilder and then try pkgdev commit . inside that directory, it will again complain about errors in all other packages.
So now I can't use it again because I can't fix just the issues in one package: https://ppb.chymera.eu/a294b8

@thesamesam
Copy link
Member

Please show the output of git status when it misbehaves.

@arthurzam
Copy link
Member

@TheChymera I want to do a full stop, and explain a little about the flows of pkgdev and suggest how to customize it for you to be the best experience, as I see there was a little misunderstanding.
For other people reading this comment, this answer is also based on talk done at IRC channel #gentoo-dev-help, so I'm sorry if I'm out of scope.

pkgdev commit is a "smart" wrapper around git commit. In very simple terms, it does the following:

  1. It parses the current staged changes (in simple terms, those that were git added)
    If you want it to automatically add the current changes in cwd, pass -a to the invocation. With this flag, it matches behavior of repoman.
  2. It traverses the changes applied in those staged changes, to try to generate smart title.
    Note that it checks all staged changes! So if you have other files in the staged state (AKA you git added other files) it will include them in this step!
    • It infers the title "prefix", AKA package name (cat/pkg), category name (cat/*), or everywhere (*/*)
    • It scans the diff itself in hope to find a good action summary
  3. If passes -s, it uses pkgcheck scan to scan the changes for QA things. Note that it scans all staged packages!
    With this flag, it matches behavior of repoman.
  4. It finally calls git commit with all extra args passed, while using -m [title] with title from step 3.

Now, I feel like your staged part of git is a little broken, you can use git status to view state of staged/index. Please unstage all files.

How I best recommend to use pkgdev commit (this is the way I use it, and note that I already use it in various fast scripts, so it was under heavy stress):

  1. Don't use git add except in manual operations. You might conflict with pkgdev auto states (step 3)
  2. cd into the package dir and call pkgdev commit -as . (auto add files from this pkg dir, scan for QA mistakes, and include only current dir)
    The . might be unnecessary, but it makes me feel safer, so feel free to not pass .
  3. Continue work on tree as you would like.
  4. Call pkgdev push to push changes.

Because at some point I started to hate always passing -as, I added configuration support to pkgdev, so I have file ~/.config/pkgdev/pkgdev.conf with content:

[DEFAULT]
commit.scan = true
commit.mangle = true
commit.all =
commit.signoff = true

@arthurzam arthurzam removed the bug Something isn't working label Aug 31, 2022
@TheChymera
Copy link
Author

Hi @arthurzam .

So if I only do global commits for the entire package dir — as I generally do — and always and only use pkgdev commit -a -s ., it works.
However if I try to do anything else with it it causes trouble again.
This is a different dir in a fresh repo, so it's not stuff creeping in from other sources.
I am unsure what's happening but pkgdev again breaks files and then yells at me for them being broken:

chymera@decohost ~/src/overlay/dev-python/etelemetry $ cat Manifest
DIST etelemetry-0.2.2.tar.gz 25890 BLAKE2B 3d2f0b77211f8af6b752126775b4d69e93675accd4041840d9905ea01affd5b70f628f56d06312390286c468eac77e04f139f2a6839d54aa1b2f9245af54447b SHA512 478d6a529c4363a699bc3c3ff84e02c168fab3ba8e2397c6babf07afb7565fb34b8dcdca6d7dc7878085e6ec96acb82e96c9bf2dd5ef5b7b5ebf05e1cdb70549
chymera@decohost ~/src/overlay/dev-python/etelemetry $ pkgdev manifest .
 * generating manifest: dev-python/etelemetry::chymeric
chymera@decohost ~/src/overlay/dev-python/etelemetry $ cat Manifest
DIST etelemetry-0.2.2.tar.gz 25890 BLAKE2B 3d2f0b77211f8af6b752126775b4d69e93675accd4041840d9905ea01affd5b70f628f56d06312390286c468eac77e04f139f2a6839d54aa1b2f9245af54447b SHA512 478d6a529c4363a699bc3c3ff84e02c168fab3ba8e2397c6babf07afb7565fb34b8dcdca6d7dc7878085e6ec96acb82e96c9bf2dd5ef5b7b5ebf05e1cdb70549
DIST etelemetry-0.3.0.tar.gz 28120 BLAKE2B 4765c3fbb315f0572abec0afdce2d0f73943bb40f668bdf9b0798f2dd7e973f7e5bc9eb98a6bef537b990e2ca2720f0c1ad2c3e25088328e86d985d5d3b67519 SHA512 9332e286fdc3c11b20b33501bf65346772e2db10c01d9a093d51eaea36b3c48e72f1edd16ff15b6e1b3c589fe3caa2aa36a2bde8d211c5eab5abc913ae767d3f
chymera@decohost ~/src/overlay/dev-python/etelemetry $ git add Manifest etelemetry-0.2.2.ebuild
chymera@decohost ~/src/overlay/dev-python/etelemetry $ pkgdev commit etelemetry-0.2.2.ebuild Manifest
 * generating manifest: dev-python/etelemetry::chymeric
dev-python/etelemetry
  PythonCompatUpdate: version 0.2.2: PYTHON_COMPAT update available: python3_11
  RedundantVersion: version 0.2.2: slot(0) keywords are overshadowed by version: 0.3.0
  MissingManifest: version 0.3.0: distfile missing from Manifest: [ etelemetry-0.3.0.tar.gz ]

FAILURES
dev-python/etelemetry
  MissingManifest: version 0.3.0: distfile missing from Manifest: [ etelemetry-0.3.0.tar.gz ]
chymera@decohost ~/src/overlay/dev-python/etelemetry $ cat Manifest
DIST etelemetry-0.2.2.tar.gz 25890 BLAKE2B 3d2f0b77211f8af6b752126775b4d69e93675accd4041840d9905ea01affd5b70f628f56d06312390286c468eac77e04f139f2a6839d54aa1b2f9245af54447b SHA512 478d6a529c4363a699bc3c3ff84e02c168fab3ba8e2397c6babf07afb7565fb34b8dcdca6d7dc7878085e6ec96acb82e96c9bf2dd5ef5b7b5ebf05e1cdb70549

@TheChymera
Copy link
Author

TheChymera commented Sep 14, 2022 •
edited
Loading

@arthurzam

cd into the package dir and call pkgdev commit -as .

Also, this fix you mentioned and which I misquoted in the post above does not actually work in the stated form, the arguments need to be switched around:

chymera@decohost ~/src/overlay/dev-python/etelemetry $ pkgdev commit -as .
pkgdev commit: error: argument -s/--scan: invalid boolean value: '.'
chymera@decohost ~/src/overlay/dev-python/etelemetry $ pkgdev commit -s -a .
 * generating manifest: dev-python/etelemetry::chymeric
dev-python/etelemetry
  PythonCompatUpdate: version 0.2.2: PYTHON_COMPAT update available: python3_11
  RedundantVersion: version 0.2.2: slot(0) keywords are overshadowed by version: 0.3.0
[master 786c564] dev-python/etelemetry: add 0.3.0
 2 files changed, 39 insertions(+)
 create mode 100644 dev-python/etelemetry/etelemetry-0.3.0.ebuild

@TheChymera
Copy link
Author

@thesamesam said I should also give you git status:

chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git status
On branch master
Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   etelemetry-0.2.2.ebuild

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	../../dev-lang/
	etelemetry-0.3.0.ebuild
	../multiscale-spatial-image/
	../rsa/
	../spikeextractors/.spikeinterface-0.10.0.ebuild.swp
	../zarr/
	../../metadata/md5-cache/
	../../sci-biology/afni/files/
	../../sci-biology/fsl/
	../../sci-visualization/mricrogl/

chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git add Manifest
chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git status
On branch master
Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   etelemetry-0.2.2.ebuild

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	../../dev-lang/
	etelemetry-0.3.0.ebuild
	../multiscale-spatial-image/
	../rsa/
	../spikeextractors/.spikeinterface-0.10.0.ebuild.swp
	../zarr/
	../../metadata/md5-cache/
	../../sci-biology/afni/files/
	../../sci-biology/fsl/
	../../sci-visualization/mricrogl/

@thesamesam
Copy link
Member

Possibly #83 related (it's complaining about an ebuild which isn't staged).

@TheChymera
Copy link
Author

@thesamesam correction to the post above, apparently in addition to breaking the file, pkgdev just goes ahead and removes it from the git add list:

chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git diff | cat
diff --git a/dev-python/etelemetry/Manifest b/dev-python/etelemetry/Manifest
index 8dc3eb8..758264b 100644
--- a/dev-python/etelemetry/Manifest
+++ b/dev-python/etelemetry/Manifest
@@ -1 +1,2 @@
 DIST etelemetry-0.2.2.tar.gz 25890 BLAKE2B 3d2f0b77211f8af6b752126775b4d69e93675accd4041840d9905ea01affd5b70f628f56d06312390286c468eac77e04f139f2a6839d54aa1b2f9245af54447b SHA512 478d6a529c4363a699bc3c3ff84e02c168fab3ba8e2397c6babf07afb7565fb34b8dcdca6d7dc7878085e6ec96acb82e96c9bf2dd5ef5b7b5ebf05e1cdb70549
+DIST etelemetry-0.3.0.tar.gz 28120 BLAKE2B 4765c3fbb315f0572abec0afdce2d0f73943bb40f668bdf9b0798f2dd7e973f7e5bc9eb98a6bef537b990e2ca2720f0c1ad2c3e25088328e86d985d5d3b67519 SHA512 9332e286fdc3c11b20b33501bf65346772e2db10c01d9a093d51eaea36b3c48e72f1edd16ff15b6e1b3c589fe3caa2aa36a2bde8d211c5eab5abc913ae767d3f
chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git add Manifest
chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git diff | cat
chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git status
On branch master
Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   Manifest
	modified:   etelemetry-0.2.2.ebuild

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	../../dev-lang/
	etelemetry-0.3.0.ebuild
	../multiscale-spatial-image/
	../rsa/
	../spikeextractors/.spikeinterface-0.10.0.ebuild.swp
	../zarr/
	../../metadata/md5-cache/
	../../sci-biology/afni/files/
	../../sci-biology/fsl/
	../../sci-visualization/mricrogl/

chymera@decohost ~/src/_overlay/dev-python/etelemetry $ pkgdev commit etelemetry-0.2.2.ebuild Manifest
 * generating manifest: dev-python/etelemetry::chymeric
dev-python/etelemetry
  PythonCompatUpdate: version 0.2.2: PYTHON_COMPAT update available: python3_11
  RedundantVersion: version 0.2.2: slot(0) keywords are overshadowed by version: 0.3.0
  MissingManifest: version 0.3.0: distfile missing from Manifest: [ etelemetry-0.3.0.tar.gz ]

FAILURES
dev-python/etelemetry
  MissingManifest: version 0.3.0: distfile missing from Manifest: [ etelemetry-0.3.0.tar.gz ]
chymera@decohost ~/src/_overlay/dev-python/etelemetry $ git status
On branch master
Your branch is behind 'origin/master' by 2 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
	modified:   etelemetry-0.2.2.ebuild

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	../../dev-lang/
	etelemetry-0.3.0.ebuild
	../multiscale-spatial-image/
	../rsa/
	../spikeextractors/.spikeinterface-0.10.0.ebuild.swp
	../zarr/
	../../metadata/md5-cache/
	../../sci-biology/afni/files/
	../../sci-biology/fsl/
	../../sci-visualization/mricrogl/

@TheChymera
Copy link
Author

@arthurzam on 0.2.1-r3 and 0.2.2 the . argument still seems to be interpreted as meaning all files, and not just the current directory:

chymera@decohost ~/src/sci/sci-biology/bidsschematools $ pkgdev manifest .
 * generating manifest: sci-biology/bidsschematools::science
 * generating manifest: sci-visualization/mricrogl::science
chymera@decohost ~/src/sci/sci-biology/bidsschematools $ git stash
Saved working directory and index state WIP on master: d3c3c1840 net-misc/cernbox-client: drop 2.10.0.6519
chymera@decohost ~/src/sci/sci-biology/bidsschematools $ pkgdev manifest bidsschematools-0.*
 * generating manifest: sci-biology/bidsschematools::science

@thesamesam
Copy link
Member

Please always share git status at the beginning of output.

@TheChymera
Copy link
Author

TheChymera commented Sep 27, 2022 •
edited
Loading

@thesamesam this is what it returned:

chymera@decohost ~/src/sci/sci-biology/bidsschematools $ git status
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	../../sci-visualization/mricrogl/mricrogl-1.2.20210317.ebuild

nothing added to commit but untracked files present (use "git add" to track)

@thesamesam thesamesam mentioned this issue Oct 14, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arthurzam arthurzam

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@TheChymera @arthurzam @thesamesam