Re: i686 require SSE4.1-capable processor?
On Tue, 2024-07-16 at 14:36 +0200, Philipp Kern wrote: > Hi, > > On 2024-07-16 14:14, Andrey Rakhmatullin wrote: > > On Tue, Jul 16, 2024 at 12:46:01PM +0100, Phil Wyett wrote: > > > > > > Packages built for the i386 arch need to conform to the i386 > > > > > > baseline, > > > > > > which is currently i686. If a package contains a newer instruction > > > > > > it's a > > > > > > bug in that package and gcc is not the cause of it, the package is. > > > > > > https://buildd.debian.org/status/fetch.php?pkg=filezilla=i386=3.63.0-1%2Bdeb12u3=1704758683=0 > > > > > > indeed contains at least one compile command with -msse4.1. > > > > [...] > > > > > Yeah, I have discovered that it is indeed a cause of the d/rules in > > > > > the > > > > > filezilla package. I blame having taken over it recently, and still > > > > > haven't learned the ins and outs of it. > > > > It'd also be good to document reasons for such workarounds next time. > > > > Both the changelog and the surrounding comments don't really tell you > > > > what to watch out for in a new gcc version. There's no bug reference > > > > (GCC or Debian bug) or example error message or a pointer to possible > > > > miscompilation. > > > The addition to 'debian/rules' was in response to the below. > > > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053804 > > That bug report looks like the outcome of the "addition", not the > > reason > > for it. Did you mean > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034195 ? > > Yeah it'd have been good if there had been a link to that. E.g. in the > changelog or as a comment in debian/rules. > > > The interactions in both bugs look very weird to me, especially when > > the > > same person proposes compiling software with SSE4.1 and then complains > > that it fails on older hardware, and the reason for closing the newer > > bug > > also looks weird to me. I think it should be reopened and bumped to RC. > > I'm a bit confused as to why Filezilla bundles an ancient version of > Putty. The official Putty code does compile *that specific unit*[1] with > -msse4.1 but there is also a gate in the code to only use the > accelerated path if cpuid signals support for the new instructions. As > far as I can see you added the flag to all source files in the putty/ > subtree, thus more compilation units will use the new instructions that > are not necessarily ready for it (i.e. have extensive checking logic > upfront). It's not entirely surprising that the compiler then finds more > efficient ways to do operations using the new instructions, which will > then fail execution with invalid opcode. > > I'm with Andrey that the bug should be reopened and RC'ed because this > is effectively producing a miscompilation on i386. > > Kind regards > Philipp Kern > > [1] > https://sources.debian.org/src/putty/0.81-2/crypto/CMakeLists.txt/?hl=88#L130 > (it checks for the capability and then adds a specific library just for > that source file if successful) Hi, Reopening it and looking at it again is the way forward. I hope in conjunction with upstream where necessary this can resolved. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: i686 require SSE4.1-capable processor?
On Mon, 2024-07-15 at 17:20 +0200, Philipp Kern wrote: > [Also adding Phil] > > On 15.07.24 14:52, Andreas Ronnquist wrote: > > > Packages built for the i386 arch need to conform to the i386 baseline, > > > which is currently i686. If a package contains a newer instruction it's a > > > bug in that package and gcc is not the cause of it, the package is. > > > https://buildd.debian.org/status/fetch.php?pkg=filezilla=i386=3.63.0-1%2Bdeb12u3=1704758683=0 > > > indeed contains at least one compile command with -msse4.1. > [...] > > Yeah, I have discovered that it is indeed a cause of the d/rules in the > > filezilla package. I blame having taken over it recently, and still > > haven't learned the ins and outs of it. > > It'd also be good to document reasons for such workarounds next time. > Both the changelog and the surrounding comments don't really tell you > what to watch out for in a new gcc version. There's no bug reference > (GCC or Debian bug) or example error message or a pointer to possible > miscompilation. > > Kind regards > Philipp Kern > Hi all, The addition to 'debian/rules' was in response to the below. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053804 Debian may have moved on to where this temporary workaround is no longer needed. You may wish to contact the original reporter at some point. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Debian mentors - Packages looking for DD review and sponsorship - 2024 - 07 - 13
Evening all Debian Developers, Below is a curated list of packages in Debian Mentors[1] that are felt to be ready for review and possible sponsorship into Debian. rumur - https://mentors.debian.net/package/rumur/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071427 c-evo-dh - https://mentors.debian.net/package/c-evo-dh/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075861 wasix-libc - https://mentors.debian.net/package/wasix-libc/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058016 baby - https://mentors.debian.net/package/baby/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075734 libmobi - https://mentors.debian.net/package/libmobi/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073960 mangl - https://mentors.debian.net/package/mangl/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074777 colorize - https://mentors.debian.net/package/colorize/ RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073456 By sponsoring a package on this occasion is not a commitment to sponsoring the package in the long term if you cnnot commit to that. Supporting Debian mentors and giving of your time is appreciated. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: Ready stage for DD review/sponsoring - Too many DDs may spoil the broth. :-)
On Fri, 2024-07-12 at 10:44 +0500, Andrey Rakhmatullin wrote: > On Fri, Jul 12, 2024 at 05:54:59AM +0100, Phil Wyett wrote: > > Morning all, > > > > As we embark on a new process where packages submitted to mentors are > > reviewed > > and brought to a "Ready" stage for then busy DDs who are gracious enough to > > give > > their time to review and possibly sponsor into Debian. We have a unique > > problem > > (one which is now a nice one to have to be honest :-)) where more than one > > DD > > may input on the same package review. > > > > Could submitters to mentors and DDs please ensure that only one DD is > > working on > > a package. This is to avoid conflicting info and also not waste valuable DD > > time. If a package is taken, please find another to work on, as there are > > many > > at the "Ready" stage. > > Do you also suggest to not review packages one isn't going to sponsor? Or > how should this work? > Morning Andrey, Anyone can review packages, that has been part of mentors forever really. But whoever does review a package, I would hope they see it through its journey. * For non DDs. Hopefully take it to that ready stage where a DD can then take over and finish a packages journey. * For DDs. Hopefully take a package on prior to or at the ready stage and take it through its full journey. Is this reasonable? Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Ready stage for DD review/sponsoring - Too many DDs may spoil the broth. :-)
Morning all, As we embark on a new process where packages submitted to mentors are reviewed and brought to a "Ready" stage for then busy DDs who are gracious enough to give their time to review and possibly sponsor into Debian. We have a unique problem (one which is now a nice one to have to be honest :-)) where more than one DD may input on the same package review. Could submitters to mentors and DDs please ensure that only one DD is working on a package. This is to avoid conflicting info and also not waste valuable DD time. If a package is taken, please find another to work on, as there are many at the "Ready" stage. Many thanks for your cooperation. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Tue, 2024-07-09 at 14:23 +0200, Pierre-Elliott Bécue wrote: > Hello, > > Phil Wyett wrote on 09/07/2024 at 11:40:32+0200: > > > On Sun, 2024-07-07 at 13:20 +0200, Joerg Jaspert wrote: > > > On 17283 March 1977, Soren Stoutner wrote: > > > > > > > P.S. Based on Phil’s work on Mentors and my interactions with him, I > > > > have > > > > advocated for him to become a Debian Developer, uploading. I think > > > > his > > > > contributions to Debian will be even more impactful when he can > > > > sponsor the > > > > packages he feels are ready. > > > > > > It is only just July. He got rejected in May once - that's a bit too > > > soon yet. (The usual time for a retry is somewhere around 6 month, and > > > includes acknowleding (and working on) issues of the rejection). > > > > > > Note that it is not only technical knowledge that is required. That's > > > "just" part of it. > > > > > > > Morning Joerg, > > > > Thank you for your comments. Indeed, less than 24 hours later, I > > received an email stating my Debian Developer (DD), with upload > > application was to be closed and now has been. > > > > Regards > > FTAOD I closed this process without interacting DAM or Joerg and not > having read his mail. I will reopen it as I stated to you when the > proper time comes. > > I'm really happy that you're trying to work on making mentors.d.n more > proficient and active, and I'm also happy that you didn't get > demotivated by the different exchanges we collectively had in the past. > > As Joerg stated, we'll probably need to have a chat about the reasons > that led to the initial rejection and your thoughts on the whole > thing. That being said, I won't go into details publicly and I do hope > that you'll indeed come back to us in a few months so we can try going > forward. > > In the meantime, I'd like to express my gratitude for your commitment. > > Bests, Afternoon, There will be no seeking to reopen the application. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Sun, 2024-07-07 at 13:20 +0200, Joerg Jaspert wrote: > On 17283 March 1977, Soren Stoutner wrote: > > > P.S. Based on Phil’s work on Mentors and my interactions with him, I > > have > > advocated for him to become a Debian Developer, uploading. I think > > his > > contributions to Debian will be even more impactful when he can > > sponsor the > > packages he feels are ready. > > It is only just July. He got rejected in May once - that's a bit too > soon yet. (The usual time for a retry is somewhere around 6 month, and > includes acknowleding (and working on) issues of the rejection). > > Note that it is not only technical knowledge that is required. That's > "just" part of it. > Morning Joerg, Thank you for your comments. Indeed, less than 24 hours later, I received an email stating my Debian Developer (DD), with upload application was to be closed and now has been. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Mon, 2024-07-08 at 21:30 +0200, Baptiste Beauplat wrote: > Hi, > > On Sun, 2024-07-07 at 07:41 +0800, xiao sheng wen(肖盛文) wrote: > > Support this become a weekly thing or a monthly thing. > > > > Can mentors.debian.net sent package list to debian-devel automatically? > > It could. There is actually an issue for that[1], but no one has worked > on it yet. > > Note that, there is also an api on mentors[2], that an external > provider could use that to craft and send those weekly reports > automatically. > > Best, > > [1]: https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/42 > [2]: https://mentors.debian.net/api/ > Morning, The API currently does not seem to expose the data to extract to create such a report. When comment is done in the comment box for an upload, we have a dropdown with: * Not reviewed * Needs work * Ready The above data does not seem to be stored. The up-loader also has the ability to mark an their upload as ready. These would need to be addressed before any viable report could be thought about. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Sun, 2024-07-07 at 22:51 +0200, Andreas Tille wrote: > Hi Phil, > > Am Sun, Jul 07, 2024 at 08:48:22AM +0100 schrieb Phil Wyett: > > Thank you for the kind words. I agree whole heartedly with your comments > > that more people getting > > involved to make for a better Debian mentors would be good. Debian mentors > > is a great place to be > > around and we all learn something being involved. > > Thanks to you and all your work for mentors.d.n. Just to clarify my > mail about connecting to teams (which is done as I learned in response): > I did by no means intended to lower the importance of mentors.d.n in > general for Debian and newcomers. > > Thanks again > Andreas. > Hi Andreas, No need at all for your clarification. My words were generally meant to be an ideal for what I feel that mentors should be and what people can gain from it. Your comments regarding connecting teams are in my thoughts for how we can do better in this direction. I did reach out to the python team a little while ago to find sponsors for a few python packages that had been languishing on mentors. This turned into a discussion if the python team can approach sponsoring in a different way and the ruby team was put forward, who have a very good procedures for sponsoring. I am not yet ready to let these thoughts out as yet until they are fully formed and be best put forward to contributors to mentors etc. Regards Phil -- "I play the game for the game’s own sake" Arthur Conan Doyle - The Adventure of the Bruce-Partington Plans -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg -- signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Sun, 2024-07-07 at 11:32 +0200, Niels Thykier wrote: > Soren Stoutner: > > After reading a number of comments to the email below, I thought I would > > provide a bit of context for this email and Phil’s excellent work on > > Mentors. > > > > Recently Phil has taken it upon himself to triage every package that > > requests > > sponsorship on mentors.debian.net. Here is an example of the work he does: > > > > [...] > > Hi, > > I wholehearted agree that Phil is doing a lot of good work here and that > it is helpful to all parties involved in d-mentors. From my PoV, what > Phil does is so valuable that ideally we would provide it to all > sponsored maintainers with minimal latency. For me, that means > automating most of what Phil does. Ideally all, but I am not sure all > the things Phil does are trivial to automate where we are now. > Many thanks. > > But I have found Phil’s work to be very helpful, as I have limited time to > > handle sponsorships. When I look at a package Phil has endorsed, I can be > > sure that the simple and obvious things have already been taken care of. > > > > Thinking a bit more on this and its long term sustainability, I think we > have a spot here where we could automate the process a lot. If we look > at the list of things Phil does: > > 1. Build: > > Automate-able if we had good sandboxes/throw away build machines. > > 2. Lintian: > > I think mentors.d.o already does this. But it only works on the > artifacts uploaded and Phil probably enriches this. > > 3. Licenses: > > While ideally, we would want this to be automatic, I think we do not > have a good solution to this and I doubt we get it any time soon. > > Though an 80/20 might be in our grasp for someone interested and > I do not think it would need to depend on 1). > > 4. Build Twice (sudo pbuilder build --twice .dsc): > > Automate-able once 1) is solved. > > 5. Reproducible builds (reporotest): > > Trivially automate-able once 1) is solved. > > 6. Install/Upgrade: > > It sounds like something piuparts would check, so I assume this is > all solvable once 1) is complete. > > 7. Curating packages that pass these checks to various prospective > sponsors (such as the mail we are all replying to) > > These automations would not replace Phil since Phil in "failure" cases > provides suggestions on how to move forward. This part we would ideally > automate as well, but that is a much harder problem for most of these > checks. Still, having a "red/green" marker would enable newcomers to > figure out where they need more effort or assistance. > > The salsa-CI pipeline basically does most of these (3+7 being very clear > exceptions, do not remember if 4 is covered by salsa-ci, but adding it > would probably easy) and that infrastructure already has "no trust" code > execution flows. Another alternative might be leveraging debusine if > that can do the same and is intended for this purpose (did not check). > > In theory, we can reduce this to a already solved problem by linking the > RFS/mentors entry with the relevant CI pipeline report where possible > and a "Consider using the salsa-CI pipeline" check. Might need > tag2upload or dgit (assuming these support mentors.d.o), since that > would make the commit visible. Additional bells and whistles can be > added to the salsa-CI pipeline in the form of a small machine readable > report output that mentors.d.n could render if necessary (etc.) > > I do think it could be a major improvement our sponsorship work flow for > both sponsors and sponsored maintainers. > > 1) We promote a streamlined packaging workflow that a large portion of > Debian already follows and leverage existing infrastructure. Any > updates to our workflow would appear into the sponsor workflow > checklist workflow because they are the same underlying checks. > > 2) The workflow provides most of these checks with low latency > automation and would save the sponsored maintainers RFS + > mentors.d.o upload round trips. > > 3) The process would be a lot more sustainable, since most of it would > be automatic. > > Obviously, on paper is doable but it might require ironing out a lot of > bends or even not be possible at all. Sadly, I am not volunteering to do > it (got too much on my plate already). However, I am putting the idea > out there in case someone has time and interest in working on this area. > > I think the primary risk (problem to solve) is linking the mentors.d.o > upload to a git commit on salsa and the related pipeline data for that. > As said, I hope tag2upload/dgit could be part of the solution here (not > sure how those will cope with mentors.d.o versions being a lot more > mutable than regular uploads). For everything else, I think most of the > heavy lifting have already been done and "just" a matter of gluing it > all
Re: DD's, Debian Mentors needs you!
On Sat, 2024-07-06 at 23:45 -0700, Xiyue Deng wrote: > Soren Stoutner writes: > > > [[PGP Signed Part:Undecided]] > > After reading a number of comments to the email below, I thought I would > > provide a bit of context for this email and Phil’s excellent work on > > Mentors. > > > > Recently Phil has taken it upon himself to triage every package that > > requests > > sponsorship on mentors.debian.net. Here is an example of the work he does: > > > > https://lists.debian.org/debian-mentors/2024/07/msg00032.html > > > > When he feels a package is ready for sponsorship, he indicates that with an > > email to the list. > > > > https://lists.debian.org/debian-mentors/2024/07/msg00024.html > > > > In some cases, nobody picks these up. The email below was sent to debian- > > devel with a curated list of packages that Phil has already reviewed and > > feels > > are ready for a DD to sponsor. > > > > At any point, anyone can look at all of the packages on Mentors requesting > > a > > sponsor. > > > > https://mentors.debian.net/ > > > > But I have found Phil’s work to be very helpful, as I have limited time to > > handle sponsorships. When I look at a package Phil has endorsed, I can be > > sure that the simple and obvious things have already been taken care of. > > > > I would heartily hope that Phil continues to send periodic emails to debian- > > devel with lists of packages that he considers ready, but that are > > languishing > > on the vine because nobody has noticed them. I would also encourage anyone > > else to get involved in this process if they feel so inclined. I think > > that > > one of the most important aspects of attracting people to Debian is to make > > it > > easy for someone who is not yet a DD or DM to submit packages and have them > > be > > reviewed promptly. There is probably nothing as demotivating to a > > first-time > > contributor as putting a lot of effort into a package, having it be in good > > shape, and then never having it be sponsored simply because it didn’t get > > noticed. > > > > Soren > > > > P.S. Based on Phil’s work on Mentors and my interactions with him, I have > > advocated for him to become a Debian Developer, uploading. I think his > > contributions to Debian will be even more impactful when he can sponsor the > > packages he feels are ready. > > > > https://nm.debian.org/process/1305/ > > > > On Saturday, July 6, 2024 6:45:33 AM MST Phil Wyett wrote: > > > Hi all DD's > > > > > > Debian Mentors[1] always struggles to find available Debian Developers for > > > final reviewing and sponsoring of packages submitted too our part of the > > > project. > > > > > > We believe some packages are ready or very close to the quality for > > > sponsorship and we would request any DD who has the time and is willing, > > > to > > > have a look at one or more of the packages below and possibly sponsor them > > > into Debian. > > > > > > Mentors page: > > > https://mentors.debian.net/package/hexwalk/ > > > Request For Sponsorship (RFS): > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065008 > > > > > > Mentors page: > > > https://mentors.debian.net/package/uriparser/ > > > Request For Sponsorship (RFS): > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074542 > > > > > > Mentors page: > > > https://mentors.debian.net/package/mailgraph/ > > > Request For Sponsorship (RFS): > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074552 > > > > > > Mentors page: > > > https://mentors.debian.net/package/dmidecode/ > > > Request For Sponsorship (RFS): > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074553 > > > > > > Mentor page: > > > https://mentors.debian.net/package/selint/ > > > Request For Sponsorship (RFS): > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074592 > > > > > > Your assistance will be extremely appreciated and if announcing a few at a > > > time on the 'devel' list works, this could become a weekly thing. > > > > > > [1] https://mentors.debian.net > > > > > > Regards > > > > > > Phil > > As one of those who received help from Phil who kindly helped review my > packages and finding potential sponsors, I want to tak
Re: DD's, Debian Mentors needs you!
Morning Soren, Many thanks for the kinds words and the encouragement. As you stated wonderfully and I will additionally offer a little of my mentors motivations. Debian mentors can be the first experience of contribution to not just Debian, but Free and Open Source Software projects in general. Though technical, having mentors be welcoming and friendly (we all started knowing nothing) environment with consistency of "here are the tests/standards required by all" I hope with the help of others, make mentors a successful part of the Debian project that attracts and retains contributors. I must thank Gianfranco Costamagna who initially showed me the value of Debian mentors and encouraged me to get involved. Regards Phil On Sat, 2024-07-06 at 23:18 -0700, Soren Stoutner wrote: > After reading a number of comments to the email below, I thought I would > provide a bit of context for this email and Phil’s excellent work on Mentors. > > Recently Phil has taken it upon himself to triage every package that requests > sponsorship on mentors.debian.net. Here is an example of the work he does: > > https://lists.debian.org/debian-mentors/2024/07/msg00032.html > > When he feels a package is ready for sponsorship, he indicates that with an > email to the list. > > https://lists.debian.org/debian-mentors/2024/07/msg00024.html > > In some cases, nobody picks these up. The email below was sent to debian- > devel with a curated list of packages that Phil has already reviewed and > feels > are ready for a DD to sponsor. > > At any point, anyone can look at all of the packages on Mentors requesting a > sponsor. > > https://mentors.debian.net/ > > But I have found Phil’s work to be very helpful, as I have limited time to > handle sponsorships. When I look at a package Phil has endorsed, I can be > sure that the simple and obvious things have already been taken care of. > > I would heartily hope that Phil continues to send periodic emails to debian- > devel with lists of packages that he considers ready, but that are > languishing > on the vine because nobody has noticed them. I would also encourage anyone > else to get involved in this process if they feel so inclined. I think that > one of the most important aspects of attracting people to Debian is to make > it > easy for someone who is not yet a DD or DM to submit packages and have them > be > reviewed promptly. There is probably nothing as demotivating to a first-time > contributor as putting a lot of effort into a package, having it be in good > shape, and then never having it be sponsored simply because it didn’t get > noticed. > > Soren > > P.S. Based on Phil’s work on Mentors and my interactions with him, I have > advocated for him to become a Debian Developer, uploading. I think his > contributions to Debian will be even more impactful when he can sponsor the > packages he feels are ready. > > https://nm.debian.org/process/1305/ > > On Saturday, July 6, 2024 6:45:33 AM MST Phil Wyett wrote: > > Hi all DD's > > > > Debian Mentors[1] always struggles to find available Debian Developers for > > final reviewing and sponsoring of packages submitted too our part of the > > project. > > > > We believe some packages are ready or very close to the quality for > > sponsorship and we would request any DD who has the time and is willing, to > > have a look at one or more of the packages below and possibly sponsor them > > into Debian. > > > > Mentors page: > > https://mentors.debian.net/package/hexwalk/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065008 > > > > Mentors page: > > https://mentors.debian.net/package/uriparser/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074542 > > > > Mentors page: > > https://mentors.debian.net/package/mailgraph/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074552 > > > > Mentors page: > > https://mentors.debian.net/package/dmidecode/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074553 > > > > Mentor page: > > https://mentors.debian.net/package/selint/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074592 > > > > Your assistance will be extremely appreciated and if announcing a few at a > > time on the 'devel' list works, this could become a weekly thing. > > > > [1] https://mentors.debian.net > > > > Regards > > > > Phil > > -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Sun, 2024-07-07 at 11:29 +0500, Andrey Rakhmatullin wrote: > On Sun, Jul 07, 2024 at 07:54:25AM +0200, Andreas Tille wrote: > > Hi Phil, > > > > thanks for advertising Debian Mentors. > > > > Am Sat, Jul 06, 2024 at 02:45:33PM +0100 schrieb Phil Wyett: > > > Hi all DD's > > > > > > Debian Mentors[1] always struggles to find available Debian Developers > > > for final reviewing and > > > sponsoring of packages submitted too our part of the project. > > > > One thing I'm missing on mentors.d.n is that I it does not advertise > > existing teams. It happened from time to time that there was some > > sponsoring request of Debian Science, Debian Med or Debian Python Team > > related packages (surely others I did not notices). Asking on the > > relevant lists very easily helps getting the package in question > > sponsored. I have a personal sponsoring policy that I only sponsor from > > a Git repository in a team I'm working in. This has the advantage I can > > easily help by pushing some commit with extensive comment to teach the > > sponsee in some direct way. Making a sponsee aware how to work together > > with a team inside Debian is IMHO very important. > > > > Thus I would welcome if there could be some explicit hint to mentees > > to relevant teams. > > Note that "Offer your package directly to relevant teams and individual > developers." is sugested on https://mentors.debian.net/intro-maintainers/ > and https://mentors.debian.net/sponsors/ > Andreas, Andrey and All, Andrey has kindly offered links for relevant information here. Any additions or changes etc. of course would be subject to discussion and consensus on the mentors mailing list. Regards Phil -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Sun, 2024-07-07 at 07:41 +0800, xiao sheng wen(肖盛文) wrote: > Hi, > > Support this become a weekly thing or a monthly thing. > > Can mentors.debian.net sent package list to debian-devel automatically? > > Regards, > xiao sheng wen > 在 2024/7/6 21:45, Phil Wyett 写道: > > Hi all DD's > > > > Debian Mentors[1] always struggles to find available Debian Developers for > > final reviewing and > > sponsoring of packages submitted too our part of the project. > > > > We believe some packages are ready or very close to the quality for > > sponsorship and we would request > > any DD who has the time and is willing, to have a look at one or more of > > the packages below and > > possibly sponsor them into Debian. > > > > Mentors page: > > https://mentors.debian.net/package/hexwalk/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065008 > > > > Mentors page: > > https://mentors.debian.net/package/uriparser/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074542 > > > > Mentors page: > > https://mentors.debian.net/package/mailgraph/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074552 > > > > Mentors page: > > https://mentors.debian.net/package/dmidecode/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074553 > > > > Mentor page: > > https://mentors.debian.net/package/selint/ > > Request For Sponsorship (RFS): > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074592 > > > > Your assistance will be extremely appreciated and if announcing a few at a > > time on the 'devel' list > > works, this could become a weekly thing. > > > > [1] https://mentors.debian.net > > > > Regards > > > > Phil > > > > -- > 肖盛文 xiao sheng wen > https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 > 操作系统 > Debian QA page: > https://qa.debian.org/developer.php?login=atzlinux%40sina.com > Debian salsa: https://salsa.debian.org/atzlinux-guest > GnuPG Public Key: 0x00186602339240CB Hi Xiao and all, I am not sure if this could be done automatically. Mentors uses the expo platform and that will take some research and discussion to see what maybe could be done. We could create a wiki page with ready packages for DD attention that could be forwarded in a mail to this list at a set interval. Maybe more experienced DDs/Contributors to Mentors such as Andrey Rakhmatullin may have more insight than I here. Regards Phil -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg signature.asc Description: This is a digitally signed message part
Re: DD's, Debian Mentors needs you!
On Sat, 2024-07-06 at 17:42 -0700, Otto Kekäläinen wrote: > Hi! > > > https://mentors.debian.net/package/uriparser/ > > https://mentors.debian.net/package/mailgraph/ > > This is the same maintainer, I can take this on. > > > https://mentors.debian.net/package/selint/ > > I have worked with this maintainer before, I can help him now too. > > > After this Hexwalk still needs a mentor. Hi Otto, Many thanks for giving your time. selint has been picked up by Pierre Gruet via the Request For Sponsorship (RFS) bug[1], so I think that one is OK. The other two are happily yours. :-) [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074592 Regards Phil -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg signature.asc Description: This is a digitally signed message part
DD's, Debian Mentors needs you!
Hi all DD's Debian Mentors[1] always struggles to find available Debian Developers for final reviewing and sponsoring of packages submitted too our part of the project. We believe some packages are ready or very close to the quality for sponsorship and we would request any DD who has the time and is willing, to have a look at one or more of the packages below and possibly sponsor them into Debian. Mentors page: https://mentors.debian.net/package/hexwalk/ Request For Sponsorship (RFS): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065008 Mentors page: https://mentors.debian.net/package/uriparser/ Request For Sponsorship (RFS): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074542 Mentors page: https://mentors.debian.net/package/mailgraph/ Request For Sponsorship (RFS): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074552 Mentors page: https://mentors.debian.net/package/dmidecode/ Request For Sponsorship (RFS): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074553 Mentor page: https://mentors.debian.net/package/selint/ Request For Sponsorship (RFS): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074592 Your assistance will be extremely appreciated and if announcing a few at a time on the 'devel' list works, this could become a weekly thing. [1] https://mentors.debian.net Regards Phil -- Internet Relay Chat (IRC): kathenas Website: https://kathenas.org Instagram: https://instagram.com/kathenasorg/ Buy Me A Coffee: https://buymeacoffee.com/kathenasorg signature.asc Description: This is a digitally signed message part
Re: New requirements for APT repository signing
On Wed, 2024-02-28 at 20:20 +0100, Julian Andres Klode wrote: > APT 2.7.13 just landed in unstable and with GnuPG 2.4.5 installed, > or 2.4.4 with a backport from the 2.4 branch, requires repositories > to be signed using one of > > - RSA keys of at least 2048 bit > - Ed25519 > - Ed448 > > Any other keys will cause warnings. These warnings will become > errors in March as we harden it up for the Ubuntu 24.04 release, > which was the main driver to do the change *now*. > > If you operate third-party repositories using different key > algorithms, now is your time to migrate before you get hit > with an error. > > For the Ubuntu perspective, feel free to check out the discourse > post: > > https://discourse.ubuntu.com/t/new-requirements-for-apt-repository-signing-in-24-04/42854 Hi, Could I be pointed to the public conversation, any plans or bug reports related to this update and transition etc. for affected users? Thanks. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Bug#1061649: ITP: vdr-plugin-wirbelscan -- This plugin performs channel scans for digital tv cards
Package: wnpp Severity: wishlist Owner: Phil Wyett X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: vdr-plugin-wirbelscan Version : 2023.10.15 Upstream Author : Winfried Koehler * URL : https://github.com/wirbel-at-vdr-portal/wirbelscan-dev * License : GPL-2 Programming Lang: C++ Description : This plugin performs channel scans for digital tv cards. Notes: * Goal is to take over from embedded wirbelscan code currently in some Debian packages. * Description will need some tuning. * Package will need a sponsor if my DD/with upload process is not completed. Regards Phil -- Playing the game for the games sake. Web: * Debian Wiki: https://wiki.debian.org/PhilWyett * Website: https://kathenas.org * Social Debian: https://pleroma.debian.social/kathenas/ * Social Instagram: https://www.instagram.com/kathenasorg/ signature.asc Description: This is a digitally signed message part
Re: RFS: gnome-maps/3.30.3.1-0+deb10u1 [NMU] -- map application for GNOME
On Sun, 2020-09-13 at 15:24 +0100, Simon McVittie wrote: > On Sun, 13 Sep 2020 at 10:35:48 +0100, Simon McVittie wrote: > > On Sun, 13 Sep 2020 at 04:02:56 +0100, Phil Wyett wrote: > > > Can we have this uploaded for the upcoming 10.6? Still seen no > > > love and > > > missed so many point releases now. Just need someone with > > > permissions to > > > do it and a little time. > > > > I'll put this on my queue to review and test. > > Uploaded. In future, if you have changes for a package in stable, > please try to work with the package's maintainers first, rather than > bypassing them. > > I know the GNOME team has taken too long to respond, and I'm sorry > about > that. We are responsible for a lot of packages, of which gnome-maps is > far from our highest priority. > > smcv Hi Simon, Thank you for the response, review and upload. I will try to be more in touch with the GNOME team with future work. I hope via discussion, git and MR. To go back to time and hardware. The DPL did mention spending as part of his DebConf20 talk. Maybe an application can be made for hardware for members of the GNOME team, so they might have a stable instance on hand for its related needs. GNOME is a very important part of Debian and supporting those working on it would be a good thing. Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Re: RFS: gnome-maps/3.30.3.1-0+deb10u1 [NMU] -- map application for GNOME
On Sun, 2020-07-26 at 04:55 +0100, Phil Wyett wrote: > On Tue, 28 Apr 2020 03:54:59 +0100 Phil Wyett < > philip.wy...@kathenas.org > > wrote: > > Package: sponsorship-requests > > Severity: normal > > > > Dear mentors, > > > > I am looking for a sponsor for my package "gnome-maps" > > > > * Package name: gnome-maps > >Version : 3.30.3.1-0+deb10u1 > >Upstream Author : maps-l...@gnome.org > > * URL : https://wiki.gnome.org/Apps/Maps > > * License : GPL-2+ > > * Vcs : https://salsa.debian.org/gnome-team/gnome-maps > >Section : gnome > > > > It builds those binary packages: > > > > gnome-maps - map application for GNOME > > > > To access further information about this package, please visit the > > following URL: > > > > https://mentors.debian.net/package/gnome-maps > > > > Alternatively, one can download the package with dget using this > > command: > > > > dget -x > > > https://mentors.debian.net/debian/pool/main/g/gnome-maps/gnome-maps_3.30.3.1-0+deb10u1.dsc > > Changes since the last upload: > > > >* Non-maintainer upload > >* New upstream release > > - Make the shape layer renderer use the tile size specified in > the > > dynamic > >service file, fixing an issue with misaligned shape layer > > (GeoJSON, GPX, > >KML) rendering with the new 512 pixel tile > > - Update Icelandic translation > > > > === > > > > Note: Package requires sponsor for stable updates upload. > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947464 > > > > Regards > > > > Phil > > > > Hi all, > > Bump. Anyone fancy sponsoring with a stable release imminent? > > This RFS has been additionally mailed to the gtk-gnome list and the > gnome maintainers with zero replies/interaction to date. > > Regards > > Phil > Hi all, Ping. Can we have this uploaded for the upcoming 10.6? Still seen no love and missed so many point releases now. Just need someone with permissions to do it and a little time. Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Bug#970204: ITP: rednotebook -- Modern desktop diary and personal journaling tool.
Package: wnpp Severity: wishlist Owner: Phil Wyett X-Debbugs-CC: debian-devel@lists.debian.org * Package name: rednotebook Version : 2.20+ds-1 Upstream Author : Jendrik Seipp * URL : https://github.com/jendrikseipp/rednotebook * License : GPL-2+ Programming Lang: Python Description : Modern desktop diary and personal journaling tool. It lets you format, tag and search your entries. You can also add pictures, links and customisable templates, spell check your notes, and export to plain text, HTML, LaTeX or PDF. Additional notes: A return of the package to debian. I shall maintain this package. Package will need salsa repo and appropriate permissions creating. RFS to follow. Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Bug#970200: ITP: rednotebook -- Modern desktop diary and personal journaling tool.
Package: wnpp Severity: wishlist Owner: Phil Wyett X-Debbugs-CC: debian-devel@lists.debian.org * Package name: rednotebook Version : 2.20+ds-1 Upstream Author : Jendrik Seipp * URL : https://github.com/jendrikseipp/rednotebook * License : GPL-2+ Programming Lang: Python Description : Modern desktop diary and personal journaling tool. It lets you format, tag and search your entries. You can also add pictures, links and customisable templates, spell check your notes, and export to plain text, HTML, LaTeX or PDF. Additional notes: A return of the package to debian. I shall maintain this package. Package will need salsa repo and appropriate permissions creating. RFS to follow. Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Re: New lintian warning: mailing-list-obsolete-in-debian-infrastructure Debian Med Packaging Team
On Fri, 2020-04-24 at 09:56 +0200, Andreas Tille wrote: > Hi, > > today I've seen the first time this new lintian warning: > >mailing-list-obsolete-in-debian-infrastructure Debian Med Packaging > Team > > I wonder whether we could this set from severity Warning to Pedandic. > The point is that this address works not only as maintainer but rather > as key in several infrastrutural use case like database queries etc. > > The only reason that would convince me that a change is needed would > be > that the redirect to alioth-lists.debian.net would not work any more > at > some foreseable point of time. So please note: I would not mind > about > automatically replacing that address with something non-obsolete since > we try to do some turnover of all (about 1000) Debian Med packages per > release. But once we start this change several tools will stop > working > reliably. This is to much effort for something that looks cosmetical > in > my eyes. So if you insist that this should be at severity warning > I'll > probably rather add a lintian override automatically for all our > packages rather than automatically change the maintainer address. > > Kind regards > >Andreas. > Hi, See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958182 Regards Phil -- *** Playing the game for the games sake. *** WWW: https://kathenas.org Twitter: @kathenasorg IRC: kathenas GPG: 724AA9B52F024C8B signature.asc Description: This is a digitally signed message part
Accepted filezilla 3.46.3-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 20:51:45 + Source: filezilla Binary: filezilla filezilla-common Architecture: source Version: 3.46.3-1 Distribution: unstable Urgency: medium Maintainer: Adrien Cunin Changed-By: Phil Wyett Description: filezilla - Full-featured graphical FTP/FTPS/SFTP client filezilla-common - Architecture independent files for filezilla Changes: filezilla (3.46.3-1) unstable; urgency=medium . [ Gianfranco Costamagna ] * Import the new release on git * Updated libfilezilla-dev versioned build-dep to 0.19.3 . [ Phil Wyett ] * Team Upload * New upstream version 3.46.3 Checksums-Sha1: 90eda07c304d61f1e30e9003b039ce5390e5cca5 2144 filezilla_3.46.3-1.dsc 2b5b51e665b72b2d6e991c55b43339996baf8f9c 4720329 filezilla_3.46.3.orig.tar.bz2 ef56da10914abc531ea147b44574ae1cf94b26d9 9736 filezilla_3.46.3-1.debian.tar.xz 9d517b0f530beffca42f16f248fd294d27d1b093 17055 filezilla_3.46.3-1_source.buildinfo Checksums-Sha256: 19c4e0a4054689b0622f6733ad37ab72132917eec5038c733e727f9fee9640c7 2144 filezilla_3.46.3-1.dsc f1c5bff0a99c39447a5ea9fdfcc16cc408876ef52fa8d5e7bf041ea0717a7395 4720329 filezilla_3.46.3.orig.tar.bz2 4d06a1e590d35c4cb94dd4391a139177c6619a1626c35c4699b3509309c4c280 9736 filezilla_3.46.3-1.debian.tar.xz 8b1aa15e8c08b3b56107c3db0875ced9072e19d9d09345054884ca9265c96d84 17055 filezilla_3.46.3-1_source.buildinfo Files: e2e604d7dc981829b365965298ff4ef8 2144 net optional filezilla_3.46.3-1.dsc a4bbd17add490c7b965b643cee25171c 4720329 net optional filezilla_3.46.3.orig.tar.bz2 d0830ff21cd322b3ee1c877582349049 9736 net optional filezilla_3.46.3-1.debian.tar.xz 5c177844ddbe48982089727a5aad3017 17055 net optional filezilla_3.46.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl4XP9gACgkQ808JdE6f XdkR9w/+P5oC6Qp5gIIl/DLtCGnzq8OPlyrQZzKWf9xQ8uksAXZQ/uxJUAcwg189 V13NFkvKxOAZWX+mo5kRy23SCh3QBWvU7+4NUh8fcaqPHgKZfHnv7FIsKBgjo2f7 CG1XneVtis1JeI2F//hgXDiiP2eLEK14n+HO/a/9OcdYAwh8kcmOtnDQ9WurvVLo bEAvPdhAMAqWxD1Xm4h5rZU6t3bwwSmP3r/mQgFT4QTvgWLseTzstjPpM4dc8RsL wXKWqIvTllT1HIy9ZV1EoOIthttiDRRmNkhgyZCvGWi+RYGHmk8exiKyGNBVaulH YtPjqcmRe9L1UQzzunk8O+kKsYEoZu9gcKBbJHpyrRzV0zF2y99y1DuuDB/2cVe5 vTp0+y40E0p6zaSsz+vVtOOAfaFnbUrck2J/4URwLrck7HUb8HFx5m2Q3H7Yicl1 PZjeGk9if3/4O2vhd/QrxPv+WMDY1sOdZfVIpQbRWn7FKNfijExdotCUqnS4R6bj t9+A1Yl0GqtGWQ7u3sUMNLuvU7a/yRnDKC9IKvJYQBarVRQ6vtATWfcekuepoek8 rwdL8i5d51eMP8FAdOfDiVzAp+kgEKSauLHVzQtJi+mR4wordoNxzvKv0qL4Gqpl L0gAqdz+12wdvp0ULNbeXsp/chJ6/iXUdmJbFHRJArMBQKPuIRM= =9OR6 -END PGP SIGNATURE-
Accepted libfilezilla 0.19.3-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 20:28:17 + Source: libfilezilla Binary: libfilezilla-dev libfilezilla0 Architecture: source Version: 0.19.3-1 Distribution: unstable Urgency: medium Maintainer: Adrien Cunin Changed-By: Phil Wyett Description: libfilezilla-dev - build high-performing platform-independent programs (development) libfilezilla0 - build high-performing platform-independent programs (runtime lib) Changes: libfilezilla (0.19.3-1) unstable; urgency=medium . [ Gianfranco Costamagna ] * Import the new release on git . [ Phil Wyett ] * Team upload * New upstream version 0.19.3 Checksums-Sha1: 033cebb327901c632a604f4f09065d04752c4f7c 2022 libfilezilla_0.19.3-1.dsc d62648c57a3b1c57683bc6647332920c90baecb9 541117 libfilezilla_0.19.3.orig.tar.bz2 0e02158fd6ff51f198b03d26cde99b46607e9b57 2888 libfilezilla_0.19.3-1.debian.tar.xz abf1b5c6ea623edfaecbc8f61a4e926dfddbc0e2 7747 libfilezilla_0.19.3-1_source.buildinfo Checksums-Sha256: c4549ad73610fa808e40bb76ca952882b92cd5db3369ddefd59906f2177d8fe7 2022 libfilezilla_0.19.3-1.dsc a43d49f86d5550e9a81aee2394bac066333d5bb47943e92c629cb9d52037b43a 541117 libfilezilla_0.19.3.orig.tar.bz2 1e7ec16d44bedf36069bb523e90612b06d62af6392aa81cd27662dd37e26d841 2888 libfilezilla_0.19.3-1.debian.tar.xz 426b90fe53407561215b86bf91905dd9d11dcf47a1585b501918cc2d12f5e817 7747 libfilezilla_0.19.3-1_source.buildinfo Files: d0fd59cb32949d94a988fee12afe4c9d 2022 libs optional libfilezilla_0.19.3-1.dsc c72f6ba6a834c81f659e0172483aa747 541117 libs optional libfilezilla_0.19.3.orig.tar.bz2 6bc165997303a387b1d45a049d8ec9e4 2888 libs optional libfilezilla_0.19.3-1.debian.tar.xz 7f117525dbfccd74931c46c19d8488c4 7747 libs optional libfilezilla_0.19.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl4XO7oACgkQ808JdE6f XdnqJw/8Cc6CR4r3gbTqzEB+aGomU4EewVgnxR04Wuct6epMB5qr4yeknDJBNK1Q 16fKqA7/mlxcaMi3lEGP3x/dWwSrd8mlKRdfPKY0di6cT16XAPia30HMR6s9rMUx UtfiVFJzhLYnmAnVrU1+Fjojj+ahyg+rknkOxGJjLEnPfTAznRlj374lcaxtXUzS 6V6S5PriMCDdcF2JFoaFn3b08A8LxQ4Jj5U01as5+bX1hgRPFX0lX8lIO0vRzUhy QPtJsmJ1MAkzwGL3f6Nk8JmfsFGBih/VZLV5HV9i00muMiVTVEtVj8sunTlz48/i 4Ev9nyqRMPLWBBcaumD0a/B0tguUwLRgELJn5m+zMcEi3A04ddZFyFFOJesroQWt m76Gl6ebF5I32m7FOCf/IcUjSXhEU8Ox+rPBcpznHvuUFX+Sl11xWk/bS4OkAHf9 /qKSK8TCFbQx6IIlS5NNcT3j2B5DSHqOk6i6DAq9MQFHSww30Kzk/MUlhIrRpUie hr4fyW+WU5jXsTNyYtwenN5xA9XRqMCOyic96FfOS5YN2vscUEkEIScQc3DuzQmx zMYB2KRYrQuDS+3sAKAiiV3tvxyn7SgOSbZmGF+fsOZIM7GNUiC4/si4lvXR+sBN 6gPBCk8lzo+12mAkhZBnn4mb2EMVk/LWOEJYqDCZKU7sUzrO9mI= =GeJ0 -END PGP SIGNATURE-
Accepted pingus 0.7.6-5 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 29 Dec 2019 09:24:25 + Source: pingus Architecture: source Version: 0.7.6-5 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Phil Wyett Closes: 947574 Changes: pingus (0.7.6-5) unstable; urgency=medium . * Team upload. * Added: scons-use-python3-print.patch. (Closes: #947574). * d/control: Update 'Vcs-Browser' and 'Vcs-Git'. * d/control: Update 'Standards-Version'. Checksums-Sha1: bd7f6e1e52884f04d1769328c5daa8836c0f8710 2069 pingus_0.7.6-5.dsc 19bbacb65d5fbb6b2fe929c3baa984c4741378ea 30328 pingus_0.7.6-5.debian.tar.xz 3f7f9270fac0e58d60c7c982912ea86e33ac8774 10283 pingus_0.7.6-5_source.buildinfo Checksums-Sha256: 31a2ec9c67775c4a895779c1ada9306cc059d3ced318361f66e4ea09e29a79d1 2069 pingus_0.7.6-5.dsc 044d5ca233bb071d1ce41c4319917d69f88b61a533654b47e92aacf1961d30e9 30328 pingus_0.7.6-5.debian.tar.xz 9298d4b1011b9d67b90eb1b40338f37f3007d9ba8cf5d95780480f05363f8f8d 10283 pingus_0.7.6-5_source.buildinfo Files: 6b1995995862360c30213df7c3913dd1 2069 games optional pingus_0.7.6-5.dsc bceb1c9428d9609fb907adea6b3259a5 30328 games optional pingus_0.7.6-5.debian.tar.xz cf1a5ef9beceec61fccc51a7ea43def5 10283 games optional pingus_0.7.6-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAl4N4goACgkQkWT6HRe9 XTb5LxAAkYE8YgwiUTZI1R+NJeHffY5Nh0aeJZxnw3phPHHFTHDaeDGnOaVPk9BP XS0t9LMDty76CZDg5Xf3iILwiwZxE7KSl6T9W55AuP7RMaBfH4yQ4AAtUXfoybf1 8gg0CoCb0KHFy5Qm5I59FPRnSuIn6Kc0rftbvtIrCEtgUIoiT6BRcqUel9CiLVkl VpPzNzoDU7UgqN1RSeeop//GfDjHaWg4ECY3AwVVVvmgoikhJhJ+l3TDR42+PTyp 6d8JlqvSELAHrWnT0ZX5btLuzClXIVT57I6NpwP6r7u0UxcZRirshSmIaLoUNltC cmi63E0/FwbE/cBNTeuYD1IUg51jiv9CzizEYYgh3Uou/dRvg7HzYQRO0zvzayA8 3fVOwCfPoVZ3qgjWbWhXoKTrJERYVUabTte19ySwVCLA84YREt8hJ18ZB0RxlPhA YytH3aGefvbY/S3jPVVl7yw5nP1Y5TQYdwL41JvQ3fi1xIwq3icwte4GMSNSTHVa 9g2iMoUJicApOq+bX4xDO5jOcPUwD1RNIlNtyzw5Yq47NohvXzdcEa1ZkquH9i3L KUA7UvRhkdbXeb0TYvJj8Pwv0NyVdQjR77+/ETeXefbw8LxO9q7vRWjYS3CWdQE+ RzK7QsfcieFz9UMXloyAGE9gPH/UtqjctCDGTfEm5poR/UgDjOs= =Y/7i -END PGP SIGNATURE-
Re: Proposed change of offensive packages to -offensive
On Wed, 2017-11-22 at 21:29 +0800, Paul Wise wrote: > On Wed, Nov 22, 2017 at 8:42 PM, Phil Wyett wrote: > > > In my honest opinion, rating certain content types within a package should > > be > > done along the lines of PEGI[1]. A self regulatory rating done as part of a > > social policy and administered by the particular packages maintainer. All > > subsequent questioning of rating would be done via bug reports against the > > particular package. > > Some rating related resources are at: > > https://wiki.debian.org/OpenRating > > > * Rating set within debian folder - maybe rating file. > > Personally I think a debtags/screenshots style service would be better here. > > > * Seen on packages.d.o, PTS and query by apt etc. for package. > > * Should not be auto installed as a recommends etc. > > Preferably configurable, perhaps by installing packages with standard names. > Hi, Thanks for the link Paul. The Open Rating debtags idea I find far more appealing than package naming with the offensive or other suffix. Regards Phil -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. Web: https://kathenas.org GitLab: https://gitlab.com/kathenas Twitter: kathenasorg Instagram: kathenasorg GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A signature.asc Description: This is a digitally signed message part
Re: Proposed change of offensive packages to -offensive
On Wed, 2017-11-22 at 08:49 +, Jonathan Dowland wrote: > On Wed, Nov 22, 2017 at 01:38:43AM +, Holger Levsen wrote: > > no, please, no. > > > > policy should document technical terms. > > > > whatever else we might come up to deal with the "real world" (that is > > more complicated than that, eg think tibet, taiwan and china, or $foo) > > should not be included in -policy. > > This is about standardising the label we use for marking offensive > content, not about defining what is or isn't offensive. I'd argue that > "-offensive" suffix proposal was a technical term. > Hi, My two pence worth... In my honest opinion, rating certain content types within a package should be done along the lines of PEGI[1]. A self regulatory rating done as part of a social policy and administered by the particular packages maintainer. All subsequent questioning of rating would be done via bug reports against the particular package. Not an exhaustive list... * Rating set within debian folder - maybe rating file. * Seen on packages.d.o, PTS and query by apt etc. for package. * Should not be auto installed as a recommends etc. [1] http://www.pegi.info Regards Phil -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. Web: https://kathenas.org GitLab: https://gitlab.com/kathenas Twitter: kathenasorg Instagram: kathenasorg GPG: 1B97 6556 913F 73F3 9C9B 25C4 2961 D9B6 2017 A57A signature.asc Description: This is a digitally signed message part
suil - current packaging query
Hi all, I looked at installing audacity on stretch and found it wanted to install QT deps as well as GTK deps. Not experiencing this in the past, I said 'n' to apt and had a delve into why this was happening. I found audacity now uses suil. Package page: https://packages.debian.org/stretch/libsuil-0-0 As you can see by the deps on the page above - GTK and QT. I looked upstream and found their packaging doc. http://git.drobilla.net/cgit.cgi/suil.git/tree/PACKAGING The bottom section of the doc: *** IMPORTANT GUIDELINES FOR PACKAGING SUIL *** The purpose of Suil is to abstract plugin UI toolkits away from host code. To achieve this, Suil performs its magic by dynamically loading modules for each toolkit. The main Suil library does NOT depend on any toolkit libraries, and thus neither should your package. Please package the individual modules (e.g. libsuil_gtk2_in_qt4.so) as separate packages, which themselves depend on the involved toolkits. These packages should also be versioned as described above to support parallel installation. Please do not make the main Suil package depend on any toolkit package, this defeats the purpose of Suil and will severely irritate those who for whatever reason do not want a particular toolkit dependency. The main Suil package may have a weak dependency (e.g. "recommends") on the individual wrapper modules, and it's fine if these are installed by default, but it must be possible to install Suil without installing them if the user explicitly wishes to do so. // End Is it just me or should this package be broken down into a core and subset module packages? Any thoughts and how suil should be better packaged welcome. Bug report? Regards Phil -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. Web: https://kathenas.org Github: https://github.com/kathenas Twitter: kathenasorg Instagram: kathenasorg signature.asc Description: This is a digitally signed message part
Bug#875264: ITP: rednotebook -- -- A cross-platform journal
Package: wnpp Severity: wishlist Owner: Phil Wyett <philwy...@kathenas.org> X-Debbugs-CC: debian-devel@lists.debian.org * Package name: rednotebook Version : 2.2 Upstream Author : Jendrik Seipp <jendrikse...@web.de> * URL : https://github.com/jendrikseipp/rednotebook * License : GPL-2+ Programming Lang: Python Description: A modern desktop journal. It lets you format, tag and search your entries. You can also add pictures, links and customizable templates, spell check your notes, and export to plain text, HTML, Latex or PDF. Notes: This package was removed from debian due to webkit issues. The package, major version 2, will be introduced as a new package. I will also be taking maintainer responsibility of the package. Regards Phil -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. Web: https://kathenas.org Github: https://github.com/kathenas Twitter: kathenasorg Instagram: kathenasorg signature.asc Description: This is a digitally signed message part
Accepted live-wrapper 0.6+nmu2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 14 Jul 2017 04:43:06 +0100 Source: live-wrapper Binary: live-wrapper live-wrapper-doc Architecture: source all Version: 0.6+nmu2 Distribution: unstable Urgency: medium Maintainer: Debian Live <debian-l...@lists.debian.org> Changed-By: Phil Wyett <philwy...@kathenas.org> Description: live-wrapper - Wrapper for vmdebootstrap for creating live images live-wrapper-doc - Wrapper for vmdebootstrap for creating live images (Documentation Closes: 867282 Changes: live-wrapper (0.6+nmu2) unstable; urgency=medium . * Non-maintainer upload. * Remove incorrect instance of converting to UTF-8. * Eliminate 'pyversions' warnings at build time. * Add 'python-requests' build dependency. Fixes docs build. * Add 'squashfs-tools' dependency. (Closes: #867282). Checksums-Sha1: 0b37d77eaa2cb2b2f1c6212a57a449c35459d74d 1866 live-wrapper_0.6+nmu2.dsc 05a393c564f150159eca3e9ed6a3cb60edb7d64f 26664 live-wrapper_0.6+nmu2.tar.xz 46182198234b1f00fb8fac334f5a40f649fd52a5 27712 live-wrapper-doc_0.6+nmu2_all.deb e71cbe4cabb5bd6fbf4c9cac49aa1fa5c9dcacba 18112 live-wrapper_0.6+nmu2_all.deb 5f333b97e391f2c8e0301553be673989124842f4 9089 live-wrapper_0.6+nmu2_amd64.buildinfo Checksums-Sha256: 5c9e4f801d2e4ef14b7af27144947569eb1ce59b017687a590e510fc22605abf 1866 live-wrapper_0.6+nmu2.dsc 22bdce870359e3f9a2a895246c1a7e86f6376eb3cd0e4d6110a2bb6392524096 26664 live-wrapper_0.6+nmu2.tar.xz dc25916f3f0397eb6c31645bc269e32c93c6f8fb829d069b929a57c31af73304 27712 live-wrapper-doc_0.6+nmu2_all.deb c8dcca39253b2341c0bcaa68a5ef5107c3ffd6bd2bb5a2c4fe4db3dfc487470f 18112 live-wrapper_0.6+nmu2_all.deb 73a4a652c868abe775f6295a8ca69fa0703cc1fc5d6c258ef7ddef4fdc920509 9089 live-wrapper_0.6+nmu2_amd64.buildinfo Files: 20e34c6d579bb4b3b4303326eb1e4881 1866 misc optional live-wrapper_0.6+nmu2.dsc f9427142ccf26b19f1def02cc29ce3d3 26664 misc optional live-wrapper_0.6+nmu2.tar.xz 5c633b8aa58bdfa7eff6f0f26611a0fd 27712 doc optional live-wrapper-doc_0.6+nmu2_all.deb 83c95c557bac2568c50f9c960761841b 18112 misc optional live-wrapper_0.6+nmu2_all.deb 5d82b9cc0ab5545c821d93cea62c1518 9089 misc optional live-wrapper_0.6+nmu2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAllr7RIACgkQWHl5VzRC aE6Tkg/+MN4jilGj/455RvD63KAmhWfYIdgi/jBT1Yi8Vryd8qPStQbGVMmxcb+i o0Ot7U+5l9Ecsb9B84wFlXk56+5wFoGmNGnRMkgfj4HvHl7XcWE+C7WvdfJPcP5g OswQOnWc3FbjMtig+B9WW3zRhLq4DhRq14DMdI0Jac9cMr/uzWfzBvM427mmCIrm e1glRw+1KKqMZMbgnnwBsTxz9skQhadHi6cJqxxXBSfkxGk6NlP/l50CpKsJeR0S a1GmW8TQ3ynmggsGmxBXXyAatMIh7qijL+70HDQeSvD6IMQA1H23MgpZXGX5wEdU 8q1IRrdtW7c258LYiZOg4sCwiPmLKtGsPgdk4bBTRbohIat8OsnZux0ym2I6D2eV TFycJhTa/4CVW5i2OV1n801XBCsFHpZvjCu6CF+Svt028G+v0rYVx2pPDu6nCENM XThTB9Kvpxlfaekvx805AZrrf/aBO23KXT0ft+lPqnai3BPd1LVapKnW2NOJEWrR gx1v3LQTfe4XTzzaUTlfkUo9sbFnYKyfAJ7H+dI7czsF7suAxIE7Ocw8k8kEv56k rIy4Dp59NpMJKGnTyJF8JAgWECKLlbLUe8Jwmi6pyzEIDqLlSc4rZ0A28DUoVuhb tSfLJZd3Vybnljpho/HpKC6VWgpSZx2NvdHhsyR3jlvjMKYkFyE= =I4VJ -END PGP SIGNATURE-
