Is it limited to 6 month that the life of old library on PlatformIO system?

Actually the options should come after the publish command and then the file name. Have you tried

pio package publish --owner asukiaaa --released-at "2020-04-29 14:09:00" 1.0.0.zip

No difference with using the command.

pio package publish --owner asukiaaa --released-at "2020-04-29 14:09:00" 1.0.0.zip 
Error: Traceback (most recent call last):
  File "/home/asuki/.local/lib/python3.8/site-packages/platformio/__main__.py", line 109, in main
    cli()  # pylint: disable=no-value-for-parameter
  File "/home/asuki/.local/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/asuki/.local/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/asuki/.local/lib/python3.8/site-packages/platformio/commands/__init__.py", line 44, in invoke
    return super(PlatformioCLI, self).invoke(ctx)
  File "/home/asuki/.local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/asuki/.local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/asuki/.local/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/asuki/.local/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/asuki/.local/lib/python3.8/site-packages/platformio/commands/package.py", line 87, in package_publish
    archive_path = p.pack()
  File "/home/asuki/.local/lib/python3.8/site-packages/platformio/package/pack.py", line 120, in pack
    with FileUnpacker(src) as fu:
  File "/home/asuki/.local/lib/python3.8/site-packages/platformio/package/unpack.py", line 152, in __enter__
    self._archiver = self._init_archiver()
  File "/home/asuki/.local/lib/python3.8/site-packages/platformio/package/unpack.py", line 144, in _init_archiver
    with open(self.path, "rb") as fp:
FileNotFoundError: [Errno 2] No such file or directory: '1.0.0.zip'

============================================================

An unexpected error occurred. Further steps:

* Verify that you have the latest version of PlatformIO using
  `pip install -U platformio` command

* Try to find answer in FAQ Troubleshooting section
  https://docs.platformio.org/page/faq.html

* Report this problem to the developers
  https://github.com/platformio/platformio-core/issues

============================================================

What in theā€¦ ls returns the file name and you execute the command in the same terminal session right?

Hm the only other thing I could think of is if it requires an absolute path. Can you try

pio package publish --owner asukiaaa --released-at "2020-04-29 14:09:00" $PWD/1.0.0.zip

?

Thank you for the information.

I got other error with using $PWD for path.

pio package publish --owner asukiaaa --released-at "2020-04-29 14:09:00" $PWD/1.0.0.zip
Error: You do not have permission to set custom released date for a public package (library)

Iā€™m sure thad I have logged in.

pio account show

Profile
=======
Username:    asukiaaa
Email:       asukiaaa@gmail.com
First name:  Asuki
Last name:   Kono

Packages
========

Remote Development for Developer
--------------------------------
Forever Free Remote Development for an awesome PlatformIO Community
Expire:    -
Services:  100 Concurrent Remote Agents, 100 Shares per Remote Agent, Remote Unit Testing (100,000 sessions per month), Remote Serial Port Monitor (50,000 sessions per month), Remote Device Manager, Remote Firmware Updates (100,000 per month)

Trusted Registry for Developer
------------------------------
Forever Free Trusted Registry for an awesome PlatformIO Community
Expire:    -
Services:  Publish a public development platform (max. size 50MB), Unpublish a pushed package or version in 72h, Publish a public tool (framework, SDK, toolchain, upload and debug tools, etc.) (max. size 500MB), Automatic moderation for a public library, Publish a public library (max. size 50MB)

Do you know who has permission to specify released_at.

@ivankravets will need to clarify what is going on here.

I believe that the issue is that the error is misleading and the real issue is that you did not add the library to the registry, and is a ā€˜legacyā€™ library, hence the mention of ā€œpublic package (library)ā€. This is just a guess though, and if it is the case, I donā€™t know what the process of resolving it will be.

I would have thought it would changing things like released_at would have been fine if you are the owner of the library though.

Maybe try pio access list asukiaaa to see if it recognises that you are the library owner and have admin access to manage it? If I run that command, I get ā€œYou do not have any resources.ā€ so either that is indeed the issue, or it only works for that user.

e.g. I havenā€™t tried to do what you have done, but I get

pio access list pfeerick

elapsedMillis
-------------
URN:              prn:reg:pkg:1002:library
Owner:            pfeerick
Access level(s):  Admin
2 Likes

Thank you for the information.
I may have admin permission for utils_asukiaaa.
Do you think that I can specify released_at because I am admin of utils_asukiaaa.

pio access list asukiaaa

SomeSerial
----------
URN:              prn:reg:pkg:1274:library
Owner:            asukiaaa
Access level(s):  Admin

MPU9250_asukiaaa
----------------
URN:              prn:reg:pkg:1751:library
Owner:            asukiaaa
Access level(s):  Admin

AM2320_asukiaaa
---------------
URN:              prn:reg:pkg:5850:library
Owner:            asukiaaa
Access level(s):  Admin

EPD
---
URN:              prn:reg:pkg:6033:library
Owner:            asukiaaa
Access level(s):  Admin

ST7032_asukiaaa
---------------
URN:              prn:reg:pkg:6185:library
Owner:            asukiaaa
Access level(s):  Admin

BLVD20KM_asukiaaa
-----------------
URN:              prn:reg:pkg:6499:library
Owner:            asukiaaa
Access level(s):  Admin

ThingSpeak_asukiaaa
-------------------
URN:              prn:reg:pkg:6503:library
Owner:            asukiaaa
Access level(s):  Admin

WiredController_asukiaaa
------------------------
URN:              prn:reg:pkg:6564:library
Owner:            asukiaaa
Access level(s):  Admin

INA226_asukiaaa
---------------
URN:              prn:reg:pkg:6774:library
Owner:            asukiaaa
Access level(s):  Admin

AD5254_asukiaaa
---------------
URN:              prn:reg:pkg:6808:library
Owner:            asukiaaa
Access level(s):  Admin

I2cMotors_asukiaaa
------------------
URN:              prn:reg:pkg:7133:library
Owner:            asukiaaa
Access level(s):  Admin

utils_asukiaaa
--------------
URN:              prn:reg:pkg:7286:library
Owner:            asukiaaa
Access level(s):  Admin

I2cControlPanel_asukiaaa
------------------------
URN:              prn:reg:pkg:11105:library
Owner:            asukiaaa
Access level(s):  Admin

I2cMultipleMotors_asukiaaa
--------------------------
URN:              prn:reg:pkg:11182:library
Owner:            asukiaaa
Access level(s):  Admin

rs485_asukiaaa
--------------
URN:              prn:reg:pkg:11270:library
Owner:            asukiaaa
Access level(s):  Admin

button_asukiaaa
---------------
URN:              prn:reg:pkg:11271:library
Owner:            asukiaaa
Access level(s):  Admin

wire_asukiaaa
-------------
URN:              prn:reg:pkg:11277:library
Owner:            asukiaaa
Access level(s):  Admin

string_asukiaaa
---------------
URN:              prn:reg:pkg:11278:library
Owner:            asukiaaa
Access level(s):  Admin

Hmā€¦ I got nothingā€¦ I would have thought since it says you have admin access to that library it would workā€¦ :cry: Youā€™ll have to wait for Ivan to respond on that one, I canā€™t be of more help on that front.

I see.
Thank you for a lot of information.
I wait response.

1 Like

Yes, this option is available for super admins. We donā€™t allow users to use custom release date.

1 Like

I see, thank you for the information.