« first day (1239 days earlier)      last day (3706 days later) » 
00:00 - 19:0019:00 - 21:00

slm
12:08 AM
@FaheemMitha voted
 
12:29 AM
@slm Thanks.
 
12:51 AM
@strugee see reopen request above
@trelosae your question now has 4 reopen votes. when it has 5 it will be reopened. So you should be able to add an answer soon.
 
nice, thanks
oh btw
i'm now trying to install the 0.17 version
and when i try to get sources
it returns
root@nibelung:/usr/local/src/mpd# apt-get source mpd=0.17.6-1~bpo70+1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Picking 'mpd-dmo' as source package instead of 'mpd'
E: Ignore unavailable version '0.17.6-1~bpo70+1' of package 'mpd'
E: Unable to find a source package for mpd-dmo
 
@trelosae I don't get the mpd-dmo thing. why is it there?
apt-cache policy mpd-dmo and also apt-cache policy mpd-dmo please
btw, you really, really don't want to run these command as root if you don't have to. apt-get source should be run as user. if you need to do build-dep etc you can use sudo.
 
@FaheemMitha N: Unable to locate package mpd-dmo
 
@derobert Where does dpkg-checkbuildeps: come from? It says dpkg-dev, but I have that installed. A more recent version, perhaps?
@trelosae For both commands?
apt-get source mpd=0.17.6-1~bpo70+1
works fine here
 
@FaheemMitha yes, but they are the same
 
1:01 AM
sorry, the latter should have been apt-cache showsrc mpd-dmo
 
@FaheemMitha W: Unable to locate package mpd-dmo``N: No packages found
 
@trelosae Hmm, strange.
 
@FaheemMitha would downloading the tars from here work? packages.debian.org/wheezy-backports/mpd
 
@trelosae you have the deb-src lines for wheezy backports?
 
@FaheemMitha yes deb-src http://ftp.gr.debian.org/debian wheezy-backports main contrib non-free
 
1:03 AM
@trelosae it would, but you would need all three files, dsc, orig.tar.gz and diff, and also run dpkg-source -x whatever.dsc to unpack.
@trelosae Does apt-cache showsrc mpd give the correct version?
 
@FaheemMitha yep
 
@trelosae you ran apt-get update too?
 
@FaheemMitha yes
 
@trelosae ok, yes, you can download from the package page. i suggest wget -c url.
mpd-dmo is a deb-multimedia thing, why does it appear here?
Your sources.list doesn't have anything there, right? Check /etc/apt/sources.list.d. Long shot though.
you could also try apt-cache search mpd-dmo.
 
@FaheemMitha oh there are some lists from openmediavault one of which contains this: deb http://debian.linuxmint.com/latest/multimedia testing main non-free
should i comment it out?
 
1:11 AM
@trelosae Yes, I'd take that out. In fact, that comment out everything not debian.
This is located where?
 
@FaheemMitha /etc/apt/sources.list.d/openmediavault-millers.list
 
btw, does anyone know a way to make apt print out the sources.list it knows about without grubbing through files?
@trelosae yes, I would comment everything in that file for the moment, you can uncomment it later.
run apt-get update of course
 
@FaheemMitha yep it worked
@FaheemMitha debuild -uc -us
 dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor):
dpkg-buildpackage: export CXXFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export FFLAGS from dpkg-buildflags (origin: vendor): -g -O2
dpkg-buildpackage: export LDFLAGS from dpkg-buildflags (origin: vendor):
 
@trelosae Ok, again, I strongly recommend doing the source download and build while not root.
 
@FaheemMitha allright i'll try as another user
 
1:18 AM
try running apt-get build-dep mpd, or you can just install those manually with apt-get.
@trelosae just try as your regular user.
which directory are you in?
 
@FaheemMitha /usr/local/src/mpd/mpd-0.17.6
 
@trelosae Ok, you should add yourself to the staff group, then you will be able to write there.
you need to log out first, possibly, to make it take effect.
@trelosae i'm probably going to go back to sleep soon, so may not seen further messages immediately. but should see chat messages etc. later today, and will answer them.
 
@FaheemMitha alright see ya
 
@trelosae It is worth mentioning those extra lines in sources.list.d in your answer, when you write one.
 
@FaheemMitha will do
 
1:22 AM
@trelosae dpkg-dev (>= 1.16.1~) is probably not necessary.
just remove the dependency from the build line in debian/control in the source.
it is possible it is necessary, in which case it will error out.
 
@FaheemMitha what about dh-systemd
 
@trelosae Not sure about that.
you could try backporting it to squeeze. you got the wheezy version to build, right? 1.16?
 
funny thing is there is no package dh-systemd
 
yes, Build-Depends: debhelper (>= 8.0.0), perl so should be buildable at least
@trelosae apt-cache showsrc dh-systemd
@trelosae how to you mean, no package dh-systemd?
 
oh it doesnt exist for squeeze
 
1:28 AM
@trelosae right. so you will have to backport it.
it is just a script, so should be easily buildable. the runtime dependencies also don't seem to be a problem.
 
indeed
 
systemd is itself not in squeeze, do i don't know if that will cause a problem
but you could try it.
 
let's hope so
 
ok, off now.
 
 
2 hours later…
3:43 AM
@FaheemMitha dpkg-checkbuilddeps, it has 2 d s. Definitely not a newer version, I have it on a sarge box. Comes from dpkg-dev.
Did I mess that up on my answer...?
@FaheemMitha yes, you can print the whole sources.list (not in the normal format, though) by just running apt-cache policy
@FaheemMitha lists.debian.org/debian-devel-announce/2011/09/msg00001.html ... beware those changes when removing that dependency.
@FaheemMitha @trelosae I'd suggest just grabbing the newer dpkg-dev from squeeze-backports packages.debian.org/squeeze-backports/dpkg-dev
@FaheemMitha @trelosae I think you can just remove the dependency on dh-systemd, and remove the call in debian/rules. If you look at what it does (see packages.debian.org/sid/dh-systemd)... it's clear you don't need that at all squeeze.
Though if you want, you don't need to backport it—you could just download and install the version from sid. The dependencies should be satisfied (it depends on debhelper and perl, both unversioned).
It may not work, if it wants a perl newer than 5.8 (or was it 5.6?) that's in squeeze
In that case, you'd potentially have to do a lot of work to backport it.
(I would advise against attempting to backport perl. Too central.)
@FaheemMitha (fixed my answer to spell dpkg-checkbuilddeps right)
 
 
1 hour later…
5:11 AM
@derobert thanks for all the helpful hints.
I don't know if @trelosae will see them. if he doesn't respond, you could add them as a comment to the question.
I don't get the reference to perl. Where is a newer pert required?
 
@FaheemMitha If you grab the dh-systemd package from sid, its possible that it actually requires a perl newer than in squeeze
The dependencies don't say so, but you never know...
I think trelosae will see those messages, as I pinged him/her in one of them.
 
@derobert I see. It does sound like removing the depndency on dh-systemd is best.
 
Definitely what I'd attempt first. There is no systemd in squeeze, after all.
Though it's best not to talk about systemd. Might draw profanity-laden death threats.
... at least, it does on debian-devel :-(
 
@derobert heh. Ok, off to yoga class. take care everyone.
 
/me has stuff to get done this weekend, or he'd contemplate switching his machine to systemd.
 
5:27 AM
@derobert Watch out for those profanity-laden death threats. :-)
 
 
2 hours later…
7:56 AM
Still need one more reopen vote for
2
Q: Installing mpd 0.17 on debian squeeze

trelosaeHow could I install mpd 0.17 or even 0.16 on debian squeeze? It's been suggested to me that I should use backports, but I did not quite understand what I should do in case of unmet dependencies. For instance, mpd 0.17 exists on wheezy-backports but it depends on libraries that are a greater versi...

