Re: How can we change the keyboard layout? (was: what keyboard do you use?)
On Mon, 05 Feb 2024 21:06:30 +0100 hw wrote: > Yes, it's a misunderstanding: How can we change the keyboard layout? I recently dug into this because I am running Debian on a Chromebook, and I wanted to map the Google-key (located next to the A key, where you usually expect Caps-Lock to be) to be a Ctrl, for Emacs-Correctness. I wanted a solution that would also work when I used an external keyboard (which has an actual CapsLock next to the A), and would work both in X and in console mode. The solution I found, which should work when using Wayland as well, was to customize the lowlevel scancode-to-keycode mapping that is managed by udev. You can have different remappings for different keyboard models. This keymapping system is very powerful, but somewhat ideosyncratic, and somewhat poorly documented. And it's an edit-the-configfile system; I'm not aware of any GUI config tools for it. It took me over 2 hours to figure out and set up, after which I had a scrambled pile of notes (in a text file) but not the energy to clean them up. The next time I do it I expect it'll take me about an hour (if the same process still applies) instead of the 15 minutes it would take if I did a proper job of documenting it for myself. Some of the webpages in my notes that I remember being useful are: https://wiki.archlinux.org/title/Keyboard_input https://yulistic.gitlab.io/2017/12/linux-keymapping-with-udev-hwdb/ (including some of the comments that contain more recent info) https://medium.com/@canadaduane/key-remapping-in-linux-2021-edition-47320999d2aa Some somewhat-informative files on my computer were /lib/udev/hwdb.d/60-keyboard.hwdb (comes with udev) /usr/include/linux/input-event-codes.h (comes with linux-libc-dev package) Gotchas include: Some things *must* be in lowercase (keycodes, I think?) Some things *must* be in uppercase (certain hexadecimal stuff?) For best results, triple-check that the case you use is exactly the same as the example/sample config files. If you get this wrong, udev will just ignore the erroneous parts of your config file, (and you might think it just didn't see it) instead of giving an error message.
Re: Running 32 bit apps on 64 bit debian
On Sat, 18 Nov 2023 23:58:55 -0800 Van Snyder wrote: > I'm trying run 32 bit LinuxSusser on 64 bit Debian 12 bookworm. Have you tried running a 32-bit app that was installed via apt/dpkg ? If not, I'd recommend installing a simple 32-bit app. Two things that may happen: * it may cause the package manager to install some other packages that will fix the problem affecting 32-bit LinuxSusser. * after installing the 32-bit app, that doesn't run either, in which case investigating why the fully-debian-supported 32-bit app doesn't work, may be a useful next step. For simplicity's sake, I'd recommend a 32-bit package that you don't already have a 64-bit version installed for, that also has very few dependencies. Some candidates I would suggest are: ftp dc lsdvd I strongly suspect there's at least one of those three that you don't already have installed as a 64-bit package, and all three have relatively few dependencies.
Re: Crossgrade instructions seem broken
There's two approaches I would consider here: If you know exactly which packages you want downloaded, I think you can use "apt-get download" to just download the packages you tell it to, and it will ignore all dependency requirements, and not download any other packages. This would be a partial improvement over using wget. If you want apt to download the packages you ask for and figure out what other packages it should download so that all the dependencies can be satisfied, then you may have to fix your "apt --download-only" invocation. I would try going from > #apt --download-only install dpkg:amd64 tar:amd64 apt:amd64 to something like apt --download-only install dpkg:amd64 tar:amd64 apt:amd64 dpkg:i386- tar:i386- apt:i386- It seems to me that apt is (ignoring the --download-only at this point of the process) assuming that you are asking to install a _second_ instance of dpkg, a _second_ instance of tar, and a second instance of apt, and deciding that that is not possible/allowed. So telling it explicitly to find a solution that involves uninstalling the i386 versions of those packages may allow it to proceed to the "actually do something" part of the process, where it will notice the "--download-only" part, and download the debs for the packages it decided you need to install, and do nothing for the packages it decided you need to uninstall. I'm not 100% sure about all of this, in part because my experience is with "apt-get" instead of "apt".
Re: A hypervisor for a headless server?
On Fri, 2 Jun 2023 02:39:43 + Victor Sudakov wrote: > Please don't just say "kvm". I've tried installing different > combinations of "qemu-kvm", "virt-manager" etc and they all depend on > dozens of GUI tools. I think the problem that you are running into with qemu-kvm is that while the package doesn't "require" GUI tools, they do "recommend" them. If you turn off "install-recommends" in your apt config, you may find that you can install it without the GUI tools. "virt-manager", on the other hand, appears to be fundamentally a GUI tool.
Re: Gtk4 Package Support?
On Thu, 27 May 2021 11:54:36 -0400 Dan Ritter wrote: > libgtk-4-0 is currently in "experimental" which means that it is > both unstable and buggy. You can certainly install it and try it > out, but you shouldn't depend on it just yet. If it goes > smoothly, then it could be in the next stable release, in about > 2 years. > > https://packages.debian.org/experimental/libgtk-4-0 Probably better to use libgtk-4-1, which is based on an upstream-stable release: https://packages.debian.org/experimental/libgtk-4-1 The warnings about depending on experimental packages still apply.
Re: how to keep 2 PCs partially in sync
I've been using Unison (https://packages.debian.org/buster/unison-gtk -- there's also a commandline package) for quite a few years (a decade?) now. It works well.
Re: USB3 Monitors
On Sat, 25 Feb 2017 20:56:39 -0500 Carl Fink wrote: > Does anyone know whether Debian (or the kernel in general, I guess) > supports USB3 monitors? A quick web search finds no mention of it, if As far as I am aware, video-over-USB is "displaylink". Including "displaylink" in your web search may provide results > (I want to do this at least largely to get a > super-low-power-consumption system. USB3 monitors use as little as 5 > watts when in active use and even less in standby.) You may want to consider USB-powered monitors that use a more traditional video connection (such as HDMI). I've been using a GeChic USB-powered HDMI monitor and I've been happy with it. It pulls 2 amps off of USB.
Re: Swift lang in Debian?
On Sat, 25 Feb 2017 13:34:46 -0500 Dale Harris wrote: > I imagine this is being discussed somewhere in the larger Debian > community, but I'm having problems finding anything online, off hand. > Does anyone know if there is there any plans to package Swift language > into Debian? It has been open sourced for a while now, I think it has > a compatible license for Debian. You can install it on Ubuntu, so why > not just package it into Debian? lack of volunteers? The google password is "ITP" (stands for Intent-to-Package): https://bugs.debian.org/788327 P.S. Not _this_(http://swift-lang.org/) swift.
Re: Installing Linux on a Mac Mini without OSX
On Thu, 4 Dec 2014 13:25:37 -0500 Brian Sammon wrote: > I was recently given a Mac Mini (Intel Mid 2007) that had been wiped. ... > Is there a way to install Debian/Linux on this machine that doesn't involve > buying or borrowing (or "borrowing") a copy of OSX? Is it easier to install > linux on a USB disk and run it off of that? As a followup, I got Linux installed on it, but not (quite) Debian. I burned a CD of the Ubuntu Trusty "+mac" image. It booted and installed Linux and Grub successfully on the first try. Some things I noticed: It used version 2.02 of grub, which is newer than that used in the Wheezy I tried. The Ubuntu installer (somewhat strongly) encouraged me to create a "Reserved BIOS boot area" partition. I followed that advice. I wouldn't be surprised to learn that most/all of the features that helped with Trusty are also found in Jessie. Now that I have a bootloader installed, I think I'll have more success installing Debian on it. > Two particular subtasks that I may need to do that seem to require OSX: > 1) "Blessing" a partition Recent versions of GRUB come with a "grub_macbless" command, but I haven't tested it. > 2) Checking what version of firmware it has (some versions have BIOS >compatibility) The Boot CD for rEFInd (http://www.rodsbooks.com/refind/) reported a firmware version number, but it was a very different format from the firmware versions on Apple's site. For upgrading firmware without MacOSX, the "Firmware Restoration CD" might be the thing: http://support.apple.com/en-us/HT201518 This was apparently moot for my Mac Mini, as Apple's website doesn't list any available firmware updates for my model. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141231015651.72f2464fa218ef8963808...@brisammon.fastmail.fm
Re: Installing a bootloader on a Mac Mini without OSX
On Sun, 07 Dec 2014 15:40:33 -0500 Stefan Monnier wrote: > > I've tried the i386 install (v7.7) CD multiple times and I've tried having > > it put GRUB on the MBR and on the partition and neither way resulted > > in a bootable install. > > I think this can be made to work with a bit of twiddling (e.g. using > lilo or grub-legacy, or maybe tweaking of the partition table). > But without knowing any more details than "(not) resulted in a bootable > install", it's hard to tell. The only further details I have is that I didn't see any sign of GRUB on any of the times I rebooted after an install. The word "GRUB" never appeared on the screen, just the folder-with-a-question-mark icon. I suspect I had grub v1 on there for a minute or two, the one time I tried the Lenny amd64 disc. I had the same results there, as well. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141207200604.968df1e672c12c3f1e1ce...@brisammon.fastmail.fm
Re: Installing a bootloader on a Mac Mini without OSX
On Thu, 4 Dec 2014 13:25:37 -0500 Brian Sammon wrote: > Is there a way to install Debian/Linux on this machine that doesn't involve > > buying or borrowing (or "borrowing") a copy of OSX? Is it easier to install > > linux on a USB disk and run it off of that? Status report: I've tried the i386 install (v7.7) CD multiple times and I've tried having it put GRUB on the MBR and on the partition and neither way resulted in a bootable install. The Wheezy 7.7 amd64 install CD doesn't boot at all. Appears to be the same issue as bug #744959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744959 I found a Lenny amd64 install CD, and it boots, but with no better results than the Wheezy i386 install CD. Ubuntu has IntelMac-specific ISOs, I'll probably try one of those soon. > Two particular subtasks that I may need to do that seem to require OSX: > 1) "Blessing" a partition Still learning about this, but it appears that there are non-OSX options > 2) Checking what version of firmware it has (some versions have BIOS >compatibility) I've been playing with a rEFInd (http://www.rodsbooks.com/refind/) boot CD and it has a function for reporting your firmware version. Also, Apple's website doesn't list any firmware updates for my 2007 Mac Mini, so this is a moot point in my case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141207140942.810e188560016296c78f1...@brisammon.fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Fri, 05 Dec 2014 14:51:11 + Steve McIntyre wrote: > Hi Brian, > > You might be in luck - I'm looking into installer stuff right now and > I've literally just got an Intel Mac Mini like yours last night to > play with. To the best of my knowledge, the Mac Mini you've got *is* > EFI capable, but doesn't work in quite the way we'd normally expect. > > To confirm that, could you try the wheezy installer CD again for me > please? It hasn't come up yet in this thread, but I just noticed that the CD I've been using is labeled (by me) "7.0.0 i386". I should probably get a more recent version. A related question: i386 or amd64? Do you have a recommendation/preference? I don't have any plans to run non-opensource software. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141205105508.bf0ed677b032bdce512d2...@brisammon.fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Thu, 04 Dec 2014 21:39:08 -0800 Jimmy Johnson wrote: > As mentioned earlier, your machine is currently not using EFI. I missed that -- and how do I know that for sure? Is it possible that it's trying to use EFI, but my debian install is trying to do something not-EFI-compatible, and that's why it won't boot? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141205013223.163341bf21dd31af3554f...@brisammon.fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Thu, 04 Dec 2014 20:34:22 -0800 Jimmy Johnson wrote: > Installing to the MBR should fix your booting problems. This brings to mind another question/issue: I need to educate myself on how MBRs work on EFI machines. Questions such as: When it says it's installing Grub to the MBR, is it really installing it to an MBR, or is it installing it to EFI's alternative to an MBR? Any suggested reading? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141205002551.c643b8224d141d944790c...@brisammon.fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Fri, 5 Dec 2014 08:01:48 +0900 Joel Rees wrote: > Can we conclude that you have read this page > > https://wiki.debian.org/MacMiniIntel I have read this page, and I'm hoping to add a "If you don't have OSX" section to it, once I figure out what to add. > and followed appropriate links, such as the elilo link? (Even the PPC I'm not sure which links are appropriate, so it's quite possible that I missed one. I got the impression from the MacMiniIntel page that the elilo approach was a suboptimal one, so I've not looked into it much, as I'm hoping there's a approach that works better (than the MacMiniIntel page suggests the elilo approach would) > link may be useful for background.) > > You will probably have to interpret some things, and not expect an exact > recipe. > > You may also want to ask on the debian boot list. Thanks, I'll look into it. > And, Jerome's kidding around notwithstanding, questions over at > puredarwin are likely to yield useful information, if it takes going > that far. Yeah, that's on the todo list. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141204184119.5ca9c34edfc8071363251...@brisammon.fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Thu, 04 Dec 2014 14:46:09 -0500 Stefan Monnier wrote: > > I was recently given a Mac Mini (Intel Mid 2007) that had been wiped. > > I tried to install Debian (Wheezy) on it, and the installer reported > > success, but when it came time to eject and reboot, Debian didn't > > boot from the hard drive. > [...] > > Is there a way to install Debian/Linux on this machine that doesn't involve > > buying or borrowing (or "borrowing") a copy of OSX? > > If you managed to boot a plain-normal Debian CDROM installer, then your > machine's firmware has full BIOS support and you can boot a plain-normal > Debian install on the harddisk as well, as if the machine were > a normal PC. Hmm... I was able to boot a plain-normal (I assume it is) Debian CDROM installer, but now I can't boot the plain-normal (I assume) Debian install that the installer said it installed. The two questions I have: Can I still assume that I have the firmware version that I want? What do I do next to troubleshoot/fix this? Another random question: The installer gave me the choice of installing Grub on the partition or on the Master Boot Record. Which of these should I choose? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141204162907.0de983753677069650c9d...@brisammon.fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Thu, 04 Dec 2014 19:46:22 +0100 Jerome BENOIT wrote: > > Two particular subtasks that I may need to do that seem to require > > OSX: 1) "Blessing" a partition 2) Checking what version of firmware > > it has (some versions have BIOS compatibility) > > > > Any pointers/suggestions? > > I will look towards a grub issue, specially if your partition is a gpt > partition table. > For a gpt partition table, you must have a `bios grub' partition. > > > I'm also looking into PureDarwin as a possible solution. > > > Debian is definitely better, do not trust the folks on the PureDarwin forums. Ouch. I have not seen any extravagant claims on behalf of PureDarwin. Mostly just apologetic caveats that it's not quite yet ready for primetime. In any case my interest in PureDarwin was primarily that it might have a "bless" command and/or a way to query the firmware version. However, other messages in this thread suggest that neither of those two things are completely necessary. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141204152621.6c99683101a49b2c142ea...@fastmail.fm
Re: Installing Linux on a Mac Mini without OSX
On Thu, 04 Dec 2014 19:46:22 +0100 Jerome BENOIT wrote: > > Two particular subtasks that I may need to do that seem to require > > OSX: 1) "Blessing" a partition 2) Checking what version of firmware > > it has (some versions have BIOS compatibility) > > > > Any pointers/suggestions? > > I will look towards a grub issue, specially if your partition is a gpt > partition table. > For a gpt partition table, you must have a `bios grub' partition. > > > I'm also looking into PureDarwin as a possible solution. > > > Debian is definitely better, do not trust the folks on the PureDarwin forums. Ouch. I have not seen any extravagant claims on behalf of PureDarwin. Mostly just apologetic caveats that it's not quite yet ready for primetime. In any case, my interest in PureDarwin was primarily that it might have a "bless" command and/or a way to query the firmware version. Other messages in this thread suggest that neither of these two things may be fully necessary. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141204153052.1875257a804ff0c298980...@brisammon.fastmail.fm
Installing Linux on a Mac Mini without OSX
I was recently given a Mac Mini (Intel Mid 2007) that had been wiped. I tried to install Debian (Wheezy) on it, and the installer reported success, but when it came time to eject and reboot, Debian didn't boot from the hard drive. Googling finds me various pages about installing Linux where one of the steps is something like "Boot into OSX" Is there a way to install Debian/Linux on this machine that doesn't involve buying or borrowing (or "borrowing") a copy of OSX? Is it easier to install linux on a USB disk and run it off of that? Two particular subtasks that I may need to do that seem to require OSX: 1) "Blessing" a partition 2) Checking what version of firmware it has (some versions have BIOS compatibility) Any pointers/suggestions? I'm also looking into PureDarwin as a possible solution. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141204132537.c44457fee702caa9b3bac...@brisammon.fastmail.fm
Re: building .debs with "+b1" on the end
On Mon, 07 Jul 2014 21:08:32 +0200 Sven Joachim wrote: > On 2014-07-07 20:51 +0200, Brian Sammon wrote: > > > So I would have to install/learn "sbuild". > > If you just want to rebuild packages locally, this is not really > necessary. Are you saying there's another way to do what I want to do? Or are you saying that the thing I think I want to do is maybe not really what I want to do? > Why do you want to rebuild the packages in the first place, and do you > want your local packages to be replaced by newer versions in the > archive? Well...the problem that I was trying to solve that prompted this question, has morphed into a different problem. If I decide to ask for help with that, I'll start another thread. But I thought this "+b1" technique might be useful in the future. In general, the situation is something like: I have an unsupported (by debian) ARMv7/armhf device with an unsupported (by Debian) kernel on it, and I wanted to run version X of package Foo that I downloaded from archive.debian.org. Later versions of package Foo have new features I don't like. I found a armhf binary of version X, but it wouldn't run, so I thought I'd see if rebuilding it from the source packages would help. It did -- the program runs now, but as it turns out that didn't solve my entire problem. Now my rebuilt version of package Foo -- that seems like exactly the right time to use a "+b1" version numbering trick. If it's not more trouble than it's worth. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140708043044.9763c3e7.debian-users-l...@brisammon.fastmail.fm
Re: building .debs with "+b1" on the end
On Mon, 7 Jul 2014 20:39:06 +0100 Jonathan Dowland wrote: > On Mon, Jul 07, 2014 at 02:51:40PM -0400, Brian Sammon wrote: > > So I would have to install/learn "sbuild". > > sbuild can be used to do it, but you don't need sbuild. I think > dpkg-buildpackage would be sufficient, dpkg-buildpackage definitely doesn't have (at least, I don't see it in the manpage) anything as simple and straightforward as sbuild's "--binNMU" option. But I'd be interested in hearing recipes for doing this with dpkg-buildpackage. > but you'd ideally do it in a chroot of > some sort, which sbuild manages. Another tool to do similar is pbuilder. Are you saying that you recommend I use a chroot? For a package I'm building just for myself (for just one machine)? Hmm... I've never set up a chroot for building packages and it seems like this would be a lot of work, and a lot of disk space (my HDs are small by todays standards) for very little benefit (in my situation). If it turns out there's more than one way to do this, I think I'd probably prefer a method that doesn't require a chroot. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140708041548.e7c0db2d.debian-users-l...@brisammon.fastmail.fm
Re: building .debs with "+b1" on the end
On Mon, 7 Jul 2014 15:55:22 +0100 Jonathan Dowland wrote: > Packages in the archive with a "+bN" version suffix, such as "+b1", have be > 'binNMUd': essentially rebuilt without any source changes because the > environment has changed (such as a version bump of a library dependency). Ah! Thank you! "binNMU" is the magic word. Found the following in google: https://wiki.debian.org/binNMU http://manpages.ubuntu.com/manpages/precise/man1/sbuild.1.html So I would have to install/learn "sbuild". > In your case it would be worthwhile documenting the fact your package diffe > from the archive anyway; so I'd recommend just adding a new changelog stanz I was wrong, it turns out that binNMUs _do_ (usually) add a changelog entry, but it's a sort of ephemeral entry (e.g. the changelog entry for 2.12-1+b2 won't show in the changelog for 2.12-2 because it doesn't go into the source package) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140707145140.2989d838.debian-users-l...@brisammon.fastmail.fm
building .debs with "+b1" on the end
I want to re-build a package for personal use, and have a special version number for my custom build. Since I'm not planning on customizing the source or the debian control files, I think the ideal choice is to build a binary package with a suffix like "+b1" or "+local" on the end. An example of this sort of thing is the current wheezy package of "libcrypt-blowfish-perl" (https://packages.debian.org/wheezy/libcrypt-blowfish-perl) As near as I can tell, the 2.12-1+b2 .debs of this package was created after the 2.12-1 .debs, but from the same source code, and without creating an entry in the changelog. How would I do this? I've looked in various places, and I can't find any relevant documentation. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140707013717.19af539c.debian-users-l...@brisammon.fastmail.fm
Re: Getting apt-cdrom to work
On Fri, 29 Nov 2013 21:56:37 -0500 Brian Sammon wrote: > I'm trying to get apt to install packages from a Debian 7.0.0 CD (just > disc 1) I made a while ago. So, it turns out that was apt was looking in varying places for the CD mount point. Sometimes it was looking in /media/apt, and sometimes it was looking in /media/cdrom . If the CD wasn't mounted when I did the apt-get, it would get mounted on /media/apt. running apt with -o Debug::Acquire::cdrom="true" caused it to tell me where it was looking for the CD-ROM. I made /media/cdrom be a symlink to /media/apt and the problem went away. This is probably not the best solution, but I only needed it to work for a day. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131203193526.60345a43.bsam...@fastmail.fm
Re: Getting apt-cdrom to work
On Fri, 29 Nov 2013 21:56:37 -0500 Brian Sammon wrote: > I'm trying to get apt to install packages from a Debian 7.0.0 CD (just > disc 1) I made a while ago. So, it turns out that was apt was looking in varying places for the CD mount point. Sometimes it was looking in /media/apt, and sometimes it was looking in /media/cdrom . If the CD wasn't mounted when I did the apt-get, it would get mounted on /media/apt. running apt with -o Debug::Acquire::cdrom="true" caused it to tell me where it was looking for the CD-ROM. I made /media/cdrom be a symlink to /media/apt and the problem went away. This is probably not the best solution, but I only needed it to work for a day. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131203193625.167e1c9f.debian-users-l...@brisammon.fastmail.fm
Re: Getting apt-cdrom to work
On Sat, 30 Nov 2013 12:49:13 +0200 Andrei POPESCU wrote: > > Could you please post the output of > > apt-cache policy > apt-cache policy acpi # apt-cache policy Package files: 100 /var/lib/dpkg/status release a=now 500 ftp://ftp-nyc.osuosl.org/debian/ squeeze/non-free i386 Packages release v=6.0.8,o=Debian,a=oldstable,n=squeeze,l=Debian,c=non-free origin ftp-nyc.osuosl.org 500 ftp://ftp-nyc.osuosl.org/debian/ squeeze/contrib i386 Packages release v=6.0.8,o=Debian,a=oldstable,n=squeeze,l=Debian,c=contrib origin ftp-nyc.osuosl.org 500 ftp://ftp-nyc.osuosl.org/debian/ squeeze/main i386 Packages release v=6.0.8,o=Debian,a=oldstable,n=squeeze,l=Debian,c=main origin ftp-nyc.osuosl.org 500 http://archive.debian.org/debian-archive/debian/ lenny/main i386 Packages release v=5.0.10,o=Debian,a=oldstable,n=lenny,l=Debian,c=main origin archive.debian.org 500 http://archive.debian.org/debian-archive/debian/ etch/main i386 Packages release v=4.0r9,o=Debian,a=oldstable,n=etch,l=Debian,c=main origin archive.debian.org 500 cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official i386 CD Binary-1 20130504-15:20]/ wheezy/main Translation-en 500 cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official i386 CD Binary-1 20130504-15:20]/ wheezy/main i386 Packages origin Debian GNU/Linux 7.0.0 _Wheezy_ - Official i386 CD Binary-1 20130504-15:20 Pinned packages: # apt-cache policy acpi acpi: Installed: (none) Candidate: 1.6-1 Version table: 1.6-1 0 500 cdrom://[Debian GNU/Linux 7.0.0 _Wheezy_ - Official i386 CD Binary-1 20130504-15:20]/ wheezy/main i386 Packages 1.5-2 0 500 ftp://ftp-nyc.osuosl.org/debian/ squeeze/main i386 Packages 1.1-2 0 500 http://archive.debian.org/debian-archive/debian/ lenny/main i386 Packages 0.09-1 0 500 http://archive.debian.org/debian-archive/debian/ etch/main i386 Packages -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131130171907.613c18e3.bsam...@fastmail.fm
Getting apt-cdrom to work
I'm trying to get apt to install packages from a Debian 7.0.0 CD (just disc 1) I made a while ago. I mounted the CD, ran "apt-cdrom add" and it seemed to work successfully (it added a line to /etc/sources.list). When I run "apt-get update", I get six lines of "Ign cdrom://"... which is worrying, but since I wasn't sure, I continued on. I then tried "apt-get install acpi/wheezy", and it says "E: Release 'wheezy' for 'acpi' was not found". I have verified that there is a deb of acpi on the CD. I get this problem both with apt 0.9.7.9 from wheezy and apt 0.9.12.1 from jessie/testing. What is the next step in troubleshooting this? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131129215637.d1776251.debian-users-l...@brisammon.fastmail.fm
Re: Squeeze X broken on Inspiron 8500--how to report bug
> As I explained in that bug report, it's an incompatibility between the > Squeeze kernel and Lenny userland. Unfortunately, there is no way to > express this in package conflicts to ensure that it does not occur on > partial upgrades. Okay, so I'm clear: You're saying the Lenny xserver-xorg-video-nv is incompatible with the squeeze kernel? The thing that threw me off is that this incompatibility only manifests itself if the squeeze udev is installed. It doesn't occur with lenny udev. Also... the Lenny xserver-xorg-video-nv is similarly incompatible with the lenny-backports kernel, but that's a tangent. Also... if I upgrade xserver-xorg-video-nv to squeeze, then my situation improves to "X refuses to run", and I have to reboot to fix it. I don't think I have a custom kernel/udev/boot configuration. Is this problem going to happen to everyone who tries to run squeeze on an Inspiron 8500? Everyone who tries to run squeeze on a nvidia system? Right now this looks like a "Squeeze doesn't really support the Inspiron 8500" problem. Is the Inspiron 8500 the type of machine that debian would like to support? Granted, it is pretty old. I wouldn't disagree at all with lowering this bug report to "feature request" or reassigning it to a different package, but it seems like the current situation for the Inspiron 8500 (and other nvidia systems?) is sub-optimal, and sub-optimal, to me, means "bug report". PS... I don't have xserver-xorg-video-all or xserver-xorg-video-nouveau installed on the machine. Is that a factor? Am I using the wrong X video driver? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pazri-000113...@thinkpad
Squeeze X broken on Inspiron 8500--how to report bug
I entered a bug that upgrading udev from lenny to unstable breaks X. (It also breaks with the squeeze version of udev ) ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 ) The bug was closed without any changes to the package, or any other package. While I've found a workaround, I'm concerned that this problem means that Squeeze and X will not work out of the box for other people using an Inspiron 8500. What do I do now? Create another bug? Re-open the bug? Is reopening a bug only supposed to be done by debian-developers? Do I appeal to a higher authority within Debian? Am I wrong in thinking that this concern merits a bug report? Also, what package should the bug (new or reopened) be assigned to? I chose udev because it was the udev upgrade that triggered the problem, but maybe udev isn't the best choice. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pa64l-0008tz...@thinkpad
can't find tcpd messages in system logs
According to various tcpd docs (manpage, READMEs) it logs information via syslog. However, when I do 'grep -i tcpd /var/log/*' I see nothing. I have tcpd 7.6.dbs-8 and sysklogd 1.4.1-17 on my machine. I have stripped my /etc/syslogd.conf down to the following single line, (and restarted inetd) and still nothing: *.debug -/var/log/debug I get messages in /var/log/debug from various other programs and daemons, but nothing I can recognize as being from tcpd. What should I be looking for in my log files? Am I looking for the wrong thing, or should I conclude that something is not working right? Or (C), none of the above? Miscellaneous possibly useful details: x86 machine running a mix of Sarge and testing packages, with a few older ones mixed in--Apt does not complain. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
MakeMaker configured to put scripts in /usr/bin/
If I have Makefile.PL as follows: use ExtUtils::MakeMaker; WriteMakefile( NAME => 'MyLib', EXE_FILES => ['MyProg'] ); Then "perl Makefile.PL; make; make install" puts MyProg in /usr/bin/ I was expecting it to be put in /usr/local/bin. It seems that the debian perl package has ExtUtils::MakeMaker built with the default value of INSTALLSCRIPT set to /usr/bin/ instead of /usr/local/bin/ Since MyProg is not part of the debian distribution (and anything built this way would not be) it seems to me the default for INSTALLSCRIPT should be /usr/local/bin/ Is this something I should file as a bug/feature-request, or is it more likely that I am completely misunderstanding things? P.S. Is there a better list for me to be posting this to? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
