Search Debian Channel Logs

Monday, March 6, 2017

#debian channel featuring jelly, Yamato, Kelebor, dury, PryMar56, laja,

jelly 2017-03-06 06:45:20
!debian-next
dpkg 2017-03-06 06:45:20
#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.
kfogel 2017-03-06 06:45:26
jelly: (let me clarify: on my own boxes, I run a dist-upgrade literally daily. This is not my own box.)
jelly 2017-03-06 06:45:44
then, you shouldn't run testing on "not your own box"
dury 2017-03-06 06:45:51
jelly, see that where? on the net or just type in terminal
kfogel 2017-03-06 06:45:59
jelly: (it's rare that I have to use dpkg itself, so questions like "How to determine the Debian version number of an installed package?" do not have an automatic index in my mind, though I suppose I would puzzle it out eventually :-) )
jelly 2017-03-06 06:46:02
dury: type in irc, get message from bot
dury 2017-03-06 06:46:23
ok
jelly 2017-03-06 06:46:31
kfogel: that's a clue you shouldn't be usng testing, too :-)
kfogel 2017-03-06 06:47:54
jelly: I appreciate the help you have given me so far -- not sarcastic there at all, in case tone doesn't come through in IRC -- but in generally I think you'd have to know a lot more about a person's circumstances before giving blanket advice like that. Debian 'testing' has worked out very well as a production env for me for a very, very long time, and I evaluated the costs and benefits pretty carefully.
jelly 2017-03-06 06:47:55
kfogel: I'd restore that machine from backup if possible; if not, switch the repositiories to "stretch" instead of "testing" and try to fix the most obvious breakages
jelly 2017-03-06 06:48:54
kfogel: and it might work for you, but as you can see, it fails badly when you're dealing with a system using a... different update frequency
kfogel 2017-03-06 06:49:32
jelly: yes. We decided to have a more frequent upgrade policy for this box, for exactly that reason. However, today is the first day of that upgrade policy :-). So, we expected today to be... problematic.
kfogel 2017-03-06 06:50:18
jelly: (I did not have dictatorial sysadmin powers on this box; if I had, there would have been very frequent dist-upgrades, you can bet!)
jelly 2017-03-06 06:50:25
if you join #debian-next (over on irc.oftc.net) you'll get help more appropriate for testing. Here, I have to keep in mind other people are reading and expound on best practices
dury 2017-03-06 06:50:40
I don't know what to do though
jelly 2017-03-06 06:50:51
kfogel: keeping "stable" or "testing" in sources.list is... not the best practice :-)
hanasaki 2017-03-06 06:51:03
in what directory should admin added systemd .service files be put?
kfogel 2017-03-06 06:51:09
jelly: ah, it's on irc.oftc.net -- I mindlessly tried to join it here on Freenode and got invite-only error of course. But that's b/c it was the wrong server. I'll head over there. Thanks for your help so far.
dury 2017-03-06 06:51:21
better wired pcmcia though
jelly 2017-03-06 06:51:33
dury: that might work out of the box yes
Yamato 2017-03-06 06:51:55
credit card
dury 2017-03-06 06:52:09
which brand
jelly 2017-03-06 06:52:16
dury: did you get a message from dpkg bot?
dury 2017-03-06 06:52:27
yeah
dury 2017-03-06 06:53:50
jelly, one this info https://wiki.debian.org/acx#Firmware
dury 2017-03-06 06:53:58
and...
dury 2017-03-06 06:54:27
this one https://sourceforge.net/projects/acx100/
PryMar56 2017-03-06 06:54:56
hanasaki, man systemd.unit
jelly 2017-03-06 06:55:22
dury: sorry, someone else will have to jump in, I'm busy and away from keyboard
dury 2017-03-06 06:55:41
jelly no rush
hanasaki 2017-03-06 06:55:54
PryMar56: thanks
Kelebor 2017-03-06 06:58:28
hi
asarch 2017-03-06 06:59:27
"There is 1 newly obsolete package: linux-image-4.9.0-0.bpo.1-amd64-unsigned" <- What does it mean?
hanasaki 2017-03-06 07:08:16
PryMar56: so it looks like they should be in /etc/systemd/user/*
hanasaki 2017-03-06 07:08:16
however the service is not found after creation. not even with a daemon reload
laja 2017-03-06 07:09:39
Hello. curl https://facebook.com works, but wget https://facebook.com hangs intermittently at "Connecting to www.facebook.com..." It's weird. For several hours at a time, wget will work, then for several hours it will always hang.
laja 2017-03-06 07:13:16
Lynx also fails to load https://www.facebook.com. Other computers on the same network don't have an issue.
PryMar56 2017-03-06 07:14:55
hanasaki, /etc/systemd/system is a better choice. To see what failed, systemctl status myservice.service or tail journalctl
hanasaki 2017-03-06 07:17:52
PryMar56: why is /etc/systemd/system better?
PryMar56 2017-03-06 07:18:13
hanasaki, are you trying to start the service with --user switch?
hanasaki 2017-03-06 07:28:09
PryMar56: nope. installing a java applicaitno that runs as a server and want it to autostart on boot under a user ID. runs on a high number port