Bug#925911: RFS: lopsub-1.0.2 [ITP]
On Sun, Apr 21, 22:25, Adam Borowski wrote > On Sun, Apr 21, 2019 at 05:11:05PM +0200, Andre Noll wrote: > > That's just because I misread section 8.1 of the Debian Policy Manual. > > I've renamed the -dev package to liblopsub-dev. > > Not sure if you'd want the _source_ package to have a simple soname-less > name as well; I would but that's up to you -- that'd be nicer and make > having only-one-version transitions easier; on the other hand a > soname-encoded source name is better when there's a need for multiple > coinstallable versions. There are no plans for multiple incompatible versions. Instead, the plan is to keep the ABI compatible forever, using symbol versioning if necessary. Therefore I've changed the name of the source package from liblopsub1 to liblopsub. > * installation instructions don't really belong in the man page -- if you > can read it, you've already managed to install the package. Right. OTOH, the instructions might be helpful for the web page, which is just the html version of lopsub.7. I've moved the instructions to the README file, and adjusted lopsub.7 slightly. > * please copy the description for liblopsub1 to liblopsub-dev; it currently > says just "This package contains the development environment for the > lopsub library." It's pointless to require the user to check the other > package -- other libraries alter merely the last part. Also, it's -dev > what users pull by hand. Done. > * is there a reason for shipping the static library? Static linking is > frowned upon in a distribution -- whenever the library gets updated, > every reverse dependency has to be recompiled; this is especially nasty > for security updates. The main reason I've kept it is that the Debian Policy Manual says The static library (libraryname.a) is usually provided in addition to the shared version. But yes, nobody needs the static library, so I've removed it from the build. > * (bonus) The nicely documented process for building the example looks > like something that could be turned into an autopkgtest. Unlike > build-time tests, autopkgtests are run against installed packages, > the way an user would. That's of course extra effort, by no means > required -- but, extra testing is always good. I guess I need some help here. https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html describes the format of debian/tests/control, but does not say how to set up the test environment. Since the tests do not need to run as root, and do not access the network either, a simple chroot environment should be fine. But how do I set up such an environment for use with autopkgtest? > But in general, the package already seems to be in a releasable state. > Could you please change "UNRELEASED" to "unstable" so it can be uploaded? Done. Please have a final look. If everything is fine, I can merge the various topic branches to master (so that master becomes what is pu now), and tag the result as v1.0.3. Thanks Andre -- Max Planck Institute for Developmental Biology Max-Planck-Ring 5, 72076 Tübingen, Germany. Phone: (+49) 7071 601 829 http://people.tuebingen.mpg.de/maan/ signature.asc Description: PGP signature
Bug#927743: RFS: lablie/0.6.0-1 [ITP]
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "lablie": * Package name: lablie Version : 0.6.0-1 Upstream Author : Miroslav Kravec * URL : https://gitlab.com/kravemir/lablie https://kravemir.gitlab.io/lablie/ Section : utils It builds those binary packages: lablie - CLI tool for printable labels generation from SVG templates To access further information about this package, please visit the following URL: https://mentors.debian.net/package/lablie Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/lablie/lablie_0.6.0-1.dsc This is the first upload: * Initial release (Closes: #927737) This is finished packaging work of previous RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907809#12, which had violated policies about convenience copies of code. Also, the package and whole project was renamed. Previous name, svg-labels, was pretty much generic, and the name had been already used in an another existing project. Kind regards, Miroslav Kravec
Bug#927283: RFS: lebiniou/3.31-1 -- displays images that evolve with sound
[2019-04-18 13:21] Olivier Girondel > On 4/18/19 12:24 PM, Dmitry Bogatov wrote: > > Looks fine. Are you sure you want to upload into unstable now, during > > freeze? It may cause inconvenience should need to fix RC bug in > > previous version arise. > > Hi Dmitry, > No problem, this can wait. I was not implying that I refuse to upload. I can upload as-is, into unstable (but consider possible interactions with release-team) or you can s/unstable/experimental/ and I will upload to experimental. -- Note, that I send and fetch email in batch, once every 24 hours. If matter is urgent, try https://t.me/kaction --
Bug#927363: RFS: urlwatch/2.17-1
[2019-04-18 15:30] Maxime Werlen > I am looking for a sponsor for my package "urlwatch" > > * Package name: urlwatch >Version : 2.17-1 >Upstream Author : Thomas Perl > * URL : https://thp.io/2008/urlwatch/ > * License : BSD-3-clause >Section : web > > It builds those binary packages: > urlwatch - monitors webpages for you > > To access further information about this package, please visit the > following URL: > https://mentors.debian.net/package/urlwatch > > Alternatively, one can download the package with dget using this command: > dget -x > https://mentors.debian.net/debian/pool/main/u/urlwatch/urlwatch_2.17-1.dsc > > More information about urlwatch can be obtained from > https://github.com/thp/urlwatch. > > Changes since the last upload: > > urlwatch (2.17-1) unstable; urgency=medium > > * New upstream release > * Handling .gitignore properly in d/.gitignore Into unstable? Are you sure? During freeze we usually upload into experimental, unless you are going to get unblock from release team. Otherwise fine. -- Note, that I send and fetch email in batch, once every 24 hours. If matter is urgent, try https://t.me/kaction --
Bug#927738: marked as done (RFS: scdoc/1.9.4-1)
Your message dated Mon, 22 Apr 2019 11:17:20 +0200 with message-id <20190422091720.ga14...@angband.pl> and subject line Re: Bug#927738: RFS: scdoc/1.9.4-1 has caused the Debian Bug report #927738, regarding RFS: scdoc/1.9.4-1 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.) -- 927738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "scdoc" * Package name : scdoc Version : 1.9.4-1 Upstream Author : Drew DeVault * Url : https://git.sr.ht/~sircmpwn/scdoc * Licenses : MIT Programming Lang : C Section : text scdoc is a tool designed to make the process of writing man pages more friendly. It reads scdoc syntax from stdin and writes roff to stdout, suitable for reading with man(1). It builds those binary packages: * scdoc To access further information about this package, visit the following URL: https://mentors.debian.net/package/scdoc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scdoc/scdoc_1.9.4-1.dsc Alternatively, you can access package debian/ directory via git from URL: https://salsa.debian.org/bisco-guest/scdoc.git More information about scdoc can be obtained from https://git.sr.ht/~sircmpwn/scdoc Changes since last upload: * New upstream release (Closes: 927734) * Refreshed patch * Fix d/watch * d/rules: Set PCDIR to /usr/share/pkgconfig * d/control: Readd multiarch hints cheers, Birger --- End Message --- --- Begin Message --- On Mon, Apr 22, 2019 at 10:36:29AM +0200, Birger Schacht wrote: > * Package name : scdoc > Version : 1.9.4-1 > Changes since last upload: > > * New upstream release (Closes: 927734) > * Refreshed patch > * Fix d/watch > * d/rules: Set PCDIR to /usr/share/pkgconfig > * d/control: Readd multiarch hints ✓ -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄--- End Message ---
Bug#927738: RFS: scdoc/1.9.4-1
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "scdoc" * Package name : scdoc Version : 1.9.4-1 Upstream Author : Drew DeVault * Url : https://git.sr.ht/~sircmpwn/scdoc * Licenses : MIT Programming Lang : C Section : text scdoc is a tool designed to make the process of writing man pages more friendly. It reads scdoc syntax from stdin and writes roff to stdout, suitable for reading with man(1). It builds those binary packages: * scdoc To access further information about this package, visit the following URL: https://mentors.debian.net/package/scdoc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/scdoc/scdoc_1.9.4-1.dsc Alternatively, you can access package debian/ directory via git from URL: https://salsa.debian.org/bisco-guest/scdoc.git More information about scdoc can be obtained from https://git.sr.ht/~sircmpwn/scdoc Changes since last upload: * New upstream release (Closes: 927734) * Refreshed patch * Fix d/watch * d/rules: Set PCDIR to /usr/share/pkgconfig * d/control: Readd multiarch hints cheers, Birger