anyone?
 
 
1 hour later…
9:03 AM
@trelosae your question has now been reopened.
My recollection is that there is some utility that will run an install for packages in the build-depends in the control file. I think there was even a question about it here. Does anyone remember?
 
 
4 hours later…
1:08 PM
Are there any distros that are almost always in sync with the latest stable kernel?
 
@AsheeshR Not sure what you mean. You can install any kernel you like on most distributions. If you mean the default kernel, the answer almost by defn is no, unless it is a real moving target, like debian sid.
sid probably has a very recent kernel most of the time.
 
and Arch, right @strugee?
 
slm
arch yes
 
apt-cache policy linux-image-amd64
for example
shows 3.13+56 for unstable
@Braiam what about arch?
i guess gentoo probably uses pretty recent kernels too.
 
slm
5
A: What is the prefered way of updating all software in a Fedora installation?

slmBefore Fedora 17 None of the Red Hat distros prior to Fedora 17 included the ability to do dist-upgrades as you've asked. This had been a long discussed option on many peoples' wish list but had never been implemented. But before we start a clarification... According to the Upgrading topic ...

I talk about the different types of releasing in that QA
rolling vs. release #
 
1:14 PM
i suggest we vote up @casey's answers. he is quite close to 3000, and then he can do open/close votes.
 
slm
on it
 
@Braiam see my question above.
My recollection is that there is some utility that will run an install for packages in the build-depends in the control file. I think there was even a question about it here. Does anyone remember?
this is if you are in a debian source directory.
@slm i think that is probably enough. too much from one person, and they might roll it back
Wow, incoherent much?
0
Q: How to use virtualbox?

