Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Alexander Bochmann]

...on Wed, Jul 08, 2020 at 05:12:54PM +0200, Alexander Bochmann wrote:

 > ...on Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote:
 >  > Using the /dev/mapper device name would likely have been just as good, 
 > but I'm not sure as I didn't try that
 > I'll try if using UUIDs in the fstab makes a difference in the 
 > boot process later tonight (and maybe why, if it indeed does).

So yes, using a UUID for a split /usr mount (on lvm)
in the fstab totally doesn't work. I'm landing in the 
"Begin: Running /scripts/local-block ... done." loop too, 
ending with "ALERT! UUID= does not exist.
Dropping to a shell!"

I apparently changed my fstab from UUIDs to the /dev/mapper 
symlinks some time in 2019, way before my upgrade to beowulf 
(possibly when I migrated that machine into a VM) - so at 
least for some configurations, this problem has also been 
present in ascii.

Searching for the error messages, the hint to use device names 
shows up for older Ubuntu versions too, but I haven't found a 
good explanation why this happens. Initramfs scripting for lvm 
was never fixed to work with UUIDs?

Alex.

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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Alexander Bochmann]

...on Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote:

 > Using the /dev/mapper device name would likely have been just as good, but 
 > I'm not sure as I didn't try that

I'll try if using UUIDs in the fstab makes a difference in the 
boot process later tonight (and maybe why, if it indeed does).

The system has been migrated from hardware into a VM some time 
ago, so I can recover easily.

Alex.

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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Andrew McGlashan via Dng]

On 8/7/20 10:07 pm, Hendrik Boom wrote:
> On Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote:
>>
>>
>> On 8/7/20 7:31 am, Alexander Bochmann wrote:
>>> Hi,
>>>
>>> ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote:
>>>
>>>  > After the dist-upgrade, it failed to boot and remained at the 
>>> ministrants shell environment after having complained about not being able 
>>> to find the /usr file system via it's UUID.
>>>
>>> I have a system mostly like this (minus mdraid) with split root and /usr 
>>> on lvm each, and didn't run into your problem.
>>>
>>> My fstab uses /dev/mapper device names instead of UUIDs, but I don't see 
>>> why that should make a difference, seeing as it isn't used in the initramfs.
>>
>> Apparently with initramfs-tools it will try to mount /usr if it is in 
>> /etc/fstab ... not being able to mount /usr stopped normally boot from 
>> progressing further.
>>
>> Using the /dev/mapper device name would likely have been just as good, but 
>> I'm not sure as I didn't try that; I adjusted the 
>> /usr/share/initramfs-tools/scripts/local-top/lvm2 file
>> to specifically activate the lv so it could be found to be mounted as it 
>> should have been.
>>
>>> (On the other hand, I usually use UUIDs too, so there might be a reason it 
>>> looks that way, and I just don't remember about it right now...)
>>
>> Yes, that makes sense.
>>
>> I would think that you fixed the problem by using the /dev/mapper 
>> entry and I fixed it in the lvm2 script.
> 
> 
> I quite agree.  There's a bug that needs fixing for Devuan, but not 
> Debian.
> I may delay upgrading until it's fixed.

Not sure it will get fixed... :(
 - it seems that the problem is a bit of an edge case and won't effect anybody 
whom doesn't split /usr from root.
 - if they have split them and they don't "merge" them,
 - then the problem /may/ only arise if UUIDs are used for mount reference 
in /etc/fstab.

I don't really like my fix, but I'll probably merge /usr into root myself next 
time I'm onsite where that machine lives to avoid future issues.

> My /boot is on an old-style RAID by itself, so either copy can be used
> directly.
> 
> My /usr, by the way, is on lvm2 on RAID.
>   Do I need both adjustments?

I would think that the /dev/mapper/VG-LV in /etc/fstab would probably be fine.

Otherwise, expand the root file system LV (hopefully you have space), boot from 
a LIVE USB and move /usr back to root as well as remove the /usr entry in your 
/etc/fstab file.

Once /usr is back inside the root filesystem, then there is no need to keep the 
/usr lv.

Cheers
A.



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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Hendrik Boom]

On Wed, Jul 08, 2020 at 06:14:51PM +1000, Andrew McGlashan via Dng wrote:
> 
> 
> On 8/7/20 7:31 am, Alexander Bochmann wrote:
> > Hi,
> > 
> > ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote:
> > 
> >  > After the dist-upgrade, it failed to boot and remained at the 
> > ministrants shell environment after having complained about not being able 
> > to find the /usr file system via it's UUID.
> > 
> > I have a system mostly like this (minus mdraid) with split root and /usr 
> > on lvm each, and didn't run into your problem.
> > 
> > My fstab uses /dev/mapper device names instead of UUIDs, but I don't see 
> > why that should make a difference, seeing as it isn't used in the initramfs.
> 
> Apparently with initramfs-tools it will try to mount /usr if it is in 
> /etc/fstab ... not being able to mount /usr stopped normally boot from 
> progressing further.
> 
> Using the /dev/mapper device name would likely have been just as good, but 
> I'm not sure as I didn't try that; I adjusted the 
> /usr/share/initramfs-tools/scripts/local-top/lvm2 file
> to specifically activate the lv so it could be found to be mounted as it 
> should have been.
> 
> > (On the other hand, I usually use UUIDs too, so there might be a reason it 
> > looks that way, and I just don't remember about it right now...)
> 
> Yes, that makes sense.
> 
> I would think that you fixed the problem by using the /dev/mapper 
> entry and I fixed it in the lvm2 script.


I quite agree.  There's a bug that needs fixing for Devuan, but not 
Debian.
I may delay upgrading until it's fixed.

My /boot is on an old-style RAID by itself, so either copy can be used
directly.


My /usr, by the way, is on lvm2 on RAID.
  Do I need both adjustments?

-- hendrik


> Either way, I think there is a bug that needs to be fixed with
> initramfs-tools so that neither adjustment should be necessary.

Quite agree.  This is a bug in Devuan that originates in Debian but is 
not considered a bug there.

So, as I understand it, if /usr is mentioned in /etc/fstab, 
initramfstools will generate an initramfs that tries to mount /usr.

And that will succeed it /etc/fstab specifies /usr by the /dev/mapper
name, but not by the uuid?

So updating /etc/fstab to use the /dev/mapper name instead of a uuid
will make things work?  Even for LVM2 partitions?

As it happens, my /etc/fstab alrady uses /dev/mapper names, though it 
uses a uuid for /boot.

At the very least, this should be mentioned in the upgrade instructions.

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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Andrew McGlashan via Dng]

On 8/7/20 7:31 am, Alexander Bochmann wrote:
> Hi,
> 
> ...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote:
> 
>  > After the dist-upgrade, it failed to boot and remained at the ministrants 
> shell environment after having complained about not being able to find the 
> /usr file system via it's UUID.
> 
> I have a system mostly like this (minus mdraid) with split root and /usr 
> on lvm each, and didn't run into your problem.
> 
> My fstab uses /dev/mapper device names instead of UUIDs, but I don't see 
> why that should make a difference, seeing as it isn't used in the initramfs.

Apparently with initramfs-tools it will try to mount /usr if it is in 
/etc/fstab ... not being able to mount /usr stopped normally boot from 
progressing further.

Using the /dev/mapper device name would likely have been just as good, but I'm 
not sure as I didn't try that; I adjusted the 
/usr/share/initramfs-tools/scripts/local-top/lvm2 file
to specifically activate the lv so it could be found to be mounted as it should 
have been.

> (On the other hand, I usually use UUIDs too, so there might be a reason it 
> looks that way, and I just don't remember about it right now...)

Yes, that makes sense.

I would think that you fixed the problem by using the /dev/mapper entry and I 
fixed it in the lvm2 script.  Either way, I think there is a bug that needs to 
be fixed with
initramfs-tools so that neither adjustment should be necessary.

Cheers
A.



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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Alexander Bochmann]

Hi,

...on Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote:

 > After the dist-upgrade, it failed to boot and remained at the ministrants 
 > shell environment after having complained about not being able to find the 
 > /usr file system via it's UUID.

I have a system mostly like this (minus mdraid) with split root and /usr 
on lvm each, and didn't run into your problem.

My fstab uses /dev/mapper device names instead of UUIDs, but I don't see 
why that should make a difference, seeing as it isn't used in the initramfs.

(On the other hand, I usually use UUIDs too, so there might be a reason it 
looks that way, and I just don't remember about it right now...)

Alex.

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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Jim Jackson]

Forget it - you have Thank you.


On Tue, 7 Jul 2020, Jim Jackson wrote:

> 
> 
> 
> On Tue, 7 Jul 2020, Steve Litt wrote:
> 
> > On Mon, 6 Jul 2020 18:58:48 -0400
> > Hendrik Boom  wrote:
> > 
> > 
> > > Doesn't systemd require a merged /usr partition?  It sounds as if a 
> > > systemd-ism has crept into our boot process.
> > > 
> > > Fortunately I haven't upgraded my server to beowulf yet.
> > > 
> > > -- hendrik
> > 
> > Void Linux also symlinks all the various *bin directories together,
> > even though it's a runit distro. My objection is this merge forces you
> > to have an initramfs.
> 
> Ok, maybe I've been asleep at the back - but can you explain why, and in 
> what circumstances? 
> 
> Jim-being-a-bit-slow
> ___
> 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] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Jim Jackson]

On Tue, 7 Jul 2020, Steve Litt wrote:

> On Mon, 6 Jul 2020 18:58:48 -0400
> Hendrik Boom  wrote:
> 
> 
> > Doesn't systemd require a merged /usr partition?  It sounds as if a 
> > systemd-ism has crept into our boot process.
> > 
> > Fortunately I haven't upgraded my server to beowulf yet.
> > 
> > -- hendrik
> 
> Void Linux also symlinks all the various *bin directories together,
> even though it's a runit distro. My objection is this merge forces you
> to have an initramfs.

Ok, maybe I've been asleep at the back - but can you explain why, and in 
what circumstances? 

Jim-being-a-bit-slow
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Steve Litt]

On Mon, 6 Jul 2020 18:58:48 -0400
Hendrik Boom  wrote:


> Doesn't systemd require a merged /usr partition?  It sounds as if a 
> systemd-ism has crept into our boot process.
> 
> Fortunately I haven't upgraded my server to beowulf yet.
> 
> -- hendrik

Void Linux also symlinks all the various *bin directories together,
even though it's a runit distro. My objection is this merge forces you
to have an initramfs.

 
SteveT

Steve Litt 
May 2020 featured book: Troubleshooting Techniques
 of the Successful Technologist
http://www.troubleshooters.com/techniques
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Andrew McGlashan via Dng]

On 7/7/20 8:58 am, Hendrik Boom wrote:
> Doesn't systemd require a merged /usr partition?  It sounds as if a 
> systemd-ism has crept into our boot process.
> 
> Fortunately I haven't upgraded my server to beowulf yet.

Probably I know that Debian wants merged /usr, wasn't sure it was 
specifically due to systemd, but I think you are right.

I've upgraded 6 machines now from Ascii to Beowulf and it turns out the only 
one that I've done with this particular problem is the only one that had /usr 
as it's own file system
and not part of the root file system.

A.




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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Hendrik Boom]

