jak2000 2017-01-30 08:58:38
my fiel system was mounted as readonly......
jak2000 2017-01-30 08:58:43
*file
somiaj 2017-01-30 08:59:04
sounds like it encountered an error and needs to be fsck'ed
jak2000 2017-01-30 08:59:11
i want reboot the system: and cant because: sudo: "unable to open /var/lib/sudo/ts/jak: Read-only file system"
jak2000 2017-01-30 08:59:13
why?
somiaj 2017-01-30 09:00:47
it wants to write something there, just use 'su' to become root (you know your root password)?
jelly 2017-01-30 09:06:21
jak2000: sometimes the kernel detects a serious error on a filesystem and remounts it read-only to prevent further damage. Look at dmesg for clues.
somiaj 2017-01-30 09:18:26
jak2000: I'm kinda surprised sudo failed, but sudo writes a timestamp for your user (so you don't have to type the password each time) and it is failing to write this timestamp -- though I would like to think sudo would still work, just ask you for the password next time.....
velix 2017-01-30 09:24:16
What's a good way to build packages and backport on my own system (not for distribution)? I'm currently using a chroot with schroot as a build environment, but some guys told me to use sbuild oder pbuilder or cowbuilder or docker... What a mess. Actually, I don't like 100% automatic processes, since I often need to change configs manually. Can anyone recommend me a workflow? Please don't link me to debian.org or ubuntu ... I know all those wiki
velix 2017-01-30 09:24:16
entries.
jelly 2017-01-30 09:25:25
velix: if you manage to figure it out, make a better wiki page please.
somiaj 2017-01-30 09:26:24
velix: If i really need a clean build enviorment I just use debootstrap + chroot and manaully create a build enviorment.
somiaj 2017-01-30 09:26:31
velix: I personally use pbuilder
somiaj 2017-01-30 09:26:50
velix: as that was the tool I was directed too, pbuilder login is nice because then you can manually build the package in a chroot
velix 2017-01-30 09:27:49
hmm hmm
velix 2017-01-30 09:27:57
I think, I have to test them all ...
somiaj 2017-01-30 09:28:45
the wiki on pbuilder has a nice config, I can just do things like DIST=stretch ARCH=i386 pbuilder foo, and now i'm using a stretch chroot, also works for ubuntu chroots.
jelly 2017-01-30 09:29:25
somiaj: what about automated dch entries with ~0somiaj1 appended
somiaj 2017-01-30 09:29:29
sbuild is what gets used to build debian packages and some suggest just using that as the main tool. Though I've also seen articles that like both exist, as it gives some compention and as one tool gains a feature, the other tool adopts, etc...
nkuttler 2017-01-30 09:30:05
hm, when i send an email to a bug report, am i automatically subscribed?
somiaj 2017-01-30 09:30:28
nkuttler: as a reply or as the person who created the bug report?
nkuttler 2017-01-30 09:31:48
somiaj: i just wrote to @bugs.debian.org, so a reply i guess?
velix 2017-01-30 09:31:52
somiaj: does it support AUFS?
somiaj 2017-01-30 09:32:51
velix: not sure on that.
somiaj 2017-01-30 09:33:12
nkuttler: unsure on that, I know the original reporter is automatically subscribed, unsure about someone contributing to the report though.
missmbob 2017-01-30 09:33:35
nkuttler: no
nkuttler 2017-01-30 09:34:19
missmbob: ok. just wondering because i received a duplicate
nkuttler 2017-01-30 09:34:36
(and i subscribed to the bug in a separate step)
micw 2017-01-30 09:37:40
hi
micw 2017-01-30 09:38:01
i run stretch on my laptop. upgrade today to kernel 4.9.0 destroyed zfs-dkms :-/
micw 2017-01-30 09:38:37
http://pastebin.com/XCCf0yzc
missmbob 2017-01-30 09:38:39
try them
missmbob 2017-01-30 09:38:43
!debian-next
dpkg 2017-01-30 09:38:43
#debian-next is the channel for testing/unstable support on the OFTC network (irc.oftc.net), *not* on Freenode. If you get "Cannot join #debian-next (Channel is invite only)." it means you did not read it's on irc.oftc.net.
micw 2017-01-30 09:39:08
sure, thx
micw 2017-01-30 09:39:18
invite only?
nkuttler 2017-01-30 09:39:31
micw: oftc
micw 2017-01-30 09:39:43
i see
somiaj 2017-01-30 09:40:44
micw: did you make sure the linux-headers for the 4.9 kernel were also installed? If so check the dkms logs and see why the module did'nt build against that kernel.
tabakhase 2017-01-30 09:42:54
uhm, export -f function works fine on one system - and fails misserably on the other...
