Path: csiph.com!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: =?UTF-8?Q?H=c3=a5vard_Flaget_Aasen?= <haavard_aasen@yahoo.no>
Newsgroups: linux.debian.maint.python
Subject: advice on jsonpickle
Date: Sun, 08 Dec 2019 20:00:02 +0100
Message-ID: <zb9WG-488-9@gated-at.bofh.it>
References: <zb9WG-488-11@gated-at.bofh.it>
Old-Return-Path: <haavard_aasen@yahoo.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Approved: robomod@news.nic.it
Lines: 26
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12127

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