[DNG] lantian problem on ASCII
Dear all,
i want to build on ascii debian installer.
This require module-init-tools, that do no more exist in ascii. It is
replaced with kmod.
Now i want to build kmod from sources,
apt-get source kmod
then debuild -us -uc
bring
Now running lintian...
Could not load /usr/share/lintian/commands/lintian.pm: Could not find
a profile matching "{VENDOR}/main" for vendor devuan at /usr/bin/lintian
line 210.
Compilation failed in require at /usr/bin/lintian line 35.
my sources.list:
deb http://packages.devuan.org/merged/ ascii main contrib non-free
deb-src http://packages.devuan.org/merged/ ascii main contrib non-free
deb http://packages.devuan.org/merged/ ascii-updates main contrib non-free
deb http://packages.devuan.org/merged/ ascii-proposed-updates main
contrib non-free
deb http://packages.devuan.org/merged/ ascii-security main contrib non-free
How can i tell lintian, where to find devuan?
Thank you,
Mike
___
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
On Tue, Oct 24, 2017 at 04:39:53PM -0400, Fungal-net wrote: [cut] > > I did not ask because I wanted to blame anyone, but asked so I can solve a > problem > The above instructions are what they SHOULD be and this is HOW THEY WERE. > Since the keyring was not updated prior to the shift to amprolla3 all the > merged repositories were invalid, and this is where the new keyring was. > Only by switching the merged into devuan was I able to update the key, I just > didn't realize I had to rechange back to merged. But merged were > inaccessible without the key. > > Why not go and delete your /etc/apt/trusted.gpg.d and see if you can install > the keyring from /merged > I couldn't! I could from /devuan! > If that is true then the instructions to switch from Debian/jessie to > Devuan/jessie with onion addresses are invalid. So try not to shove this > under the carpet, yet. > In any case my question was about -ascii and -ceres not about -jessie but I > will have to make the deduction, which has proven many times in the past to > be false. Hi, nobody wants to put anything under the carpet. We have put amprolla3 out for testing because we want any bug and inconsistency to be discovered, and fixed, before it goes live for everyone in Devuan. And we are grateful to anybody helping with this process. There is no point in getting angry or upset: either you provide sufficient information on your problem or it is impossible for us to understand what is wrong. We are not in front of your computer. We don't have access to your config files. We don't know what you have changed. We can't run commands on your machine. We must rely on the information you provide in your reports. If this information is incomplete, it's very hard (if not impossible) to understand what's going on. So, please, when you report a problem, try to keep that in mind. Saying "it can't update...I have a lot of 404" or (worse) "it now works without changing anything" is close to useless. Try to put yourself on the other side, and check whether the information you have provided in your emails are sufficient to understand your problem *if you don't have access to your machine, cannot check any config, and cannot run any command* Devuan's only goal is to make Devuan a rock-solid, dependable universal operating system. That's why we never know when the next release will come out. We have never hidden any problem to Devuan users, and we will never do. HND 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] lantian problem on ASCII
On Wed, Oct 25, 2017 at 09:00:44AM +0200, m_maass wrote: [cut] > my sources.list: > > deb http://packages.devuan.org/merged/ ascii main contrib non-free > deb-src http://packages.devuan.org/merged/ ascii main contrib non-free > deb http://packages.devuan.org/merged/ ascii-updates main contrib non-free > deb http://packages.devuan.org/merged/ ascii-proposed-updates main > contrib non-free > deb http://packages.devuan.org/merged/ ascii-security main contrib non-free > > How can i tell lintian, where to find devuan? > # apt-get install devuan-lintian-profile HND 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] ..proper use of /merged and /devuan, was: Trouble with apt-get upgrade over TOR
On Tue, 24 Oct 2017 21:18:37 +0200, Arnt wrote in message <20171024211837.11a60797@d44>: > On Tue, 24 Oct 2017 18:26:45 +0100, KatolaZ wrote in message > <20171024172645.gy4...@katolaz.homeunix.net>: > > > > > jessie-proposed is under /devuan > > jessie-proposed-updates is under /devuan > > experimental is under /devuan > > ..are you now saying these 3 should be /devuan and NOT /merged? > > > > The rest is under /merges, if I have not missed something. > > > > > I think there is proposed-security as well. > > ..these 4 should be /devuan, the rest should be /merged, AIUI. ..do I understand this above correctly now? -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Error after upgrade debian wheezy to devuan jessie...
Hi, Thomas Besser writes: > [...] > As far as I understand, package libc-bin registers dpkg (?) triggers > scripts which are executed on every update of any package. > > How can I find out, which trigger script of libc-bin causes this error? > There must be a place, where dpkg stores this scripts. But where? The trigger definition for libc-bin is in /var/lib/dpkg/info/libc-bin.triggers On my machine it says $ cat /var/lib/dpkg/info/libc-bin.triggers interest ldconfig I am not sure what exactly this does, but I *guess* it triggers updating of /etc/ld.so.cache by running the ldconfig command in some way. IIRC, the error you posted earlier looked a lot like it came from a piece of Perl code but I have no idea where it would come from. My /sbin/ldconfig is a shell script wrapper that handles triggers via dpkg-trigger, an ELF binary, and passes the buck to /sbin/ldconfig.real, also an ELF binary. Both are unlikely to be directly responsible for the error message you posted. # Running Devuan jessie, BTW. I know it doesn't answer your question completely but hope this helps anyway, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ 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
On 10/25/2017 05:44 AM, Arnt Karlsen wrote: > On Tue, 24 Oct 2017 21:18:37 +0200, Arnt wrote in message > <20171024211837.11a60797@d44>: > >> On Tue, 24 Oct 2017 18:26:45 +0100, KatolaZ wrote in message >> <20171024172645.gy4...@katolaz.homeunix.net>: >> >>> >>> jessie-proposed is under /devuan >>> jessie-proposed-updates is under /devuan >>> experimental is under /devuan >> >> ..are you now saying these 3 should be /devuan and NOT /merged? >> >> >>> The rest is under /merges, if I have not missed something. >>> I think there is proposed-security as well. >> >> ..these 4 should be /devuan, the rest should be /merged, AIUI. > > ..do I understand this above correctly now? > 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] Error after upgrade debian wheezy to devuan jessie...
Hi Olaf, Am 25.10.2017 um 12:41 schrieb Olaf Meeuwissen: > Thomas Besser writes: > >> [...] >> As far as I understand, package libc-bin registers dpkg (?) triggers >> scripts which are executed on every update of any package. >> >> How can I find out, which trigger script of libc-bin causes this error? >> There must be a place, where dpkg stores this scripts. But where? > > The trigger definition for libc-bin is in > > /var/lib/dpkg/info/libc-bin.triggers > > On my machine it says > > $ cat /var/lib/dpkg/info/libc-bin.triggers > interest ldconfig > > I am not sure what exactly this does, but I *guess* it triggers updating > of /etc/ld.so.cache by running the ldconfig command in some way. > > IIRC, the error you posted earlier looked a lot like it came from a > piece of Perl code but I have no idea where it would come from. My > /sbin/ldconfig is a shell script wrapper that handles triggers via > dpkg-trigger, an ELF binary, and passes the buck to /sbin/ldconfig.real, > also an ELF binary. Both are unlikely to be directly responsible for > the error message you posted. > > # Running Devuan jessie, BTW. > > I know it doesn't answer your question completely but hope this helps > anyway, Thanks for this information, that's a step forward. I will look into this places... I have created a base image of debian wheezy earlier. I will do an upgrade there now and see if I can reproduce this error there too. Regards Thomas ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Virtualbox?
Hi Ozi, list, Ozi Traveller writes: > Has anyone installed virtualbox from jessie-backports? There is a systemd > dependency, but not sure whether it's functional or just a stub. I don't see where the systemd dependency is. Here's what I get $ apt-cache -t jessie-backports depends virtualbox | grep systemd $ Yup, no hits at all so virtualbox does not have a *direct* dependency on systemd. BTW, this is for an APT cache that was last updated a couple of minutes ago. A for using virtualbox on jessie, I just had occasion to try that out at the office when using vagrant. Here's what I found for the linux-image and virtualbox combinations on jessie w/ and w/o backports. 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. # FTR, my test were done on old, decommissioned laptop where that 3.16 # kernel works like a charm :) Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join ___ 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 Tue, 24 Oct 2017 07:44:51 -0500 Patrick Meade wrote: > However, if they are on Devuan, there is no systemd. And without > restoring the old functionality or providing new functionality, our > answer will be an empty one: "Debian upstream broke it. Sorry." And > our poor system administrator goes away empty handed, and maybe > starts looking for a new distro. 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. This could also be done with daemontools-encore, if there's a good package for it (Debian's package for just plain daemontools really sucked, last time I looked). 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
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, -- ,''`. : :' : Chris Lamb `. `'` 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] UEFI and Secure Boot
On Tue, 2017-10-24 at 09:01 +0200, marc wrote: > Secureboot is designed for them, not for you. You might come > up with a really exotic use case, where it might help you. But > if you look at it carefully enough, it relies on secureboot > redefining root to something weaker than what we want, and > running some complex infrastructure which you are unaware > of behind it. If you want a weak root, run a virtual machine > instead. Not at all. Right now if you install Fedora or Ubuntu you get the protection of secure boot. You already trust them if you are installing their OS, correct? Everyone signs the kernel package at the package manager stage so we can all use untrusted mirrors. So now they also put a signature on a grub-efi package with a key signed by the UEFI CA that embeds their company keys. Now your system validates that GRUB is clean and it checks the kernel hasn't been tampered with before executing either of them, Eventually Debian will begin shipping signed grub-efi and kernel packages. Devuan would have to pay $100 to get a signed grub-efi of its own (with a Devuan kernel signing key embedded) to ship kernels built by them if they don't just pass on the Debian grub and kernel packages unmodified. That is it, one can argue how much security benefit it brings but it is non-zero and requires minimal effort to achieve. I think you have to pay again if your grub-efi package changes but it doesn't seem to churn much. signature.asc Description: This is a digitally signed message part ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] UEFI and Secure Boot
On Mon, 2017-10-23 at 17:06 +0200, Didier Kryn wrote: > I've read previously on this list that secureboot doesn't prevent > booting from a usb key... Or did I misunderstood? Correct, so long as the boot loader on the USB key is signed by a key the system trusts. And you didn't disable booting from USB in the BIOS and slap a password on it to stop people from messing with it. All the basics of locking down a machine for an environment where people might mess with it. signature.asc Description: This is a digitally signed message part ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
