Have you tried alien?
apt-cache show alien
On 26/10/17 18:22, John Crisp wrote:
> I have a little idea I have been tossing around in brain for ages but I'm
> stuck.
>
> I'm quite used to building rpms but no experience with debs.
>
> I have some stuff I'd like to experiment with on Devuan
Intel are not the only x86 cpu manufacturer.
I use a lot of VIA Eden equipped devices (thin-clients) 32-bit, 1+ GHz,
1GB RAM usually. They run fine on 12v batteries charged by solar, have
no problems being mounted in vehicles (land or marine) and are fully
featured with IDE/SATA and network boot
If every upstream developer includes an option --with-systemd to make
their code work reliably with it, then all Debian package developers
will use the option without questioning if it is actually necessary.
Eventually, the switch packagers and developers will forget what was
actually being done
Perhaps Linus will be brave enough to stand up to RedHat and request
that they fork Linux 4.x into SystemD so that Linux 5.0 will use SysV as
the reference init. SystemD will eventually replace the Linux kernel so
why not just fork it now and take their followers with them.
On 10/07/17 16:57,
On 07/07/17 13:11, zap wrote:
> It would be good though if you could allow mate-power-manager into the
> software repository with the systemd dependencies removed though...
That would require someone to create and maintain a Devuan specific
package and possibly even forking the code depending on
Is it possible to read the reason why a package has been banned?
On 07/07/17 08:09, Ivan J. wrote:
> FYI:
>
> Banned packages in Devuan:
> http://amprolla.parazyd.cf/log/bannedpkgs.txt
smime.p7s
Description: S/MIME Cryptographic Signature
___
Dng
Thanks. I should have checked the archive for stretch too, sorry.
I purged two obsolete python packages that were not removed after
upgrading. Looking forward to amprolla3.
-Vince-
On 06/07/17 14:42, KatolaZ wrote:
> Hi,
>
> that package is not in stretch:
>
>
My 32-bit Ascii system has python-junitxml installed but
apt-show-versions says that it is not in the Ascii archive.
sudo apt-show-versions python-junitxml
python-junitxml:all 0.6-1.1 installed: No available version in archive
This appears to be the version in Debian Jessie which the machine was
I have some suggestions for some changes to Daniel Abrecht's
sd_journal_shim license and code that may be agreeable.
1. Give Daniel Abrecht an email address to use in his copyright messages
on the source code for sd_journal_shim E.g.
daniel.abre...@contributor.devuan.org
2. Change the code so
The actual upgrade process from Jessie to Ascii worked with 100MB /tmp.
After rebooting on Ascii, regular updates wouldn't work with 500MB /tmp.
I created a 6GB file system on a USB flash drive to see if it would be
enough, and it was. It's easy enough to try a smaller partition size to
find what
I was using a 100MB tmpfs for /tmp which worked on Jessie. I increased
it to 500MB and it still didn't allow apt to update on Ascii. So, to
answer your question I put /tmp on another file system with 6GB free and
the update worked. I didn't have enough free space on /tmp after all.
Reading the
(ascii)
Release:2.0
Codename: ascii
On 02/07/17 12:34, Daniel Reurich wrote:
> Hi Vincent,
>
> Can you try using apt instead?
>
>
>
> On 2 July 2017 10:35:08 AM NZST, Vincent Bentley <vi...@vincentbentley.co.uk>
> wrote:
>> I updated a 32-bit
I updated a 32-bit Devuan Jessie system today (Saturday) to Ascii. After
rebooting I needed to fix a few package dependency problems and I got
the following message when using aptitude to update.
sudo aptitude -y update
Get: 1 http://packages.devuan.org/merged ascii InRelease [113 kB]
Err
Along time ago, well designed and well behaved software could be
recognised by the number of years passed without changes. I worked at
one place that was proud of release version birthdays.
On 30/06/17 21:22, zap wrote:
>
>
> On 06/30/2017 03:45 PM, Joachim Fahrner wrote:
> I just want to use
14 matches
Mail list logo
