Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #12127 > unrolled thread

advice on jsonpickle

Started byHåvard Flaget Aasen <haavard_aasen@yahoo.no>
First post2019-12-08 20:00 +0100
Last post2019-12-08 20:00 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  advice on jsonpickle Håvard Flaget Aasen <haavard_aasen@yahoo.no> - 2019-12-08 20:00 +0100

#12127 — advice on jsonpickle

FromHåvard Flaget Aasen <haavard_aasen@yahoo.no>
Date2019-12-08 20:00 +0100
Subjectadvice on jsonpickle
Message-ID<zb9WG-488-9@gated-at.bofh.it>
I had a look at jsonpickle.
Package: https://tracker.debian.org/pkg/jsonpickle

The latest release is missing from the repository, it is also FTBFS in 
sid https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946304

I forked the repo before i started, in case i broke something.
https://salsa.debian.org/haava-guest/jsonpickle

I imported the current .dsc file to get the repo up to date. Then i 
updated it to the newest upstream version and disabled the tests that 
failed (three of them). The package is now building properly.
The tests that failed, do already have a issue ticket upstream, from 
someone else.

Can someone take a quick look at my repo and see if it's ok to push it 
to the main one?

I did think about a merge request, but do I need several requests to get 
all branches and tags updated?

Should i let the bug ticket remain open until the tests has been fixed 
upstream, or is it enough that the package is being built again?


Håvard

[toc] | [standalone]


Back to top | Article view | linux.debian.maint.python


csiph-web