Bug#963105: (no subject)
Oops, the VCS link should have said: https://salsa.debian.org/rhansen/libscgi-perl
Bug#963105: RFS: libscgi-perl/0.6-1 [ITP] -- libscgi-perl - SCGI server library for perl
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "libscgi-perl" * Package name: libscgi-perl Version : 0.6-1 Upstream Author : Viper Code Limited * URL : https://metacpan.org/release/SCGI * License : Artistic or GPL-1+ * Vcs : https://salsa.debian.org/debian/libscgi-perl Section : perl It builds those binary packages: libscgi-perl - SCGI server library for perl To access further information about this package, please visit the following URL: https://mentors.debian.net/package/libscgi-perl Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/libs/libscgi-perl/libscgi-perl_0.6-1.dsc Changes since the last upload: * Initial release. Regards, -- Richard Hansen
Bug#963019: RFS: pem/0.7.9-3 -- command line personal expense manager
Boa tarde jovem,
Já encontrou sponsor? Se quiser posso revisar.
Att,
Marcio
Em qua, 2020-06-17 às 14:10 -0500, David da Silva Polverari escreveu:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "pem"
>
> * Package name: pem
>Version : 0.7.9-3
>Upstream Author : Prasad J Pandit
> * URL : https://www.gnu.org/software/pem/
> * License : GPL-3+
> * Vcs : https://salsa.debian.org/debian/pem
>Section : misc
>
> It builds those binary packages:
>
> pem - command line personal expense manager
>
> To access further information about this package, please visit the
> following URL:
>
> https://mentors.debian.net/package/pem
>
> Alternatively, one can download the package with dget using this
> command:
>
> dget -x
> https://mentors.debian.net/debian/pool/main/p/pem/pem_0.7.9-3.dsc
>
> Changes since the last upload:
>
>* Using new DH level format. Consequently:
>- debian/compat: removed.
>- debian/control: changed from 'debhelper' to 'debhelper-
> compat' in
> Build-Depends field and bumped level to 13.
>* debian/control:
>- Added '${perl:Depends}' to Depends field.
>- Added 'Rules-Requires-Root: no' to source stanza.
>- Added Vcs-* fields.
>- Bumped Standards-Version to 4.5.0.
>- Marked pem as 'Multi-Arch: foreign'.
>- Removed redundant dh-autoreconf build dependency.
>* debian/copyright: updated copyright years.
>* debian/patches/010_use-usr-bin-perl.patch: added to use
> '/usr/bin/perl'
> instead of '/usr/bin/env perl' for interpreter invocation.
>* debian/rules: removed redundant '--with autoreconf' dh
> parameter.
>* debian/salsa-ci.yml: added to provide CI tests for Salsa.
>* debian/tests/control: added to perform a trivial CI test.
>* debian/upstream/metadata: created.
>* debian/watch: using a secure URI.
>
> Regards,
>
> --
> David da Silva Polverari
>
Packaging twemoji
hello mentors, I intend to package twemoji (Open-sourced Twitter emoji SVGs, see #878875). I guess it should be packaged in the debian-js team, even if I just package the SVGs? @Dominik: Can you tell me whether it is ok to just package the SVGs? Many Thanks and Best Regards, -- Felix Natter
Bug#963056: RFS: gnome-colors/5.5.1-2.1 [NMU, RC] -- set of GNOME icon themes
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "gnome-colors" * Package name: gnome-colors Version : 5.5.1-2.1 Upstream Author : Victor Castillejo * URL : http://code.google.com/p/gnome-colors/ * License : GPL-2 * Vcs : http://bazaar.launchpad.net/~gnome-colors-packagers/gnome-colors-pkg/debian/files Section : gnome It builds those binary packages: gnome-colors - set of GNOME icon themes gnome-colors-common - common icons for all GNOME-Colors icon themes gnome-brave-icon-theme - blue variation of the GNOME-Colors icon theme gnome-dust-icon-theme - chocolate variation of the GNOME-Colors icon theme gnome-human-icon-theme - orange variation of the GNOME-Colors icon theme gnome-illustrious-icon-theme - pink variation of the GNOME-Colors icon theme gnome-noble-icon-theme - purple variation of the GNOME-Colors icon theme gnome-wine-icon-theme - red variation of the GNOME-Colors icon theme gnome-wise-icon-theme - green variation of the GNOME-Colors icon theme To access further information about this package, please visit the following URL: https://mentors.debian.net/package/gnome-colors Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/g/gnome-colors/gnome-colors_5.5.1-2.1.dsc Changes since the last upload: * Non-maintainer upload. * Fix FTBFS. (Closes: #959628) -- Regards Sudip
Re: salsa repository request for davfs2
Hi Andrius, Thanks for explanations, I will figure out later. Woodrow On Thu, Jun 18, 2020 at 6:06 PM wrote: > Hi Woodrow, > > On 2020-06-18 13:02, Woodrow Shen wrote: > > I'm doing NMU for davfs2 and would like to access > > https://salsa.debian.org/debian/davfs2 to send a PR to the maintainer. > > Can someone help me? Thanks. > > > > My username on salsa already aligned to "woodrowshen" as NM. > > To submit a PR you do not need the access to the repository in question. > Instead, you can fork it to your namespace, create a branch and then > submit a PR to the original repository. AFAIK, opening a PR does not > require write permission. > > HTH, > Andrius > >
Bug#959171: New package version
A new package version is available at https://mentors.debian.net/debian/pool/contrib/r/r4d/r4d_1.6-1.dsc
Re: salsa repository request for davfs2
Hi Woodrow, On 2020-06-18 13:02, Woodrow Shen wrote: > I'm doing NMU for davfs2 and would like to access > https://salsa.debian.org/debian/davfs2 to send a PR to the maintainer. > Can someone help me? Thanks. > > My username on salsa already aligned to "woodrowshen" as NM. To submit a PR you do not need the access to the repository in question. Instead, you can fork it to your namespace, create a branch and then submit a PR to the original repository. AFAIK, opening a PR does not require write permission. HTH, Andrius
salsa repository request for davfs2
Hi Mentors, I'm doing NMU for davfs2 and would like to access https://salsa.debian.org/debian/davfs2 to send a PR to the maintainer. Can someone help me? Thanks. My username on salsa already aligned to "woodrowshen" as NM. Woodrow
Bug#963044: RFS: davfs2/1.5.6-0.1 [NMU] -- mount a WebDAV resource as a regular file system
Package: sponsorship-requests Severity: normal Tags: upstream Dear mentors, maintainer, I am looking for a sponsor for my package "davfs2" * Package name: davfs2 Version : 1.5.6-0.1 Upstream Author : [fill in name and email of upstream] * URL : http://savannah.nongnu.org/projects/davfs2 * License : [fill in] * Vcs : https://salsa.debian.org/debian/davfs2 Section : utils It builds those binary packages: davfs2 - mount a WebDAV resource as a regular file system To access further information about this package, please visit the following URL: https://mentors.debian.net/package/davfs2 Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/davfs2/davfs2_1.5.6-0.1.dsc Changes since the last upload: * Non-maintainer upload. * New upstream version. * Standards-Version: 4.5.0 * Fix incompatible neon library version by adding 31 to configure.ac. * Fix a lintian warning of debian-watch-uses-insecure-uri. The affected point for me is currnet version causes segmentation fault when umount.davfs2 is executed, so this is fixed by upstream release. Regards, -- Woodrow Shen (Hsieh-Tseng Shen) 4FA0 D159 803F F8B6 34E9 5A38 3970 FE24 7CB6 9685 woodrow.s...@gmail.com signature.asc Description: PGP signature
Re: Adding a user in postinstall
Hi Hilmar, On Wed, Jun 17, 2020 at 01:34:44PM +0200, Hilmar Preuße wrote: > Am 17.06.2020 um 11:55 teilte Markus mit: > > This is about g...@salsa.debian.org:debian-astro-team/gavodachs.git, > > the gavo branch. > > > > > > # create user "dachsroot" if (s)he is not already there > > if ! getent passwd dachsroot ; then > > adduser --disabled-password --gecos "" --ingroup gavo dachsroot > > fi > > > > This has never resulted in headache over all the years that we have > > been distributing the resulting package outside of Debian. But the > > CI on salsa gives: > > > > Adding user `dachsroot' ... > > Adding new user `dachsroot' (1011) with group `gavo' ... > > Creating home directory `/home/dachsroot' ... > > Stopped: Couldn't create home directory `/home/dachsroot': File exists. > > > > Removing directory `/home/dachsroot' ... > > Removing user `dachsroot' ... > > > Do you really need a created home dir for that user or would be > > adduser ... --no-create-home > > an option? >From the reactions I take it that at least I've not missed anything in the Policy that wouldn't let me adduser with home. Phew. And... well, it would be nice if this account had a home, because people are intended to work as it, and so it'd be good if trying to read or write, say, ~/.vimrc wouldn't do odd things. Well -- I'll fiddle a bit to see if I can understand what the CI is bothered by. Thanks, Markus
How to properly deal with git lfs
Hi, in the covid-19 sprint of the Debian Med project we intend to package flappie[1]. When using the normal uscan download of the tarball some files that are kept in upstream git as lfs these files are corrupted (just links to the lfs location and non-functional inside the tarball). So I naively removed these files since I assumed it would be easy to download those data later but the header files here[2] are symlinks to the mdl files (which I removed) and thus the build does not work. I have two questions about dealing with this: 1. How to sensibly get a functional tarball of the latest release? Obviously its not the normal uscan. With Git mode I have no idea how to point to the latest tag and moreover I do not know how to ensure that git-lfs is installed. 2. How to properly deal with lfs support on salsa? I remember I once had trouble with this and would like to get hints to a simple guideline. Alternatively I would decide to simply keep the debian/ dir on Salsa (may be that's sensible in general for large archives anyway) - but this makes question 1. even more relevant Kind regards Andreas. [1] https://salsa.debian.org/med-team/flappie [2] https://github.com/nanoporetech/flappie/tree/master/src/models -- http://fam-tille.de
