Processed: Re: debootstrap: hardcodes mawk as awk provider
Processing commands for cont...@bugs.debian.org: > tags 861343 +patch Bug #861343 [debootstrap] debootstrap: hardcodes mawk as awk provider Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 861343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861343 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#759428: [installation-guide] non-US is no longer existing, so there is also no "export-restricted" software
Hi, Brian Potkin wrote: > > Just committed. Tagging this bug as pending > > +Note that apt will also let you merge > > +main, contrib, and non-free so you can have restricted packages > > +(strictly spoken not belonging to &debian;) as well as packages from > > +&debian-gnu; at the same time. > > I would have "strictly speaking not belonging to...". I cannot recollect > seeing "spoken" used in this context. Ok, fixed. Holger -- Created with Sylpheed 3.5.1 under D E B I A N L I N U X 9 " S T R E T C H " . Registered Linux User #311290 - https://linuxcounter.net/
Bug#615646: [installation-guide] How do I know which CD has the package I need?
Hi, Wouter Verhelst wrote: > On Sun, Jul 29, 2018 at 02:41:44PM -0400, Nicholas D Steeves wrote: > > On Sun, Jul 29, 2018 at 11:59:34AM +0200, Wouter Verhelst wrote: > > > On Sun, Jul 29, 2018 at 07:50:18AM +0200, Holger Wansing wrote: > > > > +Also, keep in mind: if the CDs/DVDs you are using don't contain some > > > > packages > > > > +you need, you can always install that packages afterwards from your > > > > running > > > > +new Debian system (after the installation has finished). If you need > > > > to know, > > > > > > Drop the comma (you do need it in German, but English doesn't need it) > > > > If the subordinate clause precedes the main clause, then the comma is > > mandatory. Likewise, even if "then" is implied, the comma is > > mandatory. That said, a comma separating the subordinate and main > > clause is not mandatory if the subordinate clause follows the main > > clause. /\ > > no comma > > If you need to know, on which CD/DVD to find a specific package, > > visit... /\ /\ > > no comma, because/ > > "on which...package" mandatory comma =/ > > is a propositionalfor the "if...package" > > phrasesubordinate clause > > > > Are prepositional phrases enclosed by commas in German grammar? > > I don't know all the grammatical jargon :-) and my German is old and > rusty, but yes, when translated to German the phrase above would need a > comma after "know". I didn't mean to say it wouldn't need one after > "package"; it does there, which is why I didn't quote that part of the > message. > > In general, German requires a lot more commas than other languages do. I > guess they're more relaxed and can take breaks more often ;-) Me too, I cannot recall the exact grammatical rules, but in German we need the comma at both places. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: block 821053 with 821051
Processing commands for cont...@bugs.debian.org: > block 821053 with 821051 Bug #821053 [grub-installer] UEFI Secure Boot support in d-i build 821053 was not blocked by any bugs. 821053 was blocking: 820036 Added blocking bug(s) of 821053: 821051 > thanks Stopping processing here. Please contact me if you need assistance. -- 821053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#781538: debian-boot: Total trash on reboot of RAID1 partitions
On Mon, 30 Mar 2015 19:08:21 +0100 Chris Bell wrote: > Package: debian-boot > Version: jessie rc1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > >* What led up to the situation? > / was installed on first RAID1 pair of partitions, > 2nd RAID1 pair not used at first, > /srv on 3rd RAID1 pair. > I had a problem during configuration, and attempted to re-boot. > A single-line message appeared > > Recovering Journal. > > Gave up waiting and installed a new / on to the second RAID1 > pair with the first as /oldroot and the third as /srv. > Continued with configuration until forced to shut down. > > On re-boot the same 0ne-line message appeared > > Recovering Journal. > > I waited again, but there was no other message or any mention > of mdadm, so eventually gave up and looked using a knoppix > disk to find around 10 bytes on each of the 6 partitions (3 pairs) > >* What exactly did you do (or not do) that was effective (or > ineffective)? > I did not see any mention of mdadm starting, nor was there any > oportunity to escape (apart from crashing out again) > >* What was the outcome of this action? > Two disks that had been fully tested before use now totally wiped. > All I can do is attempt data recovery using testdisk > >* What outcome did you expect instead? > I expected the system to start mdadm and then boot as usual. > > -- System Information: > Sent from another system! > Pentium 3 used as a moderate resource but reliable residential > mailserver/archiver to run 24/7 > > # -- System Information: > # Debian Release: 7.8 > # APT prefers stable-updates > # APT policy: (500, 'stable-updates'), (500, 'stable') > # Architecture: amd64 (x86_64) > > # Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) > # Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > # Shell: /bin/sh linked to /bin/dash > > >
Processed: Re: Bug#615646: [installation-guide] How do I know which CD has the package I need?
Processing control commands: > tags -1 + pending Bug #615646 [installation-guide] Stupid Q: How do I know which CD has the package I need? Added tag(s) pending. -- 615646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#615646: [installation-guide] How do I know which CD has the package I need?
Control: tags -1 + pending Holger Wansing wrote: > diff --git a/en/install-methods/official-cdrom.xml > b/en/install-methods/official-cdrom.xml > index 512011690..858b018fa 100644 > --- a/en/install-methods/official-cdrom.xml > +++ b/en/install-methods/official-cdrom.xml > @@ -30,6 +30,14 @@ the installation to download the remaining files or > additional CDs. > > > > +Also, keep in mind: if the CDs/DVDs you are using don't contain some packages > +you need, you can always install that packages afterwards from your running > +new Debian system (after the installation has finished). If you need to know, > +on which CD/DVD to find a specific package, visit > + url="https://cdimage-search.debian.org/";>https://cdimage-search.debian.org/. > + > + > + > If your machine doesn't support CD booting (only relevant > on very old PC systems), but you do have a CD set, > you can use an alternative strategy such as I have committed this, with Wouter's and Brian's additional fixes. Tagging this bug as pending. -- Created with Sylpheed 3.5.1 under D E B I A N L I N U X 9 " S T R E T C H " . Registered Linux User #311290 - https://linuxcounter.net/
Bug#858159: [installation-guide] Memory requirements for installing Stretch have increased since Jessie
Hi, John Paul Adrian Glaubitz wrote: > On 07/28/2018 08:02 PM, Holger Wansing wrote: > > Currently we have in the guide for buster: > > > > Install Type| RAM (minimum) | RAM (recommended) | Hard Drive > > No desktop | 128 megabytes | 512 megabytes | 2 gigabytes > > With desktop| 256 megabytes | 1 gigabyte| 10 gigabytes > > 128 MiB still work fine for me without a desktop, even on slow machines: Ok, so we could leave the "No desktop" section as is. Since desktop environments like Gnome and KDE still move forward and add new features, it seems likely to me, that memory requirements could change over 4 years. In Jessie and Stretch, we have With desktop| 256 megabytes | 1 gigabyte| 10 gigabytes What do people think about doubling the minimum value from 256 to 512 megabytes at least? (Since Gnome is the default desktop, we should choose values here, that will work almost for Gnome. Orienting on LXDE or Xfce is probably not the right thing ...) Holger > root@elgar:~> cat /proc/cpuinfo > CPU:68060 > MMU:68060 > FPU:68060 > Clocking: 49.1MHz > BogoMips: 98.20 > Calibration:491008 loops > root@elgar:~> free -h > totalusedfree shared buff/cache > available > Mem: 114Mi21Mi 7.0Mi 1.0Mi85Mi > 86Mi > Swap: 953Mi 2.0Mi 951Mi > root@elgar:~> cat /etc/os-release > PRETTY_NAME="Debian GNU/Linux buster/sid" > NAME="Debian GNU/Linux" > ID=debian > HOME_URL="https://www.debian.org/"; > SUPPORT_URL="https://www.debian.org/support"; > BUG_REPORT_URL="https://bugs.debian.org/"; > root@elgar:~> > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > -- Created with Sylpheed 3.5.1 under D E B I A N L I N U X 9 " S T R E T C H " . Registered Linux User #311290 - https://linuxcounter.net/
Processed: Re: Bug#756859: installation-guide: USB boot
Processing control commands: > tags -1 + pending Bug #756859 [installation-guide] Fw: installation-guide: USB boot Added tag(s) pending. -- 756859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#756859: installation-guide: USB boot
Control: tags -1 + pending > On Tue, 2018-07-31 at 10:40 +0200, Holger Wansing wrote: > > diff --git a/en/howto/installation-howto.xml > > b/en/howto/installation-howto.xml > > index ff8a74184..f2afb5c3b 100644 > > --- a/en/howto/installation-howto.xml > > +++ b/en/howto/installation-howto.xml > > @@ -162,8 +162,9 @@ sticks. For details, see > />. > > > > > > Some BIOSes can boot USB storage directly, and some cannot. You may need to > > -configure your BIOS to boot from a removable drive or even a > > -USB-ZIP to get it to boot from the USB device. For helpful > > +configure your BIOS to enable USB legacy support. The boot > > device > > +selection menu should show removable drive or > > USB-HDD > > +to get it to boot from the USB device. For helpful > > hints and details, see . > > > > > > > > diff --git a/en/preparing/bios-setup/i386.xml > > b/en/preparing/bios-setup/i386.xml > > index 4c50c1e2c..73f29271d 100644 > > --- a/en/preparing/bios-setup/i386.xml > > +++ b/en/preparing/bios-setup/i386.xml > > @@ -67,6 +67,7 @@ In particular if you use an isohybrid CD/DVD image on a > > USB stick > > (see ), changing the device type to > > USB CDROM helps on some BIOSes which will not boot from a > > USB stick in > > USB harddisk mode. > > +You may need to configure your BIOS to enable USB legacy > > support. > > > > > > > Just committed. Tagging this bug as pending. -- Created with Sylpheed 3.5.1 under D E B I A N L I N U X 9 " S T R E T C H " . Registered Linux User #311290 - https://linuxcounter.net/
Bug#776313: [installation-guide] Installation manual should warn about the use of LVM partition types
Control: tags -1 + pending Holger Wansing wrote: > diff --git a/en/using-d-i/modules/partman-lvm.xml > b/en/using-d-i/modules/partman-lvm.xml > index 89b32b958..0f320ba21 100644 > --- a/en/using-d-i/modules/partman-lvm.xml > +++ b/en/using-d-i/modules/partman-lvm.xml > @@ -41,7 +41,17 @@ to be used as physical volumes for LVM. This is done in the > Use as: physical volume > for LVM . > > - > + > + > +Be aware: the new LVM setup will destroy all data on all partitions marked > with > +an LVM type code. So, if you already have an LVM on some of your disks, and > +want to install Debian additionally to that machine, the old (already > existing) > +LVM will be wiped out! The same counts for partitions, which are (for any > +reason) misleadingly marked with an LVM type code, but contain something > +different (like an encrypted volume). You need to remove such disks from the > +system, before performing a new LVM setup! > + > + > > When you return to the main partman screen, you will see > a new option Configure the Logical Volume Manager. Just committed. Tagging this bug as pending. -- Created with Sylpheed 3.5.1 under D E B I A N L I N U X 9 " S T R E T C H " . Registered Linux User #311290 - https://linuxcounter.net/
Processed: Re: Bug#776313: [installation-guide] Installation manual should warn about the use of LVM partition types
Processing control commands: > tags -1 + pending Bug #776313 [installation-guide] Installation manual should warn about the use of LVM partition types Added tag(s) pending. -- 776313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#891009: debootstrap: wrongly falls back to https://deb.debian.org when try to create Ubuntu chroot
On Wed, 21 Feb 2018 22:31:02 +0900 Hideki Yamane wrote: > And, https assures only secure *connection*, not integrity of *contents* > as GPG does, so this behavior is not good, IMO. As I said above, what https ensures and gpg does is different, and "if there's no reliable keyring then fallback to https connection" behavior is not good. I suggest to remove this feature from debootstrap, do you have any idea for it? If so, please let me know it and why. -- Hideki Yamane
