Concern about maintain on Debian official repositories

[lucascastro]

Is there any concern about maintain wallet on Debian official repository?

I have noticed that wallet software keeps the debian/ directory updated for latest wallet release,
therefore I was wondering if wallet upstream is concerned about Debian?

I also hit the https://www.eyrie.org/~eagle/software/debian.html and could notice Russ point he haven't chance to maintain the software on Debian.

Would it be good I maintain the wallet on Debian?

[whm]

If you are going to work on adding wallet to Debian there are some changes that I have not pushed up to Russ. Since Russ has said that he does not have time to work on wallet I would love it if it could get into Debian. Bill

…

Sent from my iPhone

On Jul 23, 2021, at 12:46 PM, Lucas Castro ***@***.***> wrote:  Is there any concern about maintain wallet on Debian official repository? I have noticed that wallet software keeps the debian/ directory updated for latest wallet release, therefore I was wondering if wallet upstream is concerned about Debian? I also hit the https://www.eyrie.org/~eagle/software/debian.html and could notice Russ point he haven't chance to maintain the software on Debian. Would it be good I maintain the wallet on Debian? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[lucascastro]

It'd be nice if you push all of them up to Russ. Debian has some policies about patching the source, in the end, all the patches should be forward to upstream.

[rra]

GitHub "helpfully" deleted my notification settings for all of my repositories including the ones I own, so I am just now seeing this thread. Apologies for the delayed response.

I think you also reached out in email, but to summarize for everyone else: I no longer use wallet myself and probably won't in the future, so ideally someone else should take over development. I'm willing to put in a bit of work merging patches and pushing out releases periodically while other people are using it, but only when I have some spare time, which has been very limited lately. Thus, everything is going to struggle when bottlenecked through me. I'd be happy to help with a transition to another maintainer and/or team if there are people who want to take over development.

Given that, I'm also not willing to upload wallet to Debian myself since I can't promise to maintain it, but I don't know of any reasons why this couldn't be done if someone else is willing to maintain it.

[macrotex]

I am more than willing to contribute to the ongoing development. Maybe JR or WHM would want to lead? (This is AL, by the way). I will also see if anyone else at Stanford is willing to step up.

[lucascastro]

On 9/4/21 3:35 PM, Russ Allbery wrote: GitHub "helpfully" deleted my notification settings for all of my repositories including the ones I own, so I am just now seeing this thread. Apologies for the delayed response. I think you also reached out in email, but to summarize for everyone else: I no longer use wallet myself and probably won't in the future, so ideally someone else should take over development. I'm willing to put in a bit of work merging patches and pushing out releases periodically while other people are using it, but only when I have some spare time, which has been very limited lately. Thus, everything is going to struggle when bottlenecked through me. I'd be happy to help with a transition to another maintainer and/or team if there are people who want to take over development.

I'm really interested on this, and that's on my todo list. Right now, I'm working on my mail infrastructure migration, and after that I will start working on wallet. For sure I will need help on transition, I've noticed that I'll need to study a little bit for wallet maintaince, I pretended to start documenting the code and writing some notes how stuffs works before patching.

Given that, I'm also not willing to upload wallet to Debian myself since I can't promise to maintain it, but I don't know of any reasons why this couldn't be done if someone else is willing to maintain it.

I can maintain it on Debian. About maintain it on Debian, I'll start with a testing environment and try to write some documents and notes of examples on how to use wallet, and how Wallet can fit some environments.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALJN6RPKASEEYBWRNXSKL3UAJRH5ANCNFSM5A4S3NWA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Lucas Castro

[rra]

Okay, it sounds like there's interest. Probably the best thing to do once folks are ready is to create a new organization and move this repository to that, which will make it easy to add additional people to the ACL.

[whm]

I have quite a few patches that I have applied to Russ's latest release that we use at Dropbox. The patches include fixes for AD support, encrypting file and password objects, allowing the use of a custom password generator, and the addition of a checkfile command. But, my packaging needs a bunch of work. I have gotten it to build on Debian just fine, but the patches should be merged into something sensible. I am interested in cleaning this up and bumping the version of the wallet upstream source whether it is in Russ's repo or a new one. Like everyone I am quite busy and my desires generally exceed the time I have to get things done. Note, I my Debian patches are available on my GitHub account at https://github.com/whm/wallet .

Lucas are you a Debian developer?

Bill

[lucascastro]

