[DNG] Runit for Devuan: was Debian testing drop redis
On Thu, 26 Oct 2017 23:38:27 +0200 Adam Borowskiwrote: > On Thu, Oct 26, 2017 at 04:18:12PM -0400, zap wrote: > > I only wish runit-init was still on the debian repo. or in the > > devuan repo at least... > > It was kicked out from stretch because something bad happened to its > maintainer (he still hasn't recovered and then he'll probably have > more important things to do) -- and no one volunteered to fix the RC > bug. I did even ask here on this list, but alas, I did not help > either. > > No one has stepped up to fix runit-init and restore it since then. U mean runit's author/upstream maintainer, or do you mean Debian's maintainer for runit? Where does this information come from? I haven't read any such thing. The last time I downloaded, compiled and installed runit it worked just fine. Where did you read about this problem with the (which) maintainer? If there's a problem with Debian's runit maintainer, no sweat: Pair me up with somebody who is good with making packages, and we'll create a Devuan runit package much better than Debian's old one (which was kind of difficult the last time I tried it). If runit's author/upstream author has had bad stuff happen to him to th extent that runit isn't trusted anymore, s6 is a fairly close replacement: A little more complex and a little more capable. AFAIK s6's maintainer is on the job every day improving s6, and once again, someone who knows how to build Devuan package plus me plus a little bit of guidance from s6' upstream would produce a Devuan package. Who on this list is an apt packaging ninja and wants to work on this with me? SteveT Steve Litt October 2017 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On 10/26/2017 05:38 PM, Adam Borowski wrote: > On Thu, Oct 26, 2017 at 04:18:12PM -0400, zap wrote: >> I only wish runit-init was still on the debian repo. or in the devuan >> repo at least... > It was kicked out from stretch because something bad happened to its > maintainer (he still hasn't recovered and then he'll probably have more > important things to do) -- and no one volunteered to fix the RC bug. I did > even ask here on this list, but alas, I did not help either. > > No one has stepped up to fix runit-init and restore it since then. If only I had the experience and actual skills/knowledge, I might have... but nah... not at this time do I have such things. Maybe in the future... who knows. > > > Meow! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
Hi Steve, > > I am the maintainer of Redis in Debian. All I have done is removed > > some ill-conceived hooks that were not used by anyone. I have not > > dropped sysvinit support and nor do I have any intention to do so. I > > only ask politely that you do stop to refering to my work as > > "vandalism". […] > Are you sure everyone agrees that the hooks are ill-conceived, and are > you sure *nobody* is using them? Naturally, I have no idea whether someone on a desert island is using them so that is an unfair question. However, I have not heard of anyone using them (even when they were buggy) and they are not only Debian-specific, there are much cleaner, and uniform (ie. across all possible daemons) ways of doing such things. > > If I remember correctly, one reason for > > becomig independent was to avoid Debian sabotage like we're appearing > > to see now on redis. This is not sabotage. I'm afraid I am running out of energy to expend on this issue, especially when there seems to be a non-trivial amount of bad faith on this list and I appear to have to repeat myself here and on the Github issue that this has absolutely nothing to do with systemd etc. > So just like we need to cut you a little slack, you need to cut us a > little slack. Starting with the Kangaroo Court bug 727708 > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708) and > proceeding through the last-minute bogus alternative in the General > Resolution, Debian has shown malace toward those wanting Linux to > remain an OS with interchangeable parts and smal I'm sorry but I do not have the energy, time, nor inclination to respond to this kind of unnecessary provocation. Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader 2017 `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chris Lamb = Good Maintainer (Was: Debian testing drop redis)
Patrick, > I opened a pull request with Chris Lamb to discuss reverting his changes > to the sysvinit scripts in redis-server and redis-sentinel. ^^^ I'm not sure how many times I can repeat myself on this point but this was not a sysvinit-specific change. As you can clearly see from the diff the parallel {Pre,Post}Exec calls were removed from the systemd unit file at the same time. Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader 2017 `. `'` la...@debian.org / chris-lamb.co.uk `- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Fwd: Auto-Re: gpg 2.2.x devuan jessie no TOFU TLS
Forwarded Message Subject: Auto-Re: gpg 2.2.x devuan jessie no TOFU TLS Date: Thu, 26 Oct 2017 23:40:38 +0800 From: xuchunx...@zjut.edu.cn To: fulanope...@cryptolab.net 邮件已收到,谢谢! 徐春晓 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] OT: Patching De*an based systems at scale
On Thu, Oct 26, 2017 at 11:12:08AM -0500, dev wrote: > Hi All, > I'd like to have a discussion about how to scale patch management on > De*an based systems. > Is there a better way to get information about patch fixes other than > digging up the Changelogs from a web browser? You're not insane enough to run an unreleased version on a production server, right? If so, every single update is accompanied by a DSA mail (subscribe to debian-security-annou...@lists.debian.org) or a point release (debian-announce). As you specified "De*an", these apply to both distributions matching this wildcard: if *=bi, to every package, if *=vu, ones with a systemd dependency might face a slight delay (but less than 0.1% of packages have such dependency). Both DSA and point releases do list everything that has changed in packages being updated. You may additionally install apt-listchanges and configure it to show changelogs, that will fetch relevant (and only those!) changelog entries of packages you're about to install. On a system running testing or unstable, apt-listchanges is the only way. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. ⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift ⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters ⠈⠳⣄ relevant to duties], shall be punished by death by shooting. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On Thu, Oct 26, 2017 at 04:18:12PM -0400, zap wrote: > I only wish runit-init was still on the debian repo. or in the devuan > repo at least... It was kicked out from stretch because something bad happened to its maintainer (he still hasn't recovered and then he'll probably have more important things to do) -- and no one volunteered to fix the RC bug. I did even ask here on this list, but alas, I did not help either. No one has stepped up to fix runit-init and restore it since then. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ Laws we want back: Poland, Dz.U. 1921 nr.30 poz.177 (also Dz.U. ⣾⠁⢰⠒⠀⣿⡁ 1920 nr.11 poz.61): Art.2: An official, guilty of accepting a gift ⢿⡄⠘⠷⠚⠋⠀ or another material benefit, or a promise thereof, [in matters ⠈⠳⣄ relevant to duties], shall be punished by death by shooting. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Amprolla3 is out for testing
Hi, ...on Fri, Oct 20, 2017 at 04:47:57PM -0500, goli...@dyne.org wrote: > - replace "auto.mirror.devuan.org" with "pkgmaster.devuan.org" in > your /etc/apt/sources.list > - # apt-get update > - # apt-get install devuan-keyring I just updated an ascii system that had been shut down for three months, and the only minor nitpick is that I had to get an updated devuan-keyring *before* changing the sources to pkgmaster.devuan.org... Alex. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ..proper use of /merged and /devuan, was: Trouble with apt-get upgrade over TOR
Ok, this is the message by fsmithred I was referring to on my previous note. > From: fsmith...@gmail.com > To: dng@lists.dyne.org > > My understanding is that for anything found under /merged on the server, > you should use /merged in your sources, and anything found ONLY under > /devuan needs to have /devuan in the sources. Below are the directory > listings from pkgmaster.devuan.org showing jessie, ascii and ceres, for > both /merged and /devuan. I marked the ones that are unique to /devuan > with a star. > > https://pkgmaster.devuan.org/merged/dists/ > ascii/ 11-Aug-2017 09:46 > ascii-backports/ 11-Aug-2017 09:46 > ascii-proposed-updates/ 04-Sep-2017 09:51 > ascii-security/ 11-Aug-2017 09:45 > ascii-updates/ 11-Aug-2017 09:45 > ceres/ 11-Aug-2017 09:45 > jessie/ 11-Aug-2017 09:44 > jessie-backports/ 22-Oct-2017 10:58 > jessie-proposed-updates/ 11-Aug-2017 09:42 > jessie-security/ 11-Aug-2017 09:42 > jessie-updates/ 11-Aug-2017 09:42 > > https://pkgmaster.devuan.org/devuan/dists/ > ascii/ 25-Oct-2017 10:02 > ascii-backports/ 25-Oct-2017 10:02 > *ascii-proposed/ 25-Oct-2017 10:02 > *ascii-proposed-security/ 25-Oct-2017 10:02 > ascii-proposed-updates/ 25-Oct-2017 10:02 > ascii-security/ 25-Oct-2017 10:02 > ascii-updates/ 25-Oct-2017 10:02 > ceres/ 25-Oct-2017 10:02 > *experimental/ 25-Oct-2017 10:02 > jessie/ 25-Oct-2017 10:02 > jessie-backports/ 25-Oct-2017 10:02 > *jessie-proposed/ 25-Oct-2017 10:02 > *jessie-proposed-backports/ 25-Oct-2017 10:02 > *jessie-proposed-security/ 25-Oct-2017 10:02 > jessie-proposed-updates/ 25-Oct-2017 10:02 > jessie-security/ 25-Oct-2017 10:02 > jessie-updates/ 25-Oct-2017 10:02___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] many many 404 when upgrading/installing packages
From: fulanope...@cryptolab.net > To: dng@lists.dyne.org > > KatolaZ: >> On Mon, Oct 23, 2017 at 01:15:08PM +, Fulano Diego Perez wrote: >>> >>> >>> KatolaZ: # apt-get update before trying to install/upgrade packages? One reason why you might have a 404 is that the cache kept by apt is older than the actual version. >>> >>> dont be sorry. >>> >>> yes, did the obvious updates .. >> >> OK. Could you please retry and report which packages give a 404, and >> also post the relevant sections of your sources.list? > > i just went back to default for now... It could that going back may not be giving you a 404 error but you may have the incorrect repository. Based on advise passed yesterday by fsmithred on Dev1.galaxy forum I compiled a complete list of repositories as found on pkgmanager. According to fsmithred those that are both on devuan and merged should be on merged. Those that are only on devuan and not merged should only be on devuan. So the complete list to pick from (some are optional repositories) is this: deb https://pkgmaster.devuan.org/merged/ ascii main contrib non-free deb https://pkgmaster.devuan.org/merged/ ascii-backports main contrib non-free deb https://pkgmaster.devuan.org/merged/ ascii-proposed-updates main contrib non-free deb https://pkgmaster.devuan.org/merged/ ascii-security main contrib non-free deb https://pkgmaster.devuan.org/merged/ ascii-updates main contrib non-free deb https://pkgmaster.devuan.org/devuan/ ascii-proposed main contrib non-free deb https://pkgmaster.devuan.org/devuan/ ascii-proposed-security main contrib non-free deb https://pkgmaster.devuan.org/merged/ ceres main contrib non-free deb https://pkgmaster.devuan.org/devuan/ experimental main contrib non-free deb https://pkgmaster.devuan.org/merged/ jessie main contrib non-free deb https://pkgmaster.devuan.org/merged/ jessie-backports main contrib non-free deb https://pkgmaster.devuan.org/devuan/ jessie-proposed main contrib non-free deb https://pkgmaster.devuan.org/devuan/ jessie-proposed-backports main contrib non-free deb https://pkgmaster.devuan.org/devuan/ jessie-proposed-security main contrib non-free deb https://pkgmaster.devuan.org/merged/ jessie-proposed-updates main contrib non-free deb https://pkgmaster.devuan.org/merged/ jessie-security main contrib non-free deb https://pkgmaster.devuan.org/merged/ jessie-updates main contrib non-free deb https://pkgmaster.devuan.org/devuan/ sid main contrib non-free deb https://pkgmaster.devuan.org/merged/ stable main contrib non-free deb https://pkgmaster.devuan.org/merged/ stable-backports main contrib non-free deb https://pkgmaster.devuan.org/devuan/ stable-proposed main contrib non-free deb https://pkgmaster.devuan.org/merged/ stable-proposed-updates main contrib non-free deb https://pkgmaster.devuan.org/merged/ stable-security main contrib non-free deb https://pkgmaster.devuan.org/merged/ stable-updates main contrib non-free deb https://pkgmaster.devuan.org/merged/ testing main contrib non-free deb https://pkgmaster.devuan.org/merged/ testing-backports main contrib non-free deb https://pkgmaster.devuan.org/devuan/ testing-proposed main contrib non-free deb https://pkgmaster.devuan.org/merged/ testing-proposed-updates main contrib non-free deb https://pkgmaster.devuan.org/merged/ testing-security main contrib non-free deb https://pkgmaster.devuan.org/merged/ testing-updates main contrib non-free deb https://pkgmaster.devuan.org/merged/ unstable main contrib non-free deb tor://devuanfwojg73k6r.onion/ should be replaced to use the onion address or you could add tor+https://pkg to use tor without onion addresses. After I corrected the merged/devuan confusion on a proposed.. repository the 404 error went away. The incorrect repository before the amprolla3 switch was not producing an error. This is on a really old 32bit machine running jessie, it is unrelated to the issue I talked about a couple of days ago. I hope this helps to end the confusion. I think some of those repositories, like sid, may be empty but that is not a 404 error, or the side that has non-free may be empty. I hope that someone will verify this list is correct before my mistake or misperception spills more panic. PS For https and tor you need apt-transport-https & apt-transport-tor otherwise substitute http from the list, right? PS2 The tor-project repositories are: deb tor://sdscoq7snqtznauu.onion/torproject.org/ stretch main deb tor://sdscoq7snqtznauu.onion/torproject.org/ tor-experimental-0.3.2.x-stretch main or https://deb.torproject.org/torproject.org but you must first import the gpg key___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chris Lamb = Good Maintainer (Was: Debian testing drop redis)
On 10/26/2017 09:36 AM, John Hughes wrote: Frankly it seems that some people have been rather fast to assume bad faith and very few people who commented either knew what they were talking about or made the slightest effort to actually understand what Chris Lamb had done. I opened a pull request with Chris Lamb to discuss reverting his changes to the sysvinit scripts in redis-server and redis-sentinel. We agreed that the functionality is obscure, affected users may be very hard to find, and any users who are affected can be helped with a reasonable amount of effort. I closed my pull request until such time as we discover a user who needs our help. (Note: Chris is willing to help with sysvinit users too.) Having investigated the technical issues, discussed it with a very reasonable maintainer, and come to a reasonable conclusion, I think we can call this good. Sorry for the trouble Chris, and thank you for your hard work and continued support of both the Debian and Devuan communities. Patrick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On 10/24/2017 10:50 AM, Chris Lamb wrote: > Hi -dng, > >> […] > I am the maintainer of Redis in Debian. All I have done is removed some > ill-conceived hooks that were not used by anyone. I have not dropped > sysvinit support and nor do I have any intention to do so. I only ask > politely that you do stop to refering to my work as "vandalism". > > > Regards, > Just for the record, I am not a developer, but if it is true you intend to keep sysvinit, then no one should be angry with you. and also, you should just ignore the noise. if your doing the right thing, just ignore the noise and stay happy. life is way too short to be annoyed at people who may *Never *be happy with you. I will admit, things like this frustrate me too sometimes... the noise aka... But when it comes down to it, state what your doing and if the noise continues, don't bother with them. That's the philosophy I intend to work on myself... so yeah. Thank you by the way for supporting sysvinit. I only wish runit-init was still on the debian repo. or in the devuan repo at least... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Converting srpms to debs
On 26-10-17 20:09, John Crisp wrote: On 26 October 2017 19:45:29 CEST, Vincent Bentleywrote: Have you tried alien? apt-cache show alien No, but I'm not sure that it is a full on solution. it gets you out of a hole for odd packages as far as I remember? And you don't end up with a source package? I need to be able to hack some of the source files due to different file paths, and then build as debs. According to the man page from alien -g, --generate Generate a temporary directory suitable for building a package from, but do not actually create the package. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Converting srpms to debs
If they are Perl scripts you can simple extract the contents, that is, the actual scripts and place them in a dedicated directory. However, you have to consider if your scripts call other scripts which should be in a defined path. That is what I would do avoiding having to deal with .deb conversion. The latter, is not as simple simple as it might appear, as distributions may save different parts of packages in different directories. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Converting srpms to debs
On 26 October 2017 19:45:29 CEST, Vincent Bentleywrote: >Have you tried alien? > >apt-cache show alien > > No, but I'm not sure that it is a full on solution. it gets you out of a hole for odd packages as far as I remember? And you don't end up with a source package? I need to be able to hack some of the source files due to different file paths, and then build as debs. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
Quoting Steve Litt (sl...@troubleshooters.com): > But Chris, please understand, Debian *has* done plenty of sabotage and > vandalism in the past, especially but not exclusively with the ramming > of systemd down everyone's throat, with no committment to continue to > support alternative inits and no committment to keep must-have-systemd > holloween code out of Debian-supplied software. In the opinions of many, > systemd is in itself a continuing sabotage and vandalism of GNU/Linux. [...] I'm sorry, but is Chris Lamb suddenly synonymous with the Debian Project? You now owe Mr. Lamb an immediate and unreserved public apology. Your present diatribe is flat-out inappropriate, as something directed at him. > So thanks for letting us know your position and motives: I won't again > lump you with the rest of the Debian project, and am sorry I did it > the first time. This apology rings a bit hollow since, in effect, you just now did it a second time. Suggestion: You're in a hole. Stop digging. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On Tue, 24 Oct 2017 15:50:26 +0100 Chris Lambwrote: > Hi -dng, > > > […] > > I am the maintainer of Redis in Debian. All I have done is removed > some ill-conceived hooks that were not used by anyone. I have not > dropped sysvinit support and nor do I have any intention to do so. I > only ask politely that you do stop to refering to my work as > "vandalism". Hi Chris, Are you sure everyone agrees that the hooks are ill-conceived, and are you sure *nobody* is using them? If so, then I apologize for mentioning redis earlier in the thread when I said: > If I remember correctly, one reason for > becomig independent was to avoid Debian sabotage like we're appearing > to see now on redis. But Chris, please understand, Debian *has* done plenty of sabotage and vandalism in the past, especially but not exclusively with the ramming of systemd down everyone's throat, with no committment to continue to support alternative inits and no committment to keep must-have-systemd holloween code out of Debian-supplied software. In the opinions of many, systemd is in itself a continuing sabotage and vandalism of GNU/Linux. So just like we need to cut you a little slack, you need to cut us a little slack. Starting with the Kangaroo Court bug 727708 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727708) and proceeding through the last-minute bogus alternative in the General Resolution, Debian has shown malace toward those wanting Linux to remain an OS with interchangeable parts and small, minimally designed inter-component interfaces, and some folks see the Debian project as having no credibility, and defacing the OS as proxies for Poettering and Redhat. Ask around: That opinion isn't Steve Litt's alone. So thanks for letting us know your position and motives: I won't again lump you with the rest of the Debian project, and am sorry I did it the first time. SteveT Steve Litt October 2017 featured book: Rapid Learning for the 21st Century http://www.troubleshooters.com/rl21 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Converting srpms to debs
Have you tried alien? apt-cache show alien On 26/10/17 18:22, John Crisp wrote: > I have a little idea I have been tossing around in brain for ages but I'm > stuck. > > I'm quite used to building rpms but no experience with debs. > > I have some stuff I'd like to experiment with on Devuan but need to convert > the srpms to deb format. > > Most of it is not actually compiled binaries just perl scripts to do > various tasks. > > I'd like to keep as much of the detail from the spec files as possible. > > Does anyone have any advice? > > B. Rgds > John > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > smime.p7s Description: S/MIME Cryptographic Signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Converting srpms to debs
I have a little idea I have been tossing around in brain for ages but I'm stuck. I'm quite used to building rpms but no experience with debs. I have some stuff I'd like to experiment with on Devuan but need to convert the srpms to deb format. Most of it is not actually compiled binaries just perl scripts to do various tasks. I'd like to keep as much of the detail from the spec files as possible. Does anyone have any advice? B. Rgds John -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] OT: Patching De*an based systems at scale
Hi All, I'd like to have a discussion about how to scale patch management on De*an based systems. Right now, my methodology is looping over my servers in a script and saving the output from 'apt list --upgradable'. This seems to be a utility which will display packages needing updates regardless of whether you use apt-get, apt-get dist-upgrade, or apt-get upgrade. Thing is, when I had 20 servers, this method worked quite well. Most of the servers were LAMP stacks. I now host around 60 servers with various software installed, not just Apache and Mysql anymore. The patch list gets complex and involves various software components. I don't always have time to patch right away so I need to plan for potential downtime of the more critical systems and prioritize system patches based on the criticality of the affected software. Knowing why the patch is needed or what was fixed becomes a priority. Are there any utilities out there for making patch management "easier" when dealing with multiple De*an systems? Is there a better way to get information about patch fixes other than digging up the Changelogs from a web browser? Thanks! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On Thu, Oct 26, 2017 at 05:18:30PM +0200, John Hughes wrote: [cut] > >This was not the case, hopefully. :) > ITYM "thankfully". "Hopefully" would imply that you doubted Chris Lamb's > word. > I am not a native English speaker, and I often might misuse adverbs ;) Let's carry on. KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On 26/10/17 17:05, KatolaZ wrote: John, I was among those who tried to calm the storm down. As I noted. It didn't seem to have much effect though. We should all try to be a bit more careful before coming to conclusions. I agree. Unfortunately, we have seen already silly things coming from some Debian developers. If you say so. This was not the case, hopefully. :) ITYM "thankfully". "Hopefully" would imply that you doubted Chris Lamb's word. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On Thu, Oct 26, 2017 at 04:36:18PM +0200, John Hughes wrote: [cut] > > Frankly it seems that some people have been rather fast to assume bad faith > and very few people who commented either knew what they were talking about > or made the slightest effort to actually understand what Chris Lamb had > done. > John, I was among those who tried to calm the storm down. We should all try to be a bit more careful before coming to conclusions. Unfortunately, we have seen already silly things coming from some Debian developers. This was not the case, hopefully. :) HH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On 26/10/17 16:06, KatolaZ wrote: please discard the angry comments. Evidently not everybody had a full understanding of what was going on, before posting them. We repeatedly said that there was no reason to freak out, and that the situation was under control. Thanks for confirming it yourself :) Oh really? 1st message to list with the initial misunderstanding: 2017-10-18 15:46 KatolaZ's message attempting to calm things: 2017-10-19 09:57 Jaromil "This episode is again of great shame on Debian maintainers" **2017-10-19 10:21 Jaromil "Vandalisation" 2017-10-20 10:57 Me "a little more light and a little less heat" 2017-10-20 16:27 Jaromil "it is even worse than I initially thought" 2017-10-22 11:37 Patrick Meade actually makes the effort to see what happened 2017-10-23 15:59 Frankly it seems that some people have been rather fast to assume bad faith and very few people who commented either knew what they were talking about or made the slightest effort to actually understand what Chris Lamb had done. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis
On Tue, Oct 24, 2017 at 03:50:26PM +0100, Chris Lamb wrote: > Hi -dng, > > > […] > > I am the maintainer of Redis in Debian. All I have done is removed some > ill-conceived hooks that were not used by anyone. I have not dropped > sysvinit support and nor do I have any intention to do so. I only ask > politely that you do stop to refering to my work as "vandalism". > Dear Chris, please discard the angry comments. Evidently not everybody had a full understanding of what was going on, before posting them. We repeatedly said that there was no reason to freak out, and that the situation was under control. Thanks for confirming it yourself :) We deeply respect the work of the many committed Debian developers. Their work is fundamental for the entire GNU/Linux ecosystem. HH KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] gpg 2.2.x devuan jessie no TOFU TLS
cannot work this out installed sqlite3 and gnutls available packages and -dev packages anybody confirm a working devuan jessie 2.2.x install and care to explain ? many thank yous -- -- GnuPG v2.2.1 has been configured as follows: Revision: 355ca9e (13660) Platform: GNU/Linux (x86_64-pc-linux-gnu) OpenPGP: yes S/MIME:yes Agent: yes Smartcard: yes (without internal CCID driver) G13: no Dirmngr: yes Gpgtar:yes WKS tools: no Protect tool: (default) LDAP wrapper: (default) Default agent: (default) Default pinentry: /usr/bin/pinentry Default scdaemon: (default) Default dirmngr: (default) Dirmngr auto start: yes Readline support:yes LDAP support:yes TLS support: no TOFU support:no Tor support: yes checking for SQLITE3... no configure: WARNING: *** *** Building without SQLite support - TOFU disabled *** *** *** checking for encfs... /usr/bin/encfs checking for fusermount... /bin/fusermount checking for openpty in -lutil... yes checking for shred... /usr/bin/shred checking for npth-config... /usr/local/bin/npth-config checking for NPTH - version >= 1.2... yes (1.5) checking NPTH API version... okay checking for ntbtls-config... no checking for NTBTLS - version >= 0.1.0... no checking for LIBGNUTLS... no configure: WARNING: *** *** Building without NTBTLS and GNUTLS - no TLS access to keyservers. *** *** ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis non systemd
On 26/10/17 15:55, John Hughes wrote: They are around 89 lines long. Hardly broken compared to most init scripts, check out /etc/init.d/sendmail -- a 1321 line monster in some versions. Duh, hardly "bloated" I meant to say. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Debian testing drop redis non systemd
On 25/10/17 19:51, Steve Litt wrote: How bout this: Have a "runit-supervisor-only" pacakge that installs runit but doesn't make it PID1. Have sysvinit run runit, and have runit run redis, with all the correct config. The runit run script is probably 1/10 the size of its bloatacious and apparently broken sysvinit init script, so it's easy to correctly design the runit run script. As far as I know there is nothing broken about the redis init scripts in Debian. They are around 89 lines long. Hardly broken compared to most init scripts, check out /etc/init.d/sendmail -- a 1321 line monster in some versions. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] many many 404 when upgrading/installing packages
KatolaZ: > On Mon, Oct 23, 2017 at 01:15:08PM +, Fulano Diego Perez wrote: >> >> >> KatolaZ: >>> # apt-get update >>> >>> before trying to install/upgrade packages? One reason why you might >>> have a 404 is that the cache kept by apt is older than the actual >>> version. >> >> dont be sorry. >> >> yes, did the obvious updates .. > > OK. Could you please retry and report which packages give a 404, and > also post the relevant sections of your sources.list? i just went back to default for now... > > Thanks > > KatolaZ > > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] libvirt virt-manager permissions ?
anybody have advice about getting virt-manager working ? what are required perms for qcows ? always get similar errors on any debian distro except subgraph which always works without changing perms, currently 600 root:root i have apparmor installed --- The emulator may not have search permissions for the path '/media/user/.win10ent64.qcow2'. Errors were encountered changing permissions for the following directories: /media/user : [Errno 1] Operation not permitted: '/media/user' Unable to complete install: 'Cannot access storage file '/media/user/..win10ent64.qcow2' (as uid:107, gid:113): Permission denied' Unable to complete install: 'Cannot access storage file '/media/user/..win10ent64.qcow2' (as uid:107, gid:113): Permission denied' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 91, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/create.py", line 1787, in do_install guest.start_install(meter=meter) File "/usr/share/virt-manager/virtinst/guest.py", line 403, in start_install noboot) File "/usr/share/virt-manager/virtinst/guest.py", line 467, in _create_guest dom = self.conn.createLinux(start_xml or final_xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3440, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: Cannot access storage file '/media/user/..win10ent64.qcow2' (as uid:107, gid:113): Permission denied ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Virtualbox?
On 10/25/2017 08:05 AM, Olaf Meeuwissen wrote: > Using the virtualbox package from either jessie (4.3.36-dfsg-1+deb8u1) > or jessie-backports (5.1.8-dfsg-6~bpo8+2) with a stock linux-image-amd64 > (3.16+63) from jessie works fine. That is, it installs without errors > and virtualbox images start fine (based on my provisioning Debian jessie > images and ssh-ing into them). > > Using either virtualbox package with the stock linux-image-amd64 from > jessie-backports (4.9+80~bpo8+1) however does *not* work. Installation > fails with a compile error of the vboxdrv kernel module. It looks like > the kernel API has changed (unsurprisingly when going from a major > version of 3 to 4). Neither virtualbox package seems to deal with this, > not even the one from backports. > > Next move is checking whether things work in ascii because my laptop at > the office doesn't really work with a 3.16 kernel. > Good luck with that. There is no virtualbox package in ascii/stretch. You can get the packages from virtualbox.org, and those will work in ascii. OK, that's weird - there's one in ascii-backports but not in stretch-backports. I don't know what that's about. A few minutes of googling tells me what I already know - it's not in stretch. Maybe someone else knows the right words to search to find out why that is. $ apt-cache policy virtualbox virtualbox: Installed: (none) Candidate: 4.3.36-dfsg-1+deb8u1 Version table: 5.1.30-dfsg-1 0 100 http://pkgmaster.devuan.org/merged/ ceres/contrib amd64 Packages 10 http://debian.csail.mit.edu/debian/ buster/contrib amd64 Packages 10 http://debian.csail.mit.edu/debian/ sid/contrib amd64 Packages 5.1.28-dfsg-1~bpo9+1 0 100 http://pkgmaster.devuan.org/merged/ ascii-backports/contrib amd64 Packages 5.1.8-dfsg-6~bpo8+2 0 200 http://packages.devuan.org/merged/ jessie-backports/contrib amd64 Packages 4.3.36-dfsg-1+deb8u1 0 500 http://auto.mirror.devuan.org/merged/ jessie/contrib amd64 Packages 500 http://auto.mirror.devuan.org/merged/ jessie-security/contrib amd64 Packages ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] UEFI and Secure Boot
On 10/23/2017 09:12 PM, zap wrote: no blobs of any kind with regard to wifi especially! Yes! and of course a an open source firmware with fully open source silicon init. (ex: TALOS 2, KCMA-D8, KGPE-D16, Novena and a few others with the G505S being the most free modern laptop with IOMMU and no black box supervisor processor aka ME/PSP) Other things that would be helpful would of course not use pulseaudio or systemd... . But meh... kind of hard not to use pulseaudio My devuan is pulseaudio free :D (see below) It is also notable that blobs are awful for security I try to do all these things, and also you should use something like librecmc or lede for your router. I like OPNSense on my router - pfsense has became too corporate and they are very caviler when it comes to security (still no gpg sigs for the .iso files, they claim it isn't needed as they have the hashes stored on another sever..using the same software and distro that the first useschrist.) ps, I do most of the things I mentioned... but I do not have a way to remove pulseaudio yet as of now... I use devuan on a HTPC without pulseaudio, it works fine with just ALSA no matter if I use my HDMI sound via the video card or a dedicated sound card (I bought a decent one and it sounds much better) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng