Bug#927996: RFS: diskfit/2.0.2.3 [ITP] -- Simple disk fit calculator
Good morning, an updated package is available at https://launchpad.net/~velnias/+archive/ubuntu/sandbox/+sourcefiles/diskfit/ 2.0.2.13-1~eoan~ppa1/diskfit_2.0.2.13-1~eoan~ppa1.dsc Am Dienstag, 11. Juni 2019, 00:41:15 CEST schrieb Adam Borowski: > Hi! > > On Wed, May 29, 2019 at 08:30:50AM +0200, Heiko Schäfer wrote: > > You'll need to update that for the final upload, but during the review > that's ok. Of course I will do that as soon as I have a final place to upload it. > debian/copyright needs an entry for install-sh which is under the MIT/X11 > license. I hope I got the right license text. > debians/source/options forces xz level 9 compression, which for this size of > files is harmful (doesn't improve disk space, and requires a lot of memory > on tiny machines). Please just drop these settings -- they should be used > only in special cases. I've removed this file completely. > debian/control: could you please fill in Homepage/Vcs-*, or at least drop > the commented out fields? done. > The long desc really needs to be extended. Even with trying to use the > program, I had some trouble finding out what it is for. To describe it is a big challenge for me. I hope is is a bit clearer now. I'm aware it is a quite special tool, but my search for an existing one I could integrate in my daily workflow has been unsuccessful, so I decided to write one for myself. Over 3 years being a lot of help, I decided to make it available to a broader audience by requesting it to get added to Debian. > Also, a man page is vital for a command-line tool. I added one for 'diskfit'. I did none for the GUI. > Upstreamish side: I played with the GUI a bit, and it seems to handle > selecting a dir badly (which, in my naive understanding, is what most > people will try to do). It does nothing until you click "Cancel", in > which case it'll add one of previously (not currently) show directories. > And then the program doesn't seem to do anything useful. So, if dirs > are not supported, the programs shouldn't at least try them. First of all a *big* thank you for this extra testing! At least in my version of Qt (5.12.3) it is - as wanted - not possible to just select a directory. I guess you mean the contents of an entire directory. Due to the mathematical nature of combinatorics the larger the amount of files to process, the 'much' longer it takes. On my PC it takes around 7.5 h to process 38 files. Good for an overnight calculation :-) The progress bar is updated discretely at 1 % steps, so - if you have a lot of input files - it can take a *long* time until you will see any progress. This is unavoidable, because a non-discrete update (of the underlying) diskfit process would slow down everything up to an absolutely unacceptable amount of time. There is a second drawback, if you are patient and you're close to 50 % it can happen, that the remaining 50 % will run nearly as fast as light. The progress calculation is divided into two parts: 1) the calculation of all combinations (lengthy) 2) preparing the output (*can* be lengthy, but hard to predict) The goal of this tool is to approach the target size as exactly as possible and not to use heuristical algorithms and the most common use cases will do that in a reasonable time. Of course it is not meant to recursively create a set of optimally fitted DVDs for a huge collection of movies. You could try out a similar example I use to generate the profile information while building: - choose the file pattern '[cdmMR]*' from src/diskfit, no directories just files - choose a custom target of 72240 bytes This should give you two results and will run under one second. If you have ideas how to communicate this behaviour to the user, I would be thankful. > > Meow! P.S. I love funeral doom too :-D
Bug#929773: marked as done (RFS: wf-recorder/0.1-1 [ITP] ITP)
Your message dated Tue, 11 Jun 2019 01:39:53 +0200 with message-id <20190610233953.gb15...@angband.pl> and subject line Re: Bug#929773: RFS: wf-recorder/0.1-1 ITP has caused the Debian Bug report #929773, regarding RFS: wf-recorder/0.1-1 [ITP] ITP 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.) -- 929773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "wf-recorder" * Package name : wf-recorder Version : 0.1-1 Upstream Author : Ilia Bozhinov * Url : https://github.com/ammen99/wf-recorder * Licenses : Expat Programming Lang : C Section : x11 wf-recorder is a utility program for screen recording of wlroots-based compositors (more specifically, those that support wlr-screencopy-v1 and xdg-output). Its dependences are ffmpeg, wayland-client and wayland-protocols. It builds those binary packages: * wf-recorder To access further information about this package, visit the following URL: https://mentors.debian.net/package/wf-recorder Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/w/wf-recorder/wf-recorder_0.1-1.dsc Alternatively, you can access package debian/ directory via git from URL: https://salsa.debian.org/bisco-guest/wf-recorder.git More information about wf-recorder can be obtained from https://github.com/ammen99/wf-recorder cheers, Birger --- End Message --- --- Begin Message --- On Thu, May 30, 2019 at 08:57:38PM +0200, Birger Schacht wrote: > * Package name : wf-recorder > wf-recorder is a utility program for screen recording of wlroots-based > compositors (more specifically, those that support wlr-screencopy-v1 > and xdg-output). Its dependences are ffmpeg, wayland-client and > wayland-protocols. > > It builds those binary packages: > > * wf-recorder Hi! As usually, I have no prepared setup for testing wayland tools -- but, no one among active sponsors seems to have that either. Thus, I've reviewed the packaging only, and it looks ok. Uploaded. As the program takes a number of arguments, having a man page describing it is very important. But that's a matter for after NEW -- for now, lets get the package in. Thanks for your work so far! Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Sometimes you benefit from delegating stuff. For example, ⢿⡄⠘⠷⠚⠋⠀ this way I get to be a vegetarian. ⠈⠳⣄--- End Message ---
Bug#927996: RFS: diskfit/2.0.2.3 [ITP] -- Simple disk fit calculator
Hi! On Wed, May 29, 2019 at 08:30:50AM +0200, Heiko Schäfer wrote: > an updated package is available at > > https://launchpad.net/~velnias/+archive/ubuntu/sandbox/+sourcefiles/diskfit/2.0.2.6-1~eoan~ppa1/diskfit_2.0.2.6-1~eoan~ppa1.dsc > > Please ignore the '~eoan~ppa1' for the moment, because I build my packages > currently via Ubuntu's Launchpad. 'Eoan' comes closest to 'sid'. You'll need to update that for the final upload, but during the review that's ok. debian/copyright needs an entry for install-sh which is under the MIT/X11 license. debians/source/options forces xz level 9 compression, which for this size of files is harmful (doesn't improve disk space, and requires a lot of memory on tiny machines). Please just drop these settings -- they should be used only in special cases. debian/control: could you please fill in Homepage/Vcs-*, or at least drop the commented out fields? The long desc really needs to be extended. Even with trying to use the program, I had some trouble finding out what it is for. Also, a man page is vital for a command-line tool. Upstreamish side: I played with the GUI a bit, and it seems to handle selecting a dir badly (which, in my naive understanding, is what most people will try to do). It does nothing until you click "Cancel", in which case it'll add one of previously (not currently) show directories. And then the program doesn't seem to do anything useful. So, if dirs are not supported, the programs shouldn't at least try them. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts ⣾⠁⢰⠒⠀⣿⡁ productivity. You can read it, too, you just need the ⢿⡄⠘⠷⠚⠋⠀ right music while doing so. I recommend Skepticism ⠈⠳⣄ (funeral doom metal).
Re: RFC: endorse debian-mentors as entrance to our infrastructure projects
Hi again, Jonas Meurer: > So here's the idea we came up with: We could explicitely broaden the > scope of debian-mentors to include any questions regarding Debian > infrastructure software. > That basicly would mean to explicitely mention "questions on > infrastruc-ture projects" in our docs about debian-mentors. > Additionally, when the infrastructure teams don't have time to mentor > new contributors, they could point them to debian-mentors. > > My hope is that having debian-mentors as an endorsed entry point for > diving into Debian infrastructure would lower the entry barrier > significantly for new contributors who'd like to dive into our > infrastructure software projects. Thanks a lot to everybody involved in the discussion so far. Apparently there's some support for the idea, so I'll try to drive it forward. Next step will be to update the documentation about debian-mentors: * Update the DebianMentorsFaq wiki page[1] and make it explicit that questions about Debian infrastructure projects and services are on-topic. * Update the debian-mentors list description[2]. * Maybe add a shore paragraph about the scope of the debian-mentors channels to the startpage of mentors.debian.net? While it's a separate service, it probably is an entry point for prospective contributors. * I already updated the description about #debian-mentors on the IRC wiki page[3]. [1] https://wiki.debian.org/DebianMentorsFaq [2] https://lists.debian.org/debian-mentors/ [3] https://wiki.debian.org/IRC I'll try to take care of this within the next days. Nevertheless, help would be appreciated ;) Are there any places that I'm missing? Once this is done, it should be announced on more popular channels. Misc Developer News[4] would be a good one and maybe also a dedicated mail to debian-devel-announce? [4] https://wiki.debian.org/DeveloperNews I think the key to success here is that people in Debian (especially those in infrastructure/service teams) have to adapt to the practice of pointing newbies with their questions to debian-mentors. Paul Wise: > As someone who is regularly answering mentors questions, is a DSA > member, a wiki admin, maintainer of the derivatives services and > contributor to some of the QA services, I would be happy to answer any > infrastructure questions that come up on debian-mentors. That's fantastic news. Thanks a lot for being open to it and offering help :) Sam Hartman: > I wonder whether it might be a good idea to write down which > infrastructure services people in the mentors community are most able > to help with. I don't think, that's necessary - or even helpful. Also, it would mean that some kind of "experts" for infrastructure projects would have to volunteer for ansering questions on debian-mentors, which in my eyes makes the whole idea way to complicated. I think we should give it a try without explicitely documenting *which* infrastructure services will be supported by debian-mentors. As Paul said, people on debian-mentors might be able to help with research and looking up things in case they don't know the answers themselves - something that's already very useful for new contributers that tend to get lost in the huge Debian ecosystem ;) Cheers jonas signature.asc Description: OpenPGP digital signature
Re: RFC: endorse debian-mentors as entrance to our infrastructure projects
Adrian Bunk wrote: > […] I'm not sure whether this particular sub-thread is salvagable but I thought I might briefly share the below in order that it might prevent parallel cases elsewhere. There exists a particular argument style where one participant in the discussion asks a collection of essentially reasonable "devil's advocate" questions to the group. Whilst this can superfically appear to be an instance of the Socratic method this can unfortunately be inadvertently and subconsciously interpreted as passive-agressive. This is due to the way it can mask provocative positions as "mere" questions but it generally shifts the burden of proof and — as it requires an asymmetric level of energy to "answer" the implied viewpoints — it can make as others feel cornered, leading to a defensive and ultimately unproductive discussion. Naturally, if there was any perception that this tactic was deployed deliberately this will only heighten any antagonism felt by the group. Do note that that it is not necessarily the questions themselves that are considered the problem but rather that the response is constructed predominantly of them. Personally, I have been over-indulgent in using such "devil's advocate" positions in the past, but after some feedback I realised that it did not have the intellectually stimulating quality I was hoping for and merely distanced myself from whom I wished to convince. After reducing my usage and spending moretime & effort adopting alternative modes of argument I found my attempts to connect with and ultimately persuade others to be far more effective. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
