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.
User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: Breakages and News tracking Debian Testing

Postby Snap » 06 Dec 2014 23:52

Some for KDE too. I have a few of those blacklisted.
How do I generate that list for my system?
Install apt-listbugs
This likely means that your installation is broken. -Mr Pixbuf.

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 » 07 Dec 2014 00:03

Any idea why I might get this when installing apt-listchanges:

Code: Select all

dcihon@dcihon-solydk64 ~ $ sudo apt-get install apt-listchanges
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Suggested packages:
  default-mta mail-transport-agent
The following NEW packages will be installed:
  apt-listchanges
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 85.8 kB of archives.
After this operation, 457 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian/ jessie/main apt-listchanges all 2.85.13+nmu1 [85.8 kB]
Fetched 85.8 kB in 0s (106 kB/s)         
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Preconfiguring packages ...
Can't exec "/tmp/apt-listchanges.config.ls9Tas": Permission denied at /usr/share/perl/5.20/IPC/Open3.pm line 177.
open2: exec of /tmp/apt-listchanges.config.ls9Tas configure  failed at /usr/share/perl5/Debconf/ConfModule.pm line 59.
Selecting previously unselected package apt-listchanges.
(Reading database ... 279677 files and directories currently installed.)
Preparing to unpack .../apt-listchanges_2.85.13+nmu1_all.deb ...
Unpacking apt-listchanges (2.85.13+nmu1) ...
Processing triggers for man-db (2.7.0.2-3) ...
Setting up apt-listchanges (2.85.13+nmu1) ...

Creating config file /etc/apt/listchanges.conf with new version


Deleted User 580

Re: Breakages and News tracking Debian Testing

Postby Deleted User 580 » 07 Dec 2014 01:20

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 » 08 Dec 2014 14:17

Anybody know about any grub issues with the latest updates?


Deleted User 580

Re: Breakages and News tracking Debian Testing

Postby Deleted User 580 » 08 Dec 2014 14:31

deleted

User avatar
grizzler
Posts: 2155
Joined: 04 Mar 2013 15:45
Location: The Hague, NL

Re: Breakages and News tracking Debian Testing

Postby grizzler » 08 Dec 2014 15:46

MAYBL8 wrote:Anybody know about any grub issues with the latest updates?
No problems here either.

Did you see any kind of error message during the update?
I wonder if any issues you had have anything to do with the permission errors you reported recently.
Frank

SolydX EE 64 - tracking Debian Testing

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 » 08 Dec 2014 16:34

Yea might have to do with that. I seen some errors with the /tmp directory.
I am going to reinstall tonight and go from there.
Thanks for trying to help.
I have a separate /home directory so re-installs go quite easy. As long as the problem doesn't reside in the /home folder.


User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: Breakages and News tracking Debian Testing

Postby Snap » 08 Dec 2014 18:29

Yep, no issues with grub-pc this time after upgrading this morning.
This likely means that your installation is broken. -Mr Pixbuf.

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 » 09 Dec 2014 14:29

Look like my system is now checking for bugs when doing a dist-upgrade:

Code: Select all

