[EN] When was the last update to Siduction?

[der_bud]

... please post *all* sources lists ...

+1 ,  for example I stumble across
 

Code: [Select]

Hit http://packages.siduction.org kde-frameworks InRelease
...
Get:2 http://packages.siduction.org kde-frameworks/main amd64 Packages [327 kB] which is for my understanding not longer valid, or is it? And then those jessie and sarge entries  - probably not easy to fix

[vonh]

I think the problem lay in the http://http.debian.net/debian entry in debian.list. It wasn't responding properly when I entered it into the browser. After visiting the page and selecting one of the mirrors there the list was updated and apt-get -s dist-upgrade > dist-upgrade.txt is over a 1500 lines long.

I have changed the entry in debian.list to httpredir.debian.org

[der_bud]

Over 1500 lines long dist-upgrade.txt sounds like good news , so happy dist-upgrading now (perhaps with some 'apt-get install -f' in between, though).

[vonh]

This is the updated list of reposlitories

debian.list

Code: [Select]

# debian loadbalancer
deb http://httpredir.debian.org/debian/ unstable main contrib non-free
#deb-src http://httpredir.debian.org/debian/ unstable main

mics.list

Code: [Select]

# misc. siduction-lists
#deb http://ftp.spline.de/pub/siduction/experimental unstable main
#deb-src http://ftp.spline.de/pub/siduction/experimental unstable main

#deb http://ftp.spline.de/pub/siduction/user unstable main
#deb-src http://ftp.spline.de/pub/siduction/user unstable main

passenger.list

Code: [Select]

deb https://oss-binaries.phusionpassenger.com/apt/passenger jessie main

siduction.list

Code: [Select]

# official siduction-lists
deb http://ftp.spline.de/pub/siduction/base unstable main
#deb-src http://ftp.spline.de/pub/siduction/base unstable main

deb http://ftp.spline.de/pub/siduction/extra unstable main
#deb-src http://ftp.spline.de/pub/siduction/extra unstable main

deb http://ftp.spline.de/pub/siduction/fixes unstable main
#deb-src http://ftp.spline.de/pub/siduction/fixes unstable main

deb http://packages.siduction.org/kdenext kde-frameworks main

snapshots.list

Code: [Select]

# snapshots.debian.org
# added for subversion 1.9.2 subversion bug #803725
deb http://snapshot.debian.org/archive/debian/20150924T154447Z/ unstable main

ubuntuzilla.list

Code: [Select]

deb http://downloads.sourceforge.net/project/ubuntuzilla/mozilla/apt all main

webmin.list

Code: [Select]

deb http://webmin.mirror.somersettechsolutions.co.uk/repository sarge contrib

x2go.list

Code: [Select]

# X2Go Repository (release builds)
deb http://packages.x2go.org/debian jessie main
# X2Go Repository (sources of release builds)
deb-src http://packages.x2go.org/debian jessie main

# X2Go Repository (nightly builds)
#deb http://packages.x2go.org/debian jessie heuler
# X2Go Repository (sources of nightly builds)
#deb-src http://packages.x2go.org/debian jessie heuler


[holgerw]

Hello,

before gcc5 transition in Sid:
It is recommended to avoid a mix of stable and unstable repo

after gcc5 transition, I guess:
It is strongly recommended to avoid a mix of stable and unstable repo

Apart from that you mix official unstable repo with third party (Webmin) stable repo.

@der_bud has given you an important link:
https://wiki.debian.org/DontBreakDebian#Don.27t_make_a_FrankenDebian

You should not ignore this.

Kind regards,
  Holger

[der_bud]

There are surely other people knowing more, but my short comments on your lists would be:

1.) debian.list - looks ok to me

2.) mics.list - looks ok to me, all #'ed, only needed when support says so

3.) passenger.list - (no comment, don't know anything about it)

4.) siduction.list - I would change something:
    a) as you have contrib non-free in debian.list, add those also to siduction/fixes
    b) I think kde-frameworks should not be used, better change that line to
       deb http://packages.siduction.org/kdenext/ unstable main
       for know and prepare for kdenext being probably deprecated some day in the future
   
5.) snapshots.list - I don't know about it, can it interfere with debian, like holding up packages?

6.) ubuntuzilla.list - sounds strange, page looks deprecated, what for is it?
     If it's for iceweasel, better have a look at http://mozilla.debian.net/
   
7.) webmin.list - (no comment, don't know anything about it)

8.) x2go.list - (no comment, don't know anything about it)

[piper]

There are surely other people knowing more, but my short comments on your lists would be:

1.) debian.list - looks ok to me

2.) mics.list - looks ok to me, all #'ed, only needed when support says so

3.) passenger.list - (no comment, don't know anything about it)

4.) siduction.list - I would change something:
    a) as you have contrib non-free in debian.list, add those also to siduction/fixes
    b) I think kde-frameworks should not be used, better change that line to
       deb http://packages.siduction.org/kdenext/ unstable main
       for know and prepare for kdenext being probably deprecated some day in the future
   
5.) snapshots.list - I don't know about it, can it interfere with debian, like holding up packages?

6.) ubuntuzilla.list - sounds strange, page looks deprecated, what for is it?
     If it's for iceweasel, better have a look at http://mozilla.debian.net/
   
7.) webmin.list - (no comment, don't know anything about it)

8.) x2go.list - (no comment, don't know anything about it)

+1

[absolut]

i agree with der_bud.
the unknown 3rd party repos seem to be webmin, passenger, snapshots, ubuntuzilla and x2go.

how problematic is the use of repositories targeted at "sarge" in sid? I'd say, this might lead to some problems, now or later on.

for keeping the system up-to-date via dist-upgrades (not considering the transition/state of kdenext which will be resolved at some point in time) it is best to run dist-upgrade with all 3rd party repos being disabled.

vonh, i'd like to strongly suggest that you look into all dependencies that these repos bring with them, and evaluate whether your install is still in a supportable state

best
absolut

[melmarker]

I'm not in the mood to comment the rest of the list - but one should really delete the passenger.list - if one like passenger (like me) one should install passenger via the debian repo - or maybe better and more current - via gem or bundler. One hint - one could use the debian dependencies for passenger to build the needed integration parts with apt-get build-deps $foo.