Package: fwupdate-amd64-signed
Version: 12+2
Severity: normal
=== >8 ===
Setting up fwupdate (12-2) ...
Installing fwupx64.efi to EFI system partition.
/var/lib/dpkg/info/fwupdate.postinst: 46: /var/lib/dpkg/info/fwupdate.postinst:
/usr/lib/fwupdate/cleanup: not found
Setting up gir1.2-nm-1.0:am
ation from you.
>
> I'm pretty sure that the bug you discovered is solved in the current
> mailman3/mailman3-web packages in Debian unstable/testing/stretch-
> backports.
>
> Cheers,
> jonas
>
> Am 15.03.2018 um 22:47 schrieb Jonas Meurer:
> > Hi Eric,
> >
&
w).
Take care Jonas, mailman hackers crew
On March 15, 2018 5:47:30 PM EDT, Jonas Meurer wrote:
>Hi Eric,
>
>Am 04.03.2018 um 04:59 schrieb Eric Côté:
>> Bug is still present.
>
>I did quite some testing of the mailman3 packages in the last days,
>using all possible database back
Package: mailman3-suite
Version: 0+20170523-11
Followup-For: Bug #891703
Hi,
Bug is still present.
Like I mentioned in my original report, "mailman3suite" is the user in
/usr/share/mailman3-suite/settings.py . I've had to hand edit it so my install
reads my DB settings in /etc/mailman3/mailman3
Hi (sorry for top posting)
I’m using Postgres, not SQLite. It uses the defaults set in settings.py . How I
can tell is that the user trying to log in to postgres is what is set in
settings.py, and *not* settings_local.py/mailman3-suite.py . I set different
things (user, db, pswd) there. If it
Package: mailman3-suite
Version: 0+20170523-10
Severity: important
Hi,
The default user is being read from the packaged settings.py instead of the
settings_local.py file symlinked to /etc/mailman3 .
I see error logs saying "mailmansuite" has no access, which is true since
that's not what I conf
Package: lvm2-dbusd
Version: 2.02.175-1
Severity: normal
Please add python3-udev to dependencies :).
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (1001, 'unstable'), (1000, 'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Arc
Package: src:linux
Version: 4.13.4-1
Severity: normal
Not running the kernel affected:
a) too many tolerable issues, constant journal spam with wpa_supplicant
and hung threads (will paste the kernel msg dump I had before)
b) issues with email now resolved (hopefully)
Sorry about this, but can't b
Cool, that's fine, thank you :).
On January 19, 2017 6:37:05 AM EST, Carsten Leonhardt wrote:
>Control: tags -1 - moreinfo
>Control: severity -1 wishlist
>Control: retitle -1 Please allow a dotfile to be used as configfile
>
>Hi Eric,
>
>thanks for your feedback. I'm setting the bug to severity "
Worked briefly, then I got busy with other things and moved on. I was hoping
that I could easily fix it, but alas no. However, except for that one issue
with config, it works quite well, Does The Right Thing, as expected.
I was hoping to contribute something more, but that I for another time for
Package: src:linux
Version: 4.7.2-1
Severity: grave
Justification: renders package unusable
Hello,
I spent 3 hours trying to make this work, and I couldn't. Network Manager sends
out an error -4,
and wpa_supplicant says "timed out", and using NM, it keeps trying, even though
other
devices are u
Package: inosync
Version: 0.2.1-1
Severity: normal
Tags: patch
line 134:
add:
if configfile.startswith("."):
configfile = configfile.strip(".")
right after the
if configfile.endswith(".py"):
Thanks,
Eric
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT
Hi,
My hosting provider had a major power outage in their area, and so when the
host came back up, the aria log had issues, so when I tried to start it, it
would write that in the error log. I removed the aria_log* and that other
aria_log_ file and it started successfully. I also ran an aria_ch
As I resolved it.
Sent from Blue Mail
Package: mariadb-server
Version: 10.0.16-1
Severity: important
"[ERROR] Aria engine is not enabled or did not start. The Aria engine must be
enabled to continue as mysqld was configured with --with-aria-tmp-tables"
Would have been nice to let people know in a NEWS file about the change. Now my
Source: phamm
Severity: normal
Hi,
New upstream version is 0.6.2, one in Debian is 0.5.18.
Thank you.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (1000, 'testing'), (500, 'unstable'), (400, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.14-1
16 matches
Mail list logo