Get:8 http://ftp.debian.org/debian/ testing/main apt amd64 1.0.9.4 [1,105 kB]                                       
Get:9 http://ftp.debian.org/debian/ testing/main libapt-inst1.5 amd64 1.0.9.4 [168 kB]                                                                  
Get:10 http://ftp.debian.org/debian/ testing/main apt-utils amd64 1.0.9.4 [367 kB]                                                                      
Get:11 http://www.deb-multimedia.org/ testing/main libavcodec56 amd64 10:2.5-dmo1 [3,598 kB]                                                            
Get:12 http://www.deb-multimedia.org/ testing/main libavformat56 amd64 10:2.5-dmo1 [746 kB]                                                             
Get:13 http://www.deb-multimedia.org/ testing/main libavresample2 i386 10:2.5-dmo1 [101 kB]                                                             
Get:14 http://www.deb-multimedia.org/ testing/main libavresample2 amd64 10:2.5-dmo1 [76.7 kB]                                                           
Get:15 http://www.deb-multimedia.org/ testing/main libpostproc53 amd64 10:2.5-dmo1 [74.5 kB]                                                            
Get:16 http://www.deb-multimedia.org/ testing/main libswscale3 amd64 10:2.5-dmo1 [147 kB]                                                               
Get:17 http://www.deb-multimedia.org/ testing/main libavfilter5 amd64 10:2.5-dmo1 [454 kB]                                                              
Get:18 http://www.deb-multimedia.org/ testing/main libavdevice56 amd64 10:2.5-dmo1 [84.5 kB]                                                            
Get:19 http://www.deb-multimedia.org/ testing/main ffmpeg amd64 10:2.5-dmo1 [1,217 kB]                                                                  
Fetched 23.4 MB in 49s (471 kB/s)                                                                                                                       
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of apt (1.0.9.3 → 1.0.9.4) <Outstanding>
 b1 - #772641 - apt: "E: Setting TIOCSCTTY for slave fd <fd> failed" when run as a session leader