RIPI Have Virtual box and I want to make a backup of it!How to use virtual?i have virtual-box and i want to make a backup of it!` How to use virtual?

Oh, that's what fedup means. I thought it meant people were fed up of Red Hat. Maybe some kind of mass movement of people wanting to move to Linux Mint.
@slm Your answer does not actually give an example of a rolling release.
@slm don't mean to bug you, but would be interested in learning how RH like distributions build binary kernel packages. We talked about this earlier. I might get around to a formal answer this weekend.
I just wrote an annoyed letter to Debian's ftpmasters about them not replying to me about my rejection from NEW last year. Maybe I'll get banned from Debian...
 
 
2 hours later…
slm
3:20 PM
@FaheemMitha How do you mean? Do you want me to write up how to build a binary linux kernel pkg on Fedora? It's actually pretty straightforward
@FaheemMitha I thought I included a link to a list of releases and their types
 
@slm Yes. Unless it is well documented elsewhere, i which case i guess you could post a link.
@slm Ok, I forget the url.
 
slm
This page provides general information about notable Linux distributions in the form of a categorized list. Distributions are organized into sections by the major distribution they are based on, or the package management system they are based around. Debian-based Debian GNU/Linux is a distribution that emphasizes free software. It supports many hardware platforms. Debian and distributions based on it use the .deb package format and the dpkg package manager and its frontends. {| class="wikitable" |- ! Distribution !! Description |- | 64 Studio | Attempts to specialize in audio and video...
The ones that are rolling say so in the descriptions
They're listed in this link which is my A
In software development, a rolling release or rolling update development model refers to a continually developing software system; this is instead of a standard release development model which uses software versions that must be reinstalled over the previous version. Rolling software, instead, is continually updated, in contrast to standard release software which is upgraded between versions. Rolling release development models are one of many types of software release life cycles and, in terms of software development methodology in general, rolling release development models are less commo...
 
3:36 PM
@slm Ok, I stand corrected.
 
4:20 PM
@FaheemMitha hey are you there?
 
@trelosae Yes. For the moment. Did you see @derobert's comments?
 
@FaheemMitha yes i wanted to ask about that
what should i remove from debian/rules?
would this be enough: LDFLAGS += -Wl,--as-needed

%:
        dh $@ --with autoreconf
#       dh $@ --with autoreconf --with=systemd
 
@trelosae probably
is there any other mention of systemd?
 
there is libsystemd-daemon but i have commented it out on the control file
 
@trelosae Ok. the rules file is just
LDFLAGS += -Wl,--as-needed
dh $@ --with autoreconf --with=systemd
?
 
4:24 PM
no there is a lot more
 
@trelosae Ok. This is the rules file for the wheezy backport?
 
yes
 
@trelosae one sec. i'll take a look
 
#!/usr/bin/make -f
include /usr/share/dpkg/architecture.mk

WITH_TREMOR=
ifeq ($(DEB_HOST_ARCH), arm)
WITH_TREMOR=--with-tremor
endif
ifeq ($(DEB_HOST_ARCH), armel)
WITH_TREMOR=--with-tremor
endif
ifeq ($(DEB_HOST_ARCH), armeb)
WITH_TREMOR=--with-tremor
endif

ENABLE_FFADO=
ifeq ($(DEB_HOST_ARCH), amd64)
ENABLE_FFADO=--enable-ffado
endif
ifeq ($(DEB_HOST_ARCH), armel)
ENABLE_FFADO=--enable-ffado
endif
ifeq ($(DEB_HOST_ARCH), armhf)
ENABLE_FFADO=--enable-ffado
endif
ifeq ($(DEB_HOST_ARCH), i386)
that's it
 
you'll also want to take out $(WITH_SYSTEMD) from
./configure $(WITH_TREMOR) $(WITH_SYSTEMD) $(ENABLE_FFADO) \
            --enable-sqlite \
also, the last line - $(CP_SYSTEMD_UNIT)
should probably go
those three things will probably suffice. give it a try
i'd put the debian directory under version control if you are messing with it
 
4:31 PM
svart@nibelung:/usr/local/src/mpd/mpd-0.17.6$ sudo debuild -uc -us
 dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: source package mpd
dpkg-buildpackage: source version 0.17.6-1~bpo70+1
dpkg-buildpackage: source changed by Florian Schlichting <fsfs@debian.org>
 dpkg-source --before-build mpd-0.17.6
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with autoreconf
   dh_testdir
   dh_auto_clean
 
delete mpd-0.17.6/config.log
did you create that?
 
nope
 
hmm. that's not good
what does config.log have?
i can try building it here. one sec
 
remove it and unpack it again... the build directory is dirty...
 
@trelosae you can just try removing that one file and repeating.
seems to be building here. of course, this is wheezy
 
4:38 PM
@FaheemMitha removing config.log? it failed again
 
@trelosae Error, please
what did you remove from debian/control, if anything?
 
svart@nibelung:/usr/local/src/mpd/mpd-0.17.6$ sudo debuild -uc -us
 dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: warning: using a gain-root-command while being root
dpkg-buildpackage: source package mpd
dpkg-buildpackage: source version 0.17.6-1~bpo70+1
dpkg-buildpackage: source changed by Florian Schlichting <fsfs@debian.org>
 dpkg-source --before-build mpd-0.17.6
dpkg-buildpackage: host architecture amd64
 fakeroot debian/rules clean
dh clean --with autoreconf
   dh_testdir
   dh_auto_clean
 
@trelosae I don't see a build happening. It skipped direct to the install Something went wrong
@Braiam ?
Here is my diff to rules.
 
his build tree is dirty, is better if he removes everything and unpack everything again
 
diff -r e157a318213c rules
--- a/rules
+++ b/rules
@@ -41,9 +41,11 @@
LDFLAGS += -Wl,--as-needed

%:
- dh $@ --with autoreconf --with=systemd
+ #dh $@ --with autoreconf --with=systemd
+ dh $@ --with autoreconf

override_dh_auto_configure:
+ #./configure $(WITH_TREMOR) $(WITH_SYSTEMD) $(ENABLE_FFADO) \
./configure $(WITH_TREMOR) $(WITH_SYSTEMD) $(ENABLE_FFADO) \
--enable-sqlite \
--enable-un \
@@ -79,4 +81,4 @@
override_dh_install:
dh_install
cp $(CURDIR)/debian/mpd.tmpfiles $(CURDIR)/debian/mpd/usr/lib/tmpfiles.d/mpd.conf
@Braiam fair enough.
 
4:42 PM
should i just do what @Braiam said?
 
@trelosae yes. just delete the directory you are using. then you can unpack again doing
dpkg-source -x whatever.dsc
whatever being -> mpd_0.17.6-1~bpo70+1.dsc
did you change anything in the control file. i didn't, and it doesn't seem necessary
 
i had commented out the libsystemd-daemon
 
@trelosae Ok. me too. in the build depends? actually i removed it entirely.
i recommend you do that. but first put your debian directory under version control
 
how do i do that
 
@trelosae Have you not used version control? hg, git?
 
4:47 PM
barely, i wanted to clone some github repos once
 
@trelosae Ok, in that case, never mind. just make a copy of any file before changing it. something like filename.orig would do.
 
alright
alright now in the control file i remove libsystemd-daemon, correct?
 
@trelosae right. and also dh-systemd (>= 1.4)
 
weird when i edited the control file libsystemd was already commented out
let me re-delete the folder
 
@trelosae Ok, that means that the orig tarball was possibly rebuilt, which you don't want
remove everything and start from scratch
 
4:52 PM
ok
 
and this time, change the changelog before you proceed
that will prevent overwrites. i forgot to mention that
 
oh yea i forgot about that
 
do dch -i in the source directory. this will create a new changelog entry for you, which you can modify
actually, it was probably the diff that got overwritten.
 
@FaheemMitha okey i have removed libsystemd-daemon and dh-systemd from control and the three lines from the rules. anything else?
 
5:09 PM
@trelosae you mean you changed the lines, not removed them, right?
what is diff -u rules.orig rules ?
 
44c44
<       dh $@ --with autoreconf --with=systemd
---
>       dh $@ --with autoreconf
47c47
<       ./configure $(WITH_TREMOR) $(WITH_SYSTEMD) $(ENABLE_FFADO) \
---
>       ./configure $(WITH_TREMOR) $(ENABLE_FFADO) \
82c82
<       $(CP_SYSTEMD_UNIT)
---
>
 
@trelosae yes, that looks ok. but that looks like the output from diff rather than diff -u.
did you add an entry to the changelog?
 
yes i did
 
@trelosae ok, then. i guess you are good to go.
 
@FaheemMitha seems to be compiling
 
5:15 PM
@trelosae good
 
svart@nibelung:/usr/local/src/mpd$ sudo dpkg -i mpd_0.17.6-1~bpo70+2.local_amd64.deb
(Reading database ... 60636 files and directories currently installed.)
Preparing to replace mpd 0.17.6-1~bpo70+2.local (using mpd_0.17.6-1~bpo70+2.local_amd64.deb) ...
Unpacking replacement mpd ...
Setting up mpd (0.17.6-1~bpo70+2.local) ...
Starting Music Player Daemon: mpdmkdir: cannot create directory `/run/mpd': No such file or directory
chown: cannot access `/run/mpd': No such file or directory
Failed to bind to '127.0.0.1:6600': Address already in use
i have removed the previous mpd and redid that but the output is the same
 
@trelosae hmm, looks like it is trying to do some systemd like thing.
 
@FaheemMitha now what?
 
actually, that is just a guess. i don't know a thing about systemd, but it seems at least plausible
@trelosae not sure. one sec
Looks like the problem may be mpd.init.d
I dunno. If i knew something about systemd i might be of more help
@Braiam any ideas?
 
mpd seems to be installed though
 
5:25 PM
@trelosae not properly, probably
what does
dpkg -l mpd give?
Your problem is probably:
Starting Music Player Daemon: mpdmkdir: cannot create directory `/run/mpd': No such file or directory
 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-===================-===================-======================================================
iF mpd 0.17.6-1~bpo70+2.lo Music Player Daemon
 
@trelosae Right, the second flag should be i. so
ii ...
instead you have iF.
which means unpacked i think
 
@trelosae remove it and install it again...
 
See man dpkg-query
@Braiam What good will that do?
 
btw, why you don't have /run/mpd?
 
5:27 PM
@Braiam presumably some systemd thing?
 
if that's for the pid it was previously in /var/run/mpd
 
i don't have run anything in the deb i built here.
 
nah, is not configured, so remove it or run sudo dpkg --configure -a
 
@Braiam but it errored out.
with that run error.
 
@FaheemMitha because isn't configured...
 
5:29 PM
@Braiam Well, it didn't get configured because it errored out. :-)
 
svart@nibelung:/usr/local/src/mpd$ sudo dpkg --configure -a
Setting up mpd (0.17.6-1~bpo70+2.local) ...
Starting Music Player Daemon: mpdmkdir: cannot create directory `/run/mpd': No such file or directory
chown: cannot access `/run/mpd': No such file or directory
Failed to bind to '127.0.0.1:6600': Address already in use
no message buffer overruns
 failed!
invoke-rc.d: initscript mpd, action "start" failed.
dpkg: error processing mpd (--configure):
 subprocess installed post-installation script returned error exit status 1
 
