We need more testers to the new incoming repo (how-to)

[kmb42vt]

I have a question on the debian repo's.....to which repo should I be pointing to: ftp.debian.org or debian.linuxmint.com.....the reaso I ask is because I clicked on the button that update-pack info and it says the two conflict with each other.....so I'm guessing this is why update-pack 1 & 2 are being installed.....any info would be greatly appreciated......thanks.

Cheers
Andrew

There are 2 new possible repos you can point to now if you followed the instructions for switching to the new LMDE update system from this post:

http://blog.linuxmint.com/?p=1781

These repos are (either one or the other--not both):

The "latest" repo:

Code: Select all

deb http://debian.linuxmint.com/latest testing main contrib non-free

and the "incoming" repo

Code: Select all

deb http://debian.linuxmint.com/incoming testing main contrib non-free

The "latest" (stable) repo will currently give you "update pack 1" while the "incoming" repo, which is designed for those who wish to test the next update pack before it's released, will give you "update pack 2" pre-release.

For you at this stage you need to enable the "latest" repo so you can upgrade to "Update pack 1" first. Just make absolutely sure that you've disabled the old "Debian testing" repo as well as the new "incoming" repo if you've already added it to your sources list. You can only ever choose one of the three to receive updates from.

So in short, enable the "latest" repo and disable the "incoming" repo (if already added) as well as the old "Debian testing" repo and you should be ready to upgrade to "Update pack 1". Once Update pack 1 is installed (and everything is checked out okay) and you want to switch to a "testers" hat then you can disable the "latest" repo and enable the "incoming" repo and upgrade once again.

Hope that answers your question.

[andrew5859]

Thank you....this is much better and very informative.....I've added the "latest", upgraded and am going to jump into the "testing hat" as you put it....I greatly appreciate your assistance kmb42vt.



Cheers
Andrew

[andrew5859]

How often do updates come through on "incoming"...any idea or is it as it goes...thanks

[wayne128]

How often do updates come through on "incoming"...any idea or is it as it goes...thanks

andrew,

read clem reply on zerozero questions in this post

viewtopic.php?f=187&t=76854&p=451097#p451097

[andrew5859]

Thank you Wayne, that answers my question...have a great evening

[kmb42vt]

One thing I need to mention just for the sake of mentioning it. Quite awhile ago one the updates coming from "Debian testing" caused the "startup" sound (logging in after a fresh boot/reboot) to stop working and so far this hasn't been fixed. I've experienced this on two different desktop PCs, one 8 years old and one bought new last year. Both machines are pretty much 'off the shelf' and other Linux Mint editions and every non-"Debian testing" distro I've tried so far does not exhibit this problem. The LMDE Live session doesn't exhibit this problem either nor does booting into the initial install before applying the updates (either from "Debian testing" or the new "Incoming" or "Latest" repositories). Once all updates are applied, the above sound stops working. Again, this problem first showed up 3 to 4 months ago and was posted on the LMDE forums by others then as well (I'm still trying to find the original threads but the old threads have been pretty much buried by now)

LMDX exhibits the same problem, btw. Stands to reason.

Nothing is missing from LMDE, all sound files are present and the "Gnome Login Sound" is there in "Startup applications" in the Control center and the command line is correct. In fact, when I paste the same "Gnome Login Sound" command line into the terminal it plays fine with no errors shown. I seem to recall the problem was caused by one of the startup modules (MintMenu, MintUpdate, etc) preempting the Gnome Login Sound but I can't remember the details.

The point I'm trying to make here I guess, is that update pack 1 and 2 hasn't fixed this and I'm pretty sure that this problem I'm experiencing is not isolated at all. Over a half a dozen test installs (direct to hard drive, not VM) between two different machines with different hardware and the same problem shows up after updating. The frustrating part about it is I know I had it fixed shortly after it first occurred (with help from a post of the Linux Mint forums about 3 months or so ago) but I can't recall how I did it and for once I failed to write down the solution.

So I thought I'd just mention it here.

[samriggs]

samriggs,
I had a similar issue updating to package 2, but the error messages are much more extended...

I don'y have any clues, apparently I must configure a lot of things...
But the system is running well.

I have LMDE 32 bits, liquorix kernel, desktop computer with intel core 2 duo processor, 3 GB ram, Intel graphic card.
Help, anyone?

lleriria Im running a 32bit gateway laptop intel centrino 2 gigs ram mabe its something with 32bit systems who knows although thaat shouldn't make any difference, I was getting that same error trying to install some programs also but then I redidi it and they instralled fine after that, it doesn't make sense to me, not many answers out there either.
The description on binfmt-support says this

This package provides an 'update-binfmts' script with which package maintainers can register interpreters to be used with this module without having to worry about writing their own init.d scripts, and which sysadmins can use for a slightly higher-level interface to this module.

Don't know anything about it just that it causes an error.

EDIT:
Just had another 2 updates come through and still having the issue, I am adding the whole log to see if anyone can figure this error out.

Code: Select all

(Reading database ... 163098 files and directories currently installed.)
Preparing to replace libquicktime2 3:1.2.2-0.5 (using .../libquicktime2_3%3a1.2.3-0.1_i386.deb) ...
Unpacking replacement libquicktime2 ...
Preparing to replace gstreamer0.10-lame 0.10.18-0.0 (using .../gstreamer0.10-lame_0.10.18-0.1_i386.deb) ...
Unpacking replacement gstreamer0.10-lame ...
Setting up binfmt-support (2.0.5) ...
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service smfpd and checkroot if started
insserv:  loop involving service checkroot at depth 3
insserv:  loop involving service hdparm at depth 2
insserv:  loop involving service hwclock at depth 5
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service portmap at depth 8
insserv: There is a loop between service rc.local and mountnfs if started
insserv:  loop involving service mountnfs at depth 8
insserv:  loop involving service networking at depth 7
insserv: There is a loop between service rc.local and ifupdown-clean if started
insserv:  loop involving service ifupdown-clean at depth 5
insserv: There is a loop between service smfpd and checkroot if started
insserv:  loop involving service hostname at depth 4
insserv:  loop involving service mountnfs-bootclean at depth 10
insserv:  loop involving service ifupdown at depth 7
insserv:  loop involving service fuse at depth 13
insserv: There is a loop between service rc.local and mountoverflowtmp if started
insserv:  loop involving service mountoverflowtmp at depth 10
insserv:  loop involving service mountall-bootclean at depth 9
insserv: There is a loop between service rc.local and checkfs if started
insserv:  loop involving service checkfs at depth 7
insserv:  loop involving service mtab at depth 6
insserv: There is a loop between service smfpd and mountdevsubfs if started
insserv:  loop involving service mountdevsubfs at depth 2
insserv:  loop involving service udev at depth 1
insserv:  loop involving service bootlogd at depth 4
insserv:  loop involving service smfpd at depth 1
insserv:  loop involving service mountall at depth 9
insserv: There is a loop between service smfpd and bootlogd if started
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing binfmt-support (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of jarwrapper:
 jarwrapper depends on binfmt-support; however:
  Package binfmt-support is not configured yet.
dpkg: error processing jarwrapper (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of binfmtc:
 binfmtc depends on binfmt-support; however:
  Package binfmt-support is not configured yet.
dpkg: error processing binfmtc (--configure):
 dependency problems - leaving unconfigured
Setting up libquicktime2 (3:1.2.3-0.1) ...
configured to not write apport reports
                                      configured to not write apport reports
                                                                            configured to not write apport reports
                                  Setting up gstreamer0.10-lame (0.10.18-0.1) ...
Errors were encountered while processing:
 binfmt-support
 jarwrapper
 binfmtc
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up binfmt-support (2.0.5) ...
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service smfpd and checkroot if started
insserv:  loop involving service checkroot at depth 3
insserv:  loop involving service hdparm at depth 2
insserv:  loop involving service hwclock at depth 5
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service portmap at depth 8
insserv: There is a loop between service rc.local and mountnfs if started
insserv:  loop involving service mountnfs at depth 8
insserv:  loop involving service networking at depth 7
insserv: There is a loop between service rc.local and ifupdown-clean if started
insserv:  loop involving service ifupdown-clean at depth 5
insserv: There is a loop between service smfpd and checkroot if started
insserv:  loop involving service hostname at depth 4
insserv:  loop involving service mountnfs-bootclean at depth 10
insserv:  loop involving service ifupdown at depth 7
insserv:  loop involving service fuse at depth 13
insserv: There is a loop between service rc.local and mountoverflowtmp if started
insserv:  loop involving service mountoverflowtmp at depth 10
insserv:  loop involving service mountall-bootclean at depth 9
insserv: There is a loop between service rc.local and checkfs if started
insserv:  loop involving service checkfs at depth 7
insserv:  loop involving service mtab at depth 6
insserv: There is a loop between service smfpd and mountdevsubfs if started
insserv:  loop involving service mountdevsubfs at depth 2
insserv:  loop involving service udev at depth 1
insserv:  loop involving service bootlogd at depth 4
insserv:  loop involving service smfpd at depth 1
insserv:  loop involving service mountall at depth 9
insserv: There is a loop between service smfpd and bootlogd if started
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing binfmt-support (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of jarwrapper:
 jarwrapper depends on binfmt-support; however:
  Package binfmt-support is not configured yet.
dpkg: error processing jarwrapper (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of binfmtc:
 binfmtc depends on binfmt-support; however:
  Package binfmt-support is not configured yet.
dpkg: error processing binfmtc (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 binfmt-support
 jarwrapper
 binfmtc



I don't know much about this hopefully someone can figure this out and what I need to do, it was alright with the updates until I had to do a reinstall and now I keep getting this error during updates.
Also seen a bug report on debian about this but it says in the title it should work on linux.
Heres the link http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565109
Sam

[lleiria]

samriggs,

Nope, the problem is not a reinstall, there's been more than eight months that I don't do any reinstall, that's the reason why I decided to choose LMDE though I'm not a specialist, I'm just a curious journalist. Let's hope some veteran people around here can help us.
Hey zerozero: should I wait or go to the main forum and begin another thread? Where's the people bored ?

[zerozero]

One thing I need to mention just for the sake of mentioning it. Quite awhile ago one the updates coming from "Debian testing" caused the "startup" sound (logging in after a fresh boot/reboot) to stop working and so far this hasn't been fixed. I've experienced this on two different desktop PCs, one 8 years old and one bought new last year. Both machines are pretty much 'off the shelf' and other Linux Mint editions and every non-"Debian testing" distro I've tried so far does not exhibit this problem. The LMDE Live session doesn't exhibit this problem either nor does booting into the initial install before applying the updates (either from "Debian testing" or the new "Incoming" or "Latest" repositories). Once all updates are applied, the above sound stops working. Again, this problem first showed up 3 to 4 months ago and was posted on the LMDE forums by others then as well (I'm still trying to find the original threads but the old threads have been pretty much buried by now)

LMDX exhibits the same problem, btw. Stands to reason.

Nothing is missing from LMDE, all sound files are present and the "Gnome Login Sound" is there in "Startup applications" in the Control center and the command line is correct. In fact, when I paste the same "Gnome Login Sound" command line into the terminal it plays fine with no errors shown. I seem to recall the problem was caused by one of the startup modules (MintMenu, MintUpdate, etc) preempting the Gnome Login Sound but I can't remember the details.

The point I'm trying to make here I guess, is that update pack 1 and 2 hasn't fixed this and I'm pretty sure that this problem I'm experiencing is not isolated at all. Over a half a dozen test installs (direct to hard drive, not VM) between two different machines with different hardware and the same problem shows up after updating. The frustrating part about it is I know I had it fixed shortly after it first occurred (with help from a post of the Linux Mint forums about 3 months or so ago) but I can't recall how I did it and for once I failed to write down the solution.

So I thought I'd just mention it here.

after some digging the only hints i found were viewtopic.php?f=141&t=67502&p=436688&hilit=login#p436688
is this it?

[zerozero]

Leiria and Sam, sorry but i can't make out where that error comes from,
this is today's update

Code: Select all

Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  libavcodec53 libswscale2 libvo-aacenc0 libvo-amrwbenc0
The following packages will be upgraded:
  gstreamer0.10-lame libquicktime2
2 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,486 kB of archives.
After this operation, 7,045 kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://www.debian-multimedia.org/ testing/main libavcodec53 amd64 5:0.8-0.1 [2,755 kB]
Get:2 http://debian.linuxmint.com/incoming/ testing/main libvo-aacenc0 amd64 0.1.1-1 [76.0 kB]
Get:3 http://debian.linuxmint.com/incoming/ testing/main libvo-amrwbenc0 amd64 0.1.1-1 [70.0 kB]
Get:4 http://www.debian-multimedia.org/ testing/main libswscale2 amd64 5:0.8-0.1 [103 kB]
Get:5 http://www.debian-multimedia.org/ testing/main libquicktime2 amd64 3:1.2.3-0.1 [346 kB]
Get:6 http://www.debian-multimedia.org/ testing/main gstreamer0.10-lame amd64 0.10.18-0.1 [137 kB]
Fetched 3,486 kB in 12s (283 kB/s)                                             
Selecting previously deselected package libvo-aacenc0.
(Reading database ... 230542 files and directories currently installed.)
Unpacking libvo-aacenc0 (from .../libvo-aacenc0_0.1.1-1_amd64.deb) ...
Selecting previously deselected package libvo-amrwbenc0.
Unpacking libvo-amrwbenc0 (from .../libvo-amrwbenc0_0.1.1-1_amd64.deb) ...
Selecting previously deselected package libavcodec53.
Unpacking libavcodec53 (from .../libavcodec53_5%3a0.8-0.1_amd64.deb) ...
Selecting previously deselected package libswscale2.
Unpacking libswscale2 (from .../libswscale2_5%3a0.8-0.1_amd64.deb) ...
Preparing to replace libquicktime2 3:1.2.2-0.5 (using .../libquicktime2_3%3a1.2.3-0.1_amd64.deb) ...
Unpacking replacement libquicktime2 ...
Preparing to replace gstreamer0.10-lame 0.10.18-0.0 (using .../gstreamer0.10-lame_0.10.18-0.1_amd64.deb) ...
Unpacking replacement gstreamer0.10-lame ...
Setting up libvo-aacenc0 (0.1.1-1) ...
Setting up libvo-amrwbenc0 (0.1.1-1) ...
Setting up libavcodec53 (5:0.8-0.1) ...
Setting up libswscale2 (5:0.8-0.1) ...
Setting up libquicktime2 (3:1.2.3-0.1) ...
Setting up gstreamer0.10-lame (0.10.18-0.1) ...
amadeu@amadeu ~ $


will it be related with the liquorix kernel?

[choope1]

I attempted to install sugar from the package manager. Sugar is from the one laptop per child project. Some files are missing from the incoming repo.
W: Failed to fetch http://debian.linuxmint.com/incoming/pool/main/t/tk8.5/tk8.5_8.5.9-2_i386.deb
404 Not Found

W: Failed to fetch http://debian.linuxmint.com/incoming/pool/main/libc/libconfig-inifiles-perl/libconfig-inifiles-perl_2.66-2_all.deb
404 Not Found

W: Failed to fetch http://debian.linuxmint.com/incoming/pool/main/g/goffice/libgoffice-0.8-8-common_0.8.15-1_all.deb
404 Not Found

W: Failed to fetch http://debian.linuxmint.com/incoming/pool/main/g/goffice/libgoffice-0.8-8_0.8.15-1_i386.deb
404 Not Found

W: Failed to fetch http://debian.linuxmint.com/incoming/pool/main/s/sugar-hulahop/python-hulahop_0.7.1-4+b1_i386.deb
404 Not Found

[kmb42vt]

after some digging the only hints i found were viewtopic.php?f=141&t=67502&p=436688&hilit=login#p436688
is this it? [/quote]

Heh, already found that one as you probably assumed. I've done a lot of digging as well as you might imagine. Skype sounds won't work at all either though they're set up correctly. Not the fault of the update packs I'm sure. I actually had to remove Pulse Audio completely and run straight Alsa in order to solve that problem and to be honest about it, removing Pulse from LMDE isn't a bad idea at that. To me, Pulse is to audio as Plymouth is to boot up as Nepomuk/Strigi is to KDE if you know what I mean.

Again, all these niggling problems like the two above that have been around for the last 4 to 6 months are all pretty much moot until the respin is out. I'm pretty much convinced that Clem won't release the new respin without the login sounds working.

[zerozero]

To me, Pulse is to audio as Plymouth is to boot up as Nepomuk/Strigi is to KDE if you know what I mean.

so true
Alsa works period! Plymouth, i personally, even in the distros that have it more or less well implemented (Mandriva had, PCLOS and Mageia have), look for a way to disable it: i like to see the boot up text; that Nepomuk/Strigi-thingy grrrr!!! specially now in 4.7 that they never end indexing

[samriggs]

Leiria and Sam, sorry but i can't make out where that error comes from,
this is today's update
will it be related with the liquorix kernel?

Not sure zero
two lines say its a missing lsb tag issue

Setting up binfmt-support (2.0.5) ...
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides

but I check and have lsb installed unless I am missing something note the binfmt-support
then I get this a whole wack of times

insserv: Starting smfpd depends on rc.local and therefore on system facility `$all' which can not be true!

until it tries it 99 times
Then this

update-rc.d: error: insserv rejected the script header

So it rejects it.
Then the binfmt issue again

dpkg: error processing binfmt-support (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of jarwrapper:
jarwrapper depends on binfmt-support; however:
Package binfmt-support is not configured yet.
dpkg: error processing jarwrapper (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of binfmtc:
binfmtc depends on binfmt-support; however:
Package binfmt-support is not configured yet.
dpkg: error processing binfmtc (--configure):
dependency problems - leaving unconfigured

and depency problems with jarwrapper but this could be an eclipse problem and installing packages as root seems that it could case the jarwrapper issue from something I read somehere. What gets me is it keeps saying binfmt-support is not configured yet, I really dont know how to configure it, what I am thinking is to just delete it and see if that kills the system (hopefully not ) and then reinstall it to see if that fixes it, I know debian had an issue with it but it was earlier version of binfmt-support and it was more for freebsd then it was for linux but then I found this

version.cgi.png (25.83 KiB) Viewed 4467 times

looks like I am using the unstable version of binfmt-support and it is broke and don't work
Hopefully they will fix it soon or maybe I can remove it and get binfmt-support version 1.2.18 instead until they fix it so I guess next I have to hunt that version in the repos and make a quick switch over in synaptics to dig it out and try that I guess.
Also if you read here http://bugs.debian.org/cgi-bin/pkgreport.cgi?package=binfmt-support
They are having issues with the binfmt-support for jarwrapper, warnings on innserv, problem with chroot() installation, binfmt-support/run-detectors tries to run binfmt-detector-cli., plus
Outstanding bugs -- Normal bugs; Patch Available (1 bug)
Outstanding bugs -- Normal bugs; Unclassified (3 bugs)
Outstanding bugs -- Wishlist items; Unclassified (1 bug)
So it's buggy as heck
Not much can be done about it until they fix it I guess unless I want to get an earlier version installed instead, right now it's just an annoying issue but doesn't seem to harm anything I can find, eclipse runs well, been working on it all day and running androids emulator with no issues and trying some straight java code with no issues either for the jarwrapper bug, I deleted the binfmtc as that was not needed anyhow.
I'll keep an eye on it for now to see if it tries to stop anything from working, if so I'll report it and will have to get the earlier version instead unitl they fix it.
Unless I don't need it but I don't know if its needed or not so when in doubt don't (but I usually do )
Sam

[zerozero]

sam, you can try

Code: Select all

sudo dpkg --configure --pending

http://qref.sourceforge.net/quick/ch-package.en.html

http://www.debian.org/doc/manuals/refer ... ken_system

[samriggs]

sam, you can try

Code: Select all

sudo dpkg --configure --pending

Thanks zero I tried that it gave me the same errors. I guess it won't be fixed until they fix it upstream first by the looks of it, I can wait.
Sam

[Dar-es-Salaam]

Hi zerozero

I have changed all my sourse list to what you say adndone the other command but it still is not working. That is to say the .............-pae is not configuring, is ther a step that I have not done or is missing

Where are update packs 1 & 2 I can't seeem to locate them and do I need to install them

[samriggs]

Hi zerozero

I have changed all my sourse list to what you say adndone the other command but it still is not working. That is to say the .............-pae is not configuring, is ther a step that I have not done or is missing

Where are update packs 1 & 2 I can't seeem to locate them and do I need to install them

Hello Dar-es-Salaam
Did you install grub after installing and and doing the

Code: Select all

sudo apt-get update  && sudo apt-get dist-upgrade

After the intial install? it downloads about 700mb if not more on that update.
Sometimes it doesn't install all the first time around (it took 3 times for me) then you need to do a

Code: Select all

sudo apt-get install -f

to get the rest
it will try to install grub during the update but it wont let you, you need to update the grub after this is done before reboot

Code: Select all

sudo apt-get install grub && sudo update-grub

Then switch the repos as zero showed to do, do the commands he said to get the new mintupdate, then on the bottom right you will see a shield with either blue in it or a green check mark, click that put in your password and it will update from there, you can also do it through the terminal also but this way it can show you info on the packages and a few fixes if anything goes wrong in the info button.
The intial update

Code: Select all

sudo apt-get update && sudo apt-get dist-upgrade

before switching repos is where things can go wrong if not fully installed and grub isn't updated after that.
Don't know if any of these will help but hopefully.

Zero I found some more information on the smfpd errors, it seems this happens quite a bit and a lot of folks have been having issues with ever since the update in debian, not just mint, in the smfpd there is no
etc/init.d/smfpd

Code: Select all

# # # BEGIN INIT INFO
# Provides: smfpd
# Required-Start: $ syslog $ remote_fs
# Required-Stop: $ syslog $ remote_fs
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start daemon at boot time
# Description: Enable Service Provider by daemon.
# # # END INIT INFO

This is for this error

Code: Select all

insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides

there is a fix supposidly at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589238
that says to run /usr/share/insserv/make-testsuite
When I run this in the terminal I see this

Code: Select all

addscript smfpd <<'EOF'
EOF

This shows its missing whats needed it is the only one that does not have BEGIN INIT
the only thing is I tried adding one and reran the make-testsuite and it shows no change, unless I am doing it wrong, I tried to add it into the smfpd file itself and I probably have the wrong code in there.
Can someone run there make-testsuite see if there missinf it also for the smfpd and if not what is the code for that one?
or maybe open up your /ect/init.d/smfpd and see if it is in there on yours and let me know so I can try it out to see if it fixes this issue?
I'll try it on mine and hopefully we can get a fix for this thing.
That still doesn't fix the binfmt-support but at least it kills one bug if I can get it fixed without trying another reinstall which I really don't want to do.
Thanks
Sam

[zerozero]

Gordon, for the log i saw in the other thread i looks like a broken update, something like this:
- you run update/dist-upgrade (first time after the install), it fails with that log
- you logout, login, and the system is broken
- it's something in this lines?

[samriggs]

Zero please see my edited post above I might have a fix for the smfpd but I need some info from someone to see what they got.
EDIT:
Just checked the wifes, hers is the same as mine but she doesn't have the same issue as I do but shes running a 64bit, mines a 32bit, back to the drawing board.
Thanks
Sam