Instalacja Jessie za pomoc

[pinochio]

Czy jest możliwa nowa instalacja wersji testowej za pomocą instalatora buisnesscard wersji stabilnej?
Z tego co czytam, Debian porzucił ponoc obrazy buissnescard http://dug.net.pl/news/434/

Lubię mieć zawsze wersję testową, Wheezy się nie sprawdził z moją kamerką i Netiaspotem i wcześniej najlepiej przeszła instalacja Wheezy własnie przy pomocy instalatora buisnesscard wersji stabilnej. Co proponujecie teraz, jak najlepiej zainstalować od nowa wersję testową Debiana, nie podmianą wpisów w repozytorium?

[Yampress]

Zawsze możesz zainstalować stable a potem aktualizować do testing...

Ściągnij netinstall wersji testing . Troche większy obraz ale możliwość instalacji testing jest

[mati75]

Obrazy businesscard już nie istnieją dla obecnej wersji stabilnej i testowej. Możesz użyć daily build wersji testowej: https://www.debian.org/devel/debian-installer/ i za pomocą tekstowego instalatora zainstalować system. Graficzny nie działa. Już można wykorzystać grml i grml-debootstrap do instalacji.

[ArnVaker]

Zamiast businesscard można użyć netboot, np.: http://ftp.nl.debian.org/debian/dists/s ... s/netboot/

[pinochio]

Próbuję zrobić

Kod: Zaznacz cały

apt-get dist-upgrade

Mam na koniec taki komunikat:

Czytanie list pakietów... Gotowe
W: Nieprawidłowa dystrybucja: http://deb.opera.com testing Release (oczekiwano testing, a otrzymano stable)

Mam nadzieję, że to jest normalne.

[Rafal_F]

Możesz zmienić wpis dot. opery z testing na stable. Opera ostatnio przeszła na chromium i na początku skupia się na dopracowaniu wersji na windows, oraz mac. Nie było wydania na Linuksa już od kilku ładnych miesięcy, ale jest w planach.

[pinochio]

Możesz zmienić wpis dot. opery z testing na stable. Opera ostatnio przeszła na chromium i na początku skupia się na dopracowaniu wersji na windows, oraz mac. Nie było wydania na Linuksa już od kilku ładnych miesięcy, ale jest w planach.

Puściłem w ruch dist-upgrade i poszedłem do kuchni na jakiś czas. Wracam i widzę taki komunikat:

ca-certificates (20130906) unstable; urgency=low

Update mozilla/certdata.txt to version 1.94
Certificates added (+) and removed (-):
+ "CA Disig Root R1"
+ "CA Disig Root R2"
+ "China Internet Network Information Center EV Certificates Root"
+ "D-TRUST Root Class 3 CA 2 2009"
+ "D-TRUST Root Class 3 CA 2 EV 2009"
+ "PSCProcert"
+ "Swisscom Root CA 2"
+ "Swisscom Root EV CA 2"
+ "TURKTRUST Certificate Services Provider Root 2007"
- "Equifax Secure eBusiness CA 2"
- "TC TrustCenter Universal CA III"

-- Michael Shuler <michael@pbandjelly.org> Fri, 06 Sep 2013 11:31:06 -0500

ca-certificates (20130610) unstable; urgency=low

CAcert root and class3 certificates are now installed as individual
files, no longer as the concatenation of the two. The certificates
are installed as cacert.org_root.crt and cacert.org_class3.crt for
ease of identification.

Remove obsolete debconf.org CA.
Remove obsolete SPI CA certificate expired in 2007.

-- Thijs Kinkhorst <thijs@debian.org> Mon, 10 Jun 2013 19:57:05 +0200

cups (1.6.2-10) unstable; urgency=low

From cups 1.6 the default IPP version for requests is 2.0. For remote
connections configured with ServerName in /etc/cups/cups-client.conf,
an older IPP version such as 1.1 or even 1.0 might need to be
explicitly set for printing to keep working. For example:

ServerName remote-print-server.example.com/version=1.1

-- Didier Raboud <odyx@debian.org> Mon, 17 Jun 2013 08:51:44 +0200

curl (7.32.0-1) unstable; urgency=low
From cups 1.6 the default IPP version for requests is 2.0. For remote
connections configured with ServerName in /etc/cups/cups-client.conf,
an older IPP version such as 1.1 or even 1.0 might need to be
explicitly set for printing to keep working. For example:

ServerName remote-print-server.example.com/version=1.1

-- Didier Raboud <odyx@debian.org> Mon, 17 Jun 2013 08:51:44 +0200

curl (7.32.0-1) unstable; urgency=low

From this version the threaded DNS resolver will be used. This allows for
asynchronous DNS queries and also fixes possible issues related to handling
time outs of DNS lookups.

The threaded resolver was chosen instead of the event-based one (which uses
the c-ares library) because c-ares currently lacks somewhat important
features, such as support for the Name Service Switch system.

-- Alessandro Ghedini <ghedo@debian.org> Mon, 12 Aug 2013 11:08:09 +0200

curl (7.28.1-1) experimental; urgency=low

From this version the CURLOPT_SSL_VERIFYHOST option will stop accepting "1"
as a valid value. From the documentation:

> When the value is 1, libcurl will return a failure. It was previously (in
> 7.28.0 and earlier) a debug option of some sorts, but it is no longer
> supported due to frequently leading to programmer mistakes.

-- Alessandro Ghedini <ghedo@debian.org> Mon, 26 Nov 2012 17:46:27 +0100

d-conf (0.14.0-1) experimental; urgency=low

This version of dconf has some internal changes in how applications
communicate with the dconf service. Applications that use the old
dconf library (libdconf0) can still communicate with the new dconf
service, but newly-launched applications using the new dconf library
(libdconf1) will not be able to use the old dconf service, and will
fail to load their configuration.

After upgrading, your old version of the dconf service will still be
running. Restarting your X session is recommended (log out, and log
back in); this will start a new dconf service.

-- Simon McVittie <smcv@debian.org> Wed, 24 Oct 2012 17:26:48 +0100

git (1:1.8.4~rc0-1) experimental; urgency=low

Starting with this version, gitweb and "git daemon" on Debian are
configured to look for repositories under /var/lib/git by default
instead of /var/cache/git. You may want to adjust your inetd,
rsyncd, and web server configuration to use the new base path.

See /usr/share/doc/git/README.Debian for details.

Symlinks are installed during the upgrade to ensure existing
repositories remain accessible. If no local scripts or
configuration depend on /var/cache/git then it is safe to remove
the old directory after replacing these symlinks with their
targets:

