Bug#1064092: RFS: bitwise/0.50-1 -- Interactive bitwise operation in ncurses
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "bitwise": * Package name : bitwise Version : 0.50-1 Upstream contact : Ramon Fried * URL : https://github.com/mellowcandle/bitwise * License : BSD-2-clause, GPL-3.0+, GFDL * Vcs : [fill in URL of packaging vcs] Section : science The source builds the following binary packages: bitwise - Interactive bitwise operation in ncurses To access further information about this package, please visit the following URL: https://mentors.debian.net/package/bitwise/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/b/bitwise/bitwise_0.50-1.dsc Changes since the last upload: bitwise (0.50-1) unstable; urgency=medium . * Bump to version 0.50 Enhancements: - Add r command to reverse endianness (@tianrui-wei) - Allow shortening of commands (@soleen) Bug Fixes: - Disable mouse events in interactive command mode - Fix backward key not working in some terminals - Fix divide by zero crash - Fit bit function overflow (@soleen) * debian: update to standards version: 4.6.2 * debian: Change build-depends (debhelper-compat to debhelper) * debian: Update copyright year * debian: Fix debian watch regex Regards, -- Ramon Fried
Bug#1064087: RFS: asn/0.75.3-1 [ITP] -- network OSINT CLI ASN, RPKI, BGP, Geo, Recon, Trace
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "asn": * Package name : asn Version : 0.75.3-1 Upstream contact : Adriano nitefood * URL : https://github.com/nitefood/asn/ * License : Expat * Vcs : https://salsa.debian.org/marcos.rcarvalho/asn Section : net The source builds the following binary packages: asn - network OSINT CLI ASN, RPKI, BGP, Geo, Recon, Trace To access further information about this package, please visit the following URL: https://mentors.debian.net/package/asn/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/a/asn/asn_0.75.3-1.dsc Changes for the initial release: asn (0.75.3-1) unstable; urgency=medium . * Initial release. (Closes: #1064033) Regards, -- Marcos Rodrigues de Carvalho (aka oday)
Bug#1064075: marked as done (RFS: openbox/3.6.1-12 [RC] -- standards-compliant, fast, light-weight and extensible window manager)
Your message dated Fri, 16 Feb 2024 23:16:53 +0100 with message-id and subject line Re: RFS: openbox/3.6.1-12 [RC] -- standards-compliant, fast, light-weight and extensible window manager has caused the Debian Bug report #1064075, regarding RFS: openbox/3.6.1-12 [RC] -- standards-compliant, fast, light-weight and extensible window manager 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.) -- 1064075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "openbox": * Package name : openbox Version : 3.6.1-12 Upstream contact : Dana Jansens * URL :http://www.openbox.org * License : GPL-2+, GPL-3+ * Vcs :https://github.com/mati75/openbox-debian Section : x11 The source builds the following binary packages: openbox - standards-compliant, fast, light-weight and extensible window manager libobt2v5 - parsing library for openbox libobrender32v5 - rendering library for openbox themes openbox-dev - development files for the openbox window manager gnome-panel-control - command line utility to invoke GNOME panel run dialog/menu openbox-gnome-session - command line utility to run Openbox as GNOME session openbox-kde-session - command line utility to run Openbox as KDE SC session To access further information about this package, please visit the following URL: https://mentors.debian.net/package/openbox/ Alternatively, you can download the package with 'dget' using this command: dget -xhttps://mentors.debian.net/debian/pool/main/o/openbox/openbox_3.6.1-12.dsc Changes since the last upload: openbox (3.6.1-12) unstable; urgency=medium . * Drop useless html docs about compiling. * Add gnome-settings-daemon, gnome-panel, gnome-flashback to openbox-gnome-session depends. (Closes: #1050946) Regards, -- Mateusz Łukasik --- End Message --- --- Begin Message --- Thanks for the update!--- End Message ---
Re: Question on why package was rebuilt
Hi On 2024-02-16 21:32:49 +0100, Jérémy Lal wrote: > When a package is uploaded to NEW, you have to upload both the source > > and binary package(s) for review. After the package is accepted, the > > buildds auto-build for any other architectures that don't already have > > a binary package. Migration policy requires all packages to be built on > > official buildds from their source package[1]. Since the amd64 binary > > package already existed from the upload to NEW, it wouldn't be auto- > > built and would block migration of your package to testing. > > > > This isn't what happened, I suppose, since we all debian maintainers need > to do source-only uploads after a package has been accepted through the NEW > process. > Unless I'm mistaken, that source-only upload cannot be replaced by a > binNMU, can it ? > What happened is more likely to be a standard rebuild against a new version > of a dependent library. A binNMU is enough if the source package only builds architecture dependent packages. If Architecture: all packages are involved, a source only upload is required. Cheers -- Sebastian Ramacher
Re: Question on why package was rebuilt
Le ven. 16 févr. 2024 à 04:03, Mathias Gibbens a écrit : > On Thu, 2024-02-15 at 16:20 -0800, Loren M. Lang wrote: > > Hello, > > > > I recently had a package sponsors and entered into unstable called tiv. > > It can be seen here: > > > > https://packages.debian.org/sid/tiv > > > > Everything went OK, but I see that the amd64 arch package appears to > > have been re-built for some reason. It's version is showing up with a > > +b1. I am curious if there is some long to indicate what the issue might > > have been that led to a rebuild. Could there have been a compilation > > issue or other things I should be concerned about or is it likely > > something harmless? Is there a log for this case? > > There's no cause for concern -- it's a normal part of a new package > entering the archive. > Indeed... When a package is uploaded to NEW, you have to upload both the source > and binary package(s) for review. After the package is accepted, the > buildds auto-build for any other architectures that don't already have > a binary package. Migration policy requires all packages to be built on > official buildds from their source package[1]. Since the amd64 binary > package already existed from the upload to NEW, it wouldn't be auto- > built and would block migration of your package to testing. > This isn't what happened, I suppose, since we all debian maintainers need to do source-only uploads after a package has been accepted through the NEW process. Unless I'm mistaken, that source-only upload cannot be replaced by a binNMU, can it ? What happened is more likely to be a standard rebuild against a new version of a dependent library. The "+b1" indicates a binBMU was performed[2,3]. If you look at the > buildd logs (https://buildd.debian.org/status/package.php?p=tiv), > you'll see the relevant changelog entry for the amd64 package: "Rebuild > on buildd". > A binNMU, but right. > > Mathias > > [1] -- > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#source-and-binary-uploads > [2] -- > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#source-nmus-vs-binary-only-nmus-binnmus > [3] -- > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#recompilation-or-binary-only-nmu >
Bug#1064078: RFS: smplayer/23.12.0+ds0-1 -- Complete front-end for MPlayer and mpv
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "smplayer": * Package name : smplayer Version : 23.12.0+ds0-1 Upstream contact : Ricardo Villalba * URL :https://smplayer.sourceforge.net/ * License : Expat, BSD-2-clause, LGPL-2.1+, LGPL-2+, BSD-3-clause, CC0-1.0, GPL-2+ * Vcs :https://salsa.debian.org/multimedia-team/smplayer Section : video The source builds the following binary packages: smplayer - Complete front-end for MPlayer and mpv smplayer-l10n - Complete front-end for MPlayer and mpv - translation files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/smplayer/ Alternatively, you can download the package with 'dget' using this command: dget -xhttps://mentors.debian.net/debian/pool/main/s/smplayer/smplayer_23.12.0+ds0-1.dsc Changes since the last upload: smplayer (23.12.0+ds0-1) unstable; urgency=medium . * New upstream release. (Closes: #1062700) * Add qtdeclarative5-dev to the dependencies. Regards, -- Mateusz Łukasik
Bug#1064077: RFS: qt5ct/1.8-1 -- Qt5 Configuration Utility
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "qt5ct": * Package name : qt5ct Version : 1.8-1 Upstream contact : [fill in name and email of upstream] * URL :https://sourceforge.net/projects/qt5ct/ * License : BSD-2-clause * Vcs :https://salsa.debian.org/qt-kde-team/extras/qt5ct Section : utils The source builds the following binary packages: qt5ct - Qt5 Configuration Utility To access further information about this package, please visit the following URL: https://mentors.debian.net/package/qt5ct/ Alternatively, you can download the package with 'dget' using this command: dget -xhttps://mentors.debian.net/debian/pool/main/q/qt5ct/qt5ct_1.8-1.dsc Changes since the last upload: qt5ct (1.8-1) unstable; urgency=medium . * New upstream release. * Remove patches included upstream. * Bump Standards-Version to 4.6.2, no changes needed. * Update d/copyright. * Add d/clean for fix fails to build source after successful build. (Closes: #1045559) * d/control: Remove build depends on obsolete package. Regards, -- Mateusz Łukasik
Bug#1064076: RFS: gxkb/0.9.5-1 -- X11 keyboard indicator and switcher
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "gxkb": * Package name : gxkb Version : 0.9.5-1 Upstream contact : [fill in name and email of upstream] * URL :https://zen-tools.github.io/gxkb * License : PERMISSIVE, GAP, GPL-2+, BSD-3-clause * Vcs :https://github.com/mati75/gxkb.git Section : x11 The source builds the following binary packages: gxkb - X11 keyboard indicator and switcher To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gxkb/ Alternatively, you can download the package with 'dget' using this command: dget -xhttps://mentors.debian.net/debian/pool/main/g/gxkb/gxkb_0.9.5-1.dsc Changes since the last upload: gxkb (0.9.5-1) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on libxklavier-dev. . [ Mateusz Łukasik ] * New upstream release. * Change from repack script to Files-Excluded in d/copyright. * Update d/watch. * Update d/copyright. Regards, -- Mateusz Łukasik
Bug#1064075: RFS: openbox/3.6.1-12 [RC] -- standards-compliant, fast, light-weight and extensible window manager
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "openbox": * Package name : openbox Version : 3.6.1-12 Upstream contact : Dana Jansens * URL :http://www.openbox.org * License : GPL-2+, GPL-3+ * Vcs :https://github.com/mati75/openbox-debian Section : x11 The source builds the following binary packages: openbox - standards-compliant, fast, light-weight and extensible window manager libobt2v5 - parsing library for openbox libobrender32v5 - rendering library for openbox themes openbox-dev - development files for the openbox window manager gnome-panel-control - command line utility to invoke GNOME panel run dialog/menu openbox-gnome-session - command line utility to run Openbox as GNOME session openbox-kde-session - command line utility to run Openbox as KDE SC session To access further information about this package, please visit the following URL: https://mentors.debian.net/package/openbox/ Alternatively, you can download the package with 'dget' using this command: dget -xhttps://mentors.debian.net/debian/pool/main/o/openbox/openbox_3.6.1-12.dsc Changes since the last upload: openbox (3.6.1-12) unstable; urgency=medium . * Drop useless html docs about compiling. * Add gnome-settings-daemon, gnome-panel, gnome-flashback to openbox-gnome-session depends. (Closes: #1050946) Regards, -- Mateusz Łukasik
Bug#1064074: RFS: jgmenu/4.4.1-2 -- Simple X11 menu
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "jgmenu": * Package name : jgmenu Version : 4.4.1-2 Upstream contact : Johan Malm * URL :https://jgmenu.github.io/ * License : LGPL-3+, Expat, GPL-2, LGPL-2+, GPL-2+ * Vcs :https://github.com/mati75/jgmenu Section : x11 The source builds the following binary packages: jgmenu - Simple X11 menu jgmenu-xfce4-panel-applet - xfce4-panel applet for jgmenu To access further information about this package, please visit the following URL: https://mentors.debian.net/package/jgmenu/ Alternatively, you can download the package with 'dget' using this command: dget -xhttps://mentors.debian.net/debian/pool/main/j/jgmenu/jgmenu_4.4.1-2.dsc Changes since the last upload: jgmenu (4.4.1-2) unstable; urgency=medium . [ Debian Janitor ] * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse. . [ Mateusz Łukasik ] * Backport upstream changes related to fix working with xfce4-panel. (Closes: #1063667) * Bump Standards Version to 4.6.2. * Add python3-gi, x11-xserver-utils to depends. Regards, -- Mateusz Łukasik
Bug#1060038: RFS: gtklock-userinfo-module/2.1.0-1 [ITP] -- user info module for gtklock
On Fri, 05 Jan 2024 12:13:29 +0800 Maytham Alsudany
wrote:
> Package: sponsorship-requests
> Severity: wishlist
> X-Debbugs-Cc: werdah...@riseup.net
>
> Dear mentors,
>
> I am looking for a sponsor for my package "gtklock-userinfo-module":
>
> * Package name : gtklock-userinfo-module
> Version : 2.1.0-1
> Upstream contact :
https://github.com/jovanlanik/gtklock-userinfo-module/issues
> * URL :
https://github.com/jovanlanik/gtklock-userinfo-module
> * License : GPL-3+
> * Vcs :
https://salsa.debian.org/Maytha8/gtklock-userinfo-module
> Section : misc
>
> The source builds the following binary packages:
>
> gtklock-userinfo-module - user info module for gtklock
>
> To access further information about this package, please visit the
following URL:
>
> https://mentors.debian.net/package/gtklock-userinfo-module/
>
> Alternatively, you can download the package with 'dget' using this
command:
>
> dget -x
https://mentors.debian.net/debian/pool/main/g/gtklock-userinfo-module/gtklock-userinfo-module_2.1.0-1.dsc
>
> Changes for the initial release:
>
> gtklock-userinfo-module (2.1.0-1) unstable; urgency=medium
> .
> * Initial release. (Closes: #1059901)
>
> Kind regards,
> Maytham
Hi Maytham,
looks good so far.
Two minor nitpicks I spotted: The build dependency on pkg-config should
be changed to pkgconf as that package was renamed some time ago. Also,
the Section: in d/control should be x11 since it is display-server related.
Furthermore, as the upstream readme states, the dependency on gtklock
should probably be versioned like this in d/control: gtklock (>=
${binary:Version}), ( see Debian policy § 7.1).
Personal recommendation: look into setting up you repo DEP-14 style (and
possible under the debian/ umbrella) as this will make maintaining in
the long run easier imho.
best,
werdahias
Bug#1052138: RFS: ukui-kwin/5.27.5-1 [ITP] -- UKUI window manager gl utils library
Hi, Since this package is a fork of kwin, would you mind to elaborate some technical questions: * Which version of the original kwin is used? * What is missing from the original kwin and why is a fork needed? * What changes have been made based on the original kwin? Also, it would be nice to mention this is a fork somewhere, rather than using a quick sed script to replace kwin to ukui-kwin everywhere. Thanks, Aron
Bug#1052597: RFS: libkysdk-base/2.2.0.1-1 -- common files for kylin sdk base library
Hi, It appears the included symbols file isn't complete and lintian complains: E: libkysdk-base: symbols-file-contains-current-version-with-debian-revision on symbol _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEE10json_value7destroyENS_6detail7value_tE@Base and 84 others (libkydiagnostics.so.1) [symbols] I: libkysdk-base: symbols-file-missing-build-depends-package-field libkydiagnostics.so.1 [symbols] Looking through the build log, dpkg-gensymbols has emitted some warnings: dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libkysdk-base/DEBIAN/symbols doesn't match completely debian/libkysdk-base.symbols --- debian/libkysdk-base.symbols (libkysdk-base_2.2.0.1-1_amd64) +++ dpkg-gensymbolsiEEcLA 2024-02-16 09:59:46.896778987 + @@ -18,6 +18,91 @@ _ZN3kdk11BuriedPointC2Ev@Base 2.2.0.1 _ZN3kdk11BuriedPointD1Ev@Base 2.2.0.1 _ZN3kdk11BuriedPointD2Ev@Base 2.2.0.1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEE1 0json_value7destroyENS_6detail7value_tE@Base 2.2.0.1-1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEEC 1EDn@Base 2.2.0.1-1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEEC 2EDn@Base 2.2.0.1-1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEED 1Ev@Base 2.2.0.1-1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEED 2Ev@Base 2.2.0.1-1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEEi xERKS8_@Base 2.2.0.1-1 + _ZN8nlohmann10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES2_IhSaIhEEEi xIKcEERSC_PT_@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_s erializerES4_IhSaIhE12dump_escapedERKSA_b@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_s erializerES4_IhSaIhE12dump_integerIhLi0EEEvT_@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES4_IhSaIhE12dump_integerIlLi0EEEvT_@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES4_IhSaIhE12dump_integerImLi0EEEvT_@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES4_IhSaIhE4dumpERKSE_bbjj@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES4_IhSaIhED1Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail10serializerINS_10basic_jsonISt3mapSt6vectorNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEblmdSaNS_14adl_serializerES4_IhSaIhED2Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail10type_errorD0Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail10type_errorD1Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail10type_errorD2Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail21output_string_adapterIcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc15write_characterEc@Base 2.2.0.1-1+ _ZN8nlohmann6detail21output_string_adapterIcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc16write_charactersEPKcm@Base 2.2.0.1-1 + _ZN8nlohmann6detail21output_string_adapterIcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD0Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail21output_string_adapterIcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD1Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail21output_string_adapterIcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcD2Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail8to_charsIdEEPcS2_PKcT_@Base 2.2.0.1-1 + _ZN8nlohmann6detail9dtoa_impl13format_bufferEPc@Base 2.2.0.1-1 + _ZN8nlohmann6detail9dtoa_impl16grisu2_digit_genEPcRiS3_NS1_5diyfpES4_S4_@Base 2.2.0.1-1 + _ZN8nlohmann6detail9dtoa_impl18compute_boundariesIdEENS1_10boundariesET_@Base 2.2.0.1-1 + _ZN8nlohmann6detail9dtoa_impl6grisu2IdEEvPcRiS4_T_@Base 2.2.0.1-1 + _ZN8nlohmann6detail9exception4nameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 2.2.0.1-1 + _ZN8nlohmann6detail9exceptionD0Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail9exceptionD1Ev@Base 2.2.0.1-1 + _ZN8nlohmann6detail9exceptionD2Ev@Base 2.2.0.1-1 + _ZNK8nlohmann10basic_jsonIS
