Re: #930780 ITS: pssh
Am 04.04.2020 um 09:46 teilte Jochen Sprickerhof mit: Hi Jochen, Sorry, late response! >>> * update to the latest upstream release (check #891340 or even >>> https://github.com/ParallelSSH/parallel-ssh ?) >>> >> Yes one has to do that. > > parallel-ssh seems to be a Python library and different code base, so I > would rather go with the Github fork mentioned in #891340. But there are > no new releases, so it's probably easiest to pull in the patches via > debian/patches. There is a discussion to make it upstream, so I would > propose to ask for a release after that is cleared: > > https://github.com/lilydjwg/pssh/issues/110#issuecomment-580609871 > >>> * upload to debian. >>> >> Well, probably. I'd need a sponsor for initial upload as I'm just a DM. > > I'm happy to sponsor and help maintain as well. > > Do you have time later today or tomorrow to work on it together? > Otherwise I will go ahead and do some cleanup. My hope would be to get a > fixed version into unstable by the end of the weekend. > So, you did all the work already I was expected to do. Many thanks! I'll try to continue working. Hilmar -- signature.asc Description: OpenPGP digital signature
Re: ITS: pssh
Am 14.03.2020 um 01:29 teilte Sandro Tosi mit: > On Thu, 20 Jun 2019 06:24:13 -0700 Mo Zhou wrote: >> I plan to salvage pssh and fix at least the following bug: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891340 > > Not sure if Mo is still interested in salvaging this package, other > wise this could be a nice project for someone willing to improve their > packaging skills. this would translate to: > > * bring it under PAPT maintenance > Is there more to do than creating a source package, adding a new package below the PAPT group and import the source package into it? > * update to the latest upstream release (check #891340 or even > https://github.com/ParallelSSH/parallel-ssh ?) > Yes one has to do that. > * drop python2 support, add python3 support > Has been done in upstream in one of the later commits. > * upload to debian. > Well, probably. I'd need a sponsor for initial upload as I'm just a DM. H. -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Re: [Debian PAPT] Question about salsa repo and packaging
On 16.09.2018 07:32, Sergio Durigan Junior wrote: > On Saturday, September 15 2018, Hilmar Preuße wrote: Hi, >> I'm maintaining the package rubber in the PAPT. I have a few question: >> >> 1. I'd like to revert some changes to the salsa repo for my package, as >> these changes were never uploaded to Debian and are not superseded by >> new upstream package. Is it OK to do a "git reset --hard " to make >> them disappear in my repository? > > You mean do a "git reset --hard" locally and then "git push" the > modified history? This is not ideal, but if you're the only one using > the repository, and if there was no Debian release containing the code > you're reverting, then I'd say it's OK. > I now deciced to use revert and it is OK for me. Thanks for the hint! >> 3. Recently I imported a new upstream version. According to [1] I should >> rebase my patches. Unfortunately this fails: >> >> Could anybody give me a hint, what it wrong here? > > While rebasing the patch-queue, there was a conflict with one of the > files. A conflict happens when you have two distinct versions of the > same file containing modifications that are not trivial to be > automatically merged by git. The conflict is marked above as: > > CONFLICT (content): Merge conflict in src/depend.py > > You now have to resolve this conflict before proceeding. Basically, > open the file and look for the conflict markers, which look like: > For any reason the phenomenon is gone now. One of my patches was updated, during rebase. Hilmar -- sigfault #206401 http://counter.li.org
[Debian PAPT] Question about salsa repo and packaging
Hi, I'm maintaining the package rubber in the PAPT. I have a few question: 1. I'd like to revert some changes to the salsa repo for my package, as these changes were never uploaded to Debian and are not superseded by new upstream package. Is it OK to do a "git reset --hard " to make them disappear in my repository? 2. My repo contains a stale branch called "svn". It was created during the git -> salsa migration. AFAICT this branch contains obsolete versions of some files. May I kill that branch? 3. Recently I imported a new upstream version. According to [1] I should rebase my patches. Unfortunately this fails: hille@sid:~/devel/rubber/rubber.git $ gbp pq rebase gbp:info: Switching to 'patch-queue/debian/master' First, rewinding head to replay your work on top of it... Applying: more accurate log messages when deciding whether to rebuild some file Using index info to reconstruct a base tree... M src/depend.py Falling back to patching base and 3-way merge... Auto-merging src/depend.py CONFLICT (content): Merge conflict in src/depend.py error: Failed to merge in the changes. Patch failed at 0001 more accurate log messages when deciding whether to rebuild some file hint: Use 'git am --show-current-patch' to see the failed patch Resolve all conflicts manually, mark them as resolved with "git add/rm ", then run "git rebase --continue". You can instead skip this commit: run "git rebase --skip". To abort and get back to the state before "git rebase", run "git rebase --abort". gbp:error: Couldn't run git rebase: it exited with 128 Could anybody give me a hint, what it wrong here? Many thanks! Hilmar [1] https://wiki.debian.org/Python/GitPackaging#New_upstream_release -- sigfault #206401 http://counter.li.org
Re: Bug#903438: RFA: asciinema -- Record and share your terminal sessions, the right way
Am 18.07.2018 um 21:55 teilte gustavo panizzo mit: Hi Gustavo, Forget screen recording apps and blurry video. Enjoy a lightweight, purely text based approach to terminal recording. This package provides a command line recorder for asciinema.org service or other instance of asciinema server. At first the dumb question: what main features does this application have, I can't find in script [1]? Well, except the upload feature. Thanks! H. [1] http://man.openbsd.org/script.1 -- #206401 http://counter.li.org
