Bug#947859: RFS: csstidy/1.4-6 [QA] -- CSS parser and optimiser
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "csstidy" * Package name: csstidy Version : 1.4-6 Upstream Author : Florian Schmitz * URL : http://csstidy.sourceforge.net/ * License : GPL-2 * Vcs : https://salsa.debian.org/debian/csstidy Section : utils It builds those binary packages: csstidy - CSS parser and optimiser To access further information about this package, please visit the following URL: https://mentors.debian.net/package/csstidy Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/csstidy/csstidy_1.4-6.dsc Changes since the last upload: * QA upload * In debian/control - Change to debhelper-compat - Bump debhelper to 12 - Update Standards-Version to 4.4.1 - Change Priority: from extra to optional - Add Vcs-Browser and Vcs-Git - Add Rules-Requires-Root: no * Create 005-support-python3.patch closes: #947557 - SConstruct and SConscript is python2 and python3 compatible. * Made debian/copyright dep5 compatible This package needs to be tested against SCons. In unstable it's still python2 while in experimental it's python3 Regards, Håvard
Bug#947862: RFS: rmlint/2.9.0-2 -- Extremely fast tool to remove filesystem lint
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "rmlint" * Package name: rmlint Version : 2.9.0-2 Upstream Author : Christopher Pahl * URL : https://rmlint.readthedocs.io/ * License : GPL-3+ * Vcs : https://salsa.debian.org/debian/rmlint Section : utils It builds these binary packages: rmlint - Extremely fast tool to remove filesystem lint rmlint-gui - GTK+ frontend to rmlint rmlint-doc - HTML documentation for rmlint To access further information about this package, please visit the following URL: https://mentors.debian.net/package/rmlint Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/r/rmlint/rmlint_2.9.0-2.dsc Changes since the last upload: * Replace glib-2_62.patch with upstream implementation, which provides a fallback and hopefully will allow an ia64 build. Regards, -- Carlos Maddela
gbp import-orig after upstream force update
Hi, How to do gbp import-orig after upstream did *force* push/update with the same tag? While doing packaging, there will always some trivial things I found I need to update the upstream source (I'm the author for both upstream and Debian packaging). However, if I have to give a new tag each time I do such trivial updates, then they'll go very fast for very trivial changes, which does not look good. So I always force push/update with the same tag. The problem is that I haven't been able to figure out how to have `gbp import-orig` to deal with such situation -- I always get: gbp:error: Upstream tag 'upstream/...' already exists How to fix it? Thx
Re: gbp import-orig after upstream force update
On Tue, Dec 31, 2019 at 6:28 PM Tong Sun wrote: > > Hi, > > How to do gbp import-orig after upstream did *force* push/update with > the same tag? > > While doing packaging, there will always some trivial things I found I > need to update the upstream source (I'm the author for both upstream > and Debian packaging). > > However, if I have to give a new tag each time I do such trivial > updates, then they'll go very fast for very trivial changes, which > does not look good. So I always force push/update with the same tag. > > The problem is that I haven't been able to figure out how to have `gbp > import-orig` to deal with such situation NVM, found that the real problem is actually at GH side -- force push with the same tag will not trigger GH to rebuild the .tgz tarball.
Re: gbp import-orig after upstream force update
On Tue, Dec 31, 2019 at 06:28:55PM -0500, Tong Sun wrote: > How to do gbp import-orig after upstream did *force* push/update with > the same tag? > > While doing packaging, there will always some trivial things I found I > need to update the upstream source (I'm the author for both upstream > and Debian packaging). > > However, if I have to give a new tag each time I do such trivial > updates, then they'll go very fast for very trivial changes, which > does not look good. So I always force push/update with the same tag. At the same time, it looks *horribly* from my side every time I see such things. Don't tag things until you really want to release, and by then you ought to have tested things well enough. If it's really trivial changes, then it can just wait for whenever you feel like doing a new release. > The problem is that I haven't been able to figure out how to have `gbp > import-orig` to deal with such situation -- I always get: > > gbp:error: Upstream tag 'upstream/...' already exists > > How to fix it? Thx Get a new upstream version. If from the upstream side really want to do such horrible things, then fake the version in debian by appending some +a1 version (or whatever string you prefer). Versions are meant to uniquely identify a thing. If the same version string matches different objects at different point in times, it's just conceptually wrong. Anyway, if it's really just that, gbp only checks for the presence of the upstream/ git tag; if you remove it (`git tag -d`) then it won't complain anymore. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#946213: RFS: git-delta/0.0.15 -- Syntax-highlighting pager for git and diff output
On Thu, Dec 05, 2019 at 11:03:57AM -0500, Dan Davison wrote: > I am looking for a sponsor for my package "git-delta": Hi! Last year, you started preparing this package. As it's something extremely useful, I'm anxious to see it in Debian. The alternatives suck. Alas, git-delta is written in some heathen language I don't know how to deal with (Rust's own package manager pollutes quite a bit of the system), thus it would be nice to have it properly packaged so doofuses like me can use it. Thus, a ping. 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.