@trelosae anyway, give what he says a try. i don't have better ideas.
right, same error as before. that is what i would expect
 
wait...
> mpdmkdir: cannot create directory
why?
 
well there is no /run dir
 
@Braiam yes. is that some systemd thing?
 
5:31 PM
... I see a slight problem then...
 
I have a /run directory here.
 
if i symlinked /run to /var/run?
 
on wheezy.
and apparently i have systemd installed as well, at least libsystemd-daemon0
 
@trelosae is /var/run a tmpfs?
 
how can i check that?
 
5:33 PM
mount | grep run
 
it didn't return anything
 
it should look something like
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1637004k,mode=755)
@trelosae what is your mount output?
 
/dev/sde2 on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw)
/dev/mapper/datavg-datalv on /media/1f8cf4f2-1590-48e6-b82c-46f70de24cc7 type ext4 (rw,noexec,_netdev,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0)
 
@trelosae your fallback option is to attempt a backport of systemd and build and install mpd without removing the systemd stuff. whether it will work, i dunno.
 
@FaheemMitha that seems really messy
 
5:40 PM
@trelosae yeah, it might be
ok, another possibility is to try using the mpd.init.d from the earlier wheezy package
that does use /var/run/mpd etc
 
that would go in /etc/init.d/ correct?
 
also the mpd.postinst
 
and then i would run dkpg --configure -a?
 
@trelosae No, it is in the debian directory. you would need to rebuild the deb
and then reinstall.
 
oh
 
5:44 PM
like i said, i'd replace the mpd.postinst also
 
well, i'll give it a try
 
unfortunately, there are no guarantees in this business, unless you are an expert, which i'm not
@Braiam what do you think?
@slm any opinion?
so to summarize, replace mpd.init.d and mpd.postinst in the debian directory with the ones from 0.16.7,
make a backup of the original files first. then rerun the build
 
run is created by base-files and initscripts
 
@Braiam but it is not present on his squeeze machine
it is not a systemd thing?
 
5:52 PM
@trelosae actually, another approach that would probably work here, is, since (amazingly) the Debian packaging has not applied any patches, would be do simply use the 0.17 tarball with the 0.16 packaging. this would probably work, with a little tweaking.
 
nope
 
in these cases, the patches are usually the main problem
 
@trelosae just make the symlinks ;)
sudo ln -s /run /var/run && sudo ln -s /run/lock /var/lock
 
@trelosae bad news. :-) the mpd.conf also uses /run.
 
i made the symlinks and now dpkg --configure -a gave me this:
svart@nibelung:/usr/local/src/mpd/mpd-0.17.6$ sudo dpkg --configure -a                                Setting up mpd (0.17.6-1~bpo70+2.local) ...
Stopping Music Player Daemon: mpd.
Starting Music Player Daemon: mpdFailed to open sqlite database '/var/lib/mpd/sticker.sql': unable to open database file
no message buffer overruns
 failed!
