Breakages and News tracking Debian Testing

SolydXK is too quiet for you? SolydXK Enthusiast Editions, based on Debian Testing is for you! Here you can find news about Debian Testing and Unstable too, and also tests on SolydXK programs.
The support for SolydXK EE is provided by the community.
kurotsugi
Posts: 2226
Joined: 09 Jan 2014 00:17

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 17 Dec 2014 10:25

it means that solydxk-system's init script is changed. sysvinit complained that the new runlevel is different with the old runlevel. as long as the script is running you have nothing to worry. even if it doesn't work your system will just fine.

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: Breakages and News tracking Debian Testing

Postby fleabus » 17 Dec 2014 12:48

MAYBL8 wrote:Not sure if it represents Debian Testing:
For now, it does. When Jessie becomes stable, it will represent Stable. If you want to continue to track Testing after the freeze, change "Jessie" to "Testing" and comment the backports repo... Not sure about the feasibility of using the jessie-backports repo when tracking testing, but instinct tells me that's not what "jessie-backports" is for... ;)

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: Breakages and News tracking Debian Testing

Postby fleabus » 17 Dec 2014 12:53

kurotsugi wrote:the new runlevel is different with the old runlevel. as long as the script is running you have nothing to worry.
Thanks kurotsugi. Saw that a few times myself.

User avatar
Arjen Balfoort
Site Admin
Posts: 9258
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Breakages and News tracking Debian Testing

Postby Arjen Balfoort » 26 Dec 2014 09:04

MAYBL8 wrote:Upon updating I received the following after a dist-upgrade:

Code: Select all

insserv: warning: current start runlevel(s) (empty) of script `solydxk-system' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (S) of script `solydxk-system' overrides LSB defaults (empty).
I have been looking at this, but I have no idea on how to prevent this warning.
The init script is found here: /etc/init.d/solydxk-system
and has this header:

Code: Select all

### BEGIN INIT INFO
# Provides:          solidxk-system
# Required-Start:    $all
# Required-Stop:     
# Default-Start:     2 3 4 5
# Default-Stop:      
# Short-Description: Run /usr/lib/solydxk/system/adjust.py if it exists
### END INIT INFO
You see, the start levels are default.
However, I suspect that this has to do with systemd.

I anyone could shed a light on this, I'd be very grateful!

In the mean time, I'll take a look at Mint's mintsystem package.


SolydXK needs you!
Development | Testing | Translations

kurotsugi
Posts: 2226
Joined: 09 Jan 2014 00:17

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 26 Dec 2014 19:01

However, I suspect that this has to do with systemd.
no it isn't.

Code: Select all

insserv: warning: current start runlevel(s) (empty) of script `solydxk-system' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (S) of script `solydxk-system' overrides LSB defaults (empty).
the previous start level was empty and the stop level was S. then, you/or someone else changed the header into: start (2345) stop (empty). that's when the problem started. you can check the current start runlevel using sysv-rc-conf and see whether if it has correct runlevel or not. if it correct then we can leave it.

it's a harmless message so as long as it has correct start runlevel then the script will be work. I'm not quite sure which one is "standard" but I usually using this and insserv never complained to me

Code: Select all

#!/bin/bash
### BEGIN INIT INFO
# Provides: zram
# Required-Start: $local_fs
# Required-Stop:
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
when I got this problem I remove all the sysvinit file (both the script and all sysvinit symlinks) then copy a fresh script on /etc/init.d/ then re-register it on sysvinit using insserv command like usual. it's indeed a rough way but it works.

User avatar
fleabus
Posts: 1227
Joined: 16 Sep 2013 04:24
Location: Winchester, VA USA

Re: Breakages and News tracking Debian Testing

Postby fleabus » 26 Dec 2014 20:25

It appears that dpkg 1.17.22 migrated to testing on Sunday, 21 December (last d-u on this partition was 19Dec).
Yeesh, I'm slow... I need to keep a closer eye on this stuff... :oops:

https://tracker.debian.org/news/669804
https://tracker.debian.org/pkg/dpkg

Testing-watch mailing list "most recent" page
https://lists.debian.org/debian-testing-changes/recent

Code: Select all

dv7-1270us fleabus # apt policy dpkg
dpkg:
  Installed: 1.17.21
  Candidate: 1.17.22
  Version table:
     1.17.22 0
        500 http://ftp.debian.org/debian/ testing/main amd64 Packages
 *** 1.17.21 0
        100 /var/lib/dpkg/status

