[DNG] Problem with the repository of Devuan

[aitor_czr]

Most packages disappeared from:

deb http://packages.devuan.org/merged jessie main
deb-src http://packages.devuan.org/merged jessie main

There is no live-build, no kernel, no grub...

Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Problem with the repository of Devuan

[Jaromil]

dear Aitor,

On Sun, 06 Sep 2015, aitor_czr wrote:
>Most packages disappeared from:
>deb [1]http://packages.devuan.org/merged jessie main
>deb-src [2]http://packages.devuan.org/merged jessie main
>There is no live-build, no kernel, no grub...

thanks for signaling that, nextime had a quick check and noticed this is
due to Debian repositories going through some updates. He is following
up monitoring the situation and triggering an update for Amprolla.

we can regard this situation as the sort of testing needed for our
server side of things, I'm confident in the future such glitches can be
avoided.

ciao

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Problem with the repository of Devuan

[Hendrik Boom]

On Sun, Sep 06, 2015 at 02:11:44PM +0200, aitor_czr wrote:
> Most packages disappeared from:
> 
> deb http://packages.devuan.org/merged jessie main
> deb-src http://packages.devuan.org/merged jessie main
> 
> There is no live-build, no kernel, no grub...
> 
> Aitor.

I noticed this morning that monotone was missing, but I guess there's
a more general problem.

That said, aptitiude update and aptitude safe-upgrade seemed to work properly.

I'm using

 deb http://ca.mirror.devuan.org/merged/ jessie main

deb http://ca.mirror.devuan.org/merged/ jessie main non-free contrib
deb-src http://ca.mirror.devuan.org/merged/ jessie main non-free contrib

deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free

# jessie-updates, previously known as 'volatile'
deb http://ca.mirror.devuan.org/merged/ jessie-updates main contrib non-free
deb-src http://ca.mirror.devuan.org/merged/ jessie-updates main contrib non-free


-- hendrik
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] netman, ifdown: interface wlan0 not configured

[fsmithred]

I've been testing netman and discussing it with edbarx on this thread at fdn -
http://forums.debian.net/viewtopic.php?f=3=124343=39afc987dc48172a6553bb0941d12461

netman connects but won't disconnect, and produces the following messages
in the terminal:

# click Disconnect first time:
Ignoring unknown interface wlan0=wlan0.

# click Disconnect second time:
ifdown: interface wlan0 not configured

If I try 'ifdown wlan0' in root terminal, I get the same messages. I have
to bring the interface down with 'ifconfig wlan0 inet down'.
And if I try running './backend 5' from /usr/bin/netman/ I get the same
messages.


Here's the output of 'ip a' under various circumstances (in order):

Interface down:
wlan0:  mtu 1500 qdisc pfifo_fast
state DOWN group default qlen 1000
link/ether 00:1f:33:82:e4:8b brd ff:ff:ff:ff:ff:ff

Connect with netman:
wlan0:  mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 00:1f:33:82:e4:8b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.101/24 brd 192.168.1.255 scope global wlan0
   valid_lft forever preferred_lft forever

Disconnect with netman:
wlan0:  mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 00:1f:33:82:e4:8b brd ff:ff:ff:ff:ff:ff
inet 192.168.1.101/24 brd 192.168.1.255 scope global wlan0
   valid_lft forever preferred_lft forever



My workaround (and quote from post on fdn)
ifup wants to see "allow" or "auto" associated with an interface. I tried
adding "allow-hotplug wlan0" to /etc/network/interfaces, but that didn't
help, so I removed it. Then I added it to the file in /etc/network/wifi
and added "source wifi/*" to interfaces, and that seems to fix the
problem. I can now connect and disconnect with the buttons in netman. And
'ifup/ifdown wlan0' works in root terminal now.

/etc/network/interfaces

auto lo
iface lo inet loopback