On Tue, Jul 07, 2020 at 02:00:38AM +1000, Andrew McGlashan via Dng wrote:
> Hi,
> 
> I had another "simple" server upgrade from Devuan Ascii to Devuan Beowulf, 
> these are the details and my work around for the problem.
> 
> 
> There was nothing particularly special about this server, it doesn't use 
> encrypted file systems; it started out life as a Debian Wheezy installation, 
> migrated to Devuan Jessie and
> later to Devuan Ascii and now Beowulf.
> 
> 
> The server has /boot on it's own RAID1 partition with another RAID1 volume 
> for the rest of the disk being an LVM2 volume group having a number of 
> logical volumes for root, swap,
> /usr/, /var/, /home/ and more.

Sounds just like my configuration.

> 
> 
> After the dist-upgrade, it failed to boot and remained at the ministrants 
> shell environment after having complained about not being able to find the 
> /usr file system via it's UUID.
> 
> It had another error as well which was fixed by allocating 25% to RUNSIZE 
> variable (up from 10%) in /etc/initramfs-tools/initramfs.conf
> 
> - it was unable to find "rm" when running the boot up scripts before 
> dumping itself to the initramfs shell.
> 
> 
> Once at the initramfs prompt after fixing the first problem, I was able to do 
> the following:
> 
> (initramfs) lvm
> 
> lvm> vgchange -ay
> 
> lvm> exit
> 
> (initramfs) exit
> 
> 
> And then the server would continue to boot properly.
> 
> 
> _The second fix, which I consider to be "clunky", was to adjust the 
> /usr/share/initramfs-tools/scripts/local-top/lvm2 file, adding in a line near 
> the bottom as highlighted_
> 
> activate "$ROOT"
> *activate "/dev/mapper/vg0-usr"*
> activate "$resume"
> 
> 
> Then I rebuilt the initramfs in the usual way.
> 
> update-initramfs -u -k all
> 
> 
> The original lvm2 script specifically only activated the root file system 
> (/dev/mapper/vg0-root), even though /usr (/dev/mapper/vg0-usr) was in the 
> exact same volume group as a
> separate file system, thus stopping boot from succeeding as expected.
> 
> Other volumes come online in due course okay.
> 
> 
> All was good with subsequent reboots.
> 
> 
> Now, cludge or clunky, this was required because the /usr file system was 
> [and continues to be] separate to the root file system and the initramfs only 
> cared to enable the root
> file system, leaving all other logical volumes as being "NOT AVAILABLE", 
> including /usr which was definitely required!
> 
> 
> Have I fixed this appropriately, or should I some how fix it another way?
> 

Doesn't systemd require a merged /usr partition?  It sounds as if a 
systemd-ism has crept into our boot process.

Fortunately I haven't upgraded my server to beowulf yet.

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

[DNG] Upgrade problem [ ascii -> beowulf ] failed to boot, left at initramfs shell -- with fix and query

[Andrew McGlashan via Dng]

Hi,

I had another "simple" server upgrade from Devuan Ascii to Devuan Beowulf, 
these are the details and my work around for the problem.


There was nothing particularly special about this server, it doesn't use 
encrypted file systems; it started out life as a Debian Wheezy installation, 
migrated to Devuan Jessie and
later to Devuan Ascii and now Beowulf.


The server has /boot on it's own RAID1 partition with another RAID1 volume for 
the rest of the disk being an LVM2 volume group having a number of logical 
volumes for root, swap,
/usr/, /var/, /home/ and more.


After the dist-upgrade, it failed to boot and remained at the ministrants shell 
environment after having complained about not being able to find the /usr file 
system via it's UUID.

It had another error as well which was fixed by allocating 25% to RUNSIZE 
variable (up from 10%) in /etc/initramfs-tools/initramfs.conf

- it was unable to find "rm" when running the boot up scripts before 
dumping itself to the initramfs shell.


Once at the initramfs prompt after fixing the first problem, I was able to do 
the following:

(initramfs) lvm

lvm> vgchange -ay

lvm> exit

(initramfs) exit


And then the server would continue to boot properly.


_The second fix, which I consider to be "clunky", was to adjust the 
/usr/share/initramfs-tools/scripts/local-top/lvm2 file, adding in a line near 
the bottom as highlighted_

activate "$ROOT"
*activate "/dev/mapper/vg0-usr"*
activate "$resume"


Then I rebuilt the initramfs in the usual way.

update-initramfs -u -k all


The original lvm2 script specifically only activated the root file system 
(/dev/mapper/vg0-root), even though /usr (/dev/mapper/vg0-usr) was in the exact 
same volume group as a
separate file system, thus stopping boot from succeeding as expected.

Other volumes come online in due course okay.


All was good with subsequent reboots.


Now, cludge or clunky, this was required because the /usr file system was [and 
continues to be] separate to the root file system and the initramfs only cared 
to enable the root
file system, leaving all other logical volumes as being "NOT AVAILABLE", 
including /usr which was definitely required!


Have I fixed this appropriately, or should I some how fix it another way?


Kind Regards
AndrewM




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

Re: [DNG] Upgrade problem [ ascii -> beowulf ] chrooted bind9 server -- /usr/share/dns/root.hints issue -- with fix

[Gabe Stanton via Dng]

It should be. I had the same problem a little over a month ago and that
fixed it for me. Been running fine since.


