Regarding python-usb and #712206

2014-12-15 Thread Ruben Undheim
Hi everyone, I just realized that it might be better to ask on this mailing list. There are packages that depend on pyusb>1.0 that we would like to get into debian. There is also at least one example of a package already in the archive that bundles pyusb>1.0 as part of the package itself (quisk).

RFS: python-zeroconf/0.17.1-1 [ITP]

2015-05-25 Thread Ruben Undheim
tion about python-zeroconf can be obtained from https://github.com/jstasiak/python-zeroconf. Changes since the last upload: - Initial release Regards, Ruben Undheim -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trou

RFS: pychromecast/0.6+20150327git9d14219-1 [ITP]

2015-05-25 Thread Ruben Undheim
tion about python-zeroconf can be obtained from https://github.com/balloob/pychromecast . Changes since the last upload: - Initial release Regards, Ruben Undheim -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas

Uploading pyusb 1.0.0~b2 to unstable

2015-06-17 Thread Ruben Undheim
Hi, Could someone in the Python Modules Team help me get the version of pyusb in experimental uploaded to sid. I've prepared the package here: https://mentors.debian.net/package/pyusb It also contains python3-usb which people are waiting for. See: http://bugs.debian.org/787792 https:

Re: Uploading pyusb 1.0.0~b2 to unstable

2015-06-18 Thread Ruben Undheim
Hi, I've done the suggested changes and reuploaded to mentors. However, I'm not able to push to the svn repository. It's strange, I get "Authorization failed" even though I'm a member of the scm_python-modules alioth group. I've never used svn on alioth before, only git. I checked out the follow

Re: Uploading pyusb 1.0.0~b2 to unstable

2015-06-19 Thread Ruben Undheim
Hi again Vincent! I was able to push it to svn now. I tried again the same thing from a different computer. Thank you very much for helping me out. Regards Ruben -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lis

RFS: python-spur_0.3.14-2

2015-10-18 Thread Ruben Undheim
Package: sponsorship-request Severity: normal Dear mentors, Can someone sponsor an FTBFS-fix version of python-spur? It is maintained in the Python modules team and in the Vcs in git-dpm format: git://anonscm.debian.org/python-modules/packages/python-spur.git It closes #802158 with severity

Need help uploading Python3 version of pychromecast

2016-12-13 Thread Ruben Undheim
Dear fellow Python Modules Team members, I have prepared the Python3 binary package for pychromecast. (all dependencies are now in sid finally) Since I am a DM only, I cannot upload new binary packages. Can one of you help me out with this one-time upload, please? The package is checked in and

Add me to Salsa

2018-07-11 Thread Ruben Undheim
Hi, I was a member in this team on alioth, and I am maintaining these packages (in the team): - pychromecast - python-spur - python-zeroconf - pyusb - pyvisa - pyvisa-py Since I would like to push the updates to the GIT repository, I need access. Can you please add me to the team? My lo

Re: Add me to Salsa

2018-07-11 Thread Ruben Undheim
I just figured out that I accidentally registered with the username "rubund-guest-guest". Just FYI :D On Wed, Jul 11, 2018 at 12:22:36PM +0200, Ruben Undheim wrote: > Hi, > > I was a member in this team on alioth, and I am maintaining these packages > (in the te

Re: git-dpm -> gbp conversion (mass-change)

2018-08-04 Thread Ruben Undheim
Hi, > > 2/ Ondrej Novy will do a mass-change from git-dpm to gbp on team packages. > > Related to this, Piotr will review and amend the team policy if necessary, > > as > > well as work on the pipeline to make sure the policy gets published from > > salsa. Good initiative! The last upload of git-

Re: git-dpm -> gbp conversion (mass-change)

2018-08-08 Thread Ruben Undheim
Hi, > The problem with git-debrebase will be the same as with git-dpm. As soon > as you try to upgrade / merge a new upstream release, you dive into a > rebase/conflict nightmare. So in other words, you prefer to solve the same conflicts manually with quilt/quilt refresh or get similar but worse