Processed: bug 1062438 has no owner

2024-02-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> noowner 1062438
Bug #1062438 [wnpp] RFP: monobit -- tools for working with monochrome bitmap 
fonts
Removed annotation that Bug was owned by Gürkan Myczko .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: retitle 1062438 to RFP: monobit -- tools for working with monochrome bitmap fonts

2024-02-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 1062438 RFP: monobit -- tools for working with monochrome bitmap fonts
Bug #1062438 [wnpp] ITP: monobit -- tools for working with monochrome bitmap 
fonts
Changed Bug title to 'RFP: monobit -- tools for working with monochrome bitmap 
fonts' from 'ITP: monobit -- tools for working with monochrome bitmap fonts'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1062438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1063317: O: django-anymail

2024-02-05 Thread Scott Kitterman
Package: wnpp
Severity: normal
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Control: affects -1 src:django-anymail

I'm no longer interested in the package and no one from the Debian
Python Team expressed interest in it, so orphaning.

I've updated the package to the current upstream and updated for the
switch to hatchling, so that package is in good shape for now.  Upstream
is moderately active.

Scott K



Processed: O: django-anymail

2024-02-05 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:django-anymail
Bug #1063317 [wnpp] O: django-anymail
Added indication that 1063317 affects src:django-anymail

-- 
1063317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#826643: ITP: tn5250j -- A 5250 terminal emulator for the AS/400

2024-02-05 Thread Jeffrey Walton
It looks like tn5250j has moved to GitHub, .



Bug#1063269: ITP: python-respx -- Utility for mocking out the Python HTTPX and HTTP Core libraries.

2024-02-05 Thread Yogeswaran Umasankar
Package: wnpp
Severity: wishlist
Owner: Yogeswaran Umasankar 
X-Debbugs-Cc: debian-de...@lists.debian.org, kd8...@gmail.com

* Package name: python-respx
  Version : 0.20.2 
  Upstream Contact: Jonas Lundberg 
* URL : https://github.com/lundberg/respx
* License : BSD-3-clause
  Programming Lang: Python
  Description : Utility for mocking out the Python HTTPX and HTTP Core 
libraries.

RESPX is a mock router, capturing requests sent by HTTPX,
 mocking their responses. Inspired by the flexible query API
 of the Django ORM, requests are filtered and matched against
 routes and their request patterns and lookups. It is depends
 for some of the science packages. I would like to maintain
 this under Debian Python Team.



Bug#1062827: RFP: pydevtool -- CLI dev tools powered by pydoit

2024-02-05 Thread Drew Parsons

On 2024-02-05 18:44, Drew Parsons wrote:

building and testing.  The scipy team have created pybuild, which uses


That should read "The scipy team have created dev.py" of course.

(debian created pybuild)



Processed: ITP: qttinysa -- QT Gui for a tiny SA Spectrum Analyser

2024-02-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 1063230 ITP: qttinysa -- QT Gui for a tiny SA Spectrum Analyser
Bug #1063230 [wnpp] ITP: QtTinySA -- QT Gui for a tiny SA Spectrum Analyser
Changed Bug title to 'ITP: qttinysa -- QT Gui for a tiny SA Spectrum Analyser' 
from 'ITP: QtTinySA -- QT Gui for a tiny SA Spectrum Analyser'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1063230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1061541: marked as done (ITP: ruby-redis-client -- redis-client is a simple, low-level, client for Redis 6+.)

2024-02-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 Feb 2024 19:00:18 +
with message-id 
and subject line Bug#1061541: fixed in ruby-redis-client 0.19.1-1
has caused the Debian Bug report #1061541,
regarding ITP: ruby-redis-client -- redis-client is a simple, low-level, client 
for Redis 6+.
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.)


-- 
1061541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Vivek K J 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: ruby-redis-client
  Version : 0.19.1
  Upstream Contact: jean.bouss...@gmail.com