source wifi/*# I added this line


/etc/network/wifi/my-essid

auto lo
iface lo inet loopback

allow-hotplug wlan0   # I added this line
iface wlan0 inet dhcp
wpa-ssid my-essid
wpa-psk "my-secret-password"


Running devuan/angband/exegnu/jessie

-fsmithred

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] trollproof spec

[Jonathan Wilkes]

On 09/03/2015 07:40 AM, Jaromil wrote:

dear Jonathan,

On Thu, 03 Sep 2015, Jonathan Wilkes wrote:


I have a spec for "trollproofs" which might help with moderation.  Instead
of the moderator having a binary choice between "block" or "pass", he/she
can just choose a difficulty level for a particular topic which the
community adheres to in order to encourage good faith.

What you sketch exists already even before Bitcoin, is called Hashcash
and I have good reasons to think Satoshi Nakamoto knew it.  We did run
that on dyne/freaknet server back than as an experiment, pity it didn't
took off instead of the lame and centralized DKIM thing nowadays
everyone uses.

However I doubt hashcash can be regarded as something to defend from
trolls. After all, trolling is a art...


This uses Hashcash at its core, sure.  But where Hashcash tries to
be unobtrusive, trollproof is direct and ugly.  The point isn't to expend
as little energy as possible to keep email operational-- rather it's to
generate as much POW as possible so that the trolls decide not to
climb up to your level.  (Conversely, if you are a troll you can use it
to prove you're a pyschopath and not just someone wasting time
on a lunchbreak at the office.)

Here's a prototype to play with:

--- Begin TP Message ---
#!/bin/bash
# Here's a quick quine-like implementation of a trollproof message.
# Do a sha256sum of this message and you'll see five zeros at the
# beginning of the hash. Run this program on your computer yourself to
# get a sense of how long that takes.
#
# Unlike Hashcash, the idea is to use trollproofs within the social layer
# of the application. You can force your own provable waiting
# period before sending a testy email. Or you can prove to the rest of the
# list that you own a botnet. The sky's the limit.
#
# For the purposes of this list, I'd suggest using it to wrap your messages
# when systemd-related thread flames up. If none of the other apparently
# impassioned participants are willing to burn cpu cycles in solidarity with
# you then congratulations! You have proof of trolls.
#
# But beware-- if others are willing to play along it means you'll actually
# have to _read_ and _consider_ the responses from people who may think
# differently than you do. This will undoubtedly result in undefined 
behavior.

#
# Best,
# Jonathan
#
echo "Building a TP Message... please be patient..."
FILE=$(<"$0"); DATE=`date`
HEAD=`printf "%s\n%s" "--- Begin TP Message ---" "$FILE"`
HEAD+=`printf "\n%s\n%s" "--- Begin TP Work ---" "$DATE"`
FOOT=`printf "%s\n%s" "--- End TP Work ---" "--- End TP Message ---"`
POW=0; HASH=""; I=0
while [ "$POW" -eq "0" ]; do
HASH=`printf "%s\n%s\n%s\n" "$HEAD" "$I" "$FOOT" | sha256sum`
if [ "${HASH:0:5}" = "0" ]; then
let POW=1
else
let I=I+1
fi
done
echo "$HEAD"; echo "$I"; echo "$FOOT"
--- Begin TP Work ---
Sun Sep  6 00:35:42 EDT 2015
475976
--- End TP Work ---
--- End TP Message ---

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] netman, ifdown: interface wlan0 not configured

[Edward Bartolo]

Hi fsmithred,

I think, Disconnect was failing in your case with the default
configuration of netman's /etc/network/wifi/* files, for the reason,
that I assumed that ifdown would automatically find where the
currently used interfaces file was located.

Since ifup worked the way netman invoked it, I think, doing the same
for ifdown should do the trick also for you without having to modify
any 'interfaces' files on your system.

It will help me improve the project if you find some time to test this
while connected to wifi but using your previous versions of
/etc/network/interfaces and /etc/network/wifi/your-wifi-file. The
command is simply as follows:

# ifdown wlan0 -i /etc/network/wifi/your-wifi-file


Edward

On 06/09/2015, fsmithred  wrote:
> I've been testing netman and discussing it with edbarx on this thread at fdn
> -
> http://forums.debian.net/viewtopic.php?f=3=124343=39afc987dc48172a6553bb0941d12461
>
> netman connects but won't disconnect, and produces the following messages
> in the terminal:
>
> # click Disconnect first time:
> Ignoring unknown interface wlan0=wlan0.
>
> # click Disconnect second time:
> ifdown: interface wlan0 not configured
>
> If I try 'ifdown wlan0' in root terminal, I get the same messages. I have
> to bring the interface down with 'ifconfig wlan0 inet down'.
> And if I try running './backend 5' from /usr/bin/netman/ I get the same
> messages.
>
>
> Here's the output of 'ip a' under various circumstances (in order):
>
> Interface down:
> wlan0:  mtu 1500 qdisc pfifo_fast
> state DOWN group default qlen 1000
> link/ether 00:1f:33:82:e4:8b brd ff:ff:ff:ff:ff:ff
>
> Connect with netman:
> wlan0:  mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 00:1f:33:82:e4:8b brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.101/24 brd 192.168.1.255 scope global wlan0
>valid_lft forever preferred_lft forever
>
> Disconnect with netman:
> wlan0:  mtu 1500 qdisc pfifo_fast
> state UP group default qlen 1000
> link/ether 00:1f:33:82:e4:8b brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.101/24 brd 192.168.1.255 scope global wlan0
>valid_lft forever preferred_lft forever
>
>
>
> My workaround (and quote from post on fdn)
> ifup wants to see "allow" or "auto" associated with an interface. I tried
> adding "allow-hotplug wlan0" to /etc/network/interfaces, but that didn't
> help, so I removed it. Then I added it to the file in /etc/network/wifi
> and added "source wifi/*" to interfaces, and that seems to fix the
> problem. I can now connect and disconnect with the buttons in netman. And
> 'ifup/ifdown wlan0' works in root terminal now.
>
> /etc/network/interfaces
>
> auto lo
> iface lo inet loopback
>
> source wifi/*# I added this line
>
>
> /etc/network/wifi/my-essid
>
> auto lo
> iface lo inet loopback
>
> allow-hotplug wlan0   # I added this line
> iface wlan0 inet dhcp
> wpa-ssid my-essid
> wpa-psk "my-secret-password"
>
>
> Running devuan/angband/exegnu/jessie
>
> -fsmithred
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Problem with the repository of Devuan

[Franco Lanza]

On Sun, Sep 06, 2015 at 08:30:27PM +0200, Jaromil wrote:
> we can regard this situation as the sort of testing needed for our
> server side of things, I'm confident in the future such glitches can be
> avoided.


Technically this is what happened:

- we update amprolla at fixed interval ( 30 mins ), when it checks if
  something is changed on a configured debian mirror AND to the devuan
  package repository, suite by suite. If something is changed in a suite
  on one of the mirror monitored, it rebuild the /dists/ directory for
  this suite.

- As the server running amprolla is hosted in OVH, France, we use the
  OVH hosted debian mirror has it's (of course) fast and with very low
  latence for us.

- It seems that the OVH mirror is down, and amprolla doesn't manage this
  situation well, so, it take the unavailable files from the down mirror
  as a change where all packages aren't available anymore, and then it
  rebuild the merged repo with only the packages from other mirrors.

Actually i've manually reconfigured amprolla to use another debian
mirror and then start to rebuild the repo forcing the total rebuild, in
few minutes all will work as usual and expected.

In the long run, to avoid the repeating on the same issue, i will fix
amprolla to fallback to a secondary mirror in case the first one fail,
and then to abort operations if also the secondary is failing, maybe
dropping a notice/warning email to let us know immediatly that something
is going wrong.

Thanks to report the issue.


-- 

Franco (nextime) Lanza
Lonate Pozzolo (VA) - Italy
SIP://c...@casa.nexlab.it
web: http://www.nexlab.net
paypal: https://paypal.me/nexlab

NO TCPA: http://www.no1984.org
you can download my public key at:
http://danex.nexlab.it/nextime.asc || Key Servers
Key ID = D6132D50
Key fingerprint = 66ED 5211 9D59 DA53 1DF7  4189 DFED F580 D613 2D50
---
echo 
16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D212153574F444E49572045535520454D20454B414D204F54204847554F4E452059415020544F4E4E4143205345544147204C4C4942snlbxq
 | dc
---



signature.asc
Description: PGP signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Debian packages are missing from Devuan's merged repository

[Hendrik Boom]

It appears that devuan is having trouble accessing at least some
packages from debian repositories.

Evidence:

I can't install monotone, the distributed revision management tool I use.

A few minutes before I noticed I was unable to install monotone, 
I had done 
aptitude update
aptitude safe-upgrade
and it found the following list of packages to upgrade:

: The following packages will be upgraded: 
:   bind9-host dnsutils gir1.2-gdkpixbuf-2.0 google-chrome-stable host 
:   iceweasel libbind9-90 libdns-export100 libdns100 libgdk-pixbuf2.0-0 
:   libgdk-pixbuf2.0-common libirs-export91 libisc-export95 libisc95 
:   libisccc90 libisccfg-export90 libisccfg90 liblwres90 libnss3 libvlc5 
:   libvlccore8 vlc vlc-data vlc-nox vlc-plugin-notify vlc-plugin-pulse 
: 26 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

When I told it to go ahead, it went through the usual set of upgrade 
progress messagess, ending with:

: Setting up vlc-plugin-pulse (1:2.2.1-dmo1+cve1) ...
: Processing triggers for libc-bin (2.19-18) ...
:  
: Current status: 0 updates [-26].

So it looks as if that, at least, worked properly.

Are these all packages found in devuan's own repository?

Are packages that would need to be upgraded from debian's repository
simply ignored if devuan's 'merged' fails to find them, so they are neither
upgraded nor mentioned?

Or did the upgrade somehow make changes that interfere with
aptitude's ability to find packages?

I used dpkg and packages.debian.org for a workaround.

Links from packages.debian.org will eventually lead to a 
downloadable .deb file.  I ended up using dpkg to install both monotone 
and its dependency, libbotan.

Dependency tracking by hand could get quite tedious if there are a lot 
of them.  Not to mention that from now on, libbotan will be known as a 
package I asked for, and not as one installed as a dependency.

-- hendrik


On Sun, Sep 06, 2015 at 11:25:31AM -0400, Hendrik Boom wrote:
> On Sun, Sep 06, 2015 at 02:11:44PM +0200, aitor_czr wrote:
> > Most packages disappeared from:
> > 
> > deb http://packages.devuan.org/merged jessie main
> > deb-src http://packages.devuan.org/merged jessie main
> > 
> > There is no live-build, no kernel, no grub...
> > 
> > Aitor.
> 
> I noticed this morning that monotone was missing, but I guess there's
> a more general problem.
> 
> That said, aptitiude update and aptitude safe-upgrade seemed to work properly.
> 
> I'm using
> 
>  deb http://ca.mirror.devuan.org/merged/ jessie main
> 
> deb http://ca.mirror.devuan.org/merged/ jessie main non-free contrib
> deb-src http://ca.mirror.devuan.org/merged/ jessie main non-free contrib
> 
> deb http://security.debian.org/ jessie/updates main contrib non-free
> deb-src http://security.debian.org/ jessie/updates main contrib non-free
> 
> # jessie-updates, previously known as 'volatile'
> deb http://ca.mirror.devuan.org/merged/ jessie-updates main contrib non-free
> deb-src http://ca.mirror.devuan.org/merged/ jessie-updates main contrib 
> non-free
> 
> 
> -- hendrik
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng