Processed: Re: Bug#367515: Bug#749991: debian-installer: Wrong kernel in debian-installer package

2019-11-05 Thread Debian Bug Tracking System
Processing control commands:

> tags 749991 + pending
Bug #749991 [debian-installer] debian-installer: Wrong kernel in 
debian-installer package
Bug #926795 [debian-installer] di-netboot-assistant: Unable to install Debian 
Buster amd64 from d-i n-a at 2019-04-10 generated boot-file
Added tag(s) pending.
Added tag(s) pending.
> tags 367515 + pending
Bug #367515 [anna] kernel ABI mismatch message should tell user to look for an 
updated CD
Added tag(s) pending.

-- 
367515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367515
749991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749991
926795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#367515: Bug#749991: debian-installer: Wrong kernel in debian-installer package

2019-11-05 Thread Debian Bug Tracking System
Processing control commands:

> tags 749991 + pending
Bug #749991 [debian-installer] debian-installer: Wrong kernel in 
debian-installer package
Bug #926795 [debian-installer] di-netboot-assistant: Unable to install Debian 
Buster amd64 from d-i n-a at 2019-04-10 generated boot-file
Ignoring request to alter tags of bug #749991 to the same tags previously set
Ignoring request to alter tags of bug #926795 to the same tags previously set
> tags 367515 + pending
Bug #367515 [anna] kernel ABI mismatch message should tell user to look for an 
updated CD
Ignoring request to alter tags of bug #367515 to the same tags previously set

-- 
367515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367515
749991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749991
926795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#367515: Bug#749991: debian-installer: Wrong kernel in debian-installer package

2019-11-05 Thread Holger Wansing
Control: tags 749991 + pending
Control: tags 367515 + pending


Ben Hutchings  wrote:
> On Tue, 2019-11-05 at 22:17 +0100, Holger Wansing wrote:
> [...]
> > I just noticed that the relevant message currently appears with netinst 
> > image,
> > too (because build badly broken).
> > 
> > So, maybe we should not restrict the above proposed changing to the 
> > "netboot"
> > installation method?
> > (means: skipping the "check if you are using an up-to-date netboot image" 
> > part)
> 
> That seems reasonable.

Ok.

Now committed.

Tagging bugs as pending


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#367515: Bug#749991: debian-installer: Wrong kernel in debian-installer package

2019-11-05 Thread Ben Hutchings
On Tue, 2019-11-05 at 22:17 +0100, Holger Wansing wrote:
[...]
> I just noticed that the relevant message currently appears with netinst image,
> too (because build badly broken).
> 
> So, maybe we should not restrict the above proposed changing to the "netboot"
> installation method?
> (means: skipping the "check if you are using an up-to-date netboot image" 
> part)

That seems reasonable.

Ben.

-- 
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.




signature.asc
Description: This is a digitally signed message part


Bug#944207: d-i netinst image with firmware: should NOT be labeled "Official amd64 NETINST" image

2019-11-05 Thread Holger Wansing
Package: debian-cd
X-Debbugs-CC: debian-boot@lists.debian.org


Discovered with image "firmware-10.1.0-amd64-netinst.iso"
from 
https://cdimage.debian.org/cdimage/unofficial/non-free/images-including-firmware/10.1.0+nonfree/amd64/iso-cd/

That image is labeled 
» Debian GNU/Linux 10.1.0 "Buster - Official amd64 NETINST 20190908-01:08" «

Should be something like
"UNOFFICIAL netinst with firmware" or the like, right?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#609335: marked as done (apt-setup lacks support for loading additional discs after installing from netinst with firmware)

2019-11-05 Thread Debian Bug Tracking System
Your message dated Tue, 5 Nov 2019 22:39:16 +0100
with message-id <20191105223916.a3716c722f349775df4b6...@mailbox.org>
and subject line Bug #609335 apt-setup lacks support for loading additional 
discs after installing from netinst with firmware
has caused the Debian Bug report #609335,
regarding apt-setup lacks support for loading additional discs after installing 
from netinst with firmware
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
609335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-setup
Version: 1:0.52
Severity: normal

Since there was no reaction to 
http://lists.debian.org/debian-boot/2010/12/msg00562.html , I am filing
bugs so the issues can be fixed eventually.

Steve McIntyre wrote:
> I was assuming (and said) that you'd be able to use these firmware
> netinsts simply for bootup, then move on to use a full media set to
> install the rest of the system. Unfortunately, that's not the case as
> it's a netinst CD and so will contain not_complete in .disk/cd_type. I
> can hack things in debian-cd to make this work, but there's all kinds
> of assumptions in apt-setup about media types and I don't want to
> break them.
[...]
> It would be nice to have some discussion about what's expected/desired
> from the cd_type, and let's see if we can make it more generic. Should
> I have an extra flag file (".disc/non_free_firmware") that we can add
> code to detect here, or is that redundant?

