This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Packaging of asciinema cli #141
Comments
|
/cc @swills |
|
The atom feed is enough for me. SourceForge used to be the place for mailing lists, but I think they've gone a bit evil now. We have a mailman server if you want to use that. |
|
The atom feed is enough for me too. |
|
Personally, I'd prefer an email of some kind, either mailing list or github issue email, either is fine. Thanks! |
|
I'd also prefer email notifications (to minimize update lag), but I'd be fine with the atom feed. |
|
I have just released 1.2.0 /cc @larryv @swills @Dr-Terrible @zanchey @jakubjedelsky |
|
@sickill Done! Thank you for the reminder. v1.2.0 tested with both Go1.4.x and Go1.5.x (Gentoo/Linux x86-64), and everything works as expected, with all the unit tests passing. Ebuild just pushed in my overlay: Dr-Terrible/go-overlay@4859682. |
|
@Dr-Terrible wow, that was quick! Thanks! |
|
@youtux thanks for updating Homebrew package! |
|
@sickill you are welcome. Also, I use sibbell.com to get updates via email every time a starred github project gets a new tag. |
|
I've updated the Ubuntu packages; sorry for the delay. |
|
@zanchey thanks! |
|
updated in MacPorts, only 3 months late 😓 |
|
@larryv no prob, thanks! |
|
We have a new release! This new 1.3 version is back on Python (read more about it here: http://blog.asciinema.org/post/and-now-for-something-completely-different/). Sorry if this adds you more work (switching build toolchain from Go to Python)! But I believe in the long run the packaging will be simpler, especially that as of this version we have zero external dependencies 💥 |
|
Sorry @sickill, I can't add a python package to my go overlay, so I'm forced to remove asciinema. Or at least, I'll keep and maintain the previous Golang implementations, but not the new ones in python (there are too many dependencies to wrangle). |
|
@Dr-Terrible ok. Maybe original portage package maintainers will be able to update the 0.9.8 ebuild to 1.3.0. Thanks! |
|
Updated in MacPorts. As you can see from that diff, switching back to Python made things rather easier for me. Thank you! 😄 |
|
@sickill I think so, but at the moment there is no maintainer for the ebuild, so it will take some time before asciinema will be properly added to the Portage tree. To speed up a little the process, I think I'm going to submit a proper ebuild (at least for v1.3.0) in the next days, if I'm not too busy doing other stuff. |
|
Love the change to python3, it's much more better to package it for me. Builds for Fedora 24,23 and EPEL 7 are prepared and will go to testing repos soon. |
|
Done in the Ubuntu PPA. Likewise, the packaging is significantly smaller now. |
|
i'm the maintainer for debian, I've recently subscribed to the blog, i'll subscribe to the releases atom feed. working on the 1.3.0 package, just a week latter i finished to work on go package, please don't switch language implementations again |
|
@gfa thanks for your work Gustavo. No worries, we are staying with Python for good. |
|
Finally updated to 1.3.0 in FreeBSD ports. Thanks for the heads up. |
|
@swills awesome, thanks! |
|
Hey there good people! We have a new release, 1.4.0 - https://pypi.python.org/pypi/asciinema/1.4.0 |
ku1ik
changed the title
|
@sickill cool, update is going to Fedora and EPEL 7 testing repos right now. It should be in stable in 7 (fedora) or 14 (epel) days. |
|
Uploaded, new builds pending - sorry for the wait! |
|
Hey! We have a new release, v2.0.0. https://github.com/asciinema/asciinema/releases/tag/v2.0.0 🎉🎉🎉 |
|
Congrats to v2, @sickill ! 🎉 I'm a little bit out of focusing to the asciinema development right now. Is the 2.0.0 version backward compatible with older releases (1.4.0)? I would like to push the update to current stables, but not sure if it won't break something. Thanks! |
|
@jakubjedelsky thanks! It uses new file format, so recordings created with this new version can't be played in the terminal with 1.4.0 and older. All recordings (old and new) can be played with 2.0 though, and also web player and asciinema-server have been updated a while ago to support asciicast v2 format. |
|
@sickill nice! Many thanks for these details 👍 |
|
2.0.0 committed to FreeBSD ports. |
|
@swills fantastic, thanks! |
|
I've added Ubuntu packages for the currently released versions. 2.0.0 was already in Bionic, which has a different tarball than the one I downloaded from Github. The upstream packaging can't be backported (requires new debhelper), so I've used the existing packaging with the upstream tarball. There's been a bit of a delay due to other pressures - sorry. If anyone would like to take over maintaining the Ubuntu PPA, I'm happy to hand it over! |
|
@zanchey asciinema is up to date in debian, any reason why is not being imported in ubuntu? |
|
It's up to date in testing and imported into bionic, which as you know are both unreleased, and so the PPA is for people wishing to use a new version of asciinema on an older version of Ubuntu (or Debian). |
|
Thank you @zanchey for you work on this! |
|
I've just released 2.0.1 ✨ https://pypi.org/project/asciinema/2.0.1/ There was a bug in 2.0 in config file handling code, which caused creation of the file at @zanchey do you think there's a chance for 2.0.1 to be included in final Bionic release? I see final beta freeze is tomorrow 😐 |
|
My packages don't get pulled into the official releases, but I'll try and get a 2.0.1 version uploaded today. |
|
Done. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Opening this issue to discuss the best way for package maintainers to be notified about new asciinema releases.
We could create a mailing list for this, or use https://github.com/asciinema/asciinema/releases.atom like @jakubjedelsky suggested (asciinema/asciinema#43 (comment)). Alternatively I could be reopening this issue and pinging you here in the comments whenever new release is out. Any other ideas and/or preferences?
/cc @jakubjedelsky @zanchey @Dr-Terrible @larryv
UPDATE: So I just keep this issue open and comment when there's new release. Package maintainers can subscribe to this issue to get notified.
The text was updated successfully, but these errors were encountered: