pijul_org / pijul

#149 "pijul pull" prints "Dependency not found"

Opened by laumann, on August 24, 2017
Closed
laumann commented on August 24, 2017

I just pulled from pijul_org/pijul:master and received one patch with the following output:

% pijul pull laumann@nest.pijul.com:pijul_org/pijul
Hash: AVdszbaEeNl6IWzEoofAZvnF54ywI6aihZgFGgXiJrjP1EJOhUmLzana4Ctq6XNXWb89Jmm7xJRJdWugVImX7q0
Authors: ["pmeunier <pe@pijul.org>"]
Timestamp: 2017-08-23 12:48:12.780670231 UTC

    Fixing conflicts in Cargo.lock

Shall I pull this patch? [ynkad] y
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found

I guess a dependency is missing, but which?

Note, I haven't looked that much into this yet, I'm just reporting it for now.

pmeunier commented on August 24, 2017

Ok, I suspected this (and I'm relieved).

The branch system in Pijul 0.7.2 had a pretty bad bug, fixed by #AUDjnli5MkeqLkc7LQCyUwdqrEvzzVnAWqDtQ5zwux3YOAazBIHh7ur-8XTL4Chx_hL-xUa0LXuOE3TL5x2zOYs. I believe your current issue is due to that.

Could you try to start again from a fresh repository?

laumann commented on August 24, 2017

A fresh clone works fine - I'll just migrate to that. I recompiled pijul locally to print the "missing" dependencies and pulled again:

$ pijul pull laumann@nest.pijul.com:pijul_org/pijul
Hash: AVdszbaEeNl6IWzEoofAZvnF54ywI6aihZgFGgXiJrjP1EJOhUmLzana4Ctq6XNXWb89Jmm7xJRJdWugVImX7q0
Authors: ["pmeunier <pe@pijul.org>"]
Timestamp: 2017-08-23 12:48:12.780670231 UTC

    Fixing conflicts in Cargo.lock

Shall I pull this patch? [ynkad] y
Hash: AVdszbaEeNl6IWzEoofAZvnF54ywI6aihZgFGgXiJrjP1EJOhUmLzana4Ctq6XNXWb89Jmm7xJRJdWugVImX7q0
Authors: ["pmeunier <pe@pijul.org>"]
Timestamp: 2017-08-23 12:48:12.780670231 UTC

    Fixing conflicts in Cargo.lock

Shall I pull this patch? [ynkad] 
% pijul/target/release/pijul pull laumann@nest.pijul.com:pijul_org/pijul                                                                                                                               ~/pijul/pijul [22:12]
Hash: AVdszbaEeNl6IWzEoofAZvnF54ywI6aihZgFGgXiJrjP1EJOhUmLzana4Ctq6XNXWb89Jmm7xJRJdWugVImX7q0
Authors: ["pmeunier <pe@pijul.org>"]
Timestamp: 2017-08-23 12:48:12.780670231 UTC

    Fixing conflicts in Cargo.lock

Shall I pull this patch? [ynkad] y
Hash: AYo2Imo-fVoXmBi6UL6yWqn8r-jey6grJ5ZsBT1vA6XXX641I83N6SZ8VSdd5je2M6McCjgnhsvQBGokRbsip-g
Authors: ["pmeunier <pe@pijul.org>"]
Timestamp: 2017-08-24 08:42:42.696256844 UTC

    `is_root`: decide whether a key is the root key

Shall I pull this patch? [ynkad] y
Hash: AWbqYCburC7U7bsgdfp9ikBkeTj_DoE9EgymK00Y_ME5FD-WLzQw11hhrDNRkjxUuSIy56D7AVYVbDrUCbWdBaw
Authors: ["pmeunier <pe@pijul.org>"]
Timestamp: 2017-08-24 08:42:00.800135133 UTC

    new method `get_file_names`: find the path to the file in which a key is.

Shall I pull this patch? [ynkad] y
ERROR:libpijul::apply: Dependency not found Sha512(MwkRjFWm_tpm-y94xUpzF6UmLbQn-0DcflFyrnYHp5IqvJOCv5ZyrBu0wiukmeATDBPux09d8d5oFtVSQf3dnA)
ERROR:libpijul::apply: Dependency not found Sha512(XEFYEp5yOeL_jdv0EqvesGYqk20YhtHG1LK-vvvs2uPRFA5uKKJLODDryGs_exzD9stZ95xRgBvirvaFHxwOyQ)
ERROR:libpijul::apply: Dependency not found Sha512(ZvFp2h1InjmeXe2b67RNkGeu5wwcyU5STEf_d4ucsrVMzOhfJ2mNn8KT5I657IT72lpJuQeqjjr5DrdI7jTSxg)
ERROR:libpijul::apply: Dependency not found Sha512(zJLt0bPUts6FrEJKhbFbXbJdR8cLKMGsYlLM2Yw71yGfyLniAU1jsK5mn8RwFsluyq19cxF75qqgd1-ITjjvAw)
ERROR:libpijul::apply: Dependency not found Sha512(OfAG6gaN1D2aIxwLEfbp3DZ6SmcLuUaIdQuIEgXaAea-FxhYj37L1W9cmrYe8_9-HDQPVkqEuXG3pfEal9UE3A)
ERROR:libpijul::apply: Dependency not found Sha512(bCju719zA8MFMU4iDv0ApORYJykXmelBFa9EtCQILLvSlSvHgts4s38mzGYU31lQIVip76UZY9koV0JI8a-Eyg)
ERROR:libpijul::apply: Dependency not found Sha512(mnO3DvCOzGDBhMirtfDl6ro405Xe1unaLDWTAS_zmlbhyVFF23fwn_BdbnxjZnOq4IRpCEWr2gj6O9Qhye_waA)
ERROR:libpijul::apply: Dependency not found Sha512(65lw_dwPVD_fNQ8DFL4mPpE93GevPDJ5Fr0iQTZwmfN3tODrX4wKvwZFphWaN-pqY0OSSS544e9yz4jRm5tSzQ)
ERROR:libpijul::apply: Dependency not found Sha512(zVFQHUsomIl4vUw03EGPEvlVO9zKqnN8mbIr9Sqd-yCPQLXhYJZfXwTW9oyNmG2TfXwS_AMPOJNFfS0PD56wfw)
ERROR:libpijul::apply: Dependency not found Sha512(tp4Jz1j2PEZGCRqmqMy_rp19kS9JR_duJdlrYulxjH4Jjrjp1D0cWYvhHrH0x7P9wLPlDBbjDfw_U7hvBWyOMg)
ERROR:libpijul::apply: Dependency not found Sha512(MwoP4ezkg4yTsw-Umn7JKSPedZ48p8G6xbzLe9RhvMXrHzkoLPxtY1-5BtloS8b5bhPVdcpZIjUrjt5--3Flxg)
ERROR:libpijul::apply: Dependency not found Sha512(2a59ho_BNNhTzphI6Yl7S1ExaxgmlJLPqgjNuPhnKYu6sQEVC35CXO3Safk5eO883It0l0skO10PDW97mHhGHQ)
ERROR:libpijul::apply: Dependency not found Sha512(IGeGJdDcwhMlI69S9IzwG68rxpgsT8xpsmqZNb11N8SGMMX32N9fGMLfPktw5m3EtBL9A-fJP0pqNBur10fJwA)
ERROR:libpijul::apply: Dependency not found Sha512(iWxJ8MwyIIz7ZN8yZmBTTtSwUjAS_q7uB7BpIWC67Ddj96KmVgK4rd6_EruT6XApXqRxoCK1pTQnDWUi_BedKw)
ERROR:libpijul::apply: Dependency not found Sha512(P8bWxP1xgEXRrAWRCcgEGX--3xd7o2HZ_eHdW_oHQBgJ-2XUDLNzcAld-V4cmZcIp6hw2ay7r6Wf1elFkwQNpg)
ERROR:libpijul::apply: Dependency not found Sha512(-hiGhhEuQZR1FF7XOhRxUSGYDxIDQy-Dl4C8DFpghmaEP_83k8Moq-DLYVuVhoP-BkkJk7CeCUzMt2xMs8TNTQ)
ERROR:libpijul::apply: Dependency not found Sha512(AVr-Uq895GHTtkZfUWnJ4QSDGZkrqXXp4QrK1yGhkPRdWDTR7Fv1uGoikRbqnOn7-350YLfWVsS6CPImILrF3Q)
ERROR:libpijul::apply: Dependency not found Sha512(QOOued1Hx-8XW5ZS4St4XdwwsEqZ3zr0Ri87flw4HwvySTfl_wMnmm2ywuOWNHzo-cD5hN_C3yWLDEaZ0f5Lqg)
ERROR:libpijul::apply: Dependency not found Sha512(zJoregn8c5J44ZDTVzyLrBb-Yty_fYs6Y45aFpy3wWrbxSUyqORct6FfjNUy04HK4DzNl0r1ZhGv1z_qAZmPKQ)
ERROR:libpijul::apply: Dependency not found Sha512(21GDEDBGk--MGOffafa3aX3R0BLwo2rd5c5dcqWNtfe22NfhiDQiJEl_yrKpQjqeSEmzwxqEXMV9GqWurj7ZEA)
ERROR:libpijul::apply: Dependency not found Sha512(tr8kLgFJMtEqNSeJxKk6DJ9k9dv1XXwCdCTj7i4xyts8SPchtiQupRzW-P41jL9sK3aLHR4iH5N-c-BuWhD1tA)
ERROR:libpijul::apply: Dependency not found Sha512(vRcKS-v9rQBUbNUpWKkkLohD9kKzG26ywI3E73ZSTXggbEubgcvdymXgkeqC3oLv4ydigc4aaBSDHXM88ve7Xg)
ERROR:libpijul::apply: Dependency not found Sha512(wyX7IbgwNnJ8nX6yw3W4qM_1hA9NAXFBmjWJmPUJMBxUsghTr9CEbN3nLphx_MdebuWqS0HgR7B41ojZqiXl3Q)
ERROR:libpijul::apply: Dependency not found Sha512(tp4Jz1j2PEZGCRqmqMy_rp19kS9JR_duJdlrYulxjH4Jjrjp1D0cWYvhHrH0x7P9wLPlDBbjDfw_U7hvBWyOMg)
ERROR:libpijul::apply: Dependency not found Sha512(zheqBXdXjYwTvi6bITAYfbZ5Qbd6T-MTqSgaX6XBVnSNd3Lke6p1TAjpLQYEzDWKmXxnulZm8WEeVTHtUK2PTA)
ERROR:libpijul::apply: Dependency not found Sha512(wKy1-zqVHzpRQMRtFFRtBbt8RXGZmSXDJ2R4xJ0p2tlzpMtl8QmBBACxjbHZx2QHF32PYI0YE3Geuxi_Z9dP5Q)
ERROR:libpijul::apply: Dependency not found Sha512(FfHhE_POPuz7gjd5Xld_Rbm85gkw9q3wR_P9hFmYUBwKeEGdQyzIAxwXAhxEu9w7msEO5O1M9su2k0beCMDDNQ)
ERROR:libpijul::apply: Dependency not found Sha512(tp4Jz1j2PEZGCRqmqMy_rp19kS9JR_duJdlrYulxjH4Jjrjp1D0cWYvhHrH0x7P9wLPlDBbjDfw_U7hvBWyOMg)

Which is quite interesting...

porglezomp commented on August 30, 2017

I run into this on a fresh clone while trying to pull your patches to fix Cargo.lock:

pijul clone https://nest.pijul.com/porglezomp/pijul
cd pijul
pijul pull https://nest.pijul.com/laumann/pijul:master

produces:

Hash: AfvvlyyRWWiyCGUN1GwTWdgqwu9CYi_03EiLo1_MIAzgKADAX4zGzKdKOBfHwqfAz51R1ov7noHRXlTtXNUvP7k
Authors: ["Thomas Jespersen <laumann@protonmail.com>"]
Timestamp: 2017-08-30 13:22:01.176418522 UTC

    Add Cargo.lock back again

Shall I pull this patch? [ynkad] y
Hash: AenBX1ecaGYGp2bWywjM_d0_hJY5FIz1E1MdLxvQ6B6936-HGZvXWDSRyjys68IAntNQU0RiOjklJYLJqoRDCcc
Authors: ["Thomas Jespersen <laumann@protonmail.com>"]
Timestamp: 2017-08-30 13:19:49.008546928 UTC

    Fix Cargo.lock conflict

Shall I pull this patch? [ynkad] y
ERROR:libpijul::apply: Dependency not found
ERROR:libpijul::apply: Dependency not found
(…and 24 more times)
porglezomp commented on August 30, 2017

Also interesting: after I do this, Pijul thinks that every single file in the repository is untracked.

laumann commented on August 31, 2017

@porglezomp Oh, that's not good - I've had similar issues... Thanks for trying it though!

The "everything is untracked" is another weird thing. I've been able to fix that sometimes by running pijul revert. It sometimes happens just by switching branches.

EDIT Can confirm the multiple ERROR:libpijul::apply: Dependency not found errors, but I do not get the "everything is untracked" syndrome. Instead I got that pijul/Cargo.lock has been deleted, but not yet recorded. pijul revert fixes it (and Cargo.lock looks fine).