* URL : https://github.com/redis-rb/redis-client
* License : Expat
  Programming Lang: Ruby
  Description : redis-client is a simple, low-level, client for Redis 6+.

 Contrary to the redis gem, redis-client doesn't try to map all Redis commands
 to Ruby constructs, it merely is a thin wrapper on top of the RESP3 protocol.

 This package is a dependency of gitlab. This package will be maintained by
 Debian ruby team.
--- End Message ---
--- Begin Message ---
Source: ruby-redis-client
Source-Version: 0.19.1-1
Done: Vivek K J 

We believe that the bug you reported is fixed in the latest version of
ruby-redis-client, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1061...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vivek K J  (supplier of updated ruby-redis-client package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 26 Jan 2024 11:23:01 +0530
Source: ruby-redis-client
Binary: ruby-redis-client
Architecture: source all
Version: 0.19.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Vivek K J 
Description:
 ruby-redis-client - Simple low-level client for Redis 6+
Closes: 1061541
Changes:
 ruby-redis-client (0.19.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1061541)
Checksums-Sha1:
 6e543b3d7b3221811c58b0d09d9c6408c221c1cf 2086 ruby-redis-client_0.19.1-1.dsc
 eebe9e80521881a59e62c4b6caebd96b32773420 23983 
ruby-redis-client_0.19.1.orig.tar.gz
 70edadf38b65d5b81e6b4c69912b459ac7ff6246 2744 
ruby-redis-client_0.19.1-1.debian.tar.xz
 1d8ba39bb71e45af9deca6e4d30e0d7d95d60e90 23508 
ruby-redis-client_0.19.1-1_all.deb
 7307fa14422230a9356b7106acdcfbac7f108e25 9557 
ruby-redis-client_0.19.1-1_amd64.buildinfo
Checksums-Sha256:
 e7811f51e32481528efe642d61b812ce8091a9431156d682a63e8dbac68e3eb6 2086 
ruby-redis-client_0.19.1-1.dsc
 9aeefcaf692d07c347ba20db455141963277a5879c3490d82219b86b677c5f08 23983 
ruby-redis-client_0.19.1.orig.tar.gz
 825782b0aad406ffe90c461826a840341ff85a431bbc06baa01adc169c543e42 2744 
ruby-redis-client_0.19.1-1.debian.tar.xz
 d4a2044a453f22cf72ba290e1a3cb4b213697283a16812755766bc6ae4b3894e 23508 
ruby-redis-client_0.19.1-1_all.deb
 f978d23141974d1c608a83c3e99aa8d6f427d96cc0444acbe1e6d3d9791f9be1 9557 
ruby-redis-client_0.19.1-1_amd64.buildinfo
Files:
 b6559b488a97b5c600a4e4df2c72c160 2086 ruby optional 
ruby-redis-client_0.19.1-1.dsc
 8a16ff6329c94b5739e90af42ffeef76 23983 ruby optional 
ruby-redis-client_0.19.1.orig.tar.gz
 16e38606b511c6176a112ba73c9114c0 2744 ruby optional 
ruby-redis-client_0.19.1-1.debian.tar.xz
 7831fd17929dbfcd3e6bfc4515627ae2 23508 ruby optional 
ruby-redis-client_0.19.1-1_all.deb
 4ebebc37ba06cb5dab84faefd9a3a1d0 9557 ruby optional 
ruby-redis-client_0.19.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmW+VvMACgkQj1PgGTsp
S3Xd7RAAlSThHvWWrN6F8swgA2MvmTcjnaXUPhHXWcy0DLPvczFG7CqblHPOEETI
Sy+4KyJcsXVHiZ5f+yaZL8dYKuJc1FBkUZJD3P26UiwAvdQr+K/T//+LQHzZOPny
5Zpj/amVTYAFr9mpm7xN01vGb8JB8wI4T7UOqOrxFJowHma8LdIQw78Wvva6zO5S
YqeFz3psfmbR02cc+vOebGGG62X9LH/m+jxI84FNGo+yvCylCCvxrV4Tme6Uk5xh
+zGjT++f+mDDqF3EnHCv1qc6gc3/D1KqAbRg4QfksuxPWL8AicONsKn1p3pnDLOR
7xi15jonyET7BeVnPhWImE7cjC2wmbSdUzsS6lBuDoiX4r2KHmduOZXHB7byX3jt
JB+BGe1kIkoVQdY3+x2W2SkW5/IpZJZp88mSMUP5qQeDMGgNXPFlsBziVOr35zhZ
NOMOCQXI3QkdfwVM78QK5KspaPdTGML66vSwL1HVW17+EEzIuHgq6QsGLNwa8983
kFJWkrFV1rDoFykzYKfVWWKUcQ3Cz6+DYPyyWa9yYhox65YvxM9J+WJlgoCvyhGC

Bug#1009125: marked as done (ITP: php-fruitcake-php-cors -- Cross-origin resource sharing library for the Symfony HttpFoundation)

2024-02-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 Feb 2024 19:00:18 +
with message-id 
and subject line Bug#1009125: fixed in php-fruitcake-php-cors 1.3.0-1
has caused the Debian Bug report #1009125,
regarding ITP: php-fruitcake-php-cors -- Cross-origin resource sharing library 
for the Symfony HttpFoundation
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.)


