control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "cdist"
>
>* Package name: cdist
> Version : 4.2.2-1
EALREADYINUNSTABLE.
G.
Hi,
>Gianfranco, i've uploaded version 1.3.0-1 to mentors, would you sponsor it?
>
>https://mentors.debian.net/debian/pool/main/a/asciinema/asciinema_1.3.0-1.dsc
uploaded with one change:
Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/asciinema.git
^^ this is the updated Vcs field,
Hi,
>still works for this pkg, i verified it. for consistency i will keep the
>change on the next upload
it works *again*, because somebody should have implemented some rewriterule
in the server, that changes gitweb to cgit (as you can see, the link is changed
into the cgit one).
I have to say
control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "pylucene"
I'm willing to sponsor this, but I have some questions/showstoppers:
1) licenses: some licenses are BSD, and there are some missing copyrights.
please add them (grep -Ri license and grep -Ri c
Hi,
>Now (new version) actually uses liblucene4.10-java from Debian both as
>Build-Depends and runtime dependency.
>And that's actually why I've added more Build-Depends.
>
>lucene-java-4.10.1 is just there because it's in upstream tarball.
>I was trying to avoid repackaging of upstream tarball
hi,
>I am looking for a sponsor for my package "palp"
it's in.
G.
control: owner -1 !
control: tags -1 moreinfo
Hi,
> I am looking for a sponsor for my package "node-es6-module-transpiler"
EMISSINGRUNTIMEDEPS.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802530
G.
Hi,
> I am looking for a sponsor for my package "node-ast-util"
on my way
G.
control: owner -1 !
control: tags -1 moreinfo
> I am looking for a sponsor for my package "vim-lastplace"
1) please use for debian copyright the same license as upstream if possible
(this makes easier to forward patches)
2) I'm not sure about the directories and installation path
│ ├── vim
Hi,
>Is it worth keeping a patch downstream for such a trivial fix?
I don't think it is worth a patch, lets keep patches for real bugs :)
G.
Hi,
>I would like to create 3 packages for the core part: lib (for the shared
>library object), dev (for headers), and doc (for documentation generated by
>doxygen).
maybe two binaries? I guess you need one package for each repo.
e.g.
git1 providing the lib and headers
git2 providing the core
>I'm not sure I follow. Three binary packages (lib, dev, doc) is fairly
>standard for a shared library package. I would expect each git repo to
>be a separate source package, unless they are very tightly coupled together.
that was what I meant :)
the doc can be the doxygen for the library, or so
Hi,
>yes, but it seems still sometime wrong
it is good, just called "3.0.2-2"
please use -1 as versioning and dput -f on mentors until it gets accepted.
>we should be near :)
last thing: how do I enable such extension?
G.
Hi,
>Ah ok, sorry. :-) I removed the package and uploaded it again as 3.0.2-1 .
usually there is no need to remove the package on mentors
>In the vim-policy[1] by the vim package team they recommend to use
>vim-addon-manager. That means, install the debian package
>vim-addon-manager (which is
Hi,
>* Packaging fix: unowned directory after purge (Closes: #832347).
>
>PS: Would be thankful for any hints if my solution also written
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832347 is not the best or
>not really Debianic.
It seems fine, maybe you might have introduced some pos
control: owner -1 !
control: tags -1 moreinfo
Hi
>I am looking for a sponsor for this updated backport of btrfs-progs.
I see some other changes other than the no-change bpo
-Depends: btrfs-progs, ${misc:Depends}, ${shlibs:Depends}
+Depends: btrfs-progs (= ${binary:Version}), ${misc:Depends
Hi,
>I am looking for a sponsor for my package "nfft"
done!
G.
Hi,
>Oh man, I'd completely forgotten I'd made those modifications to my
>tree! I never got a definitive answer to the discussion on the
>following debian-backports thread. Could you please take a look at it
>and let me know if I should a) keep these modifications b) drop them
>c) change the
Hi
>I agree. Something known to be >buggy shouldn't be uploaded >anywhere
>other than maybe experimental. When >I talked about low priority in my
>previous e-mail, I meant to refer to >disruptive and major changes as you
>describe. Thanks!
I would say *everything* is buggy by definition. The dec
control: owner -1 !
control: tags -1 moreinfo
Hi,
> I am looking for a sponsor for my package "nbconvert"
I admit you already have a Python packaging knowledge higher than mine :)
It has been a long time since my last nitpick, and this time I found one!
hurray!
:)
1) why aren't you build
control: close -1
control: close 833373
sponsoring them.
g.
Hi,
>That's not surprising : the bot takes the ipython in unstable and not the one
>in experimental! Notice that the dep on ipython is indirect, so
>I don't know which package needs a versioned dep :-/
I would wild guess:
reverse-depends -r experimental -b ipython
Reverse-Build-Depends-Indep
Hi,
> I am looking for a sponsor for my package "9wm"
sponsored.
G.
control: owner -1 !
control: block -1 826704
control: block -1 826705
control: tags -1 moreinfo
> This package is the very core part of "Torch", a
> state-of-the-art machine learning framework.
> Note, this package requires luajit from experimental,
> and the basic functionality seems to be w
control: owner -1 !
control: tags -1 moreinfo
control: block -1 by 826715
please ping back when rundime-deps are in the archive
also you have some lintian issues
X: lua-torch-xlua: package-contains-no-arch-dependent-filesI: lua-torch-xlua:
extended-description-is-probably-too-short
G.
control: owner -1 !
control: tags -1 moreinfo
control: block -1 by 826715
please ping back when dependencies are in the archive
G.
Hi,
>The description specially ask NOT to attempt to "fix" this.
This is something that the maintainer should be aware of, even if
there is no fix.
The point is that the maintainer is expected to be able to read the tag
and know the possible issues by this warning
>I see that this tag draws too
control: owner -1 !
control: tags -1 moreinfo
control: block -1 by 826715
some questions:
why do not build-depend on the dev package?
I'm talking about "lua-torch-torch7"
also, there is some sadness in the libreadline.so link, are you sure there is
no better way to fix that?
what about a pack
Hi,
>Could you please upload an updated version of the package where I've increased
>GAMMARAY_LAUNCHER_TIMEOUT and see if it makes the build pass?
>
> https://mentors.debian.net/debian/pool/main/g/gammaray/gammaray_2.5.1-2.dsc
done
G.
Hi,
>However, I will wait for an answer from the Yubico people before adding
>myself as an Uploader and making the Vcs-* links point to Alioth.
wonderful, thanks for the nice work!
G.
On Tue, Aug 02, 2016 at 04:44:43PM +, Gianfranco Costamagna wrote:
> Hi,
>
> >
>changed the target release to experimental,
>require 'luajit >= 2.1' as B-D.
fails
http://debomatic-amd64.debian.net/distribution#experimental/lua-torch-torch7/0~20160803-g17ff317-1/buildlog
sbuild-build-depends-lua-torch-torch7-dummy : Depends: luajit (>= 2.1.0~beta2)
but it is not going to
Hi,
>Sorry for this late replay, I've been working on your advices and meanwhile
>packaging a new released version (4.6.4).
>You'll see in this new version I had to repack upstream sources to make the
>package DFSG compliant. Oliver did it with a script (prep.sh); I've used uscan
>and >excludin
control: owner -1 !
control: tags -1 moreinfo
>to wheezy-backports-sloppy as a first step to backporting other
1) really? what about don't care to wheezy anymore?
Did you get in touch with the maintainers? they seems active, one of them
is a DM, and might be able to upload it for you if needed
Hi,
>I've checked MACS2/IO/PeakIO.pyx and I think the typing of the function
>call should be fine - so probably the problem is somewhere else - but
>where?
I don't have the answer, but upstream seems to be aware of a new bug report
https://github.com/taoliu/MACS/issues/140
what I'm really not su
Hi,
>this version was a source only upload. If I build on my local machine
>emboss-data does not contain any dir /usr/share/man. However, the
>binary package on the Debian mirror contains /usr/share/man/man1 with
>has two symlinks which are identical to those in the emboss package.
seems you
Hi,
>This is due to, actually "trepl" doesn't B-D on the "lua-torch-torch7-dev"
>package. It is a runtime dependency. I'll leave a comment there.
>Keeping this runtime B-D there because it declares explicit dependency
>relationship.
oh, ok
>I've thought about spliting it up -- inspece verbose d
Hi,
Il Sabato 13 Agosto 2016 14:18, Lumin ha scritto:
>Please sponsor, thanks.
X: lua-torch-nn: package-contains-no-arch-dependent-files
and also, why are you installing files ending with ".c" in usr/include?
G.
Hi,
> I am looking for a sponsor for my package "phatch"
> Changes since the last upload:
>
> * Non-maintainer upload.
> * debian/patches:
> + Add fix-loading.patch to fix load with latest version of
>python-imaging
>and python-pil. (Closes: #811184, LP: #1567827)
this looks good t
control: tags -1 moreinf
Hi,
>* Initial release (Closes: #739035)
lets try a review:
1) std-version is 3.9.8 now
2) debhelper (>= 9), libncurses5-dev (>= 5.9),
unzip (>= 6.0), libsdl2-dev (>= 2.0.2), libsdl1.2-dev (>= 1.2.15),
gcc (>= 4:4.9)
do you really need both sdl1.2 and sdl2?
do y
Hi,
>The original uploader removed himself from uploaders. The maintaining
>team (in CC) didn't respond to my mail [pkg-telepathy-maintainers] in
>the last 2,5 weeks.
sorry for coming late (and thanks Paul for sponsoring it).
As already said, that team needs some care and new blood.
e.g. for thi
control: owner -1 !
control: tags -1 moreinfo
Hi,
(chances are higher when a bug is opened)
>Changes since the last upload:
>
>iptables-persistent (1.0.4+nmu1) unstable; urgency=low
>
> * Non-maintainer upload.
> * Loads the firewall before network-pre.target, as suggested by systemd
>u
control: tags -1 moreinfo
>This should also be reverted:
>https://github.com/hrydgard/ppsspp/commit/e81fa01bf0f5e75c6ab16ca1d525dc73e36bcf62
>
>The entire ffmpeg situation was a temporary hack back then - the above
>should have never been comitted.
and please remove moreinfo tag once the package
Hi,
Hi Gustavo
>My bad, I based my work of the master branch of the git repo. I'll start
>again using the released tag (and apply the same chages to the master)
not needed.
they are changes done by the maintainer, so all you need to do is list them in
changelog
[ Person1 ]
* fix bump
* patch
control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "cdist"
fix copyright and try again.
G.
Hi,
>RFS asn1c/0.9.27+dfsg-1 -- ASN.1 compiler for C
ok, done!
G.
Hi,
> Yes, I know that usage of an own license is discouraged due to the
>many issues that may arise. However I do certainly have a point in
>creating this license as I wanna keep the right to re-license which is
>not included by GPL.
I don't want to start a new thread, because I really t
(dropping people who reads mentors)
> Yes, that is a good point and it certainly proves that GPL would work
>in this regard; but what about the other two issues:
I guess so
> Now this is an additional restriction: you need to provide everything
>that is necessary to run your software und
control: owner -1 !
control: tags -1 moreinfo
>bcron
>
> * Use `dh-text' to avoid duplication in `debian/control'
ERR.
G.
Hi,
>04_tools.patch is updated. It's really hard to find a good replacement
>for the fonts... fonts-droid was dropped and noto is not really the
>replacement for it
and fonts-droid-fallback from fonts-android?
G.
control: block -1 by 834313
>perror? I filed RFS for dh-text, and it received neutral-to-positive
>reviews.
yes, but this bug needs the other one to be fixed, or the dh-text
need reverted.
>Please, not not upload yet. I plan to finally understand piuparts
>and check with it too.
this would b
Hi
sorry for stepping in :)
> - added autotools-dev to build-depends.
> - added dh_autotools-dev_updateconfig and
> dh_autotools-dev_restoreconfig to fix FTBFS on new architectures
> such as ppc64el. Closes: #759453, #535842
what about using autoreconf? it should fix the issue
Hi,
>I am looking for a sponsor for my updated backport of "btrfs-progs"
can you please prepare a backport of 4.7.1 instead?
I can upload it on deferred/5, to see it go in testing in the meanwhile.
G.
control: owner -1 !
control: tags -1 moreinfo
(ccing people who expressed interest in this update)
> I am looking for a sponsor for the package "backbone"
here we are, but I have some questions/issues:
1) why did you drop so much build-dependencies?
2) missing copyrights/licenses:
* @licens
Hi Jonas!
>Do you intend to help maintain the package collaboratively, or take over
>maintenance?
I see a team upload, so I guess the former of course
>If the former, then you should coordinate your work with current
>maintainers (fine that you seek help and guidance from others too, but
>don
(dropping the cc list from my next email, please follow #835658 if you care
about the thread)
>Don't take for granted that what you find obvious is equally obvious to
>others. Especially when raised as an explicit question: Makes you seem
>like taking me for a fool (which I am sure was not
control: owner -1 !
control: tags -1 moreinfo
Hi,
>I'm looking for an sponsor for my updated package python-jsmin
pull-debian-source python-jsmin
dget -u
https://mentors.debian.net/debian/pool/main/p/python-jsmin/python-jsmin_2.2.1-1.dsc
debdiff python-jsmin*.dsc > debdiff
lets look at the
Hi, can you please have a look at the build failures?
thanks
g++ -MMD -g -O2 -fdebug-prefix-map=/«BUILDDIR»/scid-4.6.4+dfsg1=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -O3 -march=native -fno-rtti -fno-exceptions -std=c++11
-pthread -Wall
hi, done!
thanks,
G.
Hi,
>I tried to fix the issue with the duplicated definition of log2 in
>clustalo in Git[1] but failed. It probably failed since even if I
>remove the line that should be excluded by #ifndef HAVE_LOG2 the problem
>persists and so I assume there is another log2 definition done
>somewhere.
pull-
Hi,
>> Also, it's now xz compressed, which I anticipated is something
>> Gianfranco might hassle me about if I didn't enable haha.>
>
>If you're not uploading a new upstream version you can't change the
>tarball compression (unless you're changing the source package name,
>which I don't recommen
control: owner -1 !
control: tags -1 moreinfo
Hi
(no need to cc me, I'm subscribed to bug reports)
> I am looking for a sponsor for the package "paflib".
> This is a packaging update :
>
> paflib (0.3.0-1) unstable; urgency=medium
>
> * New upstream release
missing changes:
d/control: one mai
control: owner -1 !
control: tags -1 moreinfo
Hi,
>I'm looking for an sponsor for my updated package couchapp
some questions before sponsoring or giving you DM
1)
INSTALL_REQUIRES = ['restkit==4.2.2', 'watchdog==0.6.0']
why is restkit manually listed in runtime dependencies?
2)
Vcs-Git: h
Hi Gustavo
>> INSTALL_REQUIRES = ['restkit==4.2.2', 'watchdog==0.6.0']
>> why is restkit manually listed in runtime dependencies?
>
>that's for setuptools, I could patch it out, but why?
please read what I wrote :)
python-restkit is a build-dependency, and listed in install_requires keyword.
d
Hi,
>Porterboxes. See https://dsa.debian.org/doc/guest-account/ about getting
>access for non-DDs.
or if you aren't a DM, and have some patches to test, send them to me and I'll
try to
do test builds.
(note: my time is limited, so try to avoid ~100 patches to test, unless
I can script them and
control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "phalanx":
* New upstream version.
- New version builds with GCC 6. (Closes: #811584)
this one can become a subsection of "new upstream version"
> * debian/copyright: Update and change Format tag
control: tags -1 moreinfo
Hi
>remove gcc,
>let sdl 1.2 (remove unused sdl2)
>update versions from unstable
oh... no sdl2 ready code?
>>fixed.
>>i only can test in these archs, but i changed it to => any
>
>Depends: ${shlibs:Depends}, ${misc:Depends}, libsdl1.2 (>= 1.2.15)
libsdl1.2 explicit
Hi Adam,
>Actually, if you've read responses to this bug report:
I read them, but the title for the RFS was wrong, we were talking about
unstable.
The RFS is targeting testing, that is impossible because that version is not
even in unstable.
look at the mentors package
Version:4.7.2-
Hi, while waiting for Bruno's review, I'm adding another little (unasked)
one.
debdiff steghide_0.5.1-10_amd64.deb steghide_0.5.1-11_amd64.deb
you are installing too many manpages
-rw-r--r-- root/root /usr/share/man/man3/BmpFile.3.gz
-rw-r--r-- root/root /usr/share/man/man3/BmpFile.h.3.gz
Hi
>ohhh, totally get it. thanks for spotting it
thanks for getting it ;)
is the only way i found to silence lintian about non-encrypted Vcs- urls
"https://anonscm.debian.org/cgit/collab-maint/couchapp.git";
and
"https://anonscm.debian.org/git/collab-maint/couchapp.git";
simple as that :)
control: owner -1 !
control: tags -1 moreinfo
>- add debugging symbols packages
why? they are autogenerated now
https://wiki.debian.org/AutomaticDebugPackages
other stuff seems good
G.
Hi,
>I'm sure you remember - budgie-desktop is just very weird under debian &
>ubuntu and the standard debhelper - all packages seem to be generated but the
>desktop never >launches :/
yep I remember
>I look forward to the future budgie-desktop where the maintainer is to recode
>using C and i
Hi,
I won't test/review, unless you want it to be uploaded in Debian
(with an RFS bug), sorry!
>1) Standards-Version is 3.9.6 because the test suite may perform remote
>network operations. I've tried to locate and disable these, but I'm not
>sure if I've gotten them all.
network is disabled
Hi,
>This is actually because of lack of dependency on doxygen.
>When you do not have doxygen installed, the manpages are simply not
>created with
>no errors whatsoever.
>Although when you have it there is some difference, it drops to 6 lines,
>instead
>of 300.
-> Considering build-dep doxyge
control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "clsparse"
missing copyrights:
e.g.
Copyright 2015 Vratis, Ltd.
wrong licenses: I see lots of expat under
./src/library/kernels/*
2) usual cl missing header failure
http://debomatic-i386.debian.net/distr
control: tags -1 moreinfo
Hi,
> * mmh
sounds interesting, lets see:
1)
-rw-r--r-- root/root 840 2016-08-24 06:33 ./usr/share/man/man1/mmh.1.gz
-rw-r--r-- root/root 794 2016-08-24 06:33
./usr/share/man/man1/mmhwrap.1.gz
-rw-r--r-- root/root 1065 2016-08-24 06:33 ./usr/share
Hi
>Hello @all,
LGTM, sponsoring soon if Adrian is not objecting :)
(right now it is on deferred/5)
G.
Hi,
>Ugh, please don't pressure me here. I am in the middle of the review process
>for Joerg's packages.
deleted, I thought you were too busy to review it, and without a bug such
requests
are easily forgotten :)
Nice to see you back on track!
thanks a lot
G.
Hi,
>I was actually referring to the original version 0.5.1-10 from the
>Debian archive.
>When you have doxygen it builds the same way you have in the version I
>uploaded. I was just reproducing the same result.
>I was not clear about it, sorry.
>In any case:
ok this makes sense now :)
BTW, w
control: owner -1 !
control: tags -1 moreinfo
Hi,(please don't use html in mail, when possible)
>budgie-desktop:
1) lots of missing copyrights, e.g.
Copyright (C) 2015-2016 Solus Project
Copyright 2014 Josh Klar (original Budgie work, prior to
Budgie 10)
2) I see a lot of autogenerated file
Hi,
>Upstream has opted to merge the source packages together to ease
>building and distribution. Didn't see a benefit to reversing that.
>
>I meant: is there anything extra a good source package should do when it
>absorbs another?
usually nothing, just provide the new binaries from the new s
Hi
>because there is still some stuff to sort out with the new usbguard 0.6
>release, i fixed the bugs in the already uploaded release and made a new
>debian revision. I hope that approach is oke.
simple is better! sponsored
G.
Hi
>Thanks for reviwing! I must say I've addressed most of your points but
>testing the new version (25), I've found that it doesn't work as
>expected in Scid. Scid has a feature to play versus Phalanx (tactical
>game) but it needs a special version. The package in sid works well
>while new versi
Hi,
>Please review my new package for kpmcore,
ok
>thanks for any tips or advice!
using mentors would be so appreciated
review:
1) grep copyright . -Ri
missing copyrights
2)
usr/lib/*/libkpmcore.so.2*
usr/lib/*/libkpmcore.so.3
why are you installing both SONAMEs?
3) dpkg-gensymbols is
Hi,
>I know this approach
>works, but is it the "right" way? Does it matter?
your way is the best one if you also add a patch to automatically install the
file
inside the upstream build system.
Otherwise you can avoid a patch and add the desktop file inside the debian
directory,
and ask u
Hi Ghislain,
>> your way is the best one if you also add a patch to automatically install
>> the file
>> inside the upstream build system.
>It would be better to send upstream a patch to include the .desktop
>file in their source tree and install it using their build system. If
>they refuse
control: owner -1 !
control: tags -1 moreinfo
Hi,> * Non-maintainer upload.
changes are huge, but being half mia, and on lowNMU threshold...
(and too many bugs here, so lets do it)
> * New upstream release (closes: #833081, #811988, #798624, #645616).> *
> Updated to Standards-Version
Forgot lintian
9)
I: libcgicc source: binary-control-field-duplicates-source field "section" in
package libcgicc5
I: libcgicc source: quilt-patch-missing-description
0002-Non-empty-html-index.patch
I: libcgicc source: quilt-patch-missing-description
003-no-old-style-config.patch
W: libcgicc5:
Hi
>22 days old (needed 5 days)
>Valid candidate
>
>
>So what might be the problem here?
wild guess, many packages have a dependency on the old version.
but they are arch:all, so binNMU isn't possible (or is, but nobody
wants to try them).
So, sourceful uploads are needed for reverse-
Hi,
>I did a source only upload of seqan which somehow leaded to the fact
>that autobuilders ignored it[1]. What can I do?
>
>Kind regards
https://sources.debian.net/src/seqan/1.4.2%2Bdfsg-1/debian/control/
Arch:all package.
and you removed seqan-apps, so it won't migrate unless you file a
Hi,
BTW you did upload the arch:all package, no there isn't stuff
that autobuilders should do.
Last thing:gasic needs to be fixed to see the package removed
(it depends on the package you want to remove)
https://sources.debian.net/src/gasic/0.0.r18-3/debian/control/
G.
Hi Adam,
>This "must" policy requirement has long gone past "pointless" deep into the
>"actively harmful" land. It is universally ignored, and I'd advise you to
>do so too.
what about changing the policy? I admit I never cared too much about
such priorities, and I would like it to be relaxed/
Hi,
>I am looking for a sponsor for my package "mmh"
and I was waiting for it :)
uploaded.
G.
Hi
>I am looking for a sponsor for my package "globjects"
LGTM, sponsored.
G.
Hi,
>P.S. Actually this fixes a lintian Error.
ough! I missed it thanks!
G.
Hi Thomas,
> e.g. I can understand you copyright changes, and I like it, as well as
> compat level and watch file, but rules seems more complicate, maybe PYBUILD
> can help here?
ping?
G.
signature.asc
Description: OpenPGP digital signature
Hi,
>* Add patch to fix crash
>- 0003 - update to upower 0.99API to stop panel crash
please don't forget to also fix the RPATH issue you have
E binary-or-shlib-defines-rpath
usr/bin/budgie-wm /usr/lib/i386-linux-gnu/mutter
usr/bin/budgie-wm /usr/lib/x86_64-linux-gnu/mutter
thanks,
G.
Hi mentors,
I did a doona upload, with "closes #foo" in changelog, getting
a lintian error:
E possible-missing-colon-in-closes
closes #838630
since the bug is closed, because the system closes bugs even without the colon,
isn't this time to drop that error?
I'm not sure why something that work
Hi,
>It doesn't look closed to me.
Indeed, the bug was pending and then excluded from the list in BTS
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=doona&archive=no&pend-exc=pending-fixed&pend-exc=fixed&pend-exc=done&sev-inc=critical&sev-inc=grave&sev-inc=serious&repeatmerged=no
this is why
control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "pyzo"
ERR:
--- pyzo-4.2.1/pyzo/util/qt/__init__.py 1970-01-01 01:00:00.0 +0100
+++ pyzo-4.3/pyzo/util/qt/__init__.py 2016-09-28 10:21:34.0 +0200
@@ -0,0 +1,134 @@
+# -*- coding: utf-8 -*
control: owner -1 !
control: tags -1 moreinfo
Hi Sean,
>libzxcvbn-dev - password strength estimation library - development files
>libzxcvbn0 - password strength estimation library
I'm a little bit worried about the makefile :(
CFLAGS ?= -O2 -Wall -Wextra -Wdeclaration-after-statemen
201 - 300 of 1488 matches
Mail list logo
