Bug#863789: RFS: logdata-anomaly-miner/0.0.8-1
control: close -1 Hi, >I am looking for a sponsor for my package "logdata-anomaly-miner" I sponsored it in experimental (due to the freeze), but please: 1) drop the patch (python2.6 is dead now) I don't see lintian complains without that patch. (waiting eventually for a -2 in experimental :) ) and ops, the NEWS file was still pointing at unstable, please fix that G.
Bug#863278: RFS: usbguard/0.7.0-1
Hello On Wed, May 24, 2017 at 07:43:35PM +0200, Muri Nicanor wrote: * New upstream version 0.7.0 This release contains a backwards incompatible change because it changes how the device hash is computed for Linux root hub devices How is it handled for users that already have a config file? do they need to create a new configuration file? Can the update to the config file by done automatically? (postinst) does this version need a newer kernel than older versions? -- IRC: gfa GPG: 0X44BB1BA79F6C6333 signature.asc Description: Digital Signature
Bug#863278: RFS: usbguard/0.7.0-1
control: owner -1 ! control: tags -1 moreinfo the package builds fine with pbuilder but tests fails when i try to build using sbuild. FAIL UseCase/001_cli_policy.sh (exit status: 1) some tests are skipped, i feel they should run perhaps usbguard should build-depend on sudo? UseCase/002_cli_devices.sh.log: + sudo -n dd bs=4096 count=1 if=/dev/zero of=/tmp/usbguard_disk UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 81: sudo: command not found UseCase/002_cli_devices.sh.log: + sudo -n modprobe dummy_hcd UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 82: sudo: command not found UseCase/002_cli_devices.sh.log: + sudo -n rmmod g_mass_storage UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 83: sudo: command not found UseCase/002_cli_devices.sh.log: + sudo -n modprobe g_mass_storage file=/tmp/usbguard_disk iSerialNumber=555666111 UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 84: sudo: command not found UseCase/002_cli_devices.sh.log: + '[' 127 -ne 0 ']' UseCase/002_cli_devices.sh.log: + exit 77 UseCase/002_cli_devices.sh.log: SKIP UseCase/002_cli_devices.sh (exit status: 77) this should be easy to fix Packaging/spell-check.sh.log: Skipping test because some dependecies are missing Packaging/spell-check.sh.log: ASPELL: Packaging/spell-check.sh.log: PANDOC: /usr/bin/pandoc Packaging/spell-check.sh.log: SKIP Packaging/spell-check.sh (exit status: 77) thanks! -- IRC: gfa GPG: 0X44BB1BA79F6C6333 signature.asc Description: Digital Signature
Bug#863278: RFS: usbguard/0.7.0-1
On Thu, Jun 01, 2017 at 06:07:40PM +0800, gustavo panizzo wrote: > some tests are skipped, i feel they should run > > > perhaps usbguard should build-depend on sudo? > > UseCase/002_cli_devices.sh.log: + sudo -n dd bs=4096 count=1 if=/dev/zero > of=/tmp/usbguard_disk > UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 81: sudo: > command not found > UseCase/002_cli_devices.sh.log: + sudo -n modprobe dummy_hcd > UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 82: sudo: > command not found > UseCase/002_cli_devices.sh.log: + sudo -n rmmod g_mass_storage > UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 83: sudo: > command not found > UseCase/002_cli_devices.sh.log: + sudo -n modprobe g_mass_storage > file=/tmp/usbguard_disk iSerialNumber=555666111 > UseCase/002_cli_devices.sh.log: ./UseCase/002_cli_devices.sh: line 84: sudo: > command not found > UseCase/002_cli_devices.sh.log: + '[' 127 -ne 0 ']' > UseCase/002_cli_devices.sh.log: + exit 77 > UseCase/002_cli_devices.sh.log: SKIP UseCase/002_cli_devices.sh (exit > status: 77) No, it's a bad idea to do things requiring root during tests, especially modprobe/rmmod. And please remember that just calling sudo is not enough to get root. -- WBR, wRAR signature.asc Description: PGP signature
Bug#863278: RFS: usbguard/0.7.0-1
On June 1, 2017 6:13:06 PM GMT+08:00, Andrey Rahmatullin wrote: >> UseCase/002_cli_devices.sh.log: SKIP UseCase/002_cli_devices.sh >(exit status: 77) >No, it's a bad idea to do things requiring root during tests, >especially >modprobe/rmmod Maybe those tests can be run using autopkgtests I'd prefer to run tests if they are available >And please remember that just calling sudo is not enough to get root. Of course, sudo's configuration was explicit in my mind, my bad I didn't mentioned it. -- IRC: gfa GPG: 0x44BB1BA79F6C6333 Sent from my mobile. Please excuse my brevity and typos. signature.asc Description: PGP signature
Bug#863894: RFS: groonga/7.0.3-1
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "groonga" for experimental * Package name: groonga Version : 7.0.3-1 Upstream Author : Groonga Project * Url : http://groonga.org/ * Licenses: LGPL-2.1 Section : database It builds those binary packages: * groonga * groonga-server-common * groonga-server-gqtp * libgroonga-dev * libgroonga0 * groonga-tokenizer-mecab * groonga-token-filter-stem * groonga-plugin-suggest * groonga-bin * groonga-httpd * groonga-doc * groonga-examples * groonga-munin-plugins To access further information about this package, visit the following URL: https://mentors.debian.net/package/groonga Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/groonga/groonga_7.0.3-1.dsc More information about groonga can be obtained from http://groonga.org/ Changes since last upload: * New upstream release. * debian/patches/fix-nginx-FTBFS-on-kfreebsd.patch - Refresh patch to fix FTBFS on kFreeBSD. * debian/copyright - Add missing copyright about benchmark. Regards, pgpqjnNunreMi.pgp Description: PGP signature
Bug#859778: [supp...@mentors.debian.net: xtrs uploaded to mentors.debian.net]
package sponsorship-requests tag 859778 - moreinfo thanks $ dput mentors xtrs_4.9d-1_amd64.changes Checking signature on .changes gpg: /home/branden/src/GIT/debian/xtrs_4.9d-1_amd64.changes: Valid signature from D19E9C7D71266DCE Checking signature on .dsc gpg: /home/branden/src/GIT/debian/xtrs_4.9d-1.dsc: Valid signature from D19E9C7D71266DCE Uploading to mentors (via http to mentors.debian.net): Uploading xtrs_4.9d-1.dsc: done. Uploading xtrs_4.9d.orig.tar.gz: done. Uploading xtrs_4.9d-1.debian.tar.xz: done. Uploading xtrs-dbgsym_4.9d-1_amd64.deb: done. Uploading xtrs_4.9d-1_amd64.buildinfo: done. Uploading xtrs_4.9d-1_amd64.deb: done. Uploading xtrs_4.9d-1_amd64.changes: done. Successfully uploaded packages. - Forwarded message from "mentors.debian.net" - Date: Thu, 1 Jun 2017 21:11:41 + (UTC) From: "mentors.debian.net" To: g.branden.robin...@gmail.com Subject: xtrs uploaded to mentors.debian.net Hi. Your upload of the package 'xtrs' to mentors.debian.net was successful. Others can now see it. The URL of your package is: https://mentors.debian.net/package/xtrs The respective dsc file can be found at: https://mentors.debian.net/debian/pool/contrib/x/xtrs/xtrs_4.9d-1.dsc If you do not yet have a sponsor for your package you may want to go to https://mentors.debian.net/sponsors/rfs-howto/xtrs and set the "Seeking a sponsor" option to highlight your package on the welcome page. You can also send an RFS (request for sponsorship) to the debian-mentors mailing list. Your package page will give your suggestions on how to send that mail. Good luck in finding a sponsor! Thanks, -- mentors.debian.net - End forwarded message - Regards, Branden signature.asc Description: PGP signature
Bug#848327: Bug#824532: [Pkg-auth-maintainers] Bug#848327: RFS: libu2f-host/1.1.3-1
X-Debbugs-CC: sramac...@debian.org Hi, On Sun, Jan 29, 2017 at 10:21:18PM +0100, Michael Biebl wrote: > To make this perfectly clear (again): I, as udev/systemd maintainer, > object to maintaining that u2f udev rule as a downstream patch in udev > and I will remove that patch from src:systemd post stretch. It's simply > not maintainable (as proven by the outdated rule we ship). > > Possible solutions for you to consider: > 1/ get those udev rules accepted at systemd upstream (was rejected afair) > 2/ split the rules out into a -common package which doesn't require > libu2f-host0 to be installed > 3/ rework u2f support so it doesn't requires those udev rules. Since no other workable solutions were proposed, and since Michael made it clear that this is not baggage he would carry in udev, I updated the proposed upload: https://anonscm.debian.org/cgit/pkg-auth/libu2f-host.git/log/?h=rfs-848327 This should take care of all previous comments (and some extras from Sebastian Ramacher), though I regret that the bikeshedding made us miss the stretch window. There are still a couple of nitpicks: I'm not sure what is the appropriate Priority for libu2f-udev (optional?) and I need to make a few MultiArch-related changes, which should be pushed tomorrow. Best, nicoo signature.asc Description: PGP signature
Bug#863894: marked as done (RFS: groonga/7.0.3-1)
Your message dated Fri, 2 Jun 2017 01:08:08 +0200 with message-id <20170601230808.zbznqrtwtgrjw...@angband.pl> and subject line Re: Bug#863894: RFS: groonga/7.0.3-1 has caused the Debian Bug report #863894, regarding RFS: groonga/7.0.3-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.) -- 863894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863894 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "groonga" for experimental * Package name: groonga Version : 7.0.3-1 Upstream Author : Groonga Project * Url : http://groonga.org/ * Licenses: LGPL-2.1 Section : database It builds those binary packages: * groonga * groonga-server-common * groonga-server-gqtp * libgroonga-dev * libgroonga0 * groonga-tokenizer-mecab * groonga-token-filter-stem * groonga-plugin-suggest * groonga-bin * groonga-httpd * groonga-doc * groonga-examples * groonga-munin-plugins To access further information about this package, visit the following URL: https://mentors.debian.net/package/groonga Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/groonga/groonga_7.0.3-1.dsc More information about groonga can be obtained from http://groonga.org/ Changes since last upload: * New upstream release. * debian/patches/fix-nginx-FTBFS-on-kfreebsd.patch - Refresh patch to fix FTBFS on kFreeBSD. * debian/copyright - Add missing copyright about benchmark. Regards, pgptVRtHN0LtG.pgp Description: PGP signature --- End Message --- --- Begin Message --- On Fri, Jun 02, 2017 at 02:24:28AM +0900, Kentaro Hayashi wrote: > I am looking for a sponsor for my package "groonga" for experimental > > * Package name: groonga > Version : 7.0.3-1 > Changes since last upload: > > * New upstream release. > * debian/patches/fix-nginx-FTBFS-on-kfreebsd.patch > - Refresh patch to fix FTBFS on kFreeBSD. > * debian/copyright > - Add missing copyright about benchmark. Looks good, uploaded. I'm somewhat unhappy about binary-without-manpage being overridden -- stuff in /{,usr/}{,s}bin/ is supposed to be a public interface for either humans or scripts thus should be documented. No one forces you to write such documentation immediately (perfection is not (yet) mandatory), but it's still a real issue rather than a false positive. Thus, I'd suggest either dropping the override, writing some docs, or moving the executables. But, that's no regression from 7.0.2-1, thus 'ere we go. Meow! -- Don't be racist. White, amber or black, all beers should be judged based solely on their merits. Heck, even if occasionally a cider applies for a beer's job, why not? On the other hand, corpo lager is not a race.--- End Message ---
Bug#863432: marked as done (RFS: bluemon/1.4-7 [QA-Upload])
Your message dated Fri, 2 Jun 2017 01:35:00 +0200 with message-id <20170601233500.ltq3s54zsj3lj...@angband.pl> and subject line Re: Bug#863432: RFS: bluemon/1.4-7 [QA-Upload] has caused the Debian Bug report #863432, regarding RFS: bluemon/1.4-7 [QA-Upload] 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.) -- 863432: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for a QA-Upload for the package "bluemon" * Package name: bluemon Version : 1.4-7 * License : GPL-2 Section : net It builds those binary packages: bluemon- Activate or deactivate programs based on Bluetooth link quality To access further information about this package, please visit the following URL: https://mentors.debian.net/package/bluemon Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/b/bluemon/bluemon_1.4-7.dsc Changes since the last upload: bluemon (1.4-7) unstable; urgency=medium * QA upload. * Convert to Source-Format 3.0 (quilt) * debian/control, debian/compat: - change debhelper-compat level to 10 * debian/control: - set Maintainer to QA group, package is orphaned (#762537) - add dependency on lsb-base for init script - run wrap-and-sort -sa - declare policy-compliance for Policy 3.9.8 - Add a homepage field * debian/rules: - use dh * debian/prerm+preinst: - Remove prerm file, was only needed for upgrades from version 1.3-1.2, which no longer is in any supported Debian release - Remove preinst file, debhelper does the right thing automatically * debian/dirs: - Remove, not needed * debian/init: - Add $remote_fs to Required-Start/-Stop - Also stop at runlevel 1 - Don't start daemon on restart action if disabled in /etc/defaults/bluemon (Closes: #679109) * debian/copyright: - Add a machine-readable copyright-file * debian/patches: - add-cppflags-hardening.patch: Add CPPFLAGS and LDFLAGS to pass hardening options to the compiler. This also fixes build with binutils-gold (Closes: #612181) - add clang-ftbfs.diff to Fix FTBFS with clang: Fixed the non-void function should return a value in bluetooth-monitor.c (Closes: #740036) Patch from Arthur Marble Regards, Andreas Moog -- PGP-encrypted mails preferred PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624 signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Fri, May 26, 2017 at 09:25:23PM +0200, Andreas Moog wrote: > I am looking for a sponsor for a QA-Upload for the package "bluemon" > > * Package name: bluemon >Version : 1.4-7 > Changes since the last upload: > > bluemon (1.4-7) unstable; urgency=medium > >* QA upload. >* Convert to Source-Format 3.0 (quilt) >* debian/control, debian/compat: > - change debhelper-compat level to 10 >* debian/control: > - set Maintainer to QA group, package is orphaned (#762537) > - add dependency on lsb-base for init script > - run wrap-and-sort -sa > - declare policy-compliance for Policy 3.9.8 > - Add a homepage field >* debian/rules: > - use dh >* debian/prerm+preinst: > - Remove prerm file, was only needed for upgrades from version 1.3-1.2, >which no longer is in any supported Debian release > - Remove preinst file, debhelper does the right thing automatically >* debian/dirs: > - Remove, not needed >* debian/init: > - Add $remote_fs to Required-Start/-Stop > - Also stop at runlevel 1 > - Don't start daemon on restart action if disabled in > /etc/defaults/bluemon >(Closes: #679109) >* debian/copyright: > - Add a machine-readable copyright-file >* debian/patches: > - add-cppflags-hardening.patch: Add CPPFLAGS and LDFLAGS to pass > hardening >options to the compiler. This also fixes build with binutils-gold >(Closes: #612181) > - add clang-ftbfs.diff to Fix FTBFS with clang: >Fixed the non-void function should return a value in >bluetooth-monitor.c (Closes: #740036) >Patch from Arthur Marble These changes are unfit for unstable during the freeze. On the other hand, it happens that the release date is already known, and it happens to be 15 days from now --
Bug#848327: Bug#824532: [Pkg-auth-maintainers] Bug#848327: RFS: libu2f-host/1.1.3-1
Am 02.06.2017 um 00:13 schrieb Nicolas Braud-Santoni: > Since no other workable solutions were proposed, and since Michael made it > clear > that this is not baggage he would carry in udev, I updated the proposed > upload: > > https://anonscm.debian.org/cgit/pkg-auth/libu2f-host.git/log/?h=rfs-848327 > > This should take care of all previous comments (and some extras from Sebastian > Ramacher), though I regret that the bikeshedding made us miss the stretch > window. > This is unfortunate indeed that no solution was implemented in time. I'm willing to apply a one-time fix to udev/systemd so we don't ship stretch with outdated rules. Nicolas, please send me a patch against https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/extra/rules/70-debian-uaccess.rules?h=stretch including all the entries you want to see added for Stretch. I will try to get this into 9.0 or 9.1 then. I plan to remove debian/extra/rules/70-debian-uaccess.rules once buster opens for development. So please get this sorted out for buster. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#850670: marked as done (RFS: rpyc/3.3.0-1 [ITP])
Your message dated Fri, 02 Jun 2017 04:26:51 + with message-id and subject line closing RFS: rpyc/3.3.0-1 [ITP] has caused the Debian Bug report #850670, regarding RFS: rpyc/3.3.0-1 [ITP] 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.) -- 850670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Control: block 850097 by -1 Dear mentors, I am looking for a sponsor for my package "rpyc" Package name: rpyc Version : 3.3.0-1 Upstream Author : Tomer Filiba URL : https://github.com/tomerfiliba/rpyc License : MIT Section : python I am packaging this as a dependency of flexget (ITP: #724718). It builds these binary packages: python3-rpyc - transparent and symmetric Remote Python Call library -- Python3 module python3-rpyc-doc - transparent and symmetric Remote Python Call library -- documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/rpyc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/rpyc/rpyc_3.3.0-1.dsc Cheers, Carl --- End Message --- --- Begin Message --- Package rpyc has been removed from mentors.--- End Message ---
Bug#851762: marked as done (RFS: hamlib/3.1.0-1+nmu1 [NMU])
Your message dated Fri, 2 Jun 2017 06:28:51 +0100 with message-id <20170602052851.3elrzu6wk32lw...@zephyr.silentflame.com> and subject line Closing inactive RFSs has caused the Debian Bug report #851799, regarding RFS: hamlib/3.1.0-1+nmu1 [NMU] 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.) -- 851799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "hamlib" * Package name : hamlib Version : 3.1.0-1+nmu1 Upstream Author : Kamal Mostafa , Colin Tuckley * URL : https://sourceforge.net/projects/hamlib/ * License : LGPLv2 Section : hamradio It builds those binary packages: libhamlib++-dev - Development C++ library to control radio transceivers and receive libhamlib-dev - Development library to control radio transceivers and receivers libhamlib-doc - Documentation for the hamlib radio control library libhamlib-utils - Utilities to support the hamlib radio control library libhamlib2 - Run-time library to control radio transceivers and receivers libhamlib2++c2 - Run-time C++ library to control radio transceivers and receivers libhamlib2-perl - Run-time perl library to control radio transceivers and receivers libhamlib2-tcl - Run-time Tcl library to control radio transceivers and receivers lua-hamlib2 - Run-time Lua library to control radio transceivers and receivers python-libhamlib2 - Run-time Python library to control radio transceivers and receive To access further information about this package, please visit the following URL: https://mentors.debian.net/package/hamlib Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/h/hamlib/hamlib_3.1.0-1+nmu1.dsc More information about hamlib can be obtained from https://sourceforge.net/projects/hamlib/ Changes since the last upload: * NMU * New upstream release * Changed manpages directory in manpage-hyphen-fixes.patch * Added Lua binding * Fixed broken libhamlib2-tcl package * Bump Standards-version to 3.9.8 Regards, Ervin Hegedüs --- End Message --- --- Begin Message --- Please feel free to re-open if you have an updated source package. -- Sean Whitton signature.asc Description: PGP signature --- End Message ---
Bug#851799: marked as done (RFS: hamlib/3.1.0-1)
Your message dated Fri, 2 Jun 2017 06:28:51 +0100 with message-id <20170602052851.3elrzu6wk32lw...@zephyr.silentflame.com> and subject line Closing inactive RFSs has caused the Debian Bug report #851799, regarding RFS: hamlib/3.1.0-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.) -- 851799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "hamlib" * Package name : hamlib Version : 3.1.0-1 Upstream Author : Kamal Mostafa , Colin Tuckley * URL : https://sourceforge.net/projects/hamlib/ * License : LGPLv2 Section : hamradio It builds those binary packages: libhamlib++-dev - Development C++ library to control radio transceivers and receive libhamlib-dev - Development library to control radio transceivers and receivers libhamlib-doc - Documentation for the hamlib radio control library libhamlib-utils - Utilities to support the hamlib radio control library libhamlib2 - Run-time library to control radio transceivers and receivers libhamlib2++c2 - Run-time C++ library to control radio transceivers and receivers libhamlib2-perl - Run-time perl library to control radio transceivers and receivers libhamlib2-tcl - Run-time Tcl library to control radio transceivers and receivers lua-hamlib2 - Run-time Lua library to control radio transceivers and receivers python-libhamlib2 - Run-time Python library to control radio transceivers and receive To access further information about this package, please visit the following URL: https://mentors.debian.net/package/hamlib Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/h/hamlib/hamlib_3.1.0-1.dsc More information about hello can be obtained from https://sourceforge.net/projects/hamlib Changes since the last upload: * Team upload * New upstream release * Changed manpages directory in manpage-hyphen-fixes.patch * Added Lua binding * Fixed broken libhamlib2-tcl package * Bump Standards-version to 3.9.8 Regards, Ervin Hegedüs -- I � UTF-8 --- End Message --- --- Begin Message --- Please feel free to re-open if you have an updated source package. -- Sean Whitton signature.asc Description: PGP signature --- End Message ---
Bug#854938: marked as done (RFS: wxmaxima/16.12.2-2)
Your message dated Fri, 2 Jun 2017 06:28:51 +0100 with message-id <20170602052851.3elrzu6wk32lw...@zephyr.silentflame.com> and subject line Closing inactive RFSs has caused the Debian Bug report #854938, regarding RFS: wxmaxima/16.12.2-2 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.) -- 854938: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854938 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "wxmaxima" * Package name: wxmaxima Version : 16.12.2-2 Upstream Author : [fill in name and email of upstream] * URL : [fill in URL of upstreams web site] * License : [fill in] Section : math It builds those binary packages: wxmaxima - GUI for the computer algebra system Maxima wxMaxima is a powerful gui for maxima, the computer algebra system. One simple example about what it does do would be: (%i1) x^3+y=1; (%o1) y+x^3=1 (%i2) solve(%,x); (%o2) [x=((sqrt(3)*%i-1)*(1-y)^(1/3))/2,x=-((sqrt(3)*%i+1)*(1-y)^(1/3))/2,x=(1-y)^(1/3)] To access further information about this package, please visit the following URL: https://mentors.debian.net/package/wxmaxima Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wxmaxima/wxmaxima_16.12.2-2.dsc More information about wxMaxima can be obtained from https://andrejv.github.io/wxmaxima/ Changes since the last upload: * Resolved an incompatibility with the gcl debian is currently shipped with. (closes: bug#853787) * debian/compat: Updated the standards version to 10. Regards, Gunter Königsmann --- End Message --- --- Begin Message --- Please feel free to re-open if you have an updated source package. -- Sean Whitton signature.asc Description: PGP signature --- End Message ---
Bug#860496: RFS: drgeo/1.1.0-10.3 [NMU, RC]
Dear Patrick, Please accept my apologies for allowing this RFS to fall through the cracks. On Fri, Apr 21, 2017 at 08:30:00AM -0400, Patrick Hetu wrote: > The new version is here: > > https://mentors.debian.net/debian/pool/main/d/drgeo/drgeo_1.1.0-10.3.dsc You've written - All modifications to .scm, .cc and .h files are compatibility fixes for guile-2.x. Except comments in geo/drgeo_figure.cc that are disabling undo/redo mecanisms that are causing a segfault. So the commenting out of the undo/redo mechanism isn't part of making drgeo compatible with guile 2.0? In that case, it should be in a separate quilt patch. Additionally, the new line in d/rules cp -vf /usr/share/gettext/config.rpath . is not documented in the changelog. More generally, per Adam, maybe we should just remove drgeo from Debian. The current version is 16 and we are still on version 1.1 .. would anyone want to install this? -- Sean Whitton signature.asc Description: PGP signature