Re: Request for moving Salsa repository to debian group

On 1/15/24 18:00, Soren Stoutner wrote: Done. On Saturday, January 13, 2024 3:54:46 PM MST Robin Gustafsson wrote: I am working on a QA upload for the hunspell-uz package, which has not previously used a VCS for the Debian packaging. I created a repository at: https://salsa.debian.org

Re: Salsa repository requested

On 1/14/24 21:09, Bruno Naibert wrote: I am a maintainer of the html2text package https://tracker.debian.org/pkg/html2text and I would like to have access as a maintainer in the Salsa repository https://salsa.debian.org/debian/html2text/. Could you adjust my access permissions? Done. -- Regar

Re: Request for moving Salsa repository to debian group

Hi Soren, On 1/11/24 23:59, Soren Stoutner wrote: I am working on a QA upload for the hunspell-uz package, which has not previously used a VCS for the Debian packaging.  I created a repository at: https://salsa.debian.org/soren/uzbek-wordlist

Bug#1057332: sponsorship-requests: Bottom/0.9.6 -- A customizable cross-platform graphical process/system monitor for the terminal

Hi Douglas, On 12/3/23 16:29, Douglas Baggett wrote: Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: doug.bagg...@gmail.com This package `bottom` is **REALLY NICE**. https://github.com/ClementTsang/bottom The author has packages for debian already made from nightlys. It should

Re: Looking to find a sponsor

Hi Jordan, (I'm CC:ing you this time in case you're not subscribed to the list.) [...] The package is a Python app called CraftServerSetup that allows the user to  create and manage game servers for the popular video game Minecraft. CraftServerSetup seems to be non-free software. If so, it

Re: Questions about ITP in Debian

On Mon, May 29, 2023 at 6:24 PM Tadeu Sampaio wrote: > > Thx Robin for the fast response! So what is needed in order to proceed with > the ITP below, we need a sponsor? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024547 > > Best regards, > Tadeu The (currently) last message [1] on tha

Re: Questions about ITP in Debian

Hi, On Mon, May 29, 2023 at 5:36 PM Tadeu Sampaio wrote: > > Hi, thx for your attention! Please, can you clarify this for me? For an ITP > to be submitted, it is necessary that the person applies to become a member > (Debian New Maintainers)? I am asking regarding this ITP: > https://bugs.debi

Re: Maintaining a package across several debian codenames

On Mon, Apr 10, 2023 at 11:30 AM Robin ALEXANDER wrote: > > Hi, > > Let's assume I wish to maintain package_A across unstable and bullseye- > backports. I understand from > https://dep-team.pages.debian.net/deps/dep14/ that: > > 1. I need to create 3 branches in my git repository: > - upstream/lat

Bug#1024452: RFS: cbonsai/1.3.1-1 -- terminal-based bonsai tree generator

a fields * Update standards version to 4.6.1, no changes needed. . [ Robin Gustafsson ] * Restore debian/manpages * Remove rebuild in cross-arch builds * Build manpage with upstream's Makefile * Wrap-and-sort control files Regards, Robin

Bug#1023775: RFS: php-laravel-framework/8.83.26+dfsg-1 [RC] -- web application framework for PHP

-framework/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/p/php-laravel-framework/php-laravel-framework_8.83.26+dfsg-1.dsc Changes since the last upload: php-laravel-framework (8.83.26+dfsg-1) unstable; urgency=

Re: RFS: python-decouple/3.6-3 -- Helps you to organize your Django/Flask settings

