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.

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

Packaging of asciinema 2.0.2 #116

Open
sickill opened this issue Jun 30, 2015 · 49 comments
Open

Packaging of asciinema 2.0.2 #116

sickill opened this issue Jun 30, 2015 · 49 comments

Comments

@sickill
Copy link
Contributor

@sickill sickill commented Jun 30, 2015

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 (#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.

@sickill
Copy link
Contributor Author

@sickill sickill commented Jun 30, 2015

/cc @swills

@zanchey
Copy link

@zanchey zanchey commented Jun 30, 2015

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.

@Dr-Terrible
Copy link

@Dr-Terrible Dr-Terrible commented Jun 30, 2015

The atom feed is enough for me too.
If by any chance I miss a release and users are complaining, feel free to poke me via GitHub's issues through my Gentoo overlay.

@swills
Copy link
Contributor

@swills swills commented Jun 30, 2015

Personally, I'd prefer an email of some kind, either mailing list or github issue email, either is fine. Thanks!

@larryv
Copy link

@larryv larryv commented Jul 1, 2015

I'd also prefer email notifications (to minimize update lag), but I'd be fine with the atom feed.

@sickill
Copy link
Contributor Author

@sickill sickill commented Feb 22, 2016

I have just released 1.2.0 /cc @larryv @swills @Dr-Terrible @zanchey @jakubjedelsky

@Dr-Terrible
Copy link

@Dr-Terrible Dr-Terrible commented Feb 22, 2016

@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.

@sickill
Copy link
Contributor Author

@sickill sickill commented Feb 22, 2016

@Dr-Terrible wow, that was quick! Thanks!

@sickill
Copy link
Contributor Author

@sickill sickill commented Mar 2, 2016

@youtux thanks for updating Homebrew package!

@youtux
Copy link

@youtux youtux commented Mar 2, 2016

@sickill you are welcome. Also, I use sibbell.com to get updates via email every time a starred github project gets a new tag.

@zanchey
Copy link

@zanchey zanchey commented Mar 6, 2016

I've updated the Ubuntu packages; sorry for the delay.

@sickill
Copy link
Contributor Author

@sickill sickill commented Mar 6, 2016

@zanchey thanks!

@larryv
Copy link

@larryv larryv commented May 14, 2016

updated in MacPorts, only 3 months late 😓

@sickill
Copy link
Contributor Author

@sickill sickill commented May 14, 2016

@larryv no prob, thanks!

@sickill
Copy link
Contributor Author

@sickill sickill commented Jul 13, 2016

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 💥

@youtux youtux mentioned this issue Jul 13, 2016
3 of 4 tasks complete
@Dr-Terrible
Copy link

@Dr-Terrible Dr-Terrible commented Jul 15, 2016

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).

@sickill
Copy link
Contributor Author

@sickill sickill commented Jul 15, 2016

@Dr-Terrible ok. Maybe original portage package maintainers will be able to update the 0.9.8 ebuild to 1.3.0. Thanks!

@larryv
Copy link

@larryv larryv commented Jul 15, 2016

Updated in MacPorts. As you can see from that diff, switching back to Python made things rather easier for me. Thank you! 😄

@Dr-Terrible
Copy link

@Dr-Terrible Dr-Terrible commented Jul 16, 2016

@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.

@jakubjedelsky
Copy link
Contributor

@jakubjedelsky jakubjedelsky commented Jul 16, 2016

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.

@zanchey
Copy link

@zanchey zanchey commented Jul 17, 2016

Done in the Ubuntu PPA. Likewise, the packaging is significantly smaller now.

@gfa
Copy link

@gfa gfa commented Jul 29, 2016

i'm the maintainer for debian, I've recently subscribed to the blog, i'll subscribe to the releases atom feed.
I prefer email but i run a rss-> email gateway so is the same for me

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

@sickill
Copy link
Contributor Author

@sickill sickill commented Jul 30, 2016

@gfa thanks for your work Gustavo. No worries, we are staying with Python for good.

@swills
Copy link
Contributor

@swills swills commented Aug 2, 2016

Finally updated to 1.3.0 in FreeBSD ports. Thanks for the heads up.

@sickill
Copy link
Contributor Author

@sickill sickill commented Aug 2, 2016

@swills awesome, thanks!

@sickill
Copy link
Contributor Author

@sickill sickill commented Apr 11, 2017

Hey there good people! We have a new release, 1.4.0 - https://pypi.python.org/pypi/asciinema/1.4.0

@sickill sickill changed the title Notifying package maintainers about new releases Packaging of asciinema 1.4.0 Apr 11, 2017
@jakubjedelsky
Copy link
Contributor

