POLL: Are you tracking new Mint Repo or "Debian Testing" or?
Forum rules
LMDE 2 has reached end of support as of 1-1-2019
LMDE 2 has reached end of support as of 1-1-2019
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I am now tracking "Latest" after a brief foray with "Stable"
LMDE4
HP Pavilion 500-260ea
8Gb ram
AMD A10 6700 (3.7GHz) 4 core
Nvidia GTX 645
HP Pavilion 500-260ea
8Gb ram
AMD A10 6700 (3.7GHz) 4 core
Nvidia GTX 645
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I have LMDE tracking Debian Unstable here...I'm quite that adventurous
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Tracking "Incoming" but nothing new has shown up for the past 3 days... now I'm worried.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Stable are, IMHO, always worth to care about
And if there is a need any 'latest' app, who knows how to install, then she/he knows...
And if there is a need any 'latest' app, who knows how to install, then she/he knows...
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I voted 'testing' but it is a hybrid. I also use pinning to get some stuff from 'unstable'.
My /etc/apt/preferences is:
$ cat /etc/apt/preferences
Package: *
Pin: release o=linuxmint
Pin-Priority: 700
Package: *
Pin: origin packages.linuxmint.com
Pin-Priority: 700
Package: *
Pin: origin mirror.internode.on.net/pub/linuxmint-packages
Pin-Priority: 700
Package: *
Pin: release a=testing
Pin-Priority: 500
Package: *
Pin: release a=unstable
Pin-Priority: 300
and sources.list is:
$ inxi -r
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://mirror.internode.on.net/pub/linuxmint-packages/ debian main upstream import backport
deb http://mirror.internode.on.net/pub/debian/ testing main contrib non-free
deb http://mirror.internode.on.net/pub/debian-security/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org testing main non-free
deb http://mirror.internode.on.net/pub/debian/ unstable main contrib non-free
deb http://www.debian-multimedia.org unstable main non-free
Active apt sources in file: /etc/apt/sources.list.d/opera.list
deb http://deb.opera.com/opera/ stable non-free #Opera Browser (final releases)
I do all updates (every few days) at command line with:
$ sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
and I stay aware of 'issues' by reading relevant forums and apt-listchanges. I have been doing this since Day 1 release of LMDE as well as on a number of 2011-09 installs. Never had a need for MintUpdate/Incomiing/Latest; never had a breakage that was not readily fixed by waiting a few days or grabbing the odd library/app from 'unstable'. Pinning keeps upgrades aimed at 'testing'; as well as allowing newer apps when needed/wanted. Learn about pinning people!!
Best damn system I have ever run in 20+ years of Linux use.
cheers,
rhodry.
My /etc/apt/preferences is:
$ cat /etc/apt/preferences
Package: *
Pin: release o=linuxmint
Pin-Priority: 700
Package: *
Pin: origin packages.linuxmint.com
Pin-Priority: 700
Package: *
Pin: origin mirror.internode.on.net/pub/linuxmint-packages
Pin-Priority: 700
Package: *
Pin: release a=testing
Pin-Priority: 500
Package: *
Pin: release a=unstable
Pin-Priority: 300
and sources.list is:
$ inxi -r
Repos: Active apt sources in file: /etc/apt/sources.list
deb http://mirror.internode.on.net/pub/linuxmint-packages/ debian main upstream import backport
deb http://mirror.internode.on.net/pub/debian/ testing main contrib non-free
deb http://mirror.internode.on.net/pub/debian-security/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org testing main non-free
deb http://mirror.internode.on.net/pub/debian/ unstable main contrib non-free
deb http://www.debian-multimedia.org unstable main non-free
Active apt sources in file: /etc/apt/sources.list.d/opera.list
deb http://deb.opera.com/opera/ stable non-free #Opera Browser (final releases)
I do all updates (every few days) at command line with:
$ sudo apt update && sudo apt upgrade && sudo apt dist-upgrade
and I stay aware of 'issues' by reading relevant forums and apt-listchanges. I have been doing this since Day 1 release of LMDE as well as on a number of 2011-09 installs. Never had a need for MintUpdate/Incomiing/Latest; never had a breakage that was not readily fixed by waiting a few days or grabbing the odd library/app from 'unstable'. Pinning keeps upgrades aimed at 'testing'; as well as allowing newer apps when needed/wanted. Learn about pinning people!!
Best damn system I have ever run in 20+ years of Linux use.
cheers,
rhodry.
Life isn't about waiting for the storm to pass...
it's about learning to dance in the rain.
it's about learning to dance in the rain.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I'll bet by next year the "latest Mint" will be Debian
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I'm not quite sure which I'll choose. I guess I was using Mint Repo when I installed on a new laptop on a month-long trip. Here was my sources.list:
But I got home and I run several straight Debian systems, testing and stable (and oldstable, I love KDE3) and to keep from using up too much of my capped bandwidth (and wasting too much time) I run approx, an apt proxy on my Lenny server. So I just got home and tried to change my sources.list to point to straight Debian testing as filtered through my approx server:
Now apt-get dist-upgrade wants to do use amounts of changes (everything was current using my old sources.list).
I guess that would give me a straight Debian testing system, for the most part. The package updates seem fairly minor.
So I guess my questions is why is there a difference? Are the Mint repos a tad older and better tested? I would be glad to download less stuff (testing & sid have huge package churn), but on the other hand most of my local systems do use straight TESTING and continuing to use the Mint repos seems like it would oblige me to download everything twice. I like to stay current but not necessarily cutting edge and wheezy has been a fairly major headache the last few months since the post-SQUEEZE thaw. I think for my straight Debian systems I'll keep them pointed to squeeze when it becomes stable.
It looks like a dist-upgrade would remove a few Minty-packages, I guess I could just do an "apt-get update" which would keep everything and only require 877 MB of new packages instead of 1,361 MB. mintupdate seems to think I need about 1GB of updates with my modified approx sources.list.
For now I think I'll do a "apt-get dist-upgrade -d" which will put all the latest Debian testing packages on my approx server (I'll need them when I update my other systems) but won't install them.
Code: Select all
deb http://packages.linuxmint.com/ debian main upstream import
deb http://debian.linuxmint.com/latest testing main contrib non-free
#deb http://security.debian.org/ testing/updates main contrib non-free
deb http://debian.linuxmint.com/latest/security testing/updates main contrib non-free
#deb http://www.debian-multimedia.org testing main non-free
deb http://debian.linuxmint.com/latest/multimedia testing main non-free
Code: Select all
deb http://packages.linuxmint.com/ debian main upstream import
### deb http://debian.linuxmint.com/latest testing main contrib non-free
deb http://lenny:9999/debian/ testing main contrib non-free
#deb http://security.debian.org/ testing/updates main contrib non-free
### deb http://debian.linuxmint.com/latest/security testing/updates main contrib non-free
deb http://lenny:9999/security/ testing/updates main contrib non-free
#deb http://www.debian-multimedia.org testing main non-free
### deb http://debian.linuxmint.com/latest/multimedia testing main non-free
deb http://lenny:9999/multimedia/ testing main non-free
Code: Select all
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
aptdaemon gcc-4.3 libpulse-browse0 mintinstall python-aptdaemon
The following NEW packages will be installed:
colord dnet-common dpkg-ruby fonts-dustin gir1.2-cogl-1.0
gir1.2-coglpango-1.0 icc-profiles lib32tinfo5 libaacplus2 libcamel-1.2-23
libcogl-common libcogl-pango0 libcogl5 libcolord1 libdnet libebackend-1.2-1
libedata-book-1.2-9 libedata-cal-1.2-11 libedataserverui-3.0-0 libfame-0.9-1
libgdata11 libglapi-mesa libgraphite2-2.0.0 libgtkhtml-4.0-0
libgtkhtml-4.0-common libgtkhtml-editor-4.0-0 libgweather-3-0
libhunspell-1.3-0 libimobiledevice2 libio-socket-inet6-perl libjson0
liblcms2-2 libmozjs7d libnetfilter-conntrack3 libnl3 libnm-glib4 libnm-util2
libodbc1 libopenal-data libp11-kit0 libraw2 libroar-compat1 libroar1
libsmokebase3 libsocket6-perl libsonic0 libtinfo5 libunique-3.0-0
libv4lconvert0 libxml-commons-external-java libxml-commons-resolver1.1-java
libxml-sax-base-perl libzthread-2.3-2 ntrack-module-libnl-0 rtkit
ruby-httpclient ruby-kde4 ruby-phonon ruby-plasma ruby-qt4 ruby-qt4-script
ruby-qt4-test ruby-qt4-uitools ruby-qt4-webkit xfce4-notifyd xulrunner-7.0
The following packages have been kept back:
gnome-utils xorg xserver-xorg xserver-xorg-core xserver-xorg-input-evdev
xserver-xorg-input-synaptics xserver-xorg-input-wacom xserver-xorg-video-apm
xserver-xorg-video-ark xserver-xorg-video-ati xserver-xorg-video-chips
xserver-xorg-video-cirrus xserver-xorg-video-fbdev xserver-xorg-video-i128
xserver-xorg-video-i740 xserver-xorg-video-intel xserver-xorg-video-mach64
xserver-xorg-video-mga xserver-xorg-video-neomagic
xserver-xorg-video-nouveau xserver-xorg-video-openchrome
xserver-xorg-video-r128 xserver-xorg-video-radeon
xserver-xorg-video-rendition xserver-xorg-video-s3
xserver-xorg-video-s3virge xserver-xorg-video-savage
xserver-xorg-video-siliconmotion xserver-xorg-video-sis
xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-trident
xserver-xorg-video-tseng xserver-xorg-video-vesa xserver-xorg-video-vmware
xserver-xorg-video-voodoo
The following packages will be upgraded:
acpid alsa-utils amarok amarok-utils apache2 apache2-mpm-prefork
apache2-utils apache2.2-bin apache2.2-common apt apt-utils aqualung ark
audacious-plugins audacity autopoint banshee baobab binfmt-support binutils
blinken bluez btrfs-tools bzip2 ca-certificates calibre calibre-bin cantor
cantor-backend-kalgebra cdrdao cervisia cheese cheese-common chromium
chromium-browser chromium-inspector cifs-utils clementine conky-all
coreutils cpp cpp-4.4 cpp-4.5 cpp-4.6 cron cups cups-bsd cups-client
cups-common cups-pdf cups-ppdc curl cvsservice dash dbus dbus-x11 dcraw
debhelper debianutils deskbar-applet dia dia-gnome dia-libs
dictionaries-common djview-plugin djview4 djvulibre-bin djvulibre-desktop
dmidecode dmsetup dnsmasq-base dpkg dpkg-dev dragonplayer dselect
dvd-slideshow ed empathy espeak espeak-data ethtool evolution-data-server
evolution-data-server-common exiftran exim4 exim4-base exim4-config
exim4-daemon-light exo-utils extlinux fakeroot fancontrol feh ffmpeg
ffmpegthumbs file filelight flac foomatic-db foomatic-db-engine
freespacenotifier fuse fuse-utils g++ g++-4.4 g++-4.6 gcalctool gcc gcc-4.4
gcc-4.4-base gcc-4.5 gcc-4.5-base gcc-4.6 gcc-4.6-base gcj-4.6-base
gcj-4.6-jre-lib gdb gdbserver gdebi gdebi-core gdebi-kde gdm3 geeqie
geeqie-common geeqie-dbg geoclue geoclue-hostip geoclue-localnet
geoclue-manual geoclue-yahoo geoip-database gettext gettext-base ghostscript
ghostscript-cups ghostscript-x giblib1 gimp gimp-data gir1.2-atk-1.0
gir1.2-clutter-1.0 gir1.2-freedesktop gir1.2-gdkpixbuf-2.0 gir1.2-glib-2.0
gir1.2-gtk-2.0 gir1.2-gtk-3.0 gir1.2-json-1.0 gir1.2-pango-1.0 git git-man
gksu glib-networking gnome-dictionary gnome-icon-theme gnome-mag
gnome-mplayer gnome-panel gnome-screenshot gnome-search-tool gnome-session
gnome-session-bin gnome-session-canberra gnome-session-common
gnome-system-log gnome-system-monitor gnome-utils-common gnupg-agent gnupg2
google-gadgets-common google-gadgets-gst google-gadgets-qt gpac gpgsm
grub-common grub-pc grub-pc-bin grub2-common gs-common gstreamer0.10-nice
gtk2-engines-pixbuf gtk2-engines-xfce gvfs gvfs-backends gvfs-bin gvfs-fuse
h264enc handbrake-cli handbrake-gtk hddtemp hpijs htop hugin hugin-data
hugin-tools ia32-libs ia32-libs-gtk iceape iceape-browser iceape-chatzilla
icedove iceweasel ifupdown imagemagick info install-info iso-codes
java-common juk k3b k3b-data k3b-extrathemes k9copy kalgebra kalzium
kanagram kapptemplate kate kbd kbruch kcachegrind kcalc kcharselect
kde-config-cddb kde-window-manager kdebase-runtime kdebase-workspace
kdebase-workspace-bin kdebase-workspace-data
kdebase-workspace-kgreet-plugins kdemultimedia kdemultimedia-kio-plugins
kdesdk-dolphin-plugins kdesdk-kio-plugins kdesdk-misc kdesdk-strigi-plugins
kdeutils kdf kdm keyutils kgeography kgpg khangman khelpcenter4 kig
kinfocenter kipi-plugins kiten klettres klibc-utils klipper kmix kmplot
kmtrace kompare kpartloader kremotecontrol krosspython kscd kstars ksysguard
ksysguardd ktimer ktouch kturtle kuiviewer kwalletmanager kwordquiz leafpad
lib32asound2 lib32asound2-plugins lib32bz2-1.0 lib32gcc1 lib32ncurses5
lib32stdc++6 lib32v4l-0 lib32v4l-dev libaa1 libanyevent-perl
libapache2-mod-php5 libappconfig-perl libapt-pkg-perl libarchive1 libasound2
libasound2-plugins libass4 libatasmart4 libatk1.0-0 libatk1.0-data
libaudiofile0 libavcodec53 libavdevice53 libavfilter2 libavformat53
libavutil51 libbluetooth3 libbluray1 libbrlapi0.5 libburn4 libbz2-1.0
libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev libc6-i386 libcaca0
libcairo-perl libcanberra-gtk-module libcanberra-gtk0 libcanberra-gtk3-0
libcanberra0 libcdio-cdda0 libcdio-paranoia0 libcdio10 libcheese-gtk20
libcheese1 libcln6 libclutter-1.0-0 libclutter-gst-1.0-0
libclutter-gtk-1.0-0 libcluttergesture-0.0.2-0 libcrypt-passwdmd5-perl
libcups2 libcupscgi1 libcupsdriver1 libcupsimage2 libcupsmime1 libcupsppdc1
libcurl3 libcurl3-gnutls libcurses-ui-perl libcv2.1 libcvaux2.1
libdate-manip-perl libdb4.8 libdb5.1 libdbus-1-3 libdbus-glib-1-2
libdbus1.0-cil libdbusmenu-qt2 libdca0 libdevmapper1.02.1 libdjvulibre-text
libdjvulibre21 libdpkg-perl libdpkg-ruby1.8 libdvdnav4 libdvdread4 libebml3
libebook1.2-10 libecal1.2-8 libechonest1.1 libedataserver1.2-14 libedit2
libegroupwise1.2-13 libenchant1c2a libespeak1 libevent-1.4-2 libevolution
libexo-1-0 libexo-common libffi5 libffmpegthumbnailer4 libfile-listing-perl
libflac++6 libflac8 libfluidsynth1 libfreetype6 libfuse2 libgadu3
libgail-3-0 libgail-common libgail18 libgarcon-1-0 libgarcon-common libgcc1
libgcj-bc libgcj-common libgcj12 libgcrypt11 libgdata-common libgdict-1.0-6
libgdk-pixbuf2.0-0 libgee2 libgeoclue0 libgeoip1 libgexiv2-0 libgfortran3
libggadget-1.0-0b libggadget-qt-1.0-0b libgimp2.0 libgirepository-1.0-1
libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglew1.6 libglu1-mesa
libgmp10 libgmpxx4ldbl libgnome-keyring0 libgnome-mag2 libgnome2-0
libgnome2-common libgnomeui-0 libgnomeui-common libgnutls26 libgomp1
libgpac0.4.6 libgpg-error0 libgphoto2-2 libgphoto2-port0 libgpm2
libgpod-common libgpod4 libgs9 libgs9-common libgsf-1-114 libgsf-1-common
libgstfarsight0.10-0 libgtk-3-0 libgtk-3-bin libgtk-3-common
libgtk-vnc-2.0-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop2-7
libgtop2-common libgvnc-1.0-0 libgweather-common libhighgui2.1 libhpmud0
libhsqldb-java libhttpclient-ruby1.8 libijs-0.35 libimlib2
libio-socket-ssl-perl libiptcdata0 libiso9660-7 libisofs6 libjack0
libjs-jquery libjson-glib-1.0-0 libk3b6 libk3b6-extracodecs
libkastencontrollers4 libkastencore4 libkastengui4 libkate1 libkcddb4
libkde4-ruby1.8 libkdecorations4 libkdeeduui4 libkeduvocdocument4
libkephal4abi1 libkeyutils1 libkiten4 libklibc libkscreensaver5 libksgrd4
libksignalplotter4 libkwineffects1abi1 libkworkspace4 liblcms1 liblouis-data
libltdl7 liblvm2app2.2 libmagic1 libmagick++4 libmagickcore4 libmagickwand4
libmarblewidget11 libmediainfo0 libmediastreamer0
libmission-control-plugins0 libmjpegtools-2.0-0 libmlt++3 libmlt-data
libmlt4 libmng1 libmodplug1 libmp4v2-1 libmpc2 libmpfr4 libmusicbrainz4c2a
libmx-1.0-2 libncurses5 libncursesw5 libnet-dbus-perl libnet-ssleay-perl
libnice10 libnm-glib-vpn1 libnotify-bin libnotify4 libnss-mdns libnss3-1d
libntrack-qt4-1 libntrack0 libofa0 liboktetacore4 liboktetagui4
liboktetakastencontrollers4 liboktetakastencore4 liboktetakastengui4
libopenal1 libopenraw1 liborc-0.4-0 libortp8 libpam-modules
libpam-modules-bin libpam-runtime libpam0g libpanel-applet2-0 libpango-perl
libpango1.0-0 libpangomm-1.4-1 libpciaccess0 libpcsclite1 libperl5.12
libphonon4 libpkcs11-helper1 libplasma-geolocation-interface4 libplasma-ruby
libplasma-ruby1.8 libplasmaclock4abi1 libplasmagenericshell4 libplist1
libpolkit-gtk-1-0 libpoppler-glib6 libpoppler-qt4-3 libpoppler13
libpostproc51 libppl-c4 libppl9 libprocesscore4abi1 libprocessui4a libproxy0
libpstoedit0c2a libpulse-mainloop-glib0 libpulse0 libpurple0 libpwl5
libqjson0 libqt3-mt libqt4-ruby1.8 libqtruby4shared2 libquadmath0
libquicktime2 libqxt-core0 libqxt-gui0 libraptor1 librasqal3 librcd0
libreadline5 libreadline6 libregexp-assemble-perl libreoffice
libreoffice-base libreoffice-base-core libreoffice-calc libreoffice-common
libreoffice-core libreoffice-draw libreoffice-emailmerge
libreoffice-filter-mobiledev libreoffice-gnome libreoffice-gtk
libreoffice-impress libreoffice-java-common libreoffice-math
libreoffice-report-builder-bin libreoffice-style-crystal
libreoffice-style-galaxy libreoffice-style-tango libreoffice-writer
librsvg2-2 librsvg2-common libscience4 libscim8c2a libsdl-image1.2
libselinux1 libsensors4 libsepol1 libservlet2.5-java libslang2 libsmbclient
libsmokekdecore4-3 libsmokekdeui4-3 libsmokekfile3 libsmokekhtml3
libsmokekio3 libsmokeknewstuff2-3 libsmokeknewstuff3-3 libsmokekparts3
libsmokektexteditor3 libsmokekutils3 libsmokenepomuk3 libsmokephonon3
libsmokeplasma3 libsmokeqtcore4-3 libsmokeqtdbus4-3 libsmokeqtgui4-3
libsmokeqtnetwork4-3 libsmokeqtopengl4-3 libsmokeqtscript4-3
libsmokeqtsql4-3 libsmokeqtsvg4-3 libsmokeqttest4-3 libsmokeqtuitools4-3
libsmokeqtwebkit4-3 libsmokeqtxml4-3 libsmokesolid3 libsmokesoprano3
libsnmp-base libsnmp15 libsolidcontrol4abi1 libsolidcontrolifaces4abi1
libsox-fmt-alsa libsox-fmt-base libsox1b libssh-4 libssl1.0.0 libstdc++6
libstdc++6-4.4-dev libstdc++6-4.6-dev libstreamanalyzer0 libstreams0
libswscale2 libtalloc2 libtaskmanager4abi1 libtdb1 libthunar-vfs-1-2
libthunarx-2-0 libtiff4 libtorrent-rasterbar6 libtotem-plparser17
libtracker-client-0.10-0 libtracker-sparql-0.10-0 libtumbler-1-0
libupower-glib1 libusb-1.0-0 libv4l-0 libv4l-dev libvcdinfo0 libvdpau1
libvisual-0.4-plugins libvncserver0 libvpx0 libwbclient0 libweather-ion6
libwebkitgtk-1.0-0 libwebkitgtk-1.0-common libwebkitgtk-3.0-0
libwebkitgtk-3.0-common libwildmidi-config libwildmidi1 libwpd-0.9-9
libwpg-0.2-2 libwps-0.2-2 libwxsvg0 libx11-6 libx11-data libx11-dev
libx11-xcb1 libxerces2-java libxerces2-java-gcj libxfce4util-bin
libxfce4util-common libxfce4util4 libxfcegui4-4 libxine1 libxine1-bin
libxine1-console libxine1-ffmpeg libxine1-misc-plugins libxine1-plugins
libxine1-x libxml-libxml-perl libxml-sax-expat-perl libxml-sax-perl
libxml-twig-perl libxml2 libxml2-utils libxmmsclient-glib1 libxmmsclient6
libzen0 linux-headers-3.0.0-1-amd64 linux-headers-3.0.0-1-common
linux-image-3.0.0-1-amd64 linux-libc-dev listen lm-sensors locales
lockfile-progs lokalize lsb-base lsb-core lsb-release lxterminal marble
marble-plugins media-player-info mediainfo mediainfo-gui melt
mesa-common-dev min12xxw miro miro-data mjpegtools moc moc-ffmpeg-plugin
mousetweaks mpg321 mplayerthumbs mtpaint multiarch-support
nautilus-sendto-empathy ncurses-base ncurses-bin ncurses-term
network-manager network-manager-gnome network-manager-openvpn
network-manager-pptp network-manager-pptp-gnome network-manager-vpnc
notification-daemon ntfs-3g obexd-client odbcinst odbcinst1debian2 okteta
openclipart-libreoffice openclipart-png openoffice.org-style-crystal
openshot openshot-doc openssh-client openssh-server openssl orage os-prober
parley perl perl-base perl-modules perlmagick phonon php5 php5-cli
php5-common pidgin plasma-dataengines-workspace plasma-desktop
plasma-netbook plasma-scriptengine-googlegadgets
plasma-scriptengine-javascript plasma-scriptengine-python
plasma-scriptengine-ruby plasma-scriptengine-superkaramba
plasma-scriptengine-webkit plasma-scriptengines
plasma-widget-networkmanagement plasma-widgets-workspace policykit-1-gnome
poppler-data poppler-utils poxml pstoedit psutils pulseaudio
pulseaudio-esound-compat pulseaudio-module-gconf pulseaudio-module-x11
pulseaudio-module-zeroconf pulseaudio-utils python python-aeidon
python-brlapi python-crypto python-dateutil python-decorator python-django
python-egenix-mxdatetime python-egenix-mxtools python-evolution python-eyed3
python-gnomeapplet python-gnomedesktop python-gnomekeyring python-gobject
python-gpod python-gudev python-httplib2 python-kde4 python-libtorrent
python-libxml2 python-mako python-mechanize python-minimal python-mlt3
python-mutagen python-nautilus python-numpy python-openssl python-paramiko
python-parted python-pkg-resources python-pygoocanvas python-pyinotify
python-pymtp python-qt4 python-qt4-dbus python-rsvg python-simplejson
python-sip python-uno python-webob python-wnck python3 python3-minimal
python3.2 python3.2-minimal qshutdown radeontool readline-common ristretto
rocs rsyslog samba samba-common samba-common-bin scribus shotwell
simple-scan smbclient smbfs socat sox ssh sshfs step streamtuner sudo
sun-java6-bin sun-java6-jre sun-java6-plugin sweeper synaptic syslinux
syslinux-common system-tools-backends systemsettings telepathy-gabble
telepathy-mission-control-5 telepathy-salut thunar thunar-data tomboy tor
tor-geoipdb totem totem-mozilla totem-plugins traceroute transcode-utils
tsocks ttf-dustin ttf-kochi-gothic ttf-lyx ttf-opensymbol
ttf-sazanami-gothic ttf-sazanami-mincho tumbler tumbler-common tzdata udisks
umbrello unetbootin unetbootin-translations unixodbc uno-libs3 update-inetd
upower ure usbutils vcdimager videotrans vim vim-common vim-runtime vim-tiny
vinagre whois winbind winetricks wpasupplicant x11-common xfce4
xfce4-battery-plugin xfce4-clipman xfce4-clipman-plugin xfce4-dict
xfce4-fsguard-plugin xfce4-goodies xfce4-indicator-plugin xfce4-session
xfce4-timer-plugin xfce4-utils xfdesktop4 xfdesktop4-data xfsprogs xfwm4
xmms2-core xmms2-plugin-alsa xmms2-plugin-id3v2 xmms2-plugin-mad
xmms2-plugin-vorbis xnest xserver-common xserver-xorg-input-all
xserver-xorg-video-all xul-ext-adblock-plus xul-ext-torbutton yelp
youtube-dl zenity zenity-common zoo
930 upgraded, 66 newly installed, 5 to remove and 36 not upgraded.
Need to get 1,125 MB/1,361 MB of archives.
After this operation, 43.8 MB of additional disk space will be used.
Do you want to continue [Y/n]?
So I guess my questions is why is there a difference? Are the Mint repos a tad older and better tested? I would be glad to download less stuff (testing & sid have huge package churn), but on the other hand most of my local systems do use straight TESTING and continuing to use the Mint repos seems like it would oblige me to download everything twice. I like to stay current but not necessarily cutting edge and wheezy has been a fairly major headache the last few months since the post-SQUEEZE thaw. I think for my straight Debian systems I'll keep them pointed to squeeze when it becomes stable.
It looks like a dist-upgrade would remove a few Minty-packages, I guess I could just do an "apt-get update" which would keep everything and only require 877 MB of new packages instead of 1,361 MB. mintupdate seems to think I need about 1GB of updates with my modified approx sources.list.
For now I think I'll do a "apt-get dist-upgrade -d" which will put all the latest Debian testing packages on my approx server (I'll need them when I update my other systems) but won't install them.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
It looks like a lot of those new Debian packages were already on my approx server, some packages were downloading at 11.8 MB a second instead of my more normal lowly 200-300kb (thank you ATT DSL, "Now with caps for extra tastiness"®©). I haven't updated any testing systems in > 1 month, so the must have been there at least that long. So I guess there is quite a delta between the Mint Repos and the regular Debian testing ones. But I gather my system will continue to work even if I point my sources.list to the standard testing repositories.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
with the sources.list you had (pointing at latest) you were using update-packs and the last one was around end of august, that's why you are seeing that huge difference now pointing the systems to testing again.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
How do I tell?
Here is my /etc/apt/sources.list as set up by the installer. I added the deb-src lines not added by softare-properties
deb http://packages.linuxmint.com/ debian main upstream import
deb-src http://packages.linuxmint.com/ debian main upstream import #Added by software-properties
deb http://debian.linuxmint.com/latest testing main contrib non-free
deb-src http://debian.linuxmint.com/latest testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org testing main non-free
deb-src http://www.debian-multimedia.org testing main non-free
Here is my /etc/apt/sources.list as set up by the installer. I added the deb-src lines not added by softare-properties
deb http://packages.linuxmint.com/ debian main upstream import
deb-src http://packages.linuxmint.com/ debian main upstream import #Added by software-properties
deb http://debian.linuxmint.com/latest testing main contrib non-free
deb-src http://debian.linuxmint.com/latest testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free
deb http://www.debian-multimedia.org testing main non-free
deb-src http://www.debian-multimedia.org testing main non-free
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Thanks for the clarification, zerozero. I think if I only had LMDE sticking to update-packs would be a great idea. less package churn, less breakage. But most of my systems are straight Debian and I'm downloading those packages on to my proxy server anyway (and dealing with the breakage). So I'm now Debian Testing.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I quit incoming repos in favor of sid. My final conclusion is that the new mint repos schema is not working right now -at least for me.
I was folllowing LMDE from it' s very first days running testing with no real problems. Than, i changed to the new incoming repos -for curiosity and cause there was a request for more users to test them. No breakage occured either.
My last "incoming" upgrade, took place last August, the 30th: about 700 mb's of updates. Today, the calnedar points to October, the 29th and so sign for the 4th update pack
I know, Clem has stated clearly that right now, he concentrates in Mint 12. So, i guess that the new package is gonna hit the repos not before the end of November -maybe later. Unfortunately, nothing more specific is announced yet.
I do not want to wait for 3 months or more in order to get a gb (?) of updates. Furthermore, afaik, this delay is not due to LMDE (which is acceptable) but due to something completely different. When i am running a kind of a rolling distro, i want to know a few standard things regarding the frequency of the updates: daily, once a week, once a month? It is not like a "Stable" release when the "release when it is ready" moto works best.
My worst fear is that LMDE is something like a sub-project, not as important for the devs as the main edition.
I am fully aware that Clem has not plenty of time -but that arises an obvious question: why they do not abandon the ubuntu-based or the debian-based Mint? A clarification is needed here.
PS1: some mint users are looking elsewhere for a nice kde distro -and some of them are simply gnome refugees hating the new gnome 3. Mint KDE is not here for them. Bad synchronization.
PS2: please count this post just as a feedback for an ex- "incoming repos" follower
PS3: i am reading easily books written in english but i rarely write anything the english. Take it as an excuse
I was folllowing LMDE from it' s very first days running testing with no real problems. Than, i changed to the new incoming repos -for curiosity and cause there was a request for more users to test them. No breakage occured either.
My last "incoming" upgrade, took place last August, the 30th: about 700 mb's of updates. Today, the calnedar points to October, the 29th and so sign for the 4th update pack
I know, Clem has stated clearly that right now, he concentrates in Mint 12. So, i guess that the new package is gonna hit the repos not before the end of November -maybe later. Unfortunately, nothing more specific is announced yet.
I do not want to wait for 3 months or more in order to get a gb (?) of updates. Furthermore, afaik, this delay is not due to LMDE (which is acceptable) but due to something completely different. When i am running a kind of a rolling distro, i want to know a few standard things regarding the frequency of the updates: daily, once a week, once a month? It is not like a "Stable" release when the "release when it is ready" moto works best.
My worst fear is that LMDE is something like a sub-project, not as important for the devs as the main edition.
I am fully aware that Clem has not plenty of time -but that arises an obvious question: why they do not abandon the ubuntu-based or the debian-based Mint? A clarification is needed here.
PS1: some mint users are looking elsewhere for a nice kde distro -and some of them are simply gnome refugees hating the new gnome 3. Mint KDE is not here for them. Bad synchronization.
PS2: please count this post just as a feedback for an ex- "incoming repos" follower
PS3: i am reading easily books written in english but i rarely write anything the english. Take it as an excuse
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Disclaimer: this is in no way any kind of formal information, just my take in reality;asymmetros wrote:I quit incoming repos in favor of sid. My final conclusion is that the new mint repos schema is not working right now -at least for me.
I was folllowing LMDE from it' s very first days running testing with no real problems. Than, i changed to the new incoming repos -for curiosity and cause there was a request for more users to test them. No breakage occured either.
My last "incoming" upgrade, took place last August, the 30th: about 700 mb's of updates. Today, the calnedar points to October, the 29th and so sign for the 4th update pack
I know, Clem has stated clearly that right now, he concentrates in Mint 12. So, i guess that the new package is gonna hit the repos not before the end of November -maybe later. Unfortunately, nothing more specific is announced yet.
I do not want to wait for 3 months or more in order to get a gb (?) of updates. Furthermore, afaik, this delay is not due to LMDE (which is acceptable) but due to something completely different. When i am running a kind of a rolling distro, i want to know a few standard things regarding the frequency of the updates: daily, once a week, once a month? It is not like a "Stable" release when the "release when it is ready" moto works best.
My worst fear is that LMDE is something like a sub-project, not as important for the devs as the main edition.
I am fully aware that Clem has not plenty of time -but that arises an obvious question: why they do not abandon the ubuntu-based or the debian-based Mint? A clarification is needed here.
PS1: some mint users are looking elsewhere for a nice kde distro -and some of them are simply gnome refugees hating the new gnome 3. Mint KDE is not here for them. Bad synchronization.
PS2: please count this post just as a feedback for an ex- "incoming repos" follower
PS3: i am reading easily books written in english but i rarely write anything the english. Take it as an excuse
I have to agree with some of the points you raise here, specially the frequency of the UP, but:
- sometimes those UP are dependent on upstream issues that Mint has no control off, and we are in such a moment now, the xserver/nvidia mess is not solved, although we can see now a light in the end of the tunel, and on the other hand gnome-shell is just at the doorstep;
- so what could Clem do? release an UP4 now, before the shell, with a broken xserver, or wait until everything settles down?
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Thank you for the reply. You see, the initial plan (and the official announcement) mentioned an update pack per month -and, officially, this has not changed. Of course, this is not a simple task and options must be examined: apart from the nvidia things, some upgrades now in sid/wheezy, demanding the remove of mintinstall, vlc or the installation of nautilus (the latter, not too appropriate for a xfce system )
The ideal plan, i m talking when someone suggests a new upgrading system, is to concentrate on this, to back-up this and to support this -the best he cans. But as you said, gnome-shell is ante portas, not to mention kde and fluxbox editions. (i ve read also -a few days ago- that Clem is interested in mate).
Too many things to be done . That 's why i commented about the abandonment of ubuntu or debian as a base.
Maybe, a good alternative is to change the policy for the incoming repos: release when it' s time, not when is ready. Then, the latter will be the motto for the "latest" Mint, the one recommended to the users (as Debian recommends stable and not testing)
The ideal plan, i m talking when someone suggests a new upgrading system, is to concentrate on this, to back-up this and to support this -the best he cans. But as you said, gnome-shell is ante portas, not to mention kde and fluxbox editions. (i ve read also -a few days ago- that Clem is interested in mate).
Too many things to be done . That 's why i commented about the abandonment of ubuntu or debian as a base.
Maybe, a good alternative is to change the policy for the incoming repos: release when it' s time, not when is ready. Then, the latter will be the motto for the "latest" Mint, the one recommended to the users (as Debian recommends stable and not testing)
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I am tracking Latest and Stable. The Latest install was done at the end of last month. The Stable install is in progress--the computer from which I am posting this now. Actually I had installed the original LMDE 201009 back when it came out, but that one got broken (my fault).
Hey, I don't suppose Clem can track these individual LMDEs like he does with the various flavors of Mint that he puts on the monthly stats on the blog...maybe through updates/upgrades? But then, reading these posts, everyone seems to have a little bit different system...(which, of course, is great when considering choices in Linux). Hmm, looking at the September stats, I don't see a "Repartition of Linux Mint users across releases."
Hey, I don't suppose Clem can track these individual LMDEs like he does with the various flavors of Mint that he puts on the monthly stats on the blog...maybe through updates/upgrades? But then, reading these posts, everyone seems to have a little bit different system...(which, of course, is great when considering choices in Linux). Hmm, looking at the September stats, I don't see a "Repartition of Linux Mint users across releases."
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Mostly I am tracking LMDE Latest on my notebook and LMDE Incoming on my desktop. But sometimes I get impatient and I do one or two updates from Debian testing on my notebook.
As my internet connection at home is really slow, I don't really like those new "update packs". For me, it is more practical to do updates more frequently, but download fewer packages per update than with those "update packs".
Best wishes,
Silberwoelfin
As my internet connection at home is really slow, I don't really like those new "update packs". For me, it is more practical to do updates more frequently, but download fewer packages per update than with those "update packs".
Best wishes,
Silberwoelfin
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
My cousin bricked her XP harddrive this morning. put in a used harddrive and LMDE_Xfce pointing to lastest.
She bricked it so hard for a little while I thought she lost to whole motherboard, the BIOs would even post.
Didn't want to confuse her too much putting in the latest and greatest. And keeps me from having to spend a lot of time with updates.
She bricked it so hard for a little while I thought she lost to whole motherboard, the BIOs would even post.
Didn't want to confuse her too much putting in the latest and greatest. And keeps me from having to spend a lot of time with updates.
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
I've been on Testing since the first .iso of LMDe, but with each kernel change and subsequent updates my system was running slower and slower (old 1.7GHz Celeron, 1.25GB RAM). Finally, I couldn't stand the Gnome 3 being pushed forward, so I reinstalled an old (February?) LMDE image, pointed it to Stable and I'm quite happy with how the thing are now. Fast and snappy. And I can't wonder why isn't there an official Stable iamge for LMDe, since I can't imagine how would it pan out to install latest .iso and try switching to stable?
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Is this why I can't install any decent DVD authoring tools? Synaptic is choked right now? Gunna have to fix that or go back to LM 10. =/
- tdockery97
- Level 14
- Posts: 5058
- Joined: Sun Jan 10, 2010 8:54 am
- Location: Mt. Angel, Oregon
Re: POLL: Are you tracking new Mint Repo or "Debian Testing"
Just re-did my LMDE install with repos pointed to Squeeze. I want to have the Gnome 2 desktop for another 2 years or so.
Mint Cinnamon 20.1