On Mon, 2020-07-06 at 00:39 +1000, Andrew McGlashan via Dng wrote:
> Hi,
> 
> Okay, not fully fixed after reboot... apparmor gave problems as
> previously discussed on the list.
> 
> Also needed to adjust:
> 
>/etc/apparmor.d/local/usr.sbin.named
> 
> 
> Added a line:
> 
>/var/lib/named/** rw,
> 
> 
> Then restarted apparmor service:
> 
>service apparmor reload
> 
> 
> And then bind would start properly, immediately and again after
> another reboot.
> 
> 
> Should it be all good now?
> 
> 
> Thanks
> A.
> 
> 
> On 6/7/20 12:04 am, Andrew McGlashan via Dng wrote:
> > Hi,
> > 
> > I just upgraded fron Devuan ascii to beowulf with the server
> > running bind9 in a chroot environment and bind would not start.
> > 
> > 
> > _This was the relevant error in /var/log/daemon.log_
> > 
> > Jul  5 23:36:43 bind9-server-name named[6476]: *could not
> > configure root hints from '/usr/share/dns/root.hints': file not
> > found*
> > Jul  5 23:36:43 bind9-server-name named[6476]: *loading
> > configuration: file not found*
> > Jul  5 23:36:43 bind9-server-name named[6476]: *exiting (due to
> > fatal error)*
> > 
> > 
> > _Fixed as follows:_
> > 
> > # mkdir -p /var/lib/named/usr/share/dns
> > # cp -pv /usr/share/dns/* /var/lib/named/usr/share/dns/
> > 
> > 
> > _NB: No upgrade changes were made to any config file including the
> > /etc/default/bind9 file below._
> > 
> > # cat /etc/default/bind9
> > 
> > # Set RESOLVCONF=no to not run resolvconf
> > RESOLVCONF=yes
> > 
> > # startup options for the server
> > #OPTIONS="-u bind"
> > 
> > 
> > # Added -t ... for running of bind9 in a chroot environment
> > #OPTIONS="-u bind -t /var/lib/named"
> > # Added -4 to foce IPV4 lookups only
> > OPTIONS="-u bind -4 -t /var/lib/named"
> > 
> > ### NB: This symbolic link is needed for the chroot environment
> > too
> > #(without needing to change /etc/init.d/bind9 file)
> > #
> > # cd /run/named
> > # ln -s /var/lib/named/run/named/named.pid .
> > 
> > 
> > Kind Regards
> > AndrewM
> 
> ___
> 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] Upgrade problem [ ascii -> beowulf ] chrooted bind9 server -- /usr/share/dns/root.hints issue -- with fix

[Andrew McGlashan via Dng]

Hi,

Okay, not fully fixed after reboot... apparmor gave problems as previously 
discussed on the list.

Also needed to adjust:

   /etc/apparmor.d/local/usr.sbin.named


Added a line:

   /var/lib/named/** rw,


Then restarted apparmor service:

   service apparmor reload


And then bind would start properly, immediately and again after another reboot.


Should it be all good now?


Thanks
A.


On 6/7/20 12:04 am, Andrew McGlashan via Dng wrote:
> Hi,
> 
> I just upgraded fron Devuan ascii to beowulf with the server running bind9 in 
> a chroot environment and bind would not start.
> 
> 
> _This was the relevant error in /var/log/daemon.log_
> 
> Jul  5 23:36:43 bind9-server-name named[6476]: *could not configure root 
> hints from '/usr/share/dns/root.hints': file not found*
> Jul  5 23:36:43 bind9-server-name named[6476]: *loading configuration: 
> file not found*
> Jul  5 23:36:43 bind9-server-name named[6476]: *exiting (due to fatal 
> error)*
> 
> 
> _Fixed as follows:_
> 
> # mkdir -p /var/lib/named/usr/share/dns
> # cp -pv /usr/share/dns/* /var/lib/named/usr/share/dns/
> 
> 
> _NB: No upgrade changes were made to any config file including the 
> /etc/default/bind9 file below._
> 
> # cat /etc/default/bind9
> 
> # Set RESOLVCONF=no to not run resolvconf
> RESOLVCONF=yes
> 
> # startup options for the server
> #OPTIONS="-u bind"
> 
> 
> # Added -t ... for running of bind9 in a chroot environment
> #OPTIONS="-u bind -t /var/lib/named"
> # Added -4 to foce IPV4 lookups only
> OPTIONS="-u bind -4 -t /var/lib/named"
> 
> ### NB: This symbolic link is needed for the chroot environment too
> #    (without needing to change /etc/init.d/bind9 file)
> #
> # cd /run/named
> # ln -s /var/lib/named/run/named/named.pid .
> 
> 
> Kind Regards
> AndrewM



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

[DNG] Upgrade problem [ ascii -> beowulf ] chrooted bind9 server -- /usr/share/dns/root.hints issue -- with fix

[Andrew McGlashan via Dng]

Hi,

I just upgraded fron Devuan ascii to beowulf with the server running bind9 in a 
chroot environment and bind would not start.


_This was the relevant error in /var/log/daemon.log_

Jul  5 23:36:43 bind9-server-name named[6476]: *could not configure root 
hints from '/usr/share/dns/root.hints': file not found*
Jul  5 23:36:43 bind9-server-name named[6476]: *loading configuration: file 
not found*
Jul  5 23:36:43 bind9-server-name named[6476]: *exiting (due to fatal 
error)*


_Fixed as follows:_

# mkdir -p /var/lib/named/usr/share/dns
# cp -pv /usr/share/dns/* /var/lib/named/usr/share/dns/


_NB: No upgrade changes were made to any config file including the 
/etc/default/bind9 file below._

# cat /etc/default/bind9

# Set RESOLVCONF=no to not run resolvconf
RESOLVCONF=yes

# startup options for the server
#OPTIONS="-u bind"


# Added -t ... for running of bind9 in a chroot environment
#OPTIONS="-u bind -t /var/lib/named"
# Added -4 to foce IPV4 lookups only
OPTIONS="-u bind -4 -t /var/lib/named"

### NB: This symbolic link is needed for the chroot environment too
#    (without needing to change /etc/init.d/bind9 file)
#
# cd /run/named
# ln -s /var/lib/named/run/named/named.pid .


Kind Regards
AndrewM




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

Re: [DNG] upgrade to ascii dkim stopped working

[Gregory Nowak]

On Thu, Feb 28, 2019 at 05:55:46PM +0100, info at smallinnovations dot nl wrote:
> opendkim (2.11.0~alpha-8) unstable; urgency=medium On systems using
> systemd, this version replaces /etc/default/opendkim with the files
> /etc/systemd/system/opendkim.service.d/overrride.conf and
> /etc/tmpfiles.d/opendkim.conf carrying over non-default settings. --

Which means that on systems not using systemd /etc/default/opendkim is
still being honored. In fact, a fragment of /etc/init.d/opendkim
reads:

# Include opendkim defaults if available
if [ -f /etc/default/opendkim ] ; then
. /etc/default/opendkim
fi

> So may be i am wrong but i have not found any means
> to get opendkim 2.11 working. Downgrading to 2.9 worked immediately and
> because it is a production system i for now do not have more time to
> investigate it any further.

You did put the error message you're getting into your favorite
search engine before giving up, yes?

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] upgrade to ascii dkim stopped working

[info at smallinnovations dot nl]

On 28-02-19 08:08, KatolaZ wrote:
>> Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of
>> systemd bugreports, notes about being a native systemd daemon but simply
>> not working from postfix. I downgraded opendkim from 2.11 to 2.9 and
>> everythings is working again.
>>
>> Of course i have now put a hold on 2.9 but my other systems will stay at
>> jessie for the foreseeable future.
>>
> Hi Nick,
>
> I don't know how you concluded that opendkim has been infected by
> systemd, and that this might result in a breakage. As a matter of
> fact, opendkim has no dependency on systemd or systemd-related stuff,
> not even indirect ones.
>
> I guess the opendkim package might be shipping a systemd unit file,
> but that cannot cause any breakage, since it is just a declarative
> initialisation file interpreted by systemd. And there is no way to get
> systemd running in Devuan, unless you download it from Debian repos.
>
> There must be something else going on, since there are several reports
> of perfectly-working opendkim installations in ascii and beowulf.
>
> HND
>
> KatolaZ
>
Hi Katolaz,

I have two main reasons to think it is:

1) the mail from apt-list changes news after upgrading:

opendkim (2.11.0~alpha-10+deb9u1) stretch; urgency=medium This updates
corrects an issue where the opendkim configuration file was not being
read. It also sets the opendkim user in the configuration file rather
than as part of the systemd service file. In order to have a correctly
working system post update, it is important not to reject the changes in
the package provided configuration file. This may require manually
integrating local changes with the changes provided in this update.
Failure to do this may result in the opendkim daemon running as root
instead of as its own user. In the updated configuration, opendkim will
initially start as root, read both it's configuration files and private
keys required for signing and then drop priviledges to the opendkim user
specified in the configuration file prior to start of normal operations.
-- Scott Kitterman Tue, 12 Sep 2017 23:36:11 -0400

opendkim (2.11.0~alpha-8) unstable; urgency=medium On systems using
systemd, this version replaces /etc/default/opendkim with the files
/etc/systemd/system/opendkim.service.d/overrride.conf and
/etc/tmpfiles.d/opendkim.conf carrying over non-default settings. --
Scott Kitterman Mon, 07 Nov 2016 12:14:31 -0500

2) this blogpost
https://jschumacher.info/2017/06/upgrading-to-debian-stretch-with-dovecot-postfix-opendkim/
which mentions that"During the system upgrade, opendkim daemon was
reconfigured as a native systemd daemon,which
meant */etc/default/opendkim* and */etc/init.d/opendkim* became
obsolete, even though I was asked to install the new package maintainers
version of /etc/default/opendkim."

My best guess is that somehow opendkim "thinks" that systemd has been
installed based on systemd files present on my system. I am very certain
that systemd is not running on my system. apt list systemd --installed
returns empty too. So may be i am wrong but i have not found any means
to get opendkim 2.11 working. Downgrading to 2.9 worked immediately and
because it is a production system i for now do not have more time to
investigate it any further.

Although i am preparing a clean install instead of a upgraded system
from Debian Wheezy to Debian Jessie to Devuan Jessie to Devuan ASCII.


Grtz,


Nick



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

Re: [DNG] upgrade to ascii dkim stopped working

[KatolaZ]

On Wed, Feb 27, 2019 at 10:30:29PM +0100, info at smallinnovations dot nl wrote:
> On 25-02-19 00:18, Gregory Nowak wrote:
> > On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl 
> > wrote:
> >> After upgrading a production server to ascii from jessie, opendkim
> >> stopped working. When i start opendkim manually i get the error
> >> "Starting OpenDKIM: install: cannot create directory ‘’: No such file or
> >> directory". I kept the original configfiles. There is a update remark
> >> from debian about when systemd is installed but of course i do not have
> >> systemd installed. Someone recognizing this problem and may be knows a fix?
> > All I can tell you is that I do have opendkim working on Ascii. I did
> > the upgrade to Ascii about a year ago, and don't recall any major
> > issues with opendkim. Might dpkg-reconfigure on the opendkim package
> > help? I wish I had a more specific answer for you.
> >
> > Greg
> >
> >
> Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of
> systemd bugreports, notes about being a native systemd daemon but simply
> not working from postfix. I downgraded opendkim from 2.11 to 2.9 and
> everythings is working again.
> 
> Of course i have now put a hold on 2.9 but my other systems will stay at
> jessie for the foreseeable future.
> 

Hi Nick,

I don't know how you concluded that opendkim has been infected by
systemd, and that this might result in a breakage. As a matter of
fact, opendkim has no dependency on systemd or systemd-related stuff,
not even indirect ones.

I guess the opendkim package might be shipping a systemd unit file,
but that cannot cause any breakage, since it is just a declarative
initialisation file interpreted by systemd. And there is no way to get
systemd running in Devuan, unless you download it from Debian repos.

There must be something else going on, since there are several reports
of perfectly-working opendkim installations in ascii and beowulf.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


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

Re: [DNG] upgrade to ascii dkim stopped working

[J. Fahrner via Dng]

