Displaying 20 results from an estimated 300 matches similar to: "Missing devel packages?"
2017 Jan 05
1
doveadm output format changes
It appears that doveadm output format changes every now and then,
without particular notice.
For example, the following command:
doveadm -f pager mailbox status 'messages recent' '*'
did output something like this until v2.2.24 :
mailbox: Mailbox1
messages: 58
recent: 12
^L
mailbox: Mailbox2
messages: 128
recent: 0
but switched to that in v2.2.26 :
Mailbox1
messages: 58
2017 Jan 25
1
2.2.26.0 : accessing "mdbox_deleted" content destroys indexes
Accessing or listing "mdbox_deleted" contents seems to destroy MDBOX
indexes.
Examples of commands which triggers this problem ($home being the home
directory of $user, and mail_location being mdbox:~/mdbox):
doveadm -o mail="mdbox_deleted:$home/mdbox" -f table mailbox status -u
"$user" 'messages vsize' INBOX
doveadm -v import -s -u "$user"
2024 Mar 14
0
CentOS Virt SIG and packages' priority problems?
Hello,
some days ago I followed these instructions
https://sigs.centos.org/virt/tdx/host/
and after enabling the repo I installed the tdx necessary bits as
indicated, with the command
dnf install kernel-tdx qemu-kvm-tdx libvirt-tdx
This gave me:
libvirt 9.5.0-1.el9s
qemu-kvm 8.0.0-15.el9s
kernel 5.14.0-395.el9s
But now if I run a usual "dnf update" I'm proposed
2003 Mar 10
2
File name too long
Hi,
I've got a File name too long problem using rsync-2.5.6 or rsync 2.5.5-0.1
(debian)
I had a look to the mailing list archive and to the todo file and all I've
seen was that the problem only appears on old special systems.
I'm using debian 2.2.20. (is it too old?)
I've already posted this bug in debian bug tracking system
2023 Mar 21
1
"doveadm altmove -r" not working ?
> On 21/03/2023 00:26 EET Benoit Branciard <benoit.branciard at univ-paris1.fr> wrote:
>
>
> Hello,
>
> I have some trouble using "doveadm altmove -r".
>
> Regular "doveadm altmove" is OK, selected mails were moved to alternate
> storage as expected. But I can't manage to get them back to original
> location, "doveadm altmove
2023 Mar 20
3
"doveadm altmove -r" not working ?
Hello,
I have some trouble using "doveadm altmove -r".
Regular "doveadm altmove" is OK, selected mails were moved to alternate
storage as expected. But I can't manage to get them back to original
location, "doveadm altmove -r" has no effect.
We are using Dovecot 2.3.4 (Debian Buster package).
mail_location =
2023 May 03
0
mock fails on gpg with epel - ?
On 01/05/2023 15:10, lejeczek via CentOS wrote:
> Hi guys,
>
> Does your 'mock' work when used with 'centos-stream+epel-9-x86_64' config?
> It fails for me with every rpm packages I tried:
>
> -> $ mock -r centos-stream+epel-9-x86_64 --rootdir=~/mock
> --localrepo=/devs/var/www/dnf.repo --chain --continue
> rpmbuild/rpm.src/pass-1.7.4-6.el9.src.rpm
2024 Jan 12
1
No suspend after update
On Wed, Jan 10, 2024 at 11:57?PM Michael B Allen <ioplex at gmail.com> wrote:
>
> Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and now it
> won't suspend with the following error:
...
> [ 72.805437] Freezing of tasks failed after 20.006 seconds (1 tasks
> refusing to freeze, wq_busy=0):
> [ 72.805450] task:NFSv4 callback state:I stack:0 pid:2191
2023 May 01
2
mock fails on gpg with epel - ?
Hi guys,
Does your 'mock' work when used with
'centos-stream+epel-9-x86_64' config?
It fails for me with every rpm packages I tried:
-> $ mock -r centos-stream+epel-9-x86_64 --rootdir=~/mock
--localrepo=/devs/var/www/dnf.repo --chain --continue
rpmbuild/rpm.src/pass-1.7.4-6.el9.src.rpm
...
CentOS Stream 9 - BaseOS 1.6 MB/s | 1.6 kB???? 00:00
The GPG keys listed for the
2023 Mar 21
1
"doveadm altmove -r" not working ?
Hi,
Your problem might be similar to mine a long time ago. IMO behavior of
"doveadm altmove -r" command with mdbox format is different to sdbox format:
- With sdbox format, when you move back a message to primary storage
(aka default storage), only the message and the file containing it are
affected. There is nothing impacted.
- With mdbox format, a file in storage contains
2012 Jun 22
1
cumulative userdb ?
in Dovecot 2.0, is it possible to have kind of "cumulative" multiple
userdb ?
that is, for all users:
- extract some attributes (let's say: uid, gid, home) from a first
userdb (Passwd for example),
- an extract some other attributes (mail for example, but overwriting
those from the first userdb in case of redundancy) from a second userdb
(LDAP for example) ?
This is *different*
2024 Jan 10
1
no video with Aspeed (ast module) and latest kernel
Hello,
I have a CentOS Stream 9 server.
It is an Intel D50DNP1SBB one with:
02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics
Family (rev 52) (prog-if 00 [VGA controller])
DeviceName: ASPEED AST2600
Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family
Flags: medium devsel, IRQ 16, NUMA node 0, IOMMU group 42
Memory at 94000000 (32-bit,
2024 Jan 12
1
No suspend after update
I have two suggestions about how to keep - for a while - the 388 kernel.
First - Use DNF to remove the bad kernels. Then when a new one comes in
it will take one of those slots.
Second - Increase the number of installed kernels. That change is in
yum.conf.
https://linuxconfig.org/how-to-remove-old-unused-kernels-on-centos-linux
If the number is too high, you may run out of room in /boot
2005 Apr 13
3
Patch for tunnelserver mode in protocol_subnet.c
Hello,
Here is a patch for protocol_subnet.c with two modifications :
- in tunnelserver mode, tinc must check subnets in the ".../hosts/owner"
config file, not in "c->config_tree" (which is the configuration
of the meta-connection from which we receive the ADD_SUBNET message).
- this checking can be made before the check of the owner, especially
before any
2012 Nov 19
0
upgrade 1.0.15 -> 2.1.7: MBOX index compatibility and performance
Hi,
we just upgraded our mailserver from Dovecot 1.0.15 to Dovecot 2.1.7.
We use MBOX format (due to legacy compatibility), system users,
PAM+GSSAPI auth, filesystem quotas, and indexes located on a separate
filesystem:
mail_location =
mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot/indexes/%16Hu/%u
The 2.1.7 configuration files have been rewritten based on default
templates
2023 Mar 03
1
EL9 says: pcp-pmie[2870]: Low random number entropy available 15.6%
Hi,
I've discovered an issue which I don't understand. On a new test install
of EL9 I saw this message in the logs:
Mar 01 08:09:18 <hostname> pcp-pmie[2870]: Low random number entropy
available 15.6%avail at beta.corp.invoca.ch
This is on a 64 core "AMD Opteron(tm) Processor 6282 SE" server but I also
got the same low entropy on an EL9 KVM guest running on a "AMD
2022 Jun 01
2
Update RPM GPG key for EL9
Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
# rpm --import RPM-GPG-KEY-nwra
error: RPM-GPG-KEY-nwra: key 1 import failed
gpg key info:
sec rsa2048/35DDB0B86218AC2F
created: 2017-08-16 expires: never usage: SC
trust: ultimate validity: ultimate
ssb rsa2048/6A7FBC1E9DB22E8E
created: 2017-08-16 expires: never usage: E
Can someone
2022 Jun 01
2
Update RPM GPG key for EL9
On 6/1/22 13:43, Fabian Arrotin wrote:
> On 01/06/2022 19:51, Orion Poplawski wrote:
>> Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
>>
>> # rpm --import RPM-GPG-KEY-nwra
>> error: RPM-GPG-KEY-nwra: key 1 import failed
>>
>> gpg key info:
>>
>> sec? rsa2048/35DDB0B86218AC2F
>> ????? created: 2017-08-16?
2023 Mar 02
1
EL9/udev generates wrong device nodes/symlinks with HPE Smart Array controller
Simon Matter <simon.matter at invoca.ch>
> 2) some symlinks created by udev are just wrong and therefore very
> dangerous to use:
> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda
> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdb1
> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2
I think it maybe caused by sd driver asynchronous
2023 Mar 02
1
EL9/udev generates wrong device nodes/symlinks with HPE Smart Array controller
Hi,
> Simon Matter <simon.matter at invoca.ch>
>> 2) some symlinks created by udev are just wrong and therefore very
>> dangerous to use:
>> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0 -> ../../sda
>> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part1 -> ../../sdb1
>> scsi-SHP_LOGICAL_VOLUME_500143801722C0B0-part2 -> ../../sdb2
>
> I think it