-- 
see shy jo


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1:0.123


Since commit 4a2145d3, apt-setup supports scanning additional media also when
installing from netinst-with-firmware image.


So closing this bug

Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---


Bug #609335 apt-setup lacks support for loading additional discs after installing from netinst with firmware

2019-11-05 Thread Holger Wansing
Version: 1:0.123


Since commit 4a2145d3, apt-setup supports scanning additional media also when
installing from netinst-with-firmware image.


So closing this bug

Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#367515: Bug#749991: debian-installer: Wrong kernel in debian-installer package

2019-11-05 Thread Holger Wansing
Hi,

Holger Wansing  wrote:
> That looks reasonable.
> I have prepared a proposal for this:
> 
> 
>  snip ===
> 
> diff --git a/debian/anna.templates b/debian/anna.templates
> index 66677ee..3709584 100644
> --- a/debian/anna.templates
> +++ b/debian/anna.templates
> @@ -66,14 +66,14 @@ Template: anna/no_kernel_modules
>  Type: boolean
>  Default: false
>  # :sl2:
> -_Description: Continue the install without loading kernel modules?
> +_Description: No kernel modules found
>   No kernel modules were found. This probably is due to a mismatch between
>   the kernel used by this version of the installer and the kernel version
>   available in the archive.
>   .
> - If you're installing from a mirror, you can work around this problem by
> - choosing to install a different version of Debian. The install will probably
> - fail to work if you continue without kernel modules.
> + You should make sure that your installation image is current (check if you
> + are using an up-to-date netboot image), or - if that's the case - try a
> + different mirror, preferably deb.debian.org.
>  
>  Template: anna/retriever
>  Type: string

I just noticed that the relevant message currently appears with netinst image,
too (because build badly broken).

So, maybe we should not restrict the above proposed changing to the "netboot"
installation method?
(means: skipping the "check if you are using an up-to-date netboot image" part)


Holger
-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug #712907: grub-installer: No longer installs automatically on a normal machine with one hard drive

2019-11-05 Thread Holger Wansing
Version: 1.103


Guido Günther  (13 Aug 2015):
> On Wed, Apr 01, 2015 at 07:54:52PM +0200, Cyril Brulebois wrote:
> > Hi,
> > 
> > and sorry for the lag.
> > 
> > Sam McLeod  (2015-03-07):
> > > Thanks Cyril, I did indeed miss that, that's great - I'll test it today.
> > > 
> > > It looks like the example pressed hasn't been updated to include this
> > > feature: https://www.debian.org/releases/jessie/example-preseed.txt
> > 
> > This seems to be fixed by:
> > 
> >  69619  sthibault # Due notably to potential USB sticks, the location of 
> > the MBR can not be
> >  69619  sthibault # determined safely in general, so this needs to be 
> > specified:
> >  69619  sthibault #d-i grub-installer/bootdev  string /dev/sda
> >  69619  sthibault # To install to the first device (assuming it is not a 
> > USB stick):
> >  69619  sthibault #d-i grub-installer/bootdev  string default
> 
> Just wanted to confirm that adding:
> 
> d-i grub-installer/bootdev  string default
> 
> to the preseed.cfg file Petter mentioned in the very beginning of this
> thread[1] makes the Jessie install succeed without prompts for me in a
> kvm virt-install installation so it indeed looks fixed.
> 
> Cheers,
>  -- Guido


Fixed in grub-installer 1.103

Closing this bugreport (a forgotten one from 2015)


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#907970: Bug #907970: Please stop using debiandoc-sgml (deprecated)

2019-11-05 Thread Holger Wansing
Control: tags -1 + pending


Osamu Aoki (4 Sep 2018):
> Package: debian-installer
> Version: 20180610
> Severity: normal
> Tags: patch
> 
> I am in process of dropping debiandoc-sgml.  So please convert
> partman-doc to DocBook XML with attached patch.

Just committed, thanks Osamu.
Tagging this bug as pending.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Processed: Bug #907970: Please stop using debiandoc-sgml (deprecated)

2019-11-05 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + pending
Bug #907970 [debian-installer] Please stop using debiandoc-sgml (deprecated)
Added tag(s) pending.

-- 
907970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: Bug#944189: Needs source-only re-upload to be able to migrate

2019-11-05 Thread Cyril Brulebois
Control: retitle -1 haveged-udeb uninstallable: depends on non-udeb libhavege2

Steve McIntyre  (2019-11-05):
> On Tue, Nov 05, 2019 at 05:24:54PM +0100, Cyril Brulebois wrote:
> >
> >As mentioned on IRC, rebuilding will likely not fix the actual problem,
> >which is the udeb depending on the library. That the migration is
> >prevented because of a missing source-only upload is another topic.
> 
> Ugh, yes. I missed that, seeing what looked like an obvious fix. It
> was, just a fix for a different bug... :-)

Right, adjusting bug title to reflect the actual problem you were
getting and that I'm fixing; it's just been uploaded with a
source-only upload, which should also help transition-wise.

Details are in:
  
https://salsa.debian.org/debian/haveged/commit/2e6b6a581c4db9e5dbfb685cdd20bfd8fcb646c5


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Re: Bug#944189: Needs source-only re-upload to be able to migrate

2019-11-05 Thread Steve McIntyre
On Tue, Nov 05, 2019 at 05:24:54PM +0100, Cyril Brulebois wrote:
>
>As mentioned on IRC, rebuilding will likely not fix the actual problem,
>which is the udeb depending on the library. That the migration is
>prevented because of a missing source-only upload is another topic.

Ugh, yes. I missed that, seeing what looked like an obvious fix. It
was, just a fix for a different bug... :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"When C++ is your hammer, everything looks like a thumb." -- Steven M. Haflich



Re: Bug#944189: Needs source-only re-upload to be able to migrate

2019-11-05 Thread Cyril Brulebois
Hi Steve,

(Spotted because I've been a subscriber of the haveged package since
some upload earlier this year…)

Steve McIntyre  (2019-11-05):
> On Tue, Nov 05, 2019 at 03:39:54PM +, Steve McIntyre wrote:
> >Source: haveged
> >Version: 1.9.8-1
> >Severity: important
> >Tags: d-i
> >
> >Current d-i daily builds are failing because of haveged, e.g. in
> >
> >  
> > https://d-i.debian.org/daily-images/amd64/20191105-00:03/build_cdrom_gtk.log
> >
> >The following packages have unmet dependencies:
> > haveged-udeb : Depends: libhavege2 (>= 1.9.8) but it is not installable
> >E: Unable to correct problems, you have held broken packages.
> >make[2]: *** [Makefile:674: stamps/get_udebs-cdrom_gtk-stamp] Error 100
> >make[1]: *** [Makefile:298: _build] Error 2
> >make: *** [Makefile:292: build_cdrom_gtk] Error 2
> >
> >I'm going to do a no-change source-only upload to unjam this.
> 
> And here's the trivial NMU diff
> 
> diff -Nru haveged-1.9.8/debian/changelog haveged-1.9.8/debian/changelog
> --- haveged-1.9.8/debian/changelog2019-10-16 20:13:07.0 +0100
> +++ haveged-1.9.8/debian/changelog2019-11-05 15:45:28.0 +
> @@ -1,3 +1,12 @@
> +haveged (1.9.8-1+nmu1) unstable; urgency=high
> +
> +  * NMU
> +  * Source-only upload with no changes outside of the changelog to get
> +testing migration working. This is currently blocking d-i daily
> +builds. Closes: #944189
> +
> + -- Steve McIntyre <93...@debian.org>  Tue, 05 Nov 2019 15:45:28 +
> +

As mentioned on IRC, rebuilding will likely not fix the actual problem,
which is the udeb depending on the library. That the migration is
prevented because of a missing source-only upload is another topic.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)<https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Re: daily images not deploying?

2019-11-05 Thread Steve McIntyre
Hi Vincent,

Apologies for the delayed response - I've been ill for most of the
last week and I guess others are busy. :-/

On Tue, Nov 05, 2019 at 01:06:42AM +, McIntyre, Vincent (CASS, Marsfield) 
wrote:
>(Resending to -boot, no response from -cd)
>
>Hello
>
>I was trying to retrieve
>
>http://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/
>
>and got a 404.
>
>Further investigation showed and found there were no images at all in
>
>https://d-i.debian.org/daily-images/amd64/daily/
>
>just log files.
>
>The last directory containing cd-rom/ hdmedia/ and netboot/
>subdirectories is
>https://d-i.debian.org/daily-images/amd64/20191026-00:17/
>
>Sorry if I'm behind the play here but is this expected?
>
>Kind regards
>Vince
>
>PS I now see the build_netboot.log (and others) contains this failure:
>
>  The following packages have unmet dependencies:
>   haveged-udeb : Depends: libhavege2 (>= 1.9.8) but it is not installable
>  E: Unable to correct problems, you have held broken packages.

It's caused by haveged not migrating into testing as expected - see

  https://tracker.debian.org/pkg/haveged 

for more. I've just uploaded an NMU to fix this, so things should
settle shortly I hope.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"The problem with defending the purity of the English language is that
 English is about as pure as a cribhouse whore. We don't just borrow words; on
 occasion, English has pursued other languages down alleyways to beat them
 unconscious and rifle their pockets for new vocabulary."  -- James D. Nicoll