Code: Select all

Repos:     Active apt sources in file: /etc/apt/sources.list
           deb http://packages.solydxk.com/testing/ solydxk main upstream import
           deb http://community.solydxk.com/testing/ solydxk main
           deb http://ftp.debian.org/debian testing main contrib non-free
           deb http://security.debian.org/ testing/updates main contrib non-free
Upgraded dpkg, ran a d-u. 92 packages, nvidia, systemd updates, no bug reports or errors, all quiet.


User avatar
belze
Posts: 221
Joined: 29 Sep 2014 16:31
Location: Torino, Italy

Re: Breakages and News tracking Debian Testing

Postby belze » 08 Feb 2015 19:41

-------
Image

kurotsugi
Posts: 2226
Joined: 09 Jan 2014 00:17

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 08 Feb 2015 20:36

the permanent removal stage means that the RC bug counts will heavily dropped and the release date is drawing near. the next stage would be force removal of every non-key packages (and if needed, the removal of key packages with RC bug). if we look into the stats, after debian reach this stage, we could roughly calculate that debian stable will got released between 6-12 weeks :3

User avatar
belze
Posts: 221
Joined: 29 Sep 2014 16:31
Location: Torino, Italy

Re: Breakages and News tracking Debian Testing

Postby belze » 08 Feb 2015 20:38

after that debian testing will became much more fun to track!
stay tuned!
-------
Image

Deleted User 580

Re: Breakages and News tracking Debian Testing

Postby Deleted User 580 » 15 Feb 2015 10:09

deleted

User avatar
Arjen Balfoort
Site Admin
Posts: 9258
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Breakages and News tracking Debian Testing

Postby Arjen Balfoort » 15 Feb 2015 14:55

The user session is not set by default.

For reference, this is mine:

Code: Select all

#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the system location
# guest-account-script = Script to be run to setup guest account
# logind-load-seats = True to automatically set up multi-seat configuration from logind
# logind-check-graphical = True to on start seats that are marked as graphical by logind
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#logind-load-seats=false
#logind-check-graphical=false
#log-directory=/var/log/lightdm
#run-directory=/var/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters

#
# Seat defaults
#
# type = Seat type (xlocal, xremote)
# xdg-seat = Seat name to set pam_systemd XDG_SEAT variable and name to pass to X server
# pam-service = PAM service to use for login
# pam-autologin-service = PAM service to use for autologin
# pam-greeter-service = PAM service to use for greeters
# xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login option
# greeter-show-remote-login = True if the greeter should offer a remote login option
# user-session = Session to load for users
# allow-user-switching = True if allowed to switch users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as root)
# display-stopped-script = Script to run after stopping the display server (runs as root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as root)
# session-cleanup-script = Script to run when quitting a user session (runs as root)
# autologin-guest = True to log in as guest by default
# autologin-user = User to log in with by default (overrides autologin-guest)
# autologin-user-timeout = Number of seconds to wait before loading default user
# autologin-session = Session to load for automatic login (overrides user-session)
# autologin-in-background = True if autologin session should not be immediately activated
# exit-on-failure = True if the daemon should exit if this seat fails
#
[SeatDefaults]
#type=xlocal
#xdg-seat=seat0
#pam-service=lightdm
#pam-autologin-service=lightdm-autologin
#pam-greeter-service=lightdm-greeter
#xserver-command=X
#xserver-layout=
#xserver-config=
#xserver-allow-tcp=false
#xserver-share=true
#xserver-hostname=
#xserver-display-number=
#xdmcp-manager=
#xdmcp-port=177
#xdmcp-key=
#unity-compositor-command=unity-system-compositor
#unity-compositor-timeout=60
#greeter-session=example-gtk-gnome
greeter-hide-users=false
#greeter-allow-guest=true
#greeter-show-manual-login=false
#greeter-show-remote-login=true
#user-session=default
#allow-user-switching=true
#allow-guest=true
#guest-session=
#session-wrapper=lightdm-session
#greeter-wrapper=
#guest-wrapper=
#display-setup-script=/usr/share/lightdmxrandr.sh
#display-stopped-script=
#greeter-setup-script=
#session-setup-script=
#session-cleanup-script=
#autologin-guest=false
#autologin-user=solydxk
#autologin-user-timeout=0
#autologin-in-background=false
#autologin-session=UNIMPLEMENTED
#exit-on-failure=false

