Bug#787800: RFS: iperf3/3.0.11-1
Hi Vincent, On Fri, Jul 17, 2015 at 04:08:25PM -0700, Vincent Cheng wrote: Hi Raoul, On Fri, Jul 17, 2015 at 2:05 AM, Raoul Borenius boren...@dfn.de wrote: Hallo Vincent, Thanks for taking the time to check my package! On Sat, Jul 04, 2015 at 03:21:43PM -0700, Vincent Cheng wrote: Control: tag -1 + moreinfo Control: owner -1 ! Hi Raoul, On Fri, Jun 5, 2015 at 12:59 AM, Raoul Borenius boren...@dfn.de wrote: perf3 (3.0.11-1) unstable; urgency=medium * new upstream version * bumped standards version to 3.9.6 Your changes look ok, but I've noticed that src:iperf3 builds library packages that are installed into multiarch paths (because you're using dh compat level 9), but your packages are not actually multiarch-ified. Please implement multiarch support in your package [1]. Thanks for pointing that out! I've followed the multiarch guide and rebuilt the iperf package: https://mentors.debian.net/package/iperf3 Your -dev package should be declared as MA: same as well. Adding Ah, ok. I misread the recipe because it just talked about adding MA: same to the library package. Thanks! multiarch support to your package is also worth mentioning in d/changelog. Ok, added that! Would you mind checking once more? https://mentors.debian.net/package/iperf3 Thanks a lot! Raoul smime.p7s Description: S/MIME cryptographic signature
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
Hi, Quoting Daniel Stender (2015-07-19 17:52:16) I'm looking for a convenient way to test build source packages against resp. on hurd-i386 or kfreebsd-amd64 instead of setting up simple end user Qemu boxes and build within them. Sbuild and qemu-debootstrap somehow? there seems to be this: https://wiki.debian.org/qemubuilder but I never tried that and don't know if these instructions still work. sbuild itself only supports two chroot methods right now (schroot and sudo, settable via $chroot_mode, look into sbuild.conf(5)) so it currently is not able to make use of qemu. I've eyed the adt-virt-* from the autopkgtest package for a while. It would be cool to add support for them to sbuild because then sbuild would immediately support building in a chroot, in lxc, qemu or a machine connected via ssh. Since adt-run does package builds itself, these tools probably are powerful enough for that purpose. I just have no time to implement this :) cheers, josch signature.asc Description: signature
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
On Mon, 20 Jul 2015 10:04:18 +0200, Johannes Schauer wrote: Quoting Daniel Stender (2015-07-19 17:52:16) I'm looking for a convenient way to test build source packages against resp. on hurd-i386 or kfreebsd-amd64 instead of setting up simple end user Qemu boxes and build within them. Sbuild and qemu-debootstrap somehow? there seems to be this: https://wiki.debian.org/qemubuilder but I never tried that and don't know if these instructions still work. cowbuilder and qemu-debootstrap work for me (with armhf and armel, haven't tried with other architectures): http://info.comodo.priv.at/blog/cowbuilder_crossbuilds_for_raspbian.html The linked article http://blog.waja.info/2013/11/25/crossbuilding-debian-packages-with-sbuild-for-raspbian/ explains a setup with sbuild and qemu; also for Raspbian and armhf but it's probably worth a try for hurd or kfreebsd as well. Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #85: Windows 95 undocumented feature -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150720081412.gh26...@colleen.colgarra.priv.at
Re: Fwd: Trying to run build time tests using nosetest for python-pysam
On 2015-07-20 10:54, Andreas Tille wrote:
unfortunately I did not got any response from Debian Python team and
I'm simply lost how to run the tests.
Maybe change the dh_auto_test override to something like:
override_dh_auto_test:
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS=cd tests {interpreter} pysam_test.py
dh_auto_test || echo Ignoring test failures
Also note the following in tests/00README.txt:
In order for the script pysam_test.py to work, you will need pysam in
your PYTHONPATH.
There is also a pysam_test_offline.py which may be more suitable for
build environments without network.
Kind Regards,
Bas
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/491ed4942eab05e71eff3d7278ab3...@xs4all.nl
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
Hi, Quoting gregor herrmann (2015-07-20 10:14:12) cowbuilder and qemu-debootstrap work for me (with armhf and armel, haven't tried with other architectures): http://info.comodo.priv.at/blog/cowbuilder_crossbuilds_for_raspbian.html The linked article http://blog.waja.info/2013/11/25/crossbuilding-debian-packages-with-sbuild-for-raspbian/ explains a setup with sbuild and qemu; also for Raspbian and armhf but it's probably worth a try for hurd or kfreebsd as well. crossbuilding is not equal to native building. I think Daniel was looking for a way to test if their packages build natively on hurd-i386 or kfreebsd-amd64. But crossbuilding from linux (which I'll just assume Daniel runs on their host) to hurd or kfreebsd will lead to different results than natively building on these kernels in (probably) most cases. cheers, josch signature.asc Description: signature
Fwd: Trying to run build time tests using nosetest for python-pysam
Hi, unfortunately I did not got any response from Debian Python team and I'm simply lost how to run the tests. Any help would be really appreciated Andreas. - Forwarded message from Andreas Tille andr...@an3as.eu - Date: Wed, 15 Jul 2015 14:21:48 +0200 From: Andreas Tille andr...@an3as.eu To: debian-...@lists.debian.org, debian-pyt...@lists.debian.org Subject: Trying to run build time tests using nosetest for python-pysam Hi, I tried to add build-time tests for python-pysam[1]. I admit I'm a bit confused about the fact that this involves compiler calls like: ... warning: no files found matching 'tests/tabix_data' writing manifest file 'pysam.egg-info/SOURCES.txt' skipping 'pysam/csamtools.c' Cython extension (up-to-date) building 'pysam.csamtools' extension x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 - fPIC -D_FILE_OFFSET_BITS=64 -D_USE_KNETFILE= -Isamtools -Ipysam -I/usr/include -I/usr/include/python2.7 -c pysam/csamtools.c -o build/temp.linux-x86_64-2.7/pysam/csamtools.o -Wno- error=declaration-after-statement -DSAMTOOLS=1 ... and that it finally ends with ... In file included from pysam/cfaidx.c:261:0: pysam/htslib_util.h:12:1: warning: function declaration isn’t a prototype [-Wstrict-prototypes] int hts_get_verbosity(); ^ x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack- protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-2.7/pysam/cfaidx.o -Lpysam -lz -lhts -o build/lib.linux-x86_64-2.7/pysam/cfaidx.so -- Ran 0 tests in 0.010s OK (same result with python3). I wonder what I'm missing here and how the build time test could be properly runned. Kind regards Andreas. [1] git://anonscm.debian.org/debian-med/python-pysam.git -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150715122148.gc17...@an3as.eu - End forwarded message - -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150720085449.ga17...@an3as.eu
Re: Build on hurd-i386 and kfreebsd-amd64 ... at home
On Mon, 20 Jul 2015 10:34:17 +0200, Johannes Schauer wrote: Quoting gregor herrmann (2015-07-20 10:14:12) cowbuilder and qemu-debootstrap work for me (with armhf and armel, haven't tried with other architectures): http://info.comodo.priv.at/blog/cowbuilder_crossbuilds_for_raspbian.html crossbuilding is not equal to native building. I think Daniel was looking for a way to test if their packages build natively on hurd-i386 or kfreebsd-amd64. Right; I might have misunderstood the original question, maybe because Daniel mentioned qemu-debootstrap :) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #40: not enough memory, go get system upgrade -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150720085823.gi26...@colleen.colgarra.priv.at
failing package uploads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, mentors I am currently in the process of packaging libgtkflow, ITP-Bug can be found under [0] I had a successful package upload to the debian mentors mirror yesterday . Today i fixed several mistakes that have been reported to me. Thus i wanted to reupload the packages, but i screwed up somehow. I did the following things: 1. Uploaded the package (after signing) with dput mentors libgtkflow-versionfoo-1_amd64.changes - - Nothing happened on the website 2. Tried to upload again. - - Dput told me that the package is already uploaded and there is nothing to do 3. Deleted the package on debian mentors and tried to reupload - - Dput tells me that the package is already uploaded and there is nothing to do 4. Force-Reuploaded the package with dput -f mentors libgtkflow-versionfoo-1_amd64.changes - - Upload went through but nothing happened. The FAQ tells me that it if i upload via FTP, i must wait about 30 minutes until changes take effect. About an hour has passed since the last upload and still nothing happened. Now it's been more time and there is no change. Where did i screw up and how do i get my package in again? Any help would be very appreciated. My packaging files can be found at [1] and the github-repo that i create my tarball from is present at [2] Thanks in advance, Grindhold P.S.: I know that most of you guys prefer packaging-related stuff to be hosted on alioth, but i wasnt even able to create a project on there. Can anyone link me a tutorial on how to use alioth? [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792885 [1] https://github.com/grindhold/libgtkflow_packaging [2] https://github.com/grindhold/libgtkflow -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVrQMOAAoJEBuqgJs6izSEAK8QAIVJGzJBFPpSdlNyCvXs+GHQ f4T+AoOkexCBXJ5ayexpYnr5iBKeRuIeOQ37rHXDF7VKK4zTPIiM+Mlj5zFhBK5g wGBZx+dtnC5sF8ZGQgf+TvHj2FPvFh4UOqEz/mX1AtDpv3iCw9AnO/lUjw+YeLg8 tICF0IJLlp6l5OKab+OqsfkOuGpqC/31bOi53T8pvtM1zI93OjBIRs2j02tpfUr+ DZ4T0Tr0HMkKzKtCpjfyJVugQY5hLPdH/OKpIq1W2E3kHPFFxrIBlk2rhVGSOlb2 1Dm9DWAjBsauPTwpauf/2KCksnmm2zdPGeK09GWZD2d9AKIgd0AyXv484fah8O7g h75cBI7Me4oX/QDLThV8KFqTjO8sxOs4n2BcaxtPXgSIOZOYk/0FJN/ItUK7h7ZI QCBL0bOY+dWZcDh2nF0+2w/PMUdGc0dg4PFYl3HRkJuhdCJYwLrLfqKAkN0ZTFR9 yElLY9knmWfBRhAlAadNqsCle91+cPTAyJ3DGd2xtyXHKJIjwZNHMBh+kjOZuKe/ 7JU76cmz6epjA3Ukbchw3iCFpFZe9dy4Zl65LnjckWzJiSM1b0ykMCjYWmFPQGr9 0F5Q9SEJtqheskTw155mgrD4+oZe86zZQNlBLvQC1x915tXjkaTmWX5/3Iodt6Qc MKy2lDiqpMBNwxWs9lDw =KD0g -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55ad030e@skarphed.org
Fwd: Packaging fest-swing and its dependencies
Hi, I did not got any response from Debian Java list until now and thus I'm trying here. The short story is that I somehow seem to need a maven.rules entry for git://anonscm.debian.org/pkg-java/fest-swing-1.x.git but simply failed guessing how to do this. Any help is appreciated Andreas. - Forwarded message from Andreas Tille andr...@an3as.eu - Date: Fri, 17 Jul 2015 20:40:18 +0200 From: Andreas Tille andr...@an3as.eu To: Potter, Tim (Cloud Services) timothy.pot...@hp.com Cc: debian-j...@lists.debian.org debian-j...@lists.debian.org, Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Subject: Re: Packaging fest-swing and its dependencies Hi Tim, On Fri, Jul 03, 2015 at 06:20:46AM +, Potter, Tim (Cloud Services) wrote: The artifact in the libjsr305-java package has the version 0.x, you need a Maven rule (in debian/maven.rules) like this one: org.jsr-305 jsr305 * s/.*/0.x/ * * Andreas, if you get stuck with apparently unsatisfiable Maven dependencies, I’ve found it handy to check out a large number of projects from the pkg-java repository on alioth and search through the debian/maven.rules files for tips. I admit I tried to find any clue but failed. To me maven.rules is some regexp-replacement but I do not have the slightest idea how to find out what needs to be replaced and by what it should be replaced. The clue above suggested by Emmanuel has in my eyes no relation to the error I had faced. For instance current build of fest-swing-1.x starts with errors like: [ERROR] /tmp/buildd/fest-swing-1.x-20130304/fest-swing/src/main/java/org/fest/swing/driver/ComponentDriver.java:[17,33] error: package org.fest.assertions does not exist [ERROR] /tmp/buildd/fest-swing-1.x-20130304/fest-swing/src/main/java/org/fest/swing/driver/ComponentDriver.java:[17,0] error: static import only from classes and interfaces [ERROR] /tmp/buildd/fest-swing-1.x-20130304/fest-swing/src/main/java/org/fest/swing/driver/ComponentEnabledCondition.java:[26,26] error: package org.fest.assertions does not exist [ERROR] /tmp/buildd/fest-swing-1.x-20130304/fest-swing/src/main/java/org/fest/swing/timing/Condition.java:[22,26] error: package org.fest.assertions does not exist [ERROR] /tmp/buildd/fest-swing-1.x-20130304/fest-swing/src/main/java/org/fest/swing/timing/Condition.java:[23,26] error: package org.fest.assertions does not exist How can I now guess a maven.rules line to fix this? Can somebody point me to the relevant piece inside the long error log which gives a clue about the needed replacement? Kind regards Andreas. -- http://fam-tille.de - End forwarded message - -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150720133809.gf17...@an3as.eu
Bug#793021: RFS: iep/3.6.1-2 [RC]
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package iep * Package name: iep Version : 3.6.1-2 Upstream Author : Almar Klein almar.kl...@gmail.com * URL : http://www.iep-project.org/ * License : BSD Section : science It builds those binary packages: iep - Interactive Editor for Python (Python 3) iep-common - Interactive Editor for Python (common files) python3-ieplib - Interactive Editor for Python (Python 3 modules) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/iep Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/iep/iep_3.6.1-2.dsc Changes since the last upload: * Rename entry point from iep to iep-ide. (Closes: #792748) Best regards, Ghislain -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55ad023a.4000...@gmail.com
Re: failing package uploads
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 07/20/2015 06:43 PM, Joseph Herlant wrote: Hi Joseph, Hi Andrey Thanks for your help. It works again now. Unfortunately i cannot tell you what exactly went wrong, because i fiddled around with dput.cf and tried to use dcut because the debug messages told me so. Unfortunately the success-report-emails come with a delay of ~15 minutes, so i am not able to correlate my changes with the successful upload :S The package is now once again available on [0] Yours, Grindhold [0] http://mentors.debian.net/package/libgtkflow -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVrT1hAAoJEBuqgJs6izSESWwP/jvetM77rkuXYcE1shueu2Yb eESjq2ZrdXABTtCIWmEzs5yNhlIC1SSjzy1enaUKvVUc3rHUhW3V/A6qd75PhJ8L pAI5qnOynst0CKlPJoRwXMK8VB003i7N90gs/2FFApJbkyXyGjVxdJX/rHrsSVXZ dYGh48L8q65wD45/Y6L7x/Q5tKz95PCovRlPkrtAjLQlZgRmAiuymrzS0CiR+Lwf pWIEeBATQU1joHksagzAWAyMlG1zprWihF2ppPGCLXocyfYFcPtj9wfdc4PhROdE ddH8HlHaDu2cR2Xl9Bfd+hWcQpMz664MVG/9Rb866DND7zLQGF/adm1i5rEy6RDa UACu8ArC+agJeggeSZRdENl7++LP84yxv+l3Ph55R4Sygqpseut5ljr1CNl/ALV3 GuUXKesKPjvavZRitqKf7Ui706XbdHM5gtjf3i7ucksZsEaOuuF7YC5a+BDhX1X6 J2q04oBXI8XHoqRCe77eK4IPl/q38+leRxNUXL8/SVlzV874c+1VfD9hJ4NhUa/a Fb4X5kwmYZ0j9EIH+8QTMdlOyZlGmZ++P6Jh4wWTU3u/BFYmrittI8G/hrItovEo PN8iiAoij2ukjMeG/qBiPvJ9+RYJ8/Z5HhlluoY7S0zjb6VxkLtXhOzla4RZMHN2 HZ1+ntb4nNQeC97GyPte =l+w/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55ad3d61.7010...@skarphed.org
Re: failing package uploads
Hi Daniel, Can you remove the .upload file, retry to upload the package in debug mode (-d) and send the output please? Thanks Joseph
Bug#792895: marked as done (RFS: glipper/2.4-5)
Your message dated Mon, 20 Jul 2015 16:27:33 + with message-id e1zhduf-0004np...@quantz.debian.org and subject line closing RFS: glipper/2.4-5 has caused the Debian Bug report #792895, regarding RFS: glipper/2.4-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 792895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package glipper * Package name: glipper Version : 2.4-5 Upstream Author : Laszlo Pandy laszl...@gmail.com * URL : http://launchpad.net/glipper * License : GPL-2+ Section : utils It builds those binary packages: glipper- Clipboard manager for GNOME To access further information about this package, please visit the following URL: http://mentors.debian.net/package/glipper Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/g/glipper/glipper_2.4-5.dsc Changes since the last upload: * debian/control: - Bump Standards-Version to 3.9.6. - Added dh-python to Build-Depends. [ Thanks Ernesto Domato ] * debian/patches: - Update the autostart-only-in-gnome.txt path to include the MATE desktop (Closes: #724599). Regards, José Ernesto Dávila Pantoja -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVrBGkAAoJELA1+Eo3xIzmU5YP/jZbCJc3cEa1mUwploYasNmb JSU7Bcm0whmb91NjBzXWmoL+2DfEVHl8J4Hny3hON0idF4ocp/pYpSELUw5rAe8P 2KgtHG69xtcr1rQZLoQYDTsZAY+WwTttp6c+zRUHiLWUvpuMIQPyWo/utv+LwcJV EVWFZqsB6EJ8UyfHz+IABywbidkdSaQuQby4H4J1bC8dkDC9KEFsQDunpg245EPr TcrI6Qju1/xZsTqJZa0P+vzYfreJIqTaEjRlvAliSmpUzmIt/YslkR4l6L8lA7eG N9P4PD4xzcshdLtgqmlBco7AFrcwz7eJH8c7EQ0YbeLoPr9Jzl7fp9KcBxzFqTuE yNTQXOCxF1xu1hAMgOdlrF+QmFGATpOcKHAch80WTrcxH1gSgEDpvl9Iiceczlf2 kHNA2NOi7MSUpxMZsSHeW0cjX0ERTYG0ncqHUH3TsmKcxiFicp1kY1TbNjv3TiQw gpWLfW+hunjjHMewRKBQE9rYyf0iaPUHJr9N79HimMnaNDtCejb5s2Iex/LUiSgs KoMMp5+EUTyEpyYSyh05xs/DF6k0tXa04fb0UJ5CkFPhK0igmUHU2kJJE6AYjjNV OtWiPJr00KkTHQ79ivar6rYLaW4ZPdq2jk6lm3wRBgeeqUyPFYgP2lMSdXsK2agH cYb5KwA4OSncTM5s7PRg =+WOy -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Package glipper version 2.4-5 is in unstable now. https://packages.qa.debian.org/glipper---End Message---
Re: failing package uploads
On Mon, Jul 20, 2015 at 04:17:50PM +0200, Daniel Brendle wrote: 3. Deleted the package on debian mentors and tried to reupload - - Dput tells me that the package is already uploaded and there is nothing to do dput checks for .upload, it doesn't ask the server, -f skips that (you should already know that, though). P.S.: I know that most of you guys prefer packaging-related stuff to be hosted on alioth, but i wasnt even able to create a project on there. Can anyone link me a tutorial on how to use alioth? You shouldn't create projects on alioth. Your repos should be hosted on the respective team projects or collab-maint. See https://wiki.debian.org/Teams/CollabMaint. See also https://lists.debian.org/debian-devel-announce/2012/01/msg6.html about gaining commit access to collab-maint. -- WBR, wRAR signature.asc Description: Digital signature
Re: Bug#788844: RFS: gbutils/5.6.6-1 [ITP]
Hi Tomasz, Il giorno dom, 19/07/2015 alle 21.59 +0200, Tomasz Buchert ha scritto: On 15/07/15 15:11, Pietro Battiston wrote: Il giorno dom, 12/07/2015 alle 20.38 +0200, Tomasz Buchert ha scritto: On 11/07/15 00:37, Pietro Battiston wrote: [...] Just to clarify: I had understood your suggestion, and my answer to it is I don't think it is practical for users. Think of it as replacing cat, echo, grep and others with unixutils cat, unixutils echo, unixutils grep... the similarity breaks when we look at the userbase, but for those who do use gbutils... I think you get my point. Frankly, I don't get your point. These are basic Unix programs, used all the time in scripts, command line, etc. And there is also tradition. The program command interface is not a bad idea: git uses it and I don't think that people find git impractical. No, but it does not happen frequently (if ever... at least to me) that a single command line includes several git calls: it is frequent instead with executables from gbutils, and this is the point I was confusely trying to make. (BTW: then, I am not a fan of the switch from git-buildpackage to gbp buildpackage, but it's probably just a matter of habit... and anyway I'm going OT) But I don't really care, as long as the people at the NEW queue have nothing against it and the multitude of commands does not collide with anything else in the whole archive (have you checked?). Yes! At least against anything which can be installed in /usr/bin - do you think I am missing something? [...] Related to your other email, I updated build-depends and depends so that now all utilities/functionalities are compiled and installed, and introduced a patch fixing a few typos in the previously not installed utilities. Updated package: http://mentors.debian.net/debian/pool/main/g/gbutils/gbutils_5.6.6 -1.dsc Thanks again! You're welcome. Do you want me to sponsor it? Well... it would be great! A.k.a. I currently don't have any alternative. (in any case, don't forget to verify that there are no collisions, apt-file search is your friend) Done, see above, Pietro -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1437423853.28335.61.ca...@pietrobattiston.it
Bug#793021: marked as done (RFS: iep/3.6.1-2 [RC])
Your message dated Mon, 20 Jul 2015 19:27:50 -0700 with message-id caczd_tcgs8crksphdwyf+hmq+jxvjg6b7hon42b_2kmavgb...@mail.gmail.com and subject line Re: Bug#793021: RFS: iep/3.6.1-2 [RC] has caused the Debian Bug report #793021, regarding RFS: iep/3.6.1-2 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package iep * Package name: iep Version : 3.6.1-2 Upstream Author : Almar Klein almar.kl...@gmail.com * URL : http://www.iep-project.org/ * License : BSD Section : science It builds those binary packages: iep - Interactive Editor for Python (Python 3) iep-common - Interactive Editor for Python (common files) python3-ieplib - Interactive Editor for Python (Python 3 modules) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/iep Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/iep/iep_3.6.1-2.dsc Changes since the last upload: * Rename entry point from iep to iep-ide. (Closes: #792748) Best regards, Ghislain ---End Message--- ---BeginMessage--- Already uploaded to sid [1], thus closing this bug report. Regards, Vincent [1] https://lists.debian.org/debian-devel-changes/2015/07/msg02253.html---End Message---
Bug#787800: marked as done (RFS: iperf3/3.0.11-1)
Your message dated Mon, 20 Jul 2015 19:41:38 -0700 with message-id caczd_tashstsdrzezzwhwk6qcx6vtwddf3fnakq4-cmbtcg...@mail.gmail.com and subject line Re: Bug#787800: RFS: iperf3/3.0.11-1 has caused the Debian Bug report #787800, regarding RFS: iperf3/3.0.11-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 787800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787800 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package iperf3 * Package name: iperf3 Version : 3.0.11-1 Upstream Author : Jon Dugan, ESnet * URL : http://software.es.net/iperf/ * License : BSD-3-clause Section : net It builds those binary packages: iperf3 - Internet Protocol bandwidth measuring tool libiperf-dev - Internet Protocol bandwidth measuring tool (development files) libiperf0 - Internet Protocol bandwidth measuring tool (runtime files) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/iperf3 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/iperf3/iperf3_3.0.11-1.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: perf3 (3.0.11-1) unstable; urgency=medium * new upstream version * bumped standards version to 3.9.6 Regards, Raoul Gunnar Borenius ---End Message--- ---BeginMessage--- Hi Raoul, On Sun, Jul 19, 2015 at 11:18 PM, Raoul Borenius boren...@dfn.de wrote: Hi Vincent, On Fri, Jul 17, 2015 at 04:08:25PM -0700, Vincent Cheng wrote: Hi Raoul, On Fri, Jul 17, 2015 at 2:05 AM, Raoul Borenius boren...@dfn.de wrote: Hallo Vincent, Thanks for taking the time to check my package! On Sat, Jul 04, 2015 at 03:21:43PM -0700, Vincent Cheng wrote: Control: tag -1 + moreinfo Control: owner -1 ! Hi Raoul, On Fri, Jun 5, 2015 at 12:59 AM, Raoul Borenius boren...@dfn.de wrote: perf3 (3.0.11-1) unstable; urgency=medium * new upstream version * bumped standards version to 3.9.6 Your changes look ok, but I've noticed that src:iperf3 builds library packages that are installed into multiarch paths (because you're using dh compat level 9), but your packages are not actually multiarch-ified. Please implement multiarch support in your package [1]. Thanks for pointing that out! I've followed the multiarch guide and rebuilt the iperf package: https://mentors.debian.net/package/iperf3 Your -dev package should be declared as MA: same as well. Adding Ah, ok. I misread the recipe because it just talked about adding MA: same to the library package. Thanks! Any package that is co-installable on different archs, i.e. ships all arch-specific files in multiarch directories with all other files being identical across different archs, should be declared as MA: same. It may be worth reading up on the specification if you're unsure about the semantics of MA-related fields. [1] multiarch support to your package is also worth mentioning in d/changelog. Ok, added that! Would you mind checking once more? https://mentors.debian.net/package/iperf3 Looks good, uploaded; thanks for your contribution to Debian! I've left some feedback on the other RFS bug reports you have open (#787801 and #787802) a while ago, by the way. Regards, Vincent [1] https://wiki.ubuntu.com/MultiarchSpec---End Message---