Summary:
 apt(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n
**********************************************************************
****** Exiting with an error in order to stop the installation. ******
**********************************************************************
E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (10)
E: Failure running script /usr/sbin/apt-listbugs apt
Now I just need to learn if the bug is serious enough not to install.


User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: Breakages and News tracking Debian Testing

Postby Snap » 09 Dec 2014 15:08

What maxibuntu said 7 posts above, plus checking Debian Testing based distros forums for breakages and solutions.

For me it still makes sense tracking Testing because it's what HEs are still based on (UPs coming or not), but I will stop doing it when Jessie becomes stable. From that point I'll only plan to track Stable and Sid, since SolydXK won't have any official release based on Testing.

In this case:

http://forums.solydxk.nl/viewtopic.php?f=9&t=162

http://forums.solydxk.nl/viewtopic.php?f=35&t=240
REPOS
(Updated 9.23.13)

deb http://packages.solydxk.nl/production/ solydxk main upstream import # "SolydXK"
deb http://community.solydxk.nl/production/ solydxk main # "SolydXK-Comm"
deb http://http.us.debian.org/debian/ unstable main contrib non-free #"SID"
deb http://www.deb-multimedia.org sid main non-free #"SID Multimedia"
Edit your /etc/apt/preferences to:
Package: *
Pin: release o=solydxk
Pin-Priority: 700

Package: *
Pin: origin packages.solydxk.nl
Pin-Priority: 700

Package: *
Pin: release o=Debian
Pin-Priority: 700

OR: just delete or rename it.

==========================================

Edit:

The use of apt-listbugs (in the repos) is a help.
Tracking other Debian Sid forums is also a plus...

Siduction
http://forum.siduction.org/index.php?board=22.0

Aptosid
http://aptosid.com/index.php?name=PNphp ... c27c096455

LMDE
http://forums.linuxmint.com/viewtopic.p ... 97#p406197
http://forums.linuxmint.com/viewtopic.p ... 8&t=133211
http://forums.linuxmint.com/viewtopic.php?f=141&t=67502
http://forums.linuxmint.com/viewtopic.p ... 7&t=159257

GeneC
EDIT: The last links were broken. Corrected.
This likely means that your installation is broken. -Mr Pixbuf.

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 » 09 Dec 2014 15:25

Snap,
Thanks for putting all that info together. I will be referring back to that in the future.
I am going to stick with Debian Testing. (EE) if it stll going to be called that. I think that is what fits best for me.
Packages are a little more updated.
More of a rolling release. (The reason I came here in the first place along with following ZZ from LMDE).
It is stable enough for me. Occasional breakages I can live with.
From the sounds of everyone here looks like the majority are going to stay with stable.
Thanks
Dan


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

Re: Breakages and News tracking Debian Testing

Postby belze » 12 Dec 2014 23:47

I just added testing to my sources.list and d-u my main box. I expected a smooth process and all was good.
Cheers
-------
Image

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

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 13 Dec 2014 06:24

From that point I'll only plan to track Stable and Sid, since SolydXK won't have any official release based on Testing.
a little advice, if you don't mind, sid and testing is lot similar. there's no strict boundaries between them so on most time you won't notice the differences. the differences is usually less than 100 package. all the stuff for sid is applicable for testing too. I'd say the only differences between testing and sid is that you need to wait 2-10 days until a package move into testing. if you're not a "player" and don't want to get all those nasty bug you can use any sid based ISO then change the repo to testing.

the real "unstable" in debian is actually the experimental branch. sid and testing have same purposes which is "to prepare next stable version". on a certain perspective we can say that testing and sid is actually one distro branch.

User avatar
Snap
Posts: 1244
Joined: 25 Aug 2013 20:01
Location: Spain

Re: Breakages and News tracking Debian Testing

Postby Snap » 13 Dec 2014 08:23

Thanks, kurotsugi. I know testing and sid are close. The idea is keeping my main system on Stable and having the rolling stuff in VMs. Maybe a bare metal install too. I really want to play as long as my main desktop keeps going rock solid.
This likely means that your installation is broken. -Mr Pixbuf.

Image

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

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 13 Dec 2014 19:21

I see :3

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

Re: Breakages and News tracking Debian Testing

Postby fleabus » 14 Dec 2014 14:54

kurotsugi wrote:the real "unstable" in debian is actually the experimental branch.
I always thought, from reading Debian docs, that experimental did not contain a full working distribution, only experimental packages, and so must be enabled temporarily with Sid (or whatever) to get them, rather than remaining constantly enabled? Please correct me if I'm wrong, as it's been a while since I cruised the docs over there...

I dimly remember that when I hung out in Sid Breakages with zz and wayne and GeneC, zz used to temp-enable an experimental line in sources just to pull in bleeding edge kernels and whatnot...

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

Re: Breakages and News tracking Debian Testing

Postby belze » 14 Dec 2014 16:22

If you enable experimental you have to ask apt to gran packages from there using -t option. Experimental has a default lower value in pinning. Thst's what i knoe.
-------
Image

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

Re: Breakages and News tracking Debian Testing

Postby kurotsugi » 15 Dec 2014 06:28

yes experimental is disabled by default. it have the lowest pin value (50), even lower than your current package (100). thus, you can safely keep it your list. if you want something from experimental you need declare it on your command by using "-t experimental" option. it's not advised to install something from experimental if you can find it on testing/sid but sometimes certain package only exist on experimental.

experimental branch only exist on debian. other distro divided as stable-unstable or stable-testing-unstable. debian's experimental is equal with other distro's "unstable". other distro's "testing" is divided into testing and sid (unstable) because debian highly stressed on stability. regardless the name, sid (unstable) is actually quite stable because in reality it's the "testing" branch.

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

Re: Breakages and News tracking Debian Testing

Postby fleabus » 15 Dec 2014 07:05

kurotsugi wrote:.... thus, you can safely keep it your list.
Thanks kurotsugi, good to know... :)

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 » 17 Dec 2014 04:30

Not sure if this goes here.
This is my repo list right now:
Not sure if it represents Debian Testing:

Code: Select all

dcihon@solydk64 ~ $ inxi -r
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb http://repository.solydxk.com/ solydxk main upstream import
           deb http://ftp.debian.org/debian jessie main contrib non-free
           deb http://security.debian.org/ jessie/updates main contrib non-free
           deb http://ftp.debian.org/debian/ jessie-backports main contrib non-free
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).



Return to “Testing Zone”

Who is online

Users browsing this forum: No registered users and 2 guests