Proper suffix to repack a tarball with doxygen generated docs
Hello, I'm the maintainer of the lwip package. The orig tarball includes some doxygen generated files, that trigger the lintian "source-is-missing" error[1]. I'm going to repack the tarball to remove those files, but I'm not sure about which suffix should I use. Should I use "dfsg", b/c the orig includes some minified JS that are not readable nor modifiable? Is "ds" more appropriate for this case? or any other? Thanks! [1] https://lintian.debian.org/maintainer/jlle...@member.fsf.org.html#lwip
Bug#947409: RFS: clp/1.17.3+repack1-2 -- Coin-or linear programming solver
so it checks for __i386__ which is not defined on amd64 (nor x32). There are many defines which would be enough; you can for example check for: #elif defined(__i386__) || defined(__x86_64__) Also, it could be nice to keep the optimized code on armhf as well, which would make the ARM line: #elif defined(__ARM_FEATURE_SIMD32) || defined(__ARM_NEON) Currently, the code _does_ compile but is slow on any arch other than arm64 and i386. And not many people run scientific code on either. ok, I've updated the patch as you suggested. I hope it is correct. I uploaded it on mentors again with the same version number. Håvard
Multiple Profiles in a single build-simple-cdd build
Hi mentors, Can build-simple-cdd build a CD using multiple profiles using .conf file? I managed to build a custom CD version under a single profile using a local working directory. However, I failed many times with merging multiple profiles like: 1. First attempt (using space) profiles="custom util" auto_profiles="custom" dist="stable" export CONTRIB=1 export NONFREE=1 mirror_components="main contrib non-free" 2. Second attempt (using comma) profiles="custom,util" auto_profiles="custom" dist="stable" export CONTRIB=1 export NONFREE=1 mirror_components="main contrib non-free" Both profiles has their independent .packages. The custom is responsible for installing ufw (which both did) while util.packages is responsible for installing tree (which both failed). I'm aware default.profiles will always get included so there must be a way. Man pages does not explain much either. https://manpages.debian.org/buster/simple-cdd/simple-cdd.1.en.html Please shed some light. Thanks in adv. Regards, Holloway If you are not the intended recipient, please contact the sender immediately and delete all copies. The sender holds zero liability for any damages caused. If the content is digitally and cryptographically signed/encrypted by GNU Privacy Guard (GPG) key, please seek out the public key with the sender email at: https://pgp.mit.edu
Re: Please help for Upstream package
Any update for me. we will l10n + keyboard support for Next Version of Debian. On Tue, Sep 3, 2019 at 12:47 AM Ko Ko Ye` wrote: > Hi Sir / Madam > > I am Ko Ko Ye, Debian Fan and Ubuntu Team Leader at Myanmar. > > I am supporting debian base DFSG software. > > locales my_MM, shn_MM > [1] [2] > > keyboard "my" and "zg" xkb > xkeyboard 2.24 [3] > > ibus-table-myanmar > ibus-table-burmese > ibus-table-zawgyi > [4] > > ibus-keymagic-* > [5] > > now I am port to > fonts-myanmar [6] (aka) ttf-myanmar-fonts package > > who can sponsor or check fonts-myanmar package? #939174 [7] > > with regards. > > [1] https://launchpad.net/~ubuntu-l10n-my > [2] https://launchpad.net/~ubuntu-l10n-shn > [3] https://www.freedesktop.org/wiki/Software/XKeyboardConfig/ v2.24 > [4] https://launchpad.net/ibus-table-burmese/ > https://mentors.debian.net/package/ibus-table-myanmar > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939173 > [5] https://keymagic.net > https://mentors.debian.net/package/ibus-keymagic > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939176 > [6] https://mentors.debian.net/package/fonts-myanmar > [7] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939174 > > -- > > with regards *Ko Ko Ye`* > > +95 97989 22022 > +95 94500 22022 > +95 9731 47907 > kokoye2...@gmail.com > kokoye2...@ubuntu.com > > skype: kokoye2007 > jitsi: kokoye2007 > > http://ubuntu-mm.net > http://wiki.ubuntu.com/kokoye2007 > http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm > -- with regards *Ko Ko Ye`* +95 97989 22022 +95 94500 22022 +95 9731 47907 kokoye2...@gmail.com kokoye2...@ubuntu.com skype: kokoye2007 jitsi: kokoye2007 http://ubuntu-mm.net http://wiki.ubuntu.com/kokoye2007 http://wiki.ubuntu.com/MyanmarTeam http://loco.ubuntu.com/teams/ubuntu-mm
RFS: kt-update/0.18.11 -- lightweight distribution management
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "kt-update" * Package name: kt-update Version : 0.18.11 Upstream Author : Jean-Jacques Brucker * URL : https://github.com/jbar/kt-update * License : GPL-2.0 * Vcs : None Section : admin It builds those binary packages: kt-update - lightweight distribution management To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kt-update Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kt-update/kt-update_0.18.11.dsc This tools was initially of fork of cron-apt. It has since been completely rewrite. AUTHORS files has then been cleaned, with the participation of the cron-apt main developer : Ola Lundqvist. It aims to facilitate installed configurations administration (and avoid to deal with some FrankenDebian or FrankenGauSSIan). It may replace cron-apt, enhance tasksel, and provide extra features. The main feature is to manage an apt source.list which may contain extra directives. Almost all of kt-update's features could (and should IMHO) be provided by apt. But it seemed more easy to me write such features from cron-apt sources, than to fork apt (and maybe contribute later). Can we keep the source on github, or should I push it on salsa.debian.org ? Regards, pgpS6EapaWbLd.pgp Description: OpenPGP digital signature
Bug#947598: RFS: libcommoncpp2/1.8.1-8 [QA] [RC] -- Header files and static libraries for Common C++ "2"
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "libcommoncpp2" * Package name: libcommoncpp2 Version : 1.8.1-8 Upstream Author : [fill in name and email of upstream] * URL : http://www.gnu.org/software/commoncpp/ * License : GPL-2 * Vcs : https://salsa.debian.org/pkg-voip-team/libcommoncpp2 Section : devel It builds those binary packages: libcommoncpp2-dev - Header files and static libraries for Common C++ "2" libccgnu2-1.8-0v5 - GNU package for creating portable C++ programs libcommoncpp2-doc - Documentation files for Common C++ "2" To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcommoncpp2 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcommoncpp2/libcommoncpp2_1.8.1-8.dsc Changes since the last upload: * QA upload. * Fix ftbfs with gcc-9. (Closes: #925739) * Update Standards-Version to 4.4.1 Note: I am not having permission to push to the repo. The changes are also available at 'debian/sid' branch of: https://salsa.debian.org/sudip-guest/libcommoncpp2 Do I need to open a merge request to have the changes pushed in the repo? -- Regards Sudip
Bug#947600: RFS: trace-cmd/2.8.3-4 -- Utility for retrieving and analyzing function tracing in the kernel
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "trace-cmd" * Package name: trace-cmd Version : 2.8.3-4 Upstream Author : Steven Rostedt * URL : http://kernelshark.org/ * License : GPL-2 * Vcs : https://github.com/sudipm-mukherjee/trace-cmd.git Section : devel It builds those binary packages: trace-cmd - Utility for retrieving and analyzing function tracing in the kernel kernelshark - Utilities for graphically analyzing function tracing in the kernel. To access further information about this package, please visit the following URL: https://mentors.debian.net/package/trace-cmd Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/t/trace-cmd/trace-cmd_2.8.3-4.dsc Changes since the last upload: * Add dependency for mipsel Note: trace-cmd/2.8.3-3 was failing to build in mipsel. Please build on a mipsel system to verify it builds. Though Adam has already tested it, but there is no harm in testing again to check I have not messed up. My access request to eller (mipsel) is still pending, so I couldnot test it. -- Regards Sudip
Bug#947550: RFH: salsa.debian.org/debian/dbab
Pls help. Thanks -- Forwarded message - From: Tong Sun Date: Fri, Dec 27, 2019 at 10:06 PM Subject: RFH: salsa.debian.org/debian/dbab To: Debian Bug Tracking System Package: wnpp Severity: normal I've created/updated the salsa repo at: https://salsa.debian.org/debian/dbab For the package of https://tracker.debian.org/pkg/dbab The reason that I’m asking for reviewing is that, - this is the first time that I created a salsa project all by myself - also, this is the first time that I am doing the packaging and uploading all by myself The package was tested on both gbp and sbuild (http://paste.debian.net/1122767/). It's also lintian-clean. And I’ve done my best to fix anything I can. However, a second pair of eyes, i.e., any kind of reviews and suggestions are appreciated. Thanks Tong
Bug#947610: RFS: shotwell/0.30.7-2 -- digital photo organizer
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "shotwell" Package name: shotwell Version : 0.30.7-2 Upstream Author : Jim Nelson URL : https://wiki.gnome.org/Apps/Shotwell License : LGPL-2.1 Vcs : https://jff.email/cgit/shotwell.git Section : gnome It builds those binary packages: shotwell - digital photo organizer shotwell-common - digital photo organizer - common files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/shotwell Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/shotwell/shotwell_0.30.7-2.dsc or from git: https://jff.email/cgit/shotwell.git/?h=release%2Fdebian%2F0.30.7-2 Changes since the last upload: * debian/control: Remove outdated gnome-doc-utils from Build-Depends (Closes: #945141, #945294). * Switch to debhelper-compat: - debian/control: Replace debhelper with debhelper-compat. - Remove debian/compat. The build with sbuild --no-arch-all && sbuild --no-arch-any && sbuild and pdebuild and the tests with Lintain are ok. Piuparts fails about "package purging left files on system" mostly from a mime package. +--+ | Summary | +--+ Build Architecture: amd64 Build Type: full Build-Space: 250376 Build-Time: 85 Distribution: sid Host Architecture: amd64 Install-Time: 343 Job: /data/entwicklung/linux/debian/shotwell/shotwell_0.30.7-2.dsc Lintian: info Machine Architecture: amd64 Package: shotwell Package-Time: 440 Piuparts: fail Source-Version: 0.30.7-2 Space: 250376 Status: successful Version: 0.30.7-2 Finished at 2019-12-28T12:35:21Z Build needed 00:07:20, 250376k disk space 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#947611: RFS: simple-scan/3.34.2-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.34.2-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.34.2-1.dsc or from git: https://jff.email/cgit/simple-scan.git/?h=release%2Fdebian%2F3.34.2-1 Changes since the last upload: * New upstream release. * Switch to debhelper-compat: - debian/control: change to debhelper-compat (=12). - remove debian/compat. * Declare compliance with Debian Policy 4.4.1.2 (No changes needed). * debian/control: Switch to Rules-Requires-Root: No. The build with sbuild and pdebuild and the tests with Lintain are ok. Pi uparts fails about "package purging left files on system" mostly from a mime package. +--+ | Summary | +--+ Build Architecture: amd64 Build Type: full Build-Space: 26044 Build-Time: 34 Distribution: sid Host Architecture: amd64 Install-Time: 281 Job: /data/entwicklung/linux/debian/simple-scan/simple-scan_3.34.2-1.dsc Lintian: info Machine Architecture: amd64 Package: simple-scan Package-Time: 328 Piuparts: fail Source-Version: 3.34.2-1 Space: 26044 Status: successful Version: 3.34.2-1 Finished at 2019-12-28T14:32:58Z Build needed 00:05:28, 26044k disk space 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#947622: RFS: python-pyperclip/1.7.0-1 [QA] -- Cross-platform clipboard module for Python3
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-pyperclip" * Package name: python-pyperclip Version : 1.7.0-1 Upstream Author : * URL : https://github.com/asweigart/pyperclip * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/python-pyperclip Section : python It builds those binary packages: python3-pyperclip - Cross-platform clipboard module for Python3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-pyperclip Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-pyperclip/python-pyperclip_1.7.0-1.dsc Changes since the last upload: * QA upload * New upstream version 1.7.0 * Clean up, after python2 removal * Change to debhelper-compat in debian/control * Reformat dependencies in debian/control * Change python3-qt4 to python3-pyqt5 as a possible runtime-dependency. * Change python-pytest to python3-pytest * Bump debhelper to 12 * Update Standards-Version to 4.4.1 * Add Rules-Requires-Root * Rebase patch * Add salsa CI Can the sponsor also give me access to the git repository? Thanks, Regards, Håvard
Debian source search by file name
Hi, Is it possible to do Debian source search by file name? I wanted to see examples of overriding debian-watch-does-not-check-gpg-signature in debian/source/lintian-overrides files, so I did: https://codesearch.debian.net/search?q=path%3Adebian%2Fsources%2Flintian-overrides https://codesearch.debian.net/search?q=gpg+signature+path%3Adebian%2Fsources%2Flintian-overrides But none gave results I want. Both say: . . . had no results. Please read the FAQ to make sure your syntax is correct. I think my syntax is correct, right?
Bug#947598: marked as done (RFS: libcommoncpp2/1.8.1-8 [QA] [RC] -- Header files and static libraries for Common C++ "2")
Your message dated Sat, 28 Dec 2019 21:28:10 +0100 with message-id <20191228202810.ga15...@angband.pl> and subject line Re: Bug#947598: RFS: libcommoncpp2/1.8.1-8 [QA] [RC] -- Header files and static libraries for Common C++ "2" has caused the Debian Bug report #947598, regarding RFS: libcommoncpp2/1.8.1-8 [QA] [RC] -- Header files and static libraries for Common C++ "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.) -- 947598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947598 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 "libcommoncpp2" * Package name: libcommoncpp2 Version : 1.8.1-8 Upstream Author : [fill in name and email of upstream] * URL : http://www.gnu.org/software/commoncpp/ * License : GPL-2 * Vcs : https://salsa.debian.org/pkg-voip-team/libcommoncpp2 Section : devel It builds those binary packages: libcommoncpp2-dev - Header files and static libraries for Common C++ "2" libccgnu2-1.8-0v5 - GNU package for creating portable C++ programs libcommoncpp2-doc - Documentation files for Common C++ "2" To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libcommoncpp2 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libc/libcommoncpp2/libcommoncpp2_1.8.1-8.dsc Changes since the last upload: * QA upload. * Fix ftbfs with gcc-9. (Closes: #925739) * Update Standards-Version to 4.4.1 Note: I am not having permission to push to the repo. The changes are also available at 'debian/sid' branch of: https://salsa.debian.org/sudip-guest/libcommoncpp2 Do I need to open a merge request to have the changes pushed in the repo? -- Regards Sudip --- End Message --- --- Begin Message --- On Sat, Dec 28, 2019 at 11:45:56AM +, Sudip Mukherjee wrote: > * Package name: libcommoncpp2 >Version : 1.8.1-8 > Changes since the last upload: > >* QA upload. >* Fix ftbfs with gcc-9. (Closes: #925739) >* Update Standards-Version to 4.4.1 Hi! I've uploaded the fix as it's not a regression elsewhere, but it would be nice if you could improve broken man pages as well. > Note: I am not having permission to push to the repo. The changes are > also available at 'debian/sid' branch of: > https://salsa.debian.org/sudip-guest/libcommoncpp2 > > Do I need to open a merge request to have the changes pushed in the repo? I guess so -- I don't have access to the voip team as well. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.--- End Message ---
Re: Bug#947550: RFH: salsa.debian.org/debian/dbab
Hello Tong, I’m not a mentor but I recently pushed an existing package to Salsa. I now used the same procedure on your dbab package, you can see the result at https://salsa.debian.org/glts-guest/dbab. Here’s what I did: gbp import-dscs --debsnap dbab cd dbab git remote add origin g...@salsa.debian.org:glts-guest/dbab.git git push --all -u origin git push --tags With this procedure all the history of snapshots/pristine-tars gets imported, see https://salsa.debian.org/glts-guest/dbab/-/network/master. I see that you didn’t import the existing history, so maybe your goal is different … I have this setting in ~/.gbp.conf to import the pristine tarballs properly: [DEFAULT] pristine-tar = True That’s it. Hope this is helpful. Cheers,
Bug#947665: RFS: libgadu/1:1.12.2-4 [QA] [RC] -- Gadu-Gadu protocol library
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "libgadu" * Package name: libgadu Version : 1:1.12.2-4 Upstream Author : NA * URL : http://toxygen.net/libgadu/ * License : LGPL-2.1 * Vcs : https://github.com/porridge/libgadu Section : libs It builds those binary packages: libgadu3 - Gadu-Gadu protocol library - runtime files libgadu-dev - Gadu-Gadu protocol library - development files libgadu-doc - Gadu-Gadu protocol library - documentation To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libgadu Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libg/libgadu/libgadu_1.12.2-4.dsc Changes since the last upload: * QA upload. * Fix ftbfs with GCC-9. (Closes: #925743) Note: Only fixed ftbfs, I guess the remaining lintian warnings can be done later. The Vcs repo seems unused now. Shall I push it to salsa on next update? -- Regards Sudip
Re: Debian source search by file name
On 2019-12-28 at 14:47, Tong Sun wrote:
> Hi,
>
> Is it possible to do Debian source search by file name?
>
> I wanted to see examples of overriding
> debian-watch-does-not-check-gpg-signature in
> debian/source/lintian-overrides files, so I did:
>
> https://codesearch.debian.net/search?q=path%3Adebian%2Fsources%2Flintian-overrides
> https://codesearch.debian.net/search?q=gpg+signature+path%3Adebian%2Fsources%2Flintian-overrides
>
> But none gave results I want. Both say:
>
> . . . had no results. Please read the FAQ to make sure your syntax is correct.
>
> I think my syntax is correct, right?
Try:
https://codesearch.debian.net/search?q=gpg-signature+path%3Adebian%2Fsource%2Flintian-overrides
which works for me right now.
The only differences I see between this and your second URL above are A:
the use of the correct path ("source" instead of "sources"), and B: the
use of 'gpg-signature' instead of 'gpg signature'.
If I drop the 'gpg-signature' part from this search term, I get the same
error you got. I'm guessing that that's because there's no actual search
term for *within* the file, and the search engine isn't going to report
the entire file; if I'm right, that would be the other reason the first
URL you gave doesn't find anything, aside from the path typo.
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
Bug#941947: RFS: misspell-fixer/0.1-1 [ITP] -- Tool for fixing common misspellings, typos in source code
Thank you. I have made some small modifications partially to address your recommendation and the excuses listed here: https://tracker.debian.org/pkg/misspell-fixer - I have removed the mentioned files. https://github.com/vlajos/misspell-fixer/commit/0aeb0ea73e7ce5b0e3c8500886abc57168c8b78c - Updated the standards-version. https://github.com/vlajos/misspell-fixer/commit/81d9894d8875913cf0d397c99eb88a04a8d50dca - Added Multi-Arch: foreign. https://github.com/vlajos/misspell-fixer/commit/4f51acf15f22a2ec58a1c317b4563483f6282aa4 But unfortunately most of the remaining excuses are a little unclear for me... Could you please help me to understand them? > Rejected due to piuparts regression - > https://piuparts.debian.org/sid/source/m/misspell-fixer.html If I follow the link it says: piuparts-result: failed-testing 0.1-1 And when I follow this link as well: https://piuparts.debian.org/sid/state-failed-testing.html#misspell-fixer it says: misspell-fixer:all (0, 0) (Lajos Veres ) dependency grep is successfully-tested So I see only a success message. I tried to decypher this log: https://piuparts.debian.org/sid/fail/misspell-fixer_0.1-1.log I see a big list after this line: ERROR: FAIL: After purging files have disappeared: But I cannot really figure out how could misspell-fixer's purge remove them. When I install the package, removed it, then tried to purge I received this: $ apt-get install misspell-fixer ... $ apt-get remove misspell-fixer ... $ dpkg --purge misspell-fixer dpkg: warning: ignoring request to remove misspell-fixer which isn't installed And this line appears in the above log with a warning. Could this cause this problem somehow? > Migration status for misspell-fixer (- to 0.1-1): BLOCKED: Rejected/violates > migration policy/introduces a regression Is this one just the end result of the others? Or is there some other issues I do not see? > Not built on buildd: arch all binaries uploaded by kilobyte, a new > source-only upload is needed to allow migration This buildd related error message is also not really clear for me. Should I do something differently? I believe the "too young" will be fixed by time. And I guess the "not considered" is the result of the others. Sorry for bothering you with these ones... Best regards, Lajos Veres On Tue, 24 Dec 2019, Adam Borowski wrote: > On Tue, Dec 24, 2019 at 11:21:15AM +, Lajos Veres wrote: > > Thank you. > > Do I understand well that removing those 2 files would fix these issues? > > Yeah. > > > On Mon, 23 Dec 2019, Adam Borowski wrote: > > > There are minor issues such as: > > > * unused file debian/misspell-fixer-docs.docs > > > * redundant debian/README.source (Homepage: is a field it two other files > > > already) > > > > > > but, I've uploaded to NEW as is. > > > Meow! > -- Lajos Veres vla...@gmail.com
Bug#947677: RFS: python-jsbeautifier/1.10.2-1 [QA] -- JavaScript unobfuscator and beautifier (python3)
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "python-jsbeautifier" * Package name: python-jsbeautifier Version : 1.10.2-1 Upstream Author : Einar Lielmanis, Liam Newman * URL : https://github.com/beautify-web/js-beautify * License : MIT * Vcs : https://salsa.debian.org/debian/python-jsbeautifier Section : python It builds those binary packages: python3-jsbeautifier - JavaScript unobfuscator and beautifier (python3) jsbeautifier - JavaScript unobfuscator and beautifier To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-jsbeautifier Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-jsbeautifier/python-jsbeautifier_1.10.2-1.dsc Changes since the last upload: * QA upload * New upstream version 1.10.2 - Upstream change fix: closes: #931384, #873005 * Update copyright year and author in debian/copyright * Update debian/watch * Change to debhelper-compat * Reformat dependencies * Bump debhelper to 12 * Update Standards-Version to 4.4.1 * Add Rules-Requires-Root * Remove python2 line in debian/rules Can the sponsor also give me access to the salsa repository? Thanks. Regards, Håvard
Bug#941947: RFS: misspell-fixer/0.1-1 [ITP] -- Tool for fixing common misspellings, typos in source code
On Sat, Dec 28, 2019 at 10:25:59PM +, Lajos Veres wrote: > I have made some small modifications partially to address your > recommendation and the excuses listed here: > https://tracker.debian.org/pkg/misspell-fixer > > - I have removed the mentioned files. > https://github.com/vlajos/misspell-fixer/commit/0aeb0ea73e7ce5b0e3c8500886abc57168c8b78c > - Updated the standards-version. > https://github.com/vlajos/misspell-fixer/commit/81d9894d8875913cf0d397c99eb88a04a8d50dca > - Added Multi-Arch: foreign. > https://github.com/vlajos/misspell-fixer/commit/4f51acf15f22a2ec58a1c317b4563483f6282aa4 > > But unfortunately most of the remaining excuses are a little unclear for me... > Could you please help me to understand them? > > > Rejected due to piuparts regression - > > https://piuparts.debian.org/sid/source/m/misspell-fixer.html > > If I follow the link it says: > piuparts-result: failed-testing 0.1-1 > > And when I follow this link as well: > https://piuparts.debian.org/sid/state-failed-testing.html#misspell-fixer It claims, among others, that basically every file on the system has disappeared. That's nonsense. Looks like that part of the infrastructure made a boo-boo. A package with no preinst/postinst/prerm/postrm can't possibly fail piuparts testing -- it carries only static files that are added/removed by dpkg. You have no Replaces that'd allow a file conflict, and your package is a leaf one with no bogus symlinks that could possibly redirect something else. And, it passes piuparts on my box. > > Migration status for misspell-fixer (- to 0.1-1): BLOCKED: > > Rejected/violates migration policy/introduces a regression > > Is this one just the end result of the others? Yeah. > > Not built on buildd: arch all binaries uploaded by kilobyte, a new > > source-only upload is needed to allow migration > > This buildd related error message is also not really clear for me. Should > I do something differently? According to new Release Team's rules, only packages built on the official infrastructure are allowed to the new release, and the first upload can't possibly be. Until someone implements a better way, every package has to be built twice, and arch:all don't currently allow automated rebuilds. This means, you need to make another upload. And for this reason I did not wait until nits like the redundant files are fixed: that second upload is a good opportunity to fix them. > > > > There are minor issues such as: > > > > * unused file debian/misspell-fixer-docs.docs > > > > * redundant debian/README.source (Homepage: is a field it two other > > > > files > > > > already) Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.
Bug#947680: RFS: ploop/1.15-7 [QA] [RC] -- tools to work with ploop devices and images
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "ploop" * Package name: ploop Version : 1.15-7 Upstream Author : NA * URL : https://wiki.openvz.org/Ploop * License : GPL-2.0+ * Vcs : None Section : libs It builds those binary packages: ploop - tools to work with ploop devices and images libploop-dev - ploop API development library libploop1 - ploop API library To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ploop Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/ploop/ploop_1.15-7.dsc Changes since the last upload: * QA upload. * Fix ftbfs with GCC-9. (Closes: #925803) * Update Standards-Version to 4.4.1 * Update compat level to 12 -- Regards Sudip
Bug#947622: marked as done (RFS: python-pyperclip/1.7.0-1 [QA] -- Cross-platform clipboard module for Python3)
Your message dated Sun, 29 Dec 2019 02:45:07 +0100 with message-id <20191229014507.gc22...@angband.pl> and subject line Re: Bug#947622: RFS: python-pyperclip/1.7.0-1 [QA] -- Cross-platform clipboard module for Python3 has caused the Debian Bug report #947622, regarding RFS: python-pyperclip/1.7.0-1 [QA] -- Cross-platform clipboard module for Python3 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.) -- 947622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947622 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 "python-pyperclip" * Package name: python-pyperclip Version : 1.7.0-1 Upstream Author : * URL : https://github.com/asweigart/pyperclip * License : BSD-3-clause * Vcs : https://salsa.debian.org/debian/python-pyperclip Section : python It builds those binary packages: python3-pyperclip - Cross-platform clipboard module for Python3 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-pyperclip Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-pyperclip/python-pyperclip_1.7.0-1.dsc Changes since the last upload: * QA upload * New upstream version 1.7.0 * Clean up, after python2 removal * Change to debhelper-compat in debian/control * Reformat dependencies in debian/control * Change python3-qt4 to python3-pyqt5 as a possible runtime-dependency. * Change python-pytest to python3-pytest * Bump debhelper to 12 * Update Standards-Version to 4.4.1 * Add Rules-Requires-Root * Rebase patch * Add salsa CI Can the sponsor also give me access to the git repository? Thanks, Regards, Håvard --- End Message --- --- Begin Message --- On Sat, Dec 28, 2019 at 07:19:34PM +0100, Håvard Flaget Aasen wrote: > * Package name: python-pyperclip >Version : 1.7.0-1 > Changes since the last upload: > >* QA upload >* New upstream version 1.7.0 >* Clean up, after python2 removal >* Change to debhelper-compat in debian/control >* Reformat dependencies in debian/control >* Change python3-qt4 to python3-pyqt5 as a possible runtime-dependency. >* Change python-pytest to python3-pytest >* Bump debhelper to 12 >* Update Standards-Version to 4.4.1 >* Add Rules-Requires-Root >* Rebase patch >* Add salsa CI ✓ > Can the sponsor also give me access to the git repository? ✓ -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.--- End Message ---
Bug#947677: marked as done (RFS: python-jsbeautifier/1.10.2-1 [QA] -- JavaScript unobfuscator and beautifier (python3))
Your message dated Sun, 29 Dec 2019 03:43:17 +0100 with message-id <20191229024317.ga24...@angband.pl> and subject line Re: Bug#947677: RFS: python-jsbeautifier/1.10.2-1 [QA] -- JavaScript unobfuscator and beautifier (python3) has caused the Debian Bug report #947677, regarding RFS: python-jsbeautifier/1.10.2-1 [QA] -- JavaScript unobfuscator and beautifier (python3) 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.) -- 947677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947677 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 "python-jsbeautifier" * Package name: python-jsbeautifier Version : 1.10.2-1 Upstream Author : Einar Lielmanis, Liam Newman * URL : https://github.com/beautify-web/js-beautify * License : MIT * Vcs : https://salsa.debian.org/debian/python-jsbeautifier Section : python It builds those binary packages: python3-jsbeautifier - JavaScript unobfuscator and beautifier (python3) jsbeautifier - JavaScript unobfuscator and beautifier To access further information about this package, please visit the following URL: https://mentors.debian.net/package/python-jsbeautifier Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/python-jsbeautifier/python-jsbeautifier_1.10.2-1.dsc Changes since the last upload: * QA upload * New upstream version 1.10.2 - Upstream change fix: closes: #931384, #873005 * Update copyright year and author in debian/copyright * Update debian/watch * Change to debhelper-compat * Reformat dependencies * Bump debhelper to 12 * Update Standards-Version to 4.4.1 * Add Rules-Requires-Root * Remove python2 line in debian/rules Can the sponsor also give me access to the salsa repository? Thanks. Regards, Håvard --- End Message --- --- Begin Message --- On Sun, Dec 29, 2019 at 01:03:33AM +0100, Håvard Flaget Aasen wrote: > * Package name: python-jsbeautifier >Version : 1.10.2-1 > Changes since the last upload: > >* QA upload >* New upstream version 1.10.2 > - Upstream change fix: closes: #931384, #873005 >* Update copyright year and author in debian/copyright >* Update debian/watch >* Change to debhelper-compat >* Reformat dependencies >* Bump debhelper to 12 >* Update Standards-Version to 4.4.1 >* Add Rules-Requires-Root >* Remove python2 line in debian/rules ✓ > Can the sponsor also give me access to the salsa repository? ✓ > Thanks. It's you who's doing the actual work -- thus bigger thanks to you! Meow. -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄ etc), let the drink age at least 3-6 months.--- End Message ---
Re: Debian source search by file name
Oh thanks a lot for trying it out, finding the solution, and giving
comprehensive explanation!
Really appreciate it!
On Sat, Dec 28, 2019 at 5:16 PM The Wanderer - wande...@fastmail.fm wrote:
>
> On 2019-12-28 at 14:47, Tong Sun wrote:
>
> > Hi,
> >
> > Is it possible to do Debian source search by file name?
> >
> > I wanted to see examples of overriding
> > debian-watch-does-not-check-gpg-signature in
> > debian/source/lintian-overrides files, so I did:
> >
> > https://codesearch.debian.net/search?q=path%3Adebian%2Fsources%2Flintian-overrides
> > https://codesearch.debian.net/search?q=gpg+signature+path%3Adebian%2Fsources%2Flintian-overrides
> >
> > But none gave results I want. Both say:
> >
> > . . . had no results. Please read the FAQ to make sure your syntax is
> > correct.
> >
> > I think my syntax is correct, right?
>
> Try:
>
> https://codesearch.debian.net/search?q=gpg-signature+path%3Adebian%2Fsource%2Flintian-overrides
>
> which works for me right now.
>
> The only differences I see between this and your second URL above are A:
> the use of the correct path ("source" instead of "sources"), and B: the
> use of 'gpg-signature' instead of 'gpg signature'.
>
> If I drop the 'gpg-signature' part from this search term, I get the same
> error you got. I'm guessing that that's because there's no actual search
> term for *within* the file, and the search engine isn't going to report
> the entire file; if I'm right, that would be the other reason the first
> URL you gave doesn't find anything, aside from the path typo.
>
> --
>The Wanderer
>
> The reasonable man adapts himself to the world; the unreasonable one
> persists in trying to adapt the world to himself. Therefore all
> progress depends on the unreasonable man. -- George Bernard Shaw
>
Re: Bug#947550: RFH: salsa.debian.org/debian/dbab
Thanks a lot David, for your explanation and detailed commands. I was trying to find a way out reading the convoluted user manual, and finally found one way that worked (and much much more convoluted than the commands you listed and yet achieving much less). Thanks a lot, I wish I had known them earlier. I am now trying to apply to my existing repo, wish me luck... On Sat, Dec 28, 2019 at 3:52 PM David Bürgin - dbuer...@gluet.ch wrote: > > Hello Tong, > > I’m not a mentor but I recently pushed an existing package to Salsa. I > now used the same procedure on your dbab package, you can see the result > at https://salsa.debian.org/glts-guest/dbab. Here’s what I did: > > gbp import-dscs --debsnap dbab > cd dbab > git remote add origin g...@salsa.debian.org:glts-guest/dbab.git > git push --all -u origin > git push --tags > > With this procedure all the history of snapshots/pristine-tars gets > imported, see https://salsa.debian.org/glts-guest/dbab/-/network/master. > I see that you didn’t import the existing history, so maybe your goal is > different … > > I have this setting in ~/.gbp.conf to import the pristine tarballs > properly: > > [DEFAULT] > pristine-tar = True > > That’s it. Hope this is helpful. > > Cheers, > >
Bug#947452: RFS: kworkflow/20191112-1 [ITP] -- Inglorious kernel developer workflow scripts
Hi Adam! Em sex., 27 de dez. de 2019 às 19:17, Adam Borowski escreveu: > > On Fri, Dec 27, 2019 at 01:12:26AM -0300, Rodrigo Carvalho wrote: > > * Package name: kworkflow > >Version : 20191112-1 > > > Changes since the last upload: > > > >* Initial release. Closes: #946781 > > Hi! > I'm afraid that autopkgtest fails, as it tries to access the current user's > $HOME. No package should reach outside of its build dir, during either the > compile or test step. > > You can eg. set $HOME to $AUTOPKGTEST_TMP which is a valid writeable dir. Thanks for the tip. I uploaded a new version. I hope now it works fine. > > autopkgtest [23:13:22]: test kw-basic-test: [--- > error: could not lock config file /home/kilobyte/.gitconfig: No such file or > directory > error: could not lock config file /home/kilobyte/.gitconfig: No such file or > directory > Running test [checkpatch_wrapper_test] > = > testWarning > testError > testChecks > testCorrect > > Ran 4 tests. > > OK > Running test [commons_test] > = > testParseRegularConfig > testParseUnsupportedFile > testDefaultConfigFile > testLocalConfigFile > > Ran 4 tests. > > OK > Running test [configm_test] > = > testExecuteConfigManagerSAVEfails > testSaveConfigFileCHECK_CONFIGfails > testSaveConfigFileCHECK_CONFIGS_DIRECTORY > testSaveConfigFileCHECK_SAVED_CONFIG_FILE > testSaveConfigFileCHECK_DESCRIPTION > testSaveConfigFileCHECK_GIT_SAVE_SCHEMA > testSaveConfigFileCHECK_FORCE > testListConfigsCHECK_NO_CONFIGS > testListConfigsOUTPUT > testGetOperationWithForce > testGetOperationThatShouldFail > testRemoveOperationThatShouldFail > testRemoveOperation > > Ran 13 tests. > > OK > Running test [explore_test] > = > testExplore > > Ran 1 test. > > OK > Running test [fish_completion_test] > = > testKwCompletion > > Ran 1 test. > > OK > Running test [get_maintainer_wrapper_test] > = > testPrintFileAuthorForFile > testPrintFileAuthorForDir > testGetMaintainers > > Ran 3 tests. > > OK > Running test [help_test] > = > testHelp > > Ran 1 test. > > OK > Running test [kw_dash] > = > testDash > install: cannot create directory ‘/home/kilobyte’: Permission denied > cp: cannot create directory '/home/kilobyte/.config/kw': No such file or > directory > sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or > directory > > Ran 1 test. > > OK > Running test [kw_test] > = > install: cannot create directory ‘/home/kilobyte’: Permission denied > cp: cannot stat '/tmp/autopkgtest.gQu1DL/build.mAh/src/tests/etc/.': No such > file or directory > sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or > directory > testVariables > testExported > > Ran 2 tests. > > OK > Running test [kwio_test] > = > testAlertOptions > testAlertDefaultOptions > testAlertCommandPrinting > > Ran 3 tests. > > OK > Running test [kwlib_test] > = > linuxRootCheckTest > cmdManagerTESTMODETest > cmdManagerSILENTTest > cmdManagerSAY_COMPLAIN_WARNING_SUCCESS_Test > detectDistroTest > joinPathTest > findKernelRootTest > isAPatchTest > > Ran 8 tests. > > OK > Running test [ssh_test] > = > vmSshFailsTest > vmSshTest > vmSshCommandTest > vmSshScriptTest > > Ran 4 tests. > > OK > = > Total: 12 test file(s) > Test file(s) SUCCEEDED > test_codestyle > install: cannot create directory ‘/home/kilobyte’: Permission denied > cp: cannot create directory '/home/kilobyte/.config/kw': No such file or > directory > sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or > directory > test_maintainers > install: cannot create directory ‘/home/kilobyte’: Permission denied > cp: cannot create directory '/home/kilobyte/.config/kw': No such file or > directory > sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or > directory > test_explore > Initialized empty Git repository in > /tmp/autopkgtest.gQu1DL/autopkgtest_tmp/.git/ > install: cannot create directory ‘/home/kilobyte’: Permission denied > cp: cannot create directory '/home/kilobyte/.config/kw': No such file or > directory > sed: can't read /home/kilobyte/.config/kw/kworkflow.config: No such file or > directory > > Ran 3 tests. > > OK > autopkgtest [23:13:24]: test kw-basic-test: ---] > autopkgtest [23:13:25]: test kw-
Re: Multiple Profiles in a single build-simple-cdd build
On Sat, Dec 28, 2019 at 6:33 PM Chew, Kean Ho wrote: > > Hi mentors, > > Can build-simple-cdd build a CD using multiple profiles using .conf file? > Managed to found a good example and tested it successfully only my side (https://salsa.debian.org/debian/simple-cdd). The problem was due to the --auto-profiles' argument values was not the same as --profiles' argument values. The fix is to have both of them using the same value. The separation using space or comma were both tested and both resulted positive working outcome. Based on the guide, it is recommending comma approach, something like: locale=en_US profiles="x-basic,ltsp" auto_profiles="x-basic,ltsp" ... Therefore, I'm closing this thread as solved. Happy holiday all. Regards, Holloway
