Bug#883383: ITP: liblog-any-adapter-tap-perl -- logging adapter suitable for use in TAP testcases
Package: wnpp Severity: wishlist Owner: Jonas Smedegaard -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: liblog-any-adapter-tap-perl Version : 0.3.3 Upstream Author : Michael Conrad * URL : https://github.com/silverdirk/perl-Log-Any-Adapter-TAP * License : Artistic or GPL-1+ Programming Lang: Perl Description : logging adapter suitable for use in TAP testcases Log::Any::Adapter::TAP shows logging output when running testcases. E.g. all "warn" and more serious messages are emitted as "diag" output on STDERR, and less serious messages as "note" comments on STDOUT. Needed by libdata-tablereader-perl. Will be maintained in the Debian Perl team. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAloj3egACgkQLHwxRsGg ASG4dRAAm2Cdw2xsDyj5BWBpd+D8pzcpqF9QnySZGt0EMr5MXmF8rAhGYNwTn+Jz ts47M6xXR3wU6qbXiAdrR6gcpn9gNIfnllukfPPikEOXQWHcwW8xr6rgcYakagm9 t2JrTbZ3f/N+0C5l+GXt/VPb7cOaatHivOCrEqCGPi4J8qkb+CzCwvW8bUlLjX5B QTEbiHfDw+hVJURkAWj9XgWH6l8uvnj3/LrCGfnMHqRaDe/sT2E/+7Up/CXPNkHE XkUtTZMLAJGZBE7hg5uu9+20ZmONP1gnhKb21+sYKR9NNDdf38Vr+e/NbrNUFnHA eMwf7oit78LvGBQfIKz7H8huV6/j21XWoiLogISfm5D5kgOJSP+DPg/BxtP8dcyM 6DLCHofrfQ1akGn0PbqJhAPwGIYh/SWh9OPEEY0B3x5gyCcrrRop3Nie0jMruhWp 5mjhGodouTgFpeEZhPfvsrOCPCzemjZRqyc2e8PqmNqVINQgQ3tNVHcPueAQBLBl DOsAvb7R0erOm9ck0EK+FCrfRC1dZH2+/IcPeMKVphYhJpCZDnlEk094v0Qf1dVA PmnQ/LinbOVokvLdk3Q+4l+udybZsIVJLk69gvXrpJr5Mp2UCOMhCtrV0lNj4+E4 Zg1M6OXbW6+nIak9dsfpu4oMtANOcpa+Mm6jQoVLrtxMR/sBDgw= =tqXM -END PGP SIGNATURE-
Bug#883393: ITP: jool -- Open Source SIIT and NAT64 Translator for Linux
Package: wnpp Severity: wishlist Owner: Bjoern Buerger * Package name: jool Version : 3.5.5 Upstream Author : Jool Dev Team * URL : http://jool.mx/ * License : GPLv3+, GPL Programming Lang: C Description : Open Source SIIT and NAT64 Translator for Linux SIIT mangles packets, simply replacing IPv4 headers and IPv6 headers. Stateful NAT64 will enable you to run multiple IPv6 client nodes behind a few IPv4 addresses. Jool is an Open Source implementation of IPv4/IPv6 Translation on Linux which aims to be fully rfc-compliant, building a bridge between IPv4-only and IPv6-only networking nodes. I consists of two kernel modules and a set of corresponding userspace tools. See http://jool.mx/en/intro-jool.html#compliance for details. --- Relevance, Maintenance, License --- Jool is one of the newer implementations for SIIT/NAT64 and has a small, but active user community (see https://github.com/NICMx/Jool). It was funded by NIC Mexico and co-developed with ITESM. I use it in several networks and it seems to be a viable solution to provide IPv4 connectivity to IPv6-only networks. Depending on the client device you can use NAT4/DNS64 odr 464XLAT and therefore have a smooth transition from IPv4-only to IPv6-only networking. There is some dkms support available in the source package, but it clearly needs some love, since e.g. quite old versions of the debian helper tools are used and the userspace code is currently not packaged at all. I am currently discussing details with the upstream authors, including the current license situation. Jool is currently licensed unter GPLv3+, leading to an incompatibility with the linux lernel GPL2 (only). Upstream is currently discussing a license change for that matter, so it might take some time before we can actually start uploading packages. Since this will be my first debian package, I'd like to start maintaining the package with the help of a sponsor. Bjørn
Re: ISO download difficult (was: Debian Stretch new user report (vs Linux Mint))
On Sat, 02 Dec 2017 11:39:56 +, Medical Wei wrote: >Actually I am thinking about people with non-free firmware problems to get >additional firmware and download them to another USB disk. >In this way the user don't need to re-download an "non-official" ISO to >install Debian. Last time I tried to download the non-free firmware and put it on another USB disk, I ended up in changing to a shell from the installer and unpacking the firmware blobs to the correct place manually because I wasn't able to figure out how the layout on the firmware disk had to be for the installer to find it. Because the docs are so vague about that and the installer didn't bother to log the path it was looking at to any log that I was able to find. And yes, I am a DD and should be able to figure that out. Any no, I didn't file a bug report because I didn't have time to do that at the time I was fiddling with the machine and now the machine is live and I can't take it out to reproduce the issue to be able to produce a meaningful bug report. And yes, I know that ranting doesn't help. If you agree, bear in mind that I was ranting about my own stupidity, not about the superiority of Debian's installer and the docs. Those are fine. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Bug#883398: ITP: node-randomfill -- Fill a buffer with random value
Package: wnpp Severity: wishlist Owner: ro...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: node-randomfill Version : 1.0.3 Upstream Author : * URL : https://github.com/crypto-browserify/randombytes * License : Expat Programming Lang: JavaScript Description : Fill a buffer with random value This package allows one to fill a buffer with random value using well known Node.js API in browser context . This a dependency of browserify. Browserify is a javaScript tool that allows developers to write Node.js-style modules that compile for use in the browser. . Node.js is an event-based server-side JavaScript engine .
Re: Debian Stretch new user report (vs Linux Mint)
On Fri, 1 Dec 2017 10:15:41 +, Jonathan Dowland wrote: >On Fri, Dec 01, 2017 at 02:34:40PM +0800, Paul Wise wrote: >>It would have been best for him to download the ISO with non-free >>firmware embedded, do you know how he made the decision to download >>the ISO without non-free firmware? > >I can't even find it from following links on debian.org, although I know >that it exists. Agreed, I failed last week finding that ISO. >>Sounds like you need to get him to file a bug against ntfs-3g and >>against whichever meta-package or other component should be installing >>ntfs-3g. > >We've missed the boat, he's not using Debian anymore. Yes. We're approaching a worst-of-both-worlds scenario: We're not Free enough to have the FSF recommend us, and we're not non-free enough for our OS to run on current hardware used by Linux beginners, and cause them to end up with OSses that are (a) not Debian, and (b) even less Free than Debian. It's the same story we had five years ago when our release cycle changed. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: Debian Stretch new user report (vs Linux Mint)
On Fri, 1 Dec 2017 21:38:46 +0500, Andrey Rahmatullin wrote: >ALso AFAIK when packages are temporarily removed from testing for various >reasons that may break the user systems (or, at least, make their >experience worse when they want to install something). At least I've seen >a position of "testing is not for users but to help us make stable", >correct me if I'm wrong. And still, testing is in _wide_ use by beginners because that's what the semi-beginners recommend since stable is old. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: ISO download difficult (was: Debian Stretch new user report (vs Linux Mint))
On Sun, Dec 03, 2017 at 04:37:24PM +0100, Marc Haber wrote: Last time I tried to download the non-free firmware and put it on another USB disk, I ended up in changing to a shell from the installer and unpacking the firmware blobs to the correct place manually because I wasn't able to figure out how the layout on the firmware disk had to be for the installer to find it. Because the docs are so vague about that and the installer didn't bother to log the path it was looking at to any log that I was able to find. And yes, I am a DD and should be able to figure that out. FWIW, I've had the same experience. I think it is time to revisit firmware distribution on easily-accessible images. Mike Stone
Announce: cme now supports autopkgtest
Hello cme now supports the autopkgtest [1] parameters defined either in debian/control or in debian/tests/control [2]. autopkgtest parameters are checked with 'cme check dpkg' and can be modified using 'cme edit dpkg' [3] Required packages: - cme - libconfig-model-dpkg-perl 2.104 - libconfig-model-tkui-perl (for 'cme edit' command) In case of problem, you can ask for help on #debian-perl or report a bug on libconfig-model-dpkg-perl All the best [1] https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html [2] https://manpages.debian.org/testing/libconfig-model-dpkg-perl/Config::Model::models::Dpkg::Tests::Control.3pm.en.html [3] https://github.com/dod38fr/config-model/wiki/Managing-Debian-packages-with-cme -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
Bug#883414: ITP: autosuspend -- A configurable daemon to suspend a system in case of inactivity
Package: wnpp Severity: wishlist Owner: Johannes Wienke * Package name: autosuspend Version : 1.0.0 Upstream Author : Johannes Wienke * URL : https://github.com/languitar/autosuspend * License : GPL Programming Lang: Python Description : A configurable daemon to suspend a system in case of inactivity Autosuspend is a configurable daemon to suspend a system in case of inactivity. Its main usage scenario are home servers like NAS systems or media centers that should be sleeping if they are not needed. Autosuspend provides a set of configurable checks that determine whether the system is currently active or not. These checks do not depend on Xorg (though one check supports querying X idle time). There are a lot of different scripts roaming around the internet for this purpose but none of them is really generic and as flexible as autosuspend. Moreover, they have not been packaged. Autosuspend tries to collect the various efforts to provide such a system in a well-maintained daemon that is ready for use. I am the author of the software and plan to provide package updates whenever necessary. I hope that by providing this software as a package in Debian more users can easily make use of it and don't need to fight with outdated scripts found somewhere on the internet. Ultimately, this hopefully reduces unnecessary energy consumption. I have already drafted the required Debian packaging infrastructure, which is available here: https://github.com/languitar/autosuspend-debian. A first request for a review regarding this on the IRC channels was positive and proposed to open the ITP.
Re: Debian Stretch new user report (vs Linux Mint)
On 12/01/2017 05:31 PM, Alf Gaida wrote:
> On 01.12.2017 16:53, Ian Jackson wrote:
>> Simon McVittie writes ("Re: Debian Stretch new user report (vs Linux Mint)"):
>>> I find it interesting that we're having this conversation at the same
>>> time as a thread about how there should be a configuration option that
>>> denies our users the opportunity to choose to install non-free software.
>> Perhaps you mean: a configuration option that allows a user not to be
>> nagged to install non-free software.
>>
>> FAOD I agree that the current situation with install images for random
>> PCs is quite unsatisfactory, but I don't know how to square the circle.
>>
>> Ian.
>>
> Ian, thats dead easy - put the needed packages onto the iso and be done
> with. The installer should have an option to opt-in contrib and/or
> non-free. Done. Ok, that was the technical part. The other part of the
> story would be that the FSF wouldn't like us for that step.
The FSF wouldn't be the only one. I at least, and probably a lot of
Debian contributors, would start hating Debian for promoting hardware
that needs non-free drivers if the non-free ISO was the default one. If
this drives some of our users away, never mind, we're doing free
software, that's what Debian is about.
> and some other people who think
> that every debian user need to be educated that one has to buy hardware
> that would work without non-free things.
Yes, I do believe it's important to educate people to free software.
> The majority of the users would be happy.
Happy, but using non-free software. This isn't what Debian is about.
I've signed-up on the social-contract, and I stand by it.
> What do we weight more: Happy users or free software?
Free software, definitively. If users aren't happy, it's not our fault,
but the one of hardware makers that are promoting non-free software.
Instead trying to convince Debian people, it'd be better if you spent
your energy trying to convince hardware makers.
> The FSF has answered this before - Debian is not
> free, so they don't recommend us.
Honestly, and with all due respect, I don't care the FSF view. It just
happens to be the same as mine, which is good. But what the FSF view is,
isn't what motivates me. It's what the Debian view is. That's what
counts when contributing to Debian, not the view of a 3rd party
organization, even if it deserves a lot of respect, like the FSF.
> Their choice. We choose to promote and
> deliver iso's without any non-free. Our choice. And for the people with
> the needed knowledge there are iso's that will work well with nearly all
> hardware. Sounds fair, doesn't it?
Instead of flaming the FSF, you should probably advocate for having the
non-free ISO promoted a little bit more. Please leave the FSF alone,
it's a very nice organization, and they do super nice work. We aren't
working against each others.
> Debian
> will be limited to users who prefer free software or have the knowledge
> to work around these limitations. Or are able to find the working isos
> with non-free.
It's probably that last bit that needs to be fixed. In my view, it'd be
fine to promote this ISO a little bit more, as long as we write in BOLD
that this contains non-free drivers, and how bad hardware makers are.
Cheers,
Thomas Goirand (zigo)
Re: Debian Stretch new user report (vs Linux Mint)
On Sun, 3 Dec 2017 21:17:59 +0100, Thomas Goirand wrote: >The FSF wouldn't be the only one. I at least, and probably a lot of >Debian contributors, would start hating Debian for promoting hardware >that needs non-free drivers if the non-free ISO was the default one. If >this drives some of our users away, never mind, we're doing free >software, that's what Debian is about. Debian is also about providing an Universal Operating System, and I have seen BIG installations of Debian on server farms moving to PragBF because the Broadcom network chips on those servers required people jumping through hoops while PragBF just works. We're actively driving _real_ users, those that also shell out money to sponsor Debian, away from Debian with those steps. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber | " Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834
Re: ISO download difficult (was: Debian Stretch new user report (vs Linux Mint))
On Sat, Dec 02, 2017 at 11:59:08AM +, Sue Spence wrote: > On 2 December 2017 at 11:49, Holger Levsen wrote: > > > On Sat, Dec 02, 2017 at 12:32:29PM +0100, Geert Stappers wrote: > > > URL is https://cdimage.debian.org/cdimage/unofficial/non-free/ > > cd-including-firmware/ > > > > so who will make nonfree.debian.net and non-free.debian.net > > http-redirect to that URL? :) > > I'll be writing a blog post this weekend which links to it, if only for my > own sake. I get the joke of course, but Debian is free with or without the > firmware so I wouldn't set up such a redirect out of my own pedantic > notions of correctness, never mind everyone else's. :) How about https://works-on-pcs.debian.org? :-) Personally, as a developer, I will say there is one benefit of being so user-unfriendly that the usable ISO is hidden under the beware-of-leopard sign, which is that it serves as a "you have to be this technically aware to install debian" barrier. As a result, we don't have the low signal-to-noise bug reports that are all-too-common on Ubuntu's launchpad.net. So if we want to reform our "FSF-ly correct freedom is more important than being friendly to novices" (and it's not clear Debian as a whole agrees with this sentiment), folks might want to consider that this probably means we will need to have more people doing bug triage. Personally, I think prioritizing users who just want to a working PC/Laptop over the FSF is the right choice, since I belong to the pragmatic wing of the Open Source movement, but I suspect I'm in the minority in the Debian community. Which is fine; I'll just continue to enjoy the high quality of most bug reports in the Debian BTS. :-) - Ted
Re: Debian Stretch new user report (vs Linux Mint)
On 03.12.2017 21:17, Thomas Goirand wrote: > The FSF wouldn't be the only one. I at least, and probably a lot of > Debian contributors, would start hating Debian for promoting hardware > that needs non-free drivers if the non-free ISO was the default one. If > this drives some of our users away, never mind, we're doing free > software, that's what Debian is about. With all due respect - i can't follow here, no way. In that case i never ever has joined Debian nor spend an hour on it. So - first thing was to read and understand the Debian Social Contract. Do you remember, you once aggreed with this too: 1. Debian will remain 100% free We provide the guidelines that we use to determine if a work is "free" in the document entitled "The Debian Free Software Guidelines". We promise that the Debian system and all its components will be free according to these guidelines. We will support people who create or use both free and non-free works on Debian. We will never make the system require the use of a non-free component. ^^ And i take that dead serious - i work only on free software, but i use non-free too. And i think i will do so in future. 4. Our priorities are our users and free software We will be guided by the needs of our users and the free software community. We will place their interests first in our priorities. We will support the needs of our users for operation in many different kinds of computing environments. We will not object to non-free works that are intended to be used on Debian systems, or attempt to charge a fee to people who create or use such works. We will allow others to create distributions containing both the Debian system and other works, without any fee from us. In furtherance of these goals, we will provide an integrated system of high-quality materials with no legal restrictions that would prevent such uses of the system. ^^ Hmm, i can't read anything about: I don't care about users, they suck, i do free software. > Happy, but using non-free software. This isn't what Debian is about. > I've signed-up on the social-contract, and I stand by it. > >> What do we weight more: Happy users or free software? > Free software, definitively. If users aren't happy, it's not our fault, > but the one of hardware makers that are promoting non-free software. > Instead trying to convince Debian people, it'd be better if you spent > your energy trying to convince hardware makers. Cool - but i don't aggree here - i work hard on free software, not for free software. I want happy users to use this software. I left out the FSF part - nothing new. And promoting our free ISOs will not make them working better. If they work on some hardware or in some virt. machines - cool. But in real life a new Debian user has some hardware and not much experience in running a linux system. And do you really expect that a new user will be interested in Debian politics first hand? I guess no. If we drive those users away from Debian they are a loss for the whole FOSS ecosystem. But if they stay and become educated over time ... > It's probably that last bit that needs to be fixed. In my view, it'd be > fine to promote this ISO a little bit more, as long as we write in BOLD > that this contains non-free drivers, and how bad hardware makers are. > > Cheers, > > Thomas Goirand (zigo) > It is not only the last bit. And i don't think that 'a little bit more' promotion is sufficient. We should clearly state why we prefer the free ones. But we should not hide the non-free ones and should have them on the same site. With a clear statement why these images are not prefered. Cheers Alf Gaida (agaida)
Re: recommends for apparmor in newest linux-image-4.13
On Wed, Nov 29, 2017 at 11:51:55AM -0800, Russ Allbery wrote: > Michael Stone writes: > > On Tue, Nov 28, 2017 at 08:22:50PM -0800, Russ Allbery wrote: > > >> Ubuntu has successfully shipped with AppArmor enabled. > > > For all the packages in debian? Cool! That will save a lot of work. > > Yes? I mean, most of them don't have rules, so it doesn't do anything, > but that's how we start. But indeed, Ubuntu has already done a ton of > work here, so it *does* save us quite a bit of work. The fact that AppArmor doesn't do anything if it doesn't have any rules is why we have a chance of enabling it by default. The problem with SELinux is that it's "secure" by the security-weenies' definition of secure --- that is, if there isn't provision made for a particular application, with SELinux that application is secure the way a computer with thermite applied to the hard drive is secure --- it simply doesn't work. Every few years, I've tried turning on SELinux on my development laptop. After it completely fails and trying to make it work just work for the subset of application that I care about, I give up and turn it off again. Having some kind of LSM enabled is, as far as I am concerned, better than nothing. (And I speak as someone who chaired the IP Security working group at the IETF, and was the technical lead for the MIT Kerberos V5 effort. If admitting that I'm too dumb or don't have enough patience to figure out how to make SELinux work on my development laptop means that someone is going to revoke my security-weenies' union card, I'm happy to turn it in) - Ted
Bug#883429: ITP: nanopass-framework-scheme -- Embedded DSL for writing compilers in Scheme
Package: wnpp Severity: wishlist Owner: Göran Weinholt * Package name: nanopass-framework-scheme Version : 1.9 Upstream Author : Dipanwita Sarkar, Andrew W. Keep, R. Kent Dybvig, Oscar Waddell * URL : https://github.com/nanopass/nanopass-framework-scheme * License : MIT/Expat Programming Lang: Scheme Description : Embedded DSL for writing compilers in Scheme This is a build dependency of Chez Scheme.
Should tasks be considered harmful?
tl;dr: Desktop tasks have unexpected (from the user point of view) side effects due to dependencies. This can be considered harmful since the installer task selection can easily can trick a user into installing a "substandard" system. Yesterday I did something I rarely do: I installed Debian from scratch on a laptop. This is not something I do a lot, simply because there is no reason with the excellent upgrade support Debian has. Even when I occasionally change hardware, I usually migrate as much configuration as possible - including the list of installed packages. I must admit that I had very high expectations based on my previous experience with Debian. I expected a smooth install ending up with a system where everything just worked. And it was close. But not quite. And the failure was so unnecessary, and potentionally so difficult to figure out for new users, that I think it is worth considering as a much larger problem than a simple installation bug. This old laptop had a built-in 3G modem (an Ericsson F3507g - not that it matters), which I "knew" would work fine in Debian. Aleksander, Dan and all the contributors have done a very nice job with ModemManager. But the modem did not work. Because ModemManager wasn't installed at all! How did that happen? I had briefly looked at desktop task choices during installation, and not being too fond of any of the DEs, I arbitrarily selected LXDE. Figured it couldn't hurt having a lightweight DE on an almost 10 year old laptop. What I missed completely was that the lxde package, which obviously is a dependency of task-lxde-desktop, has this in its recommends: wicd | network-manager-gnome So it drags in wicd instead of network-manager-gnome. Which I can perfectly understand from a lightweight point of view. But the problem is that these two packages don't support the same features, and 'lightweight' isn't a good selection criteria during installation. In a perfect world, the installer could have had sufficient information about the hardware and the users wishes to make this choice. But it has not. So it should install the options which are most likely to work for all users. Which is clearly network-manager in this case. Replacing wicd with network-manager-gnome, which drags in network-manager and modemmanger, fixed my modem issue. But how would a user without any previous knowledge of modemmanager or Linux networking be able to figure this out? As a new user, would you even dare to rip out the core network tool which was installed by default, to replace it with something else? I don't think so. Many users would be stuck with a non-working 3G modem and not being able to fix it. Which I find terribly sad, knowing the hard work put into making ModemManager work as well as it does. Now, of anyone is still reading, you are probably wondering why I didn't just open a bug instead of writing this long story here. Well, AFAICS there is no bug. There is nothing wrong with the installer. It just did what I asked it to, since I selected this specific task. I don't think it is reasonable to expect the installer to do any dependency validation or overrides. That would be crazy. T There is also nothing wrong with the task-lxde-desktop. It depends of lxde, which it obviously must do. I don't think there is anything wrong with lxde either. Recommending wicd is fine with me. It's just not suitable for everyone, and therefore unsuitable as an installation default. But that should not be a concern for lxde. And there is certainly nothing wrong with wicd. It serves its purpose, and does it well. A limited feature set is a perfectly valid design choice. So the installation end result is bad, but every package and subsystem does exactly what they are supposed to do. It is the overall system design that fails. Which is why I think this is more of a policy question than a bug. Thinking on how I went wrong, I have come to the conclusion that I would have been much better off if there were no desktop task choice at all. If I just got Gnome or whatever would be the default. Then I would also get the one and only "default set of Debian packages", without any unexpected replacements. I would of course still be free to change the default desktop selection after installation, as well as anything else. But then I would have had a much better opportunity to see the consequences, if dependencies caused important system packages to be replaced. IMHO the task selection during installation is harmful. Unpredictable (from user point of view) results cannot be avoided, since any additional package selected during installation will modify the resolved set of dependencies. I believe there was a similar problem related to automatic package selection based on detected network environment during install. This has been resolved. But the underlying issue is still there: If you allow the installer to select or deselect *any* package during installation, then it is very
Bug#883430: ITP: stex -- stex to latex and latex to html converters and associated tools
Package: wnpp Severity: wishlist Owner: Göran Weinholt * Package name: stex Version : 1.2.1 Upstream Author : R. Kent Dybvig and Oscar Waddell * URL or Web page : https://github.com/dybvig/stex * License : MIT/Expat Programming Lang: Scheme, TeX Description : stex to latex and latex to html converters and associated tools This is a build dependency of Chez Scheme.
Re: Debian Stretch new user report (vs Linux Mint)
On 12/03/2017 11:20 PM, Alf Gaida wrote: > It is not only the last bit. And i don't think that 'a little bit more' > promotion is sufficient. We should clearly state why we prefer the free > ones. But we should not hide the non-free ones and should have them on > the same site. With a clear statement why these images are not prefered. As I wrote to you privately (why did you send 2 separate emails?), this last paragraph shows we agree: we both want the ISO including these bad firmwares to be reachable, as long as we very much insist on the fact that it's an unfortunate non-free workaround for bad hardware vendors, and that we prefer the version not including these. So let's not argue more! :) Cheers, Thomas Goirand (zigo)
Re: Should tasks be considered harmful?
On Mon, Dec 4, 2017 at 6:43 AM, Bjørn Mork wrote: > But how would a user without any previous knowledge of modemmanager or > Linux networking be able to figure this out? It sounds like you are looking for isenkram to be integrated into the installer so that the knowledge of which package maps to which hardware is available to the user when doing an install and for modemmanager to declare which devices it supports via AppStream and for installing modemmanager to pull in networkmanager and remove wicd: https://tracker.debian.org/pkg/isenkram http://people.skolelinux.org/pere/blog/tags/isenkram/ https://wiki.debian.org/AppStream/Guidelines#Announcing_supported_hardware -- bye, pabs https://wiki.debian.org/PaulWise
Re: Debian Stretch new user report (vs Linux Mint)
On Mon, Dec 4, 2017 at 5:22 AM, Marc Haber wrote: > Debian is also about providing an Universal Operating System, and I > have seen BIG installations of Debian on server farms moving to PragBF > because the Broadcom network chips on those servers required people > jumping through hoops while PragBF just works. Could you link to PragBF? I can't find any mention of it on web search engines. -- bye, pabs https://wiki.debian.org/PaulWise