-- 
1009125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp

* Package name: php-fruitcake-php-cors
  Upstream Author : Barry vd. Heuvel 
* License : MIT
  Description : Cross-origin resource sharing library for the Symfony 
HttpFoundation
 Library and middleware enabling cross-origin resource sharing for your
 http-{foundation,kernel} using application. It attempts to implement the W3C
 Recommendation for cross-origin resource sharing.

Regards
Katharina

--
--- End Message ---
--- Begin Message ---
Source: php-fruitcake-php-cors
Source-Version: 1.3.0-1
Done: Robin Gustafsson 

We believe that the bug you reported is fixed in the latest version of
php-fruitcake-php-cors, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1009...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robin Gustafsson  (supplier of updated php-fruitcake-php-cors 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Jan 2024 00:04:52 +0100
Source: php-fruitcake-php-cors
Binary: php-fruitcake-php-cors
Architecture: source all
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Robin Gustafsson 
Description:
 php-fruitcake-php-cors - Cross-origin resource sharing library for Symfony 
HttpFoundation
Closes: 1009125
Changes:
 php-fruitcake-php-cors (1.3.0-1) unstable; urgency=medium
 .
   [ Katharina Drexel ]
   * Initial packaging
 .
   [ Robin Gustafsson ]
   * Initial release (Closes: #1009125)
Checksums-Sha1:
 041d68200955c846dbbd6b49a25053b24827ed8f 2291 
php-fruitcake-php-cors_1.3.0-1.dsc
 23fc52256a3f7b4210293c643da525cd910b5410 8956 
php-fruitcake-php-cors_1.3.0.orig.tar.xz
 ee2d6c4b4d6d005729e2379840076595d877d2ba 3072 
php-fruitcake-php-cors_1.3.0-1.debian.tar.xz
 754e49db84517716b0dade27ccee5dcedf668080 6824 
php-fruitcake-php-cors_1.3.0-1_all.deb
 310ff076ec32d91aaf8fea8eeddd871e283e418e 8628 
php-fruitcake-php-cors_1.3.0-1_amd64.buildinfo
Checksums-Sha256:
 6eef598cd9ca8f2cb1b5b006bea52faa60bddef6911fb517c8425abcd14d5dcc 2291 
php-fruitcake-php-cors_1.3.0-1.dsc
 47312f820cbfa15dbacd01e03a9bac440a61e1bdc1a74c6315d511f3714da85b 8956 
php-fruitcake-php-cors_1.3.0.orig.tar.xz
 89dfe68e33940e006a715d67ec2f198b6ba90d3605a0ff731e64ebe65b0d06b7 3072 
php-fruitcake-php-cors_1.3.0-1.debian.tar.xz
 5ad282da312fd4b4ff5176c4f64ffe65d8fc75b81c7dcfbf30a98e3e910bcdf2 6824 
php-fruitcake-php-cors_1.3.0-1_all.deb
 d153fbf88e0beae80e401dea5fff11015ab27445caa9e157557a6edafbb93d7f 8628 
php-fruitcake-php-cors_1.3.0-1_amd64.buildinfo
Files:
 69463c9c56d3bd9c4961eb8a26766602 2291 php optional 
php-fruitcake-php-cors_1.3.0-1.dsc
 bf881ffa82c95dbb102e05a8e7e4f5a0 8956 php optional 
php-fruitcake-php-cors_1.3.0.orig.tar.xz
 caf3967d7a30df54c0ed088b78b1b514 3072 php optional 
php-fruitcake-php-cors_1.3.0-1.debian.tar.xz
 769def92110bc19f896eb0b851bafcc1 6824 php optional 
php-fruitcake-php-cors_1.3.0-1_all.deb
 d42c06cb0383edcb95b695f03938c1de 8628 php optional 
php-fruitcake-php-cors_1.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEESLC/dKNbQnm0zJBRnS1ied5zQWEFAmW23fIACgkQnS1ied5z
QWF7+RAAjs58GbS+XPn+QKzaXqAfdwJw1y+TvL2QaE+zAsoKerW7DgUaHKAoP+AA
AoIYAnaXPzETMPdX9gVls7NPdV4SHwkgI+vn+brjgz77ZOETxZWOxWev+goMqtQd
TGtogoAX9mEb47fvDMsGM0ykXYvaXgEhJTtQ1TRpp9QDDVRUEGebVG4brPnj7n7c
H+tkQwUiGyuAindP4ULRhValmDZb/92NPge3qzyZ802+TIZtfvpfip3wVf/XgyfA
CsuHHLA76TpSfUzmOoAc/gT7AH9psX6nX/yKzD0LEGk/4Uij8WlAtXHti1jJwIxa
YWS6P6u2NDNw1egcl1s5i1jkyhUYvYY9IdpG7uASO1T0HZqSTd914UXWM6UMMkoz
Qt9KBrw3SIDyVWUhD8rg04hbX4DyfBk3AyiwQTBODWlrYAp5O+3mw+nHji1a9v2t
2N/7ZnKlPfoSKbbgtEkH4Egd48swVZb43QFijOPdZ6i/YWOX1KH/1oAiBt9bUn4y

Bug#1063230: ITP: QtTinySA -- QT Gui for a tiny SA Spectrum Analyser

2024-02-05 Thread Patrick Winnertz
Package: wnpp
Severity: whishlist
Owner: Patrick Winnertz 
X-Debbugs-Cc: debian-de...@lists.debian.org

Package name: qttinysa
Version : 0.9.1
Upstream Author : Ian  (g4ixt)
URL : https://github.com/g4ixt/QtTinySA
License : GPL-v3
Programming Lang: Python
Description : QT Gui for a tiny SA Spectrum Analyser

A python program to replicate some of the TinySA Ultra on-screen
commands on the PC with a 3D plotting possibility. 

-- 
Dr. Patrick Winnertz
Tel.: 0049 (0)163/2536369
Leostraße 26
68789 St. Leon-Rot



Bug#1062827: RFP: pydevtool -- CLI dev tools powered by pydoit

2024-02-05 Thread Drew Parsons

On 2024-02-03 21:07, c.bu...@posteo.jp wrote:

I checked upstream README.md.
I have no clue what this is.

Can someone explain please?

Am 03.02.2024 18:05 schrieb dpars...@debian.org:

Package: wnpp

* Package name: pydevtool
* URL : https://github.com/pydoit/pydevtool
  Description : CLI dev tools powered by pydoit

Python dev tool. doit powered, integration with:
- click and rich for custom CLI
- linters: pycodestlye, pyflakes



I can only explain phenomenologically, based on what scipy is trying to 
do with it.


scipy uses it in a dev.py script,
https://github.com/scipy/scipy/blob/eb6d8e085087ce9854e92d6b0cdc6d70f0ff0074/dev.py#L125
dev.py is a developers' tool used to run scipy's tests,
https://scipy.github.io/devdocs/dev/contributor/devpy_test.html
See also
https://scipy.github.io/devdocs/building/index.html

pydevtool provides a cli submodule, from which scipy uses 
UnifiedContext, CliGroup, Task
These are used to create and organise a Test class, keeping track of 
parameters used when running tests,

such as verbosity level or install prefix.

pydevtool itself is built on top of doit, which is a framework for 
managing general tasks.


The dev tasks in question here are building and testing the package (we 
want to use it for the test tasks).


dev.py also has other tasks

Probably the best way to think about it is that dev.py is scipy's 
counterpart to debian's pybuild, providing a solution to the challenge 
of building a complex python package.  We've created pybuild, which uses 
dhpython as a framework for managing the tasks involved in building and 
testing.  The scipy team have created pybuild, which uses pydevtool 
(together with click, doit) as a framework for managing the tasks.


`grep Task dev.py` gives a list of other tasks that dev.py can handle:
Test
RefguideCheck
Build
Test
Bench
Mypy
Doc
RefguideCheck

So pydevtool is used to help manage the execution of these various 
tasks.




Processed: Add bug block information

2024-02-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 1032204 by 1063094
Bug #1032204 [src:plover] plover: Please upgrade to new version 4.0.0.dev12
1032204 was not blocked by any bugs.
1032204 was not blocking any bugs.
Added blocking bug(s) of 1032204: 1063094
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1032204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: O: python-sparkpost

2024-02-05 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:python-sparkpost
Bug #1063171 [wnpp] O: python-sparkpost
Added indication that 1063171 affects src:python-sparkpost

-- 
1063171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1063171: O: python-sparkpost

2024-02-05 Thread Scott Kitterman
Package: wnpp
Severity: normal
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Control: affects -1 src:python-sparkpost

I'm no longer interested in the package (it was only packaged to support
django-anymail, which is also about to be orphaned).

This is an interface to a proprietary mail service.  The company was
acquired in 2021 and nothing has happened with the package upstream
since then.

The package itself is in reasonably good condition.  There is one Python
3.12 related issue that will be addressed in the upload that orphans the
package.

Scott K



Bug#1012289: RFH: lintian -- Debian package checker

2024-02-05 Thread Bastien Roucariès
Le lundi 5 février 2024, 12:42:04 UTC Bill Allombert a écrit :
> On Mon, Feb 05, 2024 at 12:28:02PM +0100, Axel Beckert wrote:
> > Hi Bill,
> > 
> > Bill Allombert wrote:
> > > By the way, what happened to lintian.debian.org ?
> > 
> > Seems as if someone (not me, just noticed it today when
> > "private/refresh-data" failed…) pulled the plug on at least the DNS
> > name. Probably because it hasn't been updated since Felix' try to
> > rewrite it, which AFAIK was never finished, but the old thing also no
> > more worked. (There's probably a lot of legacy code in
> > "lib/Lintian/Output" related to one of these two website generations,
> > maybe even both.)
> 
> I used to generate my own copy of it because the official one was
> out of date. 

Help here is welcome. I really like the l.d.o site particularly the graph
> 
> > IMHO it's generally a good thing, except that it would have been
> > better to redirect it to the according UDD pages instead.
> 
> Yes, because there are ton of places still linking to lintian.debian.org
> (e.g. wikipedia). We should ask DSA to redirect to salsa or UDD.
> 
> Cheers,
> 



signature.asc
Description: This is a digitally signed message part.


Bug#1012289: RFH: lintian -- Debian package checker

2024-02-05 Thread Bill Allombert
On Mon, Feb 05, 2024 at 12:28:02PM +0100, Axel Beckert wrote:
> Hi Bill,
> 
> Bill Allombert wrote:
> > By the way, what happened to lintian.debian.org ?
> 
> Seems as if someone (not me, just noticed it today when
> "private/refresh-data" failed…) pulled the plug on at least the DNS
> name. Probably because it hasn't been updated since Felix' try to
> rewrite it, which AFAIK was never finished, but the old thing also no
> more worked. (There's probably a lot of legacy code in
> "lib/Lintian/Output" related to one of these two website generations,
> maybe even both.)

I used to generate my own copy of it because the official one was
out of date. 

> IMHO it's generally a good thing, except that it would have been
> better to redirect it to the according UDD pages instead.

Yes, because there are ton of places still linking to lintian.debian.org
(e.g. wikipedia). We should ask DSA to redirect to salsa or UDD.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Bug#1012289: RFH: lintian -- Debian package checker

2024-02-05 Thread Axel Beckert
Hi Bill,

Bill Allombert wrote:
> By the way, what happened to lintian.debian.org ?

Seems as if someone (not me, just noticed it today when
"private/refresh-data" failed…) pulled the plug on at least the DNS
name. Probably because it hasn't been updated since Felix' try to
rewrite it, which AFAIK was never finished, but the old thing also no
more worked. (There's probably a lot of legacy code in
"lib/Lintian/Output" related to one of these two website generations,
maybe even both.)

IMHO it's generally a good thing, except that it would have been
better to redirect it to the according UDD pages instead.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#1012289: RFH: lintian -- Debian package checker

2024-02-05 Thread Bill Allombert
On Mon, Feb 05, 2024 at 03:26:29AM +0100, Axel Beckert wrote:
> Hi,
> 
> Bastien Roucariès wrote:
> > Le dimanche 4 février 2024, 14:02:58 UTC Bill Allombert a écrit :
> > > Areyou still available as lintian maintainer ? It sure would need an 
> > > upload.
> > I can
> > 
> > I am doing some pull request update
> 
> By coincidence I started to work on Lintian today (well, actually
> yesterday) again, too, but saw these two mails only afterwards. Mostly
> fixed the systemd/udev/usrmerge related test suite failures as well as
> merged some of the open merge requests.
> 
> Let's try together to get a release done soon.

By the way, what happened to lintian.debian.org ?

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Bug#698988: O: nvi - 4.4BSD re-implementation of vi

2024-02-05 Thread Tobias Heider
On Sat, Jan 26, 2013 at 12:38:07AM +, Stuart Prescott wrote:
> Package: wnpp
> Severity: normal
> 
> The maintainer for the "nvi" package has indicated that he is unable to
> maintain this package for the time being. I'm marking this package as orphaned
> now. If you want to be the new maintainer, please take it -- see
> http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions
> how to adopt a package properly.
> 
> Description-en: 4.4BSD re-implementation of vi
>  Vi is the original screen based text editor for Unix systems.
>  It is considered the standard text editor, and is available on
>  almost all Unix systems.
>  .
>  Nvi is intended as a "bug-for-bug compatible" clone of the original
>  BSD vi editor. As such, it doesn't have a lot of snazzy features as do
>  some of the other vi clones such as elvis and vim. However, if all
>  you want is vi, this is the one to get.
> 

Looks like this is still orphaned over ten years later.

As an active nvi user I would love to step up and help, but the biggest
problem I see is that the choice of upstream project. Since the original
is gone there isn't a clear successor.

The BSDs all have their own forks which diverged over time (and those don't
build on Linux).
The other two options there are today are https://repo.or.cz/nvi.git which
d/control currently points to and more recently https://github.com/lichray/nvi2.

The first has a very low commit frequency (last commit was 2020, before
that 2016) and sticks very closely to the original source. nvi2 has added
new features such as multibyte support and is starting to receive bug fixes
and features from the different *BSD forks.

I have been thinking of proposing a new package for nvi2 but maybe it would
make more sense to move this one to the more active upstream.  It looks like
some of the issues we are carrying patches for in Debian might be fixed there
already and if not they seem active enough to merge our fixes.

What would be the best way forward here? ITA and eventually switch the upstream
or start a new package and let this one continue its slow death?

Tobias