mv --backup /var/cache/git/* /var/lib/git/
rmdir /var/cache/git
rm /var/lib/git/*~

-- Jonathan Nieder <jrnieder@gmail.com> Sun, 28 Jul 2013 17:46:05 -0700

git (1:1.8.2~rc0-1) experimental; urgency=low

The default behavior of "git push" when run without specifying any
ref names will change in the upcoming Git 2.0 release.

The previous default behavior was to use "matching" semantics: push
all branches for which there is already a branch of the same name on
the remote end. The new default is "simple" semantics: push the
current branch to a branch of the same name, provided that "git
pull" is configured to integrate with that branch. You can get a
glimpse of the future with

echo '[push] default = simple' >>~/.gitconfig

See Documentation/RelNotes/1.8.2.txt and the entry on push.default
in git-config(1) for details.

-- Jonathan Nieder <jrnieder@gmail.com> Mon, 18 Feb 2013 16:48:53 -0800

git (1:1.8.0-1) experimental; urgency=low

Git's bash completion script is now loaded on the fly when tab
completion is attempted for the 'git' or 'gitk' command. This
change involved moving the completion script. If your ~/.bashrc
previously contained

. /etc/bash_completion.d/git

then it should be corrected to

if [ -e /usr/share/bash-completion/completions/git ]; then
. /usr/share/bash-completion/completions/git
elif [ -e /etc/bash_completion.d/git ]; then
. /etc/bash_completion.d/git
fi

or, better,

. /etc/bash_completion

See /usr/share/doc/bash-completion/README.Debian for details.

-- Jonathan Nieder <jrnieder@gmail.com> Sun, 13 Jan 2013 08:59:42 -0800

libhtml-tree-perl (5.03-1) unstable; urgency=low

[THINGS THAT MAY BREAK YOUR CODE OR TESTS]
* as_HTML no longer indents <textarea>

-- gregor herrmann <gregoa@debian.org> Mon, 07 Oct 2013 21:27:45 +0200

libio-socket-ssl-perl (1.961-1) unstable; urgency=low

Upstream version 1.956 introduced the following major behaviour changes:

* BEHAVIOR CHANGE: make default cipher list more secure, especially
- no longer support MD5 by default (broken)
- no longer support anonymous authentication by default (vulnerable to man in
the middle attacks)
- prefer ECDHE/DHE ciphers and add necessary ECDH curve and DH keys, so that
it uses by default forward secrecy, if underlying Net::SSLeay/openssl
supports it
- move RC4 at the end, e.g. 3DES is preferred (BEAST attack should hopefully
been fixed and now RC4 is considered less safe than 3DES)
- default SSL_honor_cipher_order to 1, e.g. when used as server it tries to
get the best cipher even if client preferes other ciphers
PLEASE NOTE that this might break connections with older, less secure
implementations. In this case revert to 'ALL:!LOW:!EXP:!aNULL' or so.
* BEHAVIOR CHANGE: SSL_cipher_list now gets set on context not SSL object and
thus gets reused if context gets reused. PLEASE NOTE that using
SSL_cipher_list together with SSL_reuse_ctx has no longer effect on the
ciphers of the context.
* rework hostname verification schemes
- BEHAVIOR CHANGE: fix SMTP - now accept wildcards in CN and subjectAltName
- BEHAVIOR CHANGE: fix IMAP, POP3, ACAP, NNTP - now accept wildcards in CN
* BEHAVIOR CHANGE: anywhere wildcards like www* now match only 'www1', 'www2'..
but not 'www'

-- Salvatore Bonaccorso <carnil@debian.org> Wed, 27 Nov 2013 15:34:34 +0100

libio-socket-ssl-perl (1.951-1) experimental; urgency=low

Upstream version 1.951 introduced the following two major behaviour changes:

* ssl_verify_mode now defaults to verify_peer for client.
Until now it used verify_none, but loudly complained since 1.79 about it.
It will not complain any longer, but the connection might probably fail.
Please don't simply disable ssl verification, but instead set SSL_ca_file
etc so that verification succeeds!
* it will now complain if the builtin defaults of certs/my-ca.pem or ca/
for CA and certs/{server,client}-{key,cert}.pem for cert and key are used,
e.g. no certificates are specified explicitly.
In the future these insecure (relative path!) defaults will be removed
and the CA replaced with the system defaults.

-- Salvatore Bonaccorso <carnil@debian.org> Sun, 07 Jul 2013 22:33:29 +0200

libio-socket-ssl-perl (1.88-1) unstable; urgency=low

Upstream version 1.79 introduced the following change: IO::Socket::SSL will
complain if SSL_verify_mode is SSL_VERIFY_NONE for client unless it was
explicity set this way. In the future the default will change to verify the
server certificate and apps, which don't provide the necessary credentials
should fail.

The module will carp with:

*******************************************************************
Using the default of SSL_verify_mode of SSL_VERIFY_NONE for client
is deprecated! Please set SSL_verify_mode to SSL_VERIFY_PEER
together with SSL_ca_file|SSL_ca_path for verification.
If you really don't want to verify the certificate and keep the
connection open to Man-In-The-Middle attacks please set
SSL_verify_mode explicitly to SSL_VERIFY_NONE in your application.
*******************************************************************

-- Salvatore Bonaccorso <carnil@debian.org> Mon, 13 May 2013 21:58:44 +0200

openvpn (2.3~rc1-1) experimental; urgency=low

auth-pam and down-root plugins renamed to:
openvpn-plugin-auth-pam.so
openvpn-plugin-down-root.so

-- Alberto Gonzalez Iniesta <agi@inittab.org> Tue, 06 Nov 2012 13:22:13 +0100

samba (2:4.0.10+dfsg-3) unstable; urgency=low

The SWAT package is no longer available.

Upstream support for SWAT (Samba Web Administration Tool) was removed in
samba 4.1.0. As a result, swat is no longer shipped in the Debian Samba
packages. Unfortunately, there is currently no replacement.

Details why SWAT has been removed upstream can be found on the
samba-technical mailing list:

https://lists.samba.org/archive/samba-t ... 90572.html

-- Ivo De Decker <ivo.dedecker@ugent.be> Tue, 22 Oct 2013 07:52:54 +0200

(q to quit)

No, udało mi się wszystko skopiować.
To chyba jest związane nie tylko z tą operą? Zaryzykuję i zamknę te okno.

[ArnVaker]

To jakieś changelogi po prostu, normalna sprawa przy zainstalowanym pakiecie apt-listchanges.

PS Czemu nie zainstalowałeś od razu testinga?

[pinochio]

Bo nie chciałem ryzykować i nie wiedziałem z czego skorzystać najlepiej. Nie byłem pewny. Teraz wyskoczyło mi niebieskie okienko z potwierdzeniem, czy chcę coś jakiś pakiet zupgradować. Oo, teraz następne okienko i pytanie odnośnie konfiguracji pakietu libc6: i386. Restart services during package upgrades without asking? Proponuje mi no. Co zrobić?

[ArnVaker]

Ja bym się zgodził. Generalnie instalacja testinga na czysto to było jednak lepsze wyjście moim zdaniem. Jeśli wcześniej używałeś businesscard, to mogłeś użyć tego co wyżej podałem, daje takie same możliwości.