On 9/6/21 10:45 PM, Bill MacAllister wrote: I have quite a few patches that I have applied to Russ's latest release that we use at Dropbox. The patches include fixes for AD support, encrypting file and password objects, allowing the use of a custom password generator, and the addition of a checkfile command. But, my packaging needs a bunch of work. I have gotten it to build on Debian just fine, but the patches should be merged into something sensible. I am interested in cleaning this up and bumping the version of the wallet upstream source whether it is in Russ's repo or a new one. Like everyone I am quite busy and my desires generally exceed the time I have to get things done. Note, I my Debian patches are available on my GitHub account at https://github.com/whm/wallet <https://github.com/whm/wallet> .

About repository, My plan is to set up a gitlab instance. Is it fine for you submit patches?

Lucas are you a Debian developer?

Actually I maintain 3 (three) packages on Debian. I was out of development, of course I'll need to review the Debian Maintainer Guide (debmake-doc) and Debian reference. I'll not be so busy for next two months (I guess), during this time I pretend to get all this done. I'll need help to review patches.

Bill — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#81 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALJN6UHML3JQUHYJD7Q2XDUAVVDDANCNFSM5A4S3NWA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

-- Lucas Castro

[whm]

On 2021-09-07 07:40, Lucas Castro wrote: About repository, My plan is to set up a gitlab instance. Is it fine for you submit patches?

Haven't used gitlab before, but I don't expect that to be a problem. If you setup the repo there that is where I will submit patches.

> Lucas are you a Debian developer? > Actually I maintain 3 (three) packages on Debian.

Great!

I'll not be so busy for next two months (I guess), during this time I pretend to get all this done. I'll need help to review patches.

I'll help. I'll try to be timely, but I get distracted easily. It is great this is moving forward. Bill

…

-- Bill MacAllister ***@***.***> A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?

[whm]

On 2021-09-07 09:28, Bill MacAllister wrote: I'll help. I'll try to be timely, but I get distracted easily.

See, I do get distracted. How do we move this forward? What can I do? The current state of my build is that I have been patching the debian branch and building from there. This stems from having problems, years ago now, updating master and then getting a debian build out of it. I just avoided the problem by not updating the wallet version and just incrementing the debian version. Currently I am applying 18 patches. Should I just start work on applying my patches to Russ's latest master and work from there? Russ, I know that the repository is old and does not follow more modern practice. Do you have suggestions to for restructuring the repo? Bill

…

-- Bill MacAllister ***@***.***> "Can't sing louder than the guns when I'm gone, so I guess I'll have to do it while I'm here." Phil Ochs

[lucascastro]

Hello, back o this.
After about two year after this, if someone still interested on this, I'm going to set an mailiing list for the wallet,
set a testing environment and try to development some feature from TODO list.

rra, mhm, macrotex, any cocern what should be the best way keep in touch about development/testing/releases?

[whm]

On 2023-06-22 17:03, Lucas Castro wrote: Hello, back o this. After about two year after this, if someone still interested on this, I'm going to set an mailiing list for the wallet, set a testing environment and try to development some feature from TODO list. rra, mhm, macrotex, any cocern what should be the best way keep in touch about development/testing/releases? -- Reply to this email directly, view it on GitHub [1], or unsubscribe [2]. You are receiving this because you commented.Message ID: ***@***.***> Links: ------ [1] #81 (comment) [2] https://github.com/notifications/unsubscribe-auth/AAHXMBPHZ23BQ3J2FKJBKCTXMTMLVANCNFSM5A4S3NWA

A mailing list would be a good start. I have continued to develop wallet functionality for both personal use and use at work. My work is at https://github.com/whm/wallet. It is basically a set of quilt patches on top of Russ's repository. I would really like to see my changes as part of a wallet package in an official Debian release. My changes include: * Support for arbitrary ldap-attr filters * Encryption of password and file objects at rest * Removal of support for webauth * Support for AD KDCs * Added checkfile command to download file/password objects when they change * Expand the password generation controls I have additionally written a version of the wallet-client in Perl. We should consider creating a package for the perl client. It allows wallet to be used on systems where a wallet c client has not been built. I have also done some work on implementing wallet name spaces. Name spaces allows the delegation of password and file creation to non-ADMIN users. This is mostly documentation of how to configure wallet defaults, but there is still some outstanding work. Users that are owners of an object need to be able to set the ACLs on the object. Currently only ADMINs can set ACLs. One thing that I have been ignoring is the database. Russ's has said in the past that it is something that he would like to re-work if he ever got the time. We probably should take a second look at that as well. I have talked to Russ about becoming a Debian developer, but have only taken the initial halting steps. It is unlikely that I will make much progress in that direction this summer, but would be very happy to work with you in any wallet work you want to do. Bill

…

-- "What can be asserted without evidence can also be dismissed without evidence." Christopher Hitchens

[chuhn]

FTR: Since Trixie Debian ships official wallet packages maintained by @whm. This issue should be closed.