> Question (cc'ing d-m): it took me several iterations uploading to > mentors (and fixing the feedback items, etc). Since dcut does not > operate on the mentors repository, how can I replace an upload with the > same revision number? (Hope that makes sense..) > > Thanks! > Matt You can upload th

Re: debian folder and version control system repository

On Wed, Dec 29, 2021 at 2:00 PM Geert Stappers wrote: > In-Reply-To: > > Subject: Re: Packaging help: users and directories > > On Wed, Dec 29, 2021 at 01:03:52PM +0100, Robin Gustafsson wrote: > > On Wed, Dec 29, 2021 at 12:35 PM Gavin Henry wrote: > > > [...] >

Re: Packaging help: users and directories

On Wed, Dec 29, 2021 at 2:03 PM Gavin Henry wrote: >> >> > Is it best practice to have: >> > >> > 1. debian folder in your main repo >> > 2. debian folder branch in main repo >> > 3. Separate repo for this >> >> A separate repo hosted on salsa.debian.org. > > Thanks. That's for an official package

Re: Packaging help: users and directories

Hi Gavin, On Wed, Dec 29, 2021 at 12:35 PM Gavin Henry wrote: > [...] > Is it best practice to have: > > 1. debian folder in your main repo > 2. debian folder branch in main repo > 3. Separate repo for this A separate repo hosted on salsa.debian.org. On Wed, Dec 29, 2021 at 12:37 PM Gavin Henry

Re: How to revive an abandoned package? (Qtile)

Hi Damien, On Sun, Nov 21, 2021 at 10:09 PM Damien Calloway wrote: > > Hello! > > I am an avid Pythonista and I was disappointed to learn that > > sudo apt install qtile > > No longer works. In my research, it appears that the qtile project relies on > packagers for each distribution - they do n

Re: include additional git repo in package

Hi Peymaneh, > the dist-repo has no releases or tags, so uscan would usually download HEAD. Perhaps you could ask upstream for tags matching their releases? It seems they're already updating version numbers within the "dist" repo for every release anyway. > A situation were one would want to pac

Re: libgrokj2k: version 9.2 uploaded

Hi Aaron, > I've upgraded this package priority to high as it fixes a CVE > present in previous version. > It would be great if we can get this migrated. > oops, never mind - I see Bullseye is in freeze. You could ask the release team for an unblock [1]. Security fixes are usually important and

Bug#990424: RFS: cbonsai/1.2.1-1 -- terminal-based bonsai tree generator

] * Fix FTCBFS (Closes: #984908) . [ Robin Gustafsson ] * Track upstream's versioned releases * New upstream version 1.2.1 * Remove obsolete patches * Set upstream metadata fields: Bug-Database, Bug-Submit. * Avoid explicitly specifying -Wl,--as-needed linker flag. Note

Re: avoiding autoremoval for what seems like a spurious build error

On Tue, May 4, 2021 at 7:48 PM Stephen Sinclair wrote: > > In any case, I was not so much asking for help building/reproducing, > as I was asking what I can do other than to reply to the bug, which > seems not to be eliciting a response, to either avoid or delay the > auto-removal process. Is aut

Re: avoiding autoremoval for what seems like a spurious build error

Hi Stephen, On Thu, Apr 29, 2021 at 5:26 PM Stephen Sinclair wrote: > > Hi Mentors, > > My package siconos currently has a bug filed [1] and has been marked > for autoremoval from testing. > > The problem is that I cannot reproduce it. Did you build the package in a clean environment? Against on

Bug#983146: sponsorship-requests: Backup next generation (bung)

Charles, > I tried hard to make a source .deb but did not manage to do so. Would > you like me to share the system I use to create the .deb? A source package is required for inclusion in Debian. The binary packages are built automatically on Debian infrastructure and must use certain build tools

Bug#983146: sponsorship-requests: Backup next generation (bung)

Hi Charles, Where can I find the Debian source package? I found .deb files, but not how they're generated. Also, installing the files under /opt is disallowed for official packages. Regards, Robin

Bug#981987: RFS: cbonsai/0.0~git20210115.e107005-1 [ITP] -- terminal-based bonsai tree generator

.e107005-1) unstable; urgency=medium . * Initial release (Closes: #981965) Regards, -- Robin Gustafsson

Does 32-bit arithmetic overflow mean arch incompatibility?

Hi mentors, Does the possibility of arithmetic overflow on 32-bit systems mean that the software is to be considered incompatible with 32-bit architectures? A package I'm working on has some test failures on 32-bit due to overflows. I only maintain architecture-independent packages and I'm not su

Re: Package ghostwriter E source-is-missing

Hi seb, On Sat, Jan 23, 2021 at 6:54 PM wrote: > > I'm not sure how to resolve the error indicated by Lintian on the > Ghostwriter package (https://mentors.debian.net/package/ghostwriter/). > > > ghostwriter source > > > > E source-is-missing > > debian / missing-sources / 3rdparty /

Re: Question about lintian bad-whatis-entry warning

Hi Aaron, > How can I get more insight into the problem? Lintian's explanation for bad-whatis-entry [1] mentions that it's "lexgrog" that fails to parse your header. (Looking at Lintian source [2], it's indeed just running lexgrog on your file and checking the exit code.) The lexgrog man page co

Bug#977898: RFS: movim/0.17.1-1.1 [NMU] [RC] -- decentralised social network fully based on XMPP

e the last upload: movim (0.17.1-1.1) unstable; urgency=medium . * Non-maintainer upload. * Use php-illuminate-database 6 (Closes: #976886) Regards, -- Robin Gustafsson

Bug severity for blocking a transition

Hi mentors, Is blocking a transition always RC? Or how would I deduce the appropriate bug severity? I'm particularly interested due to the relation between bug severity and the policy for NMUs. Regards, Robin

Re: Finding files for d/clean when using sbuild

Thank you, Baptiste and Paul! Glad to know I'm not the only one in need of this. Baptiste Beauplat wrote: > [...] > I tried to give it a more serious thought and I came up with the > alternative of using the commands hooks as recommended in #424846[1]. > > I came up with the following: > [...]

Finding files for d/clean when using sbuild

Hi mentors, More than once now, I've made the mistake of missing certain files that ought to be added to debian/clean. I typically use sbuild when building packages, so these extra files get thrown out after the build anyways, so they're not obvious to me. What's the recommended way to find such

Bug#972402: RFS: libphp-swiftmailer/6.2.3-1 [ITA] -- Swiftmailer, free feature-rich PHP mailer

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

Build fails on i386 due to overflows in tests

Dear mentors, A package I'm maintaining fails to build on i386 [1]. Specifically, the build-time tests are failing. I believe numerical overflows to be the cause. I'm unsure about the best course of action. The built package is architecture-independent (interpreted code). However, the packaged li

Bug#960742: RFS: lazpaint/7.1.3 ITP -- add LazPaint to Debian

I recall another RFS [1] with the same problem (binary-only package containing binaries produced with Lazarus). Perhaps something from that thread could help you. [1]: http://bugs.debian.org/964087 Regards, Robin

Bug#961428: RFS: python-discord/1.3.3+dfsg-1 [ITP] -- API wrapper for Discord written in Python

) Regards, -- Robin Gustafsson

Re: Packaging pyca

> I created the current package with the tools installed under Buster > using dh_make and the Lintian on Buster seems to be happy, except to the > jquery stuff of course. Maybe this leads to the outdated versions. It does indeed. > Currently I provide this for people installing PyCA on their curr

Re: Packaging pyca

Hi Sven, I'm a new contributor myself and cannot sponsor the package nor answer all of your questions, but I can offer some suggestions. > Currently there is a Lintian error, due to the fact, that PyCA > itself ships an own version of jquery This would not be allowed in Debian. Firstly, the jQue

Re: Debian package postupgrade script

Hi Tong Sun, > I've made some breaking changes to my package, > https://github.com/suntong/dbab/commit/3ab123e5a90f2b37021a8a1b27dc6eaf2a9b87d6#diff-087e6c3b5855f52a443f266d08a555d1R77-R78 > and would like to remove the old configure files in postupgrade step. Judging from the commit message, it

Re: RFS: stateserial -- Displays serial port modem status lines

Hi Aristo Chen, I recommend you follow the sponsorship process outlined here [1]. That would make it easier for potential sponsors to find your package. [1] https://mentors.debian.net/sponsor/rfs-howto Regards, Robin

Re: A question about uscan and MUT with different versions

Hi Leopold, > salsa ci build the package but other test fails and I don't know if it's > a package issue or salsa ci. Unfortunately, I don't know the cause of those failures. Considering how early the jobs failed I'd guess your package wasn't even involved yet, though. > > FWIW, the --download-c

Re: A question about uscan and MUT with different versions

Hi Leopold, > However, when I push it to salsa and run ci, the command executed is this: > > uscan --download --download-current-version > > and fails because the "data" modules has different version number that > the original main or this is what I understand [2]. > > Some of you knows how to man

Re: tsvtree: A command line tool to display TSV data in tree-like format

Hi Marcelo, I'm a new/inexperienced contributor myself, but I have some suggestions that could hopefully be useful to you. > I have split the package and the debianization in different > repositories. It is fairly common to keep the packaging on a separate branch, if your actual preference is to

Re: package prevented from migration due to "regression", but regression bug is fixed

> > yes, that's exactly what you'll need to do. Also, it would be better if > > you closed it with a fixed version as well. > > Ok, I will skip this since it was closed by someone else but in the > future it would require a package update, got it. I think you can do that with the "fixed" command

Re: How to update upstream when upstream has no releases

Hi Tong Sun, > I was using `gbp import-orig --sign-tags --uscan` but it seems that > `--uscan` cannot be used with `gbp import-orig` under the case of no > upstream releases. I believe it'll work if the debian/watch file is set up such as to have uscan download the upstream's git repo. The "direc

Re: Question about blocked package to testing

Hi Elías, > -Under build system it's fine [2] but with salsa-ci pipeline[3] it fails. > Do you know why? The error in the build output [1] implies that GPICK_BUILD_DATE is expected, but not found, among the environment variables. You probably have it set in your local environment, but it's not b