Am 2019-02-27 22:30, schrieb info at smallinnovations dot nl:

Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of
systemd bugreports, notes about being a native systemd daemon but 
simply

not working from postfix. I downgraded opendkim from 2.11 to 2.9 and
everythings is working again.


I'm using rspamd and also use it for dkim signing. Works very well.
https://rspamd.com/doc/modules/dkim_signing.html

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

Re: [DNG] upgrade to ascii dkim stopped working

[Gregory Nowak]

On Wed, Feb 27, 2019 at 10:30:29PM +0100, info at smallinnovations dot nl wrote:
> Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of
> systemd bugreports, notes about being a native systemd daemon but simply
> not working from postfix. I downgraded opendkim from 2.11 to 2.9 and
> everythings is working again.

Interesting:

$ apt-cache policy opendkim
opendkim:
  Installed: 2.11.0~alpha-10+deb9u1
  Candidate: 2.11.0~alpha-10+deb9u1
  Version table:
 *** 2.11.0~alpha-10+deb9u1 500
500 http://deb.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status

$ apt-cache policy postfix
postfix:
  Installed: 3.1.9-0+deb9u2
  Candidate: 3.1.9-0+deb9u2
  Version table:
 *** 3.1.9-0+deb9u2 500
500 http://deb.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status

Yes, I do have opendkim working from postfix.
Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] upgrade to ascii dkim stopped working

[info at smallinnovations dot nl]

On 25-02-19 00:18, Gregory Nowak wrote:
> On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl 
> wrote:
>> After upgrading a production server to ascii from jessie, opendkim
>> stopped working. When i start opendkim manually i get the error
>> "Starting OpenDKIM: install: cannot create directory ‘’: No such file or
>> directory". I kept the original configfiles. There is a update remark
>> from debian about when systemd is installed but of course i do not have
>> systemd installed. Someone recognizing this problem and may be knows a fix?
> All I can tell you is that I do have opendkim working on Ascii. I did
> the upgrade to Ascii about a year ago, and don't recall any major
> issues with opendkim. Might dpkg-reconfigure on the opendkim package
> help? I wish I had a more specific answer for you.
>
> Greg
>
>
Apparently opendkim 2.11 has been polluted/infected by systemd. Lots of
systemd bugreports, notes about being a native systemd daemon but simply
not working from postfix. I downgraded opendkim from 2.11 to 2.9 and
everythings is working again.

Of course i have now put a hold on 2.9 but my other systems will stay at
jessie for the foreseeable future.

Grtz.

Nick




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

Re: [DNG] upgrade to ascii dkim stopped working

[Gregory Nowak]

On Sun, Feb 24, 2019 at 03:55:08PM +0100, info at smallinnovations dot nl wrote:
> After upgrading a production server to ascii from jessie, opendkim
> stopped working. When i start opendkim manually i get the error
> "Starting OpenDKIM: install: cannot create directory ‘’: No such file or
> directory". I kept the original configfiles. There is a update remark
> from debian about when systemd is installed but of course i do not have
> systemd installed. Someone recognizing this problem and may be knows a fix?

All I can tell you is that I do have opendkim working on Ascii. I did
the upgrade to Ascii about a year ago, and don't recall any major
issues with opendkim. Might dpkg-reconfigure on the opendkim package
help? I wish I had a more specific answer for you.

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] upgrade to ascii dkim stopped working

[info at smallinnovations dot nl]

After upgrading a production server to ascii from jessie, opendkim
stopped working. When i start opendkim manually i get the error
"Starting OpenDKIM: install: cannot create directory ‘’: No such file or
directory". I kept the original configfiles. There is a update remark
from debian about when systemd is installed but of course i do not have
systemd installed. Someone recognizing this problem and may be knows a fix?

Grtz

Nick




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

Re: [DNG] upgrade to ascii

[Olaf Meeuwissen]

Hi,

KatolaZ writes:

> On Mon, Jan 01, 2018 at 01:59:23PM +0900, Olaf Meeuwissen wrote:
>> Hi,
>>
>> [...]  I just upgraded
>> myself using (almost) the same without any problems and blogged about
>> it here
>>
>>   https://paddy-hack.gitlab.io/posts/upgrading-devuan-from-jessie-to-ascii/
>
> very nice report, indeed. Thanks.

Glad you liked it.  I cleaned up the log for readability and added a bit
on cleaning up *.dpkg* files.  I've also written a separate post on some
of the "issues" I ran into.

  https://paddy-hack.gitlab.io/posts/a-fortnight-with-ascii/

Happy to see that the theme issues (the ones I noticed at least) are all
fixed in clearlooks-phenix-darkpurpy.

@golinux: Thanks!

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] upgrade to ascii

[KatolaZ]

On Mon, Jan 01, 2018 at 01:59:23PM +0900, Olaf Meeuwissen wrote:
> Hi,
> 
> Hendrik Boom writes:
> 
> > So is this what I should have in my /etc/apt/sources.list to upgrade
> > from jessie to ascii?
> >
> > deb http://pkgmaster.devuan.org/merged ascii main
> > deb http://pkgmaster.devuan.org/merged ascii-updates main
> > deb http://pkgmaster.devuan.org/merged ascii-security main
> > deb http://pkgmaster.devuan.org/merged ascii-backports main
> >
> > and nothing else?
> 
> That should work just fine.  Backports is optional.  I just upgraded
> myself using (almost) the same without any problems and blogged about
> it here
> 
>   https://paddy-hack.gitlab.io/posts/upgrading-devuan-from-jessie-to-ascii/
> 
> Hope this helps,

Hi Olaf,

very nice report, indeed. Thanks.

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]


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

Re: [DNG] upgrade to ascii

[Olaf Meeuwissen]

Hi,

Hendrik Boom writes:

> So is this what I should have in my /etc/apt/sources.list to upgrade
> from jessie to ascii?
>
> deb http://pkgmaster.devuan.org/merged ascii main
> deb http://pkgmaster.devuan.org/merged ascii-updates main
> deb http://pkgmaster.devuan.org/merged ascii-security main
> deb http://pkgmaster.devuan.org/merged ascii-backports main
>
> and nothing else?

That should work just fine.  Backports is optional.  I just upgraded
myself using (almost) the same without any problems and blogged about
it here

  https://paddy-hack.gitlab.io/posts/upgrading-devuan-from-jessie-to-ascii/

Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Softwarehttps://my.fsf.org/donate
 Join the Free Software Foundation  https://my.fsf.org/join
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] upgrade to ascii

[info at smallinnovations dot nl]

On 31-12-17 19:34, Antony Stone wrote:

On Sunday 31 December 2017 at 19:02:41, Hendrik Boom wrote:


So is this what I should have in my /etc/apt/sources.list to upgrade
from jessie to ascii?

deb http://pkgmaster.devuan.org/merged ascii main
deb http://pkgmaster.devuan.org/merged ascii-updates main
deb http://pkgmaster.devuan.org/merged ascii-security main
deb http://pkgmaster.devuan.org/merged ascii-backports main

and nothing else?

1. That worked for me a couple of days ago.

2. I was surprised when I couldn't find this documented on the Devuan website
anywhere.


Antony.

I do not have backports enabled by default but the other ones do work in 
a virtual machine with ascii upgraded from jessie.


Grtz.

Nick

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

Re: [DNG] upgrade to ascii

[Antony Stone]

On Sunday 31 December 2017 at 19:02:41, Hendrik Boom wrote:

> So is this what I should have in my /etc/apt/sources.list to upgrade
> from jessie to ascii?
> 
> deb http://pkgmaster.devuan.org/merged ascii main
> deb http://pkgmaster.devuan.org/merged ascii-updates main
> deb http://pkgmaster.devuan.org/merged ascii-security main
> deb http://pkgmaster.devuan.org/merged ascii-backports main
> 
> and nothing else?

1. That worked for me a couple of days ago.

2. I was surprised when I couldn't find this documented on the Devuan website 
anywhere.


Antony.

-- 
"The tofu battle I saw last weekend was quite brutal."

 - Marija Danute Brigita Kuncaitis

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] upgrade to ascii

[Hendrik Boom]

So is this what I should have in my /etc/apt/sources.list to upgrade 
from jessie to ascii? 

deb http://pkgmaster.devuan.org/merged ascii main
deb http://pkgmaster.devuan.org/merged ascii-updates main
deb http://pkgmaster.devuan.org/merged ascii-security main
deb http://pkgmaster.devuan.org/merged ascii-backports main

and nothing else?

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

Re: [DNG] Upgrade to ascii not possible?

[Harald Arnesen]

Yevgeny Kosarzhevsky [2017-10-13 03:57]:

> You are right, it looks like mirrors aren't updated.
> When I replaced auto.mirror.devuan.org/merged/
>  with packages.devuan.org/devuan/
> , the upgrade has worked, however
> I've gotten 300+ orphaned packages.

I had
,
which was put in sources.list by the installer. When I changed that to
,
I got updates for init-system-helpers and rsyslog.

So it seems there is (at least was) a bug in the ascii installer.
-- 
Hilsen Harald
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to ascii not possible?

[Harald Arnesen]

Antony Stone [2017-10-12 18:11]:

> So, you're only seeing 1.46+devuan1.0
> 
 On 12 October 2017 at 21:01, Svante Signell wrote:
> On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote:
>> 1.46+devuan1.0 0
>> 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages
> The latest version is really 1.48+devuan2.0 as of today.
> Which is confirmed from
> https://packages.devuan.org/devuan/pool/main/i/init-system-helpers/
> 
> So, it beats me why you're not seeing that version available :(

I have exactly the same problem.
-- 
Hilsen Harald
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to ascii not possible?

[Yevgeny Kosarzhevsky]

You are right, it looks like mirrors aren't updated.
When I replaced auto.mirror.devuan.org/merged/ with
packages.devuan.org/devuan/, the upgrade has worked, however I've gotten
300+ orphaned packages.

On 13 October 2017 at 00:28, fsmithred  wrote:

> On 10/12/2017 11:51 AM, Yevgeny Kosarzhevsky wrote:
> > On 12 October 2017 at 23:37, Antony Stone <
> > antony.st...@devuan.open.source.it> wrote:
> >
> >>
> >>> I am trying to upgrade from devuan jessie and get unresolved deps for
> >>> rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~
> >>> (UNAVAILABLE)
>
> Svante says 1.48+devuan2.0 is in ascii today, but I'm still not seeing it.
> I do see 1.47+devuan1.0 in ceres. That might work. Or wait until 1.48
> shows up.
>
> fsmithred
>
>
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>



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

Re: [DNG] Upgrade to ascii not possible?

[fsmithred]

On 10/12/2017 11:51 AM, Yevgeny Kosarzhevsky wrote:
> On 12 October 2017 at 23:37, Antony Stone <
> antony.st...@devuan.open.source.it> wrote:
> 
>>
>>> I am trying to upgrade from devuan jessie and get unresolved deps for
>>> rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~
>>> (UNAVAILABLE)

Svante says 1.48+devuan2.0 is in ascii today, but I'm still not seeing it.
I do see 1.47+devuan1.0 in ceres. That might work. Or wait until 1.48
shows up.

fsmithred


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

Re: [DNG] Upgrade to ascii not possible?

[Antony Stone]

On Thursday 12 October 2017 at 17:51:44, Yevgeny Kosarzhevsky wrote:

> On 12 October 2017 at 23:37, Antony Stone <
> 
> antony.st...@devuan.open.source.it> wrote:
> > > I am trying to upgrade from devuan jessie and get unresolved deps for
> > > rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~
> > > (UNAVAILABLE)
> > 
> > What do you get for each of:
> > 
> > aptitude search init-system-helpers
> 
> ~# aptitude search init-system-helpers
> i init-system-helpers - helper tools for all init systems

Grrr - sorry, I meant to ask for "aptitude show init-system-helpers", but the 
below answers my question anyway...

> > apt-cache policy init-system-helpers
> 
> ~# apt-cache policy init-system-helpers
> init-system-helpers:
>   Installed: 1.46+devuan1.0
>   Candidate: 1.46+devuan1.0
>   Version table:
>  *** 1.46+devuan1.0 500
> 500 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages
> 100 /var/lib/dpkg/status

So, you're only seeing 1.46+devuan1.0

> > > On 12 October 2017 at 21:01, Svante Signell wrote:
> > > > On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote:
> > > > > 
> > > > > 1.46+devuan1.0 0
> > > > > 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages
> > > > 
> > > > The latest version is really 1.48+devuan2.0 as of today.

Which is confirmed from
https://packages.devuan.org/devuan/pool/main/i/init-system-helpers/

So, it beats me why you're not seeing that version available :(

You *have* done an "apt-get update" first, haven't you :) ?


Antony.

-- 
I have an excellent memory.
I can't think of a single thing I've forgotten.

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to ascii not possible?

[Yevgeny Kosarzhevsky]

On 12 October 2017 at 23:37, Antony Stone <
antony.st...@devuan.open.source.it> wrote:

>
> > I am trying to upgrade from devuan jessie and get unresolved deps for
> > rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~
> > (UNAVAILABLE)
>
> What do you get for each of:
>
> aptitude search init-system-helpers
>

~# aptitude search init-system-helpers
i
init-system-helpers
- helper tools for all init systems


> apt-cache policy init-system-helpers
>

~# apt-cache policy init-system-helpers
init-system-helpers:
  Installed: 1.46+devuan1.0
  Candidate: 1.46+devuan1.0
  Version table:
 *** 1.46+devuan1.0 500
500 http://auto.mirror.devuan.org/merged ascii/main amd64 Packages
100 /var/lib/dpkg/status



>
> ?
>
> Antony.
>
> > On 12 October 2017 at 21:01, Svante Signell wrote:
> > > On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote:
> > > > On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote:
> > > > > Hello,
> > > > >
> > > > > I've stuck on upgrading to ascii as there is no init-system-helpers
> > > > > available.
> > > > > Is there any solution?
> > > >
> > > > I see it in ascii main repo. What error message are you getting?
> > > >
> > > > 1.46+devuan1.0 0
> > > > 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages
> > >
> > > The latest version is really 1.48+devuan2.0 as of today.
>
> --
> This is not a rehearsal.
> This is Real Life.
>
>Please reply to the
> list;
>  please *don't* CC
> me.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>



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

Re: [DNG] Upgrade to ascii not possible?

[Antony Stone]

On Thursday 12 October 2017 at 17:24:42, Yevgeny Kosarzhevsky wrote:

> Hello,
> 
> I am trying to upgrade from devuan jessie and get unresolved deps for
> rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~
> (UNAVAILABLE)

What do you get for each of:

aptitude search init-system-helpers

apt-cache policy init-system-helpers

?

Antony.

> On 12 October 2017 at 21:01, Svante Signell wrote:
> > On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote:
> > > On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote:
> > > > Hello,
> > > > 
> > > > I've stuck on upgrading to ascii as there is no init-system-helpers
> > > > available.
> > > > Is there any solution?
> > > 
> > > I see it in ascii main repo. What error message are you getting?
> > > 
> > > 1.46+devuan1.0 0
> > > 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages
> > 
> > The latest version is really 1.48+devuan2.0 as of today.

-- 
This is not a rehearsal.
This is Real Life.

   Please reply to the list;
 please *don't* CC me.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to ascii not possible?

[Yevgeny Kosarzhevsky]

Hello,

I am trying to upgrade from devuan jessie and get unresolved deps for
rsyslog. aptitude shows: depends on init-system-helpers >= 1.47~
(UNAVAILABLE)

On 12 October 2017 at 21:01, Svante Signell 
wrote:

> On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote:
> > On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote:
> > > Hello,
> > >
> > > I've stuck on upgrading to ascii as there is no init-system-helpers
> > > available.
> > > Is there any solution?
> > >
> >
> > I see it in ascii main repo. What error message are you getting?
> >
> > 1.46+devuan1.0 0
> > 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages
>
> The latest version is really 1.48+devuan2.0 as of today.
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>



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

Re: [DNG] Upgrade to ascii not possible?

[Svante Signell]

On Thu, 2017-10-12 at 08:47 -0400, fsmithred wrote:
> On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote:
> > Hello,
> > 
> > I've stuck on upgrading to ascii as there is no init-system-helpers
> > available.
> > Is there any solution?
> > 
> 
> I see it in ascii main repo. What error message are you getting?
> 
> 1.46+devuan1.0 0
> 100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages

The latest version is really 1.48+devuan2.0 as of today.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Upgrade to ascii not possible?

[fsmithred]

On 10/11/2017 08:15 PM, Yevgeny Kosarzhevsky wrote:
> Hello,
> 
> I've stuck on upgrading to ascii as there is no init-system-helpers
> available.
> Is there any solution?
> 

I see it in ascii main repo. What error message are you getting?

1.46+devuan1.0 0
100 http://auto.mirror.devuan.org/merged/ ascii/main amd64 Packages

fsmithred

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

[DNG] Upgrade to ascii not possible?

[Yevgeny Kosarzhevsky]

Hello,

I've stuck on upgrading to ascii as there is no init-system-helpers
available.
Is there any solution?

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