[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How to add backports to Wheezy preseed



Hi,

Thanks for the reply.

I did not change the Release file of my repo, reprepro has copied everything ok it seems:
Origin: Debian Backports
Label: Debian Backports
Suite: wheezy-backports
Version:
Codename: wheezy-backports
Date: Wed, 27 Aug 2014 20:34:42 UTC
Valid-Until: Wed, 03 Sep 2014 20:34:42 UTC
NotAutomatic: yes
ButAutomaticUpgrades: yes
Architectures: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
Components: main contrib non-free
Description: Backports for the Wheezy Distribution

And in the case of "normal install" from USB-stick, there still is no need to use the "-t wheezy-backports" parameter...

Strange, and a bit inconvenient since the network mess up in preseed case.

If you have more tips, please do let me know.
Thanks.


On Thu, Aug 28, 2014 at 5:59 PM, Alexander Wirt <formorer@formorer.de> wrote:
On Thu, 28 Aug 2014, Jani Reunanen wrote:

> Hi,
>
> When I do Wheezy (i386) preseed installation with:
> d-i apt-setup/local2/repository string http://caroline/debian
> wheezy-backports main contrib non-free
> d-i apt-setup/local2/comment string Debian Backports repository
>
> installation goes through ok, but after boot I DONT HAVE network available.
> Something has been installed from the backports repository over
> normal wheezy repository and it's messing up the network stuff.
>
> If I comment out those 2 lines in the preseed, network will be just fine.
>
> Also if I do normal wheezy installation from USB-stick, reboot and then do:
> echo "deb http://caroline/debian wheezy-backports main contrib non-free" >>
> /etc/apt/sources.list
> apt-get update
> apt-get install pepperflashplugin-nonfree
> it will install pepperflashplugin ok.
> should I not always tell which repository use unless is the main one:
> apt-get install -t wheezy-backports pepperflashplugin-nonfree
> or is it so, that when package is found only in one repo, that will be used?
>
> Also there is no pinning set by default though backports instructions say:
> http://backports.debian.org/Instructions/
> "All backports are deactivated by default (i.e. the packages are pinned to
> 100
> by using ButAutomaticUpgrades: yes in the Release files."
> does not look like it since preseed does take stuff from there just fine...
> There is no /etc/apt/preferences.
> Only /etc/apt/preferences.d/ which is empty.
>
> Any ideas, is this a bug or a feature (which I did not understand
> correctly)?
> And if it is a feature, how can I add backports to the preseed so that it
> will
> not take stuff from there automatically, only when I tell by using
> -t wheezy-backports?
>
> Thanks.
>
>
> ps. in the preseed lines "caroline" is my home network reprepro server :)
Did you added the setting "ButAutomaticUpgrades" to your distribution
configuration? I don't know if reprepro copies that when mirroring. You want
to check your Release file:

curl ftp://mirror.netcologne.de/debian/dists/wheezy-backports/Release
2>/dev/null | grep Automatic
NotAutomatic: yes
ButAutomaticUpgrades: yes

You need those two settings to let your repo behave like the backports repo.

Alex




--


- Jani -

Reply to: