Just done some reviewing/tweaking. I've pushed the following changes to the git
repo, please
tell me if you have any objections.
I added a gpb.conf to make git-buildpackage actually use pristine tar and hence
result in an orig
tarball that was consistent with what is already in Ubuntu.
I found
I notice after removal from unstable tortoisehg is back in new.
However it seems that the package still build-depends on python 2 packages. In
particular it depends on python-pyqt5.qsci which has been dropped by the
qscintilla2 source package and decrufted from bullseye/sid.
It seems to me tha
On 05/01/19 12:03, peter green wrote:
I would therefore propose for now packaging only the client components of
pigpio in Debian. What do others think?
I have gone ahead and done this and uploaded to NEW.
On 18/10/18 20:36, peter green wrote:
Hi
I have been looking at getting pigpio into Debian.
Time for an update
Upstream accepted a pull request to give the libraries proper sonames.
I then added raspberry pi detection code.
I then decided to test if pigpio could be used on a Debian arm64
Hi
I have been looking at getting pigpio into Debian. I will probablly start from
the raspberry pi foundation's deb packaging and try to improve it to meet
Debian standards.
Firstly there seem to be a number of components to pigpio, I understand they
fit together as follows. Please tell me if
I have chatted with Dave Jones (waveform80) about getting gpiozero support on
more architectures. It seems sensible that as part of doing this we also
package pigpio to support remote gpio operations.
Dominik do you mind if I add myself to the uploaders for this package and work
on updating it
I took a look at packaging this a few months ago and raised the following
points, some of these points may have been obsoleted and some I have added
additional comments where appropriate.
1. The current packaging uses 3.0 (native), that is probably fine for snapshot
builds distributed by yours
After a discussion in #debian-python, it appeared to make sense to
package this and patch it so its where() function returns the location
where Debian is already providing CA certificates. This will be easier
than having to patch every python package that depends on certifi.
If you do that please
ssh-cron acts like cron, but is provided with ssh passphrases allowing
its commands to access remote systems without requiring a passphrase
to be stored in a clear-text file or resorting to ssh keys without
passphrases.
How is it provided with them? is the user required to enter them on
s
Due to insufficient rights for uploading csv2latex to
ftp-master i would like a kind mentor to review and
eventually upload csv2latex-0.18-3 (just a deb-related
fix, not upstream). I now maintain both upstream and
debian package on https://svn.gtmp.org/svn/csv2latex/
The dsc and tarballs are temp
While working on cleaning things up in raspbian I took a look at the
bustle package in debian.
Currently it is uninstallable on all architectures and furthermore it's
build-depends are uninstallable on kfreebsd. The package does appear to
build successfully on current sid amd64 linux.
Accord
> DEB:http://www.webmin.com/download/deb/webmin_1.340_all.deb
> DSC:http://download.webmin.com/download/deb/webmin_1.340.dsc
> Diff: http://download.webmin.com/download/deb/webmin_1.340.diff
> Source: http://www.webmin.com/download/webmin-1.340.tar.gz
well dpkg-source didn't seem to like
>DEB package: http://download.webmin.com/devel/deb/webmin_1.306_all.deb
>DSC file:http://download.webmin.com/devel/deb/webmin_1.306.dsc
>Original source: http://download.webmin.com/devel/tarballs/webmin-1.306.tar.gz
>Diff:http://download.webmin.com/devel/deb/webmin_1.306.dif
13 matches
Mail list logo
