Package: wnpp
Severity: wishlist

I'm opening a bug to document intent to re-introduce 'libnss-mysql':
https://tracker.debian.org/pkg/libnss-mysql

See discussion from Jing below, including links to modernized packaging.

For reference, here are all Debian bugs related to the old libnss-mysql:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;dist=unstable;ordering=normal;repeatmerged=0;src=libnss-mysql
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=111910

I suppose that if we manage to update the package and make it compatible
with Debian style we can do an upload of it to NEW that closes this bug.

/Simon

Simon Josefsson <si...@josefsson.org> writes:

> Jing Luo <jing@jing.rocks> writes:
>
>> Hi,
>>
>> Does trisquel accept trisquel-specific/native packages? I failed to
>> find any documentation on this.
>>
>> I have a package called libnss-mysql, which was removed from Debian
>> around 2015 because it was "unmaintained, upstream dead, low
>> popularity contest score, nobody uses it". Savannah has been depending
>> on libnss-mysql for about two decades; we use it for authenticating
>> member vcs access. Since it was removed from Debian (and later
>> Trisquel), Bob Proulx has been maintaining libnss-mysql, even though
>> neither the original author nor debian developers touch it
>> anymore. Very recently, Bob "official" took over/hard-forked it and
>> made a new upstream release [1]. So we can say that the upstream is
>> alive again.
>>
>> Since I am pretty sure there is no hope reintroduce libnss-mysql into
>> Debian because of the lack of interest (quite a few libnss libraries
>> are also unmaintained in Debian), I think it would be a good thing to
>> have it packaged for Trisquel, because GNU uses/needs it. Therefore I
>> would like to maintain the deb packaging of libnss-mysql, and I pushed
>> a WIP tree here [2].
>
> I am happy to sponsor an upload of this into Debian, we'll just have to
> review the packaging for latest Debian standards wrt copyright/license
> etc.  Indeed it was removed a long time ago:
>
> https://tracker.debian.org/pkg/libnss-mysql
>
> If you agree, could you add gitlab.trisquel.org username 'jas' to your
> project and we could co-maintain it?  Please add me as Maintainer so I
> can add CI/CD-style integration, it would be cool to see if using Debian
> Salsa CI/CD pipeline works on gitlab.trisquel.org (although I recall
> using this before).
>
> It is very good that Bob did a new release!  That establishes a new
> upstream and make things clear.
>
> /Simon
>
>> Which bring me to the question in the beginning: does trisquel accept
>> packages? (how) can I submit a package to Trisquel? I recently adopted 
>> an orphaned package in Debian, so I am somewhat familiar with how
>> Debian does things.
>>
>> Note: there are a few more packages that may be in a similar situation
>> where there is no hope to introduce them into Debian, but GNU and 
>> Savannah need it. I am talking about GNU Bazzar: it was maintained by
>> Canonical, but Canonical abandoned it in 2017 and made a fork called 
>> breezy, and they explicitly expressed that they would not cooperate
>> with GNU on maintaining Bazzar (very unsurprising for Canonical to say
>> this). Since then, breezy has replaced Bazzar in Debian. From other 
>> communication channels, I heard that the GNU maintainer of Bazzar now
>> is willing to pick up the development of Bazzar. I dont speak for all 
>> Savannah hackers, but because Savannah still supports Bazzar vcs, it
>> would be a bonus point for GNU and Savannah if we can get Bazzar 
>> packages into Trisquel (again). I would volunteer as the package
>> (co-)maintainer when the time comes.
>>
>>
>> [1] https://git.savannah.gnu.org/cgit/administration/libnss-mysql.git
>> [2] https://gitlab.trisquel.org/del111/libnss-mysql
>
> _______________________________________________
> Trisquel-devel mailing list
> trisquel-de...@listas.trisquel.info
> https://listas.trisquel.info/mailman/listinfo/trisquel-devel
>

Attachment: signature.asc
Description: PGP signature

Reply via email to