Bug#951408: RFS: pulseaudio/13.0-5~bpo10+1 -- PulseAudio sound server
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "pulseaudio" * Package name: pulseaudio Version : 13.0-5~bpo10+1 Upstream Author : [fill in name and email of upstream] * URL : https://www.pulseaudio.org * License : [fill in] * Vcs : https://salsa.debian.org/pulseaudio-team/pulseaudio Section : sound It builds those binary packages: pulseaudio - PulseAudio sound server pulseaudio-utils - Command line tools for the PulseAudio sound server pulseaudio-module-zeroconf - Zeroconf module for PulseAudio sound server pulseaudio-module-jack - jackd modules for PulseAudio sound server pulseaudio-module-lirc - lirc module for PulseAudio sound server pulseaudio-module-gsettings - GSettings module for PulseAudio sound server pulseaudio-module-raop - RAOP module for PulseAudio sound server pulseaudio-module-bluetooth - Bluetooth module for PulseAudio sound server pulseaudio-equalizer - Equalizer sink module for PulseAudio sound server libpulse0 - PulseAudio client libraries libpulse-mainloop-glib0 - PulseAudio client libraries (glib support) libpulse-dev - PulseAudio client development headers and libraries libpulsedsp - PulseAudio OSS pre-load library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/pulseaudio Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/pulseaudio/pulseaudio_13.0-5~bpo10+1.dsc Changes since the last bpo: pulseaudio (13.0-5) unstable; urgency=medium * Fix removal of 00-disable-autospawn.conf. The autoremoval script was wrongly put into the pulseaudio package, while it should have been in the libpulse0 package. Moreover, the version specified was wrong (set at 12.2 instead of 13.0) (Closes: #950413) -- Felipe Sateler Wed, 05 Feb 2020 23:06:41 -0300 pulseaudio (13.0-4) unstable; urgency=medium [ Steve Langasek ] * Make autopkgtests cross-test-friendly. In Ubuntu, we are in the process of moving the i386 architecture to a compatibility-only layer on amd64, and therefore we are also moving our autopkgtest infrastructure to test i386 binaries in a cross- environment. This requires changes to some tests so that they are cross-aware and can do the right thing. The pulseaudio tests currently fail in this environment, because they are build tests that do not invoke the toolchain in a cross-aware manner. I've verified that the attached patch lets the tests successfully build (and run) i386 tests on an amd64 host. Note that upstream autopkgtest doesn't currently set DEB_HOST_ARCH so this is a complete no-op in Debian for the moment. Support for cross- testing in autopkgtest is currently awaiting review at https://salsa.debian.org/ci-team/autopkgtest/merge_requests/69 and once landed, will still have no effect unless autopkgtest is invoked with a '-a' option. So this change should be safe to land in your package despite this not being upstream in autopkgtest. (Closes: #946375) [ Felipe Sateler ] * Enable autospawn automatically on sysvinit systems. Instead of having a default configuration, make pulseaudio default to disabled, and then have a sysvinit service to reenable the autospawn setting (Closes: #923203) * Allow installing pulseaudio with elogind. Because we now autospawn with non-systemd, we can use the weaker guarantees provided by elogind (Closes: #923201) * Drop postinst snippet dealing with old upgrades. 5.0 is already in oldoldstable so no need to carry it anymore * Set upstream metadata fields: Name (from ./configure), Repository, Repository-Browse. Fixes: lintian: upstream-metadata-file-is-missing See-also: https://lintian.debian.org/tags/upstream-metadata-file-is-missing.html * Bump Standards-Version. No changes needed * Enable the systemd user units dynamically, not statically. Now that there is support for systemd --user in debhelper, lets use that to enable the user units instead of having a global link (Closes: #943999) -- Felipe Sateler Fri, 31 Jan 2020 09:24:15 -0300 Changes since the last upload: * Rebuild for buster-backports. Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Bug#951403: RFS: jcc/3.6-1 [ ITA] -- generator for a Python extension from Java classes (Python 3)
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "jcc" * Package name: jcc Version : 3.6-1 Upstream Author : Andi Vadja * URL : http://lucene.apache.org/pylucene/jcc/ * License : Apache * Vcs : https://salsa.debian.org/debian/jcc Section : oldlibs It builds those binary packages: python3-jcc - generator for a Python extension from Java classes (Python 3) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/jcc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/j/jcc/jcc_3.6-1.dsc Changes since the last upload: [ Emmanuel Arias ] * New upstream version 3.6 * New maintainer (Closes: #922568): - Add myself to Maintainer field on d/control. * Bump debhelper to 12 (from 9.2): - Update debhelper to debhelper-compat on d/control Build-Depends. * Update Vcs-* repository to salsa repository. * Add myself on debian/* files copyright on d/copyright. * Bump Standard-Version to 4.4.1 * d/control: add autopkgtest-pkg-python * Remove Python2 support. * d/control: Remove X-Python-Version for Python 2 * d/salsa-ci.yml: enable salsa-ci. * d/gbp.conf: add gbp.conf file. . [Ludovico Cavedon] * Fix jdk path with Java 9 (Closes: #875579). * Fall-back to client-mode JVM is the server-mode one is not available (Closes: #885955). * Refresh patches. * Create python-jcc and python3-jcc packages, and make jcc a transitional one. Expand the "default-jdk" symlink at build time, so the run-time dependency is on the correct JDK version. * Make sure to depend on the JRE package we built against. Do not link against libjava as it is not necessary. * Change priority extra to optional. * No longer remove JCC.egg-info/SOURCES.txt during clean. * Add lintian-overrides for JRE rpath (needed because libjvm.so does not have an SONAME). * Build library with hardening=+all hardening flags. Regards, -- Emmanuel Arias 0xFA9DEC5DE11C63F1.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Bug#951392: marked as done (RFS: sosreport/3.9-1 -- Set of tools to gather troubleshooting data from a system)
Your message dated Sun, 16 Feb 2020 03:47:36 +0100 with message-id <20200216024736.ga10...@angband.pl> and subject line Re: Bug#951392: RFS: sosreport/3.9-1 has caused the Debian Bug report #951392, regarding RFS: sosreport/3.9-1 -- Set of tools to gather troubleshooting data from a system 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.) -- 951392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951392 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 "sosreport": * Package name: sosreport Version : 3.9-1 Upstream Author : Bryn M. Reeves * URL : https://sos.readthedocs.io/en/latest/ * License : GPL-2+ * Vcs : https://github.com/sosreport/sos/ Section : admin It builds those binary packages: sosreport - Collect and package diagnostic and support data To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sosreport Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_3.9-1.dsc Changes since the last upload: * New 3.9 upstream release. - Improved human-readable archive naming and support for archive labels - Improved reporting of archive output and properties - Support for automatic uploading of report archives via FTP and HTTPS - Automatic PATH support on Ubuntu distributions - Improved policy performance - Improved service status collection API - 9 new plugins: cloud_init, convert2rhel, ebpf, fwupd, login, nginx, nvidia, openstack_tripleo - 6 obsolete plugins removed or merged into other plugins: katello, last, mrggrid, mrgmessg, satellite - Significant updates to 14 plugins: dlm, dnf, ceph, foreman, gluster, gnocchi, juju, kubernetes, logs, maas, networking, openvswitch, python, plugins - The openswan plugin was renamed to libreswan to reflect the active upstream project name - Updated Red Hat presets and new Cloud Forms preset - Updates to networking plugin namespace handling - Updates to the OVN plugins (ovn_central, ovn_host) - Kernel eBPF data consolidated in a single plugin Further release information and tarballs are available at: https://github.com/sosreport/sos/releases/tag/3.9 * Other specific modifications: - d/p/0001-skip-py2-only-tests.patch: Omit Python2 only unittests Regards, --- End Message --- --- Begin Message --- On Sat, Feb 15, 2020 at 09:22:42PM +, Eric Desrochers wrote: > * Package name: sosreport >Version : 3.9-1 > Changes since the last upload: > > * New 3.9 upstream release. > - Improved human-readable archive naming and support for archive labels > - Improved reporting of archive output and properties > - Support for automatic uploading of report archives via FTP and HTTPS > - Automatic PATH support on Ubuntu distributions > - Improved policy performance > - Improved service status collection API > - 9 new plugins: cloud_init, convert2rhel, ebpf, fwupd, login, nginx, > nvidia, openstack_tripleo > - 6 obsolete plugins removed or merged into other plugins: > katello, last, mrggrid, mrgmessg, satellite > - Significant updates to 14 plugins: dlm, dnf, ceph, foreman, gluster, > gnocchi, juju, kubernetes, logs, maas, networking, openvswitch, > python, plugins > - The openswan plugin was renamed to libreswan to reflect the active > upstream project name > - Updated Red Hat presets and new Cloud Forms preset > - Updates to networking plugin namespace handling > - Updates to the OVN plugins (ovn_central, ovn_host) > - Kernel eBPF data consolidated in a single plugin > > Further release information and tarballs are available at: > https://github.com/sosreport/sos/releases/tag/3.9 > > * Other specific modifications: > - d/p/0001-skip-py2-only-tests.patch: Omit Python2 only unittests The package still has a dependency on Python2. That's not a regression thus I've uploaded as-is, but you'd probably want to fix this. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can. ⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener. ⠈⠳⣄ A master species delegates.--- End Message ---
Bug#951369: marked as done (RFS: sachesi/2.0.4+ds-1 [ITP] -- BlackBerry 10 device utility)
Your message dated Sun, 16 Feb 2020 02:47:48 +0100 with message-id <20200216014748.ga9...@angband.pl> and subject line Re: Bug#951369: RFS: sachesi/2.0.4+ds-1 [ITP] -- BlackBerry 10 device utility has caused the Debian Bug report #951369, regarding RFS: sachesi/2.0.4+ds-1 [ITP] -- BlackBerry 10 device utility 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.) -- 951369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951369 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 "sachesi" * Package name: sachesi Version : 2.0.4+ds-1 Upstream Author : https://github.com/xsacha/Sachesi/issues * URL : https://github.com/xsacha/Sachesi * License : GPL-3 Section : comm It builds those binary packages: sachesi - BlackBerry 10 device utility To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sachesi Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sachesi/sachesi_2.0.4+ds-1.dsc Changes since the last upload: * Initial release (Closes: #787482) Regards, Bastian Germann --- End Message --- --- Begin Message --- On Sat, Feb 15, 2020 at 01:18:07PM +0100, Bastian Germann wrote: > * Package name: sachesi >Version : 2.0.4+ds-1 > Changes since the last upload: > >* Initial release (Closes: #787482) Hi! While I can't test the functionality, the packaging looks good. In NEW, thanks for your work! Meow. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ A white dwarf seeks a red giant for a binary relationship. ⠈⠳⣄--- End Message ---
Bug#951392: RFS: sosreport/3.9-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "sosreport": * Package name: sosreport Version : 3.9-1 Upstream Author : Bryn M. Reeves * URL : https://sos.readthedocs.io/en/latest/ * License : GPL-2+ * Vcs : https://github.com/sosreport/sos/ Section : admin It builds those binary packages: sosreport - Collect and package diagnostic and support data To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sosreport Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sosreport/sosreport_3.9-1.dsc Changes since the last upload: * New 3.9 upstream release. - Improved human-readable archive naming and support for archive labels - Improved reporting of archive output and properties - Support for automatic uploading of report archives via FTP and HTTPS - Automatic PATH support on Ubuntu distributions - Improved policy performance - Improved service status collection API - 9 new plugins: cloud_init, convert2rhel, ebpf, fwupd, login, nginx, nvidia, openstack_tripleo - 6 obsolete plugins removed or merged into other plugins: katello, last, mrggrid, mrgmessg, satellite - Significant updates to 14 plugins: dlm, dnf, ceph, foreman, gluster, gnocchi, juju, kubernetes, logs, maas, networking, openvswitch, python, plugins - The openswan plugin was renamed to libreswan to reflect the active upstream project name - Updated Red Hat presets and new Cloud Forms preset - Updates to networking plugin namespace handling - Updates to the OVN plugins (ovn_central, ovn_host) - Kernel eBPF data consolidated in a single plugin Further release information and tarballs are available at: https://github.com/sosreport/sos/releases/tag/3.9 * Other specific modifications: - d/p/0001-skip-py2-only-tests.patch: Omit Python2 only unittests Regards,
Bug#934478: marked as done (RFS: sane-backends/1.0.27-3.2+deb10u1 -- API library for scanners -- utilities)
Your message dated Sat, 15 Feb 2020 19:29:19 +0100
with message-id <40f931e5379aa35509be47081510ab526f4f84b7.camel@jff.email>
and subject line Re: RFS: sane-backends/1.0.27-3.2+deb10u1 -- API library for
scanners -- utilities
has caused the Debian Bug report #934478,
regarding RFS: sane-backends/1.0.27-3.2+deb10u1 -- API library for scanners --
utilities
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.)
--
934478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934478
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 "sane-backends"
Package name: sane-backends
Version : 1.0.28-1~experimental1
Version : 1.0.27-4~experimental1
Upstream Author : sane-de...@alioth-lists.debian.net
URL : http://www.sane-project.org
License : GPL-2+ with sane exception, GPL-2+, GPL-3+,
Artistic, LGPL-2.1+
Section : graphics
It builds those binary packages:
sane-utils - API library for scanners -- utilities
libsane-common - API library for scanners -- documentation and support files
libsane1 - API library for scanners
libsane-dev - API development library for scanners [development files]
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/sane-backends
Alternatively, one can download the package with dget using this
command:
dget -x
https://mentors.debian.net/debian/pool/main/s/sane-backends/sane-backends_1.0.28-1~experimental1.dsc
or from git
https://jff.email/cgit/sane-backends.git/?h=release%2Fexperimental%2F1.0.28-1_experimental1
Changes since the last upload:
* New upstream release.
- New debian/patches/0040-remove_git.patch to remove git access at
build time.
- Refresh patches:
+ debian/patches/0700-mk_reproducible_results.patch.
+ debian/patches/0710-sane-desc.c_debian_mods.patch.
+ debian/patches/0715-20-sane.hwdb_multi-arch.patch.
+ debian/patches/0725-fix_link_60-libsane_rule.patch.
+ debian/patches/0100-source_spelling.patch.
- Refresh symbols file.
- Refresh lintian overrides.
* debian/rules:
- Add --exclude=/sane/ to override_dh_makeshlibs-arch to generate
only public symbols (Closes: #911597).
- Don't install obsolete hal fdi file (Closes: #913282).
* Remove architecture dependent symbols files.
* Merge release 1.0.27-3.2 into source tree.
- I disagree the changes from 1.0.27-3.1.
- Thanks to John Paul Adrian Glaubitz for the bug fix.
* New debian/patches/0725-fix_link_60-libsane_rule.patch:
- Fix directory for 20-sane.hwdb (Closes: #916239).
* New debian/patches/0155-genesys_gl847.patch:
- Fix discolored bar on GL847 chip based scanners (Closes: #912603).
* Fix missing set device to group scanner (Closes: #918358);
- New debian/99-libsane.rules.
- debian/libsane.install: Install File into /etc/udev/rules.d/
- Change debian/TROUBLESHOOTING.Debian
* debian/sane-utils.config: Remove the RUN parameter in compliance with
Debian Policy Manual section 9.3.3.1 (Closes: #915197).
* debian/copyright:
- Add year 2019 for debian/*.
- Add missing Uploaders to debian/*.
- Refresh for the new upstream release.
* Fix the lintian warning "libsane: package-name-doesnt-match-sonames
libsane1":
- debian/control: rename package libsane to libsane1.
- debian/rules: Change filenames and directories from libsane to libsane1.
- Rename debian/99-libsane.rules to debian/99-libsane1.rules.
* Refresh debian/patches/0100-source_spelling.patch.
* New debian/libsane-common.lintian-overrides and
debian/libsane1.lintian-overrides to override false positive spelling-error.
* Fix autopkgtest.
* Migrate to debhelper 12:
- Change debian/compat to 12.
- Bump minimum debhelper version in debian/control to >= 12.
* Declare compliance with Debian Policy 4.4.0 (No changes needed).
* New debian/sane-utils.lintian-overrides to override false positive missing
init.d script.
* debian/control: Add Pre-Depends ${misc:Pre-Depends} to install invoke-rc.d.
* debian/watch: Rewrite for the new Gitlab directory layout.
* debian/libsane1.symbols: Add missing build depends package field.
Build with sbuild and pdebuild and the tests with lintian and piuparts
are ok:
+--+
| Summary
Bug#934478: RFS: sane-backends/1.0.27-3.2+deb10u1 -- API library for scanners -- utilities
Closed. New upstream release work. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old pgp Key: BE581B6E (revoked since 2014-12-31). Jörg Frings-Fürst D-54470 Lieser git: https://jff.email/cgit/ Threema: SYR8SJXB Wire: @joergfringsfuerst Skype:joergpenguin Ring: jff Telegram: @joergfringsfuerst My wish list: - Please send me a picture from the nature at your home. signature.asc Description: This is a digitally signed message part
Re: Advice on packaging new upstream releases.
On Saturday, February 15 2020, Inaki Malerba wrote: > Hi everyone! Hey Inaki, > I'm looking for some advice on how to fix some problems on 2 different > packages I've been trying to update with no luck so far. > > # python-icecream. [0][1] > > The new release includes a dependency to a very small repository [2] > that's not packaged. > > My first thought was to open an ITP and try to package it, but it turns > out to be a single python script and I'm not sure if it's reasonable to > create a whole package for that. > > Should I package the new dependency? The README[3] even suggests that > it's ok to copy that single file. Would it be OK if I patch it into my > package? It's not uncommon to see small Python packages out there, often with only a single file, like this one. IMO, you should go ahead and package it properly. Other packages might depend on it, and it seems like an easy package to make anyway. > # doit [4][5] > > The latest release of this package contains a huge change on the > documentation, which breaks the linting. It contains a lot of external > javascripts and stuff. > > As python-icecream, doit made a change to depend on a custom sphinx > theme that's not packaged but I managed to fix that patching it to use > the default theme[6]. > > Having changed the theme and fixed one of lintian suggestions (the > node-html5shiv one), there are still a lot of problems with the docs > package[7]. I even thought of removing the python-doit-doc package. This one is more complicated... Apparently upstream decided to write an index.html documentation page full of minified, non-Free JS: https://github.com/pydoit/doit/commit/e7717d705d60731f750f1e27e0f633c3d0502678 If you look at index.html's header, you'll see references to things under the _static/vendor directory, or links to fonts.googleapis.com. Both are problematic: https://github.com/pydoit/doit/blob/master/doc/index.html#L10-L26 We have almost everything packaged in Debian that is needed to replace these. You will have to remove the files from the tarball (using d/copyright's Files-Excluded, plus using +dfsg in the package's version). These are the replacements that already exist in Debian: libjs-bootstrap (for bootstrap.min.js) fonts-font-awesome (for font-awesome.min.css) fonts-roboto (for the googleapis.com Roboto font) We're missing packages for "bootstrap-select.min.css" and "owl.carousel". The good thing about "owl.carousel" is that python-doit ships the non-minified JS version, which means that you can minify it during build time. The problematic part is the "bootstrap-select.min.css" file, which is only shipped in its minified version. The ideal scenario would be to package bootstrap-select and then depend on it, but I don't think it's fair to make you go through this (the package seems a bit complicated, and packaging JS is not easy sometimes). Another "good enough" approach (IMO) would be to copy a version of "bootstrap-select.js" (non-minified) into python-doit's code (using a patch under d/patch, of course), and then minify it during the build. This is not very elegant, but solves the problem (it's similar to what you proposed above, for python-icecream). All in all, it will demand a bit of work, unfortunately. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Advice on packaging new upstream releases.
Hi everyone! I'm looking for some advice on how to fix some problems on 2 different packages I've been trying to update with no luck so far. # python-icecream. [0][1] The new release includes a dependency to a very small repository [2] that's not packaged. My first thought was to open an ITP and try to package it, but it turns out to be a single python script and I'm not sure if it's reasonable to create a whole package for that. Should I package the new dependency? The README[3] even suggests that it's ok to copy that single file. Would it be OK if I patch it into my package? # doit [4][5] The latest release of this package contains a huge change on the documentation, which breaks the linting. It contains a lot of external javascripts and stuff. As python-icecream, doit made a change to depend on a custom sphinx theme that's not packaged but I managed to fix that patching it to use the default theme[6]. Having changed the theme and fixed one of lintian suggestions (the node-html5shiv one), there are still a lot of problems with the docs package[7]. I even thought of removing the python-doit-doc package. What should I do here? Thanks in advance :) 0_ https://github.com/gruns/icecream 1_ https://salsa.debian.org/debian/python-icecream 2_ https://github.com/alexmojaki/executing 3_ https://github.com/alexmojaki/executing#installation 4_ https://github.com/pydoit/doit/ 5_ https://salsa.debian.org/debian/doit/ 6_ https://salsa.debian.org/debian/doit/blob/master/debian/patches/restore_docs_theme.diff 7_ https://salsa.debian.org/debian/doit/-/jobs/481358 -- - ina signature.asc Description: OpenPGP digital signature
Bug#951369: RFS: sachesi/2.0.4+ds-1 [ITP] -- BlackBerry 10 device utility
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "sachesi" * Package name: sachesi Version : 2.0.4+ds-1 Upstream Author : https://github.com/xsacha/Sachesi/issues * URL : https://github.com/xsacha/Sachesi * License : GPL-3 Section : comm It builds those binary packages: sachesi - BlackBerry 10 device utility To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sachesi Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sachesi/sachesi_2.0.4+ds-1.dsc Changes since the last upload: * Initial release (Closes: #787482) Regards, Bastian Germann
Re: I want to collaborate with materia-gtk-theme
Hi Roberto, On 2020-02-14T18:07-0400, Roberto De Oliveira wrote: Hi Everyone! I realized materia-gtk-theme could be easily update with latest upstream version, actually I did a test with gbp and installed on my computer and it's working just fine. I sent an email to Sagar Ippalpalli but I haven't received a response. How can I help with this package (and star a path to become my self into a Debian Contributor). I sent #945847 a few months ago, unfortunately it remained unanswered! As Sergio told you, I think at this point it’s quite safe to prepare an NMU. -- Saludos, Roberto De Oliveira Cheers, Vincent signature.asc Description: PGP signature
