Brilliant, thanks Andreas.

I did actually see that reportbug was available on ubuntu but I wasn't sure if 
that was a separate system for ubuntu-specific bugs that just used the same 
name. 


thanks again
Jon

—
Jon Peirce


Open Science Tools Ltd
Creators of PsychoPy and Pavlovia.org
Twitter | Facebook | Youtube (PsychoPy)

--- original message ---
On May 5, 2021, 3:05 PM GMT+1 [email protected] wrote:

Hi Jon,

On Wed, May 05, 2021 at 01:32:21PM +0000, Jon Peirce wrote:

>> OK, thanks both. I'll use the [email protected] email from here on 
>> and I'll do my best to get reportbug running on a VM.


> I never used Ubuntu but I have heard that there is a way to report bugs

> right to Debian from a running Ubuntu machine. This link looks a bit

> aged but it was top ranking in my web search:


> https://help.ubuntu.com/community/reportbug


>> Oh, and is there a page somewhere to check on the release schedules (like 
>> freeze dates)? Maybe I can leave myself a note to check in with you at more 
>> appropriate times 


> This page names freeze dates:


> https://release.debian.org/bullseye/freeze_policy.html


> The release date (after which we can start uploading new versions again)

> is not yet fixed. Here is the latest information about the status


> https://lists.debian.org/debian-devel-announce/2021/05/msg00000.html


>> thanks


> Thanks to you for your cooperation


> Andreas.



>> —

>> Jon Peirce

>> 

>> 

>> Open Science Tools Ltd

>> Creators of PsychoPy and Pavlovia.org

>> Twitter | Facebook | Youtube (PsychoPy)

>> 

>> --- original message ---

>> On May 3, 2021, 9:17 PM GMT+1 [email protected] wrote:

>> 

>> On 03/05/21 09:44 PM, Andreas Tille wrote:

>> 

>> >> Hi Jon,

>> 

>> >> 

>> 

>> >> On Mon, May 03, 2021 at 07:28:39PM +0000, Jon Peirce wrote:

>> 

>> >> > Thanks for your help providing PsychoPy as a package via Debian Med.

>> 

>> >> 

>> 

>> >> Thanks in return for your very helpful comments.

>> 

>> >> 

>> 

>> >> For the next stable release (bullseye) we can't do anything anymore

>> 

>> >> since we are in deep freeze. However, your very detailed hints are a

>> 

>> >> very nice and structured todo list. We should make sure that we will

>> 

>> >> not loose this out of focus and thus it would be very valuable if you

>> 

>> >> would consider filing a bug report instead of a mail to some (not

>> 

>> >> really) random team members. So if you would be so kind to simply

>> 

>> >> (I know its not considered simple) fire up

>> 

>> >> 

>> 

>> >> reportbug python3-psychopy

>> 

>> >> 

>> 

>> >> and simply copy your mail into the editor interface of reportbug.

>> 

>> >> 

>> 

>> >> This would ensure we will not simply forget to work on the package.

>> 

>> 

>> > +1

>> 

>> 

>> >> > I've been doing a fair bit of packaging and installing work recently as 
>> >> > we move our test suite from Travis to GH Actions and I noticed the last 
>> >> > version wasn't quite sufficient to fully install on a clean ubuntu VM. 
>> >> > There was relatively little work to get it there (as listed below) but 
>> >> > I wonder if we can get that added to your packaging flow.

>> 

>> >> > 

>> 

>> >> > 

>> 

>> >> > Some of the things were missing python packages that could be fetched 
>> >> > with pip. The trickiest is the wxPython package - it seems you had 
>> >> > provided a wxPython package as part of the installation but I think it 
>> >> > didn't have all the dylibs it needed. I was able to fix that on this 
>> >> > version of python/ubuntu by installing forcing a new install of a wheel 
>> >> > as below. Wheels aren't available for all *nix versions though so 
>> >> > building is the right thing to do. I think I have a setup on GitHub 
>> >> > that reliably builds it now so I can probably help there.

>> 

>> >> > 

>> 

>> >> > 

>> 

>> >> > For info about our releases, we've recently pushed out our 4th bug-fix 
>> >> > release of the current series (2021.1.4) which is the current 
>> >> > recommended version, and we're now working towards our next major 
>> >> > feature release in June.

>> 

>> 

>> > Thanks a lot for all your work there!

>> 

>> 

>> >> > 

>> 

>> >> > By the way, is there a preferred way I should contact you guys 

>> 

>> 

>> > Yes, it'd be best if you could contact us at the mailing list: 
>> > [email protected]

>> 

>> > We all read it and there are several people doing packaging actively

>> 

>> > there who would be able to chime in as well.

>> 

>> > You can subscribe to the list here if you'd like: 
>> > https://lists.debian.org/debian-med/

>> 

>> 

>> >> > (I see there's a mailing list called Debian-med-packaging?) 

>> 

>> 

>> > Not many people are subscribed to -packaging mailing list due to low

>> 

>> > signal to noise ratio, at least I'm not. The list I mentioned above works 
>> > best.

>> 

>> 

>> >> > Let me know if there's anything else I can do to help

>> 

>> 

>> > It's really helpful that you are testing the package at your end.

>> 

>> 

>> > Thanks a lot,

>> 

>> > Nilesh

>> --- end of original message ---


> -- 

> http://fam-tille.de
--- end of original message ---

Reply via email to