@jakubjedelsky jakubjedelsky commented Apr 12, 2017

@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.

@sickill sickill added the help wanted label Apr 24, 2017
@zanchey
Copy link

@zanchey zanchey commented Apr 28, 2017

Uploaded, new builds pending - sorry for the wait!

@sickill sickill changed the title Packaging of asciinema 1.4.0 Packaging of asciinema 2.0.0 Feb 10, 2018
@sickill
Copy link
Contributor Author

@sickill sickill commented Feb 10, 2018

@jakubjedelsky
Copy link
Contributor

@jakubjedelsky jakubjedelsky commented Feb 12, 2018

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!

@sickill
Copy link
Contributor Author

@sickill sickill commented Feb 12, 2018

@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.

@jakubjedelsky
Copy link
Contributor

@jakubjedelsky jakubjedelsky commented Feb 12, 2018

@sickill nice! Many thanks for these details 👍

@swills
Copy link
Contributor

@swills swills commented Feb 16, 2018

2.0.0 committed to FreeBSD ports.

@sickill
Copy link
Contributor Author

@sickill sickill commented Feb 16, 2018

@swills fantastic, thanks!

@zanchey
Copy link

@zanchey zanchey commented Feb 25, 2018

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!

@gfa
Copy link

@gfa gfa commented Feb 25, 2018

@zanchey asciinema is up to date in debian, any reason why is not being imported in ubuntu?

@zanchey
Copy link

@zanchey zanchey commented Feb 25, 2018

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).

@sickill
Copy link
Contributor Author

@sickill sickill commented Feb 26, 2018

Thank you @zanchey for you work on this!

@sickill sickill changed the title Packaging of asciinema 2.0.0 Packaging of asciinema 2.0.1 Apr 4, 2018
@sickill
Copy link
Contributor Author

@sickill sickill commented Apr 4, 2018

I've just released 2.0.1

https://pypi.org/project/asciinema/2.0.1/
https://github.com/asciinema/asciinema/releases/tag/v2.0.1

There was a bug in 2.0 in config file handling code, which caused creation of the file at ~/.asciinema/config instead of ~/.config/asciinema/config. This releases fixes that.

@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 😐

@zanchey
Copy link

@zanchey zanchey commented Apr 4, 2018

My packages don't get pulled into the official releases, but I'll try and get a 2.0.1 version uploaded today.

@zanchey
Copy link

@zanchey zanchey commented Apr 6, 2018

Done.

@sickill
Copy link
Contributor Author

@sickill sickill commented Apr 6, 2018

@zanchey great, thx!

@just4t
Copy link

@just4t just4t commented Jul 8, 2018

Started today with asciinema ... First of all, thanks a lot for the tool and service.
Installed as snap app. in Linux Mint 19c desktop and over an Ubuntu 18.04 LTS powered cloud server and looks it works perfectly, but ...

  • Just noticed the installed version via snapd app. is the 1.4 and not a latest 2.0.1+ ... !?

  • Have you plans to release the asciinema 2.0.1+ snap app. package soon?

@sickill
Copy link
Contributor Author

@sickill sickill commented Jul 8, 2018

@flexiondotorg any chance you could update snap to 2.0.1?

@sickill
Copy link
Contributor Author

@sickill sickill commented Sep 10, 2018

I have temporarily removed snap installation option. It doesn't seem anyone is maintaining it anymore.

@sickill sickill changed the title Packaging of asciinema 2.0.1 Packaging of asciinema 2.0.2 Apr 28, 2019
@sickill
Copy link
Contributor Author

@sickill sickill commented Apr 28, 2019

It seems Ubuntu 18.04 has asciinema 2.0.0 (https://packages.ubuntu.com/bionic/asciinema) and 19.04 has 2.0.2 (https://packages.ubuntu.com/disco/asciinema). Any chance you can update your ppa @zanchey to 2.0.2 for those on older Ubuntu and Debian versions?

@zanchey
Copy link

@zanchey zanchey commented May 14, 2019

Done! I ended up reusing my packaging metadata, rather than copying from 19.04, as the debhelper requirements are too high for the backport to work easily.

@sickill
Copy link
Contributor Author

@sickill sickill commented May 14, 2019

@zanchey great! Thank you 🏆

@om26er
Copy link

@om26er om26er commented Jan 10, 2020

@sickill since I have been the maintainer of the snap package, I think it would make sense to bring back the snap installation instructions, probably elevated as "recommended" for Linux based systems. I had created an issue #382 before I came here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
10 participants
You can’t perform that action at this time.