Bug#972402: RFS: libphp-swiftmailer/6.2.3-1 [ITA] -- Swiftmailer, free feature-rich PHP mailer
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "libphp-swiftmailer": * Package name: libphp-swiftmailer Version : 6.2.3-1 Upstream Author : * URL : http://swiftmailer.org/ * License : Expat * Vcs : https://salsa.debian.org/php-team/pear/php-swiftmailer Section : php It builds those binary packages: php-swiftmailer - Swiftmailer, free feature-rich PHP mailer To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libphp-swiftmailer/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libp/libphp-swiftmailer/libphp-swiftmailer_6.2.3-1.dsc Changes since the last upload: libphp-swiftmailer (6.2.3-1) unstable; urgency=medium . [ Nicolas Roudaire ] * Imported upstream version 6.2.3 (Closes: #951591) * Upgrade Standards-Version to 4.5.0 * debian/control: Update debhelper-compat to 12 * debian/compat: Remove because of debhelper-compat in debian/control * Update debian/copyright * Add debian/upstream/metadata . [ Robin Gustafsson ] * Add pkg-php-tools dependency overrides * Change name of license from MIT to Expat * Remove unnecessary debian/dirs * Install docs instead of tests as documentation * Reformat files * Update maintainer info due to team adoption * Remove transitional package (Closes: #878656) * Clean up dependencies * Fix VCS URLs * Install an autoload.php file (Closes: #951605) * Bump debhelper-compat to 13 * Tweak gbp.conf * Run tests during build * Add autopkgtest tests -- Adoption into the PHP PEAR team was discussed with the current maintainer on the team's mailing list [1]. Please feel free to review and/or sponsor this even if you're not active within the team. All help is appreciated. [1]: https://alioth-lists.debian.net/pipermail/pkg-php-pear/2020-September/014730.html Regards, -- Robin Gustafsson
Bug#972407: RFS: mini-httpd/1.30-3 [QA] -- Small HTTP server
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "mini-httpd": * Package name: mini-httpd Version : 1.30-3 Upstream Author : [fill in name and email of upstream] * URL : https://www.acme.com/software/mini_httpd * License : BSD-2-clause * Vcs : https://salsa.debian.org/debian/mini-httpd Section : web It builds those binary packages: mini-httpd - Small HTTP server To access further information about this package, please visit the following URL: https://mentors.debian.net/package/mini-httpd/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/m/mini-httpd/mini-httpd_1.30-3.dsc Updated git repo: https://salsa.debian.org/Lorenzo.ru.g-guest/mini-httpd/-/tree/qa-1.30-3 Changes since the last upload: mini-httpd (1.30-3) unstable; urgency=medium . [ Lorenzo Puliti ] * QA upload. * Fix lintian error 'init-d script not starting the service': the service is now shipped as disabled with Sysv * Warn users of changes in /etc/default/mini-httpd with a NEWS file * Set rules-requires-root to 'binary-targets' * Add an experimental systemd native service: - do not start the service after install - run in foreground - use the conf file in /etc/ for other options - Same start sequence of other httpds (Apache2, Nginx..) * Bump Standards-Version to 4.5, no chages required * Bump dh-compat version to 13 * Merge the runscript from 'mini-httpd-run' package: - Add a Build-Dep on dh-runit>=2.9.0 - ship the runit service as disabled - Breaks and Replaces with 'mini-httpd-run' - ship a presubj file to easy work of QA * Update runit runscript: - use the 'invoke-run' interpreter - ship a default finish file - use the conf file in /etc instead of command line options (note that this way the server no longer run inside a chroot) * Sysv: add the syslog facility to LSB header: this is needed because the Sysv script logs to syslog by default . [ Jean ] * Update init.d script LSB Header with $network: otherwise mini-httpd starts too early during the boot sequence Regards, -- Lorenzo Puliti
Fortran issue solved but symbols issues (Was: Bug#957665: Fortran issue in paw (Was: paw: ftbfs with GCC-10))
Hi Andrius On Thu, Oct 15, 2020 at 03:34:15PM +0300, Andrius Merkys wrote: > > FFLAGS += -fallow-argument-mismatch Thanks a lot for the helpful hint which enabled me to do one step forward[1]. Unfortunately there are further errors: ... /usr/bin/ld: paw/cdf/shared/mlpdef.o:/build/paw-2.14.04.dfsg.2/build/pawlib/paw/cdf/mlpdef.c:155: multiple definition of `klnkaddr'; paw/cdf/shared/pawcdf.o:/build/paw-2.14.04.dfsg.2/build/pawlib/paw/cdf/pawcdf.c:155: first defined here /usr/bin/ld: warning: alignment 4 of symbol `pawch3_' in paw/ntuple/shared/c_decl.o is smaller than 16 in paw/code/shared/pawint3.o /usr/bin/ld: warning: size of symbol `hcfile_' changed from 12800 in paw/code/shared/hgetid.o to 4000 in paw/ntuple/shared/c_decl.o /usr/bin/ld: warning: size of symbol `pawc_' changed from 40004 in comis/code/shared/csdefn.o to 4 in paw/ntuple/shared/c_decl.o /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:31: multiple definition of `learn_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:31: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:40: multiple definition of `pat_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:40: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:19: multiple definition of `net_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:19: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:49: multiple definition of `divers_'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:49: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:92: multiple definition of `Hessian'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:92: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:91: multiple definition of `ExamplesIndex'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:91: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:90: multiple definition of `JacobianMatrix'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:90: first defined here /usr/bin/ld: paw/mlpfit/shared/mlp_inter.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:89: multiple definition of `Gamma'; paw/mlpfit/shared/mlp_gen.o:/build/paw-2.14.04.dfsg.2/src/pawlib/paw/mlpfit/mlp_gen.h:89: first defined here ... Any further hints are welcome Andreas. [1] https://salsa.debian.org/science-team/paw/-/commit/5b7695142d3580516168086feb3e97c2b1fac575 -- http://fam-tille.de
Re: Verify the library transition
On Tue, Sep 29, 2020 at 8:39 AM Andrey Rahmatullin wrote: > On Tue, Sep 29, 2020 at 08:30:33AM -0400, Tong Sun wrote: > > So `libgit2-dev` only shows up once in calligra's debian/control file. > You need to check actual dependencies of binary packages (e.g. by looking at > debs with dpkg-deb -f), not your debian/control. > And libgit2-dev is a development package, binaries will depend on the > package that contains the library itself. OK. I got: $ dpkg-deb -f calligrawords_3.2.1+dfsg-2_amd64.deb Depends | grep libgit2 || echo not found not found > > Can I safely say that all calligra packages are fine with libgit2-dev's new > > v1.0.0? > No. With the above result, can I safely say that calligrawords_3.2.1+dfsg-2_amd64.deb is not depending on libgit2 then? I"ve checked every calligra related packages and have *only* found: $ dpkg-deb -f calligra-gemini_3.2.1+dfsg-2_amd64.deb Depends calligra-libs (= 1:3.2.1+dfsg-2), calligra-gemini-data (>= 1:3.2.1+dfsg-2), calligrasheets (>= 1:3.2.1+dfsg), calligrastage (>= 1:3.2.1+dfsg), calligrawords (>= 1:3.2.1+dfsg), libc6 (>= 2.14), libgit2-28 (>= 0.26.0), libkf5configcore5 (>= 5.7.0), libkf5configwidgets5 (>= 5.7.0), libkf5coreaddons5 (>= 5.7.0), libkf5crash5 (>= 4.96.0), libkf5i18n5 (>= 5.7.0), libkf5iconthemes5 (>= 5.7.0), libkf5widgetsaddons5 (>= 5.7.0), libkf5xmlgui5 (>= 5.7.0), libqt5core5a (>= 5.14.1), libqt5gui5 (>= 5.8.0) | libqt5gui5-gles (>= 5.8.0), libqt5network5 (>= 5.14.1), libqt5qml5 (>= 5.0.2), libqt5quick5 (>= 5.6.1) | libqt5quick5-gles (>= 5.6.1), libqt5quickwidgets5 (>= 5.3.0), libqt5widgets5 (>= 5.3.0), libstdc++6 (>= 4.1.1) Thus, can I safely say that of all packages built out of calligra-3.2.1+dfsg, only calligra-gemini_3.2.1+dfsg-2 need to verify with library transition, and if it passes, then packages calligra-3.2.1+dfsg would pass as well? Finally, the most important one, I found that calligra-gemini_3.2.1+dfsg-2_amd64.deb was built with the old libgit2 (libgit2-28), not my latest libgit2-1.0, what was the problem for that? The d/control is not specifying a fixed version: grep libgit2 calligra-3.2.1+dfsg/debian/control libgit2-dev, So it should pick the latest version, right? Why is it not happening? One reason I can think of is that, my latest libgit2 is called libgit2-1.0 while the *old* one is called libgit2-28, which is in fact libgit2 v0.28.5+dfsg.1-1. Which one would debuild pick? Hmm... no quite, looking further into all those libgit2 related packages that I've already built, I saw mixed results: - $ dpkg-deb -f gir1.2-ggit-1.0_0.28.0.1-2_amd64.deb Depends gir1.2-glib-2.0, libgit2-glib-1.0-0 (>= 0.28.0.1) $ dpkg-deb -f golang-gopkg-libgit2-git2go.v28-dev_0.28.5-1_all.deb Depends pkg-config, libgit2-dev (>> 0.28~) $ dpkg-deb -f libgit2-glib-1.0-0-dbgsym_0.28.0.1-2_amd64.deb Depends libgit2-glib-1.0-0 (= 0.28.0.1-2) $ dpkg-deb -f libgit2-glib-1.0-0_0.28.0.1-2_amd64.deb Depends libc6 (>= 2.14), libgit2-28 (>= 0.28.1), libglib2.0-0 (>= 2.44.0) $ dpkg-deb -f libgit2-glib-1.0-dev_0.28.0.1-2_amd64.deb Depends gir1.2-ggit-1.0 (= 0.28.0.1-2), libgit2-glib-1.0-0 (= 0.28.0.1-2), libgit2-dev (>= 0.26.0), libglib2.0-dev (>= 2.44.0) $ dpkg-deb -f librust-libgit2-sys+https-dev_0.10.0-1_amd64.deb Depends librust-libgit2-sys-dev (= 0.10.0-1), librust-openssl-sys-0.9+default-dev $ dpkg-deb -f librust-libgit2-sys+libssh2-sys-dev_0.10.0-1_amd64.deb Depends librust-libgit2-sys-dev (= 0.10.0-1), librust-libssh2-sys-0.2+default-dev (>= 0.2.11-~~) $ dpkg-deb -f librust-libgit2-sys-dev_0.10.0-1_amd64.deb Depends librust-cc-1+default-dev (>= 1.0.42-~~), librust-cc-1+parallel-dev (>= 1.0.42-~~), librust-libc-0.2+default-dev, librust-libz-sys-1+default-dev (>= 1.0.22-~~), librust-pkg-config-0.3+default-dev (>= 0.3.7-~~), libgit2-dev - I.e., - some of them about built with libgit2-glib-1.0-0 - but some others are built with libgit2-28 (>= 0.28.1) - and some I just literally don't know, e.g., libgit2-dev (>> 0.28~) I.e., I still haven't figured out how to control the lib a package should links to. PS, here are all libgit2 related packages installed in my system, and their versions: libgit2-1.0:amd64_1.0.0+dfsg.1-1 libgit2-28:amd64_0.28.5+dfsg.1-1 libgit2-build-deps_1.0.0+dfsg.1-1 libgit2-dev:amd64_0.28.5+dfsg.1-1 libgit2-glib-1.0-0:amd64_0.28.0.1-2 libgit2-glib-1.0-dev:amd64_0.28.0.1-2 Please help. thanks!
Bug#961996: RFS: uriparser/0.9.4+dfsg-1 -- URI parsing library compliant with RFC 3986
Hello, Am Dienstag, den 02.06.2020, 08:02 +0300 schrieb Adrian Bunk: > Control: tags -1 moreinfo > > On Mon, Jun 01, 2020 at 08:29:42PM +0200, Jörg Frings-Fürst wrote: > > ... > > Changes since the last upload: > > ... > > - New debian/not-installed: > >+ Add all files of dh_missing errors. > > This would be followed by > > RFS: uriparser/0.9.4+dfsg-2 [RC] >* Fix ftbfs with dh_missing > * debian/not-installed: - Remove architecture specific path. > > ... > > - Add +dsfg staff. > > stuff > Typo corrected. The package is uploaded to mentors https://mentors.debian.net/package/uriparser/ and can downloaded https://mentors.debian.net/debian/pool/main/u/uriparser/uriparser_0.9.4+dfsg-1.dsc or from git https://jff.email/cgit/uriparser.git?h=release%2Fdebian%2F0.9.4%2Bdfsg-1 > > ... > > CU > > Jörg Frings-Fürst > > cu > Adrian 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
Speeding up test builds Re: Building a few of packages
(These are general hints, I haven't looked at your particular package.) Since the binary you want is arch-specific (_amd64 rather than _all), use dpkg-buildpackage --build=source,any. If the tests are long, you can skip them with DEB_BUILD_OPTIONS=nocheck. If you're trying to fix a test failure bug, it is often possible to manually run a single test afterwards. (How depends on what test framework upstream are using.) If you still have the previous build tree, or expect to need more than one additional build, consider using dpkg-buildpackage --no-pre-clean to re-use the parts that haven't changed. (Warning: this may not have the same result as a normal build.) Tong Sun wrote: The only way I can think of is to change d/control file, comment out all other packages. This probably won't be much faster: it's likely to build everything and just not package up the pieces you didn't ask for. To do only part of the actual build, you probably need to modify debian/rules and/or the upstream build system. But that will cause trouble to dpkg-buildpackage Changes under debian/ shouldn't. Changes to upstream files do need to be made into an actual patch (dpkg-source --commit), but this is not the same as committing to git. or gbp buildpackage, which requires me checking in those temporary changes before starting This gbp check can be turned off with --git-ignore-new.
Bug#972107: xscreensaver: looking for new sponsor
Hi Tormod, On Mon, 12 Oct 2020, at 20:50, Tormod Volden wrote: > My current sponsor for the xscreensaver package is very busy with more > important things so I am looking for someone to sponsor my > 5.44+dfsg1-1 release from > https://salsa.debian.org/debian/xscreensaver > > I also asked the previous sponsor, without luck. > > Hopefully someone that is also using xscreensaver and is willing to > continue in the future. A co-maintainer would also be welcome. > > But someone who just jumps in and uploads this release is also very > much welcome! > > Usually there are not many issues with my packages, so it shouldn't be > a big task. I have uploaded your package with a few minor changes. I used to use xscreensaver myself even though I no longer do, but I can help you with packaging and uploads, feel free to prod me next time. -- Cheers, Andrej
Bug#972107: xscreensaver: looking for new sponsor
Hi Tormod Looking at this URL, one thing doesn't fit, it's yours: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-requests;dist=unstable (Following the advice on http://mentors.debian.net/sponsor/rfs-howto ... No, that's a joke because it is a broken link, from If you specify where you saw that URL, you should be able to report it at the right place to have it fixed. https://wiki.debian.org/DebianMentorsFaq#How_do_I_get_a_sponsor_for_my_package.3F) I'm not able to find your xscreensaver package on mentors.debian.net. Would be great if you could do that... Once I get access to your source package, preferably a .dsc URL that I can use with dget. My current sponsor for the xscreensaver package is very busy with more important things so I am looking for someone to sponsor my 5.44+dfsg1-1 release from https://salsa.debian.org/debian/xscreensaver Just having had a short look at it, you claim in d/changelog to bump standards version and debhelper version. debhelper still is at 9, and d/compat is around. We're at 13. standards version should be 4.5.0. but shows me 4.1.4 at given salsa address. I doubt anyone would sponsor that. I also asked the previous sponsor, without luck. The explanation is above... probably among other things. Hopefully someone that is also using xscreensaver and is willing to continue in the future. A co-maintainer would also be welcome. But someone who just jumps in and uploads this release is also very much welcome! Debian stands for quality, so I doubt that'll happen at its current state. Usually there are not many issues with my packages, so it shouldn't be a big task. Best,
Building a few of packages
Hi, How to select only a few packages to build, out of a single source? The Calligra Suite, calligra-3.2.1+dfsg, builds 46 packages, and it took over 8 hours to build on my machine. Now I need to rebuild it, but need to rebuild only one out of the 46 packages -- calligra-gemini_3.2.1+dfsg-2_amd64.deb. What's the best way to do that? The only way I can think of is to change d/control file, comment out all other packages. But that will cause trouble to dpkg-buildpackage or gbp buildpackage, which requires me checking in those temporary changes before starting, while checking in the temporary change then revoke it later is something that I want to avoid. Please help. Thanks
Bug#972383: RFS: simple-scan/3.38.1-1 -- Simple Scanning Utility
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "simple-scan": Package name: simple-scan Version : 3.38.1-1 Upstream Author : Robert Ancell URL : https://gitlab.gnome.org/GNOME/simple-scan License : GPL-3+ Vcs : https://jff.email/cgit/simple-scan.git Section : gnome It builds those binary packages: simple-scan - Simple Scanning Utility To access further information about this package, please visit the following URL: https://mentors.debian.net/package/simple-scan/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/simple-scan/simple-scan_3.38.1-1.dsc or from git https://jff.email/cgit/simple-scan.git?h=release%2Fdebian%2F3.38.1-1 Changes since the last upload: simple-scan (3.38.1-1) unstable; urgency=medium . * New upstream release. 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
Bug#972373: RFS: dmidecode/3.3-1 -- SMBIOS/DMI table decoder
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dmidecode": Package name: dmidecode Version : 3.3-1 Upstream Author : dmidecode-de...@nongnu.org URL : https://nongnu.org/dmidecode/ License : GPL-2+ Vcs : https://jff.email/cgit/dmidecode.git/ Section : utils It builds those binary packages: dmidecode-udeb - SMBIOS/DMI table decoder (udeb) dmidecode - SMBIOS/DMI table decoder To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dmidecode/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dmidecode/dmidecode_3.3-1.dsc or from git https://jff.email/cgit/dmidecode.git/?h=release%2Fdebian%2F3.3-1 Changes since the last upload: dmidecode (3.3-1) unstable; urgency=medium . * New upstream release. - Remove upstream applied patches: + debian/patches/0140-Fix_scan_entry_point.patch + debian/patches/0005-build.patch + Refresh debian/patches/0001-hurd.patch. * Declare compliance with Debian Policy 4.5.0 (No changes needed). * Migrate to debhelper 13: - Bump debhelper-compat version in debian/control to = 13. * Remove unused debian/source/include-binaries. * Remove superficial test. * debian/copyright: - Add year 2020 to Jean Delvare and myself. 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