#
# Seat configuration
#
# Each seat must start with "Seat:".
# Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
#
#[Seat:0]

#
# XDMCP Server configuration
#
# enabled = True if XDMCP connections should be allowed
# port = UDP/IP port to listen for connections on
# key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
#
# The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn.  Alternatively
# it can be a word and the first 7 characters are used as the key.
#
[XDMCPServer]
#enabled=false
#port=177
#key=

#
# VNC Server configuration
#
# enabled = True if VNC connections should be allowed
# command = Command to run Xvnc server with
# port = TCP/IP port to listen for connections on
# width = Width of display to use
# height = Height of display to use
# depth = Color depth of display to use
#
[VNCServer]
#enabled=false
#command=Xvnc
#port=5900
#width=1024
#height=768
#depth=8


SolydXK needs you!
Development | Testing | Translations

Deleted User 580

Re: Breakages and News tracking Debian Testing

Postby Deleted User 580 » 15 Feb 2015 16:37

deleted

User avatar
MAYBL8
Posts: 1487
Joined: 10 Mar 2013 18:41
Location: Maryland Heights, MO USA
Contact:

Re: Breakages and News tracking Debian Testing

Postby MAYBL8 » 04 Mar 2015 12:37

Last 2 days no updates from Debian Testing.
I wonder what that means?


User avatar
patzy
Posts: 406
Joined: 15 Dec 2013 08:32
Location: Australia

Re: Breakages and News tracking Debian Testing

Postby patzy » 04 Mar 2015 12:48

MAYBL8 wrote:Last 2 days no updates from Debian Testing.
I wonder what that means?
Jessie has gone stable. There will probably be a "breather" before the new Debian Testing kicks off.

Chris M
Posts: 27
Joined: 01 Sep 2013 20:16

Re: Breakages and News tracking Debian Testing

Postby Chris M » 04 Mar 2015 13:19

I'm running pure Debian Testing, and updates are still coming through. Look at these to try to guess:

https://release.debian.org/migration/

https://bugs.debian.org/release-critical/

https://bugs.debian.org/release-critical/graph.png

I think we're still many days away from Jessie going stable.

User avatar
belze
Posts: 221
Joined: 29 Sep 2014 16:31
Location: Torino, Italy

Re: Breakages and News tracking Debian Testing

Postby belze » 04 Mar 2015 13:40

not less than 6 weeks i guess. :roll:
looking forward to have a way to use a real unstable/experimental repo WHILE on freeze...if that ever happens...
-------
Image

User avatar
MAYBL8
Posts: 1487
Joined: 10 Mar 2013 18:41
Location: Maryland Heights, MO USA
Contact:

Re: Breakages and News tracking Debian Testing

Postby MAYBL8 » 04 Mar 2015 14:03

Chris M,
This is what my sources.list shows:

Code: Select all

## Debian/Solydxk testing
deb http://packages.solydxk.com/testing/ solydxk main upstream import
deb http://community.solydxk.com/testing/ solydxk main
deb http://ftp.debian.org/debian testing main contrib non-free
deb http://security.debian.org/ testing/updates main contrib non-free
deb http://www.deb-multimedia.org testing main non-free
## added to make deb file
deb-src http://ftp.us.debian.org/debian/ sid main
deb http://repository.spotify.com stable non-free
Don't know how this differs from yours.


kurotsugi
Posts: 2226
Joined: 09 Jan 2014 00:17

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 04 Mar 2015 20:11

https://lists.debian.org/debian-testing ... llist.html

packages are still moving into testing. it's just that the number of RC bugs becames so low that only a small packages got updated. if you want to get packages faster you can move into sid. it's now safe to use sid since it only accept bug fixing updates.

Chris M
Posts: 27
Joined: 01 Sep 2013 20:16

Re: Breakages and News tracking Debian Testing

Postby Chris M » 05 Mar 2015 17:04

MAYBL8, my sources.list :

Code: Select all

deb http://ftp.us.debian.org/debian/ testing main non-free contrib
deb-src http://ftp.us.debian.org/debian/ testing main non-free contrib
deb http://security.debian.org/ testing/updates main contrib non-free
deb-src http://security.debian.org/ testing/updates main contrib non-free 
kurotsugi, thanks for the link and the perspective. I reached up into sid and installed the current Testing kernel before it was accepted into Testing, but never looked at it that way. Give my regards to your cat.


Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 6 guests