invoke-rc.d: initscript mpd, action "restart" failed.
dpkg: error processing mpd (--configure):
 subprocess installed post-installation script returned error exit status 1
 
6:02 PM
those the directory exist?
 
/var/lib/mpd exists but there is no sql file
 
@trelosae Hmm. let me try installing the backports mpd
yes, there is a sticker.sql created
Looks like this should get built by src/sticker.c, but it is not happening here for some reason.
src/sticker.c: ret = sqlite3_exec(sticker_db, sticker_sql_create, NULL, NULL, NULL);
 
do you have the sqlite3 libraries?
 
@Braiam who, me?
 
no i don't
 
6:11 PM
@Braiam It is not listed as a dependency though
no, i take that back
 
nvm libsqlite3-0 is installed it was in the dependencies
 
yeah, not sure what the problem is here, sorry.
i'm sure this is fixable, but you could spend more time on it. as i said earlier, the further away you get, the harder the backport. i never try more than across one release.
 
maybe i'll try with the mpd.init.d and mpd.postinst from 0.16
 
@trelosae The mpd.conf would probably also need to be replaced. if you look at it, it mentions /run.
looks like the maintainers have done quite a lot of work between 0.16 and 0.17. lots of changes
 
well /run is symlinked to /var/run now but i'll replace that as well
 
6:23 PM
@trelosae ok, then maybe you can leave it.
i'm not really sure on the best approach, sorry.
it looks like even if you installed systemd it wouldn't make any difference, like @Braiam said, the /run change doesn't really have anything to do with systemd.
probably if i was to pursue it further i'd start with the 0.16 packaging and the 0.17 tarball and tweak things as necessary. mpd probably hasn't changed much between 0.16 and 0.17.
but that could still involve a bit of work.
 
you mean the orig tarball from 0.17 and the debian tar from 0.16?
 
@trelosae correct.
 
i would rename the 0.16 debian tar to be the same name with the 0.17 deb tar and then dpkg-source -x, correct?
 
@trelosae you'd have to adjust the dsc file first. then try to unpack. one sec, let me see
yes, you could use the 0.17 dsc, but you'd have to replace the checksums for those of the 0.16 diff.gz.
then it would probably work
 
6:39 PM
Hello all.
I'm having really bad installation problems- I don't know what to do next.
I've been bouncing between installing windows 7 and ubuntu, and now the windows installation only says I have 465 harddrive space- the ubuntu one says I have 500 but it won't install properly, and also sometimes says there are existing GPT partitions.
I'm currently loaded into system rescue cd... but I don't know what to do
 
@trelosae unfortunately, it doesn't look that easy to apply the diff.
The source format changed between the 0.16 and 0.17 packages
 
ppr
2
Q: How can I install tactile audio keys on my latitude?

pprI have a Dell latitude 6430u which has three tactile keys for mute/audio decrease/audio increase. On debian (sid), either with xfce or gnome, these keys don't work well. The mute key has never work. The two others work sometimes, but not well (I have to press twice, sometimes nothing happens, .....

 
@FaheemMitha what else could I try
 
@trelosae replacing those three files in the debian directory as we discussed earlier is worth a shot probably. hard to say what problems you'll run into.
 
6:54 PM
okay i'll give it a shot now
 
it should at least build, since those files are not involved in the build process. the problem with the sql file i don't really know. if you really want to spend more time on it (which I don't recommend) i'd probably talk to the debian devs of the package, and/or the upstream devs
but you are talking a fair amount more effort. do you really need 0.17?
 
i could realy use 0.17. i am really tempted to switch to vanilla debian wheezy at this point
 
@trelosae Oh. what is stopping you? the proprietary package you have installed?
 
welll it ships as a distro actually and from what i've seen it isn't that easy to upgrade to wheezy
 
00:00 - 19:0019:00 - 21:00

« first day (1239 days earlier)      last day (3706 days later) »