Reassigning to QA Team

pdns-4.0.4-1.mga6
pdns-recursor-4.0.6-1.mga6

Assignee: bugsquad => qa-bugs

This already needs a security update:
http://openwall.com/lists/oss-security/2017/11/27/1

Keywords: (none) => feedback

Done

pdns-4.0.5-1.mga6
pdns-recursor-4.0.7-1.mga6

Source RPM: pdns-4.0.4-1.mga6.src.rpm, pdns-recursor-4.0.6-1.mga6.src.rpm => pdns-4.0.5-1.mga6.src.rpm, pdns-recursor-4.0.7-1.mga6.src.rpm

Updated pdns to the latest version

pdns-4.1.0-1.mga6
pdns-recursor-4.0.7-1.mga6

Source RPM: pdns-4.0.5-1.mga6.src.rpm, pdns-recursor-4.0.7-1.mga6.src.rpm => pdns-4.1.0-1.mga6.src.rpm, pdns-recursor-4.0.7-1.mga6.src.rpm

Please don't push until pdns-recursor is updated to 4.1.0

Done, please push

pdns-4.1.0-1.mga6
pdns-recursor-4.1.0-1.mga6

Source RPM: pdns-4.1.0-1.mga6.src.rpm, pdns-recursor-4.0.7-1.mga6.src.rpm => pdns-4.1.0-1.mga6.src.rpm, pdns-recursor-4.1.0-1.mga6.src.rpm

MGA6-32 on Dell Latitude D600 MATE
No installation issues
Googling for tutorials gave me some like http://www.servermom.org/install-powerdns-dns-server-ubuntu/, but all mention that pdns can run against bind files, but all proceed then with mysql configurations. There is no way this light laptop could pull that. But I managed to get useful feedback from commands like dnsdomainname
nsec3dig
sdig
all retrieving correct info from my own dns bind server in my network.
If the high powers approve, I will not object to OK this.

CC: (none) => herman.viaene

Reading further on pdns  https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-powerdns-with-a-mariadb-backend-on-ubuntu-14-04 , it seems one really needs poweradmin to get anywhere with pdns, but that package is not yet in our repos???

Herman,

PowerAdmin is purely optional, like phpMyAdmin, phpLdapAdmin etc. PowerDNS can be controlled fully via command line, configuration files and the database. And BTW neither is it packaged for Ubuntu, which the tutorial is based on.

And thanks for your work on testing the package! :)

For M6/64
 https://bugs.mageia.org/show_bug.cgi?id=20127#c2
Gives a cheap & cheerful test originally from Claire.

Wanting to test this, I am having mirror trouble. I need to install pdns & pdns-recursor, and cannot find them in my previous mirror, nor after having changed it. Will reboot to see if that helps.

CC: (none) => lewyssmith

Lewis,

The packages are in the updates_testing repository, probably you've forgotten to enable it?

urpmi.update --no-ignore "Core Updates Testing"

I've checked my nearest mirror (http://mirror.yandex.ru/mageia), the packages are there.

Thank you Dimitri.

Testing M6/64

I have found the problem. These 2 pkgs are *not* [yet] in issued repos:

# urpmi pdns pdns-recursor      [normal repos]
Dim pecyn o'r enw pdns          [no such package]
Dim pecyn o'r enw pdns-recursor [no such package]

# urpmi --searchmedia "Core Updates Testing" pdns pdns-recursor
I fodloni dibyniaethau, gosodir y pecynnau canlynol:
  Pecyn                          Fersiwn      Rhifyn        Arch    
(cyfrwng "Core Release2")
  lib64boost_chrono1.60.0        1.60.0       6.mga6        x86_64  
...
(cyfrwng "Core Updates Testing")
  pdns                           4.1.0        1.mga6        x86_64  
  pdns-recursor                  4.1.0        1.mga6        x86_64  
Defnyddir 26MB o le ychwanegol ar y disg.
Estynnir 5.1MB o becynnau.
Parhau i osod 7 o becynnau? (Y/n) y

    $MIRRORLIST: media/core/release/lib64boost_program_options1.60.0-1.60.0-6.mga6.x86_64.rpm
...
 $MIRRORLIST: media/core/updates_testing/pdns-4.1.0-1.mga6.x86_64.rpm       
 $MIRRORLIST: media/core/updates_testing/pdns-recursor-4.1.0-1.mga6.x86_64.rpm

Because of this - we seem to be offering updates for as yet unissued packages - I am going to ask for 'feedback'.
--------------------------------
Testing: pdns-4.1.0-1.mga6  pdns-recursor-4.1.0-1.mga6  M6/64
as per the reference in Comment 10.

# systemctl stop dnsmasq
Failed to stop dnsmasq.service: Unit dnsmasq.service not loaded. [OK]
# systemctl start pdns
# systemctl start pdns-recursor
 # systemctl -l status pdns-recursor
● pdns-recursor.service - PowerDNS Recursor
   Loaded: loaded (/usr/lib/systemd/system/pdns-recursor.service; enabled; vendo
   Active: active (running) since Llu 2017-12-25 18:59:51 CET; 5min ago
     Docs: man:pdns_recursor(1)
           man:rec_control(1)
           https://doc.powerdns.com
 Main PID: 18844 (pdns_recursor)
   CGroup: /system.slice/pdns-recursor.service
           └─18844 /usr/sbin/pdns_recursor --daemon=no --write-pid=no --disable-
...
... Listening for TCP queries on 127.0.0.1:5300
correct; but NO similar line for UDP as in previous tests.

 # netstat -pantu | grep pdns
tcp        0      0 127.0.0.1:5300          0.0.0.0:*               LISTEN      18844/pdns_recursor 
tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      18681/pdns_server   
tcp6       0      0 :::53                   :::*                    LISTEN      18681/pdns_server   
udp        0      0 0.0.0.0:53              0.0.0.0:*                           18681/pdns_server   
udp        0      0 127.0.0.1:5300          0.0.0.0:*                           18844/pdns_recursor 
udp6       0      0 :::53                   :::*                                18681/pdns_server   
This looks correct re the reference, with IPv6 additions.

 $ dig mageia.org @127.0.0.1 -p 5300
; <<>> DiG 9.10.5-P2 <<>> mageia.org @127.0.0.1 -p 5300
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50280
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mageia.org.			IN	A

;; ANSWER SECTION:
mageia.org.		1800	IN	A	163.172.148.228

;; Query time: 343 msec
;; SERVER: 127.0.0.1#5300(127.0.0.1)
;; WHEN: Llu Rha 25 19:16:59 CET 2017
;; MSG SIZE  rcvd: 55

This accords with the example. Giving this the OK
Advisory made from comments 0 & 6, and bug RPMs link.
Can validate once the feedback is cleared.

Whiteboard: (none) => MGA6-64-OK
Keywords: (none) => advisory, feedback

Lewis,

Indeed, the packages are not present in the stable repository. PowerDNS was removed from Mageia 6 due to being unmaintained at that moment; later, we've decided to reintroduce it via updates.

I've talked to our packager gurus on IRC (Neal Gompa in particular), they say there's nothing wrong with such a reintroduction. Therefore, it shouldn't be considered a problem. Cheers and thanks for testing!

(In reply to Lewis Smith from comment #12)

> we seem to be offering updates for as yet unissued
> packages 

This seems to be in accordance with policy. See the fourth bullet point under "Version Policy":

https://wiki.mageia.org/en/Updates_policy#Version_Policy

CC: (none) => jim

(In reply to Dimitri Jakov from comment #13)
> Indeed, the packages are not present in the stable repository. PowerDNS was
> removed from Mageia 6 due to being unmaintained at that moment; later, we've
> decided to reintroduce it via updates.
> 
> I've talked to our packager gurus on IRC (Neal Gompa in particular), they
> say there's nothing wrong with such a reintroduction. Therefore, it
> shouldn't be considered a problem. Cheers and thanks for testing!
Thank you for confirmation of my suspicions.
In which case, I think this would normally be classed as a 'backport' - from what I have seen of these, they look like a way of [re-]introducing packages.
And if this is so, the advisory is redundant: backports do not have them. But the repository would need changing to Backports.

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2017-0132.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED